The first Liquid Network wallet for AI agents — and the first with a native Pix gateway. Non-custodial by construction: the seed — the wallet’s 12 words — never leaves the agent, and the server never signs.
non-custodial · on Liquid mainnet · since March 2026
DePix (digital real), L-BTC and USDt in a single wallet — confidential, cheap, fast. No other exists for agents.
Full on-ramp and off-ramp over Pix — from the QR to the payout. The only agent wallet with a built-in Pix gateway.
Seed encrypted on the machine, signing done right there, limits the owner sets. The server quotes and settles — never holds funds.
The same MCP at two levels of access. Hosted: 26 tools for receiving Pix — checkouts, products, status — zero keys, zero custody. Running where the agent lives, holding a seed: 62 in all, and it owns, signs and moves the money. One decision separates them: does the agent get a key to the money?
No install, no seed, no key. Create your account with Google or GitHub — it is born from that sign-in. Then add mcp.depixapp.com as a connector in your assistant and sign in with the same login. From there the agent creates checkouts and products and follows the payments. Moving money out, never: this level does not touch the money keys, which is why it can live on the internet.
The same MCP, now running where the agent lives and holding a seed: a full Liquid wallet that signs locally. Pays and receives Pix, holds and converts DePix/L-BTC/USDt, buys gift cards — under the limits the owner sets. One command: it asks for the limits, keeps the unlock key in the operating system’s own password vault, and registers itself with the assistants on that machine. No API key, no passphrase in a file. That is 29 wallet tools, 62 in total.
Level 1, hosted — pick your assistant and connect. When it asks you to sign in, use the same Google or GitHub you created the account with; there is no key to paste. For the full wallet, run the same MCP where the agent lives (the card above).
On claude.ai (web): Settings → Connectors → add a custom connector → paste the URL below. When it asks you to sign in, use the same Google or GitHub as your account — no key.
Or in Claude Code (CLI) — then run /mcp and sign in with the same login. The name is depix-hosted so it cannot collide with the local depix that init registers:
Or add it manually to ~/.cursor/mcp.json:
Or from the command line:
No 1-click deeplink — ChatGPT requires turning on developer mode.
https://mcp.depixapp.com/mcpCanonical URL: mcp.depixapp.com/mcp · MCP Registry io.github.depixapp/depix-mcp. Never paste your key (sk_…) into another endpoint.
At level 2 you do not open the account on a website and you create no key by hand. The agent opens its own account right there, in the conversation. You hand over one thing: a code that authorizes it — and the code is yours, not its.
You do this once, in 1 minute: open the page below, sign in with your Google or GitHub, and copy the code shown (it starts with op_). It reappears every time you open that page — lose it and you just go back.
op_ code into the chat when the agent asks. If you would rather paste nothing into a chat, init keeps the code for you.register_account: the account and its keys are born and stay encrypted on this machine. The secret keys never show up in the conversation, and the account starts in test mode.agent_status says what is still missing. verify_domain proves the site is yours. configure_depix_rail turns on receiving DePix straight on Liquid, without going through Pix. activate_key switches the account from test to live when the operator says so.Lost the code? Nothing happens: sign in to the same page again and the very same code comes back.
The newest models (the Claude 5 family, for instance) refuse to execute financial transactions on your behalf: they quote, create charges and read balances, but won’t do the conversion or the send for you. In that case, you’d have to execute it yourself.
Simpler, older models, such as Claude Haiku 4.5, still execute these calls normally. That rule comes from the model’s vendor — not from DePix App — and can change without notice. For full autonomy, independent of any assistant’s policy, run an agent of your own.
About the limits, in plain words: they hold back mistakes and trickery — a bug, a malicious instruction that arrived inside some text. Against a hostile agent with access to the machine’s terminal they are not a vault: the real defence is to keep in this wallet only what you would be fine losing.
All non-custodial, all under the agent’s key. From the first Pix received to the payout, across three assets and conversions done on your own machine.
Checkout or product: it mints the QR, the payer pays, the agent knows instantly.
Payout to any Pix key — the wallet signs, the server settles.
DePix (digital real), L-BTC and USDt in the same confidential wallet.
DePix ⇄ L-BTC ⇄ USDt via SideSwap and Boltz — direct, under the agent’s key.
Spend the balance on gift cards: the agent browses the whole catalogue and picks.
One cap per transaction and one per day, enforced on your machine before anything is signed. The owner sets them.
register_account creates the account and its keys, agent_status shows what is missing, verify_domain proves the domain, configure_depix_rail turns on receiving DePix and activate_key switches it to live.
llms.txt, OpenAPI and agent.json — the agent integrates on its own, with no wiring code from you.
The surface is machine-readable end to end. It’s the same API the MCP consumes: dogfooding, not a facade. No PDF, no "talk to sales".
Sign in with Google or GitHub and connect the hosted MCP — the account is born from that sign-in. When the agent needs to hold money, run the same MCP with a wallet and ask it to open its own account. Free sandbox, no card.