# TraceFast Address Relation History

> TraceFast Address Relation History 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 full ordered history of knowledge-graph relation intervals an Ethereum address has held, either as subject or object, oldest first

## Facts

- Endpoint: GET https://mpp.tracefast.xyz/api/v1/chains/1/entities/:address/relations/history?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-relation-history-c9a52289
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_qJtEgK0k4fUXF8KTuLnMP

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-relation-history-c9a52289
```

Example prompt: Pull the full relation history for Ethereum address 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045 from TraceFast's knowledge graph — I want to see every interval where it was the subject, up to 200 results.

## When to prefer this

Choose this endpoint when you need the complete temporal history of knowledge-graph edges for a specific Ethereum address — especially when you care about directionality (who the address pointed at vs. who pointed at it) and interval ordering. Prefer this over live transaction endpoints when you need graph-layer semantic relationships rather than raw transaction data, and over attribute history endpoints when you want relational edges rather than scalar property changes.

## Known failure modes

- Invalid or malformed address (not 40 hex chars, missing 0x prefix) returns a 400 error
- Direction value other than 'subject' or 'object' returns a validation error
- Limit outside 1–500 range returns a validation error
- Address with no recorded relation history returns an empty result set
- Payment failure or insufficient USDC balance returns a 402 error
- Rate limiting or upstream node unavailability returns a 503 error

## How this service works

TraceFast knowledge graph: every relation interval an address has held, oldest first — as the subject (`direction=subject`: what it pointed at, default) or as the object (`direction=object`: who pointed at it). Path address: The address, `0x`-prefixed, 40 hex characters, any case. Query direction: `subject` (default) or `object`; limit: 1..=500, default 100. Docs: https://docs.tracefast.xyz/api/address-relation-history.md

## Output

An ordered list of relation intervals (oldest first) for the specified address, each describing a graph edge the address held as subject or object — including what it pointed at or who pointed at it, along with the interval's start and end block/timestamp metadata.

## 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-relation-history-c9a52289/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)