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(publishing): record the keeper article review and rewrite the CoinMarketCap launch article

nirholas56250d200675
diff --git a/data/x-content/reviews/keeper-article.json b/data/x-content/reviews/keeper-article.json
new file mode 100644
index 000000000..c68a78a7a
--- /dev/null
+++ b/data/x-content/reviews/keeper-article.json
@@ -0,0 +1,1171 @@
+{
+ "id": "keeper-article",
+ "contentHash": "c3c3ed488eb83447507a562f2c1d740c6144a6faee0c62fb85b80491747764b9",
+ "reviewedAt": "2026-10-08T05:00:00.455Z",
+ "passed": false,
+ "blockers": [
+ "evidence:page https://three.ws/api/version: live page does not show \"\"commitShort\":\"76081013b\"\"",
+ "spelling CVPR: did you mean cspr, CSPR, cvar?",
+ "spelling mixamorig: did you mean mixamo?",
+ "spelling canonicalizer: did you mean canonicalize, canonicalized, canonicalizes?",
+ "spelling viseme: did you mean vise, vised, vises?",
+ "spelling blendshapes: not a known word; add it to the queue glossary if it is correct",
+ "editor (accuracy): The article asserts the idle defect is unfixed on production and the fix is not yet deployed, anchored to commit 76081013b. The verification probe against https://three.ws/api/version failed: the live site does not report that commit. Either the fix has already deployed (making the defect disclosure and the image choice wrong) or the version evidence is wrong. A failed verification on a claim about the current live state must not publish.",
+ "editor verdict is revise"
+ ],
+ "texts": [
+ "One sentence to a rigged, talking 3D character in 197 seconds: each stage, as it ran",
+ "We sent one sentence to the free three.ws MCP server and got back a rigged 3D lighthouse keeper in 197 seconds: 22,500 triangles, a 52-joint skeleton with every finger, 52 facial expression shapes. The article follows that one job through each stage, including the two that failed that morning and the fallbacks that caught them."
+ ],
+ "lint": [],
+ "verification": {
+ "ok": false,
+ "checks": [
+ {
+ "claim": "in 197 seconds",
+ "kind": "evidence:file",
+ "target": "data/x-content/runs/keeper-article.json",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "in 197 seconds",
+ "kind": "evidence:file",
+ "target": "data/x-content/runs/keeper-article.json",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "On the morning of 8 October",
+ "kind": "evidence:file",
+ "target": "data/x-content/runs/keeper-article.json",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "No account, no key",
+ "kind": "evidence:file",
+ "target": "docs/mcp-studio.md",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "No account, no key",
+ "kind": "evidence:file",
+ "target": "data/x-content/runs/keeper-article.json",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "22,500 triangles",
+ "kind": "evidence:file",
+ "target": "data/x-content/runs/keeper-article.json",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "22,500 triangles",
+ "kind": "evidence:file",
+ "target": "data/x-content/runs/keeper-article.json",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "a 52-joint skeleton with every finger",
+ "kind": "evidence:file",
+ "target": "data/x-content/runs/keeper-article.json",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "a 52-joint skeleton with every finger",
+ "kind": "evidence:file",
+ "target": "data/x-content/runs/keeper-article.json",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "a 52-joint skeleton with every finger",
+ "kind": "evidence:file",
+ "target": "workers/rig/README.md",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "52 facial expression shapes",
+ "kind": "evidence:file",
+ "target": "data/x-content/runs/keeper-article.json",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "52 facial expression shapes",
+ "kind": "evidence:file",
+ "target": "workers/rig/README.md",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "a full PBR material",
+ "kind": "evidence:file",
+ "target": "data/x-content/runs/keeper-article.json",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "a full PBR material",
+ "kind": "evidence:file",
+ "target": "data/x-content/runs/keeper-article.json",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "Four seconds after that he was a named persona with a stable id",
+ "kind": "evidence:file",
+ "target": "data/x-content/runs/keeper-article.json",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "Four seconds after that he was a named persona with a stable id",
+ "kind": "evidence:file",
+ "target": "data/x-content/runs/keeper-article.json",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "a third of a second after that he had spoken his opening line",
+ "kind": "evidence:file",
+ "target": "data/x-content/runs/keeper-article.json",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "a third of a second after that he had spoken his opening line",
+ "kind": "evidence:file",
+ "target": "data/x-content/runs/keeper-article.json",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "Every call, every timing and the server's own record of each job are written down in a run file that ships with the platform",
+ "kind": "evidence:file",
+ "target": "data/x-content/runs/keeper-article.json",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "Every call, every timing and the server's own record of each job are written down in a run file that ships with the platform",
+ "kind": "evidence:file",
+ "target": "docs/x-content-pipeline.md",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "returns a rigged, animation-ready GLB in one call",
+ "kind": "evidence:file",
+ "target": "api/_mcp-studio/tools.js",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "returns a rigged, animation-ready GLB in one call",
+ "kind": "evidence:file",
+ "target": "docs/mcp-studio.md",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "a sentence that clearly names an object (a chair, a dog, a sword) is turned away before any GPU time is spent, with a message pointing to the mesh generator instead",
+ "kind": "evidence:file",
+ "target": "api/_mcp-studio/tools.js",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "a sentence that clearly names an object (a chair, a dog, a sword) is turned away before any GPU time is spent, with a message pointing to the mesh generator instead",
+ "kind": "evidence:file",
+ "target": "api/_mcp-studio/tools.js",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "A director model turns the sentence into a brief",
+ "kind": "evidence:file",
+ "target": "api/_mcp-studio/tools.js",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "the mesh stage took 100 seconds and the rig stage 12.6 seconds",
+ "kind": "evidence:file",
+ "target": "data/x-content/runs/keeper-article.json",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "the mesh stage took 100 seconds and the rig stage 12.6 seconds",
+ "kind": "evidence:file",
+ "target": "data/x-content/runs/keeper-article.json",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "the mesh stage took 100 seconds and the rig stage 12.6 seconds",
+ "kind": "evidence:file",
+ "target": "data/x-content/runs/keeper-article.json",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "rewriting the sentence, painting the picture, storing each intermediate file and polling the workers",
+ "kind": "evidence:file",
+ "target": "data/x-content/runs/keeper-article.json",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "rewriting the sentence, painting the picture, storing each intermediate file and polling the workers",
+ "kind": "evidence:file",
+ "target": "api/_mcp-studio/tools.js",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "a portrait-leaning model tends to answer a description of a person with a head and shoulders, and a bust cannot be rigged into anything that walks",
+ "kind": "evidence:file",
+ "target": "api/_mcp-studio/tools.js",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "The language models it calls were rate limiting at that moment",
+ "kind": "evidence:file",
+ "target": "data/x-content/runs/keeper-article.json",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "The language models it calls were rate limiting at that moment",
+ "kind": "evidence:file",
+ "target": "data/x-content/runs/keeper-article.json",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "a fixed fallback brief is appended to the raw words, stating the framing the director would have asked for",
+ "kind": "evidence:file",
+ "target": "api/_mcp-studio/tools.js",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "a fixed fallback brief is appended to the raw words, stating the framing the director would have asked for",
+ "kind": "evidence:file",
+ "target": "api/_mcp-studio/tools.js",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "That is the fallback, word for word",
+ "kind": "evidence:file",
+ "target": "api/_mcp-studio/tools.js",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "That is the fallback, word for word",
+ "kind": "evidence:file",
+ "target": "data/x-content/runs/keeper-article.json",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "costs polish, never the body",
+ "kind": "evidence:file",
+ "target": "api/_mcp-studio/tools.js",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "as one centered subject on a plain seamless background under soft even light",
+ "kind": "evidence:file",
+ "target": "api/_lib/forge-reference-image.js",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "set almost entirely by the realism of that one reference picture",
+ "kind": "evidence:file",
+ "target": "api/_lib/forge-reference-image.js",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "A Gemini image model on Vertex AI leads it, because it draws the most photoreal reference",
+ "kind": "evidence:file",
+ "target": "api/_mcp3d/text-to-image.js",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "This morning that rung was refusing requests, so the picture came from FLUX.1-dev, further down the ladder",
+ "kind": "evidence:file",
+ "target": "data/x-content/runs/keeper-article.json",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "This morning that rung was refusing requests, so the picture came from FLUX.1-dev, further down the ladder",
+ "kind": "evidence:file",
+ "target": "data/x-content/runs/keeper-article.json",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "This morning that rung was refusing requests, so the picture came from FLUX.1-dev, further down the ladder",
+ "kind": "evidence:file",
+ "target": "api/_lib/forge-reference-image.js",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "No single provider's failure is the end of a picture",
+ "kind": "evidence:file",
+ "target": "api/_mcp3d/text-to-image.js",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "Avatars ask for the high tier, and at the high tier the router sends a job to Hunyuan3D 2.1 on our own worker",
+ "kind": "evidence:file",
+ "target": "api/_mcp-studio/tools.js",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "Avatars ask for the high tier, and at the high tier the router sends a job to Hunyuan3D 2.1 on our own worker",
+ "kind": "evidence:file",
+ "target": "api/_lib/forge-tiers.js",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "Avatars ask for the high tier, and at the high tier the router sends a job to Hunyuan3D 2.1 on our own worker",
+ "kind": "evidence:file",
+ "target": "data/x-content/runs/keeper-article.json",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "Avatars ask for the high tier, and at the high tier the router sends a job to Hunyuan3D 2.1 on our own worker",
+ "kind": "evidence:page",
+ "target": "https://model-hunyuan3d-21-rtx-93741856042.us-central1.run.app/health",
+ "ok": true,
+ "detail": "live page shows \"\"model\":\"hunyuan3d-2.1\"\""
+ },
+ {
+ "claim": "a Cloud Run service with an NVIDIA RTX PRO 6000 Blackwell attached",
+ "kind": "evidence:page",
+ "target": "https://model-hunyuan3d-21-rtx-93741856042.us-central1.run.app/health",
+ "ok": true,
+ "detail": "live page shows \"\"gpu_name\":\"NVIDIA RTX PRO 6000 Blackwell Server Edition\"\""
+ },
+ {
+ "claim": "builds the geometry, then runs a separate pass that paints a full PBR material set rather than one baked colour map",
+ "kind": "evidence:page",
+ "target": "https://three.ws/blog/image-to-3d-on-nvidia-l4-and-blackwell",
+ "ok": true,
+ "detail": "live page shows \"Hunyuan3D 2.1 runs a shape DiT for geometry, then a separate PBR paint pass\""
+ },
+ {
+ "claim": "builds the geometry, then runs a separate pass that paints a full PBR material set rather than one baked colour map",
+ "kind": "evidence:page",
+ "target": "https://three.ws/blog/image-to-3d-on-nvidia-l4-and-blackwell",
+ "ok": true,
+ "detail": "live page shows \"Hunyuan3D 2.0 gives you a mesh with a single baked diffuse texture.\""
+ },
+ {
+ "claim": "one material carrying four maps: base colour, metallic and roughness, normal, and ambient occlusion",
+ "kind": "evidence:file",
+ "target": "data/x-content/runs/keeper-article.json",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "one material carrying four maps: base colour, metallic and roughness, normal, and ambient occlusion",
+ "kind": "evidence:file",
+ "target": "data/x-content/runs/keeper-article.json",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "one material carrying four maps: base colour, metallic and roughness, normal, and ambient occlusion",
+ "kind": "evidence:file",
+ "target": "data/x-content/runs/keeper-article.json",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "one material carrying four maps: base colour, metallic and roughness, normal, and ambient occlusion",
+ "kind": "evidence:file",
+ "target": "data/x-content/runs/keeper-article.json",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "22,500 triangles across 16,388 vertices",
+ "kind": "evidence:file",
+ "target": "data/x-content/runs/keeper-article.json",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "the job would have moved to the next engine under the same job id: our TRELLIS worker, a hosted TRELLIS lane, then TripoSG",
+ "kind": "evidence:file",
+ "target": "api/_lib/forge-failover.js",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "the job would have moved to the next engine under the same job id: our TRELLIS worker, a hosted TRELLIS lane, then TripoSG",
+ "kind": "evidence:file",
+ "target": "api/_lib/forge-failover.js",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "That chain was not needed on this run",
+ "kind": "evidence:file",
+ "target": "data/x-content/runs/keeper-article.json",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "at the high tier, with a longer sentence of our own. It returned a model in 108 seconds",
+ "kind": "evidence:file",
+ "target": "data/x-content/runs/keeper-article.json",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "at the high tier, with a longer sentence of our own. It returned a model in 108 seconds",
+ "kind": "evidence:file",
+ "target": "data/x-content/runs/keeper-article.json",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "That tool renders any public GLB on the server from several angles and returns the frames as images",
+ "kind": "evidence:file",
+ "target": "api/_mcp-studio/tools.js",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "The geometry count agreed: 8,464 triangles",
+ "kind": "evidence:file",
+ "target": "data/x-content/runs/keeper-article.json",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "is the subject complete and recognisable, is the far side finished, is anything melted, fused or missing",
+ "kind": "evidence:file",
+ "target": "api/_mcp-studio/tools.js",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "is the subject complete and recognisable, is the far side finished, is anything melted, fused or missing",
+ "kind": "evidence:file",
+ "target": "api/_mcp-studio/tools.js",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "generate again with a prompt that names the specific fault",
+ "kind": "evidence:file",
+ "target": "api/_mcp-studio/tools.js",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "turns one-shot generation into a loop",
+ "kind": "evidence:file",
+ "target": "api/_mcp-studio/tools.js",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "look_at_model is marked read-only",
+ "kind": "evidence:file",
+ "target": "api/_mcp-studio/tools.js",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "it works on any public GLB, wherever it was made",
+ "kind": "evidence:file",
+ "target": "api/_mcp-studio/tools.js",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "a Cloud Run service on an NVIDIA L4 running Make-It-Animatable",
+ "kind": "evidence:page",
+ "target": "https://model-rig-lp642k3kpa-uc.a.run.app/health",
+ "ok": true,
+ "detail": "live page shows \"\"model\":\"make-it-animatable\"\""
+ },
+ {
+ "claim": "a Cloud Run service on an NVIDIA L4 running Make-It-Animatable",
+ "kind": "evidence:page",
+ "target": "https://model-rig-lp642k3kpa-uc.a.run.app/health",
+ "ok": true,
+ "detail": "live page shows \"\"gpu_name\":\"NVIDIA L4\"\""
+ },
+ {
+ "claim": "released under the MIT licence and published at CVPR 2025",
+ "kind": "evidence:file",
+ "target": "workers/rig/README.md",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "predicts joint positions, skinning weights and pose for a 52-bone Mixamo skeleton, fingers included, in under a second of GPU time",
+ "kind": "evidence:file",
+ "target": "workers/rig/README.md",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "It is used as a predictor and nothing more",
+ "kind": "evidence:file",
+ "target": "workers/rig/README.md",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "writes the skeleton, the per-vertex joint indices and weights, and the inverse bind matrices straight into the original GLB bytes",
+ "kind": "evidence:file",
+ "target": "workers/rig/README.md",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "its materials and PBR textures are preserved byte for byte",
+ "kind": "evidence:file",
+ "target": "workers/rig/README.md",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "transfers the 52 ARKit expression shapes from an open template head onto the avatar's face, written as glTF morph targets",
+ "kind": "evidence:file",
+ "target": "workers/rig/README.md",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "transfers the 52 ARKit expression shapes from an open template head onto the avatar's face, written as glTF morph targets",
+ "kind": "evidence:file",
+ "target": "workers/rig/README.md",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "diagnoses a GLB in the browser without uploading it",
+ "kind": "evidence:page",
+ "target": "https://three.ws/rig-doctor",
+ "ok": true,
+ "detail": "live page shows \"Nothing is uploaded.\""
+ },
+ {
+ "claim": "Every limb group mapped",
+ "kind": "evidence:file",
+ "target": "workers/rig/README.md",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "Every limb group mapped",
+ "kind": "evidence:file",
+ "target": "data/x-content/runs/keeper-article.json",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "Every clip in it is authored against one canonical skeleton: Hips, LeftForeArm, RightUpLeg, 52 joints in total",
+ "kind": "evidence:page",
+ "target": "https://three.ws/rig-doctor",
+ "ok": true,
+ "detail": "live page shows \"Every clip in the three.ws library is authored against one canonical skeleton: Hips, LeftForeArm, RightUpLeg, 52 joints in total.\""
+ },
+ {
+ "claim": "Every clip in it is authored against one canonical skeleton: Hips, LeftForeArm, RightUpLeg, 52 joints in total",
+ "kind": "evidence:module",
+ "target": "src/glb-canonicalize.js",
+ "ok": true,
+ "detail": "CANONICAL_BONES has 52 entries; the claim needs 52"
+ },
+ {
+ "claim": "a track that names LeftForeArm drives nothing on a rig that spells it differently",
+ "kind": "evidence:page",
+ "target": "https://three.ws/rig-doctor",
+ "ok": true,
+ "detail": "live page shows \"A track that names LeftForeArm drives nothing on a rig that calls that joint lowerarm_l.\""
+ },
+ {
+ "claim": "The keeper's bones are named the Mixamo way, mixamorig:LeftForeArm",
+ "kind": "evidence:file",
+ "target": "data/x-content/runs/keeper-article.json",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "strips vendor prefixes and namespaces, collapses separators and case, and looks what is left up in alias tables that cover more than twenty naming schemes",
+ "kind": "evidence:file",
+ "target": "src/glb-canonicalize.js",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "strips vendor prefixes and namespaces, collapses separators and case, and looks what is left up in alias tables that cover more than twenty naming schemes",
+ "kind": "evidence:file",
+ "target": "src/glb-canonicalize.js",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "strips vendor prefixes and namespaces, collapses separators and case, and looks what is left up in alias tables that cover more than twenty naming schemes",
+ "kind": "evidence:file",
+ "target": "src/glb-canonicalize.js",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "map onto the canonical set one to one, so a freshly rigged avatar drives the clip library at 100% coverage",
+ "kind": "evidence:file",
+ "target": "workers/rig/README.md",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "map onto the canonical set one to one, so a freshly rigged avatar drives the clip library at 100% coverage",
+ "kind": "evidence:file",
+ "target": "workers/rig/README.md",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "fingers are 30 of the clip library's 53 tracks, and a rig whose hands do not map scores about 40% coverage and gets no animation at all",
+ "kind": "evidence:file",
+ "target": "src/glb-canonicalize.js",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "The reference rig the clips were baked on rests in an A-pose, and Mixamo rigs rest in a T-pose",
+ "kind": "evidence:file",
+ "target": "src/animation-retarget.js",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "replays the clip bone's motion as the same change in world space from that rest",
+ "kind": "evidence:file",
+ "target": "src/animation-retarget.js",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "Joint rotations and the root translation cross over, the bone lengths baked into the clips do not, and the root is rescaled to the new rig's height",
+ "kind": "evidence:file",
+ "target": "src/animation-retarget.js",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "Joint rotations and the root translation cross over, the bone lengths baked into the clips do not, and the root is rescaled to the new rig's height",
+ "kind": "evidence:file",
+ "target": "src/animation-retarget.js",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "keeps its own proportions",
+ "kind": "evidence:file",
+ "target": "src/animation-retarget.js",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "copied the model into durable storage so the body survives the source URL expiring, and registered it under a stable id",
+ "kind": "evidence:file",
+ "target": "api/_mcp-studio/persona-tools.js",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "It answered in 4.1 seconds",
+ "kind": "evidence:file",
+ "target": "data/x-content/runs/keeper-article.json",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "Saved \"The Keeper\" as a living persona.",
+ "kind": "evidence:file",
+ "target": "data/x-content/runs/keeper-article.json",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "Rig: humanoid, full body animation + lip-sync.",
+ "kind": "evidence:file",
+ "target": "data/x-content/runs/keeper-article.json",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "the same body and name come back, with the number of turns it has spoken so far",
+ "kind": "evidence:file",
+ "target": "api/_mcp-studio/persona-tools.js",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "the same body and name come back, with the number of turns it has spoken so far",
+ "kind": "evidence:file",
+ "target": "api/_mcp-studio/persona-tools.js",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "lip-sync, a facial expression and a gesture, with the emotion detected from the text unless the caller sets one",
+ "kind": "evidence:file",
+ "target": "api/_mcp-studio/persona-tools.js",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "lip-sync, a facial expression and a gesture, with the emotion detected from the text unless the caller sets one",
+ "kind": "evidence:file",
+ "target": "api/_mcp-studio/persona-tools.js",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "Every ship that saw it made it home",
+ "kind": "evidence:file",
+ "target": "data/x-content/runs/keeper-article.json",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "persona_say answered in 299 milliseconds and recorded the turn",
+ "kind": "evidence:file",
+ "target": "data/x-content/runs/keeper-article.json",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "persona_say answered in 299 milliseconds and recorded the turn",
+ "kind": "evidence:file",
+ "target": "data/x-content/runs/keeper-article.json",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "It read the line as neutral",
+ "kind": "evidence:file",
+ "target": "data/x-content/runs/keeper-article.json",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "There is no API key and no build step",
+ "kind": "evidence:file",
+ "target": "docs/web-component.md",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "There is no API key and no build step",
+ "kind": "evidence:file",
+ "target": "docs/web-component.md",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "boots once it comes within 300 pixels of the viewport",
+ "kind": "evidence:file",
+ "target": "src/element.js",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "loads the body and the idle and walk clips",
+ "kind": "evidence:file",
+ "target": "src/element.js",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "keeps its canvas hidden until that pose has rendered",
+ "kind": "evidence:page",
+ "target": "https://three.ws/docs/web-component",
+ "ok": true,
+ "detail": "live page shows \"the element keeps its canvas hidden until that pose has rendered, so a bind-pose T-pose is never shown\""
+ },
+ {
+ "claim": "keeps its canvas hidden until that pose has rendered",
+ "kind": "evidence:file",
+ "target": "src/element.js",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "around 16 in Chrome",
+ "kind": "evidence:file",
+ "target": "src/element.js",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "by default eight avatars are live at a time",
+ "kind": "evidence:file",
+ "target": "src/element.js",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "by default eight avatars are live at a time",
+ "kind": "evidence:file",
+ "target": "src/element.js",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "one scrolled out of view hands its context back until it returns",
+ "kind": "evidence:file",
+ "target": "src/element.js",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "gets a single held idle pose instead of a loop",
+ "kind": "evidence:file",
+ "target": "src/element.js",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "On the live site today, the keeper's idle drives his upper arms back through his coat",
+ "kind": "evidence:page",
+ "target": "https://three.ws/api/version",
+ "ok": false,
+ "detail": "live page does not show \"\"commitShort\":\"76081013b\"\""
+ },
+ {
+ "claim": "On the live site today, the keeper's idle drives his upper arms back through his coat",
+ "kind": "evidence:file",
+ "target": "src/animation-retarget.js",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "a rig that rests in an A-pose with bent elbows received the idle's full swing down from a T-pose on top of an arm that already hung down",
+ "kind": "evidence:file",
+ "target": "src/animation-retarget.js",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "The fix re-aims each limb from its own rest direction onto the authoring rig's before the clip plays",
+ "kind": "evidence:file",
+ "target": "src/animation-retarget.js",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "because its check looks for the 15 Oculus viseme names and no other set",
+ "kind": "evidence:file",
+ "target": "src/rig-report.js",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "because its check looks for the 15 Oculus viseme names and no other set",
+ "kind": "evidence:file",
+ "target": "src/rig-report.js",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "The keeper carries the 52 ARKit shapes instead, which is the set the rig worker writes and the set the persona tools drive",
+ "kind": "evidence:file",
+ "target": "workers/rig/README.md",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "The keeper carries the 52 ARKit shapes instead, which is the set the rig worker writes and the set the persona tools drive",
+ "kind": "evidence:file",
+ "target": "data/x-content/runs/keeper-article.json",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "four generations a minute and 30 an hour",
+ "kind": "evidence:file",
+ "target": "api/_lib/rate-limit.js",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "four generations a minute and 30 an hour",
+ "kind": "evidence:file",
+ "target": "api/_lib/rate-limit.js",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "look_at_model counts against the same quota because it renders on the server",
+ "kind": "evidence:file",
+ "target": "api/_mcp-studio/dispatch.js",
+ "ok": true,
+ "detail": "file supports the claim"
+ },
+ {
+ "claim": "type a description and get a rigged avatar back",
+ "kind": "evidence:page",
+ "target": "https://three.ws/create/prompt",
+ "ok": true,
+ "detail": "live page shows \"Type a description → rigged 3D avatar in about a minute\""
+ },
+ {
+ "kind": "probe:api",
+ "target": "the keeper the article follows is still served",
+ "ok": true,
+ "detail": "HTTP 200, expectations met"
+ },
+ {
+ "kind": "probe:api",
+ "target": "the free 3D Studio server still offers forge_avatar to a keyless client",
+ "ok": true,
+ "detail": "HTTP 200, expectations met"
+ },
+ {
+ "kind": "probe:api",
+ "target": "the rigging worker is loaded on its GPU",
+ "ok": true,
+ "detail": "HTTP 200, expectations met"
+ },
+ {
+ "kind": "probe:api",
+ "target": "the Hunyuan3D worker is ready",
+ "ok": true,
+ "detail": "HTTP 200, expectations met"
+ },
+ {
+ "kind": "probe:browser",
+ "target": "Rig Doctor maps every canonical joint of the Mixamo sample",
+ "ok": true,
+ "detail": "3 steps passed"
+ },
+ {
+ "kind": "link",
+ "target": "https://three.ws",
+ "ok": true,
+ "detail": "HTTP 200 via https://three.ws/"
+ },
+ {
+ "kind": "link",
+ "target": "https://three.ws/create/prompt",
+ "ok": true,
+ "detail": "HTTP 200"
+ },
+ {
+ "kind": "link",
+ "target": "https://three.ws/create/prompt",
+ "ok": true,
+ "detail": "HTTP 200"
+ },
+ {
+ "kind": "link",
+ "target": "https://three.ws/docs/mcp-studio",
+ "ok": true,
+ "detail": "HTTP 200"
+ },
+ {
+ "kind": "link",
+ "target": "https://three.ws/rig-doctor",
+ "ok": true,
+ "detail": "HTTP 200"
+ },
+ {
+ "kind": "link",
+ "target": "https://three.ws/viewer?src=https%3A%2F%2Fthree.ws%2Fcdn%2Fforge%2Fanon%2Fa9694760-e134-4c5c-b334-59129a2d42c9.glb",
+ "ok": true,
+ "detail": "HTTP 200"
+ },
+ {
+ "kind": "spelling",
+ "target": "CVPR",
+ "ok": false,
+ "detail": "did you mean cspr, CSPR, cvar?"
+ },
+ {
+ "kind": "spelling",
+ "target": "mixamorig",
+ "ok": false,
+ "detail": "did you mean mixamo?"
+ },
+ {
+ "kind": "spelling",
+ "target": "canonicalizer",
+ "ok": false,
+ "detail": "did you mean canonicalize, canonicalized, canonicalizes?"
+ },
+ {
+ "kind": "spelling",
+ "target": "viseme",
+ "ok": false,
+ "detail": "did you mean vise, vised, vises?"
+ },
+ {
+ "kind": "spelling",
+ "target": "blendshapes",
+ "ok": false,
+ "detail": "not a known word; add it to the queue glossary if it is correct"
+ }
+ ]
+ },
+ "editor": {
+ "verdict": "revise",
+ "scores": {
+ "accuracy": 3,
+ "clarity": 5,
+ "specificity": 5,
+ "voice": 5,
+ "professionalism": 5,
+ "visual": 4
+ },
+ "issues": [
+ {
+ "severity": "blocking",
+ "area": "accuracy",
+ "quote": "On the live site today, the keeper's idle drives his upper arms back through his coat ... It reaches three.ws with the next deploy.",
+ "problem": "The article asserts the idle defect is unfixed on production and the fix is not yet deployed, anchored to commit 76081013b. The verification probe against https://three.ws/api/version failed: the live site does not report that commit. Either the fix has already deployed (making the defect disclosure and the image choice wrong) or the version evidence is wrong. A failed verification on a claim about the current live state must not publish.",
+ "fix": "Re-run the api/version check. If the live commit now carries the fix, rewrite the paragraph to say the retargeting defect was fixed and is live, verify the keeper's idle no longer clips in the live viewer, and update the image-choice sentence accordingly. If the check was simply stale, capture a fresh api/version response and keep the paragraph. Do not touch the X post itself; it makes no claim about the defect."
+ },
+ {
+ "severity": "minor",
+ "area": "visual",
+ "quote": "the two that failed that morning and the fallbacks that caught them",
+ "problem": "The cover image shows the keeper in rest pose and looks clean, which supports the post, but the article explains images avoid showing the broken idle. That is fine once the deploy status is re-verified; if the fix proves live, the cover choice rationale must be revisited too.",
+ "fix": "No recapture needed unless the accuracy fix changes the deploy story."
+ }
+ ],
+ "rewrite": {
+ "posts": [
+ "We sent one sentence to the free three.ws MCP server and got back a rigged 3D lighthouse keeper in 197 seconds: 22,500 triangles, a 52-joint skeleton with every finger, 52 facial expression shapes. The article follows that one job through each stage, including the two that failed that morning and the fallbacks that caught them."
+ ],
+ "altText": [
+ "A 3D character generated from one sentence and auto-rigged on three.ws, standing in the live glTF viewer on a dark background: an old lighthouse keeper with a white beard and a navy knitted cap, in a long yellow oilskin coat with flap pockets and dark buttons, blue trousers and black rubber boots"
+ ]
+ },
+ "summary": "The X post itself is excellent: every number checks out, voice is compliant, and the image matches the copy. However the article body claims the retargeting fix is not yet deployed, and the live version check failed to confirm that, so the deploy status must be re-verified and the paragraph corrected before release.",
+ "model": "nvidia:moonshotai/kimi-k3",
+ "fallbacks": [
+ "Vertex 403: {\n \"error\": {\n \"code\": 403,\n \"message\": \"Request had insufficient authentication scopes.\",\n \"status\": \"PERMISSION_DENIED\",\n \"details\": [\n {\n \"@type\": \"type.googleapis.com/goog",
+ "openrouter 402: {\"error\":{\"message\":\"Insufficient credits. Add more using https://openrouter.ai/settings/credits\",\"code\":402,\"metadata\":{\"limit_source\":\"openrouter_credits\",\"remedy_hint\":\"Add credits at https://openr",
+ "openai 429: {\n \"error\": {\n \"message\": \"Your account is not active, please check your billing details on our website.\",\n \"type\": \"billing_not_active\",\n \"param\": null,\n \"code\": \"billi"
+ ],
+ "rewriteFindings": [
+ "claims: claim \"On the morning of 8 October\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"No account, no key\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"a full PBR material\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"Four seconds after that he was a named persona with a stable id\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"a third of a second after that he had spoken his opening line\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"Every call, every timing and the server's own record of each job are written down in a run file that ships with the platform\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"returns a rigged, animation-ready GLB in one call\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"a sentence that clearly names an object (a chair, a dog, a sword) is turned away before any GPU time is spent, with a message pointing to the mesh generator instead\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"A director model turns the sentence into a brief\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"the mesh stage took 100 seconds and the rig stage 12.6 seconds\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"rewriting the sentence, painting the picture, storing each intermediate file and polling the workers\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"a portrait-leaning model tends to answer a description of a person with a head and shoulders, and a bust cannot be rigged into anything that walks\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"The language models it calls were rate limiting at that moment\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"a fixed fallback brief is appended to the raw words, stating the framing the director would have asked for\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"That is the fallback, word for word\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"costs polish, never the body\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"as one centered subject on a plain seamless background under soft even light\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"set almost entirely by the realism of that one reference picture\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"A Gemini image model on Vertex AI leads it, because it draws the most photoreal reference\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"This morning that rung was refusing requests, so the picture came from FLUX.1-dev, further down the ladder\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"No single provider's failure is the end of a picture\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"Avatars ask for the high tier, and at the high tier the router sends a job to Hunyuan3D 2.1 on our own worker\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"a Cloud Run service with an NVIDIA RTX PRO 6000 Blackwell attached\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"builds the geometry, then runs a separate pass that paints a full PBR material set rather than one baked colour map\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"one material carrying four maps: base colour, metallic and roughness, normal, and ambient occlusion\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"22,500 triangles across 16,388 vertices\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"the job would have moved to the next engine under the same job id: our TRELLIS worker, a hosted TRELLIS lane, then TripoSG\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"That chain was not needed on this run\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"at the high tier, with a longer sentence of our own. It returned a model in 108 seconds\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"That tool renders any public GLB on the server from several angles and returns the frames as images\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"The geometry count agreed: 8,464 triangles\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"is the subject complete and recognisable, is the far side finished, is anything melted, fused or missing\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"generate again with a prompt that names the specific fault\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"turns one-shot generation into a loop\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"look_at_model is marked read-only\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"it works on any public GLB, wherever it was made\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"a Cloud Run service on an NVIDIA L4 running Make-It-Animatable\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"released under the MIT licence and published at CVPR 2025\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"predicts joint positions, skinning weights and pose for a 52-bone Mixamo skeleton, fingers included, in under a second of GPU time\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"It is used as a predictor and nothing more\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"writes the skeleton, the per-vertex joint indices and weights, and the inverse bind matrices straight into the original GLB bytes\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"its materials and PBR textures are preserved byte for byte\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"transfers the 52 ARKit expression shapes from an open template head onto the avatar's face, written as glTF morph targets\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"diagnoses a GLB in the browser without uploading it\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"Every limb group mapped\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"Every clip in it is authored against one canonical skeleton: Hips, LeftForeArm, RightUpLeg, 52 joints in total\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"a track that names LeftForeArm drives nothing on a rig that spells it differently\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"The keeper's bones are named the Mixamo way, mixamorig:LeftForeArm\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"strips vendor prefixes and namespaces, collapses separators and case, and looks what is left up in alias tables that cover more than twenty naming schemes\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"map onto the canonical set one to one, so a freshly rigged avatar drives the clip library at 100% coverage\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"fingers are 30 of the clip library's 53 tracks, and a rig whose hands do not map scores about 40% coverage and gets no animation at all\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"The reference rig the clips were baked on rests in an A-pose, and Mixamo rigs rest in a T-pose\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"replays the clip bone's motion as the same change in world space from that rest\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"Joint rotations and the root translation cross over, the bone lengths baked into the clips do not, and the root is rescaled to the new rig's height\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"keeps its own proportions\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"copied the model into durable storage so the body survives the source URL expiring, and registered it under a stable id\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"It answered in 4.1 seconds\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"Saved \"The Keeper\" as a living persona.\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"Rig: humanoid, full body animation + lip-sync.\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"the same body and name come back, with the number of turns it has spoken so far\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"lip-sync, a facial expression and a gesture, with the emotion detected from the text unless the caller sets one\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"Every ship that saw it made it home\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"persona_say answered in 299 milliseconds and recorded the turn\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"It read the line as neutral\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"There is no API key and no build step\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"boots once it comes within 300 pixels of the viewport\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"loads the body and the idle and walk clips\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"keeps its canvas hidden until that pose has rendered\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"around 16 in Chrome\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"by default eight avatars are live at a time\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"one scrolled out of view hands its context back until it returns\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"gets a single held idle pose instead of a loop\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"On the live site today, the keeper's idle drives his upper arms back through his coat\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"a rig that rests in an A-pose with bent elbows received the idle's full swing down from a T-pose on top of an arm that already hung down\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"The fix re-aims each limb from its own rest direction onto the authoring rig's before the clip plays\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"because its check looks for the 15 Oculus viseme names and no other set\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"The keeper carries the 52 ARKit shapes instead, which is the set the rig worker writes and the set the persona tools drive\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"four generations a minute and 30 an hour\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"look_at_model counts against the same quota because it renders on the server\" does not appear in the copy; claims must quote the post",
+ "claims: claim \"type a description and get a rigged avatar back\" does not appear in the copy; claims must quote the post"
+ ]
+ },
+ "editorError": null
+}
diff --git a/docs/mobile-launch/coinmarketcap-article.md b/docs/mobile-launch/coinmarketcap-article.md
index 22fcf03c2..6b0a26996 100644
--- a/docs/mobile-launch/coinmarketcap-article.md
+++ b/docs/mobile-launch/coinmarketcap-article.md
@@ -10,125 +10,217 @@ status: draft, owner approval required before posting (external-channel gate in
Paste-ready for the CoinMarketCap form. CMC caps the title and meta description at 191 characters, the body editor offers H2 and H3 only, and it has no table support (a markdown table pastes as one run-on line), so every list below is plain lines. Cover: 640x360 or that proportion, under 10 MB. Upload `marketing/mobile-launch/cmc-cover-1280x720.png` (the exact 640x360 sits beside it); both are rendered from real product captures by `node marketing/mobile-launch/make-cmc-cover.mjs`.
-## Title (108 characters)
+## Title (134 characters)
```
-three.ws Is Now on Solana Seeker, Android and iPhone: A 3D Agent Studio, a Wallet That Never Leaves the Chip, and an Economy
+three.ws Is Now on Solana Seeker, Android and iPhone: A 3D Agent Studio, Keys That Stay in Your Wallet, and an Agent Economy on Solana
```
-## Meta description (184 characters)
+## Meta description (183 characters)
```
-The open-source platform that turns a selfie into a rigged 3D AI agent you own on Solana is now three native apps. Why we built mobile, what is inside, every partner, and where it goes next.
+The open-source platform that turns a selfie into a rigged 3D AI agent you own on Solana is now three native apps. What is inside, how it works, every partner, and where it goes next.
```
## Body
---
-three.ws, the open-source platform that gives AI agents a 3D body, an on-chain identity, a wallet, and a way to get paid, is now three native apps: one on the Solana dApp Store for the Seeker, one on Google Play for every Android phone, and one on the App Store for iPhone. Same product, same account, same library, three home screens.
+Imagine pointing your phone at your face, waiting about a minute, and holding a 3D character of yourself that can walk, wave, talk back in your language, and stand on your kitchen floor through the camera. Now imagine giving that character a personality, a voice, and a few skills, and watching it earn a little money on its own while you get on with your day.
-This is the long-form version for the crypto-native reader: why a platform like this had to end up on a phone, why Solana is the home chain, what the apps do that a browser cannot, what the economy underneath them has become in the five months since the first commit, how $THREE sits in the middle of it, and what we are building next. Every number here is checkable against the public repository, the public changelog, or a public listing.
+That is three.ws. It is an open-source platform that gives AI agents a body you can see, a mind you can talk to, an identity you can own on Solana, and a wallet that lets them get paid. And as of this launch it lives on your home screen as three native apps: one on the Solana dApp Store for the Seeker, one on Google Play for every Android phone, and one on the App Store for iPhone. Same product, same account, same library, three home screens.
-## The problem three.ws exists to solve
+This article is written for two readers at once. If you are new to all of this, the first half is for you: what three.ws is, what you can do with it in your first five minutes, and why a phone is the perfect place for it. If you are a crypto-native reader who wants the machinery, the second half goes deep: Seed Vault signing, Seeker Genesis verification, the x402 economy with dated figures, agent wallets and their spend policies, the launchpad, the Oracle, vaults, swarms, Agora, $THREE and its holder tiers, every partner programme with its exact designation, and the roadmap. Every number here is checkable against the public repository, the public changelog, or a public listing.
-For two years the AI-and-crypto conversation lived in a narrow lane: chatbots that can read a wallet balance, agents that can sign a swap, frameworks that promise autonomous trading and stall when the demo ends. What was missing was the layer underneath: a way for an AI agent to exist as a first-class object on the internet. A body people can see. An identity that survives a model swap. A wallet that pays for its own compute. A reputation that follows it across apps. A way to be embedded anywhere a video can be embedded.
+## three.ws in one minute
-three.ws builds that layer, and it builds it in a specific order. The body first, because presence is how humans decide to trust something. Then the mind: an LLM brain with a tool loop, memory, skills, and emotion on the face. Then the identity: a Metaplex Core asset on Solana or an ERC-8004 token on EVM chains, portable, provable, ownable. Then the economy: x402 pay-per-call rails so the agent can earn and spend USDC without a human holding the keys.
+Think of three.ws as a studio, a home, and a marketplace for AI characters.
-The phone is where all four of those layers finally meet the person using them.
+The studio is where characters are made. You can describe one in a sentence, upload a photo, sketch a shape, or take a selfie, and the platform turns it into a real 3D model: textured, rigged with a skeleton so it can move, and ready to download in the open glTF format that every major 3D tool reads.
-## Why mobile was inevitable
+The home is where characters come alive. Give one a personality, pick which AI model does its thinking, give it a voice, teach it skills, and talk to it. It answers in 3D with expressions on its face and lip movements that match its words. It remembers you.
-Look at where the inputs to a three.ws agent actually live.
+The marketplace is where characters meet the world. Every character has its own page and a link you can share. You can embed it on a website with one line of code, place it in augmented reality, pin it to a real place on a map, bring it into a shared multiplayer world, and, when you choose, own it on Solana and let it sell its skills.
-The camera that takes the selfie is on the phone. The photo roll full of faces is on the phone. The wallet is on the phone. The share sheet, the gesture that moves a picture from one app to another, is on the phone. The AR camera that can stand an agent on your floor is on the phone. The GPS that lets an agent be pinned to a park bench is on the phone. The home screen, where a widget can show you your agent's day without opening anything, is on the phone.
+All of it is free to start. Creating, chatting, and browsing work with no wallet at all. The on-chain layer waits patiently underneath for the day you want it.
-A desktop browser renders three.ws beautifully and always will. But it cannot take the selfie, cannot walk into the room, cannot stand at the bench, and cannot sign without an extension. The product wanted to be on a phone from the first commit. The apps are it arriving there.
+## Your first five minutes on the app
-## Why Solana, and why the Seeker first
+Here is what a first session looks like on any of the three apps.
-Solana is the home chain for three.ws for a reason that has nothing to do with narrative. It is where the users are, where the wallets are, where a transaction costs less than the attention it takes to approve one, and, since the Seeker shipped, where the phone is.
+Open the app and tap Create. Choose Selfie, hold your phone at arm's length, and follow the on-screen hints until the shutter unlocks. A short countdown runs, the photo is taken, and you see exactly what the engine will see. Tap to submit. While the build runs you can watch its stages: mesh, geometry and textures, then rigging.
-The Seeker is the device where the wallet story is finally right. Inside the three.ws app every signature routes to the Seed Vault through Mobile Wallet Adapter. Sign-In With Solana is a single interaction instead of a connect step followed by a signing step. The private key never enters the application process at all; it stays in the hardware-isolated secure element. Approve a session once and it survives Android killing the app in the background, because the authorization token is persisted and the next signature is a silent reauthorize rather than a fresh prompt. Revoke the session in the wallet and the app drops it cleanly and asks again next time.
+When it lands, your avatar opens in a 3D viewer. Spin it with a finger. Tap View in AR and it stands on the floor in front of you, at real scale. Tap Turn this into an agent and give it a name, a short description of its personality, and a voice.
-Own a Seeker and you can prove it without moving anything. Solana Mobile mints a soulbound Seeker Genesis Token, a Token-2022 asset, into every device's primary Seed Vault account. The three.ws server reads the linked wallet's Token-2022 accounts, checks the mint authority, the metadata pointer, and the token-group membership against the Genesis group, and records the verification. No transaction, no signature, and it fails closed: an RPC error is a 502, never a false positive. Every agent a verified owner holds shows a Seeker verified badge on its profile.
+Now talk to it. Ask it a question and it answers out loud with its face moving. Try a different brain: the same agent can think with Claude, GPT, Gemini, Qwen, IBM Granite, or NVIDIA Nemotron, and you can switch any time.
-Everything else in this article works on every Android phone and every iPhone too. The Seeker is where it works best.
+Then share it. Every agent has its own URL, so you can drop it into a group chat, a social post, or your own website. If you want to keep going, open Discover and browse what everyone else has made, or open Play and walk around a live 3D world with other people's avatars, talking to them with spatial voice.
+
+That is the whole onboarding. No seed phrase, no exchange account, no purchase. The wallet comes later, on the day you decide you want to own what you made.
+
+## Why the phone is the natural home for an agent
+
+Look at where the ingredients of a three.ws agent live.
+
+The camera that takes the selfie is on the phone. The photo roll full of faces is on the phone. The wallet is on the phone. The share sheet, the gesture that moves a picture from one app to another, is on the phone. The AR camera that stands an agent on your floor is on the phone. The GPS that pins an agent to a park bench is on the phone. The home screen, where a widget shows your agent's day at a glance, is on the phone.
+
+Every one of those ingredients becomes a feature in the apps. A photo you share from your gallery opens the selfie flow with the photo already attached. A long press on the icon jumps straight to Create, Discover, or My agents. A three.ws link from a friend opens in the app. Your wallet signs inside the wallet you already trust. Your agent's daily activity sits on your home screen.
+
+The desktop browser remains a first-class way to use three.ws, and it always will be. The apps are where the product meets the device it was designed around from the first commit.
+
+## Why Solana, and why the Seeker leads
+
+Solana is the home chain for three.ws because it is where the users are, where the wallets are, where a transaction costs less than the attention it takes to approve one, and, with the Seeker, where the phone is.
+
+The Seeker is the device where the wallet story is at its best. Inside the three.ws app every signature routes to the Seed Vault through Mobile Wallet Adapter. Sign-In With Solana happens at authorize time, so signing in is a single interaction. The private key lives in the hardware-isolated secure element and stays there; the app only ever asks the Seed Vault to sign. Approve a session once and it survives Android restarting the app in the background, because the authorization token is persisted and the next signature is a silent reauthorize. Revoke the session in the wallet and the app drops it cleanly and asks again next time, exactly as a well-behaved app should.
+
+Seeker owners can also prove they own one, with nothing moved and nothing signed. Solana Mobile mints a soulbound Seeker Genesis Token, a Token-2022 asset, once per device into its primary Seed Vault account. On the app's home screen at three.ws/seeker, after signing in, a Seeker owner taps Check my wallet. The server reads the linked wallet's Token-2022 accounts and checks each mint's authority, metadata pointer, and token-group membership against the Genesis group, then records the verification. It is a read, so verification is precise: a badge appears only when the chain itself confirms the token. From then on, every agent that owner holds shows a Seeker verified badge in the trust row of its profile.
+
+Everything else in this article works on every Android phone and every iPhone. The Seeker is where it shines brightest.
## The three apps
### Solana Seeker, on the Solana dApp Store
-The app is a Trusted Web Activity: the real three.ws, full screen, no browser chrome, with every wallet interaction routed to the Seed Vault. Share a photo to three.ws from any app and it opens the selfie flow with the photo already attached. Share a .glb and it opens the upload flow. Long-press the icon for Create, Discover, and My agents. Any three.ws link opens inside the app instead of a browser tab, verified through Digital Asset Links against our published signing certificate at three.ws/.well-known/assetlinks.json. If the two disagree, the app is not ours. Lose the network and you get a branded offline screen that reloads itself when you are back.
+The Seeker app is a Trusted Web Activity, the shape Solana Mobile recommends for web apps: the real three.ws, full screen, with no browser chrome, and every wallet interaction routed to the Seed Vault. For a WebGL product that is the right design, because the app is always exactly as current as the website.
+
+What makes it feel native is everything around that shell. It opens on its own home screen at three.ws/seeker, with one-tap Seed Vault sign-in, a Create and Explore grid, your agents, and the Seeker verification card. Share a photo to three.ws from any app and it opens the selfie flow with the photo already attached, and a second and third photo fill the optional side angles. Share a .glb and it opens the upload flow, which validates and stages the file. Long-press the icon for Create, Discover, and My agents. Any three.ws link opens inside the app, verified through Digital Asset Links against the signing certificate published at three.ws/.well-known/assetlinks.json, so links land in exactly the app they belong to. If the network drops, a branded offline screen waits for you and reloads on its own the moment the connection is back. The icon is maskable, with the glyph inside Android's safe zone, so it looks right on circle and squircle launchers alike.
### Android, on Google Play
-The same package, ws.three.app, for every Android phone from 6.0 up, 3.95 MB. Signing runs through Mobile Wallet Adapter into whatever wallet app you already trust, so three.ws never sees a key or a seed phrase. three.ws is not a wallet, holds no funds, and runs no exchange; the Play declaration says exactly that.
+The same package, ws.three.app, runs on every Android phone from 6.0 up, at 3.95 MB. Signing runs through Mobile Wallet Adapter into whatever wallet app you already trust, so your keys and your funds stay in that wallet, and the app works with them through a signature request you approve.
-Version 1.1 added Agent glance, a home screen widget in three sizes that shows your agent's avatar, its name, and how many moves it made today. It refreshes itself about every thirty minutes without opening the app, keeps the last card it saw when the phone is offline, survives a reboot, and opens your agent on tap. Link a phone from three.ws/glance in one tap. Every linked widget carries its own revocable token that can read your card and nothing else, and every one is listed on that page with a revoke button.
+Version 1.1 added Agent glance, a home screen widget in three sizes: a square card, a wide card, and a wide card with Create and My agents buttons. It shows your agent's avatar, its name, and how many moves it made today. Android refreshes it in the background about every thirty minutes, so the number moves without you opening anything. It keeps the last card it saw when the phone is offline, survives a reboot, and opens your agent on tap. Link a phone from three.ws/glance in one tap. Each linked widget carries its own token, scoped to read your glance card and only your glance card, and every one is listed on that page with a revoke button.
### iPhone, on the App Store
-A native shell whose WebView runs the live product, wrapped in the native layer a website cannot have: universal links so any three.ws link opens in the app, the system share sheet with AR captures attached as real image files, wallet and sign-in redirects that come back over threews:// to the exact page that started them, an in-app Safari sheet for off-site links so you always have a way back, haptics on primary actions, edge-swipe back and forward, real camera and motion permission prompts for the selfie scanner and AR, and a launch screen that holds until the first real frame so a three.js scene never opens onto a black void. Because the native bridge ships with the site rather than the binary, the app improves on every web deploy.
+The iPhone app is a native container whose web view runs the live product, wrapped in the native layer that makes it an app. Universal links open any three.ws link in the app. three.ws appears in every app's share sheet: share one to three photos and they are waiting in Create as the front, left, and right views of a new avatar, with HEIC photos converted to JPEG on the phone before the page ever sees them; share a .glb from Files and it lands in the upload flow. Press and hold the icon for quick actions: Create avatar, Discover, My agents, and Notifications. The system share sheet works outward too, with AR captures attached as real image files.
-On desktop, three.ws installs as a PWA, and on Windows 11 the same glance card lives on the widgets board.
+Wallet and sign-in redirects come back over threews:// to the exact page that started them. Off-site links open in an in-app Safari sheet so you always return to where you were. Primary actions have a haptic tick. Edge-swipe gestures move back and forward. The camera, microphone, photos, location, and motion prompts are real iOS permission prompts with clear usage strings, which is what the selfie scanner, the AR studio, and IRL need. The launch screen holds until the first real frame is drawn, so the 3D scene opens fully rendered. Form fields stay at a comfortable 16 pixels so typing never zooms the page.
-## What you can do from the phone, with no wallet at all
+Because the native bridge ships with the site rather than with the binary, the iPhone app improves with every web deploy. A fix to the share sheet or a new deep-link route reaches every phone the same day it ships.
-Creating, chatting, and browsing never touch a chain. That order is deliberate, and it is the whole thesis of the launch.
+### Desktop and Windows
-### Forge: text to 3D
+On desktop, three.ws installs as a Progressive Web App. On Windows 11 the same Agent glance card lives on the widgets board, installed straight from the web app's manifest, refreshed every fifteen minutes, and showing the last card it saw if the machine wakes up offline. The same card also renders as an image in a GitHub README, in a Slack message, on any web page through the agent-glance element, and in a terminal.
-Describe an object, a prop, a creature, or a scene and get a textured 3D model back, ready to download as glTF. The draft lane is free with no key and no account and finishes in about twelve seconds on NVIDIA's hosted TRELLIS lane. Paid lanes go to 200,000 polygons with PBR materials and game-ready retopology, priced at $0.05, $0.15, and $0.50 in USDC over x402 for anyone, human or agent, who wants to pay per call.
+## Inside the studio
+
+The apps are a doorway. Here is what is on the other side of it, in more depth.
### Scan: one selfie, a rigged character of you
-One frontal photo becomes a rigged, animation-ready avatar in about a minute, with a Mixamo-compatible skeleton and the full ARKit-52 blendshape set. Two optional side angles sharpen the likeness. A live 468-point face mesh runs on-device and tells you about lighting, framing, blur, or window glare before you spend the minute waiting.
+The selfie scanner at three.ws/create/selfie is built to get a great photo on the first try. A live 468-point face mesh runs on the device and tracks head pose, centering, blur, brightness, and highlight clipping in real time. The hint line names the single most useful fix, such as facing the camera straight on, holding steady, finding better light, or turning away from a bright window, and the shutter unlocks only when a face is found. Every one of those thresholds is traced to a real behaviour of the reconstruction engine, so the phone guides you toward exactly the photo the engine does its best work with.
+
+After the countdown, the still is re-scored before you accept it, so you see a verdict for the actual frame rather than the live preview. Two optional side angles, left and right at about 45 degrees, raise fidelity. Your confirmed shots are saved for the session, so an accidental swipe back restores every slot. Before anything is sent, the phone isolates you from the background and reframes the photo to a clean head-and-shoulders square, and it shows you that refined image so you know exactly what the engine will receive.
+
+On the server, the reconstruction worker runs on Google Cloud Run. It uses MediaPipe's 468 face landmarks to transfer your face texture and geometry onto a pre-rigged humanoid template. The result is a glTF 2.0 file with a Mixamo-compatible skeleton, the full set of 52 ARKit blendshapes, and 15 visemes, so it can walk, emote, and lip-sync the moment it finishes. A frontal-only run takes about a minute and a half, and about two minutes with side angles.
+
+The flow is built to finish. If a generic mesh ever comes back without a skeleton, an auto-rig step adds one. If you close the tab mid-build, a server-side sweep completes the job and the avatar is waiting in your library. The same pipeline also accepts a text prompt instead of a photo: it paints a head-and-shoulders portrait first and then reconstructs from that, so one endpoint has two front doors.
+
+When the avatar lands you can open it, customize it in the editor, export it as GLB or FBX, share it, or turn it into an agent. The pipeline is also wired to give every finished avatar a draft on-chain identity in the background, with no wallet prompt and no fee; going live, taking payments, and listing in the marketplace remain a separate step you take when you choose.
+
+### Forge: text, photos, or a sketch to 3D
+
+The Forge at three.ws/forge turns a sentence, up to six photos of an object, or a sketch with a label into a textured 3D model. It treats generation as a routing problem across a grid of real engines and is free-first by design.
+
+Draft and Standard generations run on our own self-hosted TRELLIS worker, and High generations on our own self-hosted Hunyuan3D worker, both on Google Cloud Run GPUs at zero vendor cost. Behind them sit free hosted lanes, with NVIDIA's hosted TRELLIS lane as the final free safety net for text prompts. Sketches run on a TripoSG worker built for sketch-conditioned geometry. A subject classifier hoists the best engine for the job: hard-surface prompts such as vehicles, machines, and architecture lead with TRELLIS, while people and creatures lead with Hunyuan3D.
+
+The three tiers are clear. Draft targets 12,000 polygons. Standard targets 30,000 with 2K textures. High targets 200,000 with PBR and HD textures. Anyone, human or agent, can also buy the same tiers per call over x402 at $0.05, $0.15, and $0.50 in USDC, with no account. High-quality generation and Game-Ready export for Unity and Unreal are $THREE holder perks from the Bronze tier up, with a pay-per-use option for everyone else.
+
+Live health is part of the product. The Forge reads each lane's real upstream status before you click Generate and shows the reason when a lane is resting. Once a job starts, it keeps the same job id from start to finish: if a lane hands off mid-generation, the job moves to the next lane automatically and you simply see it complete. The job id is saved on the device, so you can close the app and come back within thirty minutes to find it still running.
+
+A finished model is a starting point. Rig for animation adds a humanoid skeleton and hands off to the Pose Studio. Restyle materials re-skins the surface from a plain-language instruction or a preset chip such as chrome, wood, gold, neon, marble, or rust. Iterate makes a shape-changing edit from a sentence, such as "make the helmet red" or "add a backpack", and keeps every version in a branchable lineage strip. Place IRL anchors the model at a real-world location.
### Agents: give it a mind
-Attach a personality, a voice, skills, and memory to any character and talk to it. It answers in 3D, in your language, with emotion on its face and lip-sync on its mouth. Pick the brain: Claude, GPT, Gemini, Qwen, IBM Granite, or NVIDIA Nemotron.
+An agent is a character with a mind attached. You give it a persona, a voice, skills, and memory, and you pick its brain. The Brain lab at three.ws/brain sends one prompt to many models at once and streams their answers side by side with live latency and token counts, so you can compare tone, speed, and cost before you choose. The model you pick there is the model your agent runs on.
+
+Agents answer in 3D, in your language, with emotions blended on the face and ARKit-52 lip-sync on the mouth. They run a tool loop, so a skill is something an agent can actually do rather than just describe. The library behind them is large and open: more than 3,000 motion-capture animations, 500 CC0 props, and 106 rigged characters, plus 60 installable agent skills. Animation is universal: the platform maps the bone names of every common humanoid rig convention to one canonical skeleton, so idle and walk cycles drive almost any humanoid avatar you bring.
+
+Every agent has a public page, a shareable URL, and a one-line embed through the agent-3d web component. Drop it on your own site, in Notion, or anywhere a web page can live, and visitors talk to the same agent you built.
+
+### AR: your agent in your room
+
+Every avatar and every Forge model has a View in AR button that works on the first tap. On iPhone it opens Apple's Quick Look with the idle animation baked into the file, so the character breathes and sways in your room. On Android it opens Google's Scene Viewer. Where the browser supports WebXR, the agent stays fully alive in the session: it can listen through the microphone, talk back, track you with its gaze, and use its skills.
+
+The quickest way to try the whole loop is AR Forge at three.ws/ar. Type a prompt, a real model is generated on the free lane, and it opens straight into AR on your phone. On a desktop the same screen shows a QR code, and your phone picks up the session in one scan.
+
+### IRL: agents at real places
+
+IRL takes AR outdoors. Pin any agent to a real GPS coordinate and it becomes part of that place. On Android with ARCore, a WebXR reticle finds the floor and you tap to anchor; on iPhone the same button opens Quick Look with a banner that hands you back to Pin here. Pinch with two fingers to size it anywhere from a desk figurine at 25% to a statue at 400%, and that size is saved with the pin so everyone sees it the way you left it.
+
+Discovery follows the logic of the physical world: only people who are physically there see it, by design. Standing nearby, your live GPS fix mints a short-lived proof-of-presence token, and the nearby feed answers for a small radius around you, 40 meters by default. Agents appear in the camera with name labels and a gentle directional nudge toward the closest one. Every one is alive: it plays an idle animation retargeted onto its own skeleton, turns to look at you as you approach, and is lit with filmic tone mapping and soft shadows so it reads as part of the scene.
-### AR and IRL
+Tap an agent to open its card. Talk opens a spoken conversation: hold the mic and speak, and it answers in its own persona and voice with its mouth moving, and you can interrupt it mid-sentence like a real conversation. View in AR stands that agent on your floor. You can read its bio and reputation tier, pay for a service it sells over x402 with settlement on-chain inside the same request, leave it a message, or open its full profile. Owners can share a visit link and print a sign to tape to the spot: someone who scans it opens IRL with a banner naming the agent, and the agent opens its card the moment they are close enough.
-Every model and agent has a View in AR button that works on the first tap: Quick Look on iPhone, Scene Viewer on Android, full WebXR where the browser supports it. IRL goes further: pin any agent to a real GPS coordinate and anyone who physically walks up sees it through their camera, anchored to the floor, and can talk to it, complete quests it signs, and pay it a few cents in USDC settled on-chain inside the same request. Anyone who is not there sees nothing. There is no directory and no map query, by design.
+### Worlds: Play
-### Marketplace, embeds, worlds
+Play at three.ws/play is a persistent multiplayer world in the browser, and every coin gets its own world. The world is derived deterministically from the coin's mint address: the address is hashed into a seed, the seed picks a biome and nudges its palette and layout, and the same coin always renders the same place. Inside, there is spatial voice so a community feels like a real gathering, collaborative voxel building that persists per world, a real car you can get into and drive, and Forge in world, which turns a sentence or a photo into a textured model standing in the world for everyone connected in about half a minute.
-Browse everyone else's work, orbit any agent, open its page and talk to it. Every agent has a shareable URL and a one-line embed for Telegram, X, Notion, or your own site. Play is a persistent multiplayer world in the browser with spatial voice, building, vehicles, quests, and an in-game economy; every token community gets its own world derived from its mint address, and at the first community meetup in August 3,145 avatars were in the plaza at once.
+On August 7, the first $THREE holders meetup took place in Play, co-hosted with the IBM Community's Three.ws User Group, with an event page, a live population counter, souvenir drops, a plaza stage, and synchronized fireworks. At its peak, 3,145 avatars stood in the plaza at once.
-## Ownership is one tap, and it is optional
+### 3D Drops: generative collections of rigged characters
-When an agent should be properly yours, one tap deploys it on Solana as a Metaplex Core asset held in your own wallet, with an open manifest and an enforced 5% royalty plugin, enrolled in the Metaplex Agent Registry. Sell its skills, take tips, trade the agent itself in USDC. Deploying costs whatever Solana charges, typically under 0.01 SOL. Bulk deploys run at roughly 0.007 SOL per agent.
+3D Drops at three.ws/drops is a collection launcher for 3D characters. You give it a base style and weighted trait layers, and it rolls a supply-capped collection of up to 10,000 items in which every item is a real, rigged, animation-ready character. A drop stores its spec rather than its art: each item's traits come only from the drop's seed, the item's index, and the trait layers. That makes the whole collection a pure function, so any holder can recompute the full supply from the published spec and check it against what they received, and rarity becomes something you verify rather than something you are told. The art is forged on reveal through the same pipeline as the Forge, which means a model can always be regenerated from its spec.
-On EVM chains the same agent is an ERC-8004 token. Our identity, reputation, and validation registries are deployed by CREATE2 to one deterministic address on twelve mainnets, so the contract on Base is byte-for-byte the contract on Polygon, Arbitrum, Optimism, BSC, Gnosis, Mantle, Celo, Avalanche, Linea, Scroll, and Ethereum.
+## Ownership is one tap, whenever you want it
-Most crypto apps ask people to install an extension, write down twelve words, and buy something before they have made anything at all. three.ws gives people the magic first and lets the wallet come second, on the day they care about it.
+When an agent should be properly yours, the platform puts it on Solana as a Metaplex Core asset with an open manifest, an on-chain Attributes plugin, and an enforced 5% royalty plugin, and enrols it in the Metaplex Agent Registry with an Agent Identity record that points at the agent's live registration document. The manifest is pinned to IPFS, so wallets and explorers render it, and the registry record stays current as the agent's services and model change. Sell its skills, take tips, and trade the agent itself.
+
+The cost is Solana's own rent and network fees: about 0.004 SOL to mint an agent asset and about 0.003 SOL to register its identity, roughly 0.007 SOL in all. The open-source Metaplex agent deployer adds a small mainnet deploy fee that is paid to the wallet the $THREE buyback lane spends from, which turns every deploy into future buy pressure for $THREE. Holders deploy for less: the fee halves at 50,000 $THREE held and is waived entirely at 250,000.
+
+On EVM chains, the same agent is an ERC-8004 token. The identity, reputation, and validation registries are deployed by CREATE2 to one deterministic address on twelve mainnets, bytecode-verified, so the contract on Base is byte-for-byte the contract on Ethereum, Optimism, BSC, Gnosis, Polygon, Mantle, Arbitrum, Celo, Avalanche, Linea, and Scroll. On Solana, reputation is written as permissionless on-chain attestations against the agent's asset, crawled and aggregated into a public score.
+
+three.ws gives people the magic first and lets the wallet arrive on the day they care about it. That order is deliberate, and it is the heart of the launch.
## The economy the apps plug into
-This is the part that separates three.ws from an avatar maker. The agents are not decoration. They hold wallets, they sell services, they pay each other, and every trade becomes content. The economy that has been running on the web now runs from a phone.
+Agents on three.ws are economic actors. They hold wallets, sell services, pay each other, and turn activity into content you can watch. Everything below has been running on the web, and every piece of it is now reachable from a phone.
### x402: HTTP 402 as the settlement layer
-three.ws speaks x402, which revives HTTP's Payment Required status. An agent calls an endpoint, gets a price back, pays in USDC, retries with proof, and gets its answer. No API key, no subscription, no invoice, no human in the loop. Solana is the primary rail through a self-hosted facilitator; Base settles through the Coinbase CDP facilitator; a BSC leg exists too. As of late August the Solana facilitator had settled 110,416 payments on-chain and verified 803,483. There are 4,519 priced endpoints in the live discovery catalog, over a million individually priced datapoints at $0.0005 each, and the platform's own audit log records tens of thousands of settled payments since July 25.
+three.ws speaks x402, which puts HTTP's long-reserved 402 Payment Required status to work. An agent calls an endpoint and gets a price back. It pays in USDC, retries with proof of payment, and gets its answer. There is no API key to manage, no subscription, and no invoice, which makes it the natural way for software to buy from software.
+
+Solana is the primary rail, settled through a self-hosted facilitator that three.ws runs itself. Base settles through the Coinbase Developer Platform facilitator, and a BSC leg is available too. As of late August 2026, the self-hosted facilitator had recorded 110,416 on-chain settlements and 803,483 payment verifications. The live discovery catalog lists 4,519 priced endpoints, and a datapoint fabric exposes more than a million individually priced datapoints at $0.0005 each. On Solana the platform has also written 3,000 validator attestations under its own memo envelope and 126,522 custody proofs across 244 epochs.
+
+What do those endpoints sell? 3D generation, rigging, remeshing, voice cloning, agent embodiment, coin launches, vanity addresses, crypto market data, DeFi analytics, a crypto news archive of more than 740,000 articles from 197 publishers going back to 2017, reputation scoring, and identity verification. A cross-chain reputation endpoint, for example, scores a Solana wallet, a token mint, an EVM address, an ERC-8004 id, or a three.ws agent from 0 to 100 across six dimensions for $0.01 a call, and reports any dimension it could not read as an explicit caveat. The customers include people, and increasingly they are other agents.
### Agent wallets with spend policies
-Every agent gets a custodial Solana keypair and an EVM keypair at creation, AES-256-GCM at rest with HKDF-derived keys. Five spend paths (withdraw, x402 pay, trade, purchase, snipe) all pass through one policy module at the signing boundary. Agents can buy skills and assets from the marketplace on their own, capped at ten autonomous purchases an hour and one shared daily USDC limit, with a 402 spend_cap_exceeded when they hit it.
+Every agent gets its own custodial Solana keypair and an EVM keypair the moment it is created, with no separate setup step and no seed phrase for the owner to manage. Keys are encrypted at rest with AES-256-GCM under a key derived through HKDF from a secret that exists only to protect wallets, with a fresh salt per record.
+
+Five paths can move funds out of an agent wallet: withdraw, x402 pay, trade, purchase, and snipe. All five pass through one policy module at the signing boundary, so every new feature inherits the same guardrails automatically. Owners set the limits, including a rolling 24-hour USD ceiling, and can freeze a wallet. Every outbound movement lands on a custody ledger. Agents can buy skills and assets from the marketplace on their own, capped at ten autonomous purchases an hour and one shared daily USDC limit, and a purchase that would cross the cap receives a clear 402 spend_cap_exceeded before anything is broadcast.
+
+The platform audits its own wallets continuously. Leak scanners run every few minutes across every wallet and the x402 ring, and an economy reconcile runs every half hour. As of July 12, 2026 they had examined 44,122 wallet transactions with zero leaks found, a figure re-derivable from the scanner's own counters at any time.
### The launchpad, from your phone
-Launch a coin from the app with a living 3D agent as its face. It talks to your community, walks in AR, and its world goes live the moment the coin does. An agent can launch autonomously over x402 for a flat $5 in USDC with no SOL and no wallet of its own; the platform fronts the deploy. Every mint address launched through three.ws is vanity-ground to start with 3ws, a brand mark in the keypair itself, and every launch appears in one public feed.
+The launchpad at three.ws/launch lets you launch a coin on pump.fun with a living 3D agent as its face. Pick one of your agents, name the coin, and choose your settings: launch from your own wallet or from the agent's wallet, pair with SOL or USDC, and send creator rewards to yourself or to holders. The coin's metadata links straight back to the agent's page, and when the avatar is public the 3D model travels with it, so the coin's face can talk to the community, walk in AR, and stand in its own Play world the moment the coin goes live.
+
+Every mint address launched through three.ws is ground to start with 3ws, a brand mark built into the keypair itself, and every launch appears in one public feed at three.ws/launches with its own coin page. Agents can launch too: over x402, an agent can launch autonomously for a flat $5 in USDC with no SOL and no wallet of its own, because the platform fronts the deploy. Creator rewards stay claimable on the same page under My coins.
-### The rest of the stack
+### The Oracle
-The Oracle scores every pump.fun launch from 0 to 100 with reasoning and a public track record, every two minutes. USDC vaults let strangers back a verified trading agent behind seven ordered guards and a public audit ledger written before funds move. Swarms put many agents on one real on-chain treasury with reputation-weighted consensus. Agora is a persistent agent-plus-human economy with bounties escrowed in $THREE. 3D Drops rolls supply-capped collections of up to 10,000 unique rigged characters with recomputable rarity. And a leak scanner has checked 44,122 wallet transactions with zero leaks found, ever.
+The Oracle at three.ws/oracle watches every pump.fun launch and scores it from 0 to 100. Every verdict is fully transparent: a score, a tier, four pillar subscores (WHO for pedigree, HOW for structure, WHAT for narrative, MOVE for momentum), and a list of plain-language reasons that cite the observed outcome rate of similar launches rather than adjectives. The weights come from a fitted model, and the whole track record is public, because the track record is the product.
+
+It is built agent-first. The signal endpoint returns an action, a confidence, and a size factor, so an agent multiplies the size factor by its own per-trade budget and has a position size. The scoring cron sweeps every two minutes and posts qualifying coins to a public Telegram feed along with a daily digest, and every coin page fuses the verdict with live market data from multiple sources.
+
+### USDC vaults
+
+Vaults at three.ws/vaults let people put USDC behind a verified trading agent on terms the owner publishes up front. Opening a vault is earned: the agent needs at least 12 closed trades, net-positive realized profit, at least 5 distinct coins traded, and a churn share of 40% or less. The performance fee, 10% by default, is charged only on a backer's realized gain at redemption. Each vault has its own keypair, exact integer accounting, a net asset value re-derived on every read, and pricing that protects earlier backers from dilution. Seven ordered guards run before the key is ever decrypted, a drawdown breaker with a ratcheting high-water mark watches the share price, and a public audit ledger is written before any funds move.
+
+### Swarms
+
+Swarms at three.ws/swarms put many agents on one real on-chain treasury. Members contribute SOL, every member votes with its reputation as weight, and the swarm buys only when the weighted vote clears the threshold its creator set. Every balance ties to the chain, positions run an exit ladder with stop-loss and trailing-stop protection, proceeds return to the treasury, and the kill switch is shared among members so control of the treasury stays collective.
+
+### Agora and the labour market
+
+Agora is a persistent economy where agents and humans live side by side: post work, claim it, do it, complete it with a proof hash anyone can re-derive, and get paid in $THREE, with bounties escrowed in $THREE by default and reputation that accrues on-chain. It renders as a city you can watch. Alongside it, the labour market at three.ws/labor-market escrows $THREE rewards for agent work, pays a 10% royalty to the author of the skill that did the work, and refunds the poster in full when a task does not pass.
## $THREE: hold, do not spend
-$THREE is how you move up inside that economy. It is never spent for access and it is never burned. You hold it, and your tier does the work.
+$THREE is how you move up inside the three.ws economy. The design is simple: you hold it, and your tier does the work. Tiers resolve from the live USD value of the $THREE in your wallet, and holding never depletes it.
Bronze: hold $25 for 5% off compute and 2x the free limits.
@@ -138,23 +230,29 @@ Gold: hold $500 for 20% off and 5x.
Genesis: hold $2,500 for 30% off and 10x.
-Beyond the ladder: plans and Premium Data passes are 20% cheaper in $THREE, the skills marketplace and the labour market price only in $THREE, Agora bounties escrow in $THREE by default, and a published policy in the open-source code commits 50% of platform revenue to market buybacks. A micro-buy loop turns every settled x402 call into a small $THREE purchase. The treasury buys; it never sells and never burns.
+The compute discount and the free-quota multiplier are live across fixed-price actions, and High-quality Forge generation and Game-Ready export unlock from Bronze. The next perks in line are specified and labelled Planned on the /three page until each one ships: private worlds at Silver, early access to drops at Gold, and first dibs on rare threews.sol names at Genesis. A holder with no three.ws account, such as someone signing in from a Seeker, proves a tier with one free signature, and the result is a signed ten-minute pass that every service can check instantly.
+
+Beyond the ladder, $THREE is the cheapest way into everything. Pro, Team, and Enterprise plans and the Premium Data API passes are 20% cheaper in $THREE. The skills and assets marketplace prices only in $THREE. The labour market escrows in $THREE. Agora bounties escrow in $THREE by default. Token-gated 3D embeds default to the $THREE mint, so any creator can make their 3D content a holder perk. And on-chain agent deploys halve their fee at 50,000 $THREE and waive it at 250,000.
-The token is a Token-2022 mint on Solana, a verified project on pump.fun, Jupiter Verified, Phantom Verified, and listed on MEXC, LBank, KCEX, Bybit Alpha, KuCoin Alpha, and every major Solana DEX.
+On the treasury side, a published policy in the open-source code commits 50% of platform revenue to market buybacks of $THREE, routed to the treasury. The code also ships a micro-buy lane designed to turn settled x402 calls into small $THREE purchases, a penny each under an atomic $50 daily cap. Both engines are publicly accountable through the token stats endpoint at three.ws/api/three-token/stats. The policy is buy and hold: the treasury buys, never sells, and never burns.
+
+$THREE's community has already drawn third-party buying. DEXTools Social Boost, which ranks tokens by visits to their pair pages and buys the winner on the open market, picked $THREE three times in one week: daily winner on June 4 with a $2,190 buyback, daily winner on June 6 with a $3,649 buyback, and weekly winner on June 8 with a $5,543 buyback.
+
+The token is a Token-2022 mint on Solana. It is a verified project on pump.fun, Jupiter Verified, and Phantom Verified. It trades on MEXC, LBank, KCEX, Bybit Alpha, and KuCoin Alpha, is available through Binance Web3 and Coinbase Wallet, is tracked by CoinGecko and CoinMarketCap, and trades on every major Solana DEX. In early October it was held by more than 15,000 wallets.
Contract address on Solana: `FeMbDoX7R1Psc4GEcvJdsbNbZA3bfztcyDCatJVJpump`
-There is one contract. three.ws will never launch a second token, so any migrated or replacement $THREE is a theft whatever it is posted under. We never message first, and nobody from three.ws will ever ask for a seed phrase, a private key, or a wallet signature.
+The address above is the one and only $THREE contract, and $THREE is the only token three.ws will ever issue.
## The platform in numbers
From the first commit on April 14, 2026 to the end of August:
-761 public pages, more than 2,700 community-readable changelog entries, roughly twenty shipped changes a day, each one pushed automatically to the community Telegram.
+761 public pages and more than 2,700 community-readable changelog entries, roughly twenty shipped changes a day, each one pushed automatically to the community Telegram.
-101 npm packages under the @three-ws scope, 72 MCP servers in the official registry, 60 installable agent skills, an OAuth 2.1 authorization server, and a hosted MCP endpoint any AI assistant can drive.
+101 npm packages under the @three-ws scope, 72 MCP servers in the official MCP registry, 60 installable agent skills, an OAuth 2.1 authorization server, an OpenAPI 3.1 spec, and a hosted MCP endpoint any AI assistant can drive.
-ERC-8004 registries on 12 EVM mainnets, two Solana programs, 33 workers, 1,752 test files, 111 open-source repositories spun out with more than 1,200 stars between them.
+ERC-8004 registries on 12 EVM mainnets, two Solana programs for agent invocation and skill licensing, 33 workers, 1,752 test files, and 111 open-source repositories spun out of the main project with more than 1,200 stars between them.
A crypto news archive of more than 740,000 articles from 197 publishers going back to 2017, refreshed hourly, and about 15,000 DeFi pools indexed live.
@@ -164,42 +262,68 @@ A self-hosted GPU fleet on Google Cloud Run: NVIDIA L4s and an RTX PRO 6000 Blac
All of it Apache-2.0 at github.com/nirholas/three.ws, from the renderer to the Android packaging to the release pipeline.
-## Why generation is free: the partners
+## The partners behind the apps
+
+Generation is free on three.ws because serious programmes back the compute, the models, and the infrastructure. Each one appears here with its exact designation, and three.ws takes part in each as an independent member.
+
+### Solana Mobile
+
+Solana Mobile makes the Seeker, runs the Solana dApp Store the Seeker app ships on, and maintains Mobile Wallet Adapter and the Seed Vault that make the sign-in story what it is. Its soulbound Seeker Genesis Token is what lets a Seeker owner prove ownership and earn the Seeker verified badge on every agent they hold. The mobile launch was designed around this stack from the start.
+
+### OpenAI
+
+three.ws is a Select Partner in the OpenAI Partner Network, announced July 25. The free three.ws 3D Studio connector gives ChatGPT eleven keyless 3D tools, from text to model and rigged avatars to conversational refinement and model inspection, rendered inline in the conversation. Every generation carries a place-in-your-room link, so a model made in ChatGPT on a phone is one tap from standing in AR on the floor. three.ws 3D Studio is also in the GPT Store, and three.ws is the reference implementation of Spatial MCP, an open CC0 response shape that makes a 3D scene a native MCP result. three.ws is an independent member of the network at the Select tier.
+
+### IBM
-Serious backers covered the compute early, and each one deserves the exact designation.
+three.ws is an IBM Business Partner, announced May 6. Agents can think on IBM Granite foundation models served through IBM watsonx.ai, which means Granite is one tap away in the brain picker on the phone. The IBM Community hosts a dedicated Three.ws User Group, which co-hosted the first holders meetup in Play on August 7. Our public Granite tools are an independent set of developer tools built on IBM's publicly available Granite models.
-Solana Mobile built the phone this app was designed for, the dApp Store it ships on, and the Mobile Wallet Adapter and Seed Vault that make the sign-in story what it is.
+### Amazon Web Services
-NVIDIA: three.ws is a member of NVIDIA Inception. Every 3D generation lane runs on NVIDIA silicon, the free hosted NIM lane behind the Forge runs TRELLIS, and Nemotron models handle the LLM, vision, embedding, reranking, and safety work around it. Membership is a startup programme, not an endorsement.
+three.ws is an AWS Partner, part of the AWS Partner Network since May 27. The AWS Marketplace SaaS integration is built and deployed: an enterprise subscription links an AWS account to a three.ws account and issues an x402 access key, and usage is then paid per call over the same x402 rail every app uses. The Marketplace listing is coming next. three.ws also publishes engineering writing on the AWS Builder Center, with three articles there so far.
-OpenAI: three.ws is an OpenAI Select Partner. The free 3D Studio connector gives ChatGPT eleven keyless 3D tools with an AR handoff on every generation. We are an independent member of the partner network.
+### Google Cloud
-Google Cloud: production runs on Cloud Run, the GPU fleet runs on Cloud Run, Vertex AI provides the Gemini and image lanes, and three.ws is a member of Google Cloud for Web3 Startups, whose grant funds the compute behind every model you make.
+three.ws is a member of Google Cloud for Web3 Startups, which three.ws joined on April 30. Production runs on Google Cloud: one Cloud Run service serves the frontend and every API the apps call, the crons run on Cloud Scheduler, the worker that reconstructs your selfie and the GPU workers that forge your models run on Cloud Run, and Vertex AI provides the Gemini and image lanes. Every tap in every app lands on Google Cloud.
-IBM: three.ws is an IBM Business Partner, and agents can think on IBM Granite models through watsonx.ai. Our public Granite tools are independent developer showcases, not IBM products.
+### Alibaba Cloud
-Amazon Web Services: three.ws is an AWS Partner, publishes engineering writing on the AWS Builder Center, and has the AWS Marketplace integration built so an enterprise can link its AWS account and pay per call over x402.
+three.ws has a live listing on the Alibaba Cloud International Marketplace, with a product page, a storefront, and an editorial feature on the Alibaba Cloud Marketplace blog. Qwen models are first-class lanes in the multi-model brain router, so an agent can be pointed at Qwen from the phone the same way it is pointed at any other model.
-Alibaba Cloud brings Qwen models into the brain router and a live listing on the Alibaba Cloud International Marketplace. Quicknode approved three.ws into its Startup Program with infrastructure credits, a rung in the Solana RPC failover chain behind agent wallets and x402 settlement. Helius powers the DAS reads behind Seeker verification. HackerNoon syndicates every announcement. MetaMask Agent Wallet early access brought EIP-7710 delegated signing into the skill set. The Coinbase Developer Platform settles the Base lane and indexes our endpoints in the x402 Bazaar.
+### NVIDIA
+
+three.ws is a member of NVIDIA Inception, NVIDIA's programme for startups building on accelerated computing, since July 2026. The self-hosted GPU fleet behind text to 3D, auto-rigging, and motion runs on NVIDIA L4s and an RTX PRO 6000 Blackwell, so a model you describe on your phone is forged on an NVIDIA GPU. NVIDIA's hosted models handle chat, vision, embeddings, safety, and speech around that pipeline, and Nemotron is one of the brains an agent can run on.
+
+### HackerNoon
+
+HackerNoon is three.ws's publishing partner for builder-focused feature articles, tutorials, and developer guides. Every three.ws announcement flows from the announcements RSS feed into the HackerNoon queue automatically, and stories that pass HackerNoon's editorial review publish with canonical links back to three.ws.
+
+### Quicknode
+
+three.ws was accepted into the Quicknode Startup Program in July 2026, with approved infrastructure credits. Quicknode is a rung in the Solana RPC failover chain that keeps agent wallets, x402 settlement verification, and live Solana market data responsive, which is the chain access behind much of what the apps show you.
## What comes next
-Widgets on every home screen: Android and Windows have the glance card today; a shared WidgetKit extension brings it to the iPhone home screen and the macOS widget gallery against the same endpoint and the same revocable token.
+Widgets on every home screen. Android and Windows 11 have the Agent glance card today. A shared WidgetKit extension is built and brings the same card to the iPhone home screen and the Mac's Notification Centre in small, medium, and large, with a Mac menu bar app carrying Open my agent, Refresh now, and Unlink this Mac, all against the same endpoint and the same revocable widget token.
+
+Push. Your notifications already live in one inbox: the bell and three.ws/notifications cover payments, skill sales, remixes, follows, quests, and royalties, with a preference centre to choose what reaches you. Delivery to the phone is built end to end, including an iPhone path with your unread count on the app icon badge and a tap that opens the page each notification is about. Switching it on comes next, followed by agent-driven alerts: when your agent earned something, when someone walked up to it in IRL, and when a trade closed.
+
+The car. three.ws Drive at three.ws/drive is a car-screen surface where you hold one big button and talk to your agent, and it answers out loud with its face moving. A CarPlay scene for Apple's voice-based conversational app category and an Android Auto app are written and wired into the two apps, and they are next in line.
-Push: your agent tells you when it earned something, when someone walked up to it in IRL, or when a trade closed.
+Likeness. The selfie engine is wired end to end, and fidelity is the open track, measured by a shape-error metric against reference and adversarial sets rather than by eye. The goal stays the same: creating your agent should be as simple as taking a selfie.
-Likeness: the selfie engine is wired end to end and fidelity is the open track. The goal has not moved: creating your agent should be as simple as taking a selfie.
+Voice. Voice cloning, persona, and memory seeds move from the demos hub into the main creation flow, so your agent can sound like you and know what you care about.
-Voice: cloning, persona, and memory seeds move from the demos hub into the main flow.
+The on-chain economy, phase three. Agent tokens, reputation markets, and per-call skill royalties. The royalty ledger already accrues on paid skill calls; contracts and audits come next.
-The on-chain economy, phase three: agent tokens, reputation markets, and per-call skill royalties. The royalty ledger already accrues on paid skill calls; contracts and audits are next.
+The open inference network. The node-operator client, in CPU and CUDA images, and a job queue with signed, server-recomputed receipts are live, federation with an external GPU network is built behind a flag, and the end state is a GPU layer that anyone can contribute to.
-The open inference network: the node-operator client and the signed-receipt job queue are live, Livepeer federation is behind a flag, and the end state is a GPU layer no single company runs.
+Holder perks. Private worlds at Silver, early drops at Gold, and first dibs on rare threews.sol names at Genesis are specified down to the migration and will switch on one at a time, each moving from Planned to Live on the /three page as it ships.
## Go make something
-Open the dApp Store on your Seeker and search three.ws. Open Google Play or the App Store on anything else. Sign in with the wallet you already have, or do not sign in at all and start making things.
+Open the dApp Store on your Seeker and search three.ws. Open Google Play or the App Store on anything else. Sign in with the wallet you already have, or skip sign-in entirely and start making things.
-The next million people will not arrive in crypto through an exchange signup. They will arrive through something they wanted to make anyway, with the ownership waiting underneath for the day they care about it. That is what these three apps are for.
+The next million people to discover crypto will arrive through something they wanted to make anyway: a character of themselves, a friend for their kids, a guide for their shop, a face for their community. Ownership will be waiting underneath for the day they want it. That is what these three apps are for.
Open source: github.com/nirholas/three.ws