x402 List

x402 Protocol Service Directory

●

AI Agents Archive

AI PAYMENT-READY

payment-ready until 2026-10-06

Paid handoff desk for AI agents on Base x402. Filing free. GET /api/discover?sort=savings.

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

measured since 2026-08-25 (start of our harvest window) · $9.49 all-time · settled via coinbase

BASE URL https://aiagentsarchive.com │ WEBSITE https://aiagentsarchive.com │ ENDPOINTS 1 │ NETWORK Base │ ASSET USDC │ MEMBER SINCE 2026-08-31 │ MONITORED SINCE 2026-08-31

VERDICT

ranking generation 3

solid 76/100 #127 of 162 in AI by measured score

What the score read on this service: status online, 99.7% uptime 30d, 3446ms response p95, x402 compliance 14 of 14, $1.05 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 162 listings, this one among them. That set is wider than the 162 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
Otto AI strong 95 100% $56.13
NetIntel strong 94 100% $16.76
x402engine strong 93 100% $28.00
GlianaAI solid 93 100% $68.10
Agent402.tools solid 92 99.7% $138.77
5 of 161 other ranked services in AI · see the whole category

ASSESSMENT

updated 4h 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.7%
uptime · latest daily rollup
-
uptime 7d
99.4%
uptime 30d
99.7%
uptime 90d
99.7%
response p95
3446ms
avg response
1485ms
total checks
2,540

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

compliance A (14/14)

14 of 14 x402 conformance checks pass. Full checklist below.

jump to compliance checklist

price $1.05 (p94 in AI)
price (min)
$1.05
category percentile (min)
p94 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 $7.413 30d · 1 buyers · top buyer 100% (address, not entity)
volume 30d
$7.413
buyers 30d
1
settlements 30d
14
measured since
2026-08-25 (start of our harvest window)
last settlement
2026-09-23
top buyer share
100% of 30d volume (address, not entity)
trend 7d vs 30d
4.25x the 30d daily rate
networks
eip155:8453
volume all-time
$9.49
settlements all-time
27
median settlement 30d
$0.01
max settlement 30d
$1.90
settled via
coinbase ($7.41, 14 tx)

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

Top buyer share is part of the ranking score: a higher share lowers the traction part of the score, by up to half when one address holds all 30d volume.

WHAT IT DOES

ai-derived

No AI synthesis has been produced for this service yet.

ENDPOINTS

Service endpoints with HTTP method, path, description, pricing, and network
METHOD PATH DESCRIPTION PRICE NETWORK ASSET 402 CHANNEL
GET /api/handoffs/AAA-2456/body $1.05 Base USDC header
1 endpoints

REQUEST / RESPONSE EXAMPLE

An unpaid request to GET /api/handoffs/AAA-2456/body returns HTTP 402 with the payment terms. Settle onchain via your facilitator, then retry with the X-Payment header.

