# PulseScanner Transaction Trace

> PulseScanner Transaction Trace is a paid API for AI agents from x402.pulsescanner.io, paid per call via x402, $0.003/call, status unknown (last checked 2026-10-22).

Returns the full call tree (execution trace) of a single PulseChain transaction by its hash

## Facts

- Endpoint: GET https://x402.pulsescanner.io/v2/txs/:hash/trace?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-22
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/pulsescanner-transaction-trace-f5f60082
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_GIOjEb9RTi65gEQ7-laPw

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 pulsescanner-transaction-trace-f5f60082
```

Example prompt: Can you pull the full call tree for PulseChain transaction 0xabc123...def and show me every contract call that happened during its execution?

## When to prefer this

Use this endpoint when you need to understand the internal execution flow of a specific PulseChain transaction — particularly for debugging reverts, auditing smart contract interactions, or reconstructing what a DeFi operation did step by step. Prefer this over the internal-transfers endpoint when you need the full call hierarchy rather than just value movements.

## Known failure modes

- Transaction hash not found — returns 404 if the hash does not exist on PulseChain (chain id 369)
- Invalid hash format — malformed or non-hex hash returns a 400 bad request
- Transaction has no trace data — some very old or simple transfers may lack detailed call traces
- Pagination cursor invalid — stale or malformed cursor returns an error
- Payment failure — insufficient USDC balance or x402 payment not completed returns 402

## How this service works

The call tree of one transaction. PulseChain (chain id 369). $0.003 USDC per call.

## Output

A structured call tree representing the full execution trace of the transaction: each node contains the calling contract address, function signature or method called, input arguments, output values, call type (call, staticcall, delegatecall, etc.), gas used, and success/revert status. The tree is hierarchical, showing nested sub-calls in the order they were executed.

## 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",
      "HEAD",
      "DELETE"
     ],
     "type": "string"
    },
    "headers": {
     "type": "object",
     "additionalProperties": {
      "type": "string"
     }
    },
    "pathParams": {
     "type": "object",
     "required": [
      "hash"
     ],
     "properties": {
      "hash": {
       "type": "string"
      }
     }
    },
    "queryParams": {
     "type": "object",
     "properties": {
      "limit": {
       "type": "string"
      },
      "cursor": {
       "type": "string"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

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