REM Vibe Coder docs

Developers

The REM Vibe Coder API, its events stream, MCP and agent integration, webhooks and export formats - for people who script or integrate Vibe Coder.

Everything the web app does goes through one HTTP API under https://remvibecoder.com/api/v1. It is a JSON API (django-ninja) with the same rules for the web app and for your scripts: you see and change only your own chats and projects.

At a glance

Base URL

https://remvibecoder.com/api/v1

Format

JSON in and out; errors as {"code": "...", "detail": "..."}

Sign-in

REM Auth (OpenID Connect); the API uses the resulting session

Live updates

Server-Sent Events per run, with replay from any sequence number

Health

GET /api/v1/health (no sign-in): {"status": "ok", "checks": {"db", "redis", "engine"}, "modules": {...}}

Two things to know first

  1. One message = one run. POST /chats/{id}/messages starts a run (a build, a change, or an answer). Everything that happens in it is an event with a sequence number. Your client follows the events; it never polls the code.

  2. Ownership is a 404. A chat, run or project that is not yours answers 404, exactly like one that does not exist.

Download: PDF · Word · Markdown

Developers | REM Vibe Coder · REM Vibe Coder