# ChainRay MEV Detect

> ChainRay MEV Detect is a paid API for AI agents from chainray.online, paid per call via x402, $0.02/call, status unknown (last checked 2026-09-14).

Detects Miner Extractable Value (MEV) activity in a blockchain transaction by analyzing its transaction hash

## Facts

- Endpoint: GET https://chainray.online/mev-detect/:var1
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/chainray-mev-detect-9e33a84a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_t-ILo_m7Ym54BtaC2GGNA

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 chainray-mev-detect-9e33a84a
```

Example prompt: Can you check if this Ethereum transaction was hit by MEV — sandwich attack, frontrunning, or anything like that? The tx hash is 0xabc123...def456.

## When to prefer this

Use this endpoint when you need to determine whether a specific blockchain transaction was subject to MEV exploitation, such as sandwich attacks, frontrunning, or backrunning. Prefer this over generic block explorers when you need a structured, machine-readable MEV classification rather than raw transaction data. Particularly valuable for DeFi protocols, trading bots, or auditing tools that need to programmatically flag MEV incidents.

## Known failure modes

- Invalid or malformed transaction hash returns an error
- Transaction not found on the specified chain
- Unsupported blockchain network specified in the chain parameter
- Transaction is too recent and not yet confirmed, preventing analysis
- Rate limiting or payment failure returns 402

## How this service works

ChainRay /mev-detect

## Output

Returns an analysis of the specified transaction indicating whether MEV activity was detected, the type of MEV involved (e.g. sandwich attack, frontrunning, backrunning, arbitrage), and relevant on-chain details that support the classification.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "pathParams": {
     "type": "object"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "txHash"
     ],
     "properties": {
      "chain": {
       "type": "string",
       "description": "Blockchain network"
      },
      "txHash": {
       "type": "string",
       "description": "Transaction hash"
      }
     }
    }
   },
   "additionalProperties": false
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/chainray-mev-detect-9e33a84a/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from chainray.online](https://www.zero.xyz/host/chainray.online/llms.txt)