> For the complete documentation index, see [llms.txt](https://docs.fastrouter.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fastrouter.ai/api-reference/provider-x-model-supported-parameters.md).

# Provider x Model Supported Parameters

## List Provider-Model Pairs

> Returns a flat array of every (provider, model) pair available on FastRouter. Each entry shows how a given provider exposes a model: the provider's \`provider\_model\_id\`, its own pricing, the parameters it accepts (with detailed input formats in \`supported\_parameters\_v2\`), and provider-specific capability flags in \`extra\_params\`.\
> \
> This is the most granular view — use it to filter by provider or to discover all the provider variants of a model. For a single model's full provider breakdown, use \*\*GET /api/v1/modelProviderData?id={modelId}\*\*.\
> \
> \> \*\*Tip:\*\* Inspect \`supported\_parameters\_v2\` on each entry to see exactly which parameters a provider accepts (with their data types, enums, and min/max ranges).

```json
{"openapi":"3.1.0","info":{"title":"FastRouter API Reference","version":"1.0.0"},"tags":[{"name":"Models","description":"List and retrieve available AI models with pricing and capability information."}],"servers":[{"url":"https://api.fastrouter.ai","description":"Production API"}],"security":[],"paths":{"/api/v1/providerModels":{"get":{"operationId":"listProviderModels","tags":["Models"],"summary":"List Provider-Model Pairs","description":"Returns a flat array of every (provider, model) pair available on FastRouter. Each entry shows how a given provider exposes a model: the provider's `provider_model_id`, its own pricing, the parameters it accepts (with detailed input formats in `supported_parameters_v2`), and provider-specific capability flags in `extra_params`.\n\nThis is the most granular view — use it to filter by provider or to discover all the provider variants of a model. For a single model's full provider breakdown, use **GET /api/v1/modelProviderData?id={modelId}**.\n\n> **Tip:** Inspect `supported_parameters_v2` on each entry to see exactly which parameters a provider accepts (with their data types, enums, and min/max ranges).","parameters":[],"responses":{"200":{"description":"Array of provider-model entries","content":{"application/json":{"schema":{"type":"array","items":{"$ref":"#/components/schemas/ProviderModelEntry"}}}}},"429":{"$ref":"#/components/responses/RateLimitError"},"500":{"description":"Internal Server Error"}}}}},"components":{"schemas":{},"responses":{"RateLimitError":{"description":"Rate Limited - You have exceeded your request limits (TPM/RPM). Slow down or increase your limits.","content":{"application/json":{"schema":{"type":"object","properties":{"error":{"type":"object","properties":{"message":{"type":"string"},"type":{"type":"string"},"code":{"type":"string"},"status":{"type":"integer"}}}}}}}}}}}
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.fastrouter.ai/api-reference/provider-x-model-supported-parameters.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
