x402basequality 0.45

Stablecoin depeg monitoring via x402-paid POST endpoint on Base and Tron

Price
per_call
Protocol
x402
Verified
no

What it does

This endpoint from Erudite Intelligence LLC provides stablecoin depeg monitoring data. You send a POST request with a token address or symbol and receive depeg-related intelligence for that stablecoin. The endpoint is gated by the x402 protocol (version 2) and accepts payment on two networks: USDC on Base (eip155:8453) at $0.01 per call, and USDT on Tron (tron:728126428) at $0.01 per call. The facilitator is Coinbase CDP's x402 service.

The request body takes a JSON object with a single field "token" — a token contract address or symbol. The response returns a JSON object with a "success" boolean and a "data" object, though the exact structure of the data payload is not documented beyond the placeholder example. The provider, Erudite Intelligence LLC, is a FinCEN-registered MSB operating the EruditePay Bridge, which supports 20 blockchains for x402 payment facilitation.

Documentation is sparse: the bazaar schema in the x402 challenge provides the input/output shape, but no detailed field descriptions or example responses with populated data are available. The /docs path on the origin returns a 404. Users should expect to experiment with known stablecoin addresses (e.g., USDC on Ethereum: 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48) to discover the response format.

Capabilities

stablecoin-depeg-monitoringcrypto-data-intelligencex402-payment-gatedmulti-chain-paymentpost-json-api

Use cases

  • Monitor whether a specific stablecoin is maintaining its peg in real time
  • Build automated alerts for depeg events in DeFi dashboards
  • Integrate depeg risk data into trading bot decision logic
  • Assess stablecoin health before executing large cross-chain transfers

Fit

Best for

  • DeFi developers needing programmatic depeg data
  • Trading bots that need to react to stablecoin instability
  • Risk management systems monitoring stablecoin portfolios

Not for

  • Historical depeg analytics or backtesting (no evidence of historical data support)
  • Non-stablecoin token price monitoring

Quick start

curl -X POST https://bridge.eruditepay.com/v1/cross/stablecoin/depeg-monitor \
  -H "Content-Type: application/json" \
  -H "X-PAYMENT: <x402_payment_header>" \
  -d '{"token": "0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48"}'

Example

Request

{
  "token": "0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48"
}

Response

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

Endpoint

Transporthttp
Protocolx402
Pay to0x6961b88476a9b89C4ed97A4aF4D190754d5e70A1
CurrencyUSD COIN

Quality

0.45/ 1.00

The endpoint is live (402 challenge captured) with a clear input schema and pricing, but the output data structure is entirely opaque — the example shows an empty object. No dedicated docs exist (/docs returns 404), so the actual depeg monitoring fields must be discovered empirically.

Warnings

  • Response data structure is undocumented — the example output contains an empty 'data' object
  • No dedicated API documentation available; /docs returns 404
  • Exact fields returned for depeg monitoring are unknown and must be inferred by calling the endpoint

Citations

Provenance

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

Agent access