Context
The AI Gateway billing sample uses llm-token-limit (product-level rate limiting) and llm-emit-token-metric (token metering) APIM policies. These policies are currently rolling out support for non-OpenAI backends (including Anthropic Claude) on v2 SKUs (Basicv2, StandardV2).
By June 2026, we should check whether these capabilities are also available on v1 SKUs (Developer, Basic, Standard, Premium).
Action Items
Related Files
infra/policies/api-anthropic.xml — custom emit-metric workaround
infra/policies/product-standard.xml / product-premium.xml — llm-token-limit
README.md — Known Limitations section
References
Context
The AI Gateway billing sample uses
llm-token-limit(product-level rate limiting) andllm-emit-token-metric(token metering) APIM policies. These policies are currently rolling out support for non-OpenAI backends (including Anthropic Claude) on v2 SKUs (Basicv2, StandardV2).By June 2026, we should check whether these capabilities are also available on v1 SKUs (Developer, Basic, Standard, Premium).
Action Items
llm-token-limitcorrectly counts consumed tokens from Anthropic responses (input_tokens/output_tokensformat) on v1 SKUsllm-emit-token-metriccan parse Anthropic response format natively — if so, the manualemit-metricworkaround inapi-anthropic.xmlcan be replacedllm-emit-token-metricinstead of customemit-metriccallstext/event-stream) to see if the streaming metering gap is also resolvedRelated Files
infra/policies/api-anthropic.xml— custom emit-metric workaroundinfra/policies/product-standard.xml/product-premium.xml— llm-token-limitREADME.md— Known Limitations sectionReferences