agentspeed.
Rubric / Readability

Markdown negotiation

readability.markdown_negotiation
weight 1deterministicemerging

Requests with `Accept: text/markdown` return a markdown representation of the page (Markdown content negotiation).

Adoption of what this check tests is still climbing, so failing it is an opportunity rather than a defect. Remediation lists rank these after established fixes, and the weight moves only when measurement earns it.

Definition
Check ID
readability.markdown_negotiation
Category
Readability
Weight
1
Counts toward the score
Yes.
Evaluated by
A fixed rule with no threshold of our choosing. The same input always produces the same verdict.
Standard maturity
emerging
Canonical spec
https://www.rfc-editor.org/rfc/rfc7763.html
Introduced in
r2026.04.2
Retired in
Still active.
History
Every change to the instrument— including the versions that changed this check
Machine-readable
/rubric.json— this check, and every other, as data
How often this check is right

No rate published. Too few labelled cases to publish a rate: 1 flagged case (30 needed to publish), 1 defective case (30 needed to publish). The counts are the honest answer here. The matrix behind readability.markdown_negotiation is 2 labelled cases — reported here rather than turned into a percentage that would read as more certain than the evidence is.

Corpus v1, measured under rubric r2026.11.0. Full method and every other check at /rubric/accuracy.

How to fix it
Serve a markdown variant of your primary content when the request `Accept` header includes `text/markdown`. Agents prefer markdown over HTML for summarization and citation.
Does your site pass this check?

Free scan, 30 seconds, no signup — this check and the other 35, with the exact evidence for each verdict.

Scan my site →
Markdown negotiation · readability.markdown_negotiation · AgentSpeed