Usage and Reconciliation
How calls are counted and how to match them against your own logs.
Every call made through Voidnet appears in your dashboard so you can count it yourself and compare.
How counting works
A request is counted when a buyer successfully calls a billable tool on your server. The Console calls this a request. List and discover calls are not counted. If the tool returns an error, it is still shown in the log so you can see what happened, but it is not billed.
Each counted request records a request ID, the time it was received, the tool that was called, how long your server took to respond, and whether the buyer was on a free or paid tier.
Where to see it
Open Console → Published Apps → your app → Usage Logs.
The table lists every counted request for that app, most recent first. You can copy the request ID and match it to the ID in your own server logs. The time column uses the gateway's clock — compare it to your server's clock with a small window for clock drift.
Use the pagination controls to page through older calls and Export CSV to download the current page for offline comparison.
Reconciling with your own logs
Your server logs the same request ID on every call forwarded from Voidnet. To reconcile:
- Log the request ID and time on your server for each tool call.
- Open the Usage Logs tab for that app.
- Filter or page to the same time window.
- Compare counts. Every counted call appears in the log. There are no hidden states — if a call is counted, it is listed. If it is not listed, it was not counted.
If counts differ, check for calls that returned an error or were filtered as non-billable in the docs. If you still see a mismatch, contact support with the request IDs and times.
API access
The same data is available via a publisher API for programmatic reconciliation:
GET /api/console/publishers/apps/{appId}/metering?limit=50&offset=0&from=2026-08-01T00:00:00Z&to=2026-08-31T23:59:59ZThe API requires a console session. It returns records with requestId, timestamp, appName, toolName, operationType, tier, requests, durationMs, error, and buyerId, plus pagination with total.
Notes
Counts are final once they appear in the log. The v1-beta endpoint family is versioned, and any future change to counting will be announced in the changelog with a deprecation window.