Tabstack Web Research - Run a research agent with cited answers in a single API call

We launched /research today, a single API call that runs a full web research agent and returns cited answers.

Here's the pattern it replaces:

// What most teams build:

// 1. Search the web (or an index)

// 2. Fetch and read relevant pages

// 3. Synthesize across sources

// 4. Validate citations

// 5. Format for streaming

// 6. Debug all of the above forever

// What /research does:

const stream = await client.agent.research({ query: 'Your question here' })

That's it. The orchestration lives inside the call. Your codebase doesn't own it.

First 10,000 credits are free. Happy to answer questions in the comments. Give it a try → https://tabstack.ai/web-research

Three things that matter about how we built this:

1. Citations are not optional.

Every claim comes back with a source URL. Users can verify where the answer came from. That's the difference between an AI feature people trust and one they don't.

2. Live web, not an index.

Pre-indexed research APIs (Exa, Perplexity) are fast and good for broad questions. /research goes to the live web on every call. For legal, financial, and competitive intelligence work — where the answer needs to be current and sourced — that's the relevant difference.

3. SSE streaming built in.

Users watch it work in real time. No spinning wheel. Progress events as sources are found, then a complete event with the full report and all citations.

happy to share this new collaboration with @tessak22 and the @Tabstack team!

First launched on @Product Hunt last April, the @Mozilla-backed platform is launching again today, introducing a new /research endpoint.

Run agents to explore the web and answer complex questions with precision, all in a single API call. Simple, accurate, and secure. Read the docs to learn more: https://docs.tabstack.ai/guides/research/

There are multiple products in the browser automation category - @Tabstack just hits differently.

Start for free: https://tabstack.ai/web-research

How do you pick sources and avoid low quality SEO pages, and can users whitelist domains?

The citations part is what matters most to me here. For research workflows, a good looking answer is not enough if people cannot check where it came from. Live web also makes sense for topics that change quickly, especially competitive research or financial updates. How do you handle cases where sources disagree with each other? Do you show conflicting findings or choose the strongest source?

Liked the no-scraper web-extract angle — gave it a quick test with Lastest, run here: https://app.lastest.cloud/r/owYo...

The “citations are not optional” stance is exactly right, especially for legal / financial / competitive-intel use cases.

One thing I’d be curious about: do you treat citations as source links only, or as claim-level support? In research workflows, a source URL is helpful, but the trust really jumps when the user can see which sentence or assertion each source is meant to support, plus whether another source disagreed or was skipped as stale.

That extra bit of provenance would make the output much easier to use in a report without forcing someone to re-run the whole research process manually.

The "cited answers from the live web, source URLs users can verify" point is exactly the bar for any signal you'd act on financially. I work in finance and also built PolyMind (polyminds.netlify.app), which pulls real-time signal from Polymarket trades — and the hardest part was never fetching data, it was making every alert traceable back to a verifiable source so a user can sanity-check it before trusting it. Curious how Tabstack handles conflicting sources on the same question — does /research surface the disagreement, or pick a winner?

The live-web approach vs pre-indexed APIs is a real tradeoff I've thought about while building research features. Pre-indexed is faster and cheaper at scale, but for anything time-sensitive — earnings reports, product launches, competitive moves — the index lag can be 24-48h which is basically useless. Live web is the only option there.

One thing I'm curious about: when sources conflict, the "prioritize most authoritative source" approach makes sense, but how do you define authoritative? Domain reputation, recency, citation count? I've seen cases where a newer but less-established source had the correct info and an older authoritative source was stale. Would love to see the conflict resolution logic exposed more transparently in the output.

interesting product elegant in its simplicity. questions:
- how do you deal with possible hallucinations and making up URLs, since some AI are known for that?
- can I connect it to my existing orchestration layer to have all my tools in one place?

congrats on the launch and good luck!