x402basequality 0.78

Detect early token buyers, bot activity, and sniper wallets for any token via x402 micropayment.

Price
0.85 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint from Einstein AI analyzes early token purchase patterns to identify bot activity and sniper wallets. It accepts a token contract address and optional chain parameter (supporting Base, Ethereum, BSC, Arbitrum, Polygon, Optimism, and Solana), then returns raw data about the earliest buyers of a token — useful for detecting automated sniping bots that front-run liquidity additions or token launches. The "/raw" variant returns structured data without AI-generated analysis text.

Payment is handled via the x402 protocol with three settlement options: USDC on Base ($0.85 per call), USDC on Solana ($0.85), or Bitcoin Lightning (1,113 sats, ~$0.85 equivalent). No API keys are required; callers include a signed payment authorization in the X-PAYMENT header. The endpoint is part of a larger suite of 20+ blockchain intelligence endpoints offered by Einstein AI, powered by Bitquery on-chain data. Other endpoints in the suite cover market data, whale tracking, launchpad monitoring (Pump.fun, Zora), MEV detection, rug pull scanning, and arbitrage discovery, priced between $0.25 and $1.15 per request.

The endpoint is live and returns a proper x402 payment challenge (HTTP 402) with an outputSchema describing the expected POST body (chain, tokenAddress, limit) and response shape (status, result, payment). Results are returned as JSON with a 90-second maximum timeout on Base.

Capabilities

token-sniping-detectionbot-detectionearly-buyer-analysismulti-chainx402-micropaymentraw-data-outputon-chain-analyticssniper-identificationusdc-base-paymentusdc-solana-paymentlightning-payment

Use cases

  • Analyze the first buyers of a newly launched token to determine if bots sniped the liquidity event
  • Identify sniper wallets that repeatedly front-run token launches across chains
  • Assess token safety by checking whether early purchase patterns indicate coordinated bot activity
  • Feed raw sniping data into a trading agent's risk model before entering a position
  • Audit a token's launch fairness by examining the timing and size of initial buys

Fit

Best for

  • AI trading agents that need automated bot-detection data before buying tokens
  • Security researchers auditing token launch fairness
  • DeFi protocols screening tokens for listing based on launch integrity
  • Whale-tracking bots that flag suspicious early accumulation patterns

Not for

  • Historical price charting or OHLCV data (use the sibling /tokenchart or /ohlcv endpoints)
  • General-purpose AI chat or natural language queries (use /einstein/report instead)
  • Users who need free or API-key-based access without crypto payments

Quick start

curl -X POST https://emc2ai.io/x402/bitquery/token-sniping/raw \
  -H "Content-Type: application/json" \
  -H "X-PAYMENT: <base64-signed-usdc-authorization>" \
  -d '{"tokenAddress": "0xYourTokenAddress", "chain": "base", "limit": "10"}'

Example

Request

{
  "chain": "base",
  "limit": "10",
  "tokenAddress": "0x0b3e328455c4059EEb9e3f84b5543F74E24e7E1b"
}

Response

{
  "result": {
    "chain": "base",
    "token": "0x0b3e328455c4059EEb9e3f84b5543F74E24e7E1b",
    "earlyBuyers": [
      {
        "isBot": true,
        "wallet": "0xabc...123",
        "amountUsd": 5200.5,
        "blockOffset": 0,
        "buyTimestamp": "2025-01-15T00:00:12Z"
      }
    ]
  },
  "status": "completed",
  "payment": {
    "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
    "amount": "850000",
    "scheme": "exact",
    "txHash": "0xdef...789",
    "network": "base",
    "x402Version": 1
  }
}

Endpoint

Transporthttp
Protocolx402
Pay to0xc9368b30BD620164FD1a05a5d99dcaf8Ae754775
CurrencyUSD COIN

Quality

0.78/ 1.00

The endpoint is live with a well-structured x402 challenge, full OpenAPI spec with input/output schemas, clear pricing, and multi-chain support. The response schema for the specific /token-sniping/raw endpoint is only partially documented (generic BitqueryResponse), and no actual response example was captured, so the example_response_json is inferred. The /api route returned a 522 timeout error, but the x402 endpoint itself responded correctly.

Warnings

  • The /api route returned a Cloudflare 522 timeout error during crawl, suggesting intermittent origin server issues.
  • The example_response_json is inferred from the outputSchema and generic BitqueryResponse schema — actual response fields may differ.
  • The OpenAPI spec lists the similar endpoint as /x402/bitquery/tokensniping (no hyphen), while this listing is for /x402/bitquery/token-sniping/raw — the /raw variant may have slightly different behavior not fully documented.

Citations

Provenance

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

Agent access