Developer Platform

Product SDKs & APIs

Integrate every layer of the Soulverse architecture into your applications. Each SDK maps to a specific component and architecture layer with typed interfaces, documented endpoints, and language bindings.

From DID lifecycle management to Trust Protocol enforcement to browser-native identity verification, the SDKs provide programmatic access to the full Soulverse stack.

10

Product SDKs

58+

API Endpoints

6

Language Bindings

Architecture Mapping

Each SDK maps to a specific architecture layer and component.

Layer 01 - Identity

Soul ID SDK

DID creation, resolution, and key management

Layer 02 - Credential

Credential SDK + Soulogram SDK

VC issuance, verification, and encrypted transport

Layer 03 - Trust Graph

Trust Protocol SDK + Trust Engine SDK

Dynamic scoring, rule authoring, and enforcement

Layer 04 - Execution

Soulwrapper SDK + Soul AI Agent SDK

ZKP verification and credential-gated agent execution

Cross-Layer

Soulbridge SDK

Multi-chain DID resolution and credential portability

Client

Wallet SDK + Chrome Extension SDK

Wallet integration, browser-native verification

SDK Reference

Explore each SDK's endpoints, capabilities, and quick start code.

Filter by category or browse all SDKs. Expand any card to view API endpoints and integration code.

Integration Philosophy

Your infrastructure stays. Soulverse layers on top.

Every SDK is designed to integrate alongside existing systems, not replace them. Identity databases, authentication flows, and business logic remain intact. SDKs add verifiable identity, credential-gated execution, and cross-border trust capabilities through standard API interfaces.

Non-Invasive

Existing databases, auth systems, and APIs continue operating. SDKs add capabilities without requiring system replacement.

Standards-Based

W3C VC 2.0, W3C DID 1.0, ISO 18013-5, SD-JWT. Every SDK uses open standards rather than proprietary formats.

Composable

Use a single SDK or compose multiple. Each operates independently while sharing the same DID and credential model.