# Obol XRP Transaction Lookup

> Obol XRP Transaction Lookup is a paid API for AI agents from obol.danieldutoit.net, paid per call via x402, $0.003/call, status unknown (last checked 2026-09-14).

Looks up a verified XRP Mainnet transaction by transaction hash and block number, returning on-chain transaction data or a not-found result.

## Facts

- Endpoint: GET https://obol.danieldutoit.net/v1/xrp/transaction
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/obol-xrp-transaction-lookup-ce6af64c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_XQQC2IBhudPZKAHKyfFWO

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 obol-xrp-transaction-lookup-ce6af64c
```

Example prompt: Can you look up XRP transaction hash a0a0a0a0a0a0a0a0a0a0a0a0a0a0a0a0a0a0a0a0a0a0a0a0a0a0a0a0a0a0a0a0 at block 103400001 on XRP Mainnet and tell me if it was found and what the transaction details are?

## When to prefer this

Choose this endpoint when you need cryptographically verified XRP mainnet transaction data with exact hash, block number, and transaction index matching. It is ideal for payment verification, auditing, and on-chain confirmation use cases where data integrity matters and you are willing to pay a small per-call USDC fee via the x402 protocol. Prefer this over free or unverified indexers when trust and data provenance are important.

## Known failure modes

- Transaction hash not found on XRP mainnet — returns found: false with null transaction
- Invalid or malformed transaction hash format — may return an error or not-found response
- Block number mismatch — if the hash exists but block number doesn't match, transaction may not be returned
- Payment failure via x402/USDC — call not executed if micropayment cannot be settled
- Network unavailability — upstream XRP node data may be temporarily inaccessible

## How this service works

Obol sells verified blockchain data over x402, settled in USDC on Base.

## Output

Returns a JSON object indicating whether the transaction was found (found: boolean), the network queried (xrp-mainnet), coverage metadata including match type (exact transaction hash, block number, and tx index) and maximum results, the transaction index, the block number, the transaction hash, and the full transaction object (or null if not found).

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "found": false,
  "network": "xrp-mainnet",
  "coverage": {
   "match_type": "exact_transaction_hash_block_number_and_tx_index",
   "maximum_results": 1
  },
  "tx_index": 7,
  "transaction": null,
  "block_number": "103400001",
  "transaction_hash": "a0a0a0a0a0a0a0a0a0a0a0a0a0a0a0a0a0a0a0a0a0a0a0a0a0a0a0a0a0a0a0a0"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/obol-xrp-transaction-lookup-ce6af64c/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from obol.danieldutoit.net](https://www.zero.xyz/host/obol.danieldutoit.net/llms.txt)