Launch support: JavaScript, TypeScript and Python projects using OpenAPI 3.x APIs, npm packages and PyPI packages.
See supported integrationsSelf-maintaining API integrations
Booleo finds code affected by an API or SDK change, prepares the update, runs your checks and opens a draft pull request for review.
Booleo opens a draft pull request. You decide what merges.
Impact found
retrieveUpcoming() removedconst invoice = await billing.invoices.createPreview({
customer: customerId,
});The SDK removed invoices.retrieveUpcoming() and replaced it with invoices.createPreview().
Impact found
retrieveUpcoming() removedsrc/billing/preview.tsconst invoice = await billing.invoices.retrieveUpcoming({
customer: customerId,
});const invoice = await billing.invoices.createPreview({
customer: customerId,
});Checks run
When an API version changes, developers still have to understand the change, locate every affected call, edit the code and test the result. GitHub's own API upgrade guide instructs developers to review the breaking changes, make the required integration changes and test the updated integration.[1]
Booleo turns that sequence into a reviewable result. It does not wait for a broken production integration to become the reminder.
Booleo monitors the API definitions and SDK versions your repository uses. It compares old and new OpenAPI 3.x definitions, tracks resolvable npm and PyPI version changes, and accepts migration guidance published by the API provider.
Language-aware parsing and code search locate direct HTTP calls and SDK usages that can be resolved. The impact report names the files, lines and reason each usage appears to be affected. When the available evidence is insufficient, Booleo says so.
Known migrations use fixed code transformations. Changes that depend on local context can use a coding model. Provider guidance, the old interface and the new interface stay attached to the migration so the task is more specific than a general repository edit.
Booleo verifies that generated SDK methods and types exist in the new SDK or API definition. This matters because API-migration research has documented models inventing imports, constructors and constants that are absent from the target interface.[2]
Booleo uses the repository's existing GitHub checks for typecheck, lint and tests. It does not add or edit workflow files. Passed and failed checks are reported by name. A patch from a repository without meaningful checks is labelled unverified.
The draft pull request includes the source API change, affected code, edits, check results and remaining human decisions. Add context and rerun when a migration needs information that the API definition could not provide.
Developers
Connect a repository and let Booleo detect the APIs and SDKs it appears to use. When a tracked interface changes, review the impact before Booleo attempts a patch. You receive a draft pull request in the workflow you already use.
API providers
Upload the previous and new OpenAPI definitions, add the intended migration guidance and preview the detected breaking changes. Customers choose whether to install Booleo and which repositories it can access. Their affected repositories can then receive a repair based on the same provider-backed instruction.
You see aggregate release and migration status. You do not see customer source code, filenames, functions or business logic.
Internal platform teams
Give platform teams one inbox for detected API and SDK changes across connected repositories. See which code appears affected, start or dismiss a migration, add team context and track draft pull requests without taking merge control away from repository owners.
Giving an agent a changelog can be useful after someone notices the change, identifies the right version, supplies enough repository context and decides how to verify the result. It does not create an ongoing connection between the API release and every affected repository.
Booleo adds the parts a one-off prompt does not provide by itself:
This is also why Booleo does not ask a model to judge its own work. Google's experience report says simple prompting is insufficient beyond the simplest migrations and describes combining models with syntax analysis, heuristics, validation and human review.[3] In the FreshBrew benchmark, the best tested agent completed 52.3% of whole-project Java migrations, useful evidence that agents can help and that reviewable verification still matters.[4]
Booleo uses AI as one implementation tool. Your checks and your review remain the decision points.
Dependabot automates dependency version updates, including manifests, lockfiles, vendored dependencies and GitHub Actions references.[5] Booleo focuses on application source changes required by API or SDK interface changes.
GitHub shows the requested permissions before installation and lets you choose only the repositories Booleo may access.[6] Booleo requests the permissions needed to inspect code, create a migration branch, run verification and open a draft pull request:
GitHub documents that creating a branch requires Contents write, creating a pull request requires Pull requests write, and reading Actions and Checks results requires read access.[7] Booleo does not request repository administration, secrets or workflow-write permission.
Booleo opens a draft pull request. You decide what merges.
No credit card is required for Free. Scans and impact previews do not consume migration attempts.
For trying Booleo on a real integration.
$0
For individual developers maintaining production integrations.
$19 per month
For product and platform teams maintaining several repositories.
$99 per month
For API companies helping customers adopt a release.
From $299 per month
Monthly billing at launch. No annual contract or annual discount. Plan usage is visible in Settings.
At launch, Booleo monitors OpenAPI 3.x definitions and resolvable version changes for npm and PyPI SDK packages. Developers can add an API manually, and API providers can submit a release with previous and new definitions plus migration guidance.
JavaScript, TypeScript and Python projects on GitHub are supported at launch. Java, Go, GitLab, Bitbucket, GraphQL and protobuf are not launch features.
No. Booleo reports direct HTTP and SDK usages it can resolve and explains why each location appears affected. Dynamic calls, wrappers and undocumented behavioral changes can require developer or provider context. When there is not enough information, Booleo says so.
No. Booleo creates a separate branch and opens a draft pull request. A developer reviews and decides whether to merge it. Booleo does not deploy customer code.
Booleo can prepare a patch, but it labels the result unverified. A successful typecheck or lint command is reported as that specific result, not as proof that the integration works at runtime.
The failure stays visible. You can add context and retry the repair, or continue the work manually from the draft pull request. Booleo does not turn a failed check into a success state.
No. A provider can see aggregate migration status for its release. It cannot see your source code, filenames, functions or business logic.
GitHub uses Contents write permission for creating and updating a branch. Booleo writes only to a separate migration branch and opens a draft pull request. It does not push to your default branch.[7]
Yes. Choose individual repositories during GitHub App installation. You can later remove a repository, revoke the installation or delete the Booleo organization.
No. Booleo does not send repository secrets, GitHub Actions secrets, environment values or credential files to a model. Common secret files are excluded before selected code context is collected.
A one-off agent prompt can help write code. Booleo continuously connects a versioned API or SDK change to affected repository usages, checks proposed symbols against the new interface, runs repository-owned verification, prevents duplicate pull requests and delivers the evidence for human review. The coding model is one worker in that system, not the judge of its own result.
Dependabot automates dependency version updates, including manifests, lockfiles, vendored dependencies and GitHub Actions references. Booleo focuses on application source changes required by API or SDK interface changes.[5]
No.
Connect one repository, review the APIs and SDKs Booleo detects, and run your first impact scan free.
Free plan. No credit card. You choose the repository.