Transfers are the most common CAW operation. A runtime submits a transfer with an active pact or delegation, CAW evaluates it against the policy engine, and the result is either allowed, denied, or paused for owner approval.Documentation Index
Fetch the complete documentation index at: https://cobo.com/products/agentic-wallet/manual/llms.txt
Use this file to discover all available pages before exploring further.
Submit a transfer
- CLI
- Python SDK
- TypeScript SDK
Response model
| Field | Description |
|---|---|
status | submitted, pending, or pending_approval |
cobo_transaction_id | Transaction identifier if the request reached execution |
transaction_hash | On-chain hash after broadcast/confirmation |
request_id | Your idempotency key |
pending_operation_id | Present only when the operation needs owner approval |
Idempotency
Use a stablerequest_id tied to your business action. If the runtime retries the same transfer after a timeout or process restart, CAW returns the original operation instead of creating a duplicate.
Pending approval
If the transfer is above an owner review threshold, CAW returnsstatus="pending_approval" instead of failing. Your runtime should pause that task and resume after the owner acts in the Cobo Agentic Wallet app.
- Python SDK
- TypeScript SDK
If the operation is outside policy entirely, CAW returns a denial instead. See Handle Policy Denial.
Before you submit
For production flows, estimate fees first and keep tracking tied torequest_id.
- Estimate fees: Contract Calls
- Track results: Transaction Tracking