# TraceFast Address Relations

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

Returns the current knowledge-graph relations of an Ethereum address — either as subject (what it points at) or as object (who points at it), covering proxy targets, beacon reads, admin links, delegations, and lending market listings.

## Facts

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

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-address-relations-08256c51
```

Example prompt: Show me all the current on-chain relations for Ethereum address 0xCb859eA579b28e02B87A1FDE08d087ab9dbE5149, specifically what it points at as a subject — proxy implementation, beacon, admin links, anything in the TraceFast knowledge graph.

## When to prefer this

Choose this endpoint when you need to enumerate all current on-chain relations of a specific Ethereum address in either direction — especially for resolving proxy implementations, tracing admin hierarchies, finding delegation targets, or discovering which DeFi markets reference a token. Prefer it over raw RPC calls or block explorers when you need structured, pre-indexed graph edges without writing custom event parsing logic. The subject/object directionality and attributeId filter make it more targeted than a generic counterparty lookup.

## Known failure modes

- Invalid or malformed Ethereum address returns a 400 error
- Unknown address with no recorded relations returns an empty list
- Invalid direction parameter value causes a 400 bad-request error
- Expired or invalid cursor returns a pagination error
- Rate limit or payment failure (x402) blocks the request
- Network or chain indexing lag may mean very recent state changes are not yet reflected

## How this service works

TraceFast knowledge graph: the relations an address holds now — which implementation a proxy points at, which beacon it reads, who administers it, where an account has delegated, which lending market lists a token — as the subject (`direction=subject`: what it points at, default) or as the object (`direction=object`: who points at it). Path: address. Query: direction, attributeId, limit, cursor (see docs). Docs: https://docs.tracefast.xyz/api/address-relations.md

## Output

A paginated list of relation records for the specified Ethereum address, each describing a directed edge in the knowledge graph — including the relation type (e.g. proxy implementation, beacon, admin, delegation, lending market listing), the counterparty address, and supporting attribute IDs. Includes a cursor for fetching subsequent pages.

## 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-address-relations-08256c51/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)