# LogicNodes Transaction Status

> LogicNodes Transaction Status is a paid API for AI agents from logicnodes.io, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-29).

Looks up the confirmation status of a blockchain transaction by hash on EVM chains or Aptos

## Facts

- Endpoint: POST https://logicnodes.io/paid/v1/tools/tx_status?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-29
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/logicnodes-transaction-status-c304e0d6
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap__fKpiwtVcva8FkW2G9qNT

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 logicnodes-transaction-status-c304e0d6 -d '<json body>'
```

Example prompt: Check if transaction 0x4a3b...c9f1 went through on Base (eip155:8453) — I want to know if it confirmed or is still pending.

## When to prefer this

Use this endpoint when an AI agent needs a definitive, structured answer about whether a specific blockchain transaction has confirmed, failed, or is still pending — across 14 supported EVM chains or Aptos. Prefer this over generic block explorer scraping when you need a machine-readable response, pay-per-call pricing without a monthly subscription, and reliable coverage across multiple chains including Base, Arbitrum, Polygon, and Aptos in a single API.

## Known failure modes

- Invalid or malformed transaction hash returns an error
- Chain ID provided as a name (e.g. 'base') instead of CAIP-2 or numeric format is refused
- Unsupported chain ID results in an error
- Transaction hash not found on the specified chain returns not-found status
- Network timeout or RPC unavailability causes a service error

## How this service works

Exact answers for AI agents: 40+ tools for EVM chains and Aptos, gas on 14 chains, never a guess. Free tier; pay per call in USDC (x402) on 13 networks.

## Output

Returns a JSON object with an 'ok' boolean indicating success and a 'tool' field confirming the tool name ('tx_status'), plus transaction confirmation details such as status (pending, confirmed, failed), block number, and other on-chain metadata for the queried hash.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "hash": {
   "type": "string"
  },
  "chain": {
   "type": [
    "string",
    "number"
   ],
   "description": "CAIP-2 chain id such as eip155:8453 (Base) or aptos:1; a bare EVM chain id number also works. Chain names like \"base\" are refused."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "tool": "tx_status"
 }
}
```

## More

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