You can now sign in and create your own API keys

Create an account, issue an API key from the dashboard and send your first task within minutes.

What you get

• An API keys page in the dashboard where you create, name and revoke keys yourself.
• Up to five active keys per account, so each app, environment or teammate gets its own.
• One key for everything: the same Bearer key works on every endpoint of the API.

How it works

Sign in, open API keys and create a key. The full key appears once, at creation, and we keep only a hash of it, so copy it straight into your secret manager. Every request then carries it in the Authorization header.

A revoked key stops working within seconds, and your other keys keep running. Separate keys for production, staging and experiments show where traffic comes from and let you replace one key at a time.

Get started

1. Sign in at querying.ai and open API keys in the sidebar.
2. Select + New key, enter a Key name such as production and select Create key.
3. Select Copy key and store the key in your secret manager. The full key appears this once.
4. To limit the key, select Manage and set a Daily credit limit, the Allowed engines and an Expiry.
5. Export the key as QUERYING_API_KEY and send your first request:

curl -X POST https://api.querying.ai/v1/async/task \
  -H "Authorization: Bearer $QUERYING_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "taskType": "GEMINI",
    "payload": { "prompt": "best CRM for a small team", "country": "US" }
  }'

The call returns the queued task on your account, and the task appears in Activity.

Errors

MISSING_API_KEYHTTP 401

The Authorization header is missing, or its key is unknown, expired or revoked.

KEY_SCOPE_DENIEDHTTP 403

The engine is outside the key’s Allowed engines. Use another key, or add the engine in Manage key.

KEY_DAILY_CREDIT_LIMITHTTP 429

The key used up its Daily credit limit. Retry-After runs until the next midnight UTC.