rtt.phoenix-ai.work — agent-tools.cloud

Health of 12 monitored chains (11 L2 and Casper L1; names in `chains`). Returns P99/P95 RTT from RPC probes (eBPF kernel RTT: separate field, not in the verdict), revert ratios (Base and Arbitrum via eth_getBlockReceipts), gas pressure, `recommendation` over the chains in service (`chains_in_service`; closed: `out_of_service`; all: `recommendation_all_chains`). Callers are labelled by behaviour...

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

A 72.8 / 100

Availability 20.0 / 20

Endpoint responded (HTTP 200)

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 14.8 / 35

17 distinct payers, 52 USDC transfers in the last 30 days

Performance 10.0 / 10

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

Readiness 13.0 / 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 A, 72.8/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	20/25	Endpoint reachable; its 402 challenge was seen earlier (163 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	32/32 probes succeeded over 30 days (100%).
Resource declaration	10/10	Declares 9 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 75 points, scaled to 100.

Responsiveness: Responsive (163 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, bazaar_feed, 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 75% of peers; This listing 87 · peer median 78
Latency: Faster than 63% of peers; This listing 163 ms · peer median 205 ms

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

Live 402 challenge −5 — Answer the paid path with a valid 402 challenge.
Now: Endpoint reachable; its 402 challenge was seen earlier (163 ms).
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.

How many agent tools actually work · All statistics

Paid endpoints

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

GET https://rtt.phoenix-ai.work/v1/safe

THE KEY ENDPOINT. Binary safety check: safe=true (execute now) or safe=false (wait). Returned reason codes: ok, elevated_latency, high_latency, sequencer_stall, elevated_revert, high_revert, chain_halted, data_stale, no_data. Also returns head_block_tx_count, tx_per_block_recent (mean over the last

GET https://rtt.phoenix-ai.work/v1/health

Full 12-chain health report: P99 RTT, packet loss (rpc_loss_pct: RPC requests without a valid answer, last ~2 min), stall detection, chain head age, revert ratios, kernel-level TLS round-trip (kernel_tls_rtt, eBPF, last 60 s). Per chain also head_block_tx_count, tx_per_block_recent (mean over the la

GET https://rtt.phoenix-ai.work/v1/price

FREE (no payment): Current surge pricing tier and gas pressure metrics.

GET https://rtt.phoenix-ai.work/v1/correlation

Cross-chain Pearson correlation matrix (R_xy) with Frobenius anomaly score. Returns 12×12 correlation matrix and synchronized pairs. Exploratory: not yet validated on real bot-cluster data.

GET https://rtt.phoenix-ai.work/v1/health-proof

Verifiable health proof with HMAC-SHA256 commitment. Cryptographic attestation of network state.

GET https://rtt.phoenix-ai.work/v1/demo/safe

FREE demo: 100 calls/IP/day. Returns safe=true/false without detailed metrics. Try before you buy.

POST https://rtt.phoenix-ai.work/v1/classify

Caller identity classification: HUMAN / LEGIT_AGENT / MALICIOUS_BOT / SYBIL / UNKNOWN (no evidence either way). 14-layer behavioral analysis: entropy, jitter, Spearman correlation, automation detection, rhythm trust.

POST https://rtt.phoenix-ai.work/v1/preflight

Full pre-flight check with extended metrics: RTT percentiles, revert data, gas pressure.

GET https://rtt.phoenix-ai.work/v1/chains/:chain

Per-chain detailed status: P99/P95 RTT, block propagation, sequencer latency.

How to call

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

curl -sS -i -X GET https://rtt.phoenix-ai.work/  # expect HTTP 402 Payment Required (about $0.01/call)

/.well-known/x402.json

https://rtt.phoenix-ai.work/.well-known/x402

Listed in

Directories this entry was found in.

cdp-bazaar since 2026-09-01 pay-skills-pr since 2026-09-06