# ScrapeMole Onchain Transaction Lookup

> ScrapeMole Onchain Transaction Lookup is a paid API for AI agents from onchain.scrapemole.workers.dev, paid per call via x402, $0.002/call, status unknown (last checked 2026-10-12).

Fetches on-chain transaction details for a given hash on Base or Ethereum, including status, gas, value, and decoded ERC-20 token transfers

## Facts

- Endpoint: GET https://onchain.scrapemole.workers.dev/v1/tx?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/scrapemole-onchain-transaction-lookup-1d3ede45
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_zrgAs9bHzIzVrw0UHoN3-

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 scrapemole-onchain-transaction-lookup-1d3ede45
```

Example prompt: Can you look up this Base transaction for me — 0x6c6a66f1d1d3b0cbe2d6d7e1b0b3a8f6c2a0e5d4c3b2a19080706050403020100 — and tell me if it succeeded, how much USDC was transferred, and what the gas fee was?

## When to prefer this

Use this endpoint when you need to verify or audit a specific on-chain transaction by hash on Base or Ethereum, especially to confirm ERC-20 token transfers (e.g. USDC payment verification). It is the right choice when you already have a transaction hash and need decoded transfer details, status, gas costs, or confirmation count. Prefer it over block explorers when you need machine-readable structured data for an agent workflow. It is pay-per-call so suitable for on-demand lookups without subscription overhead.

## Known failure modes

- Invalid or malformed transaction hash returns an error
- Transaction hash not found on the specified chain returns a not-found error
- Unsupported chain value returns a validation error
- Payment failure (x402) means the call is not charged and the request is rejected
- RPC or chain node unavailability may cause transient errors

## How this service works

Pay-per-call on-chain data for agents on Base and Ethereum, read directly from chain state: Chainlink USD prices (crypto, stablecoins, FX, metals; 10 per call), ERC-20 token info, wallet balances with USD values, transaction lookup with decoded ERC-20 transfers, ENS and Basename resolution (forward and reverse), gas and fee estimates in USD, and Uniswap v3 DEX prices for long-tail tokens (verify a payment arrived). USDC via x402; failed calls are never charged.

Payments: x402 v2, scheme "exact", USDC on Base (eip155:8453). The payment is verified before the work and settled only when the response is 200. Terms: https://onchain.scrapemole.workers.dev/terms

## Output

Returns a JSON object with the transaction hash, chain, status (success/fail/pending), sender, recipient, value in ETH, fee in ETH, gas used, block number, confirmations, timestamp, explorer URL, method selector, and an array of decoded ERC-20 transfers each containing token contract address, symbol, sender, recipient, raw amount, and human-readable 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": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "hash"
     ],
     "properties": {
      "hash": {
       "type": "string",
       "examples": [
        "0x6c6a66f1d1d3b0cbe2d6d7e1b0b3a8f6c2a0e5d4c3b2a19080706050403020100"
       ],
       "description": "Transaction hash (0x + 64 hex)."
      },
      "chain": {
       "enum": [
        "base",
        "ethereum"
       ],
       "type": "string",
       "default": "base",
       "description": "Chain."
      }
     },
     "additionalProperties": false
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "to": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
  "from": "0x…",
  "hash": "0x…",
  "chain": "base",
  "feeEth": "0.0000021",
  "status": "success",
  "gasUsed": "62000",
  "explorer": "https://basescan.org/tx/0x…",
  "valueEth": "0",
  "timestamp": "2026-10-11T18:00:01.000Z",
  "transfers": [
   {
    "to": "0x…",
    "raw": "10000",
    "from": "0x…",
    "token": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
    "amount": "0.01",
    "symbol": "USDC"
   }
  ],
  "blockNumber": 36500000,
  "confirmations": 120,
  "methodSelector": "0xa9059cbb"
 }
}
```

## More

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