You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
restructure the initial vault and payment documentation around the primitive, integrations, and user task:
add one preview-tagged vaults page that introduces the general sensitive-value primitive before covering write-only values, aliases, immutable browser attachment, egress substitution, the initial payment contract, and future item types.
add a payments category under integrations with an overview, the supplied navigation icon, and individual stripe link and agentcard pages. the provider pages link to their respective sites, and the overview directs developers to request additional native integrations through support.
add Enable Payments in a Browser Agent beside the playwright/computer-use guide. the walkthrough follows the shared provider flow: collect the payment method in a hosted surface, prepare aliases, attach the vault, pass only aliases to the agent, observe approval outside the agent, and reconcile the merchant outcome. it opens with a provider trade-off table and copy-pasteable coding-agent tasks for exercising either the stripe link or agentcard path through the CLI. a responsibility matrix separates application, end-user, browser-agent, KERNEL, and provider work: the end user creates the purchase intent, while the application translates it into KERNEL api resources. before creating or authorizing a card, the application must independently verify the agent's proposed merchant, amount, currency, and cart, present those verified values for confirmation, and fail closed if any value cannot be verified or disagrees. it also documents behavior when a wallet is missing or not connected. shared examples name the vault for an application end user rather than a checkout.
require payment settings ui to expose at most one wallet per provider in each vault, reuse wallets in every state, and suppress provider add options once configured. the examples list existing items and fail when duplicate provider wallets already exist because the current api enforces unique item keys rather than provider-level uniqueness.
document production integration requirements found in the end-to-end flow: assert agentcard sandbox or live mode from deployment configuration; deliver hosted actions through an authenticated, expiring application route; verify stripe payment-link values from its structured response and treat dom test ids as supplemental; use active presentment pricing; collect merchant-required customer fields and truthful agent disclosures separately; surface headful browser live view through an authenticated application route; update reusable agentcard items only from supported states; run approval observation concurrently with checkout; clean up the observer and browser; and treat a matching merchant order record as the success authority instead of relying on page-specific success text.
add CLI examples across the vault, payments overview, provider, and browser-agent pages using the current kernel vaults and kernel browsers create --vault commands.
describe planned provider, card-collection, vault-management, and browser-side payment support.
redirect the previous vault routes, browser payment guide routes, and stripe link route, and add payments to the integrations overview.
payments are the first application of vaults. the primitive page explains broader credential and identity use cases while explicitly limiting the current release to wallets and cards for stripe link and agentcard. stripe link examples also match the current live-only card contract and omit the unsupported spec.test field.
testing
mint validate
mint broken-links
all five new routes return 200 in the local preview
preview badge, navigation placement, page layout, and uppercase KERNEL rendering checked in the local preview
typescript examples parsed with esbuild
python examples compiled with compile()
CLI examples checked against the current kernel/cli command definitions
new mdx pages formatted with prettier
git diff --check
focused vault lifecycle and egress payment tests against kernel/kernel commit 256e757
no live-provider enrollment or merchant payment was performed.
The reason will be displayed to describe this comment to others. Learn more.
Stale comment
Risk assessment: Very Low
Decision: Keep existing approval. Risk did not increase after the latest push.
Re-evaluated 8107eef...f258b16 from the file diff. This remains a Mintlify documentation-only change. No application, API, SDK, CI, auth, billing, schema, or infrastructure files are modified.
integrations/overview.mdx — one added payments link.
docs.json — navigation entries for the new pages, plus redirects from /vaults/overview and /vaults/payments (neither path exists on main). Theme, OpenAPI, and other site settings are unchanged.
style.css — opt-in .kernel-brand-name uppercase override. The existing global lowercase rule is unchanged.
No CODEOWNERS file exists, and the main ruleset does not require code-owner review. This automation already approved the prior commit; that approval is left in place because risk is still Very Low.
Action: Comment only. Did not re-approve. Did not dismiss approval.
The reason will be displayed to describe this comment to others. Learn more.
Stale comment
Risk assessment: Very Low
Decision: Keep existing approval. Risk did not increase after the latest push.
Re-evaluated 8107eef...131da0b from the file diff. This remains a Mintlify documentation-only change. No application, API, SDK, CI, auth, billing, schema, or infrastructure files are modified.
Latest commit 131da0b edits only vaults.mdx: replaces endpoint field tables with narrative API behavior, adds field constraints, and points to the vaults API reference.
integrations/overview.mdx — one added payments link.
docs.json — navigation entries for the new pages, plus redirects from /vaults/overview and /vaults/payments (neither path exists on main). Theme, OpenAPI, and other site settings are unchanged.
style.css — opt-in .kernel-brand-name uppercase override. The existing global lowercase rule is unchanged.
No CODEOWNERS file exists, and the main ruleset does not require code-owner review. This automation already approved an earlier commit; that approval is left in place because risk is still Very Low.
Action: Comment only. Did not re-approve. Did not dismiss approval.
The reason will be displayed to describe this comment to others. Learn more.
Stale comment
Risk assessment: Very Low
Decision: Keep existing approval. Risk did not increase after the latest push.
Re-evaluated 8107eef...9907ee2 from the file diff. This remains a Mintlify documentation-only change. No application, API, SDK, CI, auth, billing, schema, or infrastructure files are modified.
Latest commit 9907ee2 is a path/title rename only: browsers/pay-through-browser-checkout.mdx → browsers/add-payments-to-browser-agent.mdx, with matching nav, cross-links, and a redirect from the old path.
integrations/overview.mdx — one added payments link.
docs.json — navigation entries for the new pages, plus redirects from /vaults/overview, /vaults/payments, and /browsers/pay-through-browser-checkout (none of these paths exist as pages on main). Theme, OpenAPI, and other site settings are unchanged.
style.css — opt-in .kernel-brand-name uppercase override. The existing global lowercase rule is unchanged.
No CODEOWNERS file exists, and the main ruleset does not require code-owner review. This automation already approved an earlier commit; that approval is left in place because risk is still Very Low.
Action: Comment only. Did not re-approve. Did not dismiss approval.
The reason will be displayed to describe this comment to others. Learn more.
Stale comment
Risk assessment: Very Low
Decision: Keep existing approval. Risk did not increase after the latest push.
Re-evaluated 8107eef...cf96b69 from the file diff. This remains a Mintlify documentation-only change. No application, API, SDK, CI, auth, billing, schema, or infrastructure files are modified.
Latest commit cf96b69 is a path/title rename plus nav polish: browsers/add-payments-to-browser-agent.mdx → browsers/enable-payments-in-browser-agent.mdx, matching nav/cross-links, a redirect from the old path, and a static images/integration-icons/payments.svg nav icon.
integrations/overview.mdx — one added payments link.
docs.json — navigation entries for the new pages, plus redirects from /vaults/overview, /vaults/payments, /browsers/pay-through-browser-checkout, and /browsers/add-payments-to-browser-agent (none of these paths exist as pages on main). Theme, OpenAPI, and other site settings are unchanged.
style.css — opt-in .kernel-brand-name uppercase override. The existing global lowercase rule is unchanged.
No CODEOWNERS file exists, and the main ruleset does not require code-owner review. This automation already approved an earlier commit; that approval is left in place because risk is still Very Low.
Action: Comment only. Did not re-approve. Did not dismiss approval.
The reason will be displayed to describe this comment to others. Learn more.
Stale comment
Risk assessment: Very Low
Decision: Keep existing approval. Risk did not increase after the latest push.
Re-evaluated 8107eef...0b3a510 from the file diff. This remains a Mintlify documentation-only change. No application, API, SDK, CI, auth, billing, schema, or infrastructure files are modified.
Latest commit 0b3a510 edits only the page title in integrations/payments/overview.mdx (Payments → overview).
integrations/overview.mdx — one added payments link.
docs.json — navigation entries for the new pages, plus redirects from /vaults/overview, /vaults/payments, /browsers/pay-through-browser-checkout, and /browsers/add-payments-to-browser-agent (none of these paths exist as pages on main). Theme, OpenAPI, and other site settings are unchanged.
style.css — opt-in .kernel-brand-name uppercase override. The existing global lowercase rule is unchanged.
images/integration-icons/payments.svg — static nav icon.
No CODEOWNERS file exists, and the main ruleset does not require code-owner review. This automation already approved an earlier commit; that approval is left in place because risk is still Very Low.
Action: Comment only. Did not re-approve. Did not dismiss approval.
The reason will be displayed to describe this comment to others. Learn more.
Stale comment
Risk assessment: Very Low
Decision: Keep existing approval. Risk did not increase after the latest push.
Re-evaluated 8107eef...855a642 from the file diff. This remains a Mintlify documentation-only change. No application, API, SDK, CI, auth, billing, schema, or infrastructure files are modified.
Latest commit 855a642 is a path/title rename plus copy updates: integrations/payments/link.mdx → integrations/payments/stripe-link.mdx, matching nav/cross-links, a redirect from /integrations/payments/link, and a support-request note on the payments overview.
integrations/overview.mdx — one added payments link.
docs.json — navigation entries for the new pages, plus redirects from /vaults/overview, /vaults/payments, /integrations/payments/link, /browsers/pay-through-browser-checkout, and /browsers/add-payments-to-browser-agent (none of these paths exist as pages on main). Theme, OpenAPI, and other site settings are unchanged.
style.css — opt-in .kernel-brand-name uppercase override. The existing global lowercase rule is unchanged.
images/integration-icons/payments.svg — static nav icon.
No CODEOWNERS file exists, and the main ruleset does not require code-owner review. This automation already approved an earlier commit; that approval is left in place because risk is still Very Low.
Action: Comment only. Did not re-approve. Did not dismiss approval.
The reason will be displayed to describe this comment to others. Learn more.
Stale comment
Risk assessment: Very Low
Decision: Keep existing approval. Risk did not increase after the latest push.
Re-evaluated 8107eef...6a34d76 from the file diff. This remains a Mintlify documentation-only change. No application, API, SDK, CI, auth, billing, schema, or infrastructure files are modified.
Latest commit 6a34d76 is copy-only: a planned-provider note on the browser payments guide, plus outbound links on the Stripe Link and Agentcard intro paragraphs.
integrations/overview.mdx — one added payments link.
docs.json — navigation entries for the new pages, plus redirects from /vaults/overview, /vaults/payments, /integrations/payments/link, /browsers/pay-through-browser-checkout, and /browsers/add-payments-to-browser-agent (none of these paths exist as pages on main). Theme, OpenAPI, and other site settings are unchanged.
style.css — opt-in .kernel-brand-name uppercase override. The existing global lowercase rule is unchanged.
images/integration-icons/payments.svg — static nav icon.
No CODEOWNERS file exists, and the main ruleset does not require code-owner review. This automation already approved an earlier commit; that approval is left in place because risk is still Very Low.
Action: Comment only. Did not re-approve. Did not dismiss approval.
The reason will be displayed to describe this comment to others. Learn more.
Stale comment
Risk assessment: Very Low
Decision: Keep existing approval. Risk did not increase after the latest push.
Re-evaluated 8107eef...13a7a43 from the file diff. This remains a Mintlify documentation-only change. No application, API, SDK, CI, auth, billing, schema, or infrastructure files are modified.
Latest commit 13a7a43 is copy-only: example vault names (browser-checkout → user-12345) and wording on the vaults intro (project-scoped containers → scoped containers).
integrations/overview.mdx — one added payments link.
docs.json — navigation entries for the new pages, plus redirects from /vaults/overview, /vaults/payments, /integrations/payments/link, /browsers/pay-through-browser-checkout, and /browsers/add-payments-to-browser-agent (none of these paths exist as pages on main). Theme, OpenAPI, and other site settings are unchanged.
style.css — opt-in .kernel-brand-name uppercase override. The existing global lowercase rule is unchanged.
images/integration-icons/payments.svg — static nav icon.
No CODEOWNERS file exists, and the main ruleset does not require code-owner review. This automation already approved an earlier commit; that approval is left in place because risk is still Very Low.
Action: Comment only. Did not re-approve. Did not dismiss approval.
The reason will be displayed to describe this comment to others. Learn more.
Stale comment
Risk assessment: Very Low
Decision: Keep existing approval. Risk did not increase after the latest push.
Re-evaluated 8107eef...d695710 from the file diff. This remains a Mintlify documentation-only change. No application, API, SDK, CI, auth, billing, schema, or infrastructure files are modified.
Latest commit d695710 adds CLI snippets (kernel vaults ..., kernel browsers create --vault) and copy updates: Stripe Link card creation documented as live-only, spec.test removed from examples, minor vault wording tweaks.
integrations/overview.mdx — one added payments link.
docs.json — navigation entries for the new pages, plus redirects from /vaults/overview, /vaults/payments, /integrations/payments/link, /browsers/pay-through-browser-checkout, and /browsers/add-payments-to-browser-agent (none of these paths exist as pages on main). Theme, OpenAPI, and other site settings are unchanged.
style.css — opt-in .kernel-brand-name uppercase override. The existing global lowercase rule is unchanged.
images/integration-icons/payments.svg — static nav icon.
No CODEOWNERS file exists. This automation already approved an earlier commit; that approval is left in place because risk is still Very Low.
Action: Comment only. Did not re-approve. Did not dismiss approval.
The reason will be displayed to describe this comment to others. Learn more.
Stale comment
Risk assessment: Very Low
Decision: Keep existing approval. Risk did not increase after the latest push.
Re-evaluated 8107eef...b17cce0 from the file diff. This remains a Mintlify documentation-only change. No application, API, SDK, CI, auth, billing, schema, or infrastructure files are modified.
Latest commit b17cce0 adds a copy-pasteable coding-agent task in the browser payments guide. That block is documentation for developers, not a product system prompt or model-instruction file.
integrations/overview.mdx — one added payments link.
docs.json — navigation entries for the new pages, plus redirects from /vaults/overview, /vaults/payments, /integrations/payments/link, /browsers/pay-through-browser-checkout, and /browsers/add-payments-to-browser-agent (none of these paths exist as pages on main). Theme, OpenAPI, and other site settings are unchanged.
style.css — opt-in .kernel-brand-name uppercase override. The existing global lowercase rule is unchanged.
images/integration-icons/payments.svg — static nav icon.
No CODEOWNERS file exists. This automation already approved an earlier commit; that approval is left in place because risk is still Very Low.
Action: Comment only. Did not re-approve. Did not dismiss approval.
The reason will be displayed to describe this comment to others. Learn more.
Stale comment
Risk assessment: Very Low
Decision: Keep existing approval. Risk did not increase after the latest push.
Re-evaluated 8107eef...699cccb from the file diff. This remains a Mintlify documentation-only change. No application, API, SDK, CI, auth, billing, schema, or infrastructure files are modified.
Latest commit 699cccb edits only vaults.mdx: expands the primitive intro (how vaults work, payments-first framing, planned future item types) and rearranges existing API/spec copy. No new routes, nav, redirects, or CSS.
integrations/overview.mdx — one added payments link.
docs.json — navigation entries for the new pages, plus redirects from /vaults/overview, /vaults/payments, /integrations/payments/link, /browsers/pay-through-browser-checkout, and /browsers/add-payments-to-browser-agent (none of these paths exist as pages on main). Theme, OpenAPI, and other site settings are unchanged.
style.css — opt-in .kernel-brand-name uppercase override. The existing global lowercase rule is unchanged.
images/integration-icons/payments.svg — static nav icon.
The copy-pasteable coding-agent task in the browser payments guide is documentation for developers, not a product system prompt or model-instruction file.
No CODEOWNERS file exists. This automation already approved an earlier commit; that approval is left in place because risk is still Very Low.
Action: Comment only. Did not re-approve. Did not dismiss approval.
The reason will be displayed to describe this comment to others. Learn more.
Stale comment
Risk assessment: Very Low
Decision: Keep existing approval. Risk did not increase after the latest push.
Re-evaluated 8107eef...69ce29f from the file diff. This remains a Mintlify documentation-only change. No application, API, SDK, CI, auth, billing, schema, or infrastructure files are modified.
Latest commit 69ce29f edits only browsers/enable-payments-in-browser-agent.mdx: adds a Stripe Link vs Agentcard comparison table and a second copy-pasteable coding-agent task for the Agentcard CLI path. Those blocks are documentation for developers, not product system prompts or model-instruction files.
integrations/overview.mdx — one added payments link.
docs.json — navigation entries for the new pages, plus redirects from /vaults/overview, /vaults/payments, /integrations/payments/link, /browsers/pay-through-browser-checkout, and /browsers/add-payments-to-browser-agent (none of these paths exist as pages on main). Theme, OpenAPI, and other site settings are unchanged.
style.css — opt-in .kernel-brand-name uppercase override. The existing global lowercase rule is unchanged.
images/integration-icons/payments.svg — static nav icon.
No CODEOWNERS file exists, and the main ruleset does not require code-owner review. This automation already approved an earlier commit; that approval is left in place because risk is still Very Low.
Action: Comment only. Did not re-approve. Did not dismiss approval.
The reason will be displayed to describe this comment to others. Learn more.
Stale comment
Risk assessment: Very Low
Decision: Keep existing approval. Risk did not increase after the latest push.
Re-evaluated 8107eef...64b080f from the file diff. This remains a Mintlify documentation-only change. No application, API, SDK, CI, auth, billing, schema, or infrastructure files are modified.
Latest commit 64b080f edits only browsers/enable-payments-in-browser-agent.mdx: clarifies that wallet and card are API resources created by the trusted backend, adds a responsibility matrix, and documents the once-per-user vs per-purchase flow plus the connected/ready preconditions.
integrations/overview.mdx — one added payments link.
docs.json — navigation entries for the new pages, plus redirects from /vaults/overview, /vaults/payments, /integrations/payments/link, /browsers/pay-through-browser-checkout, and /browsers/add-payments-to-browser-agent (none of these paths exist as pages on main). Theme, OpenAPI, and other site settings are unchanged.
style.css — opt-in .kernel-brand-name uppercase override. The existing global lowercase rule is unchanged.
images/integration-icons/payments.svg — static nav icon.
The copy-pasteable coding-agent tasks in the browser payments guide are documentation for developers, not product system prompts or model-instruction files.
No CODEOWNERS file exists. This automation already approved an earlier commit; that approval is left in place because risk is still Very Low.
Action: Comment only. Did not re-approve. Did not dismiss approval.
The reason will be displayed to describe this comment to others. Learn more.
Stale comment
Risk assessment: Very Low
Decision: Keep existing approval. Risk did not increase after the latest push.
Re-evaluated 8107eef...4ae4166 from the file diff. This remains a Mintlify documentation-only change. No application, API, SDK, CI, auth, billing, schema, or infrastructure files are modified.
Latest commit 4ae4166 edits only browsers/enable-payments-in-browser-agent.mdx: clarifies that wallet/card are KERNEL API resources (not the end user's real payment method), updates the responsibility matrix (application vs end user vs KERNEL vs provider), and rewords the once-per-user and per-purchase steps so the application creates vault resources after the end user initiates setup or confirms a purchase.
integrations/overview.mdx — one added payments link.
docs.json — navigation entries for the new pages, plus redirects from /vaults/overview, /vaults/payments, /integrations/payments/link, /browsers/pay-through-browser-checkout, and /browsers/add-payments-to-browser-agent (none of these paths exist as pages on main). Theme, OpenAPI, and other site settings are unchanged.
style.css — opt-in .kernel-brand-name uppercase override. The existing global lowercase rule is unchanged.
images/integration-icons/payments.svg — static nav icon.
The copy-pasteable coding-agent tasks in the browser payments guide are documentation for developers, not product system prompts or model-instruction files.
No CODEOWNERS file exists, and the main ruleset does not require code-owner review. This automation already approved an earlier commit; that approval is left in place because risk is still Very Low.
Action: Comment only. Did not re-approve. Did not dismiss approval.
The reason will be displayed to describe this comment to others. Learn more.
Stale comment
Risk assessment: Very Low
Decision: Keep existing approval. Risk did not increase after the latest push.
Re-evaluated 8107eef...6219541 from the file diff. This remains a Mintlify documentation-only change. No application, API, SDK, CI, auth, billing, schema, or infrastructure files are modified.
Latest commit 6219541 edits only browsers/enable-payments-in-browser-agent.mdx: adds a fail-closed purchase-verification gate (treat agent-proposed merchant/amount/currency/cart as untrusted, compare against a trusted backend or deterministic page extraction, freeze the confirmed object) and updates the responsibility matrix plus the copy-pasteable CLI walkthroughs to match.
integrations/overview.mdx — one added payments link.
docs.json — navigation entries for the new pages, plus redirects from /vaults/overview, /vaults/payments, /integrations/payments/link, /browsers/pay-through-browser-checkout, and /browsers/add-payments-to-browser-agent (none of these paths exist as pages on main). Theme, OpenAPI, and other site settings are unchanged.
style.css — opt-in .kernel-brand-name uppercase override. The existing global lowercase rule is unchanged.
images/integration-icons/payments.svg — static nav icon.
The copy-pasteable coding-agent tasks in the browser payments guide are documentation for developers, not product system prompts or model-instruction files.
No CODEOWNERS file exists, and the main ruleset does not require code-owner review. This automation already approved an earlier commit; that approval is left in place because risk is still Very Low.
Action: Comment only. Did not re-approve. Did not dismiss approval.
The reason will be displayed to describe this comment to others. Learn more.
Stale comment
Risk assessment: Very Low
Decision: Keep existing approval. Risk did not increase after the latest push.
Re-evaluated 8107eef...a673caa from the file diff. This remains a Mintlify documentation-only change. No application, API, SDK, CI, auth, billing, schema, or infrastructure files are modified.
Latest commit a673caa edits only those MDX pages: documents production payment safeguards (one wallet per provider, keep action URLs out of the coding agent, verify presentment pricing, collect merchant-required customer fields separately, observe approval concurrently, treat the merchant order as the success authority, and assert Agentcard mode from deployment config).
integrations/overview.mdx — one added payments link.
docs.json — navigation entries for the new pages, plus redirects from /vaults/overview, /vaults/payments, /integrations/payments/link, /browsers/pay-through-browser-checkout, and /browsers/add-payments-to-browser-agent (none of these paths exist as pages on main). Theme, OpenAPI, and other site settings are unchanged.
style.css — opt-in .kernel-brand-name uppercase override. The existing global lowercase rule is unchanged.
images/integration-icons/payments.svg — static nav icon.
The copy-pasteable coding-agent tasks in the browser payments guide are documentation for developers, not product system prompts or model-instruction files.
No CODEOWNERS file exists, and the main ruleset does not require code-owner review. This automation already approved an earlier commit; that approval is left in place because risk is still Very Low.
Action: Comment only. Did not re-approve. Did not dismiss approval.
The reason will be displayed to describe this comment to others. Learn more.
Risk assessment: Very Low
Decision: Keep existing approval. Risk did not increase after the latest push.
Re-evaluated 8107eef...4350e12 from the file diff. This remains a Mintlify documentation-only change. No application, API, SDK, CI, auth, billing, schema, or infrastructure files are modified.
Latest commit 4350e12 edits only browsers/enable-payments-in-browser-agent.mdx and integrations/payments/agentcard.mdx: documents the first Agentcard checkout sequence, live-view embedding, concurrent observation/cleanup, truthful merchant disclosure fields, and treating structured payment-link data plus the merchant order record as the success authority.
integrations/overview.mdx — one added payments link.
docs.json — navigation entries for the new pages, plus redirects from /vaults/overview, /vaults/payments, /integrations/payments/link, /browsers/pay-through-browser-checkout, and /browsers/add-payments-to-browser-agent (none of these paths exist as pages on main). Theme, OpenAPI, and other site settings are unchanged.
style.css — opt-in .kernel-brand-name uppercase override. The existing global lowercase rule is unchanged.
images/integration-icons/payments.svg — static nav icon.
The copy-pasteable coding-agent tasks in the browser payments guide are documentation for developers, not product system prompts or model-instruction files.
No CODEOWNERS file exists, and the main ruleset does not require code-owner review. This automation already approved an earlier commit; that approval is left in place because risk is still Very Low.
Action: Comment only. Did not re-approve. Did not dismiss approval.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
AnnaXWang
changed the title
description
restructure the initial vault and payment documentation around the primitive, integrations, and user task:
vaultspage that introduces the general sensitive-value primitive before covering write-only values, aliases, immutable browser attachment, egress substitution, the initial payment contract, and future item types.paymentscategory under integrations with an overview, the supplied navigation icon, and individual stripe link and agentcard pages. the provider pages link to their respective sites, and the overview directs developers to request additional native integrations through support.Enable Payments in a Browser Agentbeside the playwright/computer-use guide. the walkthrough follows the shared provider flow: collect the payment method in a hosted surface, prepare aliases, attach the vault, pass only aliases to the agent, observe approval outside the agent, and reconcile the merchant outcome. it opens with a provider trade-off table and copy-pasteable coding-agent tasks for exercising either the stripe link or agentcard path through the CLI. a responsibility matrix separates application, end-user, browser-agent, KERNEL, and provider work: the end user creates the purchase intent, while the application translates it into KERNEL api resources. before creating or authorizing a card, the application must independently verify the agent's proposed merchant, amount, currency, and cart, present those verified values for confirmation, and fail closed if any value cannot be verified or disagrees. it also documents behavior when a wallet is missing or not connected. shared examples name the vault for an application end user rather than a checkout.kernel vaultsandkernel browsers create --vaultcommands.payments are the first application of vaults. the primitive page explains broader credential and identity use cases while explicitly limiting the current release to wallets and cards for stripe link and agentcard. stripe link examples also match the current live-only card contract and omit the unsupported
spec.testfield.testing
mint validatemint broken-linkscompile()kernel/clicommand definitionsgit diff --checkkernel/kernelcommit256e757no live-provider enrollment or merchant payment was performed.