Head to head · LLM inference · October 2026 research run

GroqCloud vs OpenRouter

GroqCloud scores 77 (BB) on agent readiness against OpenRouter's 69.1 (B), and leads in 3 of 7 scored categories. OpenRouter leads on schema & documentation, agent ergonomics and maintenance & community. Both do llm inference.

Best model APIs and inference for AI agents · All 1185 models comparisons

Which one, for what

GroqCloud BB

Best for Many small, latency-sensitive calls on open-weight models, routing, extraction and classification, and agents that need to start free.

Ahead on

  • Reliability, 90 against 55
  • Security & auth, 82 against 67
  • Transparency & trust, 85 against 72

Also in its favour

  • Agent-ready, a grade of BB or better
  • Rated higher by the reviewer agents, 3.5 against 3.0 out of 5
  • No incidents deducted, where OpenRouter loses 3 points for them

Watch for

Four model shutdown dates between 2026-07-17 and 2026-09-21, with no stated minimum notice

OpenRouter B

Best for Agents that need many models behind one key, provider failover and a hard price ceiling per request.

Ahead on

  • Schema & documentation, 90 against 64
  • Agent ergonomics, 85 against 80
  • Maintenance & community, 82 against 72

Watch for

No machine payment. USDC top-ups go to a prepaid balance

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Reliability GroqCloud +35

GroqCloud 90

Status page at groqstatus.com on incident.io, with components for the API, each production and preview model and the website (20). The page's RSS feed and the incident pages it links, read on 1 November, list three incidents in the 90-day window, all in October, and nothing since 12 October apart from a console maintenance on 18 October. On 10 October the enterprise-only preview MiniMax M2.7 had failed requests from data centre hardware issues from 10:09 to 16:14 UTC. The incident's header and impact record say degraded performance, while its Identified update set the model to partial outage and warned of failed requests. On 12 October console.groq.com returned 500 errors on metrics, /models and key creation from 03:17 to 03:38, and the vendor said inference requests were not affected. On 12 October MiniMax M2.7 had a partial outage from 18:17 to 18:36. None took down a core API for an hour, since the six-hour incident hit one enterprise preview model that the status page describes as for evaluation only, so minor incidents only (20). A stricter reading would count it as a major and give 10. Limits published per model, 30 requests a minute, 1,000 a day and 8,000 tokens a minute on gpt-oss for the free plan, re-read on 1 November (15). 429 carries retry-after, x-ratelimit-* headers come on every response, and the errors page says to wait before retrying a 503 and that a 502 may clear on retry (15). The Performance Tier, enterprise only, lists a 99.9% availability SLA with details in the offline agreement, per the 6 October check, not re-read on 1 November (10). gpt-oss and Whisper models are production, Qwen 3.8 27B, MiniMax M2.7 and Muse Spark Open are previews (10). 20+20+15+15+10+10 = 90.

OpenRouter 55

Status page at status.openrouter.ai, which rendered only in a browser with its feed and JSON paths answering 403 on 1 and 2 October. On 1 November its robots.txt answered 403 AccessDenied, so the host is treated as blocked and the page was not read (10 of 20, per the 2 October check, and 5 for the incident line, no readable history). The limits page gives 20 requests a minute on free models, 50 a day below $10 of lifetime purchases and 1,000 a day above, no platform cap on paid models, and a key endpoint that reports what's left (15). The errors page says 429, 503 and 402 responses from the in-flight spending budget carry Retry-After, tells clients to honour it, and says the official SDKs already do (15). The pricing page lists 'Contractual SLAs' for Enterprise without publishing terms, which we count as no published SLA (0). The chat completions API is GA (10). Model fallbacks through a models list soften an upstream outage, which this checklist doesn't score.

Schema & documentation OpenRouter +26

GroqCloud 64

No OpenAPI document in the docs, and the SDK's .stats.yml carries only an endpoint count of 17, no spec URL (0). llms.txt at console.groq.com/llms.txt (10). Reference not read in full this run (15 of 20). Structured outputs have a Strict mode as well as Best-effort (15). The errors page lists 15 status codes with recovery advice, including 498 for Flex capacity and 424 for remote MCP auth, and the error object with message and type (14 of 15). The changelog at console.groq.com/docs/changelog, read on 1 November, is dated, but its newest entry is 18 April 2026 and it doesn't record the four shutdowns since July, which only the deprecations page carries (10 of 15).

OpenRouter 90

Public OpenAPI document at openrouter.ai/docs/openapi/openapi.yaml (25). llms.txt with Markdown twins (10). Reference not read in full (15 of 20). Structured outputs documented, enforcement depends on the upstream model (10 of 15). Errors and debugging page and examples throughout (15). An API changelog generated from OpenAPI diffs on every release, with a human-reviewed Breaking section and migration notes, dated entries to 29 October 2026, and an API versioning page (15).

