YeboYebo
Request a pilot

Enterprise Grade

Built for supervised and
policy-approved automation.

From request to execution: every action routed through Yebo is evaluated, authorized, and verified before it runs.

Explore the Lifecycle

The Mandate Lifecycle

From request to execution: every action routed through Yebo is evaluated, authorized, and verified before it runs.

  1. 1
    SUBMIT

    Intent Capture

    An agent or system submits an action request (payment, approval, data access, etc.). Yebo validates the request.

  2. 2
    EVALUATE

    Policy Evaluation

    The request is evaluated against your rules: Is the action allowed? Is it within limits? Is the counterparty approved? Is the agent authorized? Result: ALLOW, REQUIRE_APPROVAL, or DENY. A denied request stops here and is logged.

  3. 3
    FORMALIZE

    Mandate Construction

    An allowed or held request is converted into a mandate that defines the action, the scope (amount, target, parameters), the governing policy hash, and a limited time window. The mandate is immutable. Any change requires a new mandate.

  4. 4
    AUTHORIZE

    Human Authorization

    If approval is required, the approver reviews the mission and approves it with a passkey on their own device. The passkey approves the mission's limits (capabilities, per-transaction limit, payees), and every payment is checked against them. 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.

  5. 5
    VERIFY

    Final Verification

    Before execution, Yebo verifies: the mandate has not changed, the authorization is valid, the request has not expired, the request has not been replayed, and the action remains within scope. If any check fails, execution is blocked.

  6. 6
    EXECUTE

    Execution or Block

    ALLOW: proceeds. REQUIRE_APPROVAL: proceeds after approval. DENY: never executes. Execution runs in dry-run mode today, so no money moves.

AUDIT TRAIL

Verifiable Record

Every approved or executed action produces a signed record (what was requested, who approved it, what policy applied, what happened), exportable for audit. Denied actions are logged in the tamper-evident audit log.

How it all fits together

Yebo sits between AI decisions and execution. The gateway enforces policy. A passkey on the approver's device approves the limits.

Enterprise Setup
Teams configure Yebo by:
  • →Defining policies and thresholds
  • →Connecting payment systems and APIs (live payouts coming soon)
  • →Assigning approvers
  • →Monitoring actions and outcomes
Human Authorization
Approvers use the Yebo approval page:
  • →Open the approval link (mobile push notifications coming soon)
  • →Review the mission and its limits
  • →Approve or deny with a passkey on their own device
  • →The gateway checks the passkey session before releasing the action

Yebo does not rely on trust.

It enforces authorization before execution.

See it live in 30 minutes

We'll walk through the complete lifecycle using your own agent workflows.

Book a DemoDeveloper Portal →