Overview
Consumption, quotas, and feature availability depend on the workspace plan. The customer portal and API response metadata are authoritative for the current workspace; documentation examples are not contractual quotas.
Operational guidance
- Read remaining-budget and rate-limit response headers when present.
- Use idempotency keys for retried mutations.
- Bound queries and paginate large result sets.
- Configure budget alerts before enabling high-volume automation.
- Treat HTTP 402 as insufficient balance and HTTP 429 as a quota or rate condition.
Automatic recharge and some usage forecasts are plan-dependent. Confirm their availability in the portal before building an unattended workflow.
See Error codes and SDK overview.