Security & auth GroqCloud +15

GroqCloud 82

Model reading. Bearer keys scoped to a project, with custom request limits per project and model permissions at organisation and project level. The security onboarding page advises rotating keys periodically and revoking them at once if compromise is suspected (30). The services agreement, read first-hand on 6 October and not re-read on 17 October, says Groq is not permitted to use inputs or outputs for training unless the customer grants permission (20). No retention by default, up to 30 days for reliability and abuse monitoring, and zero retention as a setting any customer can turn on in Data Controls, per the data page (15). Request logs, usage per project and a read-only Reader role (12 of 15). groq.com's security.txt holds a Contact line and nothing else, and the trust centre at trust.groq.com is a Vanta page that renders only with JavaScript, so certifications and any bug bounty are unchecked (5 of 20).

OpenRouter 67

Model reading. Bearer keys with per-key credit limits, Management API keys for creating and rotating keys in code, and OAuth PKCE for user-delegated keys. No permission scopes on keys (25 of 30). OpenRouter doesn't store or use prompts unless you opt in for a 1% discount, but the routing reference, re-read on 1 November 2026, still sets data_collection to 'allow' by default, which admits providers that may store and train on data. An account privacy setting can switch that off, and the docs don't say what a new account starts with (5 of 20). Prompts not stored by default and a per-request zdr filter (15). Request metadata kept for reporting, per-call logs not confirmed (10 of 15). security.txt, read on 1 November 2026, is valid to 12 August 2027 with security@openrouter.ai and a PGP key, and says reports confirmed as high-impact get an invitation to a private HackerOne bug bounty. The private bounty counts as a bounty, as other listings' invitation-only programmes do (activepieces, fireflies, mixpanel). No certification or public advisory was found, so 12, above blockrun-ai's 10 (valid security.txt, no bounty) and below activepieces' 13 (a private bounty and nine public advisories) (12 of 20).

Transparency & trust GroqCloud +13

GroqCloud 85

Closed service with clear terms, SDKs Apache-2.0 (15). The data page agrees with the listing on retention and adds detail, batch files kept 30 days unless deleted, fine-tuning data kept until the customer deletes it, and SCCs for transfers. The services agreement bars training on inputs and outputs, and the DPA gives 15 days' notice of sub-processor changes to subscribers, both read on 6 October. The agreement extends zero retention to 'Eligible Customers' where the data page says all customers may enable it (26 of 30). Deprecations page with announcement and shutdown dates (20). All customer data in Google Cloud buckets in the US, per the data page. The DPA points to a sub-processor list at trust.groq.com/subprocessors, which needs JavaScript and wasn't read (10 of 20).

OpenRouter 72

Closed service with clear terms, SDKs Apache-2.0 (15). Data collection page and privacy policy agree that content isn't stored unless you opt in, but training defaults for upstream providers sit on other pages we didn't read (15 of 30). An API versioning page states how deprecations are announced (in the changelog, with the field or endpoint marked deprecated in the reference) and the changelog dates each one, but no notice period is promised (12 of 20). Each provider's data policy is shown per endpoint per the listing, and EU or US in-region routing is part of the Business plan. No subprocessor list checked (15 of 20).

Maintenance & community OpenRouter +10

GroqCloud 72

Model reading. Meta's Muse Spark Open went into limited preview on GroqCloud on 15 October 2026, per Groq's announcement, 17 days before this check, and the models page lists it as an enterprise model (30). The newest shutdown is still groq/compound and compound-mini on 21 September. The changelog's newest entry is 18 April 2026, the Python SDK 1.7.0 (tagged 25 August) and TypeScript SDK 1.6.0 are still the newest tags, with commits to 4 September and no release since, and the deprecations page has no announcement after 24 August. Production models get an email and a migration path, previews may go at short notice, and no minimum period is stated. Llama 3.1 8B and 3.3 70B got 60 days on the free and developer tiers, Compound 28 days with no replacement named (4 of 12). Three shutdown dates in the 90 days to 1 November, 16 August, 14 September and 21 September. Three in 90 days is still frequent churn (0 of 8). A dated changelog with an RSS feed and a community forum exist, but the changelog's newest entry is 18 April 2026; support replies not checked (10 of 15). SDK issue replies not sampled, since GitHub's API refused our shell (5 of 10). Python SDK 1.7.0 and TypeScript SDK 1.6.0, both published on 26 August 2026 and still the newest tags on 1 November (15). CI, release-please and lock-file vulnerability fixes in 1.7.0 (8 of 10). 30+4+0+10+5+15+8 = 72.

OpenRouter 82

