We’re here to help

Once your account is set up (access is by invitation during the pilot), generate an API key in your dashboard. Your dashboard issues keys that look like yebo_sk_... Gateway enforcement of these keys (scopes, revocation) is coming soon.

Yes. The Developer plan is free and includes 1,000 mandates per month as a plan term (automatic metering is coming soon). No credit card required.

Yebo is called over HTTPS, so any framework that can make an HTTP request can route actions through it. The Agent Integration guide in our docs covers LangChain and LangGraph and is available to pilot customers. The TypeScript SDK is on npm: npm i @yebo-auth/sdk.

The action is blocked with a POLICY_DENIED error and the decision is written to the audit log. When an amount is above the session's per-transaction limit, the gateway can return a step-up challenge for a human to approve instead.

Not today. Yebo runs as a hosted service. If you need a dedicated or on-premise deployment, contact us at hello@yebo.dev to discuss it.

Traffic to yebo.dev and the gateway uses HTTPS, and execution receipts are ECDSA-signed and tamper-evident. Our services reach the production database over a private network, and database backups travel over TLS.

Yes. Every action the gateway lets through gets a gateway-signed receipt (ECDSA P-256, SHA-256). Public keys are published at the gateway's /authorization-receipt/keys endpoint, so anyone can verify a receipt offline with the open-source npm verifier, npx yebo-verify@0.2.0. The /verify samples are device-signed 2.0 artifacts, checked with npx yebo-verify@0.2.0. Versions before 0.2.0 cannot read them.

Retention periods are a term of your plan contract; automatic retention enforcement is coming soon. You can export receipts from the gateway in JSON, NDJSON or CSV at any time. Export via webhook is coming soon.