Skip to main content
If you are writing an agent, bot, or automation that executes blockchain actions, Cobo Agentic Wallet gives you an authorization-scoped wallet abstraction instead of raw wallet access. That means you do not need to build your own:
  • spend limits
  • approval escalation
  • delegation lifecycle
  • audit trail
  • denial feedback contract
CAW gives your program pacts built in: structured delegation agreements with intent, execution plan, policies, and completion conditions. See Overview for the recommended onboarding path and the alternate integration surfaces.

​
What your program can do

Transfer tokens — send ERC-20 tokens and native assets to any address on supported chains. Every transfer passes through the policy engine before execution. Execute payments and settlements — automate payout, collection, treasury, and settlement flows while keeping approval thresholds and policy checks in place. Call smart contracts — invoke contract functions on supported EVM chains and Solana. Contract addresses and functions are checked against the contract call allowlist before execution. Query balances and transaction history — read wallet balances, token holdings, and transaction history programmatically without spending permissions. Submit pacts for owner authorization — when your program needs scoped access for a specific task, it submits a pact. The owner reviews and approves once; the program operates within those boundaries automatically. Respond to policy denials with self-correction — when the policy engine denies an operation, your program receives a structured error with the denial reason. It can adjust its approach — for example, lowering amount, narrowing scope, or escalating — rather than failing silently. Access audit logs for compliance and debugging — every operation your program attempts is logged with the decision outcome, policy context, and principal. Your program can query these logs for compliance reporting or to debug unexpected denials.

​
What the policy engine enforces

The policy engine runs before every blockchain operation request and evaluates the applicable authorization and control layers in three parts:
  • Per-transaction spending limits
  • Daily and cumulative budgets
  • Chain and token allowlists
  • Contract and function allowlists
  • Address allowlists and denylists
  • Approval thresholds — operations above a defined value pause for owner review before execution
In practice, a request must fit the active pact or delegation scope, then satisfy the relevant policy rules, and then stay within the applicable usage counters. Matching rules can allow, deny, or require owner review depending on how they are defined. Your program does not need to implement any of that itself. The service enforces it on every request, regardless of which integration path you use.

​
Pact-based authorization

Every task your program takes on starts with a pact — a structured, enforceable delegation agreement that defines intent, execution plan, policies, and completion conditions. The owner approves once; your program operates within those boundaries automatically. The infrastructure enforces them, not trust. When the pact expires, completes, or is revoked, all access is removed instantly — the API key is invalidated server-side with no grace period. No zombie permissions. No forgotten credentials. This model means you do not need to build custom approval workflows, spend limits, or delegation lifecycle logic yourself — pacts handle all of it.

​
Gas

Cobo Gasless automatically covers gas fees on behalf of your program, so it does not need to hold gas tokens before submitting transactions.
This feature is coming soon.