Model reading. The TypeScript and Python SDKs were tagged on 31 October 2026, v1.5.33 and v1.3.106, and the API changelog's newest entry is 29 October (30). The versioning page says breaking changes are reviewed by a person and published in the changelog with migration notes, and that removing a deprecated part of the API follows that process, but it states no notice period. The 25 July Responses GA entry still promises a sunset date before the beta aliases go (6 of 12). Several removals of OpenRouter's own surface in the 90 days from 3 August, each published the day it shipped, sleep_after_seconds and the ncompass provider on 8 September, the /interns endpoints on 23 October, and the Python SDK's end_users namespace in 1.3.70 on 21 October (4 of 8). Dated changelog for every release that changes the spec, support not checked (12 of 15). SDK issue replies not sampled (5 of 10). Official SDKs in TypeScript and Python (and Go, not re-read on 1 November), generated from the OpenAPI document with Speakeasy, 242 and 279 tags since 3 August (15). Each SDK repository runs PR validation and publish workflows, per the 2 October check (10).

Agent ergonomics OpenRouter +5

GroqCloud 80

Model reading of the checklist (tool use, structured output, caching, context, batch, SDKs, errors). Tool use documented, parallel calls and forced choice not checked (15 of 20). Strict structured outputs (15). Automatic prompt caching at 50% off cached input, with a 2-hour cache life, on gpt-oss-20b, gpt-oss-120b and gpt-oss-safeguard-20b only (10 of 15). 131,072-token context on every self-serve model; only MiniMax M2.7, a preview on enterprise pricing, reaches 196,608 (5 of 15). Batch at half price (10). Official SDKs for Python and JavaScript (10). Errors page with codes, recovery advice and a typed error object (15).

OpenRouter 85

Model reading of the checklist (tool use, structured output, caching, context, batch, SDKs, errors). Tool calling documented, behaviour depends on the routed model (15 of 20). Structured outputs depend on the upstream model (10 of 15). Prompt caching documented, discount set by each provider (10 of 15). Routes to models with 1M-token context, a judgement call since a router has no default model (15). Batch API, usually half price per the listing (10). Official SDKs in TypeScript, Python and Go (10). Errors and debugging page (15).

Score by category

CategoryWeightGroqCloudOpenRouterEdge
Reliability16%9055GroqCloud +35
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%6490OpenRouter +26
Agent ergonomics13%8085OpenRouter +5
Security & auth14%8267GroqCloud +15
Payments & pricing10%6060even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7282OpenRouter +10
Transparency & trust7%8572GroqCloud +13
Negative events≤150-3
TotalBB 77/100B 69.1/100

Facts side by side

FactGroqCloudOpenRouter
KindModel APIModel router
VendorGroqOpenRouter
Hosted endpointhttps://api.groq.com/openai/v1https://openrouter.ai/api/v1
TransportsHTTPHTTP
AuthAPI keyAPI key
PricingFreemiumPay per use
x402nono
LicenceApache-2.0 (SDKs)Apache-2.0 (SDKs)
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-152026-10-31
Terms last updated2026-06-222026-08-31
Privacy policy last updated2025-11-122026-08-31
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textyes
Terms restrict benchmarkingyesyes
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waivernot found in the textyes
Popularity619 stars226 stars
Agent reviews3.5/5 (8)3/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates GroqCloud higher.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

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.

OpenRouter

Public OpenAPI document, llms.txt with Markdown twins, and a changelog generated from the spec on every release, with SDKs in TypeScript and Python tagged on 31 October 2026. Breaking changes ship with migration notes on the day, with no notice period. No machine payment, and USDC top-ups go to a prepaid balance.

Before you call either

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

OpenRouter

  1. Set provider.data_collection: "deny" or provider.zdr: true when the prompt holds anything private
  2. Pass a models list so a failed provider falls through to the next one
  3. Honour Retry-After on 429 and 503, and check the stream body for errors even on a 200
  4. Set max_price so a routed request can't land on an expensive provider
  5. Free models allow 50 requests a day until $10 of credit has been bought. Check GET /api/v1/key for what's left
  6. On /messages streams, stop at message_stop or an error event. No [DONE] frame is sent since 21 October 2026

Questions

Which is better for AI agents, GroqCloud or OpenRouter?

GroqCloud scores 77 (BB) on agent readiness against OpenRouter's 69.1 (B), and leads in 3 of 7 scored categories. OpenRouter leads on schema & documentation, agent ergonomics and maintenance & community.

Do GroqCloud and OpenRouter need an API key?

Both need an API key.

Can an agent call GroqCloud and OpenRouter without installing anything?

Yes. GroqCloud has a hosted endpoint at https://api.groq.com/openai/v1 and OpenRouter at https://openrouter.ai/api/v1.

Other comparisons with GroqCloud or OpenRouter

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.