GroqCloud vs Router.com (Ramp Router)

GroqCloud

Free plan with no card, at 30 requests a minute and 1,000 a day on gpt-oss. Four model shutdown dates between 2026-07-17 and 2026-09-21, with no stated minimum notice.

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.

GroqCloud

1. Call /models at start-up. Four model ids stopped working between July and September
2. Read retry-after on a 429 and the x-ratelimit-remaining-tokens header before the next call
3. Free plan allows 8,000 tokens a minute on gpt-oss, so keep prompts small or batch them
4. Don't build on Qwen 3.8 27B. It's a preview and previews can go at short notice
5. Treat a 498 as Flex capacity and retry later; server errors aren't billed

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