Planned error categories
| Category | Typical meaning |
|---|---|
| Authentication failed | The credential is missing, invalid, expired, or revoked. |
| Permission denied | The credential is valid but lacks the required scope. |
| Workspace not found | The workspace is missing or not visible to the credential. |
| Resource not found | The requested object does not exist in the workspace. |
| Validation failed | The request shape or field value is invalid. |
| Payload too large | The request body exceeds accepted limits. |
| Rate limited | The integration sent too many requests. |
| Conflict | The requested state change conflicts with current resource state. |
| Idempotency conflict | The same idempotency key was reused with different content. |
| Upstream unavailable | A dependent provider or integration is unavailable. |
| Source scan failed | API Context ingestion could not complete. |
| Agent context insufficient | The agent cannot answer from available evidence. |
Planned limit categories
Payload limits
Maximum body size and file/source upload limits.
Pagination
Page size, cursors, ordering, and filtering boundaries.
Rate limits
Per-credential, per-workspace, or per-route request limits.
Webhook delivery
Timeout, retry, and payload-size expectations.
Source ingestion
Crawl, document, chunk, and scan limits.
Live verification
Guardrails for running API checks from Woes.
Retry guidance
Future endpoint docs should state:- Which errors are safe to retry.
- Which errors require user action.
- Which operations support idempotency keys.
- How rate-limit reset information is returned.
- How webhook retries are scheduled.