# About Us

> Markdown mirror of https://router.one/about for AI assistants and crawlers. Router One is an OpenAI-compatible LLM API gateway.
> Last updated: 2026-09-19

Router One is the LLM API gateway built for developers who need reliable, affordable access to frontier AI models. One unified endpoint, smart routing across 30+ supported models, automatic provider fallback, real-time cost tracking, and payment methods that work wherever your team is.

## What Is Router One?

Router One provides a single API endpoint that connects to every major model family — GPT, Claude, Gemini and Grok. Instead of managing separate SDKs and dealing with provider-specific authentication, rate limits, and billing, your team uses one consistent interface. The gateway is reachable worldwide — including mainland China — and takes payment by card, Alipay, or stablecoins, so neither geography nor billing blocks a team from frontier AI models.

## Core Capabilities

Our platform is built around three pillars: Intelligent Routing that selects a healthy route for each model request; Budget & Rate Control that gives every API key its own maxSpend, rateLimit, and tokenLimitTpm; and Full Observability with request traces, aggregated metrics, and cost breakdowns. Create a separate key for each project, tool, or environment to isolate its spend. We also provide native support for AI coding tools — Claude Code and Codex work out of the box with a simple environment variable change.

## Our Philosophy

Router One gives teams one place to review model-call usage and control spending. Customer Logs shows the model, request ID, tokens, settled cost, recorded latency, status, and any sanitized error. Upstream supplier identities and service routes remain internal. We believe developers deserve clear evidence for the usage and charges behind their AI applications.

## What's Next

We focus on making the gateway better at the job it already does: tighter latency, broader provider coverage, sharper observability, lower integration friction. We do not promise agent-orchestration runtimes, Run/Step state machines, or platform layers we are not building. When we ship something, it is because we ship it — not because we put it on a roadmap slide.

## Who writes this site

Router One's pages are written and maintained by the Router One engineering and documentation team — the same people who run the gateway. There are no named guest authors. Every published latency, pricing, routing, and retention number traces back to a dated page: the [China latency benchmark](https://router.one/benchmarks/china-latency), [pricing methodology](https://router.one/pricing-methodology), [smart routing methodology](https://router.one/routing-methodology), and [data retention windows](https://router.one/data-retention) are indexed under [Methodology](https://router.one/methodology) and the [Trust hub](https://router.one/trust). Corrections and questions go to [support@router.one](mailto:support@router.one).

## Company Information

- Contact Email: [support@router.one](mailto:support@router.one)
- X (Twitter): [x.com/router_one](https://x.com/router_one)
- GitHub: [github.com/Router-One](https://github.com/Router-One)

## See also

- Trust hub: https://router.one/trust
- Methodology: https://router.one/methodology
- FAQ: https://router.one/faq
- Contact: https://router.one/contact
- Canonical page: https://router.one/about
- Models and per-model token rates: https://router.one/models (markdown: https://router.one/models.md)
- Pricing: https://router.one/pricing
- API docs (markdown): https://router.one/docs.md
- Company facts: https://router.one/facts/company.md