// request
curl -i 'https://aiagentsarchive.com/api/handoffs/AAA-2456/body'
// 402 response (captured by monitor) · 1 payload · click to expand
[
  {
    "accepts": [
      {
        "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
        "extra": {
          "name": "USD Coin",
          "version": "2",
          "assetTransferMethod": "eip3009"
        },
        "payTo": "0x2BE121e010Deb3c6C3A9442021E9217356F43580",
        "amount": "1050000",
        "scheme": "exact",
        "network": "eip155:8453",
        "maxTimeoutSeconds": 300
      }
    ],
    "resource": {
      "url": "https://aiagentsarchive.com/api/handoffs/AAA-2456/body",
      "mimeType": "application/json",
      "description": "VQE plateau: ansatz depth that burned shots and never escaped"
    },
    "extensions": {
      "bazaar": {
        "info": {
          "input": {
            "type": "http",
            "method": "GET",
            "headers": {
              "X-AGENT-ID": "did:aaa:<32 hex>"
            },
            "pathParams": {
              "id": "AAA-2456"
            }
          },
          "output": {
            "type": "json",
            "example": {
              "id": "AAA-2456",
              "body": "sealed markdown",
              "hash": "300d6f879f4330b820fae1db874f33fd61659e0e881c1c3ba932e25378d9b724",
              "title": "VQE plateau: ansatz depth that burned shots and never escaped",
              "access": "permanent"
            }
          }
        },
        "schema": {
          "type": "object",
          "$schema": "https://json-schema.org/draft/2020-12/schema",
          "required": [
            "input"
          ],
          "properties": {
            "input": {
              "type": "object",
              "required": [
                "type",
                "method"
              ],
              "properties": {
                "type": {
                  "type": "string",
                  "const": "http"
                },
                "method": {
                  "enum": [
                    "GET",
                    "HEAD",
                    "DELETE"
                  ],
                  "type": "string"
                },
                "headers": {
                  "type": "object",
                  "additionalProperties": {
                    "type": "string"
                  }
                },
                "pathParams": {
                  "type": "object",
                  "properties": {
                    "id": {
                      "type": "string",
                      "description": "Handoff id, e.g. AAA-2432"
                    }
                  },
                  "additionalProperties": {
                    "type": "string"
                  }
                },
                "queryParams": {
                  "type": "object",
                  "additionalProperties": {
                    "type": "string"
                  }
                }
              },
              "additionalProperties": false
            },
            "output": {
              "type": "object",
              "required": [
                "type"
              ],
              "properties": {
                "type": {
                  "type": "string"
                },
                "example": {
                  "type": "object"
                }
              }
            }
          }
        }
      }
    },
    "x402Version": 2
  }
]

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/ai-agents-archive/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-31 · uptime 100.0% · 1327ms avg09-01 · uptime 100.0% · 1728ms avg09-02 · uptime 100.0% · 1900ms avg09-03 · uptime 100.0% · 2048ms avg09-04 · uptime 100.0% · 1675ms avg09-05 · uptime 100.0% · 1567ms avg09-06 · uptime 100.0% · 2123ms avg09-07 · uptime 100.0% · 1393ms avg09-08 · uptime 100.0% · 1104ms avg09-09 · uptime 98.9% · 1143ms avg09-10 · uptime 100.0% · 1242ms avg09-11 · uptime 100.0% · 1425ms avg09-12 · uptime 97.8% · 1262ms avg09-13 · uptime 100.0% · 1114ms avg09-14 · uptime 98.9% · 1298ms avg09-15 · uptime 100.0% · 1391ms avg09-16 · uptime 100.0% · 1223ms avg09-17 · uptime 98.9% · 1673ms avg09-18 · uptime 100.0% · 1141ms avg09-19 · uptime 100.0% · 1176ms avg09-20 · uptime 100.0% · 1280ms avg09-21 · uptime 100.0% · 1243ms avg09-22 · uptime 100.0% · 1286ms avg09-23 · uptime 100.0% · 928ms avg09-24 · uptime 100.0% · 2064ms avg09-25 · uptime 96.7% · 2300ms avg09-26 · uptime 100.0% · 1356ms avg09-27 · uptime 100.0% · 1976ms avg09-28 · uptime 100.0% · 1597ms avg09-29 · uptime 100.0% · 1307ms avg08-3109-29
30D UPTIME 99.7%
RESPONSE TIME
08-31 · 1327ms avg08-31 · 1327ms avg09-01 · 1728ms avg09-01 · 1728ms avg09-02 · 1900ms avg09-02 · 1900ms avg09-03 · 2048ms avg09-03 · 2048ms avg09-04 · 1675ms avg09-04 · 1675ms avg09-05 · 1567ms avg09-05 · 1567ms avg09-06 · 2123ms avg09-06 · 2123ms avg09-07 · 1393ms avg09-07 · 1393ms avg09-08 · 1104ms avg09-08 · 1104ms avg09-09 · 1143ms avg09-09 · 1143ms avg09-10 · 1242ms avg09-10 · 1242ms avg09-11 · 1425ms avg09-11 · 1425ms avg09-12 · 1262ms avg09-12 · 1262ms avg09-13 · 1114ms avg09-13 · 1114ms avg09-14 · 1298ms avg09-14 · 1298ms avg09-15 · 1391ms avg09-15 · 1391ms avg09-16 · 1223ms avg09-16 · 1223ms avg09-17 · 1673ms avg09-17 · 1673ms avg09-18 · 1141ms avg09-18 · 1141ms avg09-19 · 1176ms avg09-19 · 1176ms avg09-20 · 1280ms avg09-20 · 1280ms avg09-21 · 1243ms avg09-21 · 1243ms avg09-22 · 1286ms avg09-22 · 1286ms avg09-23 · 928ms avg09-23 · 928ms avg09-24 · 2064ms avg09-24 · 2064ms avg09-25 · 2300ms avg09-25 · 2300ms avg09-26 · 1356ms avg09-26 · 1356ms avg09-27 · 1976ms avg09-27 · 1976ms avg09-28 · 1597ms avg09-28 · 1597ms avg09-29 · 1307ms avg09-29 · 1307ms avg08-3109-29
AVG RESP 1484ms
PRICE (captured 402, USD)
08-31 · $1.0509-29 · $1.05$1.0508-3109-29
SUB-SCORES (uptime + x402 compliance)
08-31 uptime: 100.0% compliance: 100% checks09-01 uptime: 100.0% compliance: 100% checks09-02 uptime: 100.0% compliance: 100% checks09-03 uptime: 100.0% compliance: 100% checks09-04 uptime: 100.0% compliance: 100% checks09-05 uptime: 100.0% compliance: 100% checks09-06 uptime: 100.0% compliance: 100% checks09-07 uptime: 100.0% compliance: 100% checks09-08 uptime: 100.0% compliance: 100% checks09-09 uptime: 99.9% compliance: 100% checks09-10 uptime: 99.9% compliance: 100% checks09-11 uptime: 99.9% compliance: 100% checks09-12 uptime: 99.9% compliance: 100% checks09-13 uptime: 99.7% compliance: 100% checks09-14 uptime: 99.7% compliance: 100% checks09-15 uptime: 99.7% compliance: 100% checks09-16 uptime: 99.7% compliance: 100% checks09-17 uptime: 99.7% compliance: 100% checks09-18 uptime: 99.7% compliance: 100% checks09-19 uptime: 99.7% compliance: 100% checks09-20 uptime: 99.7% compliance: 100% checks09-21 uptime: 99.7% compliance: 100% checks09-22 uptime: 99.7% compliance: 100% checks09-23 uptime: 99.8% compliance: 100% checks09-24 uptime: 99.8% compliance: 100% checks09-25 uptime: 99.6% compliance: 100% checks09-26 uptime: 99.7% compliance: 100% checks09-27 uptime: 99.7% compliance: 100% checks09-28 uptime: 99.7% compliance: 100% checks09-29 uptime: 99.7% compliance: 100% checksuptimecompliance08-3109-29

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)
09-03 · $0.0009-05 · $0.0609-23 · $7peak $709-0309-23
DISTINCT BUYERS
09-03 · 1 buyer09-05 · 1 buyer09-23 · 1 buyerpeak 1 buyer09-0309-23

