AI maintenance engineer for third-party APIs
Stop maintaining third-party APIs by hand.
compat watches the SDKs your code depends on. When a breaking change affects your repository, it prepares the migration, runs your own checks, and opens a pull request for you to review.
1 repository · 3 migrations a month · no card
No auto-merge.No production secrets.Disposable sandboxes.
stripe 14.25.0 → 18.0.0
apiVersion pinned; Invoice.subscription moved under parent
New release detected…
Pull request
Opens here with the checks that ran. You merge.
Upgrade stripe 14 18
compat plans, edits, verifies, then opens the pull request.
- Repository
- Sandbox
- Plan
- Edit
- Verify
- Pull request
- Repository
- compat-playground
- Branch
- pending
- Wall clock
- 00:00
- Model cost
- metering
| Check | Command | Result |
|---|---|---|
| install | npm ci | queued |
| lint | no script | queued |
| typecheck | npm run typecheck | queued |
| test | npm run test | queued |
| build | no script | queued |
Works with the APIs your product depends on.
What breaks in each SDK →Missing yours? Tell us.Works with Stripe, OpenAI, Anthropic, Deepgram, ElevenLabs, RevenueCat, LiveKit, Supabase, Clerk, Twilio.
Breaking API changes in. Tested pull requests out.
Dependency bots update versions. compat updates the code that uses them.
01
Detect
compat identifies the integrations and upstream changes that affect your repository.
02
Migrate and verify
compat updates the affected code and runs your existing tests, type checks, lint and build where available.
03
Pull request
compat opens a PR with the changes, verification results, warnings and migration context.
Upstream releases
1 of 5 seen- Stripemajor
stripe 14.25.0 → 18.0.0
apiVersion pinned; Invoice.subscription moved under parent
just published_
compat
0 PRs · 0 dismissed- Read 11 release notes
- Judge against src/billing.ts
- verdict pending
- Sandbox
- Edit
- Verify
- Pull request
Your repository
pull requestsPull requests land here, each with the checks that ran.
The Stripe row is the real run, shown in full below. The other releases are illustrative.
See the full execution pipeline →A real migration. A real pull request.
Not a concept demo. This is the artifact compat ships: the diff, every check with its result, and the warnings it asked a person to confirm.
Stripe v14 → v18 · 2 files changed · 3 checks passed, 2 not run · 190 s · $0.57 model cost
- Repository
- compat-playground
- Migration
- Stripe v14 to v18
- Wall clock
- 190 s
- Agent turns
- 16
- Repairs
- 0
- Model cost
- $0.57
Migrate Stripe SDK from v14 to v18 #2
compat-devwants to merge 1 commit intomainfromintegration-maintenance/stripe/8f2c
- package.json+1-1
- src/billing.ts+3-2
package.json "dependencies": {- "stripe": "^14.25.0"+ "stripe": "^18.0.0" }src/billing.ts@@ apiVersion @@- apiVersion: "2023-10-16",+ apiVersion: "2025-08-27.basil",@@ handleWebhook @@- return { paid: true, subscription: invoice.subscription };+ const subscription = invoice.parent?.subscription_details?.subscription ?? null;+ return { paid: true, subscription };| Check | Command | Result |
|---|---|---|
| install | npm ci | ✓ 3.0 s |
| lint | no script | not run |
| typecheck | npm run typecheck | ✓ 6.0 s |
| test | npm run test | ✓ 1.1 s |
| build | no script | not run |
Warnings and manual steps
Copied from the pull request body. compat says what it could not prove.
- 1Confirm the Stripe account's API version is compatible with the 2025-08-27.basil pin.
- 2Review downstream consumers of handleWebhook().subscription: the value is now null for invoices not parented by a subscription.
Priced on engineering time saved, not model usage.
Every plan opens the same evidence-backed pull request. Tiers differ in repositories and jobs a month.
Free
$0no card
- Repositories
- 1 repository
- Jobs
- 3 jobs a month
A first migration on one repository.
Start free- All 10 providers
- Monitoring in propose mode
Starter
$99per month
- Repositories
- 2 repositories
- Jobs
- 30 jobs a month
One small service, a couple of SDKs to keep current.
Start free- All 10 providers
- Monitoring with auto-run
Team
$299per month
- Repositories
- 10 repositories
- Jobs
- 150 jobs a month
Several services, migrations arriving as pull requests instead of tickets.
Start free- Slack notifications
- Verification overrides per repository
Business
$799per month
- Repositories
- 50 repositories
- Jobs
- 600 jobs a month
Many repositories, custom providers, procurement paperwork.
Talk to sales- Custom providers
- Security review and DPA
Design partner
First ten teams$199 per month, locked for a yearUnlimited repositories during the partnership · Providers added on request · Direct line to the people building compat
Prices can change before general availability.
You decide how autonomous compat can be.
Every SDK in your code is checked daily. Pick a policy per repository.
01
Propose
compat detects the change, drafts the migration and waits for your approval.
02
Auto-run minors
Minor and patch migrations run on their own. Majors wait for you.
03
Auto-run everything
Every relevant release runs and arrives as a pull request.
Irrelevant releases never run. Every policy ends in a pull request you review.
Built to be trusted with your code
Read our security model →Disposable sandboxes
Every migration runs in an isolated environment that is destroyed afterward.
No production secrets
compat does not need your production credentials to migrate your code.
Humans merge
compat prepares and opens pull requests. Developers stay in control of merge.
Give compat one migration.
Connect a repository and let compat turn your next API change into a tested pull request.
1 repository · 3 migrations a month · no card