Skip to content

Contributing

Anyone can propose a value to providers.dev, providers included. Every value needs evidence: a link to the provider's own page and the day it was read, or a measurement with its raw results.

No payment

No money decides a value. providers.dev takes no payment for listing, correcting or measuring an entry. A provider may supply documentation, or access for a measurement; the result is published whatever it shows.

What can be contributed

  • A correction. A value on the site is wrong for a provider and access method. It needs a link to the provider's own page that gives the right value, the sentence quoted, and the day it was read. A wrong value that came from models.dev is corrected here, by a correction with its evidence; the imported copy of models.dev is never edited.
  • A missing provider or model. It needs a link to the provider's own page or model list that shows it, and the access method it is reached with. Only the values that have evidence for that access method are filled in. The rest stays Unknown.
  • A measurement. A cache evaluation or a limit evaluation taken with groundtruth, with its raw result files. See Measure it yourself.
  • A request for a measurement. It names the provider, the access method, the model and what to measure, and says what access exists: an API key, a subscription, or access a provider offers for the measurement.

A value belongs to one provider and one access method. An API key and a subscription login are different entries, even for the same model at the same provider, and a value is never copied from one to the other.

Evidence

Every value providers.dev adds or corrects carries at least one item of evidence: its kind, a link and a date, and a note with the sentence quoted or what was run. The build fails without it. There are three kinds.

  • documented The provider says so. Anyone may propose a correction or an addition with a link to the provider's own page that says so, the sentence quoted, and the day it was read. It is published as documented, with that link and date.
    Example: OpenRouter's guide to prompt caching says "Prompt caching with DeepSeek is automated and does not require any additional configuration." The DeepSeek entries at OpenRouter are corrected to automatic caching, with the link https://openrouter.ai/docs/guides/best-practices/prompt-caching#deepseek, the date 2026-11-13 and that sentence.
  • measured Requests were sent. A measured value is never accepted as a claim. It is a measurement with its raw result files: the link is the raw result, the date the day of the run, and the note says what was run.
    Example: a cache evaluation of meta/muse-wonder, sent straight to OpenRouter on 2026-11-04. The note says "Direct to OpenRouter, Responses API with a prompt_cache_key; 20 of 27 later re-sends were served from the cache, the oldest at 25 minutes." The link is the result file in the groundtruth repository, results/openrouter-direct/R10-2026-11-04T19-00-07.json.
  • listed The provider's own model list reports it. The list is the answer of the provider's models endpoint, or its page that lists its models. The link is that list and the date the day it was read.
    Example: a provider serves a model that the catalog does not have. Its models endpoint lists the model with a context window of 200,000 tokens. The model is added with that figure, the link to the list and the day it was read.

A documented value and a measured one are both published, each with its source and date. How they are shown side by side is in the methodology.

Two ways in

The issue form, for anyone

Open an issue with the form A value is wrong or missing. It asks for the provider, the access method, the model, the field, what the site shows, what it should show, the source link, the sentence quoted or what was measured, and the date it was read. The source link is required. To ask for a measurement, choose I am asking for a measurement in the same form and say what access exists. A fault in the site itself goes in a blank issue.

A pull request, to write the change yourself

  • One change per pull request.
  • A correction goes in data/authored/overrides/<provider>.yaml. An added provider, or a model added to it, goes in data/authored/providers/<provider>.yaml. The format is in the Authoring section of the README.
  • Nothing under data/upstream/, data/sources/ or data/published/ is edited by hand. The import and the build write them.
  • npm run build && npm run check must pass. The build fails when a correction, an added provider or an added model has no evidence. Every pull request is checked with the same two commands.

The repository is github.com/ngvoicu/providers.dev.

Measure it yourself

groundtruth is the tool providers.dev measures with. It is public, under the MIT License. It runs against a provider's API with the contributor's own key, and records cache evaluations and limit evaluations with their raw results.

A measurement is proposed to the groundtruth repository, with its raw result files. providers.dev imports groundtruth's results file, observed.json. A measurement accepted there is published here on the entry it was taken on, with its access method, client, date and a link to its raw result.

A measurement has limits:

  • Small samples. A few requests at each age or size, on some days.
  • One account per route. Another plan, region or account can have another limit or another cache.
  • Dated. A provider can change a limit or its cache the next day. A measurement goes stale as all providers.dev evidence does.

How an evaluation is made and read is in the methodology: cache evaluations and the input window.

What is not accepted

  • A value with no source.
  • A measured value without its raw results.
  • A value copied from another access method.
  • A paid listing or a paid correction.

What happens to a request

providers.dev has one maintainer. No response time is promised. A request with a link to the provider's page is quick to check. A measurement waits for quota and time.

An accepted value is published with its evidence, under the project's licence, the MIT License, like everything else providers.dev adds. See the licensing page.

Contact

For anything that does not fit an issue, write to office@providers.dev: a provider that wants to supply documentation or access for a measurement, a correction that cannot be made public, or a question about the data. A wrong or missing value goes in an issue, as above.