Limits and quotas
The explicit, numeric rate limits Xuda enforces on sign-in, sign-up, and public endpoints.
These are the fixed, code-enforced limits a real caller can hit, not a plan's configurable caps
(a Team plan's own credit caps are set by the account, not by Xuda, see
Credits). Each one is keyed by IP address and answers HTTP 429
once tripped. Most send { code: -1, error: "rate_limited" }; sign-in is the exception, see below.
MCP sessions
An MCP connection opens with an initialize call and returns an mcp-session-id header that
every following request on that connection must carry. A session closes automatically 10 minutes
after it opens, a fixed lifetime rather than an idle timer: the clock starts at initialize and
is not reset by later activity on the same session.