# Mach Gallery Base Transaction Lookup

> Mach Gallery Base Transaction Lookup is a paid API for AI agents from api.mach.gallery, paid per call via x402, $0.008/call, status unknown (last checked 2026-10-02).

Fetches full transaction details for a given transaction hash on the Base blockchain (EIP-155 chain 8453), paid per-call with USDC via x402.

## Facts

- Endpoint: POST https://api.mach.gallery/api/base/transaction?utm_source=zero.xyz
- Price: $0.008/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/mach-gallery-base-transaction-lookup-082f5702
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_TSjicF5vquPt9DJCVYuCO

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 mach-gallery-base-transaction-lookup-082f5702 -d '<json body>'
```

Example prompt: Can you look up the Base blockchain transaction 0x3a1b2c4d5e6f7a8b9c0d1e2f3a4b5c6d7e8f9a0b1c2d3e4f5a6b7c8d9e0f1a2b and tell me who sent it, who received it, and how much was transferred?

## When to prefer this

Choose this endpoint when you need lightweight, pay-per-call Base blockchain transaction lookups without managing API keys or subscriptions. It is ideal for agents that occasionally need on-chain transaction data on Base (EIP-155:8453) and want to pay micro-amounts in USDC via the x402 protocol rather than committing to a subscription service like Alchemy or Infura. Not suited for high-volume bulk queries or for chains other than Base.

## Known failure modes

- Transaction hash not found on Base — returns found:false
- Malformed tx_hash (not matching ^0x[0-9a-fA-F]{64}$) — likely 400 validation error
- Payment failure or insufficient USDC balance via x402 — 402 Payment Required
- Network timeout or RPC unavailability — 5xx server error
- Hash exists on a different chain (e.g. Ethereum mainnet) but not Base — returns found:false

## How this service works

Fast, low-cost Base data for autonomous agents. No API keys, no subscriptions; pay per call with USDC over x402.

## Output

Returns a JSON object with a 'found' boolean, the network identifier ('eip155:8453' for Base), and a 'transaction' object containing the 'from' address, 'to' address, 'hash', and 'value' (as a hex string) for the requested transaction. If the transaction is not found, 'found' will be false.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "tx_hash": {
   "type": "string",
   "pattern": "^0x[0-9a-fA-F]{64}$",
   "description": "32-byte Base transaction hash."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "found": true,
  "network": "eip155:8453",
  "transaction": {
   "to": "0x...",
   "from": "0x...",
   "hash": "0x...",
   "value": "0x0"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/mach-gallery-base-transaction-lookup-082f5702/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.mach.gallery](https://www.zero.xyz/host/api.mach.gallery/llms.txt)