Enterprise · Compliance · Legal
Built for first-year SOX narratives
Every machine-originated payment routed through Yebo traces to its policy decision and, when approval is required, to the human who approved the mission's limits with a passkey. Each executed payment gets a gateway-signed receipt that can be verified offline with Yebo's open-source npm verifier, npx yebo-verify@0.2.0. Execution runs in dry-run mode today, so no money moves.
Delegation chains (coming soon)
Recording the full delegation chain of a multi-step agent workflow, so an auditor can walk from any tool call back to the human approval, is coming soon. Today the gateway records an approval reference, the mandate hash and the policy hash for each executed payment (dry run today).
- HumanPasskey approves the mission's limits
- Yebo Authorization CertificateGateway-signed receipt over the mandate hash, approval reference and policy hash
- AP2 MandateImmutable authorization primitive + policy hash
- Orchestrator AgentRoot delegation point
- Sub-AgentDelegated scope enforced by Sentinel
- Tool CallFinal execution, tracked as action_id
Compliance API
A focused set of endpoints gives compliance and legal teams everything they need:
- Full action ancestry
Coming soon: walk any tool call back through the delegation chain to its human approval.
- Exportable compliance report
Receipt export in JSON, NDJSON or CSV today. Coming soon: a period summary with denial counts and the sentinel-violation log.
- Auditor view of a single mandate
Coming soon: a sensitivity-redacted mandate for third-party sharing, with the sentinel-check summary and verifiable signature.
Full endpoint reference, request and response payloads, authentication, and export formats are available to approved partners and pilot customers under sandbox access.
Regulatory alignment
SOX (Sarbanes-Oxley)
Disbursement controls must demonstrate that material transactions were authorized by appropriate personnel, and that evidence must survive auditor testing years later.
Every payment executed through the Yebo gateway carries a gateway-signed receipt that references the approval record it ran under. Execution runs in dry-run mode today, so these are dry-run receipts and no money moves. Designed to support first-year SOX control language for machine-originated disbursements.
302 / 906 certifications
Executives personally certify controls over every disbursement, including any initiated by software.
The Yebo Authorization Certificate gives the certifying officer a durable artifact behind the signature: a gateway-signed record of what was approved and under which policy, independent of any vendor's logs. 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.
Evidence durability
Approval evidence held in a vendor's logs lasts only as long as the vendor relationship does.
YACs verify with only the artifact and a public key. No access to the payment platform, the AP vendor, or Yebo is required.
Auditor testing
Auditors sample disbursements and test that the approval control operated as described.
Each action the Yebo gateway lets through carries a gateway-signed receipt and evidence bundle for the workpaper, verifiable offline with the public keys at the gateway's /authorization-receipt/keys endpoint and the open-source npm verifier, npx yebo-verify@0.2.0.
Yebo does not provide legal advice. Consult your compliance counsel to map these capabilities to your specific regulatory obligations.
Ready to build an auditable AI stack?
Our enterprise team will walk you through integration, custom policy setup, and compliance report configuration.