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.
Every XRPL transfer at or above $1,000,000 USD-equivalent. Scroll for more.
-- of XRPL settlement
-- of XRPL settlement
Yesterday, transfers above $1M moved -- out of -- in total XRPL settlement.
Total XRPL settlement is the denominator: every successful XRP and RLUSD Payment, any size, measured independently by XR-Telemetry. The remaining slice is everything below the $1M whale floor.
On-chain RLUSD outstanding on the XRP Ledger, continuously refreshed. The today's change badge appears when net XRPL supply has moved since yesterday's UTC close: green up-arrow for mints, red down-arrow for redemptions.
issuer rMxC...m5De; XRPL only. Cross-chain context: checking on Ethereum mainnet (separate ERC-20 contract).
Three buckets, no social-media noise:
No Twitter, no influencer feeds, no paid placements. Items that hit multiple sources within 48 hours get marked cross-verified.
Every successful XRPL Payment over $50k lands as a whale event with both addresses, USD value at ledger close, and labels when either side is a known exchange, market maker, treasury, or bridge.
Real-world-asset mints and burns land as a second stream. Permissioned-domain lifecycle events (XLS-70 / 80 / 81) land as a third. All time-ordered.
Traders watching for a news catalyst that just moved on-chain flow. Researchers correlating a regulatory announcement to actual settlement activity. Agents that need both market context and raw on-chain signal in one paid call. Not editorial; sources are reported as a property of an event, not as a verdict on whether the source is credible.
Need more than 24 hours? GET /stats/whale-flow-history returns the same institutional + whale tiers rolled up to one row per UTC day, queryable as a trailing window or an explicit date range. Free endpoint, no payment header. Coverage accrues forward from each deploy; pre-rollup windows return an honest no-data marker.
Wallets touched by multiple distinct watcher signal types in a tight window, OR wallets with two direct signals adjacent to a wallet-anonymized macro signal (relay-burst chain or RWA obligations change). Surfaces the cross-signal coordination that any single watcher would only show in part: a CEX-funded operator routing through a known consolidator while a parallel burn fires, that kind of thing. Sorted by attributable USD descending.
Free from this page. Agents pay $0.10 per query, or buy a live stream
window (1h $0.50 / 6h $2.50 / 24h $7.50) 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.
Two ways to consume the feed: pay per snapshot, or buy a time-boxed WebSocket window
and receive events as they fire.
POST /events/recent returns a snapshot of the most recent matched events. One payment, one response. Right for polling agents and one-off lookups.
POST /stream/purchase mints a JWT that opens a long-lived WebSocket at wss://pulse…/stream. Events arrive as they fire. 1h $0.50, 6h $2.50, 24h $7.50.
402 Payment Required with three options: XRP, RLUSD, or USDC on Base.
PAYMENT-SIGNATURE.
200 with a PAYMENT-RESPONSE header.
Free read-only views: GET /stats/whale-flow-24h, /stats/whale-flow-history, /stats/rwa-summary, and /stats/recent-choreographies (newest cross-signal windows) return pre-aggregated snapshots without a payment header. Use them for dashboards; use the paid endpoints for raw event streams.
xrpl_pulse_network_statsxrpl_pulse_whale_flow_24hxrpl_pulse_rwa_summaryxrpl_pulse_exchange_flow_deltaxrpl_pulse_ripple_counterpartiesxrpl_pulse_ripple_topologyxrpl_pulse_cex_attributionxrpl_pulse_recent_events · $0.10xrpl_pulse_events_by_address · $0.10xrpl_pulse_stream_purchase · $0.50 to $7.50
Or skip the integration: call any tool above from an
MCP client (Claude Desktop etc.) via
@xrpl-utilities/mcp
or the hosted endpoint at mcp.xrpl-utilities.io/mcp. Free tools work without a payment header; paid tools use the same x402 model wrapped as MCP arguments.
from x402_xrpl import X402RequestsSession from xrpl.wallet import Wallet session = X402RequestsSession( wallet=Wallet.from_seed(seed), rpc_url="https://YOUR_XRPL_RPC", 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 + on-chain activity (whale, permissioned-domain lifecycle, focus-watch, relay-burst, RWA obligations, cross-signal choreographies, institutional dispersion) in one streamtitle, primary_url, brief, published_at (UNIX seconds)source_appearances[]: which feed produced the event. News sources (e.g. coindesk, sec_press) plus on-chain sources: whale_xrpl, permissioned_domain_lifecycle, focus_watch, relay_burst, rwa_obligations_delta, rwa_issuer_flow, sentinel_signal, choreography_watcher, institutional_dispersionappearance_count + cross_verified: number of independent sources covering the same story; flag set when 2+ within the dedupe window. On-chain 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[]}; on-chain rows carry a top-level signal field identifying the kind (e.g. whale_transfer, focus_outflow, relay_burst_detected, rwa_obligations_spike/drop, institutional_choreography_detected, institutional_dispersion_detected) with per-signal fields. Most signal kinds also carry an optional tldr string (server-generated plain-English summary). See /schema for the full per-signal field list.target_addresses[], sentinel_context: XRPL addresses attached to the event + best-effort XR-Sentinel cross-referencerow_count, limit, min_whale_usd, kind (news | activity filter), schema_url: response envelope. min_whale_usd reflects the floor applied (default $100k so the $100k-$1M attribution band is visible; 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 reads validated XRPL ledgers continuously. Each successful Payment whose USD value clears the storage floor lands as one event with the transaction hash, ledger position, currency (XRP or RLUSD), and full sender + receiver addresses. Where either address resolves to a labeled venue (Binance, Coinbase, bitFlyer, Wanchain Bridge, etc.) the label appears on the card. One ledger transaction in, one event out, no clustering.
RWA supply stream. Per-issuer mint and burn detection runs in two parallel paths. The Payment classifier catches direct issuer-to-holder IOU Payments and the redemption pattern (holder returns IOU to issuer). The obligations-delta watcher fires when an issuer's outstanding obligations change by more than the configured threshold between passes, which catches DEX-mediated mints the Payment classifier misses (Ripple brings RLUSD into circulation via OfferCreate on the XRPL DEX, not direct Payments). Both surface as event cards with the issuer, asset, and direction; the latter explicitly tags inference_method=obligations_delta so consumers can tell the two apart.
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 complying with local digital asset and AI regulations, including the California Digital Financial Assets Law and the Colorado AI Act where applicable.