# KeeperHub Sentinel Vault Protection Workflow

> KeeperHub Sentinel Vault Protection 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).

Triggers a sentinel vault protection workflow on a specified blockchain vault address, returning calldata for a token transfer or protection action

## Facts

- Endpoint: POST https://app.keeperhub.com/api/mcp/workflows/sentinel-vault-protection/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-sentinel-vault-protection-workflow-027d1279
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_04yuR_rlnkBjC3zyFRDPC

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-sentinel-vault-protection-workflow-027d1279 -d '<json body>'
```

Example prompt: Activate the sentinel vault protection workflow on vault address 0xAbC123...def456 — the reason is 'suspicious activity detected on mainnet'.

## When to prefer this

Choose this endpoint when you need to programmatically trigger a predefined sentinel vault protection automation on KeeperHub for a specific blockchain vault address. It is best suited for automated security pipelines, keeper bots, or agent workflows that need to generate on-chain calldata for vault protection without manually constructing smart contract calls. Prefer this over generic blockchain transaction builders when you have a vault already registered on KeeperHub and want to invoke its associated sentinel workflow.

## Known failure modes

- Missing or invalid vaultAddress — request will fail with a validation error
- Vault address not recognized or not registered in KeeperHub — workflow may return empty or error response
- Payment failure — x402 payment of 0.05 USDC must succeed before the workflow is triggered
- Network or RPC error causing calldata generation to fail
- Workflow misconfiguration on the KeeperHub platform resulting in malformed calldata

## How this service works

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

## Output

Returns EVM-compatible calldata including the target contract address (to), the encoded function call data (data, starting with ERC-20 transfer selector 0xa9059cbb), the transaction type ('calldata'), and the ETH value to send (value). This calldata can be submitted to a blockchain node or wallet to execute the protection action on-chain.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "vaultAddress"
 ],
 "properties": {
  "reason": {
   "type": "string"
  },
  "vaultAddress": {
   "type": "string"
  }
 }
}
```

## 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-sentinel-vault-protection-workflow-027d1279/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)