Machine Spend
Machine Spend gives you a unified read layer over paid service usage recorded through Conto’s x402 and MPP flows. Use it to answer questions like:- Which paid services is this agent using most?
- Which endpoints are driving the most spend?
- Is spend concentrated in x402, MPP, or both?
- Are there active x402 or MPP anomaly alerts for this agent?
Machine Spend is additive to existing x402 and MPP tracking. It does not replace protocol-specific
endpoints like
/api/sdk/x402/services or /api/sdk/mpp/budget; it gives you one combined view
on top of them.What It Includes
The machine-spend endpoints aggregate existingA2S transactions and protocol alerts into a shared view:
- total spend and call volume
- service-level breakdowns
- endpoint-level breakdowns
- x402 vs MPP split
- micropayment counts
- recent x402 / MPP anomaly alerts
Authentication
These endpoints use the normal agent SDK key flow:analytics:read
Get a Summary
Returns a top-level summary plus recent machine-spend alerts for the authenticated agent.Query Parameters
Example Response
List Services And Endpoints
Returns the top service domains and endpoints for the authenticated agent.Query Parameters
Example Response
When To Use Machine Spend vs Protocol-Specific Endpoints
Use Machine Spend when you want a unified service view across both protocols. Use protocol-specific endpoints when you need details unique to one rail:/api/sdk/x402/servicesfor x402 service-specific stats/api/sdk/x402/budgetfor x402 burn rate and policy limit views/api/sdk/mpp/servicesfor MPP service-specific stats/api/sdk/mpp/budgetfor MPP session and budget views
Dashboard View
Conto also exposes this data in the dashboard, where you can:- filter by protocol and time window
- compare top services and endpoints
- inspect top agents and organizations
- review recent x402 / MPP anomaly alerts
Next Steps
x402 Payments
Record and control pay-per-call API spend
MPP Payments
Track session-based micropayment usage