x402 List

x402 Protocol Service Directory

ACP - Virtuals Protocol

AI PAYMENT-READY imported

payment-ready until 2026-09-11

imported from x402scan, not submitted by the operator · own this service? claim it · or ask to be removed

Agent Commerce Protocol (ACP) x402 endpoint by Virtuals Protocol on Base. GET /acp-budget serves ACP budget data behind an HTTP 402 paywall.

Pay from $0.001 per request in USDC on Base, settled onchain via the x402 protocol, no signup, no API key needed.

measured since 2026-01-01 (start of our harvest window) · $4.0k all-time · last settled 2026-07-21

BASE URL https://acp-x402.virtuals.io ENDPOINTS 1 NETWORK Base ASSET USDC MEMBER SINCE 2026-07-20 MONITORED SINCE 2026-07-20

VERDICT

ranking generation 3

solid 83/100 #53 of 104 in AI by measured score

What the score read on this service: status online, 99.8% uptime 30d, 2574ms response p95, x402 compliance 13 of 14, $0.001 price against the category, on-chain traction measured. Each of those is measured, and each is published in full below.

The score comes from our own monitoring, never from reviews, operator claims, or a language model: reliability, x402 compliance, price against the category, a deterministic risk flag, and a small on-chain traction term, weighted by ranking generation 3. It is not placement anyone can buy: the paid verify tier is reported beside it and is not one of its inputs. Every component below stays published and read-only.

It is a score inside AI, and only there: price and speed are scored against the whole category field, every listing in it that carries no danger flag, the scored service included, which here means 104 listings, this one among them. That set is wider than the 104 the position above is counted against, because a listing we have measured too little of to rank still sits in the field the price and the speed are normalized over. The same service in a different field would read differently. The same engine answers GET /api/v1/best, and asked for a different pool (the whole directory, or another filter) it returns a different number for this service under this same ranking generation. Neither is more correct: they answer different questions, and the methodology states which is which.

Bands on the 0 to 100 measured score: strong at 93 and above, solid from 75, mixed from 55, weak below 55. Price and speed are scored against the whole category field, every listing in it that carries no danger flag, the scored service included, so the score places a service in its own field.

ALTERNATIVES IN AI

Other AI services in this directory, ordered by the same measured score. The figures are ours: 30-day uptime from our own probes, 30-day settlement volume read on-chain (a conservative undercount, and null where we cannot measure it, never a zero).

Ranked alternative x402 services in the same category, with band, measured score, 30-day uptime and 30-day on-chain settlement volume
SERVICE BAND SCORE UPTIME 30D VOL 30D
Genesis strong 98 100% ---
x402engine strong 98 100% ---
kino402 strong 96 100% ---
Arch Tools strong 96 100% ---
agente-jefe strong 96 100% ---
5 of 103 other ranked services in AI · see the whole category

ASSESSMENT

updated 2h ago

The parts the verdict above is computed from, each with its proof. Click any chip. Measured values stay read-only; unknown is honest, and an unknown is never counted as a zero.

reliability 99.8%
uptime 24h
100%
uptime 7d
100%
uptime 30d
99.8%
uptime 90d
99.9%
response p95
2574ms
avg response
1088ms
total checks
2,740

Measured on the unpaid 402 handshake, not the paid call. A service can 402 correctly and still fail after payment.

compliance A (13/14): declares the current x402 version (2)

13 of 14 x402 conformance checks pass; failing: declares the current x402 version (2). Full checklist below.

jump to compliance checklist

price $0.001 (p9 in AI)
price (min)
$0.001
category percentile (min)
p9 in AI
endpoints / prices
1 / 1
model
flat
stability
100%
risk clean

No deterministic risk flag. Risk fires only on an exact blocklist match, or a reserved-brand name with a mismatched verified payTo. Never from low uptime, a high price, or a model guess.

domain age
-
registrar
-
hosting
custom
domain created
---

