RiteText

API documentation

Last updated: September 11, 2026

ritetext exposes a small, public, read-only HTTP surface so agents can discover the product. PDF files are never uploaded; editing happens in the user's browser.

Machine-readable discovery

MCP

Streamable HTTP at /api/public/mcp. No authentication. Tools: get_app_info, get_routes, get_pdf_tools, get_feature_status, get_editor_capabilities, search_catalog.

Health

GET /api/public/keep-alive returns JSON { "ok": true } when the optional Supabase heartbeat table is reachable.

Authentication

Catalog APIs are public. OAuth discovery documents exist so agents can confirm that anonymous / no credential is the supported method. See auth.md.