Para
Para Technical Briefing
Published May 5, 2026
Overview
Para's Nitya Subramanian demos Para's wallet infrastructure for agentic commerce at Day Zero 06, framed around three problems with agentic payments today: hard wallet UX, plain-text private keys, and missing guardrails. Paramodal turns email verification into a fully functional wallet in seconds. The REST API provisions agent wallets with IP allowlists so a wallet for an OpenWebUI agent on a single Mac mini can only be exercised from that exact IP, then signs messages and raw transactions across Solana, Stellar, EVM, and Cosmos. Para's permissions feature enforces app-wide policies — scopes for transfers and signing, conditions like 'transaction amount < 1', plus distinct bypass and autonomous-with-policy modes for agents — at the MPC cryptography layer rather than in app code. Modular Para clients can be wrapped with x402 or MPP forwarders to slot directly into agent-payment flows.
0:00 Para — wallet infrastructure for agentic commerce
Nitya Subramanian opens with Para's pitch: wallet infrastructure that abstracts away the complexity of authentication and on-chain interaction so any company can offer wallets to users (or agents) without building it from scratch.
0:30 Modular wallets wrapped by x402 / MPP forwarders
Para's clients are modular by design — you can wrap them with x402 or MPP-compatible forwarders to slot directly into agentic-payment flows like the ones James (Stellar) and Jeff (Stable Coin Company) demoed earlier in the session.
0:50 Three problems with agentic commerce
Wallets are hard to use, agents often need access to private keys in plain text, and once an agent is loose there are no guardrails. Para has three product surfaces that address each problem.
1:20 Paramodal — email-to-wallet in seconds
Live Paramodal demo: enter an email, verify, and a fully functional wallet appears with an address, top-up, and asset list. The "log into a website" UX replaces seed phrases for end users.
2:00 REST API for agent wallets — IP allowlists
For agents, the REST API creates wallets without OAuth or email credentials. IP allowlisting means a wallet provisioned for an OpenWebUI agent on a Mac mini can only be exercised from that exact IP — sharply limits compromise blast radius.
2:40 Create a wallet via API key
Live: a one-time developer-portal API key creates a new wallet, picks the wallet type, returns a wallet ID and address. The same API wallet can later be upgraded to an authenticated user wallet seamlessly.
4:00 Sign a message — multi-chain signature
"hello day zero" gets signed via the same API key path. The returned signature is valid for Solana, Stellar, EVM, Cosmos — and a sign-raw capability lets agents sign just about any transaction shape.
5:00 Guardrails — recent multi-million-dollar agent rug
A trading bot recently accumulated 7–8 figures in PnL and then shipped the entire balance to an unknown address. Cautionary tale that motivates Para's permissions feature.
5:30 Permissions — app-wide policies with scopes
Permissions are app- or project-wide policies built from scopes (think OAuth-style permission requests). Each scope groups granular sub-capabilities and supports lists of conditions that must all evaluate true for a transaction to pass.
6:30 Bypass vs autonomous-with-policy
Two agent capabilities: one-time human bypass for a specific transaction outside the policy, or autonomous-with-policy where the agent transacts freely inside the policy envelope. Enforced at the MPC layer, not in app code.
7:00 Permissions builder — transfers + signing scopes
Live walk-through of the permissions builder as Acme Corp: select Ethereum and Polygon, add a transfers scope with a "transaction amount < 1" condition, then add a signing scope for messages. Final policy applies to every wallet under the project.
Presented by Nitya Subramanian — Para · website
Topics: Wallets
