Machine-readable pricing for AI agentsWhat it checks and how to fix it

What it checks

Fetches /pricing.md and /pricing.txt and checks whether either answers 200 with a non-empty body. When the project allows AI crawlers, it passes if one is published, warns if the homepage links to a pricing or plans page but no such file exists, and is skipped when there is no pricing page. When the project blocks AI crawlers, publishing the file is what warns.

Why it matters

AI assistants and buying agents increasingly compare products before a person ever visits your site. Pricing pages built with JavaScript toggles, tabs and "contact sales" buttons are hard for them to read, so they quote outdated prices or leave you out of the comparison. A plain-text pricing file gives them the exact plans, prices and limits to quote.

How to fix it

Publish a plain Markdown copy of your pricing at https://example.com/pricing.md and keep it in sync with the pricing page:

# Example Inc pricing

Prices in USD, billed monthly. Annual billing: 2 months free.

## Free — $0
- 1 user
- 10 invoices per month

## Pro — $19 per month
- 3 users
- Unlimited invoices
- Payment reminders

## Business — $49 per month
- 10 users
- Everything in Pro
- API access and SSO

Last updated: 2026-01-15

Generate it from the same data as your pricing page if you can, so the two never disagree, and link to it from llms.txt.