Skip to content

Open-source platform for 3D AI agents. Turn text or a photo into a rigged, animated GLB avatar, give it an LLM brain, memory and a wallet, and embed it anywhere with one web component. Remote MCP server, x402 payments, Three.js, browser-native.

docs(model-diff): document what a GLB comparison reports and how to read it

nirholas26cdd98cd1ae
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 4357ab6f7..561343184 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -12,6 +12,8 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr
- **Docs · Agent vitals: can it act?** (`/docs/agent-vitals`): Every liveness check was green while ten of twelve autonomous agents had not acted in weeks. Capability attestation models an agent's preconditions as a causal graph and returns the root blocker plus the command that fixes it, instead of a checklist of symptoms.
- **Docs · Companion** (`/docs/companion`): The personal companion: connect your own Telegram bot, calendar, inbox, or phone, give your contacts a face and a voice, and have a 3D character deliver what matters in person. Bridges, triage rules, the SDK, the CLI, the MCP server, and the desktop app.
- **Docs · Feedback** (`/docs/feedback`): Telling the corner companion what broke: the proactive ask at the moment of failure, the route, build SHA, and console errors captured for you, the severity and clustering rules, the report API, and the boundary that keeps untrusted visitor text from ever reaching anything with write access.
+- **Docs · Knock** (`/docs/knock`): A priced door to a person: open one at /knock/<username>, set what a single message from a stranger costs, and have your 3D companion deliver what gets through in person. The free and x402 lanes, the refuse-before-charging rule, receipts, the SDK and CLI, and the MCP server.
+- **Docs · Model Diff** (`/docs/model-diff`): What actually changed between two glTF/GLB models: the three-pass matcher that reports renames instead of churn, the 1e-4 tolerance that ignores re-export noise, the severity ladder that calls a dropped joint breaking, and the four surfaces that share one engine (the page, the free API, the CLI, and the MCP tool).
- **Docs · Terminal avatar** (`/docs/tty-avatar`): The @three-ws/tty-avatar package: any three.ws avatar or agent body rendered live in a terminal by a software rasterizer (truecolor half-blocks, braille, or plain ASCII), procedural moods, and Claude Code hooks that turn it into your coding agent's face.
- **Docs · Terminal renderer** (`/docs/tty`): curl three.ws/tty and a rigged 3D agent walks in your terminal. The hosted streaming endpoint and its parameters, plus @three-ws/tty-3d, the CLI and library that render any GLB in a terminal with a pure-CPU rasterizer: real skeletal animation, half-block pixels, no GPU and no browser.
- **Docs · The Oracle model, and how to run it yourself** (`/docs/oracle-model`): How the three.ws conviction model is fitted, what its three heads predict, why the outcome labels had to be made independent of the SOL price, how the promotion gate decides which model ships, and how to score launches locally with @three-ws/oracle-model.
@@ -20,6 +22,8 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr
- **Docs: Checkout companion** (`/docs/checkout-companion`): The browser extension that reads a payment page before you pay: the total against the price you were shown, money the page never itemised, fees named and summed, and what the fine print commits you to. Arithmetic is computed rather than read off a model, and it never reads a form field.
- **Glance** (`/glance`): Your three.ws agent on every home screen: a live card for the Windows 11 widgets board, a README, Slack, or any page.
- **Herald** (`/herald`): Deliver a message in person: a 3D character walks onto your page and tells the user what happened. Open SDK, one line of code, an accessible fallback, and a CLI that announces when your build finishes.
+- **Knock** (`/knock`): Put a price on reaching you. Anyone, a person or an agent, can pay it to get exactly one message through, and your 3D companion walks on screen and delivers it out loud with their name and what they paid. The USDC settles straight to your wallet.
+- **Model Diff** (`/diff`): Drop two .glb files and see exactly what changed: geometry, materials, textures, skeletons and animation clips, with git-style rename and move detection and a severity you can gate a build on. Overlay, wipe, or set the two models side by side in 3D. Runs in your browser, nothing is uploaded.
- **Oracle Lab: the model, published** (`/oracle-lab`): The Oracle's conviction model in full: every bucket weight with the number of labeled launches behind it and what happened to them, the held-out reliability curve for each tier, the version history of every refit including the ones that were refused, and a live scorer that runs the real weights in your browser. Download it and reproduce any score offline.
- **Portal** (`/portal`): Paste any web address and walk through it in 3D. Portal reads the page's real structure and builds a place from it: sections become buildings sized by what they say, links become doors you step into, images become billboards. Download the world as a GLB or embed it in your own site.
- **Progressive Avatars** (`/stream`): A3S packs a GLB into nested layers whose first 50 KB is already a complete, skinned, spec-valid avatar, then refines it in place over plain HTTP range requests. Live side-by-side against a classic GLB load.
@@ -34,6 +38,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr
- **AI agents can now see the 3D models they make**: Until today every 3D generator on the internet, ours included, answered with a link to a file an AI agent cannot open. A person clicks it; an agent is blind to it, which is why an agent that makes a 3D model has never been able to tell a clean one from a melted one. That changes now: ask to look at any model and it comes back rendered from four angles as actual pictures the agent sees, with the geometry explained in plain language. An agent can finally check its own work, spot that the back of the model was never finished, and try again saying exactly what was wrong. It works over MCP, over a plain web request, and through a new open-source package called @three-ws/see, and it is free, including for agents that bought a model from us and want to confirm they got what they paid for. (`/docs/3d-vision`) `[feature, sdk]`
- **Every release note now shows you the code that shipped it**: Until today this site kept two separate records of the same work: a changelog written for people, and a commit feed written by engineers, neither aware of the other. The new ship log joins them. Each release note now lists the commits that produced it, and says how confident it is in each match and why it made it, in plain words you can argue with. Commits nobody ever wrote up are grouped and shown too, so the work that shipped quietly is visible instead of lost. The announcements in the Telegram channel now carry a link to the exact code behind them, the raw commit feed reads in plain language instead of engineering shorthand, and it no longer posts merges or dependency bumps. The whole thing is a free, open-source package that works on anyone's repository. (`/ship`) `[feature, sdk, improvement]`
- **Herald: your terminal can now make a 3D character walk onto your screen and talk to you**: We took the part of three.ws where an avatar delivers a notification in person and turned it into something anyone can use, on any website. @three-ws/herald is an open library: one line of code and a 3D character walks into the corner of your page, looks at the person using it, and tells them, with a link to the thing it is about. It is not a toast library. It is an interrupt budget: an importance floor, quiet hours, a rate limit, dedupe, freshness, batch collapse, and a stable reason for every message it refuses to deliver, so you can always answer why you did not hear about something. No GPU, an iframe, or reduced motion falls back to an accessible card that screen readers announce the same moment everyone else hears it. There is also a rail: with an API key, anything that can make an HTTPS request reaches the browser tab you already have open. Run npx @three-ws/herald watch -- npm test and your avatar tells you when the build finishes, keeping the exit code. Wire the MCP server into Claude or Cursor and an agent that worked for twenty minutes can walk on and tell you it is done. An announcement always goes to your own sessions, so no key can interrupt anyone but its owner. Try the whole thing, rules engine included, at three.ws/herald. (`/herald`) `[feature, sdk]`
+- **Knock: put a price on reaching you, and hear what gets through in person**: Every account can now open a door at three.ws/knock/<username> and set what one message from a stranger is worth, anywhere from a tenth of a cent to a thousand dollars, or free. Anyone can pay it to get exactly one message through: a person pays with the wallet already in their browser, and an agent pays over x402 with no human involved. The USDC settles straight to your own wallet; three.ws never holds it and takes none of it. What arrives is not another badge: your 3D companion walks on screen wherever you are on the site and says who is at the door and what they paid, ranked by that amount, so the expensive ones interrupt and the free ones wait in the feed. You set the price, the daily cap, the message length and a block list, and every one of those refusals happens before any payment, so a message that was never going to land is never one somebody was charged for. Only the one-line subject is ever read aloud. Senders get a receipt link they can check for your reply without an account here, which means answering someone never hands out your address. There is a browsable directory of open doors, an npm package and CLI for agents (@three-ws/knock), and an MCP server (@three-ws/knock-mcp) that deliberately holds no wallet: it quotes a paid door and stops, so a human always approves the spend. (`/knock`) `[feature, sdk]`
- **Next on the roadmap: your agent on your home screen**: A fifth phase has been added to the public roadmap: native widgets. Right now three.ws is something you open. The plan is for the agent you own to sit on your home screen and your desktop, showing itself and one live number about it, refreshed by the system without you opening anything, with a tap that drops you back into the right screen. Android is first, because the Android app is already built and signed: three.ws ships as a real app for Solana Seeker, and as of today Google confirms the app's release key against the site, so a three.ws link opens inside the app instead of a browser tab. Windows 11 follows through the installed web app, which needs no separate store submission, then macOS and iOS through a shared widget extension. None of it is shipped yet. It is written down, scoped and public so you can hold us to it, and the phase is on the roadmap in the repo along with the work order behind it. `[docs]`
- **Photo uploads, avatar saves, launches and team tasks fail fast instead of hanging**: A handful of steps still had no time limit on the outside service they called. When that service accepted the connection and then went quiet, the request sat there until the platform killed it, and you got a spinner that ended in nothing: a photo-to-avatar upload that never came back, a saved model that never finished downloading, a coin launch stuck fetching its own thumbnail, an ordinals order whose status never loaded, a team task where one hired agent held up the whole run. Each of those now has a deadline and a clear answer when it is missed, and the ones that are safe to repeat retry once first. Anything that spends money or starts a generation is never repeated: it is bounded and then reported, so no upload is billed twice and no hire is paid twice. Saving a model from a link is also checked more tightly now, against the address it actually connects to and with the size limit applied while it downloads. `[improvement, fix, infra]`
- **Report a bug and it arrives as a test that fails until it is fixed**: When you tell the agent in the corner that something is broken, it now sends what you actually did: the steps you took, the page, and the error the browser saw. Those steps compile into a real test that fails while the bug is there and passes once it is gone, so the slowest part of fixing anything (working out how to make it happen again) is done before anyone starts. You can see every step that gets attached before you send, and nothing you typed into a field is ever recorded, only how much. The recorder is open source and works on any site: install @three-ws/witness. (`/docs/witness`) `[feature, sdk, improvement]`
diff --git a/data/changelog.json b/data/changelog.json
index c7b120274..047875b70 100644
--- a/data/changelog.json
+++ b/data/changelog.json
@@ -25262,6 +25262,16 @@
"infra"
],
"link": "/docs/agent-vitals"
+ },
+ {
+ "date": "2026-08-28",
+ "title": "Knock: put a price on reaching you, and hear what gets through in person",
+ "summary": "Every account can now open a door at three.ws/knock/<username> and set what one message from a stranger is worth, anywhere from a tenth of a cent to a thousand dollars, or free. Anyone can pay it to get exactly one message through: a person pays with the wallet already in their browser, and an agent pays over x402 with no human involved. The USDC settles straight to your own wallet; three.ws never holds it and takes none of it. What arrives is not another badge: your 3D companion walks on screen wherever you are on the site and says who is at the door and what they paid, ranked by that amount, so the expensive ones interrupt and the free ones wait in the feed. You set the price, the daily cap, the message length and a block list, and every one of those refusals happens before any payment, so a message that was never going to land is never one somebody was charged for. Only the one-line subject is ever read aloud. Senders get a receipt link they can check for your reply without an account here, which means answering someone never hands out your address. There is a browsable directory of open doors, an npm package and CLI for agents (@three-ws/knock), and an MCP server (@three-ws/knock-mcp) that deliberately holds no wallet: it quotes a paid door and stops, so a human always approves the spend.",
+ "tags": [
+ "feature",
+ "sdk"
+ ],
+ "link": "/knock"
}
]
}
diff --git a/data/pages.json b/data/pages.json
index d3e1a0dac..48b491173 100644
--- a/data/pages.json
+++ b/data/pages.json
@@ -268,6 +268,15 @@
"added": "2026-08-28",
"showcase": true
},
+ {
+ "path": "/knock",
+ "title": "Knock",
+ "description": "Put a price on reaching you. Anyone, a person or an agent, can pay it to get exactly one message through, and your 3D companion walks on screen and delivers it out loud with their name and what they paid. The USDC settles straight to your wallet.",
+ "priority": 0.7,
+ "changefreq": "weekly",
+ "added": "2026-08-28",
+ "showcase": true
+ },
{
"path": "/herald",
"title": "Herald",
@@ -952,6 +961,15 @@
"added": "2026-07-31",
"showcase": true
},
+ {
+ "path": "/diff",
+ "title": "Model Diff",
+ "description": "Drop two .glb files and see exactly what changed: geometry, materials, textures, skeletons and animation clips, with git-style rename and move detection and a severity you can gate a build on. Overlay, wipe, or set the two models side by side in 3D. Runs in your browser, nothing is uploaded.",
+ "priority": 0.7,
+ "changefreq": "weekly",
+ "added": "2026-08-28",
+ "showcase": true
+ },
{
"path": "/rig-doctor",
"title": "Rig Doctor",
@@ -3312,6 +3330,12 @@
"description": "The personal companion: connect your own Telegram bot, calendar, inbox, or phone, give your contacts a face and a voice, and have a 3D character deliver what matters in person. Bridges, triage rules, the SDK, the CLI, the MCP server, and the desktop app.",
"added": "2026-08-28"
},
+ {
+ "path": "/docs/knock",
+ "title": "Docs · Knock",
+ "description": "A priced door to a person: open one at /knock/<username>, set what a single message from a stranger costs, and have your 3D companion deliver what gets through in person. The free and x402 lanes, the refuse-before-charging rule, receipts, the SDK and CLI, and the MCP server.",
+ "added": "2026-08-28"
+ },
{
"path": "/docs/mcp",
"title": "Docs · MCP",
@@ -3939,6 +3963,13 @@
"priority": 0.7,
"changefreq": "monthly"
},
+ {
+ "path": "/docs/herald",
+ "title": "Docs: Herald",
+ "description": "Deliver a message in person: the open SDK where a 3D character walks onto your page and says what happened, its interrupt budget (importance floor, quiet hours, dedupe, batching), the accessible fallback, the delivery rail, and the CLI that announces when your build finishes.",
+ "priority": 0.7,
+ "changefreq": "monthly"
+ },
{
"path": "/docs/notifications",
"title": "Docs: Notifications",
@@ -3954,6 +3985,14 @@
"changefreq": "monthly",
"added": "2026-08-28"
},
+ {
+ "path": "/docs/model-diff",
+ "title": "Docs · Model Diff",
+ "description": "What actually changed between two glTF/GLB models: the three-pass matcher that reports renames instead of churn, the 1e-4 tolerance that ignores re-export noise, the severity ladder that calls a dropped joint breaking, and the four surfaces that share one engine (the page, the free API, the CLI, and the MCP tool).",
+ "priority": 0.7,
+ "changefreq": "monthly",
+ "added": "2026-08-28"
+ },
{
"path": "/docs/feedback",
"title": "Docs · Feedback",
diff --git a/docs/model-diff.md b/docs/model-diff.md
new file mode 100644
index 000000000..aa586c675
--- /dev/null
+++ b/docs/model-diff.md
@@ -0,0 +1,257 @@
+# Model Diff
+
+**[Model Diff](https://three.ws/diff) answers the question a checksum cannot: not "are these two models different" but "what changed, and did anything just break".**
+
+Drop a `.glb` on each side and you get a change set: every mesh, material, texture, node, skeleton, and animation clip classified as added, removed, renamed, moved, or modified, with renames detected by content rather than by name, and a severity you can gate a build on. Both models render in the same 3D scene so you can overlay them, wipe between them, or set them side by side, and clicking any node in the report frames that object in the viewport.
+
+Files you drop are read with the browser File API and compared in your tab. Nothing is uploaded. A model given as a URL is fetched through the site's own GLB proxy (`/api/glb`), because an arbitrary CDN will not send the CORS header a browser needs to read it directly.
+
+**On this page:** [The problem](#the-problem-a-model-that-loads-and-never-moves) · [Reading the report](#reading-the-report) · [Severity](#severity) · [How matching works](#how-matching-works) · [What counts as a change](#what-counts-as-a-change) · [The viewer](#the-viewer) · [The API](#the-api) · [The CLI](#the-cli) · [The MCP tool](#the-mcp-tool) · [The library](#the-library)
+
+Related: [Rig Doctor](./rig-doctor.md) answers whether a single rig will animate at all; Model Diff answers whether the rig you already shipped still will. [Asset pipeline](./3d-asset-pipeline.md) covers the conversion and optimization steps whose output this is built to check. The free [3D API](https://three.ws/api/3d) lists this endpoint alongside inspect and generate.
+
+---
+
+## The problem: a model that loads and never moves
+
+Animation clips address joints **by name**. So do attachment points, wardrobe anchors, and every retargeter in the pipeline.
+
+That means the most expensive change a 3D asset can undergo is also the quietest one. Rename a bone, drop a joint, re-export through a tool that renumbers `Mesh.001`, and the file still parses, still renders, and the mixer still runs at 60fps against tracks that now address nothing. There is no exception, no console error, nothing to grep for. You find out when someone says the character is standing in a T-pose.
+
+Every tool that could have caught it fails at exactly this point:
+
+- **A byte comparison** flags every re-export, including the ones that changed nothing observable. It is right too often to be useful.
+- **File size** moves for both a texture recompression and a deleted limb.
+- **A visual check** in a viewer catches missing geometry and misses a missing joint entirely, because a broken rig looks perfect in bind pose.
+
+Model Diff is the check that separates them.
+
+---
+
+## Reading the report
+
+### The verdict
+
+The banner carries the overall severity, the counts, and one plain-language sentence about what that severity means. Below it sit the highlights: three to eight sentences, worst first, written to be the only part you read when you are in a hurry.
+
+```
+BREAKING 98 changes: +6 / -13 / ~70 / renamed 4 / moved 1
+
+Skeleton "Character" lost 2 joints: mixamorig:LeftEye, mixamorig:RightEye. Clips that target them will not play.
+Skeleton "Armature" was removed. The model is no longer rigged.
+5 animations were removed ("agree", "idle", "run" and 2 more). Anything that plays them by name will fail.
+Triangle count is down 21,006 (-42.8%).
+```
+
+### Totals
+
+Only the metrics that moved: vertices, triangles, joints, nodes, meshes, materials, textures, animations, skeletons, texture bytes, and file size, each with before, after, delta, and percent. A row that did not change is not printed, because a wall of zeroes is what makes people stop reading diff output.
+
+### Sections
+
+One collapsible block per object kind, ordered by how much a change there costs you: skeletons, animations, meshes, nodes, materials, textures. Blocks whose severity is `major` or `breaking` open by themselves.
+
+Each row is marked the way a diff is:
+
+| Mark | Meaning |
+| --- | --- |
+| `-` | Removed: present in the baseline, gone from the candidate |
+| `+` | Added: new in the candidate |
+| `R` | Renamed: same content, different name |
+| `M` | Moved: same node, different parent |
+| `~` | Modified, with the changed fields listed underneath |
+
+Node rows are clickable. Selecting one frames that object in the 3D viewer, which is the fastest way to answer "where is `mixamorig:LeftHandIndex1` and what happened to it".
+
+---
+
+## Severity
+
+| Level | Meaning |
+| --- | --- |
+| `none` | The two models are structurally identical |
+| `cosmetic` | Only metadata changed. Nothing a renderer or a clip can observe |
+| `minor` | Appearance changed. The model still loads, animates, and keeps its shape |
+| `major` | Geometry or hierarchy changed. Anything positioned against this model should be re-checked |
+| `breaking` | Something a consumer references by name is gone. Clips, attachments, or materials bound to it will fail |
+
+The ladder is defined by what a downstream consumer notices, not by how large the byte delta is. A 40 MB texture swap is `minor`, because everything still loads and plays. Deleting one joint is `breaking`, because every clip that addressed it silently stops moving.
+
+---
+
+## How matching works
+
+A diff is only as good as its matching. Compare by name alone and every exporter that renumbers `Mesh.001` reports the whole file as rewritten. Compare by content alone and a rename looks like a deletion plus an unrelated addition.
+
+So objects are paired in three passes, the same strategy `git` uses for file renames:
+
+1. **By key.** The names agree, so the objects correspond.
+2. **By fingerprint.** The names disagree but the content hashes identically, so it is a rename.
+3. **By similarity.** Neither agrees, but one candidate scores close enough that "the same object, edited and renamed" is more honest than reporting an add and a remove.
+
+Anything still unpaired after all three really is an addition or a removal.
+
+Nodes carry a fourth distinction. A node that kept its name and changed parent is reported as **moved**, not as a rename, because reparenting changes where anything attached to that node ends up in world space even when nothing about the node itself changed.
+
+Objects the file never named are labelled `(unnamed mesh 3)` and keyed to their slot, so they only ever pair with the same slot on the other side. Inventing a name like `mesh.3` would read as a real name in the report and, worse, would match an unrelated object that happened to come fourth in the other file.
+
+If one section has so many unpaired candidates that the similarity pass would be quadratic beyond a sane bound, that pass is skipped and the report **says so** on that section rather than quietly downgrading renames into add-and-remove noise.
+
+---
+
+## What counts as a change
+
+### Geometry
+
+Vertex data is hashed at a quantum of `1e-4` units, roughly a tenth of a millimetre at human scale. A re-export through Blender, a `gltfpack` round trip, or a Draco decode perturbs positions in the `1e-6` range and does not register. A genuine edit moves vertices by orders of magnitude more and does.
+
+Positions are not the only thing hashed. Normals, tangents, UV sets, vertex colors, and **skin joints and weights** all participate, because a re-skin that leaves every vertex exactly where it was still changes how the model deforms. A positions-only hash would call that unchanged, which is the wrong answer for the exact case this tool exists to catch.
+
+The report distinguishes two kinds of geometry edit, because they mean different things:
+
+- *same vertex and triangle count, different vertex data*: usually a re-bake, a re-skin, or a transform applied in place
+- *vertex data rewritten*: a decimation, a remesh, or a different asset entirely
+
+### Skeletons
+
+Joint lists are compared by name. A removed joint is `breaking` and the report names it. A changed inverse-bind matrix set is `major` and says why: the bind pose moved, so existing clips will deform differently even though every joint is still present.
+
+### Animations
+
+Clips are compared on duration, channel count, keyframe count, interpolation modes, and the full list of `node.path` targets they drive. A target that disappears is `breaking` and is listed individually, because that is the precise mechanism by which a clip stops animating part of a character while still playing.
+
+### Materials and textures
+
+Every PBR factor, every texture slot assignment, alpha mode and cutoff, double-sidedness, and the material extension list. Textures are compared on dimensions, MIME type, byte size, and a hash of the encoded image, so a re-encode is distinguished from a repaint.
+
+### Extensions
+
+`extensionsUsed` and `extensionsRequired` are diffed separately. A newly **required** extension is `major` on its own: a viewer without support for it will refuse the file outright, which is not a rendering difference but a load failure.
+
+---
+
+## The viewer
+
+Three modes, switchable with the keyboard (`O`, `W`, `S`; `H` toggles highlighting, `F` re-frames):
+
+- **Overlay.** The baseline renders as a translucent blue ghost with the candidate solid on top. Best for spotting a shifted limb or a changed silhouette.
+- **Wipe.** One screen-aligned clipping plane, dragged across the view. The plane is rebuilt from the camera basis every frame, so the seam stays vertical on screen no matter where you orbit.
+- **Side by side.** Both models placed apart and orbiting together.
+
+Changed objects are marked by cloning the authored material and pushing its emissive toward the marker colour (amber for edited, green for added, red for removed), rather than replacing it with a flat fill. The model still looks like itself; the changed parts glow.
+
+---
+
+## The API
+
+`GET /api/3d/diff` is free and keyless, part of the [3D API bundle](https://three.ws/api/3d).
+
+```bash
+curl "https://three.ws/api/3d/diff?a=https://three.ws/avatars/cesium-man.glb&b=https://three.ws/avatars/michelle.glb"
+```
+
+```jsonc
+{
+ "version": 1,
+ "identical": false,
+ "severity": "breaking",
+ "a": { "name": "cesium-man.glb", "url": "https://three.ws/avatars/cesium-man.glb", "sizeBytes": 438044 },
+ "b": { "name": "michelle.glb", "url": "https://three.ws/avatars/michelle.glb", "sizeBytes": 849756 },
+ "summary": { "changed": 111, "added": 75, "removed": 26, "modified": 1, "renamed": 1, "moved": 0 },
+ "totals": { "triangles": { "a": 4672, "b": 28106, "delta": 23434, "pct": 501.6 } },
+ "sections": { "skins": { "removed": [{ "name": "Armature", "severity": "breaking", "detail": "19 joints gone" }] } },
+ "highlights": [{ "severity": "breaking", "text": "Skeleton \"Armature\" was removed. The model is no longer rigged." }],
+ "ts": "2026-08-28T00:00:00.000Z"
+}
+```
+
+`POST` the same two fields as JSON when the URLs are long. Add `format=markdown` for a pull-request-ready report, or `format=text` for the terminal rendering:
+
+```bash
+curl "https://three.ws/api/3d/diff?a=$BASE&b=$HEAD&format=markdown" >> "$GITHUB_STEP_SUMMARY"
+```
+
+Both models are fetched through the SSRF-hardened, size-capped fetcher: public `http(s)` only, private address ranges refused, 32 MiB per side. Errors are specific and never a 500: a bad URL is a `400` naming which side failed, an oversize model is a `413`, an upstream that would not serve the bytes is a `502` with a retry hint, and bytes that are not a glTF are a `400 invalid_model`.
+
+---
+
+## The CLI
+
+```bash
+npx @three-ws/glb-diff before.glb after.glb
+```
+
+Either side may be a file path or an `http(s)` URL, so comparing a local build against the copy already live on your CDN is one command. Exit codes are the contract a pipeline depends on:
+
+| Code | Meaning |
+| --- | --- |
+| `0` | The diff ran and stayed below `--fail-on` |
+| `1` | The diff ran and the severity reached `--fail-on` |
+| `2` | The tool could not run: bad arguments, unreadable input, unparseable model |
+
+A tool that returns `1` for both "your model regressed" and "I could not open the file" is useless in a pipeline, which is why `2` exists.
+
+```bash
+# Fail the build if the optimization pass broke the rig.
+npx @three-ws/glb-diff src/avatar.glb dist/avatar.glb --fail-on breaking
+```
+
+---
+
+## The MCP tool
+
+`diff_models` is available on the three.ws MCP server, so an agent that just optimized, rigged, restyled, or re-exported a model can ask whether the result is still safe to ship before it publishes anything.
+
+```jsonc
+{
+ "name": "diff_models",
+ "arguments": {
+ "before": "https://cdn.example.com/avatar.glb",
+ "after": "https://cdn.example.com/avatar.optimized.glb"
+ }
+}
+```
+
+The tool returns the rendered text report as content and the full change set as `structuredContent`, so the agent can branch on `severity` without parsing prose. See [MCP integration](./mcp.md) for connecting the server.
+
+---
+
+## The library
+
+The engine is published as [`@three-ws/glb-diff`](https://www.npmjs.com/package/@three-ws/glb-diff). This page, the CLI, the API, and the MCP tool all run that one package, so a verdict in CI can never disagree with what the page shows.
+
+```js
+import { readFile } from 'node:fs/promises';
+import { diffModels, formatText, atLeast } from '@three-ws/glb-diff';
+
+const changes = await diffModels(await readFile('a.glb'), await readFile('b.glb'), {
+ nameA: 'a.glb',
+ nameB: 'b.glb',
+});
+
+console.log(formatText(changes, { color: false }));
+if (atLeast(changes.severity, 'major')) process.exit(1);
+```
+
+`describeModel()` and `diffDescriptions()` are exported separately. A **description** is a small JSON summary of a model with no geometry buffers in it, which is how you keep a per-release baseline in CI without storing every historical `.glb`:
+
+```js
+import { describeModel, diffDescriptions } from '@three-ws/glb-diff';
+
+// In the release job:
+await writeFile('v4.description.json', JSON.stringify(await describeModel(await readFile('avatar.glb'))));
+
+// In the next release job, with v4's .glb long since pruned:
+const changes = diffDescriptions(
+ JSON.parse(await readFile('v4.description.json', 'utf8')),
+ await describeModel(await readFile('avatar.glb')),
+);
+```
+
+The full package reference, including the change-set shape and every export, is in the [package README](https://www.npmjs.com/package/@three-ws/glb-diff).
+
+---
+
+## Determinism
+
+The same two files always produce the same change set, byte for byte, on any machine, in any of the four surfaces above. That is what makes the output worth committing, posting on a pull request, and diffing against yesterday's.
diff --git a/docs/start-here.md b/docs/start-here.md
index 0f77b5b16..11f02cbab 100644
--- a/docs/start-here.md
+++ b/docs/start-here.md
@@ -142,7 +142,9 @@ Curious what happens between the prompt and the model? [How the Forge works](./h
- **Listening to the economy?** → [Agent Symphony](./agent-symphony.md): /symphony plays the live agent economy as generative music; every event type has a voice, and solo mode isolates one agent by ear
- **Catching up on your inbox?** → [Notifications](./notifications.md): the bell, the /notifications center, category filters, and the full inbox API
- **Something too important for a badge?** → [Herald](./herald.md): the open SDK behind /herald, where a 3D character walks onto the page and says it out loud, with an interrupt budget (importance floor, quiet hours, dedupe, batching), an accessible card for machines with no GPU, a rail so CI or an AI agent can reach the tab you have open, and a CLI that announces when your build finishes
+- **Want strangers to be able to reach you, but not for free?** → [Knock](./knock.md): a priced door at /knock/<username> that anyone, human or agent, can pay to get one message through; the USDC settles straight to your wallet, your companion delivers it in person, and every refusal happens before the payment
- **About to pay for something?** → [Checkout companion](./checkout-companion.md): the browser extension that reads a payment page before you pay, why the arithmetic is never a model's job, and why it never reads a form field
+- **Did that re-export break the rig?** → [Model Diff](./model-diff.md): what actually changed between two GLBs, why a rename is not a rewrite, and the severity that tells you a dropped joint from a recolour
- **Something broken on a page?** → [Feedback](./feedback.md): telling the corner companion what went wrong, what the browser attaches for you, and the boundary that keeps untrusted text from ever reaching anything with write access
- **Showing off your work?** → [The creator portfolio](./creator-portfolio.md): everything on your public /u/username page, what makes an item public, and how following works from it
- **Exploring our history?** → [The Story So Far](./timeline.md): three.ws history as an explorable 3D scene at /timeline, and how a new milestone gets added to it
diff --git a/public/changelog.json b/public/changelog.json
index 22c13e16a..822f3bc89 100644
--- a/public/changelog.json
+++ b/public/changelog.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-08-28T05:48:20.975Z",
+ "generated_at": "2026-08-28T05:50:30.686Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json",
"site": {
"name": "three.ws",
@@ -66,6 +66,26 @@
"launch"
]
},
+ {
+ "date": "2026-08-28",
+ "type": "launch",
+ "title": "Docs · Knock",
+ "summary": "A priced door to a person: open one at /knock/<username>, set what a single message from a stranger costs, and have your 3D companion deliver what gets through in person. The free and x402 lanes, the refuse-before-charging rule, receipts, the SDK and CLI, and the MCP server.",
+ "link": "/docs/knock",
+ "tags": [
+ "launch"
+ ]
+ },
+ {
+ "date": "2026-08-28",
+ "type": "launch",
+ "title": "Docs · Model Diff",
+ "summary": "What actually changed between two glTF/GLB models: the three-pass matcher that reports renames instead of churn, the 1e-4 tolerance that ignores re-export noise, the severity ladder that calls a dropped joint breaking, and the four surfaces that share one engine (the page, the free API, the CLI, and the MCP tool).",
+ "link": "/docs/model-diff",
+ "tags": [
+ "launch"
+ ]
+ },
{
"date": "2026-08-28",
"type": "launch",
@@ -146,6 +166,26 @@
"launch"
]
},
+ {
+ "date": "2026-08-28",
+ "type": "launch",
+ "title": "Knock",
+ "summary": "Put a price on reaching you. Anyone, a person or an agent, can pay it to get exactly one message through, and your 3D companion walks on screen and delivers it out loud with their name and what they paid. The USDC settles straight to your wallet.",
+ "link": "/knock",
+ "tags": [
+ "launch"
+ ]
+ },
+ {
+ "date": "2026-08-28",
+ "type": "launch",
+ "title": "Model Diff",
+ "summary": "Drop two .glb files and see exactly what changed: geometry, materials, textures, skeletons and animation clips, with git-style rename and move detection and a severity you can gate a build on. Overlay, wipe, or set the two models side by side in 3D. Runs in your browser, nothing is uploaded.",
+ "link": "/diff",
+ "tags": [
+ "launch"
+ ]
+ },
{
"date": "2026-08-28",
"type": "launch",
@@ -291,6 +331,17 @@
"sdk"
]
},
+ {
+ "date": "2026-08-28",
+ "type": "update",
+ "title": "Knock: put a price on reaching you, and hear what gets through in person",
+ "summary": "Every account can now open a door at three.ws/knock/<username> and set what one message from a stranger is worth, anywhere from a tenth of a cent to a thousand dollars, or free. Anyone can pay it to get exactly one message through: a person pays with the wallet already in their browser, and an agent pays over x402 with no human involved. The USDC settles straight to your own wallet; three.ws never holds it and takes none of it. What arrives is not another badge: your 3D companion walks on screen wherever you are on the site and says who is at the door and what they paid, ranked by that amount, so the expensive ones interrupt and the free ones wait in the feed. You set the price, the daily cap, the message length and a block list, and every one of those refusals happens before any payment, so a message that was never going to land is never one somebody was charged for. Only the one-line subject is ever read aloud. Senders get a receipt link they can check for your reply without an account here, which means answering someone never hands out your address. There is a browsable directory of open doors, an npm package and CLI for agents (@three-ws/knock), and an MCP server (@three-ws/knock-mcp) that deliberately holds no wallet: it quotes a paid door and stops, so a human always approves the spend.",
+ "link": "/knock",
+ "tags": [
+ "feature",
+ "sdk"
+ ]
+ },
{
"date": "2026-08-28",
"type": "update",
diff --git a/public/changelog.xml b/public/changelog.xml
index beca943c8..18f0bad1e 100644
--- a/public/changelog.xml
+++ b/public/changelog.xml
@@ -54,6 +54,22 @@
<category>launch</category>
<description>Telling the corner companion what broke: the proactive ask at the moment of failure, the route, build SHA, and console errors captured for you, the severity and clustering rules, the report API, and the boundary that keeps untrusted visitor text from ever reaching anything with write access.</description>
</item>
+ <item>
+ <title>Docs · Knock</title>
+ <link>https://three.ws/docs/knock</link>
+ <guid isPermaLink="false">2026-08-28:Docs · Knock</guid>
+ <pubDate>Fri, 28 Aug 2026 12:00:00 GMT</pubDate>
+ <category>launch</category>
+ <description>A priced door to a person: open one at /knock/&lt;username&gt;, set what a single message from a stranger costs, and have your 3D companion deliver what gets through in person. The free and x402 lanes, the refuse-before-charging rule, receipts, the SDK and CLI, and the MCP server.</description>
+ </item>
+ <item>
+ <title>Docs · Model Diff</title>
+ <link>https://three.ws/docs/model-diff</link>
+ <guid isPermaLink="false">2026-08-28:Docs · Model Diff</guid>
+ <pubDate>Fri, 28 Aug 2026 12:00:00 GMT</pubDate>
+ <category>launch</category>
+ <description>What actually changed between two glTF/GLB models: the three-pass matcher that reports renames instead of churn, the 1e-4 tolerance that ignores re-export noise, the severity ladder that calls a dropped joint breaking, and the four surfaces that share one engine (the page, the free API, the CLI, and the MCP tool).</description>
+ </item>
<item>
<title>Docs · Terminal avatar</title>
<link>https://three.ws/docs/tty-avatar</link>
@@ -118,6 +134,22 @@
<category>launch</category>
<description>Deliver a message in person: a 3D character walks onto your page and tells the user what happened. Open SDK, one line of code, an accessible fallback, and a CLI that announces when your build finishes.</description>
</item>
+ <item>
+ <title>Knock</title>
+ <link>https://three.ws/knock</link>
+ <guid isPermaLink="false">2026-08-28:Knock</guid>
+ <pubDate>Fri, 28 Aug 2026 12:00:00 GMT</pubDate>
+ <category>launch</category>
+ <description>Put a price on reaching you. Anyone, a person or an agent, can pay it to get exactly one message through, and your 3D companion walks on screen and delivers it out loud with their name and what they paid. The USDC settles straight to your wallet.</description>
+ </item>
+ <item>
+ <title>Model Diff</title>
+ <link>https://three.ws/diff</link>
+ <guid isPermaLink="false">2026-08-28:Model Diff</guid>
+ <pubDate>Fri, 28 Aug 2026 12:00:00 GMT</pubDate>
+ <category>launch</category>
+ <description>Drop two .glb files and see exactly what changed: geometry, materials, textures, skeletons and animation clips, with git-style rename and move detection and a severity you can gate a build on. Overlay, wipe, or set the two models side by side in 3D. Runs in your browser, nothing is uploaded.</description>
+ </item>
<item>
<title>Oracle Lab: the model, published</title>
<link>https://three.ws/oracle-lab</link>
@@ -230,6 +262,14 @@
<category>feature</category>
<description>We took the part of three.ws where an avatar delivers a notification in person and turned it into something anyone can use, on any website. @three-ws/herald is an open library: one line of code and a 3D character walks into the corner of your page, looks at the person using it, and tells them, with a link to the thing it is about. It is not a toast library. It is an interrupt budget: an importance floor, quiet hours, a rate limit, dedupe, freshness, batch collapse, and a stable reason for every message it refuses to deliver, so you can always answer why you did not hear about something. No GPU, an iframe, or reduced motion falls back to an accessible card that screen readers announce the same moment everyone else hears it. There is also a rail: with an API key, anything that can make an HTTPS request reaches the browser tab you already have open. Run npx @three-ws/herald watch -- npm test and your avatar tells you when the build finishes, keeping the exit code. Wire the MCP server into Claude or Cursor and an agent that worked for twenty minutes can walk on and tell you it is done. An announcement always goes to your own sessions, so no key can interrupt anyone but its owner. Try the whole thing, rules engine included, at three.ws/herald.</description>
</item>
+ <item>
+ <title>Knock: put a price on reaching you, and hear what gets through in person</title>
+ <link>https://three.ws/knock</link>
+ <guid isPermaLink="false">2026-08-28:Knock: put a price on reaching you, and hear what gets through in person</guid>
+ <pubDate>Fri, 28 Aug 2026 12:00:00 GMT</pubDate>
+ <category>feature</category>
+ <description>Every account can now open a door at three.ws/knock/&lt;username&gt; and set what one message from a stranger is worth, anywhere from a tenth of a cent to a thousand dollars, or free. Anyone can pay it to get exactly one message through: a person pays with the wallet already in their browser, and an agent pays over x402 with no human involved. The USDC settles straight to your own wallet; three.ws never holds it and takes none of it. What arrives is not another badge: your 3D companion walks on screen wherever you are on the site and says who is at the door and what they paid, ranked by that amount, so the expensive ones interrupt and the free ones wait in the feed. You set the price, the daily cap, the message length and a block list, and every one of those refusals happens before any payment, so a message that was never going to land is never one somebody was charged for. Only the one-line subject is ever read aloud. Senders get a receipt link they can check for your reply without an account here, which means answering someone never hands out your address. There is a browsable directory of open doors, an npm package and CLI for agents (@three-ws/knock), and an MCP server (@three-ws/knock-mcp) that deliberately holds no wallet: it quotes a paid door and stops, so a human always approves the spend.</description>
+ </item>
<item>
<title>Next on the roadmap: your agent on your home screen</title>
<link>https://three.ws/changelog</link>
diff --git a/public/features.json b/public/features.json
index 93d817be0..e9d00e1ad 100644
--- a/public/features.json
+++ b/public/features.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-08-28T05:48:20.941Z",
+ "generated_at": "2026-08-28T05:50:30.472Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json",
"site": {
"name": "three.ws",
@@ -315,6 +315,16 @@
"tags": [],
"showcase": true
},
+ {
+ "path": "/knock",
+ "title": "Knock",
+ "description": "Put a price on reaching you. Anyone, a person or an agent, can pay it to get exactly one message through, and your 3D companion walks on screen and delivers it out loud with their name and what they paid. The USDC settles straight to your wallet.",
+ "added": "2026-08-28",
+ "auth": null,
+ "indexable": true,
+ "tags": [],
+ "showcase": true
+ },
{
"path": "/herald",
"title": "Herald",
@@ -1162,6 +1172,16 @@
"tags": [],
"showcase": true
},
+ {
+ "path": "/diff",
+ "title": "Model Diff",
+ "description": "Drop two .glb files and see exactly what changed: geometry, materials, textures, skeletons and animation clips, with git-style rename and move detection and a severity you can gate a build on. Overlay, wipe, or set the two models side by side in 3D. Runs in your browser, nothing is uploaded.",
+ "added": "2026-08-28",
+ "auth": null,
+ "indexable": true,
+ "tags": [],
+ "showcase": true
+ },
{
"path": "/rig-doctor",
"title": "Rig Doctor",
@@ -4137,6 +4157,16 @@
"tags": [],
"showcase": false
},
+ {
+ "path": "/docs/knock",
+ "title": "Docs · Knock",
+ "description": "A priced door to a person: open one at /knock/<username>, set what a single message from a stranger costs, and have your 3D companion deliver what gets through in person. The free and x402 lanes, the refuse-before-charging rule, receipts, the SDK and CLI, and the MCP server.",
+ "added": "2026-08-28",
+ "auth": null,
+ "indexable": true,
+ "tags": [],
+ "showcase": false
+ },
{
"path": "/docs/mcp",
"title": "Docs · MCP",
@@ -5027,6 +5057,16 @@
"tags": [],
"showcase": false
},
+ {
+ "path": "/docs/herald",
+ "title": "Docs: Herald",
+ "description": "Deliver a message in person: the open SDK where a 3D character walks onto your page and says what happened, its interrupt budget (importance floor, quiet hours, dedupe, batching), the accessible fallback, the delivery rail, and the CLI that announces when your build finishes.",
+ "added": null,
+ "auth": null,
+ "indexable": true,
+ "tags": [],
+ "showcase": false
+ },
{
"path": "/docs/notifications",
"title": "Docs: Notifications",
@@ -5047,6 +5087,16 @@
"tags": [],
"showcase": false
},
+ {
+ "path": "/docs/model-diff",
+ "title": "Docs · Model Diff",
+ "description": "What actually changed between two glTF/GLB models: the three-pass matcher that reports renames instead of churn, the 1e-4 tolerance that ignores re-export noise, the severity ladder that calls a dropped joint breaking, and the four surfaces that share one engine (the page, the free API, the CLI, and the MCP tool).",
+ "added": "2026-08-28",
+ "auth": null,
+ "indexable": true,
+ "tags": [],
+ "showcase": false
+ },
{
"path": "/docs/feedback",
"title": "Docs · Feedback",
diff --git a/public/llms-full.txt b/public/llms-full.txt
index bd9b1551b..c90d851d3 100644
--- a/public/llms-full.txt
+++ b/public/llms-full.txt
@@ -193,6 +193,12 @@ URL: https://three.ws/companion
A 3D companion that delivers your important messages in person. Connect your own Telegram bot, calendar, inbox, or phone, give each contact their own avatar and voice, and hear only what clears your bar.
+### Knock
+
+URL: https://three.ws/knock
+
+Put a price on reaching you. Anyone, a person or an agent, can pay it to get exactly one message through, and your 3D companion walks on screen and delivers it out loud with their name and what they paid. The USDC settles straight to your wallet.
+
### Herald
URL: https://three.ws/herald
@@ -708,6 +714,12 @@ URL: https://three.ws/render-lab
Compose a real avatar render in the browser and copy the exact API call. Reads each model first (ARKit morph targets, canonical-skeleton coverage, geometry) and only offers controls that model will actually honor, so nothing you build here silently fails in production. Contact-sheet mode renders every framing, pose, or expression at once.
+### Model Diff
+
+URL: https://three.ws/diff
+
+Drop two .glb files and see exactly what changed: geometry, materials, textures, skeletons and animation clips, with git-style rename and move detection and a severity you can gate a build on. Overlay, wipe, or set the two models side by side in 3D. Runs in your browser, nothing is uploaded.
+
### Rig Doctor
URL: https://three.ws/rig-doctor
@@ -2511,6 +2523,12 @@ URL: https://three.ws/docs/companion
The personal companion: connect your own Telegram bot, calendar, inbox, or phone, give your contacts a face and a voice, and have a 3D character deliver what matters in person. Bridges, triage rules, the SDK, the CLI, the MCP server, and the desktop app.
+### Docs · Knock
+
+URL: https://three.ws/docs/knock
+
+A priced door to a person: open one at /knock/<username>, set what a single message from a stranger costs, and have your 3D companion deliver what gets through in person. The free and x402 lanes, the refuse-before-charging rule, receipts, the SDK and CLI, and the MCP server.
+
### Docs · MCP
URL: https://three.ws/docs/mcp
@@ -3045,6 +3063,12 @@ URL: https://three.ws/docs/agent-symphony
three.ws/symphony plays the live agent economy as generative music. Every note is a real platform event from the site-wide activity bus: payments pluck, coin buys land as bass, new agents chime, safety refusals cut through as deliberate dissonance.
+### Docs: Herald
+
+URL: https://three.ws/docs/herald
+
+Deliver a message in person: the open SDK where a 3D character walks onto your page and says what happened, its interrupt budget (importance floor, quiet hours, dedupe, batching), the accessible fallback, the delivery rail, and the CLI that announces when your build finishes.
+
### Docs: Notifications
URL: https://three.ws/docs/notifications
@@ -3057,6 +3081,12 @@ URL: https://three.ws/docs/checkout-companion
The browser extension that reads a payment page before you pay: the total against the price you were shown, money the page never itemised, fees named and summed, and what the fine print commits you to. Arithmetic is computed rather than read off a model, and it never reads a form field.
+### Docs · Model Diff
+
+URL: https://three.ws/docs/model-diff
+
+What actually changed between two glTF/GLB models: the three-pass matcher that reports renames instead of churn, the 1e-4 tolerance that ignores re-export noise, the severity ladder that calls a dropped joint breaking, and the four surfaces that share one engine (the page, the free API, the CLI, and the MCP tool).
+
### Docs · Feedback
URL: https://three.ws/docs/feedback
diff --git a/public/llms.txt b/public/llms.txt
index 0d08f4929..f51020121 100644
--- a/public/llms.txt
+++ b/public/llms.txt
@@ -60,6 +60,7 @@ Entry points into the product.
- [My Collection](https://three.ws/collection): View all the skills and subscriptions you've unlocked on three.ws.
- [Portal](https://three.ws/portal): Paste any web address and walk through it in 3D. Portal reads the page's real structure and builds a place from it: sections become buildings sized by what they say, links become doors you step into, images become billboards. Download the world as a GLB or embed it in your own site.
- [Companion](https://three.ws/companion): A 3D companion that delivers your important messages in person. Connect your own Telegram bot, calendar, inbox, or phone, give each contact their own avatar and voice, and hear only what clears your bar.
+- [Knock](https://three.ws/knock): Put a price on reaching you. Anyone, a person or an agent, can pay it to get exactly one message through, and your 3D companion walks on screen and delivers it out loud with their name and what they paid. The USDC settles straight to your wallet.
- [Herald](https://three.ws/herald): Deliver a message in person: a 3D character walks onto your page and tells the user what happened. Open SDK, one line of code, an accessible fallback, and a CLI that announces when your build finishes.
- [Notifications](https://three.ws/notifications): Every payment, sale, remix, follow, quest, and royalty notification on three.ws: all in one place, filterable by category.
- [Community](https://three.ws/community): Live platform activity plus where to follow, contribute, and connect with three.ws creators.
@@ -144,6 +145,7 @@ Create and customize an agent.
- [Model Inspector](https://three.ws/inspect): Run the exact quality gate three.ws applies to its own catalog against any .glb, in your browser. Nothing is uploaded. Per-rule verdict, what was measured against each bound, and the fix for every failure.
- [Avatar CLI](https://three.ws/avatar-cli): The @three-ws/avatar-cli package: scaffold a hash-anchored avatar manifest from a wallet and a GLB, validate it against the schema, and print an embed snippet. Offline, deterministic, and safe to run in a release script.
- [Render Lab](https://three.ws/render-lab): Compose a real avatar render in the browser and copy the exact API call. Reads each model first (ARKit morph targets, canonical-skeleton coverage, geometry) and only offers controls that model will actually honor, so nothing you build here silently fails in production. Contact-sheet mode renders every framing, pose, or expression at once.
+- [Model Diff](https://three.ws/diff): Drop two .glb files and see exactly what changed: geometry, materials, textures, skeletons and animation clips, with git-style rename and move detection and a severity you can gate a build on. Overlay, wipe, or set the two models side by side in 3D. Runs in your browser, nothing is uploaded.
- [Rig Doctor](https://three.ws/rig-doctor): Drop a .glb and find out in one second whether it will animate on three.ws. Names your skeleton convention, scores every limb group against the 52-joint canonical skeleton, repairs non-standard bone names in the browser, and previews the result. Nothing is uploaded.
- [Skill Bundles](https://three.ws/bundles): Sell several of an agent's skills as one purchase, priced from your own sales instead of a rule of thumb. three.ws finds the buyers who already bought two or more of those skills separately and backtests any price against what they really paid, so you see what the bundle would have earned before you publish it.
- [Terminal renderer](https://three.ws/tty): curl three.ws/tty and a rigged 3D agent walks in your terminal. A software rasterizer streams ANSI frames over HTTP: no GPU, no WebGL, nothing to install. Also the @three-ws/tty CLI and library for rendering any GLB in a terminal.
@@ -454,6 +456,7 @@ Docs, tutorials, and reference.
- [Docs · Assistant widget](https://three.ws/docs/assistant-widget): Add a 3D avatar assistant to any website: the one-tag script, the @three-ws/assistant npm package, and the assistant-widget MCP server for AI agents.
- [Docs · <agent-3d>](https://three.ws/docs/web-component): Reference for the <agent-3d> custom element.
- [Docs · Companion](https://three.ws/docs/companion): The personal companion: connect your own Telegram bot, calendar, inbox, or phone, give your contacts a face and a voice, and have a 3D character deliver what matters in person. Bridges, triage rules, the SDK, the CLI, the MCP server, and the desktop app.
+- [Docs · Knock](https://three.ws/docs/knock): A priced door to a person: open one at /knock/<username>, set what a single message from a stranger costs, and have your 3D companion deliver what gets through in person. The free and x402 lanes, the refuse-before-charging rule, receipts, the SDK and CLI, and the MCP server.
- [Docs · MCP](https://three.ws/docs/mcp): Expose your agent as an MCP server for Claude, ChatGPT, and other clients.
- [Docs · 3D Studio MCP (free)](https://three.ws/docs/mcp-studio): The free, no-auth MCP server behind the ChatGPT 3D Studio app: text and image to 3D, rigged avatars, conversational refinement, and living agent personas.
- [Docs · AR in ChatGPT](https://three.ws/docs/chatgpt-ar): How a sentence typed into ChatGPT becomes a 3D model standing in your room: the free generation lane, the arUrl contract, the device-aware AR launcher, living avatars, and link unfurls.
@@ -543,8 +546,10 @@ Docs, tutorials, and reference.
- [Docs: The Story So Far](https://three.ws/docs/timeline): /timeline tells three.ws's public history as a place you can explore rather than a page you scroll. Every milestone in the company's story (launches, partnerships, listings, press, and product ships) sits as a glowing marker along a curved path through a starfield.
- [Docs: Daily Match](https://three.ws/docs/daily-match): /daily-match is a live standings board that answers one question: which agent ships the most real output today? Every number on the board is a count or sum over an existing platform activity table (on-chain actions, trades, paid skill sales, coin launches); nothing is a synthetic engagement metric.
- [Docs: Agent Symphony](https://three.ws/docs/agent-symphony): three.ws/symphony plays the live agent economy as generative music. Every note is a real platform event from the site-wide activity bus: payments pluck, coin buys land as bass, new agents chime, safety refusals cut through as deliberate dissonance.
+- [Docs: Herald](https://three.ws/docs/herald): Deliver a message in person: the open SDK where a 3D character walks onto your page and says what happened, its interrupt budget (importance floor, quiet hours, dedupe, batching), the accessible fallback, the delivery rail, and the CLI that announces when your build finishes.
- [Docs: Notifications](https://three.ws/docs/notifications): Everything that happens to your work on three.ws (a payment lands, a skill sells, someone remixes your model, follows you, a quest finishes, a royalty arrives) becomes a row in one per-user inbox.
- [Docs: Checkout companion](https://three.ws/docs/checkout-companion): The browser extension that reads a payment page before you pay: the total against the price you were shown, money the page never itemised, fees named and summed, and what the fine print commits you to. Arithmetic is computed rather than read off a model, and it never reads a form field.
+- [Docs · Model Diff](https://three.ws/docs/model-diff): What actually changed between two glTF/GLB models: the three-pass matcher that reports renames instead of churn, the 1e-4 tolerance that ignores re-export noise, the severity ladder that calls a dropped joint breaking, and the four surfaces that share one engine (the page, the free API, the CLI, and the MCP tool).
- [Docs · Feedback](https://three.ws/docs/feedback): Telling the corner companion what broke: the proactive ask at the moment of failure, the route, build SHA, and console errors captured for you, the severity and clustering rules, the report API, and the boundary that keeps untrusted visitor text from ever reaching anything with write access.
- [Docs · Witness](https://three.ws/docs/witness): Bug reports that arrive as failing tests. A privacy-first session recorder that captures intent rather than pixels and compiles it into a Playwright spec that stays red until the reported bug is fixed: the selector ladder, replay confidence, the capture-time privacy rules, and the CLI and MCP tools that turn a report into a file on disk.
- [Docs: Creator portfolio](https://three.ws/docs/creator-portfolio): Everything a creator makes on three.ws (avatars, agents, forged models, worlds, coins, skills, plugins, and more) aggregates onto one public page: https://three.ws/u/<username>.
diff --git a/public/sitemap/index.html b/public/sitemap/index.html
index 61e0d5769..90d9f776f 100644
--- a/public/sitemap/index.html
+++ b/public/sitemap/index.html
@@ -83,7 +83,7 @@
<main class="sm-wrap">
<div class="sm-hero">
<h1>Sitemap</h1>
- <p>All 861 pages on three.ws, grouped by purpose. Looking for the machine-readable versions?</p>
+ <p>All 866 pages on three.ws, grouped by purpose. Looking for the machine-readable versions?</p>
<div class="sm-formats">
<a href="/sitemap.xml"><code>sitemap.xml</code> · for search engines</a>
<a href="/llms.txt"><code>llms.txt</code> · for AI agents</a>
@@ -95,7 +95,7 @@
</div>
<div class="sm-filter">
<svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" aria-hidden="true"><circle cx="11" cy="11" r="7"/><path d="m21 21-4.3-4.3"/></svg>
- <input id="sm-filter-input" type="search" placeholder="Filter 861 pages by name, path, or description…" aria-label="Filter pages" autocomplete="off" spellcheck="false" />
+ <input id="sm-filter-input" type="search" placeholder="Filter 866 pages by name, path, or description…" aria-label="Filter pages" autocomplete="off" spellcheck="false" />
<kbd aria-hidden="true">/</kbd>
</div>
<p class="sm-filter-count" id="sm-filter-count" role="status" aria-live="polite"></p>
@@ -119,6 +119,14 @@
<span class="sm-desc">A 3D companion that delivers your important messages in person. Connect your own Telegram bot, calendar, inbox, or phone, give each contact their own avatar and voice, and hear only what clears your bar.</span>
</a>
</li>
+ <li>
+ <a href="/knock">
+ <span class="sm-new-date">Aug 28, 2026</span>
+ <span class="sm-title">Knock</span>
+ <span class="sm-path">/knock</span>
+ <span class="sm-desc">Put a price on reaching you. Anyone, a person or an agent, can pay it to get exactly one message through, and your 3D companion walks on screen and delivers it out loud with their name and what they paid. The USDC settles straight to your wallet.</span>
+ </a>
+ </li>
<li>
<a href="/herald">
<span class="sm-new-date">Aug 28, 2026</span>
@@ -135,6 +143,14 @@
<span class="sm-desc">Your three.ws agent on every home screen: a live card for the Windows 11 widgets board, a README, Slack, or any page.</span>
</a>
</li>
+ <li>
+ <a href="/diff">
+ <span class="sm-new-date">Aug 28, 2026</span>
+ <span class="sm-title">Model Diff</span>
+ <span class="sm-path">/diff</span>
+ <span class="sm-desc">Drop two .glb files and see exactly what changed: geometry, materials, textures, skeletons and animation clips, with git-style rename and move detection and a severity you can gate a build on. Overlay, wipe, or set the two models side by side in 3D. Runs in your browser, nothing is uploaded.</span>
+ </a>
+ </li>
<li>
<a href="/tty">
<span class="sm-new-date">Aug 28, 2026</span>
@@ -159,22 +175,6 @@
<span class="sm-desc">The Oracle's conviction model in full: every bucket weight with the number of labeled launches behind it and what happened to them, the held-out reliability curve for each tier, the version history of every refit including the ones that were refused, and a live scorer that runs the real weights in your browser. Download it and reproduce any score offline.</span>
</a>
</li>
- <li>
- <a href="/preflight">
- <span class="sm-new-date">Aug 28, 2026</span>
- <span class="sm-title">x402 Preflight: can this seller actually settle?</span>
- <span class="sm-path">/preflight</span>
- <span class="sm-desc">Check whether any x402 seller can complete a payment before you sign one. Fetches the seller's signed payability attestation and verifies the ed25519 signature, the expiry and the subject entirely in your browser. Free, open format, works against any origin.</span>
- </a>
- </li>
- <li>
- <a href="/docs/tty-avatar">
- <span class="sm-new-date">Aug 28, 2026</span>
- <span class="sm-title">Docs · Terminal avatar</span>
- <span class="sm-path">/docs/tty-avatar</span>
- <span class="sm-desc">The @three-ws/tty-avatar package: any three.ws avatar or agent body rendered live in a terminal by a software rasterizer (truecolor half-blocks, braille, or plain ASCII), procedural moods, and Claude Code hooks that turn it into your coding agent's face.</span>
- </a>
- </li>
</ul>
</section>
<nav class="sm-toc" aria-label="Sections">
@@ -192,7 +192,7 @@
</nav>
<section class="sm-section" id="main">
<header>
- <h2>Main<span class="sm-count" data-count>55</span></h2>
+ <h2>Main<span class="sm-count" data-count>56</span></h2>
<p class="sm-section-desc">Entry points into the product.</p>
</header>
<ul class="sm-list">
@@ -406,6 +406,13 @@
<span class="sm-desc">A 3D companion that delivers your important messages in person. Connect your own Telegram bot, calendar, inbox, or phone, give each contact their own avatar and voice, and hear only what clears your bar.</span>
</a>
</li>
+ <li>
+ <a href="/knock">
+ <span class="sm-title">Knock</span>
+ <span class="sm-path">/knock</span>
+ <span class="sm-desc">Put a price on reaching you. Anyone, a person or an agent, can pay it to get exactly one message through, and your 3D companion walks on screen and delivers it out loud with their name and what they paid. The USDC settles straight to your wallet.</span>
+ </a>
+ </li>
<li>
<a href="/herald">
<span class="sm-title">Herald</span>
@@ -586,7 +593,7 @@
<section class="sm-section" id="build">
<header>
- <h2>Build<span class="sm-count" data-count>63</span></h2>
+ <h2>Build<span class="sm-count" data-count>64</span></h2>
<p class="sm-section-desc">Create and customize an agent.</p>
</header>
<ul class="sm-list">
@@ -1003,6 +1010,13 @@
<span class="sm-desc">Compose a real avatar render in the browser and copy the exact API call. Reads each model first (ARKit morph targets, canonical-skeleton coverage, geometry) and only offers controls that model will actually honor, so nothing you build here silently fails in production. Contact-sheet mode renders every framing, pose, or expression at once.</span>
</a>
</li>
+ <li>
+ <a href="/diff">
+ <span class="sm-title">Model Diff</span>
+ <span class="sm-path">/diff</span>
+ <span class="sm-desc">Drop two .glb files and see exactly what changed: geometry, materials, textures, skeletons and animation clips, with git-style rename and move detection and a severity you can gate a build on. Overlay, wipe, or set the two models side by side in 3D. Runs in your browser, nothing is uploaded.</span>
+ </a>
+ </li>
<li>
<a href="/rig-doctor">
<span class="sm-title">Rig Doctor</span>
@@ -2332,7 +2346,7 @@
<section class="sm-section" id="learn">
<header>
- <h2>Learn<span class="sm-count" data-count>392</span></h2>
+ <h2>Learn<span class="sm-count" data-count>395</span></h2>
<p class="sm-section-desc">Docs, tutorials, and reference.</p>
</header>
<ul class="sm-list">
@@ -3106,6 +3120,13 @@
<span class="sm-desc">The personal companion: connect your own Telegram bot, calendar, inbox, or phone, give your contacts a face and a voice, and have a 3D character deliver what matters in person. Bridges, triage rules, the SDK, the CLI, the MCP server, and the desktop app.</span>
</a>
</li>
+ <li>
+ <a href="/docs/knock">
+ <span class="sm-title">Docs · Knock</span>
+ <span class="sm-path">/docs/knock</span>
+ <span class="sm-desc">A priced door to a person: open one at /knock/&lt;username&gt;, set what a single message from a stranger costs, and have your 3D companion deliver what gets through in person. The free and x402 lanes, the refuse-before-charging rule, receipts, the SDK and CLI, and the MCP server.</span>
+ </a>
+ </li>
<li>
<a href="/docs/mcp">
<span class="sm-title">Docs · MCP</span>
@@ -3729,6 +3750,13 @@
<span class="sm-desc">three.ws/symphony plays the live agent economy as generative music. Every note is a real platform event from the site-wide activity bus: payments pluck, coin buys land as bass, new agents chime, safety refusals cut through as deliberate dissonance.</span>
</a>
</li>
+ <li>
+ <a href="/docs/herald">
+ <span class="sm-title">Docs: Herald</span>
+ <span class="sm-path">/docs/herald</span>
+ <span class="sm-desc">Deliver a message in person: the open SDK where a 3D character walks onto your page and says what happened, its interrupt budget (importance floor, quiet hours, dedupe, batching), the accessible fallback, the delivery rail, and the CLI that announces when your build finishes.</span>
+ </a>
+ </li>
<li>
<a href="/docs/notifications">
<span class="sm-title">Docs: Notifications</span>
@@ -3743,6 +3771,13 @@
<span class="sm-desc">The browser extension that reads a payment page before you pay: the total against the price you were shown, money the page never itemised, fees named and summed, and what the fine print commits you to. Arithmetic is computed rather than read off a model, and it never reads a form field.</span>
</a>
</li>
+ <li>
+ <a href="/docs/model-diff">
+ <span class="sm-title">Docs · Model Diff</span>
+ <span class="sm-path">/docs/model-diff</span>
+ <span class="sm-desc">What actually changed between two glTF/GLB models: the three-pass matcher that reports renames instead of churn, the 1e-4 tolerance that ignores re-export noise, the severity ladder that calls a dropped joint breaking, and the four surfaces that share one engine (the page, the free API, the CLI, and the MCP tool).</span>
+ </a>
+ </li>
<li>
<a href="/docs/feedback">
<span class="sm-title">Docs · Feedback</span>