> ## Documentation Index
> Fetch the complete documentation index at: https://docs.chatsailer.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Sailer

> Two ways into a Sailer workspace: a REST API for your code, and MCP servers for your agents.

Your team already works in Sailer. These docs are how your code and your agents
do the same.

<CardGroup cols={2}>
  <Card title="REST API" icon="code" href="/guides/quickstart">
    Your backend talks to `api.chatsailer.com`. Tokens, `/v1`, a playground.
  </Card>

  <Card title="MCP" icon="plug" href="/mcp/overview">
    Claude, ChatGPT, or Cursor talks to `mcp.chatsailer.com`. No code.
  </Card>
</CardGroup>

Pick the surface that matches who is calling. Mixing them is allowed — they
read the same workspace — but they do not share a hostname, a protocol, or an
auth story.

## REST API

The Sailer API lets you read and write the same records your team works with in
the product: contacts, the conversations they are having, and the campaigns they
belong to.

<Note>
  **Early access.** The `/v1` contract below is stable and versioned, but not
  every resource is live yet. This page lists what you can call today.
</Note>

### Available today

| Resource     | Operations                                                                       |
| ------------ | -------------------------------------------------------------------------------- |
| **Contacts** | List, search, create, retrieve, update, upsert                                   |
| **Meta**     | Describe your token (`/v1/me`), read workspace capabilities (`/v1/capabilities`) |

Organizations, deals, pipelines, notes, activities, tags, conversations, and
campaigns are part of the `/v1` design and will appear here as they ship. The
tags already exist in the reference so you can see where they will land.

### Start here

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/guides/quickstart">
    Your first authenticated request, in about two minutes.
  </Card>

  <Card title="Authentication" icon="key" href="/guides/authentication">
    Token format, scopes, and what a token can and cannot reach.
  </Card>

  <Card title="Pagination" icon="list" href="/guides/pagination">
    One cursor scheme across every collection.
  </Card>

  <Card title="Errors" icon="triangle-exclamation" href="/guides/errors">
    The error envelope and how to handle each type.
  </Card>
</CardGroup>

### Base URL

```
https://api.chatsailer.com
```

Every endpoint is under `/v1`. The version is in the path, so a future `/v2` can
land without breaking anything you build today.

## MCP

Two hosted servers. Connect one, ask in plain language, watch the model call
tools against a real workspace. First connection is read-only on purpose.

Start at [MCP](/mcp/overview), then pick a [client tutorial](/mcp/connect).