Your first agent action in 5 minutes

Create an API key, connect Claude or Cursor over MCP, and have your agent schedule a real post and read back how your posts did — end to end.

seenpaid is built to be driven by an AI agent. In five minutes you’ll go from nothing to your agent scheduling a real post and answering a real question about your account — no dashboard required. Here’s the whole path.

You’ll need a seenpaid account with at least one connected channel. New here? Run the getting-started journey first, then come back. Revenue questions additionally need attribution switched on and a revenue source connected.

Step 1 — Create an API key

1. Open the API settings

   Go to Settings → AI agents & API in the dashboard.

2. Create a key

   Click Create API key, name it (e.g. claude-agent), and copy the secret. It starts with sp_ and is shown once — store it safely. If you lose it, revoke it and make a new one.

The key is scoped to one workspace. An agent using it can act on that workspace’s data and nothing else. Full detail: API keys.

Step 2 — Connect your agent over MCP

Point your MCP client at seenpaid’s endpoint with the key as a Bearer token.

Claude Code

claude mcp add --transport http seenpaid https://api.seenpaid.com/mcp \
  --header "Authorization: Bearer sp_YOUR_KEY"

Claude Desktop / Cursor (JSON)

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

Put this in claude_desktop_config.json (Claude Desktop) or ~/.cursor/mcp.json (Cursor), then restart the app.

“Connected” means your client lists seenpaid’s tools. In Claude Code, run /mcp to confirm. You should see tools like schedule_post, validate_post and list_accounts.

Step 3 — Schedule something real

Now just talk to your agent in plain language. Try:

“Which accounts do I have connected? Then schedule ‘Testing my new setup — hello from seenpaid’ to the first one for tomorrow at 9am.”

The agent calls list_accounts, then schedule_post, and tells you what it queued. No tool names, no dashboard. Check Calendar in the dashboard if you like; the post is there.

Then push it further:

“Will this caption post cleanly to X, LinkedIn and Instagram? And how did last week’s posts do?”

That’s validate_post and a read of your engagement, driven from one sentence. With revenue attribution on, “Which of my posts made the most money this month?” works the same way through get_top_posts.

What just happened

You gave an agent a scoped key, connected it to seenpaid’s 50 tools over MCP, and it read your account and scheduled a post — the same org-scoped services the dashboard uses. From here the agent can run the whole loop: plan, validate, publish, read the results, and double down.

Where to go next

Prompt library

Ready-to-use prompts for publishing, results, automation and money.

Tools reference

All 50 tools, grouped, with inputs and outputs.

If a call returns 401 Unauthorized, the key is missing, mistyped, or revoked — check the Authorization: Bearer sp_... header. More cases in MCP server → Errors.