Swivy
Swop's wallet, login and signing platform for any app. Give every user a wallet at sign-in, approve with a passkey, and offer Sign in with Swop.
Preview: Swivy is not generally available
Swivy runs in staging today. It is not in production, and Swop's own apps still run on Privy while Swivy is prepared to replace it. The SDK packages aren't on npm yet; preview partners get access with their credentials. Anything here can change. Request early access.
Swivy in plain words
Every app that touches crypto needs three things: a way for people to log in, a wallet for each of them, and a safe way to sign what they approve. Most apps rent all three from a wallet provider and pay per user.
Swivy is Swop's own version of that platform. A user signs in with an email code (or an existing wallet), and Swivy gives them an EVM wallet and a Solana wallet on the spot. No seed phrase, no browser extension, no popup. When they do something that moves money, they approve it with a passkey (Face ID, Touch ID or a security key). Your app never holds a private key.
It's built for:
- App developers who want embedded wallets without running key infrastructure.
- Teams moving off Privy who want the same shape of SDK with costs that scale with signing, not head count. See Migrating from Privy.
- AI agents and backend jobs that need to act on a wallet inside limits, without the root key. See Agent session grants.
- Apps in the Swop ecosystem (El Dorado, Chalk, Game Film AI, Decentrabet) that will offer Sign in with Swop so users keep the same wallet everywhere.
What you get
| Capability | What it means |
|---|---|
| Login | Email code, or sign in with an EVM wallet or Phantom. Passkey, TOTP or SMS as a second factor. |
| Wallets at login | One EVM and one Solana wallet per user by default, controlled by your policy. |
| Signing | Messages, EIP-712 typed data and transactions on EVM and Solana, submitted as intents. |
| Custody choice | managed_tee (an isolated signer holds the key) or split_custody (the user's browser holds a share). See Concepts. |
| Gas sponsorship | Pay your users' network fees per network, with spend caps. See Gas sponsorship. |
| Your own RPC | Each environment routes each network to the RPC you choose, including Swop RPC. |
| Webhooks | A signed callback when an intent completes. See Webhooks. |
| Agent session grants | Scoped, expiring access for AI agents, approved by the user. |
| Sign in with Swop | A standard OpenID Connect provider, so other apps can log users in with Swop and get the same wallet. |
How it's organised
| Term | What it is |
|---|---|
| Organization | Your company. |
| Project | One user and wallet graph. Environments in the same project share users and wallets. |
| Environment | One deployable app inside a project (for example swop and streamey), with its own credentials, policy, networks, webhooks and audit log. |
| App credentials | appId + publishableKey for browsers and phones; appId + secretKey for servers. Organization admin credentials (x-swivy-admin-key) manage everything else. |
Start here
Concepts
Accounts, custody modes, policies, intents and step-up approval.
React quickstart
Email login, a wallet, a passkey and a first transaction.
Expo quickstart
The same flow on iOS and Android.
Node backend
Sessions, wallets, intents and RPC config from your server.
Sign in with Swop
OpenID Connect so users log in to your app with Swop.
Wallets & signing
Messages, typed data, transactions and the intent lifecycle.
API reference
77 endpoints, generated from Swivy's OpenAPI document.
Status & roadmap
What runs today and what comes before general availability.