No KYC — no ID, no selfie, no documents. Pay in crypto: BTC, USDT, USDC, ETH, SOL, LTC
Language: English
Get an API key

A free health check and how to read the answer

Is the search API working?

This page has no uptime gauge and no invented history. It gives you a check you can run yourself, explains how to tell our problems from a website's refusal, and says where incidents are written down.

Last updated:

Quick answer

How do I check that LLMWebSearch is working?

Call GET https://llmwebsearch.com/api/v1/credits with your key. It is free, it touches no website, and a normal JSON answer proves that the LLMWebSearch API, your key and your account work. Then run one search, which costs 1 credit from a pack priced from $1.20/1K searches. Errors on our side are never charged, and incidents are dated on the changelog.

What is the quickest health check?

The credits endpoint. It answers from our side only: authentication, the API and your account. If it returns your remaining credits, the service is up for you. If it returns 401, the key is wrong or revoked; create a new one in the dashboard.

curl: health check (free) and remaining credits
curl -s https://llmwebsearch.com/api/v1/credits \
  -H "Authorization: Bearer $LLMWEBSEARCH_API_KEY"
Python: the same check inside a monitoring script
import os
import sys

import requests

resp = requests.get(
    "https://llmwebsearch.com/api/v1/credits",
    headers={"Authorization": f"Bearer {os.environ['LLMWEBSEARCH_API_KEY']}"},
    timeout=10,
)
if resp.status_code != 200:
    print("API check failed:", resp.status_code, resp.text[:200])
    sys.exit(1)
print("API up, credits left:", resp.json()["credits_remaining"])

How do I tell our error from a website's refusal?

Look at where the problem appears in the response.

  • An HTTP error on the whole call (502 search_failed, 504 search_timeout) is on our side or upstream. It costs nothing; wait a little and retry with a growing delay.
  • A successful call with some results lacking content is about those pages. Each result carries a content_status: blocked_by_robots, blocked_by_site_policy, target_refused, fetch_failed or fetch_timeout. The search itself worked.

The second case is normal on the open web and is not an incident. The errors page lists every code.

Where are incidents recorded?

On the changelog. An incident that affects many accounts gets a dated entry: what failed, from when to when, and what changed afterwards. Calls that failed during an incident were not charged, so there is nothing to reclaim.

We do not publish an uptime percentage or a latency figure. We would rather give you a check you can run than a number you cannot verify.

What should my agent do when a call fails?

Retry only what can succeed later. A 429 rate_limited, 502 search_failed or 504 search_timeout deserves a retry after a short wait that doubles each time. A 401 or 402 needs a person: a new key or more credits. A page refused by its website should not be retried at all; use the other results of the same search instead.

Status questions

Does the credits call use any credit?

No. GET https://llmwebsearch.com/api/v1/credits is free, so a monitoring job can run it as often as your per-minute limit allows.

My search worked but one result has no content. Is that an outage?

No. That page could not be read: its content_status says why. 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.

Who do I tell about a problem the health check does not show?

Support at [email protected], with the time, the endpoint and one full failing response. A person answers within 12 hours.

From $1.20/1K searches · no KYC

Get an API key