Tarseek API · Pre-production
Models
A model page is a capability card. Pricing, context windows, availability, and deployments must come from the live catalog, not from static docs.
Implemented
Browse models in the catalog UI or
GET /v1/catalog/models. GET /v1/models and GET /v1/models/{id} return OpenAI-shaped model records scoped to your key and operational availability.Choose Compare to select up to four models across search results and compare prices, context, capabilities and available providers. Find a model applies your output, context, capability and price requirements to the catalog. These tools compare published metadata. They do not choose a model for you. Open a model for pricing tiers and measured performance. Unknown values remain unknown.
Model IDs
Use the catalog public_model_id (typically developer/model-name) as model in chat requests.
Capability card fields
| Field | Meaning | Source today |
|---|---|---|
| developer | Organization that created the model | Implemented — catalog |
| input / output modalities | text, image, audio, etc. | Implemented — catalog lists; invocation may lag |
| context_window, max_output_tokens | Limits | Partial — present when ingested; not always complete |
| supported_parameters | Normalized request fields supported by the model | Automatically derived from provider-specific official capability metadata and validated |
| supported_endpoints / features / tools / reasoning_efforts | Detailed machine-readable capability metadata | Automatically synchronized from each developer's official model pages or catalog API |
| supports_tools / structured_output / reasoning | Feature flags | Implemented — catalog booleans |
| lifecycle_status | preview, ga, deprecated | Partial — field exists; policy not enforced in gateway |
| deployments | Providers, prices, regions | Implemented — nested on catalog detail |
| availability | healthy vs circuit-open | Partial — operational filter on /v1/models; catalog may still show listed models |