YAC/1.0 receipt format (spec available to pilot partners)

Yebo Authorization Certificate

A signed receipt format for recording that an AI action was authorized under policy, within limits a human approved. Signed by the gateway (ECDSA P-256), verifiable offline with the open-source npm verifier, npx yebo-verify@0.2.0. For missions, the approver's passkey approves the mission's limits. Per-payment device signing is live and has been exercised in production: the approver's passkey signs the exact payment (amount, payee, agent, validity window), and anyone can check it offline with yebo-verify 0.2.0.

Request YAC Spec Access →Developer Docs

ECDSA P-256

Signature Algorithm

SHA-256

Canonical Digest

10 to 14

Signed receipt fields

YAC/1.0

Protocol Version

What is a Yebo Authorization Certificate?

A YAC is a receipt signed by the Yebo gateway that records the decision on an AI action and the policy hash it was decided under. The gateway produces one when it executes an approved action. Execution runs in dry-run mode today, so these are dry-run receipts and no money moves.

The certificate is signed by the Yebo gateway (ECDSA P-256, a software key held by the gateway) using a key you can verify independently: the public keys are published at the gateway's /authorization-receipt/keys endpoint. The signed fields are canonicalized, SHA-256 hashed, and the signature covers that hash, making any tampering immediately detectable.

YACs are designed to be the compliance artifact for machine-originated disbursements: the evidence a regulator, auditor, or legal team needs to answer “did a human authorize this?”

Passkey approval for missions

For missions, the approver's passkey approves the mission's limits and every payment is checked against them; policy-approved actions carry the gateway signature only. Per-payment device signing is live and has been exercised in production: the approver's passkey signs the exact payment (amount, payee, agent, validity window), and anyone can check it offline with yebo-verify 0.2.0.

Policy-bound

Carries the policy hash recorded with the mandate, inside the signed fields

Verifiable without an account

Anyone with the public key can verify with the open-source npm verifier, npx yebo-verify@0.2.0, no Yebo account required

Tamper-evident

Any field change invalidates the ECDSA signature

Partner Access

YAC is Yebo's signed authorization certificate format. Every executed Yebo mandate gets a gateway-signed, policy-bound receipt (execution is dry run today; no money moves). The full schema, signing spec, and verification endpoints are available to approved partners under sandbox access.

Request YAC Spec Access →

Multi-agent compliance →Yebo Trust Score →Developer docs →

Request access to start issuing YACs

Every action the Yebo gateway executes gets a signed YAC automatically (dry run today).

Request YAC Spec Access Book Enterprise Demo