latest.sh is an open registry of what developer tools actually cost. 324 tools across 22 categories, with every tier, usage rate, free-tier limit, and switching cost recorded in a structured form that both people and agents can read.
It exists because pricing pages are written to be persuasive, not comparable. Two hosting providers can both say “from $20/month” and mean completely different things once bandwidth, seats, and overage rates are counted. The question a developer actually has — what will this cost me at the scale I’m heading toward? — is usually the one a pricing page answers last.
Every tool is one JSON file in a public repository, validated against a schema before it can be published. The numbers
come from each vendor’s own published pricing page, and each entry carries a lastVerified
date so you can see how stale it might be. Nothing is estimated, inferred, or negotiated — if a tier says
“contact sales,” that is what the registry records.
A job runs weekly, hashes each vendor’s pricing page, and flags the ones that changed so they can be re-checked by hand. Fast-moving categories like AI coding tools are marked volatile and reviewed more often. Every change that lands is visible in the changelog.
Each tool gets a 0–100 score for how legible its pricing is: whether prices are public, whether usage rates are
documented, whether switching costs are stated, and — worth the most — whether the vendor publishes a
machine-readable pricing.md file of their own. The
leaderboard
ranks the whole registry. The point is not to shame anyone; it is to make the vendors who are straightforward about
money easy to find.
Everything here is readable by machines without scraping: an MCP server at /mcp,
a REST API described by OpenAPI, and markdown at every URL. See the
developer docs.
latest.sh is maintained by Roger Byrne. The pricing data is MIT-licensed and lives at github.com/rogermbyrne/pricing.md — corrections are pull requests, and a wrong number is a bug worth reporting. Running costs are covered by a single ad slot served through Carbon. Advertisers cannot buy a position in the registry: rankings are computed from published prices and the scoring rules above, and the same code produces the same ordering whether or not anyone is advertising.
Every tool page shows a verification date. Vendor pricing pages are hashed weekly and any that changed are flagged for re-checking, so the gap between a vendor changing a price and the registry reflecting it is usually days, not months.
Yes. The website, the REST API, and the MCP server are all free and need no account or API key. There is no paid tier and nothing is metered.
No. The data reflects published prices, and the transparency score is computed from fixed rules. A vendor who wants a better score can publish clearer pricing — that is the only lever.
Open an issue or a pull request against the repository, or see the contact page. Corrections with a link to the vendor's pricing page are merged quickly.
A plain markdown document at a predictable URL that states a product's tiers, limits, and overage rates in a form an agent can read without parsing a marketing page. Vendors who publish one score highest here, and their data stays accurate without anyone re-checking it by hand.