Anchor and Agentcard: let your browser agent pay with your user's own card

Agents should be able to buy anything online. As of today, that includes agents running in Anchor.

Anchor builds cloud browsers for AI agents. You can drive a session with your own agent, or give Anchor's agent a task in plain language. Starting today, an agent shopping in an Anchor session can pay with your user's own card through Agentcard, and Anchor lists Agentcard in its integrations.

A demo: the agent gets the task, finds the costume, and the checkout waits until the user approves on their phone.

How it works

Your user saves their card once in the Agentcard Vault, with a passkey.
Your agent shops in an Anchor session. At checkout, it types a placeholder card.
The Agentcard SDK, attached to the session, holds the payment, and your app sends the user an approval link.
The user approves on their phone with their passkey. Their device swaps in the real card, and the order completes.

The card never reaches the agent or the task text.

Your agent or Anchor's

It works both ways: with your own agent driving the session, or with Anchor's agent running a task in it. With Anchor's agent, run the task in the same session Agentcard is attached to, so the payment waits for the user.

Get started

Install the SDK next to Anchor's:

npm i @agent-cards/sdk anchorbrowser playwright

The full guide, with code for both ways, is Agentcard with Anchor. Agentcard also works with Browser Use, Kernel and Browserbase.

If your agent should be able to buy for your users, start here.

Thanks to Idan and the Anchor team for building this with us.