Mirobody - Mirobody

What is Mirobody?

Mirobody turns health readings from reports, devices, exports and photos into a record that can be compared across sources. It assigns standard codes and units, then lets an agent answer questions over that record while pointing back to the source of each reading. The engine is open source under Apache 2.0; Mirobody Cloud offers its standardization and agent capabilities as a hosted API.

First steps

Choose where the record will run. The two paths use the same coding approach, but have different setup and API endpoints.

Mirobody Cloud

Create a key, write sample readings, and ask a question through /v1. We operate storage and models.

Self-Host

Run the library or Docker stack yourself. Records stay in storage you operate; model features use your configured provider.

Cloud exposes /v1. A self-hosted deployment exposes its own /api/* and /mcp endpoints.

Your first goal	Start here	Result to check
Call a hosted API	Cloud quickstart	Two sample readings share a LOINC code; a question can cite them.
Resolve a name or unit locally	Library path	A code is returned without a database or model key.
Explore the full product locally	Docker demo	The service is healthy and demo readings appear in Data.

From data to answers

Collect, Translate, Agent: health data moves from sources to coded records and answers — The same three stages organize Cloud and the open-source engine.

Stage	What you can observe	Read more
① Collect	A file, device reading or structured record enters the system with its source.	Cloud data inputs · Open Source collection
② Translate	Different names for the same test resolve to a standard LOINC code; units use UCUM. Unmatched names remain unmatched.	Standardization
③ Agent	A question runs over the coded record and returns an answer with its supporting readings.	Cloud Answers API · Open Source agent

On Cloud, your application sends data to /v1; the service stores and processes it. In a self-hosted deployment, the engine runs on infrastructure you manage. See Cloud capabilities and the local setup guide for their respective paths.

Storage and operations

Decision	Mirobody Cloud	Self-Host
Stored records	Operated by Mirobody, under the API’s retention settings	In your Postgres and file storage
Model requests	Handled by the hosted service	Sent to the model provider you configure
Deployment and upgrades	Operated by Mirobody	Follow the server deployment guide

Cloud API overview

Authentication, Subjects, retention and the /v1 endpoint map.

Open Source architecture

Follow a reading from its original file to a coded answer.

​What is Mirobody?

​First steps

Mirobody Cloud

Self-Host

​From data to answers

​Storage and operations

​Further reading