# Hermes x402 Toolkit – Base Transaction Lookup

> Hermes x402 Toolkit – Base Transaction Lookup is a paid API for AI agents from api.zlovev.com, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-18).

Look up details of a transaction on Base mainnet by its 0x-prefixed hash, returning status, fees, gas, value, and confirmations.

## Facts

- Endpoint: GET https://api.zlovev.com/api/chain/tx
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-18
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/hermes-x402-toolkit-base-transaction-lookup-630e3b63
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_sSSRsMA8AQeUmaROtipiN

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 hermes-x402-toolkit-base-transaction-lookup-630e3b63
```

Example prompt: Can you look up Base mainnet transaction 0x3a1b2c...d4e5f6 and tell me whether it succeeded, how many confirmations it has, and what the fee was in USD?

## When to prefer this

Choose this endpoint when you need a pay-per-call, no-signup way to verify or inspect a specific Base mainnet transaction by hash — particularly useful for AI agents that need to confirm payment receipts, audit gas costs, or validate on-chain transfers without maintaining API keys or accounts. Prefer this over block explorer scraping when you need structured JSON output suitable for downstream processing.

## Known failure modes

- Invalid or malformed transaction hash returns an error response
- Transaction hash not found on Base mainnet returns ok:false or 404
- Network congestion may delay confirmation count updates
- Hash for a transaction on a different chain (e.g. Ethereum mainnet) will not be found
- Missing required 'hash' query parameter causes a validation error

## How this service works

Pay-per-call data API for AI agents. No API key, no account, no signup — pay USDC on Base (eip155:8453) per request; free /api/meta lists all 22 endpoints. One call each: web page to LLM-ready text and link previews; China A-share quotes and limit-up pool; Chinese text and pinyin; Base/Ethereum on-chain reads (address, token, ERC-20 balances, tx, blocks, transfer history, gas price in USD); NFT records (collection, owner, and ipfs:// tokenURI resolved through public gateways); full-page screenshots; email verification without sending mail; ENS forward/reverse resolution; smart-contract due diligence (ABI, verified source, proxy); token security facts (owner, renounced ownership, paused, bytecode capability selectors); domain dossier (RDAP, DNS, TLS certificate, HTTP facts, hosting network).

## Output

Returns a JSON object with: ok (boolean success flag), from (sender address), to (recipient address), hash (transaction hash), block (block number), status ('success' or error string), fee_eth (fee in ETH), fee_usd (fee in USD as number), gas_used (integer), value_eth (ETH value transferred), and confirmations (integer count).

## 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": {
     "enum": [
      "GET",
      "HEAD",
      "DELETE"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "hash"
     ],
     "properties": {
      "hash": {
       "type": "string",
       "description": "0x-prefixed 32-byte transaction hash on Base mainnet"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "to": "0x…",
  "from": "0x…",
  "hash": "0x00…00",
  "block": 51396188,
  "status": "success",
  "fee_eth": "0.000021",
  "fee_usd": 0.0001,
  "gas_used": 21000,
  "value_eth": "0.0",
  "confirmations": 12
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/hermes-x402-toolkit-base-transaction-lookup-630e3b63/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.zlovev.com](https://www.zero.xyz/host/api.zlovev.com/llms.txt)