peekpandaErrors and retries
Handle safe envelopes, authorization failures and rate limits predictably.
Download Markdown ↓Status codes
The public adapter maps invalid input to 400, missing credentials to 401, missing subscription to 402, authorization failures to 403, missing records to 404, conflicts to 409 and throttles to 429. A read that runs out of its time budget answers 503 timeout with Retry-After; send the same read again after it. A 403 is authorization_required for a missing scope and workspace_not_accessible for a tenancy the credential cannot reach; switch workspace for the second rather than asking for a new scope. Unexpected failures are sanitized.
Retry-After
Honor Retry-After when supplied. Do not retry unchanged 400, 401, 402 or 403 responses. Never retry an uncertain provider-writing command unless its idempotency or job-status contract makes that safe.
Freshness
A successful HTTP response proves transport and authorization only. It does not make a provider observation current beyond the source date included in the payload.
AI agent or LLM? Read this page as markdown