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 Search API

Bing search results: organic results, knowledge cards, rich modules, market and safe-search controls and pagination. A replacement for the retired Microsoft API.

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

// from request to code

Integrate Bing Search

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

APIBing Search
More options 9
Search query

Send a Bing query and optional native display or date filters.

Search origin

Optionally provide a named location, coordinates, or both.

Market & pagination

Choose at most one localization token and the native organic offset.

Content & device

Choose content filtering and desktop, tablet or mobile results.

Your request updates the code instantly.

Open the Playground →
https://ecll-litescrape-v3--site-mcp.modal.run/mcp

Add the server URL to your MCP client, then call the tool below. A free allowance is available without a key.

tools/call.json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "bing_search",
    "arguments": {
      "q": "pizza shops in New York",
      "location": "New York, New York",
      "mkt": "en-US",
      "first": 1,
      "safeSearch": "moderate",
      "device": "desktop"
    }
  }
}

Read all parameters →

JSON POST request example

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

POST · application/json
{
  "q": "python documentation"
}

// request reference

Bing Search parameters

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

Engine and query

q
QueryRequired

Bing search query after trimming.

Type string · GET query or POST JSON

Example / input hint: pizza shops in New York

  • Accepted length: 1 through 2,048 characters.
  • Control characters are rejected.
  • Bing query syntax such as quoted phrases and exclusions remains available.
engine
EngineOptional

Selects the Bing web-search engine.

Type string · GET query or POST JSON · Default bing

Accepted valuesbing

Search origin

location
LocationOptional

Named city-level origin used to localize the Bing request.

Type string · GET query or POST JSON

Example / input hint: New York, New York

  • Maximum length: 256 characters.
  • Control characters are rejected.
lat
LatitudeOptional

Latitude from -90 through 90.

Type number · GET query or POST JSON

Example / input hint: 40.7128

  • May be supplied independently or with lon.
lon
LongitudeOptional

Longitude from -180 through 180.

Type number · GET query or POST JSON

Example / input hint: -74.0060

  • May be supplied independently or with lat.

Localization

mkt
MarketOptional

Case-insensitive Bing language-country market token.

Type string · GET query or POST JSON

Example / input hint: en-US

  • Format: two-letter language and country, such as en-US.
  • Cannot be combined with cc.
cc
CountryOptional

Case-insensitive two-letter country of origin.

Type string · GET query or POST JSON

Example / input hint: US

  • Format: US or GB.
  • Cannot be combined with mkt.

Pagination, filters, and device

first
First resultOptional

One-based native offset for organic results.

Type integer · GET query or POST JSON · Default 1

Example / input hint: 1

  • Range: 1 through 9,007,199,254,740,991.
  • Prefer litescrape_pagination.next when it is returned.
safeSearch
SafeSearchOptional

Bing adult-content policy; values are case-insensitive.

Type string · GET query or POST JSON · Default moderate

Accepted valuesoffmoderatestrict
filters
Bing filtersOptional

Native Bing display or date filter expression.

Type string · GET query or POST JSON

Example / input hint: ex1:"ez5_20069_20433"

  • Maximum length: 8,192 characters.
  • Control characters are rejected.
device
DeviceOptional

Selects desktop, tablet, or mobile result behavior.

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 ads, inline_videos, litescrape_pagination, organic_results, pagination, related_searches, search_information, search_metadata, search_parameters, knowledge_graph, knowledge_graph_list, answer_box, answer_box_list, carousel_results, copilot_answer, coupons_results, events_results, inline_images, inline_shopping_results, local_map, local_results, recipes_results, related_questions, short_videos, top_shopping_results, top_stories, top_stories_link, 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.

Illustrative success response. Result groups and optional fields depend on upstream content.

200 · application/json
{
  "search_metadata": {
    "id": "a4d234f6b74a330f8a8d5069",
    "status": "Success",
    "bing_url": "https://www.bing.com/search?q=pizza+shops+in+New+York"
  },
  "search_parameters": {
    "engine": "bing",
    "q": "pizza shops in New York",
    "mkt": "en-US",
    "device": "desktop"
  },
  "knowledge_graph": {
    "title": "Pizza",
    "description": "A baked flatbread dish with toppings."
  },
  "organic_results": [
    {
      "position": 1,
      "title": "Example Pizza",
      "link": "https://example.com/pizza"
    }
  ],
  "pagination": {
    "next": "https://www.bing.com/search?q=pizza+shops+in+New+York&first=11"
  },
  "litescrape_pagination": {
    "next": "https://ecll-litescrape-v3--site-api-web.modal.run/api/bing/search?q=pizza+shops+in+New+York&first=11"
  },
  "submit_feedback_for_this_response_here": "https://ecll-litescrape-v3--site-api-web.modal.run/api/feedback/example-not-a-valid-token"
}

More Bing APIs