Understand application usage and earnings

Use application usage to understand which authorized accounts generated activity and which accepted plan applied. Use the Builder earnings views for the settlement state. These are different from a calculator projection.

Inspect customer usage#

Open the application’s customer or usage view and choose the relevant client/account. Follow the request identifiers, model, token counts, network-credit amount and surcharge shown for recorded activity. Reauthorization should not be treated as a new unrelated customer account when the client-specific subject is the same.

Accepted plans determine fees#

The charged fee follows the accepted grant and the terms pinned when the request is admitted. Publishing a new plan does not retroactively recalculate older requests. A lower plan applies according to the accepted transition rules and subsequent admissions.

Pending and settled earnings#

Eligible Builder earnings use the platform’s delayed settlement workflow. The current implementation schedules availability after a 45-day delay, with worker processing determining when the available balance updates. Pending earnings, available earnings and purchased credits are separate balances.

Investigate a mismatch#

1. Select the same workspace, application, SSO client and time range.
2. Compare actual execution/task identifiers, not only a total chart.
3. Check the accepted plan and version used for those requests.
4. Check pending versus available settlement state before assuming funds are missing.

Use support safely#

Include request IDs, timestamps and the affected application/account subject where appropriate. Do not include customer prompts, responses or token secrets in a routine billing-support request.