Cryptographic Mandate Controls

Simple pricing. No surprises.

Free for developers. Enterprise pricing that scales with your mandate volume. Start a 14-day pilot on any paid plan with no commitment.

14-day pilot available on all paid plans. No commitment required.

Developer

Build and test with the full Yebo pipeline. No credit card.

Free
  • 1,000 mandates per month
  • Sandbox gateway access
  • API key management
  • MCP server (@yebo-auth/mcp-server)
  • Standard policy packages
  • Community support
Start Building

Starter

Production authorization for teams running AI in finance or operations.

$2,500/mo
  • Up to 50,000 mandates/mo
  • Standard policy packages
  • 30-day audit log retention
  • YAC receipt generation
  • Stripe + ACH adapters
  • Email support (48hr SLA)
Start 14-Day Pilot
Most Popular

Growth

Advanced controls and compliance for scaling enterprise AI operations.

$8,000/mo
  • Up to 250,000 mandates/mo
  • Custom policy configuration
  • 1-year audit log retention
  • SOX evidence exports
  • All execution adapters
  • Priority 24/7 support
  • Integration engineering hours
Contact Sales

Enterprise

Dedicated infrastructure, custom SLAs, and a dedicated solutions architect.

Custom
  • Unlimited mandates (tiered)
  • Dedicated infrastructure instance
  • Custom security SLAs
  • Multi-region deployment
  • TAM + Solutions Architect
  • Compliance audit support
Request Quote

Usage-based pricing

Pay per mandate processed. Included mandates in each plan, then metered usage after that.

$0.04
Base Rate
Per mandate, Starter tier
$0.02
Growth Rate
250,000+ mandates/mo
Custom
Enterprise Rate
Volume tiers negotiated

What counts as a mandate?

One mandate = one authorization request through the Yebo pipeline. Preflight checks (POST /preflight) and verification calls do NOT count.

Counted
POST /intent/execute - creates a mandate
Counted
POST /execute - direct execution with a signed mandate
Not counted
/preflight, /verify, /receipt - reads only

Why finance-systems teams pay for mandate controls

Your executives certify controls over every disbursement under Sections 302 and 906, including any that software initiates. The approval evidence behind those certifications usually lives in a vendor's logs, and it lasts only as long as the vendor relationship does.

Yebo produces a cryptographic mandate for every approved payment: independently verifiable proof of who approved exactly what, exportable as an audit artifact, and durable long after the vendor is gone. If the mandate cannot be produced, the payment does not move.

Approval bound toPayment parameters
Verification requiresArtifact + public key
Evidence lifetimeVendor-independent
PostureFail-closed

Start with a 14-day pilot

Pick one workflow. We set up one policy package. You see exactly what Yebo blocks, approves, and escalates. No commitment.

Enterprise contracts: hello@yebo.dev · Proposal within 48 hours