Company Wallets are built for teams that need to automate high-volume signing workflows — treasury operations, deployers, rebalancers, payment rails — without giving up granular control over who can sign what.Documentation Index
Fetch the complete documentation index at: https://docs.0xkey.io/llms.txt
Use this file to discover all available pages before exploring further.
What Company Wallets will provide
| Capability | Description |
|---|---|
| Role-based access | Separate users, API keys, and policies for operators, approvers, and services |
| Multi-party approvals | Root quorum and policy consensus for sensitive activities |
| Signing automation | Server-side SDKs and policies for batch jobs, sweeps, and programmatic flows |
| Co-signing | Shared custody models requiring both user and backend approval |
| Import / export | Migrate existing keys and HD wallets into isolated org structures |
Shared building blocks today
Company Wallets will build on capabilities documented under Developers → Policies and Crypto ecosystems — already available in Phase 1:- Policies — CEL rules with EVM, Solana, and EIP-712 contexts
- Delegated access — narrow backend signing permissions
- Root quorum — multi-user approval thresholds
- Pending activities — approve / reject in the Dashboard
- Server SDKs — SDK reference tab (
@0xkey-io/sdk-server, Go examples)
Embedded Wallets vs Company Wallets
| Embedded Wallets | Company Wallets | |
|---|---|---|
| Primary user | End users in your app | Your team / backend services |
| Org model | Sub-org per user | Parent org automation |
| Auth surface | Passkey, OTP, OAuth via Auth Proxy | API keys, passkeys, co-signers |
| Phase 1 | Supported | Coming soon |
SDKs (server-side)
When Company Wallets ship, expect first-class support in:- TypeScript server packages —
@0xkey-io/sdk-server,@0xkey-io/core - Go SDK — examples for delegated access and transaction management