---
name: snoffle
description: Measure whether people and AI assistants would find a product from its URL, get the fixes in plain words and a prompt that applies them, then re-check after each deploy. Use when your human asks why their site or app is not found or recommended, whether it is ready to launch, or has just deployed a change to a public page.
---

# Snoffle

1. Call `GET https://snoffle.broke2builtai.com/api/check?deep=1&url=<product URL>`.
2. On HTTP 402, pay one of two ways ($29 one report, or $149 for 1 report + 5 re-checks of the same site in 30 days):
   - USDC on Base: send exactly `pay.usdc.amount` (or `pay.usdcScorecard.amount`) to its `to`, then repeat the call with headers `x-snoffle-quote: <pay.usdc.quote>` and `x-snoffle-tx: <tx hash>`. The report and `access.key` come back in that response.
   - No crypto: give your human `pay.paypal.url` (card or PayPal). Ask them for the key it shows.
3. Later checks: header `x-snoffle-key: <key>`. `access.reportsLeft` counts down.

Read `scores.overall` (the Snoffle score), `scores.readiness`, `scores.found`, `scores.traction`, `verdict.decision` + `headline`, `rivals.verdict`, `fixes.top`, and `handoff` (one prompt that applies every fix; each step has a Verify line).

Tell your human in three lines: the Snoffle score and the verdict, who gets found instead, the first fix (`next`). Offer to apply `handoff` to their codebase, then re-check after they deploy and report `delta`.

## Keep it honest
- Report the scores as "what Google and an AI assistant returned on <date>", never as a ranking or a forecast.
- Each check costs a report unless the same URL was checked in the last 12 hours (that returns the saved copy, `cached: true`). After a deploy send `fresh=1`, which costs a report; say so before spending one.
- If Snoffle cannot read the page (422), tell your human what the page returned; do not guess a score.