M82 LABS — EARLY ACCESS
m82 Labs watches the APIs you depend on, detects the breaking changes and deprecations, finds the call sites they reach, and opens a pull request carrying the evidence. What a self-healing API integration is →
THE PIPELINE
Five steps, and the second one is the product. Nothing reaches your repositories until the change has been confirmed against the vendor’s own spec.
WHAT LANDS IN YOUR REPO
A pull request that argues for itself.
billing/charges.py:84
- charge = stripe.Charge.create(amount=amount, source=token)+ charge = stripe.Charge.create(amount=amount, payment_method=token)jobs/sync.py:210 passes a token from a config value I could not resolve. The replacement is correct if that value is a payment method id. Worth a look.
BOUNDARIES
What m82 Labs will not do.
No auto-merge flag and no high-confidence bypass. Every fix waits for a person, every time.
The agent process can only edit files in a directory. git, tokens, network and merge decisions remain outside.
CI configuration, .env files and the git directory are off limits.
Only an artifact decides whether it happened, and a judgement with nothing observed behind it opens nothing.
VENDORS WATCHED
clean spec — teaches false positives
The claim is checked against the snapshot, so a heads-up never opens a pull request on its own.
high churn — model deprecations
Where the spec is quiet about a deprecation, the live API is asked directly before a line is written.
stale spec — forces the prose path
The change is read out of prose first, then confirmed against what the API actually answers.
dated versions — pinned callers
Three maintained specs, read as YAML and stored as JSON; a change lands in a dated version and a repo pinned before it is left alone.
not OpenAPI — a Discovery document
Google's own description of the API is diffed the same way, down to the field, with nothing invented to make it fit.
no spec at all — the SDK is the artifact
It publishes no machine-readable spec, so the generated client is read instead — and the dated retirement table is what gives you sixty days rather than a broken build.
an open slot — not a roadmap
The next vendor is decided by what teams actually ask for. Tell us which one you need.
PRICING
Plans that scale with your team.
$39/month
FEATURED
$129/month
$399/month
EARLY ACCESS
Connect a repository and m82 Labs shows you every vendor change that reaches it — including the ones that do not.
Diagram: the vendor APIs you use feed an engine that opens a single pull request, “Replace removed Charges.source with payment_method”, in your repositories acme/payments, acme/jobs and acme/legacy. How it works describes the same run in full.