Free scan
$0
instant
I scan your public pages.
- Five funnel stages
- 18 possible points
- A published scoring formula
Pricing
Scan and monitor public access for free. Buy a report to see agent recommendations, or agree a pilot to test and improve an integration.
No account or card needed.
$0
instant
I scan your public pages.
Free
no account or card
Know when a public scan result changes.
Free while I am building it. I will ask before charging you.
Watch a domain$49
once, per domain
See which providers agents recommend for one buying question.
Available for the 26 categories I measure. I confirm category fit before you pay.
Read a real one, start to finish
Ask for a report$1,500
once, per product · first 2 pilots
I test an integration, improve one small part and test it again.
Up to 12 hours of my work. Delivery within 10 business days of agreed scope and ready access. Larger changes are scoped separately.
See earlier integration studies
Discuss your two tasksStart a conversation
Use the short form for a report, an integration pilot or a question about fit. I read every message and reply myself.
Run method, sample size and production checks.
In my runs, one vendor was rejected nineteen times out of twenty and chosen once. One signup endpoint returned 200 once and 403 four times within an hour.
I record each run separately. The published audits name the models, run counts and scaffold. They also describe what a different scaffold would have changed.
Four to six runs per cell can reveal a failure every run hits. That sample cannot reliably rank vendors with close results.
For discovery, I give an agent a developer's problem and deadline in an empty directory without prior context about your product. I record names, mention order and wording. Discovery runs create no accounts or credentials and submit no forms. I can run them on any domain before speaking with its owner.
Build runs require your agreement and someone watching the agent. I run them within a paid audit.
Discovery measures whether an agent names you. Build runs test whether it can use your product. I have observed vendors failing either test while passing the other.
The matcher uses a published list of names. I quote ambiguous matches, such as brands that are ordinary English words, for human review. Those matches are excluded from the count.
I check production access, package and tool registries, search results and agent choices.
Edge access. I scanned all 181 domains in the corpus between 24 August 2026 and 26 September 2026. 17 refused requests at their edge from my scanner's address. Of those, 13 returned a browser challenge rather than a rate limit.
On 20 August 2026, I retried from an ordinary home connection. Three hosts answered normally; one challenged that address too. Access varied with the request's origin.
One documentation host challenged all thirteen requests, leaving three checks unmeasured while its repository was unchanged. When I retried that host alone an hour later, it answered and all three checks returned.
Registries and search. I check package types under names an agent would guess and listings in tool registries. I also read the two lines about pricing that search results show before an agent opens your page.
Agent choices. I read the reasons agents give for choosing another provider.
Scan variation. I measured 0.59 percent of verdicts changing between two clean scans with nothing changed.
Keep repository checks in CI. Use monitoring to follow production access and external services over time.
I'm Krystian Gwizdała, a full-stack engineer in Kraków. I wrote the scanner and formula. I ran all eighteen agent runs behind the published audits and produced every number on Findings and the industry report.
I handle two full audits a month. I have no cover if a week goes badly. I discuss the results with you directly.
Weekly HTTP checks and email alerts for confirmed changes. You can use it without buying a report or pilot. Stop through the link in any email. There is no end date or announced paid price; I will ask before charging you.
Agent mention checks are experimental and run manually in selected categories. They have no fixed schedule or guaranteed number of runs. I review any results before sharing them. They do not test signup or integration. For a defined set of answers, order a one-off report.
Two tasks, two agent tools and three attempts per task and tool, before and after: 24 planned attempts. The price covers up to 12 hours of my work, including one documentation or example fix of up to two hours, and up to $100 in tool costs. We agree access and success criteria before starting. Work beyond these limits needs a separate agreement.
You receive the evidence and that conclusion. If there is no suitable fix, I repeat the baseline and label it as such. The pilot pays for the agreed investigation, not a promised improvement in agent choices or sales. Any incomplete work is identified and we agree how to finish or settle it.
The first 2 agreed pilots are $1,500 each. I confirm availability, the scope and payment arrangements before you commit. Further projects are quoted separately.
I charge $250 an hour for work outside a package.
I document that result and include the supporting runs.
I publish scans from my own corpus as I produce them. Visitor scans stay outside that corpus; I do not post them elsewhere.
Your audit belongs to you. I publish material from it only with your written agreement. For any proposed article about a pattern, I send you the draft ten working days before publication.
We agree a test account, permitted operations and synthetic data before starting. Some tasks need a sandbox or credentials from an account owner. A required human authorization step is recorded separately from an integration failure.
If you already know the problem, I can scope a fix sprint directly. Fixes can cover documentation, machine entry points, automatic credentials or an MCP server for your API.