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

# Quickstart

> Connect an AI agent to SeeSaw in five minutes

## 1. Get your API key

The Open API is in **beta**: keys are currently issued by the SeeSaw team.
Contact us through your existing SeeSaw channel (or the in-app feedback form)
and tell us the account you want the key attached to. Self-service key
management in the app is on the way.

You'll receive a key that looks like this:

```
sspat_k9XcTq2mVfLw…
```

<Warning>
  The full key is shown **once** at creation. Treat it like a password — it
  reads your account's balance and positions. If it leaks, revoke it
  immediately (`DELETE /v1/users/me/api-keys/{id}` on the app API, or ask the
  team).
</Warning>

## 2. Connect

For [Claude Code](/mcp/clients/claude-code), one command:

```bash theme={null}
claude mcp add --transport http seesaw https://api.seesaw.fun/mcp \
  --header "Authorization: Bearer sspat_YOUR_KEY"
```

Other clients (Cursor, VS Code, Claude Desktop, raw JSON config) are covered
in [Client Setup](/mcp/clients/claude-code).

Verify: ask your agent to list its tools. You should see **14 SeeSaw tools**,
from `search_topics` to `list_my_topics`.

## 3. First query

Ask your agent something like:

> Find trending predictions about the World Cup and summarize the odds.

A typical run calls `search_topics` (or `list_topics`) and reads the option
probabilities off the result:

```json theme={null}
{
  "data": [
    {
      "id": "9cef7a1a-235c-4aac-9715-cd3732ee75b5",
      "type": "prediction",
      "title": "Will the Nasdaq close up or down tomorrow?",
      "status": "open",
      "options": [
        { "id": "4d995c85-…", "name": "Yes", "probability": "0.7995", "is_winner": false },
        { "id": "d502b13a-…", "name": "No", "probability": "0.2005", "is_winner": false }
      ],
      "total_volume": "112551.8486",
      "traders_count": 104,
      "end_time": "2026-07-10T15:59:00Z",
      "url": "https://seesaw.fun/topic/9cef7a1a-235c-4aac-9715-cd3732ee75b5"
    }
  ],
  "next_cursor": "bzoy",
  "has_more": true
}
```

Probabilities are **strings** (`"0.7995"` = 79.95%), and every topic carries a
`url` your agent can hand back to humans.

Prefer curl? The same capability over REST:

```bash theme={null}
curl -H "Authorization: Bearer sspat_YOUR_KEY" \
  "https://api.seesaw.fun/open/v1/topics?sort=trending&limit=5"
```

## Next steps

<CardGroup cols={2}>
  <Card title="Tools overview" icon="wrench" href="/mcp/tools/overview">
    All 14 tools and when to use which.
  </Card>

  <Card title="REST reference" icon="code" href="/api-reference/introduction">
    Endpoint-by-endpoint OpenAPI reference.
  </Card>

  <Card title="Rate limits" icon="gauge" href="/rate-limits">
    Per-key quotas and how to handle 429s.
  </Card>

  <Card title="Authentication" icon="key" href="/authentication">
    Key lifecycle, security, and revocation.
  </Card>
</CardGroup>