Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/karpathy/llm-council/llms.txt

Use this file to discover all available pages before exploring further.

LLM Council exposes a lightweight REST API through its FastAPI backend, running on http://localhost:8001. All endpoints accept and return JSON, require no authentication, and are designed exclusively for local use. CORS is pre-configured to allow requests from http://localhost:5173 (Vite dev server) and http://localhost:3000, so the bundled React frontend works out of the box without any additional setup.
The API is stateful — you must create a conversation before you can send messages to it. Every message endpoint requires a valid conversation_id obtained from POST /api/conversations.

Base URL

http://localhost:8001
All resource endpoints are prefixed with /api/. The single exception is the root health check at /.

Request & Response Format

Every request body must be sent as JSON with the Content-Type: application/json header. All successful responses are returned as JSON. HTTP status codes follow standard conventions: 200 for success, 404 when a resource is not found.

Authentication

No authentication is required. The server is intentionally designed for local-only use and does not implement API keys, tokens, or session management.

Health Check

Ping the root endpoint to verify the backend is running before making any API calls.
curl http://localhost:8001/
Response:
{
  "status": "ok",
  "service": "LLM Council API"
}

Endpoint Reference

MethodEndpointDescription
GET/Health check — confirms the backend is alive
GET/api/conversationsList all conversations, newest first
POST/api/conversationsCreate a new empty conversation
GET/api/conversations/{id}Get a full conversation with all messages
POST/api/conversations/{id}/messageSend a message and run all 3 council stages (blocking)
POST/api/conversations/{id}/message/streamSend a message and receive stage updates via SSE

Explore the API

Conversations

Create, list, and retrieve conversations along with their full message history.

Messages

Send a message and block until all three council stages have completed.

Streaming

Receive real-time stage-by-stage progress via Server-Sent Events.

Build docs developers (and LLMs) love