Request a demoLog in

Automate your treasury. Build in minutes.

Nearly everything your team does in the dashboard, your code can do too. CLI, SDKs, webhooks and docs — automate from your shell, your CI, or an AI agent. Approving payouts and issuing API keys stay with a signed-in person, on purpose.

The Developer tier is free — sign-ups are by referral right now, ask us for a code.

A developer sitting with a Guveno wallet, surrounded by CLI, npm, code, API, config and docs icons

Your language, your toolchain.

Grab the CLI for your shell and CI, or the SDK for Node or Python. Same API underneath.

@guveno/clion npm→
npm install -g @guveno/cli
@guveno/wallet-sdkon npm→
npm install @guveno/wallet-sdk
guvenoon PyPI→
pip install guveno

A full wallet backend, without the backend.

✻
HD wallet groups: Create Bitcoin & Ethereum wallet groups with 12- or 24-word seeds in a single call.
✻
Deposit addresses: Derive labelled addresses on demand and hand them straight to your users.
✻
Balances & monitoring: Read live balances and totals straight from the chain, per wallet or company-wide.
✻
Webhooks: Subscribe to deposits and withdrawals, from detected to confirmed or rejected, with signed HMAC callbacks.
✻
Withdrawals from CI: Sign and broadcast withdrawals from a pipeline with your own key provider.
✻
Company-wide totals: Pull balances, totals and stats across every wallet in the org with one call.
For AI agents

The crypto wallet that AIs love.

Give your agent a key, not the keys. It drives the same CLI, SDKs and API your engineers use, with no plugin to install. Credentials come from environment variables, the CLI fails fast instead of waiting on a prompt when no terminal is attached, and --json gives it output it can parse.

✻
A key for one job: Give each agent its own API key, limited to the wallets and actions it needs. Lock it to the IP addresses it runs from and give it an expiry date. Only a signed-in person, confirming it’s them at that moment, can create a key or widen what it can do.
✻
Agents ask, people approve: Let the key request payouts and nothing more. The agent raises a withdrawal request through the API or the Node or Python SDK, a person approves it, and what they approve is exactly what gets signed: same address, same amount. No API key can approve a request.
✻
Guardrails on the key, not in the prompt: Guveno checks what a key may do on every request, instead of trusting the agent to follow instructions. An API key alone can’t sign, so an agent that reads balances and requests payouts never needs your encryption password or recovery phrase.
✻
Never above its issuer: An agent’s key can never do more than the person who issued it, and it narrows automatically when that person’s role or access changes.
agent prompt

“What’s in the treasury wallet, and what went out last?”

what it runs
guveno balances treasury-btc --json
guveno list-withdrawals --wallet-id treasury-btc --limit 5 --json

Both run on the API key alone, with read access to that wallet: no password, and nothing that can sign. Creating a wallet or signing a send also needs your encryption password or your own key material, and create-wallet prints the new recovery phrase, so keep those steps with a person or a dedicated signing host.

Point your agent at:@guveno/clion npm→@guveno/wallet-sdkon npm→guvenoon PyPI→the docs →
Or ask an assistant about the docs
View as Markdown (opens in a new tab)Open in ChatGPT (opens in a new tab)Open in Claude (opens in a new tab)Open in Perplexity (opens in a new tab)

Try the CLI right here.

This is a real feel for the tool — type a command (or tap one) and see what comes back. Nothing leaves your browser.

# try the Guveno CLI — type 'guveno --help' or tap a command below
$guveno
try

Built for one, or two of you.

You don't need a company to need a real wallet. The Developer tier is free, and it's the same wallet the enterprise plans run on — just fewer seats.

✻
Solo founders: Take crypto in your product without standing up custody yourself. Free while you build, and nothing to migrate when it works.
✻
Micro teams: Two org members on the free tier, five on Startup — same wallet, same API, you just add seats.
✻
Solopreneurs & contractors: Invoice in crypto, keep each client's funds in their own labelled wallet, and hand over a clean audit trail at the end.
✻
Side projects: Bitcoin & Ethereum testnets are included free, so an idea costs nothing until it has real users.
Not building anything — just want a wallet for yourself? Personal wallets →

Common questions

Yes. The Developer plan is free: 3 secure wallets, 100 monitored addresses, Bitcoin & Ethereum testnets, webhooks and full API access.
Node.js (@guveno/wallet-sdk on npm) and Python (guveno on PyPI), plus the @guveno/cli command line and a documented REST API.
Yes, with no plugin to install. An agent uses the same CLI, Node and Python SDKs and REST API your team does, through an API key a person creates and scopes in the dashboard. Give it a key that can only request payouts, and no payout goes out until a person approves it. Give it signing rights and it also needs your encryption password or your own key material, like any automated signer.
No. An agent that can run shell commands can use the Guveno CLI, and one that can run Node or Python can use the SDKs. guveno --help lists the commands, and guveno <command> --help lists each command’s flags.
Register a webhook. You get signed (HMAC) callbacks when deposits are detected, confirmed or rejected and when withdrawals are broadcast, confirmed or rejected, with delivery logs and secret rotation built in.
Shipping this with a team? Guveno for teams →