apisloth
APISLOTHStart watching
Continuous change desk/ Edition 001

When the APIs you depend on change, apisloth updates your code.

apisloth watches OpenAPI contracts, finds the change that matters, updates the repositories it affects, and opens a pull request with the evidence attached.

Connect your first APIInspect a simulated run
INPUTOpenAPI contracts
OUTPUTReviewable pull requests
PROOFVerification tier attached

The control loop / 04 stages

A quiet system for a noisy dependency.

API migrations usually arrive as surprise project work. apisloth turns them into a repeatable loop: observe, isolate, implement, prove. You review the pull request instead of rediscovering the contract.

  1. ObserveSPEC SNAPSHOT

    Watch the contract.

    apisloth periodically scrapes the OpenAPI documents your repositories depend on.

  2. IsolateSEMANTIC DIFF

    Separate signal from churn.

    A structured diff identifies endpoints, schemas, and requirements that actually changed.

  3. ImplementSCOPED EDIT

    Change the right code.

    Codex receives the old spec, new spec, repository context, and the exact contract delta.

  4. ProvePULL REQUEST

    Open a verified PR.

    The update is built, tested, contract-checked when possible, and reported without hand-waving.

Simulated run / honest output

A change arrives at 03:17. A pull request leaves before stand-up.

This static trace mirrors the full path: stored snapshots, structured contract diff, repository-aware implementation, and explicit verification.

run_1842 / billing-client
PR ready for review
Contract delta4 additions / 2 removals

@@ components.schemas.Subscription

− enum: [starter, pro]

+ enum: [free, growth, scale]

+ required: [billing_email]

@@ POST /v1/subscriptions

− 200 application/json

+ 201 application/json

Implementation traceelapsed 00:00:54
  • 03:17:08specnew snapshot stored
  • 03:17:09diff2 breaking changes
  • 03:17:14editclient + fixtures updated
  • 03:18:02verifytier T3 achieved

Proposed branch

apisloth/update-run_1842

T3
Build ✓Tests ✓Contract ✓

Verification / no silent skips

Proof has a name.

Every pull request states exactly how far verification got. When automation cannot run, apisloth says so and leaves a manual path forward.

T0

Manual handoff

Nothing runnable. The PR is marked unverified and includes a concrete test checklist.

Checklist attached

T1

Build confidence

The detected build, typecheck, or lint command completes against the proposed change.

Build passes

T2

Repository proof

Your repository’s own test suite passes with the implementation in place.

Tests pass

T3

Contract proof

Tests are rerun against a mock server synthesized from the new API specification.

New contract passes

The next contract change is already scheduled

Let it become a pull request, not a fire drill.

Create your workspace

Public signup / no card required