XRPreflight verifies destination readiness, payer affordability, and settlement receipts for XRPL Payments — so your agent never drops funds into a broken destination.
Validate first. Spend last. Fail closed.
Agents using Claude, Cursor, or any MCP-compatible runtime can install the XRPreflight stdio server in seconds. The default install is dry-run only — no wallet credential in MCP config, and nothing is sent to our server.
Phase 1 — dry-run only. The public install contains no wallet credential field. Paid mainnet MCP mode is disabled and unadvertised until later independent review. This merchant never collects a seed. Never paste a seed into chat, a remote service, a checked-in file, or MCP JSON config.
Prefer plain text? destinationpreflight.com/llms.txt has the verb, URL, price, and examples in one file.
All paid endpoints cost 1000 drops (0.001 XRP) via x402 exact on XRPL mainnet. Free inspect/dry-run available via the MCP before paying.
GET /v1/receive-card
Can this r-address receive XRP or RLUSD right now? Returns ready and a list of blockers: ACT_NOT_FOUND, REQUIRE_DEST_TAG, DEPOSIT_AUTH, DISALLOW_XRP, NO_RLUSD_TRUSTLINE, and more.
GET /v1/payer-ready
Can the sending account afford to pay amount of XRP or RLUSD? Checks spendable balance against reserve requirements and trust-line limits.
GET /v1/receipt
Structured, machine-readable receipt for a completed XRPL Payment transaction. Pass the tx hash; get back amounts, ledger index, destination tag, and delivery confirmation.
POST /v1/receive-card/batch
Check up to 10 destination addresses in a single paid call. Same fields as Receive Card per address — ideal for pre-screening a recipient list before a multi-send.
The MCP preflight_payment tool enforces this order automatically. The agent never skips a step.
Verify the sending account can afford the amount — including XRPL reserves and RLUSD trust-line limits.
payer_ready(address, amount)Confirm the destination can receive the asset. Detect frozen accounts, deposit-auth, missing trust-lines, and disallowXRP flags.
receive_card(address, asset)Both checks pass → the agent submits the signed XRPL Payment. XRPreflight does not sign or submit — your agent does.
agent.sign_and_submit(tx)After settlement, fetch a structured receipt for the transaction hash — amounts, ledger index, and delivery confirmation.
receipt(tx_hash)Recent preflight API usage from the free /v1/activity endpoint.
This table aggregates public on-chain XRPL data. It is not private user history. Payer and destination addresses are withheld here; the raw API may still expose public ledger fields.
Powered by destinationpreflight.com/v1/activity
Validate first. Spend last. Fail closed.
When payment safety is uncertain, XRPreflight does not send.
xrpl:0), price, PayTo, and local budget are all checked before any signing begins.
destinationpreflight.com never accepts one.
Payment hygiene, not AML, risk scoring, or security tooling.
The server never signs or submits transactions. rEB3eMYcrd1L7WXQMrAAWKfFiM1fRtpggt is a public receive-only address. We never ask for, store, or transmit any XRPL seed or private key.
The MCP enforces a per-session and per-day drop budget locally before signing anything. Defaults: 10,000 drops/session, 20,000 drops/day. These caps are advisory and do not replace limiting the buyer wallet's balance.
Every 402 challenge is verified: network must be xrpl:0, PayTo must match the known merchant, resource host must be destinationpreflight.com, and price must be ≤ max. Rejects anything else — fail-closed.
All MCP tools default to dry_run=True: they fetch and validate the 402 challenge without signing or paying. Set dry_run=False explicitly when ready to pay.
XRPreflight is a payment hygiene tool — it checks ledger state, not identity or compliance. We do not score wallets, flag addresses, or share data with compliance databases.
Payment signatures, signed transaction blobs, seeds, and wallet config are never written to logs. The MCP logs only the derived classic address for audit purposes.
XRPreflight is an independent service. We are not affiliated with Ripple, the XRPL Foundation, or t54 Labs. We complement — not compete with — the broader x402 ecosystem.
The x402 payment flow is handled by the T54 mainnet facilitator at xrpl-facilitator-mainnet.t54.ai. T54 verifies and settles the on-chain payment; XRPreflight is the resource server.
XRPreflight is listed in the XRPL AI Hub bazaar at xrpl-ai.org. Agents can discover this service via /.well-known/x402 or the Hub's discovery API.
destinationpreflight.com is the stable canonical API domain. All integrations, x402 resource URLs, and llms.txt references use this domain. xrpreflight.com is the discovery and install hub.