Transparency

Data sources & methodology

How we get prices, which models appear, and how the calculator works.

Primary data source

Model names, per-token prices, and context windows are pulled from the OpenRouter Models API — a public aggregator that tracks pricing across major LLM providers. We run an automated fetch script; we do not manually edit individual model prices.

Dataset version and last fetch time are shown in the site header on the calculator page.

Model selection (automatic)

Not every OpenRouter model is listed. An auto-selection pipeline applies:

Full rule patterns live in selection_rules.json in our repository — we keep the site summary short so it stays in sync with the pipeline.

Loading current catalog…

Cost formula

For each model, estimated cost is:

cost = (input_tokens / 1M × input_price) + (output_tokens / 1M × output_price)

Where:

What we do not include

Always verify on the provider's official pricing page before production commitments.

Capability & benchmark references

LabAgenticFlow does not publish its own benchmark scores or quality rankings. Capability chips on the calculator (Tools, Vision, context window) are derived from OpenRouter API metadata — not from our testing.

For independent quality, latency, and throughput comparisons, see:

Flagship models on the calculator may show a See provider benchmarks → link. URLs are configured in data/selection_rules.json (benchmark_links) and point to third-party aggregators or official provider docs — we do not scrape or display scores on-site.

Official provider pricing pages

Update frequency

Pricing and catalog membership refresh on a daily cron (06:00 UTC via GitHub Actions). We update when providers change rates or ship new models — not on a meaningless hourly ticker. The live counts in the box above reflect the latest committed data/models.json.