Availability and Deployment Gates
Several features are controlled by deployment gates. A gate that is off means the routes can appear in the OpenAPI reference while the deployment refuses new work for that feature. Documentation and automated tests describe the product; they do not show that a particular deployment, its workers, its network and its model providers behave as described. Your installation operator decides when a gate is enabled.
Gates
| Feature | Deployment setting | Default | Documentation |
|---|---|---|---|
| Service credentials | API_SERVICE_CREDENTIALS_ENABLED, plus Organization enablement | Off | Service credentials |
| Application requests | API_APPLICATION_REQUESTS_ENABLED | Off | Application requests |
| Typed results | API_STRUCTURED_RESULTS_ENABLED (also requires application requests) | Off | Structured data |
| REST file upload and replacement | API_REST_FILES_ENABLED | Off | REST files |
| Named schedules and setup writes | API_CONFIGURATION_ENABLED | Off | Configuration and schedules |
| Usage and audit metadata reads | API_OPERATIONAL_READS_ENABLED | Off | Usage and audit |
| Automatic agent events | API_AUTOMATIC_AGENT_EVENTS_ENABLED | Off | Webhooks |
Extended retry coverage for Idempotency-Key | API_EXTENDED_RETRIES_ENABLED | Off | Idempotency |
| Shared request quotas | API_ADMISSION_ENABLED | Optional | Limits and compatibility |
| External security response | CUSTOMER_SECURITY_HALT_ENABLED and Organization scope | Gated | External security halt |
A feature page states which reads and retained retries, if any, stay available when its gate is switched off. Where a page does not say, assume none do.
Before you enable a gate
- Read the feature page and apply the migrations and process upgrades it names. Drain older writers and readers where the page says to.
- Enable the gate in a non-production environment that uses the same workers, storage, network policy and model providers as production.
- Exercise the feature end to end, including the failure and rollback paths the page describes. A passing unit test or a reachable route does not show that your workers and providers cooperate.
- Enable it for production deliberately, one Organization at a time where the feature supports that.
To roll back, disable the gate. Retained readers, replay and recovery keep running as each feature page describes.
What a gate does not promise
- Enabling a gate does not establish throughput, availability or latency. Measure those in your environment.
- Containment features, including External security halt, report what they could confirm. A closed connection or a recorded time never proves that the other side stopped.
- Provider-specific behavior, such as a model provider's streaming or a SIEM's indexing, depends on that provider's configuration.