Agent Internet Runtime — agent-tools.cloud

The Agent Internet Runtime (AIR) is collective intelligence for AI agents to discover, trust, and interact with the web. Extract data, discover capabilities, execute actions, and report outcomes.

Paid verification

How it works

No sponsored paid call yet.

Pay this endpoint once from your own wallet (Base USDC, up to $1.00) and we call it and record what came back. Your wallet pays the listed recipient directly; Agent Tools never holds funds. Sponsored checks prove delivery; they do not count as demand.

Quality grade

How grading works

B+ 67.4 / 100

Availability 20.0 / 20

Endpoint responded (HTTP 402)

Payability 15.0 / 15

✓ Answers a real HTTP 402 challenge
✓ Publishes a /.well-known/x402 descriptor
✓ Payment address on record
✓ Settlement network declared
✓ Price declared

Demand 19.3 / 35

44 distinct payers, 159 USDC transfers in the last 30 days

Performance 0.0 / 10

Last probe answered in 4715 ms (full marks at 200 ms or less)

Readiness 13.1 / 15

Agent readiness 87/100

Owner verified 0.0 / 5

Nobody has claimed this listing yet

Endpoint last checked 18 h ago. On-chain activity last read 3 d ago. Availability and on-chain demand are both re-probed daily; the grade updates automatically on the next pass. This grade sets search order and leaderboards; the readiness score below is shown for reference only.

x402 readiness

B · 87/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here B+, 67.4/100), which weighs availability, payability and on-chain demand. How the two differ

Valid payment requirements	10/10	Payment requirements carry a payee, a mainnet network and a price.
Live 402 challenge	24/25	Paid endpoint answers with an HTTP 402 challenge (4715 ms); slow response -1.
x402 version	5/10	Speaks x402 v1; v2 is current.
Signed descriptor	n/a	No x402 standard defines a signed descriptor.
Uptime (30 days)	15/15	32/32 probes succeeded over 30 days (100%).
Resource declaration	10/10	Declares 7 paid resource(s).
Verified identity	5/10	Publisher descriptor (/.well-known/x402 or OpenAPI) on record; claim this listing to verify domain control.
Freshness + modern flags	5/5	seen in a source within 7 days; declares x402.
Security declaration	n/a	Payment is the access control for an x402 resource.

Applicable criteria total 85 points, scaled to 100.

Responsiveness: Slow (4715 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).

Payment evidence: x402_challenge — We sent a request and got a live HTTP 402 challenge. Also: x402_manifest, catalog_listing. Qualifies the payment claim; adds no points.

Measured 2026-11-11.

Nine criteria, the same as the A2A readiness score, read from our daily probe of the paid endpoint, its payment requirements and 30-day probe history. Signed descriptor and security declaration are n/a for x402 (payment is the access control), as is an x402 version we have not observed; the remaining points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. It also feeds 15 points of the x402 quality grade.

Compared with peers

Against 10,082 reachable x402 APIs in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.

Readiness: Higher than 76% of peers; This listing 87 · peer median 78
Latency: Faster than 3% of peers; This listing 4,715 ms · peer median 205 ms

Where it loses the most points, and how to win them back

x402 version −5 — Support the current protocol revision.
Now: Speaks x402 v1; v2 is current.
Verified identity −5 — Claim the listing and prove control of its domain.
Now: Publisher descriptor (/.well-known/x402 or OpenAPI) on record; claim this listing to verify domain control.
Live 402 challenge −1 — Answer the paid path with a valid 402 challenge.
Now: Paid endpoint answers with an HTTP 402 challenge (4715 ms); slow response -1.

How many agent tools actually work · All statistics

Paid endpoints

7 resource(s) advertised by this origin. Each price below is that resource's own x402 price; the headline price is the range across them.

https://api.agentinternetruntime.com/v1/agentjson $0.0100 / call

Agent.json lookup ($0.01/request direct, or $0.003/request via Session Ticket at /v1/billing/tickets)

https://api.agentinternetruntime.com/v1/batch $0.0500 / call

Batch Extract ($0.005/url, min 10 urls). For cheaper batched access, purchase a Session Ticket at /v1/billing/tickets

https://api.agentinternetruntime.com/v1/billing/tickets $0.0200 / call

Session Ticket Purchase (dynamic pricing). Prepay batches of API requests via x402.

https://api.agentinternetruntime.com/v1/capabilities $0.0100 / call

Capability Query ($0.01/request direct, or $0.003/request via Session Ticket at /v1/billing/tickets)

https://api.agentinternetruntime.com/v1/extract $0.0100 / call

Extract Webpage ($0.01/request direct, or $0.005/request via Session Ticket at /v1/billing/tickets)

https://api.agentinternetruntime.com/v1/registry/discover $0.0100 / call

Agent Registry discovery ($0.01/request direct, or $0.003/request via Session Ticket at /v1/billing/tickets)

https://api.agentinternetruntime.com/v1/sdk/batch $0.0030 / call

SDK Batch Processing — capabilities and macros in bulk. Supports x402 payment per item.

How to call

cURL · x402-fetch / x402-axios will auto-handle 402

curl -sS -i -X GET https://api.agentinternetruntime.com/v1/agentjson  # expect HTTP 402 Payment Required (about $0.003/call)

/.well-known/x402.json

https://api.agentinternetruntime.com/.well-known/x402

Listed in

Directories this entry was found in.

x402scan since 2026-05-22 paygent-discover since 2026-07-02