# LogicNodes Aptos Transaction Status

> LogicNodes Aptos 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-28).

Looks up the status of an Aptos blockchain transaction by its hash on mainnet or testnet

## Facts

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

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-aptos-transaction-status-97f0e9e7 -d '<json body>'
```

Example prompt: Can you check whether my Aptos mainnet transaction with hash 0xabc123... went through successfully?

## When to prefer this

Use this endpoint when you need a deterministic, exact answer about an Aptos transaction's status and want to avoid guesswork. Prefer it over general-purpose blockchain explorers when building automated agent workflows that need reliable machine-readable responses with pay-per-call pricing via USDC.

## Known failure modes

- Invalid or malformed transaction hash returns an error
- Unknown chain CAIP-2 ID causes a bad-request error
- Transaction not yet indexed may return pending or not-found status
- Network connectivity issues to Aptos node may cause timeouts
- Payment failure via x402 prevents the call from executing

## 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 and the tool name, along with transaction status details indicating whether the given Aptos transaction hash was confirmed, pending, or failed on the specified chain.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "hash": {
   "type": "string"
  },
  "chain": {
   "type": "string",
   "description": "Aptos CAIP-2 id: aptos:1 (mainnet, default) or aptos:2 (testnet)"
  }
 }
}
```

## Response schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/logicnodes-aptos-transaction-status-97f0e9e7/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)