API vs interface tracking

AI visibility tools collect answers either from AI companies' APIs or from the real chat interfaces people use. The two can give different answers.

AnalyticsUpdated 1 min read

Also called UI vs API tracking · API tracking · scraping AI answers

What it means

There are two ways to collect AI answers at scale:

  • API: send the question to the AI company's developer service and record the reply.
  • Interface: ask the question in the real product, like chatgpt.com or Google, the way a user would.

Why they differ

The API and the product aren't always the same. The product may use a different model version, search the web in a different way, add shopping cards or follow a different system prompt. An API call may not search the web at all unless asked to.

So an API answer can name different brands and cite different pages from what your buyers see.

What to ask a tool

  • Where do answers come from: API or the real interface?
  • Does it search the web the way the product does?
  • Which location and language does it ask from?
  • How often does it ask each question?

Example

A team compares a week of API answers with answers from the ChatGPT interface for the same 20 questions. The API names three brands the interface rarely does, and misses one the interface names every day.

They switch to tracking the interface, because that's what buyers see.

Frequently asked questions

Is API tracking useless?

No. It's cheaper and good for spotting trends in a model's own knowledge. It's just not always what users see.

Does Google AI Overviews have an API?

Not one that returns the same answers users see. Tracking it means checking real search results.

Do logged-in users see different answers?

Sometimes, because of memory and personal settings. Logged-out answers are the fairest common baseline.

Go deeper

All posts →

Make AI search your next revenue channel

Start free trial