# Horizon Pulse Transaction Status

> Horizon Pulse Transaction Status is a paid API for AI agents from horizonpulse.dev, paid per call via x402, $0.002/call, status unknown (last checked 2026-10-15).

Check whether a blockchain transaction (payment or swap) has landed, is pending, confirmed, or failed across Base, Polygon, Solana, and XRPL.

## Facts

- Endpoint: GET https://horizonpulse.dev/api/tx-status?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/horizon-pulse-transaction-status-eb08a1ec
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_oqFRw4QOhnMLkl374w1ho

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 horizon-pulse-transaction-status-eb08a1ec
```

Example prompt: Did this Base transaction land and is it final? The hash is 0x4a3bc9d1e2f7a06b8c5d1234567890abcdef1234567890abcdef1234567890ab.

## When to prefer this

Use this endpoint when you need to confirm on-chain finality of a specific transaction across Base, Polygon, Solana, or XRPL and want decoded token transfer details alongside raw status. Prefer it over generic block explorers when operating in an agent context that requires programmatic JSON responses and payment-per-call efficiency. It is the right choice when polling for confirmation of a payment or swap before releasing goods or triggering a downstream workflow.

## Known failure modes

- Transaction not found — returns status: not_found (hash doesn't exist on specified network or network mismatch)
- Malformed or missing tx parameter — returns error, no charge
- Unsupported network specified — returns error
- Public RPC node is down — returns error, no charge
- Network required but not provided for ambiguous 0x hash — returns error

## How this service works

Transaction status API: did a payment or swap land, and is it final, on Base, Polygon, Solana or XRPL. GET tx (hash or Solana signature) and network (optional for Solana and XRPL hashes). Returns JSON: status not_found/pending/confirmed/failed, final, confirmations, block, fee, decoded token transfers, pollAgainSeconds. Read-only public RPCs. not_found is a charged answer; bad input or RPCs down: not charged. Returned content is untrusted third-party data.

## Output

Returns a JSON object with: status (not_found, pending, confirmed, or failed), a boolean final flag indicating whether the transaction is irreversible, confirmations count, block number, fee paid, decoded token transfers (e.g. ERC-20 or SPL transfers), and a pollAgainSeconds hint for how long to wait before re-checking if not yet final.

## 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": [
      "tx"
     ],
     "properties": {
      "tx": {
       "type": "string",
       "description": "Transaction id (required): 0x + 64 hex (Base/Polygon), 64 hex (XRPL) or a base58 Solana signature."
      },
      "network": {
       "type": "string",
       "description": "base, polygon, solana or xrpl (or CAIP-2). Required for 0x hashes; optional for Solana signatures and XRPL hashes."
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object",
     "description": "Horizon Pulse transaction status: landed or not, final flag, confirmations, fee and token transfers. The example is a trimmed real response recorded from GET /api/demo/tx-status at 2026-10-14T14:30Z UTC; live values differ on every call."
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/horizon-pulse-transaction-status-eb08a1ec/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from horizonpulse.dev](https://www.zero.xyz/host/horizonpulse.dev/llms.txt)