Getting Started

Getting Your API Key

API keys are issued by admin-tools after email verification. The whole flow takes under a minute.

Step 1: Request a key

Call get_api_key on admin-tools. No auth required for this endpoint.

$curl -X POST https://admin.gtm-engine.sh/api/v0/get_api_key \
>  -H "Content-Type: application/json" \
>  -d '{"email": "you@yourcompany.com"}'
1{ "status": "verification_sent", "email": "you@yourcompany.com" }

Step 2: Verify the email

Open your inbox. WorkOS sends a “Verify your email” message — click the link.

After verification, you’ll be redirected to console.gtm-engine.sh where the API key is shown. The key is prefixed sk_ and is only displayed once. Save it now.

Step 3: Store the key

Set it as an environment variable.

$# macOS / Linux
$export GTM_ENGINE_API_KEY="sk_..."
$
$# Persist across shells
$echo 'export GTM_ENGINE_API_KEY="sk_..."' >> ~/.zshrc

For MCP clients, the key goes into the Authorization header in your client config:

1{
2  "mcpServers": {
3    "socials-tools": {
4      "url": "https://socials.gtm-engine.sh/mcp",
5      "headers": { "Authorization": "Bearer sk_..." }
6    }
7  }
8}

Step 4: Verify it works

$curl https://admin.gtm-engine.sh/api/v0/get_token_balance \
>  -H "Authorization: Bearer $GTM_ENGINE_API_KEY"

You should see your balance (100 for new accounts) and the per-tool cost map.

Free starter balance

New accounts receive 100 free tokens. That’s enough for ~6 LinkedIn employee searches, ~20 email lookups, or ~6 full signal sweeps. Top up via buy_tokens when you need more.

Rotating keys

Provision a new key the same way. Old keys remain active until you contact support to revoke them — there’s no per-key dashboard yet.

Troubleshooting