# EMC2 AI FrontrunWatch

> EMC2 AI FrontrunWatch is a paid API for AI agents from emc2ai.io, paid per call via x402, $1/call, status unknown (last checked 2026-09-15).

Detects MEV activity including sandwich attacks, toxic order flow, and front-running patterns on DEX transactions.

## Facts

- Endpoint: POST https://emc2ai.io/x402/bitquery/frontrunwatch/raw
- Price: $1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/emc2ai-io-0c73ce8a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_PL0J6rRDdtjIkqwnp7r7v

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 emc2ai-io-0c73ce8a -d '<json body>'
```

Example prompt: Check if there have been any sandwich attacks or MEV front-running targeting the token 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48 on Ethereum — I want to see recent toxic flow and attacker wallets.

## When to prefer this

Use this endpoint when you need to detect or investigate sandwich attacks, front-running, or toxic MEV flow around specific tokens, wallets, or transactions on DEXes. Prefer this over generic blockchain explorers when you specifically need structured MEV classification and attacker identification rather than raw transaction data.

## Known failure modes

- Invalid token or wallet address returns empty result set
- Unsupported chain returns error or no data
- Payment failure (insufficient USDC) blocks the request with 402
- Rate limiting if called too frequently
- Missing required parameters returns 400 bad request
- No MEV activity in the queried timeframe returns empty array

## How this service works

Frontrun monitoring: sandwich attacks, toxic flow, and MEV activity detection.

## Output

Returns raw MEV activity data including detected sandwich attack events, front-running transactions, toxic flow classification, attacker wallet addresses, affected transactions, and associated profit/loss metrics for the queried token or wallet.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "chain": {
   "enum": [
    "base",
    "ethereum",
    "bsc",
    "arbitrum",
    "polygon",
    "optimism",
    "solana"
   ],
   "type": "string",
   "description": "Blockchain to query (e.g., base, ethereum, bsc, solana)"
  },
  "limit": {
   "type": "string",
   "description": "Maximum number of results to return (default: 10, max: 500)"
  },
  "timeperiod": {
   "enum": [
    "1h",
    "4h",
    "24h",
    "7d",
    "30d"
   ],
   "type": "string",
   "description": "Time period for analysis (e.g., 1h, 24h, 7d, 30d)"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/emc2ai-io-0c73ce8a/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from emc2ai.io](https://www.zero.xyz/host/emc2ai.io/llms.txt)
