Documentation
AIPI is a local-first API integration intelligence workspace. The local companion indexes code, runs requests, and stores evidence; the interface and MCP tools let your coding agent work with that evidence without uploading the repository.
The shortest path: initialize AIPI in a repository, ask your agent to discover task context, prepare the bounded handoff, then run the revision-linked verification plan.
Getting started
Install AIPI, initialize a repository, and verify your IDE connection.
5 MINK Maps
Read the caller-to-handler graph, contract state, findings, and evidence.
8 MINMCP tools
Discover, prepare handoffs, run verification, and inspect evidence from an agent.
12 MINLocal + cloud
Understand the local execution boundary, pairing, and optional team metadata.
6 MINCore model
AIPI organizes work around four connected records:
- Contract — normalized method, route, environment, and schema.
- K Map — the implementation chain and related source references.
- Evidence — a redacted runtime request, response, diff, or diagnostic.
- Verification receipt — the checks and source revision that proved a change.
Need the command?
npx @vmise/aipi-companion@latest init