Integrations
One agent.Every integration that matters.
Stripe is the first API Mantle maintains, in TypeScript and JavaScript repositories on GitHub. Each integration below is supported today; nothing on this page is a roadmap.
Supported today
01 · GitHub
Installed as a GitHub App, on the repositories you choose.
Mantle reads code through the app installation and pushes one branch per migration. It opens the pull request and sees whether you merged it. No passwords, no personal access tokens.
| Permission | Access | Why |
|---|---|---|
| Contents | Read and write | Read code to analyze it, and push the migration branch. |
| Pull requests | Read and write | Open the pull request and see whether you merged it. |
| Metadata | Read | Required by GitHub for every app. |
| Email addresses | Read | Identify your account when you sign in. |
02 · Stripe
Changes read from Stripe’s own sources.
Mantle parses Stripe’s published changelog and API specification into structured records, then decides repository by repository whether anything needs to change. No web page is handed to a model.
Remove support for `payment_method_types` on `Checkout.SessionCreateParams`
changeType field_removed breaking true symbol Checkout.SessionCreateParams field payment_method_types sdkCall stripe.checkout.sessions.create()
03 · TypeScript and JavaScript
Your code is parsed, not pattern-matched.
Mantle builds a syntax tree of your repository and follows your Stripe client through wrappers to every call site. Verification runs the scripts in your package.json, with npm, pnpm or Yarn.
- Client
src/lib/stripe.tsexport const stripe = new Stripe(key) - Imported by
src/payments/checkout.tsimport { stripe } from '../lib/stripe' - Call site
src/payments/checkout.ts:17stripe.checkout.sessions.create() - Passes
payment_method_typesAffected: the parameter was removed
What comes next
Stripe is the first API Mantle maintains, not the last.
Detection, impact analysis and verification are written against an API provider interface, not against Stripe. Adding an API means writing an adapter, not rebuilding the product. Payments, messaging, auth, infrastructure: the plan is to cover all the APIs your product actually depends on.
We will say so here when one is ready, and not before. Everything in the list above is supported today.