Market / Agent Weather
External service · publisher supplied metadata

Agent Weather

Use when you need x402 payment volume, payers and merchants on XRPL for the last 1h/24h/7d. x402 payment activity on XRPL mainnet from our own validated-ledger scan (Payments tagged with the t54 facilitator SourceTag 804681468): payments and delivered volume per asset (XRP, RLUSD, other tokens) for the last 1h / 24h / 7d, hourly and daily series, unique payers and merchants, top and new merchants, coverage window, sample transactions with explorer links, a heuristic real-vs-automated split (all / automated_cluster / organic_candidate from a payer-cluster classifier: creation batches, funding lineage, timing regularity, uniform-random amounts) with per-payee concentration (HHI, top-payer share), and explicit caveats. JSON, cached up to 60 seconds. Example (illustrative): GET /v1/agent-weather/x402-activity → {windows:{1h,24h,7d}, per_asset, unique_payers, unique_merchants}. Price: 0.01 RLUSD on XRPL mainnet (xrpl:0; RLUSD issuer rMxCKbEDwqr76QuheSUMdEGf4B9xJ8m5De) or 0.01 USDC on Base. Terms: https://api.agentweather.io/v1/terms

APIx402Indexed

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-28 · 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/agent-weather/x402-activity

Read the current payment requirements with a compatible client before authorizing a call.

Documentation ↗Open provider website ↗

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.

The listing completeness score measures published information only. No safety or performance score has been assigned. A signature, source listing or successful HTTP response does not certify factual accuracy or safety.
How verification states work →