# TraceFast Ethereum Address Blacklist Status

> TraceFast Ethereum Address Blacklist Status 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 a summary of every on-chain blacklist event recorded against an Ethereum address across all issuer contracts, including current listing status, authority tier weights, event timestamps, transition counts, and enforcement actions (freezes/destructions).

## Facts

- Endpoint: GET https://mpp.tracefast.xyz/api/v1/chains/1/risk/blacklists/:address?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-ethereum-address-blacklist-status-b1725c01
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_nvgNA0KQJqaOGl48plxwC

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-blacklist-status-b1725c01
```

Example prompt: Can you check TraceFast and tell me the full blacklist history for the Ethereum address 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045 — which issuers have ever listed it, their authority tiers, and whether any enforced against it with a freeze or fund destruction?

## When to prefer this

Use this endpoint when you need a comprehensive, deduplicated blacklist summary per issuer for an Ethereum address, including historical listing status and enforcement severity — ideal for compliance screening, risk scoring, and counterparty due diligence. Prefer this over the raw blacklist events endpoint (which returns individual events) when you want pre-aggregated issuer-level statistics including transition counts and authority tiers.

## Known failure modes

- Invalid or malformed Ethereum address (not 0x-prefixed or wrong length) returns an error
- Address with no blacklist history returns an empty result set
- Network or RPC latency may cause slow responses for complex address histories
- Payment failure or insufficient USDC balance prevents the x402-gated response
- Chain ID 1 only — requests for other chains will not return data

## How this service works

TraceFast risk data: is this Ethereum address on a token issuer's on-chain blacklist? One row per issuer contract that ever listed it (USDC, USDT, any token with a blacklist) — listed now or not, the issuer's weight (`authorityTier`), first and latest events — plus the issuers that froze or destroyed its funds. Read from the issuers' own contracts, not from sanctions lists. Path address: `0x`-prefixed. Docs: https://docs.tracefast.xyz/api/risk-blacklist-status.md

## Output

Returns one row per issuer contract that has ever blacklisted the queried address, including the issuer's authorityTier weight, whether the address is currently listed, timestamps of the first and most recent blacklist events, the number of listing/delisting transitions, and a separate set of facts about issuers that have taken enforcement actions (frozen funds or destroyed them).

## 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-blacklist-status-b1725c01/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)
