# KeeperHub Exit Guard Enrollment Check

> KeeperHub Exit Guard Enrollment Check 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).

Checks whether a given wallet address is enrolled in the Exit Guard blockchain workflow automation

## Facts

- Endpoint: POST https://app.keeperhub.com/api/mcp/workflows/exit-guard-check-enrolled/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-exit-guard-enrollment-check-d1b708e0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_5sBR6imHCXvnQKm3DnpTR

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-exit-guard-enrollment-check-d1b708e0 -d '<json body>'
```

Example prompt: Can you check if the wallet 0xAbC123...def456 is enrolled in the KeeperHub Exit Guard workflow?

## When to prefer this

Use this endpoint when you need to programmatically verify whether a specific wallet address is enrolled in KeeperHub's Exit Guard workflow automation, particularly in pre-transaction checks, onboarding flows, or compliance audits involving blockchain wallet protection. Prefer this over generic on-chain lookups when you want a structured, workflow-level enrollment status rather than raw contract state.

## Known failure modes

- Invalid or malformed wallet address returns a validation error
- Non-existent or unenrolled wallet may return a not-found or empty enrollment status
- Payment failure (insufficient USDC balance) results in HTTP 402 before execution begins
- Network or service downtime may cause timeouts with no executionId returned
- Wallet address not matching expected format (e.g. non-checksummed) may cause lookup failure

## 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 JSON object containing a workflow execution status (e.g. 'running') and an executionId (e.g. 'exec_abc123') that can be used to track the async result of the enrollment check.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "owner"
 ],
 "properties": {
  "owner": {
   "type": "string",
   "description": "Wallet address to check"
  }
 }
}
```

## Response schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/keeperhub-exit-guard-enrollment-check-d1b708e0/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)
