The hybrid synthesize endpoint runs a multi-stage pipeline that ingests PDFs and company profiles, extracts causal entities and relationships, synthesises them into novel research ideas, and applies a novelty gate before returning a structured synthesis result. The pipeline streams progress as Server-Sent Events (SSE), so your client receives incremental updates as each stage completes.Documentation Index
Fetch the complete documentation index at: https://wuweism.com/llms.txt
Use this file to discover all available pages before exploring further.
Authentication is optional. If you include a valid
Authorization header, results are associated with your account and persisted in your session history. Without a token, the synthesis runs anonymously and is not saved.Run a synthesis
- Content-Type:
multipart/form-data - Response:
text/event-stream(SSE) - Max duration: 300 seconds (5 minutes)
Minimum inputs
You must supply at least 2 total sources across files and companies combined. For example: 1 PDF + 1 company, or 2 PDFs, or 2 companies.Form data parameters
PDF files to include in the synthesis. Maximum 6 files. Each file must be a valid PDF. Files are parsed, scientifically analysed, and their causal entities are extracted before synthesis.
JSON-encoded array of company names to include as intelligence sources. Maximum 5 companies. The pipeline retrieves recent research and product context for each company and incorporates it alongside your PDFs.Example:
'["DeepMind", "Anthropic", "Meta AI"]'A guiding question or theme that orients the synthesis. The pipeline uses this focus to rank ideas and structure the output.Example:
"causal mechanisms of neuroplasticity under chronic stress"Whether to run the refinement stage with parallel threads. Set to
"true" or "false".Number of concurrent refinement threads when
enableParallelRefinement is "true". Higher values produce richer output but increase latency.SSE events
The response is a stream of SSE events. Each event has anevent name and a JSON data payload. Parse them incrementally as they arrive.
Timeline
Stages execute in this order:ingestion → pdf_parsing → entity_harvest → synthesis → novelty_gate → recovery_plan → completed
Each stage emits timeline_stage_started, then timeline_stage_completed (or timeline_stage_skipped if the stage is not applicable given your inputs).
Event reference
ingestion_start
ingestion_start
Emitted once when the pipeline begins processing your inputs.
files— number of PDF files received.
pdf_processed
pdf_processed
Emitted once per PDF file after it has been successfully parsed.
scientific_analysis_complete
scientific_analysis_complete
Emitted after all PDF scientific analyses finish.
timeline_stage_started
timeline_stage_started
Emitted when a pipeline stage begins.
timeline_stage_completed
timeline_stage_completed
Emitted when a pipeline stage finishes successfully.
timeline_stage_skipped
timeline_stage_skipped
Emitted when a pipeline stage is skipped (e.g.,
recovery_plan when no failures occurred).complete
complete
Emitted as the final event when the pipeline finishes. Contains the full synthesis result.
error
error
Emitted if a fatal error occurs. The stream closes after this event.
