Quick answer
What are the LLMWebSearch terms in brief?
You buy prepaid search credits for the LLMWebSearch web search API from a crypto balance topped up with at least $25. 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. Search credits have no expiry date: what you do not use this month is still there next year. Our page reader follows each site's robots.txt, the acceptable use policy is part of these terms, and the seller is SerpGoat LLC. No KYC is required to open an account.
1. Who agrees to these terms?
The account holder and SerpGoat LLC, the company that runs LLMWebSearch. The account holder can be a person or an organisation. By creating an account, sending a top-up or calling the API, the account holder accepts these terms and the acceptable use policy.
2. What do you sell?
Access to a web search API. A call to https://llmwebsearch.com/api/v1/search runs a live web search and returns ranked results; the first pages can be read and returned as Markdown or plain text. A call to https://llmwebsearch.com/api/v1/extract reads URLs you already have.
We do not write the pages we return and we do not edit them. Results change over time, and the same query can bring different results an hour later. The API returns sources, not a written answer: your own model reads the pages, writes the reply and cites the URLs.
3. How do accounts and keys work?
Sign in with an account number; an email address is optional. Your account number is how you sign in, so store it carefully. With an optional email on file you can recover it; with no email, a lost number is gone for good.
Make one API key per agent, app or teammate and revoke any of them from the dashboard without touching the others. Every call made with one of your keys spends your credits, so treat keys like passwords and revoke a key as soon as it leaks. Keep to one account per person or organisation.
4. How are credits used, and do they expire?
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. 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.
Search credits have no expiry date: what you do not use this month is still there next year. Credits disappear only when you close your account or when we close it for a breach of these terms. If we ever stop the service, we give at least 30 days' notice so you can spend the rest of your credits or ask for their value to be moved.
5. How do I pay?
Prices are listed in US dollars on the pricing page. You fund a balance in BTC, USDT, USDC, ETH, SOL, LTC, at least $25 at a time, and you buy credit packs from it. Send the exact amount on the network the payment page shows; the top-up is credited once the payment has been checked and confirmed on the blockchain.
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. The sender pays the network fee.
6. When do I get money or credits back?
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 applies these rules to concrete cases.
7. What rules apply when pages are read for me?
Three rules run on every read and no account can turn them 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.
You decide what you do with the text you receive, and you are responsible for respecting the rights of its authors. 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.
8. Are there limits on how fast I can search?
Yes. Every account has a per-minute call limit, shown in the dashboard; ask support and it can be raised. A call over the limit gets 429 rate_limited and is not charged. We may also slow the reading of pages from a single website to spare it.
9. Can I resell access to the API?
You can build products on top of LLMWebSearch, such as an agent, an app or a report that uses search results. You cannot sell our API itself, or a thin layer around it, as a search API to others without our written agreement. Ask at [email protected] if you are unsure where the line is.
10. When can you suspend an account?
When an account breaks these terms or the acceptable use policy, when a payment proves fraudulent, or when a law requires it. A person looks at the facts before a suspension. We tell you why, unless the law forbids it.
11. What do you promise, and what not?
We provide the service as it is offered on the day you use it. We do not guarantee that a query returns a particular result, that a website lets our reader in, or that the API is never interrupted. Calls that end in an error cost nothing, which caps what a failure costs you.
12. How far does your liability go?
As far as the law permits, our total liability for all claims is capped at what you paid us during the 12 months before the event behind the claim. We are not liable for indirect harm such as lost revenue or lost data. Nothing here limits a liability that the law forbids us to limit.
13. Will the API or the prices change under me?
Not without notice. In version 1 of the API, we may add fields and parameters, but we do not rename or remove the ones you use; a breaking change would come as a new version. Packs you already hold are never repriced: a higher price affects only packs bought after its publication. Both kinds of change are dated on the changelog.
14. How are these terms updated?
Each version carries its date, and changes are listed on the changelog. A change that takes away a right you have applies only to credits bought after it is published. Write to [email protected] with any question about these terms.