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)

Quickstart (first successful call)

Steps

  1. Obtain Virtual Key + Base URL for your environment.
  2. Pick a model from the published catalog (Routing & models).
  3. Send a minimal chat.completions request with any OpenAI-compatible client.

curl template

curl -sS "$BASE_URL/v1/chat/completions" \
  -H "Authorization: Bearer $ROUTIC_VIRTUAL_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model":"YOUR_CATALOG_MODEL","messages":[{"role":"user","content":"ping"}]}'

Next

  1. Models, SKUs & usage
  2. Errors & retries
  3. HTTP & errors
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)