Read-only data infrastructure
for agent-native treasury allocation.
StableLens grades stablecoins and yield pools on a 17-dimension venue-aware risk model (DeFi + CeFi profiles), exposes the data over a public MCP server, and lets agents pay per call via x402 — no signup, no contract, no minimum spend. We never custody, sign, or execute. The agent owns the decision; we provide the inputs.
Why read-only?
StableLens is read-only by architectural choice. We never custody funds, sign transactions, or execute trades. That separation is the structural reason an agent can wire us into a decision loop without our service surface picking up custodial or fiduciary obligations on the agent operator’s behalf — we’re a data and methodology provider, not a counterparty. As agent-native treasury workflows evolve and any supervisory regime that follows takes shape, the read-only posture is designed to compose with whichever framework emerges — but we do not claim alignment with any specific named regulatory regime today.
Methodology, code, scoring formulae are all public. Every grade is tagged with the model version that produced it. There are no black-box pricing models, no sponsored grades, no undisclosed issuer relationships.
Tools
Eight tools exposed over MCP and as a parallel REST surface. The MCP tools/list response and the OpenAPI 3.1 spec are the canonical references; the table below is a quick survey.
Risk grade + 17-dimension venue-aware breakdown for a yield pool
Filter pools by compliance, chain, custodian, yield, TVL, capacity
Per-jurisdiction compliance status for a stablecoin
Decompose a pool's APY into real-yield, borrower-interest, incentive components
Diff two attestation reports — reserve / audit-firm / methodology changes
Depeg-event history — deviation, recovery, severity, root cause
Decision-support: gas, bridge cost, yield delta, recommendation
Webhook rule fired on every pool snapshot matching criteria (HMAC-signed on Team+)
Auth
Two paths in. Choose API key for sustained volume or x402 for ad-hoc per-call access.
API key
x-api-key header. Provision a key at /pricing on any tier; rate limits gate access. Best for agents running sustained workloads.
x402 micropayment
Unauthenticated request returns HTTP 402 with a payment envelope. Submit a signed transfer authorization, the call proceeds. Settled in USDC on Base. Best for ad-hoc per-call usage with no signup.
Rate limits + pricing
| Tier | Price | API rate limit | Webhooks |
|---|---|---|---|
| Free | $0 | 100 calls / day | — |
| Starter | $29/mo | 1,000 calls / day | — |
| Pro | $79/mo | 10,000 calls / day | Unsigned, ≤10 rules |
| Team | $249/mo | 25,000 calls / day per seat | HMAC-signed, ≤50 rules, replay endpoint |
| Institutional | $1,000+/mo | Unlimited | KMS-signed feed, custom payloads, audit trail |
x402 per-call pricing
- Read-only data tools (6 endpoints)$0.01 per call
- analyze_capital_move$0.05 per call
- register_criteria_rule$0.10 per registration (webhook fires not metered)
x402 settlement on Base in USDC. Receipts logged for billing reconciliation.
Connected agents
Partner integrations will appear here as they ship. Building an AI yield agent or agent-platform that should consume StableLens data? agents@stablelens.com — we’ll prioritise design partners.
Citing StableLens
APA: StableLens. (2026). Risk Methodology v2.0. https://stablelens.com/methodology
BibTeX: @misc{stablelens_v20_2026, title={StableLens Risk Methodology v2.0}, author={StableLens}, year={2026}, url={https://stablelens.com/methodology}}