File structure

Five sections are required. Every other section is optional, and an omitted section takes its defaults. Unknown keys fail boot, so a typo surfaces as a named error rather than a silently ignored setting.

Required sections:

• listen: bind address, public URL, TLS termination
• oidc: your identity provider (IdP), including issuer, client, claim mapping, and who may sign in
• session: the bearer tokens the gateway mints, with secret and lifetime
• store: PostgreSQL, for device grants and rate-limit counters
• upstreams: where inference goes, whether Anthropic, Amazon Bedrock, Claude Platform on AWS, Google Cloud's Agent Platform, or Microsoft Foundry

Optional sections:

• admin: Admin API auth and retention for spend limits
• enforcement: spend-limit fail-open or fail-closed behavior
• pricing: contracted rates and a discount multiplier for the spend meter and for the cost figures developers see
• models and auto_include_builtin_models: admin-curated model list and per-upstream IDs
• managed: managed settings policies by IdP group
• telemetry: OTLP forwarding to your observability stack
• access_control, limits, timeouts, rate_limits: IP allow/deny, request size caps, upstream time-to-first-byte, and per-IP sign-in limits