ONE is preparing: 01 / INITIALIZING MODEL ROUTER. Evaluating routing across providers.
Current state
01 / INITIALIZING MODEL ROUTER.

Evaluating routing across providers.

ONEDocs

API reference

A scaffold for the canonical, versioned description of an API contract.

Working scaffold: This is an index and content plan, not a live API specification. Do not infer endpoint behavior from placeholders.

An API reference should be generated from or reviewed against the same contract used by the service. It should identify the supported version, authentication requirements, endpoints, schemas, status codes, pagination, streaming behavior, and deprecation policy.

The planned reference pages are:

Once the contract is stable, link each guide example to the relevant reference section and test every sample against a non-production environment.