Usage Reporting

AISIX Cloud collects usage information from the managed gateway and uses it for usage views, billing-oriented workflows, and managed budget evaluation.

In managed mode, the gateway serves AI traffic and emits usage events to Cloud. These events help teams understand consumption and let AISIX Cloud evaluate managed budgets.

Usage Flow

This is one of the main differences between self-hosted operation and Cloud-managed operation. A self-hosted gateway can serve requests locally; a managed gateway also reports usage back to AISIX Cloud.

The managed gateway sends usage-oriented data to the control plane through /dp/telemetry.

Usage events include request outcome and consumption signals such as status, latency, token usage, and cost when those values are available. Streaming chat requests can also report time to first token.

Relationship to Budgets

Usage reporting provides the consumption data that AISIX Cloud uses for managed budget workflows. Budget policy itself is covered in Budgets.

When a hard-stop budget is exceeded, the managed gateway can return 429 for affected requests. Warn-only budgets remain visible in Cloud but do not block traffic.

If a caller receives a budget-related 429, inspect the configured budget policy first. If the budget policy looks correct but Cloud usage appears incomplete, then check the telemetry path.

Usage Verification

When reported usage does not match the traffic you expected, confirm the managed gateway is healthy, the gateway can reach /dp/telemetry, and the request is live gateway traffic rather than only a Cloud UI check.

If usage still appears incomplete, check whether budget or telemetry errors are hidden behind general proxy failures.

Next Steps

You have now seen how managed gateways report usage to AISIX Cloud. Continue with Playground and Managed Gateway Requests to understand what Cloud UI checks can and cannot prove.