The warm tier · your own organization
Create a mandate
A mandate lets an agent spend without holding the key that decides how much it may spend. This creates one: two humans, two quorums with different thresholds, a policy that caps the agent, and an organization wallet governed by that policy.
Where the keys live
Your operators’ signing keys are generated by your browser and never leave it. Only the public halves reach this server, because a Privy key quorum has never consumed anything else. That means the organization is created under our Privy app but is not ours to spend from: every mutation additionally needs a signature from keys we do not have. We are the registrar, not the custodian.
If you would rather not rely on us at all, the same flow exists as npm run privy:setup against your own Privy app. Either way you end with the same .env block and the same organization shape, and either way you can self-host from the repository.
The organization
Two operators minimum. Funding the agent takes one signature; raising the cap takes two. That asymmetry is the only thing standing between an agent and its own spending limit, so one operator is not offered.
Your operators’ signing keys are generated by your browser and stay in this tab. Only the public halves are sent, which is all a Privy key quorum consumes. The server refuses the request outright if a private key ever appears in it.