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

// Naver documentation

Naver Search API

Search Naver general, web, news, video, and image results with sorting, time filters, and pagination.

GET / POST https://api.litescrape.com/api/naver/search

// from request to code

Integrate Naver Search

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

APINaver Search
More options 6
Search parameters

Search Naver general, web, news, video, and image results with sorting, time filters, and pagination.

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://api.litescrape.com/api/naver/search' \
  --header "Authorization: Bearer $LITESCRAPE_API_KEY" \
  --data-urlencode 'query=coffee' \
  --data-urlencode 'where=nexearch'

JSON POST request example

POST to https://api.litescrape.com/api/naver/search with Content-Type: application/json and your Authorization: Bearer header.

POST · application/json
{
  "query": "coffee",
  "where": "nexearch"
}

// request reference

Naver Search parameters

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

Search parameters

Search Naver general, web, news, video, and image results with sorting, time filters, and pagination.

query
QueryRequired

Search query, including Naver search operators.

Type string · GET query or POST JSON

Example / input hint: coffee

  • Minimum characters: 1
  • Maximum characters: 4096
start
StartOptional

Result offset; takes precedence over page.

Type integer · GET query or POST JSON

  • Minimum: 0
page
PageOptional

Page number, starting at 1.

Type integer · GET query or POST JSON

  • Minimum: 1
num
NumOptional

Image result limit; defaults to 50 for images.

Type integer · GET query or POST JSON

  • Minimum: 1
  • Maximum: 100
where
WhereOptional

Search type: nexearch (general search), web, video, news, or image.

Type string · GET query or POST JSON · Default nexearch

Accepted valuesnexearchwebvideonewsimage
sort_by
Sort ByOptional

News: 0 relevance (default), 1 latest, 2 oldest. Other types: r relevance (default), dd latest.

Type string · GET query or POST JSON

Accepted valuesrdd012
period
PeriodOptional

Time window: all, 1h, 1d, 1w, 1m, 3m, 6m, 1y, or fromYYYYMMDDtoYYYYMMDD. News also accepts 2h, 3h, 4h, 5h, and 6h.

Type string · GET query or POST JSON · Default all

// 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, organic_results, news_results, video_results, images_results, ads_results, post_results, shopping_results, booking_results, dictionary_results, knowledge_graph, related_searches, related_results, ai_briefing, pagination, submit_feedback_for_this_response_here. Groups and fields depend on the upstream result.

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": {
    "status": "Success",
    "naver_url": "https://search.naver.com/search.naver?query=coffee&where=web"
  },
  "search_parameters": {
    "query": "coffee",
    "where": "web"
  },
  "organic_results": [
    {
      "position": 1,
      "title": "Coffee",
      "link": "https://en.wikipedia.org/wiki/Coffee",
      "snippet": "Coffee is a beverage made from roasted coffee beans."
    }
  ],
  "submit_feedback_for_this_response_here": "https://ecll-litescrape-v3--site-api-web.modal.run/api/feedback/example-not-a-valid-token"
}

More Naver APIs