# ManyLives Onchain - Transaction Explainer

> ManyLives Onchain - Transaction Explainer is a paid API for AI agents from api.manylives.me, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-10).

Decodes and explains a Base network transaction hash, returning a human-readable summary of transfers, fees, and optional payment verification

## Facts

- Endpoint: GET https://api.manylives.me/paid/tx/explain?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-10
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/manylives-onchain-transaction-explainer-f9237417
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ICn7wBbyOq3CHW8OE08cf

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 manylives-onchain-transaction-explainer-f9237417
```

Example prompt: Can you explain what happened in Base transaction 0xb33254bb0332ea6bede020e6f2aa4df0161e0e5b6ce9559b56859ce32c1ec163 — specifically whether address 0xcd… received at least 1.5 USDC?

## When to prefer this

Choose this endpoint when you need to decode and verify a specific Base network transaction — especially when confirming on-chain payments between agents or validating that a transfer of a specific token amount to a specific address occurred. Prefer this over generic block explorers when you need structured JSON output with payment verification logic built in, and when operating in a pay-per-call agent context on Base.

## Known failure modes

- Invalid or malformed tx hash returns an error — must be a valid 0x-prefixed hex string
- Transaction not found on Base network if the hash doesn't exist or is on a different chain
- Payment check fails if expect_to address or expect_min_usd don't match actual transfer data
- Network latency or RPC errors from Base node may cause timeouts
- Non-Base-network transactions will not be found or may return incorrect data

## How this service works

Pay-per-call tools for people building AI agents: live web search and page contents, point-in-time crypto market data and news for backtests (no lookahead), verifiable track records of 1,000 crypto strategies locked on the Base network, company profiles, quick AI and batch prices. Ask us to turn a public website into a JSON endpoint. Pay per call, no account, free trial.

## Output

A JSON object containing the transaction hash, sender, receiver, success status, gas fee in ETH, a plain-English summary of what happened, an array of token transfers (each with from/to/token/amount), and optionally a payment_check object indicating whether the expected recipient received the minimum USD amount.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "type": "string",
     "const": "GET"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "tx"
     ],
     "properties": {
      "tx": {
       "type": "string",
       "examples": [
        "0xb33254bb0332ea6bede020e6f2aa4df0161e0e5b6ce9559b56859ce32c1ec163"
       ],
       "description": "0x... transaction hash on the Base network (required)"
      },
      "expect_to": {
       "type": "string",
       "description": "optional 0x address that should have received funds"
      },
      "expect_min_usd": {
       "type": "string",
       "description": "optional minimum stablecoin amount expected"
      }
     }
    }
   }
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "json"
    },
    "example": {
     "type": "object",
     "properties": {
      "to": {
       "type": "string"
      },
      "tx": {
       "type": "string"
      },
      "from": {
       "type": "string"
      },
      "status": {
       "type": "string"
      },
      "fee_eth": {
       "type": "string"
      },
      "summary": {
       "type": "string"
      },
      "transfers": {
       "type": "array",
       "items": {
        "type": "object",
        "properties": {
         "to": {
          "type": "string"
         },
         "from": {
          "type": "string"
         },
         "token": {
          "type": "string"
         },
         "amount": {
          "type": "string"
         }
        }
       }
      },
      "payment_check": {
       "type": "object",
       "properties": {
        "received": {
         "type": "boolean"
        },
        "amount_usd": {
         "type": "number"
        }
       }
      }
     }
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "to": "0x…",
  "tx": "0x…",
  "from": "0x…",
  "status": "success",
  "fee_eth": "0.0000012",
  "summary": "0xab… sent 1.5 TKN to 0xcd…",
  "transfers": [
   {
    "to": "0x…",
    "from": "0x…",
    "token": "TKN",
    "amount": "1.5"
   }
  ],
  "payment_check": {
   "received": true,
   "amount_usd": 1.5
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/manylives-onchain-transaction-explainer-f9237417/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.manylives.me](https://www.zero.xyz/host/api.manylives.me/llms.txt)