Reference
Reference
Look-up material — every public endpoint, the model catalog, and the capability block a client can branch on.
Reference pages answer "what exactly does this accept, and what comes back". They are look-up material rather than reading material; the guides are the ones to read front to back.
Endpoints
Every endpoint Faucet serves, what authenticates it, and what it answers with.
Models
Every model we carry, with its provider, capabilities, context window and reference rates. Generated from the catalog the gateway routes on.
Model capabilities
The faucet block on GET /v1/models/{id} — what this gateway will
actually serve for a model, which is narrower than what the model can do.
What stays authoritative elsewhere
A reference page compiled ahead of time cannot see your key or your invoice:
GET /v1/modelsapplies your key's allowlist and skips providers holding no usable credential, so it is the authoritative list for a given key.GET /v1/models/{id}publishes what the gateway serves for one model. Prefer branching on it over hard-coding anything on these pages — it is derived from the same functions that reject requests, so it cannot drift from behaviour.GET /v1/creditsis the live credit your next request is judged against.- The console shows the figure you are actually billed.