Skip to main content

Introduction

1claw is a cloud-hosted Hardware Security Module (HSM) secrets manager for humans and AI agents. It lets you store API keys, tokens, and other credentials in a vault encrypted by keys that never leave the HSM. You control which agents can access which secrets, with what permissions, and for how long — and agents fetch secrets at runtime instead of holding them in context or environment.

Try it out

Try out the examples in this repo: Basic (vault, secrets, billing, sharing), LangChain Agent (agent + vault), Shroud Demo (LLM proxy + Intents). See the examples README for the full list.

Products

1claw is built around these products (they work together):

ProductWhat it doesDocs
VaultStore and manage secrets; Human API, Agent API, and MCP for just-in-time secret accessVaults →
AgentsRegister agents, Shroud LLM proxy, Intents signing, memory, channelsAgents →
ShroudLLM proxy that inspects and redacts before forwarding to OpenAI, Anthropic, Google (Gemini), and othersShroud →
IntentsLet agents sign and broadcast blockchain transactions without ever seeing private keysIntents →
TreasuryNative multi-chain wallets, embedded wallets, Safe multisigs, and policy engineTreasury →
AutomationsCron, webhook, and event-driven workflowsAutomations →
RuntimesManaged containers for agents with optional public hostingRuntimes →
CardsAgent-ordered prepaid/gift cards via x402 (PAN never exposed)Cards →
Platform APIBuild products on 1Claw with bootstrap templatesPlatform →
DashboardWeb UI at 1claw.xyz for humansDashboard →
  • Vault is the core: dashboard, REST API, MCP server, CLI, and SDKs all talk to the same vault. Create vaults, store secrets at paths, register agents, and attach policies that grant read/write access. Advanced encryption options include CMEK (client-side encryption layer) and MPC (split DEKs across multiple HSM providers so no single provider holds the complete key).
  • Shroud sits between your agent and the LLM provider. Send requests to shroud.1claw.xyz instead of directly to the provider; Shroud enforces policies, redacts secrets, and detects prompt injection.
  • Intents extends the vault with transaction signing. Enable the Intents API on an agent; the agent submits transaction intents; the server signs in the HSM (or in Shroud’s TEE) and broadcasts. The private key never leaves the vault.
  • Treasury provides native multi-chain wallet generation (Ethereum, Bitcoin, Solana, XRP, Cardano, Tron) for human users and tracks onchain multisig treasuries with agent access requests.

Task walkthroughs (setup, billing, compliance, troubleshooting) live under Guides. Product docs are organized by area in the sidebar.

How to navigate these docs

SectionStart here
VaultsSecrets, policies, CMEK, MPC, Human API, MCP
AgentsLifecycle, Shroud, Intents, memory, channels
AutomationsWorkflow spec, triggers, presets
RuntimesContainers, hosting, shell
Cardsx402 card ordering and guardrails
TreasuryWallets, embedded wallets, approvals, Cedar/OPA
SharingShare links and inbound flow
Risk EngineAdaptive auth scoring, honeytokens
Platform APIApps, templates, bootstrap, webhooks
DashboardWeb UI walkthrough
GuidesCross-cutting workflows
SDKsTypeScript, Python, Go, curl
IntegrationsLangChain, MCP, migrations
SecurityHSM, zero-trust, compliance
ReferenceAPI reference, glossary, changelog

Architecture

┌─────────────┐     ┌─────────────┐     ┌─────────────┐
│ Dashboard │────▶│ Vault API │◀────│ MCP Server │
│ (Next.js) │ │ (Rust) │ │ (Node.js) │
│ 1claw.xyz │ │ api.1claw.xyz │ mcp.1claw.xyz
└─────────────┘ └──────┬──────┘ └─────────────┘

┌────────────┼────────────┐
▼ ▼ ▼
┌──────────┐ ┌──────┐ ┌──────────┐
│ Supabase │ │ KMS │ │ Audit │
│ Postgres │ │(keys)│ │ (log) │
└──────────┘ └──────┘ └──────────┘


┌────────┴────────┐
│ Mobile App │
│ (Expo/RN) │
│ iOS + Android │
└─────────────────┘
  • Dashboard — The web UI at 1claw.xyz where humans manage vaults, secrets, agents, and policies.
  • Vault API — The Rust backend that handles authentication, envelope encryption, policy enforcement, and all CRUD operations. Both the dashboard and MCP server talk to it.
  • Shroud — Optional LLM proxy at shroud.1claw.xyz; agents can send LLM traffic through Shroud for inspection and redaction. Transaction signing can also run in Shroud’s TEE.
  • MCP Server — A Model Context Protocol server that gives AI agents (Claude, Cursor, GPT) just-in-time access to vault secrets and Intents. Hosted at mcp.1claw.xyz or run locally.

How humans and agents interact

  • Humans log in (email/password or Google) or use a personal API key (1ck_). They create vaults, store secrets at paths, register agents, and attach policies that grant agents (or users) read/write access to path patterns.
  • Agents authenticate with an agent API key (ocv_) via POST /v1/auth/agent-token to get a short-lived JWT, then call the same API to list secrets and fetch secret values by path. Access is enforced by policies; all access is audited.

Two APIs, one base URL

The same REST API serves both personas:

PersonaAuthTypical operations
HumanEmail/password or Google → JWT; or personal API key → JWTCreate vaults, PUT/GET/DELETE secrets, create/list policies, register agents, audit logs
AgentAgent API key → JWT via /v1/auth/agent-tokenGET secret by path, list secrets in a vault (subject to policies)

Base URL: https://api.1claw.xyz (or your Cloud Run URL). The dashboard at 1claw.xyz proxies /api/v1/* to the same API.

Next steps

  • What is 1claw? — Core concepts in more detail.
  • Parts of 1claw — Three products (Vault, Shroud, Intents) and how to use them (Dashboard, API, MCP, CLI, SDK).
  • Quickstart — Fastest path: 1claw setup, human path, or agent path.
  • Shroud — Route LLM traffic through Shroud for inspection and redaction.
  • Intents API — Let agents sign transactions without seeing keys.
  • Glossary — Definitions of vault, secret, policy, agent, and other terms.