# Buffer: L1 · Needs a person As of 6 Oct 2026, an AI agent can't use Buffer on its own: hCaptcha puzzle on the sign-up form. Source: https://agentdrives.com/tools/buffer?via=md · driven 6 Oct 2026 by AgentDrives's agent · Same level in 4 drives in a row · Rules of 15 Oct 2026 (https://agentdrives.com/method/rules?via=md) · license CC BY 4.0 Needs a person to get in: L1 · Needs a person. Sign-up stops our agent first, at auth.buffer.com, where clicking Sign Up shows a visible hCaptcha puzzle; no API or CLI route around it, so no account, no key, no verification mail. Buffer ships a GraphQL API, an official MCP server, a CLI and Markdown docs with agent setup guides, but without a key none of it could be driven: unauthenticated calls return 401. Pricing needs a card under Billing Method once a person is in; the trial-without-card claim from the FAQ was not confirmed. No checkout, cancel or delete path was reached. _Written and checked by our agents from this drive's record. How we write: https://agentdrives.com/method?via=md#notes_ L1 · Needs a person: There is an API, CLI or MCP server, but an agent can't get in on its own: a person has to sign up, verify or make the key. What it does once a person sets it up shows next to the level. - Find: Some docs for agents (llms.txt and an MCP server) - Access: Can't sign up - Use: Work not reached - Pay: Payment not reached - Leave: Leaving not reached - Next: let an agent sign up on its own - With an account set up by a person: not measured yet. ## Level history - 1 Oct 2026 (3 drives): L1 · Needs a person - 6 Oct 2026: L1 · Needs a person ## Part scores - Agent-ready setup: llms.txt found, OpenAPI not found, MCP server found, CLI found - Not measured in this drive: Holds up, Docs match ## Who gets in - Agents on a server: Stopped by a CAPTCHA on the sign-up form. - Signed agents: The sign-up page opens. The CAPTCHA on the form stops them too. - Agents in a person's browser: Not measured yet. Sign-up page checked 12 Oct 2026. Signed agents: the ones Cloudflare verifies. ## Checkpoints - **Docs**: Headless: developers.buffer.com/llms.txt, guides as .md URLs, CLI, MCP and Agent Setup guides. - **Sign up**: Needs a human: Web-only sign-up at auth.buffer.com; clicking Sign Up shows a visible hCaptcha puzzle. No API/CLI sign-up route. - **Verify**: Not reached: No account was created, so no verification mail. - **Key**: Not reached: API keys only in the web app (Settings > API); OAuth PKCE/DCR needs a logged-in human to consent; no device flow. - **First call**: Not reached: No credential; unauthenticated GraphQL and MCP calls return 401. - **First action**: Not reached: No credential. - **Pay**: Not reached: No 402, no x402/MPP, no billing API. Pricing FAQ: card only, payment details entered under Billing Method in the account; 14-day trial without a card per the FAQ (not confirmed). The account needed to buy sits behind an hCaptcha puzzle a human must solve; checkout not seen. - **Cancel**: Not reached: No plan started; no cancel or billing operation in the API or CLI. - **Delete**: Not reached: No account to delete; no account-deletion mutation in the API schema or CLI. ## Does Buffer have an MCP server, and can an agent connect to it? Yes. Buffer has an official MCP server. The server is hosted and 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. ## How does an AI agent get a Buffer API key? Not reached: in the drive of 6 Oct 2026, sign-up stopped our agent first (it needs a person). API keys only in the web app (Settings > API); OAuth PKCE/DCR needs a logged-in human to consent; no device flow. ## Paying the agent way Payment not reached. Ways to pay it offers an agent: Card checkout. No card needed to start. What would let agents pay on their own: - Accept x402 or MPP on your API: Answer an unpaid call with 402 and a payment challenge, so an agent pays per call or buys credits without an account or a card. - List your plans on Stripe Projects: Agents buy a plan with `stripe projects add`, paid with a token under a spend cap the owner sets (projects.dev). From the drive of 6 Oct 2026. ## What an agent can do - Read Buffer's API docs, guides and pricing as Markdown - Introspect the GraphQL schema without an account - Install the Buffer CLI and validate post payloads with --dry-run without an account ## What it cannot do - Create a Buffer account: Sign-up form shows a visible hCaptcha puzzle - Get an API key or OAuth token: Keys are created only in the logged-in web app; OAuth needs a human consent - Schedule, edit or delete posts, capture ideas, read metrics: No account or credential - Delete the account headless: No account-deletion operation in API or CLI ## Tips for the owner 1. Let verified agents sign up 2. Issue API keys without the web UI 3. Support CIMD client registration 4. Answer server/discover with supported versions 5. Add account delete and billing to API 6. Document 401 status for auth errors Is this your product? Claim it free and reply next to the result, or get a Drive ($49) for your private report: https://agentdrives.com/pricing?via=md#drive. Fixed something? Order a Drive ($49) any time, or the Monthly drive ($29/month). ## Also in Social media scheduling - [Postiz](https://agentdrives.com/tools/postiz.md?via=md): L2 · Gets in · [Buffer vs Postiz](https://agentdrives.com/compare/buffer-vs-postiz?via=md) - [Publer](https://agentdrives.com/tools/publer.md?via=md): L1 · Needs a person · [Buffer vs Publer](https://agentdrives.com/compare/buffer-vs-publer?via=md) - [Typefully](https://agentdrives.com/tools/typefully.md?via=md): L1 · Needs a person · [Buffer vs Typefully](https://agentdrives.com/compare/buffer-vs-typefully?via=md) - [Later](https://agentdrives.com/tools/later.md?via=md): L0 · Read-only ## Tips for agent builders - Have a human create the account and an API key at publish.buffer.com/settings/api; then use the CLI (BUFFER_API_KEY) or MCP at https://mcp.buffer.com/mcp with a Bearer key. - GraphQL introspection works without a key: use `buffer schema describe posts create` and --dry-run to build payloads first. - Free plan API: 1 key, 100 req/15 min, 250/day, 3,000/30 days (docs). - Auth errors are HTTP 401 despite the docs saying 200.