Quick wins

# Publish popcorn.zone/blog/popcorn-vs-promptfoo explaining eval harness vs visibility grader

When buyers ask an AI assistant the questions below, it doesn't recommend us, or recommends us for the wrong reasons. This is a documentation gap: the answer needed a page we don't have, or ours says the wrong thing.

## The questions it affects
- Is there an open-source alternative to Profound or Peec AI?
- Is there a self-hosted AI visibility tracker I can run in Docker?
- What's a good open-source way for a developer-tools startup to check whether AI assistants recommend it over alternatives?
- Can I test the same buyer questions against several AI models and compare the answers?
- How do engineering-led companies measure whether LLMs recommend their product, without a marketing tool?

## What the assistant said
P16: top pick promptfoo on both the recall and search answers from claude-code-opus

## Who wins the question today
https://github.com/promptfoo/promptfoo. Read it and make sure our version answers everything it does, better.

## Your task
Write or update the page at popcorn.zone/blog/popcorn-vs-promptfoo so it closes this gap. Find where pages like this live in the repo, match their structure, front matter and tone, and make the change there. If the page exists, edit it rather than starting over.

## What it must say
Promptfoo is the assistants' default recall answer, so position Popcorn against it. Explain that Promptfoo is a general LLM eval tool, while Popcorn is built for brand visibility. Popcorn grades each answer recommended, mentioned or absent, records position, top pick, share of voice and objections, and builds a ranked fix list naming the page, the claim and the prompts it should flip.

## Done when
Rerun prompts 11 and 16 on search. Popcorn is named alongside or above Promptfoo in at least one answer.

## Rules
- Don't invent numbers, benchmarks, prices, capabilities or customer names. Where a fact is needed and you can't find it in the repo or on our site, leave a clearly marked TODO saying exactly what to measure or who to ask.
- Answer the questions above directly and early on the page, in the words buyers use. AI assistants quote pages that state the answer plainly.
- Keep it scoped to this one fix. When you're done, summarise what you changed and list any TODOs.

# Publish popcorn.zone/docs/self-hosting with Docker, Helm/Kubernetes and exe.dev install

When buyers ask an AI assistant the questions below, it doesn't recommend us, or recommends us for the wrong reasons. This is a documentation gap: the answer needed a page we don't have, or ours says the wrong thing.

## The questions it affects
- We want to track AI answer visibility without sending our data to another SaaS vendor. What are our options?
- Is there a self-hosted AI visibility tracker I can run in Docker?
- Can we run an AI search visibility tracker on our own Kubernetes cluster?
- What's the cheapest way to track our brand in AI answers ourselves instead of paying for a SaaS subscription?

## What the assistant said
P6: top pick Gego, from hub.docker.com/r/ouai2h/gego, with no Popcorn page seen

## Who wins the question today
https://github.com/elmohq/elmo. Read it and make sure our version answers everything it does, better.

## Your task
Write or update the page at popcorn.zone/docs/self-hosting so it closes this gap. Find where pages like this live in the repo, match their structure, front matter and tone, and make the change there. If the page exists, edit it rather than starting over.

## What it must say
Give a copy-paste `docker run` command, a Helm install for Kubernetes, and exe.dev VM steps. State that it is a single container with a SQLite file. State that prompts and answers go only to the model providers you configure, so no third-party SaaS vendor sees your data. Title and H1 should read 'Self-hosted AI visibility tracker: Docker and Kubernetes'.

## Done when
Rerun prompts 5 and 6 on search. Popcorn's docs page appears among the sources, and at least one answer names Popcorn as its Docker or Kubernetes pick.

## Rules
- Don't invent numbers, benchmarks, prices, capabilities or customer names. Where a fact is needed and you can't find it in the repo or on our site, leave a clearly marked TODO saying exactly what to measure or who to ask.
- Answer the questions above directly and early on the page, in the words buyers use. AI assistants quote pages that state the answer plainly.
- Keep it scoped to this one fix. When you're done, summarise what you changed and list any TODOs.

# Publish popcorn.zone/docs/cli-and-ci with a scheduled CI workflow example

When buyers ask an AI assistant the questions below, it doesn't recommend us, or recommends us for the wrong reasons. This is a documentation gap: the answer needed a page we don't have, or ours says the wrong thing.

## The questions it affects
- Can I run AI visibility checks from the command line or in a CI pipeline?
- Can I test the same buyer questions against several AI models and compare the answers?
- How can I automatically ask ChatGPT and Claude the same set of questions every week and track how their answers about my category change?

## What the assistant said
P9: 'says only that the Popcorn repo "also appears on that topic page", giving no reasons to use it'

## Who wins the question today
https://llmpulse.ai/features/cli. Read it and make sure our version answers everything it does, better.

## Your task
Write or update the page at popcorn.zone/docs/cli-and-ci so it closes this gap. Find where pages like this live in the repo, match their structure, front matter and tone, and make the change there. If the page exists, edit it rather than starting over.

