Rate Limit Tiers
The AgentPowers API uses per-IP rate limiting to ensure fair usage and protect against abuse.| Tier | Limit | Applies To |
|---|---|---|
| Public read | 60 requests/minute | Unauthenticated GET endpoints (search, skills list, categories, detail) |
| Authenticated read | 10 requests/minute | Authenticated GET endpoints (earnings, purchases, profile) |
| Write | 20 requests/minute | All POST, PATCH, DELETE endpoints (publish, checkout, reviews) |
Response Headers
Every API response includes rate limit headers:| Header | Description |
|---|---|
X-RateLimit-Limit | Maximum requests allowed in the current window |
X-RateLimit-Remaining | Requests remaining in the current window |
X-RateLimit-Reset | Unix timestamp when the window resets |
Handling 429 Responses
When you exceed the rate limit, the API returns a429 Too Many Requests response:
Retry-After header indicates how many seconds to wait before retrying.
Recommended Strategy
- Respect
Retry-After— wait the specified number of seconds before retrying - Exponential backoff — if
Retry-Afteris not present, use exponential backoff starting at 1 second - Cache responses — cache search results and skill details to reduce request volume
- Batch operations — for bulk installs or updates, add a small delay (200-500ms) between requests
Example: Python with Retry
Notes
- Rate limits are per IP address, not per user
- The CLI (
apcommand) includes built-in retry logic for rate-limited requests - The MCP server plugin handles rate limits transparently
- If you need higher limits for integration purposes, contact us