GET https://api.ticonai.com/v1/models returns the models that are active and visible to your key. Use an id from this list as the model field of a request.
curl -sS https://api.ticonai.com/v1/models \
-H "Authorization: Bearer $AIP_API_KEY"{
"object": "list",
"data": [
{ "id": "your-model-id", "object": "model", "created": 1767225600, "owned_by": "provider-slug" }
]
}| Field | Meaning |
|---|---|
id | The model id to send in requests. It may contain a slash, such as family/name. |
object | Always model. |
created | Unix time the model was added to the catalog. |
owned_by | The provider slug in the catalog. |
If the key has an allowed-models restriction, the list contains only those models. See API keys.
One model
GET https://api.ticonai.com/v1/models/{id} returns a single entry in the same shape. An unknown model, and a model the key may not use, both answer 404 model_not_found, so the response does not reveal which models exist.
curl -sS https://api.ticonai.com/v1/models/your-model-id \
-H "Authorization: Bearer $AIP_API_KEY"Context windows and prices
The list is intentionally minimal. Context window, maximum output, capabilities and the price per 1M input, cached-input and output tokens are published on the website's models and pricing pages. Prices are in BDT. See Billing and wallet for how they turn into a charge.
Using a model that does not exist
curl -sS https://api.ticonai.com/v1/models/no-such-model \
-H "Authorization: Bearer $AIP_API_KEY"A completion request for an unknown model also answers 404 model_not_found; for a model your key may not use it answers 403 model_not_allowed.