Detect a bridge transfer in a fund flow

1Trace the fund flow

Run a multi-hop fund-flow trace from the source. This is C4-metered — the heaviest primitive — because it walks paths across several hops.

curl "https://api.1st-node.com/v1/intel/eth/0x9a..f2/flow?dir=out&hops=3" \
  -H "Authorization: Bearer sk_live_..."

2Spot the bridge terminal

Inspect each path's terminal entity. A category of bridge means the funds left the chain there. The label carries a confidence you should record.

> { "paths": [ { "hops": [
>   "0x9a..f2", "0x28..a1", "0x77..bd" ],
>   "terminal_entity": "Stargate",
>   "category": "bridge", "confidence": 0.87,
>   "value_usd": 150000 } ] }

3Confirm the bridge label

Call labels on the terminal address to confirm the bridge attribution independently before you treat the path as a cross-chain exit.

curl https://api.1st-node.com/v1/intel/eth/0x77..bd/labels \
  -H "Authorization: Bearer sk_live_..."

4Resume on the destination chain

Record the bridge hop, then continue the investigation with a fresh trace on the destination chain (for example tron) so the flow stays connected across the gap.