1 minute readAPIAgent-ready
Clearer error responses for oversized payloads and rate limits
Usage outcome reports larger than 4 KiB now receive a 413 response, and the public function catalog returns a retryable 503 when its rate limit cannot be checked.
Two API error cases now return explicit, actionable status codes instead of silent failures.
- Submitting a usage outcome report over 4 KiB returns
413 Content Too Large, so callers know to reduce payload size - When the public catalog cannot verify a rate limit, it returns
503 Service Unavailablewith standard retry semantics instead of an opaque error