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.
Authentication
Sessions, CSRF, stream tickets and signed links; roles and errors.
API reference
Chats, messages, runs, plans, questions, projects, code, billing - with examples.
Run events and streaming
The event types of a build and how to follow one live over SSE.
MCP and agents
Your MCP servers in builds, building MCP servers, and the REM CloudHub tools.
Webhooks
Payment events, content revalidation and the REM Platforms event feed.
Export formats
The code zip, the git repository layout, documents and the generated README.
At a glance
Base URL |
|
Format | JSON in and out; errors as |
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 |
|
Two things to know first
One message = one run.
POST /chats/{id}/messagesstarts 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.Ownership is a 404. A chat, run or project that is not yours answers
404, exactly like one that does not exist.