HomeWith Turnkey, you can provision a dedicated wallet for every user as part of your application’s signup flow, at any scale. Users authenticate with familiar methods like passkeys, email, or social login. They never manage keys or install extensions.Documentation Index
Fetch the complete documentation index at: https://turnkey-0e7c1f5b-graham-docs-revamp.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
Powered by Turnkey
- Moonshot — millions of self-custodial wallets powering one of crypto’s fastest-growing consumer apps
- Infinex — seamless onchain UX for a unified DeFi experience
- Axiom — global DeFi trading platform with embedded wallet infrastructure
Key implementation decisions
Turnkey enables developers to tailor non-custodial, embedded user wallets across dimensions such as custody model, authentication, and more. See the key implementation decisions below to curate the exact user experience you need.| Decision | Explanation | Learn more |
|---|---|---|
| Custody model | Choose who can authorize the enclave to sign: the user only (non-custodial), your application (custodial), or both with scoped permissions (hybrid). | Custody models |
| Authentication methods | Choose user auth methods: Passkeys, OAuth/email, or SMS. You can use the Auth Proxy for backend-signed OTP/OAuth/signup without your own backend, or wire auth to your app. | Authentication Overview, Auth Proxy |
| Policies and guardrails | Set guardrails for what your end users can do, such as spending limits, allowed destinations, or multi-party approval. Optionally let users configure their own guardrails within your app. | Policies, Delegated Access |
| Session management | Allow a user to take multiple, contiguous actions in a defined period of time. Actions include: Read-write or read-only. | Sessions |
| Wallet architecture | Choose between key-based (HD) or smart contract wallets for your users. Turnkey supports both. | Wallets Concept, Transaction Management |
| Gas sponsorship | Integrate a gasless UX via sponsored transactions to cover who pays gas and how transactions are broadcast. | Transaction Management, Sending sponsored transactions |
| Key portability | Determine whether users can import or export keys. | Import wallets, Export wallets |
| Recovery flows | Define how users regain access if they lose their authenticator. Options include email recovery and backup passkeys. | Email recovery |
| Agent-delegated signing | Let end users grant scoped signing authority to AI agents or automated systems from their own wallet. The user retains root control and can revoke access at any time. | End-User Delegated Agent Signing |
Example: Neobank-style embedded consumer wallet
Typical requirements and how Turnkey addresses them:| Requirement | Turnkey capability |
|---|---|
| Seamless onboarding | Passkey registration and automated wallet provisioning. See Quickstart or Integration Guide |
| User custody without key exposure | Keys remain in secure enclaves; only signatures are returned. See Security |
| Gasless UX | Sponsored transactions and sending sponsored transactions |
| Email-based auth and recovery | Sub-organization recovery |
| Send without wallet setup | Claim links: send via URL; recipient claims with email |
| Backend automation | Delegated access and scoped signing policies |
| Multichain support | Chain-agnostic derivation and signing. See Networks and Wallets Concept |
| Fast integration | Use the Embedded Wallet Kit for built-in auth and wallet UI components. See Quickstart |