Launching today
DCP
Give your AI agents encrypted permission and keys
18 followers
Give your AI agents encrypted permission and keys
18 followers
Today, many agents read keys and sensitive info from dotenv files, configs, or memory. One bad prompt or compromised tool can drain your wallet, API bill, or private data. DCP makes agents safe for real work: your wallets and API keys stay encrypted on your own machine. Give each agent only the scopes it needs; it asks, you approve from Telegram or App. Daily budgets, logs, and instant revoke keep you in control. Open source, non-custodial, and works with Claude, Cursor, OpenClaw, and Hermes.
DCP
Hey PH! I’m Iftakhar, building DCP.
AI agents are moving from answering questions to executing real work: signing transactions, using API keys, making payments, and calling tools across apps.
But there’s a problem: agents should not hold private keys, raw credentials, or sensitive information.
DCP is my attempt to solve that. It is a local permission vault for AI agents.
The flow is simple:
agent asks
you approve on Telegram or in the app
DCP signs locally
secret never enters the model context
What works today:
- desktop app
- local encrypted vault
- Telegram approvals
- Solana wallet signing
- API credential storage
- budgets and approval limits
- MCP-compatible agent flow
- open source repo
I built this because I think the next bottleneck for agents is not intelligence. It is permission.
If agents are going to act for us, they need a safe way to use wallets, credentials, and sensitive tools without taking custody.
Would love feedback from people building agents, wallets, MCP tools, x402 apps, or anything around agent commerce.
Website: https://dcpagent.com
Docs: https://dcpagent.com/docs
Download: https://dcpagent.com/#download
GitHub: https://github.com/1lystore/dcp
the harder question underneath this product is whether detecting AI use in a technical interview is actually the right goal. a senior engineer who knows how to use AI tools effectively might be more valuable than one who can whiteboard without them. curious if there's a way to configure what counts as unauthorized versus what's just how people actually work now