Detect volume anomalies for Base tokens via x402-paid crypto intelligence endpoint.
What it does
The volume-anomaly endpoint at bridge.eruditepay.com provides crypto data intelligence focused on detecting trading volume anomalies for tokens on the Base blockchain. It accepts a POST request with a JSON body containing a token address (or symbol) and returns anomaly data. The endpoint is gated by the x402 payment protocol (v2), requiring per-call payment of $0.01 (10,000 base units of USDC on Base, 6 decimals) or the equivalent in USDT on Tron.
The endpoint is operated by Erudite Intelligence LLC, a FinCEN-registered MSB. Payment settlement is facilitated through the EruditePay x402 Bridge, which supports 20 blockchains. The x402 challenge confirms two accepted payment rails: USDC on Base (eip155:8453) via the Coinbase CDP facilitator, and Tether USD on Tron (tron:728126428).
Documentation is sparse — the Bazaar schema embedded in the x402 challenge provides the input/output structure, but no detailed field descriptions for the response beyond a generic `{"success": true, "data": {}}` example. There is no OpenAPI spec, and the docs.eruditepay.com link referenced on the landing page was not crawled. The actual contents of the `data` object in the response are unknown.
Capabilities
Use cases
- —Detect unusual trading volume spikes for tokens on Base to flag potential pump-and-dump activity
- —Monitor token volume patterns as part of an automated trading or risk management pipeline
- —Integrate volume anomaly signals into a crypto research dashboard
- —Agent-driven portfolio surveillance that pays per query via x402
Fit
Best for
- —Crypto trading bots needing real-time volume anomaly signals
- —On-chain analysts monitoring Base ecosystem tokens
- —AI agents with x402-compatible wallets seeking pay-per-call crypto intelligence
Not for
- —Users needing volume anomaly detection on chains other than Base (endpoint is Base-specific)
- —Anyone requiring detailed historical volume data or full order-book analytics (response schema is opaque)
- —Free-tier or API-key-based access — this is strictly pay-per-call via x402
Quick start
curl -X POST https://bridge.eruditepay.com/v1/base/token/volume-anomaly \
-H "Content-Type: application/json" \
-H "X-PAYMENT: <x402_payment_header>" \
-d '{"token": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913"}'Example
Request
{
"token": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913"
}Response
{
"data": {},
"success": true
}Endpoint
Quality
The endpoint is live (402 challenge captured) with a clear payment schema and input format, but the response payload is entirely opaque — the example shows an empty data object. No OpenAPI spec or detailed docs were available. The actual analytical output is unknown, limiting usefulness for agents evaluating this endpoint.
Warnings
- —Response schema is opaque: the only example shows {"success": true, "data": {}} with no field descriptions
- —No OpenAPI specification available
- —docs.eruditepay.com was referenced but not crawled; /docs on the bridge returns 404
- —The endpoint description is generic ('Crypto data intelligence') and does not detail what volume anomaly metrics are returned
- —Token input field description says 'Token address or symbol' but it is unclear which tokens or symbols are supported
Citations
- —Endpoint returns x402 v2 challenge with USDC on Base (10000 base units = $0.01) and USDT on Tron as accepted payment methodshttps://bridge.eruditepay.com/v1/base/token/volume-anomaly
- —Operated by Erudite Intelligence LLC, FinCEN MSB registered (BSA ID 31000324258137)https://bridge.eruditepay.com
- —EruditePay Bridge supports 20 blockchains for x402 payment facilitationhttps://bridge.eruditepay.com
- —Input schema accepts a POST with JSON body containing a 'token' field (address or symbol)https://bridge.eruditepay.com/v1/base/token/volume-anomaly