Models
The model registry: capabilities, pricing, aliases, and sync.
Providers sell access; models are what requests actually address. Synapass keeps a registry of every model it may route to, with the facts routing needs: the real context window, capabilities, price, and priority.
What a model record holds#
| Field | Why routing needs it |
|---|---|
| Context window | Prompts that exceed it are rejected with context_length_exceeded before any provider is called |
| Capabilities | Vision, tool use, JSON mode — requests that need a capability only reach models that have it |
| Price | Per-token input/output pricing feeds lowest_cost routing and pre-call ceiling checks |
| Priority | The operator's ordering preference inside priority and weighted strategies |
| Aliases | Stable names your applications use while the underlying model changes |
| Disabled flag | Take a model out of rotation without deleting its history |
The registry is the reason lowest_cost is honest: it prices from the same
per-model data that the ceiling check uses, not from marketing pages.
Discovery: sync remote models#
Providers add and deprecate models constantly. Instead of hand-maintaining the catalogue, discover it:
- Register the provider (Providers).
- Run Sync models (dashboard → Providers, or the admin API).
- Synapass discovers the provider's remote models while preserving your local pricing, aliases, and disables — a sync never silently overwrites operator-owned data.
Newly discovered models arrive enabled with provider-reported metadata; attach your pricing and aliases, then set priority.
Aliases: stable names for moving targets#
Point applications at an alias ("support-draft", "code-fast") and repoint
the alias when a better model appears. Production traffic shifts with a
dashboard edit, not a deployment — and the request log still records which
concrete model answered each call.
Disabling vs deleting#
Disable a model to take it out of rotation while keeping its request history,
scores, and analytics intact. Delete only when you mean to forget it. Disabled
models are skipped by every strategy and reported as such in /explain.
Models and policy#
A policy may restrict which models a request may reach — by name, alias, or capability. The routing pipeline filters to eligible models first, then orders by strategy. If the filter empties the set, the request is denied with the rule named, and zero provider calls are made.