Platform API: daily rate limits removed on several endpoints, new rate limit headers

The Platform API no longer applies a daily request cap to these endpoint groups:

End Users API (/v2/end-users/)
Conversations API create, read, update, end, end-handoff, attachment, and messaging endpoints
Knowledge API article endpoints (/v2/knowledge/articles/)

Per-minute and per-second limits stay the same for these endpoints. See the global rate limits and each API’s own reference page for the current values.

New rate limit headers

The Platform API and the MCP server now return X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset on every successful authenticated response. A 429 response caused by rate limiting also returns Retry-After. Use these headers to pace your requests and avoid hitting a limit. See rate limit headers and working with rate limits for details.

MCP server limits

Since September 8, 2026, the MCP server has applied a budget per AI Agent. An OAuth-authenticated request is budgeted per user instead of per Agent. See the MCP server row in the rate limits table for the current values. Today’s change adds the rate limit headers above to MCP responses. The MCP limits themselves do not change.