Welcome to SaaS 2.0: How AI Agents Connect to and Control Every Website in My Portfolio
SaaS 2.0 websites expose both a fast human UI and a permissioned protocol layer (/llms.txt, /.well-known/agent-gate.json, /.well-known/ucp, and WebMCP) so AI agents inspect, query, and stage checkouts without scraping HTML.
Embedded Slide Deck Breakdown (7 Slides)
- Slide 1: SaaS 1.0 built screens for human clicks; SaaS 2.0 builds typed capabilities alongside the human UI.
- Slide 2: Layer 1 Context — /llms.txt, /get-started.md, and Accept: text/markdown (.md) twins cut crawler token waste.
- Slide 3: Layer 2 Governance — /.well-known/agent-gate.json (SlateSwitch) declares open, lead-gate, and productized tiers.
- Slide 4: Layer 3 Execution — /wp-json/webmcp/v1/tools + browser navigator.modelContext expose live catalog schemas.
- Slide 5: Layer 4 Commerce — /.well-known/ucp stages pre-filled human-confirmed checkout links (paid: false).
- Slide 6: Connected Portfolio — All Clear Digital, Chris Slater AI, OneFront, and ClipMaster share one protocol spine.
- Slide 7: 4-Step Upgrade Path — Ship llms.txt, agent-gate.json, WebMCP read tools, and UCP checkout handoff.
SaaS 2.0 (the agent-controllable web) is an application architecture in which a website exposes both a fast visual interface for human visitors and a deterministic, permissioned protocol surface—combining /llms.txt, /.well-known/agent-gate.json, /.well-known/ucp, and browser-native WebMCP—so autonomous AI agents can discover, query, and prepare transactions without scraping HTML.
1. Why SaaS 1.0 Websites Break When AI Agents Arrive
Traditional SaaS 1.0 websites assume every visitor is a human clicking menus inside a browser viewport. When coding agents, research assistants, or shopping agents visit a screen-only site, they waste tokens parsing layout chrome, trigger bot blocks, and lack typed primitives to verify live pricing or stage a cart.
2. SaaS 1.0 vs. SaaS 2.0 Architecture Comparison
| Capability Layer | SaaS 1.0 (Human-Only Web) | SaaS 2.0 (Live Portfolio Stack) |
|---|---|---|
| Site Discovery | XML sitemaps + HTML nav menus | /llms.txt + /get-started.md + XML sitemaps |
| Article Reading | Full HTML DOM parsing | SSR HTML + JSON-LD + Accept: text/markdown (.md twins) |
| Agent Access Rules | All-or-nothing robots.txt / WAF blocks |
/.well-known/agent-gate.json (open, lead-gate, productized) |
| Tool Execution | Brittle Playwright / headless DOM clicks | /wp-json/webmcp/v1/tools + navigator.modelContext |
| Checkout Handoff | Manual human form entry from scratch | /.well-known/ucp + pre-filled cart URL (paid: false human confirmation) |
3. Walking Through the 4 Live Layers on chrisslater.ai & All Clear Digital
/.well-known/agent-gate.json(SlateSwitch Governance): Declaresschema_version: "2026-11-14", supported presets (open,lead-gate,productized), handshake endpoints on allcleardigital.com, and available WebMCP tools./wp-json/webmcp/v1/tools&navigator.modelContext: Exposes Model Context Protocol (2024-11-05) tools over REST and registers them in-browser so agents callsite.list_productsagainst live WooCommerce inventory./.well-known/ucp(Universal Commerce Protocol v1.0): Publishes checkout session endpoints and human-authorized redirect handlers so agents stage carts withpaid: falsewhile humans authorize payment.- Markdown Twins & Structured Entity Graphs: Pairs clean
.mdtwins withPerson,BlogPosting, andFAQPageJSON-LD, aligning with Princeton & Georgia Tech KDD 2024 Generative Engine Optimization findings on structured factual authority.
Explore the $495 Agentic Engine Optimization (AEO) + MCP Starter Code Blueprint → | Run a Free 30-Second AI Readiness Scan →
Frequently Asked Questions
What does SaaS 2.0 mean for normal business websites?
It means your website stops being a passive digital brochure that only humans can click. A SaaS 2.0 website keeps its fast human storefront while adding structured discovery (/llms.txt and /.well-known/agent-gate.json) and typed tools (WebMCP) so AI assistants can accurately read your offers, check availability, and hand a ready-to-pay checkout link to your customer.
Does letting AI agents connect to my site allow them to charge credit cards without permission?
No. POST /wp-json/webmcp/v1/checkout and /.well-known/ucp enforce a human-in-the-loop boundary: the agent validates the SKU and generates a pre-populated checkout URL with paid: false. The human buyer opens that link and completes payment through standard PCI-compliant gateways.
Can WordPress or WooCommerce sites support SaaS 2.0 without a total rewrite?
Yes. chrisslater.ai runs a hybrid WordPress + React 19 architecture where WooCommerce powers catalog state and encrypted deliverable fulfillment while lightweight PHP route handlers serve /.well-known/agent-gate.json, /.well-known/ucp, and /wp-json/webmcp/v1/* in milliseconds.
About Chris Slater & Website Architecture Services
Chris Slater builds fast, machine-readable websites and AI search systems from Nokomis, Florida through All Clear Digital. Start with a manual $149 AI Visibility Snapshot (delivered in 48 hours), a 50-query $750 AI Search Visibility Audit, or a full Website Rebuild (Theme-Level Hybrid, Decoupled React Hybrid, or Full-Stack Application Build with zero PHP).
Running WordPress or PHP? Test your domain with the free PHP2Shell Exposure Checker (a version indicator) or read Move Off PHP: From the October 2 Warning to the October 21 NSA Advisory. Because the checker relies on version headers, backported builds and hidden headers mean it cannot prove a site is or isn’t exposed.