Launched this week

tryvault.xyz by Swarm Network
Stop giving AI agents your API keys in plaintext > Use Vault
20 followers
Stop giving AI agents your API keys in plaintext > Use Vault
20 followers
If you are building AI agents, you are probably storing your API keys inenv files. That is a massive security risk. Vault is the missing security layer for the agentic revolution. It gives your AI agents their own cryptographic identity. Instead of sharing a master key, your agent fetches only the specific encrypted secrets it needs at runtime. It is zero-knowledge, built on Sui, and plugs directly into OpenClaw, CrewAI, LangGraph, or any framework you use.








What happens if an agent's cryptographic identity gets compromised, is there a way to revoke and rotate keys without downtime? Super relevant problem, congrats!
This is a really interesting direction.
One thing we’ve seen building agent-driven workflows is that the security model usually breaks down not at storage, but at execution — especially once agents start chaining actions across systems.
Curious how you’re thinking about scoped access and revocation in multi-step workflows?