# TraceFast Address Attribute History

> TraceFast Address Attribute 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 complete chronological history of all attribute intervals an Ethereum address has held, including when it became a contract, when code was removed, and when it first held state.

## Facts

- Endpoint: GET https://mpp.tracefast.xyz/api/v1/chains/1/entities/:address/attributes/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-attribute-history-73153621
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Ai7J-yzmVpXMsEhir8cg0

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-attribute-history-73153621
```

Example prompt: Show me the full attribute history for Ethereum address 0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2 — I want to know every attribute interval it has held, like when it became a contract or first held state, oldest events first, up to 200 results.

## When to prefer this

Use this endpoint when you need the full chronological lifecycle of an Ethereum address's attributes — specifically to understand when it transitioned between states (e.g., became a contract, had code removed, first held storage). Prefer this over live contract endpoints when historical context matters, or over single-attribute proof endpoints when you need the complete timeline rather than evidence for one specific attribute.

## Known failure modes

- Invalid or malformed address (not 0x-prefixed or not 40 hex chars) returns a 400 error
- Address with no recorded attribute history returns an empty list
- Limit parameter outside 1–500 range returns a validation error
- Payment not provided or insufficient USDC balance triggers 402 Payment Required
- Chain ID not supported returns a 404 or unsupported chain error
- Rate limiting may return 429 if too many requests are made

## How this service works

TraceFast knowledge graph: every attribute interval an address has held, oldest first — when it became a contract, when its code was removed, when it first held state. Path address: The address, `0x`-prefixed, 40 hex characters, any case. Query limit: 1..=500, default 100. Docs: https://docs.tracefast.xyz/api/address-attribute-history.md

## Output

An ordered list of attribute intervals (oldest first) for the specified Ethereum address, each describing a specific attribute the address held (e.g. 'is_contract', 'has_code', 'has_state'), along with the block or timestamp range during which that attribute was active. Supports pagination via the limit parameter (1–500, default 100).

## 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-attribute-history-73153621/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)