https://test-mirobody-api.thetahealth.ai/v1, pass an mb_live_* key, and the agent answers from each end-user’s real health data.
Account management — API keys, usage, and a live Playground — lives in the developer console at test-platform.mirobody.ai. These docs are a reference and guide; the console is where you sign in and manage everything.
Live today: build against the global test cluster — API
https://test-mirobody-api.thetahealth.ai/v1, console test-platform.mirobody.ai. Production is provisioning; the China test environment is now live too (Regions). The console defaults to Chinese — use the language switch (top-right) for English.Sign in & get an API key
Sign in to the console with email code — enter your email, receive a 6-digit code, and sign in. Then open API Keys and create one; the secret is shown once. (Need an evaluation account? Email Mirobody Support.)
Open the console → API Keys
Sign in, create an
mb_live_* key, and copy it.Make your first call
user field isolates each end-user as a Subject — pass each of your users’ stable ids. See the full Chat reference.Give the Subject some data
A fresh Subject has no data, so the agent will say so. Write a record (or upload a report with
POST /v1/files) and ask again:retention is required on POST /v1/data (no default) — omitting it returns 400. See Data and Files.Prefer clicking over curl?
The console has a Playground — run chats, upload files, and inspect tool steps with no code.Playground
Try the agent in the browser against your account.
Usage
Requests, tokens, and cost.
See it live
Mirobody app
chat.mirobody.ai — the flagship consumer product, the same engine behind this API.
Developer console
Create
mb_live_* keys, view usage, and try the Playground.Next steps
API Reference
Auth, multi-tenancy, retention, and every
/v1 endpoint.SDK Examples
curl / Python / Node, streaming and file upload.
China Region
Base URLs, storage residency, models, and limits.
Compliance
PIPL / data residency; request a DPA.