# Mostly Right documentation

Source: https://mostlyright.md/docs/

Find data you can use, search it from your application, or build a table from your own sources.

## Start with what you want to do

| Your goal | Start here | What you get |
| --- | --- | --- |
| Read an existing dataset | [Use a public dataset](/docs/guides/use-public-datasets/) | Schema, sample rows, JSON queries and Parquet downloads. |
| Add search to an application | [Search API](/docs/reference/search/) | A request scoped to your chosen public tables. |
| Write JavaScript or TypeScript | [JavaScript guide](/docs/guides/javascript/) | A working fetch example and the server SDK's installation status. |
| Connect an AI assistant | [MCP setup](/docs/guides/mcp/) | Tools to discover, read and build datasets. |
| Build your own dataset | [Install and sign in](/docs/start/install/), then [first dataset](/docs/start/first-dataset/) | A hosted build with a schema, checks and a stable dataset page. |
| Automate a workflow | [For agents](/docs/guides/for-agents/) and [CLI reference](/docs/reference/cli/) | Structured output, returned identifiers and failure recovery. |

## Read a dataset first

Browse the [catalog](/datasets/), open a dataset and choose **Use**. Select a table, then choose an API example, Search API, JavaScript SDK, MCP setup or download. Examples use the selected table's identifier.

Public metadata and previews can be inspected without a key. Authenticated requests use the key class their API requires. Keep application keys on your server. Read [access and limits](/docs/reference/public-dataset-api/) before connecting a browser or scheduling bulk reads.

## Build and verify

A dataset contains one or more tables. A recipe names a table's sources, output columns, transformation and checks. The CLI submits the recipe to the hosted service; acquisition and transformation run there.

Before building, inspect sources and run `recipe explain` and `recipe forecast`. Use a separate scratch table for a sample run. **A new table's first successful run goes live, even when it is a truncated sample.** Run the real table in full, follow its progress, and verify rows, checks and coverage.

A successful run produces an immutable table version. Being live in your workspace and being publicly listed are separate decisions. Refresh requires a supported continuation plan or declared rebuild; it is not guaranteed by a successful first build.

- [Build workflow](/docs/build/): source inspection, recipes, testing and verification.
- [Enrich a table](/docs/build/enrich/): deterministic improvements and available small models.
- [Prepare and test search](/docs/reference/cli/search/): readiness, revisions and real queries.
- [Match records](/docs/reference/cli/match/): profiles, matching jobs and evidence.
- [Publish and refresh](/docs/build/publish-and-refresh/): visibility, cadence and resync.

## Read the docs with an agent

Every current documentation page has **View as Markdown** beside its title. The [documentation index](/docs/llms.txt) links to those pages; [all documentation](/docs/llms-full.txt) contains their full text. Both are generated from these human-readable pages.

Use [/llms.txt](/llms.txt) for platform discovery and [/llms-full.txt](/llms-full.txt) for the dataset catalog. These are separate from the documentation files. Install the current build skill with `mr-data`, or connect through MCP, before asking an agent to build a dataset.
