Query recent MEV attacks on Base by token/contract address, paid per-call via x402 in USDC or USDT.
What it does
This x402-gated endpoint from Erudite Intelligence LLC returns data on recent MEV (Maximal Extractable Value) attacks on the Base blockchain. Callers POST a JSON body containing a token or contract address and receive structured intelligence about MEV activity targeting that address. The endpoint is described as "Crypto data intelligence" in its x402 challenge.
Payment is required per call at a cost of $0.01 (10,000 base units of a 6-decimal stablecoin). Two payment options are accepted: USDC on Base (network eip155:8453, settled via the Coinbase CDP x402 facilitator) or USDT on Tron (network tron:728126428). The x402 v2 protocol is used, with a maximum payment timeout of 300 seconds.
Documentation is sparse — the endpoint's output schema only shows a generic `{"success": true, "data": {}}` example, so the exact structure of the returned MEV attack data is not documented. The provider (Erudite Intelligence LLC) also operates the EruditePay x402 Bridge facilitator, which handles payment verification and settlement across 20 blockchains. No dedicated docs page for this MEV intelligence endpoint was found.
Capabilities
Use cases
- —Check whether a specific token or contract on Base has been targeted by recent MEV attacks
- —Monitor DeFi protocols for sandwich attacks and other MEV exploitation
- —Integrate MEV risk data into trading bots or portfolio dashboards
- —Audit smart contracts for MEV vulnerability exposure
- —Feed MEV intelligence into on-chain security alerting pipelines
Fit
Best for
- —DeFi developers monitoring MEV exposure on Base
- —Security researchers analyzing MEV bot activity
- —Trading agents that need real-time MEV risk signals
Not for
- —Historical MEV analysis across non-Base chains (only Base is indicated in the URL path)
- —Free or high-volume bulk data retrieval (each call costs $0.01)
- —Users without crypto wallets to pay via x402
Quick start
curl -X POST https://bridge.eruditepay.com/v1/base/mev/recent-attacks \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402_payment_header>" \
-d '{"address": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913"}'Example
Request
{
"address": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913"
}Response
{
"data": {},
"success": true
}Endpoint
Quality
The endpoint is live (402 challenge captured) with a clear input schema (POST with an address field) and pricing ($0.01 per call in USDC or USDT). However, the output schema is essentially a stub ({"data": {}}), there are no dedicated docs, and the actual structure of MEV attack data returned is unknown. This limits practical usability without trial-and-error.
Warnings
- —Output data structure is undocumented — the example only shows an empty object
- —No dedicated API documentation found (docs, api, pricing, README paths all return 404)
- —The exact fields and format of MEV attack data must be discovered empirically
- —Only a generic 'Crypto data intelligence' description is provided by the endpoint itself
Citations
- —Endpoint returns x402 v2 challenge with price of 10000 base units USDC on Base or USDT on Tronhttps://bridge.eruditepay.com/v1/base/mev/recent-attacks
- —Provider is Erudite Intelligence LLC, operating the EruditePay x402 Bridge facilitatorhttps://bridge.eruditepay.com
- —USDC on Base uses asset address 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 with 6 decimalshttps://bridge.eruditepay.com
- —The facilitator URL for Base payments is https://api.cdp.coinbase.com/platform/v2/x402https://bridge.eruditepay.com/v1/base/mev/recent-attacks
- —Input schema requires a POST with JSON body containing an 'address' field described as 'Token or contract address to analyze'https://bridge.eruditepay.com/v1/base/mev/recent-attacks