Skip to Content

Usage

Path: /org/usage

Audience: members and administrators. Per-request records are in Request logs; balance changes in Balance and ledger.

What you can see

DimensionQuestion it answers
By memberWho consumes the most? Is someone approaching their limit?
By modelWhere does the spend actually go?
By dayWhat is the trend? Was there an anomalous day?

A time range can be selected. Aggregation granularity and retention are platform configuration.

Two definitions worth reading

“A day” means Asia/Shanghai (Beijing time). Not your browser’s timezone, and not the server’s. A day’s usage is the Beijing-time calendar day regardless of where you are.

Request counts settle, refunds do not un-count them. A call that reaches settlement counts once. A refund returns money but not the count — the fact that the call happened is preserved. This differs from the balance ledger, so reconcile accordingly.

Export

Usage and request logs both export to CSV. An export keeps your current filters — narrow the view first, then export what you are looking at.

Per-member visibility

To be completed: how much per-member detail an ordinary member should see (for example, whether they can see colleagues’ individual spend) is not finally decided. In the current implementation members can view per-member aggregates; treat the console as the source of truth and check this page for changes.