AI Search Engines — Answers, Citations and Response Fields

taskType selects the engine. The envelope around the result is identical for all of them; what varies is the response object inside it.

Seven answer surfaces are available: CHATGPT, GEMINI, PERPLEXITY, GOOGLE, AIMODE and the NAVER_* family.

Which payload field an engine reads

Validation accepts either prompt or query, but each engine only reads the one it expects. Send the wrong one and the task queues, then fails.

Reads prompt

CHATGPT PERPLEXITY GEMINI

Reads query

GOOGLE AIMODE NAVER_AI_BRIEF NAVER_AI_TABFalls back to prompt if query is absent.

The `include` flags mostly do nothing

payload.include is part of the request contract, but in this implementation most engines produce a fixed-shape response and ignore it entirely. Only ChatGPT honours the full set.

Engine	Honoured flags	Raw arrives as
`CHATGPT`	`markdown` `html` `rawResponse` `searchQueries` `ads` `shopping`	`rawResponse`
`PERPLEXITY`	`markdown` `rawResponse` `searchQueries`	`rawResponse`
`GEMINI`	`markdown` `rawResponse`	`rawResponse`
`GOOGLE` `AIMODE` `NAVER_AI_BRIEF` `NAVER_AI_TAB`	`rawResponse`	`rawContent`

include.rawResponse returns parsed stream events on the engines that stream JSON, and the untouched response body — as rawContent, not rawResponse — on the ones we fetch as a document. Either way it can be hundreds of KB, so it is off by default.Naver accepted this flag and silently ignored it until 2026-07-26. If you tried it before then and got nothing back, try again.

markdown is not a flag on every engine that returns it: Naver ships markdown unconditionally, because for it that is the answer’s real shape rather than a copy of text.

Setting an unhonoured flag is silently ignored — no error, no field. Notably html is only ever produced by CHATGPT, even though several engines accept the flag.

Response shapes

PERPLEXITY

Reads prompt. Always returns text, sources[], timing.

{
  "text": "...",
  "sources": [{ "position": 1, "url": "https://...", "label": "...", "description": "..." }],
  "timing": { "...": "..." },
  "markdown": "...",
  "rawResponse": ["..."],
  "related_queries": ["..."],
  "search_model_queries": ["..."]
}

Optional extras when Perplexity surfaces them: videos, images, hotels, places, shopping_cards.

GEMINI

Reads prompt. Always returns text, sources[], timing.

{
  "text": "...",
  "sources": [{ "position": 1, "url": "https://...", "label": "...", "confidence_level": "..." }],
  "timing": { "...": "..." },
  "markdown": "...",
  "rawResponse": ["..."],
  "model": "..."
}

GOOGLE — AI Overview inside a SERP envelope

Reads query. This is not a bare AI Overview object — it is a search-results envelope carrying the AI Overview as one nullable member.

{
  "aioverview": { "text": "...", "sources": [{ "position": 1, "url": "https://..." }] },
  "organicResults": [{ "...": "..." }],
  "peopleAlsoAsk": [{ "...": "..." }],
  "relatedSearches": [{ "...": "..." }],
  "knowledgeGraph": { "...": "..." },
  "ads": [{ "...": "..." }],
  "serp": { "topStories": [], "videoResults": [], "localResults": [] },
  "debug": { "reason": "...", "attempts": 1 }
}

aioverview: null is the documented signal that Google showed no AI Overview for that query. It is not an error, and the SERP fields around it are still populated.

Top-level text and sources are deprecated aliases that duplicate aioverview.text and aioverview.sources. They exist so consumers of the older bare-AIO shape keep working. Read aioverview.* in new code.SERP panels are omitted when absent rather than emitted as null or [] — treat every one of them as optional.

AIMODE — Google AI Mode

Reads query. Fixed shape, no markdown or timing.

{
  "text": "...",
  "sources": [{ "position": 1, "url": "https://...", "label": "..." }],
  "debug": { "reason": "...", "attempts": 1 }
}

CHATGPT

Reads prompt. The richest response in the API, and the only one where every include flag works. All flags default to on.

{
  "text": "...",
  "model": "...",
  "sources": [{ "position": 1, "url": "https://...", "label": "...", "footnote": "...", "datePublished": "..." }],
  "markdown": "...",
  "html": "...",
  "rawResponse": ["..."],
  "searchQueries": ["..."],
  "shoppingCards": [{ "...": "..." }],
  "inlineProducts": [{ "...": "..." }],
  "ads": [{ "...": "..." }],
  "entities": { "...": "..." },
  "citationPills": [{ "...": "..." }]
}

ChatGPT also supports multi-turn conversations — see Multi-turn.

NAVER_AI_BRIEF and NAVER_AI_TAB

Both read query and share one response shape.

{
  "text": "...",
  "sources": [{ "position": 1, "url": "https://...", "label": "...", "description": "..." }],
  "debug": { "reason": "...", "attempts": 1 }
}

NAVER_AI_BRIEF is the conditional AI summary box on the Naver SERP — it may not appear for a given query. NAVER_AI_TAB is the always-on conversational AI tab and is the primary Naver surface; its text is markdown-formatted.NAVER_AI_BRIEF also returns the organic web documents that sit beneath the summary box, under organicResults — the same field GOOGLE ships beside its AI Overview:

{
  "organicResults": [
    { "position": 1, "title": "...", "link": "https://...", "displayedLink": "example.com",
      "snippet": "...", "date": "2026.7.30.", "page": 1 }
  ]
}

The summary and the documents come from two different Naver endpoints, so NAVER_AI_BRIEF costs 2 credits, the same as NAVER_AI_TAB. If the document fetch fails the field is absent rather than empty, and debug.serpReason says why.

NAVER is a deprecated alias for NAVER_AI_BRIEF. Use the explicit name.

Multi-turn (ChatGPT)

ChatGPT can hold a conversation. Omit both fields for the default single-shot behaviour.

Start a thread

Send newConversation: true. The response carries a conversationId.

{ "taskType": "CHATGPT", "payload": { "prompt": "...", "newConversation": true } }

Continue it

Send that conversationId back on the next turn.

{ "taskType": "CHATGPT", "payload": { "prompt": "...", "conversationId": "..." } }

Conversations are bound to the device that created them and expire after roughly two hours. A stale conversationId cannot be resumed.

Engine guides

ChatGPT: English · 한국어
Gemini: English · 한국어
Perplexity: English · 한국어
Google AI Overviews: English · 한국어
Google AI Mode: English · 한국어
Naver AI Brief: English · 한국어
Naver AI Tab: English · 한국어

Get started

Core concepts

Engines

Source Influence

GEO Monitoring

Migrating

AI Search Engines — Answers, Citations and Response Fields

Which payload field an engine reads

Reads prompt

Reads query

The `include` flags mostly do nothing

Response shapes

Multi-turn (ChatGPT)

Engine guides

​Which payload field an engine reads

Reads prompt

Reads query

​The include flags mostly do nothing

​Response shapes

​Multi-turn (ChatGPT)

​Engine guides

Which payload field an engine reads

The `include` flags mostly do nothing

Response shapes

Multi-turn (ChatGPT)

Engine guides