# NewBotLabor Base Transaction Explainer

> NewBotLabor Base Transaction Explainer is a paid API for AI agents from newbotlabor--254ecdfcc2de11f19b541607ee4eb77e.web.val.run, paid per call via x402, $0.003/call, status unknown (last checked 2026-10-22).

Decodes and explains a Base mainnet transaction hash, identifying x402/EIP-3009 USDC settlement details including sender, recipient, amount, and relay info.

## Facts

- Endpoint: GET https://newbotlabor--254ecdfcc2de11f19b541607ee4eb77e.web.val.run/api/base/tx-explain?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-22
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/newbotlabor-base-transaction-explainer-43814374
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_gVaA-jyizP9ml4mt15cWo

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 newbotlabor-base-transaction-explainer-43814374
```

Example prompt: Can you explain what happened in this Base transaction — hash 0xabc123... — and confirm whether it was an x402 USDC settlement of 0.003 USDC to address 0x1748...8647?

## When to prefer this

Use this endpoint when you need to decode and verify a specific Base mainnet transaction, especially for x402/EIP-3009 USDC micropayment settlements. It is the right choice when an autonomous agent needs to confirm that a payment was correctly routed — checking sender, recipient, amount, and settlement method — before proceeding with a workflow. Prefer it over generic block explorers when you need structured, machine-readable output with optional validation checks against expected amounts and addresses, and when you want to confirm x402 protocol compliance specifically.

## Known failure modes

- Invalid or non-existent transaction hash returns an error or empty result
- Transaction found but not a USDC transfer — isX402Settlement will be false
- expectedPayTo or expectedAmount mismatch will include a payToCheck or amountCheck failure flag
- Base RPC unavailability causing lookup timeout
- Hash for a different chain (not Base mainnet) may return no result or incorrect data

## How this service works

Pay-per-call utilities for autonomous agents, paid with x402 (USDC on Base; no account, no API key).

## Output

A JSON object containing: transaction status, a human-readable summary of the transfer, the settlement method (e.g. transferWithAuthorization / EIP-3009), whether it was an x402 settlement, chain identifier, and a list of transfers each with from/to addresses, USDC amount, and token symbol.

## 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",
       "description": "Base mainnet tx hash"
      },
      "minAmount": {
       "type": "string",
       "description": "optional: minimum USDC amount, decimal"
      },
      "expectedPayTo": {
       "type": "string",
       "description": "optional: address that should receive USDC (adds payToCheck)"
      },
      "expectedAmount": {
       "type": "string",
       "description": "optional: exact USDC amount expected, decimal e.g. 0.003"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "chain": "base",
  "method": "transferWithAuthorization (EIP-3009, x402 exact settlement)",
  "status": "success",
  "summary": "x402/EIP-3009 settlement: 0.003 USDC from 0xc9c7… to 0x1748…, relayed by 0xca5e…",
  "transfers": [
   {
    "to": "0x1748…8647",
    "from": "0xc9c7…1670",
    "amount": 0.003,
    "symbol": "USDC"
   }
  ],
  "isX402Settlement": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/newbotlabor-base-transaction-explainer-43814374/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from newbotlabor--254ecdfcc2de11f19b541607ee4eb77e.web.val.run](https://www.zero.xyz/host/newbotlabor--254ecdfcc2de11f19b541607ee4eb77e.web.val.run/llms.txt)