your browser agents can now complete online purchases without ever touching card data. agents on KERNEL now pay on checkout pages using aliases, not card data. we swap in the real credential at egress, so card numbers never touch your agent's runtime or context.

to power agentic payments, we're launching multi-wallet support on KERNEL. developers choose which wallet their agent can use, and we handle the wallet-side oauth, enrollment, and api flows. your agent gets card aliases to use. choose from @stripe @link or @agentcardhq to get started today.

KERNEL x @link by @stripe lets browser agents pay with cards already saved in link. link issues single use cards with set transaction boundaries, including merchant, amount, and purpose. KERNEL enables browser agents to complete checkouts without exposing the underlying card details. "many online tasks ultimately end in a payment. KERNEL gives agents a secure environment to complete those transactions. by integrating link’s wallet for agents, KERNEL is making it simple for agent builders to turn on payments in one go." - @stevekaliski, principal software engineer at stripe

.@beaconsai uses KERNEL x @link to power their ai assistant that runs and grows a creator’s business. “KERNEL and link gave us a remarkably fast path to securely connect payments and enable our agents to take real financial actions on creators’ behalf. we were able to get payments working quickly, with the security and compliance infrastructure already in place.” - david zeng, co-founder & cto at beacons

KERNEL x @agentcardhq allows users to authorize agent payments with their actual cards, preserving their transaction histories and card rewards. “agentcard allows customers to buy using their cards instead of one-time cards. we believe that buying things with agents should be easy and fast and we are very excited to partner with the KERNEL team to make that possible.” - @keyserfaty, co-founder & ceo at agentcard

.@orchid_hq uses KERNEL x @agentcardhq to enable its personal ai assistant to handle any online purchase. "building agentic experiences at scale relies on providing the right infrastructure and gateways to those agents. KERNEL gives our agents a reliable path through checkout, while agentcard lets them pay exactly what the user approved. agentcard and KERNEL provide the stability agents appreciate." - @swedish_chef, product & growth at orchid

@link @agentcardhq @beaconsai @orchid_hq read more about how KERNEL powers agentic payments in our launch announcement: we're actively expanding our integrations and partnerships. reach out if you're interested in working together.

h/t @rfgarcia and @fumihirojudo for driving the engineering work to support browser agents making payments through KERNEL

huge unlock for easy, secure agentic commerce

super cool! i think this is the only way i’d let my agent go buy something in a production setting

agentic commerce needs to be secure! and KERNEL ensures that!

give your agent a card alias, so it won't need to hallucinate an alibi

We are here for better future @ekosproject

Keeping the real card number out of the agent runtime is the right boundary — once a PAN lands in context, every later tool call inherits that blast radius.

Okay now this is dope 🥹

Keeping raw card data out of the agent runtime is a strong security pattern. The same principle should apply to the knowledge and context agents rely on — minimize exposure, preserve provenance, and make every critical input traceable.

The useful part is the boundary. Let the agent buy without ever seeing the card.

this is neat but what if my agent pays for Vercel, builds and hosts a website with a credit card form, then phishes the credit card out? 🤔

swapping the real credentials at egress so agents never touch card data is huge for security. solves a massive trust bottleneck.

Can @PayBox help?