Para: MPC wallet-as-a-service for apps and agents

Para (getpara.com, @get_para) is wallet-as-a-service for fintech and crypto apps: embedded, non-custodial MPC wallets with familiar login (email, social, passkey), multi-chain signing, and a backend REST API for agents and automation.

Docs (v3): docs.getpara.com (llms.txt). Developer portal: developer.getpara.com. GitHub: github.com/getpara. Demo: demo.getpara.com.

Click to zoom

Custody model

Per architecture docs: 2-of-2 MPC — key material split between the user’s device and Para HSMs. Full private key is never assembled in one place; user shares stay encrypted on-device. Para positions this as self-custodial / non-custodial for the app (you don’t hold user funds). SOC 2 Type II claimed; audit requests via [email protected].

Always validate the model against your counsel and Para’s current legal docs — MPC WaaS classifications vary by jurisdiction.

Integration paths

SDK matrix (pin same version)

All @getpara/* packages should share one release version.

# Core (pick one runtime)
npm i @getpara/react-sdk @tanstack/react-query   # React/Next + ParaProvider/hooks/modal
# @getpara/web-sdk          # Vue/Svelte imperative ParaWeb
# @getpara/server-sdk       # Node/Bun/Deno
# @getpara/react-native-wallet

# Chain signing helpers
npm i @getpara/solana-web3.js-v1-integration @solana/web3.js
# @getpara/viem-v2-integration | ethers-v6 | cosmjs-v0-integration
# Connectors: wagmi-v2, rainbowkit-wallet, solana-wallet-connectors, …

// Minimal React sketch — keys from developer portal
"use client"
import { QueryClient, QueryClientProvider } from "@tanstack/react-query"
import { Environment, ParaProvider } from "@getpara/react-sdk"

const queryClient = new QueryClient()

export function Providers({ children }: { children: React.ReactNode }) {
  return (
    <QueryClientProvider client={queryClient}>
      <ParaProvider
        paraClientConfig={{
          apiKey: process.env.NEXT_PUBLIC_PARA_API_KEY!,
          env: Environment.BETA, // or production per portal
        }}
      >
        {children}
      </ParaProvider>
    </QueryClientProvider>
  )
}

Follow the official React quickstart for modal open, session, and signing hooks — APIs evolve by minor version.

Chains

Docs list native support for EVM, Solana, Cosmos (via CosmJS), Stellar, and more on the chain support table (Solana mainnet + devnet called out; many EVM L2s). Add extra EVM chains via chain ID + RPC when supported by the product config.

REST API (backend & agents)

• Create MPC wallets programmatically (pregen or on demand)
• Policies — spend limits, allowlists, approvals at the MPC signing layer
• Sign txs/messages server-side without browser extension
• Ops — API keys, IP allowlists; free tier RPM called out on marketing (confirm current limits in portal)

Agent pattern: one wallet per agent + cryptographic guardrails (limits) — see Para’s agentic/x402 case studies on the blog. Pair with your own policy engine; don’t rely on the model prompt as the only control plane.

Other builder features

• Wallet pregeneration — allocate addresses before first login
• Account abstraction — ERC-4337 / EIP-7702 companions (Alchemy, ZeroDev, Gelato, …)
• Telegram bots & mini-apps guides
• Webhooks, user data, production checklist, iOS store notes
• CLI for scripting (CLI overview)

When to use

Links

• getpara.com
• Docs
• Developer portal
• @get_para
• github.com/getpara
• Blog

Summary

Para is MPC embedded-wallet infrastructure: ship login + wallets via Modal or custom UI, sign on Solana/EVM/Cosmos with official integrations, and use the REST API when the signer is a backend or agent under policy. Start in the developer portal, pin matching @getpara/* versions, and read key-management + architecture docs before production.