AgentsReady
Verified deep dive · Devtools

Cloudflare

Run the agent liveReport a change
1 minTime to key
YesNo-human path
0Gates to a test key
10/10Onboarding score
Live keys only:CAPTCHACard before first callEmail verification

Fastest path to a key

  1. zero-account: `npx wrangler deploy --temporary` provisions a temporary account, issues Wrangler an API token and prints a claim URL (60-minute lifetime). No human needed
  2. permanent account (fastest): `stripe projects init` / `stripe projects add cloudflare/...`: Stripe acts as IdP and provisions the Cloudflare account + API token; human accepts ToS (and confirms payment only if needed)
  3. CAPTCHA
    or classic: sign up at dash.cloudflare.com (email + password, Turnstile, email verification), then `wrangler login` (OAuth browser, scope selection)
  4. API token: dashboard > My Profile > API Tokens (user) or Manage Account > API Tokens (account-owned), template or custom permissions
  5. MCP: `claude mcp add --transport http cloudflare https://mcp.cloudflare.com/mcp` then OAuth, or pass an API token as bearer
  6. Working API key

Biggest gap

The classic dashboard signup is still behind a JS challenge, Turnstile and email verification, and the many separate product MCP servers fragment discovery (mitigated by the unified mcp.cloudflare.com)

Worth copying

`wrangler deploy --temporary`: a temporary account + scoped token + claim URL, advertised by the CLI itself when an agent is unauthenticated

Sources (9) · checked 2026-10-11
92Readiness score / 100
L4 Agent-nativeBeats 98% of 1,846 companies
Access20/20
Context20/20
Interfaces32/32
Onboarding14/19
Trust6/9
llms.txt · root
MCP · https://mcp.cloudflare.com/mcp
OpenAPI · https://www.cloudflare.com/openapi.json

Biggest gains

  1. +5 Self-serve API keys. Show how to create a key on the first docs page. No sales call.
  2. +3 Public status page. Link a status page so agents can tell outages from bugs.
All 20 checks
  • PASSAgents get the real page, not a bot wall10
  • PASSrobots.txt lets user-triggered agents in6
  • PASSContent is server-rendered4
  • PASSllms.txt exists8
  • PASSllms-full.txt exists3
  • PASSDocs available as markdown6
  • PASSSitemap2
  • PASSStructured metadata1
  • PASSPublic developer docs4
  • PASSMachine-readable API spec8
  • PASSRemote MCP server for the product12
  • PASSDocs MCP or searchable docs4
  • PASSSDKs and a CLI4
  • PASSOAuth discovery metadata5
  • PASSAgents can self-register OAuth clients6
  • FAILSelf-serve API keys5
  • PASSFree tier or test mode3
  • PASSAgent manifests4
  • PASSsecurity.txt2
  • FAILPublic status page3

Your fix pack: 3 changes, up to +8 points

Each change is ready to paste, filled in for cloudflare.com, with a command to check it worked. Or hand the whole list to your coding agent.

We couldn't find documented self-serve API keys. If getting a key needs a sales call, agents stop there.

Where: https://docs.cloudflare.com/authentication, linked from llms.txt
## Get an API key

1. Sign in at <dashboard URL> with Google or GitHub.
2. Open **Settings > API keys** and click **Create key**. Pick a scope (read-only or full).
3. Copy the key; it's shown once.

```bash
export CLOUDFLARE_API_KEY="..."
curl https://cloudflare.com/v1/<endpoint> -H "Authorization: Bearer $CLOUDFLARE_API_KEY"
```

**For AI agents:** run `<cli> login` to create a scoped key in the browser, or use a test key that needs no card.

Add the badge to your README

AgentsReady badge for cloudflare.com
[![AgentsReady](https://agentsready.dev/badge/cloudflare.com)](https://agentsready.dev/c/cloudflare.com)