/openrouter/providers/search

POST /api/openrouter/providers/search

Price: 5 credits

List the inference providers OpenRouter routes to

How to use it

The provider directory behind the routing: headquarters, datacentre regions, and the data policy that decides whether prompts are retained or used for training. Read `data_policy` here rather than inferring retention from the provider's brand. To filter models by provider, pass the `name` value from here to the `providers` filter of /openrouter/models/search; that filter also accepts providers this directory does not list.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• q string nullable — Keep only providers whose name or alias contains this text (examples: "amazon")
• count integer required — Max result count (min: 1)

Response

• @type string (default: "OpenrouterProvider")
• alias string required
• name string nullable
• display_name string nullable
• adapter_name string nullable
• base_url string nullable
• headquarters string nullable
• datacenters array (default: [])
• has_chat_completions boolean nullable
• has_completions boolean nullable
• is_abortable boolean nullable
• is_moderation_required boolean nullable
• is_byok_enabled boolean nullable
• sends_client_ip boolean nullable
• pricing_strategy string nullable
• required_attestation_types array (default: [])
• status_page_url string nullable
• image string nullable
• data_policy object nullable
  • @type string (default: "OpenrouterDataPolicy")
  • is_training boolean nullable
  • is_training_openrouter boolean nullable
  • is_retaining_prompts boolean nullable
  • retention_days integer nullable
  • can_publish boolean nullable
  • requires_user_ids boolean nullable
  • terms_url string nullable
  • privacy_url string nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — The entity was not found, or a precondition failed Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.