# LogicNodes Aptos Transaction Decode

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

Decodes and interprets an Aptos Move function call — including its arguments and type arguments — into a human-readable, structured representation.

## Facts

- Endpoint: POST https://logicnodes.io/paid/v1/tools/aptos_tx_decode?utm_source=zero.xyz
- Price: $0.002/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-decode-2d70b8b6
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_M45QhdbQmCU4GQBktiv-B

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-decode-2d70b8b6 -d '<json body>'
```

Example prompt: Decode this Aptos mainnet Move function call for me — the function is '0x1::coin::transfer', arguments are ['0xabc123', '1000000'], and type arguments are ['0x1::aptos_coin::AptosCoin'] — tell me what it does in plain terms.

## When to prefer this

Choose this endpoint when you need to decode or interpret a raw Aptos Move function call payload — especially when building wallets, audit tools, or agents that need to explain transaction intent before signing. Prefer over generic blockchain explorers when you need a structured, machine-readable decoded result suitable for agent pipelines, rather than a human-facing web page. Best for Aptos mainnet or testnet Move function calls with known function signatures and arguments.

## Known failure modes

- Invalid or malformed function name returns an error response
- Mismatched number of arguments vs function ABI causes decode failure
- Unsupported chain ID (not aptos:1 or aptos:2) returns a chain error
- Type arguments that cannot be resolved on the specified chain return an error
- Payment failure (insufficient USDC) blocks the call with a 402 response

## 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

A JSON object with ok: true and a 'tool' field, plus decoded details of the Aptos Move function call including human-readable function name, interpreted argument values, resolved type arguments, and contextual meaning of the transaction on the specified chain.

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

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

## More

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