Skip to main content
The AI Studio API is served from https://ai.tuturuuu.com and accepts workspace-scoped ttr_ai_ credentials through the standard bearer header:
The plaintext credential is shown once. Store it in a secret manager and never place it in browser bundles, URLs, logs, or source control.
For a workspace-aware quickstart with copyable cURL and server-side TypeScript examples, open AI Studio, select a workspace, and choose Developer docs. That module links directly to the same workspace’s keys, Playground, credits, and run observability.
Creating or rotating a credential requires both the workspace manage_ai_keys permission and a standing platform-admin approval for that workspace. Listing and revoking existing credentials remain available without issuance approval. Removing approval does not invalidate existing credentials. Registered external apps may instead use a short-lived ttr_app_ access token. The app registration and issued token must both include workspace:session and ai:use; speech requests require tts:use. These requests must also send the normalized workspace ID returned by the app-token exchange:
The external-app path is temporarily exempt from workspace credit deductions. It is not unrestricted access: registration status, linked workspace, current user membership, model policy, payload bounds, workspace request rate, stable request IDs, and usage auditing remain enforced. Browser sessions, internal satellite sessions, ordinary Studio keys, and unrecognized callers never receive this exemption.

​
OpenAI-compatible endpoints

Requests support stable x-request-id values and the idempotency-key header. Streaming responses use server-sent events. Errors use an OpenAI-compatible error object and include the stable request ID for support correlation. Model access is the intersection of the globally enabled catalog, global Studio defaults, workspace policy, plan or root grants, and the key’s own model restrictions. A model visible elsewhere in Tuturuuu is not necessarily available to a Studio key. The legacy global/workspace Studio enablement switches no longer gate model execution. Credit availability, model policy, credential status, budgets, rate limits, and abuse controls remain authoritative.

​
Native extensions

Tuturuuu-native response metadata reports billed workspace credits, provider cost when permitted, run and trace IDs, token or media units, and timing information. These fields extend the compatible response without changing the standard OpenAI fields. Text endpoints accept an optional bounded tool-loop extension:
max_steps must be between 1 and 8. The listed tools are deterministic, server-owned demonstration tools; arbitrary HTTP requests and code execution are not accepted. Non-streaming responses include tuturuuu.steps with only the ordered step number, type, name, status, and latency. Streaming responses emit the same sanitized trace in the final response.completed event before [DONE]. Workspace Studio dashboards combine settled ai_studio_runs with unmatched deductions from ai_credit_transactions. This includes ordinary workspace deductions and the signed-in member’s personal deductions when a free workspace uses a personal credit balance, without double-counting ledger rows linked to a Studio run. Billed credits and settled provider cost are shown separately; registered external-app runs therefore report provider cost while showing zero billed workspace credits. The usage and run-log responses include identifiers, model, feature, credential source, status, token or media units, settled credits and cost, and timing metadata. They never include raw prompts, model outputs, tool payloads, ledger metadata, or unsanitized provider errors. The legacy /api/ai/generate endpoint remains available as a compatibility adapter. New integrations should use the /v1 Studio endpoints.

​
Speech

POST /v1/audio/speech accepts input, optional voice, optional response_format (wav or pcm), and the google/gemini-3.1-flash-tts-preview model. The response is downloadable audio and is never cached. Google currently prices the model by text input tokens and audio output tokens; Tuturuuu records both provider cost and generated audio duration-derived token usage.

​
Retention and content capture

Metadata logging is enabled by default. Prompt, output, and tool content is captured only when the workspace enables content capture. Use the Studio retention controls to review the active policy before submitting sensitive data.