post_v1_compliance_accreditation

CreateAccreditation records an ASSERTED accreditation state for a subject — the subject's own assertion, with no verifier.

CreateAccreditation records an ASSERTED accreditation state for a subject — the subject's own assertion, with no verifier. Every CONFIRMED state (provider_verified, reviewer_confirmed) and every rejected/expired state is a DECISION recorded via the decision endpoint, attributed to the reviewer — a create can never stamp a confirmation. The underlying figures (income, net worth) are never stored; only the method, category, and state.


Tool	`post_v1_compliance_accreditation`
Door	`https://api.hanzo.ai/v1/mcp`
Method	`tools/call` (JSON-RPC 2.0)
Arguments	7
Operation	`POST /v1/compliance/accreditation`
Product	compliance

Arguments

Field	Type	Required	Default	Values	Description
`basis`	`string`	—	—	—	Basis is the qualification category: income, net_worth, professional_license, or entity.
`evidenceDocId`	`string`	—	—	—	EvidenceDocID references an evidence document in the org's sealed data room.
`expiresAt`	`integer`	—	—	—	ExpiresAt is the unix second a confirmation ages out; 0 means none.
`method`	`string`	—	—	—	Method is how the state was established: self_attested, third_party_letter, or provider_verified.
`note`	`string`	—	—	—	Note is a non-PII operator note.
`status`	`string`	—	—	—	Status may only be "asserted" (empty reads as asserted); every confirmed, rejected or expired state is recorded via the decision endpoint.
`subjectId`	`string`	—	—	—	SubjectID names the subject this record is about; it must exist within the org.

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_accreditation",
         "arguments": {
           "basis": "<basis>",
           "evidenceDocId": "<evidenceDocId>",
           "expiresAt": 0,
           "method": "<method>",
           "note": "<note>",
           "status": "<status>",
           "subjectId": "<subjectId>"
         }
       }
     }'

Values are the operation's own defaults and enumerated values where it declares them, and a <placeholder> where neither source declares one. expiresAt holds a stand-in that cannot be spelled that way — JSON gives a number, a boolean and a timestamp no placeholder form — so that value is this page's, not the API's. Neither the door nor the operation 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_accreditation`	`POST /v1/compliance/accreditation`	compliance	Records an ASSERTED accreditation state for a subject — the subject's own assertion, with…

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).

post_v1_compliance_accreditation

Arguments

Call it

The operation behind it

On this page