Give your AI a live web search, and see the price before it runs.
A ranked list of public web pages for any query, asked from Claude, ChatGPT, Cursor, Codex or your own code. No search-API account or key of your own: each search is quoted before it runs and paid from one toolfare balance, next to the tools that read, crawl and answer from the pages it finds.
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.
Ranked pages for any query
From $0.021Search the public web and return ranked result pages
- “Search the web for recent articles on MCP server security.”
- “Find the official docs page for the Stripe Checkout Sessions API.”
- “What are people writing about our product launch? Give me the top ten 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_searchSearch the public web and return ranked result pages
From $0.021
Required parameters:
queryOptional parameters:
limit
Use it when
- Your agent needs current information that is not in its training data.
- You want a list of sources to choose from, not a finished answer.
- You need to find the right URLs before reading or crawling them.
- You are building an agent or LLM app that needs a search step it can call itself.
Look elsewhere when
- You want one written answer with its sources cited, not a list of pages. Use this instead
- You already have the URL and need the page’s text. Use this instead
- You need Google’s organic results for a keyword, by location and language. Use this instead
Web Search directly, or through toolfare
Directly
- An account and API key with a search API vendor
- A separate plan, invoice and rate-limit tier
- Your own code to call it and pass the results to the model
Through toolfare
- Pay per search, quoted before it runs, from the same balance as every other tool
- No search vendor key to put in an agent’s config
- Search, read, crawl and answer tools behind one connection
It is a plain search call: toolfare keeps no index of its own and does not re-rank, filter or summarise the results.
Limits
- Public web only — nothing behind a login or paywall.
- One query per call; the number of results is set with `limit`, ten by default.
- The order is the search provider’s own ranking, not a Google position. Use Search Results for Google rankings.
- 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
A search your agent can run itself: it sends a query and gets back a ranked list of public web pages to read or cite. Here it is one tool, `web_search`, reachable over MCP, the toolfare CLI or HTTP.
No. toolfare holds the supplier account. You sign in once with OAuth for MCP, or use one toolfare API key in scripts and servers.
Each tool’s current price is shown on this page and quoted before the call runs.
Yes. Create an API key in the toolfare console and call the tool over HTTP, or run it from a shell script with the toolfare CLI.
No. Web Search is a general web search for finding pages an agent can read. For Google’s organic results for a keyword, with location and language, use Search Results.