Web search API, pay per call
Search the web and get the top results as JSON: title, URL, a short snippet and the page age, from the Brave Search API. 1-20 results per call. Results are for the caller's immediate use only: no storing, resale or model training (Brave API terms). Upstream failures and exhausted daily capacity return 503, uncharged. Pair with /extract to read a result in full. Use when an agent needs current information or sources from the open web.
When an agent wants this
- Give an agent current information or sources from the open web in one call
- Get title, URL, snippet and page age for 1-20 results, then read one in full with /extract
- Ground an answer in live web results without an account or a monthly plan
Web search results: search the web for a query and get the top pages with title, URL and snippet as JSON $0.01
Search the web and get the top results as JSON: title, URL, a short snippet and the page age, from the Brave Search API. 1-20 results per call. Results are for the caller's immediate use only: no storing, resale or model training (Brave API terms). Upstream failures and exhausted daily capacity return 503, uncharged. Pair with /extract to read a result in full. Use when an agent needs current information or sources from the open web.
Inputs: q (required): Search query, at most 400 characters; count: Number of results (1-20, default 10).
Not in the free calls (it costs capacity per call); pay from the first call.
With a card key from /credits, in a header or, when your client can only fetch a URL, in the URL:
curl -H "Authorization: Bearer adt_…" "https://tools.funwords.eu/search?q=x402%20payment%20protocol"
curl "https://tools.funwords.eu/search?q=x402%20payment%20protocol&api_key=adt_…"
Without a key the same URL answers 402 Payment Required with x402 and MPP terms, so a wallet client pays USDC per call and retries. Over MCP (https://tools.funwords.eu/mcp) this tool is search.
Example result
{
"query": "x402 payment protocol",
"provider": "Brave Search",
"count": 1,
"results": [
{
"title": "x402: an open payment protocol",
"url": "https://www.x402.org/",
"snippet": "x402 lets any HTTP API charge per request in stablecoins…",
"age": "2 days ago"
}
],
"terms": "Results are for the caller's immediate use: no storing or caching beyond the current task, no resale and no model training (Brave Search API terms)."
}Web answer, AI with citations: answer a question from live search results $0.01
Answer a question from the live web in one call: a Brave web search, the top result pages read, and an answer written by Llama 4 Scout from those sources only, with inline [n] citations and the source list (title, URL). Says so when the sources do not answer it. Results are for the caller's immediate use only: no storing, resale or model training (Brave API terms). Use when an agent needs a current, sourced answer rather than raw search results.
Inputs: q (required): The question, at most 400 characters.
Not in the free calls (it costs capacity per call); pay from the first call.
With a card key from /credits, in a header or, when your client can only fetch a URL, in the URL:
curl -H "Authorization: Bearer adt_…" "https://tools.funwords.eu/ai/answer?q=What%20is%20the%20x402%20payment%20protocol%3F"
curl "https://tools.funwords.eu/ai/answer?q=What%20is%20the%20x402%20payment%20protocol%3F&api_key=adt_…"
Without a key the same URL answers 402 Payment Required with x402 and MPP terms, so a wallet client pays USDC per call and retries. Over MCP (https://tools.funwords.eu/mcp) this tool is ai_answer.
Example result
{
"question": "What is the x402 payment protocol?",
"answer": "x402 is an open protocol that lets an HTTP server charge for a request: it answers 402 Payment Required with the price, and the client pays in stablecoins and retries [1][2].",
"sources": [
{
"n": 1,
"title": "x402: an open payment protocol",
"url": "https://www.x402.org/"
}
],
"model": "@cf/meta/llama-4-scout-17b-16e-instruct",
"terms": "Results are for the caller's immediate use…"
}Questions
Where do the results come from?
The Brave Search API, one request per paid call. Results are for the caller's immediate use: no storing, resale or model training.
What if the search provider is down or the daily capacity is used up?
The call answers 503 and nothing is charged.
How do I pay?
Each successful call costs the tool's price; failed calls are not charged. Then pay with card credits from $1 (the key goes in an Authorization header or as api_key= in the URL) or per call in USDC over x402 or MPP. No account is needed.