Fanful agent setup

One place for agents to start.

Paste the setup prompt into any AI coding agent. It points the agent to Fanful MCP, API manifests, CLI docs, skills, webhook recipes, SDK planning notes, and the safety boundaries for confirmed writes.

Open setup prompt API reference Skills

Quick setup

Already have an agent?

Give it this prompt URL first, then let it decide whether to use MCP, direct HTTP, the CLI, or docs-only guidance.

https://fanful.net/agent-setup/prompt.md

curl -fsS https://fanful.net/llms.txt
curl -fsS https://fanful.net/api/agent/action-contracts
curl -fsS https://fanful.net/api/agent/workflow-triggers
curl -fsS https://docs.fanful.net/api.md
curl -fsS https://docs.fanful.net/skills.md

Point the agent here

Use the setup prompt as the first instruction for Codex, Claude, ChatGPT, Cursor, or another coding agent.

Prefer machine contracts

Use MCP, HTTP manifests, action contracts, and markdown mirrors instead of scraping dashboard UI.

Keep secrets out of prompts

Bearer tokens, admin credentials, webhook signing secrets, Stripe ids, and raw listener ids belong in transport headers or environment variables.

Confirm before writes

Mutations require exact confirmation text, idempotency, stale-state guards when relevant, reason, and audit correlation.

All routes

Where agents should go next.

llms.txt

MCP endpoint

Public Streamable HTTP MCP endpoint for network clients.

API reference

Human-readable API map, auth model, recipes, and code examples.

API markdown

Compact model-readable API reference mirror.

Agent skills

Copyable Fanful skills/prompts for coding agents.

Agent skills markdown

Model-readable skill catalog and prompt blocks.

Developer docs

Task-first docs for humans and agents.

llms.txt

Canonical discovery file for AI agents and crawlers.

Action contracts

Shared confirmation, audit, idempotency, and redaction rules.

Workflow triggers

Signed webhook event catalog, subscription registry, and delivery boundaries.

CLI docs

Current Fanful CLI commands layered on the shared agent contracts.

Webhook payloads are signed event notifications. Agents should verify signatures, dedupe by event/idempotency key, and read linked manifests before taking action.