EDITORIAL ARTICLE
Cobo Agentic Wallet: Giving an Agent Enforceable Permissions with Pact
Product analysis · Sources reviewed October 28, 2026. Based on Cobo’s public materials. We did not create a wallet or make a transaction.
A user asks an on-chain agent to check funds each day and make small swaps under specified conditions. They want automation without giving the agent unlimited control of the entire wallet.
Cobo Agentic Wallet’s central design is for a person to approve a Pact defining a purpose and permissions, after which the agent can request transactions within that scope. It combines an on-chain wallet, signing, authorization and mobile governance. Cobo Agentic Wallet
Cobo’s background
Cobo provides digital-asset wallet and custody infrastructure and says it was founded in 2017. Agentic Wallet extends its existing MPC signing and wallet-management capabilities to users and teams who want agents to perform on-chain actions. Product announcement
MPC (multi-party computation) can enable parties to cooperate on signing without giving the agent a complete private key. Its security boundary depends on the participants, key shares, policies and recovery design. The word “MPC” alone does not establish absolute security.
Pact: turning a task into boundaries
Imagine a user says: “On Base, spend up to $10 a day on a specified data service for one week.” A Pact might need to express the task, assets, budget, duration, destination and termination conditions.
This is a conceptual illustration; confirm which conditions a particular product version actually supports. Cobo describes mobile approval, adjustment and monitoring of agents, with Pact limiting transactions. Product page
| Capability | Provider description | What to verify |
|---|---|---|
| Scope | Pact binds tasks, rules and duration | Which rules are enforced and which are descriptive? |
| Signing | MPC signing with permissions shared among participants | How does recovery work if a party is offline, a key is exposed or a backup fails? |
| Use cases | Payments, transfers, swaps and other on-chain actions | Do the same rules apply to every supported chain and action? |
| Exceptions | User approvals, monitoring and freezing | Can an in-progress or signed transaction be stopped? |
| Integration | Agent skill and mobile experience | Version, geography, account eligibility and audit records |
Who signs, and who can recover?
Cobo’s product page describes two signing relationships: agent and Cobo for automatic actions permitted by a Pact, and user and Cobo for governance and high-value approvals. It also describes non-custody by default and optional custody; recovery depends on the actual configuration and backup process. Cobo FAQ
The ability to set rules does not mean the user signs every transaction live: the mode and Pact matter. Support for multiple networks also does not mean identical policies, assets, payment protocols or recovery options on each network.
Early launch materials and the product page use different wording about modes and availability. Check current documentation, the actual interface and contract; neither an early “coming soon” statement nor a current marketing description establishes availability to everyone.
Recipes provide an execution path
Cobo uses Recipes to describe organized on-chain tasks such as transfers, swaps and x402 requests, reducing how much contract and parameter composition an agent must do itself. Product overview
A Recipe does not eliminate bad data, model misunderstanding, protocol risk or mistaken approvals. Verify the destination contract, quote, permissions, fees and outcome for each use.
Business model: early access and planned usage pricing
The FAQ says Agentic Wallet is free during early access and planned to use usage-based pricing after full launch. Confirm actual pricing, eligibility and network costs with Cobo. Official FAQ
Cobo’s existing business includes wallet and digital-asset infrastructure. An agent wallet could bring its signing, security and services to new customers; that is an inference, not disclosed Agentic Wallet revenue.
| Dimension | Cobo Agentic Wallet | MetaMask Agent Wallet |
|---|---|---|
| Starting point | MPC, Pact and authorization governance | User on-chain transactions and wallet security flows |
| Agent controls | Pact and policy checks described by Cobo | Guard Mode, allowlists and risk checks described by MetaMask |
| User interaction | Mobile approval and monitoring emphasized | Supported interactions and transaction modes depend on configuration |
| Availability and pricing | Free early access; full-launch usage price to confirm | Independent agent-wallet charges require confirmation |
This comparison uses public descriptions and has not been tested under identical conditions. Verify each difference against the MetaMask quickstart and Cobo’s configuration.
Questions before choosing
- Which chains, assets, contracts and agent actions can a Pact cover?
- Who participates in signing while the user is offline, and how do exception approvals reach them?
- What is the recovery procedure if the device is lost, Cobo is unavailable or a policy must be revoked?
- How does a freeze affect signed, pending or cross-chain transactions?
- How do early-access eligibility, fees and full-release contract terms change?
Where are rules enforced?
Pact organizes user authorization and an execution plan. The key questions are which requests receive policy checks before signing, how signers cooperate, and who can change or revoke rules in each mode.
| Scenario | If relying on a prompt alone | Control to verify with the provider |
|---|---|---|
| Agent tries an unapproved recipient | The model may misunderstand the task | Can recipient addresses and contracts be rejected? |
| Agent makes several transactions quickly | Each transaction may appear below the limit | How do cumulative limits handle concurrency and pending transactions? |
| User’s phone is offline | Exceptions cannot be confirmed immediately | How are authorized actions and exception approvals handled? |
| Transaction signed but unconfirmed | The interface may still show it as pending | What can revocation or freezing actually stop before or after broadcast? |
These are evaluation questions, not claims that Cobo experienced these failures. Start with authorization, refusal, revocation and recovery in a supported test environment before considering real funds.
Different customers, different priorities
An individual trader may care most about mobile approvals, recovery and security feedback; a team running multiple agents may prioritize budgets per Pact, policy changes, log export and bulk administration. An API purchaser must also check whether x402 requests are supported for the specific chain and asset: swap support does not imply payment support for every API.
Compare network fees, conversion costs, provider charges and geographic availability as well as the early-access fee. The public pricing plan is not a substitute for the customer’s actual contract.
Assessment: Cobo connects agent authorization with wallet signing and user governance. Evaluate where rules are enforced, what the user can revoke and how recovery works for the intended task.