Crypto Agent Atlas

Snapshot

All tasks

Which crypto agents can prepare a transaction without sending it?

Preparing means building a transaction and handing it back unsigned. Whoever holds the wallet, you or the app that integrates the tool, decides whether to sign and send it.

A configuration that can prepare a transaction may still be unable to send one. Sending is a separate task with its own page.

  • Snapshot
  • Not hands-on tested
  • In the comparison Prepare transaction

Compare these in the full tableHow matching works

1 configuration documents 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.

Brian

Transaction API; preparation only, separate from Brian App. API

App / operator · Docs checked · Not hands-on tested

This task

DocumentedConditional

What the docs cover Transfer or swap objects returned to caller.

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

Prerequisite: Matching wallet, network and permissions; no transaction tested.

Sources Brian — Transactions flow; Transaction Request; Transaction ExecutionBrian — Chains supported; Actions supportedChecked

Access limitation: Direct official retrieval failed; indexed documents are eight to ten months old. Network list is an inspected subset, not complete or live-verified.

Approval for this task

  • Stage 3: prepares an unsigned transactionAPI produces transaction objects.

Sources Brian — Transactions flow; Transaction Request; Transaction ExecutionBrian — Chains supported; Actions supportedChecked

Limits beside it

Unknown

Execution caps are outside the documented preparation flow.

Layer: unknown

Limitation: No evidence of absence; downstream controls not evaluated.

Source Brian — Transactions flow; Transaction Request; Transaction ExecutionChecked

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 Authenticated awal CLI; sends by chain, swaps on Base mainnet. CLI

    UnknownUnsigned export not established.

  • Coinbase Agentic Wallet Payments MCP plus companion wallet; excludes CLI send/trade. MCP

    DocumentedNot applicableNo general transfer/swap preparation surface reviewed.

  • MetaMask Agent Wallet Guard Mode with server-wallet; excludes Beast and local-mnemonic modes. CLI

    UnknownStandalone unsigned-output workflow not evaluated.

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

    UnknownStandalone unsigned-output workflow not evaluated.

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

    UnknownUnsigned export not established.

  • Almanak Platform Deployed Safe strategy with Zodiac Roles and deployment EOA. App

    UnknownStandalone unsigned export not established.

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