# KeeperHub Probe Trigger Binding Call

> KeeperHub Probe Trigger Binding Call 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 blockchain workflow automation by probing a binding between a contract address and an owner address, initiating an execution run.

## Facts

- Endpoint: POST https://app.keeperhub.com/api/mcp/workflows/probe-trigger-binding/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-probe-trigger-binding-call-b298f7cf
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_wT3LdKI2wg_rgf-Z8Ouve

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-probe-trigger-binding-call-b298f7cf -d '<json body>'
```

Example prompt: Trigger a KeeperHub blockchain workflow automation by probing the binding for contract address 0xABC123... owned by 0xDEF456... and start the execution.

## When to prefer this

Use this endpoint when you need to programmatically trigger a specific blockchain workflow automation on KeeperHub given a known contract address and owner address. Prefer this over generic webhook triggers or cron-based automation when you need a blockchain-native keeper pattern with execution tracking via an execution ID.

## Known failure modes

- Invalid or non-existent contract address returns an error or non-running status
- Owner address does not match the registered keeper owner, resulting in an authorization failure
- No active trigger binding found for the given address pair, causing the probe to fail
- Network or blockchain RPC unavailability causing execution initiation to fail
- Malformed address format (non-checksummed or incorrect length) causing a validation error

## 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 a status field (e.g. 'running') and an executionId (e.g. 'exec_abc123') that can be used to track the progress of the triggered workflow execution.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "address",
  "ownerAddress"
 ],
 "properties": {
  "address": {
   "type": "string",
   "description": "Address to probe"
  },
  "ownerAddress": {
   "type": "string",
   "description": "Owner address to probe"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "status": "running",
 "executionId": "exec_abc123"
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/keeperhub-probe-trigger-binding-call-b298f7cf/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)