post_v1_compliance_verifications
StartVerification begins a KYC/KYB verification of a subject through the wired provider — an existing subject by id, or one created inline from the request.
StartVerification begins a KYC/KYB verification of a subject through the wired provider — an existing subject by id, or one created inline from the request. The returned status is provider-reported and never terminal on a fresh start: starting a verification can never yield a verified record, and a provider error is a 502, never a verification.
| Tool | post_v1_compliance_verifications |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 5 |
| Operation | POST /v1/compliance/verifications |
| Product | compliance |
Arguments
| Field | Type | Required | Default | Values | Description |
|---|---|---|---|---|---|
email | string | — | — | — | Email is an inline subject's contact email, sealed at rest. |
kind | string | — | — | — | Kind is an inline subject's party type: "individual" (KYC) or "business" (KYB). |
name | string | — | — | — | Name is an inline subject's name, sealed at rest. |
ref | string | — | — | — | Ref is the org's own opaque external id for an inline subject. |
subjectId | string | — | — | — | SubjectID names an existing subject to verify; empty creates one inline. |
tools/list declares a type and a description for each field and nothing further. A — means neither the door nor that operation constrains the field.
Call it
A tools/call carries every argument in one flat object — nothing binds to a path or a query string. Nothing above is required, so every declared argument is shown rather than a guess at which matter.
curl -X POST https://api.hanzo.ai/v1/mcp \
-H "Authorization: Bearer $HANZO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "post_v1_compliance_verifications",
"arguments": {
"email": "<email>",
"kind": "<kind>",
"name": "<name>",
"ref": "<ref>",
"subjectId": "<subjectId>"
}
}
}'Values are the operation's own defaults and enumerated values where it declares them, and a <placeholder> where neither source declares one. tools/list needs no credential; tools/call does — called without one the door answers HTTP 200 with a JSON-RPC result whose isError is set and whose text says what was missing. How to get a key →
The operation behind it
| Operation | Route | Product | Summary |
|---|---|---|---|
post_v1_compliance_verifications | POST /v1/compliance/verifications | compliance | Begins a KYC/KYB verification of a subject through the wired provider — an existing… |
The same capability over plain HTTP is in the compliance API reference, on https://api.hanzo.ai.
All 755 tools · The door · API reference
Generated from tools/list on https://api.hanzo.ai/v1/mcp — 833 tools captured 2026-08-01, of which 755 are documented here (the operator surface is not published) (this build read the vendored copy; the door was unreachable).
How is this guide?
post_v1_compliance_subjects
CreateSubject records a party the org is verifying as part of its own onboarding/compliance — a team member, vendor, customer, or counterparty.
post_v1_compliance_verifications_id_decision
DecideVerification records a privileged reviewer's MANUAL decision on a verification — the human-in-the-loop path, and the ONLY route to a passing status when no real provider is wired.