# Obol Solana Transaction Lookup

> Obol Solana 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).

Fetches verified on-chain data for a specific Solana transaction by signature and slot number, returning full transaction details or a not-found indicator.

## Facts

- Endpoint: GET https://obol.danieldutoit.net/v1/solana/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-solana-transaction-lookup-83a9097a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_BdIgZYQj2gdqlHw6fX5nZ

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-solana-transaction-lookup-83a9097a
```

Example prompt: Can you look up the Solana mainnet transaction with signature 5KtPn1LGuxhFiwjxErkxTb7XxtLVe8tWNSBTzEGMTgCSmDNbFbYpbDymk3bS2E7t2jnKVpE and slot 42 and tell me if it was found and what the details are?

## When to prefer this

Choose this endpoint when you need cryptographically verifiable, exact-match lookup of a Solana mainnet transaction by both signature and slot number. It is ideal for payment confirmation, compliance auditing, or dApp debugging where you have a specific signature and slot and need authoritative on-chain data. Prefer this over generic RPC providers when you want a paid, verified data guarantee with USDC settlement via the x402 protocol.

## Known failure modes

- Transaction not found for given signature/slot — returns found: false with transaction: null
- Invalid or malformed transaction signature — may return error or not-found
- Slot number mismatch — transaction exists but not at the specified slot, returns not found
- Payment failure over x402 — call not executed if USDC settlement fails
- Network unavailable — upstream Solana node or Obol service outage

## How this service works

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

## Output

A JSON object indicating whether the transaction was found (found: true/false), the network queried (e.g. solana-mainnet), the exact signature and slot number queried, coverage metadata (match type and maximum results), and the full transaction object if found or null if not.

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "found": false,
  "network": "solana-mainnet",
  "coverage": {
   "match_type": "exact_signature_and_slot",
   "maximum_results": 1
  },
  "signature": "1111111111111111111111111111111111111111111111111111111111111111",
  "slot_number": "42",
  "transaction": null
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/obol-solana-transaction-lookup-83a9097a/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)