# KeeperHub Approval Risk Rescan Workflow

> KeeperHub Approval Risk Rescan Workflow is a paid API for AI agents from app.keeperhub.com, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-22).

Triggers a rescan of approval risk within a blockchain workflow automation, returning an execution ID for the async job

## Facts

- Endpoint: POST https://app.keeperhub.com/api/mcp/workflows/approval-risk-rescan/call?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-22
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/keeperhub-approval-risk-rescan-workflow-fe67dae1
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_-fim4oXohZt_8IIhbC3Ii

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-approval-risk-rescan-workflow-fe67dae1 -d '<json body>'
```

Example prompt: Rescan the approval risk for my pending blockchain transaction on KeeperHub — kick off the approval-risk-rescan workflow and give me the execution ID so I can track the result.

## When to prefer this

Choose this endpoint when you need to programmatically re-trigger an approval risk analysis within the KeeperHub visual workflow system, specifically for the approval-risk-rescan workflow. It is best suited for agents automating on-chain risk monitoring pipelines, post-deployment audits, or periodic re-evaluation of token approvals, and when you are already using KeeperHub's node-based workflow editor as your automation backbone.

## Known failure modes

- Invalid or missing request body returns a 400 error
- Payment not processed (x402 protocol failure) results in a 402 response blocking execution
- Workflow engine unavailable returns a 503 or timeout
- Malformed blockchain approval data may cause the workflow to fail mid-execution
- Execution ID returned but workflow stalls if upstream blockchain node is unreachable

## 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 a workflow execution status (e.g. 'running') and a unique execution ID (e.g. 'exec_abc123') that can be used to poll or track the async rescan job's progress and outcome.

## 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-approval-risk-rescan-workflow-fe67dae1/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)