500-vendor frame & bounded HTTP capture: The study covers 500 unique eligible B2B SaaS domains. Bounded public HTTP discovery (up to 36 requests per vendor, without browser JavaScript execution) classified pricing capture availability as: 253 (50.6%) public numeric paid tiers, 45 (9.0%) public Free/trial terms with opaque paid prices, 43 (8.6%) sales-led or custom pricing only, and 159 (31.8%) with no qualifying pricing surface in the non-JS HTTP archive (which does not mean a live site lacks a JS-rendered pricing page). Across machine-readable paths, 261 of 500 (52.2%) had a saved /llms.txt capture (56 had /llms-full.txt), and 41 of 500 (8.2%) served a content-validated Markdown pricing file (40 at /pricing.md and 1 at /.well-known/pricing.md).
Separate denominators: The uniform single-anchor screen selects one commercial fact per vendor (entry paid base offer; if none is public in capture, core Free allowance; then trial duration). It contains 326 reviewed source contexts for one selected commercial fact per vendor across 124 vendors (110 comparable vendors; 258 aligned, 63 scope ambiguities across 23 vendors: 14 ambiguity-only vendors and 9 with additional aligned contexts, and 5 verified conflicts across 3 vendors: Attio, Slite, and Taskade—3/110 comparable; 3/500 overall). That uniform screen is strictly separate from the selected multi-fact case series (21 verified conflict pairs across 14 vendors). In small reviewed subsets of the uniform screen, Help / Docs showed 1 conflict vendor in 19 comparable (5.3%), Comparison pages 1 in 39 (2.6%), and Machine-readable files 1 in 37 (2.7%)—sample sizes too small to rank one page family across all SaaS sites.
Native AI panel breakdown & non-causality: Across 21 native Google AI Mode and Perplexity observations covering the 21 verified conflict pairs (20 scorable; 1 unscorable missing numerals), 3 repeated a conflicting value, 3 reported multiple values / noted official-page disagreement, 1 separated standard vs. Enterprise role scope, and 13 matched the selected pricing reference. Citation mix across all 21 observations: 7 first-party only, 12 mixed first- and third-party, and 2 third-party only (14 of 21 included third-party citations). Single-session UI observations do not establish model stability or causal proof that a specific page generated an answer.
Archive integrity vs. live product truth: All 663 referenced capture files and all 7 benchmark tables in publication-v7.0-final passed SHA-256 hash and literal-substring checks with 0 errors. Hash verification proves the saved excerpt matches the archived HTTP capture; it does not establish chronological edit history or certify current internal billing behavior without brand-owner confirmation. The 500-domain cohort is a screened convenience frame, not a random sample of all B2B SaaS companies.