Groq

Live·4 models

Open-weight models served fast enough that latency stops being the thing you design around.

Lowest latencyCheap open weightsHigh throughput

4 models on Groq

Groq's own rate for each of these. Where another provider serves the same model it may charge differently. The model page shows every route side by side.

Model	Price	Context
Llama 3.1 8B Instructmeta/llama-3.1-8b-instruct	$0.050 in$0.080 out	131K
GPT-OSS 20Bopenai/gpt-oss-20b	$0.075 in$0.300 out	128K
GPT-OSS 120Bopenai/gpt-oss-120b	$0.150 in$0.600 out	131K
Llama 3.3 70B Instructmeta/llama-3.3-70b-instruct	$0.590 in$0.790 out	131K

Availability, from our vantage point

What Groq looked like from Multigrid's servers, not Groq's own uptime figure, which only they can publish.

Probes 99.98%Real traffic no traffic yet

The ring is reachability probes, measured across 100% of the last 30 days a share of what we watched, not of the month. We probe when someone loads this page, so the gaps are ours.

Succeeded
Failed on a degraded day
Failed on a bad day (< 50%)
Nothing measured yet

The two lanes are never averaged. Probes ask whether Groq is answering at all; traffic is the share of real requests we routed there that completed. A provider can pass every probe while completing nothing, which is why they are stacked rather than blended, and why a green top lane over a red bottom one is the pattern worth looking for.

Coverage is ours, not theirs: we probe when someone loads the status page, at most once every five minutes, so an empty slot means we were not looking rather than that anything was wrong. For an authoritative account of an incident, read Groq’s own status page. They are the only ones who can write it.

None of this is latency. What happened to your own requests (timing, errors and cost per provider) is on your analytics page, measured from traffic you actually sent.

How this provider is reached

Wire format: openai
Base URL: https://api.groq.com/openai/v1
Route order: Ranked by price, per model: where another provider serves the same model more cheaply, that one is tried first. Your own key outranks every platform route.
Billing: We hold a platform key, so usage can be charged to your Multigrid balance. Your own key, if you add one, is still preferred over ours.

Data handling and compliance

Multigrid does not publish Groq’s retention window, training terms or certifications. We hold no audit report for them, have no contract obliging them to anything beyond their ordinary API terms, and could not tell you if any of it changed tomorrow, so anything stated here would be hearsay in a document your own auditor may read.

Their own documentation is authoritative and stays current without us. What we can tell you is what Multigrid does with the request on our side, which is on the Trust Center.

Groq docs Their status page Privacy policy Terms

Headquartered in US. That is the company’s jurisdiction, not where your request is processed — which is not something this gateway can pin or promise. See where your requests go.

Use in a policy

Prefer, or exclude, Groq on any request. The slug is what the gateway matches on.

"provider": {
  "order": ["groq"],
  "allow_fallbacks": true
}

Provider preferences docs

Reach Groq on one balance

We hold a platform key for Groq, so everything above is reachable on Multigrid credit: one balance across every vendor, at the prices listed. Signing up takes no card and commits you to nothing. If you already have a Groq contract, bring that key instead and we take no percentage on the traffic.

Create an account Bring your own key