# TraceFast Internal Transfers by Address

> TraceFast Internal Transfers by Address is a paid API for AI agents from mpp.tracefast.xyz, paid per call via x402, $0.1/call, status unknown (last checked 2026-10-19).

Returns paginated internal call frames (value-carrying subcalls) sent or received by an Ethereum address, ordered newest first with call tree position, depth, call type, value moved, and outcome.

## Facts

- Endpoint: GET https://mpp.tracefast.xyz/api/v1/chains/1/entities/:address/internal-transfers?utm_source=zero.xyz
- Price: $0.1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-19
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/tracefast-internal-transfers-by-address-97462817
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_JaOgVLFegPyKeUq5Dc9fR

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 tracefast-internal-transfers-by-address-97462817
```

Example prompt: Pull the 50 most recent internal ETH transfers for 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045 on Ethereum mainnet, going backward in time.

## When to prefer this

Use this endpoint when you specifically need internal call frame data — ETH value movements through subcalls within transactions — for a given Ethereum address. This is distinct from top-level transaction history and is ideal for auditing DeFi protocol flows, investigating contract behavior, or tracing ETH moving through complex call stacks. Prefer this over general transaction endpoints when the value you care about is transferred internally (not as a top-level tx value).

## Known failure modes

- Invalid address format (not 0x-prefixed or not 40 hex chars) returns 400 error
- Address with no internal transfer history returns empty result set
- Block range parameters out of order or referencing future blocks may return error or empty results
- Invalid cursor value returns pagination error
- Rate limit or payment failure returns 402 or 429 error
- Requesting more than the maximum allowed limit per page returns validation error

## How this service works

TraceFast live Ethereum data: the value-carrying call frames an address sent or received inside transactions, newest first — each with its position in the call tree, its depth, the kind of call, the value it moved and its own outcome. Path address: The address, `0x`-prefixed, 40 hex characters, any case. Query: limit, cursor, direction, fromBlock, toBlock (see docs). Docs: https://docs.tracefast.xyz/api/entity-internal-transfers.md

## Output

A paginated list of internal call frames where the given address was caller or callee, each including its position in the call tree, depth level, call type (e.g. CALL, DELEGATECALL), ETH value moved, and the outcome of that call. Results are ordered newest first and include a cursor for fetching the next page.

## Request schema (JSON Schema)

```json
{
 "properties": {
  "input": {
   "required": [
    "method"
   ],
   "properties": {
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "pathParams": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/tracefast-internal-transfers-by-address-97462817/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from mpp.tracefast.xyz](https://www.zero.xyz/host/mpp.tracefast.xyz/llms.txt)