Common REST statuses
400for malformed cursors or invalid query combinations401for missing or invalid credentials403for keys that do not have access to the requested operation404for missing trader or asset subjects on stats reads422for validation failures429for rate limiting
Common MCP failures
- missing MCP credentials
- invalid partner API key
- partner API key without access to the requested operation
- invalid tool arguments
Operational guidance
- Log and preserve
requestIdfrom REST failures when asking for support. - Prefer explicit time bounds and limits when an agent is exploring large result sets.
- If a response is narrower than expected, check the echoed applied bounds and remember that some rows can be silently suppressed by access or eligibility rules.
- Use the generated API reference for endpoint-specific error examples and response schemas.