Borrower health-factor lookup by EVM addressGET /v1/health/:address · x402 API by liquita-x402-edge
Borrower health-factor lookup by EVM address. Returns current health factor, collateral, debt, and protocol across all monitored lending markets.
What does this x402 API do?
Borrower health-factor lookup by EVM address. This is an x402-gated GET API resource from liquita-x402-edge. TOLL·402 did not invoke this route automatically because doing so was not considered safe. The listing records $0.001 USD-denominated per request on Base. No settled paid call has been verified.
- Published price
- $0.001 USD-denominated per request
- Networks
- Base
- Latest evidence
- TOLL·402 did not invoke this route automatically because doing so was not considered safe
- Resource ID
- c35c3d24aa732c2b7a279d36
Start with a quote-only recipe. Payment signing stays in your project.
const response = await fetch("https://liquita-x402-edge.liquita.workers.dev/v1/health/:address", {
method: "GET",
});
console.log(response.status);
console.log(Object.fromEntries(response.headers));
console.log((await response.text()).slice(0, 1000));
// A valid 402 is a quote, not a completed paid call.This sends no payment. Inspect the 402 response before adding a wallet-enabled client.
- Exact route checked
not safely testable · unresolved-url-template
- Origin reachable
HEAD https://liquita-x402-edge.liquita.workers.dev/ returned 200.
- Observed in cdp-bazaar
The registry record was observed and retained with provenance.
- Observed in 402-index
Discovered through bazaar.
- Registry record checked
Registry health: healthy.
What evidence supports this listing?
Each record has an exact-route quote outcome. Unresolved templates and potentially mutating methods are labeled instead of being invoked without provider-specific test input. A quote is still separate from a settled paid call. Read the discovery and verification methodology →
Which networks and payment options does it accept?
The normalized listing price is $0.001 USD-denominated per request. Raw protocol requirements remain visible below for implementation and audit use.