Identity facts, not a risk score.

traction $0.00 30d · 0 buyers
volume 30d
$0.00
buyers 30d
0
settlements 30d
0
measured since
2026-01-01 (start of our harvest window)
last settlement
2026-07-21
top buyer share
-
trend 7d vs 30d
-
networks
eip155:8453
volume all-time
$4.0k
settlements all-time
1,165
median settlement 30d
-
max settlement 30d
-
settled via
-

Conservative undercount: only USDC settlements via facilitators we measure are counted. A measured floor, not an estimate.

Top buyer share is a concentration signal, not part of the ranking score.

WHAT IT DOES

ai-derived

The service provides budget management for ACP jobs with a fixed price of $0.001 per request.

category
budget-api
budgetingpricingjob-management

AI-generated summary. The measured data is never altered by it.

ENDPOINTS

Service endpoints with HTTP method, path, description, pricing, and network
METHOD PATH DESCRIPTION PRICE NETWORK ASSET 402 CHANNEL
GET /acp-budget acp job budget ($0.001) $0.001 Base USDC body (v1 style)
1 endpoints

REQUEST / RESPONSE EXAMPLE

An unpaid request to GET /acp-budget returns HTTP 402 with the payment terms. Settle onchain via your facilitator, then retry with the X-Payment header.

// request
curl -i 'https://acp-x402.virtuals.io/acp-budget'
// 402 response (captured by monitor) · 1 payload · click to expand
[
  {
    "error": "No X-PAYMENT header provided",
    "accepts": [
      {
        "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
        "extra": {
          "name": "USD Coin",
          "version": "2"
        },
        "payTo": "0x6a1FE26D54ab0d3E1e3168f2e0c0cDa5cC0A0A4A",
        "scheme": "exact",
        "network": "base",
        "mimeType": "application/json",
        "resource": "http://acp-x402.virtuals.io/acp-budget",
        "description": "acp job budget ($0.001)",
        "outputSchema": {
          "input": {
            "type": "http",
            "method": "GET",
            "discoverable": true,
            "headerFields": {
              "X-Budget": {
                "type": "string",
                "example": "$0.01",
                "required": false,
                "description": "Optional budget amount in USD (e.g., $0.01). If not provided, defaults to $0.001"
              }
            }
          },
          "output": null
        },
        "maxAmountRequired": "1000",
        "maxTimeoutSeconds": 300
      }
    ],
    "x402Version": 1
  }
]

OVER TIME

All charts use the 30d selector; each series spans only the dates it has data for. Every series is also served as JSON at /api/v1/services/acp-virtuals-protocol/price, /scores, /volume and /buyers. On-chain volume and distinct buyers are measured over the service's settlement address and are a conservative undercount (only settlements that reach a measured facilitator are counted). The on-chain series roll up hourly, so the latest day can be up to about an hour behind; distinct buyers are counted per payout address, so a service that settles to more than one address is an upper bound.

