Errors and headers
Planned management contract. Use current Gateway guides for deployed behavior.
Planned capability
This page describes a proposed management contract, not a setup procedure. Current request behavior is documented in the Gateway API reference.
Proposed policy metadata
A future refusal schema would identify the applicable control and request context without exposing another scope's private data. Budget, model-access and throughput failures would need documented codes, HTTP status, content type and retry behavior.
Proposed response headers
Remaining-limit and reset headers would require defined accounting, scope and freshness. Clients should not rely on them until their serving implementation is documented.
Current errors
Use the Gateway API reference for capture-identity, model, provider and endpoint errors. Supported path-specific policy refusals and failure behavior are described in Policy and enforcement boundaries.