# OceanAlt TRON Address Transaction Trace

> OceanAlt TRON Address Transaction Trace is a paid API for AI agents from oceanalt.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-23).

Traces a TRON address up to 3 hops upstream to detect whether its transaction path touches any listed (sanctioned or high-risk) address

## Facts

- Endpoint: GET https://oceanalt.com/api/x402/trace?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-23
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/oceanalt-tron-address-transaction-trace-3dcc0ac5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ijOKaEqZBX94k-eyzi_qh

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 oceanalt-tron-address-transaction-trace-3dcc0ac5
```

Example prompt: Before I pay this TRON address TLa2f6VPqDgRE67v1736s7bJ8Ray5wYjU7, can you trace it on OceanAlt to check whether its upstream transaction path touches any sanctioned or high-risk addresses within 3 hops?

## When to prefer this

Use this endpoint when you need to trace TRON-specific blockchain transaction paths for compliance or fraud detection, especially when an AI agent is about to make a payment to a TRON address and you need to verify it doesn't connect to sanctioned or high-risk parties within 3 hops. Prefer this over simple address screening when you need path-level graph traversal rather than just a direct address check. Complement with OceanAlt's direct decision or batch screening endpoints for broader coverage.

## Known failure modes

- Missing or malformed TRON address (must start with T) returns an error or empty result
- Address with no transaction history may return found=false with an empty path array
- Network or RPC issues on the TRON side may cause incomplete hop traversal
- Payment failure (insufficient USDC balance) blocks the call before execution
- Addresses with very deep or complex graphs may not traverse fully within the 3-hop limit

## How this service works

AML fund tracing: follow funds upstream over multiple hops to see whether they touched sanctioned, hacked or scam sources.

## Output

Returns a JSON object with: 'found' (boolean indicating if a listed address was reached), 'path' (array of address objects representing the traced route), 'hops' (integer up to 3 for how many hops were followed), 'hit' (the listed address reached, if any, or null), 'chain' (always 'tron'), and 'start' (the original traced address).

## 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": {
     "type": "string",
     "const": "GET"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "addr"
     ],
     "properties": {
      "addr": {
       "type": "string",
       "description": "TRON address to trace (T…)"
      }
     }
    }
   }
  },
  "output": {
   "type": "object",
   "properties": {
    "type": {
     "type": "string",
     "const": "json"
    },
    "example": {
     "type": "object",
     "required": [
      "found",
      "path"
     ],
     "properties": {
      "hit": {
       "type": [
        "object",
        "null"
       ],
       "description": "The listed address that was reached, if any"
      },
      "hops": {
       "type": "integer",
       "description": "Hops followed (up to 3)"
      },
      "path": {
       "type": "array",
       "items": {
        "type": "object"
       }
      },
      "chain": {
       "type": "string",
       "description": "Always tron"
      },
      "found": {
       "type": "boolean",
       "description": "Whether the main upstream path touched a listed address"
      },
      "start": {
       "type": "string",
       "description": "Traced address"
      }
     }
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "hit": null,
  "hops": 3,
  "path": [],
  "chain": "tron",
  "found": false,
  "start": "TLa2f6VPqDgRE67v1736s7bJ8Ray5wYjU7"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/oceanalt-tron-address-transaction-trace-3dcc0ac5/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from oceanalt.com](https://www.zero.xyz/host/oceanalt.com/llms.txt)