# Connect Groq > Connect a Groq API key, add a conversational feature and verify responses, model access and rate-limit recovery on a phone preview. Canonical: https://www.rnblocks.dev/docs/connectors/groq Updated: 2026-10-01 Use Groq to power an AI chat feature with a model available to your Groq account. Groq is the provider listed in Studio; it is different from Grok. ## Before you start - An app in Studio. - A Groq account with an API key and access to the model your app will request. ## Get a Groq API key Section: https://www.rnblocks.dev/docs/connectors/groq#key Open the [Groq quickstart](https://console.groq.com/docs/quickstart) and follow **Create an API Key** to Groq Console. Create a key for this app and copy the secret value privately. ## Connect Groq to this app Section: https://www.rnblocks.dev/docs/connectors/groq#connect 1. **Open the app in Studio** — Select **App options (+) → Connectors → Groq**. A **Connect Groq** request in the conversation opens the same setup. Connections belong to the app you have open. 2. **Save the credential privately** — Paste your credential into **API Key** and select **Save**. Keep it out of the conversation and app source. RNBlocks stores the credential for this app; the saved value is masked in this form. 3. **Return to your conversation** — Close the connection panel and continue the feature you requested. **Connected** means a credential is saved; the feature still needs a successful request and a test in your app. ### Figure: Connect Groq, step by step App options (+) opens Connectors. Choose Groq, enter its API Key privately and select Save. The saved view masks the value and shows Connected. 1. **App options** — The actual App options menu above the + button. It contains separate Supabase, Connectors and App memory actions. 2. **Choose a service** — The Connectors catalogue contains OpenAI, Anthropic, Groq, ElevenLabs and Replicate cards with their own logos. 3. **Add your key** — Groq connector detail with its original logo, use cases, documentation link, private API Key field and Save button. The field is empty. 4. **Saved connection** — Illustrative saved Groq connection. Connected appears beside its name, the saved value is masked, and Update and Disconnect controls are available. No credential is shown. 1. Open App options (+) → Connectors in the app you want to connect. 2. Choose Groq in the catalogue, then enter your API Key in its private form and select Save. 3. Return to the conversation and test the feature. Connected means a credential is saved, not that a provider request has succeeded. The actual connection screens. Empty form and illustrative saved state; no credential is shown. ## Try a useful conversation Section: https://www.rnblocks.dev/docs/connectors/groq#test For example: “Add a study helper using Groq. Let me ask about a topic, get a short explanation and then answer one practice question.” 1. **Ask a short question** — In the iOS or Android preview, ask the helper to explain a topic. Check the response and the loading state. 2. **Continue the exchange** — Answer the practice question and verify that the app uses the relevant previous message. Check saved history separately if your app includes it. 3. **Check a recoverable error** — Make sure a failed response leaves your question visible and gives you a way to try again. Avoid repeated automatic retries while diagnosing a quota problem. ### Figure: A conversation in Aria Aria’s dark native chat screen shows a request to plan a relaxed weekend and an example assistant response. A message field sits above Chat, History and Profile tabs. 1. Send a short request and check the response in the native preview. 2. If the app promises history, reopen it and check that each person sees their own conversations. Aria’s native chat layout, illustrated from the app with an example conversation. ## Handle model and rate-limit errors Section: https://www.rnblocks.dev/docs/connectors/groq#recovery Check the active model and limits in your Groq account. A model name used in an older example may no longer be available. Rate limits can apply even when the key is valid; review [Groq’s rate-limit guidance](https://console.groq.com/docs/rate-limits) and let Studio inspect the exact error. ## Costs and the information your app sends Section: https://www.rnblocks.dev/docs/connectors/groq#costs-and-data Your connected provider handles its own API usage and billing. Those charges are separate from RNBlocks credits used while building your app. Review the provider’s quota and billing before testing with a large audience. An AI feature sends the information needed for that request to its provider. Decide what your app should send, explain that clearly to your users, and test any permission and decline choices before release. Connecting a service does not automatically add a saved history, private file library or every feature in that provider’s API. - [Understand credits and usage](https://www.rnblocks.dev/docs/credits-and-usage) ## Update or disconnect Section: https://www.rnblocks.dev/docs/connectors/groq#manage Open **App options (+) → Connectors → Groq**. To replace the saved credential, enter the new value and select **Update**, then test the feature again. **Disconnect** removes this app’s saved Groq credential. Features that use it will need a working connection again. It does not close your provider account, cancel provider billing, revoke the original key at the provider, or erase data already sent there. Reopen Connectors to check the saved connection state. ## Continue - [Connector overview](https://www.rnblocks.dev/docs/connectors) - [Connect Supabase for saved conversations](https://www.rnblocks.dev/docs/connectors/supabase) - [Preview and test](https://www.rnblocks.dev/docs/previewing-screens) ## Official references - [Groq API quickstart](https://console.groq.com/docs/quickstart) - [Groq rate limits](https://console.groq.com/docs/rate-limits)