{"slug": "the-web-is-about-to-get-a-second-door", "title": "The Web Is About to Get a Second Door", "summary": "The article announces the emergence of WebMCP, a new structured interface layer for the web designed specifically for AI agents, analogous to ARIA for screen readers. It highlights that AI agent traffic to US retail sites surged 4,700% year-over-year in 2025, and the AI agent market is projected to grow from $7.8 billion to $52.6 billion by 2030. The piece argues that websites must proactively build this machine-readable \"second door\" to remain accessible and competitive as traditional search engine usage declines.", "body_md": "**And most websites aren’t ready for it or even aware it's already happening.**\n\n**Picture this: it’s 2028.**\n\nYou ask your AI assistant to find you the best memory SDK for the agent you’re building. The assistant doesn’t google it. Doesn’t open a browser. It traverses the web through a structured layer, calling APIs, querying tool registries, reading schema definitions, in the time it takes you to pour a coffee. It finds VEKTOR Memory at vektormemory.com. Not because you told it to look there. Because the site had a door built for machines to walk through.\n\nA door that said: “Here are the things I can do. Here is how you use them. Here is what you’ll get back.”\n\nThat door is called WebMCP. It’s about capability declaration at interaction time.\n\n**WebMCP is ARIA for agents that executes.**\n\nARIA (Accessible Rich Internet Applications) is a set of HTML attributes that say: “this button submits a form, this region is navigation, this element is a modal.” Screen readers can’t see. They need the page to declare its structure and intent explicitly, in a form their parsing systems understand. Without ARIA, a screen reader guesses from visual cues — exactly the same failure mode as an AI agent trying to scrape a page.\n\nThe underlying idea is identical: the web was built for sighted humans, so you add a parallel semantic layer that non-visual consumers can parse reliably. One was built for assistive technology. One was built for AI.\n\nAnd we built it into vektormemory.com over the last month. Why?\n\nBecause you can’t stop progress, it’s going to happen whether you implement it or not.\n\nAnd it uses fewer tokens, meaning api costs lowered!\n\nGot your attention now, I know you burn through those tokens…\n\nMythos I need more cookie recipes, faster. Mythos, FASTER!!\n\nAll the cookie recipes will be mine…\n\nMythos: Aren’t we supposed to be debugging and penetration testing the company website?\n\nShoosh, Mythos I’m on my break, I also need my European summer holiday travel itinerary completed and more cookie recipes!\n\nMythos: You are aware I am a supercomputer llm in the Colossus Data centre; you can get cookie recipes from the web…\n\nAnyway here you go, 2780 newly synthesised cookie recipes and 1287 points in your itinerary for Europe, which means you can spend exactly 13 mins in each location.\n\nThe peanut butter pecan with goji berries and matcha swirl is my personal favorite.\n\nWould you like that in a .md file with diagrams?\n\n(No Ai bot could make comedy gold like this?)\n\n**The numbers tell you where this is going**\n\nThere are already 2 layers in motion, one for humans and one for agentic bots, both traversing at the same time. As humans move to full search via LLM, the bots will be doing the legwork to extract the info and provide it back in a more sophisticated and efficient format.\n\nWait till they put adverts into llm’s! Great! (sarcasm) Llm ad blocker, anyone?\n\nAdobe Analytics reported a 4,700% year-over-year increase in traffic from AI agents to US retail sites in 2025. Not a typo. Four thousand, seven hundred percent.\n\nThat’s not a wave comin, that’s a wave already crashing. The AI agent market hit $7.8 billion in 2025 and is projected to reach $52.6 billion by 2030 at a 46.3% CAGR. IDC projects that by the end of 2026, AI copilots will be embedded in 80% of enterprise workplace applications. Gartner predicted traditional search engine volume will drop 25% by 2026 because of AI chatbots and virtual agents.\n\nNone of this means the web disappears. But it does mean the web gets a second interface — one that wasn’t designed for eyes, hands, and scroll wheels. One that was designed for structured reasoning systems that need clarity, precision, and zero ambiguity about what actions are available and what they cost.\n\nThe question facing every developer and every website owner is the same question that faced businesses when mobile browsers appeared: do you build for the new interface now, while it still earns you first-mover advantage? Or do you wait and scramble to catch up later?\n\nWe chose now.\n\n**Why AI agents break on the modern web**\n\nHere’s the fundamental mismatch: the web was designed for humans. Its entire interaction paradigm assumes a visual system, a motor system, and a brain that can disambiguate context with tremendous common sense. “Add to cart” means something because you’re already looking at a product page. You can see the shopping cart icon in the corner. The visual hierarchy guides you naturally.\n\nAn AI agent doesn’t have any of this. When it encounters a webpage, it sees HTML — thousands of lines of markup describing text, styling, layout, meta-information. To interact with a button, it has to:\n\nStep 1: Process the entire HTML document\n\nStep 2: Run vision model inference on the rendered page screenshot\n\nStep 3: Identify which elements look interactive\n\nStep 4: Guess each element’s semantic meaning based on context\n\nStep 5: Predict side effects of clicking\n\nStep 6: Execute, observe the result, adapt, repeat\n\nThis is expensive. It’s slow. It’s brittle. A site redesign, an A/B test, a new checkout flow — any of these can break an agent’s workflow entirely because it was navigating by sight, not by structure.\n\nThe arXiv research paper (Perera, 2025, arXiv:2508.09171) that validated this approach ran 1,890 real API calls across online shopping, authentication, and content management scenarios. The result? Traditional visual scraping methods require staggeringly more compute. WebMCP’s structured approach cuts that processing overhead by 67.6% while maintaining a 97.9% task success rate. Users save 34–63% in API costs for agent-assisted tasks.\n\nThis isn’t a marginal improvement in a footnote. It’s the difference between agents being an expensive curiosity and a viable production infrastructure.\n\n**What WebMCP actually is**\n\nWebMCP (Web Model Context Protocol) is a new W3C web standard co-developed by engineers at Google and Microsoft, formally proposed in August 2025 and entering Chrome’s early preview in February 2026 via Chrome 146.\n\nThe core idea adds more depth for agents: websites expose their functionality as tools—JavaScript functions with natural language descriptions, structured parameter schemas, and defined return types — that AI agents can call directly through a browser-native API called navigator.modelContext.\n\nInstead of guessing, agents ask: “What can I do here?” The website answers explicitly. Instead of simulating a human clicking through a form, an agent calls a structured function and gets a structured response.\n\nThink of it as making your website simultaneously serve two very different users: humans via your visual design, and agents via your tool registry. The HTML, CSS, animations, your brand experience — none of that changes. You’re adding a second door to a building that already has one. Humans use the front door. Agents use the API door. Both get what they need.\n\nWebMCP is positioned as a client-side extension of the Model Context Protocol (MCP) that Anthropic introduced in November 2024. Where traditional MCP operates server-side via JSON-RPC — letting agents talk to databases, APIs, internal tools — WebMCP runs in the browser. The tools live in JavaScript on your site. There’s no separate backend to maintain. The business logic you’ve already written becomes the tool implementation.\n\n**The two ways to implement it**\n\nWebMCP gives developers two implementation paths. Picking the right one depends on the complexity of what you’re exposing.\n\nThe Declarative API is HTML-native. You annotate existing form elements with attributes that describe them to agents:\n\nSearch\n\nThat’s it. The agent sees this and knows it can invoke a search_memories tool with a query parameter. For simple, single-step interactions—a search form, a contact form, a filter interface—the Declarative API gets you WebMCP support in under ten minutes.\n\nThe Imperative API is for complex, multi-step or conditional workflows. You use JavaScript to register tools programmatically:\n\nif (navigator.modelContext) {\n\nnavigator.modelContext.registerTool({\n\nname: \"activate_vektor_license\",\n\ndescription: \"Activates a VEKTOR Memory license key to enable persistent storage and graph wiring\",\n\nparameters: {\n\nlicenseKey: {\n\ntype: \"string\",\n\npattern: \"^[A-F0-9]-XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX$\",\n\ndescription: \"VEKTOR license key in format XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX\"\n\n}\n\n},\n\ncallback: async ({ licenseKey }) => {\n\nconst result = await validateAndActivateLicense(licenseKey);\n\nreturn {\n\nsuccess: result.valid,\n\ntier: result.tier,\n\nmemoryCapacity: result.limits.memories,\n\nmessage: result.message\n\n};\n\n}\n\n});\n\n}\n\nThe Imperative API gives you complete control over validation, state management, error handling, and return shapes. It’s what you reach for when the tool involves conditional logic, multi-step processes, or interactions that need to communicate state back to the agent clearly.\n\nThe key constraint in both cases: tools execute visibly on your page. The user can see what’s happening. This isn’t agents running silent automations in the background — it’s agents working within the same interface humans use, maintaining transparency and user trust.\n\nAlso this is in demo mode, no actual live real database info is being given, the agent is viewing demo info to give back to the user.\n\nThe actual working WebMCP layer instructions:\n\nWrite webmcp.js → /public/webmcp.js\n\nWrite backend routes → /server/routes/webmcp.js\n\nCreate /.well-known/webmcp.json manifest\n\nWrite llms.txt → /public/llms.txt\n\nPatch server/index.js to mount the routes\n\nUpdate robots.txt\n\n✅ GET /api/memory/status → System health pulse (no auth)\n\n✅ POST /api/memory/query → Natural language search\n\n✅ POST /api/memory/store → Write test (requires license format)\n\n✅ POST /api/license/activate → Format validation + capabilities\n\n✅ POST /api/demo/request → Email to [hello@vektormemory.com](mailto:hello@vektormemory.com)\n\n✅ POST /api/compare → Competitor analysis\n\n✅ POST /api/agent/reason → Multi-step reasoning demo\n\n**Why we built this demo info into our website**\n\nVEKTOR Memory is a persistent memory SDK for AI agents. The irony of an agent memory product being unreachable by agents was not lost on us.\n\nBefore WebMCP, if a developer asked Claude to “look up VEKTOR Memory and see if it could help with our project,” Claude would navigate to vektormemory.com, read the visual content, maybe try to extract some relevant text, and return a summary. That interaction is fine. It works. But it’s a one-way transaction: Claude reads the page, summarizes it for you, and that’s it. The agent doesn’t have hands on vektormemory.com. It can’t trial the product. It can’t activate a license. It can’t demonstrate memory recall with a live query. It can only read and report back.\n\n**Plus, it uses a lot of tokens…**\n\nCurrent (Pre-WebMCP) Workflow\n\nAgent evaluating VEKTOR:\n\nWeb search for “VEKTOR memory” → ~500 tokens (search query + results parsing)\n\nFetch vektormemory.com → ~2,000 tokens (HTML, CSS, marketing copy)\n\nParse pricing page → ~800 tokens (extracting actual pricing from messy HTML)\n\nRead docs → ~3,000 tokens (multiple doc pages to understand architecture)\n\nRead comparison articles → ~2,000 tokens (VEKTOR vs Mem0, vs OpenAI, etc.)\n\nSynthesize understanding → ~1,500 tokens (agent thinking/reasoning)\n\nReport back to user → ~500 tokens\n\nTotal: ~10,300 tokens per evaluation\n\n**With WebMCP v2.0.0\nAgent evaluating VEKTOR:**\n\nDiscover .well-known/webmcp.json → ~50 tokens (JSON manifest)\n\nCall query_memory → ~400 tokens (demo results already structured)\n\nCall memory_status → ~200 tokens (JSON metrics, no parsing needed)\n\nCall compare_vektor → ~300 tokens (structured comparison, no scraping)\n\nCall vektor_agent → ~250 tokens (reasoning demo already formatted)\n\nSynthesize understanding → ~400 tokens (agent thinking, but on structured data)\n\nReport back to user → ~400 tokens\n\nTotal: ~2,000 tokens per evaluation\n\nToken Savings: ~80% reduction\n\n**Pre-WebMCP costs:**\n\nHTML parsing (dense, unstructured) → high token overhead\n\nMultiple page fetches → redundant content\n\nNatural language comparison text → requires reasoning to extract\n\nMarketing copy → requires filtering signal from noise\n\nAgent has to synthesize understanding from messy sources\n\nWebMCP costs:\n\nJSON responses (compact, structured) → minimal overhead\n\nSingle endpoint per capability → no page crawling\n\nStructured comparisons → agent reads, doesn’t synthesize\n\nHonest demo mode labels → agent trusts the data\n\nAgent receives understanding, doesn’t extract it\n\nScaling Effect\n\nIf VEKTOR gets 1,000 agents/month evaluating:\n\nIf agents also use VEKTOR in production (storing + querying memories repeatedly), the savings multiply further because WebMCP tools are the primary interaction layer, not a secondary research layer.\n\n**The Real Cost Savings**\n\nThe token math is significant, but the bigger cost is agent time + hallucination risk:\n\nWithout WebMCP: Agent spends 10K+ tokens trying to extract accurate architectural details from marketing-heavy docs, potentially gets confused about:\n\nWhether MAGMA graph really has 4 layers or if that’s marketing speak\n\nWhether 8ms latency is real or best-case\n\nWhat data actually persists vs. what’s demo\n\nHow licensing actually works\n\n→ Results in wrong recommendations or wasted integration time\n\nWith WebMCP: Agent spends 2K tokens, gets:\n\nStructured MAGMA layer visualization\n\nRealistic performance data (8ms p50, 12ms p95)\n\nExplicit “demo mode” labels\n\nDirect contact path\n\n→ Results in accurate evaluations and faster conversions\n\n**Bottom Line**\n\n~80% token reduction per agent evaluation, scaling to $200+/month savings per 1K monthly agents. But more importantly: agents get honest data, make better decisions, waste less time on bad fits, and when VEKTOR IS a fit, they onboard faster with accurate expectations.\n\nWebMCP changes that completely. When an agent visits vektormemory.com now, it finds a machine-readable layer that says: here are things you can do, not just things you can read.\n\n**We deployed seven DEMO tools:**\n\nstore_memory — Agents can demo test writing facts, preferences, or decisions to the VEKTOR memory graph with specified importance weighting and semantic tags. The agent sees the complete MAGMA wiring logic (how semantic, temporal, causal, and entity layers would connect) but no data actually persists — this is validation and showcase, not production storage. Demo mode.\n\nquery_memory — Natural language search demonstrating 8ms recall latency. Agents can ask “what do I know about React hooks?” and get back semantically ranked results from a realistic demo graph. Every result shows which graph layer matched and why. Demo mode.\n\nmemory_status — System health pulse: memory count (8,742), last write timestamp, DB size (24.3 MB), graph edge density (0.73), performance metrics (8ms p50, 12ms p95). Any agent can pull status without authentication. Shows realistic graph structure — 12,841 semantic edges, 8,743 temporal edges, 6,521 causal edges, 9,284 entity edges. Demo mode, but data structure is honest.\n\nactivate_vektor_license — Format validation for license keys (any correctly-formatted UUID passes). Returns capability set (persistent storage, REM cycle compression, multi-agent support, MAGMA graph wiring, WebMCP access). Clear message: “Format validated in demo mode. For real activation with payment, contact [hello@vektormemory.com](mailto:hello@vektormemory.com) or visit [https://vektormemory.com/product](https://vektormemory.com/product).\"\n\nrequest_vektor_demo — Agents submit name, email, intended use case, and AI provider. Emails [hello@vektormemory.com](mailto:hello@vektormemory.com) with all details and reply-to address. Returns confirmation with expected response time (24 hours). No calendar system, no scheduling API — just email-based contact. Simple, direct, honest.\n\ncompare_vektor — Takes a competitor name (Mem0, OpenAI Memory, etc.) and returns structured comparison: architecture, latency, privacy, pricing, offline capability, graph wiring, WebMCP support. Designed for agent research. Includes a verdict (e.g., “VEKTOR wins on privacy, latency, and cost”) and links to docs.\n\nvektor_agent — The most powerful tool. Takes a natural language goal and returns a reasoning flow: parse intent → search semantic layer → traverse causal edges → rank by temporal recency → synthesize response. Shows the multi-step reasoning architecture. Returns demo synthesis with clear label: “This is demo reasoning. Live reasoning requires persistent graph installation.” This is the core VEKTOR value proposition — not simple vector search, but graph-based multi-step reasoning — delivered as a callable tool that demonstrates the capability without executing on real data.\n\nThe net effect: any agent that visits vektormemory.com can now evaluate the product, trial the core functionality, understand the architecture, research competitors, and request a demo — without the user ever leaving their conversation window. Every tool is labeled demo mode. Every tool includes contact email and documentation links. Every tool returns honest capability descriptions and realistic data structures.\n\n**The Future Possibilities:**\n\nThe agent doesn’t need to leave the chat.\n\nThis is the part that matters for the developer ecosystem.\n\nIf you’re building with Claude, ChatGPT, or any agent framework, your agents now have a path to discover and interact with VEKTOR Memory that doesn’t require pre-configuration. You don’t need to install an MCP server. You don’t need to add VEKTOR to your agent’s tool registry. You don’t need to write integration code.\n\nYou tell your agent: “I want to understand if VEKTOR Memory is right for my use case.” The agent — if it has browser capabilities — navigates to vektormemory.com, discovers the seven WebMCP tools via the .well-known/webmcp.json manifest, calls query_memory to test search performance, calls store_memory to understand the writing interface, calls compare_vektor to research competitors, and calls request_vektor_demo to book a conversation with the team.\n\nAll of this happens in the chat window. The agent returns an accurate evaluation: “Here’s what VEKTOR does well, here’s where it might not fit your needs, and here’s how to get started if it’s a match.”\n\nThis is the vision of agent-native software: products that don’t need to be explicitly integrated to be discoverable or usable. Products that make themselves available to reasoning systems through structured, machine-readable interfaces that are honest about their capabilities.\n\nWebMCP is the discovery and interaction protocol. VEKTOR’s demo tools are the implementation — carefully designed to show real architecture, realistic performance, actual limitations, and a clear path to real usage.\n\nThe llms.txt file we deployed to vektormemory.com/llms.txt is the companion piece. Where WebMCP handles structured tool interaction, llms.txt handles discoverability — it’s a plain text file that tells AI crawlers exactly what VEKTOR is, what it does, and what tools are available. It’s indexed by the same systems that power Claude’s web search, ChatGPT browsing, and Perplexity.\n\nThe combination means VEKTOR is findable by agents even before they visit the site, and fully evaluable once they do.\n\n**What changes in practice**\n\nFor developers actively building agent infrastructure, this changes several practical workflows.\n\nEvaluation: Instead of manually testing a memory SDK by writing integration code, your agent can trial the core functionality on the product site in demo mode. Query performance, search interface design, response shapes, competitive positioning — all evaluable without setup code. The agent gets an honest picture: “This is a demo, but here’s how the production system would work.”\n\nArchitecture understanding: Rather than reading documentation, agents can call vektor_agent with a question about multi-step reasoning and see the actual reasoning flow returned — parse → semantic search → causal traversal → temporal ranking → synthesis. Understanding MAGMA graph architecture becomes concrete rather than theoretical.\n\nCompetitive research: Agents conducting tool comparison research get structured, accurate differentiation data from compare_vektor instead of trying to extract it from marketing copy. The comparison is designed for agent consumption and includes honest assessments (“VEKTOR wins on privacy and cost; you lose vendor lock-in concerns; latency is faster”).\n\nDemo booking: Demo requests flow directly to [hello@vektormemory.com](mailto:hello@vektormemory.com) with full context (use case, AI provider, agent name) embedded in the email. No calendar system — just immediate, accountable contact.\n\nResearch before purchase: An agent can evaluate whether VEKTOR fits a use case before a human ever needs to download anything. The evaluation is based on realistic data, honest limitations, and actual performance characteristics. A developer gets a recommendation from their agent: “Use VEKTOR if you need offline-capable, local-first memory with structured graph reasoning. Skip it if you need cloud sync or team collaboration features.”\n\nFor product teams integrating VEKTOR into their agent infrastructure, WebMCP also means clearer onboarding. Users interact with VEKTOR-powered features through agents without needing to understand memory graph internals. The agent mediates the complexity. The tool schemas enforce validation. And critically — agents can evaluate fit before integration, reducing wasted implementation effort.\n\n**The uncomfortable truth about web design**\n\nThere’s a harder implication underneath all of this, one worth naming directly.\n\nA substantial portion of web design over the last twenty years was optimized for human visual processing. Dark patterns, friction-by-design, information hidden behind seven clicks, pricing buried in comparisons — these design choices work because humans are finite attention systems who give up. Agents don’t give up. They’re tireless, systematic, and they read the terms of service.\n\nWebMCP, by making sites machine-readable, makes them accountable to machine scrutiny. A site that hides its cancellation flow three levels deep might be navigable by a human who eventually finds it — but to an agent with a WebMCP tool called cancel_subscription, the friction disappears. The agent calls the tool and it’s done.\n\nThis will be painful for some business models. It will be clarifying for product teams who actually want to serve users well. If your product is good, agents discovering it, evaluating it accurately, and using it when it fits is pure upside. If your product relies on user confusion to function, WebMCP is an existential concern.\n\nVEKTOR has one position here: we want agents to find us, evaluate us honestly in demo mode, and use us when we’re the right fit. If we’re not the right fit for a given use case, we’d rather an agent tell a user that clearly than have them waste time with a bad integration.\n\n**The seven tools we exposed are designed around transparency:**\n\nHonest capability descriptions (“DEMO: this is demo mode, here’s what production would do”)\n\nRealistic performance metrics (8ms actual latency, real graph edge counts)\n\nClear limitations (format validation only for license activation; no data persistence in store_memory)\n\nDirect contact path (email to [hello@vektormemory.com](mailto:hello@vektormemory.com), not hidden behind scheduling systems)\n\nStructured comparisons (agent-readable competitive analysis with verdicts)\n\nAn agent that evaluates VEKTOR should come away with an accurate picture — positive or negative. And crucially, they should come away knowing exactly how to move from evaluation to real usage: contact [hello@vektormemory.com](mailto:hello@vektormemory.com), visit [https://vektormemory.com/docs](https://vektormemory.com/docs), or install vektor-slipstream locally for offline-first persistent memory.\n\nThat’s the bet we’re making on agent-native software: that transparency and honest capability descriptions are better long-term than friction-by-design. That agents discovering us accurately is better than users fumbling through dark patterns. That a clear “this might not be right for you” is better than a misleading trial that wastes their time.\n\n**The timeline you need to know**\n\nWebMCP moved from independent proposals at Microsoft, Google, and Amazon to a W3C Community Group Draft in under nine months. Chrome 146 shipped early preview support in February 2026. Edge and other Chromium-based browsers are following. A stable cross-browser release is coming.\n\nThe standard is still a W3C Community Group Draft, not a full W3C Recommendation — the API surface could change. Implementers should be prepared for iteration. But the direction is clear, the momentum is real, and the co-sponsorship of two of the world’s largest browser vendors means this isn’t an experimental sketch that gets abandoned.\n\nThe developer opportunity window is right now. Early implementations get indexed by AI crawlers as they train on the new web. Agents that use Chrome 146+ Canary for browsing already discover WebMCP tools. The sites that build for this now will be the sites that agents know how to use fluently when WebMCP hits stable release and browser support becomes universal.\n\n**For the builders**\n\nIf you build websites or developer tools, here’s the practical picture.\n\nWebMCP requires no backend changes. You ship JavaScript. You annotate forms. You register tools. The .well-known/webmcp.json manifest file tells agents what tools exist before they even load your page. The llms.txt file makes your site's capabilities discoverable at the AI crawler level.\n\nImplementation time for a simple site: a few hours. For a complex product with multi-step workflows: a few days, most of it designing the tool schemas and testing interaction patterns with real agents.\n\nThe install cost is low. The ceiling is high. Any product that currently requires a human to navigate a UI to accomplish a task can potentially expose that task as a WebMCP tool — making it accessible to the billions of agent-assisted interactions that are already happening, and the tens of billions more that are coming.\n\n**The web has always had two modes**\n\nThere’s a frame that makes all of this feel less dramatic than the headlines suggest.\n\nThe web has always had two modes. There’s the human mode — visual, gestural, experiential. And there’s the machine mode — crawlers, scrapers, API consumers, RSS readers. SEO is the discipline of making your site work well in machine mode. Schema.org markup, sitemap.xml, robots.txt, structured data — these are all ways of saying “here is what this site means, in a form a machine can reason about.”\n\nWebMCP is SEO for agent-native interactions. It’s the discipline of making your site work well for the new generation of machine visitors — not crawlers indexing content, but reasoning systems taking actions.\n\nThe sites that invested in structured data in the early 2010s ranked better in search. The sites that invest in WebMCP tool quality in 2026 will be discovered and used more fluently by agents. The technical debt is the same on both sides: sites that ignore it don’t break, they just become progressively less visible to the systems that matter.\n\nVEKTOR Memory was built for agents from the ground up — local-first memory graphs, sub-10ms recall, causal graph wiring designed for multi-turn reasoning. Having agents discover and use VEKTOR through a structured protocol they were designed to speak natively is the logical next step in that mission.\n\n**The second door is open.**\n\nvektormemory.com — persistent memory for AI agents.\n\nWebMCP manifest: [https://vektormemory.com/.well-known/webmcp.json](https://vektormemory.com/.well-known/webmcp.json)\n\nDiscovery file: [https://vektormemory.com/llms.txt](https://vektormemory.com/llms.txt)\n\nDocumentation: [https://vektormemory.com/docs](https://vektormemory.com/docs)\n\nSources: Adobe Analytics (2025), arXiv:2508.09171 (Perera, Aug 2025), Salesforce Research (2025), IDC 2026 forecast, Gartner (Feb 2024), McKinsey Global Institute (2025), developer.chrome.com/docs/ai/webmcp, github.com/webmachinelearning/webmcp\n\nWebMCP, AI Agents, Web Development, LLM, Agent Architecture, Agentic AI, API Design, Developer Tools, W3C Standards, Token Optimization, AI Memory, Semantic Search\n\n**Bonus Content: Checklist to Help Implement**\n\nDrop into llm and Reconfigure to Your Web/VPS Situation:\n\nWebMCP Build & Testing Checklist\n\nFor Teams Building Agent-Native Products with WebMCP\n\nLesson learned from VEKTOR: Single-LLM validation is not enough. Always test with multiple LLMs and validate discovery + functionality across different agent environments.\n\n**Phase 1: Build & Manifest**\n\nManifest Creation\n\nCreate /.well-known/webmcp.json at your domain root\n\nInclude all required fields:\n\nschema_version: \"1.0\"\n\nname (product name)\n\ndescription (what you do, key claims)\n\nurl (product website)\n\ncontact (support email)\n\nmodes array (at least [\"demo\"] or [\"demo\", \"production\"])\n\ndefaultMode (current environment)\n\ndocsUrl (root docs link)\n\ntools array (all endpoints)\n\nPer-Tool Definition\n\nFor EACH tool, verify:\n\nname (unique identifier)\n\ndescription (what it does, key metrics if demo)\n\nurl (absolute path to endpoint)\n\nmethod (GET/POST/PUT)\n\nparameters (JSON Schema with required, properties, patterns)\n\noutputSchema (JSON Schema for response shape)\n\ndocsUrl (anchor link to specific tool docs, e.g. #query_memory)\n\nmodes (which environments this tool works in)\n\nInput Validation\n\nAll required fields have required: [...] in parameters\n\nUUID/email/enum fields have regex patterns or format validators\n\nNumeric fields have min/max bounds\n\nString fields have maxLength constraints\n\nOptional fields have sensible defaults\n\nOutput Documentation\n\noutputSchema matches actual API responses\n\nAll response fields are typed (string, number, object, array)\n\nObjects have nested property definitions\n\nArrays specify item schema\n\nSpecial fields documented (mode, operation, latencyMs)\n\nDemo Mode Labeling\n\nAll responses include mode: \"demo\" or mode: \"production\" field\n\nManifest declares which modes apply (per-tool)\n\nRoot-level defaultMode tells agents current state\n\nDocs explain what demo means (no persistence, fake data, etc.)\n\nDocumentation\n\nllms.txt created at root (plaintext index)\n\nLists all tools with HTTP paths and descriptions\n\nIncludes contact email and docsUrl\n\nExplains demo vs production (if applicable)\n\nPer-tool docs exist (anchor links from manifest match real sections)\n\n**Phase 2: Implementation & Deployment**\n\nEndpoint Implementation\n\nAll tools return valid JSON (not HTML, not empty)\n\nAll responses include required fields (success, operation, mode, docsUrl, contactEmail)\n\nError responses are JSON (not 500 HTML)\n\nHTTP status codes are correct (200 for success, 400 for validation, 401 for auth, 403 for permission)\n\nCORS headers allow cross-origin calls (Access-Control-Allow-Origin: *)\n\nSecurity & Rate Limiting\n\nRate limiting enforced per IP/user (at least for mutations)\n\nLicense validation enforces format (if applicable)\n\nSensitive data not logged (passwords, tokens, keys)\n\nNo hardcoded credentials in public code\n\nSSL/TLS enforced (HTTPS only)\n\nDeployment\n\nManifest is served from /.well-known/webmcp.json (correct path)\n\nllms.txt served from /llms.txt (correct path)\n\nAll endpoints respond with 200/correct status codes\n\nContent-Type headers correct (application/json for manifest/endpoints, text/plain for llms.txt)\n\nNginx/proxy properly configured to serve static files and proxy API calls\n\nCDN or caching is aware of manifest (avoid stale responses)\n\nMetrics & Observability\n\nDemo endpoints return realistic metrics (numeric, not strings)\n\nStatus endpoint includes measurement metadata (timestamps, sampleSize, measurement_window)\n\nLatency metrics include percentiles (p50, p95, p99)\n\nAll numeric claims are verifiable (not marketing-only)\n\n**Phase 3: Single-LLM Validation**\n\n(Perplexity/Claude/Gemini/Openai/Grok)\n\nDiscovery Testing\n\nPerplexity can fetch and parse /.well-known/webmcp.json\n\nPerplexity can fetch and parse /llms.txt\n\nAll 7 (or your count) tools are listed in manifest\n\nAll tool paths and methods are correct\n\nManifest Validation\n\nRoot-level fields present: name, contact, docsUrl, modes, defaultMode\n\nAll tools have: name, url, method, parameters, outputSchema, docsUrl, modes\n\nContact email matches across manifest and responses\n\nJSON is valid (Perplexity can parse it)\n\nEndpoint Testing\n\nPerplexity can call each endpoint (non-destructive)\n\nResponses are valid JSON\n\nResponses include mode: “demo” or mode: “production”\n\nResponses include docsUrl and contactEmail\n\nNo 403/500 errors on GET endpoints\n\nSchema Validation\n\nInput schemas are well-formed JSON Schema\n\nOutput schemas are well-formed JSON Schema\n\nRequired fields documented\n\nPatterns/validation rules enforced\n\nDefaults provided where applicable\n\nScore & Gaps\n\nPerplexity scores your manifest (example: 7/10)\n\nPerplexity identifies gaps (missing docsUrl, outputSchema, modes)\n\nPerplexity validates metrics (realistic, verifiable)\n\nPerplexity notes edge/WAF issues (if any)\n\nSign-off: Perplexity produces validation report with score\n\n**Phase 4: Patch & Improve (Based on Single-LLM Feedback)**\n\nAddress All Gaps\n\nAdd per-tool docsUrl (if missing)\n\nAdd per-tool outputSchema (if missing)\n\nAdd modes declaration (if missing)\n\nAdd root-level docsUrl (if missing)\n\nFix any HTTP status code issues\n\nFix any response format issues\n\nRe-Deploy\n\nCopy updated manifest to production\n\nVerify manifest is live (curl it)\n\nAll tools have docsUrl\n\nAll tools have outputSchema\n\nAll tools have modes\n\nSign-off: Updated manifest deployed, Perplexity confirms improvements\n\n**Phase 5: Second-LLM Validation (Gemini, Claude, etc.)**\n\nIndependent Testing\n\nSecond LLM fetches manifest independently\n\nSecond LLM scores manifest (should match or improve on first LLM score)\n\nSecond LLM tests same endpoints\n\nSecond LLM validates same requirements\n\nComparative Validation\n\nDoes second LLM find the same gaps as first? ✅ (confidence +)\n\nDoes second LLM find NEW gaps first LLM missed? ⚠️ (check if real)\n\nDoes second LLM agree on metrics realism? ✅ (confidence +)\n\nDoes second LLM have different concerns? ℹ️ (document for future)\n\nScore Comparison\n\nFirst LLM: 7/10 → 9/10 (after patch)\n\nSecond LLM: Should be 9/10+ (if patch was effective)\n\nDifference > 1 point: Investigate why (different testing approach, different standards)\n\nSign-off: Second LLM produces independent validation report\n\n**Phase 6: Cross-LLM Agent Testing**\n\nReal-World Agent Scenarios\n\nClaude agent can discover tools via .well-known/webmcp.json\n\nPerplexity agent can discover and call tools\n\nGemini agent can discover and call tools\n\nOther agents (ChatGPT, Grok, open-source) can discover tools\n\nFunctionality Testing\n\nAgents can validate input against inputSchema\n\nAgents can validate output against outputSchema\n\nAgents understand demo mode (don’t expect persistence)\n\nAgents navigate to docsUrl for tool help\n\nAgents contact if they need help\n\nEdge Case Testing\n\nWhat happens if agent sends invalid input?\n\nWhat happens if endpoint returns 403 (WAF block)?\n\nWhat happens if outputSchema is missing?\n\nWhat happens if docsUrl is broken?\n\n**Phase 7: Documentation & Public Launch**\n\nPublic Validation Results\n\nPublish Perplexity’s validation report (score, findings)\n\nPublish Gemini’s validation report (score, findings, comparison)\n\nCreate “WebMCP Integration” badge/certification\n\nDocument known issues and workarounds (e.g., WAF blocks)\n\nAgent Ecosystem Integration\n\nRegister manifest with WebMCP registry (if exists)\n\nEnsure llms.txt is indexed by search agents\n\nMonitor /.well-known/webmcp.json for agent traffic\n\nTrack adoption by LLM (Claude, Perplexity, Gemini, etc.)\n\nOngoing Maintenance\n\nMonitor endpoint response times (latency claims must be accurate)\n\nUpdate outputSchema if API response changes\n\nAdd new tools to manifest and llms.txt\n\nFix any WAF/edge issues that appear\n\nRe-validate with LLMs after major changes\n\nChecklist Summary\n\nPhaseStatusOwnerDate\n\nBuild & Manifest⏳Dev —\n\nImplementation & Deploy⏳DevOps —\n\nSingle-LLM Validation (Perplexity)⏳QA —\n\nPatch & Improve⏳Dev —\n\nSecond-LLM Validation (Gemini)⏳QA —\n\nCross-LLM Agent Testing⏳QA —\n\nLaunch & Maintenance⏳PM —\n\nKey Learnings (From VEKTOR)\n\nWhat Worked\n\nManifest-first approach (define before implement)\n\nPer-tool docsUrl and outputSchema (agent UX)\n\nDemo mode declaration in manifest (agents know upfront)\n\nRealistic metrics with percentiles (verifiable, not marketing)\n\nMultiple LLM validation (confidence)\n\nWhat to Watch\n\nWAF can block legitimate tool paths (whitelist WebMCP traffic)\n\nHTTP status codes matter (agents validate responses)\n\nCORS headers critical for discovery (cross-origin calls)\n\nResponse consistency matters (all tools should follow same schema)\n\nllms.txt must be discoverable (agent indexing depends on it)\n\nBest Practices\n\nAlways validate with multiple LLMs — Single validation is insufficient\n\nTest discovery before functionality — Manifest first, then endpoints\n\nDeclare demo mode in manifest — Don’t make agents infer it\n\nInclude realistic metrics — 8ms latency claims need percentiles\n\nKeep docs fresh — docsUrl must always point to current docs\n\nMonitor agent traffic — Track which LLMs discover and use your tools\n\nIterate on feedback — First validation is rarely perfect (7/10 → 9/10)\n\nVersion: 1.0\n\nLast Updated: 2026–05–23\n\nWeb Development\n\nAI Agent\n\nAgentic Ai\n\nLLM", "url": "https://wpnews.pro/news/the-web-is-about-to-get-a-second-door", "canonical_source": "https://dev.to/vektor_memory_43f51a32376/the-web-is-about-to-get-a-second-door-2g53", "published_at": "2026-05-23 03:06:07+00:00", "updated_at": "2026-05-23 03:33:51.016806+00:00", "lang": "en", "topics": ["artificial-intelligence", "developer-tools", "web3"], "entities": ["VEKTOR Memory", "WebMCP", "ARIA"], "alternates": {"html": "https://wpnews.pro/news/the-web-is-about-to-get-a-second-door", "markdown": "https://wpnews.pro/news/the-web-is-about-to-get-a-second-door.md", "text": "https://wpnews.pro/news/the-web-is-about-to-get-a-second-door.txt", "jsonld": "https://wpnews.pro/news/the-web-is-about-to-get-a-second-door.jsonld"}}