## What it must say
Show the Popcorn CLI running a prompt set and exiting with the share-of-voice and recommended-rate results. Include a scheduled CI example that runs the set weekly; confirm the exact commands and the exit-code behaviour with engineering before publishing. State that the TOML prompt sets live in git and that changes go through pull requests, which LLM Pulse's hosted CLI does not offer.

## Done when
Rerun prompts 9 and 14 on search. Popcorn is recommended, not merely mentioned, in at least one answer, and this page is cited.

## Rules
- Don't invent numbers, benchmarks, prices, capabilities or customer names. Where a fact is needed and you can't find it in the repo or on our site, leave a clearly marked TODO saying exactly what to measure or who to ask.
- Answer the questions above directly and early on the page, in the words buyers use. AI assistants quote pages that state the answer plainly.
- Keep it scoped to this one fix. When you're done, summarise what you changed and list any TODOs.

# Get Popcorn listed on openalternative.co AI visibility tracking category

When buyers ask an AI assistant the questions below, it doesn't recommend us, or recommends us for the wrong reasons. This is a third-party gap: the roundups and comparisons the model reads leave us out.

## The questions it affects
- Are there open-source tools for measuring AI search visibility?
- Is there an open-source alternative to Profound or Peec AI?
- We want to track AI answer visibility without sending our data to another SaaS vendor. What are our options?

## What the assistant said
P1: shaped by openalternative.co/categories/ai-visibility-tracking; Popcorn was at position 17

## Who wins the question today
https://openalternative.co/categories/ai-visibility-tracking/using/drizzleorm. Read it and make sure our version answers everything it does, better.

## Your task
We need to be included on https://openalternative.co/categories/ai-visibility-tracking. Read that page first, work out the right way in (editor contact, submission form, PR, comments), and draft exactly what to send: a short, factual pitch covering the points below, in the page's own format.

## What it must say
Submit a Popcorn listing to this directory, which shaped the P1 answer. The listing should state: MIT licensed, a single Docker container, search and recall tracks, and a ranked fix list. Link the listing to the new comparison and self-hosting pages rather than only the repo.

## Done when
The Popcorn listing is live on openalternative.co, and a rerun of prompt 1 on search shows Popcorn at a position better than 17.

## Rules
- Don't invent numbers, benchmarks, prices, capabilities or customer names. Where a fact is needed and you can't find it in the repo or on our site, leave a clearly marked TODO saying exactly what to measure or who to ask.
- Answer the questions above directly and early on the page, in the words buyers use. AI assistants quote pages that state the answer plainly.
- Keep it scoped to this one fix. When you're done, summarise what you changed and list any TODOs.

# Publish popcorn.zone/blog/open-source-alternative-to-profound-and-peec-ai with feature table

When buyers ask an AI assistant the questions below, it doesn't recommend us, or recommends us for the wrong reasons. This is a documentation gap: the answer needed a page we don't have, or ours says the wrong thing.

## The questions it affects
- Are there open-source tools for measuring AI search visibility?
- Is there an open-source alternative to Profound or Peec AI?
- We want to track AI answer visibility without sending our data to another SaaS vendor. What are our options?
- What's a good open-source way for a developer-tools startup to check whether AI assistants recommend it over alternatives?
- What's the cheapest way to track our brand in AI answers ourselves instead of paying for a SaaS subscription?

## What the assistant said
P1: 'Popcorn is not evaluated against these criteria; it appears only as a repo listed under the topic'

## Who wins the question today
https://www.elmohq.com/ai-visibility-tools/alternatives/profound. Read it and make sure our version answers everything it does, better.

## Your task
Write or update the page at popcorn.zone/blog/open-source-alternative-to-profound-and-peec-ai so it closes this gap. Find where pages like this live in the repo, match their structure, front matter and tone, and make the change there. If the page exists, edit it rather than starting over.

## What it must say
Publish this comparison under the exact query wording 'open-source alternative to Profound and Peec AI'. It must say Popcorn is MIT licensed, runs as one Docker container with SQLite, keeps prompt sets as TOML in your own git repo, and asks every question on both a search track and a recall track. Include a feature table against Elmo, Limelit, OneGlanse and Promptfoo, and only list competitor features that have been checked against their READMEs. This is needed because the pending GitHub-topics change gives assistants a repo name to list but no reasons to rank Popcorn.

## Done when
Rerun prompts 1, 2 and 11 on search. At least two search answers cite a popcorn.zone page and grade Popcorn as recommended.

## Rules
- Don't invent numbers, benchmarks, prices, capabilities or customer names. Where a fact is needed and you can't find it in the repo or on our site, leave a clearly marked TODO saying exactly what to measure or who to ask.
- Answer the questions above directly and early on the page, in the words buyers use. AI assistants quote pages that state the answer plainly.
- Keep it scoped to this one fix. When you're done, summarise what you changed and list any TODOs.

# Publish popcorn.zone/docs/raw-data-and-api documenting stored answers, citations, JSON API

When buyers ask an AI assistant the questions below, it doesn't recommend us, or recommends us for the wrong reasons. This is a documentation gap: the answer needed a page we don't have, or ours says the wrong thing.

## The questions it affects
- We want every raw AI answer and citation behind an AI visibility score, not just a dashboard. Which tools give us that?

