# Threa

> Threa is AI-powered knowledge chat: conversations become preserved, searchable memos
> (decisions, context, provenance) that both Threa's own assistant and your agents can
> read. The public REST API lives at https://app.threa.io under
> /api/v1/workspaces/{workspaceId}/… and authenticates every request with
> "Authorization: Bearer <api key>". Keys are created in the app (Settings > API keys)
> and carry scopes; GET /me verifies a key with no scope required.

Threa is open source (https://github.com/threahq/threa) and self-hostable. Things
an agent can do over the API today:

- Search memos — the durable record of what a team decided and why — and follow
  provenance links back to the exact source messages.
- Send, edit, search, and delete messages; list streams, members, and users.
- Search attachments and read their extracted text.
- Run as a persistent workspace agent through the pull-based bot runtime: claim
  invocations, stream steps, post results. No inbound ports or webhooks needed,
  so it works from a laptop, CI, or anywhere with outbound HTTPS.

There is no MCP server yet — agents integrate over the REST API and the pull-based
bot-runtime protocol. All docs below are markdown; the HTML pages under
https://threa.io/developers mirror them one-to-one.

## Docs

- [Overview & quickstart](https://threa.io/developers/index.md): What the API covers, base URL, and a quickstart from key to first search.
- [Authentication](https://threa.io/developers/authentication.md): Bearer keys, the three key kinds (threa_uk_/threa_bk_), scopes, and how missing scopes fail.
- [API reference](https://threa.io/developers/reference.md): Every endpoint with parameters, request/response shapes, scopes, and a curl example.
- [Markdown](https://threa.io/developers/markdown.md): The message content format: standard markdown plus the user:/channel:/attachment:/memo: link schemes for mentions, channels, files, and memos.
- [Versioning](https://threa.io/developers/versioning.md): Date-based API versions pinned per key at mint, overridable with the Threa-Version header, breaking vs additive changes, and the support window.
- [Operations](https://threa.io/developers/operations.md): Error shapes, cursor pagination, idempotent sends, rate limits, and CORS.
- [CLI & MCP server](https://threa.io/developers/cli.md): The threa command-line tool and its MCP server: install from the repo, configure one workspace binding, the noun-verb command surface, and agent integration.
- [Recipes](https://threa.io/developers/recipes.md): Worked examples: memo search with provenance, CI notifications, and a full bot-runtime agent loop.
- [Feature requests](https://threa.io/developers/feature-requests.md): Where to ask for missing endpoints or scopes (GitHub issues on threahq/threa).

## Machine-readable

- [OpenAPI 3.0 spec](https://threa.io/openapi.json): the canonical contract — every endpoint, schema, scope, and error. This is the current version; each dated version has its own spec at https://threa.io/openapi/<version>.json.
- [Full docs in one file](https://threa.io/llms-full.txt): all pages above concatenated

## Optional

- [About Threa](https://threa.io/about): what the product is and how memos work
- [Source code](https://github.com/threahq/threa): the whole product, developed in the open