The missing authorisation layer for the agentic economy.

Get access How it works

Scroll to see how it works

01 / Agents

Agents are starting to spend.

They buy, book and call paid tools on their own.

02 / The risk

Nothing bounds what they can do.

A fooled agent can spend like anyone else.

03 / The envelope

SafeShake gives each one an envelope.

Signed limits: what, from whom, and how much.

04 / The check

Every action is checked first.

Inside the envelope, it runs. Outside, it doesn't.

05 / The record

Every decision becomes proof.

A record anyone can verify, without us.

002One install, three capabilitiesENV_001 / bsea/0.2Signed by principal

One 2-minute install.Three new capabilitiesfor your agents.

Observe today. Enforce when you are ready. Transact later. The same envelope throughout.

[01]Observe

See every agent's spend, and who approved it. Nothing is blocked.

ChargebackEvidenceIn pilot

A figure walking across a giant SafeShake mark in a beam of light

[02]Enforce

The same envelope reserves before anything runs.

BudgetsContainmentOn roadmap

A robotic hand and a human hand reaching towards the SafeShake mark

[03]Transact

SafeShake authorizes. Your systems move the money.

PurchasesPayeesLater

For developers →For enterprise →

1Signed object

4Questions answered

2Modes, same rules

591Automated tests

004Anatomy

004Signed once, never edited

What's inside an envelope.

Scroll to open it up

Tap a field

[01] Owner

Who delegated

[02] Allocation

What, and how much

[03] Rules

Under which rules

[04] Validity

For how long

[05] Signature

Signed by the principal

[06] Record

Every action, chained

005 / Two modes

Observe first.Enforce when ready.

01{{mt0}}
02{{mt1}}
03{{mt2}}
04{{mt3}}

006 / IntegrationEvery control keeps its job

Sits besidewhat you already run.

One layer is missing from the stack: delegated authority. Scroll along it.

Who the agent is

Identity provider

Envelopes name owners and bind to identities you already issue.

Delegated authority

SafeShake

Self-hosted in your environment. Checks the envelope, holds the evidence.

Routes, limits keys

AI gateway

A gateway policy asks SafeShake before forwarding.

Orchestrate

Agent frameworks

Hooks or middleware ask before each model and tool call.

Consumed

Models, tools, MCP

An MCP server and local proxy see the calls hooks miss.

Owned, settled, proven

Economic record

Removable. The evidence stays usable without us.

{{iNo}} / 06Layer in the stack

007 / Verification

Anyone can check the record.

Checked offline, with no access to SafeShake. Every entry is chained to the one before, so edits and deletions show up.

$ safeshake verify legal-october.json PASS envelope id is the content hash of its body PASS envelope signed by the declared principal key {{vl4}} {{vl5}} PASS event signatures verify against the public key

legal-october.json{{chSum}}

#0410{{bt0}}{{bs0}}

#0411{{bt1}}{{bs1}}

#0412{{bt2}}{{bs2}}

#0413{{bt3}}{{bs3}}

#0414{{bt4}}{{bs4}}

Delegate, don't surrender

The line is yours.

A person sets the limits. The agent can be fooled and still can't cross them: it only asks, it never holds the keys.

An audience in front of a SafeShake screen

BuiltAnd working

YouSet the limits

Every actAnswerable after

0 keysHeld by the agent

009Recognition

009On the record

Filed. Published.Tested.

PatentPatents pendingOn the core system

Tested591Automated tests

Open verifierChecks offlineNo access to SafeShake needed

Agents are going to spend money for us, whether we're ready or not. Every one of them should do it inside limits a person signed, with a record anyone can check.

Zack Field

Co-founder + CEO