Alchemy is rolling out a new payments product aimed at AI agents. The Block reports that the company unveiled “AgentCard,” a virtual payment card designed to let AI agents transact through familiar card rails.
The immediate hook is simple. AgentCard “will default to Visa-issued tokens,” The Block says. That means the first version leans on Visa’s tokenized infrastructure rather than asking developers to wire in crypto payments from day one.
What “Visa-issued tokens” likely means for builders
Tokenization matters because it changes how the system handles payment credentials. With a Visa-issued token default, the agent’s payment flow can stay closer to mainstream card processing, at least for the initial rollout.
For developers, that can reduce integration friction. Instead of building agent payment logic across multiple payment types at launch, they can start with a card abstraction that already fits into existing payment ecosystems.
Crypto support, but not as the first default
Alchemy’s card is not positioned as a crypto-only tool. The Block notes that AgentCard “will support crypto and agent-native payment protocols when available.”
will support crypto and agent-native payment protocols when available.
In other words, crypto is on the roadmap, not the default configuration. That distinction matters for teams trying to assess timelines, because “when available” is doing a lot of work here. The product may still require additional infrastructure, partner integrations, or protocol support before it can route payments through more native channels.
Why this product matters beyond another card wrapper
AI agents need payments that work without constant human supervision. A virtual card that can be driven programmatically is one route. By starting with Visa-issued tokens, AgentCard also signals a pragmatic strategy: use standardized rails first, then widen the funnel once agent payment protocols mature.
But this also raises a basic systems question. If crypto support depends on “when available,” then agent payment compatibility will likely vary by deployment context and protocol maturity. Teams building agent workflows will still need to account for what payment routes are supported at the time they ship.
The operational risk: payment rails still have limits
Even with token defaults, payment infrastructure is not a magic wand. Card rails come with their own compliance constraints, funding flows, and transaction controls. AgentCard’s design choices, as described by The Block, suggest Alchemy is trying to fit agents into existing payment tooling rather than bypass it.
That is not inherently bad. It just means the “AI agent payments” story here is more about orchestration and developer experience than about removing risk from the equation.
The Block’s report is brief on dates, integrations, and supported protocols beyond the default Visa token path. For now, the takeaway is directional. AgentCard is built to begin with Visa-style tokenization and expand into crypto and agent-native payment routes when the supporting options are ready.