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

Evaluating routing across providers.

ONEDocs

Choose an integration

Compare common integration approaches without assuming a platform-specific SDK or protocol.

Working scaffold: The options below are common patterns, not a claim that ONE currently provides every option. Publish only the paths that are tested and supported.

Common approaches

ApproachUseful whenConfirm before recommending
Direct HTTP APIYou want to make requests from any language with explicit control over the wire formatSupported endpoint, auth, request schema, streaming protocol, and error format
Maintained client libraryYou want typed helpers for requests and responsesOfficial package names, supported languages, versioning, and feature coverage
Compatible clientYou already use a client that speaks a compatible protocolExact compatibility scope, unsupported options, and migration differences
Agent or orchestration frameworkYour application needs multi-step execution, tool dispatch, or managed stateWhether ONE supports the framework directly or whether the application owns orchestration

How to choose

Start with the smallest approach that satisfies the application's needs. A direct request is a useful baseline because it makes authentication, input, output, and errors visible. Add an SDK or framework only when it reduces meaningful work and its behavior is documented.

An SDK is not automatically interchangeable with a compatible API. Verify base URL configuration, request serialization, streaming, errors, and advanced options with an integration test before describing it as a drop-in replacement.

Suggested default

For a new integration, document one recommended path and keep alternatives brief. Link to a separate guide for each supported library instead of adding untested choices to the first-use walkthrough.

On this page