Rate Limits
Request limits for Weely developer APIs and MCP.
Rate Limits
Weely applies rate limits so the API and MCP stay reliable for everyone. Final plan-based quotas will be published here; treat the guidance below as orientation until then.
Status
| Area | Status |
|---|---|
| MCP | Per-client limits apply |
| REST API | Platform and plan quotas coming soon |
| Published quotas | Coming soon |
Planned shape (subject to change)
Limits will depend on your Weely plan. Expect something in this family:
| Window | Orientation (not final) |
|---|---|
| Per minute | Tens of requests |
| Per hour | Hundreds to low thousands |
| Per day | Higher daily ceiling by plan |
Do not hard-code these placeholder figures into production integrations.
When you are limited
Throttled calls return HTTP 429. A typical body:
{
"error": "rate_limit_exceeded",
"message": "Too many requests. Try again shortly."
}Retry with exponential backoff. Respect Retry-After when the response includes it.
Tips
- Cache reads (
short_url:read, analytics) when you can - Prefer bulk endpoints over tight create/update loops
- Use MCP tools for agent workflows instead of hammering REST from a script
- See Authentication for tokens and scopes
Final platform and plan limits will be published here when the public developer host is fully live.