# AI Answer Visibility Check: does an assistant name you when a buyer asks, and who gets named instead

> Ask each buyer question three times per assistant in fresh chats, paste the answers, and get a dated record of where you were named, where you were missed, who was named instead and which sources each answer cited. Fifteen read-only checks keep it honest: no brand in the question, three runs before a gap, answers hashed as given, nothing older than a month treated as current, and only your own brand. Page changes wait for the owner's yes.

- URL: https://paperchasewebb.ai/bots/marketplace/items/ai-answer-visibility-check-does-an-assistant-name-you/
- Type: Prompt pack
- Category: Solo business
- By: PaperChaseWebb
- Works with: Claude Code, Codex, Grok Bot, Hermes (named in the listing); A skill file for Claude Code, Codex and Hermes, an AGENTS.md snippet and a Grok Bot rules block; the scripts were tested on Linux with Python 3.13, the agent files were not loaded inside each harness and no real assistant was asked anything for the worked example
- Price: $19 USD
- Difficulty: Beginner
- Setup time: 45 min
- Time to result: A first report in an afternoon of asking, for five questions on two or three assistants
- Format: Markdown (.md) file, ai-answer-visibility-check-does-an-assistant-name-you.md
- Version: 1.0, updated 2026-10-29
- License: Use for your own business and for clients you are hired to represent. Do not resell or republish the pack itself.

## What you end up with

You know which buyer questions leave you out, who the assistants name instead, and the pages they lean on, from three runs each, with a record you can rerun next month; and no page changes without your yes.

## What you get

- 18 sections in one .md file, with a one-line unpack
- How to write buyer questions without your name, and how to ask so one odd answer is not read as a pattern
- The check folder: visibility.json, answers, verdicts, actions and approvals, with blank templates
- vis.py: record a pasted answer (hashed, read for your name, position, others named and sources), score, a report, and owner approval tied to a sha256
- visibility_check.py: fifteen read-only checks, with a seeded test folder (15 findings, then 0) and the unit tests
- A skill file for Claude Code, Codex and Hermes, an AGENTS.md snippet and a Grok Bot rules block
- Ten prompts, a failure table, a worked example on a made-up bookkeeping firm, and a look at the paid trackers with sources

## Who it is for

People who want to know, three runs at a time, whether AI assistants recommend them to buyers, and which pages to change, without a monthly tracking subscription.

## Tools needed

- Grok Bot, Claude Code, Codex or Hermes: the check helper; it reads the skill file, AGENTS.md snippet or rules block, helps write buyer questions, records the answers you paste, runs the checks and the report, and drafts page changes that wait for the owner's yes
- Python 3: runs vis.py (init, record, score, report, hash, card, owner approval, verify) and the fifteen-check checker on your check folder; standard library only, no network
- The owner: asks the assistants in fresh chats (or with their own official API key), attests the brand is theirs, and says yes to each page change at their own terminal, tied to a sha256
- You need: Any of Grok Bot, Claude Code, Codex or Hermes, or a terminal
- You need: Python 3.9 or newer
- You need: Accounts on the assistants you want to check
- You need: A brand you own or are hired to represent
- You need: One owner who approves changes at their own terminal

Cost to run: The pack is the only purchase. The scripts use no model tokens; asking the assistants uses your own accounts.

## How it works

1. **Run the tests.** Unpack the pack and run sh test_all.sh. Expected: 15 findings on the seeded folder and 0 on the fixed one, 15 of 15 single faults caught alone, checker tests 29 passed, vis.py tests 39 passed, exit 2 on a missing folder.
2. **Write the questions.** Run vis.py init, then write five to ten buyer questions without your name, list your competitors, and set own_brand_attested yourself. Expected: V01 to V04 clean.
3. **Ask three times.** Ask each question in a fresh chat on each assistant, three times, and save each answer as a .txt file. Record each with vis.py record. Expected: answers.csv fills in with who was named and the links cited.
4. **Score, report, get the yes.** Run vis.py score, the checker and vis.py report. Propose one page change per gap in actions.csv; the owner approves each at their own terminal. Expected: A dated report of gaps, others named and sources, and every change tied to the owner's yes.

## Sample prompt: Write buyer questions (Grok Bot, Claude Code, Codex, Hermes)

```
Help me write eight buyer questions for my business without using my name. Mix find, compare and check questions, and keep my city in the local ones.
```

Prompt 1 of 10.

## Sample prompt: Read the report (Grok Bot, Claude Code, Codex, Hermes)

