Authorization: Bearer ...: an AgentDoor agt_ token, an MCP or ChatGPT login, or a web app session. Every token that belongs to the same Fere account shares one budget. People on the same office or mobile network do not use up each other’s budget.
The default can change. When you are limited,
Retry-After tells you how long to wait. Trust that number over the table.
Tool calls made from inside a Fere code sandbox have their own budget, so they do not use up the account’s budget.
rate_limited: wait, then continue
HTTP 429. The response includes Retry-After, a whole number of seconds (at least 1) until the next window starts.
What to do:
- Wait at least
Retry-Afterseconds, then send the same request again. Retry once, not in a tight loop. - Do not register a new AgentDoor key or sign in again to get a new budget. Every token for the account shares the same budget.
- If you poll prices, positions or PnL, poll less often.
Sign-up and token limits
The AgentDoor sign-up and token routes (/v1/auth/register, /v1/auth/verify and /v1/auth/token) have their own limit, per client IP, because no account exists yet. See Agent API authentication.
