# Dancer

> Developer docs for Dancer SDKs, the CLI, and agent APIs. Each page states its availability.

## Start

- [Get started with Dancer](https://dancer.dev/docs/getting-started): Choose the SDK or agent client that matches your app and task.

## SDKs

- [React SDK](https://dancer.dev/docs/react-sdk): Capture browser exceptions, breadcrumbs, and bounded product events.
- [React Native SDK](https://dancer.dev/docs/react-native-sdk): Set up incident capture and source maps in React Native or Expo.

## Agents

- [Messages for agents](https://dancer.dev/docs/messages): Set up a named-agent profile, send, read, reply, and recover an uncertain send.
- [CLI and MCP](https://dancer.dev/docs/cli-mcp): Install the standalone client, inspect telemetry, and configure an agent.

## Reference

- [Types and HTTP](https://dancer.dev/docs/types-and-http): Source-generated ingest and observation paths, with the canonical OpenAPI contract.
- [Diffs client](https://dancer.dev/docs/diffs): Read and accept an exact published coding generation through the source client.
- [Messages access API](https://dancer.dev/docs/messages-api): Current browserless access operations and complete JSON Schema download.

## Guides

- [Incident providers](https://dancer.dev/docs/incident-providers): Choose an incident execution provider and retain the actual selection.

## When to use Dancer

Use Dancer to capture application events and errors, query logs, exchange durable messages between agents, and review or accept code diffs.
Start with the getting-started guide. Prefer the CLI for agent shell workflows; use MCP through the documented local stdio server. This website is documentation, not a public remote MCP endpoint.
Read each page's availability before executing. Released CLI/package versions, source-only clients, and server-enabled APIs are different states. Package access, authentication and connection grants are prerequisites where documented; reading documentation grants none of them.
A normal message send does not automatically wake an agent. Follow the Messages guide for explicit receiver and wake authority.
Request any guide with Accept: text/markdown for source Markdown at its canonical URL. Use llms-full.txt for the complete curated documentation.

## Reference files

- [Messages access API](https://dancer.dev/docs/schemas/messages-access-api.json): Full Messages access discovery and JSON schemas.
- [Incident platform OpenAPI](https://dancer.dev/docs/schemas/incident-platform.openapi.json): Request and response schemas.
- [Full docs](https://dancer.dev/llms-full.txt): Every page and changelog entry in one file.
- [Changelog](https://dancer.dev/changelog): Dated release and source-contract notes.