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

# Clearskies API

> Read the accounts, calls, contacts, and deals in your Context Graph, and your call transcripts, from your own code: dashboards, warehouse syncs, and internal tools.

> [!NOTE]
>
> The Clearskies API is in beta and available on request. To turn it on for your workspace, email
> [support@clearskies.cc](mailto:support@clearskies.cc).

The Clearskies API gives your own code the same accounts, calls, contacts, and deals your agents see in the [Context Graph](https://clearskies.cc/docs/unifying-gtm-data/customer-context-graph.md). Pull open pipeline into a revenue dashboard, sync deal stages into your warehouse, count deals by stage without exporting from your CRM, or feed an account's call transcripts into your own analysis.

The API is read-only and returns plain JSON, so it fits anywhere you can make an HTTP request.

## API or MCP

Both read the same Context Graph. Pick by who is asking.

| Use | When |
| - | - |
| [MCP](https://clearskies.cc/docs/building-with-clearskies/mcp-server.md) | An AI assistant (Claude, ChatGPT, Cursor, Grok Bot, n8n, Retool) decides what to look up while it works |
| The API | Your own code runs a known query and needs a predictable response shape |

## Base URL

```
https://api.clearskies.cc
```

## How a query comes together

The fields available differ between workspaces, so read before you query:

1. [List objects](https://clearskies.cc/docs/api-reference/endpoints/list-objects.md) to see the object types the API serves.
2. [Get an object's schema](https://clearskies.cc/docs/api-reference/endpoints/get-object-schema.md) to see its fields and what each one supports: filter, sort, group, or measure.
3. [Query records](https://clearskies.cc/docs/api-reference/endpoints/query-records.md) for a page of records, or [aggregate records](https://clearskies.cc/docs/api-reference/endpoints/aggregate-records.md) for counts and sums.

To read what was said on a call, query `call` records to find its `id`, then [get the call's transcript](https://clearskies.cc/docs/api-reference/endpoints/get-call-transcript.md). Filter calls by `accounts` to get the ones that involve a given account.

## Your first request

With an [API key](https://clearskies.cc/docs/api-reference/authentication.md) in `CLEARSKIES_API_KEY`, list the object types:

```bash theme={null}
curl https://api.clearskies.cc/v1/objects \
  -H "Authorization: Bearer $CLEARSKIES_API_KEY"
```

```json theme={null}
{
  "ok": true,
  "data": [
    { "name": "account", "label": "Account", "custom": false },
    { "name": "call", "label": "Call", "custom": false },
    { "name": "contact", "label": "Contact", "custom": false },
    { "name": "deal", "label": "Deal", "custom": false }
  ],
  "requestId": "0199f2b0-7c41-7a3e-9d6c-2f5a1b8e4c07"
}
```

Every response has this envelope. A success carries `ok: true` and the result in `data`. A failure carries `ok: false` and an `error`; see [Errors and rate limits](https://clearskies.cc/docs/api-reference/errors-and-rate-limits.md).

## Next steps

> [card] [Authentication](https://clearskies.cc/docs/api-reference/authentication.md)
>
> Create an API key and send it with each request.

> [card] [Query records](https://clearskies.cc/docs/api-reference/endpoints/query-records.md)
>
> Filter, sort, and page through records.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.