Namebeam
The Documented Climb

The AI citation case study nobody else will publish: our own, starting at zero.

Every tool in this category tells businesses it can get them named by ChatGPT, Claude, Perplexity, and Gemini. We could not find one that publishes its own climb, dated, from zero, with the losses printed the same size as the wins. So this is that case study, and Namebeam itself is the subject.

Entry 001 published 2026-08-07. Updates on a fixed cadence, win or lose.
Why this page exists

If a vendor will not show you their own climb, ask why.

Terry Carter built Namebeam, so read this page as biased and check the raw files yourself; every entry names them. The Citation Ledger holds the raw dated self-check entries. This page is the running case study built on top of them: one brand, one number over time, every method named, every miss kept at full size. We could not find another vendor in this category publishing their own climb from zero. This page exists so that at least one exists.

The terms, fixed in advance

Re-runs happen on a fixed cadence and get published whatever the number is. No entry is edited after the fact. Namebeam has zero paying customers today; that number is published here and changes here first when it changes. Nothing on this page promises the number will move. The promise is only that whatever it is, it gets printed here, dated.

Entry 001, the starting line, published 2026-08-07

Every dated check to date says the same thing: zero.

0
times Namebeam has been named by an AI engine in any dated check so far

Three separate check sets, three methods, one result. They are listed separately because they are different protocols, and blending different datasets into one number is the exact habit this brand exists to refuse.

Check setResultWindow
Twenty-answer protocol, four engines (Citation Ledger Entry 001, corpus NB-0001)0 of 202026-07-29
Run 2 variance re-check, three engines, cumulative with Run 10 of 352026-07-29
Customer-zero index checks, five engines (NB-CZ series, public append-only log)0 of 62026-07-24 to 2026-07-31

Sources: CITATION_LEDGER_ENTRY_001_2026-07-29.md, NB-0001_run2_variance_summary.md, and the public ai-visibility-index log. Each check set keeps its own sample and date on every future entry of this page.

What has been shipped to move the number, dated

All dated 2026-07-31 in the public log: llms.txt, ai-instructions.html, JSON-LD Dataset and FAQ schema, a live homepage check, and the published index itself. Whether any of it moves the number is exactly what the next entries of this page will show.

Honesty note. AI answers vary run to run and can change without notice. A zero today is not a permanent verdict, and a first mention tomorrow would not be proof of skill. The value of this page is the dated series, not any single point on it.
Standing line

The climb is public from here.

The number moves, or we print that it did not. Either way it lands on this page, dated, sourced, at the same size.

Run my free check Read the raw ledger