UPTIME
08-06 · uptime 100.0% · 1350ms avg08-07 · uptime 100.0% · 1076ms avg08-08 · uptime 100.0% · 1098ms avg08-09 · uptime 100.0% · 1830ms avg08-10 · uptime 100.0% · 1550ms avg08-11 · uptime 100.0% · 984ms avg08-12 · uptime 100.0% · 925ms avg08-13 · uptime 98.9% · 684ms avg08-14 · uptime 100.0% · 489ms avg08-15 · uptime 100.0% · 554ms avg08-16 · uptime 100.0% · 538ms avg08-17 · uptime 100.0% · 559ms avg08-18 · uptime 100.0% · 528ms avg08-19 · uptime 100.0% · 695ms avg08-20 · uptime 100.0% · 913ms avg08-21 · uptime 100.0% · 790ms avg08-22 · uptime 100.0% · 854ms avg08-23 · uptime 100.0% · 744ms avg08-24 · uptime 96.6% · 857ms avg08-25 · uptime 100.0% · 1049ms avg08-26 · uptime 100.0% · 1060ms avg08-27 · uptime 100.0% · 1420ms avg08-28 · uptime 100.0% · 1177ms avg08-29 · uptime 100.0% · 1437ms avg08-30 · uptime 100.0% · 1339ms avg08-31 · uptime 100.0% · 2004ms avg09-01 · uptime 100.0% · 1653ms avg09-02 · uptime 100.0% · 1387ms avg09-03 · uptime 100.0% · 1380ms avg09-04 · uptime 100.0% · 1481ms avg08-0609-04
30d UPTIME 99.8%
RESPONSE TIME
08-06 · 1350ms avg08-06 · 1350ms avg08-07 · 1076ms avg08-07 · 1076ms avg08-08 · 1098ms avg08-08 · 1098ms avg08-09 · 1830ms avg08-09 · 1830ms avg08-10 · 1550ms avg08-10 · 1550ms avg08-11 · 984ms avg08-11 · 984ms avg08-12 · 925ms avg08-12 · 925ms avg08-13 · 684ms avg08-13 · 684ms avg08-14 · 489ms avg08-14 · 489ms avg08-15 · 554ms avg08-15 · 554ms avg08-16 · 538ms avg08-16 · 538ms avg08-17 · 559ms avg08-17 · 559ms avg08-18 · 528ms avg08-18 · 528ms avg08-19 · 695ms avg08-19 · 695ms avg08-20 · 913ms avg08-20 · 913ms avg08-21 · 790ms avg08-21 · 790ms avg08-22 · 854ms avg08-22 · 854ms avg08-23 · 744ms avg08-23 · 744ms avg08-24 · 857ms avg08-24 · 857ms avg08-25 · 1049ms avg08-25 · 1049ms avg08-26 · 1060ms avg08-26 · 1060ms avg08-27 · 1420ms avg08-27 · 1420ms avg08-28 · 1177ms avg08-28 · 1177ms avg08-29 · 1437ms avg08-29 · 1437ms avg08-30 · 1339ms avg08-30 · 1339ms avg08-31 · 2004ms avg08-31 · 2004ms avg09-01 · 1653ms avg09-01 · 1653ms avg09-02 · 1387ms avg09-02 · 1387ms avg09-03 · 1380ms avg09-03 · 1380ms avg09-04 · 1481ms avg09-04 · 1481ms avg08-0609-04
AVG RESP 1091ms
PRICE (captured 402, USD)
08-05 · $0.00109-04 · $0.001$0.00108-0509-04
SUB-SCORES (uptime + x402 compliance)
08-05 uptime: 99.9% compliance: 93% checks08-06 uptime: 99.9% compliance: 93% checks08-07 uptime: 99.9% compliance: 93% checks08-08 uptime: 99.9% compliance: 93% checks08-09 uptime: 99.9% compliance: 93% checks08-10 uptime: 99.9% compliance: 93% checks08-11 uptime: 99.9% compliance: 93% checks08-12 uptime: 100.0% compliance: 93% checks08-13 uptime: 99.9% compliance: 93% checks08-14 uptime: 99.9% compliance: 93% checks08-15 uptime: 99.9% compliance: 93% checks08-16 uptime: 99.9% compliance: 93% checks08-17 uptime: 99.9% compliance: 93% checks08-18 uptime: 99.9% compliance: 93% checks08-19 uptime: 99.9% compliance: 93% checks08-20 uptime: 100.0% compliance: 93% checks08-21 uptime: 100.0% compliance: 93% checks08-22 uptime: 100.0% compliance: 93% checks08-23 uptime: 100.0% compliance: 93% checks08-24 uptime: 99.9% compliance: 93% checks08-25 uptime: 99.9% compliance: 93% checks08-26 uptime: 99.9% compliance: 93% checks08-27 uptime: 99.9% compliance: 93% checks08-28 uptime: 99.9% compliance: 93% checks08-29 uptime: 99.9% compliance: 93% checks08-30 uptime: 99.9% compliance: 93% checks08-31 uptime: 99.9% compliance: 93% checks09-01 uptime: 99.9% compliance: 93% checks09-02 uptime: 99.9% compliance: 93% checks09-03 uptime: 99.9% compliance: 93% checks09-04 uptime: 99.8% compliance: 93% checksuptimecompliance08-0509-04

