From 3704831b1277aa5c034febc78b51fee5bfdf74a5 Mon Sep 17 00:00:00 2001 From: masnwilliams <43387599+masnwilliams@users.noreply.github.com> Date: Mon, 2 Nov 2026 16:49:51 +0000 Subject: [PATCH] Update agentcard links to agentcard.com --- integrations/wallets/agentcard.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/integrations/wallets/agentcard.mdx b/integrations/wallets/agentcard.mdx index 007ebf05..9901b786 100644 --- a/integrations/wallets/agentcard.mdx +++ b/integrations/wallets/agentcard.mdx @@ -3,7 +3,7 @@ title: "AgentCard" description: "Use Agentcard to approve browser checkouts against an enrolled payment method" --- -[agentcard](https://www.agentcard.sh/) collects a user's card in a hosted enrollment flow and authorizes each browser checkout against that enrolled payment method. the card number and cvc stay with agentcard. your agent receives non-secret aliases. +[agentcard](https://agentcard.com/vault?utm_source=kernel&utm_medium=partner_docs&utm_campaign=integration) collects a user's card in a hosted enrollment flow and authorizes each browser checkout against that enrolled payment method. the card number and cvc stay with agentcard. your agent receives non-secret aliases. KERNEL's native integration holds a recognized checkout request while the user approves it, lets agentcard execute it, and replays the processor response to the browser. this alias-based integration is an exception to KERNEL's [`fill` api](/vaults/fill), not another form of that operation. see [payments on KERNEL](/browsers/payments) for the shared offering and lifecycle. @@ -171,7 +171,7 @@ wallet commands. #### Import an existing user -complete agentcard's [enrollment or sign-in flow](https://docs.agentcard.sh/vault/adding-a-card) +complete agentcard's [enrollment or sign-in flow](https://docs.agentcard.com/vault/adding-a-card) in your own application and store the resulting `usr_` user id. if you've already connected the user, reuse that id; don't enroll them again.