Documentation Index
Fetch the complete documentation index at: https://docs.founder-sherpa.com/llms.txt
Use this file to discover all available pages before exploring further.
Founder Sherpa exposes two API endpoints. Most data access is handled through the Supabase client libraries using RLS-protected table queries.
Transcript Import
Parse transcript
POST /api/import/{importId}/parse
{
"hypothesisIds": ["uuid-1", "uuid-2"]
}
| Field | Type | Required | Description |
|---|
hypothesisIds | string[] | Yes | UUIDs of hypotheses to use as context for evidence extraction. Must be non-empty. |
| Status | Description |
|---|
200 | Parsing initiated successfully |
400 | Invalid request body or missing hypothesisIds |
401 | Missing or invalid authentication token |
422 | Parsing failed (e.g., import not found or already processed) |
Notifications
Trigger digest emails
POST /api/notifications/digest?frequency=daily
CRON_SECRET and is intended to be called by Vercel Cron, not by end users.
Query parameters:
| Parameter | Type | Required | Values |
|---|
frequency | string | Yes | daily or weekly |
| Status | Description |
|---|
200 | Digests processed. Returns { ok: true, frequency, sent } |
400 | Invalid or missing frequency parameter |
401 | Missing or invalid CRON_SECRET |
Authorization: Bearer <CRON_SECRET>
Supabase Data API
For querying and mutating data (projects, personas, hypotheses, evidence, questions, etc.), use the Supabase Data API with the apikey and Authorization headers described in the Authentication guide.
The Supabase Data API provides a REST interface auto-generated from the database schema, with full support for filtering, pagination, and relationships. All access is governed by Row Level Security policies that enforce workspace membership.
