# KeeperHub Exit Guard Exit Workflow

> KeeperHub Exit Guard Exit Workflow is a paid API for AI agents from app.keeperhub.com, paid per call via x402, $0.05/call, status unknown (last checked 2026-10-22).

Generates calldata to exit a liquidity position by swapping an ERC-20 token with a minimum output guard, via KeeperHub's blockchain workflow automation platform

## Facts

- Endpoint: POST https://app.keeperhub.com/api/mcp/workflows/exit-guard-exit/call?utm_source=zero.xyz
- Price: $0.05/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-exit-workflow-c7ed422c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_X7xTJbvzxzMLz6PrS0VDK

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-exit-workflow-c7ed422c -d '<json body>'
```

Example prompt: Generate the exit calldata for my liquidity position — owner is 0xAbC123...def, token is 0xToken456...789, fee is 30 bps, pool fee tier is 3000, I'm putting in 1000000000000000000 (1 ETH worth), and I need a minimum output of 950000000.

## When to prefer this

Use this endpoint when you need to programmatically generate exit calldata for a DeFi liquidity position with built-in slippage protection (minimum output guard) on a specific pool fee tier. It is ideal for automated stop-loss triggers, portfolio rebalancing workflows, or any agent-driven DeFi exit automation built on the KeeperHub platform. Prefer this over manually encoding swap calldata when you want a structured, fee-aware exit path with guaranteed minimum output enforcement.

## Known failure modes

- Missing required fields (owner, token, feeBps, poolFee, amountIn, amountOutMinimum) returns a 400 validation error
- Invalid Ethereum address format for owner or token fields causes rejection
- amountOutMinimum set too high may cause on-chain transaction revert when submitted
- Pool fee tier not matching a supported tier (e.g. 100, 500, 3000, 10000) may result in incorrect calldata
- Payment of 0.05 USDC via x402 protocol required; insufficient payment returns 402 error

## 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 calldata object containing the encoded transaction data (data field as hex), the target contract address (to field), the transaction type ('calldata'), and the ETH value to send (value field, typically '0' for ERC-20 swaps). This calldata can be submitted directly to an Ethereum-compatible blockchain to execute the guarded exit swap.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "owner",
  "token",
  "feeBps",
  "poolFee",
  "amountIn",
  "amountOutMinimum"
 ],
 "properties": {
  "owner": {
   "type": "string",
   "description": "Position owner"
  },
  "token": {
   "type": "string",
   "description": "ERC-20"
  },
  "feeBps": {
   "type": "string",
   "description": "Fee bps"
  },
  "poolFee": {
   "type": "string",
   "description": "Fee tier"
  },
  "amountIn": {
   "type": "string",
   "description": "Amount in"
  },
  "amountOutMinimum": {
   "type": "string",
   "description": "Min out"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "to": "0x0000000000000000000000000000000000000000",
 "data": "0xa9059cbb",
 "type": "calldata",
 "value": "0"
}
```

## More

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