The commercial legibility layer

Make your pricing readable to AI.

AI buyers, search agents, and procurement copilots need clear, machine-readable pricing to recommend you. pricing.md gives machines the commercial truth.

Try examples:

Built for AI buyers. Useful for humans.

AI systems summarize and compare offers.

Most pricing pages leave out critical facts.

Bad source material creates bad results.

The fix is simple: publish /pricing.md A clean, structured file that tells AI systems exactly what you sell, for how much, and under what terms. See the schema ->

Pricing crash-test lab

Watch a pricing page turn into machine-readable facts.

Model view

1 Your pricing page (raw)

pricing page

Simple pricing, built for scale

Everything you need to grow. No hidden fees.

Monthly Annual (save 20%)

Starter $29/mo

Growth $99/mo

Scale Custom

Unlimited projects	✓	✓	✓
Team collaboration	-	✓	✓
Advanced analytics	-	✓	✓
Priority support	-	-	✓
SLA	-	-	✓

2 AI buyer extracted

{
  "plans": [
    {"name": "Starter", "price": 29, "period": "month"},
    {"name": "Growth", "price": 99, "period": "month"},
    {"name": "Scale", "price": null, "period": null}
  ],
  "billing": {
    "intervals": ["month", "year"],
    "annual_discount": "20%"
  },
  "features": [
    "Unlimited projects",
    "Team collaboration",
    "Advanced analytics",
    "Priority support",
    "SLA"
  ]
}

Confidence: medium

3 Gaps and risks

Missing priceScale plan has no priceHigh
Missing periodAnnual pricing not specifiedHigh
Hidden limitsNo usage limits or capsMed
Unclear features"Advanced analytics" is vagueMed
Missing termsNo refund, SLA, or contract infoMed
No payment infoNo accepted methods or billing detailsLow

4 pricing.md (the fix)

---
title: Acme Pricing
currency: USD
intervals: [month, year]
annual_discount: 20%
---

## Plans
| Plan | Price | Interval |
| --- | ---: | --- |
| Starter | $29 | month |
| Growth | $99 | month |
| Scale | Custom | year |

## What's Included
- Unlimited projects
- Team collaboration
- Advanced analytics
- Priority support
- SLA

## Terms
- 14-day refund
- SLA: 99.9% uptime
- Payment: Card, ACH, Wire
- Contract: Standard Terms
- Overages: None

Legibility score

92/100

Excellent Highly readable to AI systems

Schema
Fields
Types
Examples

Audit score

62/100

Needs ImprovementYour pricing page leaves important commercial facts unclear or hidden from AI systems.

See all issues ->

At a glance

3Plans detected 7/16Facts captured 5Critical gaps HighRisk level

What this means

AI systems may misinterpret or omit key details about your offer.
You risk losing comparisons to competitors with clearer data.
Fixing is fast: publish a /pricing.md file and test again.

Next step

Generate your /pricing.md

Get a first draft file you can review, edit, and publish in minutes. Generate Now

Trusted by forward-thinking teams SaaS Founders RevOps Teams AI Agencies Product Marketers Procurement Leaders Growth Teams

How it works

A four-step audit loop for commercial source material.

pricing.md treats your pricing page like source code for buyer agents. The goal is not prettier markdown. The goal is a durable file that can be quoted, compared, routed, and checked.

Capture the offer

Start with the visible pricing page, sales deck, service menu, or billing notes buyers already see.

Extract the facts

Pull out plan names, prices, intervals, limits, usage meters, discount rules, payment paths, terms, and buyer-fit boundaries.

Expose ambiguity

Flag missing prices, hidden limits, unsupported claims, vague feature names, and terms that force AI systems to guess.

Publish the file

Ship /pricing.md, reference it from /llms.txt, and keep it updated whenever plans or terms change.

Why it matters

Pricing pages now have two audiences.

Human buyers scan for confidence.

They need packages, proof, fit, and a clear next step. If the page hides too much, they leave or ask sales to clarify basic facts.

AI buyers need structured facts.

They compare vendors from snippets, markdown, docs, scraped text, and cached summaries. If your offer is ambiguous, the generated recommendation becomes ambiguous too.

Procurement copilots need terms.

Billing cadence, renewal behavior, cancellation, refund windows, payment methods, security review, and procurement contact paths all affect whether a buyer can act.

RevOps needs a source of truth.

A maintained /pricing.md reduces drift across the website, sales copy, support answers, agent snippets, and AI-search summaries.

Checker

Score your pricing copy before an agent does.

The checker runs locally in the browser. Paste copy, a markdown file, or notes from a pricing page to see which commercial facts are missing.

Pricing page text or markdown

62/100

Agent-readiness

Needs Improvement

A buyer agent can infer the plan ladder, but prices, limits, terms, and action paths are still incomplete.

Generator

Draft a first `/pricing.md` from a messy offer.

This creates a reviewable source file from structured inputs. You still own the commercial, legal, and billing accuracy.

Generated markdown

Examples

Use the file shape that matches the way you charge.

Each example is a complete source file pattern, not a teaser. Copy the one closest to your model, then tighten the numbers and terms.

SaaS plans

Free, Pro, Team, Enterprise

