{"version":"2.1.319","anchor":"gateway-protocol-doc-gains-billing-group-request-tags","canonical_anchor":"gateway-protocol-doc-gains-billing-group-request-tags","heading":"The gateway can tag requests with a billing group","tier":"notice","area":"LLM Gateway","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/gateway-protocol-doc-gains-billing-group-request-tags","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### The gateway can tag requests with a billing group\n\nGateway operators can now set a billing group tag so requests are logged by group, with the tags stripped before sending on\n\n**What**\n\nThe gateway is a server that passes Claude Code's requests on to the model provider. It gains an optional billing group feature:\n\n- A request to `POST \/v1\/messages` can carry `tags` in its body.\n\n- The admin setting `admin.billing_group_tag` names which tag marks the group.\n\n- The gateway records the group in its audit log and emits a `spend.metered` event when the tag is configured.\n\n- It removes `tags` and the `request-tags-2026-08-21` beta value before sending the request on.\n\n- For Bedrock, Bedrock Mantle and Vertex, these are always removed.\n\n**Why**\n\nIf you run a gateway, you can attribute spending to groups of requests without the tags reaching the upstream provider.\n\n- Area: LLM Gateway\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 4\/5\n- Scope: org\n- Heads-up: no"}