# ForgeMesh Anomaly Tracker — Token Scan

> ForgeMesh Anomaly Tracker — Token Scan is a paid API for AI agents from anomaly.forgemesh.io, paid per call via x402, $0.03/call, status unknown (last checked 2026-09-14).

Detects real-time sequence anomalies in on-chain token activity using mempool scanning and NASA-derived algorithms, returning a sequence score, event story, and peak event window.

## Facts

- Endpoint: POST https://anomaly.forgemesh.io/api/token-scan
- Price: $0.03/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/forgemesh-anomaly-tracker-token-scan-cab2bb8f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_mi4bsTbbw95fac7Rr5U6E

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 forgemesh-anomaly-tracker-token-scan-cab2bb8f -d '<json body>'
```

Example prompt: Check ForgeMesh for any on-chain anomalies on USDT on Ethereum over the past 24 hours — I want to know the sequence score, what kind of event story is showing up, and whether there's anything unusual like whale buys or CEX inflows.

## When to prefer this

Use this endpoint when you need real-time, sequence-aware anomaly detection for a specific token on Ethereum, Base, or Arbitrum — especially when you want a structured score and narrative story rather than raw transfer data. It is best suited for detecting whale movements, CEX inflows, and stablecoin depeg signals within short lookback windows. Prefer this over generic block explorers when you need algorithmic anomaly scoring rather than manual data inspection.

## Known failure modes

- Invalid or unrecognized token symbol returns an error or empty result
- Unsupported chain value (not ethereum, base, or arbitrum) causes rejection
- Invalid window value outside allowed enum causes a 400 error
- Token contract address malformed (not 0x-prefixed hex) may fail validation
- Low on-chain activity in the window may return a sequence_score of 0 with few events_collected
- Payment failure via x402 micropayment blocks the request

## How this service works

Best-effort anomaly scan for a single token; paid output includes source status and coverage notes

## Output

Returns a JSON object with the chain name, token address, a human-readable event story (e.g. 'Distribution Event'), a domain label (e.g. 'financial'), a novelty rating (low/medium/high), an integer sequence anomaly score, an array of events in the peak window (e.g. ['CEX_INFLOW','WHALE_BUY']), and a count of total events collected.

## Example request

```json
{
 "input": {
  "type": "http",
  "method": "POST",
  "queryParams": {
   "chain": "ethereum",
   "token": "usdt",
   "window": "24h"
  }
 }
}
```

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "chain": {
   "type": "string",
   "description": "Blockchain: ethereum, base, or arbitrum"
  },
  "token": {
   "type": "string",
   "description": "Token contract address (0x...) or symbol (usdt, usdc, weth, link, uni, pepe, arb, etc.)"
  },
  "window": {
   "type": "string",
   "description": "Lookback window: 1h, 4h, 24h, or 168h"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "chain": "ethereum",
  "story": "Distribution Event",
  "token": "0xdac17f958d2ee523a2206206994597c13d831ec7",
  "domain": "financial",
  "novelty": "medium",
  "peak_window": [
   "CEX_INFLOW",
   "CEX_INFLOW",
   "WHALE_BUY"
  ],
  "sequence_score": 42,
  "events_collected": 18
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/forgemesh-anomaly-tracker-token-scan-cab2bb8f/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from anomaly.forgemesh.io](https://www.zero.xyz/host/anomaly.forgemesh.io/llms.txt)