# Dealtab

> Dealtab is a brand-deal pipeline for creators: deals from lead to paid, deliverable deadlines, usage-rights and exclusivity end dates, and the invoices brands owe. It has a hosted MCP server and a REST API, so a creator's AI assistant can read and update their account with a key they create and can revoke.

Links below are relative to the host serving this file.

- MCP: Streamable HTTP at `/mcp`. Authenticate with `Authorization: Bearer <api key>` (keys start with `dtab_sk_`) or OAuth where the assistant supports it.
- REST: `/api/v1/*` with the same tools and the same bearer key. The OpenAPI 3.1 document is at `/api/v1/openapi.json`. Errors are JSON on every path; 401s point at `/.well-known/oauth-protected-resource/api/v1`, 429s carry `Retry-After`.
- Scopes: `read`, `write`, `send`. New keys get `read` and `write`. Over MCP a key lists only the tools its scopes allow; REST answers 403 for the others. Emailing a brand needs `send` and two calls: `preview_chase_email` returns a confirmation token (valid 10 minutes) that `send_chase_email` requires. Show the creator the draft and get a yes before sending.
- Money inputs are strings in major units as typed ("1,250.50") plus a currency. Dates are `YYYY-MM-DD`; resolve relative dates yourself. Ids are uuids (case-insensitive).
- Limits: 120 requests a minute per key (refused requests count too) and 20 brand emails a day.
- Dealtab never calls a language model.

## Docs

- [Use Dealtab from your AI assistant](/docs/agents): what it does, setup for ChatGPT, Claude, Grok, Cursor and Claude Code, the tool list, example prompts, safety model, REST and FAQ
- [Full docs in Markdown](/llms-full.txt): the same content as one plain-text file

## API

- [MCP server](/mcp): remote MCP endpoint (POST, Streamable HTTP, stateless); needs a bearer key or OAuth token
- [OpenAPI document](/api/v1/openapi.json): REST endpoints, inputs and outputs

## Optional

- [Settings, Agents](/settings#agents): where a signed-in creator creates and revokes API keys