Skip to main content

Base URL

faster proxy endpoint: (in progress)

Health Check

Check server status and cache performance.

Response

string
Service status: healthy or degraded
string
Server role: standalone, prefiller, or decoder
string
Model name being served
boolean
Whether GPU is available and initialized
boolean
Whether prefix caching is enabled
object
Cache performance statistics (if caching enabled)
float
Server uptime in seconds

Generate Prediction

Generate next action prediction from a prompt.

Request Body

string
required
rrweb event data as newline-delimited JSON. Each line should be a valid rrweb event object
integer
default:50
Maximum number of tokens to generate (range: 1-512)
float
default:0.3
Sampling temperature (range: 0.0-2.0). Lower values produce more deterministic outputs
boolean
default:false
Enable streaming response (currently not implemented)

Response

string
Generated rrweb event predictions as newline-delimited JSON
integer
Request processing latency in milliseconds
integer
Number of tokens generated in the response

Error Responses

All errors return JSON with a standard format:

Status Codes

Success
Request completed successfully
Bad Request
Invalid request parameters (e.g., temperature out of range)
Service Unavailable
Model not ready or server not initialized
Internal Server Error
Unexpected server error during prediction

Performance Tips

Optimize Cache Hits: Send rrweb events in consistent session sequences to maximize prefix cache reuse. Events from the same session with consistent ordering will achieve higher cache hit rates and lower latency.
Typical Latency:
  • Single-node: ~800ms (P50), ~1.5s (P99)
  • Disaggregated: ~250ms (P50), ~450ms (P99) (in progress)
  • Cache hit rate of 90%+ dramatically reduces latency for similar event sequences

rrweb Event Format

The API expects rrweb events as newline-delimited JSON strings. Common event types:
  • Type 2 (Meta): Page metadata and viewport info
  • Type 3 (Incremental): User interactions (clicks, input, scroll, etc.)
    • source: 2 = MouseInteraction
    • source: 5 = Input
    • source: 3 = MouseMove
  • Type 4 (IncrementalSnapshot): DOM mutations
Example event structure: