Groq through Squiid

What Groq is

Groq is an inference provider rather than a model lab. It hosts open-weight models on custom Language Processing Unit hardware and serves them through an OpenAI-compatible API, with tokens per second that are typically several times what a GPU-hosted copy of the same model returns. It also serves speech models for fast transcription. Because the API keeps the OpenAI shape, moving a route from a frontier provider to Groq is a configuration change rather than a rewrite, which is how most teams end up trying it.

Speed changes what you can build. In a vibe-coded app Groq is the provider you pick for anything a human is waiting on: autocomplete that has to keep up with typing, a voice agent where a pause reads as a failure, streaming UI that should finish before the user looks away, or an agent loop that makes twenty small model calls per action and cannot afford a second each. It is usually paired with a frontier model, fast tier in front and a careful tier behind.

Why connect it through Squiid

Running two or three providers means two or three keys, which is the problem Squiid exists to remove. Groq is provisioned instantly, the upstream key stays with Squiid, and calls go to https://api.squiid.io/v1/groq/... with Authorization: Bearer $SQUIID_API_KEY. OpenAI-compatible clients work by pointing their base URL at the gateway (gateway convention). Tokens are metered at Groq's published per-model rate against your credits, shown beside every other service in the dashboard, and settled on one invoice. Auto top-up with a ceiling keeps a latency-critical route funded without handing anyone an open-ended card.

• One account, one key, one bill, one dashboard. Groq sits beside every other service your project uses, on the same invoice and the same credit balance.
• Key custody. Squiid holds the Groq credentials. Your code carries SQUIID_API_KEY, so GROQ_API_KEY, GROQ_BASE_URL never land in a repository, a preview deployment or an agent’s context.
• Metering you can see. Every call is counted per service and per day, so you know what Groq costs before the month ends.
• Pause on zero. When prepaid credits run out the gateway stops authorizing usage instead of running up a bill you did not fund.
• One rotation. Rotating the Squiid key cuts off every agent, worker and deployment at once, with no provider key to hunt down.

What you get

• Open-weight models on LPU hardware at high tokens per second
• OpenAI-compatible endpoints through the gateway
• Fast speech to text on the same key
• Latency-tier and quality-tier providers under one credential
• Groq list pricing, no markup

How to connect Groq

One variable replaces the provider credentials this service would normally need. Requests go to the gateway and the official SDKs work by pointing their base URL at it (gateway convention).

# .env
# replaces GROQ_API_KEY, GROQ_BASE_URL
SQUIID_API_KEY=sq_live_xxxxxxxxxxxxxxxxxxxxxxxx

# every request: https://api.squiid.io/v1/groq/...
# header:       Authorization: Bearer $SQUIID_API_KEY

Pricing through Squiid

Groq charges per input and output token by model, and per audio hour for speech models, at the provider's listed price. Squiid passes that through at par: one dollar of prepaid credit is one dollar of Groq usage, with no markup and no per-request margin.

Groq has no subscription attached on Squiid today. If a plan is required for a feature you need, it passes through at the provider’s listed price with no Squiid fee.

Squiid adds no markup to provider prices. There is a free plan at $0 a month with a 15% fee when you top up credits, Solo at $19.97 a month with a top-up fee that starts at 8% and falls to 3.5% as your spend grows, Team from $29.97 a seat a month with the same ladder one point lower, and Custom with a rate of 3% or less. Credits are prepaid, so Groq usage stops when the balance reaches zero rather than producing an invoice you did not fund. Auto top-up with a cap keeps production running without handing anyone an open-ended card.

If you leave

Nothing to move: Groq is usage-metered, so leaving means creating your own Groq key and pointing the client at it. Squiid never owns your code, your schema or your domain, and the gateway speaks Groq's own API, so the client change is a base URL. The handover page lists what happens for every provider in the catalogue.

Works with every coding agent

Groq through Squiid is just an HTTP call with a bearer token, so every agentic coding tool can use it with the single key already in your environment:

• Claude Code
• Cursor
• ChatGPT
• Codex
• Grok
• Gemini CLI
• GitHub Copilot
• Windsurf
• Perplexity
• Devin
• Replit
• v0
• Lovable
• Cline

Vibe coding a feature on Groq usually means asking for it in plain language and letting the agent write the integration. Because the key is Squiid’s rather than the provider’s, it can do that without ever holding a credential that could be leaked, logged or committed.