Endpoint
GET /v1/models, so any OpenAI SDK or tool that performs model discovery — client libraries, gateways, playgrounds, evaluation harnesses — works against each::sense without modification. It requires the same API key as chat completions and is a convenient first call to verify that your key and base URL are configured correctly.
The full list is returned in a single response. There is no pagination and no query parameters are required.
Code Examples
Response
Response Fields
Model Selection
The agent orchestrates 500+ underlying AI models, but exposes a single
eachsense/beta model through the OpenAI-compatible interface. Model selection happens automatically based on your request.eachsense/beta is not one model — it is the router entry point. When you send a request, each::sense analyzes the intent (text generation, image creation, video, code, and so on) and dispatches it to the best-suited underlying model, so you never hard-code a specific vendor model ID.
In practice this means:
- Use
eachsense/betafor every request. It is also the default when themodelfield is omitted, so existing OpenAI integrations work unchanged. - Don’t cache assumptions about capabilities per model ID. Capabilities evolve behind the same identifier as new underlying models are added to the routing pool.
- Steer routing with request parameters, not model IDs. Use
mode("max"vs"eco") to trade quality against cost and latency, andbehaviorto switch between agent, plan, and ask styles — see Chat Completions for details.
401 response from this endpoint indicates a missing or invalid API key; verify the Authorization: Bearer header before debugging anything else.