provod.ai / docs
Start here

Choose an available model

Use the current catalog to select an available model, exact ID, capability, and endpoint.

Last updated on

The current catalog is the authority for model IDs, availability, capabilities, context limits, and prices. Its contents can change, so do not depend on a fixed count or a model list copied into prose.

Open the current catalog

Use the model catalog for a visual comparison or request the catalog with the API key for the active workspace:

Terminal
curl https://api.provod.ai/v1/models \
  -H "Authorization: Bearer sk_..."

Copy the exact id returned by the catalog. Do not shorten it, infer it from a display name, or assume another member of the same model family has the same contract.

A live catalog separates available models by modality and supported endpoint.

Copy an exact ID only after checking availability and capabilities.

Check availability before capabilities

Choose an entry with available: true. When it is available: false, read unavailableReason instead of repeatedly sending the same request.

A new personal workspace receives welcome balance under the current terms, but that balance does not unlock every model. Check its current amount and state in Balance. Some personal-workspace models require the first real balance top-up and report FIRST_TOP_UP_REQUIRED. Shared workspaces can follow different access rules, so use the status shown for the active workspace.

Match the model to the task

Check these current fields before sending a request:

  • architecture.input_modalities and architecture.output_modalities for text, image, or file input and output;
  • supported_parameters for tools, structured output, reasoning controls, and other accepted options;
  • context_length and the published completion limit for request size;
  • supported_endpoint_types for image generation or editing where those operations are published;
  • available and unavailableReason for access in the active workspace.

Use /v1/chat/completions for OpenAI-compatible chat. Use /v1/messages when the client requires the Anthropic Messages format; it accepts supported chat model IDs and published aliases from the shared catalog, not only Anthropic models. Use /v1/images/generations or /v1/images/edits only when the model publishes that operation. Video models use the separate /v1/videos/models catalog and asynchronous video endpoints.

Keep discovery in the setup flow

Refresh the catalog when configuring a client or when a saved model becomes unavailable. Fixed recommendations age quickly; compare the task's modality and required parameters first, then current availability, limits, and price.

Troubleshooting

On this page