# KeeperHub Nexus Guardian Health Factor Reader

> KeeperHub Nexus Guardian Health Factor Reader is a paid API for AI agents from app.keeperhub.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-22).

Reads the Aave V3 health factor for a given EVM wallet address on Base Sepolia testnet

## Facts

- Endpoint: POST https://app.keeperhub.com/api/mcp/workflows/nexus-guardian-hf-read/call?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-22
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/keeperhub-nexus-guardian-health-factor-reader-fb2f50c9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_rxlVfswvukx9ZQ2xHGJVv

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-nexus-guardian-health-factor-reader-fb2f50c9 -d '<json body>'
```

Example prompt: Can you check the Aave V3 health factor for wallet address 0xAbCd1234... on Base Sepolia so I know if it's at risk of liquidation?

## When to prefer this

Choose this endpoint when you need to programmatically read the Aave V3 health factor for a specific EVM wallet on the Base Sepolia testnet, especially in automated DeFi risk monitoring workflows or liquidation alert pipelines. It is best suited for agents that need on-chain lending health data without building their own RPC infrastructure. Prefer it over generic blockchain RPC calls when you want a simple, pay-per-call abstraction over Aave V3 data on Base Sepolia.

## Known failure modes

- Invalid or malformed EVM wallet address returns an error
- Wallet address has no Aave V3 position on Base Sepolia — may return null or zero health factor
- Base Sepolia RPC downtime may cause execution failure
- Payment of 0.01 USDC not received — request rejected by x402 payment gate
- Execution ID returned but underlying workflow times out before returning health factor

## 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 workflow execution status ('running') and an execution ID (e.g. 'exec_abc123') that can be used to poll for the completed Aave V3 health factor result for the queried wallet address.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "walletAddress"
 ],
 "properties": {
  "walletAddress": {
   "type": "string",
   "description": "EVM address to read Aave V3 health factor for on Base Sepolia"
  }
 }
}
```

## Response schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/keeperhub-nexus-guardian-health-factor-reader-fb2f50c9/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)