HTTP Server

A lightweight streaming HTTP server built on Bun.serve(). Exposes the full agent loop as an API with SSE streaming and synchronous endpoints.

ra --http                        # default port 3000
ra --http --http-port 8080       # custom port
ra --http --http-token secret    # with authentication

Endpoints

Endpoint	Method	Description
/chat	POST	SSE stream — real-time token streaming
/chat/sync	POST	Blocking JSON — waits for the full response
/sessions	GET	List stored sessions

Authentication

When --http-token is set, all requests require a Bearer token:

Authorization: Bearer <token>

Requests without a valid token receive a 401 Unauthorized response.

Request body

Both /chat and /chat/sync accept the same request body:

{
  "messages": [
    { "role": "user", "content": "Hello" }
  ],
  "sessionId": "optional-session-id"
}

Pass sessionId to resume a previous conversation. Omit it to start a new session.

Streaming response (/chat)

The streaming endpoint returns Server-Sent Events (SSE):

data: {"type":"text","delta":"Hello"}
data: {"type":"text","delta":" there!"}
data: {"type":"tool_call_start","id":"tc_1","name":"Read"}
data: {"type":"tool_call_delta","id":"tc_1","argsDelta":"{\"path\":\"src/index.ts\"}"}
data: {"type":"tool_call_end","id":"tc_1"}
data: {"type":"done","sessionId":"ses_abc123"}

Synchronous response (/chat/sync)

Returns the full response as JSON after the agent loop completes:

{
  "response": "Hello there!",
  "sessionId": "ses_abc123"
}

Configuration

app:
  http:
    port: 3000
    token: my-secret-token

Or via CLI flags:

ra --http --http-port 8080 --http-token secret

Example

# Streaming
curl -N http://localhost:3000/chat \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer secret" \
  -d '{"messages": [{"role": "user", "content": "Hello"}]}'

# Synchronous
curl http://localhost:3000/chat/sync \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer secret" \
  -d '{"messages": [{"role": "user", "content": "Hello"}]}'

See also

• HTTP API Reference — full endpoint specification
• Sessions — session persistence and resume
• Configuration — HTTP config fields