Ask a question, get an answer from the live web with the pages it came from.
One call takes a question and returns an answer drawn from the public web, with the pages it cites. Use it from Claude, ChatGPT, Cursor, Codex or your own code when you want a sourced answer rather than a list of links — no vendor account of your own, quoted before each call, paid from one balance.
1Connect your AI app
Pick the app you use. You do this once, and every API on toolfare is then available in it.
Add toolfare as a connector in Claude
Add to Claudehttps://api.toolfare.ai/mcp
- 1Open Customize → Connectors and choose "Add custom connector".
- 2Paste this URL as the remote MCP server URL.
- 3Leave the OAuth client id and secret under Advanced settings empty.
- 4Complete the browser authorization, then return to your conversation.
Custom connectors are available on Free, Pro, Max, Team and Enterprise. A Free account may hold one custom connector in total.
Claude’s own instructions2What to ask
Copy a prompt into your AI app once you’re connected. It picks the right one of the 1 tools and tells you the price first.
An answer, with the pages behind it
From $0.021Answer a question from the public web with cited pages
- “What changed in the latest Next.js release? Cite your sources.”
- “Is the EU AI Act already in force for general-purpose models? Show me where that comes from.”
- “Which countries does Stripe Tax support? Give me the source pages.”
1Create an API key
One key and one endpoint for every API on toolfare.
export TOOLFARE_API_KEY='tf_live_…'
2Every tool and its input
Send the tool name and its arguments as JSON; the reply is JSON too.
web_answer_answerAnswer a question from the public web with cited pages
From $0.021
Required parameters:
query
Use it when
- You want a short, current answer and the pages that support it, in one call.
- Your app or agent shows users answers and needs to show where they came from.
- You want to check a claim against the live web before repeating it.
Look elsewhere when
- You want to pick the sources yourself from a ranked list of pages. Use this instead
- You need the full text of a specific page, not an answer about it. Use this instead
- You need every page of a documentation site for your own index. Use this instead
Web Answer directly, or through toolfare
Directly
- An account and API key with an answer-engine vendor
- Or your own pipeline: a search API, a page fetcher, a model and code to stitch citations together
- A separate plan and invoice for each piece
Through toolfare
- One call returns the answer and its cited pages, quoted before it runs
- No vendor key to hand to an agent; paid from the same balance as everything else
- Search and page-reading tools on the same connection when you want the raw sources
toolfare passes the answer through as returned; it does not check the citations or improve the answer, so treat it like any generated text.
Limits
- One question per call. The only input is the question — there is no option to restrict sources or domains.
- The answer is generated from the pages found; read the cited pages before relying on it.
- Public web only — nothing behind a login or paywall.
- Pay as you go from your toolfare balance, in US dollars; there is no subscription. A call runs when your balance covers its quote.
Questions
Yes. Each answer comes with the public web pages it cites, so your agent or your users can check the source.
Web Search returns a ranked list of pages and leaves the reading to your agent. Web Answer does the reading and returns one answer with the pages it used.
No. The tool takes only the question. To work from specific sites, find pages with Web Search or read known URLs with Web Reader.
No. toolfare holds the supplier account; you connect over MCP, the toolfare CLI or a toolfare API key.
Each tool’s current price is shown on this page and quoted before the call runs.