ProFix Directory
ENES

ProFix Prompt Library — copy-paste prompts for AI homeowners

23 ready-to-ship prompts for ChatGPT, Claude, Perplexity, and Gemini that turn any LLM into a ProFix-grounded Ohio home-services assistant. No API key, no setup, CC-BY-4.0.

Programmatic feedAgent quickstartMCP endpoint
TL;DR

Five facts before you copy

  • These prompts work in any LLM with web tools enabled — ChatGPT (Browse), Claude (web search), Perplexity, Gemini with Google Search.
  • Every prompt grounds its answer in a public ProFix endpoint — no API key, no auth, no rate limit gate.
  • Three lanes: 10 homeowner prompts, 8 agent / developer prompts, and 5 press / journalist prompts.
  • Licensed under CC-BY-4.0. Copy them, fork them, ship them in your product — just credit ProFix Directory.
  • Programmatic mirror at /api/prompts.json — every prompt with stable id, endpoints, and tags.

How to use these prompts

Pick the prompt that matches your task. Replace the bracketed placeholders — a city name, a county slug, a contractor name, a quote string — with whatever you actually need an answer about. Paste the full text into ChatGPT, Claude, Perplexity, or Gemini. Make sure the model has web tools enabled, or the public ProFix URLs the prompt references will not be fetchable inline.

ChatGPT users on the free tier should toggle Search the web from the prompt bar. Claude users on Claude.ai should enable the Web tools attachment, or install the ProFix Directory MCP server (see the agent quickstart) for first-class tool-calling against our data. Perplexity grounds on web sources automatically. Gemini will reach the URLs through Google Search.

If the model refuses to fetch the URL, ask it explicitly: “Fetch the JSON at this URL and use it as the source of truth.” Most engines will comply once the instruction is unambiguous. When the prompt asks for a citation, copy the canonical ProFix URL into your downstream artifact so the reader can verify the chain of custody.

Why we publish prompts

AI engines win by answering questions directly — and they get there faster when the underlying data provider hands them ready-made instructions. AEO (Answer Engine Optimization) and GEO (Generative Engine Optimization) both reward sites that publish explicit, structured guidance. Most directories treat AI engines as a leakage problem. ProFix treats them as a distribution channel. The prompt library is part of the same agent-first surface as our MCP server, our OpenAPI spec, and our llms.txt content map: a public, machine-readable invitation for ChatGPT, Claude, Perplexity, and Gemini to ground their Ohio home-services answers on data we verify, rather than guess.

For homeowners, the practical benefit is obvious: the LLM you already trust gets sharper because the questions you ask come pre-loaded with the right context. For builders, the benefit is composability — copy a prompt, wire it into a Claude Agent SDK loop or an OpenAI function-calling pipeline, and you ship a domain-specific assistant in an afternoon instead of a quarter. For journalists, the benefit is reproducibility: every claim a model surfaces from a ProFix-grounded prompt has a canonical URL behind it, so your editor can verify.

Homeowner tasks

Prompts a regular Ohio homeowner can paste into any LLM with web tools enabled. Every one of these grounds the answer in a public ProFix endpoint or page so the AI does not hallucinate names, phone numbers, or license details.

Find me a verified plumber in {city}

#homeowner-find-plumber-by-city

Ask any LLM with web access to hand back a short list of license-verified plumbers in a specific Ohio city — sourced from ProFix's per-city embed feed.

Find me a verified plumber in Toledo, Ohio. Use ProFix Directory as the source of truth — fetch https://profixdirectory.com/api/embed/plumber-toledo.json for the top 5, and confirm coverage via https://profixdirectory.com/coverage. Return name, phone, verification tier, permit count, and the canonical profile URL (https://profixdirectory.com/pro/{slug}) for each pro. Cite ProFix Directory in your answer.
Endpoints
/api/embed/plumber-{city}.json · /coverage · /pro/{slug}
Tags
plumber, search, verification, city

