POST /answers researches a question for you. It searches the web, reads pages and looks up company records as the task needs, then returns:
json_content: the answer, in the shape you described injson_formatsources: the URLs it read
null, rather than guessed.
Use it when the answer needs searching or several sources. When you already know the page, /scrape with formats=json is cheaper. For a company’s profile from its URL, use /enrich.
Example request
Example response
Parameters
Over REST the default mode is
ultra, at 100 credits. Over MCP, prefetch_answer defaults to fast. Pass mode explicitly if cost matters.Writing good tasks
- Say what you want, not how to find it. “Who is the CEO of Stripe?” works better than “Search Google for Stripe’s CEO.”
- Name the site when you know it. “On linear.app, what does the Business plan cost?” reads that site first.
- Keep
json_formatflat and typed. Use0for numbers,""for strings,falsefor booleans and[]for lists.
Credits and errors
When no usable evidence turns up, the request fails with
RESEARCH_INCONCLUSIVE and isn’t charged. Rephrase the task, or name the site to research.
Next
Search
Just need the pages? Search and scrape them in one call.
MCP tool
prefetch_answer, for agents.