## Source

`TODO`: "Cleanup public API schema (+ add MCP to it)"

## Current state

Audience decision: agents and power users. A public third-party API is not required; prioritize a stable MCP/agent contract.

`packages/api` defines the HTTP contract with Effect `HttpApi` (`Projects`, `Waitlist`, prefix `/api`). MCP tools are defined separately in `packages/mcp/src/tools.ts`, and there is no published OpenAPI/machine-readable schema.

## Acceptance

- [ ] Inventory every public HTTP endpoint and MCP tool, including auth requirements, scopes, success and error shapes.
- [ ] Generate one machine-readable schema from the Effect definitions and expose it for the app and supported agent/local tooling.
- [ ] Generate or verify the client from that schema instead of maintaining a parallel hand-written surface.
- [ ] Describe MCP tools from the same source of truth, or add a checked mapping so the two cannot drift.
- [ ] Document authentication, pagination (where present), errors and at least one example per endpoint/tool.
- [ ] Add contract tests that fail on an undocumented or breaking change.
- [ ] Decide the versioning/compatibility policy before the first public consumers depend on it.


<sub>Generated on _MrBeast_ using _opencode/deepseek-v4.1-flash_ in _ses_e8326e581ffeJviTmSkomwnKES_</sub>