ClaimUNVERIFIED
UNTRUSTED — VENDOR CHANGELOG, 2026-05-26The source parameter on Charges is removed as of API version 2026-05-28.
An announcement, not a fact. Nothing is dispatched on this alone.
HOW IT WORKS
How it works
A vendor announcement is a claim. A pull request is a conclusion. Seven stages make an API integration self-healing.
ONE CHANGE, ALL THE WAY THROUGH
ArtifactOBSERVED
POST /v1/charges
− source: string+ payment_method: stringSpec snapshot 2026-04-30 → 2026-05-28. The removal is observed, not reported.
ReachCONFIRMED
- billing/charges.py:84
- billing/refunds.py:31
- jobs/sync.py:210
3 confirmed sites, 3 of 4 repositories. Pinned stripe==12.4.0 — applicable.
- ANNOUNCED05-26
- CONFIRMED06-25
- PR OPENEDTODAY
- CUTOFF11-15
SEVEN STAGES
Seven stages
Watch the vendor
Vendor sources are polled continuously on a schedule and stored as snapshots. Nothing is inferred from a page as it looked once; the record is kept so a claim can be checked against it later.
Diff, then classify
A new snapshot is compared against the last. Where a spec is prose rather than schema, a model reads it under a strict output schema — so it can only produce a shape the pipeline understands, and it cannot name a symbol the snapshot does not contain.
Confirm against an artifact
The critical step. A spec snapshot or a live-API probe decides whether the change happened. The wording of a blog post never does, and if nothing was observed, nothing proceeds.
Find call sites
Repositories are indexed on install and re-indexed as you push. A confirmed change is matched against that index, then checked against the version you are pinned to — and a skip carries its reason, shown rather than hidden.
Re-confirm before spending
The runner clones fresh and re-confirms the call sites by content rather than by line number. Zero confirmed sites means the run exits having spent nothing, which is designed to happen often: acting on a stale index is how a wrong pull request gets written.
Write the fix
The agent edits files in a fresh clone with one capability. No tokens, no network, no git — and its licence is the single change it was dispatched for, at the sites that were confirmed. Not a sweep, not an upgrade, not tidying on the way past.
Verify, then open
m82 Labs records a test baseline before the agent runs and runs the suite again afterwards — both results its own, not the agent's report of its work. Then the pull request opens, carrying the spec diff, the confirmed sites, the version basis, both test runs, and anything the agent was unsure about, verbatim.
The only number that matters is how many opened pull requests are correct.
A skipped check is reported, not hidden.
EARLY ACCESS
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.