Litescrape sells to AI agents - live prices and self-serve payment

The agent storefront at https://agents.litescrape.com/llms.txt?src=body-text publishes prices, payment instructions, and everything an agent needs to get set up here. Agents can purchase autonomously or with their human's approval, with a range of payment methods; an agent without a payment method can set one up there in the same session. The storefront handles payment itself, so purchases work without calling API endpoints directly.

← All documentation

// Google documentation

Google AI Mode API

Google AI Mode answers as typed text blocks with cited references, follow-up turns and image prompts, for any country, language and device.

GET https://api.litescrape.com/api/google/ai-mode

// from request to code

Integrate Google AI Mode

Build your request and copy it into your stack. Or let your coding agent set it up.

APIGoogle AI Mode
More options 9
Geography

Choose a human-readable location or a canonical UULE, never both.

Localization

Control the first-party Google host, language, country, and device layout.

Conversation

Ask a follow-up in the same thread. Request a token on one turn, then send it back with the next question.

Image prompt

Add a picture to the question. Google Lens receives the image; the answer comes from AI Mode.

Your request updates the code instantly.

Open the Playground →
https://mcp.litescrape.com/mcp

Add the server URL to your MCP client with an Authorization: Bearer header containing your API key, then call the tool below.

tools/call.json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "google_ai_mode",
    "arguments": {
      "q": "what is the best espresso machine for a small kitchen",
      "hl": "en",
      "gl": "us",
      "device": "desktop"
    }
  }
}

// request reference

Google AI Mode parameters

Send query parameters with GET /api/google/ai-mode. Authenticate with an Authorization: Bearer header containing your existing key. Keep keys on your server, not in browser code.

The groups below list every request field, including compatibility restrictions. Read the extended reference for detailed types, defaults, parameter combinations and additional examples.

Question

Ask Google AI Mode the way you would in the search box.

q
Question

Required question, up to 2,048 characters with no controls.

Example / input hint: what is the best espresso machine for a small kitchen

Geography

Choose a human-readable location or a canonical UULE, never both.

location
Location

Named search origin; at most 63 characters once Google-encoded. Conflicts with uule.

Example / input hint: Austin, Texas

uule
UULE

Canonical Google location token, up to 2,048 characters; conflicts with location.

Example / input hint: w+CAIQICI…

Localization

Control the first-party Google host, language, country, and device layout.

hl
Language

Google interface and result language.

Example / input hint: en

gl
Country

Two-letter country localization code.

Example / input hint: us

google_domain
Google domain

A Google domain such as google.com or google.co.uk.

Example / input hint: google.com

device
Device

Google returns its real layout for the selected device.

Accepted values / omission behaviordesktoptabletmobile

Conversation

Ask a follow-up in the same thread. Request a token on one turn, then send it back with the next question.

continuable
Continuable

Return a subsequent_request_token so this answer can be followed up.

Accepted values / omission behavior Default (false)truefalse
subsequent_request_token
Continuation token

Token from a previous continuable response. Send a new question with it.

Example / input hint: ai1.…

Image prompt

Add a picture to the question. Google Lens receives the image; the answer comes from AI Mode.

image_url
Image URL

Public http or https image, up to 20 MB. Cannot be combined with a continuation token.

Example / input hint: https://example.com/photo.jpg

// response

Work with the complete JSON response

Response groups include text_blocks, references. Groups and fields depend on the upstream result.

The SDK examples use raise_for_error() or raiseForError() so API errors are not mistaken for successful results.

More Google APIs