Skip to main content
AgentKey uses a single master key to authenticate every request your agent makes. One key covers all eight tool categories — search, scrape, social, crypto, finance, business, e-commerce, and account — and is tied directly to your shared credit balance. You do not wire up per-provider credentials or manage multiple tokens. Once your key is in place, your agent can call any of the 1,800+ tools without any additional authentication setup.

​
Your master key

Your key looks like ak_ followed by a long random string, for example ak_abc123.... You create and manage keys from the console. Each key is scoped to your account, so a single compromised key can affect your entire balance and all services.
Your master key is a secret. Anyone who has it can make requests and spend your credits on your behalf. Never commit it to source control, embed it in client-side or browser code, or paste it into a public chat, a shared document, or a screenshot.

​
How to set up your key

1

Create a key in the console

Sign in to the console and generate a new master key. Copy the value — it is shown only once in full. Store it somewhere secure immediately, such as a password manager.
2

Add credits to your balance

Your key is linked to a pay-as-you-go credit balance. Top up your balance from the console before making your first call. See Pay-as-you-go for how costs work across different tools and providers.
3

Provide the key during install

After you install AgentKey, the setup flow prompts you for your key and stores it in the correct location for your agent and operating system. Follow those prompts exactly — do not hard-code the key into a project file or an environment variable you commit to version control.

​
Storing keys safely

Keeping your key secure is straightforward if you follow a few simple practices:
  • Let the setup flow store the key. The installer places your key in the right location for your environment. Do not copy it into .env files, config files, or scripts that live in a repository.
  • Use a separate key per environment. Create distinct keys for development, staging, and production. That way you can rotate or revoke one key without disrupting the others.
  • Rotate immediately if a key is exposed. If you accidentally commit a key, paste it in a chat, or suspect it has been leaked, go straight to the console, revoke the old key, and generate a new one. Update any running installations promptly.
The exact steps for provisioning and rotating keys — including per-environment setup — are confirmed during installation and available in the console. This page describes the general authentication model; refer to the console for the authoritative workflow.