Web search API: frequently asked questions

LLMWebSearch is a web search API for AI agents that returns ranked results with the content of the top pages in Markdown, paid in crypto with no ID upload. Prepaid credits from $1.20/1K searches never expire. No KYC — no ID, no selfie, no documents. Pay in crypto. It is operated by SerpGoat LLC; the about page explains what happens during a call.

Each result carries its position, title, URL, host, snippet and, when it was read, the page's main content as Markdown or plain text with its word count and publication date when known. You choose how many results to get, from 1 to 20, and how many of the first ones are read, from 0 to 10, with the read parameter.

No. The API returns sources, not a written answer: your own model reads the pages, writes the reply and cites the URLs. That keeps the choice of model, tone and citations with you, and you pay no extra tokens for a summary you may not want.

Results come from a live web search run at the moment of your call, in the order the search engine ranks them; nothing is served from an old index. We do not run an index of our own, so we make no claim about how many pages it holds.

Yes. Set topic to news for news results and time_range to day, week, month or year. Choose the country and language of the results, a time range (past day, week, month or year), web or news results, and domains to include or exclude.

Yes, with the extract endpoint, https://llmwebsearch.com/api/v1/extract. Reading pages whose URLs you already have costs 1 credit for each started group of 3 pages returned with content, up to 20 URLs per call; refused or failed URLs are not counted. The same robots.txt rules apply.

As of October 2026, the 5,000 searches pack is $9.25, the 100,000 searches pack $145 and the 1,000,000 searches pack $1,200. The rate falls from $1.85/1K searches to $1.20/1K searches. Every pack is on the pricing page.

One credit pays for one search: up to 20 ranked results, with the pages of the first 3 read and returned as Markdown. Reading 4 to 10 pages makes it 2 credits. A call that ends in an error costs nothing. Each response states its cost in credits_used, so your agent can track spending as it goes.

No. Search credits have no expiry date: what you do not use this month is still there next year. That suits agents whose usage rises and falls from one month to the next.

No. Invalid parameters, a wrong key, a rate limit or an error on our side cost nothing. A page that a website refuses inside a successful search does not change that search's price either.

No. There is no free tier: the 5,000-search pack is the way to try it, bought from the minimum top-up; whatever you added only to reach that minimum comes back on request within 30 days, in USDT or USDC, as long as it is unspent.

Count the searches one task runs, then multiply by the tasks per day. A quick lookup is one search; a research task that plans several queries uses several. Run a day of real traffic on the 5,000 searches pack, then size the next pack from the credits_used totals.

BTC, USDT, USDC, ETH, SOL, LTC. USDT on TRC-20 or ERC-20, USDC on ERC-20. The crypto payment guide walks through a top-up.

None of them. Sign in with an account number; an email address is optional. The no-KYC page compares this with what other search APIs ask.

$25. Money on your balance does not expire and buys search credits whenever you want. When a pack is cheaper than the minimum top-up, the part you paid only to reach that minimum comes back to you on request within 30 days of payment, in USDT or USDC, provided it is still unspent. The rest of a balance is not returned unless the law requires it.

To your balance, in two cases. A pack bought in the last 72 hours goes back to your balance if less than 20% of its credits were spent. If a pack does not work and support cannot fix it within 24 hours, the whole pack goes back to your balance. Top-ups stay on the balance and are not paid out unless the law requires it; whatever you added only to reach the minimum top-up comes back on request within 30 days, in USDT or USDC, as long as it is unspent. The refund policy works through three examples.

Not today. Every call is paid from a prepaid balance. The crypto payment guide compares this with the providers that take per-call USDC.

One line per call, kept 30 days: the time, the account, the first 60 characters of the query, the number of results and pages, and the credits. The privacy policy has the full list.

No. We do not train any model on your queries or on what the API returns, and we add no rule of our own against storing results; the rights of the sites whose pages you read still apply.

We add no restriction of our own. The pages still belong to their authors, so copyright and each site's terms apply to what you keep and republish.

No. They see our page reader, LLMWebSearch/1.0 (+https://llmwebsearch.com/bot/), and never your account, key or identity.

Always. Our reader respects robots.txt: it introduces itself as LLMWebSearch, follows the rules a site writes for it or for all robots, and leaves out the content of any page it is not allowed to read. The page reader page shows the rules site owners can write.

The result stays in the list with its title, URL and snippet, and content_status says why there is no text: blocked_by_robots, blocked_by_site_policy or target_refused.

No. When a site turns our reader away, the result comes back without content and with the site's status: we never solve CAPTCHAs, sign in to accounts or work around a block or a paywall. If a site lets the reader in, the page is read normally; if not, its answer is passed on to you.

Add User-agent: LLMWebSearch and Disallow: / to your robots.txt. A site that sets Content-Signal: ai-input=no in its robots.txt keeps its pages out of your results' content.

Yes. The Python and Node.js guides cover searches, retries and parallel calls, and the quick start starts with curl. The API is plain HTTPS and JSON, so no SDK package is needed.

Yes, through a small MCP server you run yourself, shown on the MCP page. It gives the client a web search tool that returns sources with their text.

Yes. The LangChain and LlamaIndex page wraps the API as a tool and as a retriever, in a few dozen lines.

Yes. The OpenAI page gives the JSON schema of a web_search function and the loop that runs it and feeds the results back.

Both are covered: an HTTP Request tool for an n8n AI agent, and the MCP server added to OpenClaw.