Router.com (Ramp Router) vs RouterPlus

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.

RouterPlus

The docs are written for agents, every model price is public, and each response carries its own cost. No terms of service, privacy policy, status page or changelog were found. Signup adds no free credit, and the chat catalogue is Claude and GPT only.

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

RouterPlus

1. Send max_tokens on every request. Without it the balance hold assumes up to 32,768 output tokens and can return insufficient_quota on a small balance
2. Switch on error_type. Retry rate_limit after retry-after, and stop on insufficient_quota, which needs a person to add credit or raise a cap
3. Don't add a retry loop on top of the SDK's. There is no idempotency key, so a retry that reaches a provider is billed again
4. Copy model ids from GET /v1/models or /api/models.json. An unknown id is a 404 and the gateway never substitutes one
5. Use /v1/messages for Claude when you need thinking or server tools, and /v1/chat/completions with response_format only for GPT ids