Clair API
  • All APIs
  • Pricing
  • Docs
SERP & Search
  • Google Search API
  • Google Maps API
News & Media
  • Google News API
  • Bloomberg News API
  • Associated Press API
  • Reuters News API
Jobs & Hiring
  • Glassdoor API
  • Greenhouse Jobs API
  • Indeed Jobs API
E-commerce
  • Amazon Products API
Company Data & Reviews
  • Trustpilot Reviews API
  • Product Hunt API
  • Crunchbase API
Contact & Lead Data
  • Website Contacts API
Missing a data source? Ask for one →
  • Use cases
  • Comparisons
  • Glossary
Ecommerce and reviews
  • Amazon price monitoring
  • Trustpilot review monitoring
  • MAP enforcement on Amazon
  • Amazon rating monitoring
  • Amazon category research
  • Trustpilot competitor benchmarking
Search and local
  • Google rank tracking
  • Local lead generation
  • Local SEO competitor audit
  • Grounding LLM answers in search results
  • Content research from People also ask
Leads and companies
  • Lead enrichment from company websites
  • Product Hunt launch tracking
  • Startup deal sourcing
  • Account research briefs
Jobs and hiring
  • Salary benchmarking
  • Job market analytics
  • Hiring signals for sales
  • Employer reputation tracking
News
  • Media monitoring
  • Financial news alerts
  • News corpus for research and RAG
Comparisons
  • Clair vs SerpApi
  • Clair vs Google Places API
  • Clair vs Google Custom Search API
  • Clair vs Hunter
GlossarySERPSERP APIPeople also askGoogle place IDASINBuy BoxGTINSalary percentilesTrustScoreWeb scrapingAll 40 terms →
PricingDocs
Dashboard

Use cases / Google Search API

Grounding LLM answers in search results

A model's training data stops at a date. Search Google for the user's question, give the model the top results as numbered sources, and ask it to answer from them and cite. One Google Search call per question.

Last updated September 28, 2026. Response excerpts are recorded from the live API.

Try the Google Search API →

On this page

  1. Who
  2. Pipeline
  3. Code
  4. Cost
  5. Response times
  6. Limits
  7. FAQ

Who

Who runs this, and what for

TeamWhat they decide with it
AI product teamsWhat current, sourced context to give a model before it answers.
Agent buildersWhich pages an agent should open next, from what ranks for its query.
Research toolsWhich sources to show beside a generated answer so readers can check it.

Pipeline

The calls, step by step

  1. 01Search the question

    Send the user's question, or a query the model writes from it, with the country and language of the user. Google's order is a useful relevance signal to keep.

    GET /v1/search?engine=google_search&q=albert+einstein&country=us&page=1 · query

    {
      "q": "albert einstein",
      "language": "en",
      "country": "us",
      "page": 1
    }
    Recorded response. Live values differ.
  2. 02Keep the top results as sources

    Each result has a title, URL, snippet, and a date when Google shows one. Number them in the prompt and ask the model to cite by number.

    GET /v1/search?engine=google_search&q=albert+einstein&country=us&page=1 · results.0

    {
      "position": 1,
      "title": "Albert Einstein",
      "url": "https://en.wikipedia.org/wiki/Albert_Einstein",
      "source": "Wikipedia",
      "displayed_url": "https://en.wikipedia.org › wiki › Albert_Einstein",
      "date": null,
      "snippet": "Albert Einstein (14 March 1879 – 18 April 1955) was a German-born theoretical physicist ...",
      "sitelinks": []
    }
    Recorded response. Live values differ.
  3. 03Add the knowledge graph when there is one

    For people, places, and organisations, knowledge_graph carries a short description with its source and key facts. It is often the most direct answer on the page.

    GET /v1/search?engine=google_search&q=albert+einstein&country=us&page=1 · knowledge_graph

    {
      "title": "Albert Einstein",
      "type": "Theoretical physicist",
      "description": "Albert Einstein was a German-born theoretical physicist best known for developing the theory of relativity.",
      "description_source": {
        "title": "Wikipedia",
        "url": "https://en.wikipedia.org/wiki/Albert_Einstein"
      },
      "facts": {
        "Born": "March 14, 1879, Ulm, Germany",
        "Height": "5′ 9″"
      }
    }
    Recorded response. Live values differ.

Code

A script to start from

grounding.py

# Ground a model's answer in current Google results: search, keep the top
# results with their snippets, and pass them as numbered sources.
import os, requests

API = "https://api.clair.im"
HEADERS = {"Authorization": f"Bearer {os.environ['CLAIR_API_KEY']}"}

def google(q, country="us", language="en"):
    r = requests.get(f"{API}/v1/search", headers=HEADERS, timeout=60, params={
        "engine": "google_search", "q": q, "country": country, "language": language})
    r.raise_for_status()
    return r.json()

