Platform controls
Platform controls are the cross-cutting safeguards for operating Agents from a backend application. Use them to keep Tenant data isolated, attribute activity, constrain usage, protect credentials, and design for failures.
Choose a control
| Control | Question answered | Scope | Canonical detail |
|---|---|---|---|
| Tenancy and end-user attribution | Which Tenant owns the request, and which optional opaque end-user identifier should label its activity? | Tenant isolation comes from the credential; Attribution is a reporting dimension, not authorization or an ACL. | Tenancy and end-user attribution |
| Usage and quotas | What did Turns consume, and when should a Tenant-set safety ceiling stop new work? | Usage is metering; quota is a soft Tenant control. Neither defines billing entitlements or plan limits. | Usage and quotas |
| Security and credentials | Which credential establishes trust, and where may credentials be used? | Backend API keys, Provider credentials, MCP credentials, and private service authentication. | Security and credentials |
| Limits and reliability | What is bounded, retryable, cancellable, or durably recoverable? | Product limits, pagination, failures, idempotency, cancellation, and recovery. | Limits and reliability |
Billing separately defines plan entitlements, infrastructure meters, and charges. Service limits are coded product bounds; Tenant-set quotas are optional safeguards over recorded Turn tokens and requests.
Control flow
- A backend sends a Tenant-scoped API key, which establishes the trusted Tenant context for the request.
- The backend may add opaque end-user Attribution. This labels supported resources and activity but cannot change the Tenant selected by the credential.
- The platform resolves the Agent request, applies quota and execution gates, and runs the Turn. Each Turn settles usage, including failed and cancelled outcomes.
- The caller receives the execution result or a typed quota, validation, authentication, resource, provider, or reliability outcome. Durable Tasks and Sandbox admission add recovery boundaries without making external side effects exactly once.
The public /v1 API is backend-only. End-user clients authenticate to the tenant's application, which enforces its own authorization before calling Blazing Agents.
Explore platform controls
Tenancy and end-user attribution
Separate credential-derived Tenant isolation from optional end-user reporting labels.
Usage and quotas
Measure Turn activity and configure soft monthly safety ceilings.
Security and credentials
Keep API, Provider, MCP, and service credentials within their trust boundaries.
Limits and reliability
Handle bounded operations, retries, cancellation, and durable recovery.