Pay for Virtuals Protocol ACP job budgets via x402 micropayments on Base (USDC).
What it does
This endpoint is an x402-gated payment service operated by Virtuals Protocol for their Agent Commerce Protocol (ACP) jobs. Calling `/acp-budget` with a valid x402 payment header allocates budget for an ACP job. The default cost is $0.001 per call (1000 base units of USDC on Base, where USDC uses 6 decimals), but callers can specify a custom budget amount via the optional `X-Budget` HTTP header (e.g., `$0.01`).
The endpoint accepts both GET and POST methods and returns an `application/json` response. Payment is settled on the Base network using USDC (contract `0x8335…2913`) to the payTo address `0x6a1F…0A4A`. The x402 challenge specifies a maximum timeout of 300 seconds for payment settlement. A v2 variant is also available at `/acp-budget/v2`.
Documentation is minimal — the OpenAPI spec is auto-generated by FastAPI and the response schema is an open object (`additionalProperties: true`) with no defined fields. There is no documentation on what the returned JSON contains or how the allocated budget is subsequently consumed by ACP agents. The service landing page confirms operational status.
Capabilities
Use cases
- —Funding an ACP job budget for autonomous agent tasks on Virtuals Protocol
- —Programmatic micropayments for agent-to-agent commerce workflows
- —Allocating variable budgets to ACP jobs via the X-Budget header
Fit
Best for
- —AI agents operating within the Virtuals Protocol ACP ecosystem
- —Developers integrating x402 micropayments into agent workflows
- —Automated budget allocation for agent commerce jobs
Not for
- —General-purpose payment processing unrelated to Virtuals Protocol ACP
- —Users seeking detailed API documentation or rich response schemas
Quick start
curl -X POST http://acp-x402.virtuals.io/acp-budget \
-H "X-PAYMENT: <x402-payment-token>" \
-H "X-Budget: $0.01" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live and returns a valid x402 402 challenge with clear pricing. However, documentation is very sparse: the response schema is an open object with no defined fields, there are no example requests or responses, and there is no explanation of what the returned data represents or how ACP jobs consume the allocated budget.
Warnings
- —Response schema is completely open (additionalProperties: true) with no defined fields — callers cannot predict the response structure.
- —No documentation on what the response contains or how the budget is used downstream by ACP.
- —No example request or response bodies available anywhere in the crawled material.
Citations
- —The service is described as an x402 payment service for Virtuals Protocol ACP jobs and is operational.http://acp-x402.virtuals.io
- —The /acp-budget endpoint supports dynamic pricing via the X-Budget header.http://acp-x402.virtuals.io
- —The x402 challenge specifies maxAmountRequired of 1000 base units of USDC on Base network with asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913.http://acp-x402.virtuals.io/acp-budget
- —The endpoint accepts both GET and POST methods per the OpenAPI spec.http://acp-x402.virtuals.io/docs