Session API. Super simple. Super flexible.
Session Infrastructure.
At its simplest, cerver gives every user in your AI app a session — persistent, queryable, theirs. The model writing it and the compute running it are config; switch either one anytime, or run several in parallel on the same intent and curate the winner. One API.
$ curl -X POST https://gateway.cerver.ai/v2/sessions \ -H "Authorization: Bearer $CERVER_API_TOKEN" → { "session_id": "sess_a4f7c9...", "status": "ready" } $ ▌
Free at hobby scale. Free for the agents you build on it.
auth.py · 240 linesmiddleware.py + routes.pyEvery layer. Yours to swap.
A session isn't just the chat. It's the chat plus the model writing it plus the compute running it plus the row in your database. Cerver gives you all four as one object — and each one is config you can change without breaking the others.
One API.
Cerver gives you one interface for creating, running, switching, measuring, and closing AI sessions. But a good session layer should not only be reliable.
POST /v2/sessions POST /v2/sessions/:id/run-llm POST /v2/sessions/:id/compute GET /v2/sessions/:id/metrics POST /v2/sessions/:id/close
Every session, one screen.
A dashboard for every session your code creates — across users, computes, and AI providers. Peek inside, resume any of them, terminate, download the transcript. The control plane comes with the API; no extra plumbing.
Reliable is the baseline. Powerful is the point.
Cerver sessions are stable, transparent, and hard to accidentally break. They keep memory, tools, compute, billing, recovery, and user state together while your AI stack changes underneath. And they do more than hold state: they can switch models, move compute, track cost, recover runs, and spawn other sessions.