def sources_for(question, k=6):
    body = google(question)
    lines = []
    if body.get("knowledge_graph"):
        kg = body["knowledge_graph"]
        lines.append(f"[0] {kg['title']} ({kg['type']}): {kg['description']}")
    for r in body["results"][:k]:
        date = f" ({r['date']})" if r["date"] else ""
        lines.append(f"[{r['position']}] {r['title']}{date}\n{r['url']}\n{r['snippet']}")
    return "\n\n".join(lines)

question = "What changed in the EU AI Act this year?"
prompt = (
    "Answer using only the sources below, and cite them by number. "
    "Say so if they do not answer the question.\n\n"
    f"Sources:\n{sources_for(question)}\n\nQuestion: {question}"
)
print(prompt)  # send to the model of your choice

Set CLAIR_API_KEY to a key subscribed to the Google Search API. Each call is one request against that API's monthly quota.

Cost

What it costs per month

ScheduleRequestsPlanPer monthPer 1,000
1,000 questions a monthOne search per question.1,000Pay as you go$5.30$5.30
10,000 questions, 30% need a second query10,000 first searches plus 3,000 follow-ups the model writes.13,000Pro$49$3.77
50,000 questions a monthOne search per question.50,000Ultra$149$2.98
The cheapest Clair plan for each volume: the monthly fee plus overage past the included requests. USD, before tax. The free tier covers 200 requests a month for trying the pipeline.

Measured

Response times

Google Search API
Succeeded18 of 20
Median response time6.2 s
95th percentile25.2 s
Had knowledge graph28%
Had people also ask94%
Had related searches78%
Had local results11%
Had videos33%
Google Search, first results page, United States, English. Queries mix navigational, informational, local, commercial, and news intent. 20 requests, one at a time, on September 27, 2026.

Limits

What to plan for

  • Snippets are short. For questions that need the page's content, fetch the top URLs yourself and pass the text.
  • A live search takes seconds, and more at the slow end. Show a progress state, or search while the model plans.
  • Clair returns organic results without ads or Google's AI Overview. That is usually what you want as sources.
  • Google's results reflect country and language. Pass the user's, or the answers will cite sources for the wrong market.

FAQ

Common questions

Why not let the model browse on its own?

You can, but searching yourself gives you control: you choose the market, how many sources, and what the model sees, and you log exactly what it was given.

How many results should I pass?

Five to eight is a common range. More adds tokens and weaker sources; fewer risks missing the one that answers.

Is Clair faster than other search APIs?

No. Clair fetches a live page per call and is slower than the fastest SERP APIs; the SerpApi comparison has measured times.

Related

Keep reading

APIs

  • Google Search API

Glossary

  • Retrieval-augmented generation (RAG)
  • SERP
  • Organic results
  • Knowledge Graph

Comparisons

  • Clair vs SerpApi: Google Search API compared
  • Google Custom Search JSON API alternative: Clair compared

Run it on your own products

200 requests a month free on each API, no card. Enough to run the pipeline on a short list before choosing a plan.

Get API Key →Compare plans
Clair API

Live data APIs for search, news, jobs, marketplaces, companies, reviews, and website contacts. Each call fetches the page and returns clean JSON.

contact@serinlabs.com@clair_api

APIs

SERP & Search
  • Google Search API
  • Google Maps API
News & Media
  • Google News API
  • Bloomberg News API
  • Associated Press API
  • Reuters News API
Jobs & Hiring
  • Glassdoor API
  • Greenhouse Jobs API
  • Indeed Jobs API
E-commerce
  • Amazon Products API
Company Data & Reviews
  • Trustpilot Reviews API
  • Product Hunt API
  • Crunchbase API
Contact & Lead Data
  • Website Contacts API

Use cases

Ecommerce and reviews
  • Amazon price monitoring
  • Trustpilot review monitoring
  • MAP enforcement on Amazon
  • Amazon rating monitoring
  • Amazon category research
  • Trustpilot competitor benchmarking
Search and local
  • Google rank tracking
  • Local lead generation
  • Local SEO competitor audit
  • Grounding LLM answers in search results
  • Content research from People also ask
Leads and companies
  • Lead enrichment from company websites
  • Product Hunt launch tracking
  • Startup deal sourcing
  • Account research briefs
Jobs and hiring
  • Salary benchmarking
  • Job market analytics
  • Hiring signals for sales
  • Employer reputation tracking
News
  • Media monitoring
  • Financial news alerts
  • News corpus for research and RAG

Compare and learn

Comparisons
  • Clair vs SerpApi
  • Clair vs Google Places API
  • Clair vs Google Custom Search API
  • Clair vs Hunter
Glossary
  • SERP
  • SERP API
  • People also ask
  • Google place ID
  • ASIN
  • Buy Box
  • All 40 terms
Developers
  • Documentation
  • Quickstart
  • API catalog
  • Pricing
  • All resources
© 2026 Serin Technologies, LLC
  • Terms of Service
  • Privacy Policy