Choose a model and understand its price
Access depends on your key and current channels. Check live pricing, full model IDs, and supported endpoints.
The model pricing page shows published models and prices. /v1/models lists models available to your key. Check the current page for model availability and prices.
Copy the full model ID
Copy the complete model ID from the API response or console. An ID may include a channel prefix. Do not remove the prefix or guess API parameters from a display name.
Channels offering the same model family may differ in price, context limits, supported endpoints, and availability. A listed model does not necessarily support every API format.
Check the supported request format
| Endpoint | Confirm before use |
|---|---|
/v1/responses | Responses support; some channels require stream: true |
/v1/chat/completions | Chat Completions support and model-specific parameter limits |
API compatibility does not imply support for every parameter. Follow the model and channel’s capabilities when a parameter is rejected. Changing a parameter does not resolve an unrelated upstream access restriction.
Read pricing in context
- Check the unit: prices per million tokens and prices per request are different units.
- Separate input and output: input, output, and cache-related usage may have separate prices.
- Check groups and tiers: group multipliers, billing rules, and context tiers can affect the final charge.
A multiplier in a channel name is only a label. Actual charges follow the current pricing configuration and usage logs; do not multiply the charge again by the number in the name.
Verify with a small request
- Check your key and wallet, then select an available model.
- Send a short request and confirm it finishes successfully.
- Check the model, token usage, and charge in usage logs before running larger workloads.
Partial text in a stream does not prove the whole request succeeded. Check for errors and incomplete completion events.
Wallet and service availability
The wallet is the entry point for balances and top-up options. Payment methods, credit validity, invoicing, and other commercial services depend on current console features and support confirmation.
Include a request ID and error message in your ticket. Never include your API key.