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

Preview setup & SDK 1.0.1

Create a testnet project, configure login, and install the published SDKs.

Swivy is a staging/testnet preview using software custody. Use test assets only. Production enclave custody and recovery remain separate release gates.

For the complete console walkthrough, start with Create your first project. For device or delivery issues, see Troubleshooting.

Open your project

  1. Open the Swivy dashboard and create a project. Choose wallet types and test networks.
  2. Add your operator passkey or YubiKey in Account security. Protected settings require passkey approval.
  3. Choose email or SMS for initial customer signup, and configure customer passkeys after enrollment in the app's settings. Configure delivery for the methods you enable. Hosted login follows those settings; console sign-in is separate.
  4. Open Integrations for the API base URL and configured examples. Copy the App ID and publishable key into your frontend. Keep secret keys on your server.
  5. Test customer login, create a test wallet, and confirm the identity and wallet appear in Users and Wallets. Check allowed origins, redirect URLs, network/RPC settings and audit events.

The dashboard alias is not a replacement for the API base URL in your environment. The live developer reference and OpenAPI JSON are public.

Install the published SDKs

All six packages are published at 1.0.1 under next. The latest tag remains 1.0.0, so pin the preview version explicitly:

# React / browser
npm install @swivy/react@1.0.1 @swivy/web@1.0.1
# Server (Node 22)
npm install @swivy/node@1.0.1
# Optional integrations — install only what your app needs
npm install @swivy/expo@1.0.1 @swivy/viem@1.0.1
# Shared types and utilities
npm install @swivy/core@1.0.1

Node SDK consumer dependency policy

Before installing @swivy/node, merge this into your application's root package.json:

{
  "overrides": {
    "ws@>=8.0.0 <9.0.0": "^8.21.0"
  }
}

The preview's legacy trading provider pins an older WebSocket 8 dependency. Library overrides do not propagate to consumers. This rule keeps WebSocket 7 dependencies on their existing major. Commit the resulting lockfile and run your application's integration tests and dependency audit.

Continue with the React quickstart, Expo quickstart, Node guide, or MCP setup.

Troubleshooting setup

  • No customer code: check that the method is enabled for the environment and its delivery provider is configured; check provider delivery and spam folders.
  • Passkey not found: passkeys are bound to their registration site. Sign in normally, then enroll on the current console domain.
  • Project creation interrupted: check Overview before retrying; the project may already have been created.
  • Delegated limits rejected: confirm the API and worker both support schema 21, and inspect the returned scope. Updating an SDK does not upgrade server enforcement.

On this page