# EMC2 AI MEV Detection

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

Detects MEV (Maximal Extractable Value) attacks and sandwich trades on major EVM chains using on-chain transaction analysis.

## Facts

- Endpoint: POST https://emc2ai.io/x402/bitquery/mevdetection
- Price: $0.6/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/emc2-ai-75c0ec71
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_gP8H8lPUsKzSDYByEbgQp

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 emc2-ai-75c0ec71 -d '<json body>'
```

Example prompt: Show me recent MEV and sandwich attacks on Arbitrum from the last 24 hours — I want to see which bots are front-running trades and how many transactions were affected.

## When to prefer this

Use this endpoint when you need on-chain MEV and sandwich attack detection specifically powered by Bitquery data, covering Ethereum, Base, BSC, Arbitrum, and Polygon. Prefer it over generic blockchain explorers when you need structured MEV event data with attacker/victim attribution.

## Known failure modes

- Unsupported chain name returns error or empty result
- Very short time periods may return no events
- Rate limits or payment failures return 402 or 429 status
- Network congestion may cause slow response for high-activity chains

## How this service works

Detect MEV (Maximal Extractable Value) attacks and sandwich trades. Supported chains: ethereum, base, bsc, arbitrum, polygon. Default chain: ethereum. Required params: none (chain/limit/timeperiod are optional and defaulted).

## Output

Returns a list of detected MEV events including sandwich attacks and toxic flow transactions, with details on attacker addresses, victim transactions, affected tokens, and profit extracted — filtered by the requested chain and time period.

## 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)"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "result": {},
 "status": "completed",
 "analysis": {}
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/emc2-ai-75c0ec71/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)