mandate_verification: The agent's verification level is too low
A mandate on the path names minAgentVerification, and the serviceNode has no current attestation at or above that level: its attested level is lower, the verification provider attests nothing for it, its attestation expired, or the provider is off or unavailable. It is checked when a stream is opened or delegated, on every spend, and for the payee a payment authorization (POST /owner/v1/streams/{id}/payment-authorizations) names. Nothing is allocated, billed or authorized (fail closed).
What to do
- Ask the provider about the agent:
POST /owner/v1/kya/checks{serviceNode}, then retry. The levels arenone<key_bound<operator_identified<operator_verified. - If the check answers
kya_subject_unknown, the agent's operator completes the provider's checks first. - If the deployment runs with
CORE_KYAoff, every agent is refused under a mandate that requires a level. Open a budget whose mandate requires no level, or ask the operator to turn KYA on. - A running mandate can only raise
minAgentVerification, never lower it.
On the wire
HTTP 409, error type halted (or mandate_error on open/delegate).
On spending, a client that does not send Dynamo-Error-Detail: 1 to a route that predates 1.4.0 sees the legacy reason cap, so its response shape is unchanged. Opted-in clients, and the routes that always answer in detail such as payment authorizations, see mandate_verification.
On a stream open or delegation or a human payment, a client that does not send Dynamo-Error-Detail: 1 gets {"error": "mandate", "reason": "mandate_verification", "detail": "…"}: the precise reason, without errorDetail. The child adoption preparation (POST /owner/v1/streams/{id}/children/adopt-prepare) sends errorDetail to every client. The plugin wire's child open (POST /plugin/v1/streams/{id}/children) answers HTTP 409 {"error": "child open refused (fail closed)", "reason": "mandate_verification"}, with no detail and no errorDetail.
A mandate names minAgentVerification only when the request that sets it is pinned at Dynamo-Version 1.8.0 or later; an earlier pin (on a single-tenant core, also a request that names no version) is refused with 400 invalid_request. On the multi-tenant hosted tier a request that names no version is served the account's default (1.8.0 for new accounts).
The detailed open refusal:
{
"error": "mandate",
"reason": "mandate_verification",
"detail": "…",
"errorDetail": {
"type": "mandate_error",
"code": "mandate_verification",
"message": "…",
"param": "mandate",
"doc_url": "…/errors/mandate_verification.md",
"fix": "the serviceNode needs a current attestation at or above the mandate's minAgentVerification: run POST /owner/v1/kya/checks for it (CORE_KYA on), or use a mandate that requires a lower level"
}
}
See KYA and all error codes.