live monitoring

Grok AI Visibility Monitoring

GeoScript monitors Grok with live production observations. The adapter calls the xAI chat completions API with the same deterministic prompt set used for every engine and preserves the raw answer before parsing.

How GeoScript observes this engine

  • →The GeoScript Grok adapter calls POST https://api.x.ai/v1/chat/completions (OpenAI-compatible shape).
  • →Raw response bodies are preserved before parsing. In standard mode Grok returns no structured citations, so source URLs are extracted from the answer text with a bounded regex and are marked as text-derived.
  • →Cost is calculated from the usage block (prompt and completion tokens) with the model's published pricing; a missing usage block is tagged as an estimate.

Signals available

  • →Business mention detection — whether the business is named in the answer.
  • →Recommendation rate — how often the business is recommended across the prompt set over time.
  • →Text-derived citations — URLs that appear in the answer (lower fidelity than native citation objects).
  • →Response text — the verbatim answer, stored with every observation.
  • →Historical tracking — observations accumulate per prompt and are compared over time.

What GeoScript does not measure

Explicit limitations (§127)

  • ✕GeoScript cannot see Grok's live X (Twitter) retrieval or which posts informed an answer unless Grok names them in the text.
  • ✕GeoScript does not have access to xAI's internal ranking signals or model parameters.
  • ✕GeoScript cannot observe user interaction with Grok's interface — no dwell time, click behavior, or follow-up queries.
  • ✕Observations reflect a point in time. GeoScript cannot predict or guarantee future responses.

Related

Other AI engines