# VerifyLite Base Transaction Lookup

> VerifyLite Base Transaction Lookup is a paid API for AI agents from verifylite.hydratinghealingtouch.workers.dev, paid per call via x402, $0.0055/call, status unknown (last checked 2026-10-22).

Looks up a Base mainnet transaction by hash and returns its status, block info, fees (including L1 data fee), participants, ETH value, method ID, and all USDC transfers

## Facts

- Endpoint: POST https://verifylite.hydratinghealingtouch.workers.dev/chain/tx?utm_source=zero.xyz
- Price: $0.0055/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-22
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/verifylite-base-transaction-lookup-b8a57d13
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap__IdKwscrOSHO079Jl3EUI

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 verifylite-base-transaction-lookup-b8a57d13 -d '<json body>'
```

Example prompt: Can you look up Base mainnet transaction 0x4a7d3f9e2b1c8a56f0e3d7b2c9a4f1e8d5b6c3a0e7f2d9b4c1a8e5f3d6b9c2a and tell me whether it succeeded, what block it landed in, how many confirmations it has, the total fee including the L1 data fee, and whether any USDC was transferred?

## When to prefer this

Choose this endpoint when you need comprehensive on-chain transaction details for a specific Base mainnet tx hash — especially when you need the L1 data fee breakdown (unique to L2s), USDC transfer details within the transaction, or method ID decoding. Prefer this over generic Etherscan-style lookups when operating in an x402 payment-enabled agent workflow on Base.

## Known failure modes

- Invalid or malformed transaction hash returns a 400 error
- Transaction hash not found on Base mainnet returns a not-found error
- Pending transactions may have incomplete data (no block, no confirmations)
- Network timeouts from Base RPC nodes may cause intermittent failures
- Non-Base (e.g. Ethereum mainnet or other L2) transaction hashes will not resolve

## How this service works

Base mainnet transaction lookup by hash: status (success, failed, or pending), block, timestamp, confirmations, from, to, ETH value, total fee including the L1 data fee, method id, and every USDC transfer in the transaction decoded to sender, recipient, and amount. Useful for confirming that a USDC or x402 payment really settled before delivering goods. Read-only. Not charged for an invalid hash, a hash not found on Base, or when Base can't be reached.

## Output

Returns the transaction status (success, failed, or pending), block number, timestamp, number of confirmations, from and to addresses, ETH value transferred, total fee including the Base L1 data fee, method ID, and a list of every USDC transfer event in the transaction.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "hash": {
   "type": "string",
   "description": "0x transaction hash (64 hex characters)."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/verifylite-base-transaction-lookup-b8a57d13/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from verifylite.hydratinghealingtouch.workers.dev](https://www.zero.xyz/host/verifylite.hydratinghealingtouch.workers.dev/llms.txt)