🔍 Federated documentation search
One query, fifteen vendors. The mesh fans your query out across every source in parallel, merges the results by relevance, and returns them with the full provenance trail: which vendor, which version, the canonical URL, the license, and when it was last updated. Filter by vendor when you already know whose docs you need.
{ "query": "edge functions env vars",
"vendors": ["netlify", "vercel"],
"limit": 5 }
{ "vendor": "netlify",
"title": "Environment variables",
"heading_path": "Build > …",
"source_url": "https://docs.netlify.com/…",
"license": "Netlify Docs (llms.txt)",
"last_updated": "2026-08-30",
"score": 274.66 }
🩺 Errors-to-Docs Bridge
Paste any stack trace or error log. The bridge extracts error signatures — exception classes, k8s state reasons, errno codes, exit codes — and matches them against the index, returning the three closest official documentation sections with a fix sketch. Crucially, it declines to guess: every answer carries an explicit disclaimer that this is a closest-match, not a diagnosis, and unknown errors return labeled "closest matches" rather than confident nonsense.
Input: Warning Failed kubelet Back-off restarting failed container…
Error: CrashLoopBackOff: container failed to start
Output: signatures: ["CrashLoopBackOff", …]
matches:
1. kubernetes — "How Pods handle problems with containers"
→ Container restart policy (score 252.4)
https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/
2. netlify — "Fix a failed deploy"
🏷 Version awareness
Kubernetes docs are indexed per release branch (v1.32, v1.29) — so a question about pod lifecycle returns both versions side-by-side, letting you spot behavioral changes between releases. Every answer names its version. This is the anti-"2021 blog post" feature: the mesh grounds answers in the exact version you run.
search: "container restart policy"
kubernetes v1.32 → "Container restart policy" score 252.4
kubernetes v1.29 → "Container restart policy" score 236.4
↑ same section, two releases — diffs become visible
⚖️ License-aware ingestion
Ingestion is gated on legality, not convenience. Vendors enter the mesh only via (a) permissive licenses (CC-BY-4.0, MIT, Apache-2.0) or (b) official agent interfaces (llms.txt, `.md` endpoints) that explicitly permit machine consumption. Vendors with unclear or restrictive terms — Terraform (BUSL), Grafana (AGPL) — are deliberately excluded. Every single response names its license; the coverage page documents both sides of that line.
🤖 Fully agent-operable
Everything above is exposed as WebMCP tools — structured, schema-described
capabilities registered in the page via document.modelContext.registerTool().
A visitor's existing agent (ChatGPT in the in-app browser, or any MCP-compatible agent in Chrome)
discovers and calls them directly. The human sees the same cited sources on screen —
collaboration, not automation.