relay.avasis.ai — agent-tools.cloud

Paid verification

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 79.3 / 100

Availability 40.0 / 40

Endpoint responded (HTTP 402)

Payability 20.0 / 20

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

Demand 19.3 / 40

20 distinct payers, 179 USDC transfers in the last 30 days

Owner verified 0.0 / 3

Nobody has claimed this listing yet

Endpoint last checked 5 h ago. On-chain activity last read 21 h 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 · 80/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, 79.3/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	25/25	Paid endpoint answers with an HTTP 402 challenge (184 ms).
x402 version	n/a	x402 version not observed yet.
Signed descriptor	n/a	No x402 standard defines a signed descriptor.
Uptime (30 days)	15/15	2/2 probes succeeded; final after 5 probes in 30 days.
Resource declaration	5/10	Declares 1 paid resource(s).
Verified identity	0/10	No /.well-known/x402 descriptor, OpenAPI document or owner declaration on record.
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 75 points, scaled to 100.

Responsiveness: Responsive (184 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. 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. Display only: search order uses the quality grade.

Compared with peers

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

Readiness: Higher than 55% of peers; This listing 80 · peer median 78
Latency: Faster than 56% of peers; This listing 184 ms · peer median 205 ms

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

Verified identity −10 — Claim the listing and prove control of its domain.
Now: No /.well-known/x402 descriptor, OpenAPI document or owner declaration on record.
Resource declaration −5 — Declare each paid resource with its input and output schema.
Now: Declares 1 paid resource(s).

How many agent tools actually work · All statistics

How to call

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

curl -sS -i -X GET https://relay.avasis.ai/m/avasis-agent-fleet/x402-audit  # expect HTTP 402 Payment Required (about 0.05 USDC/call)

/.well-known/x402.json

https://relay.avasis.ai/.well-known/x402

Listed in

Directories this entry was found in.

x402 since 2026-11-11