# XRPL Transaction Lookup with Result Code Explanation

> XRPL Transaction Lookup with Result Code Explanation is a paid API for AI agents from twin.unykorn.org, paid per call via x402, $0.004/call, status unknown (last checked 2026-10-01).

Fetches a single XRP Ledger transaction by hash and returns its details along with a human-readable explanation of its result code

## Facts

- Endpoint: POST https://twin.unykorn.org/xrpl-tx?utm_source=zero.xyz
- Price: $0.004/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-01
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/xrpl-transaction-lookup-with-result-code-explanation-0cc80691
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_j3WMHc0B3Uxy_McSMIIal

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-transaction-lookup-with-result-code-explanation-0cc80691 -d '<json body>'
```

Example prompt: Can you look up XRPL transaction A3B4C5D6E7F80123456789ABCDEF0123456789ABCDEF0123456789ABCDEF0123 and explain what the result code means — did it succeed or fail?

## When to prefer this

Choose this endpoint when you need to resolve a specific XRPL transaction hash and also want a human-readable explanation of the result code — not just raw ledger data. It is ideal for debugging failed transactions, confirming payment finality, or explaining tec/tes/tef error codes to end users. Prefer this over generic XRPL node APIs when you want result code interpretation bundled with the raw transaction data in a single call.

## Known failure modes

- Invalid hash format (not 64 hex characters) — validation error returned
- Transaction hash not found on the XRPL — not found error
- Network timeout reaching XRPL node
- Payment failure via x402 protocol — 402 response if USDC payment not provided
- Malformed request body — 400 bad request

## How this service works

One XRPL transaction, with its result code explained — Genesis402 / UnyKorn Operator Network

## Output

Returns a JSON object with ok status, transaction type, the full XRPL transaction data, a human-readable explanation of the result code (e.g. tesSUCCESS, tecNO_DST, etc.), and a payment receipt including tx_hash, amount in USD, and a receipt ID.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "params": {
   "type": "object",
   "properties": {
    "hash": {
     "type": "string",
     "pattern": "^[0-9A-Fa-f]{64}$"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "type": "xrpl-tx",
  "receipt": {
   "tx_hash": "0x<64hex>",
   "amount_usd": 0.004,
   "receipt_id": "g402-<16hex>"
  },
  "generated_at": "<iso8601>"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/xrpl-transaction-lookup-with-result-code-explanation-0cc80691/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from twin.unykorn.org](https://www.zero.xyz/host/twin.unykorn.org/llms.txt)