DocsAccount & workspace

OpenAPI specification

Model IDs and options in examples are illustrative. Select an available model from GET /v1/models and check its capabilities and current prices.

Provider keys

Manage your keys on the Providers page. Keys belong to your selected personal or organization account and are shared across its workspaces. Playgrounds use that account’s keys and balance.

Your keys are used first

For supported models, RelayOn tries your eligible provider keys first. Your provider bills successful requests directly; RelayOn does not charge a routing fee or deduct that usage from your balance.

When your keys are unavailable

Where supported, RelayOn can use your balance when no eligible key is available or your provider rejects the available keys because of access, quota or rate limits. The model’s listed price and your spending limits apply. Legacy ar/ routes require your own usable keys. Every model in the catalogue has a published RelayOn balance price.

A request is not submitted again after output has started or when its processing status is uncertain.

Models and providers

Use the catalogue’s lab/model ID. The lab identifies the model creator; it does not choose the serving provider. Set provider.only to restrict providers, provider.order to prefer an order, or provider.allow_fallbacks: false to stay with the first eligible provider. These options use provider IDs and cannot broaden your access or spending permissions.

Chat completions accept either model or an ordered models array of up to five canonical IDs. Provider fallback keeps the same model; switching models requires that explicit list. Automatic routing tries eligible account keys before permitted paid capacity. Accepted jobs and requests that have started producing output are never rerouted.

Existing bare and provider-prefixed IDs retain their established behavior. Where an ID also names a canonical model, supply provider: {} to opt into canonical routing. For multipart transcription, send provider preferences as JSON in the provider field.

Account access

Personal and organization keys stay separate. Organization owners and admins manage shared keys; members can use them for requests. API-key provider, model and connection restrictions still apply.