Crypto Agent Atlas

Snapshot

All tasks

Which crypto agents can pay for a service on their own?

Paying for a service means the agent pays a provider from a funded wallet while using that provider, rather than moving funds for you in general.

Each row says which payments its documentation covers. A configuration that can pay for services is not thereby able to send or trade.

Only payments this snapshot records as a task are listed. Other tools’ current documentation may describe payment features, such as x402, that aren’t recorded as a task here, so a tool missing from this page isn’t shown to be unable to pay.

  • Snapshot
  • Not hands-on tested
  • In the comparison Pay for service

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.

Coinbase Agentic Wallet

Payments MCP plus companion wallet; excludes CLI send/trade. MCP

Agent connector · Docs checked · Not hands-on tested

This task

DocumentedConditional

What the docs cover Automatic x402 payments on supported chains.

Chains for this task Base, Polygon PoS, Solana

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

Sources Coinbase — Two ways to use; Which should I use?Coinbase — How does it work?; What can agents do?; You stay in control ofChecked

Access limitation: Release stage not established by inspected sources.

Approval for this task

  • Stage 5: executes without per-action human approvalFunded wallet, permitted x402 payment within configured limits.

Sources Coinbase — How does it work?; What can agents do?; You stay in control ofCoinbase — What it does; NotesChecked

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

Limits beside it

Documented enforcement

User-set per-call and per-session payment caps.

Layer: unknown

Excluded path: Precise enforcement layer and session reset rules not established.

Source Coinbase — What it does; NotesChecked

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

    Not reviewedThis task isn’t recorded for this configuration.

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

    Not reviewedThis task isn’t recorded for this configuration.

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

    Not reviewedThis task isn’t recorded for this configuration.

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

    Not reviewedThis task isn’t recorded for this configuration.

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

    Not reviewedThis task isn’t recorded for this configuration.

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

    Not reviewedThis task isn’t recorded for this configuration.

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