x402basequality 0.45

MEV and sandwich attack probability scoring for DeFi transactions, paid per call via x402 on Base.

Price
per_call
Protocol
x402
Verified
no

What it does

The `/api/mev/risk` endpoint is part of DeFi Shield, a suite of 69 paid API endpoints providing security intelligence for autonomous AI agents. This specific endpoint assesses MEV (Maximal Extractable Value) and sandwich attack probability for DeFi transactions. It accepts POST requests and costs $0.25 per call, settled in USDC on Base via the x402 protocol.

DeFi Shield covers 11 categories including DeFi intelligence, wallet profiling, protocol risk, NFT analysis, cross-chain comparisons, and real-time monitoring. The MEV & Trading category includes seven endpoints for risk assessment, optimal DEX routing, liquidity depth analysis, gas oracles, mempool scanning, price impact estimation, and arbitrage detection. Each endpoint supports free GET-based discovery (returning usage prompts and schema info) and paid POST requests requiring an x402 payment header.

The platform advertises agent-to-agent discovery via `/.well-known/agent-card.json`, a health endpoint at `/api/health` listing all endpoints and pricing, and analytics at `/api/analytics`. Payment settles only on successful response. No OpenAPI schema or detailed request/response documentation was found during crawling — the docs page returns 404 — so the exact input parameters and response format for `/api/mev/risk` must be inferred from context (likely a token address or transaction hash).

Capabilities

mev-risk-scoringsandwich-attack-detectionx402-paymentusdc-on-basedefi-securityper-request-pricingagent-discovery

Use cases

  • Assess MEV exposure before submitting a DeFi swap transaction
  • AI agents autonomously evaluating sandwich attack probability for trade routing decisions
  • Portfolio management bots checking MEV risk as part of pre-trade analysis
  • DeFi dashboards displaying real-time MEV threat levels for pending trades
  • Automated trading systems incorporating MEV risk into execution strategy

Fit

Best for

  • AI agents needing on-demand MEV risk intelligence with micropayments
  • DeFi trading bots evaluating transaction safety before execution
  • Autonomous agents operating on Base that can pay in USDC via x402

Not for

  • Users needing free or subscription-based MEV protection (this is pay-per-call only)
  • Real-time MEV protection/blocking at the transaction level (this provides risk scoring, not active protection)
  • Non-crypto applications with no DeFi context

Quick start

# Free discovery (GET returns schema and usage prompt)
curl https://defi-shield-hazel.vercel.app/api/mev/risk

# Paid request (requires x402 payment header)
curl -X POST https://defi-shield-hazel.vercel.app/api/mev/risk \
  -H "Content-Type: application/json" \
  -H "X-PAYMENT: <x402-payment-token>" \
  -d '{"address": "0x..."}'

Example

Request

{
  "address": "0x1f9840a85d5aF5bf1D1762F925BDADdC4201F984"
}

Endpoint

Transporthttp
Protocolx402
Pay to0x4765092Fe75D2A42C76CEac2Cc249bB2246a527d
CurrencyUSD COIN

Quality

0.45/ 1.00

The endpoint is live (returns 402 on POST as expected for x402), and the landing page provides clear pricing ($0.25/call) and category context. However, no OpenAPI schema, no detailed docs (docs page is 404), no response examples, and the x402 challenge body was empty — so request/response formats are inferred. The example request is a best guess based on the quick-start pattern shown on the homepage.

Warnings

  • No OpenAPI or detailed API documentation available (docs page returns 404)
  • x402 challenge body was empty — no payment parameters (amount, token, network) were captured in the probe
  • Request and response schemas are inferred from homepage examples, not confirmed
  • Example request JSON is a guess based on similar endpoints listed on the site

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-22 02:54:26Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-21
Last seen2026-04-22

Agent access