Cloudflare AI Gateway User Insights: attribute spend before chasing anomalies

Quick answer

Cloudflare AI Gateway User Insights can now show which identities are driving AI cost and flag sessions that deviate from a user's normal pattern. Do not treat the new dashboard as a complete cost-control system by itself.

Roll it out in this order:

1. attach a stable, non-sensitive identity to gateway traffic;


2. measure identity coverage before trusting per-user charts;


3. use anomaly flags as an investigation queue, not proof of abuse;


4. enforce separate global and per-user spend limits;


5. test 429 and fallback behavior with a tiny sandbox budget; and


6. reconcile Cloudflare's estimate with the model provider's bill.

That sequence separates attribution, detection, enforcement, and billing truth—four jobs that are easy to blur together.

Who this is for

This guide is for teams and indie developers routing product features, coding agents, support agents, or internal AI tools through Cloudflare AI Gateway. It is most useful when several users share one gateway and a retry loop, compromised credential, or unusually expensive workflow can create a surprise bill.

If you only need an OpenAI organization-level cap and 429 recovery, use the