M82 Labs — home
SIGN INGET STARTED

M82 LABS

Never miss a vendor API deprecation.

M82 Labs finds the code each change hits and opens a tested pull request. You review and merge.

Self-maintaining API integrations →

GET STARTEDHOW IT WORKS
VENDOR API CHANGES — FOUND · CONFIRMED · FIXED — 

THE PIPELINE

Every fix arrives with its evidence.

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.

  1. 01

    Detect

    Every watched vendor’s spec and changelog is polled and stored as a snapshot. A new snapshot is diffed against the last one, and the difference is what starts everything.

    Poll · Snapshot

  2. 02

    Confirm

    An announcement is a claim. A spec snapshot or a probe of the live API decides whether the change actually happened — never the wording of a blog post.

    Spec probe · Live API

  3. 03

    Match

    Call sites are found across your repositories and checked against the version you are pinned to. If the change cannot reach your code, nothing else happens.

    Call sites · Pins

  4. 04

    Fix

    An agent edits files in a fresh clone. It holds no credentials, reaches no network, and its licence to edit is bounded by the one change it was sent for.

    Fresh clone · Sandboxed

  5. 05

    Verify

    M82 Labs runs your tests, checks what was touched against what was allowed, and opens a pull request carrying all of it.

    Tests · Review

WHAT LANDS IN YOUR REPO

A pull request that argues for itself.

The diff, the evidence and the test run, in one place.

PULL REQUESTacme/payments
Vendor
Stripe
Change
Charges.source removed
Confirmed by
spec snapshot 2026-08-01
Reach
3 of 4 repositories
  • acme/payments
  • acme/jobs
  • acme/legacy
  • acme/docs

billing/charges.py:84

- charge = stripe.Charge.create(amount=amount, source=token)+ charge = stripe.Charge.create(amount=amount, payment_method=token)
baseline126 passed2 failedafter fix128 passed0 failed

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

Limits with no off switch.

What M82 Labs will not do.

  • Never merges

    No auto-merge flag and no high-confidence bypass. Every fix waits for a person, every time.

  • Agent holds no credentials

    The agent process can only edit files in a directory. git, tokens, network and merge decisions remain outside.

  • Never touches workflows, secrets or lockfiles

    CI configuration, .env files and the git directory are off limits.

  • Never opens a PR on opinion

    Only an artifact decides whether it happened, and a judgement with nothing observed behind it opens nothing.

VENDORS WATCHED

The APIs your code depends on.

Eight APIs today, with more on the way.

  • Stripe

    Payments, subscriptions and invoicing

  • OpenAI

    Hosted models, audio and embeddings

  • Slack

    Team messaging, bots and app surfaces

  • Clerk

    Sign-up, sessions and organisations

  • Firebase Authentication

    Hosted sign-in and identity tokens

  • Anthropic

    Claude models over an API

  • Resend

    Transactional email and delivery webhooks

  • Shopify

    Products, orders and inventory over GraphQL

  • Coming soon

    Decided by what teams ask for

PRICING

Pick a plan, start shipping fixes.

Every feature on every plan. Change or cancel any time.

Starter

$39/month

Repositories monitored
3
Pull requests per month
10
Evidence for every change
Included
GET STARTED

FEATURED

Team

$139/month

Repositories monitored
10
Pull requests per month
50
Evidence for every change
Included
GET STARTED

Scale

$299/month

Repositories monitored
30
Pull requests per month
200
Evidence for every change
Included
GET STARTED
Full comparison

GET STARTED

Find out what your repos are already behind on.

Connect a repository and M82 Labs shows you every vendor change that reaches it — including the ones that do not.

GET STARTED

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.