Project login providers
Any valid server-side project API key can list its project’s login providers and enable an eligible one. The setting applies to every app in the project across networks.SDK examples
Endpoints
Returned result
The list returns aproviders array in ProtoJSON. The SDK returns that array directly. Each entry includes providerKey, label, enabled (the project’s setting) and eligible (the current plan includes it). Activation wraps the selected provider in the provider field. The SDK returns that provider directly with enabled: true. Calling it again preserves the project’s existing settings. Swig manages upstream provider configuration and credentials.
Errors
Register an email wallet app
POST /identity/api/email-wallet-apps/ensure creates the registration or returns the same client ID when all settings match. Enable the project’s email provider first using swig.idp.enableProvider("email").
The response contains the public
clientId, registered callback, template ID, agent public key and, when selected, project paymaster address. The verified email determines the wallet address before the user approves creation.
Who owns identity integration
The IDP SDK owns identity integration guidance: OAuth, email OTP, SMS OTP, session handling, and how a completed login becomes a Swig session. Once a user has a session, the Developer SDK picks it up:TypeScript
Public IdP routes
These routes are public. They are listed here as the current backend contract.
The JWKS routes are what you use to verify identity tokens server-side.
For client wallet lookup and status, see the public wallet boundary.
Request accounting is covered in Pricing & quotas.
Why this matters
- Do not send a Swig API key to these routes. They are not API-key guarded, and doing so leaks a server credential into a client-facing call path.
- Do not model login as a server-to-server call. The user’s client completes the flow; your server verifies the result.
- A project API key can manage provider enablement through the project login provider endpoints above.
What is not here
There is no/identity/api/auth/passkey/start route. If you have an
integration pointed at that path, it is targeting an endpoint that does not
exist in the current backend.
Where to go instead
IDP SDK
OAuth and OTP login flows that create Swig sessions

