{"version":"2.1.284","anchor":"gateway-docs-serve-get-apioauthusage-so-usage-and-the-s","canonical_anchor":"gateway-docs-serve-get-apioauthusage-so-usage-and-the-s","heading":"Gateway guide explains how to show dollar amounts in \/usage and the status line","tier":"notice","area":"Gateway","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/gateway-docs-serve-get-apioauthusage-so-usage-and-the-s","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### Gateway guide explains how to show dollar amounts in \/usage and the status line\n\nThe bundled gateway guide now tells operators how to serve spending data so `\/usage` and the status line can show dollars\n\n**Unclear.** The client-side request to this endpoint was not confirmed in this build.\n\n**What**\n\nA gateway is a server some organisations put between Claude Code and the model provider. The implementation guide for gateway operators that ships with Claude Code now describes an extra endpoint, `GET \/api\/oauth\/usage`, that returns the signed-in user's own spending cap.\n\nThe guide says newer Claude Code clients signed in to a gateway call this endpoint and add dollar amounts to `\/usage` and the status line. If the gateway answers with a 404 or another error, they show the percentage alone. It sets out the expected response shape: amounts in cents, whole percentages, and a reset time that must match the overage-reset header, since dollars are only shown alongside the percentage when the two agree to the second.\n\n**Why**\n\nPeople working behind a company gateway can see how much they have spent, not only a percentage, once their gateway serves this endpoint.\n\n- Area: Gateway\n- Names: `\/usage`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}