Gemini scraper API

Request

curl -X POST "https://api.answerline.dev/v1/monitor/gemini" \
  -H "Authorization: Bearer $API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"prompt":"iPhone 17 or Galaxy S26?","country":"US"}'

import { Client } from "@answerline/sdk";

const client = new Client({ apiKey: process.env.API_KEY! });
const answer = await client.monitor.gemini({
  "prompt": "iPhone 17 or Galaxy S26?",
  "country": "US"
});

import os
from answerline import Client

with Client(os.environ["API_KEY"]) as client:
    answer = client.monitor.gemini(
        prompt="iPhone 17 or Galaxy S26?",
        country="US",
    )

Every request option is on the Gemini reference page.

What you get back

Full field definitions are on the Gemini reference page.

The Gemini app answer versus grounding in the Gemini API

This endpoint returns the answer the Gemini app gives a user for a prompt and market, as text, markdown, links, sources, citationPills and shoppingCards.

Google’s developer API offers grounding with Google Search for your own prompts. Its guide (checked 2026-09-17, ai.google.dev) says a grounded response contains the search queries the model executed, url_citation annotations that tie text segments to source URLs, and a search-suggestions HTML snippet whose use is governed by the Gemini API terms. The same page says Gemini 3 models are billed per search query the model decides to run, and Gemini 2.5 and older per prompt.

Grounding is a tool for building your own product. For measuring what Gemini tells the public it has a flaw: model choice, system instructions and tool settings are yours, so you measure your configuration. The app answer reflects Google’s choices, which are what users see.

The app also shows product cards beside shopping answers, with prices, stores and ratings, which come back here as shoppingCards. For e-commerce brands that card is the recommendation. Place cards (places) are not returned today. And citationPills records which sources sit behind each inline chip in the app, including section-summary chips that cite several sources at once.

An annotated response

The excerpt follows the result schema for POST /v1/monitor/gemini. Values are illustrative; the request set include.markdown to true.

{
  "success": true,
  "result": {
    "text": "Both phones are strong choices. The iPhone 17 favours...",
    "markdown": "Both phones are strong choices.\n\n## Camera\nThe iPhone 17 favours...",
    // Sources in order. position is an integer here.
    "sources": [
      {
        "position": 1,
        "label": "iPhone 17 vs Galaxy S26: camera test",
        "url": "https://www.example-tech.de/vergleich/iphone-17-galaxy-s26",
        "description": "Side-by-side photos in low light..."
      },
      {
        "position": 2,
        "label": "Galaxy S26 review",
        "url": "https://www.example-mobile.com/reviews/galaxy-s26",
        "description": "Battery life and display..."
      }
    ],
    // One entry per (chip, source). citationPillId is 1-based and shared by every
    // source in the same chip; position points into result.sources.
    // label is always present but may be "" -- fall back to domain.
    "citationPills": [
      { "label": "iPhone 17 vs Galaxy S26: camera test", "citationPillId": 1, "url": "https://www.example-tech.de/vergleich/iphone-17-galaxy-s26", "domain": "example-tech.de", "position": 1 },
      { "label": "", "citationPillId": 1, "url": "https://www.example-mobile.com/reviews/galaxy-s26", "domain": "example-mobile.com", "position": 2 }
    ]
    // "shoppingCards" appears when Gemini shows products, e.g.:
    // "shoppingCards": [{ "position": 1, "title": "Example Phone 17", "productId": "1234567890",
    //   "productLink": "https://www.google.com/search?q=...&prds=productid%3A1234567890",
    //   "price": { "raw": "€949.00", "value": 949, "currency": "EUR" }, "store": "Example Shop",
    //   "storeCount": 4, "rating": 4.6, "reviews": 812, "brand": "Example" }]
  }
}

Every answer is the one gemini.google.com shows for the prompt. result.provenance reads searchMode engine-default and interface web-app, or desktop-web on some requests for include.html or include.screenshot (all fields).

Notes for this engine

• shoppingCards[] always has position, title, productLink and productId. price (raw, value, currency), oldPrice, store, storeCount, brand, description, rating, reviews, thumbnail, images, catalogId and gpcId appear when Gemini shows them. storeLink, shipping and deliveryTime are not filled.
• places is not returned today.
• citationPills is empty and shoppingCards absent when there are none.
• html (with include.html) links a copy of the Gemini page as it was when the answer was captured.

Shopping cards appear only on answers where Gemini shows products. Read shoppingCards with a default, and report the share of answers that carried them.

citationPills[].label can be "". Identify sources by domain or url.

Gemini answers vary between runs, so sample each prompt several times per period and report rates with sample sizes; see sampling vs census.

This endpoint has no hl or city option, so the prompt text is your only language control. It accepts a US state, which implies country US, and answers from inside that state (states). For multilingual studies write each prompt in the market’s language and keep the translations fixed across runs; multilingual AI answers covers the design.

Related: the best Gemini scrapers compared, monitoring Gemini, AI visibility tracking, competitor analysis, every request field.

From the blog

Docs

• Quickstart
• API reference
• Engine features
• Async tasks and batches
• Webhooks
• Coverage
• Pricing and failures
• Rate limits

Other engines