# Start here

Understand Refracto and choose a path through the documentation.

Refracto turns coverage of an event into briefings and other content for your publication, organisation or agent. It groups related reporting, makes the resulting content available in your workspace and delivers published output through your own channels.

## Choose your path

- **Use a workspace:** start with [access and workspaces](/docs/workspaces), then [select coverage](/docs/coverage) and [review briefings](/docs/briefings).
- **Connect a website:** read [Feed API integration](/docs/feed-api) and the [publication rules](/docs/publishing).
- **Connect an agent:** follow [MCP access](/docs/mcp), then use the [agent guide](/docs/for-agents).

## From coverage to content

The public engine stages are Ingest, Cluster, Classify, Measure, Brief, Verify, Notarize and Deliver. They describe the journey from source reporting to usable output. A cluster groups coverage of an event; a briefing is content generated from that coverage for your workspace.

Watchdog checks briefings and can request rewrites within the applicable plan limits. Keep editorial review in your workflow: a generated briefing is not permission to publish it everywhere.

## What this guide covers

The guide explains customer workflows and supported public integration contracts. Available screens and actions depend on your workspace, role, plan and enabled features. A feature visible in the product catalogue may still be marked coming soon; that label takes precedence over an illustrative demo.

For the current offer, see [plans and usage](/docs/plans) and [pricing](https://refracto.ai/en/pricing). For a working integration, use the contract returned by your own endpoint rather than guessing a route or a field.
