Skip to content
Methodology

Agent content contracts

ia.agent-content-contracts · 1.12

Read MAY Recommendation AR-READ-11 AR-ACT-01

Why it matters

Agents need concise, stable contracts for high-friction product questions before they can act safely. auth.md explains authentication flows and token handling. pricing.md explains plan and billing constraints without forcing agents to scrape marketing pages.

How to fix it

Publish /auth.md and /pricing.md when the site has sign-in or paid plans.

  1. Write /auth.md with the auth flow, the scopes and the token lifetime.

    # Authentication

Use OAuth 2.0 authorization code with PKCE S256.
Scopes: read, write.
Tokens expire after 1 hour.

  2. Write /pricing.md with each plan, its price, its limits and the billing period.

    # Pricing

| Plan | Price | Limit |
|---|---|---|
| Free | 0 EUR | 100 calls/day |
| Pro | 29 EUR/month | 10,000 calls/day |

  3. Link both files from llms.txt.

Verify

curl -sf https://{domain}/pricing.md

Expected: HTTP 200 with a Markdown body (run the same command for /auth.md)

Run a new scan for this checkpoint:

isagentready results {domain} --checkpoint ia.agent-content-contracts
Details Mapping, lifecycle and references
AR mapping
Partial match
Score role
Bonus
Introduced
2026-08-24
Methodology version
2026-10-22

Checkpoint data (JSON)