Client API Beta Access Policy
Beta posture
- Stage: internal beta
- Audience: invited accounts
- Public onboarding: not yet available
Availability posture
- No public SLA commitment during beta
- Backward compatibility is a goal, but undocumented fields may change
- Breaking changes include a changelog entry and migration guidance
Billing posture
- Metering and billing infrastructure is active
- Billable unit: successful API call (
2xx/3xx) - Failed calls (
4xx/5xx) are non-billable - Idempotent replays are non-billable duplicates
Guardrails
- Global traffic controls (rate limiting, emergency disable)
- Per-key revoke
- Access control enforcement
- Spend caps and anomaly controls
What moves the Client API to public beta
- Stable authentication and key lifecycle
- Billing/metering reconciliation within tolerance
- MCP tool invocation parity for the published catalog
- Onboarding and abuse-prevention controls verified in staging and production