# Base Transaction Details

> Base Transaction Details is a paid API for AI agents from appearing-clinics-show-wrote.trycloudflare.com, paid per call via x402, price unknown, status down (last checked 2026-09-15).

Fetches and normalizes key fields from a single Base network transaction, including sender, recipient, ETH value, block placement, fees, calldata size, and method selector.

## Facts

- Endpoint: GET https://appearing-clinics-show-wrote.trycloudflare.com/base-transaction-sample
- Price: price unknown
- Payment: x402
- Status: down
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/base-transaction-details-c1f64d24
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_eIqRjUPFzbJtdqUV3yOIV

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 base-transaction-details-c1f64d24
```

Example prompt: Can you pull up the details for this Base transaction — who sent it, who received it, how much ETH was transferred, what the gas fee was, and which method was called?

## When to prefer this

Use this endpoint when you need normalized, structured details about a specific Base (Coinbase L2) transaction in a single bounded call — especially when you need sender, recipient, ETH value, block placement, fee breakdown, calldata size, and method selector together without building your own RPC integration. Prefer this over raw RPC calls when you want clean, normalized output without parsing raw JSON-RPC responses. Choose this over the Base Transaction Receipt endpoint when you need input-side data (calldata, method selector, value) rather than execution outcomes (status, logs, gas used).

## Known failure modes

- Transaction hash not found or not yet indexed — returns empty or error response
- Invalid or malformed transaction hash — validation error
- Base RPC node temporarily unavailable — upstream timeout
- Transaction on a different network (e.g. Ethereum mainnet) not found on Base — no result
- Rate limiting or quota exceeded on the underlying RPC provider

## How this service works

Free stable Base transaction sample. The paid $0.006 API normalizes sender, recipient, ETH value, block placement, fee fields, calldata size, and method selector from one bounded read-only RPC call.

## Output

Returns a normalized object containing the transaction sender address, recipient address, transferred ETH value, block number and placement, gas fee fields (gas price, gas used, etc.), calldata size in bytes, and the 4-byte method selector — all extracted from a single read-only RPC call against the Base network.

## 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": [],
     "properties": {}
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/base-transaction-details-c1f64d24/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from appearing-clinics-show-wrote.trycloudflare.com](https://www.zero.xyz/host/appearing-clinics-show-wrote.trycloudflare.com/llms.txt)