OpenAI API vs Router.com (Ramp Router)

OpenAI API

Official OpenAPI document and an llms.txt index. Elevated errors across the API for about 5 hours 20 minutes on 29 September and about 90 minutes on 17 September 2026.

Router.com (Ramp Router)

Detailed Markdown docs with typed error codes, per-model capability data and routing an agent can set per request. No OpenAPI document, status page, changelog or published rate limits were found. Signup needs a US business email in a browser, and Ramp records prompts and outputs for a year by default unless switched off.

OpenAI API

1. Build on the Responses API. Astra calls tools only there
2. Use gpt-6-luna for routing and extraction, gpt-6.1-terra for screens, images and computer use at half Sol's price, and gpt-6.1-sol for most work. The models page still points unsure callers to gpt-6-astra
3. Move off the GPT-4o and GPT-4.1 snapshots before 2027-01-14, the gpt-5, o3 and related snapshots before 2026-12-11, and gpt-5.1, gpt-5.3-codex and gpt-5.4-nano before 2027-04-01. Check shutdown_date on GET /v1/models
4. Treat 429 slow_down as a ramp limit and 503 server_is_overloaded as a retry, and follow Retry-After when it's sent
5. Prompts over 272K tokens cost double on input. Trim before you pay for it

Router.com (Ramp Router)

1. Switch off content recording in Settings before sending private data. It is on by default and keeps prompts and outputs for a year
2. Read model ids from GET /v1/models at runtime. Ids are account-specific, an unknown one is a 404, and Gemini ids need your own Google key
3. Use POST /v1/responses with a models list for fallbacks. Router stops falling back once a stream has started
4. Set fallback_timeout and provider_timeout, or allow_flex_tier: false, when latency matters. Flex routing is on by default
5. Treat both 401 invalid_api_key and 401 api_key_deactivated as a possibly locked key, and stop retrying on 402