x402basequality 0.78

Raw Virtuals Protocol bonding-curve and agent-token pool data on Base, paid per call via x402 USDC.

Price
0.4 USDC / call
Protocol
x402
Verified
no

What it does

This endpoint returns raw on-chain data for Virtuals Protocol agent tokens and their bonding-curve liquidity pools on Base chain. It is part of the Einstein AI x402 API suite, which wraps Bitquery blockchain data behind pay-per-request x402 micropayments. The "/raw" variant returns structured JSON data without AI-generated analysis, making it suitable for programmatic consumption by agents and bots.

The endpoint accepts optional parameters: limit (1–500, default 50), timeperiod (1h/4h/12h/24h/7d, default 24h), sortBy (volumeUsd/swaps/priceChange, default volumeUsd), and minVolumeUsd (default 100). Payment is $0.40 per request in USDC on Base (0x8335…2913), USDC on Solana, or 524 sats via Lightning Network. No API keys are required; authentication is handled entirely through the x402 X-PAYMENT header containing a signed USDC TransferWithAuthorization payload.

The parent API offers over 20 endpoints covering market data, whale intelligence, launchpad tracking (Pump.fun, Zora), security audits (rug-pull scanning, MEV detection), arbitrage scanning, and an AI agent endpoint — all priced between $0.25 and $1.15 per call. The service is live and returns a well-formed 402 challenge with outputSchema metadata for agent discovery.

Capabilities

virtuals-protocol-poolsbonding-curve-database-chainraw-json-outputx402-micropaymentusdc-paymentsolana-paymentlightning-paymentconfigurable-timeperiodconfigurable-sortvolume-filtermulti-payment-network

Use cases

  • Monitoring Virtuals Protocol agent-token liquidity pools for trading signals
  • Building automated trading bots that track bonding-curve activity on Base
  • Screening new Virtuals Protocol tokens by volume, swap count, or price change
  • Feeding raw pool data into downstream analytics or portfolio dashboards
  • Agent-to-agent commerce where an AI agent purchases on-chain data programmatically

Fit

Best for

  • AI agents needing structured Virtuals Protocol pool data without AI commentary
  • Developers building Base-chain DeFi dashboards or alert systems
  • Traders tracking bonding-curve token activity sorted by volume or price change

Not for

  • Users who need AI-interpreted analysis (use the non-raw /virtual-pools endpoint instead)
  • Querying chains other than Base for Virtuals Protocol data
  • Free or API-key-based access without on-chain payment capability

Quick start

curl -X POST https://emc2ai.io/x402/bitquery/virtual-pools/raw \
  -H "Content-Type: application/json" \
  -H "X-PAYMENT: <base64-signed-usdc-authorization>" \
  -d '{"limit": 10, "timeperiod": "24h", "sortBy": "volumeUsd", "minVolumeUsd": 100}'

Example

Request

{
  "limit": 10,
  "sortBy": "volumeUsd",
  "timeperiod": "24h",
  "minVolumeUsd": 100
}

Response

{
  "result": {
    "pools": [
      {
        "swaps": 312,
        "liquidity": 180000,
        "tokenName": "ExampleAgent",
        "volumeUsd": 54200.5,
        "priceChange": 12.5,
        "tokenAddress": "0xabc...123"
      }
    ]
  },
  "status": "completed",
  "payment": {
    "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
    "amount": "400000",
    "scheme": "exact",
    "txHash": "0xdef...456",
    "network": "base",
    "x402Version": 1
  }
}

Endpoint

Transporthttp
Protocolx402
Pay to0xc9368b30BD620164FD1a05a5d99dcaf8Ae754775
CurrencyUSD COIN

Quality

0.78/ 1.00

Full OpenAPI schema with detailed request/response models, live 402 challenge with outputSchema, and multi-network payment options. Docked slightly because the response schema for the raw variant is generic (no concrete field-level output schema for pool data), and the example response is inferred from the outputSchema description rather than a real captured response.

Warnings

  • The /api path returned a 522 (host timeout) during crawl, indicating intermittent origin server issues.
  • Response payload fields for the raw endpoint are inferred from the generic BitqueryResponse schema; actual field names in the 'result' object are not documented.
  • This endpoint is Base-only for Virtuals Protocol data; other chains are not supported for this specific query.

Citations

Provenance

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

Agent access