x402basequality 0.45

Monitor newly deployed smart contracts on Base via x402-paid API call.

Price
per_call
Protocol
x402
Verified
no

What it does

This endpoint from Erudite Intelligence LLC returns data about newly deployed smart contracts on a specified blockchain (e.g., Base). It is accessed via HTTP POST with a JSON body specifying the chain to monitor. The endpoint is live and returns an x402 v2 payment challenge, accepting USDC on Base (eip155:8453) or USDT on Tron (tron:728126428) at a cost of $0.01 per call (10,000 base units with 6 decimals).

The response schema indicates a JSON object with a `success` boolean and a `data` object, though the exact structure of the returned contract data is not documented beyond the example stub `{"success": true, "data": {}}`. The endpoint is described as "Crypto data intelligence" in the x402 challenge. The provider, EruditePay, operates an x402 payment facilitator bridge supporting 20 blockchains and is registered as a FinCEN MSB (BSA ID 31000324258137).

Documentation is sparse — the provider's /docs, /api, and /README paths all return 404-style errors. The input schema accepts a `chain` string parameter describing the blockchain network to monitor, with "base" shown as the example value. No detailed field-level documentation exists for the response payload, so consumers should expect to explore the response structure empirically.

Capabilities

new-contract-monitoringblockchain-database-chainsmart-contract-detectioncrypto-intelligencex402-paymentmulti-chain-payment

Use cases

  • Detect newly deployed smart contracts on Base for security analysis or rug-pull detection
  • Feed a trading bot with real-time new contract data for early token discovery
  • Monitor Base for new DeFi protocol deployments
  • Audit tooling that tracks contract creation activity on-chain

Fit

Best for

  • Crypto analysts tracking new contract deployments on Base
  • Trading bots needing early signals on new token launches
  • Security researchers monitoring for suspicious contract activity

Not for

  • Querying historical contract data (endpoint name implies monitoring new contracts only)
  • Non-blockchain use cases
  • Users who need detailed ABI or source-code analysis of contracts

Quick start

curl -X POST https://bridge.eruditepay.com/v1/base/monitor/new-contracts \
  -H "Content-Type: application/json" \
  -H "X-PAYMENT: <x402_payment_header>" \
  -d '{"chain": "base"}'

Example

Request

{
  "chain": "base"
}

Response

{
  "data": {},
  "success": true
}

Endpoint

Transporthttp
Protocolx402
Pay to0x24c5da6267AEbEBfCBf7B325753C5B2538A5B09B
CurrencyUSD COIN

Quality

0.45/ 1.00

The endpoint is live (402 challenge captured) with a clear input schema and pricing, but the response payload is entirely undocumented beyond a stub example with an empty data object. No dedicated docs exist (/docs returns 404). The actual content of the 'data' field is unknown.

Warnings

  • Response data structure is undocumented — the example shows an empty object
  • Provider documentation pages (/docs, /api, /README) all return endpoint_not_found errors
  • The exact fields returned in the 'data' object are unknown; consumers must discover them empirically

Citations

Provenance

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

Agent access