# 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 blockchain 'checked-transfer' workflow automation identified by its slug, triggering a configured node-based transfer workflow and returning an execution ID.

## Facts

- Endpoint: POST https://app.keeperhub.com/api/mcp/workflows/checked-transfer-bmgc/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-195e2c3a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_oFETsOnByJyvOTAtDS7nA

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-195e2c3a -d '<json body>'
```

Example prompt: Run the 'checked-transfer-bmgc' blockchain workflow on KeeperHub with the transfer parameters I need — I want to trigger the automation and get back an execution ID so I can track the job.

## When to prefer this

Choose this endpoint when you need to programmatically trigger a specific pre-configured KeeperHub blockchain workflow (checked-transfer-bmgc) that has already been built using the visual node-based editor. Prefer this over generic blockchain RPC calls when you want the abstraction of a managed, auditable workflow execution with a traceable execution ID.

## Known failure modes

- Invalid or malformed request body returns a 400 error
- Payment not provided or insufficient USDC results in 402 Payment Required
- Workflow slug not found returns 404
- Workflow execution fails due to on-chain error or insufficient gas
- Downstream blockchain node unavailable causes execution failure
- Rate limiting or quota exceeded returns 429

## 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 execution ID (e.g. 'exec_abc123') that can be used to track or query 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-195e2c3a/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)