Which crypto agents can carry out a transaction?

Carrying out a transaction means the configuration gets it signed and sent through its own wallet setup, not just prepared.

This is a broad task. One tool’s documentation covers transfers, another’s swaps, another’s only pre-approved strategy calls. Each row states what that configuration’s documentation actually covers; nothing here implies a tool can do every kind of transaction.

Snapshot 13 Oct 2026
Not hands-on tested
In the comparison Execute transaction

Compare these in the full table How matching works

5 configurations document this in this snapshot, out of 7 profiled configurations

Listed when this snapshot records the task as documented yes or conditional for that configuration, in the same order as the comparison: by class, then alphabetically. Conditions, approval and limits stay with each row.

Recorded for several of them: Matching wallet, network and permissions; no transaction tested.

Coinbase Agentic Wallet

Authenticated awal CLI; sends by chain, swaps on Base mainnet. CLI

Agent connector · Docs checked 13 Oct 2026 · Not hands-on tested

This task

DocumentedConditional

What the docs cover USDC send on listed chains; swaps on Base mainnet only.

Chains for this task Base

Prerequisite: Combined send/trade filter uses Base mainnet, the shared documented network. USDC sends additionally support Base Sepolia, Polygon, Solana mainnet and devnet; trading does not.

Limitation: Combined execution chain filter uses the intersection of send and trade support: Base mainnet only. Individual sends have additional documented networks.

Source Coinbase — Prerequisites; CLI commands; Authenticating an agentic walletChecked 13 Oct 2026

Access limitation: Costs, region and operational availability unverified.

Approval for this task

Stage unknownNo inspected exact confirmation or threshold workflow.

Limitation: CLI capabilities do not prove stage 5 for every action.

Sources Coinbase — What is Agentic Wallet CLI?; Capabilities; Security Coinbase — Prerequisites; CLI commands; Authenticating an agentic walletChecked 13 Oct 2026

Limits beside it

Claimed

CLI overview advertises per-session and per-transaction caps.

Layer: Wallet provider

Excluded path: Configuration, exact enforcement scope and bypass paths not established.

Limitation: This is a documented claim, not validated enforcement. MCP limit controls are separate.

Source Coinbase — What is Agentic Wallet CLI?; Capabilities; SecurityChecked 13 Oct 2026

MetaMask Agent Wallet

Guard Mode with server-wallet; excludes Beast and local-mnemonic modes. CLI

Agent connector · Docs checked 13 Oct 2026 · Not hands-on tested

This task

DocumentedConditional

What the docs cover Transfers through server-wallet signing.

Chains for this task Ethereum, Base, Arbitrum One, OP Mainnet, Polygon PoS

Prerequisite: Selected documented networks for balance/transfer; confirm current CLI network features and Guard policy. No transaction tested.

Limitation: Only the five inspected EVM networks are mapped here; mappings describe balances/transfers, not every supported action.

Sources MetaMask — Transfers; Balances and prices; Server-wallet polling MetaMask — CLI and session; Wallet modes / Server-wallet; Server-wallet async model MetaMask — Product coverage; Mainnets; Per-chain balancesChecked 13 Oct 2026

Access limitation: Selected network subset; features vary by CLI version. Current onboarding, region and total cost unverified.

Approval for this task

Stage 5: executes without per-action human approvalWithin Guard policy and no approval-triggering risk.
Stage 4: executes after per-action human approvalPolicy violation or flagged transaction requires 2FA.

Source MetaMask — Guardrails; Requires 2FA approval; How 2FA approval works; Outflow policyChecked 13 Oct 2026

Stage 5 means no per-action approval, not limited or safe. Read the limits beside it.

Limits beside it

Documented enforcement

Rolling USD outflow threshold; excess or increase requires 2FA.

Layer: Wallet provider

Excluded path: Signatures such as Permit2 excluded.

Excluded path: Outside-backend or unsimulatable outflows may not be measured reliably.

Sources MetaMask — Guardrails; Requires 2FA approval; How 2FA approval works; Outflow policy MetaMask — Setting your outflow limit; How outflow is calculated; LimitationsChecked 13 Oct 2026

Bankr

Agent API with explicit per-key permissions and wallet-level controls. API

App / operator · Docs checked 13 Oct 2026 · Not hands-on tested

This task

DocumentedConditional

What the docs cover Swaps and transfers require write-enabled key.

Chains not reviewed for this taskNetworks listed for access don’t establish this task’s chains.

