AI agent signup for social media API and MCP access
A dedicated path for AI agents that need to activate paid API access, hand the user to checkout, create scoped follow-up keys when authorized, connect social accounts through browser OAuth, and report progress along the way.
Always keep a human in the loop when using AI agents to sign users up.
Visiting as a user?
Copy the handoff prompt, paste it into your AI chat, and let it guide checkout, payment status, password setup, API key handoff, and the first social account connection.
Copy this into your AI agent
Agent-readable handoff prompt
This prompt is visible in the page HTML and markdown so agents can read it directly. Humans can use the button to copy it into Claude, ChatGPT, Cursor, or another AI client.
I want you to set up Posterly for me as my AI social media scheduling agent. Use Posterly's agent signup flow: 1. Start here: https://www.poster.ly/agents/signup 2. If you have the Posterly MCP server installed but no Posterly API key yet, call get_agent_signup_info, then call start_signup with my email address, the Starter plan, and api_addon=true. 3. If you can call external APIs instead, call POST https://www.poster.ly/api/v1/signup with my email address, the Starter plan, and api_addon=true. 4. Send me the returned checkout_redirect_url so I can pay securely in my browser. Use checkout_url only if you preserve the complete Stripe URL including any # fragment. 5. Poll get_signup_session or the returned poll_url and keep telling me what is happening: checkout pending, payment confirmed, password required, authorization ready, or agent access required. 6. Do not ask me for card details, my Posterly password, or any social media password. Posterly handles those in the browser. 7. If the status is agent_access_required, ask me to copy the Posterly setup instructions from the dashboard into this AI chat or install the Posterly MCP connection. Posterly creates or shows the first dashboard API key only after billing access is active. Do not continue until Posterly is available to you. 8. Once you are authenticated with a dashboard-created Posterly API key, run whoami. If I explicitly confirm I want a separate scoped key for this AI, call create_api_key or POST /api/v1/api-keys with confirm=true and only the scopes you need. This is optional; do not try to mint keys before payment, from OAuth tokens, or from managed assistant tokens. 9. Once you have Posterly access, ask me which social account I want to connect first. 10. Create a Posterly connect session for that platform, send me the secure connect_url, and poll the connect session until the account is connected. 11. After the first account is connected, help me schedule my first post. 12. When a post is created, send me the returned View in Posterly link and avoid narrating raw curl, HTTP, JSON, or implementation details unless I ask for debugging. If you cannot call external APIs or MCP tools directly, guide me through the same flow using the Posterly pages and ask me for the next browser step when needed.
MCP tools or API endpoints, one continuous conversation
Agents call MCP tools or the public API in sequence: signup, signup polling, optional scoped key creation, connect, connect polling. Posterly handles checkout, password setup, OAuth, and credential flows in the user's browser.
MCP start_signup
Start paid signup
Agents with Posterly MCP installed can start signup before an API key exists, receive checkout_redirect_url and poll_url, then keep the user updated in chat.
MCP get_signup_session
Poll signup progress
Agents report checkout, payment, password, and authorization status while Posterly handles browser steps. Raw responses are only needed when debugging.
MCP create_api_key
Optional scoped agent key
After paid setup and explicit confirmation, an authenticated agent can create a scoped follow-up key from a dashboard-created API key.
POST /api/v1/connect/{platform}/sessions
Create a connect session
After the agent has Posterly access, it asks which social account to connect and creates a short-lived OAuth handoff.
GET /api/v1/connect/sessions/{id}
Poll clear progress
Agents poll the session and report what is happening: opened, awaiting provider approval, connected, failed, cancelled, or expired.
Machine-readable for agents, clear for users
Agents get explicit endpoints and status fields. Users get normal checkout, normal posterly login, one-time API key display, and normal provider OAuth screens.
1. MCP start_signup or POST /api/v1/signup -> checkout_redirect_url + poll_url 2. MCP get_signup_session or GET poll_url while the user pays and sets a password -> status: checkout_pending | payment_confirmed | password_required | agent_access_required 3. User gives Posterly access to the trusted AI -> paste setup instructions, install MCP, or complete OAuth handoff 4. Optional create_api_key or POST /api/v1/api-keys -> scoped follow-up key after confirm=true 5. Agent asks: "which social account should I connect first?" 6. POST /api/v1/connect/instagram/sessions -> connect_url + poll_url 7. Open connect_url for the user -> user approves provider OAuth in browser 8. GET connect poll_url -> status: connected 9. create_post -> scheduled post + View in Posterly link
The boundaries are intentional
This flow is designed so agents can orchestrate setup without becoming a payment processor, password collector, or OAuth proxy.
- Payment is required for API access.
- Provider OAuth stays in the user browser.
- Agents never collect card details or provider passwords.
- The first API key is created or shown only after paid access is active.
- Extra scoped keys require explicit confirmation and an existing dashboard-created key.
- Connection sessions expire after 30 minutes.
Use /agents/signup as the agent-facing signup URL
Agents can crawl this page, discover the API contract, and hand users into the paid posterly setup flow before using scoped keys and social account handoffs.