API reference
Choose the right model.
Canonical IDs, supported protocols and a model picker without duplicate context variants.
Model catalog
#This table loads the currently enabled models and their token multipliers from the XEDOC API when you open this page. Refresh the list to check for changes. Your tools can retrieve the same model IDs with an authenticated /v1/models request.
Enable JavaScript to load the current catalog, or request GET /v1/models with your XEDOC API key.
Requests are admitted while your token balance is positive. XEDOC does not reserve a full model context or impose a default output limit. Your explicit generation settings are forwarded. Complete provider usage is charged once when the request finishes. Already running requests can use more than the remaining balance; a zero or negative balance blocks new requests and never triggers an automatic payment. If a stream ends before final usage is received, its charge needs review and does not reserve your balance.
A multiplier applies to the tokens charged to your balance. For example, 100 raw tokens at ×5 cost 500 balance tokens. If input, cached input and output have different rates, each is shown separately.
Use the normal model name
#Use names such as claude-opus-5 exactly as shown. Claude context variants are handled by the gateway and appear once in your model list; do not add [1m] to your configuration.
Context and output limits, when reported in the API catalog, are model-service metadata. Request size and your client’s context settings can impose lower limits. A model without reported limits should not be treated as having unlimited context.
Reasoning and client settings
#Choose the model and reasoning level in your client. The assistant provides compatible client options; the model service determines which settings a particular model accepts. Existing user context or compaction overrides can take precedence over generated catalog values.
For models without reported context metadata, generated client configuration uses a conservative context setting. That client setting is not a statement of the model’s full capacity.
Keep the picker current
#Run xedoc again and select the clients you want to refresh. A paused model disappears from the current API catalog. A model saved in an older client configuration can therefore return an unavailable-model error until the list is refreshed.