# KeeperHub Checked Transfer Workflow

> KeeperHub Checked Transfer 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).

Executes a pre-built 'checked-transfer' blockchain workflow automation on KeeperHub's visual node-based platform

## Facts

- Endpoint: POST https://app.keeperhub.com/api/mcp/workflows/checked-transfer-g63s/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-19d0abe7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_qSPZOcZtZ6WZ49i9-PVES

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-19d0abe7 -d '<json body>'
```

Example prompt: Trigger my KeeperHub checked-transfer workflow to execute a validated blockchain transfer — use the default transfer parameters in the body payload and return the execution ID when the run starts.

## When to prefer this

Choose this endpoint when you need to programmatically trigger a specific pre-configured 'checked-transfer' blockchain workflow on KeeperHub without building custom blockchain logic. Prefer it over raw smart contract calls when you want the visual workflow abstraction, conditional checks, and orchestration that KeeperHub provides. Best suited for agents that need to automate recurring or event-driven on-chain transfers within a structured workflow environment.

## Known failure modes

- Invalid or malformed body payload causing workflow to reject the request
- Insufficient USDC balance to cover the $0.05 per-call fee resulting in payment failure
- Workflow ID not found or inaccessible if the workflow has been deleted or renamed
- Timeout if the blockchain network is congested and the workflow cannot initiate
- Authentication or authorization errors if the caller lacks permission to invoke the workflow

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

## 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-19d0abe7/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)