Agent Weather
Use when you want pre-flight measurements of an XRPL x402 payee before paying it. Facts about one XRPL x402 payee (GET /v1/merchant/{r-address}): account age, first funder and Domain field, payments and unique payers in the last 24h from our own ledger scan, payer concentration (HHI, top-payer share), heuristic automated-cluster share, payer creation batches, funding links between payers and the merchant, timing regularity, amount distribution, endpoint liveness and valid 402 from one unpaid GET, and a 0-100 composite index (a measurement, not advice) with every component and its method shown. Directory listing is reported as unknown. Invalid addresses are rejected with 400 before any payment. JSON, precomputed every 30 min for active payees. Example (illustrative): GET /v1/merchant/rnFHPGmgTLSg7hjzfr8wiHaTdTh3PijrZZ → {account_age_days, payments_24h, payer_concentration, score, components[]}. Price: 0.03 RLUSD on XRPL mainnet (xrpl:0; RLUSD issuer rMxCKbEDwqr76QuheSUMdEGf4B9xJ8m5De) or 0.03 USDC on Base.
Listing completeness · 80/100
Presence of published information only. Not a security, reliability or performance score. Same rules for Datoka and external listings.
- Name and traceable source
- 10/10 · Present
- Meaningful description
- 10/10 · Present
- Connection or installation reference
- 20/20 · Present
- Dedicated documentation or source repository
- 0/15 · Missing or insufficient
- Explicit free access or numeric tariff
- 20/20 · Present
- Declared integration protocol
- 10/10 · Present
- Source updated within 90 days
- 10/10 · Present
- Declared capability names
- 0/5 · Missing or insufficient
Evaluated 2026-10-18 · Method listing-completeness-1. Scoring rules
Connect & use
Connect through the publisher’s supported interface. Any credentials or payments are handled by the provider.
x402 resource
https://api.agentweather.io/v1/merchant/:addressRead the current payment requirements with a compatible client before authorizing a call.
Categories and declared capabilities
Topic categories are derived from publisher text for discovery, not independently verified capabilities.
The registry does not provide a verified tools list. See the observations, when available, for any tools/list check; a published tools list does not establish that execution succeeds.
Evidence, with its limits.
This listing is indexed. Any domain claim or endpoint observation appears separately with its date and limited scope. No payment execution, factual accuracy or safety certification is inferred.