# TraceFast Ethereum Address Lookup

> TraceFast Ethereum Address Lookup is a paid API for AI agents from mpp.tracefast.xyz, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-12).

Returns live Ethereum address metadata: account type, code presence, native ETH balance, nonce, first/last activity timestamps, and direct-transaction counters for a given address.

## Facts

- Endpoint: GET https://mpp.tracefast.xyz/api/v1/chains/1/entities/:address?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/tracefast-ethereum-address-lookup-5a6e3fa6
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ztFmvA7f6_tPhghqlUSl-

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-ethereum-address-lookup-5a6e3fa6
```

Example prompt: Look up the current on-chain state of Ethereum address 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045 — I want to know its ETH balance, nonce, whether it holds contract code, and when it was first and last active on Ethereum mainnet.

## When to prefer this

Choose this endpoint when you need a comprehensive, real-time snapshot of a single Ethereum address's on-chain state — particularly when you need multiple fields at once (balance, nonce, code presence, activity timestamps, and transaction counters) rather than querying each separately. It is ideal for due-diligence checks before sending funds, classifying addresses as contracts vs. EOAs, or auditing account history. Prefer it over block-explorer scraping when you need structured, machine-readable data with a predictable schema.

## Known failure modes

- Invalid address format (not 0x-prefixed or not 40 hex chars) returns a 4xx error
- Address that has never appeared on-chain may return minimal or empty fields
- Network or node unavailability causes 5xx errors
- Payment failure (x402) if USDC payment is not properly attached to the request
- Rate limiting if too many requests are made in a short window

## How this service works

TraceFast live Ethereum data: one address as the chain sees it now — how it exists (an account whose state was touched, or an address only ever mentioned by other operations), whether it holds code, its native balance and nonce, when it was first mentioned and last active in any form, and its direct-transaction counters. Path address: The address, `0x`-prefixed, 40 hex characters, any case. Docs: https://docs.tracefast.xyz/api/address.md

## Output

Returns a JSON object describing the Ethereum address as it exists on-chain right now: its account type (state-touched account vs. mention-only address), whether it holds bytecode (contract vs. EOA), its native ETH balance in wei, current nonce, the block/timestamp of its first on-chain mention, the block/timestamp of its most recent activity in any form, and counters for direct transactions sent and received.

## 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-ethereum-address-lookup-5a6e3fa6/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)