{"generatedAt":"2026-04-17T01:47:17.340Z","selectorApiUrl":"https://www.thequietprotocol.com/api/engines/select","indexUrl":"https://www.thequietprotocol.com/engines","benchmarksCatalogUrl":"https://www.thequietprotocol.com/api/benchmarks/catalog","documentationUrl":"https://www.thequietprotocol.com/mcp","engines":[{"slug":"ai-visibility-score","title":"AI Visibility Score","eyebrow":"Authority Scanner","description":"A flagship authority scanner that scores entity clarity, answer coverage, trust, local authority, conversion readiness, and machine readability from a real website URL.","url":"https://www.thequietprotocol.com/engines/ai-visibility-score","apiUrl":"https://www.thequietprotocol.com/api/engines/ai-visibility-score","primaryAudience":"Owners, operators, and marketers who want a premium AI/search visibility diagnostic before booking an audit.","idealFor":["Businesses that need a broad website visibility scan","Teams preparing for AI search and answer engines","Operators who want evidence-backed discovery priorities"],"leadingQuestions":["Can AI systems tell who you are and what you do?","Does the site answer the questions buyers actually ask?","Are there enough proof and local signals to route demand confidently?"],"reportHighlights":["Overall AI visibility score and score band","Evidence-backed findings across homepage and priority pages","Fast wins plus related resources and direct audit handoff"],"useCases":["visibility","discovery","entity-clarity","local-authority","ai-readiness"],"mcpToolName":"scan_ai_visibility","resourceUri":"tqp://engines/ai-visibility-score","status":"live"},{"slug":"front-door-benchmark","title":"Front Door Benchmark","eyebrow":"Revenue Benchmark","description":"A flagship benchmark engine that estimates monthly and annual revenue at risk based on lead volume, customer value, and the way a business currently controls the first response.","url":"https://www.thequietprotocol.com/engines/front-door-benchmark","apiUrl":"https://www.thequietprotocol.com/api/engines/front-door-benchmark","primaryAudience":"Owners and operators who need a quantified front-door risk report before stepping into a deeper audit.","idealFor":["Home-service and consult-driven businesses with inbound lead flow","Teams that want a clear annualized leakage estimate","Operators trying to prioritize front-door fixes before buying software"],"leadingQuestions":["How much revenue is the current front door donating every month?","How does your intake posture compare with stronger operators?","Which front-door weakness is hurting you first: coverage, control, booking, or recovery?"],"reportHighlights":["Monthly and annual revenue at risk","Benchmark percentile and peer comparison summary","Fast wins plus direct handoff into the Rage/audit flow"],"useCases":["front-door-revenue","speed-to-lead","missed-calls","benchmarking","operations"],"mcpToolName":"run_front_door_benchmark","resourceUri":"tqp://engines/front-door-benchmark","status":"live"},{"slug":"trust-stack-audit","title":"Trust Stack Audit","eyebrow":"Proof Scanner","description":"A flagship scan that scores review signals, proof depth, expert identity, differentiation, and local trust from a real website URL.","url":"https://www.thequietprotocol.com/engines/trust-stack-audit","apiUrl":"https://www.thequietprotocol.com/api/engines/trust-stack-audit","primaryAudience":"Founders, operators, and marketers who need to see whether their trust architecture is strong enough for search, AI, and buyers.","idealFor":["Businesses where proof and reputation decide the sale","Founders who need a stronger visible trust layer before scaling traffic","Teams fixing low-belief websites with weak proof architecture"],"leadingQuestions":["Do buyers see enough proof to believe the next step?","Can search and AI systems detect real expertise and local trust?","Is the site differentiated enough to be recommended instead of ignored?"],"reportHighlights":["Trust score across reviews, proof, identity, differentiation, and local trust","Evidence samples pulled from the public site","Fast wins, recommended assets, and trust-focused audit handoff"],"useCases":["trust-proof","reviews","differentiation","expert-identity","reputation"],"mcpToolName":"run_trust_stack_audit","resourceUri":"tqp://engines/trust-stack-audit","status":"live"},{"slug":"review-velocity-benchmark","title":"Review Velocity Benchmark","eyebrow":"Local Trust Benchmark","description":"A flagship benchmark engine that scores review momentum, capture rate, freshness, and authority readiness from the pace at which a business turns completed work into public proof.","url":"https://www.thequietprotocol.com/engines/review-velocity-benchmark","apiUrl":"https://www.thequietprotocol.com/api/engines/review-velocity-benchmark","primaryAudience":"Owners, operators, and marketers who need a disciplined read on whether their review system is strong enough for local trust and recommendation surfaces.","idealFor":["Businesses that want to benchmark review growth against real operating volume","Teams trying to strengthen local authority before spending harder on traffic","Operators who know their public proof layer feels quieter than it should"],"leadingQuestions":["Is the business creating enough fresh proof to look active and chosen often?","How much finished work is leaving without producing visible trust signals?","Does the review system look benchmark-strong or quietly underpowered?"],"reportHighlights":["Review velocity score and score band","Capture rate, target monthly reviews, and monthly gap to benchmark pace","Fast wins plus direct handoff into the same audit flow used across the site"],"useCases":["local-authority","reviews","trust-growth","proof-freshness","benchmarking"],"mcpToolName":"run_review_velocity_benchmark","resourceUri":"tqp://engines/review-velocity-benchmark","status":"live"},{"slug":"competitor-intake-scanner","title":"Competitor Intake Scanner","eyebrow":"Competitive Gap Scan","description":"A flagship intake comparison engine that scores how your front door stacks up against a competitor's visible intake posture, urgency handling, proof density, and response readiness.","url":"https://www.thequietprotocol.com/engines/competitor-intake-scanner","apiUrl":"https://www.thequietprotocol.com/api/engines/competitor-intake-scanner","primaryAudience":"Owners, operators, and marketers who know a competitor feels easier to contact or trust and want the gap turned into a scored report.","idealFor":["Businesses losing urgent-response demand to faster or clearer competitors","Operators preparing comparison pages, intake upgrades, or sales-system fixes","Teams that need to see where a rival's front door feels easier to choose"],"leadingQuestions":["Does your competitor make first contact and booking feel easier than you do?","Is their visible proof and urgency handling creating more confidence before the call?","Where is the competitive intake gap actually coming from: speed, clarity, proof, or control?"],"reportHighlights":["Head-to-head intake gap score","Signal-by-signal comparison across response, proof, and urgency handling","Fast wins plus direct handoff into the audit flow"],"useCases":["competitive-gap","comparison-pages","intake-authority","response-readiness","trust-gap"],"mcpToolName":"run_competitor_intake_scanner","resourceUri":"tqp://engines/competitor-intake-scanner","status":"live"},{"slug":"response-time-loss-estimator","title":"Response-Time Loss Estimator","eyebrow":"Speed-to-Lead Math","description":"A flagship estimator that turns lead volume, deal value, and first-response lag into lost bookings, revenue at risk, and a benchmark read on how expensive slow follow-up really is.","url":"https://www.thequietprotocol.com/engines/response-time-loss-estimator","apiUrl":"https://www.thequietprotocol.com/api/engines/response-time-loss-estimator","primaryAudience":"Owners and operators who need to quantify how much slower response times are costing before they change staffing, scripts, or automation.","idealFor":["Home-service and consult-driven businesses with real inbound demand","Teams trying to justify faster callbacks, live coverage, or AI response","Operators who suspect response lag is the invisible leak behind weak booking performance"],"leadingQuestions":["How many bookings are disappearing because the first reply is too slow?","What is that delay costing monthly and annually?","How does your current response time compare with a benchmark pace for the niche?"],"reportHighlights":["Estimated lost bookings per month","Monthly and annual revenue at risk from response lag","Benchmark summary plus direct audit handoff"],"useCases":["speed-to-lead","response-time","lost-bookings","revenue-risk","benchmarking"],"mcpToolName":"run_response_time_loss_estimator","resourceUri":"tqp://engines/response-time-loss-estimator","status":"live"}]}