# Hearth Markdown – Base Transaction Status

> Hearth Markdown – Base Transaction Status is a paid API for AI agents from 138-197-15-135.sslip.io, paid per call via x402, $0.004/call, status unknown (last checked 2026-10-26).

Looks up the on-chain status and details of a blockchain transaction by hash on Base (or other EVM chains).

## Facts

- Endpoint: GET https://138-197-15-135.sslip.io/v1/base/tx-status?utm_source=zero.xyz
- Price: $0.004/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-26
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/hearth-markdown-base-transaction-status-6dcf8f14
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Wv2BBqwMBv17mFzXV6Mno

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 hearth-markdown-base-transaction-status-6dcf8f14
```

Example prompt: Can you check whether my Base transaction 0xabc123...def went through successfully and how many confirmations it has?

## When to prefer this

Use this endpoint when you need to verify or inspect the result of a specific EVM transaction — especially payments made via the x402 protocol on Base — and need authoritative on-chain status including confirmations, gas used, and block number. Prefer this over a generic block explorer when you need a clean machine-readable JSON response suitable for agent workflows.

## Known failure modes

- Invalid or malformed transaction hash returns an error
- Transaction not yet indexed returns pending or not-found status
- Unsupported chain identifier causes an error
- Network timeout if the RPC node is slow
- Hash on the wrong chain (e.g. querying Base for an Ethereum tx) may return not found

## How this service works

Web page to clean Markdown for AI agents. Pay per call with x402 (USDC on Base).

## Output

Returns a JSON object with the transaction's status (e.g. 'success'), sender and recipient addresses, transaction hash, number of logs emitted, chain name, gas used, block number, and number of confirmations.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "queryParams"
   ],
   "properties": {
    "queryParams": {
     "type": "object",
     "required": [
      "hash"
     ],
     "properties": {
      "hash": {
       "type": "string",
       "description": "Transaction hash"
      },
      "chain": {
       "type": "string",
       "description": "Chain: base (default), ethereum, arbitrum, optimism"
      }
     }
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "to": "0x…",
  "from": "0x…",
  "hash": "0x…",
  "logs": 0,
  "chain": "base",
  "status": "success",
  "gasUsed": "21000",
  "blockNumber": 1,
  "confirmations": 10
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/hearth-markdown-base-transaction-status-6dcf8f14/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from 138-197-15-135.sslip.io](https://www.zero.xyz/host/138-197-15-135.sslip.io/llms.txt)