AI-programming interface for API work

API changes should finish with proof.

AIPI gives coding agents the exact implementation chain, bounded context, and verification loop they need to change APIs without guessing.

Local-first MCP-native No repo upload
AIPI / launch-readiness
LOCAL
ACTIVE TASK · API CONTRACT
GET/patient/launch_patient
CALLERAppSidebar.tsxline 218
→
ROUTElaunch_patientmismatch
→
SCHEMAPatientSession1 drift
−userId: numbercaller
+patient_id: stringhandler
VERIFICATION RECEIPT3 checks passed
VERIFIED
Revision 8f3a1c · Development · 38ms
00 / WHY

Your agent can write the change. It still needs to know what the change can break.

01

Frontend calls, backend handlers, schemas, and tests live in different places.

02

Logs say what failed. They rarely identify the responsible contract and code path.

03

“Looks fixed” is not a revision-linked replay, diff, or proof receipt.

01 / THE LOOP

From intention to verified change.

AIPI is the evidence layer beside your agent—not another editor, chat, or giant context window.

01

Discover task context

AIPI searches local workspace files, AST symbols, K Map contracts, findings, and runtime evidence—then traces the smallest relevant chain.

caller → route → handler → schema → test
02

Prepare a bounded handoff

The agent receives a compact, revision-aware context pack instead of an unbounded repository dump. You keep the coding agent you already use.

620 / 2,400 tokens
03

Verify the change

AIPI runs the saved replay, contract diff, and linked checks, then records an immutable proof receipt against the active Git revision.

verified @ 8f3a1c
02 / K MAPS

See the integration—not just the endpoint.

K Maps connect every API contract to the code and evidence around it. Open a source reference in your IDE, inspect a schema drift, or jump straight into a replay.

  • Implementation chains across frontend, routes, models, schemas, and tests.
  • Revision awareness so stale proof never looks current.
  • Evidence receipts with redacted request, response, timing, and checks.
Explore K Maps documentation
KNOWLEDGE MAP · CHECKOUT6 NODES / 7 EDGES
FRONTENDCheckoutPanel.tsxfetch /api/orders
CALLERuseCheckout()payload · 4 fields
POST/api/ordersCONTRACT · VERIFIED
SCHEMAOrderInputzod · 4 fields
PROOFapi-replay200 · 41ms
03 / WHERE YOU WORK

One local engine. Every coding surface.

EXTENSION

VS Code + Cursor

A narrow, native side-panel for task context, K Maps, agent handoff, and verification.

Installation guide
STDIO MCP

Any MCP client

The same tool contract works without the UI. Your editor remains the control plane.

Browse MCP tools
127.0.0.1
04 / LOCAL BY DEFAULT

Your source, credentials, payloads, and private network stay on your machine.

The companion binds to loopback, redacts sensitive evidence, and serves MCP over local stdio. Cloud sync is opt-in and designed for shared contract metadata—not captured payload bodies.

Read the data boundary
05 / INSTALL

From repository to evidence loop in one command.

AIPI detects your project structure, writes project-local MCP configuration, and starts or reuses the local companion.

No global install No cloud account required Preserves existing MCP config
Terminalzsh

# Run inside the repository you want AIPI to understand

$ npx @vmise/aipi-companion@latest init
✓ project indexed
✓ Codex, Cursor & VS Code configured
✓ local companion ready
07 / TEAM CLOUD

Local speed. Shared confidence.

Create a cloud account to follow team sync, shared environments, CI receipts, and governance features as they become available. Local AIPI stays usable without an account.

START WITH ONE REPOSITORY

Give your coding agent something better than a guess.

Install AIPI