One Vault.
Every Agent.
Complete Control.
AI agents need your wallet, passport, API keys, addresses. DCP lets you decide who gets what, when. Agents request, you approve, vault delivers. One vault, every agent, complete control.
Trading Agent
requests transaction signing
Connected Agents
Works with
AI Agents Are Powerful.
But They're Locked Out.
AI can book flights, trade crypto, manage emails, make purchases. But it needs access to your sensitive data — wallets, API keys, passwords, identity. Today, there's no safe, standard way to do this.
Agents can't safely access your sensitive data
Your AI needs your wallet to trade. Your travel agent needs your passport. Your shopping bot needs your credit card. But there's no safe way to give them access without handing over raw credentials.
→ You either don't use AI for real tasks, or you risk everything.
Every agent invents its own security
Claude has one approach. Your trading bot has another. Each tool, framework, and agent handles secrets differently. No standards. No consistency. You're managing 10 different systems.
→ Fragmented, incompatible, impossible to audit.
You can't share data between agents
Your passport info is stuck in one agent. Your address is in another. You enter the same data 5 times for 5 different AI tools. Want to switch agents? Start over.
→ Redundant data, security gaps, vendor lock-in.
The Real Cost
AI agents could transform how you work, trade, travel, and shop. But without a secure, standard way to handle sensitive data, you're stuck. You can't use AI for anything real. DCP fixes this.
DCP: A Standard Way to Handle Secrets
Instead of every agent inventing its own security, they all talk to your vault. You enter your data once. Every agent that needs it can request access. You approve or deny. Standard, secure, reusable.
Safe Access
Agents get results, never raw secrets
One Vault, Many Agents
All your AI tools share the same vault
Standard Protocol
Every agent uses the same secure method
Reusable Data
Enter once, use everywhere
One Vault. Multiple Agents.
Store your data once. Every agent that needs it can request access. Each with its own permissions and limits.
Travel Agent
Shopping Bot
DeFi Agent
Email AI
Payment API
Automation Agent
Same vault. Different permissions. Complete control.
Your travel agent can read passport data but can't touch your wallet. Your DeFi agent can sign transactions but can't see your passport. Each agent gets exactly what it needs — and you approve every request.
How DCP Keeps You Safe
DCP sits between your AI agents and your sensitive data. Agents request, you approve, the vault acts. Your secrets never leave.
Agents Get Results, Not Secrets
Your AI asks to sign a transaction. The vault signs it internally and returns the signature. The private key never leaves the vault — agents get results, not raw keys. For reading operations (like passport data), every request needs your approval.
Set Limits That Actually Work
Per-transaction limits. Daily budgets. Auto-approve thresholds. Session timeouts. Your trading bot can spend 1 SOL per trade, 2 SOL per day — and it physically can't go over.
See Everything Your AI Does
Every action logged. Who requested, what happened, how much, when. Exportable to JSON or CSV. Like a security camera for your AI — but with receipts.
Get Started in 5 Minutes
Download
Get the app. Mac, Windows, or Linux. Double-click to install. Like any normal app.
Create Your Vault
Open the app. Set a password. Write down 12 backup words (keep them safe — this is your recovery key).
Add Your Stuff
Create wallets (Solana, Ethereum, Base). Store API keys, personal info, addresses — whatever you want AI to use.
Connect Your AI
Add one line to connect Claude or Cursor. Or use the CLI, REST API, or SDK for custom agents. When your AI needs something, you'll see a popup: approve or deny.
Download
Get the app. Mac, Windows, or Linux. Double-click to install. Like any normal app.
Create Your Vault
Open the app. Set a password. Write down 12 backup words (keep them safe — this is your recovery key).
Add Your Stuff
Create wallets (Solana, Ethereum, Base). Store API keys, personal info, addresses — whatever you want AI to use.
Connect Your AI
Add one line to connect Claude or Cursor. Or use the CLI, REST API, or SDK for custom agents. When your AI needs something, you'll see a popup: approve or deny.
What You Can Actually Do
AI Trading Bot
The situation
You want a bot to trade crypto automatically. But giving it your wallet key? That's asking for trouble.
With DCP
You set a budget — "max 2 SOL per day, ask me above 0.5 SOL." The bot trades freely within limits. Tries to go over? You get a popup. Tries to drain your wallet? Blocked.
Result
Automated trading with a safety net.
Claude Books Your Flight
The situation
You tell Claude "Book me a flight to Tokyo." But Claude needs your passport info.
With DCP
Claude asks your vault for passport data. You see: "Claude wants to read identity.passport.* — Approve?" You click yes. Claude gets the data (from your local vault, not the cloud) and books the flight. Every request logged.
Result
AI handles real tasks. You control every data access.
Multiple Agents, Different Access
The situation
You use different AI helpers — one for trading, one for emails, one for shopping. Each needs different access.
With DCP
Your trading bot can only sign Solana transactions (max 2 SOL/day). Your email AI can only read your email address. Your shopping AI can spend up to $50 per order. Each agent gets exactly what it needs — nothing more.
Result
A team of AI agents, each with its own permissions.
Agents on a Remote Server
The situation
You run OpenClaw or similar autonomous agents on a VPS 24/7. But you don't want your private keys on a remote server.
With DCP
Your keys stay on your local machine. The VPS agent connects to your vault through an encrypted relay. It sends signing requests, your vault signs locally, results go back. Keys never touch the server.
Result
Remote agents, local keys.
Built So Your Keys Can't Leave
| What Goes Wrong | Without DCP | With DCP |
|---|---|---|
| Agent gets hacked | Attacker has your private keys. Wallet drained. | Attacker has a signed result. Your keys are still locked in the vault. |
| Prompt injection attack | Agent leaks your API keys or passwords | Every access requires your approval. Audit log tracks everything. Crypto keys stay locked — agents get signatures only. |
| Agent goes rogue (spends too much) | No limits. Wallet emptied. | Daily budget enforced. Per-transaction cap. Auto-blocked. |
| Your computer is stolen | Keys are in plaintext config files | Vault is encrypted (XChaCha20). Useless without your passphrase. |
| You lose your password | Keys gone forever | 12-word recovery phrase restores everything |
100% Local
Your vault is a file on your computer. Nothing uploads. Works offline.
You approve every action
Popup for every sensitive request. You decide.
Open source
Every line on GitHub. Apache-2.0. Audit it yourself.
Free forever
No subscription, no tokens, no fees. No catch.
Store Anything. Use Everywhere.
DCP isn't just for crypto wallets. Store API keys, personal info, addresses — anything your AI agents need. Enter once, use across all your agents.
Crypto Wallets
Solana, Ethereum, Base — create or import
API Keys & Tokens
OpenAI, Stripe, AWS, GitHub tokens — agents call APIs on your behalf
Personal Identity
Name, email, phone, passport, driver's license — for bookings and forms
Addresses
Home, work, shipping — for booking and delivery
Health
Blood type, conditions, medications, emergency contact
Custom
Any data you define — your own scopes and fields
Completely Free
DCP is open source under Apache-2.0. No subscription. No transaction fees. No token to buy. No premium tier. The public relay is free (rate-limited). You can self-host everything.
Connect Any Agent in 60 Seconds
Claude Desktop
via MCP
Cursor
via MCP
Custom Agents
via REST API
Trading Bots
via SDK
VPS Agents
via Relay
CLI Automation
Terminal
Simple Integration Example
# Your agent talks to DCP's local vault
import requests
result = requests.post("http://127.0.0.1:8420/v1/vault/sign", json={
"chain": "solana",
"agent_name": "my-trading-bot",
"amount": 1.5,
"currency": "SOL",
"unsigned_tx": "..."
})
# DCP checks your rules, asks for approval if needed
# Returns signed transaction — never the private key
signed_tx = result.json()["signed_tx"]For Developers
Quick Start
# Install CLI npm install -g @dcprotocol/cli # Create vault dcp init # Create wallets dcp create-wallet --chain solana dcp create-wallet --chain ethereum dcp create-wallet --chain base # Store data dcp add identity.email you@example.com dcp add credentials.api.openai sk-... # Start local server npx @dcprotocol/server # runs at http://127.0.0.1:8420
Frequently Asked Questions
A vault on your computer. AI agents ask to use your wallets and data. You approve or deny. They get results, not raw secrets.
All Platforms
Choose your platform and architecture