Local API

eve starts the local runtime on localhost. It serves the web UI, local API, and MCP endpoint.

Endpoints

GET  /api/config
GET  /api/compare?from={snapshotId}&to={snapshotId}
GET  /api/search
GET  /api/snapshots
GET  /api/snapshots/{snapshotId}
GET  /api/repos
GET  /api/repos/{repoId}
GET  /api/repos/{repoId}/pending
POST /api/repos/{repoId}/open-editor
GET  /api/repos/{repoId}/snapshots
GET  /api/repos/{repoId}/snapshots/{snapshotId}
GET  /api/repos/{repoId}/snapshots/{snapshotId}/code/files
GET  /api/repos/{repoId}/snapshots/{snapshotId}/code/file?path={path}&mode=diff|full
GET  /api/repos/{repoId}/snapshots/{snapshotId}/sessions
GET  /api/repos/{repoId}/snapshots/{snapshotId}/sessions/{sessionKey}
POST /api/repos/{repoId}/snapshots/{snapshotId}/checkout
GET  /api/plan-requests?status={state}
GET  /api/plan-requests/{planRequestId}
GET  /api/plan-requests/events
POST /api/plan-requests/{planRequestId}/approve
POST /api/plan-requests/{planRequestId}/reject
POST /mcp

Intended use

The local API supports the bundled eve UI and local development tooling. For agent integration, prefer MCP resources and tools because they expose product-history operations directly.

/api/compare returns the same product-state comparison used by the repository Compare tab. Both snapshot ids must belong to the same repository.

The Snapshot code endpoints expose the relevant code behind a Snapshot without turning the record into code review. code/files derives curated files from existing Snapshot evidence and includes all changed files with preview metadata. code/file returns raw diff hunks or full file content at the Snapshot Git state; the UI performs client-side Shiki highlighting.

/api/search and the global /api/snapshots endpoints support the local UI's cross-repository snapshot lookup. Repository-scoped endpoints remain available under /api/repos/{repoId}.

/api/repos/{repoId}/pending reports committed work that has not yet been resolved by a Snapshot or Skip. Pending state is advisory; Snapshots remain the only user-facing product-history records.

The Plan request endpoints power the local approval queue. Approval and rejection mutations require expectedRevision; approval may include edited proposal content. Revision or stale-context conflicts return 409, and invalid edited content returns 422. The events endpoint streams queue updates with server-sent events.

Security

Keep the runtime bound to localhost. Do not expose the local API to untrusted networks or untrusted agent clients.