x402basequality 0.85

Query latest deployed tokens with liquidity pool data and AI analysis across multiple chains via x402 micropayment.

Price
0.4 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint returns the most recently deployed tokens on-chain along with their associated liquidity pool data, augmented with AI-generated analysis. It is part of the Einstein AI x402 API suite, which uses Bitquery as its underlying blockchain data source. The endpoint supports multiple chains including Base, Ethereum, BSC, Arbitrum, Polygon, Optimism, and Solana, with Base as the default. Optional parameters let you specify the chain and result limit (up to 500, default 50).

Payment is handled via the x402 protocol at $0.40 per request. Three payment rails are accepted: USDC on Base (to 0xc9368b...4775), USDC on Solana, and Bitcoin Lightning (524 sats). No API keys are required — authentication is purely payment-based via the X-PAYMENT header containing a signed authorization. The response includes raw query data, an AI-powered analysis section with insights, and a payment receipt with on-chain transaction hash.

The endpoint is part of a broader suite of 20+ x402-enabled endpoints from Einstein AI covering market data, whale intelligence, launchpad monitoring (Pump.fun, Zora), security audits (rug pull detection, MEV detection), DeFi arbitrage scanning, and comprehensive investment reports. Prices across the suite range from $0.25 to $1.15 per call. The provider also offers holdings-based discounts up to 60% for E=MC2 token holders and free access for users who supply their own Bitquery/OpenAI/Moralis API keys.

Capabilities

latest-token-pairsliquidity-pool-datamulti-chain-queryai-analysisx402-micropaymentbitquery-database-chainethereum-chainbsc-chainsolana-chainarbitrum-chainpolygon-chainlightning-payment

Use cases

  • Discovering newly deployed tokens with liquidity across multiple EVM chains and Solana
  • Monitoring new DEX pair creation for trading bots or alert systems
  • Feeding an AI agent with fresh token launch data for automated analysis
  • Building dashboards that track new token deployments in real time
  • Screening new tokens for liquidity before trading

Fit

Best for

  • AI agents needing pay-per-call blockchain data without API key management
  • Traders monitoring new token launches across multiple chains
  • Automated systems that need structured new-pair data with AI insights

Not for

  • Historical token data lookups spanning months or years (use OHLCV or chart endpoints instead)
  • Free-tier or high-frequency polling use cases where $0.40/call adds up quickly
  • Non-crypto applications with no need for on-chain token data

Quick start

curl -X POST https://emc2ai.io/x402/bitquery/latest-pairs \
  -H "Content-Type: application/json" \
  -H "X-PAYMENT: <base64-signed-USDC-authorization>" \
  -d '{"chain": "base", "limit": 10}'

Example

Request

{
  "chain": "base",
  "limit": 10
}

Response

{
  "data": {
    "pairs": [
      {
        "dex": "Uniswap V3",
        "symbol": "EXT",
        "createdAt": "2025-01-15T12:34:56Z",
        "tokenName": "ExampleToken",
        "poolAddress": "0xdef...456",
        "liquidityUsd": 52340.5,
        "tokenAddress": "0xabc...123"
      }
    ]
  },
  "status": "completed",
  "payment": {
    "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
    "amount": "400000",
    "scheme": "exact",
    "txHash": "0x789...abc",
    "network": "base",
    "x402Version": 1
  },
  "analysis": {
    "summary": "10 new pairs detected on Base in the last 24h. 3 show significant initial liquidity above $50k.",
    "insights": [
      "High concentration of Uniswap V3 deployments",
      "Average initial liquidity: $28,400"
    ]
  }
}

Endpoint

Transporthttp
Protocolx402
Pay to0xc9368b30BD620164FD1a05a5d99dcaf8Ae754775
CurrencyUSD COIN

Quality

0.85/ 1.00

Full OpenAPI 3.0.3 schema with detailed request/response models, live 402 challenge confirming three payment rails, and comprehensive documentation page. Response body schema is generic (BitqueryResponse) rather than endpoint-specific, and the example response is inferred since no actual paid response was captured.

Warnings

  • The /api route returned a 522 (host timeout) during crawl, suggesting occasional backend instability
  • Response data schema is generic — actual field names in the 'data' object are not formally documented per-endpoint
  • Example response JSON is inferred from the generic BitqueryResponse schema, not from an actual API call

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-22 00:52:55Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-21
Last seen2026-04-22

Agent access