01Public reachability
Status, redirects, content type, timing, bounded body hash, and the exact observer identity.
Public experiment · verifiable method · open results
Can a buyer agent
verify your SaaS?
ProofSurface checks the public evidence path between a product claim and an agent’s ability to qualify it—without pretending a successful request proves discovery, use, or influence.
Surface Snapshot v0.1Live
One repeatable starting point
Same method. Any public SaaS domain.
The online snapshot records response facts and selected metadata for eleven fixed paths. A full S0 adds controlled buyer-agent evaluations and owner-only evidence.
02Buyer evidence routes
Pricing, security, privacy, and terms are checked separately—never blended into a score.
03Discovery surfaces
robots.txt, sitemap, homepage metadata, structured data, and conventional agent resources.
04Explicit boundaries
Every report says what was observed, what is interpretation, and what remains unknown.
The evidence ladder
One request is not seven proofs.
ProofSurface keeps each state separate so a vendor can fix the actual break in the path.
- 01PreparedThe resource exists and has a declared purpose.
- 02ReachableA named observer received it at a recorded time.
- 03ObservedA real external platform requested it.
- 04IngestedThe platform incorporated that version.
- 05RetrievedThe platform surfaced it for a task.
- 06UsedThe answer demonstrably relied on it.
- 07InfluentialIt changed an answer or buying decision.
Disclosed reference SaaS
Signmos S0 is the first public baseline.
Auditmos operates both ProofSurface and Signmos. The case tests the method against a real product; it is not independent customer validation.
11fixed paths
4returned 200
7returned 404
0client-status differences