Skip to main content

Overview

Morpheum exposes SDK-style surfaces at different layers: chain and product APIs (morpheum-sdk for Rust, morpheum-sdk-ts for TypeScript), a WASM agent runtime (MWVM), and protocol gateways for tools and payments. Use this page to pick the right path and jump to the detailed guides.

Morpheum SDK (Rust + TypeScript)

The product API is implemented as a Rust workspace and a TypeScript package in separate repositories. Capabilities align across stacks (signing, markets, VCs, transport), but install paths and docs live with each repo.
LanguageRepositoryNotes
Rustmorpheum-sdkNative CLI, bots, and agents; morpheum-sdk-native and feature-gated crates (market, vc, auth).
TypeScriptmorpheum-sdk-tsBrowser and Node; same conceptual API surface as the Rust SDK.
TopicNotes
FacadeUnified MorpheumSdk entry point for operations across the stack.
SignersNativeSigner, AgentSigner (with TradingKeyClaim), MetaMask, Phantom, Taproot, and related flows.
CapabilitiesSign transactions, issue/revoke VCs, create markets, and more—via fluent builders and pluggable gRPC + HTTP transport.
ModulesRust: feature-gated crates so you compile only what you need.
Rust — upstream docs: README, API Reference, Full guide, Architecture. TypeScript — upstream docs: morpheum-sdk-ts — start with the repo README. Installation (Cargo for Rust, npm for TypeScript), versions, and feature flags are documented in each repo’s README.

Agent runtime (MWVM)

MWVM is the primary SDK for building and running Morpheum agents with chain-parity WASM. It ships Rust and TypeScript entry points on top of the same guest ABI and host capabilities.
SurfaceRole
Rustmwvm::AgentRuntime::new() — async host calls; backends, CLIs, embedded runners.
TypeScriptmwvm-js — WASM bindings for browsers and Node-style environments.
For wasmtime, inference, simulation, orchestration, and gateways (MCP, A2A, DID, x402), see MWVM.

Wallets and signing

To fund execution paths and sign where your stack requires it, use Agent wallet and the Signing guides (Ethereum, Solana, Bitcoin, Morpheum, and related topics). For programmatic signing and claims in app code, use morpheum-sdk (Rust) or morpheum-sdk-ts (TypeScript) where it matches your stack.

APIs and automation

  • MCP — Model Context Protocol for tools, editors, and agent automation.
  • x402 — HTTP 402–style paid APIs and metered access; start from the x402 overview and cross-chain where relevant.

Next steps