Regions, countries and location for AI search tasks

payload.country follows each engine’s country rules and defaults. Doubao always asks from mainland China. payload.location sets the question’s location on supported engines. Check the engine-specific rules below before submitting.

Country

Send an ISO 3166-1 alpha-2 code in payload.country:

curl -X POST https://api.querying.ai/v1/async/task \
  -H "Authorization: Bearer $QUERYING_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "taskType": "GEMINI", "payload": { "prompt": "best CRM for a small team", "country": "GB" } }'

A value that is not an ISO 3166-1 alpha-2 code returns 400 VALIDATION_ERROR. The default and the meaning of country depend on the engine:

Engine	Without `country`	Notes
Most engines	`US`	Check the engine’s `countries` policy in `GET /v1/capabilities` before choosing a country.
`NAVER_AI_BRIEF`, `NAVER_AI_TAB`, `NAVER_SERP`	`KR`
`COMMERCE_SERP`	Site’s country	The catalogue spans `US`, `KR`, `JP`, `IN` and `DE`. An explicit `country` must match the selected `site`. See Commerce Search.
`COMMERCE_PRODUCT`	URL’s storefront country	The catalogue spans `US`, `KR`, `JP`, `IN` and `DE`. An explicit `country` must match the storefront in `url`: for example, `amazon.com` uses `US` and `amazon.co.jp` uses `JP`. See Commerce Product.
`WEB_SCRAPE`	`US`	`KR` for domestic Coupang and Olive Young storefronts. An explicit country is kept.
`QWEN`	`US`	Sets both the exit country and the answer locale. `CN` asks from mainland China.
`DOUBAO`	Ignored	Doubao answers guests only in mainland China, so every task asks from a mainland exit whatever `country` says.
`CHATGPT`, `GEMINI`	`US`	`CN` is answered as for a user in mainland China, at Beijing unless you send `location`. `CHATGPT` answers `HK` the same way, at Hong Kong’s Central.
`GOOGLE`	`US`	Google shows no AI Overview to the China market, so `CN` returns the international results (`gl=us`) Google shows a device in Beijing.
`KEYWORD_VOLUME`	Required	Only served countries; `CN` and `RU` are rejected. See Keyword volume.
`PROMPT_RESEARCH`	Required	`KR` and `US` only. See Prompt Research.

Unsupported countries

A taskType and country pair that cannot be served returns 422 REGION_UNSUPPORTED at submit. Retrying does not help.

`taskType`	Unsupported
`PERPLEXITY`	`CN`
`KEYWORD_VOLUME`	`CN`, `RU`, and any country outside its served list
`PROMPT_RESEARCH`	Every country except `KR` and `US`
`COMMERCE_SERP`	Every country except the selected site’s country
`COMMERCE_PRODUCT`	Every country except the URL’s storefront country

Read countries.policy for each engine in GET /v1/capabilities: only lists supported countries; all_except lists exclusions. Commerce lists the countries across its catalogue; each request must still match its site or product URL. Country acceptance and execution location follow the engine-specific rules above. The following error includes the cause in details:

{
  "success": false,
  "error": {
    "code": "REGION_UNSUPPORTED",
    "message": "PERPLEXITY cannot be served for country='CN': ... retrying will not help. ...",
    "details": { "taskType": "PERPLEXITY", "country": "CN", "cause": "no_proxy_route", "retryable": false },
    "timestamp": "2026-10-19T09:00:00.000Z"
  }
}

Location

Set payload.location to the point the question is asked from, as latitude and longitude in decimal degrees. The engine answers as a user standing there, so “near me” questions bring places around that point. country sets the market and location sets where the user stands, so send a point inside country. This request asks ChatGPT from SoHo, New York:

curl -X POST https://api.querying.ai/v1/async/task \
  -H "Authorization: Bearer $QUERYING_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "taskType": "CHATGPT", "payload": { "prompt": "Best coffee shops near me for working on a laptop", "country": "US", "location": { "latitude": 40.72288, "longitude": -73.99875 } } }'

Engines	Behavior
`CHATGPT`, `GEMINI`, `GOOGLE`, `AIMODE`, `GOOGLE_SERP`	Accept `location`. The result returns the same point as `location`.
`COMMERCE_SERP`, `COMMERCE_PRODUCT`	Reject `location` with `422 VALIDATION_ERROR`; only the documented Commerce payload fields are accepted.
Every other engine	Rejects the field with `422 LOCATION_UNSUPPORTED`.

location must be an object with exactly two keys: latitude (-90 to 90) and longitude (-180 to 180). Other keys or out-of-range values return 400 VALIDATION_ERROR. Map apps show the coordinates of any spot you pick, and the dashboard’s Playground finds them for a place name.

List what each engine serves

GET /v1/capabilities returns every public taskType with its aliases, input fields, price, location support and country policy. It needs no API key, is read from the same rules that enforce submits, and can be cached for 5 minutes. Add ?taskType= to get one engine; aliases are accepted.

curl "https://api.querying.ai/v1/capabilities?taskType=PERPLEXITY"

{
  "success": true,
  "data": {
    "engines": [
      {
        "taskType": "PERPLEXITY",
        "aliases": [],
        "endpoint": "/v1/async/task",
        "credits": 1,
        "input": { "required": ["prompt"], "optional": ["country", "include"] },
        "location": false,
        "evidence": true,
        "countries": { "policy": "all_except", "unsupported": [{ "country": "CN", "cause": "no_proxy_route" }] },
        "example": { "prompt": "best running shoes for flat feet", "country": "US" }
      }
    ]
  }
}

Field	Description
`aliases`	Older names that run as this `taskType`.
`endpoint`	Where to submit it.
`credits`	Credits per completed task. For `WEB_CRAWL` it is per page returned.
`location`	Whether `payload.location` is accepted.
`evidence`	Whether `include.html` is accepted. See HTML pages.
`countries`	`{ "policy": "all_except", "unsupported": [...] }`, or `{ "policy": "only", "supported": [...] }` for engines with a fixed list.
`example`	A minimal payload that passes validation.

An unknown taskType returns 400 VALIDATION_ERROR. See also the capabilities reference.

Throughput

Rate limits, backpressure, concurrency and batching are covered in Credits and limits. To submit many tasks in one request, see Batches and grids.

Get started

Core concepts

Answer engines

Search and web data

Request options

Research

GEO monitoring

Account and data

Regions, countries and location for AI search tasks

Country

Unsupported countries

Location

List what each engine serves

Throughput

​Country

​Unsupported countries

​Location

​List what each engine serves

​Throughput

Country

Unsupported countries

Location

List what each engine serves

Throughput