Best for standard software plans with seats, feature tiers, support levels, procurement notes, and optional overages.

Plan prices and billing cadence
Seat, project, and usage limits
Upgrade, cancellation, and sales paths

Open file

Usage AI

Credits, runs, tokens, overages

Best for products where AI usage changes the bill and buyers need to know how credits are counted, reset, and capped.

Primary meter and included usage
Overage rules and premium routes
Abuse controls and billing exceptions

Open file

Services

Audits, sprints, retainers

Best for consulting, implementation, agency, or advisory offers where scope, timeline, exclusions, and fit matter as much as price.

Fixed-scope package menu
Timeline and deliverables
Fit rules and intake path

Open file

Schema

The minimum viable commercial schema.

The standard is intentionally plain markdown so teams can publish it quickly. The structure below is what the checker scores and what AI systems can quote reliably.

Block	Status	What belongs there
Metadata	Required	Title, owner, canonical source, currency, last updated date, contact.
Plans	Required	Plan names, prices, billing intervals, included features, buyer fit.
Limits	Required	Seats, credits, projects, storage, requests, support levels, reset rules.
Usage	Conditional	Meters, overages, premium routes, usage caps, abuse controls.
Terms	Required	Renewal, cancellation, refunds, taxes, contracts, payment methods.
Procurement	Recommended	Security review, invoice path, vendor forms, DPA, SLA, contact route.
Examples	Recommended	Representative customer scenarios and expected monthly or annual totals.
Change policy	Recommended	How pricing changes are announced and when old terms expire.

Canonical file skeleton

# Acme Pricing
Last updated: 2026-05-28
Canonical source: https://acme.com/pricing.md
Currency: USD
Contact: billing@acme.com

## Plans
| Plan | Price | Interval | Best for | Includes | Limits |
| --- | ---: | --- | --- | --- | --- |
| Starter | $29 | month | Individuals | Core features | 1 seat |
| Growth | $99 | month | Teams | Collaboration | 10 seats |
| Scale | Custom | annual | Enterprises | SLA, security | Contracted |

## Usage Rules
- Annual billing saves 20%.
- Credits reset monthly.
- Overage requires admin approval.

## Terms
- Refund window: 14 days.
- Cancellation: self-serve before renewal.
- Payment: card, ACH, wire.

## Action Path
Start self-serve or contact sales.

Pricing

Free standard, paid audits when accuracy matters.

The public checker, generator, docs, and examples are free. Paid services are fixed-scope when a team wants its actual offer audited, rewritten, and tested.

Self-serve

Public Toolkit

Guide to the /pricing.md file
Local browser checker
Markdown generator
SaaS, usage AI, and services examples

Use Toolkit

Fixed scope

Agent-Readable Pricing Audit

$750

Review of one pricing surface
/pricing.md and /pricing.txt draft
Offer clarity notes and missing-facts report
Buyer-agent summary test

Request Audit

Company site

AI-Readable Website Audit

$2,500

Pricing file plus llms.txt
Claims and proof inventory
Comparison prompts and action-path rewrite
Deployment guidance for static source files

Scope Website Audit

Implementation

Install Sprint

Custom

Files installed and tested
Structured offer rewrite
Agent-readable docs and before/after tests
Scope depends on site size and approval path

Plan Sprint

Docs

Publish once, keep it boring, update it when pricing changes.

The docs are designed for teams that need a working file today. Markdown is enough if the fields are explicit, stable, and linked from the right places.

Where to put files

https://yourdomain.com/pricing.md for the canonical markdown file.
https://yourdomain.com/pricing.txt for a plain-text fallback.
https://yourdomain.com/llms.txt with links to pricing, docs, security, and support source files.

Validation checklist

Every plan has a name, price, interval, buyer fit, and included limits.
Usage-based pricing defines meters, resets, caps, and overage behavior.
Terms include renewal, cancellation, refunds, taxes, payment methods, and contract paths.
The action path tells a buyer what to do next without guessing.

Maintenance rules

Update the file on the same day public pricing changes.
Keep old or grandfathered terms named separately when they still affect customers.
Use plain language over brand language for commercial facts.
Link evidence for claims that affect procurement or regulated buyers.

Open pricing.md Open pricing.txt Open llms.txt View source file Join the community

Make your pricing readable to AI.

Watch a pricing page turn into machine-readable facts.

Audit score

At a glance

What this means

Next step

A four-step audit loop for commercial source material.

Capture the offer

Extract the facts

Expose ambiguity

Publish the file

Pricing pages now have two audiences.

Human buyers scan for confidence.

AI buyers need structured facts.

Procurement copilots need terms.

RevOps needs a source of truth.

Score your pricing copy before an agent does.

Needs Improvement

Draft a first /pricing.md from a messy offer.

Use the file shape that matches the way you charge.

Free, Pro, Team, Enterprise

Credits, runs, tokens, overages

Audits, sprints, retainers

The minimum viable commercial schema.

Canonical file skeleton

Free standard, paid audits when accuracy matters.

Public Toolkit

Agent-Readable Pricing Audit

AI-Readable Website Audit

Install Sprint

Publish once, keep it boring, update it when pricing changes.

Where to put files

Validation checklist

Maintenance rules

Draft a first `/pricing.md` from a messy offer.