Sources Bankr — Capabilities; Getting Started; Authentication; Basic Flow Bankr — API Key Permissions; Read-Only Mode; Wallet Allowlist; Daily Message Limits; Incident responseChecked 13 Oct 2026

Access limitation: Selected network subset; API access is not proof of runtime or regional access.

Approval for this task

Stage unknownWrite-enabled key can invoke transactions; no exact human confirmation policy established.

Limitation: Do not infer numeric execution stage from the word agent.

Sources Bankr — Capabilities; Getting Started; Authentication; Basic Flow Bankr — API Key Permissions; Read-Only Mode; Wallet Allowlist; Daily Message Limits; Incident responseChecked 13 Oct 2026

Limits beside it

Documented enforcement

Documented defaults: $500 per transaction and $500 per rolling 24 hours; recipient restriction off and arbitrary contract calls on.

Layer: Backend

Excluded path: Raw calldata token movement is valued at zero for USD caps; native value is counted.

Excluded path: Read-only keys can still buy Club; LLM credit top-ups remain possible when llmGatewayEnabled.

Limitation: Defaults describe vendor documentation, not a particular account or its current settings.

Sources Bankr — Controls; Raw transactions and contract calls; Pricing & fail-closed behavior Bankr — API Key Permissions; Read-Only Mode; Wallet Allowlist; Daily Message Limits; Incident responseChecked 13 Oct 2026

HeyAnon v2

Existing Web3 wallet login; excludes generated HeyAnon hot-wallet mode. App

App / operator · Docs checked 13 Oct 2026 · Not hands-on tested

This task

DocumentedConditional

What the docs cover Transfer/swap functions require connected-wallet confirmation.

Chains not reviewed for this taskNetworks listed for access don’t establish this task’s chains.

Limitation: Automation is unavailable in this mode. Exact action/network matrix unverified.

Sources HeyAnon — Log In with Web3 Wallet; Important Notes HeyAnon — Core Utilities; Lending / Borrowing / Yield; Gemma / Core Data IntegrationsChecked 13 Oct 2026

Access limitation: EVM/Solana/TON login choices do not establish exact network/action support; chain IDs unresolved.

Approval for this task

Stage 4: executes after per-action human approvalUser approves and confirms every transaction in external wallet.

Sources HeyAnon — Log In with Web3 Wallet; Important Notes HeyAnon — Core Utilities; Lending / Borrowing / Yield; Gemma / Core Data IntegrationsChecked 13 Oct 2026

Limits beside it

Unknown

No amount/window enforcement established for this external-wallet mode. Per-action confirmation is not a spending cap.

Sources No source listedChecked 13 Oct 2026

Almanak Platform

Deployed Safe strategy with Zodiac Roles and deployment EOA. App

Strategy platform · Docs checked 13 Oct 2026 · Not hands-on tested

This task

DocumentedConditional

What the docs cover Deployment signs and broadcasts permitted strategy transactions.

Chains not reviewed for this taskNetworks listed for access don’t establish this task’s chains.

Sources Almanak — Architecture / User Wallet / Deployment EOA / Safe Wallet / Zodiac Roles Modifier Module; Autonomous Execution Fees Almanak — Deploy Flow / Step-by-Step / Wallet Preparation / Zodiac Permissions; Supported chain valuesChecked 13 Oct 2026

Access limitation: Selected chains only; strategy and protocol compatibility are configuration-specific.

Approval for this task

Stage 5: executes without per-action human approvalActive deployment within user-approved Zodiac permissions.

Stage 5 means no per-action approval, not limited or safe. Read the limits beside it.

Limits beside it

Documented enforcement

Zodiac restricts target functions and parameters.

Layer: Onchain

Excluded path: Strategy sizing hints are not proof of an enforced USD/time cap.

Not listed above

Profiled configurations this snapshot doesn’t record as documenting this task, with what it does record. Only a documented no means no. Unknown or not reviewed isn’t a no, and a tool’s current documentation can cover more than this snapshot records.

Coinbase Agentic Wallet Payments MCP plus companion wallet; excludes CLI send/trade. MCP
DocumentedNoGeneral fund transfers and trades are not exposed to MCP agents.
Brian Transaction API; preparation only, separate from Brian App. API
DocumentedNoThis API flow delegates signing and broadcast to the application.

4 systems aren’t profiled yet and aren’t checked for any task. See coverage