Routic
HomeModelsDocs
Log inGet Started
HomeModelsDocs
Log inGet Started

On this site

Gateway & boundaries

Gateway scope & capability boundaries (overview)Routing, model names & upstream mappingRate limits, quotas, budgets & safety baselineExplicitly not in MVP (avoid over-promising)

Integration

Quickstart (first successful call)OpenAI-compatible API surfaceAuthentication & Virtual KeysErrors, retries & idempotencyStreaming & parameter support matrix (placeholder)

Client guides

Using Routic in CursorUsing Routic with Claude CodeUsing Routic with Aider

Billing & catalog

Cost comparison: Routic vs direct APIModels, SKUs, usage & billing objectsInvoices, reconciliation & disputes (placeholder)

Operations

Observability & request IDsSLA & support channels (placeholder)

Reference

HTTP semantics & error payloads (sketch)Glossary (gateway & billing)

Docs parity & gaps

Recommended reading orderGaps vs OpenAI’s official docsGaps vs OpenRouter-style aggregatorsGaps vs LiteLLM docs (customer vs ops)

Explicitly not in MVP (avoid over-promising)

What we usually do not promise in MVP

  • Full unified IdP / auth.* rollout (LiteLLM UI paths may remain).
  • Mandatory first-party Next console (apps/console is not MVP-required).
  • Exposing live supplier topology traces to end customers.
  • Private doc ACLs (public docs baseline per tech selection).
  • Claiming full parity with every vendor-native feature behind one OpenAI surface without a SKU matrix.

See also

  • Scope & boundaries
  • Recommended reading order
Routic

Productized model catalog and billing on an OpenAI-compatible gateway Available models follow your product and contract; backend suppliers are not shown publicly

Products

  • Features
  • Compare
  • Use cases
  • Flow
  • Models

Developers

  • Examples
  • API Docs

Resources

  • Documentation
  • Contact Sales

Company

  • Contact Sales
  • Terms of Service
  • Privacy Policy

© 2026 Routic. All rights reserved.

Operated by PISTISAPI LIMITED (Hong Kong)