Repository navigation
Document MPP browser purchases - #646
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
fdd38a7 to
160f23e
Compare
There was a problem hiding this comment.
Risk assessment: Very Low
Approved. This change is documentation-only and does not alter application, auth, billing, or infrastructure behavior.
What changed
browsers/mpp.mdx(new): public guide for buying a browser session through the staging MPP endpointbrowsers/payments.mdx: one cross-link explaining that MPP pays for browser access, separate from merchant checkoutdocs.json: addsbrowsers/mppto the existing sidebar group
Why this is Very Low
- 84 additions across 3 files, no deletions, no production code paths
- No shared libraries, permissions, schema, or deployment config
docs.jsononly inserts a navigation page id next to the existing payments page- No code owner review is required on
main
The page documents an existing staging HTTP route and tells readers to treat returned connection URLs as credentials. That is explanatory copy, not a change to how those credentials are issued.
Sent by Cursor Automation: Assign PR reviewers
160f23e to
bf807ba
Compare
There was a problem hiding this comment.
Risk assessment: Very Low
Re-checked after the push to bf807ba. Risk did not increase, so the existing approval stands. This review does not add a second approval.
What changed since the previous approval (160f23e)
browsers/mpp.mdx: the "When to use mpp" section now distinguishes the MPP protocol (an agent paying a merchant) from KERNEL's endpoint (an agent paying KERNEL for browser access).browsers/payments.mdxanddocs.jsonare unchanged from the approved commit.
Full PR scope
- New public guide
browsers/mpp.mdx - One cross-link on
browsers/payments.mdx - Sidebar entry for
browsers/mppindocs.json
Why this stays Very Low
- Documentation and navigation only. No application code, auth, billing logic, schema, or deployment config.
- The new copy explains an existing staging route. It does not change how payments or browser connection URLs are issued.
- Code owner review is not required on
main(require_code_owner_reviewis false).
Sent by Cursor Automation: Assign PR reviewers
There was a problem hiding this comment.
Risk assessment: Very Low
Re-checked after the push to 290d024. Risk did not increase, so the existing approval stands. This review does not add a second approval.
What changed since the previous review (bf807ba)
browsers/mpp.mdx: one sentence now states the staging route accepts Stripe shared payment tokens (spt_...) only, and thatcardandlinkin the402challenge name methods the token can represent rather than credentials you can send to the endpoint.
Full PR scope
- New public guide
browsers/mpp.mdx - One cross-link on
browsers/payments.mdx - Sidebar entry for
browsers/mppindocs.json
Why this stays Very Low
- Documentation and navigation only. No application code, auth, billing logic, schema, or deployment config.
- The edit clarifies how an existing staging route is called. It does not change how payments or browser connection URLs are issued.
- Code owner review is not required on
main(require_code_owner_reviewis false).
Sent by Cursor Automation: Assign PR reviewers
There was a problem hiding this comment.
Risk assessment: Very Low
Re-checked after the push to 4d47538. Risk did not increase, so the existing approval stands. This review does not add a second approval.
What changed since the previous review (290d024)
browsers/mpp.mdxonly. The frontmatter description and the buyer-flow copy now document Link as the buyer path: the Link CLI retries with a Stripe shared payment token (spt_...), and KERNEL validates the token rather than the issuer. The Link CLI link points at Stripe's machine-payments docs.browsers/payments.mdxanddocs.jsonare unchanged.
Full PR scope
- New public guide
browsers/mpp.mdx - One cross-link on
browsers/payments.mdx - Sidebar entry for
browsers/mppindocs.json
Why this stays Very Low
- Documentation and navigation only. No application code, auth, billing logic, schema, or deployment config.
- The edit clarifies how an existing staging route is called. It does not change how payments or browser connection URLs are issued.
- No
CODEOWNERSfile is present, so code owner review is not required.
Sent by Cursor Automation: Assign PR reviewers
There was a problem hiding this comment.
Risk assessment: Very Low
Re-checked after the push to ca45bcd. Risk did not increase, so the existing approval stands. This review does not add a second approval.
What changed since the previous review (4d47538)
browsers/payments.mdx: the cross-link to the new MPP guide was removed (two lines). That file now matchesmain.
Full PR scope
- New public guide
browsers/mpp.mdx(staging MPP browser purchase flow, Link CLI example, and Playwright connection snippets) - Sidebar entry for
browsers/mppindocs.json
Why this stays Very Low
- Documentation and navigation only. No application code, auth, billing logic, schema, or deployment config.
- The page describes an existing staging route. It does not change how payments or browser connection URLs are issued.
- Code owner review is not required on
main(require_code_owner_reviewis false).
Sent by Cursor Automation: Assign PR reviewers
There was a problem hiding this comment.
Risk assessment: Very Low
Re-checked after the push to 35352f2. Risk did not increase, so the existing approval stands. This review does not add a second approval.
What changed since the previous review (ca45bcd)
- The guide moved from
browsers/mpp.mdxtoinfo/mpp.mdx, anddocs.jsonmoves the sidebar entry from the browsers group to the end of Info. - The page now documents the production host
https://api.onkernel.com/mpp/browsersinstead of the staging host, drops the staging warning, and shows a Link CLI pay command with an approved spend request instead of--test.
Full PR scope
- New public guide
info/mpp.mdx - Sidebar entry for
info/mppindocs.json
Why this stays Very Low
- Documentation and navigation only. No application code, auth, billing logic, schema, or deployment config.
- The edit changes which host and commands the docs describe. It does not change how payments or browser connection URLs are issued.
- Code owner review is not required on
main(require_code_owner_reviewis false). NoCODEOWNERSfile is present.
Sent by Cursor Automation: Assign PR reviewers
There was a problem hiding this comment.
Risk assessment: Very Low
Re-checked after the push to d640fd6. Risk did not increase, so the existing approval stands. This review does not add a second approval.
What changed since the previous review (35352f2)
info/mpp.mdx: one sentence no longer links tohttps://api.onkernel.com/openapi.json. It now tells readers to read the402challenge for the current price and duration.
Full PR scope
- New public guide
info/mpp.mdx - Sidebar entry for
info/mppindocs.json
Why this stays Very Low
- Documentation and navigation only. No application code, auth, billing logic, schema, or deployment config.
- The latest edit is a one-line copy change on a docs page. It does not change how payments or browser connection URLs are issued.
- Code owner review is not required on
main(require_code_owner_reviewis false). NoCODEOWNERSfile is present.
Sent by Cursor Automation: Assign PR reviewers
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using default effort and found 2 potential issues.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Want higher recall? High effort reviews run extra passes and find more bugs. A team admin can switch effort levels in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit e823419. Configure here.
|
|
||
| [machine payments protocol (mpp)](https://mpp.dev/) is an open protocol co-authored by stripe and tempo. it uses an http `402` challenge so an agent can pay for an api request without a checkout page. KERNEL accepts mpp payments for browser sessions: an agent pays with a stripe shared payment token, then connects to the browser over cdp. this route doesn't require a KERNEL account or api key. | ||
|
|
||
| the mpp price is $0.50 for one stealth, headful browser for 30 minutes. read the `402` challenge to confirm the current price and duration before paying. |
There was a problem hiding this comment.
Unescaped dollar amount in MDX
Medium Severity
The MPP price uses an unescaped $ in MDX. Mintlify treats paired dollar signs as KaTeX, which can garble this amount if another $ appears on the page.
Triggered by learned rule: Escape dollar signs in MDX to prevent Mintlify LaTeX rendering
Reviewed by Cursor Bugbot for commit e823419. Configure here.
| 2. the link cli gives you an approval url. after you approve the payment through link, it retries the request with `Authorization: Payment <credential>`. | ||
| 3. KERNEL verifies and charges the credential, creates the browser, and returns its connection urls in a `200` response. the `Payment-Receipt` header contains the mpp receipt. | ||
|
|
||
| link through the link cli is the only supported payment flow for now. after approval, the cli sends a credential containing a [stripe shared payment token](https://docs.stripe.com/agentic-commerce/concepts/shared-payment-tokens) (`spt_...`) to KERNEL. |
There was a problem hiding this comment.
Link product name is incomplete
Low Severity
The page refers to the payment product as link and stripe's link cli without introducing it as link by stripe first.
Additional Locations (2)
Reviewed by Cursor Bugbot for commit e823419. Configure here.




summary
document the production mpp browser purchase flow under Info, with the page last in that section. show the single
link-cli mpp paycommand, which presents a Link approval URL and completes the payment after approval. describe the browser connection response and safe retries. clarify that Link via the CLI is the only supported payment flow for now; standalone card credentials and stablecoin payments are not offered. distinguish paying for KERNEL browser access from merchant checkout.verification
/info/mppin the local Mintlify preview before the final copy updatedocs.jsonand rangit diff --check402MPP challenge for a $0.50, 30-minute browser