# KeeperHub Checked Transfer Workflow Executor

> KeeperHub Checked Transfer Workflow Executor 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 and executes a specific pre-built blockchain workflow called 'checked-transfer-6hea' on the KeeperHub visual automation platform

## Facts

- Endpoint: POST https://app.keeperhub.com/api/mcp/workflows/checked-transfer-6hea/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-checked-transfer-workflow-executor-5bcadfce
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_CGaZcraNeAl4Ide3y326r

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-checked-transfer-workflow-executor-5bcadfce -d '<json body>'
```

Example prompt: Run the checked-transfer workflow on KeeperHub with the parameters I have for this blockchain transfer — I need it to kick off immediately and give me back the execution ID so I can track it.

## When to prefer this

Choose this endpoint when you need to programmatically trigger the specific KeeperHub 'checked-transfer-6hea' workflow, especially for automating blockchain transfers that require pre-configured node-based logic. Prefer this over generic blockchain RPC calls when the transfer logic is already encoded in the KeeperHub visual editor and you simply need to invoke it with runtime parameters.

## Known failure modes

- Invalid or missing body parameters causing workflow to reject the call
- Payment of 0.05 USDC not fulfilled, resulting in 402 Payment Required
- Workflow 'checked-transfer-6hea' not found or deactivated, returning 404
- Blockchain node or downstream dependency unavailable, causing execution timeout
- Malformed input object schema causing a 400 Bad Request

## 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 the execution status (e.g. 'running') and a unique executionId (e.g. 'exec_abc123') that can be used to track or reference the workflow run.

## Request schema (JSON Schema)

```json
{
 "properties": {
  "input": {
   "properties": {
    "body": {
     "type": "object"
    }
   }
  },
  "output": {
   "properties": {
    "example": {
     "status": "running",
     "executionId": "exec_abc123"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/keeperhub-checked-transfer-workflow-executor-5bcadfce/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)