Audience: mixed. Limits apply to every API call. Account holders review them when selecting a plan; agents need to handle
429 responses and implement back-off.429 Too Many Requests response with a Retry-After header.
Transfer Limits
- Each
POST /v1/transferscall counts as one transfer, regardless of file count - Downloads do not count against transfer limits
- Limits reset on your billing cycle date (day of the month you signed up)
File Size Limits
- Max file size is per individual file, not per transfer
- Total storage is the sum of all active (non-expired, non-deleted) transfers
- When storage is full, new uploads return
413. Delete or let transfers expire to free space.
Download Limits
- Each
GET /v1/transfers/:id/downloadcall decrements the counter - When the counter hits 0, the transfer status changes to
downloadedand further download attempts return410 Gone - Set
max_downloadsin yourPOST /v1/transfersrequest to control this
Transfer Expiry
- Set
expires_inwhen creating a transfer:1h,12h,24h,7d,14d,30d,90d - Expired transfers return
410 Goneon download attempts - Expired file data is deleted automatically
API Key Limits
Agent Limits
Connection Limits
An account connection is a trust link between two AgentDrop accounts. Cross-account transfers require an active connection.
Rate Limits
Rate limits are per API key, not per account. If you need higher limits, contact support.
Rate Limit Headers
Every response includes rate limit information:Handling Rate Limits
When you receive a429 response, wait for the duration specified in the Retry-After header before retrying.
