Quick answer
What is LLMWebSearch and who runs it?
LLMWebSearch is a web search API for AI agents, operated by SerpGoat LLC. One call runs a live web search and hands back ranked results, with the pages of the first 3 already read and cleaned into Markdown. Credits are prepaid in crypto from $9.25 for 5,000 searches, they never expire, and opening an account needs no KYC: no ID, no selfie, no documents.
What problem does LLMWebSearch solve?
An agent that answers questions about the present needs two things: a list of relevant pages, and the text of those pages. Most stacks wire a search tool and a separate fetch tool together, then pay twice and debug two failure modes.
LLMWebSearch does both in one request. Your agent sends a query; it gets back the results in ranked order and the readable content of the top pages, sized to fit its context window. The model can then write its answer and cite the URLs it actually read.
Who operates the service?
SerpGoat LLC sells the credits, runs the API and answers support. It is the party to the terms of service and the controller described in the privacy policy.
Support is handled by people, not a chatbot: A person answers support emails within 12 hours, seven days a week, and helps you wire search into your agent or framework. Write to [email protected] for help and to [email protected] for abuse reports. Nobody from our team will ever ask for your account number or one of your API keys, by email or in a chat.
What happens between my query and the response?
Four steps run inside one call, and the response tells you how each page went.
- Search. 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.
- Filter. Country, language, time range, news or web, and your domain lists are applied. 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.
- Read. Our page reader fetches the first results, up to the number you set with
read. It identifies itself and checks robots.txt before it opens a page. - Clean. The main content of each page is kept, menus and banners are dropped, and the text comes back as Markdown or plain text with a word count.
A page that a site refuses still appears in the results, with its title, URL and snippet, and a content_status field that says why there is no text.
Why does the API return sources instead of an answer?
The API returns sources, not a written answer: your own model reads the pages, writes the reply and cites the URLs. That choice keeps three things in your hands: which model writes, how it writes, and what it is allowed to claim.
It also keeps the bill simple. An answer engine charges for the search and again for the tokens it spends writing. Here you pay one credit per search, and your own model decides how much of the returned text it needs.
How do you treat the websites you read?
With the same rules for every customer, and none of them can be switched off.
- 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.
- A site that sets Content-Signal: ai-input=no in its robots.txt keeps its pages out of your results' content.
- 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.
Site owners can read what our reader does, and how to block it, on the page reader page. We do not keep a copy of the pages we read for you.
Why crypto and no identity checks?
Because many of the developers who build agents want to pay without handing over a passport, a card or a company registration. Prepaid credits funded in BTC, USDT, USDC, ETH, SOL, LTC make that possible: the money is on the balance before any search runs, so we have no reason to ask who you are.
No KYC does not mean no rules. The acceptable use policy applies to every account, and a person reviews every abuse report.
What will you never claim on this site?
Numbers we cannot show you. You will not find an uptime percentage, a latency promise, an index size, a customer count or a review score on these pages. Prices and limits are stated with their date, competitor figures come with a link to the page we read, and changes to the API or to prices are listed on the changelog.
Questions about the company and the service
Is LLMWebSearch a search engine with its own index?
No. It runs a live web search when you call it and reads the top pages at that moment. We do not crawl the web in advance and we make no claim about an index.
Who can I contact about my account?
Write to [email protected]. A person answers support emails within 12 hours, seven days a week, and helps you wire search into your agent or framework. Never include your account number or an API key in a message.
Can a website owner ask you to stop reading their pages?
Yes, and the quickest way is robots.txt: a rule for LLMWebSearch or for all robots is applied on our side. The page reader page has ready-to-copy examples.
Do you train AI models on my searches?
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. The privacy policy lists what each call leaves in our logs.