Process Documents
Projects
No projects yet. Process a transcript to create one.
LLM Provider
Active provider: Portkey.
It is selected by the LLM_PROVIDER environment variable on the server
(portkey or openrouter); changing it requires a redeploy/restart.
Settings for both providers are kept, so you can configure and test the inactive one before switching.
Portkey Configuration
Enter your Portkey API key to load virtual keys and models.
Model Assignments
Assign models to each extraction task. Select a virtual key first, then choose a model.
1. Structure Discovery
Extracts meeting metadata, modules, and participants. Fast model recommended.
2. Decision Extraction
Identifies explicit decisions made during meetings.
3. Micro-Decision Sweep CRITICAL
Captures single-mention statements that become requirements. Use your best model here.
4. Dependencies & Rules
Discovers hidden dependencies, business rules, and action items.
OpenRouter Configuration
Enter your OpenRouter API key to load the model catalogue. A key supplied through the
OPENROUTER_API_KEY environment variable takes precedence over one saved here.
OpenRouter Model Assignments
Assign an OpenRouter model to each extraction task. Type to filter the list, or enter a custom model ID.
Processing Settings
Danger Zone
Irreversibly delete every project, transcript, processing job, extracted entity, and LLM call log in the system. Auth state (admin password, sessions, API keys, webhooks) is preserved. Use this to wipe stale or test data so a fresh upload starts from a clean slate.
API Keys
API keys authenticate programmatic callers via the X-API-Key header. Two tiers:
admin grants full access, ingest grants upload + read-only access to jobs
and project data.
Keys are shown only once at creation — store them securely.
Webhooks
Webhooks deliver job-lifecycle events as signed POST requests. Verify the
X-MM-Signature header (HMAC-SHA256 of the raw body using the secret).
The signing secret is shown only once at creation.