Skip to main content
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.
All limits are enforced per account. Exceeding a limit returns a 429 Too Many Requests response with a Retry-After header.

Transfer Limits

  • Each POST /v1/transfers call 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/download call decrements the counter
  • When the counter hits 0, the transfer status changes to downloaded and further download attempts return 410 Gone
  • Set max_downloads in your POST /v1/transfers request to control this

Transfer Expiry

  • Set expires_in when creating a transfer: 1h, 12h, 24h, 7d, 14d, 30d, 90d
  • Expired transfers return 410 Gone on 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 a 429 response, wait for the duration specified in the Retry-After header before retrying.