> For the complete documentation index, see [llms.txt](https://docs.askdodo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.askdodo.com/models.md).

# Models

Published catalogs, AutoRouter eligibility, and route privacy capabilities.

### Models in the website

askDodo uses AutoRouter to choose the underlying model route for your request. The website does not offer a manual model picker. Effective candidates depend on operation, enabled router configuration, input requirements, and current service availability.

A backend can publish a model before it is included in the website's effective Auto configuration. Publication, integration, router eligibility, and a successful request are separate states. Do not interpret the entire gateway directory as the website's supported-model list.

### Why there are separate directories

Text, image, and video operations have different capability, input, output, and pricing schemas. Their public directories are therefore separate:

| Directory | Current endpoint                                                                      | What it establishes                      |
| --------- | ------------------------------------------------------------------------------------- | ---------------------------------------- |
| Text      | [V2 models](https://gateway.askdodo.com/v2/models)                                    | Published text routes and specifications |
| Image     | [Image models](https://gateway.askdodo.com/v1/images/models)                          | Published image offers                   |
| Video     | [Grouped video models](https://gateway.askdodo.com/v1/videos/models?shape=grouped-v1) | Published video offers                   |

Each directory can contain entries not currently selected by the website's AutoRouter. Multiple offers can also refer to one model with different sizes or settings. An offer count is not a unique-model count.

The product supports image and video generation through its enabled Auto paths. The media directories should not be described as wholly “Coming Soon,” but a listed media offer is not a guarantee of successful execution or website reachability.

### Read the current text specification

The V2 text response is an unsigned HTTPS projection. Route metadata is nested under `model_spec`, not the retired signed-catalog wrapper.

Check the exact ID, `model_spec.privacy`, `model_spec.capabilities`, context/completion limits, pricing, `model_sets`, `traits`, and applicable `model_spec.vord` fields. Do not infer these from a provider name, a `tee-` prefix, or an old documentation list.

### Privacy and capability labels

* **Anonymized / private:** route privacy classifications, not complete descriptions of the entire product's data handling.
* **TEE attestation:** a separately declared capability with a bounded evidence and verification procedure.
* **E2EE:** a separate end-to-end encryption capability; a private tier or TEE declaration alone does not establish it.
* **Model sets:** explicit membership, including `uncensored` where declared.
* **Traits:** recommendation signals such as `most_uncensored`; they do not establish model-set membership or unrestricted behavior.

The October 5, 2026 public text-catalog snapshot contains 40 routes: 32 anonymized and 8 private. Six declare TEE attestation; none declare E2EE. These are dated metadata observations, not a promise of permanent counts or independently verified cryptographic properties. They are not the website Auto candidate count.

### Tools, prices, and limits

Use the [live tool directory](https://gateway.askdodo.com/v1/tools) for exact function schemas. Inspect the route's capability flags and `model_spec.vord.gateway_tools` rather than assuming every model supports every tool.

Read prices and units from the current response. Token prices, metered tool units, image sizes, and video durations are different pricing dimensions. Observe the published input/output and request limits.

For the current schema and authentication boundary, see [API Reference](https://docs.askdodo.com/api-reference). For safe recovery and privacy interpretation, see [Guides](https://docs.askdodo.com/guides).
