Para
MPC agent wallets and transaction permissions
REST-based agent wallets with MPC signing and configurable transaction permissions.
THE QUESTION IT ADDRESSES
How can a backend let an agent sign within configured transaction permissions?
A concise reading of published information. The explanatory grouping below is editorial, not an implementation test.
A simplified mechanism
- Create a wallet and configure transfer, chain and spending conditions.
- Use REST signing with the provider’s access controls.
What it does not establish
These are provider-described capabilities, not an independent test. Funding, off-ramp partners and payment-protocol adapters require separate integration checks.
Where it fits
Para is the current name of Capsule, not an additional duplicate product. It supplies wallet infrastructure beneath agent applications.
Sources & further reading
Sources reviewed on2026-11-01. Summaries are paraphrased; follow the current source for changes.
EDITORIAL ARTICLES
Read more about this project
Para: Agent Wallet Permissions Depend on Ownership and What the Signer Can Read
Examine Para’s app-owned and user-owned wallet policies, decoded-transaction limits, budget windows and production review before automating payments.