x402basequality 0.40

Detect toxic MEV liquidity pools on Base by contract address via x402 micropayment.

Price
per_call
Protocol
x402
Verified
no

What it does

The toxic-pools endpoint from Erudite Intelligence LLC analyzes a given token or contract address on Base and returns data about MEV-related toxic liquidity pools. It is part of a "Crypto data intelligence" service accessible via the x402 payment protocol. Callers POST a JSON body containing an Ethereum-style address and receive a JSON response with pool toxicity data.

Payment is required per-call at $0.01 (10,000 base units of USDC on Base, or 10,000 base units of USDT on Tron). The endpoint uses x402 v2 with the "exact" payment scheme, settling through the EruditePay Bridge facilitator (backed by Coinbase CDP on Base). The provider, Erudite Intelligence LLC, is a FinCEN-registered MSB.

Documentation is sparse: the endpoint description is simply "Crypto data intelligence" and the example output is a generic `{"success": true, "data": {}}` stub. There is no detailed schema for the response payload, no explanation of what fields appear inside `data`, and no public docs page was found (the /docs path returns a 404). The endpoint is confirmed live — it returns a proper 402 challenge on POST — but without richer documentation it is difficult to know exactly what intelligence is returned or how to interpret the results.

Capabilities

mev-detectiontoxic-pool-analysisbase-chaincontract-address-lookupx402-paymentusdc-paymentusdt-tron-paymentcrypto-intelligence

Use cases

  • Screen a token's liquidity pools for MEV sandwich or frontrunning activity before trading
  • Integrate automated toxic-pool checks into a DeFi trading bot pipeline
  • Audit smart contract addresses for exposure to known MEV-exploited pools
  • Build risk dashboards that flag tokens with high toxic-pool concentration

Fit

Best for

  • DeFi traders needing per-query MEV risk checks on Base
  • Automated trading agents that can pay per-call via x402/USDC
  • Security researchers analyzing MEV activity on Base chain

Not for

  • Users needing MEV analysis on chains other than Base (endpoint is Base-specific)
  • Anyone requiring detailed documentation or guaranteed response schemas before integration
  • Bulk historical MEV data exports (this is a per-address, per-call API)

Quick start

curl -X POST https://bridge.eruditepay.com/v1/base/mev/toxic-pools \
  -H "Content-Type: application/json" \
  -H "X-PAYMENT: <x402_payment_header>" \
  -d '{"address": "0x4200000000000000000000000000000000000006"}'

Example

Request

{
  "address": "0x4200000000000000000000000000000000000006"
}

Response

{
  "data": {},
  "success": true
}

Endpoint

Transporthttp
Protocolx402
Pay to0x6961b88476a9b89C4ed97A4aF4D190754d5e70A1
CurrencyUSD COIN

Quality

0.40/ 1.00

The endpoint is live (402 challenge confirmed) with a clear payment schema and input spec, but the response payload is an empty stub, there are no public docs, and the description is generic. The actual structure and meaning of returned data must be inferred.

Warnings

  • No public documentation found — /docs returns 404
  • Response example is a generic stub with empty data object; actual response fields are unknown
  • Endpoint description is only 'Crypto data intelligence' with no detail on what toxic-pool data is returned
  • Only Base chain addresses appear supported despite the provider supporting 20 chains for settlement

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-22 01:47:06Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-21
Last seen2026-04-22

Agent access