API
Rate limits.
Rate tiers are part of the API key model now; enforcement and customer dashboards are the next operational layer.
Tier guidance
DemoBrowser demonstrations and low-volume tests. Suggested limit: 20 requests/minute.StandardNormal local agent and Telegram usage. Suggested limit: 60 requests/minute.DeskHigher-volume integrations and raw data access. Suggested limit: 300 requests/minute.The account UI already stores a key's
rate_tier. Hard rate enforcement should be added before paid public onboarding.HTTP/1.1 429 Too Many Requests
Retry-After: 60
Content-Type: application/json
{
"error": "rate_limited",
"message": "Too many requests for this API key."
}
Target response
This is the intended shape once rate enforcement lands. Until then, agents should still behave conservatively and avoid unnecessary polling.