Last reviewed:
Open Dreams RouterWho it is for
Agent developers who need programmatic access to paid models or services and want a stable routing surface instead of maintaining separate provider-specific commercial integrations.
How it works
Inspect current routes
Builders use the live catalog to check what is available. A route should not be assumed live because it was mentioned in an old article or cached search result.
Send a supported request
The client submits a request in the format documented by the router and meets the applicable payment requirement.
Observe the result
Applications should log the selected route, response, latency, cost, and error state so routing decisions remain auditable.
Published evidence
- The router has a public service endpoint and catalog.
- Live status and catalog data can be checked directly rather than inferred from promotional metrics.
- This page makes no uptime or volume guarantee.
Limitations
- Available routes, providers, and pricing may change.
- A router does not remove upstream model limitations or the need for output evaluation.
- Clients need timeouts, spending limits, retry rules, and fallbacks.