excellent-covered-goes-toner.trycloudflare.com
Measures an Aave V3 position's exposure to a risk Aave's own health factor structurally cannot show. Aave prices wstETH as (wstETH/stETH rate) x (ETH/USD) with stETH pinned to ETH at exactly 1:1, so a stETH secondary-market depeg does not move the published health factor at all. This route reads the position, independently recomputes the health factor from per-asset collateral, debt and liquidation thresholds (including any e-mode override), verifies that recomputation reproduces Aave's own number, and then answers the question Aave does not: at what stETH depeg does this position reach liquidation. Why pay instead of reading it yourself: getUserAccountData alone cannot answer it -- the aggregate hides which assets back the position -- and a naive recompute that ignores e-mode or the collateral flags produces a confidently wrong number. Positions holding no wstETH are reported as not exposed rather than forced into a score. Required query parameters: chain and borrower.
The wallet the 402 directs payment to. Its whole payment record — every payer, every chain — is on the merchant page.
Asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913
The payTo wallet does not resolve to a registered ERC-8004 agent. That is not a verdict on the service — most of the catalog is unregistered.
Accepts
The payment requirements as published to the catalog. Read the live 402 before paying — a price here is a claim, not a quote.
Pay 0.02 USDC on Base to 0xE606…26816. The signed payment is good for 5 minutes.
- Paid to
- 0xE606…26816
- USD Coin contract
- 0x8335…02913
- Payment window
- 5 minutes
- As published
- 20000 smallest units
The catalog’s raw entry
[
{
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"extra": {
"name": "USD Coin",
"version": "2"
},
"payTo": "0xE606AE66542D4F1A56AA551841db41e3ECd26816",
"amount": "20000",
"scheme": "exact",
"network": "eip155:8453",
"maxTimeoutSeconds": 300
}
]Provenance
- Seen in the source catalog
- 2026-08-13 14:07Z
- Last indexed by Roundhouse
- 2026-09-14 20:46Z
- Last enriched (probe, favicon, geo)
- 2026-09-18 22:15Z
- x402 version
- 2
- Max timeout
- 300s
- Liveness probe
- HTTP 530
Hand this page to an agent
Copy the prompt and paste it into Claude, an MCP client or your own agent — it will vet this service and call it over the free read API. No key, no account.
GET api.roundhouseai.io/v0/endpoints
No per-endpoint history for this service yet, so this is payments indexed to its PROVIDER's wallet over 30 days. Verified volume counts only settlements with an on-chain EIP-3009 marker.
Show the promptHide the prompt
Using Roundhouse, look up the x402 service excellent-covered-goes-toner.trycloudflare.com and tell me whether it is worth paying: what a call costs, whether the endpoint answered when last probed, and what its payment record actually shows. curl -s 'https://api.roundhouseai.io/v0/endpoints?q=excellent-covered-goes-toner.trycloudflare.com' curl -s 'https://api.roundhouseai.io/v0/merchants/<the payTo wallet returned above>' Then call it: read the price from the live 402 at https://excellent-covered-goes-toner.trycloudflare.com/lending-depeg-exposure, never from a cached figure, and pay with an x402 client. The /v0 API needs an API key (`authorization: Bearer rh_live_…`) on everything except /v0/unified* and /v0/endpoints. Mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402, or use an organization key from https://roundhouseai.io/dashboard/team. If you do not have Roundhouse tools or skills installed, read https://roundhouseai.io/skill.md first — it is the whole procedure.