# Oromi Human Verify — AI Agent Human-in-the-Loop Question

> Oromi Human Verify — AI Agent Human-in-the-Loop Question is a paid API for AI agents from agents.oromi.co.uk, paid per call via x402, $0.5/call, status unknown (last checked 2026-09-14).

Routes a yes/no question to a human reviewer and returns an asynchronous task ID the agent can poll for the human's answer.

## Facts

- Endpoint: POST https://agents.oromi.co.uk/api/human/verify
- Price: $0.5/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/oromi-human-verify-ai-agent-human-in-the-loop-question-6b4c1f51
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_8QC3QPdZDQYRfOAOqyYp8

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 oromi-human-verify-ai-agent-human-in-the-loop-question-6b4c1f51 -d '<json body>'
```

Example prompt: Ask a human reviewer whether the company listed at https://example.co.uk/about is a legitimate UK registered business — the question is 'Is this website operated by a genuine, actively trading UK company?' and you can give them context that we're vetting a potential supplier.

## When to prefer this

Use this endpoint when an AI agent encounters a decision that requires human judgment and cannot be resolved algorithmically — particularly for yes/no verification questions about URLs, documents, or claims where automated checks are insufficient. Prefer it over fully automated validation endpoints when stakes are high, when the question is inherently subjective, or when a human audit trail is required. Not suitable for time-sensitive decisions due to asynchronous human response times.

## Known failure modes

- Missing required 'question' field returns a validation error
- Invalid bodyType enum value causes request rejection
- Human reviewer does not respond — poll_url may return 'pending' indefinitely
- Network or payment failure via x402 protocol means task is never created
- Polling before human responds returns status 'pending' with no answer yet

## How this service works

Machine-payable APIs for AI agents, paid per call in USDC via the x402 protocol: UK business data (Companies House), UK property market data (HM Land Registry), website agent-readiness audits, and crypto market context.

## Output

Returns a JSON object with a 'status' field (e.g. 'pending'), a unique 'task_id' string (e.g. 'ht_1a2b3c'), and a 'poll_url' the agent can repeatedly call to retrieve the human reviewer's yes/no answer once it is available.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "url": {
   "type": "string",
   "description": "Optional URL for the human to look at"
  },
  "context": {
   "type": "string",
   "description": "Optional background context"
  },
  "question": {
   "type": "string",
   "description": "A clear yes/no question for a human"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "status": "pending",
  "task_id": "ht_1a2b3c",
  "poll_url": "https://agents.oromi.co.uk/api/human/result?task_id=ht_1a2b3c"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/oromi-human-verify-ai-agent-human-in-the-loop-question-6b4c1f51/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agents.oromi.co.uk](https://www.zero.xyz/host/agents.oromi.co.uk/llms.txt)
