API Reference
This section documents the public Tuturuuu HTTP API. It is reference material for integrators calling Tuturuuu endpoints from outside the platform.Tuturuuu is mid-migration from the legacy
apps/web Next.js platform
(port 7803) to a TanStack Start frontend plus a dedicated Rust backend
(port 7820). Endpoint hosts and paths may shift as routes move behind the
Rust backend. See
Tanstack + Rust migration
for the current state.What this API covers
Today this section documents the public AI generate endpoint, which lets you run text completions against supported models using a workspace API key. See Generate AI Completion. More public endpoints will be documented here over time. The full surface of internal and migrated platform routes is defined by the backend OpenAPI contract rather than enumerated here.Authentication
Authentication depends on the endpoint:- Workspace API keys. The public AI generate endpoint authenticates with a
workspace-scoped API key, supplied in the request body as an
accessKeyobject containing anidand avalue. Keys are validated against theworkspace_api_keystable and must carry the scope for the model you request. - Bearer tokens / session cookies. Migrated platform routes behind the Rust
backend authenticate the caller’s Supabase session — either a browser session
cookie or a
Bearertoken — and some accept app-session tokens. These routes are not general-purpose public endpoints; they back first-party Tuturuuu apps.
Canonical OpenAPI specification
The authoritative machine-readable contract for the Rust backend lives in the repository at:Tuturuuu Rust Backend API spec is the source of truth for migrated routes,
their request/response schemas, security requirements, and status codes. The
legacy public API also lives under apps/web/src/app/api/v1 until the
corresponding routes finish moving behind the Rust backend.