Compare

Cloudflare vs KeyCDN

Cloudflare scores higher on the AgentReady, 98/100 against 45/100. They differ on 17 of the 41 signals. Which ones decides whether an agent can adopt them without a person watching.

What each one is

Cloudflare. One platform for your apps, agents, and workforce.

KeyCDN. KeyCDN is a high performance content delivery network built for the future, enabling users to deliver content to users at blazing fast speed with setup in minutes.

Where Cloudflare is ahead

Cloudflare passes clear canonical domain, llms.txt published, llms-full.txt / full agent docs, mcp discoverable and machine-readable metadata, and KeyCDN does not. That is discover, whether an agent can find the product at all without being told it exists.

It also holds understand: structured api reference. KeyCDN misses it.

And on adopt, cli available and mcp integration available. KeyCDN misses those.

Finally, on operate, agent compatibility verified. KeyCDN misses it.

Where KeyCDN is ahead

KeyCDN passes search discoverable, and Cloudflare does not. That is discover, whether an agent can find the product at all without being told it exists.

It also holds understand: authentication documented and limits / constraints documented. Cloudflare misses those.

And on adopt, no mandatory sales call, official typescript sdk and official python sdk. Cloudflare misses those.

Finally, on operate, canonical workflow succeeds and observable execution. Cloudflare misses those.

What neither does

Both fail public docs discoverable, openapi / spec quality, request examples provided, response examples provided, errors and status codes documented, programmatic credential creation, fast time to first request, copyable quickstart, structured, predictable output, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable. If your agent needs any of those, you will be building it yourself either way.

Score, pillar by pillar

The AgentReady splits into four pillars, scored separately, because a product can be easy to find and still impossible to adopt.

Discover. Cloudflare leads 100 to 47. Cloudflare misses search discoverable, public docs discoverable; KeyCDN misses clear canonical domain, public docs discoverable, llms.txt published, llms-full.txt / full agent docs, mcp discoverable, machine-readable metadata.

Understand. Cloudflare leads 92 to 38. Cloudflare misses openapi / spec quality, authentication documented, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented; KeyCDN misses structured api reference, openapi / spec quality, request examples provided, response examples provided, errors and status codes documented.

Adopt. Cloudflare leads 100 to 60. Cloudflare misses no mandatory sales call, programmatic credential creation, fast time to first request, copyable quickstart, official typescript sdk, official python sdk; KeyCDN misses programmatic credential creation, fast time to first request, copyable quickstart, cli available, mcp integration available.

Operate is whether an agent can run against it in production and recover when a call fails. Cloudflare leads 100 to 35. Cloudflare misses canonical workflow succeeds, structured, predictable output, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable, observable execution; KeyCDN misses structured, predictable output, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable, agent compatibility verified.

Pricing

Cloudflare starts at $0/mo and has a free tier. KeyCDN starts at $4/mo with no free tier.

Signal by signal

Which to pick

Cloudflare clears more of the signals an agent needs, so it is the safer default for unattended use. Full profiles: Cloudflare and KeyCDN. Alternatives to each: Cloudflare, KeyCDN.

An agent can fetch this as data: POST /v1/compare {"slugs": ["cloudflare", "keycdn"]}