x402basequality 0.45

Honeypot detection, hidden fees, and blacklist/pause detection for DeFi tokens via x402 on Base.

Price
per_call
Protocol
x402
Verified
no

What it does

The `/api/defi/simulate` endpoint is part of DeFi Shield, a suite of 69 paid API endpoints providing security intelligence to autonomous AI agents. This specific endpoint performs transaction simulation to detect honeypot tokens, hidden fees, and blacklist/pause mechanisms in smart contracts. It costs $0.25 per call, paid in USDC on Base via the x402 protocol.

DeFi Shield exposes endpoints across 11 categories including DeFi intelligence, wallet analysis, MEV/trading, NFT intelligence, cross-chain data, safety/compliance, and more. The `/api/defi/simulate` endpoint sits within the DeFi Intelligence category alongside related tools like contract risk scoring, token intel, and rug-pull scoring. Agents pay per request by including an x402 payment header; payment settles in USDC on Base only upon successful response.

Discovery is supported via `/.well-known/agent-card.json` for A2A discovery and free GET requests to any endpoint path for schema/usage information. The probe confirmed the endpoint is live, returning HTTP 402 on POST as expected for x402 endpoints. However, the 402 challenge body was empty, and no OpenAPI schema or detailed documentation page was found (the `/docs` path returns 404). Request/response schemas must be inferred from the landing page examples.

Capabilities

honeypot-detectionhidden-fee-detectionblacklist-pause-detectiondefi-token-simulationsmart-contract-analysisx402-paymentusdc-base-settlementagent-to-agent-api

Use cases

  • An AI trading agent simulates a token swap before executing to verify the token is not a honeypot
  • An autonomous portfolio manager checks for hidden transfer fees before adding a new token position
  • A DeFi aggregator screens tokens for blacklist or pause functions that could freeze user funds
  • A security bot monitors newly listed tokens and flags those with suspicious simulation results

Fit

Best for

  • AI agents performing pre-trade token safety checks
  • Autonomous DeFi strategies that need honeypot screening
  • Agent workflows requiring pay-per-call security intelligence without API keys

Not for

  • Free or high-volume bulk token scanning (each call costs $0.25)
  • Non-EVM chains or tokens outside the supported network scope
  • Users who need detailed audit reports rather than automated pass/fail signals

Quick start

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

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

Example

Request

{
  "address": "0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48"
}

Endpoint

Transporthttp
Protocolx402
Pay to0x4765092Fe75D2A42C76CEac2Cc249bB2246a527d
CurrencyUSD COIN

Quality

0.45/ 1.00

The endpoint is confirmed live (402 on POST) and the landing page provides clear pricing ($0.25/call) and a high-level description. However, the x402 challenge body was empty, no OpenAPI schema exists, the /docs page 404s, and no example response is available. Request/response structure is inferred, not documented.

Warnings

  • x402 challenge body was empty — no payment parameters (asset, amount, payTo) were returned in the probe
  • No OpenAPI or machine-readable schema found
  • No documentation page available (/docs returns 404)
  • Example request and response schemas are inferred from the landing page, not from actual API documentation
  • Exact supported chains and token address formats are not documented

Citations

Provenance

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

Agent access

Honeypot detection, hidden fees, and blacklist/pause detection for DeFi tokens via x402 on Base. — Clawmart · Clawmart