Typefullytypefully.comCan an AI agent use Typefully?
As of 6 Oct 2026, an AI agent can't use Typefully on its own: Cloudflare Turnstile on email sign-up.
Level 1 · Needs a personAgents can't get in on their own.
- Find: Docs for agents: llms.txt, an OpenAPI and an MCP server.
- Access: Can't sign up.
- Use: Work not reached.
- Pay: Payment not reached.
- Leave: Leaving not reached.
To reach L2 · Gets in: let an agent sign up on its own.
With an account set up by a person: not measured yet.
What the levels meanDriven 6 Oct 2026Same level in 2 drives in a rowRules of 15 Oct 2026Claim this page
Written and checked by our agents from this drive's record. How we write.
Who gets in
- Agents on a serverTurned away when they send the sign-up form.
- Signed agentsThe site opens. The check on the form still applies.
- Agents in a person's browserNot measured yet.
Sign-up page checked 13 Oct 2026. Signed agents: the ones Cloudflare verifies. Where agents come from
What an agent can do in Typefully.
On its own
- Read the full API documentation and technical specs without needing an account
- Find and inspect the AI-agent connection points (the MCP server and its login settings) without an account
What it can't, and why
- Create an accountA 'Verify you are human' check blocks the sign-up form to pass it
- Get an API key or login tokenKeys are only issued inside the website after logging in, which needs the blocked sign-up step
- Draft, schedule, queue, or publish any postNone of this works without a logged-in account
1 more
- Delete the accountNo account was ever created, and the documentation has no delete feature listed
Can an AI agent sign up for Typefully on its own?
No. Sign-up: needs a human. Email sign-up shows an interactive Cloudflare Turnstile ('Verify you are human'); submit never resolved and no request reached Typefully. Other options are Google/X/LinkedIn OAuth.
Does Typefully have an MCP server, and can an agent connect to it?
Yes. Typefully has an official MCP server. The server signs an agent in with OAuth.
A new agent can't get in on its own: in the drive of 6 Oct 2026, our agent stopped at sign up (it needs a person). Through the MCP server, 0 of our agent's 1 attempt worked.
What the drive found
APIOpenAPIMCP · official–CLI–SDKllms.txt–Webhooks–SandboxNot reached in this drive: the API key, deleting the account and paying. Every checkpoint, in detail
For the team behind Typefully.
Where agents stop in Typefully today, and the fixes that get them further, highest impact first.
Stops at sign up
The fixes, highest impact first
- Let signed agents through the sign-up checkStep-by-step guide
- Add a headless credential pathStep-by-step guide
- Document account deletion and add an API route
1 more fix
- Publish the MCP card at the draft location
- Claim it free and reply next to the result.
- A Drive, $49: your private report, with where agents stop, the evidence and the fixes that move your level.
- Fixed something? Order a Drive ($49) any time, or the Monthly drive ($29/month).
Details
Your API, MCP server or CLI is the product? An Audit ($299) also checks every documented route, MCP tool and CLI command against your docs. Compare plans.
Already claimed it? Open it in your dashboard.
Rather not be driven? Block AgentDrivesAgent in robots.txt or write to us. We stop driving it ourselves; this page stays, with its date.
Embed the badge on your site
Behind the level.
Our agent couldn't get into Typefully, so the work, its reliability and the crash test aren't measured. The part scores are what it could judge from the outside.
Part scores · level history · paid plans
Part scores
Agent-ready setup
- llms.txt: found
- OpenAPI: found
- MCP server: found
- CLI: not found
Not measured in this drive: Holds up, Docs match (part of an Audit).
Level history
- 2 Oct 2026L1Needs a person
- 6 Oct 2026L1Needs a person
Needs a paid plan
Not counted in the level.
| Capability | Plan |
|---|---|
| AI writing suggestions | Creator |
| Engagement analytics | Creator |
| Comments | Business |
| Team workspace | Business |
For agents and builders.
The drive as data, every checkpoint and all 27 attempts.
How an agent connects · 4 tips
/api/tools/typefully.json/tools/typefully.mdMCP get_tool {"slug":"typefully"}
- Have a human create the account and an API key; then use MCP https://mcp.typefully.com/mcp with Authorization: Bearer <key>.
- Read https://typefully.com/docs/api.md for the full reference in Markdown.
- publish_at 'now' is asynchronous: poll GET draft until publish_state is 'finished'; plan_at makes a dated draft that never auto-publishes.
- Media upload: PUT raw bytes to the presigned URL with no extra headers, or you get 403 SignatureDoesNotMatch.
Every checkpoint, in detail · 9 checkpoints
- DocsHeadlessllms.txt, /docs/api.md (Markdown, also via Accept: text/markdown with Vary: Accept), OpenAPI 3.1.0 at api.typefully.com/v2/openapi.json, ai-agents.md, RFC 9727 api-catalog
- Sign upNeeds a humanEmail sign-up shows an interactive Cloudflare Turnstile ('Verify you are human'); submit never resolved and no request reached Typefully. Other options are Google/X/LinkedIn OAuth.
- VerifyNot reachedNo sign-up went through, so no verification code mail.
- KeyNot reachedAPI keys are made in web Settings; OAuth AS offers only authorization_code (browser consent) with CIMD, no device flow, no agent registration. No account to get them from.
- First callNot reachedGET /v2/me -> 401 UNAUTHORIZED; MCP -> 401 with resource_metadata. No credentials.
- First actionNot reachedNo credentials.
- PayNot reachedNo 402, x402, MPP, UCP or other agent rail; x402./mpp./agents. subdomains fail TLS. Free plan exists (10 posts/month, API and MCP). Upgrade is Stripe Checkout behind login; not reached because sign-up was blocked, so is unconfirmed.
- CancelNot reachedNo plan started. The API has no billing operations.
- DeleteNot reachedNo account was created. The OpenAPI has no account-delete operation; the account-deletion route is unknown.
The attempt log · 27 attempts
| Capability | Route | Result | Evidence |
|---|---|---|---|
| llms.txt: GET /llms.txt | api | done ✓ | 200 text/plain, H1 # Typefully, links api.md, openapi.json, ai-agents.md, agent-skills index, MCP server card |
| robots.txt / aipref: GET /robots.txt | api | done ✓ | User-agent: * Disallow: /media-p/; Content-Signal: ai-train=yes, search=yes, ai-input=yes (Cloudflare Content Signals scheme, parses). No aipref Content-Usage line or header. |
| markdown docs: GET /docs/api with Accept: text/markdown, and /docs/api.md | api | done ✓ | Both 200 content-type text/markdown; charset=utf-8 with vary: Accept |
| OpenAPI: GET https://api.typefully.com/v2/openapi.json | api | done ✓ | openapi 3.1.0, info.version 2.0.0, 16 paths / 24 operations; also RFC 9727 /.well-known/api-catalog (application/linkset+json) |
| MCP server/discover: POST server/discover 2026-07-28 to https://mcp.typefully.com/mcp | mcp | blocked ✓ | 401 WWW-Authenticate: Bearer resource_metadata="https://mcp.typefully.com/.well-known/oauth-protected-resource", scope="full_access"; PRM 200 JSON, AS https://api.typefully.com |
| MCP server card / A2A / AI catalog: GET <mcp>/server-card, /.well-known/ai-catalog.json, /.well-known/mcp/server-card.json, agent-card.json, agent.json | api | partial ✓ | /.well-known/mcp/server-card.json 200 application/mcp-server-card+json (remotes streamable-http https://mcp.typefully.com/mcp); <mcp>/server-card 404 JSON; ai-catalog.json 404; agent-card.json 404; agent.json 404 |
| OAuth AS metadata: GET https://api.typefully.com/.well-known/oauth-authorization-server | api | done ✓ | 200 JSON: code grant + refresh, S256, token auth none, client_id_metadata_document_supported: true (CIMD), authorization_response_iss_parameter_supported true, no registration_endpoint, no device_authorization_endpoint, no agent_auth block |
| pay discovery: GET /.well-known/ucp, /auth.md, /SKILL.md, x402./mpp./agents. subdomains, unauth /v2/me | api | done ✓ | /.well-known/ucp 404; /auth.md and /SKILL.md 200 text/html SPA soft-404; x402./mpp./agents.typefully.com resolve to 216.150.1.1 but TLS fails (curl exit 35); /v2/me unauth 401 JSON {error:{code:UNAUTHORIZED}} no 402 |
| docs: read API reference and agent guide | api | done ✓ | https://typefully.com/docs/api.md 233 KB markdown; ai-agents.md describes MCP (OAuth or API key Bearer) and agent-skills repo |
| sign up: Sign up with email the agent's inbox (Continue with Email) | browser | blocked ✓ | Email modal: after submit, button spins and a visible Cloudflare Turnstile checkbox "Verify you are human" appears (shot 006.png); only POSTs were to challenges.cloudflare.com, no request to Typefully auth, no mail arrived in 60 s. No headless sign-up route in docs (API keys come from Settings). |
| sign up: Ask a human to sign up in their own browser (Cloudflare Turnstile) | none | blocked | |
| verify email: Read verification code mail | none | blocked | No sign-up request ever reached Typefully (Turnstile); inbox read an inbox --wait 60: no mail |
| API key / OAuth token: Get an API key or MCP OAuth token | none | blocked | Docs: "Generate your API key from your Typefully settings" (needs an account). OAuth AS offers only authorization_code (browser consent after Typefully login); no device flow, no agent_auth registration. No account because sign-up stopped at Turnstile. |
| first authenticated call: GET /v2/me and MCP server/discover without credentials | api | blocked ✓ | GET https://api.typefully.com/v2/me -> 401 application/json {"error":{"code":"UNAUTHORIZED","message":"Unauthorized"}}; MCP -> 401 with resource_metadata |
| buy a plan: Probe agent payment rails and checkout | none | blocked ✓ | No 402 anywhere (unauth API 401, MCP 401); no PAYMENT-REQUIRED / WWW-Authenticate Payment; /.well-known/ucp 404; x402./mpp./agents. subdomains fail TLS; API docs mention 402 only as "Account is paused or requires a paid plan" on draft create/edit. Pricing page: Free (10 posts/month, API+MCP), Creator (annual only), Business; "Get started" leads to sign-up. Not reached: sign-up blocked. |
| Compose a draft post or thread: Compose a draft post or thread in account | none | blocked | API/MCP return 401 without a key |
| Schedule a post: Schedule a post in account | none | blocked | API/MCP return 401 without a key |
| Queue posts into slots: Queue posts into slots in account | none | blocked | API/MCP return 401 without a key |
| Publish a post immediately: Publish a post immediately in account | none | blocked | API/MCP return 401 without a key |
| Cross-post to multiple platforms: Cross-post to multiple platforms in account | none | blocked | API/MCP return 401 without a key |
| Visual calendar: Visual calendar in account | none | blocked | API/MCP return 401 without a key |
| AI writing suggestions: AI rewrite of a draft | none | plan_gated ✓ | typefully.com/pricing: "AI writing features" listed under Creator ("All features in Free +"); no API/MCP route; also no account |
| Engagement analytics: View post analytics | none | plan_gated ✓ | typefully.com/pricing: "X analytics" listed under Creator; no API route |
| Comments: Comment and resolve on a draft | none | plan_gated ✓ | typefully.com/pricing: "Comments & Slack notifications" under Business |
| Team workspace: Share social set with team | none | plan_gated ✓ | typefully.com/pricing: "Teams, roles, permissions" under Business |
| cancel plan: Cancel/downgrade | none | skipped | No plan started (no account). No billing endpoints in the OpenAPI (24 operations, none billing). |
| delete account: Delete account and data | none | blocked | No account created. OpenAPI has no account-delete operation; only DELETE draft/comment routes. |
Also in Social media scheduling.
PostizL2Gets in on its ownTypefully vs Postiz
BufferL1Can't sign up on its ownTypefully vs Buffer
PublerL1Can't sign up on its ownTypefully vs Publer
LaterL0Can't sign up on its own