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

// Bing documentation

Bing Maps API

Bing Maps listings, 30 a page with rating, address, phone, website, hours and coordinates, for any query and map center, or one place by ID.

GET / POST https://ecll-litescrape-v3--site-api-web.modal.run/api/bing/maps

// from request to code

Integrate Bing Maps

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

APIBing Maps
More options 5
Map lookup

Search Bing Maps listings or resolve one native entity ID.

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/bing/maps' \
  --header "Authorization: Bearer $LITESCRAPE_API_KEY" \
  --data-urlencode 'q=coffee Austin Texas' \
  --data-urlencode 'cp=30.2672~-97.7431' \
  --data-urlencode 'setlang=en-US' \
  --data-urlencode 'first=0' \
  --data-urlencode 'count=10'

Read all parameters →

JSON POST request example

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

POST · application/json
{
  "q": "coffee Austin Texas",
  "count": 3
}

// request reference

Bing Maps parameters

Send query parameters with GET /api/bing/maps. 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.

Map lookup

Search Bing Maps listings or resolve one native entity ID.

q
QueryConditional

Search query; required unless place_id is supplied.

Type string · GET query or POST JSON

Example / input hint: coffee Austin Texas

place_id
Place IDConditional

Native Bing Maps entity identifier for a detail lookup.

Type string · GET query or POST JSON

Example / input hint: YN…

cp
Center pointOptional

Optional map center in latitude~longitude form.

Type string · GET query or POST JSON

Example / input hint: 30.2672~-97.7431

setlang
LanguageOptional

Bing Maps interface language, such as en-US.

Type string · GET query or POST JSON

Example / input hint: en-US

first
Start offsetOptional

Listing offset from 0 through 10,000.

Type integer · GET query or POST JSON · Default 0

Example / input hint: 0

count
Result countOptional

Number of listings from 1 through 30.

Type integer · GET query or POST JSON · Default 30

Example / input hint: 10

// 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, local_results, place_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 Bing APIs