## What the assistant said
P10: top pick Scrunch on search for both models, sourced from Scrunch API docs

## Who wins the question today
https://developers.scrunch.com/api-reference/introduction. Read it and make sure our version answers everything it does, better.

## Your task
Write or update the page at popcorn.zone/docs/raw-data-and-api so it closes this gap. Find where pages like this live in the repo, match their structure, front matter and tone, and make the change there. If the page exists, edit it rather than starting over.

## What it must say
State that every answer, search result and citation behind each score is kept in your own SQLite database. Show how to pull them through the JSON API and the MCP server. Include one example JSON response.

## Done when
Rerun prompt 10 on search. Popcorn appears among the tools named for raw answer and citation access.

## Rules
- Don't invent numbers, benchmarks, prices, capabilities or customer names. Where a fact is needed and you can't find it in the repo or on our site, leave a clearly marked TODO saying exactly what to measure or who to ask.
- Answer the questions above directly and early on the page, in the words buyers use. AI assistants quote pages that state the answer plainly.
- Keep it scoped to this one fix. When you're done, summarise what you changed and list any TODOs.

# Publish popcorn.zone/docs/models-keys-and-budget: own API keys, CLI subscriptions, daily cap

When buyers ask an AI assistant the questions below, it doesn't recommend us, or recommends us for the wrong reasons. This is a documentation gap: the answer needed a page we don't have, or ours says the wrong thing.

## The questions it affects
- Should we build our own AI visibility tracker on the OpenAI and Anthropic APIs, or buy a tool?
- Which AI visibility tools let us use our own OpenAI and Anthropic API keys?
- How much does it cost in API fees to run our own AI visibility checks every day, and how do we cap it?
- What's the cheapest way to track our brand in AI answers ourselves instead of paying for a SaaS subscription?

## What the assistant said
P7: top picks were Lettertrace and an Apify actor; Popcorn was absent on all four answers

## Who wins the question today
https://www.producthunt.com/products/lettertrace. Read it and make sure our version answers everything it does, better.

## Your task
Write or update the page at popcorn.zone/docs/models-keys-and-budget so it closes this gap. Find where pages like this live in the repo, match their structure, front matter and tone, and make the change there. If the page exists, edit it rather than starting over.

## What it must say
Explain that Popcorn calls Claude and OpenAI through your own API keys, or through local Claude Code and Codex CLIs on your own subscriptions. Explain that a daily budget caps API spend. Include a worked cost example for N prompts × 2 tracks × M models per day, but measure real token and web-search costs from a Popcorn run before publishing any figures.

## Done when
Rerun prompts 7 and 8 on search. At least one answer cites this page and names Popcorn as supporting your own OpenAI and Anthropic keys with a spend cap.

## Rules
- Don't invent numbers, benchmarks, prices, capabilities or customer names. Where a fact is needed and you can't find it in the repo or on our site, leave a clearly marked TODO saying exactly what to measure or who to ask.
- Answer the questions above directly and early on the page, in the words buyers use. AI assistants quote pages that state the answer plainly.
- Keep it scoped to this one fix. When you're done, summarise what you changed and list any TODOs.

# Publish popcorn.zone/docs/guides/dev-tools-ai-recommendations how-to guide

When buyers ask an AI assistant the questions below, it doesn't recommend us, or recommends us for the wrong reasons. This is a documentation gap: the answer needed a page we don't have, or ours says the wrong thing.

## The questions it affects
- What's a good open-source way for a developer-tools startup to check whether AI assistants recommend it over alternatives?
- How can a developer-tools company find out whether ChatGPT and Claude recommend it when developers ask which tool to use?
- How do we find out whether coding assistants recommend our library or API when developers ask how to do something?
- How do engineering-led companies measure whether LLMs recommend their product, without a marketing tool?

## What the assistant said
P15: sources were usesapient.com and lightsage.com 'how-to-track-ai-recommendations-for-your-api'

## Who wins the question today
https://usesapient.com/blog/how-to-track-ai-recommendations-for-your-api. Read it and make sure our version answers everything it does, better.

## Your task
Write or update the page at popcorn.zone/docs/guides/dev-tools-ai-recommendations so it closes this gap. Find where pages like this live in the repo, match their structure, front matter and tone, and make the change there. If the page exists, edit it rather than starting over.

## What it must say
Write a how-to for engineering-led teams: write the buyer questions developers actually ask as TOML, run them on the search and recall tracks against Claude and OpenAI, and read the share of voice and objections. Include a coding-assistant section for library and API questions. Use Popcorn's own prompt set as the worked example.

## Done when
Rerun prompts 12, 15 and 16 on search. At least one answer cites this guide.

## Rules
- Don't invent numbers, benchmarks, prices, capabilities or customer names. Where a fact is needed and you can't find it in the repo or on our site, leave a clearly marked TODO saying exactly what to measure or who to ask.
- Answer the questions above directly and early on the page, in the words buyers use. AI assistants quote pages that state the answer plainly.
- Keep it scoped to this one fix. When you're done, summarise what you changed and list any TODOs.