Export and portability¶
This page sets out what you can take out of Rig, in what format, and what is not available as an export today.
Your data¶
With your own warehouse, Rig queries the data in place and loads ingested data into it. The tables stay in your own account, so there is no export step for them. The context layer that Rig builds holds descriptions, sample values and usage statistics for those tables, not copies of the tables.
With a Rig-hosted warehouse, ingested data is held in a MotherDuck database provisioned for
your workspace. Query results can be read through the MCP tool execute_sql and through the
API.
Definitions and context¶
| What | Format | How |
|---|---|---|
| Semantic model: every metric, the tables it references and the joins between them | One OSI (Open Semantic Interchange) JSON document | GET /{client_id}/metrics/osi |
| Metrics | JSON | GET /{client_id}/metrics/list |
| Tables and columns with their descriptions | JSON | GET /{client_id}/fde/context/tables, GET /{client_id}/fde/context/table/{table_id} |
| Business terms | JSON | GET /{client_id}/fde/context/terms |
| Usage rules | JSON | GET /{client_id}/fde/context/rules |
| Joins | JSON | GET /{client_id}/fde/context/joins |
An OSI document exported from one workspace can be imported into another with
POST /{client_id}/metrics/osi.
These operations are in Preview and authenticate with a user session. See the API reference. The same content can be read by an agent through the MCP server.
Rig holds metric definitions, including their SQL, and exports them in the OSI document. Your dbt project and its transformation logic stay in your own repository and warehouse.
Workflow results¶
| What | Format | How |
|---|---|---|
| The result of a run | JSON | GET /{client_id}/workflows/{workflow_id}/runs/{run_id}, field final_context. Works with an API token. |
| A rendered report | PDF download from the report in the application |
People directory¶
People and team records can be read as SCIM 2.0 resources from
GET /{client_id}/scim/v2/Users and GET /{client_id}/scim/v2/Groups.
Not available today¶
- A single bulk export of the whole context layer in one file. The OSI document holds the metrics and the tables and joins they use, not column descriptions, business terms or usage rules; export those with the endpoints above.
- Export endpoints that return CSV or Parquet.
- A bulk export of conversation history.
- Export of metric definitions as dbt YAML.