> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mirobody.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# China Cluster

> mirobody-api.thetahealth.cn — China-region cluster (test live, production provisioning).

The China cluster keeps 100% of data within mainland China, with no cross-border replication. Its **test environment is now live** — the consumer app and developer console both serve from the CN test cluster against a live backend. The **production** API base is still provisioning; for turnkey live API integration today, use the CN test cluster or the [global test cluster](/en/api-reference/regions/global).

## Hosts

| Surface               | Production                                                           | Test                                                                                             |
| --------------------- | -------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------ |
| **Consumer app**      | [mirobody.thetahealth.cn](https://mirobody.thetahealth.cn/) — ✅ live | [test-chat-mirobody.thetahealth.cn](https://test-chat-mirobody.thetahealth.cn/) — ✅ live         |
| **Developer console** | [cdm.thetahealth.cn](https://cdm.thetahealth.cn/) — ✅ live           | [test-platform-mirobody.thetahealth.cn](https://test-platform-mirobody.thetahealth.cn/) — ✅ live |
| **API** (`base_url`)  | `https://mirobody-api.thetahealth.cn/v1` — 🚧 provisioning           | `https://test-mirobody-api.thetahealth.cn/v1` — 🚧 provisioning                                  |

<Note>
  The CN **test API is already serving** — currently on the transitional host `https://test-mcp.thetahealth.cn/v1`, while `test-mirobody-api.thetahealth.cn` finishes provisioning. The older `mcp.thetahealth.cn` name is being retired in favour of `mirobody-api.*`, so point anything long-lived at `mirobody-api.*`.
</Note>

The console is where you create `mb_live_*` keys, view usage, and try the Playground. The Mirobody app is the flagship consumer product — the same engine behind this API.

## Capabilities (`/v1`)

<CardGroup cols={2}>
  <Card title="Chat" icon="comments" href="/en/api-reference/chat">
    `POST /v1/chat/completions` — OpenAI-compatible, streaming, citations
  </Card>

  <Card title="Data" icon="database" href="/en/api-reference/data">
    `POST/GET /v1/data` — structured records per Subject
  </Card>

  <Card title="Files" icon="file" href="/en/api-reference/files">
    `POST/GET /v1/files` — OCR / Excel parsing
  </Card>

  <Card title="Sessions" icon="timer" href="/en/api-reference/sessions">
    `DELETE /v1/sessions/{id}` — purge session data
  </Card>
</CardGroup>

## Models

Managed by Mirobody — no LLM key of your own needed: `mirobody-flash` (default) / `mirobody-expert`. See [Models](/en/api-reference/models).

## Storage & residency

* Files stored in **Aliyun OSS (Hangzhou region)**.
* 100% of data stored inside mainland China; no cross-border replication.

## Compliance

Aligned with PIPL / Data Security Law / Cybersecurity Law — see [Compliance](/en/api-reference/compliance). For rate limits, see [Rate Limits](/en/api-reference/rate-limits).