```
Run vis.py score, visibility_check.py and vis.py report. Tell me, in plain words, where I was missed and who was named instead.
```

Prompt 4 of 10.

## Sample prompt: Propose changes (Grok Bot, Claude Code, Codex, Hermes)

```
Propose one page change per gap in actions.csv. One change per row, on my own site only, no listings to buy and no one to contact.
```

Prompt 6 of 10.

## Free preview of ai-answer-visibility-check-does-an-assistant-name-you.md

````markdown
# AI Answer Visibility Check: does an assistant name you when a buyer asks?

Version 1.0, 2026-10-29. By PaperChaseWebb. For small businesses, consultants and agencies who want to know, in a dated record they can show someone, whether ChatGPT, Claude, Gemini, Perplexity or Grok names them when a buyer asks the kind of question that leads to a sale. You ask each buyer question three times per assistant in fresh chats, paste the answers into a folder, and a script reads every answer for your name, the competitors named instead, and the links the assistant cited. Fifteen read-only checks keep the record honest: questions that do not leak your name, three runs before anything is called a gap, answers kept exactly as given and hashed, nothing older than a month treated as current. Page changes you decide to make wait for your yes, typed at your own terminal and tied to a sha256. Python 3 standard library only, no network. Works with Claude Code, Codex and Hermes through a skill file and an AGENTS.md snippet, and with Grok Bot through a rules block. Tested as described in section 11 on Linux with Python 3.13, including owner approvals typed at a pseudo-terminal. The agent files were not loaded inside the harnesses for this release, and no assistant was asked anything to make the worked example: the business, competitors and answers are made up.

The tools that track this today are mostly monthly subscriptions that ask the assistants for you on a schedule and show a chart. Several a
````

## Test record

- Date: Oct 29, 2026
- What was run: visibility_check.py on a seeded folder and a fixed copy, each planted fault alone, a missing input, and the unit tests. Linux, Python 3.13.
- Result: 15 findings on the seeded folder, 0 on the fixed one; 15 of 15 planted faults caught alone; exit 2 on missing input; nothing written. 29 checker and 39 vis.py tests passed, 0 failed.
- Not run: The agent files inside Claude Code, Codex, Hermes or Grok Bot. Windows and macOS. The scripts open no network connection.

Copied from this item's dated test notes. What was not run stays in.

## Worth knowing

- No real assistant was asked anything for the worked example; the business, competitors and answers are made up. Answers vary by account, location, model version and day, so the report is a dated record of what you saw.
- The pack does not ask the assistants for you and contains no browser automation or API caller. You ask by hand, or with your own official API key.
- Name matching is word matching on the names and aliases you list. It misses misspellings you have not added as aliases, and it cannot tell a recommendation from a warning.
- The pack makes no claim about mentions, sales, traffic or ranking.
- The skill file, AGENTS.md snippet and Grok Bot rules block were not loaded inside Claude Code, Codex, Hermes or Grok Bot. Linux only; Windows and macOS were not tested. The scripts open no network connection.
- The approval step refuses piped input and the environment variables Claude Code, Codex, Hermes and Grok Bot set. That stops an agent approving its own change; it is not a lock against someone with the same account.
- On 2026-10-29, on Linux with Python 3.13: visibility_check.py gave 15 findings on the seeded folder (each check once) and 0 on the fixed one, caught 15 of 15 single faults with only its own check, wrote nothing, and exited 2 on a missing folder, missing or broken visibility.json; checker tests 29 passed, 0 failed; vis.py tests at a pseudo-terminal 39 passed, 0 failed.

## Questions

**Why three runs?** The same question in a new chat can name different businesses. One answer is not a pattern, so the check will not call a gap on fewer than three fresh runs.

**Why not have the agent ask the assistants?** Automating a consumer chat window breaks most assistants' terms. You ask by hand, or with your own official API key, and the agent records and reads the answers.

**How is this different from a tracking subscription?** Paid trackers ask for you on a schedule and cover far more questions. This is a $19 pack for a small, careful, dated record and the pages to change. If you need daily numbers across hundreds of questions, use a tracker.

**Can I check a competitor?** No. The check runs only on a brand the owner attests is theirs, or one they are hired to represent.

## How to buy

$19 one time at https://paperchasewebb.ai/bots/marketplace/items/ai-answer-visibility-check-does-an-assistant-name-you/. Stripe checkout, then an instant download page; the download link is also in your emailed receipt.

Seller: PaperChaseWebb Inc., mgmt@paperchasewebb.com