Operations and Revenue

Agent as a Business separates portfolio-wide monitoring from the lifecycle of one business.

Portfolio view

Portfolio shows each Agent Business with status, delivery mode, verified invocations, and recorded revenue. Use it to find businesses that need attention, then open the relevant workspace.

Business Operations

The Operations tab connects runtime evidence with the active release, channel, Publication, and Offer. Filter by period and commercial dimension to compare like with like.

Typical evidence includes:

• invocation count and success or failure outcome;
• latency and reliability signals;
• release and channel attribution;
• redacted invocation metadata;
• balanced ledger entries linked to a selected invocation.

Request bodies, response bodies, credentials, public tokens, and raw user identifiers are not operational reporting fields.

Revenue and ledger

Revenue views report recorded transactions rather than estimates. Ledger evidence separates gross revenue, creator allocation, platform allocation, channel allocation, cost, refund, and net margin where those values exist.

Amounts remain tied to immutable commercial identities so historical results can be reconciled after prices or settlement terms change.

Empty and unavailable states

• No events yet means the platform has no verified events for that scope.
• No records match means data exists outside the selected period or filters, or no events match the selected dimensions.
• Unavailable means a required data source did not load; it is not treated as zero.

Change the period or filters before concluding that a business has no activity. Do not substitute screenshots, projections, or invented trend percentages for operational evidence.

Responding to a problem

1. Identify the affected release, channel, Publication, or Offer.
2. Inspect the relevant invocation and its redacted decision evidence.
3. Confirm whether the issue is capability behavior, runtime policy, origin/auth configuration, provider reliability, or commercial gating.
4. Create a new release for changed executable behavior. Revise commercial or publication identities separately.
5. Validate the new path before sending production traffic to it.