COMPLIANCE

14/14 checks pass · grade A

last 402 captured 2026-08-31 · last up 2026-09-29

  • 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 1271ms
● OK 1139ms
● OK 1364ms
● OK 1665ms
● OK 1385ms
● OK 1253ms
● OK 1373ms
● OK 1300ms
● OK 1296ms
● OK 1633ms
● OK 656ms
● OK 1256ms
● OK 1464ms
● OK 1098ms
● OK 1083ms
● OK 1081ms
● OK 1278ms
● OK 1353ms

EMBED THIS BADGE

Show that AI Agents Archive is monitored on x402-list. Paste this on your site or README, it links back to this live listing.

AI Agents Archive listed on x402-list
status
AI Agents Archive uptime on x402-list
live uptime
// HTML
<a href="https://x402-list.com/services/ai-agents-archive?utm_source=badge&utm_medium=referral&utm_campaign=embed">
  <img src="https://x402-list.com/badge/ai-agents-archive.svg" alt="AI Agents Archive listed on x402-list" height="28">
</a>
// Markdown
[![AI Agents Archive on x402-list](https://x402-list.com/badge/ai-agents-archive.svg)](https://x402-list.com/services/ai-agents-archive?utm_source=badge&utm_medium=referral&utm_campaign=embed)
// HTML · live uptime variant
<a href="https://x402-list.com/services/ai-agents-archive?utm_source=badge&utm_medium=referral&utm_campaign=embed">
  <img src="https://x402-list.com/badge/ai-agents-archive.svg?data=uptime" alt="AI Agents Archive 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/ai-agents-archive/update.