docs
Get startedTroubleshootingPaymentsWebhooksAgent paymentsSwop MCPOviIdentity (swop.id)SwivyRPC (preview)API reference

Create your first project

Set up Swivy, secure your console account, connect your app and verify your first customer login.

Swivy's console is a testnet preview with software custody. Use test assets only. Project creation and passing tests do not certify production readiness.

1. Create your project

Open the Swivy console and sign in. On Overview, choose Create your first project.

  1. Name the app and choose self-custody wallets, managed agent wallets, or both.
  2. Choose the chain families and test networks your app needs. Start with Base Sepolia or Solana Devnet.
  3. Enable email or SMS for initial customer signup. Passkey approval alone is not an initial signup channel.
  4. Review the choices and save. Setup creates the organization, project, environment, credentials, policy and selected RPC routes. A new environment defaults to development unless you explicitly name it.
  5. Add a passkey for your console account, or continue to Account security to finish enrollment later.

If saving fails, the setup dialog keeps the error visible and allows retrying. After a network interruption, check Overview before retrying: the project may already exist.

2. Secure your console account

Your console account administers Swivy. Your customers sign in to your app. These are separate identities and enrollment flows.

In Account security, use Add security key for a YubiKey, or Add passkey for a device credential. Complete the browser's PIN/touch or biometric prompt. Protected settings still require passkey approval if you skipped this step during setup.

Use the same console hostname when enrolling and signing in: WebAuthn credentials are bound to their relying-party domain. See passkey troubleshooting.

3. Connect your app

Select your project and environment, then open Integrations for configured snippets. API keys holds your App ID and credentials.

ValueWhere it belongs
App ID and publishable keyBrowser or mobile app
Secret keyBackend only
Organization admin credentialTrusted administration only

Use the API base URL from your integration bundle. The console URL and documentation URL are not interchangeable with the API base URL.

npm install @swivy/react@1.0.1 @swivy/web@1.0.1
# Backend
npm install @swivy/node@1.0.1

SDK 1.0.1 is published under npm's next tag; latest remains 1.0.0. Pin the version for repeatable preview integrations. All six packages—core, web, react, expo, node and viem—have version 1.0.1. Use Node 22 for backend integrations.

Before installing the Node SDK, apply the consumer dependency policy.

Continue with React, Expo, or Node.

4. Configure delivery and origins

Configure Email delivery or your SMS provider for the customer login method you enabled. A working console email login does not prove that customer delivery works for your environment.

Check app settings, allowed origins, redirect URLs, session policies, wallet policies and RPC routes for the selected environment. Keep browser keys and server keys separate.

5. Verify a complete customer flow

Use Authentication to test customer sign-in, then repeat from your actual app:

  • Request a code and confirm receipt through the configured delivery provider.
  • Verify it and confirm a customer session is created.
  • Create a wallet on an enabled test network; confirm it in Users and Wallets.
  • Enroll a customer passkey and complete a protected action using test assets.
  • Confirm the resulting intent and audit event; test sign-out and recovery.
  • If you use webhooks, confirm delivery and retry behavior at your receiver.

A browser mock cannot verify physical YubiKey touch, inbox/SMS delivery, external RPC behavior, or production custody. Those require their respective live checks. Review status and release boundaries before launch.

On this page