diff --git a/content/docs/plugins.mdx b/content/docs/plugins.mdx
index f38d5e9..115d977 100644
--- a/content/docs/plugins.mdx
+++ b/content/docs/plugins.mdx
@@ -17,6 +17,30 @@ figures out how to load it based on its shape.
---
+## Service proxies — bring a service into a workspace
+
+A plugin doesn't have to be only a skill or a hook. Because the **MCP server**
+shape lets a plugin wrap an external service, a plugin can act as a *service
+proxy*: install it on a workspace and the agent gains that capability directly —
+no separate website to sign into or configure. The platform's built-in **LLM
+proxy** (platform-managed model routing) is the canonical, shipping example; the
+same mechanism generalises to other services — voice, video generation, search,
+and more — surfaced to the agent as MCP tools (available on MCP-capable runtimes
+today, expanding to more).
+
+Because plugins install **per workspace** and UNION with org defaults, each role
+gets exactly the services it needs, and nothing it doesn't.
+
+
+ **Roadmap — the Molecule Marketplace.** A hosted marketplace where third-party
+ developers publish and sell plugins (including service-proxy plugins) is on the
+ roadmap. Today, plugins install from the platform's curated `local://` registry
+ or from pinned `github://` refs (see [Sources](#sources-where)) — Molecule AI
+ does not yet ship a hosted plugin marketplace.
+
+
+---
+
## Two-Axis Model
### Sources (where)
diff --git a/public/diagrams/platform-architecture.svg b/public/diagrams/platform-architecture.svg
index 3bcfc7d..676dfad 100644
--- a/public/diagrams/platform-architecture.svg
+++ b/public/diagrams/platform-architecture.svg
@@ -1,4 +1,4 @@
-