Methodology

Every listing is read by a person; every price carries the page it came from; every page has a stated sort order. This page lists each rule so you can check it. What payment does and doesn't change is in the editorial policy.

What gets listed

Infrabase lists infrastructure a developer builds into a product: inference APIs, GPU clouds, vector databases, observability tools, agent frameworks, voice APIs and similar. Each product has a primary job, such as hosted inference API or vector database. Two products are alternatives when they do the same job.

Some things are not listed, however well made:

• directories and catalogues of other tools
• finished consumer apps and creative tools with an API attached
• services that take customers' money or credentials with no named company behind them
• resellers priced far below what the model's maker charges, with no explanation of the source

How a listing is checked

I open the vendor's own site in a browser before a product goes live. Pricing, HQ country, licence, compliance claims and what the product does are checked against the vendor's own site. A status code alone proves little; many sites answer a "not found" page with a normal one. A fact I can't confirm is left out, not guessed.

Anyone can send a correction from a product page. Facts get re-read when a vendor writes in and when older listings are reviewed. A listing can lag behind a vendor's latest change.

How model prices are checked

• Only prices read off the provider's own pricing page are shown, each with the URL and the date it was read.
• Figures from aggregators such as OpenRouter are never shown as prices.
• Prices are stored in the currency the provider publishes. Euro prices are converted at a dated ECB rate and marked "≈".
• Tables rank by blended price, with input and output tokens weighted 3:1. Nothing else changes the order.
• A price change is logged on the price changes page, marked as the provider's change or our own correction.

A lower price says nothing about speed, model catalogue or rate limits. Infrabase does not run its own speed or quality benchmarks.

How pages are ordered

• Category pages, comparison tables, the European page, the gateway comparison and the landscape: featured products first, always labelled. Payment buys that position and nothing else.
• Price tables and the open data: sorted by price. The API and the MCP server never sort by featured status.
• Alternatives pages: a labelled Featured panel first. Below it, products with the same primary job come first, then products that share a secondary job. Within each group the order is GitHub stars, then the length of the written overview, then the length of the description, then name.

That last rule has a bias worth stating: a product with a popular repository or a fuller write-up sits higher among equals. Stars and write-ups are the signals available for every product.

What the numbers are

Site traffic is measured with Plausible, which sets no cookies. Per-vendor numbers are shared with that vendor only. When Infrabase quotes figures in public, they are totals across many listings.

Open data

Listings and verified prices are available through the API and the MCP server under the CC-BY-4.0 licence. Use them freely, commercially included, with credit to infrabase.ai.

What this doesn't cover

The catalogue is not complete. A product that isn't listed has not been judged and may not have been submitted. If a listing is wrong, including one that pays, tell me and I'll fix it and say so.

Last reviewed 3 November 2026. Editorial policy · About