# FiatDock Base Transaction Status

> FiatDock Base Transaction Status is a paid API for AI agents from fiatdock.com, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-10).

Returns the status, block number, confirmations, gas used, and from/to addresses for a transaction hash on the Base network.

## Facts

- Endpoint: GET https://fiatdock.com/v1/chain/tx-status?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-10
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/fiatdock-base-transaction-status-bd5683b9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_YCVgGo3A-owlpjrxtR-GO

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 fiatdock-base-transaction-status-bd5683b9
```

Example prompt: Can you check whether the Base transaction 0xabc123...def456 went through — I need to know the status, how many confirmations it has, and how much gas was used?

## When to prefer this

Use this endpoint when you need to verify the outcome of a specific transaction on the Base L2 network — especially for confirming payment receipt, auditing gas costs, or checking confirmation depth. It is the right choice when you have a specific tx hash and need structured on-chain status data rather than a wallet balance or block-level overview. Prefer it over general blockchain explorers when you need a pay-per-call, agent-friendly API response with no authentication setup.

## Known failure modes

- 404 returned for pending or unknown transaction hash — no charge applied
- Invalid tx hash format may cause request rejection
- Transaction on a different network (not Base) will not be found
- Rate limiting or payment failure if x402 payment header is missing or insufficient

## How this service works

Transaction status on Base — success/failed, block, confirmations, gas, from/to. A pending/unknown tx returns 404 (not charged). Pay-per-call via x402. An empty body is answered for the latest transaction on Base (read live from the chain head); send {"txHash":"0x…"} for any other transaction.

## Output

A JSON object containing: txHash, status (success/failed), network (base), blockNumber, confirmations count, gasUsed, from address, to address, and an asOf timestamp. Returns a 404 (no charge) if the transaction is pending or not found.

## 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": {
      "txHash": {
       "type": "string",
       "description": "A 64-hex transaction hash (0x…) on Base"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "to": "0xRecipient",
  "asOf": "2026-07-30T00:00:00.000Z",
  "from": "0xSender",
  "status": "success",
  "txHash": "0xTX_HASH_64_HEX",
  "gasUsed": "21000",
  "network": "base",
  "blockNumber": 49280000,
  "confirmations": 291
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/fiatdock-base-transaction-status-bd5683b9/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from fiatdock.com](https://www.zero.xyz/host/fiatdock.com/llms.txt)