The Research System

Lesson preview

Search APIs give you the territory — the raw web content that exists. But synthesizing that territory into a coherent, citable answer belongs to your model, where you control the reasoning and the citation behavior. For anything client-deliverable, prefer raw-retrieval APIs (Exa, Tavily, Firecrawl, Brave, Parallel, Linkup) and do the synthesis yourself. Use synthesized-answer products like Perplexity Sonar for your own internal speed, where you don't need to stand behind every citation. As the web fills with AI-generated content, extraction quality — getting clean, complete, de-noised text out of a page — is increasingly the bottleneck, not search ranking. That's the argument for Firecrawl-class tooling in every research pipeline. Each API has a distinct job to be hired for. Exa is best for semantic research — its 'Find Similar' and Websets features make it the go-to for finding conceptually related content, not just keyword matches. Tavily is agent-focused and works well in tool-calling loops. Firecrawl leads on extraction quality: it can search, scrape, interact with dynamic pages, and crawl entire sites; the open-source core has 130k GitHub stars and integrates natively with Lovable. Perplexity Sonar combines search and synthesis with inline citations, priced on both tokens and a flat $5 per 1,000 searches. 40 per request, and its Monitor API handles continuous tracking. Linkup ranks 1 on the SimpleQA factuality benchmark, making it the right choice for accuracy-critical work in finance, legal, or health-adjacent domains. Brave offers an independent index with strong privacy defaults, roughly 670ms latency, and 2,000 free requests per month.

Key terms in this module

Semantic search

Semantic search is a way of searching by meaning instead of exact words, so it finds passages that say what you asked even when they use different wording. It usually works by comparing embeddings, which are lists of numbers that capture what a piece of text means.

Subagent

A subagent is a helper AI agent that a main agent hands a side task to: it works in its own separate context, with its own instructions and tool access, and sends back only a summary. This keeps the main conversation focused and lets tasks run in parallel.

Frequently asked questions

Who is "The Research System" for?

This Expert module in AI-Native Operator's Field Manual is for operators, founders and growth teams who run AI in real work and want production-grade judgement. It takes about 8 minutes and ends with a 5-question quiz.

Do I need to code?

Not necessarily. The workflows use operator tools such as Claude, n8n and Lovable; some exercises are easier if you are comfortable editing a config file or prompt template.

What comes before and after this module?

Before "The Research System", take "Lead Generation & GTM Engineering" (module 8 of AI-Native Operator's Field Manual). Afterwards, continue with "The Content Engine".

Related modules

• Previous
  Lead Generation & GTM Engineering

  Signal-driven plays that turn a stack into pipeline.

• Next
  The Content Engine

  LinkedIn, repurposing, and digital twins that produce voice, not slop.

• Same topic
  The Evidence Base: Why Most AI Initiatives Fail

  The failure rate is not a technology story. Every major study lands on the same cause: organizations that don't learn.

• Same topic
  RAG: When It's the Right Answer

  Retrieval and generation are two systems. Evaluate them separately, or debug them never.