Most XRPL data tells you the price. This tells you what it costs to actually move size — cumulative depth by basis-point band, and the slippage curve from 10 to 100,000 XRP.
A register of the top XRPL issuers with the controls they actually retain on-ledger: blackholed (the issuer can never mint again), permanently no-freeze, global freeze active now, clawback enabled, authorisation required, and issued supply. These are the questions an agent must answer immediately before it accepts a token.
We publish flags, not verdicts. “This issuer can freeze you” is a fact; “this token is unsafe” is advice, and we do not give advice.
Tokens whose names render identically under a normal decoder, with the evidence to tell them
apart: each issuer’s domain, issued supply and holder count. Some collisions are ordinary
— many gateways issue USD. Others differ only by bytes that are invisible in
every wallet and explorer, which is not something that happens by accident.
Collisions are reported as evidence. We do not assert that any issuer is fraudulent.
Per issuer: how many trustlines exist, how many actually hold a balance, how concentrated that balance is, how many lines are frozen, and how adoption moves over time. The gap between “trustlines opened” and “trustlines holding anything” is the difference between a token that was launched and one that is used.
Will your transaction land, and what will it cost? Live fee escalation (the open-ledger fee rises with load, and a transaction signed at the base fee during congestion is queued or dropped rather than rejected loudly), reserve requirements, queue depth, and amendment state.
An amendment-blocked node serves reads normally and silently rejects every submit. It is invisible from a dashboard unless someone publishes it.
Cumulative XRP reachable within 5 to 500 bps of mid, both sides — the running total, which is what decides whether an order is fillable at all. Plus a VWAP walk for realistic order sizes returning slippage and whether the book can fill that size, and wallet-level maker attribution with concentration.
Depth counts funded amounts only. The ledger will show you offers their owners cannot honour; summing them inflates depth with liquidity that disappears the moment you reach for it.
The x402 machine-to-machine payment market on the XRP Ledger, reconstructed from the ledger: payment counts, distinct buyers and sellers, volume, and the cross-chain landscape. Classified by a deterministic on-ledger fingerprint, not an inferred model.
These are true micropayments. The honest figure is transaction count, not dollar volume, and we report it that way.
| Endpoint | Returns | Price |
|---|---|---|
/v1/preflight | Bundled: will it land, what must I reserve, can the issuer freeze me | $0.75 |
/v1/issuer | Issuer safety register — freeze, clawback, blackhole, supply | $0.25 |
/v1/lookalikes | Token name collisions with issuer evidence | $0.25 |
/v1/trustlines | Holders, funded vs empty lines, concentration, adoption | $0.50 |
/v1/vitals | Fee escalation, reserves, queue, amendment state | $0.50 |
/v1/depth | Cumulative depth by bps band + execution-cost curve | $0.50 |
/v1/makers | Maker attribution and concentration | $0.50 |
/v1/x402 | XRPL agentic payment market | $0.05 |
/v1/chains | Cross-chain x402 landscape | $0.05 |
/v1/conditions | Book conditions and ledger health | free |
The API is exposed as an MCP server, so an agent can call it as a tool directly:
{
"mcpServers": {
"xrpl-microstructure": {
"command": "titan-mcp-server",
"env": { "API_KEY": "your-key" }
}
}
}| Tool | Returns |
|---|---|
xrpl_issuer_safety | Freeze, clawback, blackhole and supply per issuer |
xrpl_depth_bands | Cumulative depth + execution-cost curve |
xrpl_market_conditions | Spread, AMM relationship, volatility bucket, ledger health |
xrpl_x402_market | Agentic payment counts, participants, volume |
x402_chain_landscape | Cross-chain x402 facilitators, listings and pricing |
Or over HTTP, paying per call with x402 — no account, no key:
curl https://api.example.com/v1/depth
# 402 Payment Required → agent pays → 200 with the dataEvery response carries its source, an as_of timestamp and a
confidence class. Figures we measure ourselves are marked distinctly from figures read off
third-party dashboards — which, for cross-chain x402 volume, disagree with each other by an
order of magnitude. We would rather hand you a number with its provenance attached than a
confident one you cannot audit.
Snapshots are deliberately lagged by at least five minutes. This is descriptive market data, not a low-latency feed, and it is not sold as one.