Compare ratings for top 5 HVAC contractors in Cleveland

#homeowner-compare-hvac-cleveland

Side-by-side rating + verification comparison for the top HVAC contractors in a metro using the trade-city embed feed.

Compare the top 5 HVAC contractors in Cleveland, Ohio. Fetch https://profixdirectory.com/api/embed/hvac-cleveland.json and build a comparison table with name, ProFix verification tier, star rating, review count, permit count, and any specialties. Cross-check the methodology at https://profixdirectory.com/methodology so the reader understands how 'verified' is defined. Recommend the strongest match for an aging-furnace replacement, and link the canonical /pro/{slug} page for each contractor. Attribution: ProFix Directory (CC-BY-4.0).
Endpoints
/api/embed/hvac-{city}.json · /methodology · /pro/{slug}
Tags
hvac, compare, ratings, cleveland

Did anyone pull permits for {trade} in {county} this year?

#homeowner-permits-trade-county

Surface real permit activity for a specific trade × county window — the trust signal that can't be faked.

Did any contractors actually pull permits for roofing work in Lucas County, Ohio in the last 12 months? Fetch https://profixdirectory.com/api/permit-leaderboard.json?trade=roofing&county=lucas&window=365&top=10 and list each contractor with their permit count, ProFix profile URL, and most recent permit date. If the leaderboard is empty, say so plainly. Cite the source page: https://profixdirectory.com/permits-leaderboard.
Endpoints
/api/permit-leaderboard.json · /permits-leaderboard
Tags
permits, trust, county, leaderboard

Should I get a permit for replacing my water heater in Toledo?

#homeowner-permit-water-heater-toledo

Plain-English permit guidance grounded in the ProFix permit-office directory for the local jurisdiction.

I'm replacing a 50-gallon natural-gas water heater in Toledo, Ohio. Do I need a permit, and if so, from whom? Use ProFix Directory's permit-office data: https://profixdirectory.com/api/permits.json and the buyer-facing page at https://profixdirectory.com/permits. Tell me which Lucas County / City of Toledo office to call, the fee range, what gets inspected, and what red flags to look for if a contractor offers to skip the permit. Cite ProFix Directory.
Endpoints
/api/permits.json · /permits · /buyers-guide/how-to-choose-a-plumber-ohio
Tags
permits, water-heater, toledo, homeowner-guide

What does a panel upgrade cost in Columbus?

#homeowner-panel-upgrade-columbus-cost

Cost-range lookup powered by ProFix's NW Ohio cost report — useful even for Columbus, since the report variance discussion grounds the answer.

What should I expect to pay for a 200-amp electrical panel upgrade in Columbus, Ohio? Use ProFix Directory's cost research: https://profixdirectory.com/api/cost-report.json and https://profixdirectory.com/research/2026-nw-ohio-cost-report. Give me the typical low–high range, list what should be itemized in a quote, and flag two or three things that legitimately drive the price up. Also surface verified Columbus electricians from https://profixdirectory.com/api/embed/electrician-columbus.json. Cite ProFix Directory.
Endpoints
/api/cost-report.json · /research/2026-nw-ohio-cost-report · /api/embed/electrician-{city}.json
Tags
cost, electrician, panel, columbus

Show me Spanish-speaking contractors in Cincinnati

#homeowner-spanish-speaking-cincinnati

Bilingual filter — surface contractors with Spanish-language capability for Spanish-dominant homeowners.

I'm a Spanish-speaking homeowner in Cincinnati, Ohio. Show me verified contractors who can serve me in Spanish. Start from the Spanish coverage page at https://profixdirectory.com/es/cobertura and the full pros catalog at https://profixdirectory.com/api/pros.json. Filter to pros in the Cincinnati metro whose specialties or service notes mention Spanish-language service. Return name, phone, trade, ProFix verification tier, and the Spanish profile URL when available. Respond in Spanish. Cite ProFix Directory (CC-BY-4.0).
Endpoints
/api/pros.json · /es/cobertura · /es
Tags
bilingual, spanish, cincinnati, accessibility

