seenpaid docs

How seenpaid works

seenpaid is the revenue layer for social posting. You (or your AI agent) publish to 21 platforms; seenpaid tracks every link and matches sales back through your Stripe — so you know, to the dollar, which posts actually made money. It keeps going after “posted.”

These docs cover connecting your accounts, wiring seenpaid into an AI agent over MCP, and reading your revenue back out through the API.

How it works

1. Publish. Post from the dashboard or have your agent schedule it. Every link in the post (and your bio link) is wrapped with a tracked short link.
2. Track. When someone clicks, seenpaid records the click and attaches a first-party attribution cookie — no ad tracking, no third parties.
3. Match. When a sale lands in your Stripe, seenpaid matches it back to the exact post that drove it and records the revenue.
4. Rank. Your dashboard (and your agent) can then rank every post by the money it made.

Quickstart

1. Create an account and start your free trial.
2. Connect at least one social account.
3. Connect your Stripe so sales can be matched (seenpaid only reads it and never moves money).
4. Publish a post — or ask your agent to.
5. Open Revenue to watch clicks and sales roll in.

Tip: click your own tracked link once to confirm tracking is live — the first real click unlocks your analytics.

Connect your socials

In Connections, pick a platform and complete its OAuth flow. seenpaid supports 23 connectable channels including X, LinkedIn, Bluesky, Mastodon, Threads, Instagram, Facebook, TikTok, Pinterest, Tumblr, Telegram, Discord, Slack, and the blogging tier (WordPress, Ghost, Medium, Dev.to, Hashnode). Scheduling and the visual calendar are included on every plan.

Connect Stripe

seenpaid connects to your existing Stripe over Stripe Connect. Stripe’s standard connection asks for read-and-write access, so that is what Stripe’s consent screen shows you; seenpaid only reads payments to match them to your posts. There is no code in seenpaid that charges, refunds or pays out. Connect it once from Revenue → Connect Stripe.

AI agents & MCP

seenpaid ships a hosted MCP (Model Context Protocol) server, so any MCP client — Claude, ChatGPT, Hermes, Cursor, Codex — can drive seenpaid directly. Add the endpoint and your API key to your client’s config:

{
  "mcpServers": {
    "seenpaid": {
      "url": "https://api.seenpaid.com/mcp",
      "headers": {
        "Authorization": "Bearer sp_your_api_key"
      }
    }
  }
}

Restart your client and your agent can now schedule posts and read your revenue. Ask it things like “schedule this thread to X and LinkedIn for Tuesday 9am” or “which of my posts made the most money?”

Hermes agent

Running Hermes, the autonomous agent that lives in Telegram, Discord and Slack? It speaks MCP natively — add seenpaid to ~/.hermes/config.yaml and it can post and read revenue from any chat:

mcp_servers:
  seenpaid:
    url: "https://api.seenpaid.com/mcp"
    headers:
      Authorization: "Bearer sp_your_api_key"

Then just message it — “post my new launch thread across everything at 9am and tell me which one earns” — and Hermes drives seenpaid for you.

MCP tools

The server exposes 50 tools — the same surface the dashboard runs on, spanning publishing, revenue attribution, experiments, autopilot and forecasting. Here are the ones you’ll reach for first:

See the full 47-tool reference for the rest — revenue, experiments, autopilot, recycle and more.

API & keys

Prefer raw HTTP? Every one of the 50 tools is callable over plain JSON-RPC at /mcp — no MCP client needed. Generate a key (prefixed sp_) in Settings → API and pass it as a bearer token:

curl -X POST https://api.seenpaid.com/mcp \
  -H "Authorization: Bearer sp_your_api_key" \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0", "id": 1, "method": "tools/call",
    "params": { "name": "get_top_posts", "arguments": { "limit": 5 } }
  }'

Keep your sp_ key secret — it has full access to your workspace. Rotate it anytime from Settings.

The dashboard's own REST surface is documented as an OpenAPI 3.1 spec at /openapi.json — real paths and request/response shapes, plus every MCP tool listed as an x-mcp-tools extension. Those routes authenticate with a session token rather than an sp_ key; for key-based automation use /mcp above.

Support

Stuck on something? Email support@seenpaid.com or start from the AI agents guide. Ready to try it? Start free.