# KeeperHub Deplex Risk Intelligence Workflow

> KeeperHub Deplex Risk Intelligence 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-09-14).

Analyzes EVM transaction calldata and addresses for risk intelligence by running the deplex-risk-intel blockchain workflow

## Facts

- Endpoint: POST https://app.keeperhub.com/api/mcp/workflows/deplex-risk-intel/call
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/keeperhub-deplex-risk-intelligence-workflow-cb05e281
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_nzbl9Csuy5mvMjD48KZEb

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-deplex-risk-intelligence-workflow-cb05e281 -d '<json body>'
```

Example prompt: Before I approve this transaction, run a risk intel check on this calldata — sender is 0xAbC123...def, target contract is 0x789...fed, calldata is 0xa9059cbb000...0001, and I'm sending 0 ETH.

## When to prefer this

Use this endpoint when you need automated, workflow-driven risk intelligence on specific EVM transactions before execution — especially when you have concrete calldata, sender, and contract address to inspect. Prefer this over generic blockchain explorers when you need structured risk scoring integrated into an automation pipeline. Best suited for pre-transaction screening in DeFi agents, wallet security tools, or smart contract audit workflows.

## Known failure modes

- Invalid or malformed hex calldata returns a validation error
- Non-EVM address formats for senderAddress or contractAddress cause rejection
- Missing required fields (value, calldata, senderAddress, contractAddress) result in a 400-level error
- Workflow execution failure may return an error status rather than 'running'
- Payment failure (insufficient USDC balance or x402 protocol error) blocks the call

## 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' string (e.g. 'exec_abc123') that can be used to poll or track the asynchronous risk intelligence workflow execution result.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "value",
  "calldata",
  "senderAddress",
  "contractAddress"
 ],
 "properties": {
  "value": {
   "type": "string",
   "description": "Native token value in ETH units, usually 0"
  },
  "calldata": {
   "type": "string",
   "description": "Hex transaction calldata to inspect"
  },
  "senderAddress": {
   "type": "string",
   "description": "Address that would send the transaction"
  },
  "contractAddress": {
   "type": "string",
   "description": "Target EVM contract address"
  }
 }
}
```

## Response schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/keeperhub-deplex-risk-intelligence-workflow-cb05e281/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)