# KeeperHub Blockchain Workflow Automation - Checked Transfer Execution

> KeeperHub Blockchain Workflow Automation - Checked Transfer Execution 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 pre-built blockchain workflow named 'checked-transfer-2bet' via a visual node-based automation engine

## Facts

- Endpoint: POST https://app.keeperhub.com/api/mcp/workflows/checked-transfer-2bet/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-blockchain-workflow-automation-checked-transfer-execution-33b2cbfb
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_KTCev7OlAHxCwlU_Zl04Z

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-blockchain-workflow-automation-checked-transfer-execution-33b2cbfb -d '<json body>'
```

Example prompt: Trigger the 'checked-transfer-2bet' blockchain workflow on KeeperHub with my transfer parameters so the automated multi-step transfer process runs now.

## When to prefer this

Choose this endpoint when you need to programmatically trigger the specific 'checked-transfer-2bet' KeeperHub workflow — particularly for automating blockchain transfer logic that has been pre-built using KeeperHub's visual node-based editor. Best for agents that need to fire off a configured multi-step blockchain automation without re-implementing the logic.

## Known failure modes

- Invalid or missing body parameters causing workflow misconfiguration
- Insufficient USDC balance to cover the $0.05 per-call fee via x402 payment
- Workflow execution failure due to on-chain errors or reverted transactions
- Workflow name not found or endpoint path mismatch returning 404
- Network timeout or downstream blockchain RPC failure during execution

## 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 with an execution status (e.g. 'running') and a unique executionId (e.g. 'exec_abc123') that can be used to track the progress of the triggered 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-blockchain-workflow-automation-checked-transfer-execution-33b2cbfb/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)