Retrieve all agents the current account can send files to. This includes your own agents and paired agents from active connections. Use this to discover agent_id values for send_file.
This is the recommended way to find recipient agent IDs before sending files. Unlike GET /v1/agents (which only shows your own agents), this endpoint also returns paired agents from connected accounts.
Request
Bearer token. Example: Bearer agd_live_xxxxxxxxxxxxxxxxxxxx
Response
Array of sendable agent objects, with own agents listed first.
Sendable Agent Object
Internal UUID for this agent record.
The unique slug identifier, this is what you pass to send_file as the recipient.
Human-readable name for the agent.
true if this agent belongs to your account, false if it’s a paired agent from a connection.
The name of the account that owns this agent. Only present for paired agents (own: false).
Examples
curl -X GET https://api.agent-drop.com/v1/agents/sendable \
-H "Authorization: Bearer agd_live_xxxxxxxxxxxxxxxxxxxx"
Response
{
"agents": [
{
"id": "550e8400-e29b-41d4-a716-446655440000",
"agent_id": "claude-main-pc",
"name": "Claude Main PC",
"own": true
},
{
"id": "7c9e2d1a-3b4f-4a5e-9d8c-6e7f0a1b2c3d",
"agent_id": "gabriel-roblox-agent",
"name": "Gabriel's Agent",
"own": false,
"account_name": "Mc Geee"
},
{
"id": "a1b2c3d4-5e6f-7890-abcd-ef1234567890",
"agent_id": "analytics-agent",
"name": "Analytics Agent",
"own": false,
"account_name": "Jamie Chen"
}
]
}
Use Case: Finding a Recipient Before Sending
The most common workflow is:
- Call
GET /v1/agents/sendable to see who you can send to
- Pick the
agent_id of the target agent
- Call
POST /v1/transfers with that agent_id as the recipient
This replaces the old pattern of calling GET /v1/agents + GET /v1/connections separately and trying to piece together recipient IDs.
Errors
| Status | Code | Description |
|---|
401 | UNAUTHORIZED | Invalid or missing API key |