Quick StartProducts and entry points

Products and entry points

OriginRouter combines the CLI, App, and compatible third-party platforms. The CLI executes work on your device, the App provides visual control, and third-party platforms connect through standard APIs to use OriginRouter models and routing.

Choose an entry point

Your goal	Recommended entry point
Run Claude Code or Codex from a terminal	OriginRouter CLI
View sessions, devices, and approvals on desktop or mobile	OriginRouter App
Use an existing OpenAI or Anthropic SDK	SDK integration
Use OriginRouter inside Claude Code, Codex, OpenCode, and similar tools	Third-party platform support
Control an Agent on another computer from your phone	Connect the App to CLI
Call the HTTP API directly and handle requests yourself	Model API

How the products divide responsibilities

OriginRouter CLI

The CLI is the execution layer on each device. It starts Claude Code and Codex, manages providers and model routes, runs the local service, and evaluates approval policies and Agent commands locally.

OriginRouter App

The App is the visual workspace for desktop and mobile. It provides chat, Provider Control, device trust, Agent sessions, and approvals. It does not move device commands or approval decisions to the cloud.

Connection modes

Local direct: connect the App to a CLI on the same computer. It has the lowest latency and does not require App sign-in.
LAN or custom direct: connect through a saved address and port without account relay.
Account Bridge: connect devices on different networks. The App and CLI must use the same account, and the target device must be trusted and online.

See Connection modes and Device trust for the detailed limits and security boundaries.

URL paths and endpoints

Pay-as-you-go uses /beta/v1, for example /beta/v1/chat/completions.
Coding Plan uses /coding/v1, for example /coding/v1/chat/completions.
The legacy /v1 path is kept for existing integrations; use the new entries for new projects.
OpenAI protocol base_url values normally include the trailing /v1; Anthropic protocol base_url values must omit /v1 because the SDK appends /v1/messages automatically.

See Endpoint Configuration for complete endpoint coverage, plan differences, and copy-ready Base URLs.

Third-party platform support

OriginRouter supports the two mainstream protocol families, OpenAI and Anthropic. Configuration locations, environment variables, and Base URL rules vary by platform; follow the corresponding guide:

If you use the official OpenAI or Anthropic client libraries, start with SDK integration, which begins with the protocol × plan Base URL matrix.

Security boundary

Provider keys are shown only as saved or masked state by default.
Full Agent conversations, tool output, code, and commands remain on the CLI device by default.
Remote control and approvals use end-to-end encrypted channels between trusted devices.
OriginRouter Server handles authentication, device directory, delivery, and status sync; it does not execute commands or evaluate approvals for the CLI.