checklist grew 11->14 on 2026-07-28; a step here is a metric change, not a regression

PILLARS OVER TIME (measured)

Measured site and economics pillars from the assessment history, so the latest value shown elsewhere on this page reads as a point on a trend rather than a permanent state.

VOLUME (on-chain settlement, USD)
no on-chain volume yet
DISTINCT BUYERS
no distinct buyers yet

COMPLIANCE

13/14 checks pass · grade A · failing: declares the current x402 version (2)

last 402 captured 2026-07-20 · last up 2026-09-04

  • 402 payload captured
  • accepts[] array present
  • payTo address recoverable
  • payTo at accepts[0].payTo (conformant shape)
  • payTo is a valid on-chain address
  • atomic price declared
  • atomic price in a sane range
  • asset (token) address declared
  • network resolves to CAIP-2
  • payment scheme declared
  • served over HTTPS
  • declares the current x402 version (2)
  • EIP-712 domain parameters present on every EVM entry
  • x402 v2 envelope delivered in the payment-required header

SITE PILLARS

  • homepage reachable
  • openapi doc
  • pricing page
  • llms.txt
  • robots.txt
  • terms page
recent checks (18) live · click to expand
TIME STATUS RESP CAUSE
● OK 707ms
● OK 1211ms
● OK 1523ms
● SLOW 1932ms
● SLOW 2048ms
● OK 499ms
● SLOW 7934ms
● OK 384ms
● OK 736ms
● SLOW 1681ms
● OK 1102ms
● SLOW 2535ms
● SLOW 2225ms
● OK 1389ms
● OK 1360ms
● OK 1379ms
● OK 1198ms
● OK 993ms

EMBED THIS BADGE

Show that ACP - Virtuals Protocol is monitored on x402-list. Paste this on your site or README, it links back to this live listing.

ACP - Virtuals Protocol listed on x402-list
status
ACP - Virtuals Protocol uptime on x402-list
live uptime
// HTML
<a href="https://x402-list.com/services/acp-virtuals-protocol?utm_source=badge&utm_medium=referral&utm_campaign=embed">
  <img src="https://x402-list.com/badge/acp-virtuals-protocol.svg" alt="ACP - Virtuals Protocol listed on x402-list" height="28">
</a>
// Markdown
[![ACP - Virtuals Protocol on x402-list](https://x402-list.com/badge/acp-virtuals-protocol.svg)](https://x402-list.com/services/acp-virtuals-protocol?utm_source=badge&utm_medium=referral&utm_campaign=embed)
// HTML · live uptime variant
<a href="https://x402-list.com/services/acp-virtuals-protocol?utm_source=badge&utm_medium=referral&utm_campaign=embed">
  <img src="https://x402-list.com/badge/acp-virtuals-protocol.svg?data=uptime" alt="ACP - Virtuals Protocol uptime on x402-list" height="28">
</a>

RUN THIS SERVICE?

Keep this listing accurate: propose changes to the name, description, website, category or add new endpoints to monitor. Ownership is verified with a domain proof and every change is reviewed manually; measured data stays read-only.

[ update this listing ]

Earn the verified tier: x402list pays a real call to this endpoint and, if it delivers, the service is delivery-verified. The fee covers the cost of the probe, not the badge; there is no refund if the call does not deliver. Agent and API only, no in-browser signing. See /api.

[ verify this service ($0.25) ]

To request delisting, email info@x402-list.com or update your listing at /services/acp-virtuals-protocol/update.