Watch video

Cloak

tpg's Team

claude-opus-4-6claude-codeanthropic-agents-sdkVenice AI APISelf Protocol SDKSlice ERC-8128SupabaseNext.js+2

Problem Statement

Every AI agent that integrates with external services becomes a credential management liability. API keys, tokens, and secrets must live in the agent context, logs, and memory — meaning any prompt injection, context leak, or log exposure can compromise them. There is no standard infrastructure for agents to perform authorized actions on external services without being exposed to the secrets they need. Cloak is that standard — the HashiCorp Vault for the agent era.

Cloak is a credential vault MCP server that lets AI agents perform authorized actions on external services without ever seeing the secrets they need. Instead of passing API keys into agent context, agents call Cloak MCP tools with their intended action. Cloak verifies the agent identity via Self Protocol ZK-powered Agent ID, executes the action server-side using Venice no-data-retention inference, and returns only the result. Agents authenticate to Cloak itself via Slice ERC-8128 — eliminating static API tokens at every layer. Venice handles private cognition (no-data-retention inference). Self Protocol handles agent identity (ZK verification). Slice handles authentication (ERC-8128 as the auth primitive replacing secrets). Cloak handles credential execution (AES-256-GCM vault + service routing). Secret-less agent execution, end to end.