Research in rounds.
The first search provides context. What it finds should shape the next search, the source review, and the questions that still need an answer.
Why Farside exists
We needed better research.
So we built the engine.
Farside Research grew out of Research Hub in Mission Control, our operations platform. We needed an engine that people and agents could use to investigate complex questions, retain the evidence, and keep working from what they found.
THE STANDARD WE BUILD TO
A confident paragraph
isn’t enough.
Research should leave you with more than an answer. Keep the source records, inspect the citations, ask what is missing, and take the next question further.
We built the engine we wanted to use: iterative search, source grading, cited synthesis, grounded questions, focused investigations, and connected dossiers.
See the work you can inspectWHAT WE BUILD AROUND
A useful answer has
something behind it.
The research engine is built around the work that happens before and after a conclusion. These are the choices that shape the product.
Keep the evidence.
A report should remain connected to source records, citations, and extracted claims. People need to inspect how the synthesis came together.
Leave room for uncertainty.
Conflicting findings and missing evidence belong in the result. A useful investigation makes the unanswered parts visible.
Make the next step possible.
Research often leads to another question. Grounded follow-ups, rabbit-hole investigations, and dossiers keep that work connected.
ONE ENGINE / THREE WAYS IN
Wherever the question
comes from.
People need a place to read and investigate. Products need an API. Assistants need tools. Farside gives each a way to work with the same research.
The browser
Frame a research question, follow its progress, read the cited synthesis, and inspect the evidence. Keep going with grounded questions and focused investigations.
Explore the research workflowThe REST API
Submit asynchronous research, read its durable state, stream progress events, and retrieve the result. Build the research into the product you already operate.
Read the quickstartHosted MCP
Connect a compatible assistant to research tools with a scoped key. Keep estimates, paid actions, and evidence retrieval explicit in the workflow.
Connect an assistantRESEARCH STILL NEEDS JUDGMENT
Keep the work
open to review.
A citation is a route back to a source, not a guarantee that a conclusion is correct. Sources can be incomplete, outdated, or in conflict. An important claim deserves a closer look at what the source actually says.
Use Farside to collect context and investigate alternatives. Bring your own constraints, challenge the assumptions, and verify conclusions that carry real consequences.
How to read the evidenceTHE WORK STAYS WITH YOU
The evidence stays
with the answer.
A synthesis is the start. Deep research can develop the promising threads into focused investigations and related dossier documents.
Inside an investigationCONNECTED RESEARCHResearch dossier
FindingsSourcesOpen questions
01 / INVESTIGATIONA promising thread
02 / INVESTIGATIONAn unresolved question
03 / DOSSIERRelated documents
BEFORE YOU START
Good questions.
Clear answers.
What to expect from the research, and how to put it to work.
Explore the documentationWhat should I put in a research question?
Include what you need to understand, who the answer is for, and the constraints that matter. For a vendor comparison, name the use case, region, budget constraints, and evaluation criteria. A specific brief gives the research a useful direction.
Start with a briefWhat makes this more than one web search?
The engine researches in rounds. It reads and grades sources, brings the findings into a cited synthesis, and retains the evidence. Deep research takes emerging questions into follow-on investigations and a dossier.
Can I inspect the evidence behind an answer?
Yes. Research retains source records, citations, extracted claims, and open gaps. Read the evidence behind important claims, especially when sources disagree or a conclusion depends on an assumption.
Read the evidence trailCan my product or assistant use the same engine?
The REST API creates asynchronous research runs and exposes status, progress events, and results. Hosted MCP lets compatible assistants work with the research tools. Use scoped keys and check the cost before starting paid work.
Connect through MCPWhat happens after the report is finished?
Reopen the retained research, inspect the sources, ask grounded follow-up questions, or investigate a new thread. Sharing and export depend on the controls and permissions available to your account.
Work from the resultHow do credits and plan access work?
Paid research actions use credits. Review the live plan, action price, and access before starting. Reading an existing report does not spend credits. The pricing page uses the live catalog rather than estimates embedded in this site.
Review plans and credits