Verity Mod Groq API Key Setup

What the Groq API key does

Verity JE can use Groq to send a prompt to a cloud language model and receive a response. The API key authorizes those requests under your Groq account. It is not a Verity download code, a Minecraft login, or a value that this website should ever receive.

Treat it like a password. Anyone who obtains it may be able to make requests under your account until it is revoked or limited. Create it in GroqCloud, enter it only in the Verity JE settings on your computer, and keep it out of screenshots, logs, chat, streams, and repositories.

Before creating an API key

Finish the non-AI part of the Java setup first. Minecraft should launch with the exact loader and game version. Verity JE and its current dependencies should load in a clean profile. The companion or documented interaction should appear in a new test world.

If Minecraft crashes before the title screen, a Groq API key will not fix it. Resolve Java runtime, loader, dependency, duplicate-file, or mod-conflict errors before adding a cloud provider. This also reduces the amount of configuration you need to expose while asking for help.

Use Verity JE 5.7.4 with Forge 1.20.1 for the stable setup. Its changelog records a missing Groq model fix. If an older 5.7.x file reports a missing model, check the installed mod version before repeatedly replacing a valid key. The older NeoForge 3.4.1 release and the 6.0.0 betas are separate setup targets.

Create the API key in GroqCloud

1. Open GroqCloud’s API Keys page and sign in to your own account.
2. Choose Create API Key and give the key a recognizable name such as “Verity test profile.” Keep the secret out of its name.
3. Copy the generated value into your trusted local configuration or password manager. The expected result is a new entry in your Groq project’s API Keys list, not a Minecraft login or download code.

The console says only a team owner or a user with the developer role can create or manage keys. If that control is unavailable, check your Groq project permissions; a third-party key generator cannot resolve them. Groq’s quickstart links to this same official key-creation page.

Do not create an API key through a “free key generator,” paste site, support bot, video description mirror, or form claiming to configure Verity remotely. The key comes from GroqCloud. Verity Mod Guide has no setup form and cannot validate it for you.

Enter it in stable Verity JE 5.7.4

The following labels are verified in the maintainer’s published 5.7.4 Forge artifact. They are not instructions for legacy 3.4.1 or the reworked 6.0.0 beta menu.

1. Launch the Forge 1.20.1 profile containing Verity 5.7.4. At the title screen, choose Mods, select Verity, and open Config. Expect the Verity Configuration screen.
2. Open AI Settings. Set AI Provider to GROQ and paste the generated secret into API Key, without extra spaces or quotation marks.
3. Leave AI Intelligence Level at its default, FAST, for the first connection test. This is a preset control, not a field for pasting a Groq model ID.
4. Open Local LLM and turn Use Ollama off. In 5.7.4, that switch overrides AI Provider, so leaving it on sends conversation requests to the local gateway instead of Groq.
5. Apply the changes, return to the title screen, and reopen Config to check the selected provider and switch. Keep the key field out of screenshots.

For reading an existing configuration, the corresponding names are AISettings.apiKey, AISettings.aiProvider, AISettings.aiModel, and AISettings.use_ollama. Use the in-game screen to edit them; do not copy a complete configuration from another profile or invent a beta field name.

Never paste the value into Minecraft chat; chat can be logged, shown to other players, or captured by a stream.

If the setup stores a local configuration file, protect that file as a secret. Do not include it when sharing the whole profile, uploading logs, making a modpack archive, or committing launcher files to Git. A .gitignore entry is useful for repositories, but it does not erase a secret already committed to history.

First test

Open a new test world and wait until Verity appears. Open ordinary Minecraft chat with T (or your remapped chat key), type Verity, say hello., and press Enter. The name satisfies 5.7.4’s optional General > Require Verity filter. Keep General > Immersive Mode off so it does not hide the reply. Text tests the language-model connection without involving microphone permissions, speech recognition, or voice output. Wait for one request to finish before sending another.

There are three useful outcomes:

1. Text response arrives. The cloud connection works. You can test voice separately.
2. Authentication is rejected. Re-check the API key, whether it was revoked, and whether it was entered in the correct local field.
3. Timeout or service error. Check network access, service availability, account limits, and the exact error without exposing the secret.

Record the error code or message, not the API key. When a support helper asks to “see the key,” decline. Troubleshooting does not require publishing it.

Common setup failures

Hidden whitespace: copying from a formatted document or mobile note can add spaces or line breaks. Copy directly from GroqCloud and paste into the intended local field.

Wrong profile: you may edit one launcher instance while starting another. Confirm that the configuration belongs to the profile containing your selected Verity version.

Wrong active route: in 5.7.4, turn Local LLM > Use Ollama off when testing Groq, even if AI Provider already says GROQ.

Old tutorial location: a video may show an earlier UI or config path. Compare it with the current project description and changelog.

Revoked or replaced value: if you rotated the API key, make sure the local configuration contains the new value and the old process was restarted.

Network filtering: a firewall, school network, corporate policy, VPN, or DNS filter can block the request. Test with an allowed network and follow its rules; do not disable managed security controls without authorization.

Usage or service limit: read the response and GroqCloud account information. Rapid repeated requests can make diagnosis harder and may consume more usage.

Add voice only after text works

The Verity JE project describes text AI across languages, while speech-to-text and text-to-speech were tested in English. A working Groq text response proves only the model request path. Microphone access, input device selection, speech recognition, and audio output remain separate.

Test one audio direction at a time. First verify that microphone input produces recognized text. Then verify that a known text response can be spoken. Use simple English during diagnosis. Do not replace a working API key merely because the microphone is denied by the operating system.

If the API key leaks

Revoke it in GroqCloud immediately. Rotation is the primary containment action; editing the screenshot or deleting a message may not remove copies. Create a replacement, update only the trusted local configuration, restart the affected process, and verify that the old value no longer works.

Search likely exposure locations: chat history, support posts, screenshots, stream recordings, shell history, shared profile archives, cloud-sync folders, and Git history. Remove or restrict those artifacts where possible, but still assume the old value was copied.

Ongoing hygiene

Use a separate API key for Verity so it can be revoked independently. Remove keys you no longer use. Review Groq account usage for unexpected activity. Keep prompts free of passwords, private documents, personal addresses, and information you would not send to a cloud service.

When sharing a troubleshooting log, make a copy, redact secrets completely, and inspect the final text before uploading. Do not rely on partial masking or a promise that a private message will stay private.

If you prefer not to send prompts to a cloud model, use the local Ollama setup. Ollama avoids a Groq API key but requires a running local model service and enough computer resources. It is a different privacy choice, not a one-click mode.