# Introduction

1. Sign in at [the dashboard](https://usedocs.app/dashboard) with Google, GitHub, or a magic link. Every workspace starts with a 7 day free trial of Growth, no credit card.
2. Import your docs (a docs site URL, Zendesk Guide, Intercom, GitBook, Notion, or OpenAPI), then open **Settings → API and MCP**.
3. Copy `botId` and the public `botKey`. They are the keys for the widget, the Answer API, and the docs MCP server.
4. Call `POST /chat`, or connect an agent to [usedocs.app/mcp](https://usedocs.app/mcp).

## API keys

There are two kinds of credentials. The public Answer API and the docs MCP server use the embed credentials:

- **botId**: the bot's UUID, in the path and the JSON body.
- **botKey**: the public key from Settings → API and MCP, sent in the JSON body as `botKey`.
- Browser calls also need an `Origin` header on an allowed origin. Server to server calls authenticate with botKey; send Origin when the bot has allowed origins configured.

The Docs API and the workspace MCP server use a **workspace API key** from Settings → API and MCP, sent as `Authorization: Bearer ud_live_…`. A key is shown once and stored as a hash. A `content:read` key can read; a `content:write` key can also edit, publish, apply drafts, and send code changes. A key covers one bot or all of them and can be revoked at any time. Keys don't work on the dashboard's own routes, settings, or billing. People connecting Claude, Cursor, or ChatGPT sign in with OAuth instead (Integrations → AI clients).