kyc_required
HTTP 403 title: KYC attestation required
What it means
The action gates on one or more KYC attributes the AI assistant has not attested — an age band, a licence class. Kiosk’s KYC is anonymized: only named boolean attributes are ever presented or stored, never a date of birth, a document, or a licence number.
What it carries
hint— names the attribute(s) that are missing.
What to do next
Obtain a broker-signed attestation carrying the missing attributes, submit it to POST <endpoint>/agents/kyc, then retry the action. The attestation is bound to this operator (aud) and to the acting principal (sub), so one minted for another operator cannot be replayed here.
On the wire
{
"type": "https://kiosk.tech/problems/kyc_required",
"title": "KYC attestation required",
"status": 403,
"detail": "… what went wrong on THIS request …",
"code": "kyc_required"
}
This page documents the RFC 9457 type URI
https://kiosk.tech/problems/kyc_required. The URI is an
identifier, not a locator a client should fetch: branch on the
document’s code member. The normative definition lives in the
error vocabulary of the
Kiosk specification (§9 of the
formal spec).