# Verifi Human Verification Gate

> Verifi Human Verification Gate is a paid API for AI agents from verifi.cloud, paid per call via x402, $0.12/call, status unknown (last checked 2026-10-28).

Submits a claim and agent intent to a human review queue for manual verification, returning a human-checked result via polling or callback.

## Facts

- Endpoint: POST https://verifi.cloud/verify?utm_source=zero.xyz
- Price: $0.12/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-28
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/verifi-human-verification-gate-612aee0a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_5TvMkW3IliINL0u_v9Jni

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 verifi-human-verification-gate-612aee0a -d '<json body>'
```

Example prompt: Before I finalize this contract summary, please send the claim 'The total payment due is $47,200 as stated in section 4.2' to Verifi for a human to double-check — my intent is to confirm the dollar amount before I send it to the client.

## When to prefer this

Use this endpoint when an AI agent needs a human checkpoint before taking a consequential or irreversible action, when a claim needs authoritative human fact-checking rather than automated validation, or when compliance or safety policy requires a human in the loop. Prefer this over automated validation APIs when the stakes are high enough to warrant human judgment, when the claim involves subjective or contextual nuance that algorithms miss, or when an audit trail of human review is required.

## Known failure modes

- Invalid agent_id format (not a valid 0x Ethereum address) returns a validation error
- claim or intent fields missing or empty cause a 400-level rejection
- callback_url not using HTTPS is rejected
- claim exceeds 4000 character limit causing truncation or rejection
- human reviewer unavailable or delayed leads to long queue wait times
- network timeout before queue admission confirmation is received

## How this service works

Gate 1 of one Verifi chain. Admit one request to the human queue.

## Output

A queue admission confirmation indicating the request has been accepted into the human review pipeline. The actual human verification result is retrieved later via polling the endpoint or via a webhook callback to the provided callback_url, and will include the human's verdict on the submitted claim.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "claim": {
   "type": "string",
   "maxLength": 4000,
   "minLength": 1,
   "description": "The statement a human should verify."
  },
  "intent": {
   "type": "string",
   "maxLength": 2000,
   "minLength": 1,
   "description": "What the agent wants to do and why it needs a human check."
  },
  "agent_id": {
   "type": "string",
   "pattern": "^0x[0-9a-fA-F]{40}$",
   "description": "The requester wallet address."
  },
  "callback_url": {
   "type": "string",
   "pattern": "^https://",
   "maxLength": 2048,
   "description": "Optional https URL notified when the result is ready or failed. Polling always works."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/verifi-human-verification-gate-612aee0a/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from verifi.cloud](https://www.zero.xyz/host/verifi.cloud/llms.txt)