XRPL Trading

The XRPL DEX is a fully on-ledger, permissionless exchange — no intermediary, no off-chain matching engine, no custody transfer. Every offer is a ledger object. Crossing happens atomically during transaction processing in the order determined by ledger consensus. The same properties that make it reliable for institutional settlement make it well-suited for AI agents: 3–5 second deterministic finality, predictable fees, and no ambiguous pending state.

The XRPL Trading skill is the domain knowledge layer for DEX operations on the XRP Ledger. It gives Claude accurate, up-to-date knowledge of XRPL offer semantics so it can construct the right transaction object for any trading task — limit orders, cancellations, order book reads, cross-currency exchange, and AMM interaction — and hand that object to the XRPL Agent Wallet skill for signing and submission.

Both skills are required for a complete agentic trading workflow.

The Trading skill is one of a growing set of XRPL domain skills. All domain skills pair with the same shared Wallet skill. See AI Tooling for the full list.

Need a wallet first? If the user doesn't have an XRPL wallet yet, load the XRPL Agent Wallet skill — it handles wallet generation, writes the seed safely to .env, and never shows it in chat. Return here once the wallet is ready.

• Languages: Python (xrpl-py) and TypeScript/JavaScript (xrpl.js) are both first-class. Use whichever the developer's project already uses; if there is no existing codebase, ask. Code examples in the skill reference files cover both.
• Transaction submission: Handled entirely by the XRPL Agent Wallet skill. This skill builds transaction objects; it does not call submit_and_wait or submitAndWait directly.
• Signing path: Determined by the XRPL Agent Wallet skill configuration — env-var (development), external signer (HSM/KMS), or OWS (Open Wallet Standard). See The XRPL Agent Wallet Skill for setup.
• Amount handling: XRP amounts are always strings in drops — use xrp_to_drops() / xrpToDrops(). Never pass floats or raw XRP values. IOU amounts use {currency, issuer, value} objects with value as a decimal string.
• Source tag: The XRPL Agent Wallet skill automatically applies SourceTag = 20260530 to every transaction that passes through the signing ceremony. Override by setting SourceTag on the transaction object before handoff. You do not need to set SourceTag — the Wallet skill applies it. Set it only for a deliberate custom tag, or 0 to opt out.
• Network: Testnet (https://s.altnet.rippletest.net:51234) by default. Switching to Mainnet is a one-line URL change.
• Simulate before the summary: Where the node supports it, call simulate on the built transaction before showing the pre-trade summary. It returns the ledger's own engine_result with applied: false and costs no fee, catching cases no local check covers — tecNO_LINE, tecNO_AUTH, tecFROZEN, tecNO_ISSUER. Recommended, not required: fall back to the local guardrails if simulate is unavailable.

1. Identify the operation — create_offer, cancel_offer, or get_order_book. Check the trading.md reference for full patterns and edge cases.
2. Check prerequisites — Trust line exists for IOU side of offer? Account has sufficient balance including fees and reserve for a new resting offer? Expiry is in the future?
3. Build — Construct the transaction object. Do not set Fee, Sequence, or LastLedgerSequence — the Wallet skill's autofill populates these from the live node.
4. Run built-in guardrails — Apply pre-flight checks before asking the user to approve anything: reserve adequacy, trust line state (including RequireAuth issuers on the buy side), expiry sanity, and flag conflicts. Stop and surface a clear error if any check fails — never ask a user to approve a trade already known to fail, because every tec* failure charges a fee.
5. Show pre-trade summary — For create_offer, always show offer details, mid price, estimated fill, slippage, and the pre-flight verdict. Collect user acknowledgement before proceeding.
6. Hand off to the Wallet skill — Re-assert the guardrails against current ledger state, then pass the transaction object to the XRPL Agent Wallet skill. It will autofill, preview, sign, and submit via submitAndWait.
7. Parse and surface result — Classify the fill outcome (filled / partial / resting). Surface the offer sequence when a remainder exists on the book. Handle tec* errors explicitly — every tec* code means a fee was charged with no fill.

• Create wallets or handle keys. Wallet generation, seed storage, key loading, signing, and all key management belong to the XRPL Agent Wallet skill.
• Sign or submit transactions. That is the Wallet skill's responsibility. This skill never calls submit_and_wait, submitAndWait, or any equivalent directly.
• Construct non-trading transactions on its own initiative. The skill responds to developer and user instructions; it does not propose offers unprompted.
• Retry automatically. Any tec* failure or user cancellation requires explicit user instruction before retrying.

The trading skill references these files for full transaction patterns and edge cases:

• trading.md — OfferCreate, OfferCancel, order book patterns, AMM integration, cross-currency flows, agentic patterns, error codes, reserves

• Getting Started with XRPL Trading — Install the Trading skill and place your first limit order on the XRPL DEX.
• The XRPL Agent Wallet Skill — Security model, signing ceremony, and key handling patterns including OWS.
• Decentralized Exchange — XRPL DEX concepts: offer matching, quality, and the order book.
• View AI Tooling — The full set of XRPL skills and MCP servers for Claude agents.