Inspect usage and invoice provenance
Trace consumption from an event through a meter to its invoice line.
Choose the correct read surface
| Question | Public REST request |
|---|---|
| Which meters exist? | GET /v2/meters |
| What happened in each interval? | GET /v2/meters/{id}/quantities |
| What is this customer's consumption/allowance? | GET /v2/customer-meters or GET /v2/customer-meters/{customer_id}/{meter_id} |
| Which events were received? | GET /v2/usage-events |
| What is one event's record? | GET /v2/usage-events/{id} |
| Which events produced this invoice line? | GET /v2/invoice-line-items/{id}/usage-events |
| What is the usage balance? | GET /v2/usage/balance |
Use the API reference for each response shape. Quantities are consumption, not a monetary invoice total. A balance, a customer-meter view, and an invoice line answer different questions.
Quantities over time
curl --get "https://staging-api.revkeen.com/v2/meters/$REVKEEN_METER_ID/quantities" \
-H "x-api-key: $REVKEEN_API_KEY" \
--data-urlencode "start_timestamp=2026-08-01T00:00:00Z" \
--data-urlencode "end_timestamp=2026-08-08T00:00:00Z" \
--data-urlencode "interval=day" \
--data-urlencode "customer_id=$REVKEEN_CUSTOMER_ID"Set the environment variables to staging identifiers you own. The interval is hour, day, week, month, or year. Weeks start Monday. Only UTC is supported, and a request cannot produce more than 1,000 buckets. Narrow the time window or choose a larger interval rather than retrying the same oversized query.
Trace a disputed usage charge
- Retrieve the invoice and identify its usage line ID.
- Request that line's usage events with a bounded
limit; followstarting_afterfor subsequent pages. - Use
include_excludedwhen investigating entries excluded from billing. - Compare the original event identity/time, meter matches, quantity, price, allowance, and resulting billing entry.
- Explain the recorded calculation to the customer. Use the appropriate credit-note workflow for a correction; do not edit evidence or invent replacement usage.
Unknown and other-merchant event IDs return no accessible record. Record request IDs and redacted identifiers for support, not full customer payloads or credentials.
The MCP usage recipes offer approved read tools for this investigation. A REST operation does not automatically imply an MCP tool or an installed SDK method.