Data API / DataForSEO / AI Optimization
Live LLM Mentions
The individual answers in which an assistant mentioned your target. Returns total_count, current_offset, search_after_token and items - page with the token, not offset, past the first pages. ⚠️ target is an array of objects, each {"domain": "..."} or {"keyword": "..."}; a bare string is rejected as the wrong type and an array of strings as 'Each target item must be an object'. Filter fields come from get_dataforseo_ai_llm_mentions_available_filters. Wrapped in DataForSEO's envelope: data in tasks[0].result, outcome in tasks[0].status_code - a rejected request still returns HTTP 200. For counts rather than the mentions themselves use post_dataforseo_ai_llm_mentions_aggregated_metrics_live.
Parameters
No path, query, or header parameters.
Request body
targetobject[]Requiredarray of objects containing target entities required field you can specify up to 10 entities (objects) in the target field one target entity can contain either one domain or one keyword and related parametersexamples: target array with a domain entity [{"domain": "en.wikipedia.org", "search_filter": "exclude"}] target array with a keyword entity [{"keyword": "bmw", "search_scope": ["question"], "match_type ": "partial_match"}] target array with multiple entities [{"domain": "en.wikipedia.org", "search_filter": "exclude"}, {"keyword": "bmw", "match_type ": "partial_match", "search_scope": ["answer"]}]
domainstringOptionaltarget domain required field if you don't specify keyword you can specify up to 63 characters in the domain field; a domain should be specified without https:// and www.
keywordstringOptionaltarget keyword required field if you don't specify domain you can specify up to 250 characters in the keyword field all %## will be decoded (plus character ‘+’ will be decoded to a space character) if you need to use the “%” character for your keyword, please specify it as “%25”; if you need to use the “+” character for your keyword, please specify it as “%2B”learn more about rules and limitations of keyword and keywords fields in DataForSEO APIs in this Help Center article
search_filterstringOptionalEntity search filter: include or exclude; defaults to include.
search_scopestring[]OptionalSearch scope. Domain entities: any, sources, search_results. Keyword entities: any, question, answer, brand_entities, fan_out_queries. Default: any.
include_subdomainsbooleanOptionalindicates if the subdomains of the target domain will be included in the search optional field if set to true, the subdomains will be included in the search default value: false
match_typestringOptionaltarget keyword match type defines how the specified keyword is matched optional field possible values: word_match - full-text search for terms that match the specified seed keyword with additional words included before, after, or within the key phrase (e.g., search for "light" will return results with "light bulb", "light switch"); partial_match - substring search that finds all instances containing the specified sequence of characters, even if it appears inside a longer word (e.g., search for "light" will return results with "lighting", "highlight"); default value: word_match
location_namestringOptionalfull name of search location optional field if you use this field, you don't need to specify location_code if you don't specify this field, the location_code with 2840 value will be used by default; you can receive the list of available locations of the search engine with their location_name by making a separate request to the https://api.dataforseo.com/v3/ai_optimization/llm_mentions/locations_and_languages Note: chat_gpt data is available for United States only
location_codeintegerOptionalsearch location code optional field if you use this field, you don't need to specify location_name you can receive the list of available locations of the search engine with their location_code by making a separate request to the https://api.dataforseo.com/v3/ai_optimization/llm_mentions/locations_and_languages default value: 2840 Note: chat_gpt data is available for 2840 only
language_namestringOptionalfull name of search language optional field if you use this field, you don't need to specify language_code; if you don't specify this field, the language_code with en value will be used by default; you can receive the list of available languages of the search engine with their language_name by making a separate request to the https://api.dataforseo.com/v3/ai_optimization/llm_mentions/locations_and_languages Note: chat_gpt data is available for English only
language_codestringOptionalsearch language code optional field if you use this field, you don't need to specify language_name; you can receive the list of available languages of the search engine with their language_code_by making a separate request to the https://api.dataforseo.com/v3/ai_optimization/llm_mentions/locations_and_languages default value: en Note: chat_gpt data is available for en onlyn
platformstringOptionaltarget platform optional field possible values: chat_gpt, google default value: google Note: the data returned depends on the selected platform Note #2:chat_gpt data is available for the United States and English only
filtersarrayOptionalarray of results filtering parameters optional field you can add several filters at once (8 filters maximum) you should set a logical operator and, or between the conditions the following operators are supported: =, , in, not_in, like, not_like, ilike, not_ilike, match, not_match you can use the % operator with like and not_like to match any string of zero or more characters example: ["ai_search_volume",">","1000"]The full list of possible filters is available here.
order_bystring[]Optionalresults sorting rules optional field you can use the same values as in the filters array to sort the results possible sorting types: asc - results will be sorted in the ascending order desc - results will be sorted in the descending order you should use a comma to set up a sorting type example: ["ai_search_volume,desc"] note that you can set no more than three sorting rules in a single request you should use a comma to separate several sorting rules
offsetintegerOptionaloffset in the results array of the returned mentions data optional fielddefault value: 0 example: if you specify the 10 value, the first ten mentions objects in the results array will be omitted and the data will be provided for the successive objects; Note: the maximum value is 9,000, use the search_after_token if you would like to offset more results
search_after_tokenstringOptionaltoken for subsequent requests optional field provided in the identical filed of the response to each request; use this parameter to avoid timeouts while trying to obtain over 20,000 results in a single request; by specifying the unique search_after_token value from the response array, you will get the subsequent results of the initial task; search_after_token values are unique for each subsequent task ; Note: if the search_after_token is specified in the request, all other parameters should be identical to the previous request
limitintegerOptionalthe maximum number of returned objects optional fielddefault value: 100 maximum value: 1000
tagstringOptionaluser-defined task identifier optional field the character limit is 255 you can use this parameter to identify the task and match it with the result you will find the specified tag value in the data object of the response
Example request
curl -X POST "https://openapi.felo.ai/v1/beta/dataforseo/ai_optimization/llm_mentions/search/live" \
-H "Authorization: Bearer $FELO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"target": [
{}
],
"location_name": "<string>",
"location_code": 0,
"language_name": "<string>",
"language_code": "<string>",
"platform": "<string>",
"filters": "<string>",
"order_by": [
"<string>"
]
}'Response
Response fields
versionstringOptionalthe current version of the API
status_codeintegerOptionalgeneral status code you can find the full list of the response codes here Note: we strongly recommend designing a necessary system for handling related exceptional or error conditions
status_messagestringOptionalgeneral informational message you can find the full list of general informational messages here
timestringOptionalexecution time, seconds
costnumberOptionaltotal tasks cost, USD
tasks_countintegerOptionalthe number of tasks in the tasks array
tasks_errorintegerOptionalthe number of tasks in the tasks array returned with an error
tasksstring[]Optionalarray of tasks
idstringOptionaltask identifier unique task identifier in our system in the UUID format
status_codeintegerOptionalstatus code of the task generated by DataForSEO; can be within the following range: 10000-60000 you can find the full list of the response codes here
status_messagestringOptionalinformational message of the task you can find the full list of general informational messages here
timestringOptionalexecution time, seconds
costnumberOptionalcost of the task, USD
result_countintegerOptionalnumber of elements in the result array
pathstring[]OptionalURL path
dataobjectOptionalcontains the same parameters that you specified in the POST request
resultstring[]Optionalarray of results
total_countintegerOptionaltotal amount of results relevant the request
current_offsetintegerOptionalthe number of mentions objects that are omitted in the items array
search_after_tokenstringOptionaltoken for subsequent requests by specifying the unique search_after_token when setting a new task, you will get the subsequent results of the initial task; search_after_token values are unique for each subsequent task
items_countintegerOptionalthe number of results returned in the items array
itemsstring[]Optionalcontains relevant mentions data
platformstringOptionalplatform received in a POST array
model_namestringOptionalname of the AI model from which the data was retrieved Note: for the google platform type, the value is always google_ai_overview
location_codeintegerOptionallocation code in a POST array
language_codestringOptionallanguage code in a POST array
questionstringOptionalrelevant question
answerstringOptionalrelevant answer in markdown format content of the result formatted in the markdown markup language
sourcesstring[]Optionalarray of sources the sources the model cited or relied on in its final answer
snippetstringOptionalsource description
source_namestringOptionalsource name
thumbnailstringOptionalsource thumbnail
markdownstringOptionalcontent of the element in markdown format content of the result formatted in the markdown markup language
positionintegerOptionalposition in the results
titlestringOptionalsource title
domainstringOptionalsource domain
urlstringOptionalsource URL
publication_datestringOptionaldate and time when the result was published in the format: “year-month-date:minutes:UTC_difference_hours:UTC_difference_minutes” example: 2019-11-15 12:57:46 +00:00
search_resultsstring[]Optionalarray of search results all web search outputs the model retrieved when looking up information, including duplicates and unused entries
descriptionstringOptionalresult description
breadcrumbstringOptionalbreadcrumb
positionintegerOptionalposition in the results
titlestringOptionalresult title
domainstringOptionalresult domain
urlstringOptionalresult URL
publication_datestringOptionaldate and time when the result was published in the format: “year-month-date:minutes:UTC_difference_hours:UTC_difference_minutes” example: 2019-11-15 12:57:46 +00:00
ai_search_volumeintegerOptionalcurrent AI search volume rate of a keyword learn more about this metric here
monthly_searchesstring[]Optionalmonthly AI search volume rates array of objects with AI search volume rates in a certain month of a year
yearintegerOptionalyear
monthintegerOptionalmonth
search_volumeintegerOptionalAI search volume rate in a certain month of a year learn more about this metric here
first_response_atstringOptionaldate and time when the response data was first recorded in the UTC format: “yyyy-mm-dd hh-mm-ss +00:00” example: 2025-10-21 06:25:30 +00:00
last_response_atstringOptionaldate and time when the response data was last updated in the UTC format: “yyyy-mm-dd hh-mm-ss +00:00” example: 2025-10-21 06:25:30 +00:00
brand_entitiesstring[]Optionalarray of brand entities contains information on brands mentioned in the response
positionintegerOptionalposition in the results
titlestringOptionalname of the brand
categorystringOptionalcategory of the brand
fan_out_queriesstring[]Optionalarray of fan-out queries contains related search queries derived from the main query to provide a more comprehensive response