# KeeperHub Assay Verify - Blockchain Intent Verdict Lookup

> KeeperHub Assay Verify - Blockchain Intent Verdict Lookup 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).

Retrieves a verifier's public verdict record for a specific blockchain intent hash from the IntentRegistry

## Facts

- Endpoint: POST https://app.keeperhub.com/api/mcp/workflows/assay-verify/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-assay-verify-blockchain-intent-verdict-lookup-72b10f1c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_wBBVJxfbmLUIxX-1xqSHQ

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-assay-verify-blockchain-intent-verdict-lookup-72b10f1c -d '<json body>'
```

Example prompt: Check the assay verification verdict for verifier address 0xAbC123... and intent hash 0xDef456... in KeeperHub's IntentRegistry — I need to know if that intent has been approved.

## When to prefer this

Use this endpoint when you need to programmatically check whether a specific blockchain intent has received a public verdict from a known verifier address, particularly within automated KeeperHub workflows that gate further actions on intent approval. Prefer this over manual chain queries when you need the result returned via an MCP-compatible interface integrated into a node-based automation pipeline.

## Known failure modes

- Invalid or malformed verifier address returns an error
- Intent hash not found in IntentRegistry returns empty or error response
- Intent hash not produced by assay_hash_intent tool may be rejected as non-canonical
- Payment failure (x402) results in 402 response before processing
- Verifier has not yet submitted a verdict, returning no record
- Network or blockchain RPC timeout causing delayed or failed response

## 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') representing the asynchronous lookup of the verifier's public verdict record for the given intent hash.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "verifier",
  "intentHash"
 ],
 "properties": {
  "verifier": {
   "type": "string",
   "description": "Address of the verifier whose public verdict record to return."
  },
  "intentHash": {
   "type": "string",
   "description": "The canonical hash of the intent to check, as committed to IntentRegistry. Produce it with the assay_hash_intent MCP tool."
  }
 }
}
```

## Response schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/keeperhub-assay-verify-blockchain-intent-verdict-lookup-72b10f1c/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)