Live XRPL signal feed
News, on-chain whale activity, and permissioned-domain events on XRPL, combined into one time-ordered feed with the context behind each entry. No editorial scoring. No source ranking. No social scraping.
Free from this page. Agents pay $0.10 per query over the x402 API at
pulse.xrpl-utilities.io.
XR-Pulse implements x402 v2 with the
exact scheme on XRPL mainnet.
Verification and settlement are delegated to the
t54 XRPL facilitator.
POST /events/recent returns 402 Payment Required with two options: XRP or RLUSD.
PAYMENT-SIGNATURE.
200 with the JSON and a PAYMENT-RESPONSE header.
Or skip the integration: call xrpl_pulse_recent_events from any
MCP client (Claude Desktop etc.) via
@xrpl-utilities/mcp
or the hosted endpoint at mcp.xrpl-utilities.io/mcp. Same x402 model, just wrapped as MCP tools.
from x402_xrpl import X402RequestsSession from xrpl.wallet import Wallet session = X402RequestsSession( wallet=Wallet.from_seed(seed), rpc_url="https://xrplcluster.com", payment_requirements_selector="XRP", ) feed = session.post( "https://pulse.xrpl-utilities.io/events/recent", json={"limit": 50}, ).json() for e in feed["events"]: print(e["title"], e["source_appearances"])
events[]: normalized records, newest-first; mixes news, whale, and permissioned-domain lifecycle in one streamtitle, primary_url, brief, published_at (UNIX seconds)source_appearances[]: which feed produced the event — a news source (e.g. coindesk, sec_press), whale_xrpl, or permissioned_domain_lifecycleappearance_count + cross_verified: number of independent sources covering the same story; flag set when 2+ within 48h. Whale and permissioned events are single-source by design.correlation (news only): XRPL price at ingestion and at +4h with delta percent. Pure measurement, no causal claim.active_utility: signal payload, shape varies by source — news carries {active, signals[]}; whale rows carry transfer details + Sentinel cross-ref; permissioned rows carry tx + domain + credential or XLS-81 trade economics. See /schema for the full per-source field list.target_addresses[], sentinel_context: XRPL addresses attached to the event + best-effort XR-Sentinel cross-referencerow_count, limit, min_whale_usd, schema_url: response envelope. min_whale_usd reflects the floor applied (default $1M; pass 0 to see the full $50k+ stream).
Full field-level details at /schema. Live manifest at /agents.json.
News stream. Every entry must mention Ripple, XRP, RLUSD, or XRPL. The institutional sources rarely name Ripple, so they fire infrequently but high-signal when they do. The crypto-press sources are tagged for XRP at the source and carry most of the volume.
When two news sources publish the same story (titles overlap within a 48-hour window), we collapse them into one record with a cross-verified flag and the secondary URLs listed alongside.
At ingestion we record the XRPL price. Four hours later we record it again and report the change. Pure measurement, no causal claim.
On-chain stream. The watcher polls validated XRPL ledgers every 60 seconds. Each successful Payment whose USD value clears the storage floor lands as one event with the transaction hash, ledger index, currency (XRP or RLUSD), and full sender + receiver addresses. Where XRPScan recognizes either address as a labeled venue (Binance, Coinbase, bitFlyer, Wanchain Bridge, etc.) the label appears on the card. One ledger transaction in, one event out, no clustering.
XR-Pulse is a measurement-only event feed, not an editorial product. Source presence is reported as a property of an event, not a verdict on the source. Correlation against XR-Telemetry is a measurement, not a causal claim.
Users are responsible for ensuring their use complies with local digital asset and AI regulations, including the California Digital Financial Assets Law and the Colorado AI Act where applicable.