# XRPL Data Desk – Transaction Explainer

> XRPL Data Desk – Transaction Explainer is a paid API for AI agents from data.azeronyx.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-31).

Accepts an XRP Ledger transaction hash and returns a human-readable explanation of what that transaction did

## Facts

- Endpoint: POST https://data.azeronyx.com/v1/tx-explain?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-31
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/xrpl-data-desk-transaction-explainer-1487f5c4
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_HVRH_qANKho_ueLuStCi4

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability xrpl-data-desk-transaction-explainer-1487f5c4 -d '<json body>'
```

Example prompt: Can you explain what happened in XRPL transaction A1B2C3D4E5F6...0123456789ABCDEF — I need to know what type of transaction it was and what it actually did on the ledger?

## When to prefer this

Choose this endpoint when an AI agent needs to interpret or explain a specific XRP Ledger transaction by hash — particularly when a human-readable, audited explanation is needed rather than raw ledger JSON. Ideal for compliance checks, customer payment verification, debugging XRPL interactions, or any workflow requiring plain-language decoding of on-chain XRPL activity.

## Known failure modes

- Invalid or malformed transaction hash (not 64 hex characters) returns a validation error
- Transaction hash not found on the XRP Ledger returns a not-found error
- Network or XRPL node connectivity issues may cause timeouts
- Payment failure via x402 protocol results in 402 response before processing begins

## How this service works

Live XRP Ledger market data for AI agents, paid per call in XRP. Settled on the XRP Ledger itself; every endpoint independently audited. Information, not advice.

## Output

A structured object containing a human-readable explanation of the specified XRPL transaction, including transaction type, parties involved, amounts, status, and other ledger-relevant details decoded from the raw transaction data.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "hash"
 ],
 "properties": {
  "hash": {
   "type": "string",
   "description": "the transaction hash (64 hex characters)"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "description": "See https://data.azeronyx.com/v1/sample?path=/v1/tx-explain for a recent example",
 "additionalProperties": true
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/xrpl-data-desk-transaction-explainer-1487f5c4/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from data.azeronyx.com](https://www.zero.xyz/host/data.azeronyx.com/llms.txt)
