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

# Quickstart

> Create an API key and make your first tool call.

## 1. Create an API key

API keys are managed from the Salesgraph dashboard.

<Steps>
  <Step title="Open API key settings">
    Go to [Settings → API Keys](https://salesgraph.com/dashboard/settings/api-keys) in your dashboard.
  </Step>

  <Step title="Create a key">
    Name it (for example, `Production agent`) and click **Create key**.
  </Step>

  <Step title="Copy it now">
    The full key is shown **once**. Copy it and store it somewhere safe — you can't see it again.
    Keys look like `sg_live_…`.
  </Step>
</Steps>

<Warning>
  Treat your key like a password. It grants access to your organization's research and audit
  tools. If a key leaks, revoke it from the same settings page and create a new one.
</Warning>

## 2. Connect a client

The server lives at:

```
https://salesgraph.com/api/mcp
```

Authenticate with the `Authorization: Bearer <your key>` header. Most MCP clients let you
configure the URL and a header. See the per-client guides:

<CardGroup cols={3}>
  <Card title="Claude" icon="plug" href="/clients/claude" />

  <Card title="Cursor" icon="code" href="/clients/cursor" />

  <Card title="Raw HTTP" icon="terminal" href="/clients/http" />
</CardGroup>

## 3. Make your first call

Once connected, ask your agent to use a Salesgraph tool. For example:

> "Use Salesgraph to research Stripe and summarize what they do."

Your agent will call the [`research`](/tools/research) tool and return a cited markdown brief.

To test the connection directly over HTTP without a client:

```bash theme={null}
curl -s https://salesgraph.com/api/mcp \
  -H "Authorization: Bearer $SALESGRAPH_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/list"
  }'
```

A successful response lists every available tool. If you get a `401`, double-check the key
and the `Authorization` header.

## Next steps

<CardGroup cols={2}>
  <Card title="Browse the tools" icon="wrench" href="/tools/overview">
    See what each tool does and what it expects.
  </Card>

  <Card title="Understand async runs" icon="clock" href="/reference/async-runs">
    GTM and org audits run in the background — learn how to poll them.
  </Card>
</CardGroup>