Connect and manage API keys
Manage LLMIC provider credentials, distinguish client-specific keys from account-wide fallbacks and test saved connections safely.
API Connections gives you one place to manage credentials used by supported LLMIC tools. Core crawling does not require an AI provider key, but optional connected features need the appropriate provider account and access. Saving a key is only a storage action. A successful provider request is needed to confirm that the credential can perform the operation you want.
What this guide helps you do
An API integration lets LLMIC request data from a service you choose while keeping the connection understandable. This guide explains provider setup, credential storage, permission checks and how to remove a connection.
Open the connection panel
Open Settings and find API Connections in Integrations. The panel lists supported services and whether a key is saved. Choose the provider you intend to use, paste the credential into its own field and save it. Do not reuse unrelated tokens merely because their text looks similar. Google service-account JSON and a simple provider API key are different credential formats.
Choose the correct scope
Read the scope shown in the panel before editing. AI keys are shared across the signed-in account’s app workspace, while Google, SerpAPI and Radar can use the active client. An app-wide fallback can be used where that client has no saved credential. Account-wide does not mean shared across every signed-in identity on the Mac; account isolation is a separate boundary.
Test the saved connection
Use Test saved connection where it is available. The app notes that tests make provider requests and may consume quota. Test using the active client scope when you want to confirm the credential that a client’s tools will use. If the test fails, check provider permissions, account billing, model access and quotas. Repeatedly saving the same key will not repair missing permissions.
Manage AI providers and budgets
For supported AI recommendations, connect the provider you intend to use, such as OpenAI, Gemini or Claude. Review AI models & budgets where available before generating larger batches. Provider pricing and model availability can change, and a key working for one operation does not establish access to every model. Review generated suggestions and schema drafts before publishing them on a website.
Remove or rotate credentials
Use the relevant Remove key or Remove client key action when a connection is no longer needed. Removing a stored key from LLMIC is different from revoking that key at the provider. If a secret was exposed, revoke or rotate it through the provider as well. Credentials use macOS Keychain, but you should still avoid including them in exports, screenshots, messages or support requests.
Quick reference
| State or scope | Meaning |
|---|---|
| Key saved | Stored, not necessarily validated |
| Test saved connection | Makes a provider request |
| Active client | Credential associated with that client |
| App-wide fallback | Used when a client has no saved key |
| Remove key | Does not itself revoke the provider credential |
Continue learning
Next, configure Google data sources, understand account separation. Return to the documentation home to explore other guides. If the result differs from these instructions, contact support with your app version and the relevant steps. Remove private information from screenshots and never include API keys or passwords.
Frequently asked questions
Manage LLMIC provider credentials, distinguish client-specific keys from account-wide fallbacks and test saved connections safely.
Have the current LLMIC build, the account that should own the workspace, and any required subscription or provider access ready. Follow the prerequisites on this page before changing macOS security, account, or billing settings.
Check the app version, account email, selected plan or provider, permission state, and the exact message shown on screen. Those details are more useful than assuming that every setup problem has the same cause.
Follow the steps in order and stop at the first result that differs from the guide. Record that step and the exact message before retrying, reconnecting an account, or contacting support.
Confirm the expected screen or account state described in the Check the result section. Installation, authentication, provider connection, and subscription access are separate outcomes, so verify the one this guide covers.
This workflow confirms the visible setup result described here. It does not certify unrelated features, future updates, every Mac configuration, provider availability, or a payment outcome that was not completed.
Save or export the evidence, assign the approved action, and use the related guides linked on the page for the next check. After implementation, repeat the same workflow against a fresh crawl so the result is comparable.