Capture Google AI Mode answers with an API
Google now has two AI answer surfaces and they behave differently. AI Overview sits on top of a normal results page; AI Mode is the full conversational interface — follow-ups, richer layouts, product and place blocks. Monitoring one tells you nothing about the other.
The endpoint
curl -X POST https://api.answerline.dev/v1/monitor/aimode \
-H "Authorization: Bearer $API_KEY" \
-d '{ "prompt": "compare standing desks for home offices", "country": "US", "usState": "CA" }'Parsed fields cover the AI Mode surface: text/markdown, sources[] with position, searchQueries[] for the fan-out, plus products[], places[] and images[] when the interface shows them.
AI Mode vs AI Overview — why monitor both
- Different triggers: a keyword can show an AI Overview on the SERP while AI Mode answers the same intent with a different source set.
- Different layouts: AI Mode’s conversational format cites sources inline differently; product prompts surface
products[]clusters that don’t exist in Overview. - Different audiences: Overview reaches every searcher passively; AI Mode users are actively engaging — higher intent, worth measuring separately.
Use taskType: GOOGLE_AI_MODE and GOOGLE_AI_OVERVIEW side by side in one batch; same geo parameters, same schema, one pipeline.
What teams use it for
Commerce brands track products[] the way they once tracked Shopping results. Local businesses watch places[]. Publishers monitor whether their articles enter sources[] as AI Mode eats the queries that used to send them clicks. See the AI Mode engine page for the full field list, and the AI Overview monitoring post for the companion surface.