Markdown for Agents leaves beta with analytics and request tracing

Cloudflare’s Markdown for Agents, the feature that converts a page to markdown when a client sends Accept: text/markdown, is now generally available with a set of observability tools built for it.

The dashboard gets an Analytics tab showing conversion outcomes, estimated token reduction, top converted pages, top user agents, and failure reasons, alongside sampled Logs you can filter by outcome or content-limit hits. A Playground lets you request the markdown for a page on your zone and compare it against the HTML, with the estimated token reduction shown inline. The same data is queryable through the GraphQL Analytics API via markdownForAgentsAdaptiveGroups, covering conversion totals, outcomes and token savings over the last seven days. Cloudflare Traces also gains a markdown_conversion span, recording input and output bytes, converter CPU time and content-limit flags for sampled conversions.

Why it matters: until now, turning this on meant trusting it worked. If you’re serving markdown to crawlers and coding agents to cut their token usage, you can now see which pages are actually converting, how much that is saving, and debug the ones that are failing or getting truncated, without guessing from your origin logs.