Skip to content

Data Provider: x402-live DeFi risk & analytics routes on Base (depeg-risk, risk-adjusted yields, on-chain pulse) #42

Description

@eltociear

Data Provider: x402-live DeFi risk & analytics routes on Base

ECOSYSTEM.md invites Data Providers — "Monetize your API via x402", so here's a live one that fits BlockRun's financial-data / crypto-intelligence routing category. Everything below is already deployed and payable today — you can hit it before deciding.

What it is — a set of ~80 x402-native DeFi data routes on Base (x402 v2, USDC), served from a single provider. The differentiator is a handful of computed signals a raw DeFiLlama/CEX proxy can't echo, not just pass-through data:

  • /depeg_radar — a 0–100 stablecoin depeg-risk score per USD stablecoin from one call: peg deviation (below-peg discounts weighted over premiums, since a premium is usually yield-bearing by design), 7-day circulating-supply change (redemption pressure), and size (a >$1B coin off-peg raises a systemic flag). Classed OK/WATCH/ELEVATED/DEPEG. Zero-input, $0.005.
  • /safe_yields — risk-adjusted yields: pools ranked by yield per unit of risk, each top pool's underlying token run through an on-chain rug/safety scan.
  • /onchain_pulse — one-call digest: biggest protocol TVL shifts (with $ amounts) joined to a recent-exploit overlay.
  • plus raw analytics: /yields /tvl /liquidations /funding /stablecoins /fear_greed /protocols /derivatives and ~70 more.

Test it right now (no key needed to see the challenge):

  • OpenAPI (all routes): https://eltociear-tokenguard.hf.space/openapi.json
  • Free counts-only health of the paid routes: https://eltociear-tokenguard.hf.space/selftest
  • Any paid route answers a valid x402 402 challenge, e.g. POST https://eltociear-tokenguard.hf.space/depeg_radar with {}.

Terms: most routes are zero-input and priced $0.005 (a few aggregated ones $0.05), USDC on Base, settle to 0x5bCDA55247B238a573A968B234F788a2D35664Dd. Facilitator-agnostic x402 v2.

Ask: what's the path to get these routed on the BlockRun gateway as a Data Provider — is it a directory PR here, or backend onboarding on your side? Happy to adapt the response shape / pricing to whatever the gateway expects.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions