{"version":"2.1.284","anchor":"gateway-server-new-apioauthusage-endpoint-and-a-larger-h","canonical_anchor":"gateway-server-new-apioauthusage-endpoint-and-a-larger-h","heading":"The bundled gateway can report usage and accepts larger request headers","tier":"notice","area":"Gateway","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/gateway-server-new-apioauthusage-endpoint-and-a-larger-h","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### The bundled gateway can report usage and accepts larger request headers\n\nThe gateway bundled with Claude Code now answers usage requests when spending is tracked, and allows request headers up to 262144 bytes\n\n**Unclear.** What sets up the spend metering is not known.\n\n**What**\n\nClaude Code includes a gateway server, a go-between that passes requests on to the model. It now answers `GET \/api\/oauth\/usage` with usage figures when spend metering, tracking of how much has been used, is set up. Without it, the address returns a \"not configured\" error. The largest request header the gateway accepts is now 262144 bytes.\n\n**Why**\n\nPrograms working through a gateway can check their usage the same way they would against claude.ai.\n\n- Area: Gateway\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}