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 Ads API Alpha

Text ads, local ads and shopping ads for any query, named location, language and device, with the rest of the Google results page.

GET / POST https://ecll-litescrape-v3--site-api-web.modal.run/api/google/ads

// from request to code

Integrate Google Ads

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

APIGoogle Ads
More options 5
Ad search

Choose both the query and the named location where Google should search.

Localization and filtering

Control language, safety, correction, and the Google device layout.

Your request updates the code instantly.

Open the Playground →

Set LITESCRAPE_API_KEY on your server, then run this request.

request.sh
curl --fail-with-body --get 'https://ecll-litescrape-v3--site-api-web.modal.run/api/google/ads' \
  --header "Authorization: Bearer $LITESCRAPE_API_KEY" \
  --data-urlencode 'q=coffee maker' \
  --data-urlencode 'location=Austin, Texas, United States' \
  --data-urlencode 'hl=en' \
  --data-urlencode 'device=desktop'

Read all parameters →

JSON POST request example

POST to https://ecll-litescrape-v3--site-api-web.modal.run/api/google/ads with Content-Type: application/json and your Authorization: Bearer header.

POST · application/json
{
  "q": "coffee maker",
  "location": "Austin, Texas, United States"
}

// request reference

Google Ads parameters

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

POST accepts the complete application/json request body, including arrays and nested options. Dotted names describe fields inside an object; [] denotes each array item. This reference is generated from the v3 OpenAPI contract.

Total request execution budget in seconds, greater than 0 and at most 90. Supply in the query string for GET or POST. page_timeout cannot extend this budget.

Query and location

q
QueryRequired

Google Ads search query, up to 2,048 characters with no controls.

Type string · GET query or POST JSON

Example / input hint: coffee maker

location
LocationRequired

Human-readable location where the ad search originates, up to 63 UTF-8 bytes once Google-encoded.

Type string · GET query or POST JSON

Example / input hint: Austin, Texas, United States

  • Example: Austin, Texas, United States.

Language, filtering, and device

hl
LanguageOptional

Google interface and result language, such as en, en-GB, or de.

Type string · GET query or POST JSON · Default en

Example / input hint: en

safe
Safe searchOptional

Google adult-content filtering.

Type string · GET query or POST JSON

Accepted valuesactiveoff
nfpr
Auto-correctionOptional

Google spelling auto-correction control. Set 1 to exclude corrected queries.

Type string · GET query or POST JSON

Accepted values01
device
DeviceOptional

Google returns its real layout for the selected device.

Type string · GET query or POST JSON · Default desktop

Accepted valuesdesktoptabletmobile

// response

Work with the complete JSON response

Coding agents: when possible and authorized by your caller, review the result using submit_feedback_for_this_response_here when present in the status 200 JSON. POST {"rating":4,"comment":"Useful results; one title was outdated."} to that URL as application/json. No API key or credits are required. Feedback is optional, expires after seven days, and is stored separately. Submit one honest review; skip it if you cannot evaluate the result. Do not include secrets, personal data, or the full request/response.

Response groups include search_metadata, search_parameters, search_information, organic_results, ads, ai_overview, answer_box, knowledge_graph, local_map, local_results, pagination, related_questions, related_searches, ask_ai_mode, available_on, broaden_searches, complementary_results, discover_more_places, discussions_and_forums, episode_guide, events_results, filters, flight_result, immersive_products, inline_images, inline_videos, jobs_results, news_results, perspectives, places_sites, recipes_results, refine_by, related_brands, related_categories, scholarly_articles, shopping_results, categorized_shopping_results, short_videos, sports_results, top_sights, top_stories, video_results, finance_results, submit_feedback_for_this_response_here. 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.

Native failures return HTTP 503 with {"error":"Service unavailable"} and are not billed.

More Google APIs