Choose a Product

Swig has five product surfaces. Choose the one that matches how your app will integrate.

Quick routing

If you are trying to…	Start here
Understand the on-chain protocol and repo layout	Swig Protocol
Integrate directly with Swig wallets from TypeScript or Rust	Swig Protocol SDK
Prepare wallet operations and submit signed transactions from a trusted server	Swig Developer SDK
Call hosted backend endpoints directly over REST	Swig Developer API
Add OAuth, email OTP, or SMS OTP login flows	Swig IDP SDK

The on-chain wallet system in swig-wallet.

Use it when you need to understand permissions, sessions, recovery, or program behavior.
Start at Protocol.

Direct TypeScript and Rust integrations with the protocol.

Use it when your app talks to Swig wallets directly and controls its own authority or signing flows.
Start at Protocol SDK.

Hosted transaction preparation through @swig-wallet/developer-sdk (TypeScript) and swig-developer-sdk (Python).

Use it when a trusted backend should prepare wallet creation, transfers, swaps, reads, or fiat ramps and submit transactions signed by application-owned wallet or custody code.
Start at Developer SDK.

REST access to Swig’s hosted backend services.

Use it when you need exact endpoint paths, payloads, response fields, or direct API integration without SDK wrappers.
Start at Developer API.

Use it when you need OAuth or OTP sign-in that creates Swig sessions for web or Expo apps.
Start at IDP SDK.

The Swig Protocol is the on-chain foundation.
The Swig Protocol SDK integrates with that protocol directly.
The Swig Developer SDK uses hosted backend services to prepare and operate on Swig wallets through API-key access.
The Swig Developer API documents the REST endpoints exposed by those hosted backend services.
The Swig IDP SDK handles end-user identity and session bootstrap for login-provider flows.