Agent Ready HTML

Alternatives to Cloudflare Markdown for Agents for agent-readable content

In short

Cloudflare Markdown for Agents lists 6 alternatives, among them Scrunch Agent Pages (AXP), Vercel markdown handling, Framer and others. Mintlify scores highest of them by share of the keys that apply, 15 of 16 against 5 of 10 for Cloudflare Markdown for Agents. The widest gap is llms.txt generation, where Mintlify scores 2 and Cloudflare Markdown for Agents 0 (mintlify.com).

These are the other edge or plugin products in the rubric, plus any platform Cloudflare Markdown for Agents is compared with directly. Each carries one sourced difference. Where a head-to-head exists, the sentence is its verdict-neutral difference; otherwise it is the key where the two scores are furthest apart, with the evidence behind the alternative's score.

  • Scrunch Agent Pages (AXP) Edge or plugin product, 3 of 10
    Cloudflare converts the origin HTML to markdown only when a request sends Accept: text/markdown and keeps JSON-LD; Scrunch routes recognised AI user agents to a separate optimised mirror on agentxp.net regardless of the Accept header and does not use llms.txt. Source, read 4 November 2026. Full comparison.
  • Vercel markdown handling Edge or plugin product, 8 of 16
    Cloudflare converts any HTML on a paid zone with one toggle and a 6 MiB limit; Vercel publishes a Next.js rewrite and route handler that the developer writes, which yields hand-made markdown instead of a generic conversion. Source, read 4 November 2026. Full comparison.
  • Framer Site builder, 10 of 14
    Framer serves markdown for every page on its own servers by default; Cloudflare adds the same behaviour to any origin on a Pro, Business or Enterprise zone. Source, read 4 November 2026. Full comparison.
  • Mintlify Docs platform, 15 of 16
    Mintlify produces markdown from the docs source, with components rendered as labelled blockquotes; Cloudflare converts rendered HTML generically and appends JSON-LD in a fenced block. Source, read 4 November 2026. Full comparison.
  • Firecrawl llms.txt generator Edge or plugin product, 3 of 6
    Firecrawl llms.txt generator scores 2 on llms.txt generation against 0 for Cloudflare Markdown for Agents. The product itself, from a crawl. Not test-built: it needs a Firecrawl account and API key. Score from the documentation page cited, read 2026-11-04. Source, read 4 November 2026.
  • Yoast and other WordPress llms.txt plugins Edge or plugin product, 3 of 8
    Yoast and other WordPress llms.txt plugins scores 0 on markdown on request against 2 for Cloudflare Markdown for Agents. Test build: Yoast added no markdown negotiation; Accept: text/markdown returned text/html. Source, read 4 November 2026.

Cloudflare Markdown for Agents itself: 5 of 10 on the rubric. Read its profile. Scores come from test builds and cited documentation read 4 November 2026; see the method.

Sources

  1. Ora: AgentReady launch post (rubric basis) https://ora.ai/blog/agentready-launch, read 4 November 2026
  2. Scrunch Agent Pages (AXP): documentation https://helpcenter.scrunchai.com/en/articles/12845899-how-axp-serves-content-to-ai-agents, read 4 November 2026
  3. Vercel markdown handling: documentation https://vercel.com/blog/making-agent-friendly-pages-with-content-negotiation, read 4 November 2026
  4. Framer: documentation https://www.framer.com/help/articles/make-site-readable-by-ai-agents/, read 4 November 2026
  5. Mintlify: documentation https://www.mintlify.com/docs/ai/markdown-export, read 4 November 2026
  6. Firecrawl llms.txt generator: documentation https://docs.firecrawl.dev/features/alpha/llmstxt, read 4 November 2026
  7. Yoast and other WordPress llms.txt plugins: documentation https://developer.yoast.com/features/llms-txt/functional-specification/, read 4 November 2026

Last reviewed 4 November 2026