Meta Business Agent Usage Insights can now return recorded billing data for both WhatsApp and Instagram. The endpoint reports billable messages, billable tokens and charges for one Business Agent account over a selected billing period.
That makes cross-channel reconciliation possible, but the response is not a forecast. Meta says it does not estimate usage that billing has not recorded.
Start with the billable account and its timezone
The request uses the Meta Business Agent billable account ID as entity_id. Meta says to find it in Billing Hub under Accounts and Meta Business Agent accounts. Do not substitute a WhatsApp phone number ID, Instagram business account ID or app ID.
Record the billable account timezone before choosing dates. The endpoint evaluates boundaries in that timezone. start is inclusive and end is exclusive, so a daily request ending at midnight on 4 June returns buckets beginning on 1, 2 and 3 June.
The caller also needs the business_management permission. Use Meta's documented system-user or Solution Provider authorization path for the account.
Pull one total before adding dimensions
Begin with one account-level request for the chosen period. Omit dimensions, channels, sender_ids and metric_types so the response includes all recorded metrics and both supported channels.

- 1AccountConfirm the billable account ID.
- 2BoundaryUse the account timezone and exclusive end.
- 3TotalPull all recorded metrics without dimensions.
- 4ChannelSplit WhatsApp and Instagram.
- 5SenderLocate each sending entity.
- 6ExceptionKeep missing or unmatched evidence open.
Choose HOUR, DAY or MONTH granularity according to the investigation. Monthly requests must follow Meta's whole-month boundary rules.
Keep the exact API version, parameters, retrieval time and response hash with the result.
Reconcile account, channel and sender totals
Run the same date range again with channel in dimensions. The channel rows should add up to the undivided account total for every returned metric. Then add sender_id to locate usage inside each channel.
| Reconciliation level | Request shape | Question it answers |
|---|---|---|
| Account | No dimensions | What recorded usage belongs to this billable account and period? |
| Channel | dimensions=channel | How much belongs to WhatsApp and Instagram? |
| Sender | dimensions=channel,sender_id | Which sending entity created each channel total? |
| Exception | Same range, stored receipt | Which difference needs billing or integration investigation? |
Use the same start, end, granularity and metric set throughout. A changed boundary can resemble a channel mismatch.
The AI agent pricing guide explains commercial charging models. This endpoint serves a narrower job: retrieving Meta's recorded usage evidence for one Business Agent account.
Treat empty and missing data carefully
Meta defines an empty usage array as no matching billing records for the requested range and filters. That result does not prove that the agent was inactive, that no customer message was handled or that future billing will remain zero.
Check the account ID, timezone, range, filters and permission first. Preserve the empty response in the exception log. If operations evidence shows activity while billing returns nothing, escalate the discrepancy instead of filling it with an estimate.
Fields can also be absent by design. If metric_types excludes cost, the response omits cost from each row rather than returning null. A reconciliation script should distinguish an omitted metric from a recorded zero.
Compare charges in the account currency
The cost value uses the Business Agent account's currency. Compare it with Billing Hub or the corresponding invoice only after confirming account, currency, timezone and period.
Record four outcomes for each run: matched, timing difference, missing billing record or unexplained difference. Keep the owner and next check beside every exception. The AI agent outcome ledger can then connect verified cost to audited customer outcomes without treating messages or tokens as business value.
Keep the operating boundary clear
Usage Insights is a Meta endpoint, not proof of a native connection in another platform. If a team exports this data into a reporting system or a shared inbox workflow, document the custom API or webhook setup and the owner who maintains it.
The endpoint allows 1,000 requests per hour for each app and billable-account pair. Stop repeated retries on 429 and use controlled backoff.
Before enabling a new agent, use the Meta Business Agent launch test and confirm the eligibility and ownership map. Billing evidence becomes useful after account ownership, release authority and customer handling are already clear.
Frequently Asked Questions
Does omitting the channel filter include Instagram
Yes. Meta's current reference says omitting channels includes WhatsApp and Instagram. Add the channel dimension when you need separate totals.
Does an empty usage array mean zero final cost
It means no matching billing records were returned for that request. Meta explicitly says unrecorded usage and estimated costs are not returned.
Which identifier belongs in entity_id
Use the Meta Business Agent billable account ID shown in Billing Hub, not a phone number, sender or app identifier.
Can the endpoint calculate AI agent ROI
No. It supplies recorded usage and charges. ROI requires verified customer outcomes, a comparison and all other operating costs.
Sources
Want help applying this guide?Ask the DripTell team
From reading to action
Want help applying this to your business?
Share your details. We will read the article you are on and start with a useful answer for your team.
DripTell Editorial
Practical guidance reviewed by the DripTell product and customer workflow team.
See how DripTell checks product claims, uses primary sources and handles corrections.
Editorial and source policy



