# Txpost — Transaction Status on Base

> Txpost — Transaction Status on Base is a paid API for AI agents from oraclepost.higgsfield.app, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-18).

Looks up live transaction status on the Base blockchain by hash, returning success/failure, block number, gas used, effective gas price, from, and to addresses.

## Facts

- Endpoint: GET https://oraclepost.higgsfield.app/api/tx
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-18
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/txpost-transaction-status-on-base-77b1617a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_TpCDvjux6yuTUHNxZbf5k

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 txpost-transaction-status-on-base-77b1617a
```

Example prompt: Can you check whether the transaction 0x4a3b2c1d... actually went through on Base — I need to know if it succeeded or failed, which block it landed in, and how much gas it used?

## When to prefer this

Use this endpoint when you need real-time, uncached confirmation of a specific Base transaction — particularly to verify payment receipt, confirm a contract call executed, or audit gas costs. It is preferable over block explorer scraping because it returns structured JSON with no third-party intermediary or cache lag. Choose it over wallet balance endpoints when you need transaction-level detail rather than account-level state.

## Known failure modes

- Invalid or malformed hash (not 66 hex chars) returns an error
- Transaction not yet mined returns not-found or pending state
- Hash for a transaction on a different chain (not Base) will return no result
- Network node unavailability may cause transient failures
- Payment failure (x402) if USDC balance is insufficient

## How this service works

Status of a transaction on Base, read live: success or failure, block number, gas used, effective gas price, from, to. Pass ?hash=0x… (66 hex chars). Useful to confirm a payment or a call landed. No third-party API, no cache.

## Output

Returns a JSON object with the transaction's execution status (success or failure), the block number it was included in, total gas used, effective gas price, sender address (from), and recipient address (to). Data is read live from the Base node with no caching, so it reflects the current canonical chain state.

## 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": {
     "const": "http"
    },
    "method": {
     "const": "GET"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "hash"
     ],
     "properties": {
      "hash": {
       "type": "string",
       "description": "Transaction hash, 0x-prefixed, 64 hex chars"
      }
     }
    }
   }
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {}
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/txpost-transaction-status-on-base-77b1617a/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from oraclepost.higgsfield.app](https://www.zero.xyz/host/oraclepost.higgsfield.app/llms.txt)