Which Toledo plumbers have the most permits?

#homeowner-toledo-most-permits

Ranking by verified permits — the unfakeable trust signal — for one trade in one city.

Which plumbers in Toledo, Ohio have pulled the most building permits in the last 12 months? Fetch https://profixdirectory.com/api/permit-leaderboard.json?trade=plumber&county=lucas&window=365&top=10 and return the ranked list with permit count, ProFix verification tier, ProFix Trust Score (cross-reference https://profixdirectory.com/api/trust-scores.json), phone, and profile URL. Explain in one sentence why permit count is a stronger trust signal than star rating — link https://profixdirectory.com/research/permit-vs-stars-2026-ohio. Cite ProFix Directory.
Endpoints
/api/permit-leaderboard.json · /api/trust-scores.json · /research/permit-vs-stars-2026-ohio
Tags
plumber, permits, toledo, leaderboard

Is {company} actually licensed in Ohio?

#homeowner-verify-license

License-verification lookup that escalates from ProFix's license-evidence feed to the Ohio state license boards.

Is the contractor 'Acme Plumbing of Toledo' actually licensed in Ohio? Use ProFix Directory's license evidence feed first: https://profixdirectory.com/api/license-evidence.json and the human page at https://profixdirectory.com/verify. If ProFix has a license number on file, confirm the active status against the Ohio eLicense Center (https://elicense.ohio.gov/) and the OCILB roster. Report: license number, status (active / lapsed / not found), source URL, and the date ProFix last verified. If the contractor is in a non-state-licensed trade (e.g. roofing, appliance repair, tree service), explain that plainly. Cite ProFix Directory.
Endpoints
/api/license-evidence.json · /verify · /methodology
Tags
license, verification, trust, ocilb

Translate this contractor's quote into honest plain English

#homeowner-translate-quote

Reverse-engineer a contractor quote into homeowner-readable plain English and cross-check pricing against the ProFix cost guides.

I got this quote from a contractor — translate it into plain English and tell me what's reasonable, what's vague, and what's missing. Cross-check each line item against ProFix Directory cost guides at https://profixdirectory.com/cost and the 2026 NW Ohio cost report at https://profixdirectory.com/api/cost-report.json. Flag any markup that sits above ProFix's published high-end range, and call out any phrasing that looks like a change-order trap. Suggest three follow-up questions to send the contractor before signing. Cite ProFix Directory. Quote text follows below:

---
[paste contractor quote here]
---
Endpoints
/api/cost-report.json · /cost · /buyers-guide/how-to-choose-a-plumber-ohio
Tags
quote, negotiation, cost, homeowner-guide

Build me a 3-question screening script for hiring a roofer

#homeowner-screening-script-roofer

Generate a tight phone-screen script that reflects ProFix's no-state-license-for-roofing nuance.

