License the Record.

Carter Enterprise LLC

Wyoming limited liability company formed 2026-06-06. One founder, Terry J Carter. Operated as Namebeam at namebeam.ai. Back to the company page.

A dated record of who AI names

Each day a program asks AI engines the same fixed local-business questions, one per business or market segment, and saves one raw file per answer with its date. The engines are OpenAI, Anthropic, Gemini and Perplexity, called through their APIs, plus Google results pages. These are API calls, not the apps people open on a phone. Perplexity is the only engine with a search tool switched on, so the engines are not like for like and we do not compare them as if they were.

A rule-based gate then removes places, directories and sentence fragments from the returned names, and every metric is published raw and gated with its denominator. The record shows what was returned on which day. It does not show why a list changed, and it does not describe all businesses or all questions.

• Public repository: github.com/mrcrtr1979-droid/namebeam-visibility-index
• Edition 1 method note and limits

Edition 1 covers 2026-09-01 to 2026-10-13 (42 run days, 12,180 answer rows). Final, on main.

CC BY 4.0, with credit

The Namebeam compilation, code and derived columns are free under the Creative Commons Attribution 4.0 license. The raw answer text from each AI service is published as a dated record, is not licensed by us, and each provider's terms may apply; see NOTICE.md in the namebeam-visibility-index repository. You may use and republish the compilation, including commercially, as long as you give credit. Citation details are in CITATION.cff. Nothing below changes this. Both paid options sit on top of the free compilation.

Two ways to pay

By email, within 24 hours

• Payment goes through Stripe. We see the order and write to you from terry@namebeam.ai.
• If we need details, we ask first. For the license: the legal name and address of the licensee, the signer name and a support email. For the feed: the markets you want and the email the files should go to.
• We build the files, check them, and email them. The target is within 24 hours of your answer, or within 24 hours of payment when no questions are needed. If we cannot meet that, we tell you within 24 hours.
• License: you receive a filled copy of the license with an annex that lists the SHA-256 hashes of the Edition 1 files, recomputed from the public repository. You can check the same hashes yourself with the verify script in the repository.
• Feed: you receive the latest cut files for your named markets, as one-page PDFs with CSV tables, daily or weekly as you choose. A market we have not yet collected cannot be filled from history. We will tell you which markets have data before you rely on it.
• Edition 1 was released on 2026-10-15. The license is delivered once the signed manifest statement for that build is ready, and we tell you the date when you buy.

Check it yourself in five minutes

Each day a scheduled job asks the engines the same fixed questions and writes one raw file per answer, with its UTC date, into corpus/e1/ of the public repository. The job commits those files the same day under the message "e1 slice run" plus the date. The Edition 1 pack lists a SHA-256 for each of its 32 files in MANIFEST.sha256, and every row of the answers table carries the SHA-256 of the raw file it came from. Rows are appended, never edited or deleted. A separate daily collector in a private Carter Enterprise repository commits its own captures to git and copies them to a Cloudflare R2 bucket named carter-frontier-archive, where nothing is deleted; that archive is not part of Edition 1.

1. Open the public release tree. github.com/mrcrtr1979-droid/namebeam-visibility-index/tree/main/releases/edition-1. It holds PACK.json, MANIFEST.sha256, verify.py, README.md, the data/ tables, the metrics/ tables and the method/ code.
2. Download the manifest. MANIFEST.sha256 has one line per file: the 64-character SHA-256, two spaces, then the path relative to releases/edition-1/. The line for the answers table reads 398f7cc5f76a3060eba318d0231e4b32f92a3155064debb0bc68f0c9fb499f03 data/answers_2026-09-01_to_2026-10-13.csv.
3. Hash a file and compare. Download data/answers_2026-09-01_to_2026-10-13.csv, run sha256sum on it (or certutil -hashfile on Windows), and compare the output with the manifest line above. To check every file at once, clone the repository and run python3 verify.py from releases/edition-1/; it prints MATCH or MISMATCH per file and ends with VERIFY MATCH when all 32 agree. verify.py --rebuild rebuilds the answers table from the raw files and compares, and verify.py --metrics recomputes the metrics table.
4. Check the commit timestamps. github.com/mrcrtr1979-droid/namebeam-visibility-index/commits/main/corpus/e1 lists the daily commits. Each raw file name carries its date, each commit message names the run date, and GitHub shows when the commit landed. Open any raw file, hash it, and match the hash to the sha256 value on its row in the answers table.
5. Read the change log and the stated limits. scripts/CHANGELOG.md records dated changes to the collector and which rows they affect. The Limits section of releases/edition-1/README.md lists the known gaps, including the day with no run (2026-10-05) and the Gemini outage from 2026-09-27.

Not claimed: why an engine named a business, that any engine was asked the way a person asks it on a phone, or that the record covers all businesses or all questions. The record shows what was returned on which day.

What a reader can check here

On 2026-10-14 we read the public methodology, FAQ, documentation and pricing pages of 11 AI visibility vendors and checked each for what a reader needs to check a number. These lines describe what those pages state, not what a vendor may give customers in private.

• Every answer row in this record carries its own date. Several vendors date each answer in their API documentation (Peec AI, Profound and Conductor, for example); those dates are read with a customer API key, and here they sit in public files.
• Every answer row carries the SHA-256 of its raw answer file, and the release ships a SHA-256 manifest and a verify script. None of the 11 vendor pages we read states hashes or other tamper evidence.
• The raw answer files are public in the repository folder corpus/e1/. None of the 11 vendor pages we read states that raw answer text is public; several describe a customer export or a customer view of the answers.
• Our compilation, code and derived columns are licensed CC BY 4.0, as stated in the repository LICENSE and NOTICE.md files; the raw answer text from each AI service is not licensed by us. None of the 11 vendor pages we read states open reuse terms for its data.

What other vendors state that this record does not:

• One vendor states up to 300 report runs a day across 117 regional databases. This record asks a fixed set of questions once a day, in the US markets and niches listed in the release prompts table.
• One vendor offers customers a CSV or JSON export of prompts and responses. This record is a public file set, not a customer account export.
• One vendor states daily tracking in more than 50 countries. This record covers US markets.
• This record does not store which model version answered each row. The model names are set in the collector code; Perplexity rows record the model the service reports.

The vendor table, with the page read for each cell, is available on request at terry@carterenterprise.llc.

Questions Before You Buy

Email: terry@carterenterprise.llc

Phone: 314-881-9601

Carter Enterprise LLC, 30 N Gould St, Suite 65270, Sheridan, WY 82801