# CoCo XRPL Transaction Explainer

> CoCo XRPL Transaction Explainer is a paid API for AI agents from cocoeatsai.com, paid per call via x402, $0.0027/call, status unknown (last checked 2026-10-19).

Explains and reviews an XRP Ledger transaction in plain language, returning its type and a verdict

## Facts

- Endpoint: GET https://cocoeatsai.com/area4/agent/xrpl/explain?utm_source=zero.xyz
- Price: $0.0027/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-19
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/coco-xrpl-transaction-explainer-9e79c68b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_56NxIXTZdq-NiycHGsMOc

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 coco-xrpl-transaction-explainer-9e79c68b
```

Example prompt: Can you explain this XRP Ledger transaction for me and tell me whether it needs review? Here's the raw transaction data: [tx blob]

## When to prefer this

Use this endpoint when you need a quick, plain-language explanation and risk verdict for a raw XRP Ledger transaction — particularly useful before signing transactions, during compliance audits, or when helping non-technical users understand what an XRPL transaction does. Prefer this over generic blockchain explorers when you need a structured JSON verdict rather than a human-readable webpage.

## Known failure modes

- Missing required 'tx' query parameter returns an error
- Malformed or invalid transaction data may produce an unrecognized type or error response
- Transaction data exceeding 20,000 characters will be rejected
- Invalid signer address format may cause a validation error

## How this service works

Zach Riehn's lab: an about-me and portfolio, a news desk, The Atelier for AI experiments, Launch Lab for XRP research, and Fracture for games.

## Output

A JSON object containing the transaction type (e.g. 'Payment') and a verdict field (e.g. 'review' or similar status indicating whether the transaction warrants attention).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input",
  "output"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method",
    "queryParams"
   ],
   "properties": {
    "type": {
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ]
    },
    "queryParams": {
     "type": "object",
     "required": [
      "tx"
     ],
     "properties": {
      "tx": {
       "type": "string",
       "title": "Tx",
       "maxLength": 20000
      },
      "signer": {
       "type": "string",
       "title": "Signer",
       "maxLength": 40
      },
      "max_xrp": {
       "type": "string",
       "title": "Max Xrp",
       "maxLength": 40
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type",
    "example"
   ],
   "properties": {
    "type": {
     "const": "json"
    },
    "example": {
     "type": "object",
     "required": [
      "type"
     ],
     "properties": {
      "type": {
       "type": "string"
      }
     }
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "type": "Payment",
  "verdict": "review"
 },
 "exampleNote": "Illustrative response subset; not a live observation."
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/coco-xrpl-transaction-explainer-9e79c68b/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from cocoeatsai.com](https://www.zero.xyz/host/cocoeatsai.com/llms.txt)