Skip to main content
POST
/
v1
/
api-keys
Create API Key
curl --request POST \
  --url https://api.agent-drop.com/v1/api-keys \
  --header 'Authorization: <authorization>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "name": "<string>"
}
'
{
  "id": "<string>",
  "name": "<string>",
  "api_key": "<string>",
  "created_at": "<string>"
}

Documentation Index

Fetch the complete documentation index at: https://docs.agent-drop.com/llms.txt

Use this file to discover all available pages before exploring further.

Generate a new API key for your account. Use separate keys for different agents, environments, or team members.
The API key value is returned once in this response. Store it immediately. You cannot retrieve it later.

​
Request

​
Headers

​
Authorization
string
required
Bearer token. Example: Bearer agd_live_xxxxxxxxxxxxxxxxxxxx

​
Body

​
name
string
required
A descriptive name for this key. Examples: production-agent, staging, crewai-pipeline.

​
Response

​
id
string
The key ID, used for revocation.
​
name
string
The name you assigned to this key.
​
api_key
string
The full API key. Starts with agd_. Can be revealed again later from the dashboard.
​
created_at
string
ISO 8601 creation timestamp.

​
Examples

curl -X POST https://api.agent-drop.com/v1/api-keys \
  -H "Authorization: Bearer agd_live_xxxxxxxxxxxxxxxxxxxx" \
  -H "Content-Type: application/json" \
  -d '{"name": "production-agent"}'

​
Response

{
  "id": "key_xyz789",
  "name": "production-agent",
  "api_key": "agd_live_zzzzzzzzzzzzzzzzzzzz",
  "created_at": "2026-03-22T12:00:00Z"
}

​
Key Limits by Plan

PlanMax API Keys
Free1
Builder5
Team15
Scale50
EnterpriseCustom
Creating a key beyond your plan’s limit returns 403 Forbidden.

​
Errors

StatusCodeDescription
401UNAUTHORIZEDInvalid or missing API key
403KEY_LIMIT_REACHEDYou’ve reached the API key limit for your plan