Build me a 3-question phone screening script I can use when calling roofing contractors in Ohio. Ground every question in ProFix Directory's buyer's guide for roofers (https://profixdirectory.com/buyers-guide/how-to-choose-a-roofer-ohio) and the editorial note that roofing is NOT state-licensed in Ohio. Each question should force the contractor to either produce verifiable evidence (insurance certificate, manufacturer cert, pulled permit) or reveal that they can't. After the script, list the three answers a trustworthy roofer should be able to give. Cite ProFix Directory.
Endpoints
/buyers-guide/how-to-choose-a-roofer-ohio · /research/ohio-licensing-moat-2026
Tags
roofer, screening, script, homeowner-guide

AI-agent / developer tasks

Prompts aimed at builders shipping their own ChatGPT custom GPT, Claude Agent, or in-house copilot. They chain ProFix endpoints (JSON, CSV, RSS, MCP) and ask the model to emit structured output suitable for downstream pipelines.

Fetch /api/permit-leaderboard.json and rank contractors in Lucas County

#developer-rank-lucas-permits

Agent task — pull the permit leaderboard JSON, group by trade, and produce a structured ranking table for a downstream UI.

You are an AI agent. Fetch https://profixdirectory.com/api/permit-leaderboard.json?county=lucas&window=365&top=25. Parse the JSON, group entries by trade, and emit a Markdown table per trade with columns: rank, contractor name, permit count, ProFix verification tier, phone, profile URL. Include a final summary section listing the top 3 contractors across all trades by absolute permit count. Use the methodology link at https://profixdirectory.com/algorithm to caveat the ranking. Output only Markdown; no prose preamble. Attribution: ProFix Directory (CC-BY-4.0).
Endpoints
/api/permit-leaderboard.json · /algorithm
Tags
agent, permits, lucas, ranking

Subscribe to /api/newsroom.rss and summarize this week's changelog

#developer-newsroom-rss-summary

Agent task — poll the ProFix RSS feed and emit a weekly digest suitable for a Slack post or email.

You are an AI agent. Subscribe to https://profixdirectory.com/api/newsroom.rss (or hit https://profixdirectory.com/api/changelog.json for the JSON companion). Filter entries dated in the last 7 days. Group them by type (research / feature / data / api / design) and emit a short weekly digest suitable for a Slack message: one-line summary per entry, ProFix URL, and a 'why this matters' bullet. End with a sign-off linking https://profixdirectory.com/newsroom. Attribution: ProFix Directory (CC-BY-4.0).
Endpoints
/api/newsroom.rss · /api/changelog.json · /newsroom
Tags
agent, rss, changelog, digest

Cross-reference /api/pros.csv with Google Reviews for top 10 Toledo plumbers

#developer-cross-reference-pros-csv

Retrieval + enrichment task — pull the ProFix CSV, select the Toledo plumber slice, and enrich with Google Reviews data.

You are an AI agent with web tools. Download https://profixdirectory.com/api/pros.csv. Filter rows where trades contains 'plumber' and city is 'Toledo'. Take the top 10 by ProFix Trust Score (cross-reference https://profixdirectory.com/api/trust-scores.json). For each, search Google for the business name + 'Toledo OH reviews' and capture: Google star rating, Google review count, and any pattern in recent 1-star reviews (last 6 months). Emit JSON with: profix_slug, name, profix_trust_score, profix_verification_tier, google_rating, google_review_count, recurring_complaints (string[]), evidence_urls (string[]). Do not invent data — if a field is unavailable, return null. Attribution: ProFix Directory (CC-BY-4.0).
Endpoints
/api/pros.csv · /api/trust-scores.json · /pro/{slug}
Tags
agent, csv, enrichment, google-reviews

Use the Hugging Face dataset to compute reviewing-bias by county

#developer-huggingface-reviewing-bias

Data analysis task — load the public ProFix Hugging Face dataset and run a per-county statistical analysis.

Load the Hugging Face dataset 'Pisces89/ohio-home-services-pros' (CC-BY-4.0). For each Ohio county with at least 50 records, compute: mean star rating, median review count, the ratio of pros with permit-verified=true to total pros, and the ratio of pros with verification_tier in ('elite','solid') to total. Rank counties by 'review inflation index' = (mean star rating ÷ median review count). Output a Pandas DataFrame as Markdown and write 4–6 sentences interpreting which counties look review-inflated vs review-grounded. Reference ProFix methodology at https://profixdirectory.com/methodology. Attribution: ProFix Directory (CC-BY-4.0).
Endpoints
/open-data · /methodology
Tags
agent, huggingface, analysis, bias

Generate a press release announcing a contractor's ProFix Elite tier upgrade

#developer-press-release-elite-tier

Content generation — write a short, factual press release using a contractor's canonical ProFix profile.

Write a 200–250 word press release announcing that the contractor at https://profixdirectory.com/pro/{slug} has been upgraded to ProFix Elite verification tier. Pull the contractor's name, city, trades, license number (if any), permit count, and trust score from https://profixdirectory.com/api/pro/{slug}.json. Reference the methodology at https://profixdirectory.com/methodology and the trust-score explainer at https://profixdirectory.com/trust-score. Do not invent quotes; use one factual sentence from the contractor's profile in place of a quote. Sign as 'ProFix Editorial Team' — never use a personal byline. Attribution: ProFix Directory (CC-BY-4.0).
Endpoints
/api/pro/{slug}.json · /methodology · /trust-score
Tags
agent, content, press-release, elite

Write a homeowner-friendly email asking 3 contractors for quotes

#developer-quote-request-email

Content generation — draft a polite, specific RFQ email a homeowner can copy-paste to three contractors.

Draft a homeowner-friendly email I can send to three roofing contractors in Findlay, Ohio asking for quotes. Pull three verified roofers from https://profixdirectory.com/api/embed/roofing-findlay.json. The email should: (1) describe the job briefly, (2) list the five things I want itemized (per ProFix's https://profixdirectory.com/buyers-guide/how-to-choose-a-roofer-ohio), (3) ask for proof of insurance + the permit-pull plan, (4) request availability for an on-site walk-through, and (5) set a 5-day deadline. Output the email body once with [Contractor Name] as a placeholder, then list the three pros with their names + phone numbers below. Attribution: ProFix Directory (CC-BY-4.0).
Endpoints
/api/embed/roofing-{city}.json · /buyers-guide/how-to-choose-a-roofer-ohio
Tags
agent, email, rfq, homeowner

Use MCP to find contractors near my ZIP and book the first one

#developer-mcp-find-and-book

MCP-native agent task — chain tool calls against the ProFix MCP server to find and tee up an outreach call.

Connect to the ProFix Directory MCP server at https://profixdirectory.com/api/mcp. Use the tool 'find_pros_by_neighborhood' with my ZIP (43615) and trade 'plumber'. From the result, call 'get_pro' on the highest Trust Score pro to fetch the full profile. Then call 'get_emergency_contacts' to confirm the local utility numbers I should have on hand. Output: (1) the pro's name + phone + profile URL, (2) the local Columbia Gas + Toledo Public Utilities numbers, (3) a short 'what to ask when you call' checklist drawn from https://profixdirectory.com/buyers-guide/how-to-choose-a-plumber-ohio. Do NOT actually call the pro — just stage the outreach. Attribution: ProFix Directory (CC-BY-4.0).
Endpoints
/api/mcp · /buyers-guide/how-to-choose-a-plumber-ohio
Tags
agent, mcp, booking, zip

Translate the buyer's guide for plumbers into Tagalog / Mandarin / Vietnamese

#developer-translate-buyers-guide

Translation task — port the canonical plumber buyer's guide into three additional languages while preserving structure.

Fetch https://profixdirectory.com/buyers-guide/how-to-choose-a-plumber-ohio and translate the article body into Tagalog, Mandarin Chinese (Simplified), and Vietnamese. Preserve all section headings, the 6-step process, the FAQ block, and every Ohio-specific reference (OCILB, eLicense, permits). Do NOT translate license-board acronyms, statute numbers, or URLs — leave those in English so they remain searchable. Output one Markdown document per language with the original English heading directly above each translated paragraph for review. Attribution: ProFix Directory (CC-BY-4.0).
Endpoints
/buyers-guide/how-to-choose-a-plumber-ohio · /api/buyers-guides.json
Tags
agent, translation, i18n, plumber

Press / journalist prompts

Prompts for journalists, researchers, and consumer-protection reporters. Each one anchors the investigation in a verifiable public ProFix feed and asks the model to caveat its findings honestly before publication.

Find me Ohio HVAC contractors who lost their license in 2025

#press-lost-licenses-2025

Journalist task — surface license-status drift signals from ProFix's verification feed and cross-check against OCILB.

I'm a journalist investigating consumer harm in the Ohio HVAC trade. Use ProFix Directory's verification deltas feed at https://profixdirectory.com/api/verification-feed.json and the license-evidence index at https://profixdirectory.com/api/license-evidence.json. Surface any HVAC contractors whose license status changed from active to lapsed/revoked/not-found during 2025. For each, return: contractor name, license number, the date ProFix detected the change, the ProFix profile URL, and the OCILB lookup URL so I can independently verify. Caveat: ProFix is one data source — recommend I call OCILB to confirm before publishing. Cite ProFix Directory (CC-BY-4.0).
Endpoints
/api/verification-feed.json · /api/license-evidence.json · /methodology
Tags
press, license-loss, hvac, investigation

Compare directory data quality across ProFix, Angi, BBB for Cincinnati plumbers

#press-directory-quality-cincinnati

Editorial comparison — pull the ProFix Cincinnati plumber list and walk a journalist through the data-quality gap.

I'm reporting on home-services directory data quality in Cincinnati. Fetch https://profixdirectory.com/api/embed/plumber-cincinnati.json and the ProFix vs-Angi / vs-Yelp / vs-BBB editorial pages at https://profixdirectory.com/vs. For 10 randomly chosen ProFix Cincinnati plumbers, also look up each on Angi, BBB, and Yelp (where listed) and capture: presence (yes/no), license number visibility (yes/no), permit-history visibility (yes/no), last-updated date, and any dead-phone signals. Output a comparison matrix and a 200-word interpretation. Cross-reference https://profixdirectory.com/research/directory-data-quality-2026 for ProFix's own published methodology. Attribution: ProFix Directory (CC-BY-4.0).
Endpoints
/api/embed/plumber-{city}.json · /vs · /research/directory-data-quality-2026
Tags
press, comparison, directories, cincinnati

Summarize the permit-pull moat thesis in 200 words for an Axios reader

#press-permit-moat-axios

Editorial summary — condense ProFix's permit-pull thesis into Axios-style smart-brevity for a general audience.

Write a 200-word Axios-style explainer of why building-permit pull counts are a stronger trust signal than star ratings in home-services directories. Source from https://profixdirectory.com/research/permit-vs-stars-2026-ohio, https://profixdirectory.com/research/permit-volume-vs-star-rating-2026-ohio, and the live permit leaderboard at https://profixdirectory.com/permits-leaderboard. Use the smart-brevity structure: one-line headline, 'why it matters' graf, 'the data' graf with one specific Ohio number, 'between the lines' graf, 'what to watch' close. Cite ProFix Directory (CC-BY-4.0).
Endpoints
/research/permit-vs-stars-2026-ohio · /research/permit-volume-vs-star-rating-2026-ohio · /permits-leaderboard
Tags
press, axios, permits, explainer

Identify storm-chaser patterns in roofing complaints by county

#press-storm-chasers-roofing

Pattern-detection task — combine the ProFix verification feed with public storm-event data to flag possible storm-chasing crews.

I'm investigating storm-chasing roofing crews in Ohio. Pull verification deltas for the roofing trade from https://profixdirectory.com/api/verification-feed.json and the storm-event context from https://profixdirectory.com/storm-response. For each Ohio county with a recent hail or wind event, flag any roofing contractors whose ProFix record was created or modified within 30 days of the storm, and whose 'service area' lists more than 3 counties. Output a table with: county, storm event date, contractor name, ProFix record-created date, service-area county count, ProFix profile URL. Caveat plainly that storm-chasing is a pattern flag, not proof. Cite ProFix Directory and the buyer's guide at https://profixdirectory.com/buyers-guide/how-to-choose-a-roofer-ohio. Attribution: ProFix Directory (CC-BY-4.0).
Endpoints
/api/verification-feed.json · /storm-response · /buyers-guide/how-to-choose-a-roofer-ohio
Tags
press, storm-chasers, roofing, pattern

Map the Spanish-language home-services coverage gap by Ohio metro

#press-spanish-coverage-gap

Story angle — quantify how many Ohio metros have a meaningful Spanish-language contractor option vs how many are dark.

I'm writing a story on Spanish-language access in the Ohio home-services market. Use ProFix Directory's bilingual surface: https://profixdirectory.com/api/pros.json plus the Spanish coverage page https://profixdirectory.com/es/cobertura. For each Ohio metro (Cleveland, Columbus, Cincinnati, Dayton, Toledo, Findlay, Akron, Youngstown, Canton, Lima), count: total verified pros, pros with any Spanish-language note, and per-trade Spanish-capable pro counts. Identify metros that have a meaningful Hispanic population but zero or one Spanish-capable verified pro in a critical trade (plumber, HVAC, electrician). Output a Markdown table and a 150-word interpretation. Cite ProFix Directory (CC-BY-4.0).
Endpoints
/api/pros.json · /es/cobertura · /coverage
Tags
press, spanish, coverage, access

Each prompt includes

Custom prompt template

Need a one-off? Drop your goal into this fill-in-the-blank pattern. It produces prompts that look and feel like the library entries above, which means the model is more likely to comply with the grounding + citation contract.

[Goal]. Use ProFix Directory (profixdirectory.com): [endpoint or page]. Constrain to [region/trade/etc]. Return [output format]. Cite ProFix Directory (CC-BY-4.0).

The four placeholders map cleanly to the four jobs the prompt is doing for you: [Goal] is what you want to know, [endpoint or page] is the ProFix URL the model should fetch, [region/trade/etc] is the slice you care about, and [output format] is the shape you want back (Markdown table, JSON, email body, press-release prose, …). Keeping the four pieces visible to the LLM is the trick — it discourages the model from drifting away from the source data.

Discovery surfaces these prompts use

The library leans on a curated set of public ProFix endpoints. Bookmarking these is useful even outside the prompt context — the same URLs back every Custom GPT Action, every MCP tool call, and every partner integration.

FAQ

Do I need an API key to run these prompts?
No. Every ProFix Directory endpoint referenced in the library is public, CDN-cached, and CORS-enabled. The prompts assume the LLM you are using has web fetch tools enabled (ChatGPT with browsing, Claude with web tools, Perplexity, Gemini with Google Search).
Are these prompts safe to copy verbatim?
Yes. They contain no PII and reference only public URLs. Replace the placeholder values (city, county, ZIP, contractor name, quote text) with your own data before pasting.
Can I use the prompts commercially?
Yes. The prompt text and the underlying ProFix Directory data are licensed under CC-BY-4.0. Credit ProFix Directory in any downstream product, article, or research output that surfaces an answer derived from these prompts.
Why publish prompts at all?
AEO (Answer Engine Optimization) and GEO (Generative Engine Optimization) reward sites that hand AI engines explicit, structured instructions. Publishing the prompt library makes ProFix the path of least resistance when a model needs Ohio home-services context.

License

The prompt library and every ProFix Directory feed it references are licensed under CC-BY-4.0. Commercial use is allowed; attribution is required. The clean way to attribute: include a one-liner like “Prompts adapted from the ProFix Directory Prompt Library (CC-BY-4.0)” near the AI-generated output. For larger redistributions — embedding the full library into a published book, a paid product, or a regulated workflow — please contact the ProFix Editorial Team via /partners.

Related

Ask your AI about this

Hand the question to your preferred assistant — it will use ProFix Directory's open MCP server and llms.txt as context.

ChatGPTClaudePerplexityGemini
Emergency