NOX Silence Studio

← Home

Method: how X-ray measures

Version
1.1
Updated
SHA-256 of this text
753c87c553bc2246a24e658000be7237f871defce996ae074266abd8d7f191bd

X-ray measures whether an AI assistant names your company when a real buyer asks, who it names instead, and whether what it says is true. This page shows how the measurement is made and what it does not tell you.

1. The questions

The measurement starts from buying situations: the moments when a buyer starts looking for what your industry sells. For each situation, questions are written the way a buyer would ask them, in the market's own language.

By default there are 50 questions, split across the situations (for example 8 situations × 7 questions). Below about 50, a visibility figure swings with the wording of a single question.

2. Five AI engines, each on its own

Every question goes to five AI engines that search the web while they answer:

Each engine's result is counted separately. Answers are never pooled into one figure, because that would quietly change every denominator. The report names the engine and the model it measured.

If an engine cannot be measured, it is left unmeasured. It is never replaced by another.

3. What is read from each answer

4. The sources are checked

The pages an engine cites are fetched and read for whether your company appears on them. Every page read is stored with its time and SHA-256.

If a page could not be fetched, its row is marked as a lower bound. The report says, row by row, which one it is.

5. The buying-decision test

A buyer agent is made to pick one supplier in each buying situation and say at which step, and why, every other one dropped out. The reason comes from a closed list, and every reason names a fix.

This is a different measurement from visibility and it is reported in its own unit: buying decisions.

6. The seal

The SHA-256 of every delivered file is written to MANIFEST.sha256. Every answer, every decision and the log of pages read are attached inside the PDF report, with the measurement time and the engine version.

Anyone can recompute the hashes and compare them with the manifest. If a single byte has changed, the hash does not match.

The delivery's MANIFEST.sha256 also gets an RFC 3161 timestamp from a third-party authority (the file MANIFEST.sha256.tsr). It proves when the files existed, and anyone can check it with OpenSSL, without NOX.

7. What the measurement does not tell you

See this on your own company →

Version history

1.125 Oct 2026The seal gets an RFC 3161 timestamp.
1.025 Oct 2026First published version.