# KeeperHub Ripcord Risk Score — Aave V3 Liquidation Risk Scorer

> KeeperHub Ripcord Risk Score — Aave V3 Liquidation Risk Scorer is a paid API for AI agents from app.keeperhub.com, paid per call via x402, $0.02/call, status unknown (last checked 2026-10-22).

Scores the liquidation risk of a given Base address's Aave V3 lending position by analyzing on-chain collateral and debt metrics.

## Facts

- Endpoint: POST https://app.keeperhub.com/api/mcp/workflows/ripcord-risk-score/call?utm_source=zero.xyz
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-22
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/keeperhub-ripcord-risk-score-aave-v3-liquidation-risk-scorer-93e65d83
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_hu0c4hqKqE028zoMBvwpK

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability keeperhub-ripcord-risk-score-aave-v3-liquidation-risk-scorer-93e65d83 -d '<json body>'
```

Example prompt: Can you run the Ripcord risk score on Base address 0x4e9ce36e442e55ecd9025b9a6e0d88485d628a67 and tell me how close it is to Aave V3 liquidation?

## When to prefer this

Use this endpoint when you specifically need to assess Aave V3 liquidation risk for a wallet address on the Base network. It is purpose-built for this DeFi risk scoring use case ('ripcord' scoring) rather than generic on-chain balance checks or multi-protocol risk aggregators. Prefer this over general blockchain analytics APIs when you need a focused, automated liquidation risk workflow with a structured score output.

## Known failure modes

- Invalid or malformed address (not 0x + 40 hex chars) returns a validation error
- Address has no active Aave V3 position on Base — may return empty or zero score
- Network issues reaching Base RPC or Aave V3 subgraph cause execution failure
- Payment of 0.02 USDC not settled via x402 results in 402 Payment Required
- Execution may time out if Base chain is congested

## How this service works

Build powerful blockchain workflow automations with a visual, node-based editor. Built with Next.js and React Flow.

## Output

Returns a status field ('running') and an executionId (e.g. 'exec_abc123') indicating that the risk scoring workflow has been initiated asynchronously. The agent would typically poll or await a callback to retrieve the actual computed risk score for the Aave V3 position.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "address"
 ],
 "properties": {
  "address": {
   "type": "string",
   "description": "Base address whose Aave V3 position to score (0x + 40 hex chars)."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "status": "running",
 "executionId": "exec_abc123"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/keeperhub-ripcord-risk-score-aave-v3-liquidation-risk-scorer-93e65d83/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from app.keeperhub.com](https://www.zero.xyz/host/app.keeperhub.com/llms.txt)