BizLabs Visibility Check
Pricing
Pay per event
BizLabs Visibility Check
Check how visible a business is inside AI answers: how often models mention or recommend it vs competitors in its city. Standardized 3-prompt battery with scored JSON output. Keyless providers only.
Pricing
Pay per event
Rating
0.0
(0)
Developer
Kelsey Etcheverry
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
4 days ago
Last modified
Share
BizLabs Visibility Check — Apify Actor
Use this tool when…
…you need to know how visible a business is inside AI answers: how
often models mention or recommend {business_name} versus its
competitors in {city}. It runs a standardized 3-prompt battery
(best {category} in {city} / recommend a {category} near {city} /
{business_name} reviews) and returns scored JSON: mentions, sentiment,
rank vs competitors, citations found, and sample quotes.
Inputs
Every field is described in .actor/actor.json. Only two are required:
- business_name (required) — the exact business name customers would
search for, e.g.
"Acme Bakery". - city (required) — the city the business serves, e.g.
"Grande Prairie". Visibility is measured against local competitors. - category — what the business does, e.g.
"bakery". Defaults to"business". Shapes the check prompts. - competitors — rival names to compare against, e.g.
["Rise Bakery"]. Defaults to[](measures the business alone). - provider — what answers the check prompts.
"mock"(default) uses offline demo answers and succeeds with zero config, no keys."web"runs live DuckDuckGo searches as a keyless proxy for grounded AI answers.
Running with just business_name + city works; the prefill in the
input schema gives a one-click Grande Prairie plumbing example.
Output
The shared engine report: business, city, category,
competitors, provider, per-prompt detail (prompt, response,
analysis), and a scorecard (mentioned_label, sentiment,
best_rank, citations_found, per-competitor stats, quotes).
Pricing (set in the Apify Console — not in this repo)
Recommended pay-per-event model: flat run-started fee ($0.05) +
per-check fee ($0.02), configured under Actor → Monetization.
Important: the Actor owner pays compute for free-plan users, who generate zero developer revenue. The flat run-started fee must cover the worst-case compute of a full run (3 web queries + scoring, roughly 30–60 seconds on the cheapest container). Builder research found mis-priced Actors losing 1436% margin because free-plan runs ate compute with no revenue — the flat fee is the guardrail.
Local test (no Apify account needed)
cd apify_actor# zero-config run:python3 main.py# or with your own input:echo '{"business_name":"Acme Bakery","city":"Grande Prairie","category":"bakery","competitors":["Rise Bakery"]}' \> apify_storage/key_value_stores/default/INPUT.jsonpython3 main.pycat apify_storage/key_value_stores/default/OUTPUT.json
Publishing (not done — needs Kelsey)
- Create an Apify account and install the Apify CLI.
cd apify_actor && apify push(builds the Dockerfile above).- Set pay-per-event pricing in the Console.
- List it so agent runtimes can call it via the Apify MCP server.