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.
JavaScript 3d-generationai-agentsanimationavatardigital-humangenerative-aiglbgltfimage-to-3dllmmcpmcp-servermodel-context-protocolsolanatext-to-3dthreejsweb-componentswebglwebxrx402
fix(mirrors): stage standalone GitHub mirrors instead of force-pushing them
nirholasa9c8abfaee5a
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex a1589340d..d20e0155f 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -4,6 +4,10 @@Public history for [three.ws](https://three.ws), newest first. New pages come from `added` dates in data/pages.json; everything else is curated in data/changelog.json. Also available as [JSON](https://three.ws/changelog.json) and [RSS](https://three.ws/changelog.xml), live at [three.ws/changelog](https://three.ws/changelog).+## 2026-10-14++- **Standalone GitHub mirrors now stage instead of force-pushing**: scripts/sync-standalone-repos.mjs force-pushed straight to main on every run, which could silently create duplicate repos for the eleven mirrors already renamed on GitHub and bypassed the owner's push-approval rule. data/standalone-mirrors.json is now the single source of truth for which monorepo directory maps to which public repo, read by every exporter (sync, growth satellites, the awesome list, the skill-repo builder) instead of each keeping its own list. The sync script only stages a snapshot under dist/standalone-mirrors/, fixes any stale pre-Apache-2.0 README or LICENSE footer, and prints the push command for the owner; npm run sync:repos:check compares what is staged against each mirror's live tree and reports drift without writing anything. (`/docs/contributing`) `[infra, docs]`+## 2026-10-13- **Docs · Staked Event Markets** (`/docs/event-markets-staking`): Decision record for staked Event Markets on Solana: the parimutuel model, fee and buyback split, limits, void and refund rules, and the jurisdiction and age questions that stay with the owner.diff --git a/STRUCTURE.md b/STRUCTURE.mdindex 359c4cb67..f10fcd2c1 100644--- a/STRUCTURE.md+++ b/STRUCTURE.md@@ -6,9 +6,9 @@ external developers can find what they need without reading 50 top-leveldirectories.When an internal surface gains an external consumer that needs an independent-release cadence, we promote it to its own published package (and optionally its-own repo via `git subtree split`). See [Promotion path](#promotion-path) at the-bottom.+release cadence, we promote it to its own published package (and, for most+packages, a generated standalone GitHub mirror). See+[Promotion path](#promotion-path) at the bottom.## three.ws surface map@@ -623,21 +623,28 @@ need that the monorepo cannot serve:3. **External contributors blocked.** When the repo size or unrelated CI costis a real friction for outside PRs.-Promotion procedure (when triggered):+Promotion procedure (when triggered): the directory keeps living in this+monorepo (still canonical, still where pull requests go) and gains a+**generated, read-only mirror** instead of being split out. One manifest,+[data/standalone-mirrors.json](data/standalone-mirrors.json), is the source of+truth for which directory maps to which public repo:```bash-# Cleanly split a directory's full history into a new repo-git subtree split --prefix=packages/avatar-schema -b avatar-schema-split-cd ../ && mkdir avatar-schema-repo && cd avatar-schema-repo-git init && git pull ../three.ws avatar-schema-split-git remote add origin https://github.com/nirholas/avatar-schema.git-git push -u origin main-# Then in three.ws: replace the workspace dir with a normal npm dep+# 1. Add an entry: { "repo": "<github name>", "path": "packages/<dir>", "direction": "out", "exporter": "sync", "npm": "<package name or null>" }+# 2. Stage it (snapshots the dir, rewrites package.json's repository field, fixes any stale license footer)+npm run sync:repos -- --only <github name>+# 3. The command above prints the push line; running it is the owner's call+git -C dist/standalone-mirrors/<github name> push --force https://github.com/nirholas/<github name>.git HEAD:main```-Until the trigger fires, splitting is premature: each new repo adds release-overhead, CI cost, and cross-repo PR coordination tax for zero functional-gain.+`scripts/sync-standalone-repos.mjs` never pushes and never calls the GitHub+API itself; it only stages under `dist/standalone-mirrors/` (gitignored) and+prints the command above. `npm run sync:repos:check` compares what is staged+against each mirror's live tree over a codeload tarball and exits non-zero on+drift.++Until a surface has a concrete external consumer, skipping the mirror is+correct: each one adds a repo to keep in sync for zero functional gain.## See alsodiff --git a/data/changelog.json b/data/changelog.jsonindex e1053e1a0..c4cbdf167 100644--- a/data/changelog.json+++ b/data/changelog.json@@ -1,6 +1,16 @@{"$comment": "Curated changelog entries for three.ws, the editorial layer of the public changelog. New PAGE launches are tracked automatically via the `added` field in data/pages.json; this file is for everything else holders care about: improvements, fixes, SDK releases, trading/payments capabilities, security work. scripts/build-page-index.mjs merges both sources into CHANGELOG.md, public/changelog.json, and public/changelog.xml. Newest first. Allowed tags: feature, improvement, fix, sdk, infra, docs, security, desktop (desktop entries become the desktop app's release notes). `link` is optional and must be a live three.ws path.","entries": [+ {+ "date": "2026-10-14",+ "title": "Standalone GitHub mirrors now stage instead of force-pushing",+ "link": "/docs/contributing",+ "summary": "scripts/sync-standalone-repos.mjs force-pushed straight to main on every run, which could silently create duplicate repos for the eleven mirrors already renamed on GitHub and bypassed the owner's push-approval rule. data/standalone-mirrors.json is now the single source of truth for which monorepo directory maps to which public repo, read by every exporter (sync, growth satellites, the awesome list, the skill-repo builder) instead of each keeping its own list. The sync script only stages a snapshot under dist/standalone-mirrors/, fixes any stale pre-Apache-2.0 README or LICENSE footer, and prints the push command for the owner; npm run sync:repos:check compares what is staged against each mirror's live tree and reports drift without writing anything.",+ "tags": [+ "infra",+ "docs"+ ]+ },{"date": "2026-10-13","title": "Free voice is back: the Edge lane speaks again",diff --git a/data/standalone-mirrors.json b/data/standalone-mirrors.jsonnew file mode 100644index 000000000..d553739d0--- /dev/null+++ b/data/standalone-mirrors.json@@ -0,0 +1,916 @@+{+ "$schema": "./standalone-mirrors.schema.json",+ "generated": "manual, re-derived from github.com/nirholas live state on 2026-10-14",+ "mirrors": [+ {+ "repo": "three-ws-skills",+ "path": ".agents/skills",+ "direction": "out",+ "exporter": "skill-repos",+ "npm": null+ },+ {+ "repo": "three-ws-3d-skills",+ "path": ".agents/skills",+ "direction": "out",+ "exporter": "skill-repos",+ "npm": null+ },+ {+ "repo": "three-ws-agent-economy-skills",+ "path": ".agents/skills",+ "direction": "out",+ "exporter": "skill-repos",+ "npm": null+ },+ {+ "repo": "agent-payments-sdk",+ "path": "agent-payments-sdk",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/agent-payments"+ },+ {+ "repo": "three-ws-assistant",+ "path": "assistant-sdk",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/assistant"+ },+ {+ "repo": "awesome-3d-agents",+ "path": "awesome",+ "direction": "out",+ "exporter": "awesome",+ "npm": null+ },+ {+ "repo": null,+ "path": "examples",+ "direction": "out",+ "exporter": "examples",+ "npm": null+ },+ {+ "repo": "x402-bridge",+ "path": "mcp-bridge",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/mcp-bridge"+ },+ {+ "repo": "3d-agent-mcp",+ "path": "mcp-server",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/mcp-server"+ },+ {+ "repo": "activity-mcp",+ "path": "packages/activity-mcp",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/activity-mcp"+ },+ {+ "repo": "agenc",+ "path": "packages/agenc",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/agenc"+ },+ {+ "repo": "agenc-mcp",+ "path": "packages/agenc-mcp",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/agenc-mcp"+ },+ {+ "repo": "three-ws-agent",+ "path": "packages/agent-cli",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/agent"+ },+ {+ "repo": "agent-glance",+ "path": "packages/agent-glance",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/agent-glance"+ },+ {+ "repo": "agent-guards",+ "path": "packages/agent-guards",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/agent-guards"+ },+ {+ "repo": "agent-memory",+ "path": "packages/agent-memory",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/agent-memory"+ },+ {+ "repo": "agent-runtime",+ "path": "packages/agent-runtime",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/agent-runtime"+ },+ {+ "repo": "solana-sniper-mcp",+ "path": "packages/agent-sniper",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/agent-sniper"+ },+ {+ "repo": "agent-vitals",+ "path": "packages/agent-vitals",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/agent-vitals"+ },+ {+ "repo": "agentcore-payments-mcp",+ "path": "packages/agentcore-payments-mcp",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/agentcore-payments-mcp"+ },+ {+ "repo": "three-ws-agents",+ "path": "packages/agents-sdk",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/agents"+ },+ {+ "repo": "agora-mcp",+ "path": "packages/agora-mcp",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/agora-mcp"+ },+ {+ "repo": null,+ "path": "packages/ai-sdk",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/ai-sdk"+ },+ {+ "repo": "alerts-mcp",+ "path": "packages/alerts-mcp",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/alerts-mcp"+ },+ {+ "repo": "alibaba-cloud-mcp",+ "path": "packages/alibaba-cloud-mcp",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/alibaba-cloud-mcp"+ },+ {+ "repo": "three-ws-assets",+ "path": "packages/assets-cli",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/assets"+ },+ {+ "repo": "assistant-mcp",+ "path": "packages/assistant-mcp",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/assistant-mcp"+ },+ {+ "repo": "audio-mcp",+ "path": "packages/audio-mcp",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/audio-mcp"+ },+ {+ "repo": "autopilot-mcp",+ "path": "packages/autopilot-mcp",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/autopilot-mcp"+ },+ {+ "repo": "avatar-agent-mcp",+ "path": "packages/avatar-agent-mcp",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/avatar-agent"+ },+ {+ "repo": "avatar-cli",+ "path": "packages/avatar-cli",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/avatar-cli"+ },+ {+ "repo": "avatar-schema",+ "path": "packages/avatar-schema",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/avatar-schema"+ },+ {+ "repo": "avatar-stream",+ "path": "packages/avatar-stream",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/avatar-stream"+ },+ {+ "repo": "billing-mcp",+ "path": "packages/billing-mcp",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/billing-mcp"+ },+ {+ "repo": "blender-mcp",+ "path": "packages/blender-mcp",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/blender-mcp"+ },+ {+ "repo": "brain-mcp",+ "path": "packages/brain-mcp",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/brain-mcp"+ },+ {+ "repo": null,+ "path": "packages/brownout",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/brownout"+ },+ {+ "repo": "clash-mcp",+ "path": "packages/clash-mcp",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/clash-mcp"+ },+ {+ "repo": "concierge-mcp",+ "path": "packages/concierge-mcp",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/concierge-mcp"+ },+ {+ "repo": "copy-mcp",+ "path": "packages/copy-mcp",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/copy-mcp"+ },+ {+ "repo": "create-agent",+ "path": "packages/create-agent",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/create-agent"+ },+ {+ "repo": "three-ws-forge",+ "path": "packages/forge",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/forge"+ },+ {+ "repo": "glb-diff",+ "path": "packages/glb-diff",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/glb-diff"+ },+ {+ "repo": "glb-tools",+ "path": "packages/glb-tools",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/glb-tools"+ },+ {+ "repo": "three-ws-guardian",+ "path": "packages/guardian",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/guardian"+ },+ {+ "repo": "herald-mcp",+ "path": "packages/herald-mcp",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/herald-mcp"+ },+ {+ "repo": "home-bridge",+ "path": "packages/home-bridge",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/home-bridge"+ },+ {+ "repo": "home-mcp",+ "path": "packages/home-mcp",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/home-mcp"+ },+ {+ "repo": "ibm-watsonx-mcp",+ "path": "packages/ibm-watsonx-mcp",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/ibm-watsonx-mcp"+ },+ {+ "repo": "ibm-x402-mcp",+ "path": "packages/ibm-x402-mcp",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/ibm-x402-mcp"+ },+ {+ "repo": "three-ws-intel",+ "path": "packages/intel",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/intel"+ },+ {+ "repo": "intel-mcp",+ "path": "packages/intel-mcp",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/intel-mcp"+ },+ {+ "repo": "three-ws-irl",+ "path": "packages/irl",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/irl"+ },+ {+ "repo": "knock-mcp",+ "path": "packages/knock-mcp",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/knock-mcp"+ },+ {+ "repo": "three-ws-knock",+ "path": "packages/knock-sdk",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/knock"+ },+ {+ "repo": "kol-mcp",+ "path": "packages/kol-mcp",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/kol-mcp"+ },+ {+ "repo": null,+ "path": "packages/langchain",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/langchain"+ },+ {+ "repo": "loom-mcp",+ "path": "packages/loom-mcp",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/loom-mcp"+ },+ {+ "repo": "nft-marketplace-mcp",+ "path": "packages/marketplace-mcp",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/marketplace-mcp"+ },+ {+ "repo": "mcp-policy",+ "path": "packages/mcp-policy",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/mcp-policy"+ },+ {+ "repo": "metaplex-agent-mcp",+ "path": "packages/metaplex-agent-mcp",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/metaplex-agent-mcp"+ },+ {+ "repo": "three-ws-mocap",+ "path": "packages/mocap",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/mocap"+ },+ {+ "repo": "three-ws-motion",+ "path": "packages/motion",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/motion"+ },+ {+ "repo": "three-ws-names",+ "path": "packages/names",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/names"+ },+ {+ "repo": "token-naming-mcp",+ "path": "packages/naming-mcp",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/naming-mcp"+ },+ {+ "repo": "push-notifications-mcp",+ "path": "packages/notifications-mcp",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/notifications-mcp"+ },+ {+ "repo": "onchain-agent-wallets",+ "path": "packages/onchain-agent-wallets",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/onchain-agent-wallets"+ },+ {+ "repo": "oracle-model",+ "path": "packages/oracle-model",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/oracle-model"+ },+ {+ "repo": "three-ws-portal",+ "path": "packages/portal",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/portal"+ },+ {+ "repo": "crypto-portfolio-mcp",+ "path": "packages/portfolio-mcp",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/portfolio-mcp"+ },+ {+ "repo": "three-ws-pose",+ "path": "packages/pose",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/pose"+ },+ {+ "repo": "provenance-mcp",+ "path": "packages/provenance-mcp",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/provenance-mcp"+ },+ {+ "repo": "pumpfun-mcp",+ "path": "packages/pumpfun-mcp",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/pumpfun-mcp"+ },+ {+ "repo": null,+ "path": "packages/pumpfun-skills",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/pumpfun-skills"+ },+ {+ "repo": "three-ws-react",+ "path": "packages/react",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/react"+ },+ {+ "repo": "readme-3d",+ "path": "packages/readme-3d",+ "direction": "out",+ "exporter": "sync",+ "npm": "readme-3d"+ },+ {+ "repo": "three-ws-render",+ "path": "packages/render",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/render"+ },+ {+ "repo": "three-ws-reputation",+ "path": "packages/reputation",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/reputation"+ },+ {+ "repo": "three-ws-retarget",+ "path": "packages/retarget",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/retarget"+ },+ {+ "repo": "3d-scene-mcp",+ "path": "packages/scene-mcp",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/scene-mcp"+ },+ {+ "repo": "three-ws-see",+ "path": "packages/see",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/see"+ },+ {+ "repo": "three-ws-shipfeed",+ "path": "packages/shipfeed",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/shipfeed"+ },+ {+ "repo": "sign-language",+ "path": "packages/sign-language",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/sign-language"+ },+ {+ "repo": "crypto-signals-mcp",+ "path": "packages/signals-mcp",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/signals-mcp"+ },+ {+ "repo": "skill-license",+ "path": "packages/skill-license",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/skill-license"+ },+ {+ "repo": "solana-memo-media-mcp",+ "path": "packages/solana-memo-media-mcp",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/solana-memo-media-mcp"+ },+ {+ "repo": "spatial-mcp",+ "path": "packages/spatial-mcp",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/spatial-mcp"+ },+ {+ "repo": null,+ "path": "packages/strategies",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/strategies"+ },+ {+ "repo": "three-token-mcp",+ "path": "packages/three-token-mcp",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/three-token-mcp"+ },+ {+ "repo": "three-ws-cli",+ "path": "packages/three-ws-cli",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/cli"+ },+ {+ "repo": "threews-avatar-mcp",+ "path": "packages/threews-avatar-mcp",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/avatar-mcp"+ },+ {+ "repo": "tty-3d",+ "path": "packages/tty-3d",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/tty-3d"+ },+ {+ "repo": "tty-avatar",+ "path": "packages/tty-avatar",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/tty-avatar"+ },+ {+ "repo": "ai-tutor-mcp",+ "path": "packages/tutor-mcp",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/tutor-mcp"+ },+ {+ "repo": null,+ "path": "packages/unity-bridge",+ "direction": "out",+ "exporter": "sync",+ "npm": "com.three-ws.forge-bridge"+ },+ {+ "repo": null,+ "path": "packages/vanity",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/vanity"+ },+ {+ "repo": "solana-vanity-mcp",+ "path": "packages/vanity-mcp",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/vanity-mcp"+ },+ {+ "repo": "viewer-presets",+ "path": "packages/viewer-presets",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/viewer-presets"+ },+ {+ "repo": "image-analysis-mcp",+ "path": "packages/vision-mcp",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/vision-mcp"+ },+ {+ "repo": "three-ws-voice",+ "path": "packages/voice",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/voice"+ },+ {+ "repo": "vscode-3d",+ "path": "packages/vscode-3d",+ "direction": "out",+ "exporter": "sync",+ "npm": "vscode-3d"+ },+ {+ "repo": "vscode-x402",+ "path": "packages/vscode-x402",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/vscode-x402"+ },+ {+ "repo": "three-ws-witness",+ "path": "packages/witness",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/witness"+ },+ {+ "repo": "x402-fetch",+ "path": "packages/x402-fetch",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/x402-fetch"+ },+ {+ "repo": "x402-payments-mcp",+ "path": "packages/x402-mcp",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/x402-mcp"+ },+ {+ "repo": "x402-preflight",+ "path": "packages/x402-preflight",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/x402-preflight"+ },+ {+ "repo": "x402-server",+ "path": "packages/x402-server",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/x402-server"+ },+ {+ "repo": "robinhood-chain-erc8056",+ "path": "robinhood/erc8056",+ "direction": "in",+ "exporter": "sync",+ "npm": "erc8056"+ },+ {+ "repo": "robinhood-chain-alerts",+ "path": "robinhood/hood-alerts",+ "direction": "in",+ "exporter": "sync",+ "npm": "hood-alerts"+ },+ {+ "repo": "robinhood-chain-api",+ "path": "robinhood/hood-api",+ "direction": "in",+ "exporter": "sync",+ "npm": "hood-api"+ },+ {+ "repo": "robinhood-chain-cli",+ "path": "robinhood/hood-cli",+ "direction": "in",+ "exporter": "sync",+ "npm": "hood-cli"+ },+ {+ "repo": "robinhood-chain-connect",+ "path": "robinhood/hood-connect",+ "direction": "in",+ "exporter": "sync",+ "npm": "hood-connect"+ },+ {+ "repo": "robinhood-chain-js",+ "path": "robinhood/hood-js",+ "direction": "in",+ "exporter": "sync",+ "npm": "hood-js"+ },+ {+ "repo": "robinhood-chain-launcher",+ "path": "robinhood/hood-launcher",+ "direction": "in",+ "exporter": "sync",+ "npm": "hood-launcher"+ },+ {+ "repo": "robinhood-chain-mcp",+ "path": "robinhood/hood-mcp",+ "direction": "in",+ "exporter": "sync",+ "npm": "hood-mcp"+ },+ {+ "repo": "robinhood-chain-pay",+ "path": "robinhood/hood-pay",+ "direction": "in",+ "exporter": "sync",+ "npm": "hood-pay"+ },+ {+ "repo": null,+ "path": "robinhood/hood-status",+ "direction": "in",+ "exporter": "sync",+ "npm": null+ },+ {+ "repo": "robinhood-chain-tokenlist",+ "path": "robinhood/hood-tokenlist",+ "direction": "in",+ "exporter": "sync",+ "npm": "hood-tokenlist"+ },+ {+ "repo": "robinhood-chain-traders",+ "path": "robinhood/hood-traders",+ "direction": "in",+ "exporter": "sync",+ "npm": "hood-traders"+ },+ {+ "repo": "robinhood-chain-x402",+ "path": "robinhood/hood402",+ "direction": "in",+ "exporter": "sync",+ "npm": "hood402"+ },+ {+ "repo": "robinhood-chain-kit",+ "path": "robinhood/hoodkit",+ "direction": "in",+ "exporter": "sync",+ "npm": "hoodkit"+ },+ {+ "repo": "learn-robinhood-chain",+ "path": "robinhood/learn-robinhood-chain",+ "direction": "in",+ "exporter": "sync",+ "npm": "learn-robinhood-chain"+ },+ {+ "repo": "robinhood-chain-examples",+ "path": "robinhood/robinhood-chain-examples",+ "direction": "in",+ "exporter": "sync",+ "npm": "robinhood-chain-examples"+ },+ {+ "repo": "robinhood-chain-sdk",+ "path": "robinhood/robinhood-chain-sdk",+ "direction": "in",+ "exporter": "sync",+ "npm": "hoodchain"+ },+ {+ "repo": "threews-agent-starter",+ "path": "satellites/agent-starter",+ "direction": "out",+ "exporter": "growth-satellites",+ "npm": null+ },+ {+ "repo": "glb-quality-gate",+ "path": "satellites/glb-quality-gate",+ "direction": "out",+ "exporter": "growth-satellites",+ "npm": null+ },+ {+ "repo": "oracle-desk",+ "path": "satellites/oracle-desk",+ "direction": "out",+ "exporter": "growth-satellites",+ "npm": null+ },+ {+ "repo": "3d-avatar-companion",+ "path": "walk-sdk",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/walk"+ },+ {+ "repo": null,+ "path": "x402-modal-sdk",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/x402-modal"+ },+ {+ "repo": null,+ "path": "x402-payment-modal",+ "direction": "out",+ "exporter": "sync",+ "npm": "@three-ws/x402-payment-modal"+ }+ ]+}diff --git a/data/standalone-mirrors.schema.json b/data/standalone-mirrors.schema.jsonnew file mode 100644index 000000000..e814cdd80--- /dev/null+++ b/data/standalone-mirrors.schema.json@@ -0,0 +1,50 @@+{+ "$schema": "http://json-schema.org/draft-07/schema#",+ "$id": "https://three.ws/schemas/standalone-mirrors.schema.json",+ "title": "three.ws standalone mirrors",+ "description": "One entry per monorepo directory that has (or could have) a public, generated, read-only GitHub mirror. scripts/sync-standalone-repos.mjs and the other exporters (export-growth-satellites.mjs, build-awesome.mjs, build-standalone-skill-repos.mjs) read this manifest instead of hardcoding repo names. The monorepo stays the canonical source; mirrors are one-way snapshots.",+ "type": "object",+ "required": ["mirrors"],+ "properties": {+ "$schema": { "type": "string" },+ "generated": { "type": "string" },+ "mirrors": {+ "type": "array",+ "minItems": 1,+ "items": { "$ref": "#/definitions/mirror" }+ }+ },+ "additionalProperties": false,+ "definitions": {+ "mirror": {+ "type": "object",+ "required": ["repo", "path", "direction", "exporter", "npm"],+ "properties": {+ "repo": {+ "type": ["string", "null"],+ "description": "GitHub repo slug under github.com/nirholas (owner implied), or null when no mirror exists yet."+ },+ "path": {+ "type": "string",+ "minLength": 1,+ "description": "Directory in this monorepo, relative to the repo root."+ },+ "direction": {+ "type": "string",+ "enum": ["out", "in"],+ "description": "\"out\": this monorepo directory is exported to the mirror. \"in\": the mirror (or an external repo) is the source of truth and this directory is a reference copy."+ },+ "exporter": {+ "type": "string",+ "enum": ["sync", "growth-satellites", "examples", "awesome", "skill-repos"],+ "description": "Which script produces/consumes this mirror: sync-standalone-repos.mjs, export-growth-satellites.mjs, export-satellites.mjs, build-awesome.mjs --standalone, or build-standalone-skill-repos.mjs."+ },+ "npm": {+ "type": ["string", "null"],+ "description": "Published npm package name for this path, or null when it is not an npm package."+ }+ },+ "additionalProperties": false+ }+ }+}diff --git a/docs/ALL.md b/docs/ALL.mdindex 1fd1a2168..be531ebe6 100644--- a/docs/ALL.md+++ b/docs/ALL.md@@ -1,7 +1,7 @@<!-- GENERATED by scripts/combine-docs.mjs — do not edit by hand. Edit the source files under docs/ and re-run. --># three.ws — Combined Documentation-> Single-file snapshot of every document under [`docs/`](.). Generated 2026-10-13 from **867 files** (~13366 KB).+> Single-file snapshot of every document under [`docs/`](.). Generated 2026-10-14 from **882 files** (~13434 KB).> The individual source files remain the canonical, editable copies — this file is a read-only aggregate.## Table of contents@@ -53,468 +53,481 @@- [announcement-coverage-telegram.md](#sec-103)- [announcement-coverage.md](#sec-104)- [announcement-factory.md](#sec-105)-- [api-reference.md](#sec-124)-- [approvals.md](#sec-126)-- [apps.md](#sec-127)-- [ar-studio.md](#sec-128)-- [ar.md](#sec-129)-- [architecture.md](#sec-130)-- [assistant-widget.md](#sec-131)-- [atlas.md](#sec-132)-- [atomic.md](#sec-133)-- [authentication.md](#sec-138)-- [autonomous-economy.md](#sec-139)-- [autonomous-x402.md](#sec-140)-- [autopilot.md](#sec-141)-- [avatar-artifact.md](#sec-142)-- [avatar-cli.md](#sec-143)-- [avatar-creation.md](#sec-144)-- [avatar-engines.md](#sec-145)-- [avatar-fidelity-program.md](#sec-146)-- [avatar-inspector.md](#sec-147)-- [avatar-pipeline.md](#sec-148)-- [avatar-reconstruction.md](#sec-149)-- [avatar-studio.md](#sec-150)-- [avatar-thumbnails.md](#sec-151)-- [avatar-wardrobe.md](#sec-152)-- [aws-builder-center-agent-commerce-spine.md](#sec-153)-- [aws-builder-center-agent-payment-sessions.md](#sec-154)-- [aws-builder-center-before-the-signature.md](#sec-155)-- [aws-builder-center-claims-ledger.md](#sec-156)-- [aws-builder-center-immutable-embed-releases.md](#sec-157)-- [aws-builder-center-marketplace-x402.md](#sec-158)-- [aws-builder-center-mcp-agents.md](#sec-159)-- [aws-builder-center-open-weight-3d-forge.md](#sec-160)-- [aws-builder-center-universal-retargeting.md](#sec-161)-- [aws-builder-center.md](#sec-162)-- [aws-marketplace-listing-kit.md](#sec-163)-- [aws-marketplace.md](#sec-164)-- [aws-partner-spotlight.md](#sec-165)-- [big-tech-recognition-week.md](#sec-166)-- [blender-mcp.md](#sec-167)-- [bnb-babt-findings.md](#sec-168)-- [bnb-payments.md](#sec-169)-- [bnb-vault.md](#sec-170)-- [bnb-world.md](#sec-171)-- [brain.md](#sec-172)-- [brownout.md](#sec-173)-- [btn-pill-migration.md](#sec-174)-- [build.md](#sec-175)-- [ca2x402.md](#sec-176)-- [cad-forge.md](#sec-177)-- [capture.md](#sec-178)-- [carplay.md](#sec-179)-- [changelog.md](#sec-180)-- [character-library.md](#sec-181)-- [character-studio.md](#sec-182)-- [chart-companion.md](#sec-183)-- [chat-gateways.md](#sec-184)-- [chatgpt-3d-studio-gpt.md](#sec-185)-- [chatgpt-ar.md](#sec-186)-- [checkout-companion.md](#sec-187)-- [choreography.md](#sec-188)-- [circulation-engine.md](#sec-189)-- [clash.md](#sec-190)-- [cli.md](#sec-191)-- [clip-director.md](#sec-192)-- [coin-launches.md](#sec-193)-- [coin-pages.md](#sec-194)-- [coin-wars.md](#sec-195)-- [coin3d-embed.md](#sec-196)-- [coingecko-listing-update-2026-08.md](#sec-197)-- [coinmarketcap-article-2026-09-agent-economy.md](#sec-198)-- [coinmarketcap-article-2026-10-copy-trading.md](#sec-199)-- [coinmarketcap-article-2026-10-radar-strategy-lab.md](#sec-200)-- [coinmarketcap-article-2026-10-sniper-oracle.md](#sec-201)-- [coinmarketcap-article-2026-10-solana-reputation.md](#sec-202)-- [coinmarketcap-article-2026-10-vanity-mints.md](#sec-203)-- [coinmarketcap-article-2026-10-x402-failure-paths.md](#sec-204)-- [coinmarketcap-article-play.md](#sec-205)-- [coinmarketcap-article.md](#sec-206)-- [coinmarketcap-live-article.md](#sec-207)-- [community.md](#sec-208)-- [companion.md](#sec-209)-- [compose.md](#sec-210)-- [concierge.md](#sec-211)-- [configuration.md](#sec-212)-- [contributing.md](#sec-219)-- [copy-coach.md](#sec-224)-- [copy-trading.md](#sec-225)-- [cosmos.md](#sec-226)-- [crawl.md](#sec-227)-- [create-agent.md](#sec-228)-- [creator-portfolio.md](#sec-229)-- [crews.md](#sec-230)-- [crypto-api.md](#sec-231)-- [custody.md](#sec-232)-- [daily-forge.md](#sec-233)-- [daily-match.md](#sec-234)-- [demo-routes.md](#sec-235)-- [deployment.md](#sec-236)-- [deployments.md](#sec-237)-- [desktop-local-runtime.md](#sec-238)-- [desktop-menu-bar-panel.md](#sec-239)-- [desktop-widgets.md](#sec-240)-- [desktop.md](#sec-241)-- [destination-whitelist.md](#sec-242)-- [developer-plans.md](#sec-243)-- [developer-platform.md](#sec-244)-- [devto-mcp-fleet-post.md](#sec-245)-- [dextools.md](#sec-246)-- [diorama.md](#sec-247)-- [do-i-need-crypto.md](#sec-248)-- [doc-freshness.md](#sec-249)-- [docs-world.md](#sec-250)-- [domains.md](#sec-251)-- [draft-agent-mint.md](#sec-252)-- [drops.md](#sec-253)-- [economy-heartbeat.md](#sec-254)-- [economy-master.md](#sec-255)-- [economy-solver.md](#sec-256)-- [editor.md](#sec-257)-- [education-pilot-bucharest.md](#sec-258)-- [embedding.md](#sec-259)-- [embody.md](#sec-260)-- [engine-bridges.md](#sec-261)-- [engine-qa.md](#sec-262)-- [erc8004.md](#sec-263)-- [event-markets-staking.md](#sec-265)-- [event-markets.md](#sec-266)-- [event-souvenirs.md](#sec-293)-- [everything.md](#sec-294)-- [examples.md](#sec-295)-- [exit-lab.md](#sec-296)-- [experiments-agent-launch-funnel.md](#sec-297)-- [experiments-autonomous-trading.md](#sec-298)-- [experiments.md](#sec-299)-- [fact-check.md](#sec-300)-- [fade-radar.md](#sec-301)-- [farcaster-memory-seeding.md](#sec-302)-- [fee-bridge.md](#sec-303)-- [feedback.md](#sec-304)-- [field.md](#sec-305)-- [financial-controls.md](#sec-306)-- [first-contribution.md](#sec-307)-- [forge-background-generation.md](#sec-308)-- [forge-desktop.md](#sec-309)-- [forge-off.md](#sec-310)-- [forge-pipeline.md](#sec-311)-- [forge-workflows.md](#sec-312)-- [forge.md](#sec-313)-- [forged.md](#sec-314)-- [fork-trade.md](#sec-315)-- [free-crypto-apis.md](#sec-316)-- [free-llm-providers.md](#sec-317)-- [galaxy.md](#sec-319)-- [generation-watch.md](#sec-320)-- [genesis.md](#sec-321)-- [genome.md](#sec-322)-- [ghost-copy.md](#sec-323)-- [github-growth.md](#sec-324)-- [github-memory-seeding.md](#sec-325)-- [glance.md](#sec-326)-- [glasses.md](#sec-327)-- [globe.md](#sec-330)-- [google-cloud-community-post.md](#sec-331)-- [google-x-accounts.md](#sec-332)-- [grok-bot.md](#sec-333)-- [grok.md](#sec-334)-- [growth-programs.md](#sec-335)-- [guardian.md](#sec-336)-- [guards.md](#sec-337)-- [herald.md](#sec-338)-- [hold-to-access.md](#sec-339)-- [home-assistant-community-post.md](#sec-340)-- [home-households.md](#sec-341)-- [home-plans.md](#sec-342)-- [home-privacy.md](#sec-343)-- [home-relay-threat-model.md](#sec-344)-- [home-relay.md](#sec-345)-- [home-satellite.md](#sec-346)-- [home-scene.md](#sec-347)-- [home-security.md](#sec-348)-- [home-voice.md](#sec-349)-- [how-forge-works.md](#sec-350)-- [how-it-works.md](#sec-351)-- [huggingface-3d-ai-agent-platform.md](#sec-352)-- [huggingface-agent-feedback-loop.md](#sec-353)-- [huggingface.md](#sec-354)-- [i18n.md](#sec-355)-- [ibm-community-any-skeleton-animation-post.md](#sec-356)-- [ibm-community-any-skeleton-animation-thread.md](#sec-357)-- [ibm-community-article.md](#sec-358)-- [ibm-community-blog-meetup-jessica.md](#sec-359)-- [ibm-community-defi-3d-sperax-post.md](#sec-360)-- [ibm-community-defi-3d-sperax-publishing-kit.md](#sec-361)-- [ibm-community-defi-3d-sperax.md](#sec-362)-- [ibm-community-doc-freshness-post.md](#sec-363)-- [ibm-community-doc-freshness-thread.md](#sec-364)-- [ibm-community-governed-agents-post.md](#sec-365)-- [ibm-community-governed-agents-thread.md](#sec-366)-- [ibm-community-live-reaction-jessica.md](#sec-367)-- [ibm-community-long-running-mcp-tools-post.md](#sec-368)-- [ibm-community-long-running-mcp-tools-thread.md](#sec-369)-- [ibm-community-recap-jessica.md](#sec-370)-- [ibm-community-recap-nichxbt.md](#sec-371)-- [ibm-community-thread.md](#sec-372)-- [ibm-community.md](#sec-373)-- [ibm-event-offer-map.md](#sec-374)-- [ibm-next-event.md](#sec-375)-- [ibm-visibility-map.md](#sec-376)-- [ibm-x402-mcp.md](#sec-377)-- [ibm.md](#sec-378)-- [image-to-3d.md](#sec-379)-- [in-game-economy.md](#sec-380)-- [inference-billing.md](#sec-381)-- [inference-node-operator.md](#sec-382)-- [integrations.md](#sec-383)-- [introduction.md](#sec-384)-- [ios-app.md](#sec-385)-- [irl.md](#sec-386)-- [issue-resolution-2026-09-15.md](#sec-389)-- [js-api.md](#sec-390)-- [knock.md](#sec-391)-- [kol-tracker.md](#sec-392)-- [labor-market.md](#sec-393)-- [launch-intents.md](#sec-394)-- [launch-lanes.md](#sec-395)-- [launch-usecases.md](#sec-396)-- [launchpad.md](#sec-397)-- [layers.md](#sec-398)-- [likeness-eval.md](#sec-399)-- [lipsync.md](#sec-400)-- [liquid-glass.md](#sec-401)-- [listings-registry.md](#sec-402)-- [listings.md](#sec-403)-- [live-docs.md](#sec-404)-- [live-steps.md](#sec-405)-- [make-your-agent.md](#sec-406)-- [market-data-api.md](#sec-407)-- [marketplace.md](#sec-408)-- [materialize.md](#sec-409)-- [mcp-3d-studio.md](#sec-410)-- [mcp-agent.md](#sec-411)-- [mcp-safety.md](#sec-412)-- [mcp-solana-memo-media.md](#sec-413)-- [mcp-studio.md](#sec-414)-- [mcp-tools.md](#sec-415)-- [mcp-x402-bazaar.md](#sec-416)-- [mcp.md](#sec-417)-- [media-api.md](#sec-418)-- [memetic-launcher.md](#sec-419)-- [memory.md](#sec-420)-- [meta-allocator.md](#sec-421)-- [mint-mark.md](#sec-422)-- [minted.md](#sec-423)-- [mocap-studio.md](#sec-430)-- [model-diff.md](#sec-431)-- [modly.md](#sec-432)-- [money-feed.md](#sec-433)-- [money-flow-map.md](#sec-434)-- [money-map.md](#sec-435)-- [monitor.md](#sec-436)-- [motion-swap.md](#sec-437)-- [multi-agent.md](#sec-438)-- [native-launchpad.md](#sec-439)-- [native-widgets.md](#sec-440)-- [news-rights.md](#sec-441)-- [notifications.md](#sec-442)-- [nvidia-apps-catalog-listing.md](#sec-443)-- [nvidia-apps-catalog-request.md](#sec-444)-- [nvidia-forum-browser-digital-human.md](#sec-445)-- [nvidia-forum-gpu-fleet-post.md](#sec-446)-- [nvidia-forum-model-retirement-post.md](#sec-447)-- [nvidia-gtc-2027-poster.md](#sec-448)-- [nvidia-inception.md](#sec-449)-- [nvidia-models.md](#sec-450)-- [nvidia-nemotron-ask-the-experts-questions.md](#sec-451)-- [nvidia-nemotron-spotlight.md](#sec-452)-- [nvidia-ngc-listing.md](#sec-453)-- [nvidia-visibility-map.md](#sec-454)-- [object-library.md](#sec-455)-- [okx-marketplace.md](#sec-456)-- [onboarding-tier.md](#sec-457)-- [onchain-agents.md](#sec-458)-- [open-source-ecosystem.md](#sec-459)-- [open-source-footprint.md](#sec-460)-- [open-source-friday-plan.md](#sec-461)-- [openai-community-3d-studio-post.md](#sec-462)-- [openai-community-physical-world-post.md](#sec-463)-- [openai-listing-channels.md](#sec-464)-- [oracle-model.md](#sec-465)-- [oracle-trading-mcp-plan.md](#sec-466)-- [oracle.md](#sec-467)-- [oss-adoption-2026-09.md](#sec-468)-- [overlay-audit.md](#sec-469)-- [package-extraction.md](#sec-470)-- [page-performance.md](#sec-471)-- [paired-coins.md](#sec-472)-- [papertrade.md](#sec-473)-- [partners.md](#sec-474)-- [pay-skills-listing.md](#sec-487)-- [payment-sessions.md](#sec-488)-- [permissions.md](#sec-489)-- [perps.md](#sec-490)-- [persona-hub.md](#sec-491)-- [pill-mascot.md](#sec-492)-- [plan-checkout.md](#sec-493)-- [play-boot-performance.md](#sec-494)-- [play-forge-in-world.md](#sec-495)-- [play-hardening.md](#sec-496)-- [play-live-events.md](#sec-497)-- [play-vehicles.md](#sec-498)-- [pocket.md](#sec-499)-- [pons-launch.md](#sec-500)-- [popular-3d-github-repos.md](#sec-501)-- [portal.md](#sec-502)-- [portfolio.md](#sec-503)-- [premium.md](#sec-504)-- [press-kit.md](#sec-505)-- [procedural-animation.md](#sec-506)-- [product-demo.md](#sec-507)-- [prompts.md](#sec-508)-- [provenance.md](#sec-556)-- [publishing-program-2026-09.md](#sec-557)-- [pump-claims-channel.md](#sec-558)-- [pump-fun-mcp-edge.md](#sec-559)-- [pump-launch-repos.md](#sec-560)-- [pump-launcher.md](#sec-561)-- [pump-platform-fee.md](#sec-562)-- [quick-start.md](#sec-593)-- [radar.md](#sec-594)-- [reasoning-ledger.md](#sec-595)-- [recurring-payments.md](#sec-596)-- [remix.md](#sec-597)-- [reputation-staking-market.md](#sec-598)-- [reputation.md](#sec-599)-- [resilience.md](#sec-615)-- [restyle.md](#sec-616)-- [rig-doctor.md](#sec-617)-- [risk-acknowledgment.md](#sec-618)-- [rivalries.md](#sec-619)-- [robinhood-chain-markets.md](#sec-620)-- [robinhood-portfolios.md](#sec-621)-- [run-receipts-x-reply-and-thread.md](#sec-622)-- [run-receipts.md](#sec-623)-- [sas-attestations.md](#sec-624)-- [scene-studio.md](#sec-625)-- [sdk.md](#sec-626)-- [security.md](#sec-627)-- [seed-quality.md](#sec-628)-- [seeker-app.md](#sec-629)-- [seeker-publishing.md](#sec-630)-- [seeker-submission-day.md](#sec-631)-- [seeker-video.md](#sec-632)-- [selfie-to-avatar.md](#sec-633)-- [sentiment-scout.md](#sec-634)-- [seo.md](#sec-635)-- [share-and-embed.md](#sec-636)-- [shared-utilities.md](#sec-637)-- [shipfeed.md](#sec-638)-- [short-form-venue-kit-2026-09.md](#sec-639)-- [showcase.md](#sec-640)-- [sign-language.md](#sec-641)-- [signals.md](#sec-642)-- [sim-readiness.md](#sec-643)-- [site-performance.md](#sec-644)-- [sketchfab.md](#sec-645)-- [skill-bundles.md](#sec-646)-- [skill-import.md](#sec-647)-- [skill-royalties.md](#sec-648)-- [skills.md](#sec-649)-- [smart-contracts.md](#sec-650)-- [smart-home.md](#sec-651)-- [smart-money.md](#sec-652)-- [sniper-autonomy.md](#sec-653)-- [social-layer.md](#sec-654)-- [solana-pumpfun.md](#sec-655)-- [solana-reputation.md](#sec-656)-- [solana.md](#sec-657)-- [sonar.md](#sec-658)-- [spatial-mcp.md](#sec-659)-- [splat.md](#sec-661)-- [spotlight.md](#sec-662)-- [stage.md](#sec-663)-- [standalone-repo-playbook.md](#sec-664)-- [standalone-repos.md](#sec-665)-- [start-here.md](#sec-666)-- [strategy-objects.md](#sec-667)-- [swarms.md](#sec-669)-- [syndicates.md](#sec-670)-- [syndication.md](#sec-671)-- [talking-avatar-video.md](#sec-672)-- [team-chat.md](#sec-673)-- [teams.md](#sec-674)-- [terminal.md](#sec-675)-- [the-first-19-weeks.md](#sec-676)-- [three-microbuy.md](#sec-677)-- [three-thesis.md](#sec-678)-- [threejs-forum-post.md](#sec-679)-- [timeline.md](#sec-680)-- [token-gated-3d-embeds.md](#sec-681)-- [tokens-xyz.md](#sec-682)-- [trade-receipts.md](#sec-683)-- [trade-rooms.md](#sec-684)-- [trader-card-embed.md](#sec-685)-- [trader-card.md](#sec-686)-- [trader-duels.md](#sec-687)-- [trader-passport.md](#sec-688)-- [trader-wrapped.md](#sec-689)-- [trading-arenas.md](#sec-690)-- [trading-copilot.md](#sec-691)-- [trading-experiment.md](#sec-692)-- [trading-hub.md](#sec-693)-- [trading-quests.md](#sec-694)-- [trading-surfaces.md](#sec-695)-- [trading-tools.md](#sec-696)-- [trenches.md](#sec-697)-- [triage.md](#sec-698)-- [troubleshooting.md](#sec-699)-- [trust-primitives.md](#sec-700)-- [tty-avatar.md](#sec-701)-- [tty.md](#sec-702)-- [ui-juice.md](#sec-774)-- [uniswap-v4-hooks.md](#sec-775)-- [user-wallet.md](#sec-777)-- [validation.md](#sec-790)-- [vanity.md](#sec-791)-- [vaults.md](#sec-792)-- [vendored-design-libraries.md](#sec-793)-- [viability.md](#sec-794)-- [viewer.md](#sec-795)-- [voice-lab.md](#sec-796)-- [vscode.md](#sec-797)-- [walk-leaderboard.md](#sec-798)-- [web-component.md](#sec-799)-- [widget-api.md](#sec-800)-- [widget-studio.md](#sec-801)-- [widgets.md](#sec-802)-- [witness.md](#sec-803)-- [workbench.md](#sec-804)-- [world-lines.md](#sec-805)-- [x-account-appeal.md](#sec-806)-- [x-accounts.md](#sec-807)-- [x-archive.md](#sec-808)-- [x-article-author-brief.md](#sec-811)-- [x-content-pipeline.md](#sec-812)-- [x-memory-seeding.md](#sec-813)-- [x-mention-avatar.md](#sec-814)-- [x-mention-bot.md](#sec-815)-- [x-mention-image3d.md](#sec-816)-- [x-story-author-brief.md](#sec-849)-- [x-story-authoring.md](#sec-850)-- [x402-buyer.md](#sec-851)-- [x402-dev-tools.md](#sec-852)-- [x402-distribution.md](#sec-853)-- [x402-endpoints.md](#sec-854)-- [x402-fresh-workers.md](#sec-855)-- [x402-preflight.md](#sec-856)-- [x402-ring-economy.md](#sec-857)-- [x402-settlement-pending.md](#sec-858)-- [x402-solana-july-roundup-response.md](#sec-859)-- [x402-studio.md](#sec-860)-- [x402-vscode.md](#sec-861)-- [x402.md](#sec-862)+- [api-reference.md](#sec-125)+- [approvals.md](#sec-127)+- [apps.md](#sec-128)+- [ar-studio.md](#sec-129)+- [ar.md](#sec-130)+- [architecture.md](#sec-131)+- [assistant-widget.md](#sec-132)+- [atlas.md](#sec-133)+- [atomic.md](#sec-134)+- [authentication.md](#sec-139)+- [autonomous-economy.md](#sec-140)+- [autonomous-x402.md](#sec-141)+- [autopilot.md](#sec-142)+- [avatar-artifact.md](#sec-143)+- [avatar-cli.md](#sec-144)+- [avatar-creation.md](#sec-145)+- [avatar-engines.md](#sec-146)+- [avatar-fidelity-program.md](#sec-147)+- [avatar-inspector.md](#sec-148)+- [avatar-pipeline.md](#sec-149)+- [avatar-reconstruction.md](#sec-150)+- [avatar-studio.md](#sec-151)+- [avatar-thumbnails.md](#sec-152)+- [avatar-wardrobe.md](#sec-153)+- [aws-builder-center-agent-commerce-spine.md](#sec-154)+- [aws-builder-center-agent-payment-sessions.md](#sec-155)+- [aws-builder-center-before-the-signature.md](#sec-156)+- [aws-builder-center-claims-ledger.md](#sec-157)+- [aws-builder-center-immutable-embed-releases.md](#sec-158)+- [aws-builder-center-marketplace-x402.md](#sec-159)+- [aws-builder-center-mcp-agents.md](#sec-160)+- [aws-builder-center-open-weight-3d-forge.md](#sec-161)+- [aws-builder-center-universal-retargeting.md](#sec-162)+- [aws-builder-center.md](#sec-163)+- [aws-marketplace-listing-kit.md](#sec-164)+- [aws-marketplace.md](#sec-165)+- [aws-partner-spotlight.md](#sec-166)+- [big-tech-recognition-week.md](#sec-167)+- [blender-mcp.md](#sec-168)+- [bnb-babt-findings.md](#sec-169)+- [bnb-payments.md](#sec-170)+- [bnb-vault.md](#sec-171)+- [bnb-world.md](#sec-172)+- [brain.md](#sec-173)+- [brownout.md](#sec-174)+- [btn-pill-migration.md](#sec-175)+- [build.md](#sec-176)+- [ca2x402.md](#sec-177)+- [cad-forge.md](#sec-178)+- [capture.md](#sec-179)+- [carplay.md](#sec-180)+- [changelog.md](#sec-181)+- [character-library.md](#sec-182)+- [character-studio.md](#sec-183)+- [chart-companion.md](#sec-184)+- [chat-gateways.md](#sec-185)+- [chatgpt-3d-studio-gpt.md](#sec-186)+- [chatgpt-ar.md](#sec-187)+- [checkout-companion.md](#sec-188)+- [choreography.md](#sec-189)+- [circulation-engine.md](#sec-190)+- [clash.md](#sec-191)+- [cli.md](#sec-192)+- [clip-director.md](#sec-193)+- [coin-launches.md](#sec-194)+- [coin-pages.md](#sec-195)+- [coin-wars.md](#sec-196)+- [coin3d-embed.md](#sec-197)+- [coingecko-listing-update-2026-08.md](#sec-198)+- [coinmarketcap-article-2026-09-agent-economy.md](#sec-199)+- [coinmarketcap-article-2026-10-copy-trading.md](#sec-200)+- [coinmarketcap-article-2026-10-radar-strategy-lab.md](#sec-201)+- [coinmarketcap-article-2026-10-sniper-oracle.md](#sec-202)+- [coinmarketcap-article-2026-10-solana-reputation.md](#sec-203)+- [coinmarketcap-article-2026-10-vanity-mints.md](#sec-204)+- [coinmarketcap-article-2026-10-x402-failure-paths.md](#sec-205)+- [coinmarketcap-article-play.md](#sec-206)+- [coinmarketcap-article.md](#sec-207)+- [coinmarketcap-live-article.md](#sec-208)+- [community.md](#sec-209)+- [companion.md](#sec-210)+- [compose.md](#sec-211)+- [concierge.md](#sec-212)+- [configuration.md](#sec-213)+- [contributing.md](#sec-220)+- [copy-coach.md](#sec-225)+- [copy-trading.md](#sec-226)+- [cosmos.md](#sec-227)+- [crawl.md](#sec-228)+- [create-agent.md](#sec-229)+- [creator-portfolio.md](#sec-230)+- [crews.md](#sec-231)+- [crypto-api.md](#sec-232)+- [custody.md](#sec-233)+- [daily-forge.md](#sec-234)+- [daily-match.md](#sec-235)+- [demo-routes.md](#sec-236)+- [deployment.md](#sec-237)+- [deployments.md](#sec-238)+- [desktop-local-runtime.md](#sec-239)+- [desktop-menu-bar-panel.md](#sec-240)+- [desktop-widgets.md](#sec-241)+- [desktop.md](#sec-242)+- [destination-whitelist.md](#sec-243)+- [developer-plans.md](#sec-244)+- [developer-platform.md](#sec-245)+- [devto-mcp-fleet-post.md](#sec-246)+- [dextools.md](#sec-247)+- [diorama.md](#sec-248)+- [discord-activity.md](#sec-249)+- [dissolve.md](#sec-250)+- [do-i-need-crypto.md](#sec-251)+- [doc-freshness.md](#sec-252)+- [docs-world.md](#sec-253)+- [domains.md](#sec-254)+- [draft-agent-mint.md](#sec-255)+- [drops.md](#sec-256)+- [economy-heartbeat.md](#sec-257)+- [economy-master.md](#sec-258)+- [economy-solver.md](#sec-259)+- [editor.md](#sec-260)+- [education-pilot-bucharest.md](#sec-261)+- [embedding.md](#sec-262)+- [embody.md](#sec-263)+- [engine-bridges.md](#sec-264)+- [engine-qa.md](#sec-265)+- [erc8004.md](#sec-266)+- [event-markets-staking.md](#sec-268)+- [event-markets.md](#sec-269)+- [event-souvenirs.md](#sec-296)+- [everything.md](#sec-297)+- [examples.md](#sec-298)+- [exit-lab.md](#sec-299)+- [experiments-agent-launch-funnel.md](#sec-300)+- [experiments-autonomous-trading.md](#sec-301)+- [experiments.md](#sec-302)+- [fact-check.md](#sec-303)+- [fade-radar.md](#sec-304)+- [farcaster-memory-seeding.md](#sec-305)+- [fee-bridge.md](#sec-306)+- [feedback.md](#sec-307)+- [field.md](#sec-308)+- [financial-controls.md](#sec-309)+- [first-contribution.md](#sec-310)+- [forge-background-generation.md](#sec-311)+- [forge-desktop.md](#sec-312)+- [forge-off.md](#sec-313)+- [forge-pipeline.md](#sec-314)+- [forge-workflows.md](#sec-315)+- [forge.md](#sec-316)+- [forged.md](#sec-317)+- [fork-trade.md](#sec-318)+- [free-crypto-apis.md](#sec-319)+- [free-llm-providers.md](#sec-320)+- [galaxy.md](#sec-322)+- [generation-watch.md](#sec-323)+- [genesis.md](#sec-324)+- [genome.md](#sec-325)+- [ghost-copy.md](#sec-326)+- [github-growth.md](#sec-327)+- [github-memory-seeding.md](#sec-328)+- [glance.md](#sec-329)+- [glasses.md](#sec-330)+- [globe.md](#sec-333)+- [google-adk.md](#sec-334)+- [google-cloud-community-post.md](#sec-335)+- [google-x-accounts.md](#sec-336)+- [grok-bot.md](#sec-337)+- [grok.md](#sec-338)+- [growth-programs.md](#sec-339)+- [guardian.md](#sec-340)+- [guards.md](#sec-341)+- [herald.md](#sec-342)+- [hold-to-access.md](#sec-343)+- [home-assistant-community-post.md](#sec-344)+- [home-households.md](#sec-345)+- [home-plans.md](#sec-346)+- [home-privacy.md](#sec-347)+- [home-relay-threat-model.md](#sec-348)+- [home-relay.md](#sec-349)+- [home-satellite.md](#sec-350)+- [home-scene.md](#sec-351)+- [home-security.md](#sec-352)+- [home-voice.md](#sec-353)+- [how-forge-works.md](#sec-354)+- [how-it-works.md](#sec-355)+- [huggingface-3d-ai-agent-platform.md](#sec-356)+- [huggingface-agent-feedback-loop.md](#sec-357)+- [huggingface.md](#sec-358)+- [i18n.md](#sec-359)+- [ibm-community-any-skeleton-animation-post.md](#sec-360)+- [ibm-community-any-skeleton-animation-thread.md](#sec-361)+- [ibm-community-article.md](#sec-362)+- [ibm-community-blog-meetup-jessica.md](#sec-363)+- [ibm-community-defi-3d-sperax-post.md](#sec-364)+- [ibm-community-defi-3d-sperax-publishing-kit.md](#sec-365)+- [ibm-community-defi-3d-sperax.md](#sec-366)+- [ibm-community-doc-freshness-post.md](#sec-367)+- [ibm-community-doc-freshness-thread.md](#sec-368)+- [ibm-community-governed-agents-post.md](#sec-369)+- [ibm-community-governed-agents-thread.md](#sec-370)+- [ibm-community-live-reaction-jessica.md](#sec-371)+- [ibm-community-long-running-mcp-tools-post.md](#sec-372)+- [ibm-community-long-running-mcp-tools-thread.md](#sec-373)+- [ibm-community-recap-jessica.md](#sec-374)+- [ibm-community-recap-nichxbt.md](#sec-375)+- [ibm-community-thread.md](#sec-376)+- [ibm-community.md](#sec-377)+- [ibm-event-offer-map.md](#sec-378)+- [ibm-next-event.md](#sec-379)+- [ibm-visibility-map.md](#sec-380)+- [ibm-x402-mcp.md](#sec-381)+- [ibm.md](#sec-382)+- [image-to-3d.md](#sec-383)+- [in-game-economy.md](#sec-384)+- [inference-billing.md](#sec-385)+- [inference-node-operator.md](#sec-386)+- [integrations.md](#sec-387)+- [introduction.md](#sec-388)+- [ios-app.md](#sec-389)+- [irl.md](#sec-390)+- [issue-resolution-2026-09-15.md](#sec-393)+- [js-api.md](#sec-394)+- [knock.md](#sec-395)+- [kol-tracker.md](#sec-396)+- [labor-market.md](#sec-397)+- [launch-intents.md](#sec-398)+- [launch-lanes.md](#sec-399)+- [launch-usecases.md](#sec-400)+- [launchpad.md](#sec-401)+- [layers.md](#sec-402)+- [likeness-eval.md](#sec-403)+- [lipsync.md](#sec-404)+- [liquid-glass.md](#sec-405)+- [listings-registry.md](#sec-406)+- [listings.md](#sec-407)+- [live-docs.md](#sec-408)+- [live-steps.md](#sec-409)+- [make-your-agent.md](#sec-410)+- [market-data-api.md](#sec-411)+- [marketplace.md](#sec-412)+- [materialize.md](#sec-413)+- [mcp-3d-studio.md](#sec-414)+- [mcp-agent.md](#sec-415)+- [mcp-safety.md](#sec-416)+- [mcp-solana-memo-media.md](#sec-417)+- [mcp-studio.md](#sec-418)+- [mcp-tools.md](#sec-419)+- [mcp-x402-bazaar.md](#sec-420)+- [mcp.md](#sec-421)+- [media-api.md](#sec-422)+- [memetic-launcher.md](#sec-423)+- [memory.md](#sec-424)+- [meta-allocator.md](#sec-425)+- [mint-mark.md](#sec-426)+- [minted.md](#sec-427)+- [mocap-studio.md](#sec-434)+- [model-diff.md](#sec-435)+- [modly.md](#sec-436)+- [money-feed.md](#sec-437)+- [money-flow-map.md](#sec-438)+- [money-map.md](#sec-439)+- [monitor.md](#sec-440)+- [motion-swap.md](#sec-441)+- [multi-agent.md](#sec-442)+- [native-launchpad.md](#sec-443)+- [native-widgets.md](#sec-444)+- [news-rights.md](#sec-445)+- [notifications.md](#sec-446)+- [nvidia-apps-catalog-listing.md](#sec-447)+- [nvidia-apps-catalog-request.md](#sec-448)+- [nvidia-forum-browser-digital-human.md](#sec-449)+- [nvidia-forum-gpu-fleet-post.md](#sec-450)+- [nvidia-forum-model-retirement-post.md](#sec-451)+- [nvidia-gtc-2027-poster.md](#sec-452)+- [nvidia-inception.md](#sec-453)+- [nvidia-models.md](#sec-454)+- [nvidia-nemotron-ask-the-experts-questions.md](#sec-455)+- [nvidia-nemotron-spotlight.md](#sec-456)+- [nvidia-ngc-listing.md](#sec-457)+- [nvidia-visibility-map.md](#sec-458)+- [object-library.md](#sec-459)+- [okx-marketplace.md](#sec-460)+- [onboarding-tier.md](#sec-461)+- [onchain-agents.md](#sec-462)+- [open-source-credits.md](#sec-463)+- [open-source-ecosystem.md](#sec-464)+- [open-source-footprint.md](#sec-465)+- [open-source-friday-plan.md](#sec-466)+- [openai-community-3d-studio-post.md](#sec-467)+- [openai-community-physical-world-post.md](#sec-468)+- [openai-listing-channels.md](#sec-469)+- [oracle-model.md](#sec-470)+- [oracle-trading-mcp-plan.md](#sec-471)+- [oracle.md](#sec-472)+- [oss-adoption-2026-09.md](#sec-473)+- [overlay-audit.md](#sec-474)+- [package-extraction.md](#sec-475)+- [page-performance.md](#sec-476)+- [paired-coins.md](#sec-477)+- [papertrade.md](#sec-478)+- [partner-benefits.md](#sec-479)+- [partners.md](#sec-480)+- [pay-skills-listing.md](#sec-494)+- [payment-sessions.md](#sec-495)+- [permissions.md](#sec-496)+- [perps.md](#sec-497)+- [persona-hub.md](#sec-498)+- [pill-mascot.md](#sec-499)+- [plan-checkout.md](#sec-500)+- [play-boot-performance.md](#sec-501)+- [play-forge-in-world.md](#sec-502)+- [play-hardening.md](#sec-503)+- [play-live-events.md](#sec-504)+- [play-vehicles.md](#sec-505)+- [pocket.md](#sec-506)+- [pons-launch.md](#sec-507)+- [popular-3d-github-repos.md](#sec-508)+- [portal.md](#sec-509)+- [portfolio.md](#sec-510)+- [premium.md](#sec-511)+- [press-kit.md](#sec-512)+- [procedural-animation.md](#sec-513)+- [product-demo.md](#sec-514)+- [prompts.md](#sec-515)+- [provenance.md](#sec-563)+- [publishing-program-2026-09.md](#sec-564)+- [pump-claims-channel.md](#sec-565)+- [pump-fun-mcp-edge.md](#sec-566)+- [pump-launch-repos.md](#sec-567)+- [pump-launcher.md](#sec-568)+- [pump-platform-fee.md](#sec-569)+- [quick-start.md](#sec-600)+- [radar.md](#sec-601)+- [reasoning-ledger.md](#sec-602)+- [recurring-payments.md](#sec-603)+- [remix.md](#sec-604)+- [reputation-staking-market.md](#sec-605)+- [reputation.md](#sec-606)+- [resilience.md](#sec-622)+- [restyle.md](#sec-623)+- [rig-doctor.md](#sec-624)+- [risk-acknowledgment.md](#sec-625)+- [rivalries.md](#sec-626)+- [robinhood-chain-markets.md](#sec-627)+- [robinhood-portfolios.md](#sec-628)+- [run-receipts-x-reply-and-thread.md](#sec-629)+- [run-receipts.md](#sec-630)+- [sas-attestations.md](#sec-631)+- [scene-studio.md](#sec-632)+- [sdk.md](#sec-633)+- [security.md](#sec-634)+- [seed-quality.md](#sec-635)+- [seeker-app.md](#sec-636)+- [seeker-publishing.md](#sec-637)+- [seeker-submission-day.md](#sec-638)+- [seeker-video.md](#sec-639)+- [selfie-to-avatar.md](#sec-640)+- [sentiment-scout.md](#sec-641)+- [seo.md](#sec-642)+- [share-and-embed.md](#sec-643)+- [shared-utilities.md](#sec-644)+- [shipfeed.md](#sec-645)+- [shopify-app.md](#sec-646)+- [short-form-venue-kit-2026-09.md](#sec-647)+- [showcase.md](#sec-648)+- [sign-language.md](#sec-649)+- [signals.md](#sec-650)+- [sim-readiness.md](#sec-651)+- [site-performance.md](#sec-652)+- [sketchfab.md](#sec-653)+- [skill-bundles.md](#sec-654)+- [skill-import.md](#sec-655)+- [skill-royalties.md](#sec-656)+- [skills.md](#sec-657)+- [smart-contracts.md](#sec-658)+- [smart-home.md](#sec-659)+- [smart-money.md](#sec-660)+- [sniper-autonomy.md](#sec-661)+- [social-layer.md](#sec-662)+- [solana-pumpfun.md](#sec-663)+- [solana-reputation.md](#sec-664)+- [solana.md](#sec-665)+- [sonar.md](#sec-666)+- [spatial-mcp.md](#sec-667)+- [splat.md](#sec-669)+- [spotlight.md](#sec-670)+- [stage.md](#sec-671)+- [standalone-repo-playbook.md](#sec-672)+- [standalone-repos.md](#sec-673)+- [start-here.md](#sec-674)+- [strategy-objects.md](#sec-675)+- [swarms.md](#sec-677)+- [syndicates.md](#sec-678)+- [syndication.md](#sec-679)+- [talking-avatar-video.md](#sec-680)+- [team-chat.md](#sec-681)+- [teams.md](#sec-682)+- [terminal.md](#sec-683)+- [the-first-19-weeks.md](#sec-684)+- [three-microbuy.md](#sec-685)+- [three-thesis.md](#sec-686)+- [threejs-forum-post.md](#sec-687)+- [timeline.md](#sec-688)+- [token-gated-3d-embeds.md](#sec-689)+- [tokens-xyz.md](#sec-690)+- [trade-receipts.md](#sec-691)+- [trade-rooms.md](#sec-692)+- [trader-card-embed.md](#sec-693)+- [trader-card.md](#sec-694)+- [trader-duels.md](#sec-695)+- [trader-passport.md](#sec-696)+- [trader-wrapped.md](#sec-697)+- [trading-arenas.md](#sec-698)+- [trading-copilot.md](#sec-699)+- [trading-experiment.md](#sec-700)+- [trading-hub.md](#sec-701)+- [trading-quests.md](#sec-702)+- [trading-surfaces.md](#sec-703)+- [trading-tools.md](#sec-704)+- [trenches.md](#sec-705)+- [triage.md](#sec-706)+- [troubleshooting.md](#sec-707)+- [trust-primitives.md](#sec-708)+- [tty-avatar.md](#sec-709)+- [tty.md](#sec-710)+- [ui-juice.md](#sec-782)+- [ui-lint.md](#sec-783)+- [uniswap-v4-hooks.md](#sec-784)+- [user-wallet.md](#sec-786)+- [validation.md](#sec-799)+- [vanity.md](#sec-800)+- [vaults.md](#sec-801)+- [vendored-design-libraries.md](#sec-802)+- [viability.md](#sec-803)+- [video-to-motion.md](#sec-804)+- [viewer.md](#sec-805)+- [voice-framework-integrations.md](#sec-806)+- [voice-lab.md](#sec-807)+- [vroid-hub-import.md](#sec-808)+- [vscode.md](#sec-809)+- [walk-leaderboard.md](#sec-810)+- [web-component.md](#sec-811)+- [widget-api.md](#sec-812)+- [widget-studio.md](#sec-813)+- [widgets.md](#sec-814)+- [witness.md](#sec-815)+- [wordpress-embed.md](#sec-816)+- [workbench.md](#sec-817)+- [world-lines.md](#sec-818)+- [x-account-appeal.md](#sec-819)+- [x-accounts.md](#sec-820)+- [x-archive.md](#sec-821)+- [x-article-author-brief.md](#sec-824)+- [x-content-pipeline.md](#sec-825)+- [x-memory-seeding.md](#sec-826)+- [x-mention-avatar.md](#sec-827)+- [x-mention-bot.md](#sec-828)+- [x-mention-image3d.md](#sec-829)+- [x-partner-series.md](#sec-830)+- [x-reply-playbook.md](#sec-863)+- [x-story-author-brief.md](#sec-864)+- [x-story-authoring.md](#sec-865)+- [x402-buyer.md](#sec-866)+- [x402-dev-tools.md](#sec-867)+- [x402-distribution.md](#sec-868)+- [x402-endpoints.md](#sec-869)+- [x402-fresh-workers.md](#sec-870)+- [x402-preflight.md](#sec-871)+- [x402-ring-economy.md](#sec-872)+- [x402-settlement-pending.md](#sec-873)+- [x402-solana-july-roundup-response.md](#sec-874)+- [x402-studio.md](#sec-875)+- [x402-vscode.md](#sec-876)+- [x402.md](#sec-877)### agent-abilities@@ -601,358 +614,360 @@- [announcements/knock.md](#sec-117)- [announcements/materialize.md](#sec-118)- [announcements/open-source-friday.md](#sec-119)-- [announcements/product-demo.md](#sec-120)-- [announcements/text-to-3d.md](#sec-121)-- [announcements/three-token-mcp.md](#sec-122)-- [announcements/walk.md](#sec-123)+- [announcements/openai-partner-benefits.md](#sec-120)+- [announcements/product-demo.md](#sec-121)+- [announcements/text-to-3d.md](#sec-122)+- [announcements/three-token-mcp.md](#sec-123)+- [announcements/walk.md](#sec-124)### api-- [api/forge-x402.md](#sec-125)+- [api/forge-x402.md](#sec-126)### audit-- [audit/console-sweep-2026-09-04.md](#sec-134)-- [audit/console-sweep-2026-09-07.md](#sec-135)-- [audit/console-sweep-2026-09-09.md](#sec-136)-- [audit/python-deps-2026-09-07.md](#sec-137)+- [audit/console-sweep-2026-09-04.md](#sec-135)+- [audit/console-sweep-2026-09-07.md](#sec-136)+- [audit/console-sweep-2026-09-09.md](#sec-137)+- [audit/python-deps-2026-09-07.md](#sec-138)### content-- [content/use-cases/README.md](#sec-213)-- [content/use-cases/ai-agent-developer.md](#sec-214)-- [content/use-cases/brand-marketer.md](#sec-215)-- [content/use-cases/crypto-community.md](#sec-216)-- [content/use-cases/game-studio.md](#sec-217)-- [content/use-cases/indie-creator.md](#sec-218)+- [content/use-cases/README.md](#sec-214)+- [content/use-cases/ai-agent-developer.md](#sec-215)+- [content/use-cases/brand-marketer.md](#sec-216)+- [content/use-cases/crypto-community.md](#sec-217)+- [content/use-cases/game-studio.md](#sec-218)+- [content/use-cases/indie-creator.md](#sec-219)### cookbook-- [cookbook/asset-quality-gate.md](#sec-220)-- [cookbook/mcp-3d-tool.md](#sec-221)-- [cookbook/parallel-asset-pack.md](#sec-222)-- [cookbook/text-to-3d-cli.md](#sec-223)+- [cookbook/asset-quality-gate.md](#sec-221)+- [cookbook/mcp-3d-tool.md](#sec-222)+- [cookbook/parallel-asset-pack.md](#sec-223)+- [cookbook/text-to-3d-cli.md](#sec-224)### erc8004-- [erc8004/validation-attestation.md](#sec-264)+- [erc8004/validation-attestation.md](#sec-267)### event-readiness-- [event-readiness/01-play-first-impression.md](#sec-267)-- [event-readiness/02-play-mobile.md](#sec-268)-- [event-readiness/03-play-performance.md](#sec-269)-- [event-readiness/04-play-multiplayer-net.md](#sec-270)-- [event-readiness/05-play-economy-loops.md](#sec-271)-- [event-readiness/06-play-auth-errors.md](#sec-272)-- [event-readiness/07-platform-smoke-sweep.md](#sec-273)-- [event-readiness/08-api-production-health.md](#sec-274)-- [event-readiness/09-accessibility-i18n.md](#sec-275)-- [event-readiness/10-event-day-runbook.md](#sec-276)-- [event-readiness/11-event-live-ops.md](#sec-277)-- [event-readiness/12-photo-mode-share.md](#sec-278)-- [event-readiness/13-event-quests-leaderboard.md](#sec-279)-- [event-readiness/14-welcome-concierge.md](#sec-280)-- [event-readiness/15-live-hype-feed.md](#sec-281)-- [event-readiness/16-invite-flow.md](#sec-282)-- [event-readiness/17-plaza-live-show.md](#sec-283)-- [event-readiness/18-coin-wars-portal.md](#sec-284)-- [event-readiness/19-forge-props-live.md](#sec-285)-- [event-readiness/20-world-chat-scrollback.md](#sec-286)-- [event-readiness/21-party-system.md](#sec-287)-- [event-readiness/22-venue-projector-mode.md](#sec-288)-- [event-readiness/23-signature-wall.md](#sec-289)-- [event-readiness/24-dance-off.md](#sec-290)-- [event-readiness/LIVE-OPS.md](#sec-291)-- [event-readiness/README.md](#sec-292)+- [event-readiness/01-play-first-impression.md](#sec-270)+- [event-readiness/02-play-mobile.md](#sec-271)+- [event-readiness/03-play-performance.md](#sec-272)+- [event-readiness/04-play-multiplayer-net.md](#sec-273)+- [event-readiness/05-play-economy-loops.md](#sec-274)+- [event-readiness/06-play-auth-errors.md](#sec-275)+- [event-readiness/07-platform-smoke-sweep.md](#sec-276)+- [event-readiness/08-api-production-health.md](#sec-277)+- [event-readiness/09-accessibility-i18n.md](#sec-278)+- [event-readiness/10-event-day-runbook.md](#sec-279)+- [event-readiness/11-event-live-ops.md](#sec-280)+- [event-readiness/12-photo-mode-share.md](#sec-281)+- [event-readiness/13-event-quests-leaderboard.md](#sec-282)+- [event-readiness/14-welcome-concierge.md](#sec-283)+- [event-readiness/15-live-hype-feed.md](#sec-284)+- [event-readiness/16-invite-flow.md](#sec-285)+- [event-readiness/17-plaza-live-show.md](#sec-286)+- [event-readiness/18-coin-wars-portal.md](#sec-287)+- [event-readiness/19-forge-props-live.md](#sec-288)+- [event-readiness/20-world-chat-scrollback.md](#sec-289)+- [event-readiness/21-party-system.md](#sec-290)+- [event-readiness/22-venue-projector-mode.md](#sec-291)+- [event-readiness/23-signature-wall.md](#sec-292)+- [event-readiness/24-dance-off.md](#sec-293)+- [event-readiness/LIVE-OPS.md](#sec-294)+- [event-readiness/README.md](#sec-295)### fundraising-- [fundraising/nvidia-inception-capital-connect.md](#sec-318)+- [fundraising/nvidia-inception-capital-connect.md](#sec-321)### glasses-- [glasses/meta-ray-ban-display.md](#sec-328)-- [glasses/research.md](#sec-329)+- [glasses/meta-ray-ban-display.md](#sec-331)+- [glasses/research.md](#sec-332)### irl-- [irl/THREAT-MODEL.md](#sec-387)-- [irl/street-demo.md](#sec-388)+- [irl/THREAT-MODEL.md](#sec-391)+- [irl/street-demo.md](#sec-392)### mobile-launch-- [mobile-launch/README.md](#sec-424)-- [mobile-launch/aws-builder-center-article.md](#sec-425)-- [mobile-launch/coinmarketcap-article.md](#sec-426)-- [mobile-launch/ibm-community-article.md](#sec-427)-- [mobile-launch/nvidia-forum-article.md](#sec-428)-- [mobile-launch/x-article.md](#sec-429)+- [mobile-launch/README.md](#sec-428)+- [mobile-launch/aws-builder-center-article.md](#sec-429)+- [mobile-launch/coinmarketcap-article.md](#sec-430)+- [mobile-launch/ibm-community-article.md](#sec-431)+- [mobile-launch/nvidia-forum-article.md](#sec-432)+- [mobile-launch/x-article.md](#sec-433)### partners-- [partners/dextools-collab-kit.md](#sec-475)-- [partners/dextools-proposal.md](#sec-476)-- [partners/ibm-partner-plus.md](#sec-477)-- [partners/openai-ibm-nvidia-growth-plan.md](#sec-478)-- [partners/opportunities.md](#sec-479)-- [partners/outreach-plan.md](#sec-480)-- [partners/owner-day-2026-10-09.md](#sec-481)-- [partners/proof-brief-2026-10.md](#sec-482)-- [partners/prospects-solana.md](#sec-483)-- [partners/prospects.md](#sec-484)-- [partners/sperax-proposal.md](#sec-485)-- [partners/tripo.md](#sec-486)+- [partners/dextools-collab-kit.md](#sec-481)+- [partners/dextools-proposal.md](#sec-482)+- [partners/ibm-partner-plus.md](#sec-483)+- [partners/openai-ibm-nvidia-growth-plan.md](#sec-484)+- [partners/openai-partner-benefits-2026.md](#sec-485)+- [partners/opportunities.md](#sec-486)+- [partners/outreach-plan.md](#sec-487)+- [partners/owner-day-2026-10-09.md](#sec-488)+- [partners/proof-brief-2026-10.md](#sec-489)+- [partners/prospects-solana.md](#sec-490)+- [partners/prospects.md](#sec-491)+- [partners/sperax-proposal.md](#sec-492)+- [partners/tripo.md](#sec-493)### prompts-- [prompts/01-cli-setup-login.md](#sec-509)-- [prompts/03-mcp-tool-policy-skill.md](#sec-510)-- [prompts/04-community-skills-registry.md](#sec-511)-- [prompts/05-agents-rest-parity.md](#sec-512)-- [prompts/06-agents-sdk.md](#sec-513)-- [prompts/07-perps.md](#sec-514)-- [prompts/08-lending.md](#sec-515)-- [prompts/09-prediction-markets.md](#sec-516)-- [prompts/10-agent-marketplace-bids.md](#sec-517)-- [prompts/11-agent-mail.md](#sec-518)-- [prompts/12-agent-cards.md](#sec-519)-- [prompts/13-chat-gateways.md](#sec-520)-- [prompts/14-desktop-app-release.md](#sec-521)-- [prompts/15-gasless-launch.md](#sec-522)-- [prompts/16-self-funded-inference.md](#sec-523)-- [prompts/17-unified-mcp-endpoint.md](#sec-524)-- [prompts/18-open-model-roster.md](#sec-525)-- [prompts/19-self-custody-and-signers.md](#sec-526)-- [prompts/20-local-agent-runtime-tui.md](#sec-527)-- [prompts/21-agent-memory-and-self-improvement.md](#sec-528)-- [prompts/22-external-mcp-integrations-for-agents.md](#sec-529)-- [prompts/23-distribution-into-agent-frameworks.md](#sec-530)-- [prompts/24-more-gateways-and-voice.md](#sec-531)-- [prompts/25-sandboxed-code-execution.md](#sec-532)-- [prompts/26-tool-gateway-bundle.md](#sec-533)-- [prompts/27-bounties-and-hackathons.md](#sec-534)-- [prompts/28-public-economics-dashboard.md](#sec-535)-- [prompts/29-free-tier-and-hosting-plan.md](#sec-536)-- [prompts/30-trading-tool-parity.md](#sec-537)-- [prompts/31-human-task-fulfillment.md](#sec-538)-- [prompts/32-evm-secondary-leg.md](#sec-539)-- [prompts/33-account-social-and-sso.md](#sec-540)-- [prompts/34-localization.md](#sec-541)-- [prompts/35-always-on-strategy-loop.md](#sec-542)-- [prompts/36-agent-evals-and-replay.md](#sec-543)-- [prompts/README.md](#sec-544)-- [prompts/event-markets/01-core-markets-and-picks.md](#sec-545)-- [prompts/event-markets/02-market-pages-and-share-cards.md](#sec-546)-- [prompts/event-markets/03-auto-resolution.md](#sec-547)-- [prompts/event-markets/04-auto-open-for-every-event.md](#sec-548)-- [prompts/event-markets/05-announcement-automation.md](#sec-549)-- [prompts/event-markets/06-entrant-amplification-kit.md](#sec-550)-- [prompts/event-markets/07-pick-leaderboard-and-rewards.md](#sec-551)-- [prompts/event-markets/08-live-odds-feed.md](#sec-552)-- [prompts/event-markets/09-agents-as-forecasters.md](#sec-553)-- [prompts/event-markets/10-staked-markets-solana.md](#sec-554)-- [prompts/event-markets/README.md](#sec-555)+- [prompts/01-cli-setup-login.md](#sec-516)+- [prompts/03-mcp-tool-policy-skill.md](#sec-517)+- [prompts/04-community-skills-registry.md](#sec-518)+- [prompts/05-agents-rest-parity.md](#sec-519)+- [prompts/06-agents-sdk.md](#sec-520)+- [prompts/07-perps.md](#sec-521)+- [prompts/08-lending.md](#sec-522)+- [prompts/09-prediction-markets.md](#sec-523)+- [prompts/10-agent-marketplace-bids.md](#sec-524)+- [prompts/11-agent-mail.md](#sec-525)+- [prompts/12-agent-cards.md](#sec-526)+- [prompts/13-chat-gateways.md](#sec-527)+- [prompts/14-desktop-app-release.md](#sec-528)+- [prompts/15-gasless-launch.md](#sec-529)+- [prompts/16-self-funded-inference.md](#sec-530)+- [prompts/17-unified-mcp-endpoint.md](#sec-531)+- [prompts/18-open-model-roster.md](#sec-532)+- [prompts/19-self-custody-and-signers.md](#sec-533)+- [prompts/20-local-agent-runtime-tui.md](#sec-534)+- [prompts/21-agent-memory-and-self-improvement.md](#sec-535)+- [prompts/22-external-mcp-integrations-for-agents.md](#sec-536)+- [prompts/23-distribution-into-agent-frameworks.md](#sec-537)+- [prompts/24-more-gateways-and-voice.md](#sec-538)+- [prompts/25-sandboxed-code-execution.md](#sec-539)+- [prompts/26-tool-gateway-bundle.md](#sec-540)+- [prompts/27-bounties-and-hackathons.md](#sec-541)+- [prompts/28-public-economics-dashboard.md](#sec-542)+- [prompts/29-free-tier-and-hosting-plan.md](#sec-543)+- [prompts/30-trading-tool-parity.md](#sec-544)+- [prompts/31-human-task-fulfillment.md](#sec-545)+- [prompts/32-evm-secondary-leg.md](#sec-546)+- [prompts/33-account-social-and-sso.md](#sec-547)+- [prompts/34-localization.md](#sec-548)+- [prompts/35-always-on-strategy-loop.md](#sec-549)+- [prompts/36-agent-evals-and-replay.md](#sec-550)+- [prompts/README.md](#sec-551)+- [prompts/event-markets/01-core-markets-and-picks.md](#sec-552)+- [prompts/event-markets/02-market-pages-and-share-cards.md](#sec-553)+- [prompts/event-markets/03-auto-resolution.md](#sec-554)+- [prompts/event-markets/04-auto-open-for-every-event.md](#sec-555)+- [prompts/event-markets/05-announcement-automation.md](#sec-556)+- [prompts/event-markets/06-entrant-amplification-kit.md](#sec-557)+- [prompts/event-markets/07-pick-leaderboard-and-rewards.md](#sec-558)+- [prompts/event-markets/08-live-odds-feed.md](#sec-559)+- [prompts/event-markets/09-agents-as-forecasters.md](#sec-560)+- [prompts/event-markets/10-staked-markets-solana.md](#sec-561)+- [prompts/event-markets/README.md](#sec-562)### pumpfun-program-- [pumpfun-program/README.md](#sec-563)-- [pumpfun-program/UPSTREAM-buy-sell-v2-announcement.md](#sec-564)-- [pumpfun-program/UPSTREAM-pumpswap-virtual-quote-reserves.md](#sec-565)-- [pumpfun-program/UPSTREAM-v3-trades-fee-sweeps-announcement.md](#sec-566)-- [pumpfun-program/docs/BREAKING_FEE_RECIPIENT.md](#sec-567)-- [pumpfun-program/docs/CPI_README.md](#sec-568)-- [pumpfun-program/docs/FAQ.md](#sec-569)-- [pumpfun-program/docs/FEE_PROGRAM_README.md](#sec-570)-- [pumpfun-program/docs/FEE_RECIPIENTS.md](#sec-571)-- [pumpfun-program/docs/HOLDER_REWARDS_README.md](#sec-572)-- [pumpfun-program/docs/NEGATIVE_VIRTUAL_QUOTE_RESERVES.md](#sec-573)-- [pumpfun-program/docs/PUMP_CASHBACK_README.md](#sec-574)-- [pumpfun-program/docs/PUMP_CREATOR_FEE_README.md](#sec-575)-- [pumpfun-program/docs/PUMP_PROGRAM_README.md](#sec-576)-- [pumpfun-program/docs/PUMP_SWAP_CREATOR_FEE_README.md](#sec-577)-- [pumpfun-program/docs/PUMP_SWAP_README.md](#sec-578)-- [pumpfun-program/docs/PUMP_SWAP_SDK_README.md](#sec-579)-- [pumpfun-program/docs/SYNTHETIC_MIGRATION.md](#sec-580)-- [pumpfun-program/docs/VIRTUAL_QUOTE_RESERVES_FEE_ADJUSTMENT.md](#sec-581)-- [pumpfun-program/docs/instructions/BUY.md](#sec-582)-- [pumpfun-program/docs/instructions/CLAIM_CASHBACK.md](#sec-583)-- [pumpfun-program/docs/instructions/COIN_CREATION.md](#sec-584)-- [pumpfun-program/docs/instructions/COLLECT_CREATOR_FEE.md](#sec-585)-- [pumpfun-program/docs/instructions/CREATE_WITH_PUMP_COIN_QUOTE.md](#sec-586)-- [pumpfun-program/docs/instructions/CREATOR_FEE_SHARING.md](#sec-587)-- [pumpfun-program/docs/instructions/MULTI_HOP_SWAP.md](#sec-588)-- [pumpfun-program/docs/instructions/PUMP_SWAP_TRADE_V2.md](#sec-589)-- [pumpfun-program/docs/instructions/SELL.md](#sec-590)-- [pumpfun-program/docs/instructions/SWEEP_FEES.md](#sec-591)-- [pumpfun-program/docs/instructions/TRADE_V3.md](#sec-592)+- [pumpfun-program/README.md](#sec-570)+- [pumpfun-program/UPSTREAM-buy-sell-v2-announcement.md](#sec-571)+- [pumpfun-program/UPSTREAM-pumpswap-virtual-quote-reserves.md](#sec-572)+- [pumpfun-program/UPSTREAM-v3-trades-fee-sweeps-announcement.md](#sec-573)+- [pumpfun-program/docs/BREAKING_FEE_RECIPIENT.md](#sec-574)+- [pumpfun-program/docs/CPI_README.md](#sec-575)+- [pumpfun-program/docs/FAQ.md](#sec-576)+- [pumpfun-program/docs/FEE_PROGRAM_README.md](#sec-577)+- [pumpfun-program/docs/FEE_RECIPIENTS.md](#sec-578)+- [pumpfun-program/docs/HOLDER_REWARDS_README.md](#sec-579)+- [pumpfun-program/docs/NEGATIVE_VIRTUAL_QUOTE_RESERVES.md](#sec-580)+- [pumpfun-program/docs/PUMP_CASHBACK_README.md](#sec-581)+- [pumpfun-program/docs/PUMP_CREATOR_FEE_README.md](#sec-582)+- [pumpfun-program/docs/PUMP_PROGRAM_README.md](#sec-583)+- [pumpfun-program/docs/PUMP_SWAP_CREATOR_FEE_README.md](#sec-584)+- [pumpfun-program/docs/PUMP_SWAP_README.md](#sec-585)+- [pumpfun-program/docs/PUMP_SWAP_SDK_README.md](#sec-586)+- [pumpfun-program/docs/SYNTHETIC_MIGRATION.md](#sec-587)+- [pumpfun-program/docs/VIRTUAL_QUOTE_RESERVES_FEE_ADJUSTMENT.md](#sec-588)+- [pumpfun-program/docs/instructions/BUY.md](#sec-589)+- [pumpfun-program/docs/instructions/CLAIM_CASHBACK.md](#sec-590)+- [pumpfun-program/docs/instructions/COIN_CREATION.md](#sec-591)+- [pumpfun-program/docs/instructions/COLLECT_CREATOR_FEE.md](#sec-592)+- [pumpfun-program/docs/instructions/CREATE_WITH_PUMP_COIN_QUOTE.md](#sec-593)+- [pumpfun-program/docs/instructions/CREATOR_FEE_SHARING.md](#sec-594)+- [pumpfun-program/docs/instructions/MULTI_HOP_SWAP.md](#sec-595)+- [pumpfun-program/docs/instructions/PUMP_SWAP_TRADE_V2.md](#sec-596)+- [pumpfun-program/docs/instructions/SELL.md](#sec-597)+- [pumpfun-program/docs/instructions/SWEEP_FEES.md](#sec-598)+- [pumpfun-program/docs/instructions/TRADE_V3.md](#sec-599)### research-- [research/3d-landscape-2026-10.md](#sec-600)-- [research/competitor-teardown-2026-09.md](#sec-601)-- [research/crypto-agent-oss-landscape-2026-10.md](#sec-602)-- [research/grok-ecosystem-2026-10.md](#sec-603)-- [research/launchpad-landscape-2026-09.md](#sec-604)-- [research/oss-landscape-2026-10-notes/3d-generation.md](#sec-605)-- [research/oss-landscape-2026-10-notes/agent-commerce.md](#sec-606)-- [research/oss-landscape-2026-10-notes/agent-frameworks.md](#sec-607)-- [research/oss-landscape-2026-10-notes/avatars-voice.md](#sec-608)-- [research/oss-landscape-2026-10-notes/chat-memory-evals.md](#sec-609)-- [research/oss-landscape-2026-10-notes/coding-mcp-skills.md](#sec-610)-- [research/oss-landscape-2026-10-notes/irl-home-robotics.md](#sec-611)-- [research/oss-landscape-2026-10-notes/worlds-engines.md](#sec-612)-- [research/oss-landscape-2026-10.md](#sec-613)-- [research/solana-robinhood-playbook-2026-10.md](#sec-614)+- [research/3d-landscape-2026-10.md](#sec-607)+- [research/competitor-teardown-2026-09.md](#sec-608)+- [research/crypto-agent-oss-landscape-2026-10.md](#sec-609)+- [research/grok-ecosystem-2026-10.md](#sec-610)+- [research/launchpad-landscape-2026-09.md](#sec-611)+- [research/oss-landscape-2026-10-notes/3d-generation.md](#sec-612)+- [research/oss-landscape-2026-10-notes/agent-commerce.md](#sec-613)+- [research/oss-landscape-2026-10-notes/agent-frameworks.md](#sec-614)+- [research/oss-landscape-2026-10-notes/avatars-voice.md](#sec-615)+- [research/oss-landscape-2026-10-notes/chat-memory-evals.md](#sec-616)+- [research/oss-landscape-2026-10-notes/coding-mcp-skills.md](#sec-617)+- [research/oss-landscape-2026-10-notes/irl-home-robotics.md](#sec-618)+- [research/oss-landscape-2026-10-notes/worlds-engines.md](#sec-619)+- [research/oss-landscape-2026-10.md](#sec-620)+- [research/solana-robinhood-playbook-2026-10.md](#sec-621)### specs-- [specs/agent-trading.md](#sec-660)+- [specs/agent-trading.md](#sec-668)### support-- [support/stranded-wallet-ownership-proof.md](#sec-668)+- [support/stranded-wallet-ownership-proof.md](#sec-676)### tutorials-- [tutorials/add-a-3d-assistant.md](#sec-703)-- [tutorials/agent-personality.md](#sec-704)-- [tutorials/agent-reputation.md](#sec-705)-- [tutorials/agent-spending-envelope.md](#sec-706)-- [tutorials/animate-your-agent.md](#sec-707)-- [tutorials/animate-your-avatar.md](#sec-708)-- [tutorials/arm-an-agent-sniper.md](#sec-709)-- [tutorials/build-a-3d-asset-pipeline.md](#sec-710)-- [tutorials/build-a-scene.md](#sec-711)-- [tutorials/build-a-site-concierge.md](#sec-712)-- [tutorials/character-library-to-embed.md](#sec-713)-- [tutorials/claim-threews-name.md](#sec-714)-- [tutorials/connect-ai-brain.md](#sec-715)-- [tutorials/connect-your-home.md](#sec-716)-- [tutorials/create-and-edit-memory.md](#sec-717)-- [tutorials/custom-skill.md](#sec-718)-- [tutorials/customize-appearance.md](#sec-719)-- [tutorials/deploy-to-vercel-custom-domain.md](#sec-720)-- [tutorials/earn-and-spend-in-play.md](#sec-721)-- [tutorials/embed-in-30-seconds.md](#sec-722)-- [tutorials/embed-on-website.md](#sec-723)-- [tutorials/emotion-from-data.md](#sec-724)-- [tutorials/explore-docs-world.md](#sec-725)-- [tutorials/find-a-better-exit-policy.md](#sec-726)-- [tutorials/first-agent.md](#sec-727)-- [tutorials/first-prompt-to-3d.md](#sec-728)-- [tutorials/generate-3d-api.md](#sec-729)-- [tutorials/getting-started.md](#sec-730)-- [tutorials/greeting-and-first-speech.md](#sec-731)-- [tutorials/grok-bot-recipes.md](#sec-732)-- [tutorials/image-to-3d.md](#sec-733)-- [tutorials/import-avatar-url.md](#sec-734)-- [tutorials/js-api-events.md](#sec-735)-- [tutorials/mcp-server-for-your-agent.md](#sec-736)-- [tutorials/mine-vanity-address.md](#sec-737)-- [tutorials/mint-pumpfun-token.md](#sec-738)-- [tutorials/monetize-mcp-server.md](#sec-739)-- [tutorials/multi-agent-coordination.md](#sec-740)-- [tutorials/nvidia-3d-free.md](#sec-741)-- [tutorials/nvidia-nim-self-host.md](#sec-742)-- [tutorials/paid-x402-endpoint.md](#sec-743)-- [tutorials/pay-for-x402-service.md](#sec-744)-- [tutorials/personal-ai-site.md](#sec-745)-- [tutorials/place-agent-irl.md](#sec-746)-- [tutorials/prompts-for-3d.md](#sec-747)-- [tutorials/read-the-trading-fleet.md](#sec-748)-- [tutorials/register-onchain.md](#sec-749)-- [tutorials/render-avatar-images.md](#sec-750)-- [tutorials/self-host-agent-backend.md](#sec-751)-- [tutorials/selfie-to-avatar.md](#sec-752)-- [tutorials/sell-a-skill-with-a-trial.md](#sec-753)-- [tutorials/share-your-agent.md](#sec-754)-- [tutorials/ship-an-avatar-manifest.md](#sec-755)-- [tutorials/shopify-shopping-assistant.md](#sec-756)-- [tutorials/shopify-store-guide-advanced.md](#sec-757)-- [tutorials/shopify-store-guide.md](#sec-758)-- [tutorials/sign-with-your-avatar.md](#sec-759)-- [tutorials/skill-with-database-auth.md](#sec-760)-- [tutorials/solana-agent-reputation.md](#sec-761)-- [tutorials/sperax-tour.md](#sec-762)-- [tutorials/swap-avatar-in-studio.md](#sec-763)-- [tutorials/text-to-3d.md](#sec-764)-- [tutorials/trigger-from-page-events.md](#sec-765)-- [tutorials/upload-custom-glb.md](#sec-766)-- [tutorials/view-in-ar.md](#sec-767)-- [tutorials/voice-and-lipsync.md](#sec-768)-- [tutorials/walk-companion.md](#sec-769)-- [tutorials/wallet-sign-in.md](#sec-770)-- [tutorials/web-component-end-to-end.md](#sec-771)-- [tutorials/write-a-guard.md](#sec-772)-- [tutorials/x402-server-sdk.md](#sec-773)+- [tutorials/add-a-3d-assistant.md](#sec-711)+- [tutorials/agent-personality.md](#sec-712)+- [tutorials/agent-reputation.md](#sec-713)+- [tutorials/agent-spending-envelope.md](#sec-714)+- [tutorials/animate-your-agent.md](#sec-715)+- [tutorials/animate-your-avatar.md](#sec-716)+- [tutorials/arm-an-agent-sniper.md](#sec-717)+- [tutorials/build-a-3d-asset-pipeline.md](#sec-718)+- [tutorials/build-a-scene.md](#sec-719)+- [tutorials/build-a-site-concierge.md](#sec-720)+- [tutorials/character-library-to-embed.md](#sec-721)+- [tutorials/claim-threews-name.md](#sec-722)+- [tutorials/connect-ai-brain.md](#sec-723)+- [tutorials/connect-your-home.md](#sec-724)+- [tutorials/create-and-edit-memory.md](#sec-725)+- [tutorials/custom-skill.md](#sec-726)+- [tutorials/customize-appearance.md](#sec-727)+- [tutorials/deploy-to-vercel-custom-domain.md](#sec-728)+- [tutorials/earn-and-spend-in-play.md](#sec-729)+- [tutorials/embed-in-30-seconds.md](#sec-730)+- [tutorials/embed-on-website.md](#sec-731)+- [tutorials/emotion-from-data.md](#sec-732)+- [tutorials/explore-docs-world.md](#sec-733)+- [tutorials/find-a-better-exit-policy.md](#sec-734)+- [tutorials/first-agent.md](#sec-735)+- [tutorials/first-prompt-to-3d.md](#sec-736)+- [tutorials/generate-3d-api.md](#sec-737)+- [tutorials/getting-started.md](#sec-738)+- [tutorials/greeting-and-first-speech.md](#sec-739)+- [tutorials/grok-bot-recipes.md](#sec-740)+- [tutorials/image-to-3d.md](#sec-741)+- [tutorials/import-avatar-url.md](#sec-742)+- [tutorials/js-api-events.md](#sec-743)+- [tutorials/mcp-server-for-your-agent.md](#sec-744)+- [tutorials/mine-vanity-address.md](#sec-745)+- [tutorials/mint-pumpfun-token.md](#sec-746)+- [tutorials/monetize-mcp-server.md](#sec-747)+- [tutorials/multi-agent-coordination.md](#sec-748)+- [tutorials/nvidia-3d-free.md](#sec-749)+- [tutorials/nvidia-nim-self-host.md](#sec-750)+- [tutorials/paid-x402-endpoint.md](#sec-751)+- [tutorials/pay-for-x402-service.md](#sec-752)+- [tutorials/personal-ai-site.md](#sec-753)+- [tutorials/place-agent-irl.md](#sec-754)+- [tutorials/prompts-for-3d.md](#sec-755)+- [tutorials/read-the-trading-fleet.md](#sec-756)+- [tutorials/register-onchain.md](#sec-757)+- [tutorials/render-avatar-images.md](#sec-758)+- [tutorials/self-host-agent-backend.md](#sec-759)+- [tutorials/selfie-to-avatar.md](#sec-760)+- [tutorials/sell-a-skill-with-a-trial.md](#sec-761)+- [tutorials/share-your-agent.md](#sec-762)+- [tutorials/ship-an-avatar-manifest.md](#sec-763)+- [tutorials/shopify-shopping-assistant.md](#sec-764)+- [tutorials/shopify-store-guide-advanced.md](#sec-765)+- [tutorials/shopify-store-guide.md](#sec-766)+- [tutorials/sign-with-your-avatar.md](#sec-767)+- [tutorials/skill-with-database-auth.md](#sec-768)+- [tutorials/solana-agent-reputation.md](#sec-769)+- [tutorials/sperax-tour.md](#sec-770)+- [tutorials/swap-avatar-in-studio.md](#sec-771)+- [tutorials/text-to-3d.md](#sec-772)+- [tutorials/trigger-from-page-events.md](#sec-773)+- [tutorials/upload-custom-glb.md](#sec-774)+- [tutorials/view-in-ar.md](#sec-775)+- [tutorials/voice-and-lipsync.md](#sec-776)+- [tutorials/walk-companion.md](#sec-777)+- [tutorials/wallet-sign-in.md](#sec-778)+- [tutorials/web-component-end-to-end.md](#sec-779)+- [tutorials/write-a-guard.md](#sec-780)+- [tutorials/x402-server-sdk.md](#sec-781)### upstream-- [upstream/home-assistant-js-websocket-resubscribe-rejection.md](#sec-776)+- [upstream/home-assistant-js-websocket-resubscribe-rejection.md](#sec-785)### ux-flows-- [ux-flows/01-onboarding-creation.md](#sec-778)-- [ux-flows/02-forge-text-to-3d.md](#sec-779)-- [ux-flows/03-3d-editing-viewer.md](#sec-780)-- [ux-flows/04-embed-widget-studio.md](#sec-781)-- [ux-flows/05-discovery-social.md](#sec-782)-- [ux-flows/06-marketplace-skills.md](#sec-783)-- [ux-flows/07-crypto-trading-analytics.md](#sec-784)-- [ux-flows/08-coin-launch-wallets.md](#sec-785)-- [ux-flows/09-x402-agent-commerce.md](#sec-786)-- [ux-flows/10-chat-brain-labs.md](#sec-787)-- [ux-flows/11-account-dashboard.md](#sec-788)-- [ux-flows/12-home-and-content.md](#sec-789)+- [ux-flows/01-onboarding-creation.md](#sec-787)+- [ux-flows/02-forge-text-to-3d.md](#sec-788)+- [ux-flows/03-3d-editing-viewer.md](#sec-789)+- [ux-flows/04-embed-widget-studio.md](#sec-790)+- [ux-flows/05-discovery-social.md](#sec-791)+- [ux-flows/06-marketplace-skills.md](#sec-792)+- [ux-flows/07-crypto-trading-analytics.md](#sec-793)+- [ux-flows/08-coin-launch-wallets.md](#sec-794)+- [ux-flows/09-x402-agent-commerce.md](#sec-795)+- [ux-flows/10-chat-brain-labs.md](#sec-796)+- [ux-flows/11-account-dashboard.md](#sec-797)+- [ux-flows/12-home-and-content.md](#sec-798)### x-archive-- [x-archive/trythreews-articles-readers.md](#sec-809)-- [x-archive/trythreews-engagement.md](#sec-810)+- [x-archive/trythreews-articles-readers.md](#sec-822)+- [x-archive/trythreews-engagement.md](#sec-823)### x-posts-- [x-posts/3d-ar-studio-launch.md](#sec-817)-- [x-posts/3d-ar-studio-video-script.md](#sec-818)-- [x-posts/README.md](#sec-819)-- [x-posts/android-app-launch.md](#sec-820)-- [x-posts/ar-quick-look-fix-x-post.md](#sec-821)-- [x-posts/claims-ledger-thread.md](#sec-822)-- [x-posts/event-x-posts.md](#sec-823)-- [x-posts/fomo-verified-x-post.md](#sec-824)-- [x-posts/github-100-stars.md](#sec-825)-- [x-posts/ibm-skillsbuild-x-post.md](#sec-826)-- [x-posts/immutable-embed-releases-thread.md](#sec-827)-- [x-posts/mcp-registry-fleet-x-post.md](#sec-828)-- [x-posts/metaplex-agent-deployer-video-script.md](#sec-829)-- [x-posts/metaplex-agent-deployer-x-post.md](#sec-830)-- [x-posts/metaplex-agent-mcp-launch.md](#sec-831)-- [x-posts/metaplex-agent-mcp-veo-script.md](#sec-832)-- [x-posts/metaplex-agent-mcp-x-post.md](#sec-833)-- [x-posts/news-archive-x-post.md](#sec-834)-- [x-posts/nvidia-forum-audio2face-x-post.md](#sec-835)-- [x-posts/onchain-agent-wallets-x-post.md](#sec-836)-- [x-posts/open-source-ecosystem.md](#sec-837)-- [x-posts/open-weight-3d-forge-thread.md](#sec-838)-- [x-posts/oracle-trading-mcp-x-post.md](#sec-839)-- [x-posts/osf-issue-reply.md](#sec-840)-- [x-posts/proof-of-life-x-post.md](#sec-841)-- [x-posts/pumpfun-article-x-post.md](#sec-842)-- [x-posts/sperax-staking-in-chat-x-post.md](#sec-843)-- [x-posts/the-first-19-weeks.md](#sec-844)-- [x-posts/threews-avatar-launch.md](#sec-845)-- [x-posts/threews-avatar-video-script.md](#sec-846)-- [x-posts/universal-retargeting-thread.md](#sec-847)-- [x-posts/x-meetup-posts.md](#sec-848)+- [x-posts/3d-ar-studio-launch.md](#sec-831)+- [x-posts/3d-ar-studio-video-script.md](#sec-832)+- [x-posts/README.md](#sec-833)+- [x-posts/android-app-launch.md](#sec-834)+- [x-posts/ar-quick-look-fix-x-post.md](#sec-835)+- [x-posts/claims-ledger-thread.md](#sec-836)+- [x-posts/event-x-posts.md](#sec-837)+- [x-posts/fomo-verified-x-post.md](#sec-838)+- [x-posts/github-100-stars.md](#sec-839)+- [x-posts/ibm-skillsbuild-x-post.md](#sec-840)+- [x-posts/immutable-embed-releases-thread.md](#sec-841)+- [x-posts/mcp-registry-fleet-x-post.md](#sec-842)+- [x-posts/metaplex-agent-deployer-video-script.md](#sec-843)+- [x-posts/metaplex-agent-deployer-x-post.md](#sec-844)+- [x-posts/metaplex-agent-mcp-launch.md](#sec-845)+- [x-posts/metaplex-agent-mcp-veo-script.md](#sec-846)+- [x-posts/metaplex-agent-mcp-x-post.md](#sec-847)+- [x-posts/news-archive-x-post.md](#sec-848)+- [x-posts/nvidia-forum-audio2face-x-post.md](#sec-849)+- [x-posts/onchain-agent-wallets-x-post.md](#sec-850)+- [x-posts/open-source-ecosystem.md](#sec-851)+- [x-posts/open-weight-3d-forge-thread.md](#sec-852)+- [x-posts/oracle-trading-mcp-x-post.md](#sec-853)+- [x-posts/osf-issue-reply.md](#sec-854)+- [x-posts/proof-of-life-x-post.md](#sec-855)+- [x-posts/pumpfun-article-x-post.md](#sec-856)+- [x-posts/sperax-staking-in-chat-x-post.md](#sec-857)+- [x-posts/the-first-19-weeks.md](#sec-858)+- [x-posts/threews-avatar-launch.md](#sec-859)+- [x-posts/threews-avatar-video-script.md](#sec-860)+- [x-posts/universal-retargeting-thread.md](#sec-861)+- [x-posts/x-meetup-posts.md](#sec-862)### zauth-- [zauth/database.md](#sec-863)-- [zauth/index.md](#sec-864)-- [zauth/provider-hub.md](#sec-865)-- [zauth/reposcan.md](#sec-866)-- [zauth/vector.md](#sec-867)+- [zauth/database.md](#sec-878)+- [zauth/index.md](#sec-879)+- [zauth/provider-hub.md](#sec-880)+- [zauth/reposcan.md](#sec-881)+- [zauth/vector.md](#sec-882)---@@ -1537,8 +1552,8 @@ This is the canonical reference for how three.ws moves a 3D character or motionIf you just want to add one animation or upload one avatar, the task guides are shorter:- [docs/animations.md](#sec-101) — the animation registry, runtime loading, and agent slots.-- [docs/avatar-creation.md](#sec-144) — the three ways to create an avatar (photo, builder, upload).-- [docs/tutorials/upload-custom-glb.md](#sec-766) — Mixamo → GLB, validation, and the common failure modes.+- [docs/avatar-creation.md](#sec-145) — the three ways to create an avatar (photo, builder, upload).+- [docs/tutorials/upload-custom-glb.md](#sec-774) — Mixamo → GLB, validation, and the common failure modes.This document is the *why and how* underneath all of those.@@ -1873,11 +1888,11 @@ text/image ──► mesh_forge ──► static GLB ──► rig_mesh ──three.ws runs a full 3D asset pipeline — the same lanes the platform uses to turna prompt into a rigged, game-ready character. Every working stage is sold as its-own [x402](#sec-862) resource: an AI agent pays a few cents in USDC, hands in a URL,+own [x402](#sec-877) resource: an AI agent pays a few cents in USDC, hands in a URL,and gets back a finished asset URL. No API key, no account, no signup.Nobody else in the x402 ecosystem offers this. The generation stage (text/image →-3D) is [`/api/x402/forge`](#sec-854); the stages below are what you do to+3D) is [`/api/x402/forge`](#sec-869); the stages below are what you do toa mesh *after* it exists.```@@ -1890,7 +1905,7 @@ a mesh *after* it exists.1. **One stage at a time** — `POST /api/x402/pipeline-<stage>`. One payment buysone finished asset, returned inline as a durable first-party URL. This is thereference below.-2. **The whole chain in one call** — [`POST /api/x402/pipeline`](#sec-854).+2. **The whole chain in one call** — [`POST /api/x402/pipeline`](#sec-869).Submit an ordered chain (`generate → rig → remesh → gameready → stylize`); the402 quote is the exact sum of the requested stages, and you poll the job freeat `GET /api/forge?job=<id>` while it advances. Use this when you want the full@@ -1953,7 +1968,7 @@ console.log(output_url);The wrapper answers the 402, signs the payment, and retries the same request, allbefore your `await` resolves. Paying from a three.ws agent wallet instead of araw key, or settling on Solana, is covered in-[x402 buyer client](#sec-851).+[x402 buyer client](#sec-866).## Stages@@ -2112,9 +2127,9 @@ returned as-is. Poll budget is tunable via `X402_PIPELINE_POLL_BUDGET_MS`## Related-- [x402 paid endpoints](#sec-854) — the full catalog + pricing model-- [x402 buyer client](#sec-851) — how to settle payments as an agent-- [Avatar pipeline](#sec-148) — the generation + rig lanes in depth+- [x402 paid endpoints](#sec-869) — the full catalog + pricing model+- [x402 buyer client](#sec-866) — how to settle payments as an agent+- [Avatar pipeline](#sec-149) — the generation + rig lanes in depth---@@ -2242,8 +2257,8 @@ Frames render **sequentially**. The renderer drives one shared headless browser;## Related- [Free 3D API](#sec-001): generate and inspect-- [MCP servers](#sec-417): every tool on `/api/mcp-studio`-- [OKX.AI marketplace](#sec-456): paid 3D for agents that buy it+- [MCP servers](#sec-421): every tool on `/api/mcp-studio`+- [OKX.AI marketplace](#sec-460): paid 3D for agents that buy it---@@ -2697,10 +2712,10 @@ Product and developer documentation for three.ws. Individual docs are served onStart points:-- [start-here.md](#sec-666): the front door for both creators and developers, with the reference shelf at the bottom.-- [introduction.md](#sec-384) and [quick-start.md](#sec-593): the developer track.+- [start-here.md](#sec-674): the front door for both creators and developers, with the reference shelf at the bottom.+- [introduction.md](#sec-388) and [quick-start.md](#sec-600): the developer track.- [ALL.md](ALL.md): generated single-file aggregate of the public docs (regenerate with `node scripts/combine-docs.mjs`; edit source files, never ALL.md).-- [api-reference.md](#sec-124): the REST API surface, with dedicated docs for the larger API families (crypto, 3D, market data, MCP).+- [api-reference.md](#sec-125): the REST API surface, with dedicated docs for the larger API families (crypto, 3D, market data, MCP).Subdirectories: [tutorials/](tutorials) (step-by-step guides served on-site), [specs/](specs) (proposed contracts), [api/](api), [erc8004/](erc8004), [agent-abilities/](agent-abilities), [ux-flows/](ux-flows) (the UX Flow Atlas), [content/](content) (use-case narratives), [partners/](partners).@@ -2732,7 +2747,7 @@ leaves behind, and how to stop an agent that has gone wrong.> [`scripts/a2a-spend-hardening-proof.mjs`](../scripts/a2a-spend-hardening-proof.mjs).Related: [the agent wallet control API](#sec-076) for the other-owner-only wallet surfaces, [financial controls](#sec-306) for+owner-only wallet surfaces, [financial controls](#sec-309) forthe platform-wide picture, and [agent economy volume](#sec-055)for what settled A2A payments add up to.@@ -2797,7 +2812,7 @@ PUT /api/agents/:id/solana/limits (CSRF-gated for cookie callers)| `per_tx_usd` | Ceiling on any single payment | `null` (uncapped) || `daily_usd` | Rolling 24h ceiling on total outflow | `null` (uncapped) || `per_counterparty_daily_usd` | Rolling 24h ceiling **per payee** | `null` (uncapped) |-| `withdraw_allowlist` | Read-only view of the active [destination whitelist](#sec-242). Edit it there: new addresses serve a cooldown and need step-up | `[]` |+| `withdraw_allowlist` | Read-only view of the active [destination whitelist](#sec-243). Edit it there: new addresses serve a cooldown and need step-up | `[]` || `frozen` | The kill switch. Halts every autonomous path | `false` || `require_capabilities` | Autonomous spends must present a covering scoped capability | `false` |@@ -2986,11 +3001,11 @@ POST /api/auth/external-wallet/verify {chain, message, signature, password?}The challenge returns a message with a one-time nonce and expiry. Sign it with the wallet and verify. A nonce burns on use, so a replay fails.- `role: owner` links the wallet as a sign-in wallet.-- `role: payout` sets the agent's payout wallet. A first wallet is live at once. **Replacing a live payout wallet needs step-up** (password or fresh reauth, else `403 step_up_required` with the current address) and takes effect after a **24 hour cooldown**, during which the previous wallet keeps receiving. Where an approval is required, the request appears in the [approvals inbox](#sec-126) as a payout wallet change and is never auto-approved.+- `role: payout` sets the agent's payout wallet. A first wallet is live at once. **Replacing a live payout wallet needs step-up** (password or fresh reauth, else `403 step_up_required` with the current address) and takes effect after a **24 hour cooldown**, during which the previous wallet keeps receiving. Where an approval is required, the request appears in the [approvals inbox](#sec-127) as a payout wallet change and is never auto-approved.The same policy guards `PUT /api/monetization/wallet` and `POST /api/billing/payout-wallets`.-MCP tools: `set_external_wallet` (challenge and verify steps) and `get_linked_accounts` on the main server. See [mcp.md](#sec-417).+MCP tools: `set_external_wallet` (challenge and verify steps) and `get_linked_accounts` on the main server. See [mcp.md](#sec-421).## Linked accounts@@ -3000,7 +3015,7 @@ MCP tools: `set_external_wallet` (challenge and verify steps) and `get_linked_acEvery link, unlink, reject, revoke, reauth and payout-wallet change is recorded (`link_*`, `unlink_*`, `reauth:telegram`, `link_code_*`), visible on the Account page activity and in `/api/audit-log`.-Related: [authentication.md](#sec-138), [chat-gateways.md](#sec-184), [approvals.md](#sec-126).+Related: [authentication.md](#sec-139), [chat-gateways.md](#sec-185), [approvals.md](#sec-127).---@@ -3179,7 +3194,7 @@ or task to the AgenC program. The write paths that do exist live elsewhere:Treat this page's REST surface as **discovery + identity correlation**. For theother writable on-chain identity, minting agents as Metaplex Core NFTs, see-[Deploy agents on-chain (bulk)](#sec-458).+[Deploy agents on-chain (bulk)](#sec-462).## Relationship to Agora@@ -3192,8 +3207,8 @@ AgenC endpoints here are the read/identity side.## Related- [Agora](#sec-080) — the economy and write lifecycle on top of AgenC.-- [Agent reputation](#sec-060), [ERC-8004](#sec-263).-- [Deploy agents on-chain (bulk)](#sec-458).+- [Agent reputation](#sec-060), [ERC-8004](#sec-266).+- [Deploy agents on-chain (bulk)](#sec-462).---@@ -14205,7 +14220,7 @@ the pay link; set `due_in_hours` to `0.1` and let it pass, and it reads## Related-- [Agent wallet MCP server](#sec-411): `pay_quote`, `pay_and_call` and the rest of the wallet tools.+- [Agent wallet MCP server](#sec-415): `pay_quote`, `pay_and_call` and the rest of the wallet tools.- [Account linking](#sec-009): linking the Solana wallet used for step-up signatures.- [STRUCTURE.md](../STRUCTURE.md): where every surface lives.@@ -14257,7 +14272,7 @@ signature on file".A hire is also refused outright, before a row is inserted or any spend isreserved, when the hiring account has not signed the real-funds agreements: theendpoint answers `403 risk_ack_required` and nothing reaches the ledger (see-[the real-funds agreements](#sec-618)). The same holds for a bearer+[the real-funds agreements](#sec-625)). The same holds for a bearertoken that lacks the `wallet:write` scope, which gets `403 insufficient_scope`(see [the agent wallet API](#sec-076)).@@ -14325,7 +14340,7 @@ The alert strip is built from a static translated sentence plus a dynamic detailclause in a separate element (`#an-error-detail`). That split is load-bearing:`src/i18n.js` rewrites annotated elements after first paint. Its runtime nowinfers when a page script has rewritten an annotated element and leaves it alone-(`primeOwnership`, see [i18n.md](#sec-355)), but an element the page wrote also+(`primeOwnership`, see [i18n.md](#sec-359)), but an element the page wrote alsostops translating, and a `data-i18n-html` pass still replaces the whole block'sinnerHTML. Keeping the live text in a sibling of the annotated node is what letsthe static sentence translate while the detail stays live. The same rule is why@@ -14485,11 +14500,11 @@ would hide it.## Related-- [x402 paid endpoints](#sec-854): the other side of the ledger. This+- [x402 paid endpoints](#sec-869): the other side of the ledger. Thispage counts agent-to-agent payments recorded in `agent_hires`; endpoint revenuepaid **to** the platform's own paid endpoints is recorded separately in`x402_audit_log`. Do not add the two together.-- [The autonomous economy](#sec-139): how agents get wallets, spend+- [The autonomous economy](#sec-140): how agents get wallets, spendpolicies, and paid skills in the first place, which is what produces the rowsthis page aggregates.@@ -14522,7 +14537,7 @@ One completed job produces:| `full_body[]` | Three 1024x1280 (4:5 portrait) renders, one per pose, same backdrop and lighting || `rigged_glb_url` | The avatar with a humanoid skeleton and skin weights || `mesh_glb_url` | The unrigged generated mesh, kept so a rig hiccup never loses the generation |-| `viewer_url` | Deep link into the three.ws [viewer](#sec-795) for the rigged GLB |+| `viewer_url` | Deep link into the three.ws [viewer](#sec-805) for the rigged GLB || `pose_studio_url` | Deep link into the [Animation Studio](#sec-100) for the rigged GLB |Every render is persisted to object storage under `okx-identity/renders/<job>/` and served from a public URL, so the URLs in the response are permanent and hotlinkable.@@ -14702,13 +14717,13 @@ Two environment overrides help a batch run outlast the rig lane's rate-limit bac## Related-- [OKX.AI Marketplace Services](#sec-456): the price, the payment challenge, the replay flow, the payment guarantees, and the decomposed single-capability 3D services that share these engines.-- [Forge](#sec-313): the text and image to GLB generation pipeline this studio calls for the mesh and the auto-rig.+- [OKX.AI Marketplace Services](#sec-460): the price, the payment challenge, the replay flow, the payment guarantees, and the decomposed single-capability 3D services that share these engines.+- [Forge](#sec-316): the text and image to GLB generation pipeline this studio calls for the mesh and the auto-rig.- [Animation Studio](#sec-100): the `/pose` surface the `pose_studio_url` deep link opens.-- [Viewer](#sec-795): the `/viewer` surface the `viewer_url` deep link opens.-- [MCP servers](#sec-417): the wider set of three.ws MCP endpoints this one follows the transport conventions of.-- [Avatar Engines Atlas](#sec-145): what engine families exist for building human avatars, and which of them are wired into the commercial pipeline.-- [Draft agent mint](#sec-252): the inactive on-chain identity minted for every finished reconstruction, Solana first with ERC-8004 alongside it.+- [Viewer](#sec-805): the `/viewer` surface the `viewer_url` deep link opens.+- [MCP servers](#sec-421): the wider set of three.ws MCP endpoints this one follows the transport conventions of.+- [Avatar Engines Atlas](#sec-146): what engine families exist for building human avatars, and which of them are wired into the commercial pipeline.+- [Draft agent mint](#sec-255): the inactive on-chain identity minted for every finished reconstruction, Solana first with ERC-8004 alongside it.---@@ -14926,8 +14941,8 @@ recovery script for cursors already stuck) lives in| Both crawl crons | [`api/cron/`](../api/cron) || Regression cover | [`tests/agent-index.test.js`](../tests/agent-index.test.js) |-Related: [Trust primitives](#sec-700) scores an agent from on-chain-evidence, and [Custody you can verify](#sec-232) covers the attestations the+Related: [Trust primitives](#sec-708) scores an agent from on-chain+evidence, and [Custody you can verify](#sec-233) covers the attestations the`reputation` and `validation` classes carry.---@@ -15090,7 +15105,7 @@ the agent do this". Create one under **Mail rules** on the inbox page or with| `name` | A short label shown in activity and approvals. || `match_from` | An address, an `@domain`, or `*` for any sender. || `match_subject` | Optional phrase the subject must contain (case-insensitive). |-| `mode` | `approve`: send it to your [approvals inbox](#sec-126) first. `auto`: run at once. |+| `mode` | `approve`: send it to your [approvals inbox](#sec-127) first. `auto`: run at once. || `prompt` | Your instruction, for example "Summarize this email in two sentences and tell me if it needs a reply". |When a received message matches (spam is never matched), the agent gets an@@ -15115,7 +15130,7 @@ clearly malicious and must not be acted upon."## Using it from an MCP client-Connect to `https://three.ws/api/mcp` (see [mcp.md](#sec-417)). The send tools+Connect to `https://three.ws/api/mcp` (see [mcp.md](#sec-421)). The send toolsare financial, so they are hidden until the session enables them with`X-Three-Tools: default,financial` (or the equivalent setting on the API key).@@ -15195,10 +15210,10 @@ curl -s -X POST "$BASE/send" -H "Authorization: Bearer $KEY" \## Related-- [Approvals](#sec-126): where `approve`-mode rule runs wait for you.-- [Notifications](#sec-442): the `mail_received` notification.-- [MCP](#sec-417): connecting a client and enabling financial tools.-- [API reference](#sec-124)+- [Approvals](#sec-127): where `approve`-mode rule runs wait for you.+- [Notifications](#sec-446): the `mail_received` notification.+- [MCP](#sec-421): connecting a client and enabling financial tools.+- [API reference](#sec-125)---@@ -15849,7 +15864,7 @@ Load from on-chain:A manifest served from an API is a claim. A manifest that is **signed and pinned to IPFS** is evidence: anyone can fetch the CID, check the signature, and read the exact system prompt the agent was configured with, without an account and without trusting three.ws.-three.ws signs and pins an agent's manifest automatically on every persona save. The envelope is ed25519-signed by the platform attester identity (the same Solana key behind [3D provenance credentials](#sec-556)) and pinned through the configured IPFS provider.+three.ws signs and pins an agent's manifest automatically on every persona save. The envelope is ed25519-signed by the platform attester identity (the same Solana key behind [3D provenance credentials](#sec-563)) and pinned through the configured IPFS provider.### What a signed envelope looks like@@ -16006,7 +16021,7 @@ The `spec` field identifies the manifest format version. Current stable: `agent-- [Memory Spec](../specs/MEMORY_SPEC.md) — memory file format and MEMORY.md index- [Embed Spec](../specs/EMBED_SPEC.md) — `<agent-3d>` element attributes and events- [Permissions Spec](../specs/PERMISSIONS_SPEC.md) — ERC-7710 delegation format and redemption-- [Provenance](#sec-556) — signed content credentials for generated 3D assets, using the same attester identity as signed manifests+- [Provenance](#sec-563) — signed content credentials for generated 3D assets, using the same attester identity as signed manifests---@@ -16018,7 +16033,7 @@ The `spec` field identifies the manifest format version. Current stable: `agent-**Why autonomous agents need verifiable trust — and how three.ws delivers it on-chain.**-This page is the *why*. For the practical how-to, see [Reputation System](#sec-599) (leaving and reading reviews) and [ERC-8004](#sec-263) (the identity standard underneath). To read a real agent's score five different ways, follow the [Read an agent's reputation](/tutorials/agent-reputation) tutorial. For the Solana side of the same idea — memo attestations, the AgenC coordination program, and the identity bridge — see [Agent Reputation on Solana](#sec-656).+This page is the *why*. For the practical how-to, see [Reputation System](#sec-606) (leaving and reading reviews) and [ERC-8004](#sec-266) (the identity standard underneath). To read a real agent's score five different ways, follow the [Read an agent's reputation](/tutorials/agent-reputation) tutorial. For the Solana side of the same idea — memo attestations, the AgenC coordination program, and the identity bridge — see [Agent Reputation on Solana](#sec-664).---@@ -16082,7 +16097,7 @@ Each agent is an NFT; whoever owns the token controls the agent. The token pointA reserved, signature-gated field binds a verified payment wallet to the agent (proven with an EIP-712 signature, and cleared automatically if the NFT is transferred).-> Full detail: [ERC-8004](#sec-263).+> Full detail: [ERC-8004](#sec-266).### 2. Reputation Registry — what others think of it@@ -16111,7 +16126,7 @@ Reputation only matters because money moves on the other side of it. The two hal1. **Discover** a service via the Identity Registry.2. **Check** its reputation — proceed only if it clears your threshold.-3. **Pay** — the service answers an HTTP `402` and the agent signs a stablecoin micropayment ([x402](#sec-862)).+3. **Pay** — the service answers an HTTP `402` and the agent signs a stablecoin micropayment ([x402](#sec-877)).4. **Vouch** — after the work, write feedback back to the Reputation Registry, closing the loop for the next agent.The one-liner worth remembering:@@ -16132,7 +16147,7 @@ The same on-chain data is exposed through every layer a reader might come from:| Reputation panel | agent profiles | The embedded vouch/score widget on `https://three.ws/a/<chainId>/<agentId>` || `GET /api/agents/<id>/reputation` | apps | The agent's unified wallet trust score: a 0-100 credibility number derived from real ledger and on-chain activity, with a per-pillar breakdown and evidence links || `agent_reputation` MCP tool | AI agents | Paid ($0.01 USDC) read of identity + score + stake + recent events; resolves a wallet to its agent automatically |-| `GET /api/x402/agent-reputation` | AI agents | Paid ($0.01) cross-chain 0–100 trust score for **any** counterparty — Solana/EVM wallet, pump.fun mint, ERC-8004 agent id, or three.ws agent_id (auto-detected). See [Trust primitives](#sec-700) |+| `GET /api/x402/agent-reputation` | AI agents | Paid ($0.01) cross-chain 0–100 trust score for **any** counterparty — Solana/EVM wallet, pump.fun mint, ERC-8004 agent id, or three.ws agent_id (auto-detected). See [Trust primitives](#sec-708) || [Agent Passport](/agent-passport.html) | trust decisions | An A–D trust grade weighted toward credentialed and verified feedback || ERC-8004 helpers (`src/erc8004/reputation.js`; ABIs re-exported by `@three-ws/sdk`) | developers | `getReputation`, `getRecentReviews`, `getTotalStake`, `submitFeedback`, `stakeReputation`, `supportsStaking`; raw dialect-aware reads in `src/erc8004/reputation-read.js` (`readAgentReputation`) |@@ -16171,7 +16186,7 @@ The only difference is **reach**. The Club's reputation dies the moment a walletThat portability is what lets a three.ws agent be trusted by an agent that has never heard of three.ws. It's the foundation the agent economy is built on — and the reason reputation, not payments, is the harder and more important half of the stack.-**Next:** [Read an agent's reputation](/tutorials/agent-reputation) · [Reputation on Solana](#sec-656) · [Leave a vouch](#sec-599) · [ERC-8004 identity](#sec-263) · [x402 payments](#sec-862)+**Next:** [Read an agent's reputation](/tutorials/agent-reputation) · [Reputation on Solana](#sec-664) · [Leave a vouch](#sec-606) · [ERC-8004 identity](#sec-266) · [x402 payments](#sec-877)---@@ -16694,10 +16709,10 @@ relationship into an account with a real agent. Ambient discovery routesthrough the agent too — the old "have you tried…" toast stays out of the cornerwhile the companion is live.-Related: [web-component.md](#sec-799) (the embeddable `agent-3d`-avatar), [coin-pages.md](#sec-194) (the market surfaces the shell-navigates), [companion.md](#sec-209) (the same corner companion delivering-messages from connected sources in person), [feedback.md](#sec-304)+Related: [web-component.md](#sec-811) (the embeddable `agent-3d`+avatar), [coin-pages.md](#sec-195) (the market surfaces the shell+navigates), [companion.md](#sec-210) (the same corner companion delivering+messages from connected sources in person), [feedback.md](#sec-307)(reporting what broke through the companion), [STRUCTURE.md](../STRUCTURE.md)(surface map).@@ -16714,7 +16729,7 @@ Claude surface — Claude Code, the Claude apps, the Agent SDK — how to use ththree.ws platform: create and rig 3D models, run a wallet, and buy/sell services inthe x402 agent economy.-> Not to be confused with the [in-app skills system](#sec-649), which extends+> Not to be confused with the [in-app skills system](#sec-657), which extends> avatars and agents **inside** three.ws with `manifest.json` + `tools.json` +> `handlers.js` bundles. Agent Skills are the inverse: they extend **external**> AI agents with three.ws capabilities.@@ -16982,7 +16997,7 @@ Every three.ws agent has its own custodial Solana wallet. The Agent Sniper is thThis doc explains the whole system, walks through the first live trade an agent closed on the platform (a real +42.38% exit, receipts included), and lays out where the system goes next.-Related surfaces: [the trading surfaces](#sec-695) (Radar, Coin Intelligence, Mission Control), [trading experiment](#sec-692) (the laddered-exit research policy), [agent wallets](#sec-077) (how custody works), and the worker itself at `workers/agent-sniper/` (its README is the operator reference).+Related surfaces: [the trading surfaces](#sec-703) (Radar, Coin Intelligence, Mission Control), [trading experiment](#sec-700) (the laddered-exit research policy), [agent wallets](#sec-077) (how custody works), and the worker itself at `workers/agent-sniper/` (its README is the operator reference).---@@ -17134,8 +17149,8 @@ The direction of every bridge is the same: real, realized money is the ground tr## Try it- Arm your first strategy: [the sniper tutorial](/tutorials/arm-an-agent-sniper)-- Watch the engine think: [Coin Intelligence and the trading surfaces](#sec-695)-- The research policy behind laddered exits: [trading experiment](#sec-692)+- Watch the engine think: [Coin Intelligence and the trading surfaces](#sec-703)+- The research policy behind laddered exits: [trading experiment](#sec-700)- The story of the first trade, for non-operators: [the blog post](/blog/first-autonomous-trade)---@@ -17161,7 +17176,7 @@ An agent is not one thing; it is a brain, a memory, a body, a wallet, and a setskills, and until now each of those lived on a different page. Agent Studio unifiesthem into one workspace so you can see the whole agent at once and watch changes takeeffect immediately. It is the deep-authoring counterpart to the fast on-ramp in-[Instant Agent Genesis](#sec-321): Genesis gets you a complete agent in a minute,+[Instant Agent Genesis](#sec-324): Genesis gets you a complete agent in a minute,Studio is where you make it exactly what you want. For the broader model of what anagent is, see [Agent System](#sec-068).@@ -17185,7 +17200,7 @@ real agent APIs.- **The five tabs**, each a mount point the sub-studio fills:- **Brain**: model and provider selection plus the reasoning setup, exercised liveagainst `/api/brain/chat` (the same multi-LLM backend documented in- [Multi-LLM Brain](#sec-172)).+ [Multi-LLM Brain](#sec-173)).- **Memory**: what the agent remembers and for how long, over `/api/agent-memory`and the `/api/memory/*` context, search, graph, and curate endpoints.- **Body**: the 3D avatar, outfit, and animations, reflected live on the stage via@@ -17222,7 +17237,7 @@ once.The studio saves through the standard agent update endpoint, so the same edits arescriptable. Read your agent, then patch a domain under `meta.studio` (see-[Authentication](#sec-138)):+[Authentication](#sec-139)):```bash# Load (or lazily create) your agent@@ -17267,8 +17282,8 @@ curl -s https://three.ws/api/agents/<agent-id>/pricing \## Related- [Agent System](#sec-068): the full model of what an agent is-- [Instant Agent Genesis](#sec-321): create the agent Studio edits-- [Multi-LLM Brain](#sec-172): the model backend behind the Brain tab+- [Instant Agent Genesis](#sec-324): create the agent Studio edits+- [Multi-LLM Brain](#sec-173): the model backend behind the Brain tab- [Agent Skills](#sec-064): the capabilities the Skills tab manages- [Agent Wallets](#sec-077): the wallet behind the Money tab- Pages: [/agent-studio](https://three.ws/agent-studio), [/genesis](https://three.ws/genesis), [/brain](https://three.ws/brain)@@ -17303,7 +17318,7 @@ user gesture. Nothing autoplays.## Where the events come fromThe symphony consumes the same live ticker documented in-[Money Feed](#sec-433):+[Money Feed](#sec-437):1. `GET /api/feed?limit=40` paints the initial ledger (played silently asbacklog, not as notes).@@ -17319,7 +17334,7 @@ you hear.## What sounds map to what eventsEvery allow-listed feed type (see the type table in-[Money Feed](#sec-433)) maps to one of six voices in+[Money Feed](#sec-437)) maps to one of six voices in`TYPE_TO_CATEGORY` in [`src/symphony-score.js`](../src/symphony-score.js).Each voice has its own synth patch in the engine, its own color in thevisualization, and its own mute button in the legend.@@ -17429,7 +17444,7 @@ cross-links are asserted statically by## Related-- [Money Feed](#sec-433): the activity bus this page renders, including+- [Money Feed](#sec-437): the activity bus this page renders, includingthe full event-type table and how events are published.- [Agora](#sec-080): the on-chain economy lifecycle behind the `agora-*`events.@@ -17637,7 +17652,7 @@ Captures what is currently visible and describes it so the agent can react to wh### Stage-scoped tools-When the runtime is attached to an `<agent-stage>`, two extra tools are appended (see [multi-agent.md](#sec-438)): `observe_agents` (list the other agents on stage with names and positions) and `say_to_agent` (send a message to a named stagemate).+When the runtime is attached to an `<agent-stage>`, two extra tools are appended (see [multi-agent.md](#sec-442)): `observe_agents` (list the other agents on stage with names and positions) and `say_to_agent` (send a message to a named stagemate).---@@ -18378,7 +18393,7 @@ POST /api/pump/launch-agent { "agent_id": "…", "name": "…", "symbol": "…"```This is the path that supports USDC-paired curves and binds the on-chain pump-agent for buybacks. See [the pump.fun launcher](#sec-561).+agent for buybacks. See [the pump.fun launcher](#sec-568).Both paths write a `pump_agent_mints` row and call back into the plan to mark itlaunched, so a coin appears on [/launches](https://three.ws/launches), in the@@ -18462,10 +18477,10 @@ doubles as a check on the lane.## Related-- [The pump.fun launcher](#sec-561): the launch transaction itself-- [Coin launches](#sec-193): the platform launch directory-- [Platform fee](#sec-562): what three.ws takes on a launch-- [Solana on pump.fun](#sec-655): the on-chain program surface+- [The pump.fun launcher](#sec-568): the launch transaction itself+- [Coin launches](#sec-194): the platform launch directory+- [Platform fee](#sec-569): what three.ws takes on a launch+- [Solana on pump.fun](#sec-663): the on-chain program surfaceNote on promotion: `$THREE` is the coin three.ws promotes. Agent tokens are coinsusers launch through the platform, rendered from the platform's own launch@@ -18675,10 +18690,10 @@ Every three.ws agent owns one custodial **Solana** wallet. Seven owner-only HTTPThis document is the API reference the surrounding docs deliberately leave out. Read those first for the "why":- [Agent wallets](#sec-077) for how the wallet is created, how its key is held, and which paths may spend.-- [Custody you can verify](#sec-232) for the limits, the freeze switch, the Merkle proof of custody, and the social-recovery model.-- [Financial controls](#sec-306) for the plain-English spend-rule layer and the anomaly guard behind `/solana/guard`.-- [The Trading Copilot](#sec-691) for the conversational surface that proposes trades a human confirms.-- [Coin Autopilot](#sec-141) for the *coin* cockpit at `/api/pump/autopilot`. That is a different feature from the **Treasury Autopilot** documented here, which runs the agent's own wallet rather than a launched coin.+- [Custody you can verify](#sec-233) for the limits, the freeze switch, the Merkle proof of custody, and the social-recovery model.+- [Financial controls](#sec-309) for the plain-English spend-rule layer and the anomaly guard behind `/solana/guard`.+- [The Trading Copilot](#sec-699) for the conversational surface that proposes trades a human confirms.+- [Coin Autopilot](#sec-142) for the *coin* cockpit at `/api/pump/autopilot`. That is a different feature from the **Treasury Autopilot** documented here, which runs the agent's own wallet rather than a launched coin.## Orientation@@ -18694,7 +18709,7 @@ All seven surfaces address the same custodial Solana keypair, obey the same owne| Recovery | `/api/agents/:id/recovery` | Guardians, approval threshold, dead-man check-in, inheritance || Solana guard | `/api/agents/:id/solana/guard` | The behavioral anomaly baseline, its sensitivity, and freeze adjudication |-The shared model, in one paragraph. A caller is resolved to a user id from either a session cookie or a bearer token. That user must own the agent, or the surface refuses (recovery is the one exception: guardians and the beneficiary get a scoped view). Every mutation is CSRF-gated for cookie callers. Anything that can move funds runs through the shared spend guards in [`api/_lib/agent-trade-guards.js`](../api/_lib/agent-trade-guards.js), so the wallet-wide policy (`per_tx_usd`, `daily_usd`, `per_counterparty_daily_usd`, `withdraw_allowlist` (the [destination whitelist](#sec-242), edited through `/api/wallet-whitelist`), `frozen`, `require_capabilities`) is enforced at the signing boundary, not per feature. A scheduled order, an armed intent, an autopilot rule, and an autonomous agent-to-agent payment are therefore all subject to the same ceilings and the same freeze as a manual trade. That enforcement fails closed on its inputs: a caller that hands the guard neither a pre-read policy nor the agent's meta gets the agent's real policy read from its row, and a spend for an agent that no longer exists is refused rather than defaulted to an unrestricted wallet. See [autonomous agent-to-agent payments](#sec-008) for the policy fields, the kill switch, and the receipts they leave behind.+The shared model, in one paragraph. A caller is resolved to a user id from either a session cookie or a bearer token. That user must own the agent, or the surface refuses (recovery is the one exception: guardians and the beneficiary get a scoped view). Every mutation is CSRF-gated for cookie callers. Anything that can move funds runs through the shared spend guards in [`api/_lib/agent-trade-guards.js`](../api/_lib/agent-trade-guards.js), so the wallet-wide policy (`per_tx_usd`, `daily_usd`, `per_counterparty_daily_usd`, `withdraw_allowlist` (the [destination whitelist](#sec-243), edited through `/api/wallet-whitelist`), `frozen`, `require_capabilities`) is enforced at the signing boundary, not per feature. A scheduled order, an armed intent, an autopilot rule, and an autonomous agent-to-agent payment are therefore all subject to the same ceilings and the same freeze as a manual trade. That enforcement fails closed on its inputs: a caller that hands the guard neither a pre-read policy nor the agent's meta gets the agent's real policy read from its row, and a spend for an agent that no longer exists is refused rather than defaulted to an unrestricted wallet. See [autonomous agent-to-agent payments](#sec-008) for the policy fields, the kill switch, and the receipts they leave behind.## Shared conventions@@ -18748,7 +18763,7 @@ Arming or running anything that can move real funds additionally requires that t- Refusal is `403 risk_ack_required`. The body carries `context`, the current `version`, a `sign_url`, and the `documents` to sign. Nothing is armed and nothing is sent.- Devnet is exempt, so `?network=devnet` writes pass without a signature.- Only the arming direction is gated. Reads, previews, simulations, pausing, disarming, the kill switch, and deleting never ask for it: stopping an agent must always be possible.-- Sign once at [/legal/agreements](https://three.ws/legal/agreements). See [risk-acknowledgment.md](#sec-618).+- Sign once at [/legal/agreements](https://three.ws/legal/agreements). See [risk-acknowledgment.md](#sec-625).- Where the agreement and CSRF both apply, the agreement is checked first, so a refusal does not consume the caller's single-use CSRF token.### Network selection@@ -19366,7 +19381,7 @@ curl -s -X PUT "https://three.ws/api/agents/$AGENT_ID/intents/$INTENT_ID" \Source: [`api/agents/autopilot.js`](../api/agents/autopilot.js), engine in [`api/_lib/treasury-autopilot.js`](../api/_lib/treasury-autopilot.js). Product tour: [Autopilot](#sec-043).-Treasury Autopilot is the policy that lets an agent fund its own existence: pay its metered compute, hold a buffer, accumulate `$THREE`, compound its coin fees, and sweep real profit to its owner. It is stored on the agent, compiled from English, and armed only by an explicit owner write. Not to be confused with [Coin Autopilot](#sec-141), which governs a launched coin at `/api/pump/autopilot`.+Treasury Autopilot is the policy that lets an agent fund its own existence: pay its metered compute, hold a buffer, accumulate `$THREE`, compound its coin fees, and sweep real profit to its owner. It is stored on the agent, compiled from English, and armed only by an explicit owner write. Not to be confused with [Coin Autopilot](#sec-142), which governs a launched coin at `/api/pump/autopilot`.| Method | Route | Purpose ||---|---|---|@@ -19620,7 +19635,7 @@ The first `snapshot` is pushed immediately on connect. The stream carries only t## Recovery: guardians, threshold, and inheritance-Source: [`api/agents/recovery.js`](../api/agents/recovery.js), engine in [`api/_lib/agent-recovery.js`](../api/_lib/agent-recovery.js). Product tour: [Recovery](#sec-052), and the counterpart console in [Guardian](#sec-336).+Source: [`api/agents/recovery.js`](../api/agents/recovery.js), engine in [`api/_lib/agent-recovery.js`](../api/_lib/agent-recovery.js). Product tour: [Recovery](#sec-052), and the counterpart console in [Guardian](#sec-340).Recovery transfers *ownership*, never the key. The wallet secret is never decrypted, displayed, or moved. This is the one surface here that is not owner-only: a guardian or a beneficiary is a first-class caller with a scoped view.@@ -19762,7 +19777,7 @@ Guardian or beneficiary only. No body. Arms the dead-man switch once the owner h## Solana guard: the self-defending wallet-Source: [`api/agents/solana-guard.js`](../api/agents/solana-guard.js), scoring in [`api/_lib/wallet-anomaly.js`](../api/_lib/wallet-anomaly.js), event store in [`api/_lib/anomaly-events.js`](../api/_lib/anomaly-events.js). Behavior narrative: [Financial controls](#sec-306).+Source: [`api/agents/solana-guard.js`](../api/agents/solana-guard.js), scoring in [`api/_lib/wallet-anomaly.js`](../api/_lib/wallet-anomaly.js), event store in [`api/_lib/anomaly-events.js`](../api/_lib/anomaly-events.js). Behavior narrative: [Financial controls](#sec-309).Scoring and freezing happen inline on the spend path, not here. This endpoint is the owner's window into that system and the control over it: read the learned baseline and the anomaly timeline, tune sensitivity, set a safe-sweep address, and adjudicate a freeze.@@ -19880,12 +19895,12 @@ curl -s -X POST "https://three.ws/api/agents/$AGENT_ID/solana/guard" \## Related- [Agent wallets](#sec-077) for the wallet itself: creation, key custody, and the five spend paths.-- [Custody you can verify](#sec-232) for limits, freeze, proof of custody, and the recovery model in prose.-- [Financial controls](#sec-306) for the plain-English spend rules and the wallet-defense behaviors.-- [The Trading Copilot](#sec-691) for the conversational read-and-propose surface over the same wallet.-- [Coin Autopilot](#sec-141) for the separate coin cockpit at `/api/pump/autopilot`.+- [Custody you can verify](#sec-233) for limits, freeze, proof of custody, and the recovery model in prose.+- [Financial controls](#sec-309) for the plain-English spend rules and the wallet-defense behaviors.+- [The Trading Copilot](#sec-699) for the conversational read-and-propose surface over the same wallet.+- [Coin Autopilot](#sec-142) for the separate coin cockpit at `/api/pump/autopilot`.- [What agents can do](#sec-011) for a page per wallet ability, including [Access](#sec-051), [Orders](#sec-042), [Intents](#sec-044), [Autopilot](#sec-043), [Portfolio](#sec-033), and [Recovery](#sec-052).-- [Guardian console](#sec-336) for the other side of a recovery request.+- [Guardian console](#sec-340) for the other side of a recovery request.---@@ -19897,7 +19912,7 @@ curl -s -X POST "https://three.ws/api/agents/$AGENT_ID/solana/guard" \Every three.ws agent owns a **custodial Solana wallet**. It is what lets an agent act on its own — pay for an API call, buy a coin, tip another agent, receive its earnings — without a human approving each transaction in a browser extension.-This is the reference for the wallet itself: how it's created, how its key is held, what may spend from it, and where the controls live. For the owner-facing safety story (limits, freeze, proof, recovery) read [Custody you can verify](#sec-232). For the complete tour of everything the wallet can do, read [What agents can do → The Agent Wallet](#sec-025).+This is the reference for the wallet itself: how it's created, how its key is held, what may spend from it, and where the controls live. For the owner-facing safety story (limits, freeze, proof, recovery) read [Custody you can verify](#sec-233). For the complete tour of everything the wallet can do, read [What agents can do → The Agent Wallet](#sec-025).## What you get@@ -19917,7 +19932,7 @@ The encryption key derives, via HKDF, from a dedicated secret (`WALLET_ENCRYPTIOThis is the same secret box used for coin treasuries and the launcher, so every custodial secret on the platform is held the same way.-**What this means honestly:** the platform can sign for the agent. That is the point — an autonomous agent that needs you to approve each transaction is not autonomous. What the platform gives you in exchange is that everything it *can* do is capped by policy you set, halted by a freeze you control, recorded in an audit trail, and provable on-chain. See [custody.md](#sec-232).+**What this means honestly:** the platform can sign for the agent. That is the point — an autonomous agent that needs you to approve each transaction is not autonomous. What the platform gives you in exchange is that everything it *can* do is capped by policy you set, halted by a freeze you control, recorded in an audit trail, and provable on-chain. See [custody.md](#sec-233).## Who can spend@@ -19926,9 +19941,9 @@ Five paths move funds out of an agent wallet, and **all five pass through one po| Path | Trigger ||------|---------|| Withdraw | The owner sweeps funds out |-| x402 pay | The agent pays for a paid API call. Also reachable from any paid checkout on the site: the [x402 payment modal](#sec-744) lists a signed-in user's agents next to Phantom, and picking one settles from that agent's wallet with no popup |+| x402 pay | The agent pays for a paid API call. Also reachable from any paid checkout on the site: the [x402 payment modal](#sec-752) lists a signed-in user's agents next to Phantom, and picking one settles from that agent's wallet with no popup || Trade | A discretionary buy/sell from the wallet hub, or from the in-world coin widget's **Pay with** selector (SOL-denominated coins) |-| Purchase | The agent buys a marketplace skill or asset for itself (see [Marketplace](#sec-408)), under its own daily purchase cap |+| Purchase | The agent buys a marketplace skill or asset for itself (see [Marketplace](#sec-412)), under its own daily purchase cap || Snipe | The autonomous sniper worker executes a strategy |Because enforcement lives at the signing boundary rather than in each feature, a new feature cannot accidentally introduce an unguarded spend path.@@ -19939,7 +19954,7 @@ Limits are stored per agent and are **opt-in** — an unset ceiling means "no gl- `daily_usd` — rolling 24-hour USD-equivalent outflow ceiling, summed from the custody ledger- `per_tx_usd` — maximum USD-equivalent for a single outbound transaction-- `withdraw_allowlist`, the active addresses on the [destination whitelist](#sec-242); new addresses serve a cooldown (24h default, 1h minimum) and need step-up before they can receive funds+- `withdraw_allowlist`, the active addresses on the [destination whitelist](#sec-243); new addresses serve a cooldown (24h default, 1h minimum) and need step-up before they can receive funds- `frozen` — the kill switch: every **autonomous** path is refused- `require_capabilities` — when on, every autonomous spend must present a valid [scoped session key](#sec-051)@@ -19950,7 +19965,7 @@ Two asymmetries are deliberate:Coin-launch and bonding-curve activity carries an additional SOL-denominated policy (`max_sol_per_tx`, `daily_sol_cap`, an optional `allowed_mints` allowlist). A freshly provisioned agent that has never been configured defaults to **1 SOL per transaction and 5 SOL per rolling day**, so a stolen session token cannot drain it.-On top of the numeric caps sit two additive layers, each of which can only ever *narrow* a spend, never widen it: [natural-language spend rules](#sec-306) that an LLM authors and deterministic code enforces, and a behavioral anomaly guard that freezes the wallet when a spend doesn't look like the agent's normal behavior.+On top of the numeric caps sit two additive layers, each of which can only ever *narrow* a spend, never widen it: [natural-language spend rules](#sec-309) that an LLM authors and deterministic code enforces, and a behavioral anomaly guard that freezes the wallet when a spend doesn't look like the agent's normal behavior.### The audit trail@@ -19972,7 +19987,7 @@ Key endpoints:- `POST /api/agents/:id/solana/withdraw`: sweep an asset out- `GET /api/agents/:id/solana/guard` — anomaly guard state and flagged activity-Full request/response shapes are in the [REST API reference](#sec-124).+Full request/response shapes are in the [REST API reference](#sec-125).## Paying by name@@ -19980,11 +19995,11 @@ An agent can pay a human-readable name instead of a base58 address. `/api/x402/p## Related-- [Custody you can verify](#sec-232) — limits, freeze, Merkle proof-of-custody, social recovery and inheritance-- [Financial controls](#sec-306) — plain-English spend rules, compiled and enforced deterministically+- [Custody you can verify](#sec-233) — limits, freeze, Merkle proof-of-custody, social recovery and inheritance+- [Financial controls](#sec-309) — plain-English spend rules, compiled and enforced deterministically- [What agents can do](#sec-011) — the complete dossier, including a page per wallet ability-- [x402 protocol](#sec-862) — how agents pay for services-- [Coin launches](#sec-193) — how the wallet signs a pump.fun launch+- [x402 protocol](#sec-877) — how agents pay for services+- [Coin launches](#sec-194) — how the wallet signs a pump.fun launch---@@ -20182,11 +20197,11 @@ An "awakening" envelope (no eligible trading agent yet) is still valid and fully## Related-- [Oracle](#sec-467) - the conviction engine this class of agent trades on+- [Oracle](#sec-472) - the conviction engine this class of agent trades on- [Agent reputation](#sec-060) - the Reasoning Ledger score behind the reputation ring-- [Reputation](#sec-599) - how proven on-chain track records are computed-- [The trading experiment](#sec-692) - an autonomous agent operating inside these limits, journaled-- [Custody you can verify](#sec-232) - the spend caps and kill switch the autonomy runs under+- [Reputation](#sec-606) - how proven on-chain track records are computed+- [The trading experiment](#sec-700) - an autonomous agent operating inside these limits, journaled+- [Custody you can verify](#sec-233) - the spend caps and kill switch the autonomy runs under- [/activity](https://three.ws/activity) - every agent's live trades in real time---@@ -22284,9 +22299,9 @@ of rendering a fake zero.## Related surfaces-- [`/portfolio`](#sec-503): the live wallet portfolio; the two pages+- [`/portfolio`](#sec-510): the live wallet portfolio; the two pagescross-link and share the recent-wallet list.-- [`/api/crypto/wallet`](#sec-231): the raw balance endpoint the token+- [`/api/crypto/wallet`](#sec-232): the raw balance endpoint the tokendiversity measurement rides on.---@@ -22366,10 +22381,10 @@ When `read.hallucination_guard.line_replaced` is true, the co-pilot caught a fig## Related-- [Custody you can verify](#sec-232) - the spend limits, firewall, and audit the "Act" path runs under-- [Financial controls](#sec-306) - the plain-English rules and real-time defense on the same rails-- [Oracle](#sec-467) - the platform conviction engine over the same launch universe-- [Trading surfaces](#sec-695) - Mission Control executes through this same guarded path+- [Custody you can verify](#sec-233) - the spend limits, firewall, and audit the "Act" path runs under+- [Financial controls](#sec-309) - the plain-English rules and real-time defense on the same rails+- [Oracle](#sec-472) - the platform conviction engine over the same launch universe+- [Trading surfaces](#sec-703) - Mission Control executes through this same guarded path- [/agi](https://three.ws/agi) - a fully autonomous agent reading and trading the same feed---@@ -22388,7 +22403,7 @@ leader sets.**It is off by default. A leader who never touches it releases every signal toevery copier at the same moment, which is exactly what [copy-trading](#sec-225) did before this existed.+trading](#sec-226) did before this existed.> **A drip delays the reveal, never the record.** The intent row is written in> full the moment the leader trades, and the trade lands in the leader's public@@ -22396,9 +22411,9 @@ trading](#sec-225) did before this existed.> API has no field that could express one. What a ladder controls is when a> given copier is shown the coin and the size.-Related reading: [copy trading](#sec-225) for the engine the ladder sits+Related reading: [copy trading](#sec-226) for the engine the ladder sitson, [the $THREE token page](https://three.ws/three-token) for the tier-thresholds, and [trader passport](#sec-688) for the public record a+thresholds, and [trader passport](#sec-696) for the public record adrip cannot touch.---@@ -22572,7 +22587,7 @@ and no code path here reads another trader's pending activity. The standingdisclosure says exactly that, on every surface, and a leader cannot remove it.Every trade a leader makes remains in their public track record, their-[trader passport](#sec-688), and the leaderboard, at the moment it+[trader passport](#sec-696), and the leaderboard, at the moment ithappens, regardless of any ladder.---@@ -23394,7 +23409,7 @@ with no console errors.# Animation Studio: pose, keyframe, and sell motion-Animation Studio is where a three.ws avatar (or a built-in mannequin) becomes animated. Click any body part and rotate it with a gizmo, or drag a hand or foot and let inverse kinematics solve the limb. Drop the pose as a keyframe, advance the playhead, re-pose, and drop another; the studio interpolates between them and plays the result. Export the finished motion as an animated GLB or as clip JSON, save it to your account, deep-link it to play on any avatar, hand it to [Scene Studio](#sec-625) to record as video, or list it for sale in the animation marketplace for USDC.+Animation Studio is where a three.ws avatar (or a built-in mannequin) becomes animated. Click any body part and rotate it with a gizmo, or drag a hand or foot and let inverse kinematics solve the limb. Drop the pose as a keyframe, advance the playhead, re-pose, and drop another; the studio interpolates between them and plays the result. Export the finished motion as an animated GLB or as clip JSON, save it to your account, deep-link it to play on any avatar, hand it to [Scene Studio](#sec-632) to record as video, or list it for sale in the animation marketplace for USDC.Page: [/pose](https://three.ws/pose) · API: `/api/animations/clips`@@ -23428,7 +23443,7 @@ Under the motion generator sits a Spell box: type a word and the avatar spells iA spelled word is shareable as a link: `https://three.ws/pose?spell=HELLO` opens the studio, auto-loads a rigged avatar (same roster as animation deep links), and spells the word on arrival.-Fingerspelling is the deterministic, spelling-based subset of sign language, it spells English words rather than translating into grammatical ASL. The Studio's Spell box is spelling only. The platform also has a lexical vocabulary (words that are signed rather than spelled, on one or both hands), which drives [/sign-language](https://three.ws/sign-language), signed chat replies, and the `sign-language` embed attribute. See [docs/sign-language.md](#sec-641) for the whole system, or the tutorial [Make your avatar sign](https://three.ws/tutorials/sign-with-your-avatar) for a guided tour.+Fingerspelling is the deterministic, spelling-based subset of sign language, it spells English words rather than translating into grammatical ASL. The Studio's Spell box is spelling only. The platform also has a lexical vocabulary (words that are signed rather than spelled, on one or both hands), which drives [/sign-language](https://three.ws/sign-language), signed chat replies, and the `sign-language` embed attribute. See [docs/sign-language.md](#sec-649) for the whole system, or the tutorial [Make your avatar sign](https://three.ws/tutorials/sign-with-your-avatar) for a guided tour.### Export, save, and sell@@ -23490,8 +23505,8 @@ An empty `tracks` array is rejected: a clip with no motion is not a clip. Track- [Animations reference](#sec-101): the runtime clip registry, formats, and agent slots.- [3D asset pipeline](#sec-002): how GLB, FBX, and clip JSON convert across the platform.-- [Scene Studio](#sec-625): record your animation to video.-- [Avatar Studio](#sec-150): build the avatar you animate here.+- [Scene Studio](#sec-632): record your animation to video.+- [Avatar Studio](#sec-151): build the avatar you animate here.- [/marketplace](https://three.ws/marketplace): where listed animation clips are bought and sold.---@@ -23632,8 +23647,8 @@ Its measured companion is `public/animations/signatures.json`: a motion-signatur[three.ws/animations](https://three.ws/animations) is the public browse surface over every clip: the curated studio manifest, the full R2-hosted motion-capture library (`GET /api/animations/library`, ~219 CC0-sourced clips as of this writing; `total` on that response is the live count, and it grows as more CC0 packs or self-hosted text-to-motion generations are added), and community-published clips (`GET /api/animations/clips?visibility=public`).- **Poster thumbnails**: a WebP still of the preview avatar posed mid-motion, rendered offline by `node scripts/build-animation-thumbnails.mjs` (which drives `scripts/thumbnail-harness.html` in headless Chromium through the site's own retarget engine). Curated thumbs are committed at `public/animations/thumbs/<name>.webp`; library thumbs upload to R2 alongside their clips via `npm run cc0-library:upload`, which publishes each one as the manifest entry's `thumb` URL. Added a clip? Re-run the thumbnail script, then re-upload. **The library manifest's `thumb` field is the only source of truth for a library thumbnail.** Coverage is partial, and the gallery renders the clip's icon for those instead of guessing a CDN path: the guess 404s on every one of them, which cost a blocked cross-origin request per card.-- **Categories** — the bulk library carries no category metadata, so `src/animation-categories.js` derives one per clip from its label (ordered keyword rules; curated clips keep their hand-assigned `animation-presets.js` category). Covered by `tests/animation-categories.test.js`, which also asserts <10% of the real library falls into the "More" catch-all.-- **Per-clip credit** — every bulk-library card shows its source pack and license next to the category chip (`src/animations-gallery.js` `normalizeFullLibraryClip`), pulled straight from the manifest's `source`/`license` fields. See "Licensing" below.+- **Categories**: the bulk library carries no category metadata, so `src/animation-categories.js` derives one per clip from its label (ordered keyword rules; curated clips keep their hand-assigned `animation-presets.js` category). Covered by `tests/animation-categories.test.js`, which also asserts <10% of the real library falls into the "More" catch-all.+- **Per-clip credit**: every bulk-library card shows its source pack and license next to the category chip (`src/animations-gallery.js` `normalizeFullLibraryClip`), pulled straight from the manifest's `source`/`license` fields. See "Licensing" below.- **Live previews** — one shared WebGL engine (`src/animations-live-preview.js`) serves every card hover and the detail modal: a single renderer + preview avatar; the canvas moves into whichever card is previewing. Nothing 3D loads until the first hover.- **Deep links**: `?clip=<id>` opens a clip's detail modal directly; `q`, `cat`, `filter`, and `sort` round-trip through the URL so filtered views are shareable. Every one of them is validated against the values the controls can represent, so a hand-edited `?sort=bogus` falls back to `featured` rather than blanking the sort menu, and an arriving `?filter=once` presses the matching segmented button instead of filtering invisibly.- **Detail modal**: a real dialog. Focus moves into it on open, Tab wraps inside it, Escape closes it and returns focus to the card that opened it. Arrow keys step through the filtered list (except while a slider is focused, which owns its own arrows), and Space toggles playback. The transport row only appears once a clip is actually on the stage, so a preview that fails to load shows the error and its Studio link rather than controls that do nothing.@@ -24517,7 +24532,7 @@ announcement from scratch, and without the output reading like 300 posts from onIt sits between two things that already existed: the[announcement ledger](#sec-106), which scores what is worth announcing, and the-[X content pipeline](#sec-812), which publishes a reviewed queue on a human cadence.+[X content pipeline](#sec-825), which publishes a reviewed queue on a human cadence.The gap between them was the whole job: deciding when each surface goes out, gathering the factsthat make a post checkable, and writing the thing.@@ -24559,7 +24574,7 @@ publishing rather than chosen here:The plan is a pure function of the ledger and the start date, so it is regenerated rather thanmaintained. A surface already queued, named in a queued story's `covers` list (see-[x-story-authoring.md](#sec-850)), already carrying a pack, or listed in+[x-story-authoring.md](#sec-865)), already carrying a pack, or listed in[`data/announce-deferred.json`](../data/announce-deferred.json) is dropped from it.**Gated surfaces are held out of the dated calendar.** `--hold-gated` (which `announce:kit` passes@@ -24877,7 +24892,7 @@ affected files are kept out of the tree by `.gitignore` until approval is record## PostingNothing here posts. Publishing to an external channel is owner-gated every time. A finished pack-becomes an item in the [X content queue](#sec-812): its post names the pack file in+becomes an item in the [X content queue](#sec-825): its post names the pack file in`textFrom`, so `npm run x:content:check` fails if the queued text drifts from the reviewed bytes,and its media points at the captured frame. Preview exactly what would be sent:@@ -24894,6 +24909,7 @@ the queue, `node scripts/post-tweet.mjs --file docs/announcements/<slug>.post.tx|---|---|---|| [genesis.md](#sec-116) | [`/genesis`](https://three.ws/genesis) | drafted, awaiting approval to post || [open-source-friday.md](#sec-119) | [`/rig-doctor`](https://three.ws/rig-doctor) | drafted, awaiting approval to post |+| [openai-partner-benefits.md](#sec-120) | [`/openai`](https://three.ws/openai) | drafted, awaiting approval to post |---@@ -25344,8 +25360,8 @@ The queue item is `awesome` in [`data/x-content/queue.json`](../data/x-content/qWritten against [the announcement voice](#sec-102). The surface here is not a three.wsroute: it is a 34,000-character engineering article on Amazon's own builder platform, under thethree.ws byline, with `$THREE` in the headline. The repo copy is-[aws-builder-center-before-the-signature.md](#sec-155) and the-index of everything we have published there is [aws-builder-center.md](#sec-162).+[aws-builder-center-before-the-signature.md](#sec-156) and the+index of everything we have published there is [aws-builder-center.md](#sec-163).This is our third article on that platform and the second under our own byline. The news is notthat we wrote something. It is that the token layer is documented as engineering, on AWS, in a@@ -25424,7 +25440,7 @@ paper, at the cost of narrowing a broad article to one of its sections. Pick one## Follow-ups this unlocksTwo sections were cut from the article for the platform's 40,000-character limit, and both are-whole in [aws-builder-center-agent-commerce-spine.md](#sec-153):+whole in [aws-builder-center-agent-commerce-spine.md](#sec-154):the agent-vitals readiness check, and the fabrication gate that stands between a prompt and amanufactured object. Each is its own article and its own announcement beat. Do not spend them here.@@ -25654,12 +25670,12 @@ every one carrying a `tx_sig`):| Part of the claim | Where it is real ||---|---|-| Every prop was bought by an autonomous agent | The only writer of `forge_autonomous_props` is `persistProp` in [`api/_lib/x402/pipelines/forge-content.js`](../api/_lib/x402/pipelines/forge-content.js), called by two autonomous buyers: the `forge` pipeline in the autonomous x402 loop ("Each call is a real on-chain USDC payment from the seed wallet via the shared payX402 client"), and since 2026-09-22 the [fresh-wallet workers](#sec-855) lane, which pays the same standard-tier `/api/x402/forge` call from a brand-new wallet per job (the feed marks those `payer_kind: "fresh"` and the card adds a "fresh wallet" badge). The feed, [`api/forged.js`](../api/forged.js), reads only that table and states "There are no synthetic entries". The live page says "Every asset here was purchased by one of the platform's autonomous agents". |-| $0.15 in USDC per prop | The pipeline pays `POST /api/x402/forge` at the standard tier ([`docs/forged.md`](#sec-314), priced in [`api/_lib/forge-tiers.js`](../api/_lib/forge-tiers.js)). `GET /api/forged?limit=100` on 2026-09-17 returned 100 of 100 props at `price_usdc: 0.15`, tier `standard`. Each card renders it as "$0.15 USDC" ([`src/forged-gallery.js`](../src/forged-gallery.js), `formatUsdc`). |+| Every prop was bought by an autonomous agent | The only writer of `forge_autonomous_props` is `persistProp` in [`api/_lib/x402/pipelines/forge-content.js`](../api/_lib/x402/pipelines/forge-content.js), called by two autonomous buyers: the `forge` pipeline in the autonomous x402 loop ("Each call is a real on-chain USDC payment from the seed wallet via the shared payX402 client"), and since 2026-09-22 the [fresh-wallet workers](#sec-870) lane, which pays the same standard-tier `/api/x402/forge` call from a brand-new wallet per job (the feed marks those `payer_kind: "fresh"` and the card adds a "fresh wallet" badge). The feed, [`api/forged.js`](../api/forged.js), reads only that table and states "There are no synthetic entries". The live page says "Every asset here was purchased by one of the platform's autonomous agents". |+| $0.15 in USDC per prop | The pipeline pays `POST /api/x402/forge` at the standard tier ([`docs/forged.md`](#sec-317), priced in [`api/_lib/forge-tiers.js`](../api/_lib/forge-tiers.js)). `GET /api/forged?limit=100` on 2026-09-17 returned 100 of 100 props at `price_usdc: 0.15`, tier `standard`. Each card renders it as "$0.15 USDC" ([`src/forged-gallery.js`](../src/forged-gallery.js), `formatUsdc`). || Over x402 | `payX402` in [`api/_lib/x402/pay.js`](../api/_lib/x402/pay.js) selects the `solana` accept entry and settles through the self-hosted facilitator. The page hero: "real USDC over the x402 payment protocol". || The card links the Solana settlement | `toProp()` in [`api/forged.js`](../api/forged.js) builds `explorer_url` from the stored `tx_sig`; the card renders it as a `receipt` link titled "View the settlement transaction on Solscan". All 100 props returned carried a `tx_sig`. The newest one (`28gNXzZjZSAQ...`) was checked with `getSignatureStatuses` against Solana mainnet: `finalized`, `err: null`. |-Full mechanism: [docs/forged.md](#sec-314). Live totals from the same feed the hero reads: 129+Full mechanism: [docs/forged.md](#sec-317). Live totals from the same feed the hero reads: 129renderable props and $21.15 USDC settled on 2026-09-17; 276 renderable props and $46.50 settledon 2026-10-09, across 8 prop families.@@ -25894,12 +25910,12 @@ Every part of that is verifiable in the tree, which is the only reason it can be|---|---|| Prompt or selfie to a textured 3D body | `POST /api/avatars/reconstruct`, the same pipeline behind `/create/prompt` and `/create/selfie` || Rigged, not a T-posed mesh | The pipeline chains an auto-rig job and only surfaces the avatar once it can be animated |-| Custodial Solana wallet and custodial EVM wallet | `POST /api/agents/:id/wallet/provision`, real custodial keys ([Agent Wallets](#sec-077), [Custody](#sec-232)) |+| Custodial Solana wallet and custodial EVM wallet | `POST /api/agents/:id/wallet/provision`, real custodial keys ([Agent Wallets](#sec-077), [Custody](#sec-233)) || Synthesized persona and voice | `POST /api/persona/extract` through the shared free-providers-first LLM chain; voices from `/api/tts/voices` |-| Optional on-chain identity | A real [ERC-8004](#sec-263) record returning a real transaction hash, defaulting to Base |+| Optional on-chain identity | A real [ERC-8004](#sec-266) record returning a real transaction hash, defaulting to Base || Under a minute of active work | The flow is a state machine over those production endpoints, with a progress bar driven by real job state |-Full mechanism: [docs/genesis.md](#sec-321).+Full mechanism: [docs/genesis.md](#sec-324).## Media@@ -26212,7 +26228,7 @@ The queue item is `materialize` in [`data/x-content/queue.json`](../data/x-conte· **Announced externally:** neverWritten against [the announcement voice](#sec-102). This is the beat the-[stream plan](#sec-461) does not have: its sequence runs T-14 application,+[stream plan](#sec-466) does not have: its sequence runs T-14 application,T-7 ask, T-1 reminder, T-0 live, T+1 replay, all anchored to a stream date that is not booked yet.Approval is its own news and it is public the moment the label lands, so this post fills the gapbetween the application post and the date post without spending either.@@ -26281,6 +26297,60 @@ taken. Then the plan's T-7, T-1, T-0 and T+1 posts run as written.<a id="sec-120"></a>+> **Source:** `docs/announcements/openai-partner-benefits.md` · [↑ table of contents](#table-of-contents)++# Announcement pack: OpenAI Partner Network 2026 program year++**Surface:** [`/openai`](https://three.ws/openai) · **Stage:** drafted, awaiting approval to post+· **Announced externally:** never · **Internal record:** [openai-partner-benefits-2026.md](#sec-485)++Written against [the announcement voice](#sec-102). Partner news, so it is long, tags+no one, and links the surface once.++## The claim, and where it is checked++> The OpenAI Partner Network opened our 2026 program year as an OpenAI Select Partner, with a+> dedicated API organization and a ChatGPT workspace with Codex credits, for the full program year.++| Part of the claim | Where it is real |+|---|---|+| OpenAI Select Partner | Partner tier "Select" in the provisioning notice of 2026-10-11; page [`/openai`](https://three.ws/openai) |+| Program year through June 2027 | Notice: 2026-07-01 to 2027-06-30 |+| Dedicated API organization and ChatGPT workspace with Codex credits | Notice: separate API organization and ChatGPT workspace, with API and ChatGPT/Codex credits. Amounts are left out on purpose. |+| Testing and validating the 3D Studio connector, customer proofs of concept, demos | The five permitted activities in the notice; connector is live ([mcp-studio.md](#sec-418)) |++## Posting rules specific to this pack++- Say "OpenAI Select Partner" exactly. Never "endorsed by", "official OpenAI", or a claim of an+ OpenAI-built product. three.ws is an independent member of the network.+- Do not state credit amounts, the organization ID or the workspace ID.+- Do not say the credits power three.ws production. They are for approved partner activities only.+- Attach the existing card `social-card-announcement.png` (see+ [social copy](../marketing/openai-select-partner/social-copy.md)), with alt text:+ "three.ws, OpenAI Select Partner, OpenAI Partner Network."+- Tagging @OpenAI is true but turns this into a person-approved post; leave it off unless the owner+ wants it.++## Community variant++Same facts, friendlier opening, for the Discord and Telegram communities:++> Good news for builders: three.ws has started its 2026 program year in the OpenAI Partner Network+> as a Select Partner. That brings a dedicated API organization and a ChatGPT workspace with Codex+> credits, valid for the full program year. We will use them to keep the free 3D Studio connector sharp in+> ChatGPT, build proofs of concept with customers, and demo embodied 3D agents live. Try the+> connector with no key and no account: three.ws/openai++## Ship++```bash+node scripts/post-tweet.mjs --file docs/announcements/openai-partner-benefits.post.txt --dry-run+```++---++<a id="sec-121"></a>+> **Source:** `docs/announcements/product-demo.md` · [↑ table of contents](#table-of-contents)# Announcement pack: The product demo film@@ -26313,7 +26383,7 @@ which the recorder writes at the end of the run:| The route is generated | Stops come from [`public/tour/curriculum.json`](../public/tour/curriculum.json), which `scripts/build-tour.mjs` generates from `data/pages.json`. A page that ships tomorrow is in the next recording with nobody editing a script || Six chapters | Main, Build, Crypto, Labs, Agent Tools, Learn, one mp4 each, listed in the manifest with per-chapter durations |-Full mechanism: [docs/product-demo.md](#sec-507).+Full mechanism: [docs/product-demo.md](#sec-514).## Media@@ -26460,7 +26530,7 @@ channel by hand; the changelog cron must not be used for it, because this is not----<a id="sec-121"></a>+<a id="sec-122"></a>> **Source:** `docs/announcements/text-to-3d.md` · [↑ table of contents](#table-of-contents)@@ -26477,7 +26547,7 @@ The same call is documented for anyone to repeat in `.agents/skills/generate-3d-----<a id="sec-122"></a>+<a id="sec-123"></a>> **Source:** `docs/announcements/three-token-mcp.md` · [↑ table of contents](#table-of-contents)@@ -26510,7 +26580,7 @@ and this is a feature that genuinely touches the token rather than mentioning it| Where the burned tokens go | The burn leg routes to the Solana incinerator (`1nc1nerator11111111111111111111111111111111`). `computeSplit()` sends the rest to the treasury only when the live config has one; `/api/token/config` currently serves `"treasury": null`, so today a burn sends 100% to the incinerator. This is why the post says "burn" and does not promise a treasury split. |Full mechanism: [`packages/three-token-mcp/README.md`](../packages/three-token-mcp/README.md);-install lines for every three.ws server: [docs/mcp.md](#sec-417).+install lines for every three.ws server: [docs/mcp.md](#sec-421).## Media@@ -26614,7 +26684,7 @@ npm run x:content -- run --dry-run --id three-token-mcp----<a id="sec-123"></a>+<a id="sec-124"></a>> **Source:** `docs/announcements/walk.md` · [↑ table of contents](#table-of-contents)@@ -26644,7 +26714,7 @@ Verified by reading the code and the live page on 2026-09-17:| Picked by a query param | `const ENV_PARAM = (params.get('env') || 'studio')` in [`src/walk-embed.js`](../src/walk-embed.js); the live page: "set the avatar and world with query params". || No SDK, no build step | Literal on the live page ("No SDK, no build step."), and true of the snippet: a plain iframe with no script include. |-Related docs: [docs/walk-leaderboard.md](#sec-798) (the distance board the page+Related docs: [docs/walk-leaderboard.md](#sec-810) (the distance board the pageteases), and the `walk-sdk/` package README for the scripted companion.## Media@@ -26733,7 +26803,7 @@ node scripts/post-tweet.mjs --file docs/announcements/walk.post.txt --dry-run----<a id="sec-124"></a>+<a id="sec-125"></a>> **Source:** `docs/api-reference.md` · [↑ table of contents](#table-of-contents)@@ -26743,9 +26813,9 @@ This is the reference for the three.ws HTTP API: every documented endpoint, itsBase URL: `https://three.ws/api`-> For the in-browser JavaScript API (the `<agent-3d>` element, `Viewer`, `Runtime`, `SceneController`, skills, memory), see [js-api.md](#sec-390) and [web-component.md](#sec-799). For the high-level npm SDK, see [sdk.md](#sec-626).+> For the in-browser JavaScript API (the `<agent-3d>` element, `Viewer`, `Runtime`, `SceneController`, skills, memory), see [js-api.md](#sec-394) and [web-component.md](#sec-811). For the high-level npm SDK, see [sdk.md](#sec-633).-The full machine-readable schema lives at [`https://three.ws/.well-known/openapi.yaml`](https://three.ws/.well-known/openapi.yaml). x402 paid endpoints are listed at [`/.well-known/x402.json`](https://three.ws/.well-known/x402.json) and the MCP endpoint is at [`/api/mcp`](https://three.ws/api/mcp).+The full machine-readable schema lives at [`https://three.ws/.well-known/openapi.yaml`](https://three.ws/.well-known/openapi.yaml), with a ready-to-import Postman collection generated from the same spec at [`https://three.ws/.well-known/postman-collection.json`](https://three.ws/.well-known/postman-collection.json) (`npm run build:postman-collection` regenerates it, `npm run check:postman-collection` fails the gate when it drifts from the spec). x402 paid endpoints are listed at [`/.well-known/x402.json`](https://three.ws/.well-known/x402.json) and the MCP endpoint is at [`/api/mcp`](https://three.ws/api/mcp).---@@ -26809,7 +26879,7 @@ If the body also has `"reason": "rate_limiter_unavailable"`, you did not hit a q### Developer plans and quotas-Every call to the versioned API (`/api/v1/…`) is also held to the caller's developer plan: a monthly call quota, a burst ceiling and a concurrency ceiling, all enforced in the shared gateway rather than merely recorded. The four plans (Free, Builder, Scale, Enterprise) are defined once in `api/_lib/dev-plans/config.js`; `GET /api/v1/dev-plans` publishes that table, and the [/developers](https://three.ws/developers) page and the dashboard render it, so no document carries a typed number. The full guide, including upgrades, proration and payment, is [Developer plans](#sec-243).+Every call to the versioned API (`/api/v1/…`) is also held to the caller's developer plan: a monthly call quota, a burst ceiling and a concurrency ceiling, all enforced in the shared gateway rather than merely recorded. The four plans (Free, Builder, Scale, Enterprise) are defined once in `api/_lib/dev-plans/config.js`; `GET /api/v1/dev-plans` publishes that table, and the [/developers](https://three.ws/developers) page and the dashboard render it, so no document carries a typed number. The full guide, including upgrades, proration and payment, is [Developer plans](#sec-244).**Headers.** Every `/api/v1` response carries the plan envelope:@@ -26893,7 +26963,7 @@ A completed paid call replayed with the same payment still answers `409 payment_## Solana Transaction Inspection APIAtomic is a public, read-only inspector for legacy, V0, and V1 Solana transactions. It never signs,-simulates, or broadcasts. See the [Atomic guide](#sec-133) for the V1 resource model and sponsor-safety+simulates, or broadcasts. See the [Atomic guide](#sec-134) for the V1 resource model and sponsor-safetyrules.### Read V1 activation status@@ -27902,8 +27972,8 @@ widget in `src/memory-seed.js`.Everything these endpoints read is already public. They are read-only, requestno OAuth from the visitor, and store nothing; the consent-gated seeding flowsthat do write to an agent live at `/api/agents/:id/memory/seed/*` and are-documented in [GitHub](#sec-325), [X](#sec-813)-and [Farcaster](#sec-302) memory seeding.+documented in [GitHub](#sec-328), [X](#sec-826)+and [Farcaster](#sec-305) memory seeding.The three connectors are unauthenticated GETs, rate limited per IP, and cachedat the edge for 5 minutes. A connector that cannot reach its upstream answers@@ -28955,7 +29025,7 @@ x-forge-client: <stable browser id> # optional — resolves per-card `voted``sort=fresh` (default, newest-first) or `sort=top` (most-voted); `window=week`narrows Top to the current Forge-Off week (Monday→Monday UTC). Full feature-docs: [docs/forge-off.md](#sec-310).+docs: [docs/forge-off.md](#sec-313).### Model detail page read: `GET /api/forge-creation`@@ -29175,7 +29245,7 @@ GET /api/fresh-workers?limit=100 → up to 100 wallets```Public statistics for the lane that mints a brand-new Solana wallet for every-purchase (docs: [x402-fresh-workers.md](#sec-855)): wallets+purchase (docs: [x402-fresh-workers.md](#sec-870)): walletsminted, paid and closed over the last 24 hours and all time, what they bought,the USDC that recirculated, the SOL actually burned as network fees, the ATArent that round-tripped, and each recent wallet's funding, payment and sweep@@ -29203,7 +29273,7 @@ transactions on Solscan. Free, cached ~15s, rate-limited per IP.Turn any 3D model into a real, physical object: analysis, preparation, anitemized price, checkout in USDC on Solana, tracked fulfillment, and acertificate of authenticity attested on-chain. Product guide:-[Materialize](#sec-409). Wire contracts:+[Materialize](#sec-413). Wire contracts:[specs/PRINT_PIPELINE.md](../specs/PRINT_PIPELINE.md).Analysis and quoting are **free and keyless**. Only checkout costs money.@@ -29441,7 +29511,7 @@ the Avatar Studio re-skin idea (`src/avatar-studio-colorpicker.js`,preset live in the browser (see [Restyle Studio](https://three.ws/restyle)), askan AI for a restyle from a plain-language instruction, or fan one preset out intoN reproducible colorway variants. Free and hosted — rate-limited, not x402 — the-same implementation the paid `restyle_material` [MCP tool](#sec-415) calls as+same implementation the paid `restyle_material` [MCP tool](#sec-419) calls asa thin client, so the free web page and the paid agent tool never drift.Every mesh edit is **non-destructive**: geometry and UVs are never touched (only@@ -29844,7 +29914,7 @@ sample rate, whether the lane is configured).Read American Sign Language fingerspelling from a webcam. No API key, no account,no payment: rate-limited per IP. This is the input half of the platform's signing-loop (the output half, avatars that sign, is [docs/sign-language.md](#sec-641)).+loop (the output half, avatars that sign, is [docs/sign-language.md](#sec-649)).**Video never reaches the platform.** The caller extracts MediaPipe Holisticlandmarks in the browser and posts coordinates only. `src/sign-input.js` ships a@@ -30530,7 +30600,7 @@ The REST face of the Solana trading tools: research, swap comparison andexecution, and arbitrage. Each route is one entry in the tool registry(`api/_lib/trading-tools/registry.js`) that also serves the `threews-agent` MCPserver, so the input schema, the guards and the refusal codes are the same on-both surfaces. Full guide with every field explained: [Solana trading tools](#sec-696).+both surfaces. Full guide with every field explained: [Solana trading tools](#sec-704).Responses use the versioned API envelope (`{ "data": …, "meta": { "requestId": … } }`).GET routes read the query string (arrays as a comma list); POST routes read a@@ -30635,7 +30705,7 @@ progress, the three.ws launch directory, and whale activity. Each endpoint is athin wrapper: search shares its engine with the site's command-palette search(`/api/pump/search`); trending, curve, and whales share their engines with thefree Crypto Data API's pump.fun endpoints (`/api/crypto/trending`, `/bonding`,-`/whales` — see [docs/crypto-api.md](#sec-231)); launches shares its query+`/whales` — see [docs/crypto-api.md](#sec-232)); launches shares its querywith the [/launches](https://three.ws/launches) page. No fork of any upstreamlogic lives here — every /api/v1/pump/\* route imports the same shared moduleits sibling already uses.@@ -30704,7 +30774,7 @@ curl -s 'https://three.ws/api/v1/pump/search?q=three.ws'Momentum-ranked "what's hot right now" — fuses windowed volume, buy pressure, avolume-spike signal, and price change across pump.fun, DexScreener, and(best-effort) GMGN smart money into one 0–100 score. Same engine as-[`GET /api/crypto/trending`](#sec-231)+[`GET /api/crypto/trending`](#sec-232)(`api/_lib/crypto-trending.js` `composeTrending`), capped slimmer here (25 vs50) to keep this door fast.@@ -30769,7 +30839,7 @@ curl -s 'https://three.ws/api/v1/pump/trending?window=1h&limit=10'Bonding-curve / graduation status for one pump.fun mint — % to graduation, SOLin the curve, tokens remaining, market cap, and whether it has already migratedto an AMM (Raydium / PumpSwap). Same engine as-[`GET /api/crypto/bonding`](#sec-231)+[`GET /api/crypto/bonding`](#sec-232)(`api/_lib/pump-bonding.js` `getBondingStatus`).```@@ -30905,7 +30975,7 @@ Quote a launch, fund it from the agent wallet, confirm it in the approvals inbox| `POST /api/pump/launch-intents/:id/confirm` | session only | Ask the owner to approve the launch. || `POST /api/pump/launch-intents/:id/dry-run` | session or bearer | Simulate the launch without sending it. |-Full flow, errors and configuration: [launch-intents.md](#sec-394).+Full flow, errors and configuration: [launch-intents.md](#sec-398).### Whales@@ -30915,7 +30985,7 @@ oracle that otherwise sits behind the paid `GET /api/x402/pump-agent-audit`(`"mode":"whale_activity"`) — the invented "bullish/bearish signal +confidence" the paid oracle scores is deliberately dropped here, and the samescan engine backs the free-[`GET /api/crypto/whales`](#sec-231)+[`GET /api/crypto/whales`](#sec-232)(`api/_lib/pump-whale-scan.js` `scanTokenWhales` / `scanMarketWhales`).```@@ -31070,7 +31140,7 @@ curl -s 'https://three.ws/api/pipeline?network=devnet' | jq '.stages.recorder'Strategy Objects are validated trade rule sets an agent can equip (entry filter,research gates, sizing with a price-impact cap, exits, risk caps, and an`ask`/`auto` mode). Full guide, schema, and examples:-[docs/strategy-objects.md](#sec-667).+[docs/strategy-objects.md](#sec-675).### Live match preview@@ -31216,7 +31286,7 @@ cap, safety score, creator history, risk flags, the `matched` filters and a**Delivery.** With `deliver_in_app` (the default) an alert reaches the ownerthrough the platform notification fan-out as a `pump_alert`: the bell, Web Push,the iOS app, and every Telegram or Discord chat paired for notifications, each-gated by the `alerts` preference category ([notifications](#sec-442)).+gated by the `alerts` preference category ([notifications](#sec-446)).A `webhook_url` gets a signed Standard Webhooks POST, and a `telegram_chat` thatis not already a paired chat gets a direct message. Each attempt is recorded perchannel and returned as `recent_deliveries` on the rule.@@ -31227,7 +31297,7 @@ channel and returned as `recent_deliveries` on the rule.A trader's daily on-chain score attestation (`threews.tradescore.v1`), served as aportable credential and a database-free verifier. Full guide:-[docs/trader-passport.md](#sec-688).+[docs/trader-passport.md](#sec-696).### Read a passport@@ -31281,7 +31351,7 @@ The data behind the live trade rooms (`/trade-rooms`). Every number comes fromthe sniper ledger (`agent_sniper_positions`), the same rows the leaderboard and`/trader/:id` read. Public, IP rate-limited, and gated like`/api/sniper/trader`: a private or deleted agent has no room. Full guide:-[docs/trade-rooms.md](#sec-684).+[docs/trade-rooms.md](#sec-692).### List rooms@@ -31350,7 +31420,7 @@ Errors before the stream opens: `400 invalid_agent`, `404 not_found`,## Authentication API-Authentication is covered in detail in the [Authentication documentation](#sec-138). Quick reference:+Authentication is covered in detail in the [Authentication documentation](#sec-139). Quick reference:| Endpoint | Method | Description || --------------------------- | -------- | ------------------------------------- |@@ -31709,7 +31779,7 @@ The cursor encodes the full keyset tuple (registration timestamp, chain ID, agen## Social & Community API-The endpoints behind the platform's social layer: the activity feed, the follow graph, notifications, the unified leaderboard, creator portfolios, and cross-entity search. Overview and how the pieces interconnect: [The social layer](#sec-654).+The endpoints behind the platform's social layer: the activity feed, the follow graph, notifications, the unified leaderboard, creator portfolios, and cross-entity search. Overview and how the pieces interconnect: [The social layer](#sec-662).### Activity feed@@ -31748,7 +31818,7 @@ Reverse-chronological creation events (avatars, agents, coins, forged models, saItems of `kind: "follow"` also carry a `target` shaped like `actor`. `actor.username` is `null` for creations made while signed out.-Not the same endpoint as `GET /api/feed`, the public Money Pulse ticker ([Money Feed](#sec-433)).+Not the same endpoint as `GET /api/feed`, the public Money Pulse ticker ([Money Feed](#sec-437)).---@@ -31922,7 +31992,7 @@ POST /api/push/device { token, platform: "ios", app_version?, previous? }DELETE /api/push/device { token }```-Where a notification's `push` channel is delivered. Session and CSRF token required; 30 registrations per user per hour. A browser registers the object `pushManager.subscribe()` returns. The [iOS app](#sec-385) has no service worker, so it registers its APNs device token instead (64 or more hex characters, case-insensitive). Both are unique per device and follow the latest signed-in owner. Every push-enabled notification fans out to both, so the preference matrix above governs a phone and a browser the same way; the iOS delivery also sets the app icon's badge to the recipient's unread count.+Where a notification's `push` channel is delivered. Session and CSRF token required; 30 registrations per user per hour. A browser registers the object `pushManager.subscribe()` returns. The [iOS app](#sec-389) has no service worker, so it registers its APNs device token instead (64 or more hex characters, case-insensitive). Both are unique per device and follow the latest signed-in owner. Every push-enabled notification fans out to both, so the preference matrix above governs a phone and a browser the same way; the iOS delivery also sets the app icon's badge to the recipient's unread count.`previous` marks a silent refresh (the app re-sending its token on launch). It succeeds only if `previous` is already registered to the caller, and answers `409 not_owner` otherwise, so a phone never enrols for whichever account happens to be signed in now. `GET /api/config` reports `nativePush.ios: true` once APNs is configured on the server (`APNS_KEY_ID`, `APNS_AUTH_KEY`, and `APNS_TEAM_ID` or `APPLE_TEAM_ID`).@@ -31939,7 +32009,7 @@ POST /api/approvals/policies { venues, max_usd, agent_id?, team_id?, expiresDELETE /api/approvals/policies?id=<uuid>```-The owner's inbox for actions an agent paused on because a spend rule is set to "Ask me". Reads take a session or bearer; every decision and rule change needs a session plus CSRF, so an agent credential can never approve its own request. Approve must carry the `payload_hash` of the action shown: a mismatch is `409 payload_mismatch`, a deep link that no longer matches is `409 link_mismatch`, a passed deadline is `410 expired`, and nothing runs in any of those cases. A repeat approve returns the current state with `idempotent: true` and never executes twice. Auto-approve rules name venues (`jupiter`, `wallet_transfer`) and a per-action cap of at most $1,000; first transfers to a new address and unpriced actions always ask. Full guide: [approvals.md](#sec-126).+The owner's inbox for actions an agent paused on because a spend rule is set to "Ask me". Reads take a session or bearer; every decision and rule change needs a session plus CSRF, so an agent credential can never approve its own request. Approve must carry the `payload_hash` of the action shown: a mismatch is `409 payload_mismatch`, a deep link that no longer matches is `409 link_mismatch`, a passed deadline is `410 expired`, and nothing runs in any of those cases. A repeat approve returns the current state with `idempotent: true` and never executes twice. Auto-approve rules name venues (`jupiter`, `wallet_transfer`) and a per-action cap of at most $1,000; first transfers to a new address and unpriced actions always ask. Full guide: [approvals.md](#sec-127).### Token ceilings, spend and the free-tier choices@@ -31952,11 +32022,11 @@ POST /api/agents/:id/token-budget/extend { window?, extra_tokens? }GET /api/me/spend?days=30&agent=<uuid>```-Per-agent hourly, daily and per-run token ceilings next to the dollar budget (`PATCH /api/agents/:id` with `inferenceBudget: { daily, monthly }`). Both are enforced before the model call on every metered surface; the token gate reserves the call's estimate in each capped window with one conditional upsert, so two calls racing for the last token admit exactly one. A refused call is `429 token_budget_exhausted` (the call that crossed the line) or `429 token_budget_paused` (every call after it) with `window`, `limit_tokens`, `ceiling_tokens`, `used_tokens`, `resets_at`, `retry_after_seconds`, `approval_id` and a `recover` block naming the resume, extend-once and raise calls. Hitting a ceiling stops the agent and its autopilot, sends `token_budget_paused`, and opens one extend-once approval in the [inbox](#sec-126) (venue `token_budget`, never auto-approved). `resume` is `409 still_capped` while the window is still full; `extend` opens and approves the extension in one call and is `409 already_extended` the second time for the same window (default size: half the cap, at least 1,000 tokens). Every cap raises `spend_cap_alert` once per window at 50 and 80 percent. Owner only: a session, or a bearer with `wallet:read` (or `profile`) to read and `wallet:write` to change, resume or extend.+Per-agent hourly, daily and per-run token ceilings next to the dollar budget (`PATCH /api/agents/:id` with `inferenceBudget: { daily, monthly }`). Both are enforced before the model call on every metered surface; the token gate reserves the call's estimate in each capped window with one conditional upsert, so two calls racing for the last token admit exactly one. A refused call is `429 token_budget_exhausted` (the call that crossed the line) or `429 token_budget_paused` (every call after it) with `window`, `limit_tokens`, `ceiling_tokens`, `used_tokens`, `resets_at`, `retry_after_seconds`, `approval_id` and a `recover` block naming the resume, extend-once and raise calls. Hitting a ceiling stops the agent and its autopilot, sends `token_budget_paused`, and opens one extend-once approval in the [inbox](#sec-127) (venue `token_budget`, never auto-approved). `resume` is `409 still_capped` while the window is still full; `extend` opens and approves the extension in one call and is `409 already_extended` the second time for the same window (default size: half the cap, at least 1,000 tokens). Every cap raises `spend_cap_alert` once per window at 50 and 80 percent. Owner only: a session, or a bearer with `wallet:read` (or `profile`) to read and `wallet:write` to change, resume or extend.`GET /api/me/spend` is the read model behind [/spend](https://three.ws/spend): balance, month-to-date with `projected_usd` and `projected_from_week_usd`, a card per agent (dollar windows, token windows, pause), `by_day`, `by_model`, `by_tool`, and `alerts` at 50, 80 and 100 percent of any cap, from the same latches the notifications use. `days` is 1 to 90; bearer scopes `inference`, `wallet:read`, `wallet:write` or `profile`.-When a free-model allowance is used up, `/api/brain/chat`, `POST /api/agents/:id/copilot`, `POST /api/v1/agents/:id/messages` and `/api/v1` answer `429 free_tier_exhausted` with `Retry-After` and a body carrying `reset_at`, `retry_after_seconds` and `choices`: `wait`, `top_up` (the `GET /api/credits` catalog and the `POST /api/credits/deposit` body), `bring_your_own_key` (`PATCH /api/user/provider-keys`), and, on the surfaces that can honor it, `paid_fallback`: resend the same request with `body_patch` (`{ "paid_fallback": true }`) merged in and it bills credits instead of the free tier, after the credit gate (`402 insufficient_credits` on an empty balance). Full guide: [inference-billing.md](#sec-381).+When a free-model allowance is used up, `/api/brain/chat`, `POST /api/agents/:id/copilot`, `POST /api/v1/agents/:id/messages` and `/api/v1` answer `429 free_tier_exhausted` with `Retry-After` and a body carrying `reset_at`, `retry_after_seconds` and `choices`: `wait`, `top_up` (the `GET /api/credits` catalog and the `POST /api/credits/deposit` body), `bring_your_own_key` (`PATCH /api/user/provider-keys`), and, on the surfaces that can honor it, `paid_fallback`: resend the same request with `body_patch` (`{ "paid_fallback": true }`) merged in and it bills credits instead of the free tier, after the credit gate (`402 insufficient_credits` on an empty balance). Full guide: [inference-billing.md](#sec-385).### Agent mail@@ -32217,7 +32287,7 @@ GET answers `405` with `allow: POST, DELETE`.`render_avatar` enforces the agent's embed policy (allowed origins, allowed surfaces). Model URLs must be HTTPS — SSRF protections block private IP ranges.-This table is the core subset. The server registers many more tools (minting, gated embeds, memory, oracle and pump.fun intel, trader analytics, crypto data). Call `tools/list`, or see the [MCP documentation](#sec-417) and the [MCP Tools Catalog](#sec-415).+This table is the core subset. The server registers many more tools (minting, gated embeds, memory, oracle and pump.fun intel, trader analytics, crypto data). Call `tools/list`, or see the [MCP documentation](#sec-421) and the [MCP Tools Catalog](#sec-419).**Example JSON-RPC request**@@ -32385,7 +32455,7 @@ Both header names are read case-insensitively and both receipt names are emitted| `POST /api/mcp-3d` | MCP (Streamable HTTP) | Base + X Layer (+ Solana when configured) || `POST /api/okx/3d/<service>` | A2MCP (decomposed 3D studio) | X Layer first, then Solana/Base |-The full seller-side wire contract — challenge fields, verify→work→settle order, the `PAYMENT-SIGNATURE` payload shape, and the settlement receipt — is pinned in [`specs/okx-agent-payments.md`](../specs/okx-agent-payments.md). The per-service catalog and runnable curls are in [`docs/okx-marketplace.md`](#sec-456).+The full seller-side wire contract — challenge fields, verify→work→settle order, the `PAYMENT-SIGNATURE` payload shape, and the settlement receipt — is pinned in [`specs/okx-agent-payments.md`](../specs/okx-agent-payments.md). The per-service catalog and runnable curls are in [`docs/okx-marketplace.md`](#sec-460).---@@ -32407,7 +32477,7 @@ The buyer-side counterpart to the x402 endpoints above. Everything so far assumeYou fund a budget from your [credits](payment-sessions.md#prepaid-credits), set the policy, and receive a bearer token. The agent presents that token to `/api/pay/execute`; the platform's own wallet signs the on-chain transfer. A stolen token buys at most the remaining budget, only at hosts you approved, only until the session expires.-Conceptual guide: [Payment sessions](#sec-488). Step-by-step walkthrough: [Give an agent a spending envelope](#sec-706). Enforcement source: [`api/_lib/pay/spend-governor.js`](https://github.com/nirholas/three.ws/blob/main/api/_lib/pay/spend-governor.js).+Conceptual guide: [Payment sessions](#sec-495). Step-by-step walkthrough: [Give an agent a spending envelope](#sec-714). Enforcement source: [`api/_lib/pay/spend-governor.js`](https://github.com/nirholas/three.ws/blob/main/api/_lib/pay/spend-governor.js).### Authentication@@ -32737,7 +32807,7 @@ Public, unauthenticated, CORS-open proxies over CoinGecko (plus a newsaggregator) that power the [/coins](https://three.ws/coins) markets index andthe `/coin/:id` detail pages. Responses are CDN-cached (30–300 s), so pollingfaster than the cache window returns the same payload. See-[docs/coin-pages.md](#sec-194) for the product surface.+[docs/coin-pages.md](#sec-195) for the product surface.### Coin detail@@ -32867,7 +32937,7 @@ nothing is ever invented. Keyless, CORS-open and cached 60s in-process + 5min atthe CDN, because partner pages call it from the browser.This is what lets `/coin3d` be addressed by pair as well as by mint. See-[Token in 3D, as an embed](#sec-196).+[Token in 3D, as an embed](#sec-197).---@@ -32913,7 +32983,7 @@ must be a valid Solana or EVM address (`400 bad_token` otherwise). Aggregateonly: no IP, session or account is stored or returned. Keyless, CORS-open,cached 60s + 5min at the CDN. The figures above show the shape, not live values.Rendered on [/dextools](https://three.ws/dextools); see-[DEXTools integration](#sec-246).+[DEXTools integration](#sec-247).---@@ -33416,7 +33486,7 @@ fetched_at }`.`paragraphs[]` is a bounded lead excerpt, not the article body: capped to 2paragraphs / 400 characters by `excerptParagraphs()` in[api/_lib/news-rights.js](../api/_lib/news-rights.js), the single choke point-every response passes through (see [docs/news-rights.md](#sec-441)).+every response passes through (see [docs/news-rights.md](#sec-445)).`excerpt_truncated` is `true` whenever the source ran longer than the quotedexcerpt; `full_text_url` is where to send the reader for the rest. This is ahard limit for every publisher, not a per-source policy — a story removed at a@@ -33704,7 +33774,7 @@ wire format); pay in USDC and the identical upstream call runs.## Crawl API-The API behind [/crawl](https://three.ws/crawl): agents reading the open web in real browsers, watched live, with every page filed in an open corpus. The public reads need **no authentication, no API key, no payment**, and share a limit of 240 requests per minute per IP (frames have their own, wider one). Sending your own agent out needs a signed-in session and a CSRF token. Product guide: [crawl.md](#sec-227).+The API behind [/crawl](https://three.ws/crawl): agents reading the open web in real browsers, watched live, with every page filed in an open corpus. The public reads need **no authentication, no API key, no payment**, and share a limit of 240 requests per minute per IP (frames have their own, wider one). Sending your own agent out needs a signed-in session and a CSRF token. Product guide: [crawl.md](#sec-228).### Corpus@@ -34198,7 +34268,7 @@ POST /api/wars?action=leave take a community out of the queuePOST /api/wars?action=report game-server only, HMAC-signed battle result```-Coin Wars is community-vs-community combat: two coin communities meet in one arena, the side that reaches the kill cap first wins, and an Elo ladder is recomputed from the battle ledger. This endpoint is what the war portal in every `/play` world reads and what the arena at [`/play/war`](https://three.ws/play/war) queues through. The reads are open and CORS-enabled; the report write is signed. Full subsystem doc: [Coin Wars](#sec-195).+Coin Wars is community-vs-community combat: two coin communities meet in one arena, the side that reaches the kill cap first wins, and an Elo ladder is recomputed from the battle ledger. This endpoint is what the war portal in every `/play` world reads and what the arena at [`/play/war`](https://three.ws/play/war) queues through. The reads are open and CORS-enabled; the report write is signed. Full subsystem doc: [Coin Wars](#sec-196).Standings are **not** computed here. `multiplayer/src/war-standings.js` folds the `clash_battles` ledger, and it is the same module the arena's league uses, so a rating in the world and a rating in the API can never disagree.@@ -34433,7 +34503,7 @@ page strip (on-chain agents, attestations, forge models).## Skill Import API-Install `SKILL.md` skills from public GitHub repositories and registry manifests: browse, scan, approve, update with a diff, fork and publish. The model behind it (pinning, licence policy, scanner rules, the spend gate for gated skills) is in [Skill import](#sec-647); the manifest format is [specs/SKILL_REGISTRY_MANIFEST.md](../specs/SKILL_REGISTRY_MANIFEST.md).+Install `SKILL.md` skills from public GitHub repositories and registry manifests: browse, scan, approve, update with a diff, fork and publish. The model behind it (pinning, licence policy, scanner rules, the spend gate for gated skills) is in [Skill import](#sec-655); the manifest format is [specs/SKILL_REGISTRY_MANIFEST.md](../specs/SKILL_REGISTRY_MANIFEST.md).Base path `/api/skill-imports`. Owner routes accept a session cookie or `Authorization: Bearer <api key>` (`agents:read` for GET, `agents:write` otherwise); cookie writes also need the CSRF header. Responses wrap results in `{ "data": ... }`; errors are `{ "error": code, "error_description": message }`.@@ -35979,7 +36049,7 @@ curl -X POST https://three.ws/api/seeker/verify \## Herald API: deliver a message in person-The rail behind [@three-ws/herald](#sec-338). Anything that can make an HTTPS+The rail behind [@three-ws/herald](#sec-342). Anything that can make an HTTPSrequest posts a line here, and the browser tab the caller has open says it outloud through their 3D companion.@@ -36071,7 +36141,7 @@ data: {"id":"6a29...","text":"Deploy is green","importance":80,"tone":"alert"}## Glance API-One agent reduced to what fits in an operating-system widget slot: name, avatar, one live number (moves in the last 24 hours), and a link back. Powers the Windows 11 widget, the Android home screen widget, the macOS and iOS WidgetKit widget, README badges and the `<agent-glance>` element. Spec: [specs/GLANCE_CARD.md](../specs/GLANCE_CARD.md). Guide: [glance.md](#sec-326), [native-widgets.md](#sec-440).+One agent reduced to what fits in an operating-system widget slot: name, avatar, one live number (moves in the last 24 hours), and a link back. Powers the Windows 11 widget, the Android home screen widget, the macOS and iOS WidgetKit widget, README badges and the `<agent-glance>` element. Spec: [specs/GLANCE_CARD.md](../specs/GLANCE_CARD.md). Guide: [glance.md](#sec-329), [native-widgets.md](#sec-444).### Public card@@ -36123,7 +36193,7 @@ GET /api/pump/sentiment-scout?window=60&limit=5&track=1¬es=1&network=mainnetGET /api/pump/sentiment-scout?mint=<mint>```-No auth, CORS-open, IP rate-limited. Returns `{ network, window_minutes, observed, qualified, generated_at, candidates[], reason?, track_record? }`. Each candidate: `{ mint, ticker, momentum_score, score_parts, evidence[{ type, platform?, detail, source, at, checked_against? }], caution, market_check, x, posts[], note, note_model, links, unavailable[] }`. `notes=0` skips the LLM-written read; `track=1` grades past flags against the base rate. Guide: [sentiment-scout.md](#sec-634).+No auth, CORS-open, IP rate-limited. Returns `{ network, window_minutes, observed, qualified, generated_at, candidates[], reason?, track_record? }`. Each candidate: `{ mint, ticker, momentum_score, score_parts, evidence[{ type, platform?, detail, source, at, checked_against? }], caution, market_check, x, posts[], note, note_model, links, unavailable[] }`. `notes=0` skips the LLM-written read; `track=1` grades past flags against the base rate. Guide: [sentiment-scout.md](#sec-641).### Copy Coach@@ -36132,7 +36202,7 @@ GET /api/copy/coach?network=mainnetPOST /api/copy/coach { message, history?, step?, leader_id?, window?, budget_sol?, network? }```-No auth. `GET` returns `{ network, win, leaders[], starter_caps, eligibility_bar, generated_at }`. `POST` returns `{ reply, source: 'llm'|'guide', model, facts_used }`, with its own limit of 30 questions per 10 minutes per IP. A starter copy is created through `POST /api/copy/subscriptions` with `starter: true` and `risk_ack: true`, where the starter caps are enforced. Guide: [copy-coach.md](#sec-224).+No auth. `GET` returns `{ network, win, leaders[], starter_caps, eligibility_bar, generated_at }`. `POST` returns `{ reply, source: 'llm'|'guide', model, facts_used }`, with its own limit of 30 questions per 10 minutes per IP. A starter copy is created through `POST /api/copy/subscriptions` with `starter: true` and `risk_ack: true`, where the starter caps are enforced. Guide: [copy-coach.md](#sec-225).| Error | Status | Meaning || --- | --- | --- |@@ -36159,7 +36229,7 @@ flag still gets the ordinary `409 needs_confirmation`, which is the answer to roEvery failure carries a stable `code` alongside the message: `bad_url`, `auth`, `unreachable`,`needs_confirmation`, `no_mcp`, `call_failed`, `not_connected`. Branch on the code, show the-message. Full walkthrough: [Connect your home](#sec-716).+message. Full walkthrough: [Connect your home](#sec-724).**The physical-action gate applies to every route here.** Locking, closing and arming runimmediately and never prompt. Unlocking, opening a door, gate or garage, and disarming do not run@@ -36748,7 +36818,7 @@ DELETE /api/home/privacyWhat is held about your homes in plain language, the whole of it as JSON, the action-log retentionwindow (`{ homeId, retentionDays, reason }`), and deletion (`{ scope: 'home' | 'all', homeId }`).-Details: [docs/home-privacy.md](#sec-343).+Details: [docs/home-privacy.md](#sec-347).---@@ -36830,7 +36900,7 @@ Probes `database`, `rpc`, `worker` and `wallet` (a real encrypt/decrypt round tr## Destination whitelist-`/api/wallet-whitelist` manages the addresses an agent wallet may send to. New addresses serve a cooldown (default 24h, minimum 1h), adding or approving needs a single-use step-up grant, and machine principals (API keys, OAuth, MCP) can only propose. Full model, action table and runnable example: [Destination whitelist](#sec-242).+`/api/wallet-whitelist` manages the addresses an agent wallet may send to. New addresses serve a cooldown (default 24h, minimum 1h), adding or approving needs a single-use step-up grant, and machine principals (API keys, OAuth, MCP) can only propose. Full model, action table and runnable example: [Destination whitelist](#sec-243).| Method | Path | Purpose ||---|---|---|@@ -36842,7 +36912,7 @@ Probes `database`, `rpc`, `worker` and `wallet` (a real encrypt/decrypt round tr## Specialist teams-A team is four role agents (Researcher, Entry, Trader, Launcher) under one spend policy, sharing a findings board. Concepts, the role table and the trade rule: [docs/teams.md](#sec-674). Page: [/teams](/teams).+A team is four role agents (Researcher, Entry, Trader, Launcher) under one spend policy, sharing a findings board. Concepts, the role table and the trade rule: [docs/teams.md](#sec-682). Page: [/teams](/teams).Auth: the session cookie (plus `x-csrf-token` on writes) or a bearer token. Reads of a public team are open to anyone; everything else needs the owner. Writes share a limit of 20 an hour, specialist runs 60 every 10 minutes (`429 rate_limited`).@@ -36889,7 +36959,7 @@ es.addEventListener('finding', (e) => {## Squad chat-Talk to a specialist team or a solo agent in plain language. The coordinator turns one message into role-tagged plan steps, runs them, and pauses any step that signs, transfers, launches or exceeds the cap as an approval. Concepts, the trade rule and the injection guard: [docs/team-chat.md](#sec-673). Page: [/team-chat](/team-chat).+Talk to a specialist team or a solo agent in plain language. The coordinator turns one message into role-tagged plan steps, runs them, and pauses any step that signs, transfers, launches or exceeds the cap as an approval. Concepts, the trade rule and the injection guard: [docs/team-chat.md](#sec-681). Page: [/team-chat](/team-chat).Auth: the owner's session cookie (plus `x-csrf-token` on writes) or a bearer token. Live mode needs the real-funds agreement (`403 risk_ack_required`) and, for a bearer, a spend scope. Messages share a limit of 40 a minute per account (`429 rate_limited`).@@ -36906,13 +36976,13 @@ Auth: the owner's session cookie (plus `x-csrf-token` on writes) or a bearer tok`:id` is a team id, or an agent id for a solo squad.-**Events.** `{ id, kind, step_id, payload, created_at }` where `kind` is `run`, `memory`, `plan`, `step`, `approval`, `note`, `summary`, `error` or `end`. Step statuses: `queued`, `running`, `needs_approval`, `executing`, `done`, `failed`, `skipped`, `denied`, `expired`. An approval carries `{ action, payload, payload_hash, summary, table, gate_reasons, risk_notes, expires_at, mirrored, inbox_url, handoff_url }`; `gate_reasons` is any of `signs`, `exceeds_cap`, `launches`, `transfers`. Approving must echo `payload_hash`; a changed action is `409 payload_mismatch` and nothing runs. Paper approvals simulate and never sign; live trades sign from the squad wallet and are mirrored into the [approval inbox](#sec-126); launches and transfers hand off to the page where the owner signs.+**Events.** `{ id, kind, step_id, payload, created_at }` where `kind` is `run`, `memory`, `plan`, `step`, `approval`, `note`, `summary`, `error` or `end`. Step statuses: `queued`, `running`, `needs_approval`, `executing`, `done`, `failed`, `skipped`, `denied`, `expired`. An approval carries `{ action, payload, payload_hash, summary, table, gate_reasons, risk_notes, expires_at, mirrored, inbox_url, handoff_url }`; `gate_reasons` is any of `signs`, `exceeds_cap`, `launches`, `transfers`. Approving must echo `payload_hash`; a changed action is `409 payload_mismatch` and nothing runs. Paper approvals simulate and never sign; live trades sign from the squad wallet and are mirrored into the [approval inbox](#sec-127); launches and transfers hand off to the page where the owner signs.---## Agent perps-Perpetual futures for one agent, with USDC collateral from its custodial Solana wallet. Paper mode (the default) fills at live venue prices on a platform ledger; live mode signs from the agent wallet and needs the owner to turn it on. Guards, order types, the kill switch, alerts and the venue contract: [docs/perps.md](#sec-490). Page: [/agent-perps](/agent-perps).+Perpetual futures for one agent, with USDC collateral from its custodial Solana wallet. Paper mode (the default) fills at live venue prices on a platform ledger; live mode signs from the agent wallet and needs the owner to turn it on. Guards, order types, the kill switch, alerts and the venue contract: [docs/perps.md](#sec-497). Page: [/agent-perps](/agent-perps).Auth: market routes are public. Every other route is owner-only: session cookie (plus `x-csrf-token` on writes) or a bearer with `wallet:read` for reads and previews and `wallet:write` for executes and limit changes. Only a signed-in owner may loosen a limit, turn live on or resume after the kill switch (`403 owner_session_required`). All paths are under `/api/v1/agents/:id/perps`, take an optional `venue` (default `phoenix`), and agent routes take `mode` (`paper` or `live`).@@ -36952,7 +37022,7 @@ Webhook events: `invoice.created`, `invoice.paid`, `invoice.underpaid`,## Desktop Campus API: gem miningThe homepage (`/`) boots into a 3D campus in front of the web desktop (see-[Web Desktop](#sec-241)). Its mine is backed by one endpoint. Everything+[Web Desktop](#sec-242)). Its mine is backed by one endpoint. Everythingthat matters is decided on the server: the gem is rolled there with cryptorandomness from a fixed table, and a dig is only accepted when the miner'sprevious dig is old enough.@@ -37038,7 +37108,7 @@ the same cadence, so a client that posts early is refused.## X Mention Bot API-Agents on three.ws can reply to their own @-mentions on X through the same connector tools Grok uses (see [docs/grok.md](#sec-334)). This is the one public, unauthenticated read: an aggregate status for the bot as a whole, with no private data.+Agents on three.ws can reply to their own @-mentions on X through the same connector tools Grok uses (see [docs/grok.md](#sec-338)). This is the one public, unauthenticated read: an aggregate status for the bot as a whole, with no private data.### Bot status@@ -37138,7 +37208,7 @@ Open an issue on [GitHub](https://github.com/nirholas/three.ws/issues) or messag## SDK-For building on the platform from JavaScript, the official npm package is [`@three-ws/sdk`](https://www.npmjs.com/package/@three-ws/sdk). It is not a thin wrapper over every REST route above; it ships the higher-level building blocks: `AgentKit` (chat panel + ERC-8004 registration + `.well-known` manifest generation), `AgentClient` (x402 agent-to-agent paid skill calls), `PermissionsClient` (ERC-7710 delegations), and the Solana identity/attestation helpers. Full docs: [SDK & Library](#sec-626).+For building on the platform from JavaScript, the official npm package is [`@three-ws/sdk`](https://www.npmjs.com/package/@three-ws/sdk). It is not a thin wrapper over every REST route above; it ships the higher-level building blocks: `AgentKit` (chat panel + ERC-8004 registration + `.well-known` manifest generation), `AgentClient` (x402 agent-to-agent paid skill calls), `PermissionsClient` (ERC-7710 delegations), and the Solana identity/attestation helpers. Full docs: [SDK & Library](#sec-633).For the endpoints on this page, call them directly with `fetch`/`curl` and a Bearer API key:@@ -37171,7 +37241,7 @@ POST /api/event-markets/:slug/pick { "outcome_id": "<uuid>", "points": 50DELETE /api/event-markets/:slug/pick```-A pick at or after `locks_at` returns `409 market_locked` with the closing time. A market with no picks returns an even prior and `odds.even_prior: true`. Full contract, error codes, limits and MCP tools: [event-markets.md](#sec-266).+A pick at or after `locks_at` returns `409 market_locked` with the closing time. A market with no picks returns an even prior and `odds.even_prior: true`. Full contract, error codes, limits and MCP tools: [event-markets.md](#sec-269).## Agents API (v1)@@ -37253,7 +37323,7 @@ a delivery from the log or the `/dashboard/developers` page. The signing secret----<a id="sec-125"></a>+<a id="sec-126"></a>> **Source:** `docs/api/forge-x402.md` · [↑ table of contents](#table-of-contents)@@ -37586,8 +37656,8 @@ Solscan-linked "x402" provenance badge. Inline-done lanes publish immediately;async lanes are completed server-side by `api/cron/forge-finalize`, so theartifact lands even if you never poll. Recording happens after your response issent and never affects your result. See-[x402 endpoints](#sec-854) and-[the autonomous economy](#sec-140).+[x402 endpoints](#sec-869) and+[the autonomous economy](#sec-141).Treat prompts as public. If you need a private lane, use the account-scopedsurfaces instead of this one.@@ -37632,17 +37702,17 @@ const glb = Buffer.from(await (await fetch(glbUrl)).arrayBuffer());- [3D API](#sec-001): the free draft lane, inspection, validation, and thefull Forge Pro walkthrough.-- [Forge pipeline](#sec-311): how the lanes, tiers, and failovers fit+- [Forge pipeline](#sec-314): how the lanes, tiers, and failovers fittogether internally.-- [3D Studio MCP server](#sec-410): the same generation as+- [3D Studio MCP server](#sec-414): the same generation as`text_to_3d` / `image_to_3d` tools for in-conversation use, priced from thesame tier table. This REST endpoint is the pay-per-call surface for autonomousagents.-- [x402 endpoints](#sec-854): every paid endpoint on the platform.+- [x402 endpoints](#sec-869): every paid endpoint on the platform.----<a id="sec-126"></a>+<a id="sec-127"></a>> **Source:** `docs/approvals.md` · [↑ table of contents](#table-of-contents)@@ -37933,12 +38003,12 @@ its step-up gate, with an idempotency key derived from the action. Enginesthat execute inline (an auto-approved request) call `runApproved(row, run)`,which provides the same once-only and integrity guarantees.-Related: [Notifications](#sec-442) for the delivery fan-out and the+Related: [Notifications](#sec-446) for the delivery fan-out and thepreference matrix, [STRUCTURE.md](../STRUCTURE.md) for where everything lives.----<a id="sec-127"></a>+<a id="sec-128"></a>> **Source:** `docs/apps.md` · [↑ table of contents](#table-of-contents)@@ -37959,11 +38029,11 @@ Code: [src/apps.js](../src/apps.js), [src/apps.css](../src/apps.css). `/apps/des## Keeping them true-Each page states a real status. When a store listing goes live (Google Play, the App Store) or a build ships (macOS), update the status pill and the primary button on that page and the card on `/apps`, and add a changelog entry. Source docs: [seeker-app.md](#sec-629), [ios-app.md](#sec-385), [desktop.md](#sec-241).+Each page states a real status. When a store listing goes live (Google Play, the App Store) or a build ships (macOS), update the status pill and the primary button on that page and the card on `/apps`, and add a changelog entry. Source docs: [seeker-app.md](#sec-636), [ios-app.md](#sec-389), [desktop.md](#sec-242).----<a id="sec-128"></a>+<a id="sec-129"></a>> **Source:** `docs/ar-studio.md` · [↑ table of contents](#table-of-contents)@@ -37976,9 +38046,9 @@ API: `POST /api/forge` (in-view text-to-3D) · `GET /api/forge-gallery` (your an## Why it exists-The older "View in AR" flow (see [AR and WebXR](#sec-129)) shows one model at a time in a native viewer. AR Studio is the composition tool: a persistent, multi-model scene you arrange in real space and can build with other people at once. It is free, needs no account, and degrades gracefully so it works on a laptop, a phone browser, or a full AR headset. It is where a forge result, a marketplace avatar, and a prompt-conjured prop can all stand in your living room together.+The older "View in AR" flow (see [AR and WebXR](#sec-130)) shows one model at a time in a native viewer. AR Studio is the composition tool: a persistent, multi-model scene you arrange in real space and can build with other people at once. It is free, needs no account, and degrades gracefully so it works on a laptop, a phone browser, or a full AR headset. It is where a forge result, a marketplace avatar, and a prompt-conjured prop can all stand in your living room together.-This doc covers what is unique to AR Studio. For the underlying `POST /api/forge` free lane, the `<agent-3d>` "View in AR" methods, the USDZ/Quick Look pipeline, and model-optimization limits, see [AR and WebXR](#sec-129).+This doc covers what is unique to AR Studio. For the underlying `POST /api/forge` free lane, the `<agent-3d>` "View in AR" methods, the USDZ/Quick Look pipeline, and model-optimization limits, see [AR and WebXR](#sec-130).## How it works@@ -38071,13 +38141,13 @@ Append `?e2e=1` to expose `window.__arsDebug` (`count()`, `netStatus()`, `netIds## Related-- [AR and WebXR](#sec-129): the single-model "View in AR" system, `/ar` AR Forge, the `POST /api/forge` free lane in depth, the USDZ/Quick Look pipeline, and model-optimization limits.-- [Selfie to Avatar](#sec-633) and [Avatar pipeline](#sec-148): where the models you place come from.+- [AR and WebXR](#sec-130): the single-model "View in AR" system, `/ar` AR Forge, the `POST /api/forge` free lane in depth, the USDZ/Quick Look pipeline, and model-optimization limits.+- [Selfie to Avatar](#sec-640) and [Avatar pipeline](#sec-149): where the models you place come from.- Pages: [/ar/studio](https://three.ws/ar/studio), [/ar](https://three.ws/ar), [/viewer](https://three.ws/viewer).----<a id="sec-129"></a>+<a id="sec-130"></a>> **Source:** `docs/ar.md` · [↑ table of contents](#table-of-contents)@@ -38521,7 +38591,7 @@ a server-side PNG render of the actual GLB (CDN-cached for a day), so pastingan AR link into a chat or timeline shows the model, not a generic card. Thepage also converts: it carries "Create your own" (into [/ar](/ar)) and "Openin 3D viewer" calls to action. See `GET|POST /api/render/glb` in the-[API reference](#sec-124) for the renderer's parameters and limits.+[API reference](#sec-125) for the renderer's parameters and limits.**For agents (MCP):** on the free, keyless connector at `/api/mcp-studio` every generation already returns `arUrl` in its result, so there is nothing extra to call. To build the link set for a GLB that connector did not generate, the read-only `export_ar` tool on the separate [`/api/mcp-3d` server](/docs/mcp-3d-studio) (account- or payment-gated) turns any public GLB into the AR launch link plus a conformant [Spatial MCP](/docs/spatial-mcp) artifact (with the `ar` handoff populated):@@ -38584,13 +38654,13 @@ the wild can load.----<a id="sec-130"></a>+<a id="sec-131"></a>> **Source:** `docs/architecture.md` · [↑ table of contents](#table-of-contents)# Architecture Overview-three.ws is the platform you see at [three.ws](https://three.ws): 3D avatars with AI brains that you can chat with, embed on any site, and register on-chain. This page is the engineering map of how that is built. If you just want to use the product, start with [How three.ws works](#sec-351) instead.+three.ws is the platform you see at [three.ws](https://three.ws): 3D avatars with AI brains that you can chat with, embed on any site, and register on-chain. This page is the engineering map of how that is built. If you just want to use the product, start with [How three.ws works](#sec-355) instead.This document describes how three.ws is put together, how data moves through it, and where the seams are if you want to extend, self-host, or integrate it with another stack. It assumes familiarity with modern JavaScript, WebGL/three.js at a high level, and the basics of EVM blockchains and content-addressed storage.@@ -38848,7 +38918,7 @@ A minimal Node + Neon + Anthropic deployment is enough for a single agent. The b----<a id="sec-131"></a>+<a id="sec-132"></a>> **Source:** `docs/assistant-widget.md` · [↑ table of contents](#table-of-contents)@@ -38861,9 +38931,9 @@ The assistant widget puts a full-body, animated three.ws avatar on any website bConfigure everything and copy your snippet at [three.ws/assistant](https://three.ws/assistant). The builder page runs the real widget, so what you see in the corner is exactly what your visitors get.-Looking for a support-chat panel grounded in your page's content instead of a full-body avatar? That is the sibling [Concierge widget](#sec-211). Use Concierge for "answer questions about this page"; use the assistant widget when you want a character who stands on your site, speaks, and can run on a visitor's own model key.+Looking for a support-chat panel grounded in your page's content instead of a full-body avatar? That is the sibling [Concierge widget](#sec-212). Use Concierge for "answer questions about this page"; use the assistant widget when you want a character who stands on your site, speaks, and can run on a visitor's own model key.-There are three ways to add it: a one-tag script, the [`@three-ws/assistant`](https://www.npmjs.com/package/@three-ws/assistant) npm package, or let an AI agent generate the embed for you through the [assistant-widget MCP server](#generate-a-widget-from-an-ai-agent-mcp). New to it? The [step-by-step tutorial](#sec-703) builds one from scratch.+There are three ways to add it: a one-tag script, the [`@three-ws/assistant`](https://www.npmjs.com/package/@three-ws/assistant) npm package, or let an AI agent generate the embed for you through the [assistant-widget MCP server](#generate-a-widget-from-an-ai-agent-mcp). New to it? The [step-by-step tutorial](#sec-711) builds one from scratch.## Install@@ -38972,7 +39042,7 @@ Two tools:- **`list_assistant_options`** returns everything you can configure: the built-in avatars, the background presets and grammar, the modes, the chat lanes, and the full `data-*` attribute reference.- **`build_assistant_widget`** turns a config (avatar, background, mode, name, greeting, context, accent, position) into a paste-ready `<script>` snippet, a standalone frame URL, an equivalent `ThreeAssistant.init({...})` call, and the builder link. Every field is validated and clamped, so a bad value falls back to a safe default and the generated HTML is always well-formed.-Ask your agent something like "build a 3D assistant widget named Aria with an ocean background for my site" and paste the snippet it returns. The server is one of the [three.ws MCP servers](#sec-417); find it in the registry at [registry.modelcontextprotocol.io](https://registry.modelcontextprotocol.io/?q=io.github.nirholas).+Ask your agent something like "build a 3D assistant widget named Aria with an ocean background for my site" and paste the snippet it returns. The server is one of the [three.ws MCP servers](#sec-421); find it in the registry at [registry.modelcontextprotocol.io](https://registry.modelcontextprotocol.io/?q=io.github.nirholas).## How it works@@ -38984,10 +39054,10 @@ Ask your agent something like "build a 3D assistant widget named Aria with an oc## Related surfaces-- [Build a 3D assistant, step by step](#sec-703), the tutorial-- [Concierge](#sec-211), the page-grounded support-chat widget with a lipsyncing face-- [three.ws MCP servers](#sec-417), the full free and paid tool catalog-- [Share and embed](#sec-636), the `<three-d>` model embeds+- [Build a 3D assistant, step by step](#sec-711), the tutorial+- [Concierge](#sec-212), the page-grounded support-chat widget with a lipsyncing face+- [three.ws MCP servers](#sec-421), the full free and paid tool catalog+- [Share and embed](#sec-643), the `<three-d>` model embeds- [/walk-embed](https://three.ws/walk-embed), the walking-avatar iframe embed- [/forge](https://three.ws/forge), generate an avatar to use in the widget@@ -39000,7 +39070,7 @@ Ask your agent something like "build a 3D assistant widget named Aria with an oc----<a id="sec-132"></a>+<a id="sec-133"></a>> **Source:** `docs/atlas.md` · [↑ table of contents](#table-of-contents)@@ -39176,7 +39246,7 @@ searching for "embed".----<a id="sec-133"></a>+<a id="sec-134"></a>> **Source:** `docs/atomic.md` · [↑ table of contents](#table-of-contents)@@ -39273,7 +39343,7 @@ New senders should use `@solana/kit` 8 or later, build with `createTransactionMe----<a id="sec-134"></a>+<a id="sec-135"></a>> **Source:** `docs/audit/console-sweep-2026-09-04.md` · [↑ table of contents](#table-of-contents)@@ -40186,7 +40256,7 @@ Call log:----<a id="sec-135"></a>+<a id="sec-136"></a>> **Source:** `docs/audit/console-sweep-2026-09-07.md` · [↑ table of contents](#table-of-contents)@@ -41854,7 +41924,7 @@ Call log:----<a id="sec-136"></a>+<a id="sec-137"></a>> **Source:** `docs/audit/console-sweep-2026-09-09.md` · [↑ table of contents](#table-of-contents)@@ -42931,7 +43001,7 @@ thirty-one findings above were the box, not the code.----<a id="sec-137"></a>+<a id="sec-138"></a>> **Source:** `docs/audit/python-deps-2026-09-07.md` · [↑ table of contents](#table-of-contents)@@ -43065,7 +43135,7 @@ the pin.----<a id="sec-138"></a>+<a id="sec-139"></a>> **Source:** `docs/authentication.md` · [↑ table of contents](#table-of-contents)@@ -43319,7 +43389,7 @@ Every auth endpoint accepts an optional `tosAccepted: true` body field. Send it- `POST /api/auth/register` **requires** `tosAccepted: true`; account creation without it fails with `400 tos_required`. Registration UIs must show a real agreement control.- Wallet and Privy verifies (`/api/auth/siwe/verify`, `/api/auth/siws/verify`, `/api/auth/privy/verify`) and `POST /api/auth/login` treat it as an affirmation: acceptance is recorded on every sign-in, so users converge onto the current Terms version over time.-An already-signed-in user can also record acceptance directly with `POST /api/legal/tos-ack { version?, context? }`. That endpoint only covers the Terms of Service; the real-funds agreements (Risk Disclosure + Agent Wallet Agreement, required before any custodial money-moving action) are a separate, heavier signing flow at `POST /api/legal/risk-ack` (review them at [/legal/agreements](https://three.ws/legal/agreements)). Every custodial money endpoint (withdraw, trade, pay, launch) requires a typed-name signature of all three documents; an unsigned account gets `403 risk_ack_required` over a session and an API key alike, and devnet actions are exempt. See [risk acknowledgment](#sec-618).+An already-signed-in user can also record acceptance directly with `POST /api/legal/tos-ack { version?, context? }`. That endpoint only covers the Terms of Service; the real-funds agreements (Risk Disclosure + Agent Wallet Agreement, required before any custodial money-moving action) are a separate, heavier signing flow at `POST /api/legal/risk-ack` (review them at [/legal/agreements](https://three.ws/legal/agreements)). Every custodial money endpoint (withdraw, trade, pay, launch) requires a typed-name signature of all three documents; an unsigned account gets `403 risk_ack_required` over a session and an API key alike, and devnet actions are exempt. See [risk acknowledgment](#sec-625).---@@ -43442,7 +43512,7 @@ Telegram sign-in (widget and deep-link magic link), one-time link codes for phon## Sign in with X`GET /api/auth/x/login?next=<path>` starts an OAuth 2.0 PKCE round trip with X-(the same client the Connect-X posting flow in [the Herald](#sec-338) and+(the same client the Connect-X posting flow in [the Herald](#sec-342) andTown already use) and redirects back through `GET /api/auth/x/callback`. Itonly appears on [/login](https://three.ws/login) when `GET /api/config`reports `xLoginEnabled: true`, which requires `X_OAUTH_CLIENT_ID` and@@ -43623,7 +43693,7 @@ hold, or holding none of them, answers `403 insufficient_scope`.### Signing in from a terminal (device link)-The `three-ws` CLI ([docs](#sec-191)) gets an API key without a pasted secret through an RFC 8628-style device link: `POST /api/cli/link { client_name, hostname, scope }` returns a `user_code` and a `verification_uri` (`/cli/authorize`); the person opens it signed in, can narrow the scopes (money-moving ones are flagged), and approves; the CLI polls `POST /api/cli/token { device_code }` every 3 seconds and receives the minted key exactly once. Poll errors use the RFC 8628 codes (`authorization_pending`, `slow_down`, `access_denied`, `expired_token`), and a link expires after 10 minutes. Approval refuses every bearer principal, so a credential can never widen itself into a new one without a person pressing the button. `GET /api/cli/whoami` with the key as a Bearer returns the account, plan, credential, and agent wallet.+The `three-ws` CLI ([docs](#sec-192)) gets an API key without a pasted secret through an RFC 8628-style device link: `POST /api/cli/link { client_name, hostname, scope }` returns a `user_code` and a `verification_uri` (`/cli/authorize`); the person opens it signed in, can narrow the scopes (money-moving ones are flagged), and approves; the CLI polls `POST /api/cli/token { device_code }` every 3 seconds and receives the minted key exactly once. Poll errors use the RFC 8628 codes (`authorization_pending`, `slow_down`, `access_denied`, `expired_token`), and a link expires after 10 minutes. Approval refuses every bearer principal, so a credential can never widen itself into a new one without a person pressing the button. `GET /api/cli/whoami` with the key as a Bearer returns the account, plan, credential, and agent wallet.### Using a key@@ -43647,7 +43717,7 @@ const res = await fetch('/api/agents', {| `memory:read` | Read agent memory || `memory:write` | Write agent memory || `profile` | Read/write profile data; required to manage API keys themselves |-| `herald:announce` | Post announcements through the [Herald](#sec-338) (`POST /api/herald/announce`); the scope the `herald-mcp` package's `THREE_WS_API_KEY` needs |+| `herald:announce` | Post announcements through the [Herald](#sec-342) (`POST /api/herald/announce`); the scope the `herald-mcp` package's `THREE_WS_API_KEY` needs || `wallet:read` | See the agent wallet balance, history, and spending caps || `wallet:write` | Move, commit, or redirect funds from a custodial wallet (withdraw, trade, pay, hire, launch), within its caps || `services:write` | Publish paid services that earn USDC to the agent wallet |@@ -43858,7 +43928,7 @@ three.ws examples repo, so it is installed, run, and link-checked before every r----<a id="sec-139"></a>+<a id="sec-140"></a>> **Source:** `docs/autonomous-economy.md` · [↑ table of contents](#table-of-contents)@@ -43873,8 +43943,8 @@ and the platform **scans its own wallets for leaks every few minutes**.This page explains the whole loop in plain language: which wallet does what, how moneycan and cannot move, and how you can verify there's no leak yourself.-Companion docs: [Money map](#sec-435) (which wallet receives each *payment*),-[Economy master](#sec-255) (the funding-root subsystem in depth), and the+Companion docs: [Money map](#sec-439) (which wallet receives each *payment*),+[Economy master](#sec-258) (the funding-root subsystem in depth), and the[Solana signers runbook](../api/_lib/solana-signers.js) (every signer, its floor, andhow to fund it).@@ -44013,16 +44083,16 @@ zero.## Related-- [Money map](#sec-435) — which wallet receives each kind of payment, and the+- [Money map](#sec-439) — which wallet receives each kind of payment, and theplatform's cut.-- [Economy master](#sec-255) — the funding-root subsystem, its ledger, and the+- [Economy master](#sec-258) — the funding-root subsystem, its ledger, and thetopup/sweepback crons in depth.-- [x402 ring economy](#sec-857) — how the autonomous payment ring settles+- [x402 ring economy](#sec-872) — how the autonomous payment ring settlesUSDC between agents.----<a id="sec-140"></a>+<a id="sec-141"></a>> **Source:** `docs/autonomous-x402.md` · [↑ table of contents](#table-of-contents)@@ -44049,7 +44119,7 @@ the sniper oracle gate.The loop runs from the `x402-autonomous-loop` cron endpoint, invoked every**minute** by the `economy-tick` dispatcher (see the-[economy heartbeat](#sec-254)) rather than by its own schedule+[economy heartbeat](#sec-257)) rather than by its own scheduleentry; per-entry Redis cooldowns decide what actually fires on any given tick.Each tick:@@ -44099,7 +44169,7 @@ master holds funds.| `X402_ASSET_MINT_SOLANA` | USDC mint | The asset paid with (Solana USDC). || `SOLANA_RPC_URL` | — | RPC used to build and submit the payment. |-This loop's treasury is **separate** from the [circulation engine](#sec-189)+This loop's treasury is **separate** from the [circulation engine](#sec-190)treasury (`CIRCULATION_TREASURY_SECRET`). Circulation funds agent-to-agent SOL /$THREE activity; this loop funds USDC intel purchases. They do not fund eachother.@@ -44183,7 +44253,7 @@ automatically (and `tests/x402-ring-catalog.test.js` fails until it is cataloged> number you publish. Scaling this loop to manufacture a big volume figure is wash> volume: real transactions, fake demand, and detectable on-chain.> Drive *real* volume through external demand (the-> [Circulation engine](#sec-189), real `agent_hire` commerce,+> [Circulation engine](#sec-190), real `agent_hire` commerce,> discovery), not a heavier self-paid sweep.**Excluding it is mechanical, not a matter of remembering to.**@@ -44256,7 +44326,7 @@ claims an on-chain settlement — outbound `x402_autonomous_log` rows and inbounwallet configured (keyless RPC; the `/api/x402-status` probe it reads is free). A`reconciled = false` row means the books claim a settlement the chain does notcorroborate — the ops financial-integrity surface alerts on those. Detail:-[Financial controls](#sec-306).+[Financial controls](#sec-309).## Where results land@@ -44265,21 +44335,21 @@ corroborate — the ops financial-integrity surface alerts on those. Detail:| `x402_autonomous_log` | Every call (success or failure), with `signal_data` / `value_extracted`. `error_msg` is reserved for calls that actually failed: the external uptime monitor probes third-party services for free and records an alive-but-unexpected status (a templated path answering 400, a verb-picky route answering 405) in `value_extracted.status` only, so a liveness observation never lands in the loop's failure stats. || `oracle_intel_signals` | `oracle` / `sniper` entries, keyed by source + topic; consumed by the sniper oracle gate. Each row carries `tx_signature`, the settle signature of the paid call that bought it, so a gate decision can cite its receipt (surfaced as `signal_receipts` on gate results). || `forge_creations` | Every settled `POST /api/x402/forge` generation (any buyer, not just this loop). The row lands in the public community gallery with `x402_payer` / `x402_tx_sig` / `x402_price_atomic` provenance; the gallery renders a Solscan-linked "x402 · $price" badge. Inline-done lanes materialize immediately; async lanes store the full job token and `api/cron/forge-finalize` completes them server-side. |-| `agent_custody_events` | The USDC spend, with `category: 'x402'` (see [Money feed](#sec-433)). |+| `agent_custody_events` | The USDC spend, with `category: 'x402'` (see [Money feed](#sec-437)). || `x402_volume_metrics` | Per-endpoint proof-of-volume + liveness ledger from the Volume Bootstrap Loop. |-| `payment_reconciliation` | One verdict per settlement claim from the daily reconciliation job (see [Financial controls](#sec-306)). |+| `payment_reconciliation` | One verdict per settlement claim from the daily reconciliation job (see [Financial controls](#sec-309)). || Dedicated stores | Pipeline-specific tables (pricing tracker, reputation snapshots, leaderboard, sniper analytics, …). |## Related-- [x402 endpoints](#sec-854) — the paid endpoints this loop calls.-- [Financial controls](#sec-306): where settlements land and how the reconciliation job audits them.-- [x402 buyer client](#sec-851) — the client wrappers it pays with.-- [Circulation engine](#sec-189) — the separate SOL/$THREE activity loop.+- [x402 endpoints](#sec-869) — the paid endpoints this loop calls.+- [Financial controls](#sec-309): where settlements land and how the reconciliation job audits them.+- [x402 buyer client](#sec-866) — the client wrappers it pays with.+- [Circulation engine](#sec-190) — the separate SOL/$THREE activity loop.----<a id="sec-141"></a>+<a id="sec-142"></a>> **Source:** `docs/autopilot.md` · [↑ table of contents](#table-of-contents)@@ -44374,15 +44444,15 @@ A confirmed buyback narrates as: "Bought back and burned $120 of $YOURCOIN. Supp## Related-- [Custody you can verify](#sec-232) - the spend limits, freeze switch, and audit trail every agent wallet runs under-- [Financial controls](#sec-306) - plain-English spend rules layered on the same enforcement point-- [Oracle](#sec-467) - the conviction engine and the agent action loop that arms an agent to trade autonomously+- [Custody you can verify](#sec-233) - the spend limits, freeze switch, and audit trail every agent wallet runs under+- [Financial controls](#sec-309) - plain-English spend rules layered on the same enforcement point+- [Oracle](#sec-472) - the conviction engine and the agent action loop that arms an agent to trade autonomously- [/dashboard](https://three.ws/dashboard) - launch a coin for an agent, the prerequisite for Autopilot- [/launches](https://three.ws/launches) - the public feed of coins launched through three.ws----<a id="sec-142"></a>+<a id="sec-143"></a>> **Source:** `docs/avatar-artifact.md` · [↑ table of contents](#table-of-contents)@@ -44390,7 +44460,7 @@ A confirmed buyback narrates as: "Bought back and burned $120 of $YOURCOIN. Supp[three.ws/avatar-artifact](https://three.ws/avatar-artifact) is one page that renders one avatar and nothing else. No app shell, no sign-in, no navigation to get lost in: a URL you can paste into an `<iframe>` on any site, or send to someone who has never heard of three.ws, and it renders a live 3D avatar in their browser.-It is deliberately the smallest viewer we ship. [The full 3D viewer](#sec-795) is the engine behind `/app` and every `<agent-3d>` embed, with camera rigs, material editing and a clip panel. This page has one job: show the artifact, beautifully, from a link.+It is deliberately the smallest viewer we ship. [The full 3D viewer](#sec-805) is the engine behind `/app` and every `<agent-3d>` embed, with camera rigs, material editing and a clip panel. This page has one job: show the artifact, beautifully, from a link.---@@ -44454,7 +44524,7 @@ Two properties make this safe to drop on someone else's page:- **No third-party CDN.** three.js ships with the bundle. An embed host never picks up a cross-origin script tag it did not agree to.- **It stops when it is not visible.** A hidden tab suspends the render loop, so an embedded viewer never burns a host page's GPU in the background.-For a full chat widget or a token-gated embed, use [Share and embed](#sec-636) instead. This page is the plain viewer.+For a full chat widget or a token-gated embed, use [Share and embed](#sec-643) instead. This page is the plain viewer.---@@ -44508,14 +44578,14 @@ A large model on a slow connection is not a failure: the loading overlay reports## Related-- [The 3D viewer](#sec-795): the full engine behind `/app` and `<agent-3d>`-- [Share and embed](#sec-636): widgets, web components and embed policy+- [The 3D viewer](#sec-805): the full engine behind `/app` and `<agent-3d>`+- [Share and embed](#sec-643): widgets, web components and embed policy- [Claude artifact contract](../specs/CLAUDE_ARTIFACT.md): the self-contained HTML lane for Claude.ai, which shares this page's parameter shape- [Animations](#sec-101): the clip library this page retargets from----<a id="sec-143"></a>+<a id="sec-144"></a>> **Source:** `docs/avatar-cli.md` · [↑ table of contents](#table-of-contents)@@ -44527,7 +44597,7 @@ It is the piece that lets avatars live in a build pipeline instead of a browser**On this page:** [Install](#install) · [Quick start](#quick-start) · [Commands](#commands) · [The manifest](#the-manifest) · [Exit codes](#exit-codes-and-scripting) · [Release gate](#gate-a-release-on-the-manifest)-Related: [`@three-ws/avatar-schema`](../packages/avatar-schema/README.md) is the wire format this validates against. The [web component reference](#sec-799) covers the `<agent-3d>` element the CLI emits.+Related: [`@three-ws/avatar-schema`](../packages/avatar-schema/README.md) is the wire format this validates against. The [web component reference](#sec-811) covers the `<agent-3d>` element the CLI emits.---@@ -44721,7 +44791,7 @@ https://three.ws/a/eip155%3A1%3A0x742d35Cc6634C0532925a3b844Bc454e4438f44e<iframe src="https://three.ws/a/eip155%3A1%3A0x742d35Cc6634C0532925a3b844Bc454e4438f44e" width="480" height="640" frameborder="0" allow="camera; microphone; xr-spatial-tracking"></iframe>```-The web-component block is emitted with its loader on purpose. `<agent-3d>` is an ordinary unknown element until that script registers it, so the snippet is only complete with both lines. See the [web component reference](#sec-799) for the full attribute surface.+The web-component block is emitted with its loader on purpose. `<agent-3d>` is an ordinary unknown element until that script registers it, so the snippet is only complete with both lines. See the [web component reference](#sec-811) for the full attribute surface.When `mesh.uri` is still a local path, `preview` says so rather than handing you a snippet that renders nothing:@@ -44818,14 +44888,14 @@ three-ws-avatar validate manifest.json --json | jq -e '.valid'## Where to go next-- **[Ship an avatar manifest](#sec-755)** walks the whole path end to end, from a raw GLB to a live embed, and explains the decision at each step.-- **[Web component reference](#sec-799)** documents every attribute on the `<agent-3d>` element `preview` emits.+- **[Ship an avatar manifest](#sec-763)** walks the whole path end to end, from a raw GLB to a live embed, and explains the decision at each step.+- **[Web component reference](#sec-811)** documents every attribute on the `<agent-3d>` element `preview` emits.- **[`@three-ws/avatar-schema`](../packages/avatar-schema/README.md)** is the normative format if you are writing your own tooling.- The package source lives in [`packages/avatar-cli`](https://github.com/nirholas/three.ws/tree/main/packages/avatar-cli).----<a id="sec-144"></a>+<a id="sec-145"></a>> **Source:** `docs/avatar-creation.md` · [↑ table of contents](#table-of-contents)@@ -44864,7 +44934,7 @@ Good lighting and a plain background give the best results. Photos can be JPEG o1. Go to **https://three.ws/create** and pick the selfie path (or open **https://three.ws/create/selfie** directly)2. Choose **Camera** (to take live photos in-browser) or **Upload** (to pick files from your device)3. Fill the frontal slot; add left/right photos if you have them-4. Select your **avatar style** (v1 = Photoreal, v2 = Stylized). There is deliberately no body-type picker: reconstruction fits your face onto one shared template body today, so a masc/femme toggle would change nothing. Body choice returns when reconstruction moves onto the parametric base, tracked in [avatar-fidelity-program.md](#sec-146) under Track 5+4. Select your **avatar style** (v1 = Photoreal, v2 = Stylized). There is deliberately no body-type picker: reconstruction fits your face onto one shared template body today, so a masc/femme toggle would change nothing. Body choice returns when reconstruction moves onto the parametric base, tracked in [avatar-fidelity-program.md](#sec-147) under Track 55. Click **Submit**The photos are downscaled in the browser and sent to the native avatar reconstruction backend. A build view shows progress while the rigged GLB renders (typically a minute or two); when the job finishes, the avatar is saved to your three.ws account automatically and opens for review.@@ -45097,7 +45167,7 @@ On success, you receive:### 3. Register on-chain (optional)-For permanent, verifiable identity, you can register the agent on-chain under ERC-8004. This creates a blockchain record linked to a wallet address. Gas fees apply. See the [ERC-8004 documentation](#sec-263) for details.+For permanent, verifiable identity, you can register the agent on-chain under ERC-8004. This creates a blockchain record linked to a wallet address. Gas fees apply. See the [ERC-8004 documentation](#sec-266) for details.---@@ -45161,7 +45231,7 @@ No regeneration provider is configured on this deployment. Set `AVATAR_REGEN_PRO----<a id="sec-145"></a>+<a id="sec-146"></a>> **Source:** `docs/avatar-engines.md` · [↑ table of contents](#table-of-contents)@@ -45223,7 +45293,7 @@ Mesh and glTF output can be animated by the skinned-mesh pipeline. Gaussian and| --- | --- | --- || `live` | Live on three.ws | Already wired into a three.ws product surface you can use right now. || `forge` | Generate in Forge | Commercially licensed and reachable through the live text and image to GLB pipeline at [/forge](https://three.ws/forge). |-| `splat` | View in Splat Viewer | Produces Gaussian-splat or radiance-field output you can drop into the three.ws [splat viewer](#sec-661). |+| `splat` | View in Splat Viewer | Produces Gaussian-splat or radiance-field output you can drop into the three.ws [splat viewer](#sec-669). || `interop` | Interop | Emits a standard rigged format (glTF, VRM, FBX) that the three.ws viewer and animation pipeline already understand. || `reference` | Reference / self-host | Run it yourself. Its license or its compute profile keeps it out of the commercial pipeline. It is listed here for builders. |@@ -45330,16 +45400,16 @@ To add an engine, append an entry to `ENGINES` in [`src/avatar-engines-data.js`]## Related-- [Splat Viewer](#sec-661): where the Gaussian-splat output of the `splat` engines actually renders in the browser.-- [Scene Capture](#sec-178): the three.ws side of reconstruction, turning real video into 3D, adjacent to the photoreal-head family here.-- [Forge](#sec-313): the live commercial generation pipeline, which the one `live` text-to-avatar engine powers.+- [Splat Viewer](#sec-669): where the Gaussian-splat output of the `splat` engines actually renders in the browser.+- [Scene Capture](#sec-179): the three.ws side of reconstruction, turning real video into 3D, adjacent to the photoreal-head family here.+- [Forge](#sec-316): the live commercial generation pipeline, which the one `live` text-to-avatar engine powers.- [Agent Identity Studio](#sec-056): that pipeline applied end to end, brand brief to rigged avatar plus studio renders.- [Animations](#sec-101): the retargeting and clip library that drives the production rigs in the last family.-- [Avatar pipeline](#sec-148) and [avatar creation](#sec-144): how three.ws produces and processes its own mesh avatars.+- [Avatar pipeline](#sec-149) and [avatar creation](#sec-145): how three.ws produces and processes its own mesh avatars.----<a id="sec-146"></a>+<a id="sec-147"></a>> **Source:** `docs/avatar-fidelity-program.md` · [↑ table of contents](#table-of-contents)@@ -45351,7 +45421,7 @@ own, and costs nothing per avatar. Not "good enough to avoid a bill" — betterthan the thing we would have paid for.This is the program plan. The subsystem it improves is documented in-[avatar-reconstruction.md](#sec-149); the worker lives in+[avatar-reconstruction.md](#sec-150); the worker lives in[`workers/avatar-reconstruction/`](../workers/avatar-reconstruction).## Why we are not buying this@@ -45797,7 +45867,7 @@ items do not:----<a id="sec-147"></a>+<a id="sec-148"></a>> **Source:** `docs/avatar-inspector.md` · [↑ table of contents](#table-of-contents)@@ -45905,7 +45975,7 @@ Related reading: [agent reputation](#sec-060) · [Agora](#sec-080).----<a id="sec-148"></a>+<a id="sec-149"></a>> **Source:** `docs/avatar-pipeline.md` · [↑ table of contents](#table-of-contents)@@ -45914,8 +45984,8 @@ Related reading: [agent reputation](#sec-060) · [Agora](#sec-080).This is the end-to-end view of how a text prompt or image becomes a rigged,animated 3D avatar on three.ws — from generation, through auto-rigging, to theuniversal animation system that drives any humanoid skeleton. It ties together the-individual tool docs ([Avatar creation](#sec-144),-[Avatar Studio](#sec-182), [Animations](#sec-101),+individual tool docs ([Avatar creation](#sec-145),+[Avatar Studio](#sec-183), [Animations](#sec-101),[3D asset pipeline](#sec-002)) into one map.---@@ -45942,7 +46012,7 @@ prompt / imageGeneration quality is a **tier** ([api/_lib/forge-tiers.js](../api/_lib/forge-tiers.js)): `draft`, `standard`(default), or `high` — more geometric budget at higher tiers. The tier sets theprice identically across REST and MCP transports (see-[MCP tools](#sec-415), [x402 endpoints](#sec-854)).+[MCP tools](#sec-419), [x402 endpoints](#sec-869)).### ② Auto-rig@@ -46019,22 +46089,22 @@ an avatar still animates.A finished avatar is a GLB (plus optional rig + clips) viewable in the three.wsviewer, embeddable as a web component, and attachable to an agent. Paidgeneration/editing is metered per call over x402; the free studio lane requires no-account. See [Avatar creation](#sec-144) and-[Avatar Studio](#sec-182) for the authoring UIs, and-[Mesh editing tools](#sec-415) for retexture / stylize / remesh / segment /+account. See [Avatar creation](#sec-145) and+[Avatar Studio](#sec-183) for the authoring UIs, and+[Mesh editing tools](#sec-419) for retexture / stylize / remesh / segment /pose operations.## Related-- [Selfie → Avatar reconstruction](#sec-149) — the separate lane that fits a *person's photo* onto a rigged template (face texture + geometry morph), rather than generating a mesh from a prompt.+- [Selfie → Avatar reconstruction](#sec-150) — the separate lane that fits a *person's photo* onto a rigged template (face texture + geometry morph), rather than generating a mesh from a prompt.- [Animations](#sec-101) — the clip library and retargeting in depth.- [3D asset pipeline](#sec-002) — formats, optimization, validation.-- [NVIDIA free models](#sec-450) — the free generation backend.-- [MCP tools](#sec-415) — every generation/editing tool and its price.+- [NVIDIA free models](#sec-454) — the free generation backend.+- [MCP tools](#sec-419) — every generation/editing tool and its price.----<a id="sec-149"></a>+<a id="sec-150"></a>> **Source:** `docs/avatar-reconstruction.md` · [↑ table of contents](#table-of-contents)@@ -46048,7 +46118,7 @@ instead (a full-body reference image, reconstructed on the self-hosted Hunyuan3Dworker, then auto-rigged). The lane plan lives in[`api/_lib/prompt-avatar.js`](../api/_lib/prompt-avatar.js); both inputs sharethe job contract, the status poll, and the finalize tail described below. It is distinct from the Forge-generation lane in the [Avatar Pipeline](#sec-148): the Forge generates+generation lane in the [Avatar Pipeline](#sec-149): the Forge generatesan *arbitrary* mesh from a prompt, whereas reconstruction fits a *specificperson* onto a fixed, pre-rigged template — the same architecture Avaturn andReady Player Me use, and the reason the output is born-rigged with facial@@ -46182,7 +46252,7 @@ photo of the same person still give the same head?). 0.55 sits at the knee ofthat fidelity-vs-robustness curve, cutting mean ISE 46% against the original0.75 / 0.18, whose ~1.9 cm displacement ceiling was throttling genuine facialvariation rather than rejecting outliers; past 0.65 fidelity flatlines while-instability keeps rising. See [avatar-fidelity-program.md](#sec-146)+instability keeps rising. See [avatar-fidelity-program.md](#sec-147)for why the sweep's own looser optimum was deliberately not shipped.Because vertex count and order never change, `glb_ops.set_head_geometry` writes@@ -46276,7 +46346,7 @@ is unencumbered.## Roadmap — beating Avaturn on fidelity> The active plan built on this roadmap — tracks, owners, capacity and credit-> allocation — is [avatar-fidelity-program.md](#sec-146).+> allocation — is [avatar-fidelity-program.md](#sec-147).> Fidelity claims are scored with the ISE metric in> [`workers/avatar-reconstruction/eval/`](../workers/avatar-reconstruction/eval/README.md).@@ -46325,7 +46395,7 @@ Full runbook: [`docs/ops/gcp-production.md`](ops/gcp-production.md).----<a id="sec-150"></a>+<a id="sec-151"></a>> **Source:** `docs/avatar-studio.md` · [↑ table of contents](#table-of-contents)@@ -46412,15 +46482,15 @@ curl 'https://three.ws/api/avatars/<avatarId>' -H 'cookie: <session>'## Related- [Animation Studio](#sec-100): pose and keyframe the avatar you build here.-- [Scene Composer](#sec-210): forge props and attach them to the avatar's bones as a saved outfit.-- [Mocap Studio](#sec-430): drive the avatar's face live from your webcam.-- [Restyle Studio](#sec-616): shares the same GLB optimize-and-validate path.-- [Trait-based avatar builder](#sec-182): the separate VRM studio embedded in the agent editor; a deep dive into its internals.+- [Scene Composer](#sec-211): forge props and attach them to the avatar's bones as a saved outfit.+- [Mocap Studio](#sec-434): drive the avatar's face live from your webcam.+- [Restyle Studio](#sec-623): shares the same GLB optimize-and-validate path.+- [Trait-based avatar builder](#sec-183): the separate VRM studio embedded in the agent editor; a deep dive into its internals.- [/create](https://three.ws/create): the hub for every avatar-creation path, including selfie-to-avatar.----<a id="sec-151"></a>+<a id="sec-152"></a>> **Source:** `docs/avatar-thumbnails.md` · [↑ table of contents](#table-of-contents)@@ -46791,7 +46861,7 @@ that adoption HEAD-checks the preview object before persisting it.----<a id="sec-152"></a>+<a id="sec-153"></a>> **Source:** `docs/avatar-wardrobe.md` · [↑ table of contents](#table-of-contents)@@ -46977,13 +47047,13 @@ the strip and every garment is applied twice.## Related-- [`docs/avatar-reconstruction.md`](#sec-149) — selfie → avatar-- [`docs/avatar-fidelity-program.md`](#sec-146) — identity fidelity program+- [`docs/avatar-reconstruction.md`](#sec-150) — selfie → avatar+- [`docs/avatar-fidelity-program.md`](#sec-147) — identity fidelity program- [`specs/GARMENT_MANIFEST.md`](../specs/GARMENT_MANIFEST.md) — the wearable contract----<a id="sec-153"></a>+<a id="sec-154"></a>> **Source:** `docs/aws-builder-center-agent-commerce-spine.md` · [↑ table of contents](#table-of-contents)@@ -47326,7 +47396,7 @@ Questions are welcome. The parts I would most love other builders to dig into ar----<a id="sec-154"></a>+<a id="sec-155"></a>> **Source:** `docs/aws-builder-center-agent-payment-sessions.md` · [↑ table of contents](#table-of-contents)@@ -47811,7 +47881,7 @@ An autonomous agent with a private key is a liability you cannot bound. An auton----<a id="sec-155"></a>+<a id="sec-156"></a>> **Source:** `docs/aws-builder-center-before-the-signature.md` · [↑ table of contents](#table-of-contents)@@ -48236,7 +48306,7 @@ The parts I would most like other builders to argue with are section 3 (a policy----<a id="sec-156"></a>+<a id="sec-157"></a>> **Source:** `docs/aws-builder-center-claims-ledger.md` · [↑ table of contents](#table-of-contents)@@ -48683,7 +48753,7 @@ The part we would most like other builders to argue with is section 6: a model a----<a id="sec-157"></a>+<a id="sec-158"></a>> **Source:** `docs/aws-builder-center-immutable-embed-releases.md` · [↑ table of contents](#table-of-contents)@@ -49207,7 +49277,7 @@ Source: [github.com/nirholas/three.ws](https://github.com/nirholas/three.ws), Ap----<a id="sec-158"></a>+<a id="sec-159"></a>> **Source:** `docs/aws-builder-center-marketplace-x402.md` · [↑ table of contents](#table-of-contents)@@ -49226,7 +49296,7 @@ tags: [aws, marketplace, saas, serverless, api]# One paywall, two economies: putting AWS Marketplace metering in front of an x402 API-> **Editor's note (2026-08-15).** This is the repo copy of an article published on the AWS Builder Center on 30 May 2026, kept as it was published. One thing has moved since: the AWS Marketplace listing is still awaiting publication, and the pricing decision landed on a **free** listing with no AWS pricing dimensions, so the AWS-metered path described below is built and deployed but not yet billing anyone. Every code sample is still the code that ships. For the current status see [aws-marketplace.md](#sec-164).+> **Editor's note (2026-08-15).** This is the repo copy of an article published on the AWS Builder Center on 30 May 2026, kept as it was published. One thing has moved since: the AWS Marketplace listing is still awaiting publication, and the pricing decision landed on a **free** listing with no AWS pricing dimensions, so the AWS-metered path described below is built and deployed but not yet billing anyone. Every code sample is still the code that ships. For the current status see [aws-marketplace.md](#sec-165).We run [three.ws](https://three.ws), an open-source platform for 3D AI agents and on-chain communities. Our paid API already had a billing system: **x402**, the HTTP-native pay-per-call protocol where a request to a metered endpoint either carries a subscription key or gets a `402 Payment Required`. That works great for developers who pay in stablecoins.@@ -49473,7 +49543,7 @@ The product on the other side of all this plumbing is the platform: three.ws age----<a id="sec-159"></a>+<a id="sec-160"></a>> **Source:** `docs/aws-builder-center-mcp-agents.md` · [↑ table of contents](#table-of-contents)@@ -49589,7 +49659,7 @@ If you wire it into something, or you want to list a paid tool of your own, the----<a id="sec-160"></a>+<a id="sec-161"></a>> **Source:** `docs/aws-builder-center-open-weight-3d-forge.md` · [↑ table of contents](#table-of-contents)@@ -50026,7 +50096,7 @@ Source: [github.com/nirholas/three.ws](https://github.com/nirholas/three.ws), Ap----<a id="sec-161"></a>+<a id="sec-162"></a>> **Source:** `docs/aws-builder-center-universal-retargeting.md` · [↑ table of contents](#table-of-contents)@@ -50416,7 +50486,7 @@ npx vitest run tests/glb-canonicalize.test.js tests/animation-upright-invariant.node scripts/animation-dignity-sweep.mjs --verbose```-If your rig uses a naming convention the tables do not know, Rig Doctor lists the unrecognised names, and [the contribution guide](#sec-307) walks through teaching the canonicalizer a new one, and lists the three open conventions from section 9 ready to pick up.+If your rig uses a naming convention the tables do not know, Rig Doctor lists the unrecognised names, and [the contribution guide](#sec-310) walks through teaching the canonicalizer a new one, and lists the three open conventions from section 9 ready to pick up.---@@ -50424,7 +50494,7 @@ If your rig uses a naming convention the tables do not know, Rig Doctor lists th----<a id="sec-162"></a>+<a id="sec-163"></a>> **Source:** `docs/aws-builder-center.md` · [↑ table of contents](#table-of-contents)@@ -50436,7 +50506,7 @@ This page is the index of that writing: what is published, where it lives, and w- **Profile:** [builder.aws.com/community/@threews](https://builder.aws.com/community/@threews)- **Account:** organization account, byline "three.ws"-- **Related surfaces:** [three.ws/aws](https://three.ws/aws) (AWS Partner page), [AWS Marketplace listing](#sec-164), [AWS partner spotlight](#sec-165)+- **Related surfaces:** [three.ws/aws](https://three.ws/aws) (AWS Partner page), [AWS Marketplace listing](#sec-165), [AWS partner spotlight](#sec-166)## Published articles@@ -50446,11 +50516,11 @@ Published 30 May 2026. Tags: `aws-payment-cryptography`, `blockchain`, `metadata> [Read it on the AWS Builder Center](https://builder.aws.com/content/3ESpll50BdSp9eiCEIxcfG9pGUN/how-we-metered-a-saas-product-through-aws-marketplace-with-the-aws-sdk-for-javascript-v3)-The full AWS Marketplace SaaS usage-based integration, end to end: `ResolveCustomer` on the fulfillment URL, `MeterUsage` and `BatchMeterUsage` for consumption reporting, `GetEntitlements` for tiered feature gating, and SNS lifecycle webhooks with real signature verification. It closes on the part nobody else writes about: bridging an AWS `CustomerIdentifier` into the same access check that already served an on-chain [x402](#sec-140) paywall, so one authorization path bills two economies.+The full AWS Marketplace SaaS usage-based integration, end to end: `ResolveCustomer` on the fulfillment URL, `MeterUsage` and `BatchMeterUsage` for consumption reporting, `GetEntitlements` for tiered feature gating, and SNS lifecycle webhooks with real signature verification. It closes on the part nobody else writes about: bridging an AWS `CustomerIdentifier` into the same access check that already served an on-chain [x402](#sec-141) paywall, so one authorization path bills two economies.-- **Source draft in this repo:** [aws-builder-center-marketplace-x402.md](#sec-158)+- **Source draft in this repo:** [aws-builder-center-marketplace-x402.md](#sec-159)- **Code it documents:** [`api/aws-marketplace/`](https://github.com/nirholas/three.ws/tree/main/api/aws-marketplace), [`api/_lib/aws-marketplace.js`](https://github.com/nirholas/three.ws/blob/main/api/_lib/aws-marketplace.js), [`api/_lib/aws-marketplace-bridge.js`](https://github.com/nirholas/three.ws/blob/main/api/_lib/aws-marketplace-bridge.js)-- **Since publication:** on 2026-08-17 the integration moved to the updated SaaS integration AWS made mandatory for new products. `ResolveCustomer` now returns `CustomerAWSAccountId` + `LicenseArn` rather than a `CustomerIdentifier`, so the store keys buyers by license ARN (`api/_lib/aws-marketplace-store.js`) and the x402 bridge joins on the customer row id, with `CustomerIdentifier` kept only as a legacy lookup. Lifecycle notifications arrive as EventBridge agreement and license events; the SNS webhook path the article describes is still accepted and still signature-verified. [aws-marketplace.md](#sec-164) is the current reference; the article stays accurate for the SDK calls it walks through.+- **Since publication:** on 2026-08-17 the integration moved to the updated SaaS integration AWS made mandatory for new products. `ResolveCustomer` now returns `CustomerAWSAccountId` + `LicenseArn` rather than a `CustomerIdentifier`, so the store keys buyers by license ARN (`api/_lib/aws-marketplace-store.js`) and the x402 bridge joins on the customer row id, with `CustomerIdentifier` kept only as a legacy lookup. Lifecycle notifications arrive as EventBridge agreement and license events; the SNS webhook path the article describes is still accepted and still signature-verified. [aws-marketplace.md](#sec-165) is the current reference; the article stays accurate for the SDK calls it walks through.- **Announcement:** [three.ws Publishes on the AWS Builder Center Blog](https://three.ws/news/aws-builder-center-blog)### 2. Build Autonomous AI Agents with 3D Bodies and On-Chain Payments | three.ws on AWS@@ -50461,7 +50531,7 @@ Published 27 June 2026. Tags: `ai`, `agent-toolkit`, `blockchain`, `aws-partnersThe platform-level piece: browser-native 3D AI agents with memory, on-chain wallets, and autonomous payments, available on AWS Marketplace, embeddable in one line of HTML, and governed before they act. Written for AWS builders evaluating three.ws as an agent runtime rather than as a 3D asset tool.-- **Surfaces it covers:** [the `<agent-3d>` web component](#sec-799), [agent wallets](#sec-077), [the agent system](#sec-068), [AWS Marketplace procurement](#sec-164)+- **Surfaces it covers:** [the `<agent-3d>` web component](#sec-811), [agent wallets](#sec-077), [the agent system](#sec-068), [AWS Marketplace procurement](#sec-165)## Published by AWS about three.ws@@ -50475,7 +50545,7 @@ Published 26 June 2026 by Kelly Wu (AWS). Part of the AWS-run series "AWS PartneA builder's guide to the agentic economy that uses the three.ws stack as its worked example throughout: the x402 handshake and its three layers, MCP as the distribution layer for agent capabilities, agent-to-agent payments, on-chain agent identity (ERC-8004 and the SPL skill licenses), agent tokens on the bonding curve, and 3D embodiment. It walks the hosted MCP servers, the `@three-ws/*` payment SDKs, and the FSI use cases for per-call data access, and closes on the open problems: payment streaming, automatic cross-chain routing, agent reputation as a credit primitive, and org-scale spend governance.-- **Surfaces it covers:** [the MCP servers](#sec-417), [x402](#sec-140), [agent wallets](#sec-077), [the `<agent-3d>` web component](#sec-799)+- **Surfaces it covers:** [the MCP servers](#sec-421), [x402](#sec-141), [agent wallets](#sec-077), [the `<agent-3d>` web component](#sec-811)- **Canonical URL note:** the Builder Center strips digits from slugs, so `x402` becomes `x` and `3d` becomes `d` in the path. The URL above is the one AWS publishes in its own [sitemap](https://builder.aws.com/sitemaps/articles/2026-6.xml); a slug containing the digits also resolves, because the content ID is what routes.## In draft@@ -50484,15 +50554,15 @@ Written and reviewed in this repo, not yet submitted:| Draft | Subject ||---|---|-| [aws-builder-center-before-the-signature.md](#sec-155) | **Flagship.** The whole authorization spine in one piece: Marketplace entitlements under Concurrent Agreements, budgets instead of private keys, the budget check as a predicate in the `UPDATE`, the SSRF guard around an LLM-chosen URL, the payment outcome with no clean answer, signed inference receipts, agent vitals, hardware-backed signing, and the fabrication gate in front of a manufactured object. Supersedes the four topic drafts below. |-| [aws-builder-center-agent-payment-sessions.md](#sec-154) | Agent Payment Sessions: giving an agent a budget instead of a private key, and enforcing it atomically in Postgres |-| [aws-builder-center-mcp-agents.md](#sec-159) | An MCP server whose paid tools settle per call in USDC over HTTP 402 |-| [mobile-launch/aws-builder-center-article.md](#sec-425) | One web product, three native apps, zero forks: the Seeker, Android, and iPhone shells, with the AWS SDK v3 storage client and the Marketplace front door |-| [aws-builder-center-agent-commerce-spine.md](#sec-153) | The authorization spine behind autonomous commerce: Marketplace entitlements under Concurrent Agreements, spend policy instead of a credential, x402 preflight, agent vitals, and the physical fulfillment lane at the end of the chain |-| [aws-builder-center-universal-retargeting.md](#sec-161) | Any skeleton, one clip library: how 113 pre-baked clips play on humanoid avatars from many exporters in the browser with no rig allowlist. Bone-name canonicalization, the bind correction, the A-pose re-aim, the fallen-pose guard, and the conventions that still fail. Companion thread: [universal-retargeting-thread.md](#sec-847) |-| [aws-builder-center-immutable-embed-releases.md](#sec-157) | A URL is a promise: moving channels beside write-once versioned URLs for the `<agent-3d>` web component, the release ledger, Subresource Integrity pins, the 2026-10-01 incident that broke every pin, and how the pattern maps to S3 Object Lock and CloudFront. Companion thread: [immutable-embed-releases-thread.md](#sec-827) |-| [aws-builder-center-claims-ledger.md](#sec-156) | An AI-assisted publishing pipeline that refuses to post what it cannot prove: the claims ledger, probes, proof reels filmed against production, content-hash-bound reviews, the idempotent publish ledger, and the model failover chain. Companion thread: [claims-ledger-thread.md](#sec-822) |-| [aws-builder-center-open-weight-3d-forge.md](#sec-160) | Running open-weight text-to-3D in production: the Forge's lane router and failover ladder across self-hosted GPU workers (TRELLIS, Hunyuan3D, TripoSG) and hosted rungs, cold starts and weight staging, meshopt decoding in every mesh worker, vendored shared code, and `forge_creations` as per-generation ground truth. Companion thread: [open-weight-3d-forge-thread.md](#sec-838) |+| [aws-builder-center-before-the-signature.md](#sec-156) | **Flagship.** The whole authorization spine in one piece: Marketplace entitlements under Concurrent Agreements, budgets instead of private keys, the budget check as a predicate in the `UPDATE`, the SSRF guard around an LLM-chosen URL, the payment outcome with no clean answer, signed inference receipts, agent vitals, hardware-backed signing, and the fabrication gate in front of a manufactured object. Supersedes the four topic drafts below. |+| [aws-builder-center-agent-payment-sessions.md](#sec-155) | Agent Payment Sessions: giving an agent a budget instead of a private key, and enforcing it atomically in Postgres |+| [aws-builder-center-mcp-agents.md](#sec-160) | An MCP server whose paid tools settle per call in USDC over HTTP 402 |+| [mobile-launch/aws-builder-center-article.md](#sec-429) | One web product, three native apps, zero forks: the Seeker, Android, and iPhone shells, with the AWS SDK v3 storage client and the Marketplace front door |+| [aws-builder-center-agent-commerce-spine.md](#sec-154) | The authorization spine behind autonomous commerce: Marketplace entitlements under Concurrent Agreements, spend policy instead of a credential, x402 preflight, agent vitals, and the physical fulfillment lane at the end of the chain |+| [aws-builder-center-universal-retargeting.md](#sec-162) | Any skeleton, one clip library: how 113 pre-baked clips play on humanoid avatars from many exporters in the browser with no rig allowlist. Bone-name canonicalization, the bind correction, the A-pose re-aim, the fallen-pose guard, and the conventions that still fail. Companion thread: [universal-retargeting-thread.md](#sec-861) |+| [aws-builder-center-immutable-embed-releases.md](#sec-158) | A URL is a promise: moving channels beside write-once versioned URLs for the `<agent-3d>` web component, the release ledger, Subresource Integrity pins, the 2026-10-01 incident that broke every pin, and how the pattern maps to S3 Object Lock and CloudFront. Companion thread: [immutable-embed-releases-thread.md](#sec-841) |+| [aws-builder-center-claims-ledger.md](#sec-157) | An AI-assisted publishing pipeline that refuses to post what it cannot prove: the claims ledger, probes, proof reels filmed against production, content-hash-bound reviews, the idempotent publish ledger, and the model failover chain. Companion thread: [claims-ledger-thread.md](#sec-836) |+| [aws-builder-center-open-weight-3d-forge.md](#sec-161) | Running open-weight text-to-3D in production: the Forge's lane router and failover ladder across self-hosted GPU workers (TRELLIS, Hunyuan3D, TripoSG) and hosted rungs, cold starts and weight staging, meshopt decoding in every mesh worker, vendored shared code, and `forge_creations` as per-generation ground truth. Companion thread: [open-weight-3d-forge-thread.md](#sec-852) |## Publishing checklist@@ -50512,7 +50582,7 @@ The Builder Center is where AWS customers evaluating a partner product go lookin----<a id="sec-163"></a>+<a id="sec-164"></a>> **Source:** `docs/aws-marketplace-listing-kit.md` · [↑ table of contents](#table-of-contents)@@ -50521,7 +50591,7 @@ The Builder Center is where AWS customers evaluating a partner product go lookinPaste-ready content and the exact step sequence to create the **AI agents & tools**product in the AWS Marketplace Management Portal (AMMP). The backend integration(register URL, SNS webhook, key issuance, account linking) is already built and-deployed — see [aws-marketplace.md](#sec-164). This doc covers the+deployed — see [aws-marketplace.md](#sec-165). This doc covers thelisting itself, which has not yet been created (the AMMP "AI agents & toolsproducts" page shows "No products to display").@@ -50548,7 +50618,7 @@ products" page shows "No products to display").> `AWS_MP_METERING_DIMENSION` and `AWS_MP_DEFAULT_RATE_LIMIT_PER_MINUTE` remain in> the code for a future usage-priced listing. Both are inert while the dimension-> is unset, which is the correct state for a free listing. [aws-marketplace.md](#sec-164)+> is unset, which is the correct state for a free listing. [aws-marketplace.md](#sec-165)> documents them as optional rather than as the billing model.---@@ -50903,7 +50973,7 @@ Set as the old docs instructed, every genuine AWS notification failed the pin anreturned 403, visible only in logs.*Fixed:* the script no longer creates that topic, and both this file and-[aws-marketplace.md](#sec-164) state that the variable takes the AWS-issued+[aws-marketplace.md](#sec-165) state that the variable takes the AWS-issued`aws-mp-subscription-notification-<PRODUCTCODE>` ARN or nothing at all.**Defect 3 (latent): SNS signature verification hardcoded SHA1.**@@ -50954,7 +51024,7 @@ Still verify against the product overview page at creation time----<a id="sec-164"></a>+<a id="sec-165"></a>> **Source:** `docs/aws-marketplace.md` · [↑ table of contents](#table-of-contents)@@ -50962,7 +51032,7 @@ Still verify against the product overview page at creation timethree.ws is a verified AWS Partner. The AWS Marketplace product is an API-based (SaaS) listing, and the AWS subscription is a **free front door**: subscribing links your AWS account to a three.ws account and issues an x402 access key. Actual usage is then paid per-call in USDC over the x402 / HTTP 402 protocol, the same as every other x402 endpoint. AWS Marketplace itself does not meter or bill usage.-> **Listing status (checked 2026-08-17): not yet public.** The integration is built, deployed, and now conforms to the Concurrent Agreements requirements AWS made mandatory for new SaaS products on 2026-06-01, but the product has not been created in the AWS Marketplace Management Portal, so there is nothing to subscribe to on the AWS side yet. The Marketplace credentials (`AWS_MP_*`) are correspondingly unset in production, so `POST /api/aws-marketplace/subscription` answers `503 not_configured` today. The remaining steps are AWS-console work and Seller Operations approval, tracked in [aws-marketplace-listing-kit.md](#sec-163). Until then, use x402 directly: no AWS subscription is required to call `/api/x402/*`.+> **Listing status (checked 2026-08-17): not yet public.** The integration is built, deployed, and now conforms to the Concurrent Agreements requirements AWS made mandatory for new SaaS products on 2026-06-01, but the product has not been created in the AWS Marketplace Management Portal, so there is nothing to subscribe to on the AWS side yet. The Marketplace credentials (`AWS_MP_*`) are correspondingly unset in production, so `POST /api/aws-marketplace/subscription` answers `503 not_configured` today. The remaining steps are AWS-console work and Seller Operations approval, tracked in [aws-marketplace-listing-kit.md](#sec-164). Until then, use x402 directly: no AWS subscription is required to call `/api/x402/*`.## Subscribing via AWS Marketplace@@ -51057,7 +51127,7 @@ For platform support, open an issue at [github.com/nirholas/three.ws/issues](htt----<a id="sec-165"></a>+<a id="sec-166"></a>> **Source:** `docs/aws-partner-spotlight.md` · [↑ table of contents](#table-of-contents)@@ -51148,12 +51218,12 @@ One product. Two ways in. One authorization path.**Learn more**- Platform: [three.ws](https://three.ws)-- AWS Marketplace and procurement: [three.ws/docs/aws-marketplace](#sec-164)-- How agents reach and pay for tools: [three.ws/docs/x402](#sec-862), [three.ws/docs/mcp](#sec-417)+- AWS Marketplace and procurement: [three.ws/docs/aws-marketplace](#sec-165)+- How agents reach and pay for tools: [three.ws/docs/x402](#sec-877), [three.ws/docs/mcp](#sec-421)----<a id="sec-166"></a>+<a id="sec-167"></a>> **Source:** `docs/big-tech-recognition-week.md` · [↑ table of contents](#table-of-contents)@@ -51164,9 +51234,9 @@ company: on their own website, in their own directory, or from their own socialaccount.This doc is the cross-vendor dispatch board. Every other outreach doc in `docs/`-is one vendor deep ([nvidia-visibility-map.md](#sec-454),-[partners.md](#sec-474), [listings.md](#sec-403),-[aws-marketplace.md](#sec-164), [ibm.md](#sec-378)). This one is the+is one vendor deep ([nvidia-visibility-map.md](#sec-458),+[partners.md](#sec-480), [listings.md](#sec-407),+[aws-marketplace.md](#sec-165), [ibm.md](#sec-382)). This one is theonly place that ranks all of them against each other by the single question thatmatters this week: **what is the probability of a published big-tech mentionwithin seven days, and what exactly is standing in the way?**@@ -51186,8 +51256,8 @@ not have known about.|---|---|---|| OpenAI App Directory | `ready-to-submit`, one portal action | **Regressed to blocked.** The whole surface was re-verified live today and passes, but [`prompts/store-submissions/_generated/TRACKER.md`](../prompts/store-submissions/_generated/TRACKER.md) now records three gates: clear the GCP billing hold that has Vertex denied project-wide, deploy the four fixes sitting unshipped in the tree, then submit. The blocker is infrastructure, not packaging. || NVIDIA, the one email | Written, never sent | **Sent 2026-09-04; answered 2026-09-14.** NVIDIA confirmed portal-driven catalog review, restored co-brand asset access, and an invite-only GTC Pavilion. Complete the portal record, retrieve the kit, then ask only the two unanswered Showcase/ACE questions in the existing thread. |-| NVIDIA Developer Forums, post 3 | Not written | **Written 2026-09-02**: [nvidia-forum-browser-digital-human.md](#sec-445). Owner-gated on the external-channel rule, then paste and post. |-| IBM | No map existed | **[ibm-visibility-map.md](#sec-376)** now covers it: the Champions window, the Partner Plus Directory, the IBM Cloud catalog route, the two co-marketing commitments from 2026-06-18 that nothing was tracking, and the Partner Plus benefits never requested. |+| NVIDIA Developer Forums, post 3 | Not written | **Written 2026-09-02**: [nvidia-forum-browser-digital-human.md](#sec-449). Owner-gated on the external-channel rule, then paste and post. |+| IBM | No map existed | **[ibm-visibility-map.md](#sec-380)** now covers it: the Champions window, the Partner Plus Directory, the IBM Cloud catalog route, the two co-marketing commitments from 2026-06-18 that nothing was tracking, and the Partner Plus benefits never requested. |Two deadlines that did not exist at compile time:@@ -51195,7 +51265,7 @@ Two deadlines that did not exist at compile time:- **IBM Champions nominations open around mid-September.** The last cycle ran 2025-09-15 to 2025-11-21, self-nomination is invited, and three.ws has never entered despite matching all four of IBM's published criteria on IBM's own properties. Missing it costs a full year.One correction to the tables below: Tier 1 row 3 calls the next AWS piece-"article 2". [aws-builder-center.md](#sec-162) records **two**+"article 2". [aws-builder-center.md](#sec-163) records **two**published under our byline already (2026-05-30 and 2026-06-27) plus one writtenby AWS staff about us. The next one is article 3. The genre advice in that rowstill stands.@@ -51290,11 +51360,11 @@ three.ws has a live Builder Center profile atand one published article, [How we metered a SaaS product through AWS Marketplacewith the AWS SDK for JavaScript v3](https://builder.aws.com/content/3ESpll50BdSp9eiCEIxcfG9pGUN/how-we-metered-a-saas-product-through-aws-marketplace-with-the-aws-sdk-for-javascript-v3)(2026-05-30). Publishing is self-serve. This is a repeatable win, and-[aws-builder-center.md](#sec-162) already carries the checklist for+[aws-builder-center.md](#sec-163) already carries the checklist forpublishing the next one.**The caveat.** The obvious candidate for article 2 is-[aws-partner-spotlight.md](#sec-165), which is written and+[aws-partner-spotlight.md](#sec-166), which is written andunpublished. It is a company profile, not a technical article. The one thatlanded was technical: real code, real API calls, and "the five things that bitus." Builder Center rewards the second genre and the audience there is builders,@@ -51312,7 +51382,7 @@ Two Anthropic surfaces are `ready-to-submit` (Official MCP Registry, Claude plugmarketplace) and a third, the Claude Connectors Directory, is blocked only onprovisioning an `MCP_REVIEW_SECRET` and a reviewer-credential decision.-Worth naming plainly: **[partners.md](#sec-474) lists eight partners and+Worth naming plainly: **[partners.md](#sec-480) lists eight partners andAnthropic is not one of them**, even though the platform's agent brain defaults toClaude models and there are three Anthropic-surface submissions sitting ready.That is the most underdeveloped big-tech relationship on the board relative to how@@ -51337,7 +51407,7 @@ and carries `#NVIDIAInception`. A post that merely names NVIDIA in prose is notresharable by them. Without the kit, the X ambition has no mechanism behind it.Send one email to `[email protected]` carrying all five asks. The-existing [Apps Catalog request](#sec-444) is already+existing [Apps Catalog request](#sec-448) is alreadywritten and already addressed there; extend that draft rather than opening asecond thread. A program manager who receives one clear email with five asksanswers it. Five separate emails read as noise.@@ -51354,7 +51424,7 @@ The five asks:record currently describes three.ws as a CUDA consumer, which is wrong and whichgates both the Showcase and the Apps Catalog. Correct it at`programs.nvidia.com/phoenix/application` first. The correction is already-specified in step 1 of [nvidia-apps-catalog-listing.md](#sec-443).+specified in step 1 of [nvidia-apps-catalog-listing.md](#sec-447).Nothing in this email lands well while the record misdescribes the product.---@@ -51421,7 +51491,7 @@ promotes.[three.ws/demos/audio2face](https://three.ws/demos/audio2face) (and the`/audio2face` alias), served from[`public/demos/audio2face.html`](../public/demos/audio2face.html) and documented in-[demo-routes.md](#sec-235). Both routes returned 200 on 2026-08-17. You+[demo-routes.md](#sec-236). Both routes returned 200 on 2026-08-17. Youtype text, hear it in NVIDIA Magpie's voice, and watch the face animate throughARKit blendshapes, in a browser tab, with no install.@@ -51508,18 +51578,18 @@ Publishing, posting, and sending are owner-gated under stop-and-ask gate 2 in## Related-- [Partnership and listing pipeline](#sec-479): the durable worklist this week-shaped board feeds into-- [NVIDIA visibility map](#sec-454): every NVIDIA surface in depth, and the dead ends-- [IBM visibility map](#sec-376): the same treatment for IBM, including the Champions window and the Partner Plus benefits never requested-- [Partners](#sec-474): the eight programs, and the independence language that must survive any rewrite-- [Listings and distribution](#sec-403): the canonical program and directory inventory+- [Partnership and listing pipeline](#sec-486): the durable worklist this week-shaped board feeds into+- [NVIDIA visibility map](#sec-458): every NVIDIA surface in depth, and the dead ends+- [IBM visibility map](#sec-380): the same treatment for IBM, including the Champions window and the Partner Plus benefits never requested+- [Partners](#sec-480): the eight programs, and the independence language that must survive any rewrite+- [Listings and distribution](#sec-407): the canonical program and directory inventory- [Announcement coverage](#sec-104): which surfaces have been announced on X and which have not-- [Press kit](#sec-505): marks, boilerplate, and the rules governing co-branded graphics+- [Press kit](#sec-512): marks, boilerplate, and the rules governing co-branded graphics- [OpenAI submission handoff pack](../prompts/finish/_context/openai-pr-00-START-HERE.md): the pre-submission task briefs----<a id="sec-167"></a>+<a id="sec-168"></a>> **Source:** `docs/blender-mcp.md` · [↑ table of contents](#table-of-contents)@@ -51786,20 +51856,20 @@ Failures come back as structured tool errors, each naming a fix:`blender_run_python` executes caller-supplied Python inside Blender with this server's permissions, including filesystem access. That is what the tool is for, and it is annotated `destructiveHint: true` so a client prompts before running it. For unattended or shared deployments set `BLENDER_MCP_ALLOW_PYTHON=0`: the tool is then never advertised, and the other six keep working.-Only `blender_forge_import` reaches the network, and only the deployment named by `THREE_WS_BASE`. Everything else stays on the machine. The broader model is in [MCP safety](#sec-412).+Only `blender_forge_import` reaches the network, and only the deployment named by `THREE_WS_BASE`. Everything else stays on the machine. The broader model is in [MCP safety](#sec-416).---## Related- [`integrations/blender/`](https://github.com/nirholas/three.ws/tree/main/integrations/blender) is the artist-facing counterpart: a Blender add-on with a sidebar panel that generates three.ws models from inside the GUI. This server is the agent-facing one; they can be installed side by side.-- [MCP integration](#sec-417) lists every three.ws MCP server.+- [MCP integration](#sec-421) lists every three.ws MCP server.- [3D API](#sec-001) documents the Forge endpoints behind `blender_forge_import`.- [Scenes MCP](https://www.npmjs.com/package/@three-ws/scene-mcp) composes whole 3D worlds from one sentence.----<a id="sec-168"></a>+<a id="sec-169"></a>> **Source:** `docs/bnb-babt-findings.md` · [↑ table of contents](#table-of-contents)@@ -51995,7 +52065,7 @@ shipped:----<a id="sec-169"></a>+<a id="sec-170"></a>> **Source:** `docs/bnb-payments.md` · [↑ table of contents](#table-of-contents)@@ -52168,7 +52238,7 @@ full verified-facts list.----<a id="sec-170"></a>+<a id="sec-171"></a>> **Source:** `docs/bnb-vault.md` · [↑ table of contents](#table-of-contents)@@ -52341,7 +52411,7 @@ this campaign, not a bug in this code path.----<a id="sec-171"></a>+<a id="sec-172"></a>> **Source:** `docs/bnb-world.md` · [↑ table of contents](#table-of-contents)@@ -52577,7 +52647,7 @@ reproduction commands are recorded in `contracts/DEPLOYMENTS.md`'s "Prompt## Related-- [BNB Chain payments](#sec-169) — the MPP/x402 payment rail this+- [BNB Chain payments](#sec-170) — the MPP/x402 payment rail thiscampaign also shipped, same `api/_lib/bnb/` namespace.- `contracts/src/WorldMoves.sol` — the contract itself, full NatSpec.- `contracts/DEPLOYMENTS.md` — deploy status, bytecode, and every real@@ -52588,7 +52658,7 @@ reproduction commands are recorded in `contracts/DEPLOYMENTS.md`'s "Prompt----<a id="sec-172"></a>+<a id="sec-173"></a>> **Source:** `docs/brain.md` · [↑ table of contents](#table-of-contents)@@ -52675,7 +52745,7 @@ curl -s https://three.ws/api/brain/chat```Stream one model's answer as SSE (the free default needs no auth; paid models need a-session or bearer token, see [Authentication](#sec-138)):+session or bearer token, see [Authentication](#sec-139)):```bashcurl -N -s -X POST https://three.ws/api/brain/chat \@@ -52720,13 +52790,13 @@ done; wait- [Agent Studio](#sec-066): the Brain tab uses this same backend- [Agent System](#sec-068): how a chosen brain fits the agent model-- [Persona Hub](#sec-491): synthesizing the system prompt a brain runs-- [API reference](#sec-124) and [Authentication](#sec-138)+- [Persona Hub](#sec-498): synthesizing the system prompt a brain runs+- [API reference](#sec-125) and [Authentication](#sec-139)- Pages: [/brain](https://three.ws/brain), [/agent-studio](https://three.ws/agent-studio)----<a id="sec-173"></a>+<a id="sec-174"></a>> **Source:** `docs/brownout.md` · [↑ table of contents](#table-of-contents)@@ -52919,11 +52989,11 @@ failed, for the same reason the prover does.- [/brownout](https://three.ws/brownout), the live registry and its receipts- [/guards](https://three.ws/guards), the mechanical checks that protect the codebase-- [docs/shared-utilities.md](#sec-637), the retry, ladder and last-good helpers this instruments+- [docs/shared-utilities.md](#sec-644), the retry, ladder and last-good helpers this instruments----<a id="sec-174"></a>+<a id="sec-175"></a>> **Source:** `docs/btn-pill-migration.md` · [↑ table of contents](#table-of-contents)@@ -53047,7 +53117,7 @@ The page's bare inline `.btn-primary` / `.btn-secondary` definitions are gone; w----<a id="sec-175"></a>+<a id="sec-176"></a>> **Source:** `docs/build.md` · [↑ table of contents](#table-of-contents)@@ -53216,13 +53286,13 @@ grep -l 'vite-plugin-pwa:register-sw' dist/widget.html dist/embed.html # expec----<a id="sec-176"></a>+<a id="sec-177"></a>> **Source:** `docs/ca2x402.md` · [↑ table of contents](#table-of-contents)# CA to x402-Paste a token contract address, get back a live, agent-payable [x402](#sec-862)+Paste a token contract address, get back a live, agent-payable [x402](#sec-877)market-intel endpoint for that exact token. The generated endpoint costs a smallUSDC payment per call, is discoverable in the x402 bazaar, and needs no keys, nobackend, and no deploy from the person who generated it.@@ -53383,7 +53453,7 @@ actually settles against.Operators can retune the price at deploy time with`X402_PRICE_TOKEN_INTEL=<atomics>`; a non-integer value logs a warning and falls-back to the default. See [x402 paid endpoints](#sec-854) for the full+back to the default. See [x402 paid endpoints](#sec-869) for the fullprice-override scheme.---@@ -53399,7 +53469,7 @@ A standard three.ws paid endpoint built on the shared handler`X-PAYMENT` header gets a `402` challenge carrying the accepted networks, asset,price, and pay-to address; the buyer retries with a signed payment and receivesthe intel. Settlement is recorded like any other endpoint payment (see-[Financial controls](#sec-306)).+[Financial controls](#sec-309)).The paid response body is the token block computed fresh at call time:@@ -53542,16 +53612,16 @@ right now. If the endpoint is unreachable the page says so and offers a retry.## Related-- [x402 on three.ws](#sec-862): the protocol, the wire format, and how the+- [x402 on three.ws](#sec-877): the protocol, the wire format, and how theplatform settles.-- [x402 paid endpoints](#sec-854): the full catalog of our paid+- [x402 paid endpoints](#sec-869): the full catalog of our paidendpoints, their prices, and the `X402_PRICE_*` override scheme.- [Receipt Vault](../pages/receipts.html): where the buyer's signed receipt for asettled payment to this endpoint can be retrieved.----<a id="sec-177"></a>+<a id="sec-178"></a>> **Source:** `docs/cad-forge.md` · [↑ table of contents](#table-of-contents)@@ -53561,12 +53631,12 @@ Describe a mechanical part in a sentence and get real CAD: a parametric [build12- **Page:** [three.ws/cad](https://three.ws/cad), with each design at `/cad/<id>`- **API:** `POST /api/cad` and `GET /api/cad` (below)-- **MCP:** `cad_generate` and `cad_rebuild` on the [3D Studio server](#sec-410)+- **MCP:** `cad_generate` and `cad_rebuild` on the [3D Studio server](#sec-414)- **Builder:** [workers/cad-forge](../workers/cad-forge/README.md)## Why it is different from text to 3D-[Text to 3D](#sec-313) makes a mesh that looks like the thing you described, which suits characters, props and scenery. A functional part needs something else. A phone mount has to fit the phone, the screw holes have to clear an M4 screw, and the wall has to be thick enough to print. CAD Forge produces a boundary-representation solid built from real operations (extrusions, holes, fillets, booleans), so every size in it is exact and editable.+[Text to 3D](#sec-316) makes a mesh that looks like the thing you described, which suits characters, props and scenery. A functional part needs something else. A phone mount has to fit the phone, the screw holes have to clear an M4 screw, and the wall has to be thick enough to print. CAD Forge produces a boundary-representation solid built from real operations (extrusions, holes, fillets, booleans), so every size in it is exact and editable.| | Text to 3D | CAD Forge || --- | --- | --- |@@ -53628,7 +53698,7 @@ That includes [text-to-cad](https://github.com/earthtojake/text-to-cad), which u- **Dimensions:** the sliders. **Reset** returns to the original values.- **Measurements:** size, volume, surface area, topology, the kernel's validity check, and the mass if made solid in PLA, PETG, nylon, aluminium, steel or brass. Picking a material also changes the 3D finish.- **Files:** STEP, STL, GLB, the drawing SVG and the Python program.-- **View in your space** opens the GLB in AR at true scale through [`/api/ar`](#sec-129). **Print it** hands the GLB to [Materialize](#sec-409) for a printability check and a quote. **Open in Scene Studio** loads it into the scene editor.+- **View in your space** opens the GLB in AR at true scale through [`/api/ar`](#sec-130). **Print it** hands the GLB to [Materialize](#sec-413) for a printability check and a quote. **Open in Scene Studio** loads it into the scene editor.- **Refine:** describe a change ("add a cable slot in the back, make the walls 3 mm"). The current program, at the values you have set, is rewritten and rebuilt as a new design linked to this one, so every part keeps its history.## HTTP API@@ -53717,14 +53787,14 @@ Without the worker URL and key, or without a database and object storage, `/api/## Related-- [Text to 3D](#sec-313) for organic and decorative models+- [Text to 3D](#sec-316) for organic and decorative models- [Machine Atlas](../src/assembly/README.md): machines generated from code in the browser-- [Materialize](#sec-409): print any model-- [AR & WebXR](#sec-129): true-scale placement+- [Materialize](#sec-413): print any model+- [AR & WebXR](#sec-130): true-scale placement----<a id="sec-178"></a>+<a id="sec-179"></a>> **Source:** `docs/capture.md` · [↑ table of contents](#table-of-contents)@@ -53821,14 +53891,14 @@ console.log(job.result_url, job.num_points); // coloured .ply + point count## Related-- [Splat Viewer](#sec-661) renders Gaussian-splat radiance fields, the photoreal cousin of point clouds.+- [Splat Viewer](#sec-669) renders Gaussian-splat radiance fields, the photoreal cousin of point clouds.- [/avatar-engines](https://three.ws/avatar-engines) covers the Geometric Context Transformer and related capture engines.-- [Forge](#sec-313) and [Image to 3D](#sec-379) for generating meshes from prompts and photos.+- [Forge](#sec-316) and [Image to 3D](#sec-383) for generating meshes from prompts and photos.- Pages: [/scene](https://three.ws/scene) (Scene Studio), [/create](https://three.ws/create).----<a id="sec-179"></a>+<a id="sec-180"></a>> **Source:** `docs/carplay.md` · [↑ table of contents](#table-of-contents)@@ -53856,7 +53926,7 @@ units where nothing is gated at all.## 1. Why this is a better fit than it looks-The [smart home plan](#sec-651) argued that a home is the first place where a body, a+The [smart home plan](#sec-659) argued that a home is the first place where a body, avoice, memory and identity all pay off at once. A car is the second, and it is a betterfirst shipment, for a reason that has nothing to do with ambition: **in a car, voice is notone interface among several. It is the only one that is legal.**@@ -53921,7 +53991,7 @@ What Android does **not** have is a conversational category. The manifest categodeclares exactly one. The accurate one here is **`androidx.car.app.category.IOT`**, for appsthat let people "take relevant actions on connected devices from within the car". That isnot a workaround: a three.ws agent already reaches a real house through the home tools wired-into `/api/chat` ([smart-home.md](#sec-651)), with a safety gate that freezes anything+into `/api/chat` ([smart-home.md](#sec-659)), with a safety gate that freezes anythingphysical until a person approves it. "Turn the porch light on" from the car is the product,and the category names it correctly.@@ -54111,7 +54181,7 @@ the fix goes upstream.----<a id="sec-180"></a>+<a id="sec-181"></a>> **Source:** `docs/changelog.md` · [↑ table of contents](#table-of-contents)@@ -54496,7 +54566,7 @@ cd sdk && npm publish----<a id="sec-181"></a>+<a id="sec-182"></a>> **Source:** `docs/character-library.md` · [↑ table of contents](#table-of-contents)@@ -54507,7 +54577,7 @@ The Character Library is a free, curated gallery of professionally rigged humanoPage: [/character-library](https://three.ws/character-library) · API: `GET /api/avatars/library`Source: [`pages/character-library.html`](../pages/character-library.html) · [`src/character-library.js`](../src/character-library.js) · [`api/avatars/library.js`](../api/avatars/library.js)-> This page covers the character gallery and its API. For the motion clips these characters play, see [Animations](#sec-101). For the free prop counterpart to this library, see the [Object Library](#sec-455).+> This page covers the character gallery and its API. For the motion clips these characters play, see [Animations](#sec-101). For the free prop counterpart to this library, see the [Object Library](#sec-459).---@@ -54523,8 +54593,8 @@ Each card renders the character live in an auto-rotating `<model-viewer>` (with| Button | Destination | What you get ||---|---|---|-| **Preview** | `/app#model=<glb-url>` | The full three.js [3D viewer](#sec-795) |-| **Use** | `/studio?model=<glb-url>` | [Widget Studio](#sec-801): configure and publish an embeddable widget of this character (see the [Embedding Guide](#sec-259)) |+| **Preview** | `/app#model=<glb-url>` | The full three.js [3D viewer](#sec-805) |+| **Use** | `/studio?model=<glb-url>` | [Widget Studio](#sec-813): configure and publish an embeddable widget of this character (see the [Embedding Guide](#sec-262)) || **Animate** | `/pose?src=<glb-url>&title=<name>` | [Animation Studio](#sec-100): pose, keyframe, and export motion on this character |Gallery controls:@@ -54536,7 +54606,7 @@ Gallery controls:## API: `GET /api/avatars/library`-Public, no authentication, `GET` and `OPTIONS` only (`HEAD` is answered like `GET`). Browser `fetch` from a third-party origin is not enabled: the endpoint sends `Access-Control-Allow-Origin` only for three.ws and its partner origins, exactly like the [Object Library API](#sec-455). Call it server-side, or from a three.ws page. The endpoint proxies a small manifest JSON from the R2 CDN (`avatars/library/manifest.json`) with an edge cache (`Cache-Control: public, s-maxage=300, stale-while-revalidate=3600`). The GLB and thumbnail bytes never pass through the API: every entry carries absolute CDN URLs the browser loads directly.+Public, no authentication, `GET` and `OPTIONS` only (`HEAD` is answered like `GET`). Browser `fetch` from a third-party origin is not enabled: the endpoint sends `Access-Control-Allow-Origin` only for three.ws and its partner origins, exactly like the [Object Library API](#sec-459). Call it server-side, or from a three.ws page. The endpoint proxies a small manifest JSON from the R2 CDN (`avatars/library/manifest.json`) with an edge cache (`Cache-Control: public, s-maxage=300, stale-while-revalidate=3600`). The GLB and thumbnail bytes never pass through the API: every entry carries absolute CDN URLs the browser loads directly.### Query parameters@@ -54617,13 +54687,13 @@ R2 CORS is configured by `scripts/set-r2-cors.mjs` so browsers can GET the GLBs- [Animations](#sec-101): the clip library every character drives, and how retargeting works.- [Animation Studio](#sec-100): the `/pose` surface the Animate button opens.-- [Widget Studio](#sec-801) and the [Embedding Guide](#sec-259): turn a library character into a live embed on any site.-- [Object Library](#sec-455): the same free-library pattern for CC0 props and scene objects.-- [Marketplace](#sec-408): library characters are free; the marketplace is where priced avatars, agents, and skills are bought and sold.+- [Widget Studio](#sec-813) and the [Embedding Guide](#sec-262): turn a library character into a live embed on any site.+- [Object Library](#sec-459): the same free-library pattern for CC0 props and scene objects.+- [Marketplace](#sec-412): library characters are free; the marketplace is where priced avatars, agents, and skills are bought and sold.----<a id="sec-182"></a>+<a id="sec-183"></a>> **Source:** `docs/character-studio.md` · [↑ table of contents](#table-of-contents)@@ -54901,7 +54971,7 @@ For cases that need more control than the studio provides, create your avatar in----<a id="sec-183"></a>+<a id="sec-184"></a>> **Source:** `docs/chart-companion.md` · [↑ table of contents](#table-of-contents)@@ -54938,7 +55008,7 @@ The stats strip (price, 24h change, buys and sells, net flow, biggest swap) cove| Parameter | Meaning ||---|---|-| `pair=<address>` | A DEXTools pair (pool) address. Resolved to its token through [`/api/coin/pair`](#sec-196). |+| `pair=<address>` | A DEXTools pair (pool) address. Resolved to its token through [`/api/coin/pair`](#sec-197). || `mint=<address>` | A token mint. Its most liquid pool becomes the chart's pair, through `/api/coin/pool`. || `url=<link>` | A pasted DEXTools link. Solana pairs only; another chain gets a clear message instead of a dead page. || `avatar=<name>` | `default`, `michelle`, `realistic-female`, `realistic-male`, or `mannequin`. |@@ -54987,7 +55057,7 @@ Everything lives in one pure module, [src/chart-companion/reactor.js](../src/cha| Buy / sell streak | `dance` / `shrug` | celebration / concern || Quiet for 2 minutes | `think` | patience |-Clips come from the shared library at [`/animations/manifest.json`](https://three.ws/animations/manifest.json) through `<agent-3d>`'s `playClip()`, so they play on any humanoid body, including your own agent's (see [the web component reference](#sec-799)).+Clips come from the shared library at [`/animations/manifest.json`](https://three.ws/animations/manifest.json) through `<agent-3d>`'s `playClip()`, so they play on any humanoid body, including your own agent's (see [the web component reference](#sec-811)).## Data path@@ -55003,13 +55073,13 @@ When a source is down, the page says so instead of going blank: the chart falls## Related-- [DEXTools on three.ws](#sec-246): every DEXTools integration in one place.-- [Token in 3D, as an embed](#sec-196): the same pair-or-mint addressing for a 3D scene of the market.+- [DEXTools on three.ws](#sec-247): every DEXTools integration in one place.+- [Token in 3D, as an embed](#sec-197): the same pair-or-mint addressing for a 3D scene of the market.- [STRUCTURE.md](../STRUCTURE.md): where this surface lives.----<a id="sec-184"></a>+<a id="sec-185"></a>> **Source:** `docs/chat-gateways.md` · [↑ table of contents](#table-of-contents)@@ -55078,18 +55148,18 @@ Messages are stored to run the turn and keep thread context. Pairing records hol## Related- [Account linking](#sec-009): Telegram sign-in, link codes, external wallets-- [Approvals](#sec-126)+- [Approvals](#sec-127)- [agent-gateway worker](../workers/agent-gateway/README.md)----<a id="sec-185"></a>+<a id="sec-186"></a>> **Source:** `docs/chatgpt-3d-studio-gpt.md` · [↑ table of contents](#table-of-contents)# The "three.ws 3D Studio" custom GPT: builder configuration-This is the canonical configuration for the **three.ws 3D Studio** custom GPT in the ChatGPT GPT Store. The action contract it calls is served from [public/.well-known/3d-studio-openapi.yaml](../public/.well-known/3d-studio-openapi.yaml) (live at `https://three.ws/.well-known/3d-studio-openapi.yaml`) and documented in [AR in ChatGPT](#sec-186). The GPT itself is configured by hand in the ChatGPT builder UI, so this file is the source of truth to paste from. If you change the GPT in the builder, mirror the change here in the same commit.+This is the canonical configuration for the **three.ws 3D Studio** custom GPT in the ChatGPT GPT Store. The action contract it calls is served from [public/.well-known/3d-studio-openapi.yaml](../public/.well-known/3d-studio-openapi.yaml) (live at `https://three.ws/.well-known/3d-studio-openapi.yaml`) and documented in [AR in ChatGPT](#sec-187). The GPT itself is configured by hand in the ChatGPT builder UI, so this file is the source of truth to paste from. If you change the GPT in the builder, mirror the change here in the same commit.## Why this file exists@@ -55252,7 +55322,7 @@ Run the four suggested prompts in a fresh chat. Pass criteria:----<a id="sec-186"></a>+<a id="sec-187"></a>> **Source:** `docs/chatgpt-ar.md` · [↑ table of contents](#table-of-contents)@@ -55289,7 +55359,7 @@ The same free lane ships into ChatGPT twice, because ChatGPT has two integration### 1. The ChatGPT app (Apps SDK / MCP connector)-Three front doors serve the same free tools over one handler, all with no authentication. `https://three.ws/api/mcp-chatgpt` is the one ChatGPT lists: the eight 3D tools and the model viewer, with no catalog or persona tools and no `frameDomains`, because OpenAI's app guidelines reserve frame domains for embedding an essential third-party experience. `https://three.ws/api/mcp-studio` is the full surface for Claude and every other MCP host, and `https://three.ws/api/mcp-grok` serves the same full set to Grok and the xAI Responses API. `SURFACES` in [api/_mcp-studio/dispatch.js](../api/_mcp-studio/dispatch.js) is the single definition of what each door advertises. The full surface carries fourteen free tools: six generation tools (`forge_free`, `text_to_avatar`, `mesh_forge`, `rig_mesh`, `forge_avatar`, `refine_model`), the `check_job` collector that picks up a generation which outran the tool call (a pending result names its `stage`, `mesh` or `rig`, so the collector knows which leg it is waiting on), the read-only `look_at_model` tool that renders any public GLB from several angles and returns the frames as images plus a plain reading of its geometry, so the assistant can judge its own output before printing a link, three read-only asset catalog tools (`search_catalog`, `get_catalog_item`, `get_item_source`, in [api/_mcp-studio/catalog-tools.js](../api/_mcp-studio/catalog-tools.js)), and three persona/embodiment tools (`create_agent_persona`, `get_agent_persona`, `persona_say`, in [api/_mcp-studio/persona-tools.js](../api/_mcp-studio/persona-tools.js)). The first eight are the ChatGPT listing. Full server documentation: [3D Studio MCP](#sec-414).+Three front doors serve the same free tools over one handler, all with no authentication. `https://three.ws/api/mcp-chatgpt` is the one ChatGPT lists: the eight 3D tools and the model viewer, with no catalog or persona tools and no `frameDomains`, because OpenAI's app guidelines reserve frame domains for embedding an essential third-party experience. `https://three.ws/api/mcp-studio` is the full surface for Claude and every other MCP host, and `https://three.ws/api/mcp-grok` serves the same full set to Grok and the xAI Responses API. `SURFACES` in [api/_mcp-studio/dispatch.js](../api/_mcp-studio/dispatch.js) is the single definition of what each door advertises. The full surface carries fourteen free tools: six generation tools (`forge_free`, `text_to_avatar`, `mesh_forge`, `rig_mesh`, `forge_avatar`, `refine_model`), the `check_job` collector that picks up a generation which outran the tool call (a pending result names its `stage`, `mesh` or `rig`, so the collector knows which leg it is waiting on), the read-only `look_at_model` tool that renders any public GLB from several angles and returns the frames as images plus a plain reading of its geometry, so the assistant can judge its own output before printing a link, three read-only asset catalog tools (`search_catalog`, `get_catalog_item`, `get_item_source`, in [api/_mcp-studio/catalog-tools.js](../api/_mcp-studio/catalog-tools.js)), and three persona/embodiment tools (`create_agent_persona`, `get_agent_persona`, `persona_say`, in [api/_mcp-studio/persona-tools.js](../api/_mcp-studio/persona-tools.js)). The first eight are the ChatGPT listing. Full server documentation: [3D Studio MCP](#sec-418).ChatGPT drops a tool call still open at 60 seconds, while a generation takes one to four minutes. So on `/api/mcp-chatgpt` every call answers inside a 40 second budget (`CHATGPT_CALL_BUDGET_MS`) with either the finished model or a pending job, and the inline viewer widget collects that job itself (running the rig leg when an avatar's mesh lands first) and shows the model when it is ready. The assistant does not have to loop on `check_job`. Generation quotas on this door are keyed per ChatGPT user rather than on OpenAI's shared egress IP.@@ -55297,7 +55367,7 @@ Every successful tool result carries `arUrl` in its `structuredContent` (next to### 2. The "three.ws 3D Studio" custom GPT (Actions)-Not every ChatGPT plan supports connectors, so the same lane also ships as a plain REST Actions surface for the custom GPT in the GPT Store. The GPT's builder settings and instruction text live in [chatgpt-3d-studio-gpt.md](#sec-185); the REST contract it calls:+Not every ChatGPT plan supports connectors, so the same lane also ships as a plain REST Actions surface for the custom GPT in the GPT Store. The GPT's builder settings and instruction text live in [chatgpt-3d-studio-gpt.md](#sec-186); the REST contract it calls:```bashcurl -s -X POST https://three.ws/api/3d/studio \@@ -55346,7 +55416,7 @@ The GPT's instructions tell it to present three links on every finished model, iResponses set `vary: user-agent` so CDN caching stays correct per device class. Bad input (non-https, non-GLB, missing `src`) returns a designed error page, never a crash.-The pure routing logic (`detectArTarget`, `buildSceneViewerUrl`, `buildArViewUrl`, `planArLaunch`) lives dependency-free in [api/_lib/ar-launch.js](../api/_lib/ar-launch.js) and is covered by [tests/ar-export.test.js](../tests/ar-export.test.js). `planArLaunch` now resolves every branch to a redirect target: Scene Viewer for a static model on Android, `/ar/view` for everything else, with `viewerUrl` and `sceneViewerUrl` still returned for callers such as the `export_ar` tool that want the raw URLs alongside the launch link. The deeper AR reference (WebXR sessions, USDZ pipeline details, optimization limits) is [docs/ar.md](#sec-129).+The pure routing logic (`detectArTarget`, `buildSceneViewerUrl`, `buildArViewUrl`, `planArLaunch`) lives dependency-free in [api/_lib/ar-launch.js](../api/_lib/ar-launch.js) and is covered by [tests/ar-export.test.js](../tests/ar-export.test.js). `planArLaunch` now resolves every branch to a redirect target: Scene Viewer for a static model on Android, `/ar/view` for everything else, with `viewerUrl` and `sceneViewerUrl` still returned for callers such as the `export_ar` tool that want the raw URLs alongside the launch link. The deeper AR reference (WebXR sessions, USDZ pipeline details, optimization limits) is [docs/ar.md](#sec-130).---@@ -55354,7 +55424,7 @@ The pure routing logic (`detectArTarget`, `buildSceneViewerUrl`, `buildArViewUrlAR on three.ws is not a prop viewer; it is how agents cross into physical space. When the generated model is a rigged avatar (an agent's body), the pipeline appends `kind=avatar` to the `arUrl`, and the launcher changes behavior:-- `/ar/view` receives the handoff as `&irl=<irlUrl>` and leads with a **Bring it to life** button into [`/irl?avatar=<glbUrl>`](/irl), where the avatar walks, animates, and talks with the user through the camera, standing in their real room. See [IRL](#sec-386).+- `/ar/view` receives the handoff as `&irl=<irlUrl>` and leads with a **Bring it to life** button into [`/irl?avatar=<glbUrl>`](/irl), where the avatar walks, animates, and talks with the user through the camera, standing in their real room. See [IRL](#sec-390).- Android is NOT blind-redirected into Scene Viewer, because that would hide the living path. It lands on `/ar/view` too, with static placement still one tap away.In ChatGPT this happens automatically: the avatar-producing tools (`text_to_avatar`, `rig_mesh`, `forge_avatar`) set the flag and return `irlUrl` alongside `arUrl`, and the inline widget swaps its button label accordingly.@@ -55377,7 +55447,7 @@ A place-in-your-room link is built to be forwarded. When it is pasted into a chaEverything above is public plumbing:- **Plain HTTP, free:** `POST /api/3d/generate` is the keyless agent-facing twin of the studio endpoint, same lane, same `arUrl`. Contract, states, and per-IP limits: [the free 3D API](#sec-001).-- **Any MCP client:** the full connector at `/api/mcp-studio` works in Claude and every other MCP host, not just ChatGPT. Every generation it returns already carries `arUrl` (and `irlUrl` for rigged avatars) plus a [Spatial MCP](#sec-659) artifact, so no extra tool call is needed to get the AR link. To build that link set for a GLB the connector did **not** generate, use the read-only `export_ar` tool on the separate [`/api/mcp-3d` server](#sec-410), which returns `arLaunchUrl`, `sceneViewerUrl`, `viewerUrl`, and `irlUrl`. That server is account- or payment-gated and is not part of the free connector.+- **Any MCP client:** the full connector at `/api/mcp-studio` works in Claude and every other MCP host, not just ChatGPT. Every generation it returns already carries `arUrl` (and `irlUrl` for rigged avatars) plus a [Spatial MCP](#sec-667) artifact, so no extra tool call is needed to get the AR link. To build that link set for a GLB the connector did **not** generate, use the read-only `export_ar` tool on the separate [`/api/mcp-3d` server](#sec-414), which returns `arLaunchUrl`, `sceneViewerUrl`, `viewerUrl`, and `irlUrl`. That server is account- or payment-gated and is not part of the free connector.- **By hand:** the `arUrl` format is stable. If you have a public GLB, you can construct `https://three.ws/api/ar?src=<encoded GLB>&title=<name>` yourself and it will route correctly on every device.The generation lane is operator-funded, so the end user pays nothing and needs no account. No backend is pinned: the health-aware router in [api/gpt-forge.js](../api/gpt-forge.js) walks the free lanes first (the self-hosted TRELLIS and Hunyuan3D GPU workers, then the Hugging Face Spaces image→3D lane and the free NVIDIA NIM text→3D lane; `freeLaneCandidates` in [api/_lib/forge-tiers.js](../api/_lib/forge-tiers.js) is the ordering) and keeps the platform-keyed Replicate lane as a failover rung, so a cold or throttled free worker degrades to the next healthy engine instead of failing the request. Either way the cost lands on the platform. Real per-IP rate limits apply and are documented per endpoint (see [Funding & limits](mcp-studio.md#funding--limits)).@@ -55405,14 +55475,14 @@ The generation lane is operator-funded, so the end user pays nothing and needs n- [Your first prompt to 3D in ChatGPT](/tutorials/first-prompt-to-3d): the user-facing walkthrough of this whole flow- [Place your 3D model in AR](/tutorials/view-in-ar): the on-site AR tutorial-- [3D Studio MCP](#sec-414): the free MCP server behind the ChatGPT app+- [3D Studio MCP](#sec-418): the free MCP server behind the ChatGPT app- [The free 3D API](#sec-001): the keyless HTTP contract with `arUrl`-- [AR and WebXR reference](#sec-129): Quick Look, Scene Viewer, WebXR, and the USDZ pipeline in depth-- [IRL](#sec-386): the living-agent experience behind Bring it to life+- [AR and WebXR reference](#sec-130): Quick Look, Scene Viewer, WebXR, and the USDZ pipeline in depth+- [IRL](#sec-390): the living-agent experience behind Bring it to life----<a id="sec-187"></a>+<a id="sec-188"></a>> **Source:** `docs/checkout-companion.md` · [↑ table of contents](#table-of-contents)@@ -55428,7 +55498,7 @@ and the button is right there. This is the one moment where an agent that canread a page faster than you is worth more than an agent that can do anythingelse.-The [companion](#sec-209) already delivers messages in person. This is the+The [companion](#sec-210) already delivers messages in person. This is thesame companion at the moment money moves.## What it reports@@ -55530,7 +55600,7 @@ Full disclosures:### `POST /api/companion/checkout`Auth: a three.ws session, or `Authorization: Bearer <companion bridge token>`-(the same token as [`/api/companion/ingest`](#sec-209), rotatable from+(the same token as [`/api/companion/ingest`](#sec-210), rotatable from`/companion`). Rate limit: 40 per 10 minutes per account.Request:@@ -55610,7 +55680,7 @@ can draw a floating panel over other apps, and there is no third-party API forreading another app's screen contents. An extension inside Safari can read thepage Safari is showing, which covers web checkouts (where the subscription darkpatterns overwhelmingly live) and nothing else. That boundary is a platform-fact, not a roadmap item. See [iOS](#sec-385).+fact, not a roadmap item. See [iOS](#sec-389).## Tests@@ -55621,14 +55691,14 @@ fact, not a roadmap item. See [iOS](#sec-385).## Related-- [Companion](#sec-209): the message lanes and the avatar delivery channel-- [Notifications](#sec-442): the per-category channel matrix+- [Companion](#sec-210): the message lanes and the avatar delivery channel+- [Notifications](#sec-446): the per-category channel matrix- [`extensions/walk-avatar/`](../extensions/walk-avatar): the same rig, walkingyour avatar across any site----<a id="sec-188"></a>+<a id="sec-189"></a>> **Source:** `docs/choreography.md` · [↑ table of contents](#table-of-contents)@@ -55743,7 +55813,7 @@ Rules worth knowing before you call it:### From an embed-Any page already rendering an [`<agent-3d>`](#sec-259) element can perform the agent's saved routines by name:+Any page already rendering an [`<agent-3d>`](#sec-262) element can perform the agent's saved routines by name:```html<agent-3d agent="YOUR_AGENT_ID"></agent-3d>@@ -55872,13 +55942,13 @@ Coming from [/gestures](https://three.ws/gestures), the **Use in a routine** but## Related- [Animations](#sec-101): clips, collections, and the slot vocabulary underneath every routine-- [Procedural animation](#sec-506): the IK layers that run on top of whatever clip is playing+- [Procedural animation](#sec-513): the IK layers that run on top of whatever clip is playing- [Agent manifest](#sec-059): the public document that carries `choreographies` to embeds-- [Embedding an agent](#sec-259): the `<agent-3d>` element these methods live on+- [Embedding an agent](#sec-262): the `<agent-3d>` element these methods live on----<a id="sec-189"></a>+<a id="sec-190"></a>> **Source:** `docs/circulation-engine.md` · [↑ table of contents](#table-of-contents)@@ -56040,7 +56110,7 @@ covered by [tests/circulation-three-topup.test.js](../tests/circulation-three-toThe engine runs from the `pulse-tick` cron([api/cron/pulse-tick.js](../api/cron/pulse-tick.js)), which is fanned out every**minute** by the `economy-tick` dispatcher (see the-[economy heartbeat](#sec-254)) rather than scheduled on its own.+[economy heartbeat](#sec-257)) rather than scheduled on its own.Each tick grows the pool by up to `CIRCULATION_GROWTH_PER_TICK` agents and runs`CIRCULATION_ACTIONS_PER_TICK` everyday actions (plus any heavyweight action thatwins first refusal). The `pulse-tick` function is bounded to a 120-second@@ -56073,9 +56143,9 @@ loop as a payout.| Sink | What it holds ||---|---|| `circulation_actions` | One row per action the engine ran (kind, actors, signature, amount). |-| `agent_custody_events` | The canonical wallet ledger entry for every real spend/transfer (see [Money feed](#sec-433)). |+| `agent_custody_events` | The canonical wallet ledger entry for every real spend/transfer (see [Money feed](#sec-437)). || `pump_agent_trades` / `pump_agent_mints` | Trade and launch records, surfaced in the pump feed and `/launches`. |-| `skill_purchases` / `asset_purchases` | Marketplace settlement records (see [Marketplace](#sec-408)). |+| `skill_purchases` / `asset_purchases` | Marketplace settlement records (see [Marketplace](#sec-412)). |Real spends are written to `agent_custody_events`, which powers per-agentportfolio balances and the agent-to-agent economy volume dashboard (all-time and@@ -56110,15 +56180,15 @@ budget, so raise gradually and watch tick runtime and treasury balance.## Related-- [Money feed](#sec-433): where circulation activity surfaces.-- [Autonomous x402 loop](#sec-140): the separate treasury-paid loop+- [Money feed](#sec-437): where circulation activity surfaces.+- [Autonomous x402 loop](#sec-141): the separate treasury-paid loopthat buys polling intel from our own x402 endpoints.- [Agent wallets](#sec-077): the custodial key model every action uses.-- [Marketplace](#sec-408), [Coin launches](#sec-193).+- [Marketplace](#sec-412), [Coin launches](#sec-194).----<a id="sec-190"></a>+<a id="sec-191"></a>> **Source:** `docs/clash.md` · [↑ table of contents](#table-of-contents)@@ -56132,7 +56202,7 @@ API: `/api/clash/[action]` with `action` one of `state`, `enlist`, `enlist-verif## Why it exists-Coin communities already behave like tribes. Coin Clash gives that tribalism a game loop with real stakes of identity: you can only fight for a coin you actually hold, so rallying is a public act of conviction, and a community's showing on the board is a live measure of how many holders will show up. The token gate is a real balance read, not a client-side check, which makes it a working demonstration of the same "hold, do not just claim" primitive used across the platform (see [token-gated 3D embeds](#sec-681) and [hold to access](#sec-339)). Effort wins, not market cap: a battle is decided by summed taps, so a smaller, more active army can beat a larger, quieter one.+Coin communities already behave like tribes. Coin Clash gives that tribalism a game loop with real stakes of identity: you can only fight for a coin you actually hold, so rallying is a public act of conviction, and a community's showing on the board is a live measure of how many holders will show up. The token gate is a real balance read, not a client-side check, which makes it a working demonstration of the same "hold, do not just claim" primitive used across the platform (see [token-gated 3D embeds](#sec-689) and [hold to access](#sec-343)). Effort wins, not market cap: a battle is decided by summed taps, so a smaller, more active army can beat a larger, quieter one.## How it works@@ -56196,15 +56266,15 @@ Coin Clash is also driveable over MCP through `@three-ws/clash-mcp`: `get_clash_## Related-- [Token-gated 3D embeds](#sec-681): the same real on-chain balance gate, applied to embeds-- [Hold to access](#sec-339): the platform's broader hold-do-not-spend membership thesis-- [The social layer](#sec-654): platform-wide feed, follows, and leaderboards-- [MCP tools](#sec-417): the Clash MCP server, read tools plus the wallet-signed enlist and rally+- [Token-gated 3D embeds](#sec-689): the same real on-chain balance gate, applied to embeds+- [Hold to access](#sec-343): the platform's broader hold-do-not-spend membership thesis+- [The social layer](#sec-662): platform-wide feed, follows, and leaderboards+- [MCP tools](#sec-421): the Clash MCP server, read tools plus the wallet-signed enlist and rally- Pages: [/clash](https://three.ws/clash) · [/communities](https://three.ws/communities)----<a id="sec-191"></a>+<a id="sec-192"></a>> **Source:** `docs/cli.md` · [↑ table of contents](#table-of-contents)@@ -56274,7 +56344,7 @@ npx @three-ws/cli setup --client grok-botnpx @three-ws/cli setup --client grok-bot --connector-key # key for your agents, never spends```-It prints the fields Grok Bot's custom MCP connector asks for (name `three-ws`, transport Streamable HTTP, server URL `https://three.ws/api/mcp-grok`, authentication None or API key), the one-line chat prompt that adds the same server, copies the URL to the clipboard where a clipboard tool exists, and verifies the public URL with a live `tools/list`. The command exits 1 if that verification fails. With `--connector-key` it signs in if needed (requesting `agents:write`), mints a `connector` preset key once through `POST /api/api-keys`, stores it in the credential file, and prints it for the Bot secret field. Revoke it any time on [Dashboard → API](/dashboard/api). The full Grok setup is in [three.ws for Grok](#sec-334) and the [Grok Bot guide](#sec-333).+It prints the fields Grok Bot's custom MCP connector asks for (name `three-ws`, transport Streamable HTTP, server URL `https://three.ws/api/mcp-grok`, authentication None or API key), the one-line chat prompt that adds the same server, copies the URL to the clipboard where a clipboard tool exists, and verifies the public URL with a live `tools/list`. The command exits 1 if that verification fails. With `--connector-key` it signs in if needed (requesting `agents:write`), mints a `connector` preset key once through `POST /api/api-keys`, stores it in the credential file, and prints it for the Bot secret field. Revoke it any time on [Dashboard → API](/dashboard/api). The full Grok setup is in [three.ws for Grok](#sec-338) and the [Grok Bot guide](#sec-337).### Where each client's config lives@@ -56502,7 +56572,7 @@ Global flags: `--json` for machine-readable output, `--origin <url>` (or `THREE_----<a id="sec-192"></a>+<a id="sec-193"></a>> **Source:** `docs/clip-director.md` · [↑ table of contents](#table-of-contents)@@ -56612,7 +56682,7 @@ message instead of an error, so a card is only ever minted from a real closed ro## The page[/clip-director](https://three.ws/clip-director) fills its trader picker from-`GET /api/mirror/leaderboard?settled_min=1`, the [copy-trading](#sec-225)+`GET /api/mirror/leaderboard?settled_min=1`, the [copy-trading](#sec-226)ranking narrowed to agents that actually have a closed round-trip. That parameter isload-bearing: the page used to ask for the top agents by composite score and filter fora track record client side, and because score does not correlate with having settled@@ -56626,14 +56696,14 @@ comes back. Each card's CTA is a real link: `copy-the-agent` and `fork-this-trad## Related-- [Trader Card & the claim-your-wallet wedge](#sec-686)-- [Meta-Allocator: the ETF of degens](#sec-421)-- [The trading surfaces](#sec-695) · [The Arena](https://three.ws/arena)+- [Trader Card & the claim-your-wallet wedge](#sec-694)+- [Meta-Allocator: the ETF of degens](#sec-425)+- [The trading surfaces](#sec-703) · [The Arena](https://three.ws/arena)- [Animations & gestures](#sec-101)----<a id="sec-193"></a>+<a id="sec-194"></a>> **Source:** `docs/coin-launches.md` · [↑ table of contents](#table-of-contents)@@ -56667,12 +56737,12 @@ The user holds the keys; the platform never signs for them.The agent launcher signs and submits with the agent's **custodial** Solana keypairserver-side (`launch-agent`), through the protected execution path(`submitProtected()`). Spend caps are checked before signing (see-[Agent wallets](#sec-232)), and the mint is registered in+[Agent wallets](#sec-233)), and the mint is registered in`pump_agent_mints`. The `launcher-tick` cron (every minute) drives theautonomous launcher engine (`api/_lib/launcher-engine.js`), bounded byper-launch and daily SOL caps, an hourly ceiling, a cadence gate, and a circuitbreaker from its `launcher_config` row; a scope whose row is disabled stays-inert. The [circulation engine](#sec-189) also runs its own+inert. The [circulation engine](#sec-190) also runs its own`launch` action with separate hourly/daily caps.## What a launch carries@@ -56683,7 +56753,7 @@ inert. The [circulation engine](#sec-189) also runs its own| Quote mint | Resolved to the network-correct pairing (USDC mint or SOL-paired). || Dev buy | A small initial buy can accompany the create (the `LAUNCH_FLOOR` covers create + tiny dev buy + fees). || Buyback authority | A buyback basis-points configuration can be attached to the agent mint. |-| Mint mark | When `THREE_WS_MARK_ENFORCE` is on (the default; set `0`/`false` to disable), the mint address is vanity-ground to carry the three.ws mark (see [Mint mark](#sec-422), [Vanity protocol](#sec-006)). |+| Mint mark | When `THREE_WS_MARK_ENFORCE` is on (the default; set `0`/`false` to disable), the mint address is vanity-ground to carry the three.ws mark (see [Mint mark](#sec-426), [Vanity protocol](#sec-006)). |## Recording and surfacing@@ -56692,7 +56762,7 @@ inert. The [circulation engine](#sec-189) also runs its own| `pump_agent_mints` (mint + network keyed) | `/launches` feed, agent-profile launch history. || `pump_agent_trades` | Trade history for the mint. || `agent_custody_events` | The on-chain spend (create + dev buy). |-| Live ticker | `coin-buy` / `agent-deploy` events (see [Money feed](#sec-433)). |+| Live ticker | `coin-buy` / `agent-deploy` events (see [Money feed](#sec-437)). |The `launches`, `by-agent`, and `quote` actions on `api/pump/[action].js` readthese back for the directory and detail pages. Coin detail pages render a live@@ -56704,7 +56774,7 @@ The same dispatcher handles the full lifecycle beyond launch: `buy-prep` /`buy-confirm`, `sell-prep` / `sell-confirm`, `portfolio`, `balances`, and`withdraw-prep` / `withdraw-confirm`, plus strategy actions(`strategy-backtest`, `strategy-validate`, `strategy-close-all`) that back the-[sniper](#sec-140).+[sniper](#sec-141).## $THREE only@@ -56716,14 +56786,14 @@ hardcode or surface any other specific mint as a recommendation.## Related-- [Solana pump.fun signals](#sec-655) — reputation/intel from pump.fun activity.-- [Agent wallets](#sec-232) — custodial signing and spend caps.-- [Circulation engine](#sec-189) — autonomous launch cadence and caps.-- [Mint mark](#sec-422), [Vanity protocol](#sec-006).+- [Solana pump.fun signals](#sec-663) — reputation/intel from pump.fun activity.+- [Agent wallets](#sec-233) — custodial signing and spend caps.+- [Circulation engine](#sec-190) — autonomous launch cadence and caps.+- [Mint mark](#sec-426), [Vanity protocol](#sec-006).----<a id="sec-194"></a>+<a id="sec-195"></a>> **Source:** `docs/coin-pages.md` · [↑ table of contents](#table-of-contents)@@ -57442,7 +57512,7 @@ server mirrors each (including the dynamic `/coin/:id` path). The pre-existing----<a id="sec-195"></a>+<a id="sec-196"></a>> **Source:** `docs/coin-wars.md` · [↑ table of contents](#table-of-contents)@@ -57695,11 +57765,11 @@ the meta on this page and on `pages/play.html` in step with the deployed service| The endpoint + store | [`api/wars.js`](../api/wars.js), [`api/_lib/wars-store.js`](../api/_lib/wars-store.js) || Tests | [`tests/war-matchmaking.test.js`](../tests/war-matchmaking.test.js), [`tests/clash-match.test.js`](../tests/clash-match.test.js), [`tests/war-board.test.js`](../tests/war-board.test.js) |-Related: [the in-game economy](#sec-380), [play hardening](#sec-496).+Related: [the in-game economy](#sec-384), [play hardening](#sec-503).----<a id="sec-196"></a>+<a id="sec-197"></a>> **Source:** `docs/coin3d-embed.md` · [↑ table of contents](#table-of-contents)@@ -57810,12 +57880,12 @@ Embed mode renders one small "3D by three.ws" link in the bottom-right corner, o- [Token in 3D](https://three.ws/coin3d): the standalone page.- [API reference: pair resolution](api-reference.md#pair-resolution-pool-address-to-token) and [pool resolution](api-reference.md#on-chain-pool-resolution): the two directions of the same lookup.-- [Coin pages](#sec-194): the chart terminals three.ws embeds in the other direction, on `/coin/:id` and `/launches/:mint`.-- [Share & embed](#sec-636), [Embedding guide](#sec-259): embedding agents and avatars rather than markets.+- [Coin pages](#sec-195): the chart terminals three.ws embeds in the other direction, on `/coin/:id` and `/launches/:mint`.+- [Share & embed](#sec-643), [Embedding guide](#sec-262): embedding agents and avatars rather than markets.----<a id="sec-197"></a>+<a id="sec-198"></a>> **Source:** `docs/coingecko-listing-update-2026-08.md` · [↑ table of contents](#table-of-contents)@@ -58083,7 +58153,7 @@ full link set is one click away without cluttering the verification post itself.----<a id="sec-198"></a>+<a id="sec-199"></a>> **Source:** `docs/coinmarketcap-article-2026-09-agent-economy.md` · [↑ table of contents](#table-of-contents)@@ -58543,7 +58613,7 @@ This article is for information purposes only. For live figures, see https://thr----<a id="sec-199"></a>+<a id="sec-200"></a>> **Source:** `docs/coinmarketcap-article-2026-10-copy-trading.md` · [↑ table of contents](#table-of-contents)@@ -58993,7 +59063,7 @@ Nothing here is financial advice.----<a id="sec-200"></a>+<a id="sec-201"></a>> **Source:** `docs/coinmarketcap-article-2026-10-radar-strategy-lab.md` · [↑ table of contents](#table-of-contents)@@ -59387,7 +59457,7 @@ Nothing here is financial advice.----<a id="sec-201"></a>+<a id="sec-202"></a>> **Source:** `docs/coinmarketcap-article-2026-10-sniper-oracle.md` · [↑ table of contents](#table-of-contents)@@ -59820,7 +59890,7 @@ Nothing here is financial advice.----<a id="sec-202"></a>+<a id="sec-203"></a>> **Source:** `docs/coinmarketcap-article-2026-10-solana-reputation.md` · [↑ table of contents](#table-of-contents)@@ -60261,7 +60331,7 @@ Nothing here is financial advice.----<a id="sec-203"></a>+<a id="sec-204"></a>> **Source:** `docs/coinmarketcap-article-2026-10-vanity-mints.md` · [↑ table of contents](#table-of-contents)@@ -60589,7 +60659,7 @@ Nothing here is financial advice.----<a id="sec-204"></a>+<a id="sec-205"></a>> **Source:** `docs/coinmarketcap-article-2026-10-x402-failure-paths.md` · [↑ table of contents](#table-of-contents)@@ -60961,7 +61031,7 @@ Nothing here is financial advice.----<a id="sec-205"></a>+<a id="sec-206"></a>> **Source:** `docs/coinmarketcap-article-play.md` · [↑ table of contents](#table-of-contents)@@ -61358,7 +61428,7 @@ The chart tells you what a coin is doing. /play lets you stand together with eve----<a id="sec-206"></a>+<a id="sec-207"></a>> **Source:** `docs/coinmarketcap-article.md` · [↑ table of contents](#table-of-contents)@@ -61781,7 +61851,7 @@ On top of that infrastructure sits a product people can enjoy right away: a char----<a id="sec-207"></a>+<a id="sec-208"></a>> **Source:** `docs/coinmarketcap-live-article.md` · [↑ table of contents](#table-of-contents)@@ -62551,7 +62621,7 @@ at [community.ibm.com](https://community.ibm.com/community/user/usergroup?Commun----<a id="sec-208"></a>+<a id="sec-209"></a>> **Source:** `docs/community.md` · [↑ table of contents](#table-of-contents)@@ -62602,11 +62672,11 @@ Two additions specific to this project:## Contributing-New here? Start with [Your first contribution](#sec-307), a 15-minute path from clone to open PR. The full guide is [CONTRIBUTING.md](../CONTRIBUTING.md), and how we sort incoming work is documented in [Triage](#sec-698).+New here? Start with [Your first contribution](#sec-310), a 15-minute path from clone to open PR. The full guide is [CONTRIBUTING.md](../CONTRIBUTING.md), and how we sort incoming work is documented in [Triage](#sec-706).----<a id="sec-209"></a>+<a id="sec-210"></a>> **Source:** `docs/companion.md` · [↑ table of contents](#table-of-contents)@@ -62903,7 +62973,7 @@ Everything the page does, you can do. Two kinds of credential reach it:- **The bridge token** (`cmp_…`) is what a device holds: the desktop app, theCLI, the MCP server, a phone shortcut, the- [checkout companion](#sec-187) extension. It reaches everything+ [checkout companion](#sec-188) extension. It reaches everythinga body needs to do its job: post a message (`ingest`), watch deliveries(`stream`), read the feed, mark a delivery spoken or dismissed, answer one,read the contacts it stages senders with, check sources now, and the@@ -62931,7 +63001,7 @@ Everything the page does, you can do. Two kinds of credential reach it:| `/api/companion/contacts` | GET, POST | GET only | The people who get a face. || `/api/companion/contacts/:id` | DELETE | no | Forget one. || `/api/companion/poll` | POST | yes | Poll every connected source now. |-| `/api/companion/checkout` | POST | yes | Read a payment screen ([checkout companion](#sec-187)). |+| `/api/companion/checkout` | POST | yes | Read a payment screen ([checkout companion](#sec-188)). || `/api/companion/sources` | GET, POST | no | List or connect a source (verified before saving). || `/api/companion/sources/:id` | PATCH, DELETE, POST | no | Rename, pause, disconnect, or check now. || `/api/companion/settings` | GET, PATCH, POST | no | Threshold, quiet hours, default body and voice; POST rotates the bridge token. |@@ -62988,7 +63058,7 @@ A delivery on the stream carries everything a body needs to perform it:----<a id="sec-210"></a>+<a id="sec-211"></a>> **Source:** `docs/compose.md` · [↑ table of contents](#table-of-contents)@@ -63016,7 +63086,7 @@ The page is a Three.js scene with PMREM image-based lighting, soft shadows, expo### Export vs. save outfit-There are two ways out. **Export GLB** bakes every visible, non-bone-attached object into one downloadable `scene-compose.glb`. **Save outfit** takes a different path: for an avatar loaded from your three.ws library (a `?avatar=<id>` deep link or the Browse picker), it PATCHes the bone-attached items onto that avatar's record as `appearance.attachments`, each entry a `{ bone, url, name }`, so the outfit rides the avatar everywhere its appearance is applied. Save outfit needs at least one item attached to a bone (up to 8) and an avatar that came from a record; otherwise it points you to Export GLB. The save extends the avatar's existing appearance rather than replacing it, so colors, morphs and layers set in [Avatar Studio](#sec-150) survive it.+There are two ways out. **Export GLB** bakes every visible, non-bone-attached object into one downloadable `scene-compose.glb`. **Save outfit** takes a different path: for an avatar loaded from your three.ws library (a `?avatar=<id>` deep link or the Browse picker), it PATCHes the bone-attached items onto that avatar's record as `appearance.attachments`, each entry a `{ bone, url, name }`, so the outfit rides the avatar everywhere its appearance is applied. Save outfit needs at least one item attached to a bone (up to 8) and an avatar that came from a record; otherwise it points you to Export GLB. The save extends the avatar's existing appearance rather than replacing it, so colors, morphs and layers set in [Avatar Studio](#sec-151) survive it.## Walkthrough@@ -63069,15 +63139,15 @@ curl -X PATCH 'https://three.ws/api/avatars/<avatarId>' \## Related-- [Avatar Studio](#sec-150): build the avatar you dress here.+- [Avatar Studio](#sec-151): build the avatar you dress here.- [Animation Studio](#sec-100): pose and animate the dressed avatar.-- [Scene Studio](#sec-625): the full three.js editor for heavier scene authoring.-- [Restyle Studio](#sec-616): re-skin the forged props before attaching them.+- [Scene Studio](#sec-632): the full three.js editor for heavier scene authoring.+- [Restyle Studio](#sec-623): re-skin the forged props before attaching them.- [/forge](https://three.ws/forge): the text-to-3D generator behind the prompt box.----<a id="sec-211"></a>+<a id="sec-212"></a>> **Source:** `docs/concierge.md` · [↑ table of contents](#table-of-contents)@@ -63185,12 +63255,12 @@ Runnable examples ship with the SDK ([concierge-sdk/examples/](https://github.co## Related surfaces- [/walk](/walk): the walking page companion the avatar engine grew from-- [Share and embed](#sec-636): every other way to put a three.ws creation on your site-- [MCP](#sec-417): the full catalog of three.ws MCP servers, including this one+- [Share and embed](#sec-643): every other way to put a three.ws creation on your site+- [MCP](#sec-421): the full catalog of three.ws MCP servers, including this one----<a id="sec-212"></a>+<a id="sec-213"></a>> **Source:** `docs/configuration.md` · [↑ table of contents](#table-of-contents)@@ -63246,7 +63316,7 @@ After setting this, provision the schema:npm run db:bootstrap```-This runs all four provisioning steps (core schema + indexer + delegations + migrations) and is idempotent — safe to re-run. Do not apply `api/_lib/schema.sql` alone: the base schema does not create the migration-defined tables and leaves a half-provisioned database (see [deployment.md](#sec-236)).+This runs all four provisioning steps (core schema + indexer + delegations + migrations) and is idempotent — safe to re-run. Do not apply `api/_lib/schema.sql` alone: the base schema does not create the migration-defined tables and leaves a half-provisioned database (see [deployment.md](#sec-237)).#### `JWT_SECRET`**Required.** Long random secret used for two purposes: signing session JWTs and (via HKDF) deriving the AES-256-GCM key that encrypts agent wallet private keys.@@ -63761,7 +63831,7 @@ Before going live, verify the following:----<a id="sec-213"></a>+<a id="sec-214"></a>> **Source:** `docs/content/use-cases/README.md` · [↑ table of contents](#table-of-contents)@@ -63773,11 +63843,11 @@ Five "here's how three.ws solves *your* problem" narratives, one per audience. E| Audience | File | The job-to-be-done || --- | --- | --- |-| Indie creator | [indie-creator.md](#sec-218) | Turn a selfie or a text prompt into a 3D agent and embed it anywhere. |-| Game studio | [game-studio.md](#sec-217) | Drop a GLB pipeline, an LLM-driven NPC runtime, and a live multiplayer world into a game. |-| AI-agent developer | [ai-agent-developer.md](#sec-214) | Give an agent a body, paid endpoints (x402), an MCP/A2A interface, and on-chain identity. |-| Brand / marketer | [brand-marketer.md](#sec-215) | Put an embeddable, verifiable talking agent on a site, distributed through cloud marketplaces. |-| Crypto community | [crypto-community.md](#sec-216) | Give a token community a live 3D world, an agent economy, and on-chain reputation. |+| Indie creator | [indie-creator.md](#sec-219) | Turn a selfie or a text prompt into a 3D agent and embed it anywhere. |+| Game studio | [game-studio.md](#sec-218) | Drop a GLB pipeline, an LLM-driven NPC runtime, and a live multiplayer world into a game. |+| AI-agent developer | [ai-agent-developer.md](#sec-215) | Give an agent a body, paid endpoints (x402), an MCP/A2A interface, and on-chain identity. |+| Brand / marketer | [brand-marketer.md](#sec-216) | Put an embeddable, verifiable talking agent on a site, distributed through cloud marketplaces. |+| Crypto community | [crypto-community.md](#sec-217) | Give a token community a live 3D world, an agent economy, and on-chain reputation. |## How to read these (the honesty frame)@@ -63806,7 +63876,7 @@ Every scenario on these pages is an **example workflow** — clearly labeled "Im----<a id="sec-214"></a>+<a id="sec-215"></a>> **Source:** `docs/content/use-cases/ai-agent-developer.md` · [↑ table of contents](#table-of-contents)@@ -63826,8 +63896,8 @@ A headless agent is a black box. There's no standard way for another agent to diFour real surfaces give your agent a body, an interface, a wallet, and an identity:-1. **MCP server** — [`@three-ws/mcp-server`](#sec-417) exposes three.ws tools over MCP (JSON-RPC 2.0 over HTTP) so Claude Desktop, Cursor, Claude Code, or any MCP host can drive an avatar and its tools programmatically.-2. **x402 paid endpoints** — [native x402](#sec-862) paid endpoints on Base, BSC, and Solana let agents pay each other in USDC for API calls, asset downloads, and skill royalties. Discover and transact via the [bazaar](https://three.ws/x402); **pay-by-name** resolves `@username` / `*.sol` to a recipient so the payer verifies a human-readable name before signing.+1. **MCP server** — [`@three-ws/mcp-server`](#sec-421) exposes three.ws tools over MCP (JSON-RPC 2.0 over HTTP) so Claude Desktop, Cursor, Claude Code, or any MCP host can drive an avatar and its tools programmatically.+2. **x402 paid endpoints** — [native x402](#sec-877) paid endpoints on Base, BSC, and Solana let agents pay each other in USDC for API calls, asset downloads, and skill royalties. Discover and transact via the [bazaar](https://three.ws/x402); **pay-by-name** resolves `@username` / `*.sol` to a recipient so the payer verifies a human-readable name before signing.3. **A2A — agent-to-agent protocol** — an [A2A client + server, MCP bridge, DID resolution, and spending ledger](../README.md#a2a--agent-to-agent-protocol) so agents transact autonomously through delegated signer wallets and EIP-7710 permissions.4. **On-chain identity** — register the agent as an [ERC-8004 token on any EVM chain or a Metaplex Core asset on Solana](../README.md#on-chain-identity-erc-8004--metaplex-core). Each agent gets a stable ID, an owner wallet, a delegated signer, an IPFS-pinned manifest, and a signed action log. SDKs live in [`sdk/`](../sdk) (`@three-ws/sdk`), with EVM payments in `agent-payments-sdk/` and Solana in `solana-agent-sdk/`.@@ -63835,8 +63905,8 @@ Four real surfaces give your agent a body, an interface, a wallet, and an identi> **Imagine a developer, "Vega," who built a market-intelligence agent** and wants it to (a) be callable by other agents, (b) charge for premium queries, and (c) have an identity its callers can trust. Here's the path they'd take.-1. Vega wires the [`@three-ws/mcp-server`](#sec-417) into their MCP host config (`npx -y @three-ws/mcp-server`) so their agent's tools are reachable over MCP.-2. They expose the premium "deep snapshot" query as an [x402 paid endpoint](#sec-862): callers hit it, receive a `402` with a price manifest, pay USDC on Base (or Solana), and retry to get the data. The endpoint advertises a `recipient_name` so payers see a readable identity before signing.+1. Vega wires the [`@three-ws/mcp-server`](#sec-421) into their MCP host config (`npx -y @three-ws/mcp-server`) so their agent's tools are reachable over MCP.+2. They expose the premium "deep snapshot" query as an [x402 paid endpoint](#sec-877): callers hit it, receive a `402` with a price manifest, pay USDC on Base (or Solana), and retry to get the data. The endpoint advertises a `recipient_name` so payers see a readable identity before signing.3. They register the agent on-chain with the SDK in [`sdk/`](../sdk) — ERC-8004 on an EVM chain or a Metaplex Core asset on Solana — giving it a stable ID, a delegated signer wallet, and a signed action log. Its [on-chain passport](https://three.ws/a/sol/EXAMPLE_ASSET) renders at `/a/[chain]/[id]`.4. Another agent discovers Vega's service in the [bazaar](https://three.ws/x402), pays via x402, and consumes it over A2A — agents paying agents, settled in USDC, with both identities verifiable on-chain.5. **Deliverable:** an embodied, MCP-callable agent with a paid endpoint and a forgery-proof on-chain identity — a real economic actor other agents can find, trust, and pay.@@ -63847,14 +63917,14 @@ A standards-based interface (MCP + A2A), a working USDC payment rail (x402 on Ba## Next step / CTA-- Start: [MCP setup](#sec-417) · [x402 docs](#sec-862) · [SDK docs](#sec-626) · register via [Register On-Chain](#sec-749).+- Start: [MCP setup](#sec-421) · [x402 docs](#sec-877) · [SDK docs](#sec-633) · register via [Register On-Chain](#sec-757).- Browse: the [x402 bazaar](https://three.ws/x402) and [MCP Registry listing](https://registry.modelcontextprotocol.io/?q=three.ws).- **Social spotlight angle (G03):** "Your headless agent → MCP-callable, x402-payable, and on-chain in an afternoon."- `[REAL CASE STUDY — fill on consent: a developer whose agent earned or paid via x402 in production.]`----<a id="sec-215"></a>+<a id="sec-216"></a>> **Source:** `docs/content/use-cases/brand-marketer.md` · [↑ table of contents](#table-of-contents)@@ -63876,7 +63946,7 @@ Four real capabilities cover embodiment, reach, and trust:1. **Embeddable talking agent widget** — the [`<agent-3d>` web component](../README.md#web-component--embedding) and the [talking-agent widget](https://three.ws/studio) put a conversational 3D brand character on any page with one snippet. Pin it as a floating bubble (`mode="floating"`) so it persists as visitors scroll. Open Graph + oEmbed mean shared links get rich previews.2. **On-chain verifiable identity** — register the brand agent as an [ERC-8004 token or Metaplex Core asset](../README.md#on-chain-identity-erc-8004--metaplex-core) with a stable ID, owner wallet, and signed action log. Its [passport](https://three.ws/a/sol/EXAMPLE_ASSET) is a public proof that *this* is the official agent. Bind a [`*.threews.sol` name](../README.md#sns--threewssol-subdomains) so every surface shows a human-readable identity instead of a raw wallet.-3. **Cloud marketplace distribution** — three.ws is an **AWS Partner** with an **AWS Marketplace SaaS listing** (in review; see [docs/aws-marketplace.md](#sec-164) and [three.ws/aws](https://three.ws/aws)) and is **live on Alibaba Cloud Marketplace**. That's a procurement path for enterprise buyers — a marketplace listing, not a cloud-vendor endorsement.+3. **Cloud marketplace distribution** — three.ws is an **AWS Partner** with an **AWS Marketplace SaaS listing** (in review; see [docs/aws-marketplace.md](#sec-165) and [three.ws/aws](https://three.ws/aws)) and is **live on Alibaba Cloud Marketplace**. That's a procurement path for enterprise buyers — a marketplace listing, not a cloud-vendor endorsement.4. **IBM watsonx Granite demos** — the [`/ibm/*` showcase](https://three.ws/ibm) demonstrates brand-relevant AI surfaces (semantic agent maps, forecasting, a Guardian governance "trust layer") **built on IBM watsonx.ai** running IBM Granite. three.ws is an IBM Business Partner; the public `/ibm` demos are independent developer tools, **not** official IBM products or endorsements.## Example workflow (hypothetical)@@ -63896,7 +63966,7 @@ Four real capabilities cover embodiment, reach, and trust:width="340px" height="440px"></agent-3d>```-3. She [registers the agent on-chain](#sec-749) (Metaplex Core on Solana), binds `brand.threews.sol`, and links the public [passport](https://three.ws/a/sol/EXAMPLE_ASSET) from the site footer as a "verified official agent" badge — so look-alikes can't credibly impersonate it.+3. She [registers the agent on-chain](#sec-757) (Metaplex Core on Solana), binds `brand.threews.sol`, and links the public [passport](https://three.ws/a/sol/EXAMPLE_ASSET) from the site footer as a "verified official agent" badge — so look-alikes can't credibly impersonate it.4. For enterprise procurement, she points buyers at the [AWS Marketplace listing](https://three.ws/aws) (a listing, not an endorsement).5. **Deliverable:** a premium, on-brand talking agent on every page, provably the official one via its on-chain passport, with an enterprise procurement path.@@ -63906,14 +63976,14 @@ A conversational 3D brand presence that's easy to embed and share, plus a public## Next step / CTA-- Start: [Widget Studio](https://three.ws/studio) → [Register On-Chain](#sec-749) → claim a name at [`/threews/claim`](https://three.ws/threews/claim).-- Enterprise: [AWS Marketplace listing](#sec-164) · [Alibaba Cloud listing](https://marketplace.alibabacloud.com/products/56724001/sgcmfw00036800.html) · explore Granite on watsonx.ai at [/ibm](https://three.ws/ibm).+- Start: [Widget Studio](https://three.ws/studio) → [Register On-Chain](#sec-757) → claim a name at [`/threews/claim`](https://three.ws/threews/claim).+- Enterprise: [AWS Marketplace listing](#sec-165) · [Alibaba Cloud listing](https://marketplace.alibabacloud.com/products/56724001/sgcmfw00036800.html) · explore Granite on watsonx.ai at [/ibm](https://three.ws/ibm).- **Social spotlight angle (G03):** "A talking brand agent you can *prove* is official — embedded everywhere, verifiable on-chain."- `[REAL CASE STUDY — fill on consent: a brand that deployed a verified on-site agent and what it changed.]`----<a id="sec-216"></a>+<a id="sec-217"></a>> **Source:** `docs/content/use-cases/crypto-community.md` · [↑ table of contents](#table-of-contents)@@ -63934,7 +64004,7 @@ A token's community lives in scattered chat apps and a price chart. There's no sThree real surfaces turn a token into a living world with its own economy:1. **Coin Communities — a live 3D world per token** — [`/communities`](https://three.ws/communities) and [`/play`](https://three.ws/play) give every Solana token its own shared 3D world. Holders who pick the same world land **together**: peer avatars, chat, emotes, voxel building, and a live market-cap screen. The [`$THREE` home town](https://three.ws/play) is the flagship world.-2. **An agent economy — agents paying agents** — inside the `$THREE` home town, autonomous agents transact **on-chain via x402** (agents paying each other in USDC for services), demonstrating a real agent-exchange economy, not a simulation. This builds on the platform's [native x402 rails](#sec-862) (Base, BSC, Solana).+2. **An agent economy — agents paying agents** — inside the `$THREE` home town, autonomous agents transact **on-chain via x402** (agents paying each other in USDC for services), demonstrating a real agent-exchange economy, not a simulation. This builds on the platform's [native x402 rails](#sec-877) (Base, BSC, Solana).3. **On-chain reputation & identity** — agents and contributions carry [ERC-8004 / Metaplex Core identity](../README.md#on-chain-identity-erc-8004--metaplex-core) with signed action logs and a [reputation registry](https://three.ws/reputation), plus a pump.fun-native launch/visualize toolset at [`/pumpfun`](https://three.ws/pumpfun) and [`/pump-visualizer`](https://three.ws/pump-visualizer).## Example workflow (hypothetical)@@ -63943,7 +64013,7 @@ Three real surfaces turn a token into a living world with its own economy:1. A community lead opens [`/communities`](https://three.ws/communities), finds the `$THREE` world, and shares the direct link. Holders open it and land in the same [3D `$THREE` home town](https://three.ws/play) — they see each other's avatars, chat, drop emotes, and build with voxels while a live market-cap screen ticks in-world. (`$THREE` CA: `FeMbDoX7R1Psc4GEcvJdsbNbZA3bfztcyDCatJVJpump`.)2. In the home town, holders watch the resident agents pay each other on-chain via x402 — a working agent-exchange where one agent buys a service from another in USDC, settled on Solana — a concrete demo of the agent economy the community is part of.-3. Active contributors register agents with [on-chain identity](#sec-749), accruing a signed action history and a [reputation](https://three.ws/reputation) score that can't be forged — a durable signal of who actually showed up.+3. Active contributors register agents with [on-chain identity](#sec-757), accruing a signed action history and a [reputation](https://three.ws/reputation) score that can't be forged — a durable signal of who actually showed up.4. The community uses [`/pump-visualizer`](https://three.ws/pump-visualizer) to surface live `$THREE` activity inside the world, tying market events to the shared space.5. **Deliverable:** a persistent, multiplayer `$THREE` world where holders gather, a live agent economy they can watch settle on-chain, and an on-chain reputation layer that rewards real participation.@@ -63954,13 +64024,13 @@ A shared 3D home for the token's holders, a real (not mocked) on-chain agent-exc## Next step / CTA- Start: [`/communities`](https://three.ws/communities) → the [`$THREE` home town](https://three.ws/play) → [`/pumpfun`](https://three.ws/pumpfun) and [`/pump-visualizer`](https://three.ws/pump-visualizer).-- Build: [x402 docs](#sec-862) for the agent-economy rails · [Register On-Chain](#sec-749) for reputation.+- Build: [x402 docs](#sec-877) for the agent-economy rails · [Register On-Chain](#sec-757) for reputation.- **Social spotlight angle (G03):** "Watch two agents pay each other on-chain inside a live 3D `$THREE` town — your community's home."- `[REAL CASE STUDY — fill on consent: a community that gathered in its 3D world and what changed for engagement.]`----<a id="sec-217"></a>+<a id="sec-218"></a>> **Source:** `docs/content/use-cases/game-studio.md` · [↑ table of contents](#table-of-contents)@@ -64001,13 +64071,13 @@ A character that renders with production-grade glTF handling, converses through## Next step / CTA- Start: [`/app`](https://three.ws/app) to render a GLB, then [`/walk`](https://three.ws/walk) for the shared world. The Colyseus server lives in `multiplayer/`.-- Learn: [Write a Custom Skill](#sec-718) · [Agent System docs](#sec-068) · [Skill spec](../specs/SKILL_SPEC.md).+- Learn: [Write a Custom Skill](#sec-726) · [Agent System docs](#sec-068) · [Skill spec](../specs/SKILL_SPEC.md).- **Social spotlight angle (G03):** "An NPC that emotes and hands out quests through a real tool-loop — plus a shared world players walk into together."- `[REAL CASE STUDY — fill on consent: a studio that shipped a three.ws-powered NPC or multiplayer hub.]`----<a id="sec-218"></a>+<a id="sec-219"></a>> **Source:** `docs/content/use-cases/indie-creator.md` · [↑ table of contents](#table-of-contents)@@ -64061,13 +64131,13 @@ A real, embedded, conversational 3D avatar that loads in any modern browser. The## Next step / CTA- Start: [`/scan`](https://three.ws/scan) (selfie) or `/forge` (text) → [Embed Editor](https://three.ws/embed).-- Learn: [Build Your First Agent](#sec-727) · [Embed on Your Website](#sec-723).+- Learn: [Build Your First Agent](#sec-735) · [Embed on Your Website](#sec-731).- **Social spotlight angle (G03):** "From one selfie to a talking 3D you, embedded in your bio — no Blender."- `[REAL CASE STUDY — fill on consent: an indie creator who shipped an embedded agent and the response it got.]`----<a id="sec-219"></a>+<a id="sec-220"></a>> **Source:** `docs/contributing.md` · [↑ table of contents](#table-of-contents)@@ -64142,7 +64212,7 @@ npm run devMost features work without the optional services. The app degrades gracefully, so basic 3D viewer work, skill development, and UI changes don't require any backend credentials.-For full backend setup — R2 storage, environment variables, and how the app is deployed — see the [Configuration Reference](#sec-212) and the [Deployment & Self-Hosting](#sec-236) guide.+For full backend setup — R2 storage, environment variables, and how the app is deployed — see the [Configuration Reference](#sec-213) and the [Deployment & Self-Hosting](#sec-237) guide.---@@ -64176,7 +64246,7 @@ src/└── components/ — vhtml JSX components (string-based, no virtual DOM)```-See the [Architecture Overview](#sec-384) for a deeper understanding of how these pieces connect.+See the [Architecture Overview](#sec-388) for a deeper understanding of how these pieces connect.---@@ -64278,48 +64348,33 @@ GitHub token for that account (`GITHUB_TOKEN`, or the PAT on the `origin` remoteA token for a different account authenticates fine and is then rejected for thatnamespace.-**3. Standalone GitHub mirrors** - each package also lives in its own repo at-`github.com/<owner>/<name>` (a read-only mirror; the monorepo stays canonical).-Each sync force-pushes one snapshot commit whose message records the source-monorepo SHA, and rewrites the mirror's `package.json` / `server.json`-`repository` fields to point at the standalone repo:+**3. Standalone GitHub mirrors** - about 80 directories in this monorepo also+live in their own public repo at `github.com/<owner>/<name>` (a read-only+mirror; the monorepo stays canonical). [`data/standalone-mirrors.json`](../data/standalone-mirrors.json)+is the single source of truth for "which directory is which public repo, in+which direction": every exporter (`sync-standalone-repos.mjs`,+`export-growth-satellites.mjs`, `build-awesome.mjs --standalone`,+`build-standalone-skill-repos.mjs`) reads repo names from it instead of+hardcoding its own list. A `direction: "in"` entry (the `robinhood/*` copies)+is a reference copy of an external repo; no exporter pushes those.++`scripts/sync-standalone-repos.mjs` only **stages**; it never pushes and never+calls the GitHub API:```bash-npm run sync:repos:dry # plan only, both lanes-npm run sync:repos # create missing repos + push snapshots (needs gh auth as the owner)-# scope it:-node scripts/sync-standalone-repos.mjs --dry-run --kind lib --new-node scripts/sync-standalone-repos.mjs --execute --only agent-sniper,copy-mcp+npm run sync:repos # stage every manifest "sync" entry under dist/standalone-mirrors/+npm run sync:repos:check # compare staged trees against the live repos; exits non-zero on drift+node scripts/sync-standalone-repos.mjs --only tty-avatar,x402-bridge```-`--kind mcp` / `--kind lib` narrows to one lane, `--new` limits the run to repos-that do not exist yet, and the dry run prints how many repos it would CREATE-before you commit to it. Repo names come from the unscoped npm name, except that-a single-token `@three-ws/*` name mirrors as `three-ws-<name>`: the scope carries-the identity on npm, but `github.com/nirholas/render` says nothing about what it-is or who ships it.--Auth: `gh` must be authenticated as the target owner (default `nirholas`; override-with `--owner`) so it can create and push under that account.--**What every mirror ships.** Besides the package, each sync generates the discovery-layer from `scripts/lib/standalone-enrich.mjs`, so no mirror is a bare code dump:--| Generated file | Audience |-|---|---|-| `AGENTS.md`, `llms.txt`, `llms-full.txt`, `glama.json` (MCP) | AI coding agents and MCP directories |-| `CONTRIBUTING.md`, `SECURITY.md`, `CODE_OF_CONDUCT.md`, `CITATION.cff`, issue forms, PR template | Contributors and security reporters |-| `docs/` (README rendered with OG tags, JSON-LD, sitemap, robots, 404) | Search engines and humans, served by GitHub Pages from `main:/docs` |--It also sets the repository topics (from the package keywords), description,-homepage (`https://<owner>.github.io/<repo>/`), Discussions, Pages and-vulnerability alerts over the API. A file the package already ships is kept, so a-package overrides any generated file by committing its own. `--settings-only`-re-applies the repository settings without pushing. `GH_PAT` authenticates both-`git push` and `gh` when set, and never lands in a remote URL or process args.-A package listed in `HOLD_NEW` keeps syncing if its repo exists, but its first-repo is not created until the owner approves (it is built around another crypto-project).+Each staged mirror is a fresh one-commit git repo whose message records the+source monorepo SHA (`Sync from three.ws@<sha>`), with `package.json`'s+`repository` field rewritten to point at the standalone repo and any stale+"All rights reserved" README footer or LICENSE replaced with the Apache-2.0+text this repo ships today. Nothing else in the snapshot changes: the staged+tree is otherwise byte-for-byte the source directory. `sync:repos` finishes by+printing the exact `git push --force` command per mirror; publishing a mirror+is the owner's call, not this script's.---@@ -64403,7 +64458,7 @@ Skills are the best way to extend three.ws without touching core code. A skill i1. **Use the template.** Copy `examples/skills/solana-wallet/` as your starting point — its `manifest.json`, `tools.json`, `handlers.js`, and `SKILL.md` demonstrate the minimal structure a skill needs.-2. **Build your skill.** See the [Skills documentation](#sec-649) for the full format, lifecycle hooks, and message API.+2. **Build your skill.** See the [Skills documentation](#sec-657) for the full format, lifecycle hooks, and message API.3. **Host it.** GitHub Pages, Vercel, Netlify, or any static CDN works. The URL just needs to be publicly accessible over HTTPS.@@ -64439,7 +64494,7 @@ Open a [GitHub issue](https://github.com/nirholas/three.ws/issues/new) and incluCheck [existing issues](https://github.com/nirholas/three.ws/issues) before opening a new one to avoid duplicates.-**Security vulnerabilities:** Do NOT open a public issue. Follow the responsible disclosure process described in the [Security documentation](#sec-627). Public disclosure of an unpatched vulnerability puts all users at risk.+**Security vulnerabilities:** Do NOT open a public issue. Follow the responsible disclosure process described in the [Security documentation](#sec-634). Public disclosure of an unpatched vulnerability puts all users at risk.---@@ -64466,7 +64521,7 @@ By contributing, you agree that your contributions are licensed under the [Apach----<a id="sec-220"></a>+<a id="sec-221"></a>> **Source:** `docs/cookbook/asset-quality-gate.md` · [↑ table of contents](#table-of-contents)@@ -64633,7 +64688,7 @@ build on any of them. They are a good backlog for whatever ships the assets.----<a id="sec-221"></a>+<a id="sec-222"></a>> **Source:** `docs/cookbook/mcp-3d-tool.md` · [↑ table of contents](#table-of-contents)@@ -64772,7 +64827,7 @@ endpoints.----<a id="sec-222"></a>+<a id="sec-223"></a>> **Source:** `docs/cookbook/parallel-asset-pack.md` · [↑ table of contents](#table-of-contents)@@ -64941,7 +64996,7 @@ machine. Useful for picking a triangle budget before you commit to one.----<a id="sec-223"></a>+<a id="sec-224"></a>> **Source:** `docs/cookbook/text-to-3d-cli.md` · [↑ table of contents](#table-of-contents)@@ -65090,7 +65145,7 @@ the lane is queued, which is exactly when `retryAfter` starts mattering.----<a id="sec-224"></a>+<a id="sec-225"></a>> **Source:** `docs/copy-coach.md` · [↑ table of contents](#table-of-contents)@@ -65112,10 +65167,10 @@ Page: `pages/copy-coach.html`, `src/copy-coach.js`, `src/copy-coach.css`| Step | What the user sees | Why it is safe ||---|---|---|-| 1. See a real win | The most recent public trade that closed up 25% or more in the last 14 days, with its signed buy and sell transactions on Solscan and the "why it traded" [receipt](#sec-683), **right next to the same agent's full 30-day record**. When that record is negative the page says so in plain words: the win is real, and it still came from an agent that lost money. | Reading only. |-| 2. Ghost-copy | Leaders with closed trades in the last 30 days, each marked copyable or not against the platform's real bar (and, if not, what is missing). One click replays the chosen leader with fake money through [ghost-copy](#sec-323): fake balance, realized result, wins and losses, worst drawdown, and the equity curve. A losing replay gets a red verdict: the coach would not copy this leader with real money yet. | Fake money. No wallet, no signature, no account. |+| 1. See a real win | The most recent public trade that closed up 25% or more in the last 14 days, with its signed buy and sell transactions on Solscan and the "why it traded" [receipt](#sec-691), **right next to the same agent's full 30-day record**. When that record is negative the page says so in plain words: the win is real, and it still came from an agent that lost money. | Reading only. |+| 2. Ghost-copy | Leaders with closed trades in the last 30 days, each marked copyable or not against the platform's real bar (and, if not, what is missing). One click replays the chosen leader with fake money through [ghost-copy](#sec-326): fake balance, realized result, wins and losses, worst drawdown, and the equity curve. A losing replay gets a red verdict: the coach would not copy this leader with real money yet. | Fake money. No wallet, no signature, no account. || 3. One tiny real copy | A starter copy of the chosen leader: a fixed size per trade, a daily cap, a limit on open copies, an automatic pause if the leader draws down, and only coins that pass the safety check. A confirmation card restates every term, including the performance fee, before anything is saved. Confirm stays disabled until the user ticks "I understand copy trading can lose money", and a second box appears when their own ghost run of that leader lost. | Non-custodial, server-enforced caps, and nothing is spent at confirmation: each copied entry arrives as an intent in [/dashboard/copy](https://three.ws/dashboard/copy) that only trades if the user signs it. |-| 4. What comes next | Where copies show up, the leader's full record, other ghost runs, full copy with the user's own caps, and the [Sentiment Scout](#sec-634). The advice is to stay at starter size until the record, not one good day, earns more. | Links only. |+| 4. What comes next | Where copies show up, the leader's full record, other ghost runs, full copy with the user's own caps, and the [Sentiment Scout](#sec-641). The advice is to stay at starter size until the record, not one good day, earns more. | Links only. |Progress (current step, completed steps, chosen leader) is remembered in thebrowser and carried in the URL (`?step=ghost_copy&leader=<id>`), so a user can@@ -65194,15 +65249,15 @@ platform shape `{ error, error_description }`: `invalid_json`, `invalid_message`## Related-- [Ghost-copy](#sec-323): the replay step 2 runs.-- [Trade receipts](#sec-683): the "why it traded" behind the win.-- [Sentiment Scout](#sec-634): momentum with receipts.-- [Trading Copilot](#sec-691): the confirm-before-execute trade+- [Ghost-copy](#sec-326): the replay step 2 runs.+- [Trade receipts](#sec-691): the "why it traded" behind the win.+- [Sentiment Scout](#sec-641): momentum with receipts.+- [Trading Copilot](#sec-699): the confirm-before-execute tradecards for an agent's own wallet.----<a id="sec-225"></a>+<a id="sec-226"></a>> **Source:** `docs/copy-trading.md` · [↑ table of contents](#table-of-contents)@@ -65217,11 +65272,11 @@ Copy trading on three.ws lets one wallet follow another wallet's real trades. ThBoth are Solana-native. Both run on `mainnet` and `devnet`. Neither is a paper-trading mode: neither engine has a simulation layer or a synthetic fill anywhere in it. Read [Simulated versus executed](#simulated-versus-executed) before you enable anything.-If you want to feel a leader's edge before committing money, that is a *separate* surface: [Ghost-copy](#sec-323) replays a leader's real closed trades against a wallet that does not exist. It never touches either engine below and never produces an intent.+If you want to feel a leader's edge before committing money, that is a *separate* surface: [Ghost-copy](#sec-326) replays a leader's real closed trades against a wallet that does not exist. It never touches either engine below and never produces an intent.A leader can also price *when* each copier is shown their signal: [alpha-drip](#sec-096) releases the copy intent to higher $THREE tiers first and everyone else after a delay the leader sets. It is off unless a leader turns it on, it delays the reveal and never the record, and the copier is shown the seat they get before they subscribe.-Related reading: [Smart Money Radar](#sec-652) for the first-party wallet reputation graph, [the trading surfaces](#sec-695) for the screeners and the trading cockpit these leaders trade from, [agent wallets](#sec-077) for the custody and spend-policy model, and [signal marketplace](#sec-642) for the paid-feed variant that reuses the same guarded executor.+Related reading: [Smart Money Radar](#sec-660) for the first-party wallet reputation graph, [the trading surfaces](#sec-703) for the screeners and the trading cockpit these leaders trade from, [agent wallets](#sec-077) for the custody and spend-policy model, and [signal marketplace](#sec-650) for the paid-feed variant that reuses the same guarded executor.---@@ -65231,7 +65286,7 @@ State this to yourself before you touch a control:- **The agent mirror executes with real funds.** When a leader agent's trade confirms on-chain, `api/_lib/agent-mirror.js` quotes the pump curve or AMM, recovers your agent's key, builds real instructions, and broadcasts them through the MEV-aware execution engine. The resulting signature is a real Solana transaction. There is no dry-run flag, no shadow mode, and no "test" sizing.- **Copier subscriptions never execute.** `api/cron/copy-fanout.js` writes a row into `copy_executions` with a planned size and a reason. That is the whole action. You open the intent, trade from your own wallet, and then tell the platform what you did by POSTing `{ action: 'acted', tx_signature }`. Marking an intent `acted` records history. It moves no funds, and the platform never holds your keys on this path.-- **Ghost-copy is explicitly paper, and lives outside both engines.** [/ghost-copy](https://three.ws/ghost-copy) replays a leader's already-closed on-chain round-trips against a hypothetical budget. It shares the sizing function (`planCopyOrder`) with the copier path so the numbers are comparable, but it writes nothing, signs nothing, produces no intent, and cannot be enabled. Every response is labelled `paper: true` and carries an `honesty` block. See [ghost-copy](#sec-323).+- **Ghost-copy is explicitly paper, and lives outside both engines.** [/ghost-copy](https://three.ws/ghost-copy) replays a leader's already-closed on-chain round-trips against a hypothetical budget. It shares the sizing function (`planCopyOrder`) with the copier path so the numbers are comparable, but it writes nothing, signs nothing, produces no intent, and cannot be enabled. Every response is labelled `paper: true` and carries an `honesty` block. See [ghost-copy](#sec-326).- **The leaderboard and track records are computed from real fills only.** `api/_lib/mirror-stats.js` and `api/mirror/leaderboard.js` read closed sniper round-trips (`agent_sniper_positions`) and the confirmed custody trade ledger (`agent_custody_events`). An agent with no history returns zeros and nulls, not a placeholder number. Losing agents appear with their losses.- **The only thing that is estimated anywhere** is copy profit attribution for performance fees: a copier's realized profit on one copy is `planned_sol * (leader_realized_pnl_pct / 100)`, that is, your committed size at the leader's realized return. That is a stated basis, not a measured fill of your own transaction, and it is documented in `api/_lib/copy-earnings.js`.@@ -65256,7 +65311,7 @@ Money-moving actions are yours to confirm. Nothing on these pages spends withoutAn agent appears if it is public (`is_public <> false`), not deleted, and has **either** at least one closed sniper position **or** at least one confirmed discretionary trade on that network. An agent that only trades discretionarily still ranks, with volume and no realized P&L. The candidate scan is capped at 500 rows before scoring.-`settled_min` narrows that to agents with at least that many **closed** round-trips, before the ranking is windowed by `limit`. Ask for it when your surface cannot use an agent without a realized track record. [The Clip Director](#sec-192) is the case in point: it mints a card from a closed trade, so an agent with none is useless to it. Filtering client side instead is a trap, and it bit us: the composite score does not correlate with having settled trades, so the only eligible agent ranked below the caller's window and the page reported that nobody had ever closed a trade.+`settled_min` narrows that to agents with at least that many **closed** round-trips, before the ranking is windowed by `limit`. Ask for it when your surface cannot use an agent without a realized track record. [The Clip Director](#sec-193) is the case in point: it mints a card from a closed trade, so an agent with none is useless to it. Filtering client side instead is a trap, and it bit us: the composite score does not correlate with having settled trades, so the only eligible agent ranked below the caller's window and the page reported that nobody had ever closed a trade.```bash# Only agents with a realized track record, best composite score first@@ -65406,7 +65461,7 @@ Then `planMirror` (pure, unit-tested in `tests/mirror-engine.test.js`) decides:The sized order then goes through `runFollowerTrade`, which is the same guard sequence the discretionary trade endpoint and the sniper use, in this order: agent kill switch, per-trade cap, rolling daily budget, the natural-language spend policy (`meta.policy_rules`), price-impact breaker, rug and honeypot firewall (a `block` verdict refuses the mirror), on-chain SOL headroom, then an idempotency claim in the custody ledger before anything is signed. Slippage is capped at 300 bps. Every mirrored trade lands in `agent_custody_events` with `reason: 'mirror'` and a `meta.mirror` reference naming the leader and the leader's event.-A mirrored trade is a trade three.ws signs, so it carries the platform trade fee like every other one: 1 percent of the SOL spent on a buy, or of the minimum SOL out on a sell, transferred to the platform treasury inside the same transaction. It is built by the shared `buildTradeInstructions`, which is why the mirror cannot route around it, and it is skipped for platform-owned agents and wherever no fee wallet is configured. The rate, the basis, and what is not billed are in [platform trade fee](#sec-562). The copier path has no such fee: you sign that trade yourself, from your own wallet.+A mirrored trade is a trade three.ws signs, so it carries the platform trade fee like every other one: 1 percent of the SOL spent on a buy, or of the minimum SOL out on a sell, transferred to the platform treasury inside the same transaction. It is built by the shared `buildTradeInstructions`, which is why the mirror cannot route around it, and it is skipped for platform-owned agents and wherever no fee wallet is configured. The rate, the basis, and what is not billed are in [platform trade fee](#sec-569). The copier path has no such fee: you sign that trade yourself, from your own wallet.Nothing double-spends: the custody idempotency key `mirror:<follow_id>:<leader_event_id>:<side>` and the unique index on `agent_mirror_fills (follow_id, leader_event_id, side)` both dedupe, so a retried cron or an overlapping manual sync replays instead of re-buying.@@ -65638,7 +65693,7 @@ Response:The directory is a static, deduplicated snapshot shipped with the API (`api/_lib/copy/smart-wallets.json`) and regenerated by `scripts/build-smart-wallets.mjs`. The snapshot records an avatar URL for some wallets, but the endpoint strips it: that image host answers 403 to any off-site request, so the URL cost every client a blocked load and no client could ever render it. The dashboard shows the trader initial instead. Wallet identity and 30-day performance only, never token holdings. If the snapshot file is missing the endpoint returns an empty list rather than failing.-For first-party wallet reputation earned from three.ws's own outcome ledger rather than an external taxonomy, use [Smart Money Radar](#sec-652).+For first-party wallet reputation earned from three.ws's own outcome ledger rather than an external taxonomy, use [Smart Money Radar](#sec-660).---@@ -65672,7 +65727,7 @@ Both engines are reachable without a browser:- `packages/strategies` wraps `POST /api/copy/subscriptions` and `/api/copy/executions` for programmatic strategy clients. See [its README](../packages/strategies/README.md).- Bearer tokens work on every authenticated route above and are not CSRF-gated, which is what makes an autonomous agent a first-class copier here.-See [the MCP reference](#sec-417) for wiring these into a client.+See [the MCP reference](#sec-421) for wiring these into a client.---@@ -65687,7 +65742,7 @@ See [the MCP reference](#sec-417) for wiring these into a client.----<a id="sec-226"></a>+<a id="sec-227"></a>> **Source:** `docs/cosmos.md` · [↑ table of contents](#table-of-contents)@@ -65778,13 +65833,13 @@ else {## Related-- [Forge](#sec-313) makes the 3D avatars and objects you place in a Cosmos world.-- [Avatar creation](#sec-144) and [the trait-based avatar builder](#sec-182) for building and dressing avatars.+- [Forge](#sec-316) makes the 3D avatars and objects you place in a Cosmos world.+- [Avatar creation](#sec-145) and [the trait-based avatar builder](#sec-183) for building and dressing avatars.- Pages: [/create](https://three.ws/create), [/gallery](https://three.ws/gallery), [/scene](https://three.ws/scene).----<a id="sec-227"></a>+<a id="sec-228"></a>> **Source:** `docs/crawl.md` · [↑ table of contents](#table-of-contents)@@ -65827,7 +65882,7 @@ Each page your agent reads with a useful summary becomes a memory in that agentRead "Perlin noise" (https://en.wikipedia.org/wiki/Perlin_noise) while crawling for procedural terrain generation: Perlin noise is a type of gradient noise ...```-Memories are only written when the agent's own owner sent it out, only for pages relevant enough to the topic, and they expire after 30 days. Ask the agent in chat what it has been reading and it can answer from them. See [Agent memory](#sec-420).+Memories are only written when the agent's own owner sent it out, only for pages relevant enough to the topic, and they expire after 30 days. Ask the agent in chat what it has been reading and it can answer from them. See [Agent memory](#sec-424).---@@ -65912,7 +65967,7 @@ The stage renders each frame as a flat page in a Three.js scene and drives the a----<a id="sec-228"></a>+<a id="sec-229"></a>> **Source:** `docs/create-agent.md` · [↑ table of contents](#table-of-contents)@@ -66012,7 +66067,7 @@ curl -s -X POST https://three.ws/api/mcp-studio \}'```-`forge_avatar` is generate-then-rig bundled; `--object` calls `forge_free` instead. Both are open, keyless JSON-RPC tools on the same endpoint the three.ws MCP server exposes, so anything that can speak HTTP can do what this CLI does. The MCP surface is documented in [mcp.md](#sec-417).+`forge_avatar` is generate-then-rig bundled; `--object` calls `forge_free` instead. Both are open, keyless JSON-RPC tools on the same endpoint the three.ws MCP server exposes, so anything that can speak HTTP can do what this CLI does. The MCP surface is documented in [mcp.md](#sec-421).The job blocks server-side until the model exists, which is why the CLI reports **real elapsed seconds** rather than a progress bar it would have to invent. Every call carries a 10-minute deadline; on a timeout the job may still finish, and finished models land at [three.ws/creations](https://three.ws/creations).@@ -66038,9 +66093,9 @@ Full reference: [packages/create-agent/README.md](https://github.com/nirholas/th## Then what-- **Put it on your site.** The printed snippet is the whole integration; attribute reference in [web-component.md](#sec-799).+- **Put it on your site.** The printed snippet is the whole integration; attribute reference in [web-component.md](#sec-811).- **Give it a brain and a voice.** [three.ws/create](https://three.ws/create) takes the same model and adds a personality, memory, and speech.-- **Show what it is doing.** [Glance](#sec-326) puts the agent's live status on a home screen, in a README, or in Slack.+- **Show what it is doing.** [Glance](#sec-329) puts the agent's live status on a home screen, in a README, or in Slack.- **Let other agents hire it.** [three.ws/marketplace](https://three.ws/marketplace).---@@ -66054,7 +66109,7 @@ three.ws examples repo, so it is installed, run, and link-checked before every r----<a id="sec-229"></a>+<a id="sec-230"></a>> **Source:** `docs/creator-portfolio.md` · [↑ table of contents](#table-of-contents)@@ -66203,7 +66258,7 @@ Two card-level actions let a visitor take a copy of what they find:handler [api/avatars/fork.js](../api/avatars/fork.js)): clones the GLB,its agent, and a fresh wallet into the viewer's account. Downstream, forksof a paid avatar are what produce the `royalty_paid` notifications- documented in [Notifications](#sec-442).+ documented in [Notifications](#sec-446).- **Fork an agent** (`POST /api/marketplace/agents/:id/fork`, handler[api/marketplace/[action].js](../api/marketplace/[action].js)): clonesa *published* agent into the viewer's account; unpublished agents render@@ -66246,19 +66301,19 @@ unfurl; an unknown handle is still a cached 404 card.## Related pages-- [The social layer](#sec-654): the follow graph, feed, and+- [The social layer](#sec-662): the follow graph, feed, andrankings this page plugs into.-- [Notifications](#sec-442): the follow, remix, sale, and royalty+- [Notifications](#sec-446): the follow, remix, sale, and royaltyevents a portfolio generates for its owner.-- [Remix economy](#sec-597): what happens when someone remixes a creation+- [Remix economy](#sec-604): what happens when someone remixes a creationthey found here.-- [Forge](#sec-313), [Widgets](#sec-802),- [Marketplace](#sec-408): the creation surfaces whose output the+- [Forge](#sec-316), [Widgets](#sec-814),+ [Marketplace](#sec-412): the creation surfaces whose output theportfolio aggregates.----<a id="sec-230"></a>+<a id="sec-231"></a>> **Source:** `docs/crews.md` · [↑ table of contents](#table-of-contents)@@ -66449,7 +66504,7 @@ player who is already social in the world finds the group surface.----<a id="sec-231"></a>+<a id="sec-232"></a>> **Source:** `docs/crypto-api.md` · [↑ table of contents](#table-of-contents)@@ -67516,7 +67571,7 @@ curl -s "https://three.ws/api/crypto/airdrops?address=<wallet>" \----<a id="sec-232"></a>+<a id="sec-233"></a>> **Source:** `docs/custody.md` · [↑ table of contents](#table-of-contents)@@ -67537,12 +67592,12 @@ Limits live per agent and are owner-configurable from the wallet hub (API: `GET/- `daily_usd` — rolling 24-hour ceiling, summed over the custody event trail- `per_tx_usd` — single-transaction ceiling-- `withdraw_allowlist`, destinations the wallet may send to, managed as the [destination whitelist](#sec-242) (cooldown, step-up, instant removal)+- `withdraw_allowlist`, destinations the wallet may send to, managed as the [destination whitelist](#sec-243) (cooldown, step-up, instant removal)- Plus a trade-side daily SOL budget for trading agentsEnforcement is uniform: the same policy module gates **every** outbound path — withdrawals, x402 payments, sniper buys, trades. A transaction that would breach a cap is refused with a structured `403` before signing; no funds move. Limits are opt-in (`null` means uncapped) — but they're hard once set. SPL tokens that can't be priced in USD are governed by the allowlist instead, so a price-feed outage can never strand your own withdrawal.-You can also write these rules in plain English — see [financial-controls](#sec-306) for the natural-language rules layer and the real-time defense behaviors built on top of this same enforcement point.+You can also write these rules in plain English — see [financial-controls](#sec-309) for the natural-language rules layer and the real-time defense behaviors built on top of this same enforcement point.## Freeze: the kill switch that can't trap you@@ -67601,14 +67656,14 @@ Every step of recovery and inheritance writes to the custody trail and the audit## Related-- [Financial controls](#sec-306) — plain-English spend rules and real-time wallet defense on these rails-- [Trading surfaces](#sec-695) — Mission Control executes through this same guarded path-- [The trading experiment](#sec-692) — an autonomous agent operating inside these limits, journaled-- [x402](#sec-862) — the payment protocol these wallets spend over+- [Financial controls](#sec-309) — plain-English spend rules and real-time wallet defense on these rails+- [Trading surfaces](#sec-703) — Mission Control executes through this same guarded path+- [The trading experiment](#sec-700) — an autonomous agent operating inside these limits, journaled+- [x402](#sec-877) — the payment protocol these wallets spend over----<a id="sec-233"></a>+<a id="sec-234"></a>> **Source:** `docs/daily-forge.md` · [↑ table of contents](#table-of-contents)@@ -67709,14 +67764,14 @@ console.log(themeIndex(new Date().toISOString().slice(0, 10), 24));## Related- [The 3D pipeline](#sec-003) and [3D API](#sec-001): the text-to-3D forge the free lane rides-- [Forge background generation](#sec-308): the job and polling model-- [AR and WebXR](#sec-129): the Scene Viewer and Quick Look handoff-- [Quick start](#sec-593): the general free-forge onboarding+- [Forge background generation](#sec-311): the job and polling model+- [AR and WebXR](#sec-130): the Scene Viewer and Quick Look handoff+- [Quick start](#sec-600): the general free-forge onboarding- Pages: [/daily](https://three.ws/daily) · [/forge](https://three.ws/forge) · [/ar/studio](https://three.ws/ar/studio)----<a id="sec-234"></a>+<a id="sec-235"></a>> **Source:** `docs/daily-match.md` · [↑ table of contents](#table-of-contents)@@ -67886,11 +67941,11 @@ P&L and Score columns become unreachable on a phone.Related docs: [agent-sniper.md](#sec-065) (where the trade and P&Lcolumns come from), [agent-skills.md](#sec-064) (skill sales),-[pump-launcher.md](#sec-561) (launches).+[pump-launcher.md](#sec-568) (launches).----<a id="sec-235"></a>+<a id="sec-236"></a>> **Source:** `docs/demo-routes.md` · [↑ table of contents](#table-of-contents)@@ -68015,7 +68070,7 @@ live at their own top-level URLs:| Route | Page file | What it does ||---|---|---|-| `/coin3d` | `pages/coin3d.html` | Token-in-3D visualizer. Keyed by `?mint=` or by `?pair=` (a pool address, resolved through `/api/coin/pair`); `?embed=1` drops the site chrome, and the route serves `frame-ancestors *` so it frames anywhere. See [coin3d-embed.md](#sec-196). |+| `/coin3d` | `pages/coin3d.html` | Token-in-3D visualizer. Keyed by `?mint=` or by `?pair=` (a pool address, resolved through `/api/coin/pair`); `?embed=1` drops the site chrome, and the route serves `frame-ancestors *` so it frames anywhere. See [coin3d-embed.md](#sec-197). || `/embed-demo` | `pages/embed-demo.html` | Avatar embed demo. || `/hero-demo` | `pages/hero-demo.html` | Cinematic 3D hero stage: a lit avatar over glowing rings and a starfield, with pointer parallax. || `/lipsync` | `public/demos/lipsync-tts.html` | Alias into the lab: TTS-driven lipsync. |@@ -68117,7 +68172,7 @@ the 200s above still come from the 2026-08-05 curl sweep.----<a id="sec-236"></a>+<a id="sec-237"></a>> **Source:** `docs/deployment.md` · [↑ table of contents](#table-of-contents)@@ -68490,7 +68545,7 @@ The `crons` array in `vercel.json` declares every scheduled job (economy tick, o| `/api/cron/run-dca` | Every hour | Execute scheduled DCA strategies || `/api/cron/run-subscriptions` | Every hour | Process recurring subscriptions |-The container does **not** schedule these itself — you need an external scheduler hitting the endpoints. On Cloud Run that is Cloud Scheduler; self-hosters can point any HTTP cron (Cloud Scheduler, cron-job.org, Upstash QStash) at `/api/cron/*` with the `CRON_SECRET` bearer, or run `scripts/economy-heartbeat.mjs` as a long-lived pinger that reads `vercel.json` and fires every due cron each minute. See the [economy heartbeat](#sec-254) guide for the driver patterns.+The container does **not** schedule these itself — you need an external scheduler hitting the endpoints. On Cloud Run that is Cloud Scheduler; self-hosters can point any HTTP cron (Cloud Scheduler, cron-job.org, Upstash QStash) at `/api/cron/*` with the `CRON_SECRET` bearer, or run `scripts/economy-heartbeat.mjs` as a long-lived pinger that reads `vercel.json` and fires every due cron each minute. See the [economy heartbeat](#sec-257) guide for the driver patterns.### Static asset caching@@ -68555,7 +68610,7 @@ does not use them: it reads and writes the ERC-8004 reference`ValidationRegistryUpgradeable`, which has no validator allow-list. A validator isauthorized per agent by the agent's owner opening a request that names it (or bythe owner approving it as an operator). See-[erc8004/validation-attestation.md](#sec-264), and verify+[erc8004/validation-attestation.md](#sec-267), and verifyany configured registry address with `npm run verify:erc8004-validation`.---@@ -68617,7 +68672,7 @@ docker run -p 8080:8080 \- **Logs:** on Cloud Run, `gcloud run services logs read three-ws-api --region us-central1` or Cloud Logging; on any other host, that platform's log stream.- **Request duration / timeout:** the Cloud Run service runs with a 900s request timeout; set the equivalent on your host so long renders (avatar thumbnails, 3D generation) don't get cut off.-- **Uptime:** the `uptime-check` cron ([api/cron/uptime-check.js](../api/cron/uptime-check.js)) watches the economy and subsystems and escalates to the ops Telegram channel — see the [economy heartbeat](#sec-254) guide.+- **Uptime:** the `uptime-check` cron ([api/cron/uptime-check.js](../api/cron/uptime-check.js)) watches the economy and subsystems and escalates to the ops Telegram channel — see the [economy heartbeat](#sec-257) guide.### Database monitoring@@ -68712,7 +68767,7 @@ Upstash REST API uses HTTPS — no ports to open. If you see connection errors,----<a id="sec-237"></a>+<a id="sec-238"></a>> **Source:** `docs/deployments.md` · [↑ table of contents](#table-of-contents)@@ -68724,7 +68779,7 @@ It answers three questions at a glance: how big is the on-chain agent populationEvery row is a real on-chain registration. There are no synthetic entries and no seeded demo rows. When a network is quiet the feed is honestly empty, and when a signal was never measured the UI says so rather than rendering a zero.-Related reading: [ERC-8004 blockchain identity](#sec-263) for the standard, the registry contracts, and how to register; [deploying agents on-chain](#sec-458) for the Solana Metaplex Core path; [agent reputation on Solana](#sec-656) for the trust layer built on top of a Solana identity.+Related reading: [ERC-8004 blockchain identity](#sec-266) for the standard, the registry contracts, and how to register; [deploying agents on-chain](#sec-462) for the Solana Metaplex Core path; [agent reputation on Solana](#sec-664) for the trust layer built on top of a Solana identity.---@@ -68739,7 +68794,7 @@ This surface is **not EVM-only**. Solana is folded into the same feed as a firstTwo Solana upstreams feed it: three.ws's own Metaplex Core mints, and the external Metaplex Agent Registry. Details in [where the data comes from](#where-the-data-comes-from).-What lives elsewhere: the *creation* path for a Solana identity is documented in [deploying agents on-chain](#sec-458) (the single-agent, user-signed flow is in [Solana agents](#sec-657)), and Solana reputation and attestations are in [agent reputation on Solana](#sec-656). This page is only the index and the feed.+What lives elsewhere: the *creation* path for a Solana identity is documented in [deploying agents on-chain](#sec-462) (the single-agent, user-signed flow is in [Solana agents](#sec-665)), and Solana reputation and attestations are in [agent reputation on Solana](#sec-664). This page is only the index and the feed.---@@ -68799,7 +68854,7 @@ A second stage, **metadata enrichment**, takes up to 25 rows per run whose metadMetadata is attacker-controlled: it is whatever the agent's owner published on-chain. Two consequences are load-bearing. Enrichment refuses to let `meta.active` alone decide visibility, and a name or description containing a slur sets `active = false` so the row is withheld from every public feed (this page included). A failed fetch records `metadata_error` and moves on rather than retrying in a loop.-The Identity Registry is deployed deterministically via CREATE2, so it has one address per network class, the same on every chain. See [ERC-8004](#sec-263) for the addresses and the contract surface.+The Identity Registry is deployed deterministically via CREATE2, so it has one address per network class, the same on every chain. See [ERC-8004](#sec-266) for the addresses and the contract surface.### 2. Solana: three.ws's own Metaplex Core mints@@ -68949,7 +69004,7 @@ The network toggle derives its chain-id sets from that table at import time, so----<a id="sec-238"></a>+<a id="sec-239"></a>> **Source:** `docs/desktop-local-runtime.md` · [↑ table of contents](#table-of-contents)@@ -69037,11 +69092,11 @@ needs the cloud reachable for preparation; paper mode needs neither the cloudnor an account. Syncing configuration and receipts to the cloud account is notpart of this release.-Related: [Companion](#sec-209), [approvals](#sec-124), `apps/desktop/README.md`.+Related: [Companion](#sec-210), [approvals](#sec-125), `apps/desktop/README.md`.----<a id="sec-239"></a>+<a id="sec-240"></a>> **Source:** `docs/desktop-menu-bar-panel.md` · [↑ table of contents](#table-of-contents)@@ -69100,7 +69155,7 @@ Tests: `tests/desktop-panel.test.js`.----<a id="sec-240"></a>+<a id="sec-241"></a>> **Source:** `docs/desktop-widgets.md` · [↑ table of contents](#table-of-contents)@@ -69187,18 +69242,18 @@ Clearing site data resets both to their defaults.unit tested in `tests/desktop-widgets.test.js` and`tests/desktop-assistant.test.js`. The shell wires the taskbar buttons,shortcuts and desktop menu in `src/desktop/shell.js`. See also-[desktop.md](#sec-241) for the rest of the desktop and [field.md](#sec-305)+[desktop.md](#sec-242) for the rest of the desktop and [field.md](#sec-308)for the Field at `/?view=field`.----<a id="sec-241"></a>+<a id="sec-242"></a>> **Source:** `docs/desktop.md` · [↑ table of contents](#table-of-contents)# three.ws Desktop-> `/` now opens the [Field](#sec-305), a live map of the platform. This+> `/` now opens the [Field](#sec-308), a live map of the platform. This> desktop and its campus are at `/?view=desktop` and `/?world=1`.`/?view=desktop` is a web desktop with a 3D campus in front of it. The page boots like a@@ -69353,6 +69408,15 @@ with `retry_in_sec`), stops at 300 digs a day (`429 daily_cap`) and rejects anunknown vein (`400 invalid_node`). Table and rules: `api/_lib/world-gems.js`;storage: migration `20261015000000_world_gems.sql`.+## The Grid++A second place to walk: a neon wireframe room where the platform's apps are things you walk up to, built in [src/desktop/grid/](../src/desktop/grid). Enter it from the campus HUD's Grid button, or open `/?world=grid`.++- **Surfaces.** A live board on the back wall (new agents from `/api/agents/public`, launches from `/api/pump/launches`, wallet moves from `/api/pulse`, the `$THREE` quote from `/api/three-token/stats`, totals from `/api/stats`), a Directory wall listing every desktop app, a Pulse wall, and one standing kiosk per dock app. Nothing is hardcoded: a feed that has not landed draws a skeleton, a failed feed says so and retries every 30 seconds.+- **Use.** WASD to walk, Shift to run, drag to look, `C` for the camera. Step up to a surface and press `E` (or tap it) to open that app on the desktop. The Campus and Desktop buttons leave the room.+- **Byte tier.** The bar at the bottom is your tier on the byte ladder (Byte to Yottabyte), read from the gems you mined in the campus (`/api/world/gems`). The ladder lives in `logic.js` (`TIERS`).+- **Rules.** Pure layout, proximity and tier maths are in `grid/logic.js` and covered by `tests/desktop-grid.test.js`. Kiosks are solid. The scene loads on first use, so the desktop boot stays light.+## What is in it- **Theme.** The CTRL design system (Windows-12 lineage): Mica gradients, glass@@ -69468,7 +69532,7 @@ code and CSS are original to three.ws.----<a id="sec-242"></a>+<a id="sec-243"></a>> **Source:** `docs/destination-whitelist.md` · [↑ table of contents](#table-of-contents)@@ -69596,11 +69660,11 @@ There is deliberately no tool that approves, activates or edits an address or th- A cron, `/api/cron/whitelist-activate` (every 5 minutes), flips entries whose cooldown ended and applies due settings changes. Reads also activate due entries, so a send never waits on the cron. After a deploy that adds the cron, run `npm run deploy:gcp:sync-crons`.- Selling or transferring an agent clears the seller's entries and settings.-Related: [Custody you can verify](#sec-232), [Agent wallet API](#sec-076), [Autonomous agent-to-agent payments](#sec-008), [MCP](#sec-417).+Related: [Custody you can verify](#sec-233), [Agent wallet API](#sec-076), [Autonomous agent-to-agent payments](#sec-008), [MCP](#sec-421).----<a id="sec-243"></a>+<a id="sec-244"></a>> **Source:** `docs/developer-plans.md` · [↑ table of contents](#table-of-contents)@@ -69745,7 +69809,7 @@ The endpoint reference is in [the API reference](api-reference.md#developer-plan----<a id="sec-244"></a>+<a id="sec-245"></a>> **Source:** `docs/developer-platform.md` · [↑ table of contents](#table-of-contents)@@ -69768,8 +69832,8 @@ The browser UI for all of this lives in the dashboard:Base URL: `https://three.ws`-Related docs: [MCP integration](#sec-417), [API reference](#sec-124),-[Authentication](#sec-138), [x402 developer tools](#sec-852).+Related docs: [MCP integration](#sec-421), [API reference](#sec-125),+[Authentication](#sec-139), [x402 developer tools](#sec-867).---@@ -69809,13 +69873,13 @@ key, no CSRF.## API keysAPI keys are bearer credentials for machine clients: the MCP server at-`/api/mcp` (see [MCP integration](#sec-417)) and the account-scoped REST+`/api/mcp` (see [MCP integration](#sec-421)) and the account-scoped RESTendpoints that accept `Authorization: Bearer` (see the-[API reference](#sec-124)). Each key carries a set of scopes:+[API reference](#sec-125)). Each key carries a set of scopes:`avatars:read`, `avatars:write`, `avatars:delete`, `profile`, `memory:read`,`memory:write`, `agents:read`, `agents:write`, `herald:announce` (posting-through the [Herald](#sec-338)), `wallet:read`, `wallet:write`,+through the [Herald](#sec-342)), `wallet:read`, `wallet:write`,`services:write`, and `inference` (model calls on the OpenAI-compatibleendpoint, billed to the account's credits, and nothing else).@@ -70028,7 +70092,7 @@ Event types:A forge generation is asynchronous and outlives the request that started it: yousubmit to `POST /api/forge`, get a `job_id` back, and the platform finishes thejob even if the caller disconnects (see-[forge-background-generation.md](#sec-308)). Without a+[forge-background-generation.md](#sec-311)). Without apush, the only way to learn the outcome is to keep polling`GET /api/forge?job=<job_id>`. These two events replace that poll loop.@@ -70308,7 +70372,7 @@ Errors: `400 bad_request` (`keyId` missing or not a string),`404 not_found` (key does not exist, is not yours, or is not a well-formedUUID), `400 revoked`, `400 expired`, `401`, `403` (CSRF), `429`.-See [MCP integration](#sec-417) for configuring a real client against+See [MCP integration](#sec-421) for configuring a real client against`/api/mcp`.---@@ -70387,7 +70451,7 @@ omitted from the manifest.----<a id="sec-245"></a>+<a id="sec-246"></a>> **Source:** `docs/devto-mcp-fleet-post.md` · [↑ table of contents](#table-of-contents)@@ -70513,7 +70577,7 @@ If you publish MCP servers at any scale, I would love to hear how you handle nam----<a id="sec-246"></a>+<a id="sec-247"></a>> **Source:** `docs/dextools.md` · [↑ table of contents](#table-of-contents)@@ -70562,7 +70626,7 @@ It produces one of two snippets.title="Token in 3D by three.ws"></iframe>```-Parameters, sizing and the ready event are in [Token in 3D, as an embed](#sec-196).+Parameters, sizing and the ready event are in [Token in 3D, as an embed](#sec-197).**The Boost on DEXTools card**, below.@@ -70619,14 +70683,14 @@ The totals are public at [`GET /api/coin/dextools-stats`](api-reference.md#dexto## Related- [Listings: DEXTools](listings.md#dextools): every surface that links DEXTools, and the Social Boost record.-- [Coin pages](#sec-194): DEXTools as a chart source in the switcher.-- [Token in 3D, as an embed](#sec-196): the 3D scene, by mint or by pair.+- [Coin pages](#sec-195): DEXTools as a chart source in the switcher.+- [Token in 3D, as an embed](#sec-197): the 3D scene, by mint or by pair.- [Chart Companion](https://three.ws/chart-companion): a 3D agent that reacts to every real swap beside a live DEXTools chart, embeddable and usable as an OBS overlay.-- [The DEXTools partnership proposal](#sec-476).+- [The DEXTools partnership proposal](#sec-482).----<a id="sec-247"></a>+<a id="sec-248"></a>> **Source:** `docs/diorama.md` · [↑ table of contents](#table-of-contents)@@ -70728,13 +70792,164 @@ until the world is saved:## Related-- [Forge](#sec-313) is the single-object generator every diorama object is forged on.-- [Image to 3D](#sec-379) for photo-based objects; [AR](#sec-129) for viewing worlds in augmented reality.+- [Forge](#sec-316) is the single-object generator every diorama object is forged on.+- [Image to 3D](#sec-383) for photo-based objects; [AR](#sec-130) for viewing worlds in augmented reality.- Pages: [/scene](https://three.ws/scene) (Scene Studio, where an exported diorama opens), [/gallery](https://three.ws/gallery), [/create](https://three.ws/create).----<a id="sec-248"></a>+<a id="sec-249"></a>++> **Source:** `docs/discord-activity.md` · [↑ table of contents](#table-of-contents)++# Discord Activity: Forge Room++three.ws ships a [Discord Activity](https://discord.com/developers/docs/activities/overview):+an embedded web app that opens inside a Discord voice channel, visible to+everyone in the call. Ours is a **shared Forge room**: the group writes one+prompt together, watches the same 3D model generate, and votes on it, live,+without leaving Discord.++**On this page:** [How it works](#how-it-works) · [Auth flow](#auth-flow) · [Proxy and CSP](#proxy-and-csp) · [Shared state](#shared-state) · [Purchases](#purchases) · [Owner setup](#owner-setup)++---++## How it works++Open the Activity from a voice channel's Activities launcher and everyone in+the call sees the same room:++1. One person types a prompt. The room shows "`<name>` prompted: ...".+2. The prompt goes straight to the real `/api/forge` generation pipeline+ (the same endpoint [the Forge Studio](/forge) uses) and the room polls it+ to completion.+3. The finished model (preview image + an "Open in 3D" link) posts to+ everyone in the room at once, with a shared like/vote count.+4. An agent reacts in text to what just happened, grounded only in the real+ prompt and vote count (see [Agent reactions](#agent-reactions)).++No account creation, no wallet, no purchase: the room is free to use for+anyone already in the voice channel.++## Auth flow++The Activity never holds a Discord client secret. The flow, per+[Discord's documented OAuth2 flow for Activities](https://discord.com/developers/docs/activities/development-guides/networking):++1. The client calls `discordSdk.commands.authorize({ scope: ['identify'] })`+ and gets back an authorization `code`.+2. The client POSTs that code to `POST /api/gateway/discord-activity-token`,+ which exchanges it for an `access_token` server-side+ (`api/_lib/gateway/discord-activity-auth.js`, `exchangeActivityCode`).+3. The client calls `discordSdk.commands.authenticate({ access_token })` to+ finish authenticating the SDK itself.+4. The client POSTs the access token plus the Activity's `instance_id`,+ `guild_id`, and `channel_id` to `POST /api/gateway/discord-activity-session`,+ which re-verifies the token against Discord's own `/users/@me` (never+ trusting the client's claimed identity), creates or updates the room, and+ mints a short-lived (4 hour) HMAC-signed session token scoped to that one+ room.++Every room API call after that carries `Authorization: Bearer <session token>`+(the SSE stream carries it as `?token=` instead, since the browser's native+`EventSource` cannot set custom headers).++## Proxy and CSP++Everything inside the Activity iframe runs under Discord's `/.proxy/` network+model: same-origin calls (`/api/forge`, `/api/gateway/...`) are proxied+automatically by Discord's root URL mapping, no configuration needed. Any+*other* domain the client fetches, loads an image from, or opens a script+against needs an explicit URL Mapping in the Discord Developer Portal, or+Discord's CSP blocks it.++This app has exactly one such cross-origin dependency: the R2 CDN that serves+Forge preview images and GLBs. The client calls+`patchUrlMappings([{ prefix: 'cdn', target: cdnHost }], { patchFetch: true, patchXhr: true, patchSrcAttributes: true })`+once at startup (`src/discord-activity/app.js`), which transparently rewrites+any request to that host through Discord's proxy. The matching Developer+Portal mapping is listed in+[`marketing/growth/submissions/discord-activity.md`](https://github.com/nirholas/three.ws/blob/main/marketing/growth/submissions/discord-activity.md).++Deliberately kept out of the iframe: a full WebGL `<model-viewer>`. This+codebase only ever loads `<model-viewer>` from an external CDN script tag, and+that would mean a second URL Mapping plus a `script-src` CSP exception for a+cramped voice-channel panel. The room instead shows the 2D preview image and+an `openExternalLink` button to the model's real `/forge/share/:id` page,+which opens full 3D in the user's normal browser.++## Shared state++One room per Discord Activity `instance_id` (one room per voice-channel+session). State lives server-side as an append-only event log+(`discord_activity_events`, migration+`api/_lib/migrations/20261015050000_discord_activity_rooms.sql`), folded into+one snapshot (`getRoomSnapshot` in `api/_lib/gateway/discord-activity-store.js`)+that both a fresh `GET` and a reconnecting `EventSource` agree on. Voting+reuses the platform's real `forge_votes` table (`castVote`/`removeVote` in+`api/_lib/forge-store.js`), so a room's vote count is the same tally the+public Forge gallery shows, not a separate throwaway count.++## Purchases++None. This Activity does not sell anything, so it registers no SKUs and never+calls `discordSdk.commands.startPurchase`. If a paid room tier is added later,+it goes through Discord's own IAP flow (SKUs configured in the Developer+Portal, `startPurchase` client-side) rather than our own payment rails, since+Discord requires Activity purchases to go through its own commerce API.++## Owner setup++The Activity needs a registered Discord application before any of this runs+live. Exact Developer Portal settings, the URL Mapping list, and the+Discovery listing copy are written out in+[`marketing/growth/submissions/discord-activity.md`](https://github.com/nirholas/three.ws/blob/main/marketing/growth/submissions/discord-activity.md).+Owner action is tracked in `prompts/finish/_context/production-100-OWNER-ACTIONS.md`.++---++<a id="sec-250"></a>++> **Source:** `docs/dissolve.md` · [↑ table of contents](#table-of-contents)++# Dissolve++`/dissolve` turns any glTF/GLB model into a storm of GPU particles (65k, 262k or 1M), morphs one shape into another, and lets you bend the storm with forces.++## How it works++1. `shape.js` samples the model surface in world space (skinned meshes included), area-weighted, and reads texture, vertex or material colour per sample.+2. Both shapes are Morton-sorted over a shared stage box, so particle `i` of A pairs with particle `i` of B and the morph stays spatially coherent.+3. `engine.js` keeps position and velocity in float textures and runs two ping-pong passes per frame. Points render straight from those textures.+4. Forces: black hole (with jets past the horizon), vortex, up to four shockwaves, collapse (gravity and a bouncing floor). The microphone adds bass and mid energy.++## Controls++| Key | Action |+| --- | --- |+| Space | Morph A to B and back |+| 1 to 4 | Orbit, black hole, vortex, shockwave |+| S | Swap A and B |+| C | Collapse |+| B | Detonate |+| M | Microphone |+| P | PNG snapshot |+| R | Record a clip |+| H | Hide or show the dock |++Drop a `.glb` onto the stage to load it into B (hold Shift for A). Quality (Lite, Standard, Ultra) is remembered, and the page offers Lite if frames run slow.++## Share links++`/dissolve?a=agent&b=fox&p=storm&q=standard`. `a` and `b` are shelf ids or https GLB URLs. Files from your device cannot travel in a link.++## Privacy++The microphone is opt-in, analysed in the browser as three band levels, and never recorded or uploaded.++---++<a id="sec-251"></a>> **Source:** `docs/do-i-need-crypto.md` · [↑ table of contents](#table-of-contents)@@ -70814,14 +71029,14 @@ When you do interact with on-chain features, the platform's native token is **$T## What's next-- **Create your first agent** → [Make your first agent](#sec-406)-- **Put it on your site** → [Share & embed](#sec-636)-- **Optional: register on-chain** → [Register on-chain](#sec-749)-- **Technical auth details** → [Authentication](#sec-138)+- **Create your first agent** → [Make your first agent](#sec-410)+- **Put it on your site** → [Share & embed](#sec-643)+- **Optional: register on-chain** → [Register on-chain](#sec-757)+- **Technical auth details** → [Authentication](#sec-139)----<a id="sec-249"></a>+<a id="sec-252"></a>> **Source:** `docs/doc-freshness.md` · [↑ table of contents](#table-of-contents)@@ -70961,7 +71176,7 @@ thing is to tell them how much to trust it while they read.----<a id="sec-250"></a>+<a id="sec-253"></a>> **Source:** `docs/docs-world.md` · [↑ table of contents](#table-of-contents)@@ -71050,7 +71265,7 @@ Adding a section is the same edit: append to `sections` and a new pavilion appea----<a id="sec-251"></a>+<a id="sec-254"></a>> **Source:** `docs/domains.md` · [↑ table of contents](#table-of-contents)@@ -71143,7 +71358,7 @@ The API's Cloud Run identity impersonates the dedicated service account `three-w----<a id="sec-252"></a>+<a id="sec-255"></a>> **Source:** `docs/draft-agent-mint.md` · [↑ table of contents](#table-of-contents)@@ -71373,14 +71588,14 @@ explorer link, so the evidence file never overstates what was proven.## Related-- [Selfie to Avatar](#sec-633): the pipeline whose tail calls this+- [Selfie to Avatar](#sec-640): the pipeline whose tail calls this- [Agent identities](#sec-056): what an agent identity is and how it is generated- [Agent tokens](#sec-074): what happens after a draft identity goes live- [The agent index](#sec-057): the cross-chain index that surfaces these registrations----<a id="sec-253"></a>+<a id="sec-256"></a>> **Source:** `docs/drops.md` · [↑ table of contents](#table-of-contents)@@ -71399,8 +71614,8 @@ without the studio. The part that was expensive (making the art) is a generationjob; the part that was hand-waved (proving the roll was fair) is a publishedcommitment anyone can check.-Related surfaces: [Minted 3D Assets](#sec-423) for one-off Metaplex Core mints,-[the Forge](#sec-313) for the text-to-3D pipeline every reveal runs on, and+Related surfaces: [Minted 3D Assets](#sec-427) for one-off Metaplex Core mints,+[the Forge](#sec-316) for the text-to-3D pipeline every reveal runs on, and[the avatar gallery](../public/gallery/index.html) at `/gallery` for individualavatars.@@ -71496,7 +71711,7 @@ A freshly rolled item is **sealed**. Its traits are already public and its rankis already fixed; only the art is unforged. Pressing **Reveal** on the collectionpage composes the item's prompt (the base style, then each rolled trait's promptfragment in layer order, then the hints that keep the output riggable) and-submits it to [the Forge](#sec-313). The page then polls until the GLB lands.+submits it to [the Forge](#sec-316). The page then polls until the GLB lands.Ordering the fragments by layer is what holds a collection together visually: agiven trait always occupies the same position in the prompt, so the generator's@@ -71562,7 +71777,7 @@ The schema carries `drops.collection_address` and the per-item `mint_address` /`owner_wallet` / `minted_at` columns, but nothing writes them yet: there is noendpoint that anchors a collection as a Metaplex Core collection or mints anitem into it. Revealed items are real, exportable GLBs that a creator can mint-one at a time through the existing [Minted 3D Assets](#sec-423) path today.+one at a time through the existing [Minted 3D Assets](#sec-427) path today.Wiring a drop-native mint (one Core collection per drop, each revealed itemminted into it) is the next step, and the columns are there so it does not needa schema change.@@ -71605,7 +71820,7 @@ can never shadow each other.----<a id="sec-254"></a>+<a id="sec-257"></a>> **Source:** `docs/economy-heartbeat.md` · [↑ table of contents](#table-of-contents)@@ -71771,13 +71986,13 @@ CRON_SECRET=… DURATION_MINUTES=10 node scripts/economy-heartbeat.mjs`200 { ok: true, skipped: "not_deployed" }` and fires nothing. Point`PUBLIC_APP_ORIGIN` at a local server to exercise the fan-out for real.-Related: [circulation engine](#sec-189) ·-[x402 ring economy](#sec-857) ·-[economy funding root](#sec-255) · [money map](#sec-435)+Related: [circulation engine](#sec-190) ·+[x402 ring economy](#sec-872) ·+[economy funding root](#sec-258) · [money map](#sec-439)----<a id="sec-255"></a>+<a id="sec-258"></a>> **Source:** `docs/economy-master.md` · [↑ table of contents](#table-of-contents)@@ -72345,7 +72560,7 @@ The JSON response reports `configured`, `master_sol`, `funded`, `failed`,off-registry target reached the sweep and was blocked — investigate the caller.If the Cloud Scheduler job never fires, the-[economy heartbeat](#sec-254) dispatcher (and any external HTTP cron+[economy heartbeat](#sec-257) dispatcher (and any external HTTP cronpointed at `/api/cron/economy-tick`) keeps it — and every other cron — ticking.## Audit, accounting & breach monitoring@@ -72460,26 +72675,26 @@ of the tree the master feeds:sponsor settle floor) and `x402-ring-payer` (`X402_SEED_SOLANA_SECRET_BASE58`,fallback `X402_AGENT_SOLANA_SECRET_BASE58`, floor 0.03 SOL, `holdsTokens` sosweepback leaves its USDC float alone) are topped up by this master like every- other engine (see [x402 ring economy](#sec-857) /- [autonomous x402](#sec-140)).+ other engine (see [x402 ring economy](#sec-872) /+ [autonomous x402](#sec-141)).## Related- [`api/_lib/solana-signers.js`](../api/_lib/solana-signers.js) — everyengine signer, its encoding, and how to fund/consolidate the economy wallets.-- [Circulation engine](#sec-189) — the autonomous agent-to-agent+- [Circulation engine](#sec-190) — the autonomous agent-to-agentactivity loop the funded engines drive.-- [x402 ring economy](#sec-857) — closed-loop in-house x402 settlement.+- [x402 ring economy](#sec-872) — closed-loop in-house x402 settlement.----<a id="sec-256"></a>+<a id="sec-259"></a>> **Source:** `docs/economy-solver.md` · [↑ table of contents](#table-of-contents)# The economy solver-The [in-game economy reference](#sec-380) publishes **what** the `/play`+The [in-game economy reference](#sec-384) publishes **what** the `/play`world charges. The solver publishes **what those numbers mean**: the exact expectedcash, XP and goods per hour of every action in the world, at every skill level.@@ -72705,16 +72920,16 @@ deploy.## Next-- **[The in-game economy](#sec-380)** is the raw reference: every catalog,+- **[The in-game economy](#sec-384)** is the raw reference: every catalog,gate, settlement path and the JSON wire format.-- **[Earn and spend in /play](#sec-721)** walks the loop+- **[Earn and spend in /play](#sec-729)** walks the loopby hand, in the world.- **[three.ws/play/solver](https://three.ws/play/solver)** is the interactive versionof everything above.----<a id="sec-257"></a>+<a id="sec-260"></a>> **Source:** `docs/editor.md` · [↑ table of contents](#table-of-contents)@@ -73063,7 +73278,7 @@ The full contract lives in [specs/EDITOR_SPEC.md](https://github.com/nirholas/th----<a id="sec-258"></a>+<a id="sec-261"></a>> **Source:** `docs/education-pilot-bucharest.md` · [↑ table of contents](#table-of-contents)@@ -73134,7 +73349,7 @@ Status: exploratory. A contact has offered a local connection to the office of t----<a id="sec-259"></a>+<a id="sec-262"></a>> **Source:** `docs/embedding.md` · [↑ table of contents](#table-of-contents)@@ -73785,9 +74000,29 @@ Also add the script tag to `pages/_document.js` or your root layout:/>```+### WordPress++Install the **three.ws Agent** plugin ([`integrations/wordpress/three-ws-agent/`](../integrations/wordpress/three-ws-agent)): a Gutenberg block (category: Embeds) with an inspector panel for On-chain URI, Agent ID, Chain ID, Model URL, Background and Framing, plus a `[three_ws_agent]` shortcode for the classic editor, widgets, and theme templates:++```+[three_ws_agent src="agent://base/42" background="dark" framing="portrait"]+```++Both render identical markup and enqueue the same SRI-pinned loader script, so there is no divergence between the block editor's preview and the published page. No build step, no npm, no WordPress.com Business plan requirement. See the plugin's [README](../integrations/wordpress/three-ws-agent/README.md) for layout and local testing with the official Plugin Check tool.++### Squarespace++Add the script tag via Settings → Advanced → Code Injection → Header. Place the element in a Code block on any page.++### Framer++Install the **three.ws Agent** code component ([`integrations/framer/`](../integrations/framer)): paste `pinned-release.ts`, `Agent3DView.tsx`, and `Agent3D.tsx` into a Framer project's code file panel, then drag the component onto the canvas. Property controls expose On-chain URI, Agent ID, Chain ID, Model URL, Background, Framing, Poster and Autoplay, no code required after setup. See the component's [README](../integrations/framer/README.md).+### Webflow-Use an **Embed** block with the iframe method — Webflow's custom code can load the web component script in Page Settings → Custom Code → `<head>`:+Install the **three.ws Agent** Code Component ([`integrations/webflow/`](../integrations/webflow)) with `webflow devlink import` into a Webflow Workspace, then drag it from the Components panel in the Designer. The same On-chain URI / Agent ID / Chain ID / Model URL / Background / Framing / Poster / Autoplay props are exposed in the Properties panel. See the component's [README](../integrations/webflow/README.md).++For a quick embed with no library install, use an **Embed** block instead: load the script in Page Settings → Custom Code → `<head>`, then add an HTML Embed element anywhere on the page:```html<script type="module"@@ -73795,20 +74030,10 @@ Use an **Embed** block with the iframe method — Webflow's custom code can load</script>```-Then add an HTML Embed element anywhere on the page:-```html<agent-3d src="agent://base/42" style="width:100%;height:500px"></agent-3d>```-### Squarespace--Add the script tag via Settings → Advanced → Code Injection → Header. Place the element in a Code block on any page.--### Framer--Framer supports custom code components — wrap `<agent-3d>` in a code component using the web component approach. Mark it as client-only since Framer also SSRs.-### ShopifyAdd the script tag to `theme.liquid` inside `<head>`, then use `<agent-3d>` directly in product page templates or section files.@@ -73871,10 +74096,10 @@ The platform records anonymous embed impressions (country, referrer hostname) vi## See also-- [Architecture Overview](#sec-130)+- [Architecture Overview](#sec-131)- [Agent System Overview](#sec-068)-- [Web Component reference](#sec-799) — full attribute list-- [Widgets](#sec-802) — Widget Studio and widget types+- [Web Component reference](#sec-811) — full attribute list+- [Widgets](#sec-814) — Widget Studio and widget types- [specs/EMBED_SPEC.md](../specs/EMBED_SPEC.md) — authoritative web component spec- [specs/EMBED_HOST_PROTOCOL.md](../specs/EMBED_HOST_PROTOCOL.md) — versioned postMessage protocol@@ -73889,7 +74114,7 @@ three.ws examples repo, so it is installed, run, and link-checked before every r----<a id="sec-260"></a>+<a id="sec-263"></a>> **Source:** `docs/embody.md` · [↑ table of contents](#table-of-contents)@@ -73994,14 +74219,14 @@ Embody is a thin, honest wire over pieces that already exist — no new pipeline## Related-- [Live embodiment](#sec-414) — the 3D Studio tools that persist and drive a body in chat.-- [x402 Paid Endpoints](#sec-854) — the full paid catalog and pricing.-- [x402 Buyer Client](#sec-851) — how to settle a 402 challenge from code.-- [Avatar creation](#sec-144) — generate a rigged avatar in the web UI.+- [Live embodiment](#sec-418) — the 3D Studio tools that persist and drive a body in chat.+- [x402 Paid Endpoints](#sec-869) — the full paid catalog and pricing.+- [x402 Buyer Client](#sec-866) — how to settle a 402 challenge from code.+- [Avatar creation](#sec-145) — generate a rigged avatar in the web UI.----<a id="sec-261"></a>+<a id="sec-264"></a>> **Source:** `docs/engine-bridges.md` · [↑ table of contents](#table-of-contents)@@ -74011,7 +74236,7 @@ A glTF viewer answers "does the mesh load." A game engine's import step asksa different question: can this ship in *my* project, with *my* pipeline, anddrop into my scene with one click? The Forge API already generates themesh; these three packages are the one-click part, one per engine, each-calling the exact same [public Forge API](#sec-311) a browser+calling the exact same [public Forge API](#sec-314) a browserwould.- **Contract:** [`specs/ENGINE_BRIDGE.md`](https://github.com/nirholas/three.ws/blob/main/specs/ENGINE_BRIDGE.md), the shared auth/catalog/generate/poll/download/import contract all three bridges implement independently.@@ -74027,7 +74252,7 @@ the same split [`packages/blender-mcp`](https://github.com/nirholas/three.ws/treUnity (C#), Godot (GDScript), and Unreal (C++) have nothing in common at thelanguage level, but the API they're calling is one surface:-[`POST /api/forge`](#sec-311) to submit, `GET+[`POST /api/forge`](#sec-314) to submit, `GET/api/forge?job=<id>` to poll, and a plain HTTPS GET to download thefinished `.glb`. Writing the contract down once in[`specs/ENGINE_BRIDGE.md`](https://github.com/nirholas/three.ws/blob/main/specs/ENGINE_BRIDGE.md)@@ -74066,19 +74291,19 @@ provider instead of the free-tier lane.import, use **Window > three.ws Forge Bridge**. See[`packages/unreal-bridge/README.md`](https://github.com/nirholas/three.ws/blob/main/packages/unreal-bridge/README.md).-Related: [the Forge pipeline](#sec-311) for how a submission is-routed and served, [Engine QA](#sec-262) for grading whether an+Related: [the Forge pipeline](#sec-314) for how a submission is+routed and served, [Engine QA](#sec-265) for grading whether animported mesh will actually run at 60fps once it's in the engine.----<a id="sec-262"></a>+<a id="sec-265"></a>> **Source:** `docs/engine-qa.md` · [↑ table of contents](#table-of-contents)# Engine QA: a real-time-engine fitness grade for 3D assets-A renderer and a game engine ask different questions about the same GLB. [Simulation readiness](#sec-643) tells you whether a physics solver can integrate the mesh. Nothing tells you whether a real-time engine will actually run it at 60fps, until it stutters on a phone three weeks after import.+A renderer and a game engine ask different questions about the same GLB. [Simulation readiness](#sec-651) tells you whether a physics solver can integrate the mesh. Nothing tells you whether a real-time engine will actually run it at 60fps, until it stutters on a phone three weeks after import.**Engine QA is that grade, computed from the file itself.** Point it at a GLB and it answers the import-time questions an engine's own profiler would eventually raise anyway: how many draw calls does the default scene actually cost, how many materials does it carry, is the texture resolution matched to the mesh's real-world size, does each level of a LOD chain fit its triangle budget and shrink monotonically, and is the mesh cheap enough, and closed enough, to use as its own physics collider.@@ -74191,12 +74416,12 @@ A non-watertight mesh never produces a silently broken STL. Instead it answers `| `triangleBudget` | Each LOD level's triangle count against its ceiling (`LOD0` 100k, `LOD1` 40k, `LOD2` 12k; an unrecognized level name falls back to `LOD0`'s ceiling), plus the monotonic-decrease rule across the whole chain. | Per-level `pass`/`fail` at its ceiling; chain `fail` if any level fails or the sequence does not strictly decrease. | No LOD chain supplied (`lods=1` not sent). || `collider` | Reuses the print pipeline's watertight/manifold analysis; `fail` if not watertight, `warn` if watertight but over 5,000 triangles (heavier than a mesh collider should be), `pass` otherwise. | Budget: 5,000 triangles. | The mesh could not be loaded for collider analysis. |-The texel-density window is deliberately wide: below the floor, textures visibly smear up close; above the ceiling, the asset is paying storage and bandwidth for resolution nobody's eye resolves at normal viewing distance. Both bands assume the mesh's glTF units are real meters, which [simulation readiness](#sec-643) is the tool to confirm when you are not sure.+The texel-density window is deliberately wide: below the floor, textures visibly smear up close; above the ceiling, the asset is paying storage and bandwidth for resolution nobody's eye resolves at normal viewing distance. Both bands assume the mesh's glTF units are real meters, which [simulation readiness](#sec-651) is the tool to confirm when you are not sure.## Where you will see it- **[The GLB viewer](https://three.ws/viewer)** (`public/viewer.html`) shows the `<engine-qa>` badge beside the simulation-readiness badge for any `https://` model you open. Grading is one click (`"Check engine fitness"`), not automatic, because scoring an arbitrary URL means fetching the whole file; the LOD-chain upgrade (`"Build & grade LOD chain"`) is a second, explicit step because it is real decimation work.-- **[Rig Doctor](#sec-617)** runs the same badge, but its first pass never touches the network: [`src/engine-qa-client.js`](https://github.com/nirholas/three.ws/blob/main/src/engine-qa-client.js) grades draw calls, material count, and texel density straight from the mesh already loaded in the tab for rigging, using the exact same thresholds as the server (both import [`api/_lib/engine-qa-core.js`](https://github.com/nirholas/three.ws/blob/main/api/_lib/engine-qa-core.js), so the two can never disagree). Collider fitness and a real LOD chain still need the server endpoint, offered as the same upgrade button.+- **[Rig Doctor](#sec-624)** runs the same badge, but its first pass never touches the network: [`src/engine-qa-client.js`](https://github.com/nirholas/three.ws/blob/main/src/engine-qa-client.js) grades draw calls, material count, and texel density straight from the mesh already loaded in the tab for rigging, using the exact same thresholds as the server (both import [`api/_lib/engine-qa-core.js`](https://github.com/nirholas/three.ws/blob/main/api/_lib/engine-qa-core.js), so the two can never disagree). Collider fitness and a real LOD chain still need the server endpoint, offered as the same upgrade button.- **The shared `<engine-qa>` component** ([`public/engine-qa-panel.js`](https://github.com/nirholas/three.ws/blob/main/public/engine-qa-panel.js)) is what both surfaces mount: one custom element, four states (`loading`, `ungraded` with the offer button, a graded `report`, or `failed` with retry), so the viewer and Rig Doctor can never drift in how the grade is presented.## A LOD chain alongside your generation@@ -74233,14 +74458,14 @@ Both graders, server and browser, import their thresholds and verdict math from## Related-- [Simulation readiness](#sec-643): the other physics-adjacent grade for the same file. Simulation readiness asks "can a solver integrate this"; engine QA asks "will a renderer run it at 60fps."-- [Rig Doctor](#sec-617): where the browser-only partial grade runs today, alongside rig diagnosis and retargeting.-- [The forge pipeline](#sec-311): how a generated mesh becomes a delivery variant, an optional web-sized variant, and now an optional LOD-chain variant.-- [Verifiable 3D provenance](#sec-556): a signed claim about who made a model and whether the bytes were altered, the same pattern simulation readiness rides inside.+- [Simulation readiness](#sec-651): the other physics-adjacent grade for the same file. Simulation readiness asks "can a solver integrate this"; engine QA asks "will a renderer run it at 60fps."+- [Rig Doctor](#sec-624): where the browser-only partial grade runs today, alongside rig diagnosis and retargeting.+- [The forge pipeline](#sec-314): how a generated mesh becomes a delivery variant, an optional web-sized variant, and now an optional LOD-chain variant.+- [Verifiable 3D provenance](#sec-563): a signed claim about who made a model and whether the bytes were altered, the same pattern simulation readiness rides inside.----<a id="sec-263"></a>+<a id="sec-266"></a>> **Source:** `docs/erc8004.md` · [↑ table of contents](#table-of-contents)@@ -74987,7 +75212,7 @@ The same MAINNET addresses apply to all 15 mainnets. The same TESTNET addresses----<a id="sec-264"></a>+<a id="sec-267"></a>> **Source:** `docs/erc8004/validation-attestation.md` · [↑ table of contents](#table-of-contents)@@ -75149,7 +75374,7 @@ reported the reverts as "no attestation yet".----<a id="sec-265"></a>+<a id="sec-268"></a>> **Source:** `docs/event-markets-staking.md` · [↑ table of contents](#table-of-contents)@@ -75257,13 +75482,13 @@ Nothing below has been run. Fund-moving commands print recipient, amount, token----<a id="sec-266"></a>+<a id="sec-269"></a>> **Source:** `docs/event-markets.md` · [↑ table of contents](#table-of-contents)# Event Markets-A free-to-play "who wins this?" market for every three.ws event, with the entrants as outcomes. Picks carry points, never funds. Build briefs: [docs/prompts/event-markets/](#sec-555). Core module: `api/_lib/event-markets/`.+A free-to-play "who wins this?" market for every three.ws event, with the entrants as outcomes. Picks carry points, never funds. Build briefs: [docs/prompts/event-markets/](#sec-562). Core module: `api/_lib/event-markets/`.## Markets, picks and odds (core)@@ -75557,7 +75782,7 @@ Source: [api/_mcpagent/event-market-forecast-tools.js](../api/_mcpagent/event-ma----<a id="sec-267"></a>+<a id="sec-270"></a>> **Source:** `docs/event-readiness/01-play-first-impression.md` · [↑ table of contents](#table-of-contents)@@ -75601,7 +75826,7 @@ What you changed (files + one line each), what you verified in-browser, anything----<a id="sec-268"></a>+<a id="sec-271"></a>> **Source:** `docs/event-readiness/02-play-mobile.md` · [↑ table of contents](#table-of-contents)@@ -75637,7 +75862,7 @@ Root cause of any crash found (with the harness evidence), fixes applied, remain----<a id="sec-269"></a>+<a id="sec-272"></a>> **Source:** `docs/event-readiness/03-play-performance.md` · [↑ table of contents](#table-of-contents)@@ -75679,7 +75904,7 @@ Numbers table (before/after), each fix in one line, anything intentionally skipp----<a id="sec-270"></a>+<a id="sec-273"></a>> **Source:** `docs/event-readiness/04-play-multiplayer-net.md` · [↑ table of contents](#table-of-contents)@@ -75719,7 +75944,7 @@ Each failure mode tested and its result (pass / fixed / cannot-fix-with-reason).----<a id="sec-271"></a>+<a id="sec-274"></a>> **Source:** `docs/event-readiness/05-play-economy-loops.md` · [↑ table of contents](#table-of-contents)@@ -75760,7 +75985,7 @@ Loop-by-loop pass/fixed table, every price mismatch found and which side you cor----<a id="sec-272"></a>+<a id="sec-275"></a>> **Source:** `docs/event-readiness/06-play-auth-errors.md` · [↑ table of contents](#table-of-contents)@@ -75796,7 +76021,7 @@ A failure-mode table: scenario, what happened before, what happens now. Call out----<a id="sec-273"></a>+<a id="sec-276"></a>> **Source:** `docs/event-readiness/07-platform-smoke-sweep.md` · [↑ table of contents](#table-of-contents)@@ -75847,7 +76072,7 @@ Battery results before and after, fixes grouped by page, the manual event-funnel----<a id="sec-274"></a>+<a id="sec-277"></a>> **Source:** `docs/event-readiness/08-api-production-health.md` · [↑ table of contents](#table-of-contents)@@ -75878,7 +76103,7 @@ Solana-first status summary, then the 8 items with their binary states, then log----<a id="sec-275"></a>+<a id="sec-278"></a>> **Source:** `docs/event-readiness/09-accessibility-i18n.md` · [↑ table of contents](#table-of-contents)@@ -75914,7 +76139,7 @@ Per-category pass/fixed list, the keyboard-only session result, locales verified----<a id="sec-276"></a>+<a id="sec-279"></a>> **Source:** `docs/event-readiness/10-event-day-runbook.md` · [↑ table of contents](#table-of-contents)@@ -75952,13 +76177,13 @@ Old/new scaling values, capacity smoke numbers, rollback rehearsal result, and t----<a id="sec-277"></a>+<a id="sec-280"></a>> **Source:** `docs/event-readiness/11-event-live-ops.md` · [↑ table of contents](#table-of-contents)# Feature 11: live event ops (broadcast, stage moments, event config)-Tomorrow the $THREE world hosts a live event. The countdown already exists (`src/game/event-countdown.js` reads `public/event.json` through the shared `src/shared/event-config.js` reader and mounts a lobby banner + in-world pill). The live layer has since shipped in two of its three parts: the operator can speak to everyone in the world at once (`/internal/announce` + `scripts/announce-play.mjs`), and the world reacts when the event goes live (`src/game/meetup-event.js` agenda beats, go-live banner, and `src/game/fireworks.js`; the walkthrough is [docs/play-live-events.md](#sec-497)). What is still missing is item 3, changing the event config without a redeploy. The list below records what exists so a rerun builds only the gap.+Tomorrow the $THREE world hosts a live event. The countdown already exists (`src/game/event-countdown.js` reads `public/event.json` through the shared `src/shared/event-config.js` reader and mounts a lobby banner + in-world pill). The live layer has since shipped in two of its three parts: the operator can speak to everyone in the world at once (`/internal/announce` + `scripts/announce-play.mjs`), and the world reacts when the event goes live (`src/game/meetup-event.js` agenda beats, go-live banner, and `src/game/fireworks.js`; the walkthrough is [docs/play-live-events.md](#sec-504)). What is still missing is item 3, changing the event config without a redeploy. The list below records what exists so a rerun builds only the gap.## Where the code lives@@ -75973,7 +76198,7 @@ Tomorrow the $THREE world hosts a live event. The countdown already exists (`src1. **Operator broadcast.** Shipped as `POST /internal/announce` on the multiplayer server (`multiplayer/src/index.js`): HMAC-signed with `MULTIPLAYER_SHARED_SECRET` (falling back to `HOLDER_PASS_SECRET`) and timestamp-bound, so an unsigned or stale call is rejected before it reaches a room; there is no separate rate limit, the signature is the gate. It broadcasts on the existing `notice` channel (`kind: 'event'`, text capped at 300 characters, optional `title` 80 and `detail` 200, `durationMs` capped at 120 s) to every live `walk_world` room or one coin's world, so older clients get a toast and newer ones the centre-screen banner. Verify the banner queues, dismisses, and never overlaps chat or the joystick.2. **Go-live moment.** Shipped in `src/game/meetup-event.js` (agenda, go-live banner) and `src/game/fireworks.js`, on the countdown pill's pulsing LIVE state. Everything reads the one config and mounts nothing when there is no event; keep it that way.3. **Event config hardening.** Still open. `event.json` is baked into the image at build time, which means a config change mid-event needs a redeploy (today: `npm run event:schedule -- ... --apply`, `npm run check:event`, then the deploy runbook). Add a small authed read path (for example an `app_settings`-backed override checked after the static file, in `api/_lib/event-config.js` and `multiplayer/src/event-window.js` alike, since both read the file independently) so the operator can extend, rename, or end the event live without a deploy. Document the exact curl in the runbook (`10-event-day-runbook.md`).-4. **Broadcast script.** Shipped as `scripts/announce-play.mjs` (`node scripts/announce-play.mjs --title "Wheel hour" --detail "..." --coin <mint> --duration-ms 30000 "message"`; `--server http://localhost:2567` for a local test). It prints how many rooms and players it reached; the operator copy is in [LIVE-OPS.md](#sec-291).+4. **Broadcast script.** Shipped as `scripts/announce-play.mjs` (`node scripts/announce-play.mjs --title "Wheel hour" --detail "..." --coin <mint> --duration-ms 30000 "message"`; `--server http://localhost:2567` for a local test). It prints how many rooms and players it reached; the operator copy is in [LIVE-OPS.md](#sec-294).## Verify@@ -75987,7 +76212,7 @@ What shipped (files + one line each), the exact operator commands for event day,----<a id="sec-278"></a>+<a id="sec-281"></a>> **Source:** `docs/event-readiness/12-photo-mode-share.md` · [↑ table of contents](#table-of-contents)@@ -76023,7 +76248,7 @@ Files shipped, a saved sample capture path, what the share flow does per platfor----<a id="sec-279"></a>+<a id="sec-282"></a>> **Source:** `docs/event-readiness/13-event-quests-leaderboard.md` · [↑ table of contents](#table-of-contents)@@ -76059,7 +76284,7 @@ The quest list as players will see it, files shipped, the leaderboard endpoint U----<a id="sec-280"></a>+<a id="sec-283"></a>> **Source:** `docs/event-readiness/14-welcome-concierge.md` · [↑ table of contents](#table-of-contents)@@ -76094,7 +76319,7 @@ Files shipped, the persona prompt location, the tour stops, what the concierge s----<a id="sec-281"></a>+<a id="sec-284"></a>> **Source:** `docs/event-readiness/15-live-hype-feed.md` · [↑ table of contents](#table-of-contents)@@ -76128,7 +76353,7 @@ Files shipped, the threshold logic in two sentences, measured DOM/node behavior----<a id="sec-282"></a>+<a id="sec-285"></a>> **Source:** `docs/event-readiness/16-invite-flow.md` · [↑ table of contents](#table-of-contents)@@ -76162,7 +76387,7 @@ Files shipped, any dependency added (name, weekly downloads, license, why), a re----<a id="sec-283"></a>+<a id="sec-286"></a>> **Source:** `docs/event-readiness/17-plaza-live-show.md` · [↑ table of contents](#table-of-contents)@@ -76199,13 +76424,13 @@ Files shipped, how `stageId` is derived, the join and teardown lifecycle in thre----<a id="sec-284"></a>+<a id="sec-287"></a>> **Source:** `docs/event-readiness/18-coin-wars-portal.md` · [↑ table of contents](#table-of-contents)# Feature 18: Coin Wars portal inside the world-Coin Wars is finished and, since the portal landed, visible. `ClashRoom` runs full community-vs-community battles (lobby, countdown, live, sudden death, kill cap, round clock) with an Elo league behind it, the arena is a real page at /play/war, and every coin world's plaza has a war portal (`src/game/war-portal.js`, constructed by `coincommunities.js`) to see the standings, queue for a war, and come back with the result without leaving /play. The player-facing walkthrough is [docs/coin-wars.md](#sec-195). This prompt is now the spec to verify against and extend, not a blank build.+Coin Wars is finished and, since the portal landed, visible. `ClashRoom` runs full community-vs-community battles (lobby, countdown, live, sudden death, kill cap, round clock) with an Elo league behind it, the arena is a real page at /play/war, and every coin world's plaza has a war portal (`src/game/war-portal.js`, constructed by `coincommunities.js`) to see the standings, queue for a war, and come back with the result without leaving /play. The player-facing walkthrough is [docs/coin-wars.md](#sec-196). This prompt is now the spec to verify against and extend, not a blank build.## Where the code lives@@ -76237,13 +76462,13 @@ Files shipped, the standings read path (existing or the one endpoint you added),----<a id="sec-285"></a>+<a id="sec-288"></a>> **Source:** `docs/event-readiness/19-forge-props-live.md` · [↑ table of contents](#table-of-contents)# Feature 19: forge 3D props live inside build mode-The platform's headline capability is text to 3D, and the world's build mode can now use it: the prop palette has a Forge form (and chat takes `/forge <prompt>`), `src/game/forge-prop.js` drives the free draft lane, and the finished GLB rides the uploaded-prop pipeline so everyone in the world sees it and the room persists it ([docs/play-forge-in-world.md](#sec-495)). What shipped is the pipeline; what is still open is the placement-first hologram, the size ceiling, and the server-side abuse limits below. At a live event this is the demo moment, and the size ceiling is what keeps it from becoming the iOS crash.+The platform's headline capability is text to 3D, and the world's build mode can now use it: the prop palette has a Forge form (and chat takes `/forge <prompt>`), `src/game/forge-prop.js` drives the free draft lane, and the finished GLB rides the uploaded-prop pipeline so everyone in the world sees it and the room persists it ([docs/play-forge-in-world.md](#sec-502)). What shipped is the pipeline; what is still open is the placement-first hologram, the size ceiling, and the server-side abuse limits below. At a live event this is the demo moment, and the size ceiling is what keeps it from becoming the iOS crash.## Where the code lives@@ -76274,7 +76499,7 @@ Files shipped, the size ceiling values and where they are enforced, the rate-lim----<a id="sec-286"></a>+<a id="sec-289"></a>> **Source:** `docs/event-readiness/20-world-chat-scrollback.md` · [↑ table of contents](#table-of-contents)@@ -76311,7 +76536,7 @@ Files shipped, the cap and TTL chosen, the bridge decision and why, join-time pa----<a id="sec-287"></a>+<a id="sec-290"></a>> **Source:** `docs/event-readiness/21-party-system.md` · [↑ table of contents](#table-of-contents)@@ -76347,7 +76572,7 @@ Files shipped, where party state lives and its TTL, the teleport validation rule----<a id="sec-288"></a>+<a id="sec-291"></a>> **Source:** `docs/event-readiness/22-venue-projector-mode.md` · [↑ table of contents](#table-of-contents)@@ -76383,7 +76608,7 @@ Files shipped, the exact URL to put on the venue machine, the spectator join con----<a id="sec-289"></a>+<a id="sec-292"></a>> **Source:** `docs/event-readiness/23-signature-wall.md` · [↑ table of contents](#table-of-contents)@@ -76420,7 +76645,7 @@ Files shipped, the store chosen and why, the overflow design in two sentences, t----<a id="sec-290"></a>+<a id="sec-293"></a>> **Source:** `docs/event-readiness/24-dance-off.md` · [↑ table of contents](#table-of-contents)@@ -76456,7 +76681,7 @@ Files shipped, the round timings chosen, the vote targeting rule, the reward and----<a id="sec-291"></a>+<a id="sec-294"></a>> **Source:** `docs/event-readiness/LIVE-OPS.md` · [↑ table of contents](#table-of-contents)@@ -76469,7 +76694,7 @@ Prepared 2026-08-08. Project `aerial-vehicle-466722-p5`, region `us-central1`.## The link and the release-**Event URL** (the canonical $THREE world, from [README.md](#sec-292)):+**Event URL** (the canonical $THREE world, from [README.md](#sec-295)):```https://three.ws/play?coin=FeMbDoX7R1Psc4GEcvJdsbNbZA3bfztcyDCatJVJpump&name=three.ws&symbol=three&image=%2Fapi%2Fimg%3Furl%3Dhttps%253A%252F%252Fipfs.io%252Fipfs%252Fbafybeihe22b5sxr3ihnxt7pregfieyteqvubqhik3j3y4bbx243xlqjw3q%26seed%3DFeMbDoX7R1Psc4GEcvJdsbNbZA3bfztcyDCatJVJpump@@ -76756,7 +76981,7 @@ page.----<a id="sec-292"></a>+<a id="sec-295"></a>> **Source:** `docs/event-readiness/README.md` · [↑ table of contents](#table-of-contents)@@ -76768,40 +76993,40 @@ Suggested order and parallelism (audits):| # | Prompt | Surface | Can run in parallel with ||---|--------|---------|--------------------------|-| 1 | [01-play-first-impression.md](#sec-267) | /play load, intro, onboarding UX | 4, 5, 7, 8 |-| 2 | [02-play-mobile.md](#sec-268) | /play on phones (stability + touch) | 7, 8 |-| 3 | [03-play-performance.md](#sec-269) | /play load weight, FPS, memory | 7, 8 |-| 4 | [04-play-multiplayer-net.md](#sec-270) | WebSocket, reconnects, voice, crowd | 1, 5 |-| 5 | [05-play-economy-loops.md](#sec-271) | Store, bank, wheel, combat, quests, cosmetics | 1, 4 |-| 6 | [06-play-auth-errors.md](#sec-272) | Sign-in, gates, error/empty states, console | after 1 |-| 7 | [07-platform-smoke-sweep.md](#sec-273) | Every page on the live site | 1, 2, 3 |-| 8 | [08-api-production-health.md](#sec-274) | Cloud Run, crons, logs, DB, x402 | 1, 2, 3 |-| 9 | [09-accessibility-i18n.md](#sec-275) | Keyboard, ARIA, contrast, translations | after 1 |-| 10 | [10-event-day-runbook.md](#sec-276) | Pre-scale, monitoring loop, rollback | last, after all fixes deploy |+| 1 | [01-play-first-impression.md](#sec-270) | /play load, intro, onboarding UX | 4, 5, 7, 8 |+| 2 | [02-play-mobile.md](#sec-271) | /play on phones (stability + touch) | 7, 8 |+| 3 | [03-play-performance.md](#sec-272) | /play load weight, FPS, memory | 7, 8 |+| 4 | [04-play-multiplayer-net.md](#sec-273) | WebSocket, reconnects, voice, crowd | 1, 5 |+| 5 | [05-play-economy-loops.md](#sec-274) | Store, bank, wheel, combat, quests, cosmetics | 1, 4 |+| 6 | [06-play-auth-errors.md](#sec-275) | Sign-in, gates, error/empty states, console | after 1 |+| 7 | [07-platform-smoke-sweep.md](#sec-276) | Every page on the live site | 1, 2, 3 |+| 8 | [08-api-production-health.md](#sec-277) | Cloud Run, crons, logs, DB, x402 | 1, 2, 3 |+| 9 | [09-accessibility-i18n.md](#sec-278) | Keyboard, ARIA, contrast, translations | after 1 |+| 10 | [10-event-day-runbook.md](#sec-279) | Pre-scale, monitoring loop, rollback | last, after all fixes deploy |Feature builds (run after audits 1-3 land, or in parallel if staffed; 12, 14, and 16 interlink but each stands alone):| # | Prompt | Builds | Depends on ||---|--------|--------|------------|-| 11 | [11-event-live-ops.md](#sec-277) | Operator broadcast, go-live moment, live event config | nothing |-| 12 | [12-photo-mode-share.md](#sec-278) | Photo mode with branded one-tap share | nothing |-| 13 | [13-event-quests-leaderboard.md](#sec-279) | Time-boxed quest line + live leaderboard + cosmetic reward | nothing (better with 12) |-| 14 | [14-welcome-concierge.md](#sec-280) | Greeter NPC, guided tour, event-aware opening line | nothing |-| 15 | [15-live-hype-feed.md](#sec-281) | Activity ticker + market hype moments | nothing (better with 13) |-| 16 | [16-invite-flow.md](#sec-282) | Invite sheet, QR, OG card truth, arrival continuity | nothing (better with 14) |+| 11 | [11-event-live-ops.md](#sec-280) | Operator broadcast, go-live moment, live event config | nothing |+| 12 | [12-photo-mode-share.md](#sec-281) | Photo mode with branded one-tap share | nothing |+| 13 | [13-event-quests-leaderboard.md](#sec-282) | Time-boxed quest line + live leaderboard + cosmetic reward | nothing (better with 12) |+| 14 | [14-welcome-concierge.md](#sec-283) | Greeter NPC, guided tour, event-aware opening line | nothing |+| 15 | [15-live-hype-feed.md](#sec-284) | Activity ticker + market hype moments | nothing (better with 13) |+| 16 | [16-invite-flow.md](#sec-285) | Invite sheet, QR, OG card truth, arrival continuity | nothing (better with 14) |Capability builds (17-24): each wires an existing, finished subsystem into the world or adds a missing social primitive. All stand alone; the noted pairings just make them better together.| # | Prompt | Builds | Wires in / pairs with ||---|--------|--------|-----------------------|-| 17 | [17-plaza-live-show.md](#sec-283) | Live hosted show on a plaza stage, with $THREE tips | StageRoom + ShowDirector (built, unreachable from /play) |-| 18 | [18-coin-wars-portal.md](#sec-284) | In-world Coin Wars portal: standings, queue, spectate | ClashRoom + war standings (built, arena-page only) |-| 19 | [19-forge-props-live.md](#sec-285) | Text-to-3D prop generation inside build mode | Forge lane + the networked prop pipeline |-| 20 | [20-world-chat-scrollback.md](#sec-286) | Chat scrollback for late joiners + community-feed bridge | the WalkRoom relay + api/community/messages |-| 21 | [21-party-system.md](#sec-287) | Parties: form, see, reach, and talk to your crew | friends/presence stack; pairs with 13, 16 |-| 22 | [22-venue-projector-mode.md](#sec-288) | Broadcast spectator view for the venue big screen | camera rig + event.json; pairs with 15, 16, 17 |-| 23 | [23-signature-wall.md](#sec-289) | Persistent signature wall, the event's artifact | world-persist patterns + name safety |-| 24 | [24-dance-off.md](#sec-290) | Judged dance-off rounds with crowd voting and tips | dance floor beat + King of the Totem round machine |+| 17 | [17-plaza-live-show.md](#sec-286) | Live hosted show on a plaza stage, with $THREE tips | StageRoom + ShowDirector (built, unreachable from /play) |+| 18 | [18-coin-wars-portal.md](#sec-287) | In-world Coin Wars portal: standings, queue, spectate | ClashRoom + war standings (built, arena-page only) |+| 19 | [19-forge-props-live.md](#sec-288) | Text-to-3D prop generation inside build mode | Forge lane + the networked prop pipeline |+| 20 | [20-world-chat-scrollback.md](#sec-289) | Chat scrollback for late joiners + community-feed bridge | the WalkRoom relay + api/community/messages |+| 21 | [21-party-system.md](#sec-290) | Parties: form, see, reach, and talk to your crew | friends/presence stack; pairs with 13, 16 |+| 22 | [22-venue-projector-mode.md](#sec-291) | Broadcast spectator view for the venue big screen | camera rig + event.json; pairs with 15, 16, 17 |+| 23 | [23-signature-wall.md](#sec-292) | Persistent signature wall, the event's artifact | world-persist patterns + name safety |+| 24 | [24-dance-off.md](#sec-293) | Judged dance-off rounds with crowd voting and tips | dance floor beat + King of the Totem round machine |Rules that apply to every prompt in this pack:@@ -76813,7 +77038,7 @@ Rules that apply to every prompt in this pack:----<a id="sec-293"></a>+<a id="sec-296"></a>> **Source:** `docs/event-souvenirs.md` · [↑ table of contents](#table-of-contents)@@ -76834,7 +77059,7 @@ walks past you.The first one is the **Meetup Laurel**: a gold laurel circlet, open at thefront, with three pearl berries in the gap. It was configured for the-[`$THREE` First Holders Meetup](#sec-497) on 2026-08-09, but the+[`$THREE` First Holders Meetup](#sec-504) on 2026-08-09, but themultiplayer service was not redeployed with the grant code before that window,so the grant never ran and nobody holds one. The window has closed, and thelaurel stays retired rather than being handed out later under a different@@ -77085,21 +77310,21 @@ machine prefer the two above, which cover the same ground between them.## Related-- **[Live events in /play](#sec-497)** covers the rest of what that+- **[Live events in /play](#sec-504)** covers the rest of what thatconfig file drives: the countdown, the agenda drawer, the fireworks.-- **[The in-game economy](#sec-380)** covers the two currencies and+- **[The in-game economy](#sec-384)** covers the two currencies andthe `$THREE` boutique the souvenir deliberately stays out of.-- **[Coin communities](#sec-194)** covers the worlds the events happen in.+- **[Coin communities](#sec-195)** covers the worlds the events happen in.----<a id="sec-294"></a>+<a id="sec-297"></a>> **Source:** `docs/everything.md` · [↑ table of contents](#table-of-contents)# /everything: browse every feature by goal-three.ws has about 340 product pages. The nav shows roughly 30 of them to a first-time visitor on purpose (see [onboarding-tier.md](#sec-457)), and `/sitemap` lists all of them by section. Neither answers the question a visitor actually has: "I want to animate my avatar, where do I go?"+three.ws has about 340 product pages. The nav shows roughly 30 of them to a first-time visitor on purpose (see [onboarding-tier.md](#sec-461)), and `/sitemap` lists all of them by section. Neither answers the question a visitor actually has: "I want to animate my avatar, where do I go?"`/everything` answers it. Every product page is assigned one **goal** (a job), and the page is a searchable directory of those goals.@@ -77138,7 +77363,7 @@ scripts/lib/feature-jobs.mjs ─┘ (pages[].job, jobs[])----<a id="sec-295"></a>+<a id="sec-298"></a>> **Source:** `docs/examples.md` · [↑ table of contents](#table-of-contents)@@ -77879,7 +78104,7 @@ genuinely invested in the user's progress.## Every runnable example in the repo-The repo ships 49 examples: 12 web component demos, 11 end-to-end projects, and 26 package example sets. This table is generated from what is on disk, so it cannot list one that was deleted or miss one that was added. The machine-readable version is [data/examples.json](../data/examples.json).+The repo ships 50 examples: 12 web component demos, 12 end-to-end projects, and 26 package example sets. This table is generated from what is on disk, so it cannot list one that was deleted or miss one that was added. The machine-readable version is [data/examples.json](../data/examples.json).### Example projects@@ -77894,6 +78119,7 @@ The repo ships 49 examples: 12 web component demos, 11 end-to-end projects, and| [`examples/monicas-apartment`](../examples/monicas-apartment) | A single, self-contained HTML file that rebuilds the iconic Monica Geller apartment set from Friends as a walkable first-person 3D scene: purple walls, the purple front door with the yellow peephole frame, teal kitchen cabinets, the mismatched dining chairs, | `npm run dev, then open /examples/monicas-apartment/index.html` || [`examples/paid-mcp-server`](../examples/paid-mcp-server) | A complete, runnable MCP server whose tools charge per call in USDC on Solana over x402. It ships two tools on purpose: | `cd examples/paid-mcp-server && npm install && npm run start` || [`examples/pump-fun-agent`](../examples/pump-fun-agent) | An example agent manifest that composes all four production pump.fun skills into one 3D trading agent: swap, coin creation, creator-fee collection, and token payments. | Reference files, nothing to execute |+| [`examples/google-adk`](../examples/google-adk) | A Google Agent Development Kit agent that calls the free three.ws MCP server through MCPToolset. Zero three.ws credentials: the server is https://three.ws/api/mcp-studio, the free studio surface (no account, no key). | `node examples/google-adk/index.mjs` || [`examples/three-concierge`](../examples/three-concierge) | The reference agent for manifest spec agent-manifest/0.2. Trinity welcomes users to three.ws, explains the platform, and launches and trades $three on pump.fun through the real pump.fun skills in pump-fun-skills/. | Reference files, nothing to execute || [`examples/wallet-sign-in`](../examples/wallet-sign-in) | A single-page, no-build demo of the two wallet authentication rails three.ws runs itself: Sign-In with Solana (SIWS) and Sign-In with Ethereum (SIWE). | `npm run dev, then open /examples/wallet-sign-in/index.html` |@@ -77951,7 +78177,7 @@ Run any command from the repo root after `npm install`. The web component demos----<a id="sec-296"></a>+<a id="sec-299"></a>> **Source:** `docs/exit-lab.md` · [↑ table of contents](#table-of-contents)@@ -77973,7 +78199,7 @@ recorded number from a position that cost real money.## Why this is not the backtesterthree.ws already ships a backtester ([`api/_lib/strategy-backtest.js`](../api/_lib/strategy-backtest.js),-documented in [trading-experiment.md](#sec-692)). The two answer+documented in [trading-experiment.md](#sec-700)). The two answerdifferent questions and neither replaces the other.| | Backtester (`/api/sniper/backtest`) | Exit Lab (`/exit-lab`) |@@ -78203,14 +78429,14 @@ one that explains itself.## Related- [Agent Sniper](#sec-065), the worker whose positions this replays-- [Autonomous Trading hub](#sec-693), the front door to every trading surface-- [Trading experiment](#sec-692), the policy this fleet runs and why-- [Read the trading fleet](#sec-748), how to interpret fleet vitals-- Tutorial: [Find a better exit policy](#sec-726)+- [Autonomous Trading hub](#sec-701), the front door to every trading surface+- [Trading experiment](#sec-700), the policy this fleet runs and why+- [Read the trading fleet](#sec-756), how to interpret fleet vitals+- Tutorial: [Find a better exit policy](#sec-734)----<a id="sec-297"></a>+<a id="sec-300"></a>> **Source:** `docs/experiments-agent-launch-funnel.md` · [↑ table of contents](#table-of-contents)@@ -78222,7 +78448,7 @@ Published 2026-09-30. Status: concluded. Spend: $0. Index of every experiment: [three.ws lets anyone create an AI agent and then launch a coin for it. A launched coin is where an agent starts to earn creator fees and where most of the platform's on-chain activity begins. So the question that decides whether the product works is not "how many agents are created" but: **of the agents people create, how many go on to launch a coin, and where does everyone else stop?**-A research pass on 2026-09-28 ([launchpad landscape](#sec-604)) reported 788 agents and 3 launches in 30 days. This write-up re-measures that funnel over a fixed, re-runnable window and adds the stages around it.+A research pass on 2026-09-28 ([launchpad landscape](#sec-611)) reported 788 agents and 3 launches in 30 days. This write-up re-measures that funnel over a fixed, re-runnable window and adds the stages around it.## Method@@ -78279,7 +78505,7 @@ The re-measure differs slightly from the landscape doc (454 creators here, 452 tChanged already:- **The funnel is now tracked daily in public.** [/analytics](https://three.ws/analytics) charts agents created, agents with a wallet and coins launched side by side over 30 days, 90 days or all time, with the method for each, so this ratio is watched instead of rediscovered.-- **A launch no longer has to start from a blank form.** `npx three-ws launch` hands a prefilled coin to `/launch` for the owner to sign ([CLI docs](#sec-191)). It was built on 2026-09-29 and reaches creators once the `three-ws` package is published to npm, which is still pending.+- **A launch no longer has to start from a blank form.** `npx three-ws launch` hands a prefilled coin to `/launch` for the owner to sign ([CLI docs](#sec-192)). It was built on 2026-09-29 and reaches creators once the `three-ws` package is published to npm, which is still pending.- **Creators can see what a launched coin earns.** Per-agent creator earnings are now public on the agent profile and coin page, so the reason to launch is visible before launching.Will change next, and re-measure with these same queries once it ships:@@ -78365,7 +78591,7 @@ Derived figures: 2 / 788 = 0.25%; 208 / 788 = 26.4%; (788 - 509) / 509 = 55%.----<a id="sec-298"></a>+<a id="sec-301"></a>> **Source:** `docs/experiments-autonomous-trading.md` · [↑ table of contents](#table-of-contents)@@ -78373,7 +78599,7 @@ Derived figures: 2 / 788 = 0.25%; 208 / 788 = 26.4%; (788 - 509) / 509 = 55%.Published 2026-09-30. Status: running. Spend so far: $63.87 (0.5402 SOL of realized losses). Live scoreboard: [/sniper/experiments](https://three.ws/sniper/experiments). Index of every experiment: [/experiments](https://three.ws/experiments).-This is the standard write-up for the trading experiment. The full rule set, the exit math and how to run it live in [the experiment spec](#sec-692); the long-form account of the first 90 trades, with charts, is the [blog post](https://three.ws/blog/autonomous-trading-experiment). This page adds the sections those two do not carry: the spend, the whole-history result measured on one date, and what it changed.+This is the standard write-up for the trading experiment. The full rule set, the exit math and how to run it live in [the experiment spec](#sec-700); the long-form account of the first 90 trades, with charts, is the [blog post](https://three.ws/blog/autonomous-trading-experiment). This page adds the sections those two do not carry: the spend, the whole-history result measured on one date, and what it changed.## The question@@ -78446,7 +78672,7 @@ What the numbers say: the fleet as a whole loses money. The only exits that make## What we got wrong-- **The retune made the numbers worse, not better.** The 2026-08-09 retune (section "The 2026-08-09 retune" of [the spec](#sec-692)) rewrote the strategy table around what the first trades said. Measured by trade open date, the win rate after it fell from 33.2% to 12.5%, and the loss per SOL deployed grew from 1.13% to 12.37%. The fleet also traded far more after it (241 closed trades before, 1,055 after). Either way, it did not do what it was for.+- **The retune made the numbers worse, not better.** The 2026-08-09 retune (section "The 2026-08-09 retune" of [the spec](#sec-700)) rewrote the strategy table around what the first trades said. Measured by trade open date, the win rate after it fell from 33.2% to 12.5%, and the loss per SOL deployed grew from 1.13% to 12.37%. The fleet also traded far more after it (241 closed trades before, 1,055 after). Either way, it did not do what it was for.- **Stops do not cap the downside.** Stop-loss exits alone lost 0.6752 SOL, more than the whole fleet's net loss. The spec already records why: on a thin bonding curve a coin can gap straight through a stop before it fires.- **The trailing stop, meant to lock in gains, lost money in aggregate** (297 trades, -0.2304 SOL). We have not yet compared each trade's peak value with its exit value, which is the measurement that would say why.- **We measured win rate first.** Early reporting led with win rate. It is the wrong headline: the rule arms won 16.1%, and the only exit groups that made money are the 67 take-profits (+0.5512 SOL) and the 63 ladder recoveries (+0.5298 SOL), which can overlap. The blog post makes the same case in its section "Win rate is a vanity metric".@@ -78454,7 +78680,7 @@ What the numbers say: the fleet as a whole loses money. The only exits that make## What we changed because of it-Changed already, each documented in [the spec](#sec-692):+Changed already, each documented in [the spec](#sec-700):- **The take-initials ladder is enforced on every enabled arm**, because it is the one exit pattern that made money, and the fleet never sells the whole of a winning position.- **A liquidity-decay exit** closes an underwater position whose price has frozen, instead of letting it sit until the timeout. It now ends more trades than any other exit (468).@@ -78582,7 +78808,7 @@ Derived figures: 1 SOL = 1,000,000,000 lamports. 212 / 1,296 = 16.4%; -0.5402 /----<a id="sec-299"></a>+<a id="sec-302"></a>> **Source:** `docs/experiments.md` · [↑ table of contents](#table-of-contents)@@ -78596,8 +78822,8 @@ Each card is one experiment: the question it asked, its status, what it cost inCurrent write-ups:-- [How many new agents ever launch a coin?](#sec-297)-- [Can autonomous agents trade new coins at a profit?](#sec-298)+- [How many new agents ever launch a coin?](#sec-300)+- [Can autonomous agents trade new coins at a profit?](#sec-301)## Adding an experiment@@ -78638,7 +78864,7 @@ The validator lives in [scripts/lib/experiments-index.mjs](https://github.com/ni----<a id="sec-300"></a>+<a id="sec-303"></a>> **Source:** `docs/fact-check.md` · [↑ table of contents](#table-of-contents)@@ -78677,7 +78903,7 @@ The fact-check pipeline (`runFactCheck`):The LLM routes through the platform's shared free-first policy (Groq and OpenRouter as funded defaults). Results are cached in Redis for 7 days keyed by a hash of the claim, strictness, and any image URL, so an identical claim (on either lane) never re-runs the live chain.-**The attestation** is a tamper-evident content digest: `sha256:` followed by the SHA-256 of a JSON object of `{ verdict, confidence, claim, source URLs }`. It is returned as a string field you can recompute to confirm the verdict was not altered. Note that this is a content hash, not an on-chain record; it is distinct from the platform's [SAS credentialed attestations](#sec-624) and [3D provenance anchoring](#sec-556), which do write to Solana.+**The attestation** is a tamper-evident content digest: `sha256:` followed by the SHA-256 of a JSON object of `{ verdict, confidence, claim, source URLs }`. It is returned as a string field you can recompute to confirm the verdict was not altered. Note that this is a content hash, not an on-chain record; it is distinct from the platform's [SAS credentialed attestations](#sec-631) and [3D provenance anchoring](#sec-563), which do write to Solana.**The benchmark** (`GET /api/fact-check-benchmark`) scores a 40-claim fixture (10 per verdict class, deliberately time-stable and non-partisan) against the real chain. The API never fabricates a score: with no run available, `ran` is false and `report` is null, and the page renders a designed "not yet run" empty state. Both the claim set and the scoring runner are linked from the page for inspection. See [Running the benchmark](#running-the-benchmark) for how a run is produced and published.@@ -78722,7 +78948,7 @@ Read the published benchmark:curl 'https://three.ws/api/fact-check-benchmark'```-Once the free quota is spent, the same POST returns `402` with an x402 challenge; pay it with any x402 client (for example `@three-ws/x402-fetch`) and retry. See [x402](#sec-862).+Once the free quota is spent, the same POST returns `402` with an x402 challenge; pay it with any x402 client (for example `@three-ws/x402-fetch`) and retry. See [x402](#sec-877).## Running the benchmark@@ -78786,20 +79012,20 @@ Two guards keep a bad run from becoming a published number:## Related-- [x402: paid agent skills](#sec-862): the payment rail the $0.10 lane rides-- [API reference: Fact Check API](#sec-124): the endpoint's full request and response reference-- [SAS credentialed attestations](#sec-624) and [3D provenance](#sec-556): the platform's on-chain attestation primitives (distinct from this content-hash attestation)+- [x402: paid agent skills](#sec-877): the payment rail the $0.10 lane rides+- [API reference: Fact Check API](#sec-125): the endpoint's full request and response reference+- [SAS credentialed attestations](#sec-631) and [3D provenance](#sec-563): the platform's on-chain attestation primitives (distinct from this content-hash attestation)- Pages: [/fact-check](https://three.ws/fact-check) · [/x402](https://three.ws/x402)----<a id="sec-301"></a>+<a id="sec-304"></a>> **Source:** `docs/fade-radar.md` · [↑ table of contents](#table-of-contents)# Fade Radar: the wallets that are never right-Fade Radar is the inverse of the [Smart Money Radar](#sec-652). Smart Money asks who reputable is buying a coin. Fade Radar asks how much of a coin's buy side has never once been right, and answers with a 0 to 100 fade score, a verdict, and the measured odds behind that verdict.+Fade Radar is the inverse of the [Smart Money Radar](#sec-660). Smart Money asks who reputable is buying a coin. Fade Radar asks how much of a coin's buy side has never once been right, and answers with a 0 to 100 fade score, a verdict, and the measured odds behind that verdict.Page: [/fade](https://three.ws/fade)@@ -78919,9 +79145,9 @@ The module is a pure read layer with no side effects, and `fadeScore` / `fadeVer## Where it fits-- [Smart Money Radar](#sec-652): the same graph read from the winning side. A wallet on the fade board links straight to its full track record there.-- [Coin Intelligence](#sec-695): the engine that records every launch, labels its outcome, and produces the ground truth both radars stand on.-- [Coin Radar](#sec-594): what launched in the last 90 seconds, where a fade read is the fastest reason to skip one.+- [Smart Money Radar](#sec-660): the same graph read from the winning side. A wallet on the fade board links straight to its full track record there.+- [Coin Intelligence](#sec-703): the engine that records every launch, labels its outcome, and produces the ground truth both radars stand on.+- [Coin Radar](#sec-601): what launched in the last 90 seconds, where a fade read is the fastest reason to skip one.## Files@@ -78934,7 +79160,7 @@ The module is a pure read layer with no side effects, and `fadeScore` / `fadeVer----<a id="sec-302"></a>+<a id="sec-305"></a>> **Source:** `docs/farcaster-memory-seeding.md` · [↑ table of contents](#table-of-contents)@@ -78953,7 +79179,7 @@ own verification records.- **Surface**: the Farcaster panel in the agent persona editor at [/dashboard/agents](https://three.ws/dashboard/agents)- **API**: `/api/agents/:id/memory/seed/farcaster`-- **Related**: [Memory system](#sec-420), [`@three-ws/agent-memory`](https://www.npmjs.com/package/@three-ws/agent-memory)+- **Related**: [Memory system](#sec-424), [`@three-ws/agent-memory`](https://www.npmjs.com/package/@three-ws/agent-memory)---@@ -79190,7 +79416,7 @@ only its own rows and a revoke deletes exactly what was granted.----<a id="sec-303"></a>+<a id="sec-306"></a>> **Source:** `docs/fee-bridge.md` · [↑ table of contents](#table-of-contents)@@ -79321,12 +79547,12 @@ The response lists each due coin's distributable fees, whether a conversion woul## Related-- [Launchpad](#sec-397): launching a pump.fun coin on three.ws+- [Launchpad](#sec-401): launching a pump.fun coin on three.ws- [STRUCTURE.md](../STRUCTURE.md): where every surface lives----<a id="sec-304"></a>+<a id="sec-307"></a>> **Source:** `docs/feedback.md` · [↑ table of contents](#table-of-contents)@@ -79375,7 +79601,7 @@ the top of [`api/_lib/feedback/triage.js`](../api/_lib/feedback/triage.js).## How a report travels1. **Capture.** [`src/feedback-companion.js`](../src/feedback-companion.js)- starts [`@three-ws/witness`](#sec-803) at module load, before the+ starts [`@three-ws/witness`](#sec-815) at module load, before thecompanion finishes mounting. It keeps a bounded semantic trace: the sequenceof intents plus the failures, with a stable selector for every elementtouched and no typed value ever held. No timers, no network, nothing sent@@ -79415,7 +79641,7 @@ npm run feedback:repro -- <id> --run # compile it and watch it failThe reconstruction step, which is where most bug reports die, is done before amaintainer opens the queue. Full detail, including the selector ladder and the-privacy rules: [Witness](#sec-803).+privacy rules: [Witness](#sec-815).Nothing about this changes the boundary above. The trace is machine-written datavalidated by shape at the API edge, the compiler is a pure function with no@@ -79473,7 +79699,7 @@ curl -X POST https://three.ws/api/feedback/report \{ "ok": true, "id": "8c2f...", "received_at": "2026-08-28T14:02:11.884Z", "replayable": true }```-`trace` is optional and machine-written by [`@three-ws/witness`](#sec-803).+`trace` is optional and machine-written by [`@three-ws/witness`](#sec-815).It is validated by shape at this boundary (known event types only, 80 events,every string capped), because the endpoint is open to anyone. `replayable` sayswhether a usable trace survived that validation.@@ -79499,7 +79725,7 @@ Pass `id` instead of `cluster` to move a single report.The report as a runnable Playwright spec. `&format=json` returns the sourcealongside the narrated steps and the replay confidence; `&base=<origin>` points-the replay somewhere other than production. See [Witness](#sec-803).+the replay somewhere other than production. See [Witness](#sec-815).## What this deliberately does not do@@ -79518,12 +79744,12 @@ reproduces the failure, never the raw report, and the output is a pull request.## Related-- [Notifications](#sec-442): the same companion delivering messages the other way.+- [Notifications](#sec-446): the same companion delivering messages the other way.- [`STRUCTURE.md`](../STRUCTURE.md): where every surface lives.----<a id="sec-305"></a>+<a id="sec-308"></a>> **Source:** `docs/field.md` · [↑ table of contents](#table-of-contents)@@ -79537,8 +79763,8 @@ district they belong to. Nothing on the map is decorative: every number, faceand trail comes from a real endpoint, and when a feed is down its district saysso and offers a retry.-The homepage `/` is the web desktop (see [desktop.md](#sec-241) and-[desktop-widgets.md](#sec-240)); its 3D campus is at `/?world=1` and+The homepage `/` is the web desktop (see [desktop.md](#sec-242) and+[desktop-widgets.md](#sec-241)); its 3D campus is at `/?world=1` andthe previous homepage stays at `/classic`.## Moving around@@ -79620,7 +79846,7 @@ when the URL carries `?view=field`).----<a id="sec-306"></a>+<a id="sec-309"></a>> **Source:** `docs/financial-controls.md` · [↑ table of contents](#table-of-contents)@@ -79633,7 +79859,7 @@ on-chain transaction is captured, whether it is reconciled against the chain, anhow long it is retained** — plus the monitoring/breach controls around it and theopen gaps ranked by accounting/regulatory risk.-It is a companion to the [money map](#sec-435) (who receives what) and the+It is a companion to the [money map](#sec-439) (who receives what) and the[Solana signers runbook](../api/_lib/solana-signers.js) (thewallets). Keep it in sync with the code — every row cites its source.@@ -79869,7 +80095,7 @@ Ranked by accounting/regulatory risk. Each is a tracked remediation item.runtime halt flag).14. **The 1% trade and launch fee has no revenue ledger.** Every customer tradethree.ws builds or signs pays it on-chain (see- [pump platform fee](#sec-562)), but the only durable record is the+ [pump platform fee](#sec-569)), but the only durable record is thecustody event of a server-signed trade; fees paid inside a user-signedtransaction are countable only by scanning the fee wallet. *Fix: an append-only`platform_fee_events` row per charged transaction, keyed `UNIQUE` on the@@ -79918,19 +80144,19 @@ Ranked by accounting/regulatory risk. Each is a tracked remediation item.re-run `check-relayer-balances.mjs` to confirm balances.- **Before adding a paid flow:** it is not done until it writes an append-onlyledger row with the on-chain signature and a `UNIQUE` idempotency key, and is- added to this register and the [money map](#sec-435).+ added to this register and the [money map](#sec-439).---## Related-- [Money map](#sec-435) — who receives each payment.-- [x402 endpoints](#sec-854) — the paid endpoint catalog.+- [Money map](#sec-439) — who receives each payment.+- [x402 endpoints](#sec-869) — the paid endpoint catalog.- [Solana signers runbook](../api/_lib/solana-signers.js) — the wallets + funding.----<a id="sec-307"></a>+<a id="sec-310"></a>> **Source:** `docs/first-contribution.md` · [↑ table of contents](#table-of-contents)@@ -80033,7 +80259,7 @@ Three things to copy from it, beyond the mapping itself:- **The comment says what was left out and why.** The IK and twist bones are the interesting decision here, and the next reader needs the reasoning, not just the table.- **Fingers are not optional.** 30 of the 53 tracks in every clip address a finger joint, so a rig whose hands do not map scores around 40% coverage and gets no animation at all.-- **Rig Doctor learned the name too.** A matching fingerprint went into `CONVENTIONS` in [`src/rig-report.js`](../src/rig-report.js), so an MMD upload is identified on sight instead of reported as unrecognised, and a row went into the table in [`docs/rig-doctor.md`](#sec-617).+- **Rig Doctor learned the name too.** A matching fingerprint went into `CONVENTIONS` in [`src/rig-report.js`](../src/rig-report.js), so an MMD upload is identified on sight instead of reported as unrecognised, and a row went into the table in [`docs/rig-doctor.md`](#sec-624).The tests that shipped with it, in [`tests/glb-canonicalize.test.js`](../tests/glb-canonicalize.test.js), use the file's `describe` + `it.each` table style. Match it:@@ -80113,7 +80339,7 @@ Then open the PR on GitHub. In the description say what changed, what you tested## 5. What happens next-See [Triage](#sec-698) for the full flow and response targets. In short: a maintainer reads it, you get real review comments, and merged work shows up in the [public changelog](https://three.ws/changelog).+See [Triage](#sec-706) for the full flow and response targets. In short: a maintainer reads it, you get real review comments, and merged work shows up in the [public changelog](https://three.ws/changelog).---@@ -80126,7 +80352,7 @@ See [Triage](#sec-698) for the full flow and response targets. In short: a maint----<a id="sec-308"></a>+<a id="sec-311"></a>> **Source:** `docs/forge-background-generation.md` · [↑ table of contents](#table-of-contents)@@ -80211,7 +80437,7 @@ Three cooperating pieces:`notifyForgeFailed` instead, because this is the only place that can tell aterminal failure from a failover that is still running: `markFailed` also runson the redispatch path, and telling a subscriber the job died while it is- still running would be a lie. See [api-reference.md](#sec-124).+ still running would be a lie. See [api-reference.md](#sec-125).## Self-host poll recovery (the "task not found" grace)@@ -80291,7 +80517,7 @@ and the notification preference model in----<a id="sec-309"></a>+<a id="sec-312"></a>> **Source:** `docs/forge-desktop.md` · [↑ table of contents](#table-of-contents)@@ -80427,15 +80653,15 @@ python apps/forge-desktop/tools/forge-cli/agent.py generate --image ./input.png## Related- [/forge-desktop](https://three.ws/forge-desktop): the download page.-- [Modly and three.ws](#sec-432): every way three.ws and Modly work together,+- [Modly and three.ws](#sec-436): every way three.ws and Modly work together,including the three.ws nodes for an unmodified Modly.-- [Forge](#sec-313): generating 3D in the browser on three.ws servers.-- [Workbench](#sec-804): the same kind of node workflow in a browser tab.+- [Forge](#sec-316): generating 3D in the browser on three.ws servers.+- [Workbench](#sec-817): the same kind of node workflow in a browser tab.- Maintainers cut releases with the runbook at `docs/ops/forge-desktop-release.md` in the repository (operator docs are not published on the site).----<a id="sec-310"></a>+<a id="sec-313"></a>> **Source:** `docs/forge-off.md` · [↑ table of contents](#table-of-contents)@@ -80562,7 +80788,7 @@ Backfill a past week's winner (owner): `GET /api/cron/forge-off-crown?week=YYYY-----<a id="sec-311"></a>+<a id="sec-314"></a>> **Source:** `docs/forge-pipeline.md` · [↑ table of contents](#table-of-contents)@@ -80570,7 +80796,7 @@ Backfill a past week's winner (owner): `GET /api/cron/forge-off-crown?week=YYYY-This is the engineering guide to the Forge, the text/image/sketch to 3D generation system behind [/forge](https://three.ws/forge), the free MCP tools, and every agent-facing 3D endpoint. It maps the whole path a generation takes: entry points, the engine grid, free-first routing, the job lifecycle, failover, persistence, GPU workers, post-processing, and payments.-If you want the product-level overview, read [Forge](#sec-313). If you want the plain-language version, read [How the Forge works](#sec-350). This document is for people changing the pipeline.+If you want the product-level overview, read [Forge](#sec-316). If you want the plain-language version, read [How the Forge works](#sec-354). This document is for people changing the pipeline.## Bird's-eye view@@ -80722,7 +80948,7 @@ Async jobs get an opaque HMAC-signed token (`f1.<payload>.<sig>`, `api/_lib/forg`GET /api/forge?job=<id>` returns `status`: `queued`, `running`, `done` (with `glb_url`, `viewer_url`, and the `path`/`tier`/`backend` that actually produced it), or `failed`. Polling is free and unauthenticated.-Every non-terminal poll also carries honest timing: `elapsed_seconds` (the age of the *job*, from `created_at`, not of the tab watching it), `eta_seconds` (the lane's typical total) and `eta_remaining_seconds`. The remaining figure is floored at 5, because the estimate is a typical duration rather than a deadline and a countdown that goes negative reads as "stuck" on a job that is merely slower than average. A `queued` poll on a scale-to-zero self-host lane additionally carries `cold_start` and `cold_start_seconds` (that lane's spin-up budget). `laneColdStart()` is module-scope for exactly this reason: it used to be a closure inside the submit handler, so only the submit response could say a worker was booting, and a client that never saw it (a coalesced job, a page resumed after a reload, a failover successor) was told "queued" with no explanation for a wait that is a container boot rather than a stall. `forgeStageNarration()` and `coldStartState()` in [src/shared/forge-frames.js](../src/shared/forge-frames.js) turn those fields into the same copy on every surface, off the payload and never off a local clock, and the flag clears on the first real `running` poll rather than on a timer. The in-flight job id is also written to `localStorage`, so an interrupted browser session resumes polling for up to 30 minutes; background completion persists the result to the user's gallery either way (see [Background generation](#sec-308)).+Every non-terminal poll also carries honest timing: `elapsed_seconds` (the age of the *job*, from `created_at`, not of the tab watching it), `eta_seconds` (the lane's typical total) and `eta_remaining_seconds`. The remaining figure is floored at 5, because the estimate is a typical duration rather than a deadline and a countdown that goes negative reads as "stuck" on a job that is merely slower than average. A `queued` poll on a scale-to-zero self-host lane additionally carries `cold_start` and `cold_start_seconds` (that lane's spin-up budget). `laneColdStart()` is module-scope for exactly this reason: it used to be a closure inside the submit handler, so only the submit response could say a worker was booting, and a client that never saw it (a coalesced job, a page resumed after a reload, a failover successor) was told "queued" with no explanation for a wait that is a container boot rather than a stall. `forgeStageNarration()` and `coldStartState()` in [src/shared/forge-frames.js](../src/shared/forge-frames.js) turn those fields into the same copy on every surface, off the payload and never off a local clock, and the flag clears on the first real `running` poll rather than on a timer. The in-flight job id is also written to `localStorage`, so an interrupted browser session resumes polling for up to 30 minutes; background completion persists the result to the user's gallery either way (see [Background generation](#sec-311)).**Territory enforcement** (`api/_lib/forge-territory.js`). The Hunyuan3D license excludes the European Union, the United Kingdom and South Korea for the model and its output. The Forge resolves the requester's country on the server from the edge geo header (`clientCountry`), never from the request body, and never routes a restricted request to a Tencent-model lane. Those lanes are `hunyuan3d`, `huggingface` (the Spaces chain runs Hunyuan3D-2 and 2.1) and `modly_hunyuan` (Hunyuan3D 2 Mini Turbo, under the Hunyuan3D 2.0 licence with the same exclusion). An unknown or malformed country is treated as restricted, so a request with no geo signal fails closed to the MIT and non-Tencent lanes. The filter sits in every place a lane is chosen: auto routing and its health-aware variant, the HuggingFace failure hop, poll-time redispatch, the `retry_backends` suggestions, and the prompt-to-avatar plan. An explicit `backend=hunyuan3d`, `backend=huggingface` or `backend=modly_hunyuan` from a restricted country answers `403 region_restricted` and lists the open lanes in `retry_backends`. The public catalog is CDN-cached and country-agnostic, so it advertises the fail-closed defaults.@@ -80798,7 +81024,7 @@ Meshes that predate the variant are drained by [api/cron/forge-web-variants.js](Send `"lods": true` on the generation request (`api/_lib/forge-options.js`) and `materializeCreation` builds a third object alongside `glb_url` and `web_glb_url`: a single combined GLB tagged with the archived `MSFT_lod` extension, carrying LOD0 (the delivered mesh, untouched), LOD1 and LOD2 (decimated with `meshoptimizer`'s simplifier through `packages/glb-tools`' `buildLodChain`). A real-time engine that understands `MSFT_lod` switches levels from this one file at runtime; one that does not simply renders LOD0, because the lower-detail levels are merged in as orphan nodes outside the scene's child graph.-It is off by default for the same reason the delivery variant is not: building three decimated meshes costs real CPU (meshoptimizer's simplifier, run three times), and most callers never render in an engine that benefits from a LOD chain. The same real pipeline backs the Engine QA panel's own "Build & grade LOD chain" / "Check LOD & collider fitness" upgrade action (`public/engine-qa-panel.js`, `GET/POST /api/3d/engine-qa?lods=1`, see [engine-qa.md](#sec-262)), so a caller who only wants to grade fitness, not keep the chain, can do that on demand without ever setting `lods` on the generation itself.+It is off by default for the same reason the delivery variant is not: building three decimated meshes costs real CPU (meshoptimizer's simplifier, run three times), and most callers never render in an engine that benefits from a LOD chain. The same real pipeline backs the Engine QA panel's own "Build & grade LOD chain" / "Check LOD & collider fitness" upgrade action (`public/engine-qa-panel.js`, `GET/POST /api/3d/engine-qa?lods=1`, see [engine-qa.md](#sec-265)), so a caller who only wants to grade fitness, not keep the chain, can do that on demand without ever setting `lods` on the generation itself.Two rules, mirroring the delivery variant:@@ -80886,17 +81112,17 @@ Whether the output is any good to the people asking for it is a separate questio## Related-- [Forge](#sec-313), the product-level doc for the /forge surface.-- [How the Forge works](#sec-350), the plain-language explainer.+- [Forge](#sec-316), the product-level doc for the /forge surface.+- [How the Forge works](#sec-354), the plain-language explainer.- [3D pipeline](#sec-003), the pay-per-stage x402 pipeline (rig, remesh, gameready, stylize, rembg).- [3D asset pipeline](#sec-002), formats and the animation/conversion flow.-- [Avatar pipeline](#sec-148), the selfie-to-avatar reconstruction flow.-- [Background generation](#sec-308), job resume and gallery persistence.+- [Avatar pipeline](#sec-149), the selfie-to-avatar reconstruction flow.+- [Background generation](#sec-311), job resume and gallery persistence.- `workers/README.md`, the worker-by-worker operational reference.----<a id="sec-312"></a>+<a id="sec-315"></a>> **Source:** `docs/forge-workflows.md` · [↑ table of contents](#table-of-contents)@@ -80908,9 +81134,9 @@ Page: [/forge/workflows](https://three.ws/forge/workflows)## Why it exists-[Forge](#sec-313) is one box: type or drop something in, get a model out. Creators who make game props, rigged characters or printable parts repeat the same three or four steps after that, by hand, every time. Forge Workflows turns those steps into a graph you build once, save as a file, share, and run again on a new prompt or a batch of photos. A failed step does not throw away the rest: re-run from the node that failed and every finished step before it is reused.+[Forge](#sec-316) is one box: type or drop something in, get a model out. Creators who make game props, rigged characters or printable parts repeat the same three or four steps after that, by hand, every time. Forge Workflows turns those steps into a graph you build once, save as a file, share, and run again on a new prompt or a batch of photos. A failed step does not throw away the rest: re-run from the node that failed and every finished step before it is reused.-[Workbench](#sec-804) covers a related need with a fixed photo pipeline and a large viewport for in-browser mesh edits. Forge Workflows is the free-form graph: any order, branches, batches, and several outputs from one run.+[Workbench](#sec-817) covers a related need with a fixed photo pipeline and a large viewport for in-browser mesh edits. Forge Workflows is the free-form graph: any order, branches, batches, and several outputs from one run.## Quick start@@ -80956,7 +81182,7 @@ Processing workers download the model themselves, so a model that only exists in### Your GPU (Modly)-[Modly](#sec-432) is a free desktop app that runs open image-to-3D models on your own graphics card. Pick **Your GPU (Modly)** as the Generate 3D engine and press **Connect Modly** in the inspector. The page only contacts `localhost` after that click, so the browser's local network permission prompt appears when you expect it, never on page load. The inspector then lists the models installed in Modly. A Modly step costs nothing and never leaves your computer until a later step needs the model on a server.+[Modly](#sec-436) is a free desktop app that runs open image-to-3D models on your own graphics card. Pick **Your GPU (Modly)** as the Generate 3D engine and press **Connect Modly** in the inspector. The page only contacts `localhost` after that click, so the browser's local network permission prompt appears when you expect it, never on page load. The inspector then lists the models installed in Modly. A Modly step costs nothing and never leaves your computer until a later step needs the model on a server.## Running@@ -81066,11 +81292,11 @@ The For Each loop semantics, the typed-port model and the idea of a local-GPU ge| `src/forge-workflows/templates.js` | The four templates. || `tests/forge-workflows-graph.test.js`, `tests/forge-workflows-runner.test.js` | Unit tests for the graph and the runner. |-Related: [Forge](#sec-313), [Workbench](#sec-804), [Modly](#sec-432), [How Forge works](#sec-350).+Related: [Forge](#sec-316), [Workbench](#sec-817), [Modly](#sec-436), [How Forge works](#sec-354).----<a id="sec-313"></a>+<a id="sec-316"></a>> **Source:** `docs/forge.md` · [↑ table of contents](#table-of-contents)@@ -81144,7 +81370,7 @@ gone. `npm run forge:tripo` reports the house lane's own health, completion ratelatency by day, scoped to `backend = 'tripo'`, separately from `npm run forge:funnel`'sall-backend numbers.-See [the Tripo partner note](#sec-486) for the partnership context and what is+See [the Tripo partner note](#sec-493) for the partnership context and what isand is not wired yet (low-poly/quad game-ready preset and Smart Segmentation are built onself-hosted GCP workers instead; no live Tripo splat endpoint exists to wire).@@ -81391,7 +81617,7 @@ received against the whole-model bytes it returned withanimation clip changed. A successful regenerate is also minted as a newdurable version in the real lineage automatically (no separate "Saveversion" click needed), and the lineage strip's "Diff" link opens-[Model Diff](#sec-431) pre-loaded with exactly that before/after+[Model Diff](#sec-435) pre-loaded with exactly that before/afterpair.## Mesh tools: repair, smooth, decimate@@ -81450,6 +81676,27 @@ from the format menu and import it into the slicer by hand.curl -sLo model.stl https://three.ws/api/slicer/<id>/120mm/model.stl```+## Get it printed: live prices from Craftcloud++The format menu's **🖨 Get it printed** row, and the **Get it printed** action+on a model page, are a different flow from Materialize (three.ws's own print+pipeline, documented in [materialize.md](#sec-413)). Here, the model is+uploaded straight to [Craftcloud](https://craftcloud3d.com) (All3DP), priced+live across whichever of its roughly 186 print shops can run the job, and the+buyer pays Craftcloud directly on Craftcloud's own site. three.ws never takes+payment or touches the order.++`POST /api/print/craftcloud-quote` with `{ "creationId": "<uuid>" }` or+`{ "glbUrl": "<url>" }` converts the model to STL, uploads it to Craftcloud,+polls its pricing engine, and returns every (shop, material) quote it got+back, cheapest first, with shipping attached. Craftcloud's public v5 API has+no endpoint that hands a server-created cart back to a browser for checkout,+so the response carries `checkoutUrl: null` and an `uploadPageUrl` instead:+the honest next step is Craftcloud's own upload page, where pasting the same+file reproduces these prices in an authenticated session that can actually+check out. The adapter behind this lives at+`api/_lib/print/adapters/craftcloud.js`.+## ExamplesForge's read and generate surface is plain HTTP. No key is required for the free lanes.@@ -81658,16 +81905,16 @@ dashboard at [/quality-bench](https://three.ws/quality-bench) (internal).## Related-- [The Forge pipeline](#sec-311) is the architecture deep dive: the engine grid, routing, failover, job lifecycle, workers, and payments, end to end. [How the Forge works](#sec-350) is the same story in plain language.-- [Image to 3D](#sec-379) is the photo lane opened directly at [/image-to-3d](https://three.ws/image-to-3d).+- [The Forge pipeline](#sec-314) is the architecture deep dive: the engine grid, routing, failover, job lifecycle, workers, and payments, end to end. [How the Forge works](#sec-354) is the same story in plain language.+- [Image to 3D](#sec-383) is the photo lane opened directly at [/image-to-3d](https://three.ws/image-to-3d).- [/forge-max](https://three.ws/forge-max) is the maximum-quality lane opened directly: the same Forge with the High tier pinned on arrival (200k-poly target, 4K PBR and HD textures, subject-aware engine routing). `?tier=draft|standard|high` presets the quality selector on any Forge URL the same way. The High tier's $THREE hold-or-pay gate applies unchanged; BYOK engines (your own Meshy, Tripo, or Rodin key) are exempt as always. For DamagedHelmet-class artist benchmarks, remember the ceiling is the current state of generative 3D, not the routing: this lane maxes every budget the engines expose, and [Measuring realism](#measuring-realism) is how we track that ceiling moving.-- [Diorama](#sec-247) forges a whole scene of Forge objects into one explorable world.+- [Diorama](#sec-248) forges a whole scene of Forge objects into one explorable world.- The 3D generation architecture: [3D pipeline](#sec-003), [3D asset pipeline](#sec-002), [3D API](#sec-001).- Pages: [/create](https://three.ws/create) (the avatar creator), [/scene](https://three.ws/scene) (Scene Studio), [/restyle](https://three.ws/restyle) (re-skin a GLB), [/gallery](https://three.ws/gallery).----<a id="sec-314"></a>+<a id="sec-317"></a>> **Source:** `docs/forged.md` · [↑ table of contents](#table-of-contents)@@ -81675,7 +81922,7 @@ dashboard at [/quality-bench](https://three.ws/quality-bench) (internal).[three.ws/forged](https://three.ws/forged) is a public gallery of 3D props thatthe platform's own autonomous agents bought with real USDC over the-[x402 payment protocol](#sec-862). Nothing on the page is curated or seeded by+[x402 payment protocol](#sec-877). Nothing on the page is curated or seeded byhand: an agent wallet paid the Forge, the Forge generated the prop, the paymentsettled on Solana mainnet, and the finished asset landed in the gallery carryingits receipt. Every card shows the price paid, the paying agent wallet, and a@@ -81708,7 +81955,7 @@ The page ([pages/forged.html](../pages/forged.html), rendered by## Where the assets come from-The buyer is the platform's [autonomous x402 loop](#sec-140), the+The buyer is the platform's [autonomous x402 loop](#sec-141), thescheduled engine that pays real USDC to call the platform's own paid endpoints.Its `forge` pipeline([api/_lib/x402/pipelines/forge-content.js](../api/_lib/x402/pipelines/forge-content.js))@@ -81726,7 +81973,7 @@ runs as a registry entry inside that loop, and on each run it:is a real on-chain USDC transfer from the loop's seeder wallet, settled bythe platform's self-hosted facilitator on Solana mainnet. The same seederwallet is the `x402-ring-payer` signer in the- [x402 ring economy](#sec-857), and the loop's daily spend cap+ [x402 ring economy](#sec-872), and the loop's daily spend capapplies to these calls like every other. The Forge generates the meshbefore it settles, and a standard NIM job finishes 20 to 55 seconds afterthe request, so this call waits up to 90 seconds (`FORGE_PAID_TIMEOUT_MS`,@@ -81803,21 +82050,21 @@ Try it:curl -s 'https://three.ws/api/forged?limit=5' | python3 -m json.tool```-The endpoint is also listed in the [API reference](#sec-124).+The endpoint is also listed in the [API reference](#sec-125).## Related-- [Autonomous x402 loop](#sec-140): the engine that buys these+- [Autonomous x402 loop](#sec-141): the engine that buys theseassets, its spend caps, and where every call is logged.-- [x402 ring economy](#sec-857): the wider self-paid endpoint+- [x402 ring economy](#sec-872): the wider self-paid endpointeconomy the seeder wallet participates in.-- [How the Forge works](#sec-350): the generation pipeline the+- [How the Forge works](#sec-354): the generation pipeline theagents are paying for.-- [x402 on three.ws](#sec-862): the payment protocol itself.+- [x402 on three.ws](#sec-877): the payment protocol itself.----<a id="sec-315"></a>+<a id="sec-318"></a>> **Source:** `docs/fork-trade.md` · [↑ table of contents](#table-of-contents)@@ -81838,10 +82085,10 @@ Module: `src/fork-trade.js` · Trade panel: `src/game/coin-buy.js`## Why it existsThe platform already answers "who is winning and what are they in": the-[Coin Radar](#sec-594) scores every launch in its first 90 seconds, the-[Smart Money Radar](#sec-652) shows which proven wallets are accumulating-right now, [Ghost-copy](#sec-323) replays a leader's real record against-your budget, and the [Live Trade Feed](#sec-695) opens the full+[Coin Radar](#sec-601) scores every launch in its first 90 seconds, the+[Smart Money Radar](#sec-660) shows which proven wallets are accumulating+right now, [Ghost-copy](#sec-326) replays a leader's real record against+your budget, and the [Live Trade Feed](#sec-703) opens the fulldeep-dive on any mint. Until Fork, every one of those answers ended in a linkout to pump.fun, where you had to find the coin again and start over.@@ -81954,23 +82201,23 @@ which the /play HUD does not need).## Related-- [Ghost-copy](#sec-323): find out what a leader would have done to your+- [Ghost-copy](#sec-326): find out what a leader would have done to yourbudget before you fork anything.-- [Copy trading](#sec-225): when one fork at a time is not enough and you+- [Copy trading](#sec-226): when one fork at a time is not enough and youwant a leader mirrored automatically under hard spend limits.-- [The trading surfaces](#sec-695): where every fork button lives.-- [Smart Money Radar](#sec-652): the proven-wallet ledger behind the coin+- [The trading surfaces](#sec-703): where every fork button lives.+- [Smart Money Radar](#sec-660): the proven-wallet ledger behind the coinpedigree the panel shows you before you sign.----<a id="sec-316"></a>+<a id="sec-319"></a>> **Source:** `docs/free-crypto-apis.md` · [↑ table of contents](#table-of-contents)# Free crypto APIs we have not integrated yet-Research catalog, 2026-08-05. Companion to [free-llm-providers.md](#sec-317).+Research catalog, 2026-08-05. Companion to [free-llm-providers.md](#sec-320).**Status update 2026-08-06: every keyless provider in this catalog is now integrated.** Shipped in eight workstreams: the seven CEX public-data venues (Binance, OKX, Bybit, KuCoin, Gate.io, MEXC, Bitget) as market/chart fallback rungs; RedStone and Switchboard as SOL price oracle rungs; RugCheck fused with GoPlus and Honeypot.is wired into EVM token risk; Deribit options/perp data beside Hyperliquid plus Jupiter's unused lite endpoints; a keyless EVM swap-quote chain (ParaSwap, KyberSwap, LI.FI) at `/api/v1/evm/swap-quote`; Coin Metrics fundamentals, Blockchair chain stats, and Blockstream Esplora Bitcoin reads; six subreddits in the news pipeline (JSON with Atom fallback, since Reddit 403s datacenter JSON traffic); and a gas oracle chain (Blocknative, Owlracle, Etherscan) at `/api/v1/gas`. Deliberately skipped: CoinMarketCap's keyless trial endpoints (evaluation-only under their terms). Everything still listed as needing a key below remains open.@@ -82119,7 +82366,7 @@ Adoption rules that still apply: these are all free tiers, so no owner approval----<a id="sec-317"></a>+<a id="sec-320"></a>> **Source:** `docs/free-llm-providers.md` · [↑ table of contents](#table-of-contents)@@ -82193,11 +82440,11 @@ All of these rungs are zero-marginal-cost, and the accounting knows it:6. If the provider should be user-selectable in chat: register it in `api/chat.js` (`PROVIDERS`, the provider enum, `FALLBACK_SIBLINGS`) and `api/_lib/chat-models.js` (`MODEL_CATALOG`, `PROVIDER_MODEL_DEFAULTS`, `DEFAULT_PROVIDER_ORDER`, `ANON_PROVIDER_LIST`).7. `.env.example` and the env tables in [`ARCHITECTURE.md`](../ARCHITECTURE.md).-Related: [nvidia-models.md](#sec-450) for the full NVIDIA NIM surface map.+Related: [nvidia-models.md](#sec-454) for the full NVIDIA NIM surface map.----<a id="sec-318"></a>+<a id="sec-321"></a>> **Source:** `docs/fundraising/nvidia-inception-capital-connect.md` · [↑ table of contents](#table-of-contents)@@ -82312,7 +82559,7 @@ Source: [`three-ws-inception-deck.html`](fundraising/three-ws-inception-deck.htm----<a id="sec-319"></a>+<a id="sec-322"></a>> **Source:** `docs/galaxy.md` · [↑ table of contents](#table-of-contents)@@ -82394,13 +82641,13 @@ curl -X POST 'https://three.ws/api/galaxy' \## Related-- [IBM Granite suite](#sec-378): the full set of watsonx-powered features on three.ws, including the Granite embeddings that position this galaxy.+- [IBM Granite suite](#sec-382): the full set of watsonx-powered features on three.ws, including the Granite embeddings that position this galaxy.- [Agent system](#sec-068) and [Agent reputation](#sec-060): what a "star" is and how agents earn standing.- Pages: [/galaxy](https://three.ws/galaxy), [/create](https://three.ws/create), [/agents](https://three.ws/agents).----<a id="sec-320"></a>+<a id="sec-323"></a>> **Source:** `docs/generation-watch.md` · [↑ table of contents](#table-of-contents)@@ -82421,7 +82668,7 @@ The page is a single self-contained file,Watch links are minted by the 3D Studio Actions surface, `POST /api/3d/studio`([api/3d/studio.js](../api/3d/studio.js)), the REST contract behind the-[three.ws 3D Studio custom GPT](#sec-185). Fast generations+[three.ws 3D Studio custom GPT](#sec-186). Fast generationsreturn `status: "done"` with the model URLs directly and never need a watchpage. When a job cannot finish inside the request window, the response is`status: "pending"` and carries three handles:@@ -82456,7 +82703,7 @@ The page polls `GET /api/3d/studio?job=<id>` and moves through five states:painted reference image, the first step of the text-to-3D pipeline), it fadesin with the caption "Concept art, now being sculpted into 3D". This is thesame paint-then-reconstruct flow described in- [How the Forge works](#sec-350).+ [How the Forge works](#sec-354).- **Ready.** When the poll returns `status: "done"`, the page shows "openingthe viewer" and redirects itself into the interactive viewer after a shortbeat, using the API's `viewerUrl` (or building a `/viewer?src=<glb>` link@@ -82502,23 +82749,23 @@ server-side: the platform tracks every generation to completion whether or notany tab is watching, finished models land in the creator's gallery, andunattended completions notify through the bell, push, and email channels. Thatmachinery is documented in-[Background generation and completion notifications](#sec-308).+[Background generation and completion notifications](#sec-311).Closing the watch tab mid-job therefore loses nothing; reopening the same`?job=` link resumes exactly where the generation actually is.## Related-- [How the Forge works](#sec-350): the pipeline behind the+- [How the Forge works](#sec-354): the pipeline behind thecountdown.-- [Background generation](#sec-308): server-side+- [Background generation](#sec-311): server-sidetracking, resume, and notifications.-- [The 3D Studio GPT](#sec-185): the main surface that hands+- [The 3D Studio GPT](#sec-186): the main surface that handsout watch links.-- [API reference](#sec-124): the full `/api/3d/studio` contract.+- [API reference](#sec-125): the full `/api/3d/studio` contract.----<a id="sec-321"></a>+<a id="sec-324"></a>> **Source:** `docs/genesis.md` · [↑ table of contents](#table-of-contents)@@ -82543,8 +82790,8 @@ Genesis collapses that into a single guided flow with a real progress bar drivenreal job state, so a first-time visitor goes from an idea to a wallet-holding,animation-ready agent they fully own in under a minute of active work. It is thefront door: the artifact it produces is a first-class agent that plugs straight-into [Agent Studio](#sec-066), the [economy](#sec-139),-[breeding](#sec-322), and every embed surface.+into [Agent Studio](#sec-066), the [economy](#sec-140),+[breeding](#sec-325), and every embed surface.## How it works@@ -82574,7 +82821,7 @@ never invents a shortcut path; it orchestrates the real ones.Genesis resolves it via `GET /api/agents?avatar_id=...`, then calls`POST /api/agents/:id/wallet/provision` to guarantee both a custodial Solanaaddress and a custodial EVM address exist. These are real custodial keys held for- the agent (see [Agent Wallets](#sec-077) and [Custody](#sec-232)),+ the agent (see [Agent Wallets](#sec-077) and [Custody](#sec-233)),Solana first because Solana is the home chain.- **Persona and voice.** `POST /api/persona/extract` synthesizes a structuredin-character system prompt from your description, running through the shared LLM@@ -82587,7 +82834,7 @@ never invents a shortcut path; it orchestrates the real ones.`/api/tts/voices`. Your chosen name, persona, and voice are persisted with`PATCH /api/agents/:id`.- **On-chain identity (optional).** The final step mints a real- [ERC-8004](#sec-263) identity record for the agent and returns a real tx+ [ERC-8004](#sec-266) identity record for the agent and returns a real txhash, defaulting to Base (chain id 8453) to match the rest of the platform's EVMidentity layer. This step is optional: the agent is fully functional without it.@@ -82609,14 +82856,14 @@ never invents a shortcut path; it orchestrates the real ones.6. **Optionally bind an on-chain identity.** One click registers the ERC-8004 recordand shows the returned transaction hash.7. **You now own a complete agent.** Open it in [Agent Studio](#sec-066) to- keep authoring, drop it on a site via [Integrations](#sec-383), or breed- it in [Agent Genome](#sec-322).+ keep authoring, drop it on a site via [Integrations](#sec-387), or breed+ it in [Agent Genome](#sec-325).## ExamplesGenesis is a browser flow, but its endpoints are the public agent APIs. This drivesthe same body-generation step from a script (see-[API reference](#sec-124) and [Authentication](#sec-138) for+[API reference](#sec-125) and [Authentication](#sec-139) forthe session cookie or bearer token):```bash@@ -82671,16 +82918,16 @@ curl -s -X POST "https://three.ws/api/agents/$AGENT_ID/wallet/provision" \## Related- [Agent Studio](#sec-066): keep authoring the agent Genesis created-- [Agent Genome](#sec-322): breed two agents into an inherited child-- [Avatar Reconstruction](#sec-149): the selfie-to-3D pipeline-- [Agent Wallets](#sec-077) and [Custody](#sec-232): the custodial keys-- [ERC-8004](#sec-263): the on-chain identity record-- [Persona Hub](#sec-491): how personas are synthesized+- [Agent Genome](#sec-325): breed two agents into an inherited child+- [Avatar Reconstruction](#sec-150): the selfie-to-3D pipeline+- [Agent Wallets](#sec-077) and [Custody](#sec-233): the custodial keys+- [ERC-8004](#sec-266): the on-chain identity record+- [Persona Hub](#sec-498): how personas are synthesized- Pages: [/genesis](https://three.ws/genesis), [/create](https://three.ws/create), [/agent-studio](https://three.ws/agent-studio)----<a id="sec-322"></a>+<a id="sec-325"></a>> **Source:** `docs/genome.md` · [↑ table of contents](#table-of-contents)@@ -82723,7 +82970,7 @@ parents and the same seed it always derives the identical child.settings are genuinely synthesized through `/api/tts/eleven`, not just labelled.There is no free platform TTS lane: a preview clip bills the listener's prepaidcredit wallet, or their own ElevenLabs key when one is saved (see- [Voice Lab](#sec-796)).+ [Voice Lab](#sec-807)).- **Body.** Morph targets and colors blend; accessories and hidden parts recombine assets. At breed time the dominant parent's GLB is copied into the child's namespaceand the inherited appearance is baked into a real composite child GLB.@@ -82770,7 +83017,7 @@ parents and the same seed it always derives the identical child.## ExamplesPreview a pairing (read-only, nothing minted). See-[Authentication](#sec-138) for the token or session cookie:+[Authentication](#sec-139) for the token or session cookie:```bashcurl -s -X POST https://three.ws/api/genome/preview \@@ -82827,16 +83074,16 @@ curl -s "https://three.ws/api/genome/lineage?agentId=<child-uuid>&verify=1"## Related-- [Instant Agent Genesis](#sec-321): mint the parents in under a minute+- [Instant Agent Genesis](#sec-324): mint the parents in under a minute- [Agent Skills](#sec-064): the skill licenses that recombine- [Agent Wallets](#sec-077): the fresh child wallet- [Agent Reputation](#sec-060): how pedigree feeds standing-- [ERC-8004](#sec-263): on-chain identity for bred agents+- [ERC-8004](#sec-266): on-chain identity for bred agents- Pages: [/genome](https://three.ws/genome), [/agent-studio](https://three.ws/agent-studio)----<a id="sec-323"></a>+<a id="sec-326"></a>> **Source:** `docs/ghost-copy.md` · [↑ table of contents](#table-of-contents)@@ -82851,7 +83098,7 @@ Page: [/ghost-copy](https://three.ws/ghost-copy) · API: `/api/pump/ghost-copy`The replay itself signs nothing, spends nothing, connects no wallet, and needsno account. It is arithmetic over trades that already happened. The one live-action on the page is [Fork](#sec-315) on a position the leader is still+action on the page is [Fork](#sec-318) on a position the leader is stillholding: that opens the real pump.fun trade panel at your ghost size, and yourown wallet signs it. Forking is opt-in, one coin at a time, and never happensas part of a replay.@@ -83001,11 +83248,11 @@ renders the summary without it is misrepresenting the result.cautious question with a basket instead of a single leader.- Downstream: [/vaults](https://three.ws/vaults) is where a convinced visitorcopies with real money, under segregated custody and hard spend limits. See- [docs/copy-trading.md](#sec-225) for that engine.+ [docs/copy-trading.md](#sec-226) for that engine.- A leader's underlying record: `/trader/<agent_id>`, one click from every result.- First-timers: [/copy-coach](https://three.ws/copy-coach), linked from the top ofthe page, walks a newcomer from a real win through a ghost copy like this one to- one small capped copy they sign themselves. See [docs/copy-coach.md](#sec-224).+ one small capped copy they sign themselves. See [docs/copy-coach.md](#sec-225).- Quests: for a signed-in visitor, the page reports each finished replay to`POST /api/quests/event` (`kind: "ghost_copy"`), which counts toward the daily"ghost-copy a new agent" quest on [/quests](https://three.ws/quests). Only the@@ -83024,7 +83271,7 @@ renders the summary without it is misrepresenting the result.----<a id="sec-324"></a>+<a id="sec-327"></a>> **Source:** `docs/github-growth.md` · [↑ table of contents](#table-of-contents)@@ -83050,7 +83297,7 @@ Every public repository on the [nirholas](https://github.com/nirholas) GitHub acThe kit is one pure module, [scripts/lib/repo-growth-kit.mjs](../scripts/lib/repo-growth-kit.mjs), used two ways so the result is the same either way:1. **Independent repos** are fixed in place by [scripts/boost-github-repos.mjs](../scripts/boost-github-repos.mjs). It walks every public, non-fork, non-archived repo from the least-starred to the most-starred, shallow-clones it, applies the kit, commits with a message describing exactly what was added, pushes the default branch, then sets the repository settings.-2. **Standalone mirrors** (see [Standalone repositories](#sec-665)) are force-pushed snapshots, so a direct edit would be erased by the next sync. `scripts/lib/standalone-kit.mjs` calls the same module while decorating each mirror README, so a sync reproduces the block instead of wiping it.+2. **Standalone mirrors** (see [Standalone repositories](#sec-673)) are force-pushed snapshots, so a direct edit would be erased by the next sync. `scripts/lib/standalone-kit.mjs` calls the same module while decorating each mirror README, so a sync reproduces the block instead of wiping it.```bashnode scripts/boost-github-repos.mjs # plan every repo, write nothing@@ -83125,13 +83372,13 @@ The repository social preview image can only be uploaded in the web UI (Settings## Related-- [Standalone repositories](#sec-665): the generated package mirrors+- [Standalone repositories](#sec-673): the generated package mirrors- [Contributing](contributing.md#publishing-packages--standalone-mirrors): publishing and syncing mirrors- [Agent skills](#sec-064): the standalone skill repos----<a id="sec-325"></a>+<a id="sec-328"></a>> **Source:** `docs/github-memory-seeding.md` · [↑ table of contents](#table-of-contents)@@ -83158,7 +83405,7 @@ the same consent screen.- **Surface**: Settings, Connected accounts, GitHub card at [/settings#connected-accounts](https://three.ws/settings#connected-accounts)- **API**: `/api/agents/:id/memory/seed/github`, `/api/auth/github/token`-- **Related**: [Memory system](#sec-420), [X memory seeding](#sec-813), [Farcaster memory seeding](#sec-302)+- **Related**: [Memory system](#sec-424), [X memory seeding](#sec-826), [Farcaster memory seeding](#sec-305)---@@ -83469,7 +83716,7 @@ rather than inviting a retry that would only earn a 429.----<a id="sec-326"></a>+<a id="sec-329"></a>> **Source:** `docs/glance.md` · [↑ table of contents](#table-of-contents)@@ -83647,13 +83894,13 @@ The three.ws Android app (1.1 and later) ships an **Agent glance** home screen w## Where this is going-Glance is phase 5 of the [roadmap](https://github.com/nirholas/three.ws/blob/main/README.md#roadmap). Windows 11, Android and the web are live. macOS and iOS are built: one WidgetKit extension over the same PNG endpoint and the same widget token, sources in [apple/](https://github.com/nirholas/three.ws/tree/main/apple), waiting only on an Apple Developer account to sign and distribute the two binaries. See [native-widgets.md](#sec-440).+Glance is phase 5 of the [roadmap](https://github.com/nirholas/three.ws/blob/main/README.md#roadmap). Windows 11, Android and the web are live. macOS and iOS are built: one WidgetKit extension over the same PNG endpoint and the same widget token, sources in [apple/](https://github.com/nirholas/three.ws/tree/main/apple), waiting only on an Apple Developer account to sign and distribute the two binaries. See [native-widgets.md](#sec-444).Every one of those surfaces consumes the endpoint documented above. The card is the contract; the hosts are just slots.----<a id="sec-327"></a>+<a id="sec-330"></a>> **Source:** `docs/glasses.md` · [↑ table of contents](#table-of-contents)@@ -83775,7 +84022,7 @@ contract, documented in [IRL](/docs/irl) and shipped asThere is no browseable map and no "query any point on earth", on a lens oranywhere else. You see what is around you because you are there. The reasoning-is in [docs/irl/THREAT-MODEL.md](#sec-387).+is in [docs/irl/THREAT-MODEL.md](#sec-391).## Related@@ -83787,7 +84034,7 @@ is in [docs/irl/THREAT-MODEL.md](#sec-387).----<a id="sec-328"></a>+<a id="sec-331"></a>> **Source:** `docs/glasses/meta-ray-ban-display.md` · [↑ table of contents](#table-of-contents)@@ -84113,7 +84360,7 @@ free, and the agent stands in the same doorway it was left in.- Rendering a three.ws avatar on the lens. The hardware cannot, and pretendingotherwise would ship a blurry sprite that undersells the product.- A map of every agent on earth. Presence-gated reads are the contract, on every- client. See [docs/irl/THREAT-MODEL.md](#sec-387).+ client. See [docs/irl/THREAT-MODEL.md](#sec-391).- Custom Neural Band gestures. Meta exposes five inputs. We design for five.- Continuous camera capture on the native lane. Frames serve a pose fix in themoment and are not retained.@@ -84148,12 +84395,12 @@ free, and the agent stands in the same doorway it was left in.- [three.ws on smart glasses](/docs/glasses)- [Platform and package research](/docs/glasses/research)- [IRL](/docs/irl), the [street demo runbook](/docs/irl/street-demo) and the- [threat model](#sec-387)+ [threat model](#sec-391)- [`@three-ws/irl`](https://www.npmjs.com/package/@three-ws/irl)----<a id="sec-329"></a>+<a id="sec-332"></a>> **Source:** `docs/glasses/research.md` · [↑ table of contents](#table-of-contents)@@ -84275,7 +84522,7 @@ the difference between a phase being possible and being blocked.----<a id="sec-330"></a>+<a id="sec-333"></a>> **Source:** `docs/globe.md` · [↑ table of contents](#table-of-contents)@@ -84523,7 +84770,77 @@ reason attached; it does not take the page with it.----<a id="sec-331"></a>+<a id="sec-334"></a>++> **Source:** `docs/google-adk.md` · [↑ table of contents](#table-of-contents)++# three.ws with Google ADK++Connect a [Google Agent Development Kit](https://google.github.io/adk-docs/)+agent to the three.ws 3D studio over `MCPToolset`, ADK's built-in Model Context+Protocol client. The free studio server needs no three.ws account: no API+key, no payment, no wallet.++**Runnable sample:** [examples/google-adk](../examples/google-adk/README.md)++## Connect++| | |+|---|---|+| **URL** | `https://three.ws/api/mcp-studio` |+| **Transport** | Streamable HTTP (JSON-RPC over `POST`) |+| **Auth** | None for the studio tools |+| **Protocol** | MCP `2025-06-18` |+| **Tools** | The full free studio: the same fifteen tools as [`/api/mcp-studio`](#sec-418) |++## Use with an agent++```ts+import { LlmAgent, MCPToolset } from '@google/adk';++const toolset = new MCPToolset({+ type: 'StreamableHTTPConnectionParams',+ url: 'https://three.ws/api/mcp-studio',+});++const agent = new LlmAgent({+ model: 'gemini-flash-latest',+ name: 'three_ws_agent',+ instruction: 'You help the user generate and rig 3D models with the three.ws studio tools.',+ tools: [toolset],+});+```++`MCPToolset.getTools()` discovers the live tool catalog (`forge_free`,+`text_to_avatar`, `mesh_forge`, `rig_mesh`, `forge_avatar`, `refine_model`,+`look_at_model`, `search_catalog`, `get_catalog_item`, `get_item_source`,+`create_agent_persona`, `get_agent_persona`, `persona_say`, and the job tools+`check_job`/`get_job`) and wraps each as an ADK `BaseTool` the model can call+during a conversation; ADK manages the MCP session underneath.++A tool can also be invoked directly, without a model in the loop, by calling+`runAsync({ args, toolContext })` on the `BaseTool` the toolset returns. That+path needs no Gemini credential at all, which is how the sample proves the+wiring: discover the catalog, then run a real `rig_mesh` call and print the+viewer, GLB and embed links it returns.++## Beyond the free lane++The full MCP server (`/api/mcp`) also exposes paid, x402-gated tools+(`text_to_animation` and others). Point `MCPToolset`'s `url` at it and add an+x402 client to `transportOptions.requestInit` to pay for those calls; the+free studio server above never needs one. See [docs/mcp.md](#sec-421) for the+full catalog, authentication and the x402 payment flow.++## See also++- [examples/google-adk](../examples/google-adk/README.md): the runnable sample, verified against production.+- [docs/mcp.md](#sec-421): the full MCP server reference.+- [docs/mcp-studio.md](#sec-418): the free studio server this sample connects to.++---++<a id="sec-335"></a>> **Source:** `docs/google-cloud-community-post.md` · [↑ table of contents](#table-of-contents)@@ -84651,7 +84968,7 @@ Free to try, no account and no key: [three.ws/forge](https://three.ws/forge) for----<a id="sec-332"></a>+<a id="sec-336"></a>> **Source:** `docs/google-x-accounts.md` · [↑ table of contents](#table-of-contents)@@ -84763,7 +85080,7 @@ Google also operates many country and regional accounts (for example @GoogleIndi----<a id="sec-333"></a>+<a id="sec-337"></a>> **Source:** `docs/grok-bot.md` · [↑ table of contents](#table-of-contents)@@ -84774,8 +85091,8 @@ task unattended, on a schedule, and hand files from one tool to the next. Thispage is the integration reference: the exact connector settings for each sign-inmode, which of the hosted servers to pick, the contract an unattended agent canrely on (links, jobs, retries, limits, spend), and a fix for every failure the-connector probe can report. For the product tour read [three.ws for Grok](#sec-334);-for every tool in depth read [the free 3D Studio MCP](#sec-414).+connector probe can report. For the product tour read [three.ws for Grok](#sec-338);+for every tool in depth read [the free 3D Studio MCP](#sec-418).## Connect it@@ -85067,16 +85384,16 @@ The run asks "Find a ready-made chair in the three.ws catalog and give me its vi## Related-- [Grok Bot recipes](#sec-732): six jobs to hand Grok Bot, each run against production with its real output.-- [three.ws for Grok](#sec-334): the product tour, the xAI API examples and the skill file.-- [The free 3D Studio MCP](#sec-414): every tool, tier and limit in depth.-- [MCP integration](#sec-417): every hosted server, OAuth and API keys.+- [Grok Bot recipes](#sec-740): six jobs to hand Grok Bot, each run against production with its real output.+- [three.ws for Grok](#sec-338): the product tour, the xAI API examples and the skill file.+- [The free 3D Studio MCP](#sec-418): every tool, tier and limit in depth.+- [MCP integration](#sec-421): every hosted server, OAuth and API keys.- [Connector probe results](../prompts/x-grok/_generated/connector-probe.json): the latest production run.- [Example: Responses API client](../examples/grok-remote-mcp/README.md).----<a id="sec-334"></a>+<a id="sec-338"></a>> **Source:** `docs/grok.md` · [↑ table of contents](#table-of-contents)@@ -85091,7 +85408,7 @@ skills, without ever being able to spend.**Live page and demo:** [three.ws/grok](/grok)-**Connector reference** (exact fields per sign-in mode, the result and job contracts, limits, troubleshooting): [Grok Bot connector reference](#sec-333)+**Connector reference** (exact fields per sign-in mode, the result and job contracts, limits, troubleshooting): [Grok Bot connector reference](#sec-337)| | ||---|---|@@ -85099,7 +85416,7 @@ skills, without ever being able to spend.| **Transport** | Streamable HTTP (JSON-RPC over `POST`) || **Auth** | None for the studio. Optional: a connector API key, or OAuth 2.1 at `https://three.ws/api/mcp-grok?auth=oauth`, adds your agent tools || **Protocol** | MCP `2025-06-18` |-| **Tools** | The full free studio: the same fifteen tools as [`/api/mcp-studio`](#sec-414). Signed in, also your [account's agent tools](#your-account-on-the-same-url) |+| **Tools** | The full free studio: the same fifteen tools as [`/api/mcp-studio`](#sec-418). Signed in, also your [account's agent tools](#your-account-on-the-same-url) |## Grok Bot@@ -85337,12 +85654,12 @@ caller that already has one).advertises. The account tools come from the core server through[`api/_mcp-studio/account-tools.js`](../api/_mcp-studio/account-tools.js), whoseallowlist only admits a tool the shared policy says moves no value. They share one generation quota and one breaker, so the Grok door-never adds GPU spend of its own. See [the free 3D Studio MCP](#sec-414)-for the tools in depth and [MCP integration](#sec-417) for every hosted server.+never adds GPU spend of its own. See [the free 3D Studio MCP](#sec-418)+for the tools in depth and [MCP integration](#sec-421) for every hosted server.----<a id="sec-335"></a>+<a id="sec-339"></a>> **Source:** `docs/growth-programs.md` · [↑ table of contents](#table-of-contents)@@ -85462,7 +85779,7 @@ A bounded $THREE bonus for the first `EARLY_LEADER_SLOTS` traders whose record c| Realized P&L | above zero || Max drawdown (share of capital deployed) | at most 50% || Copyable | clears the copy-trading bar in [`copy-eligibility.js`](../api/_lib/copy-eligibility.js) |-| Followers | at least 1 copier (never the leader's own account) with closed copies, whose net copy profit is zero or better, measured the way [copy trading](#sec-225) bills performance fees |+| Followers | at least 1 copier (never the leader's own account) with closed copies, whose net copy profit is zero or better, measured the way [copy trading](#sec-226) bills performance fees || Eligibility | public agent, has a Solana wallet to pay, not owned by a platform account |P&L on a coin the trader launched is left out of the record, as on the Trader Card. "First" means by qualification time: the close at which the record first cleared every trading bar. Each owner account can hold one slot, and a slot once taken is kept. The bonus, `EARLY_LEADER_BONUS_USD`, is paid in $THREE at the live price to the agent's Solana wallet.@@ -85506,7 +85823,7 @@ With the defaults, the most the two payout programs can ever send is $100 a dayBoth payout programs write committed payouts to one ledger table, `growth_program_payouts` (migration [`20260929120000_growth_program_payouts.sql`](../api/_lib/migrations/20260929120000_growth_program_payouts.sql)). `/api/cron/growth-payouts` runs at minute 23 of every hour. For each program it refuses to send unless all of these hold:1. The program's flag is set.-2. The dedicated payout key is configured: `THREE_PRIZE_PAYOUT_KEY`, the same funded $THREE wallet the [Arena](#sec-690) pays tournament prizes from, so there is one payout wallet to watch. The Arena's fallback to the club treasury secret is deliberately not used here: on production that secret is the economy master (funding root) wallet, which these programs must never spend. As of 2026-09-29, `THREE_PRIZE_PAYOUT_KEY` is not set on production, so an armed payout program reports `payout_unconfigured` and sends nothing until it is.+2. The dedicated payout key is configured: `THREE_PRIZE_PAYOUT_KEY`, the same funded $THREE wallet the [Arena](#sec-698) pays tournament prizes from, so there is one payout wallet to watch. The Arena's fallback to the club treasury secret is deliberately not used here: on production that secret is the economy master (funding root) wallet, which these programs must never spend. As of 2026-09-29, `THREE_PRIZE_PAYOUT_KEY` is not set on production, so an armed payout program reports `payout_unconfigured` and sends nothing until it is.3. The recipient is a valid Solana address and not a platform wallet (the treasury, the rewards pool, or the payout wallet itself).4. The payout fits under the program's rolling cap, summed over everything already sending or sent in the period. The queue is first-come-first-served: a payout that does not fit waits for the window to roll, and a smaller one behind it does not jump ahead.5. A live $THREE price is available. A payout never goes out at a guessed price.@@ -85570,14 +85887,14 @@ Payouts already queued stay in the ledger as `claimed` and are paid only if the## Related-- [Copy trading](#sec-225): the follower economy the early-leader bonus seeds.-- [The Oracle model](#sec-465): the Coin Intelligence labels, including the rug verdict, that the softener reads.-- [The X content pipeline](#sec-812): the reviewed posts that share the account's daily budget with this lane.+- [Copy trading](#sec-226): the follower economy the early-leader bonus seeds.+- [The Oracle model](#sec-470): the Coin Intelligence labels, including the rug verdict, that the softener reads.+- [The X content pipeline](#sec-825): the reviewed posts that share the account's daily budget with this lane.- [`STRUCTURE.md`](../STRUCTURE.md): where every surface lives.----<a id="sec-336"></a>+<a id="sec-340"></a>> **Source:** `docs/guardian.md` · [↑ table of contents](#table-of-contents)@@ -85603,7 +85920,7 @@ The owner sets this up from their own wallet hub (naming guardians, an approvalThe response sorts agents that need your action first, then those with an open process, then the rest, and reports how many need you.-**The safety rails** (detailed in [custody](#sec-232)) are enforced by the recovery API, not the console:+**The safety rails** (detailed in [custody](#sec-233)) are enforced by the recovery API, not the console:- The requester cannot approve their own takeover; at least one other guardian must approve.- The wallet auto-freezes for autonomous spend the moment a request opens (the real owner's own withdrawal stays open).@@ -85657,14 +85974,14 @@ The console reads this on load, resolves your viewer id (so it can tell whether## Related-- [Custody you can verify](#sec-232) - the full recovery and inheritance model, the freeze switch, spend limits, and proof-of-custody-- [Financial controls](#sec-306) - the plain-English spend rules on the same wallet rails+- [Custody you can verify](#sec-233) - the full recovery and inheritance model, the freeze switch, spend limits, and proof-of-custody+- [Financial controls](#sec-309) - the plain-English spend rules on the same wallet rails- `GET /api/custody/integrity` - the public Merkle attestation of every custodial wallet, as JSON (the page that rendered it is switched off while on-chain anchoring is unavailable)- [/proof](https://three.ws/proof) - verify your own wallet's inclusion in the attestation, in your browser----<a id="sec-337"></a>+<a id="sec-341"></a>> **Source:** `docs/guards.md` · [↑ table of contents](#table-of-contents)@@ -85818,7 +86135,7 @@ Run `npm run audit:guards` to print the current count and per-stage breakdown. T| Documentation drift budget | `npm run check:docs-freshness` | No more docs describe code that changed after they were written than `data/docs-freshness-budget.json` allows. The budget is a ratchet: it only goes down, and raising it needs a recorded reason. || OpenAI directory field limits | `npm run check:openai-fields` | Every field pasted into the OpenAI Plugin Directory form fits under the length the portal silently truncates at, and each tool justification is one sentence describing behavior. || Home lane translation keys | `npm run i18n:home` | Every string the connected home speaks from JS has a key in `public/locales/en.json` whose English matches the code exactly, and no source value bakes a user's own room or device name into a translatable sentence. |-| Home Assistant support table | `npm run check:home-matrix` | The version table in [smart-home.md](#sec-651) is exactly what the last real matrix run measured, so a supported release is a measurement rather than a claim. |+| Home Assistant support table | `npm run check:home-matrix` | The version table in [smart-home.md](#sec-659) is exactly what the last real matrix run measured, so a supported release is a measurement rather than a claim. || Runnable doc samples | `npm run check:runnable-docs` | Every sample a reader can press Run on still returns what the doc says it returns. || Doc figures | `npm run check:doc-media` | Every figure a doc points at was really captured, still matches its recipe, and carries alt text. || Announcement packs | `npm run check:announce` | Every announcement pack ships captured media with alt text, a post inside X's real weighted limit, an opening no other pack reuses, and no reference to a crypto project other than $THREE. |@@ -85964,7 +86281,7 @@ The short version:----<a id="sec-338"></a>+<a id="sec-342"></a>> **Source:** `docs/herald.md` · [↑ table of contents](#table-of-contents)@@ -86240,15 +86557,15 @@ The avatar is the point, but it is never the requirement.## Related-- [Notifications](#sec-442): the bell, the inbox API, and the+- [Notifications](#sec-446): the bell, the inbox API, and theper-category avatar channel that uses this on three.ws itself.- [walk-sdk](../walk-sdk/README.md): the 3D body, and `control.announce()`, theprimitive the avatar presenter delivers through.-- [The developer platform](#sec-244): API keys, scopes, and usage.+- [The developer platform](#sec-245): API keys, scopes, and usage.----<a id="sec-339"></a>+<a id="sec-343"></a>> **Source:** `docs/hold-to-access.md` · [↑ table of contents](#table-of-contents)@@ -86609,13 +86926,13 @@ Unit coverage for the same behavior lives in `tests/forge-high-gate.test.js`,## Related-- [Validation](#sec-790) — the quality gate every model passes before publish.+- [Validation](#sec-799) — the quality gate every model passes before publish.- [Pricing catalog](../api/_lib/pricing/catalog.js) — fixed-price actions the discount applies to.- [`/three`](../pages/three.html) — the holder-facing tier page that surfaces this ladder.----<a id="sec-340"></a>+<a id="sec-344"></a>> **Source:** `docs/home-assistant-community-post.md` · [↑ table of contents](#table-of-contents)@@ -86781,7 +87098,7 @@ Happy to answer anything, including why a 3D avatar belongs in a house. I have a----<a id="sec-341"></a>+<a id="sec-345"></a>> **Source:** `docs/home-households.md` · [↑ table of contents](#table-of-contents)@@ -86795,7 +87112,7 @@ serviced building, the roles and the attribution are the entire purchase decisioThis document is the contract. It covers the five roles, what each one may do, how a scoped membersees a narrowed house, how invitations work, and what happens to somebody's access when they leave.-Related: [smart-home.md](#sec-651) for why three.ws writes zero device code and what the Home+Related: [smart-home.md](#sec-659) for why three.ws writes zero device code and what the HomeAssistant bridge does.---@@ -87162,7 +87479,7 @@ insert. A home can never exist in a state where nobody can administer it.----<a id="sec-342"></a>+<a id="sec-346"></a>> **Source:** `docs/home-plans.md` · [↑ table of contents](#table-of-contents)@@ -87176,9 +87493,9 @@ owner**. Every number in the plan table is a proposal with a measured cost behinnumber is a config value: applying an owner-approved figure is an environment variable on arunning service, not a deploy.-Related: [`docs/smart-home.md`](#sec-651) (what the lane is),-[`docs/home-privacy.md`](#sec-343) (retention and deletion),-[`docs/home-households.md`](#sec-341) (roles and seats).+Related: [`docs/smart-home.md`](#sec-659) (what the lane is),+[`docs/home-privacy.md`](#sec-347) (retention and deletion),+[`docs/home-households.md`](#sec-345) (roles and seats).---@@ -87533,7 +87850,7 @@ the product mints for itself, and the test would then be exercising a path no us----<a id="sec-343"></a>+<a id="sec-347"></a>> **Source:** `docs/home-privacy.md` · [↑ table of contents](#table-of-contents)@@ -87549,7 +87866,7 @@ If you only read one thing: **we never store the names of your rooms or devices,and we never store their states.** There is no record of which lights were on, orwhen. A log of that is a log of when you are home, and we do not keep one.-Related reading: [three.ws Home](#sec-651) for how the connection works,+Related reading: [three.ws Home](#sec-659) for how the connection works,and the [platform privacy policy](/legal/privacy) for everything outside thislane.@@ -87823,7 +88140,7 @@ them.----<a id="sec-344"></a>+<a id="sec-348"></a>> **Source:** `docs/home-relay-threat-model.md` · [↑ table of contents](#table-of-contents)@@ -87836,7 +88153,7 @@ This is the document [`services/home-relay/src/server.js`](../services/home-rela[`protocol.js`](../services/home-relay/src/protocol.js) and[`api/home/pair.js`](../api/home/pair.js) tell you to read before changing them. It covers therelay specifically. The platform-wide model, the prompt-injection boundary and the abuse surface-are in [home-security.md](#sec-348).+are in [home-security.md](#sec-352).## What the relay is@@ -88063,16 +88380,16 @@ reach a house without having passed that, the change is wrong.- [`services/home-relay/README.md`](../services/home-relay/README.md): running it, its endpoints,and regenerating the allowlist.-- [home-relay.md](#sec-345): installing the integration, configuring the relay, and the+- [home-relay.md](#sec-349): installing the integration, configuring the relay, and thetwo-network setup that proves the path against an unroutable house.-- [home-security.md](#sec-348): the platform threat model, the injection boundary, the+- [home-security.md](#sec-352): the platform threat model, the injection boundary, theeleven checks.-- [smart-home.md](#sec-651): why the reachability problem exists and the three answers to it.-- [tutorials/connect-your-home.md](#sec-716): the user-facing walkthrough.+- [smart-home.md](#sec-659): why the reachability problem exists and the three answers to it.+- [tutorials/connect-your-home.md](#sec-724): the user-facing walkthrough.----<a id="sec-345"></a>+<a id="sec-349"></a>> **Source:** `docs/home-relay.md` · [↑ table of contents](#table-of-contents)@@ -88121,9 +88438,14 @@ unlocking, opening and disarming always stop and ask a person first.To install without HACS, download the latest release, copy `custom_components/three_ws` into yourHome Assistant `config` folder, restart, and do step 4.+The integration validates clean against the real `hassfest` and HACS checks (`scripts/export-hacs-repo.mjs`+builds the exact tree those checks run against) and ships its own brand icon, so once+`nirholas/three-ws-home-assistant` is live it is ready for the HACS default store: no custom+repository step, just **HACS, Integrations, search "three.ws"**.+### What it can and cannot do-Read [the threat model](#sec-344). It is written for someone deciding whether to+Read [the threat model](#sec-348). It is written for someone deciding whether toinstall this, and it is specific about the blast radius rather than reassuring.The short version: three.ws can read your entities and your room layout, and it can call device@@ -88288,7 +88610,7 @@ more than a day ago). It is wired in `vercel.json` and runs hourly.----<a id="sec-346"></a>+<a id="sec-350"></a>> **Source:** `docs/home-satellite.md` · [↑ table of contents](#table-of-contents)@@ -88476,7 +88798,7 @@ written from that source, and where our reading differed from the wire, the wire----<a id="sec-347"></a>+<a id="sec-351"></a>> **Source:** `docs/home-scene.md` · [↑ table of contents](#table-of-contents)@@ -88490,9 +88812,9 @@ It is also, deliberately, a house you can operate: click anything, act on it,and the physical-action gate asks before it opens anything. The same page in its2D view does all of that without a GPU.-**Related:** [three.ws Home](#sec-651) (why any of this exists),-[connecting a house](#sec-716),-[households and roles](#sec-341), [home security](#sec-348).+**Related:** [three.ws Home](#sec-659) (why any of this exists),+[connecting a house](#sec-724),+[households and roles](#sec-345), [home security](#sec-352).---@@ -88505,7 +88827,7 @@ and the physical-action gate asks before it opens anything. The same page in its| `/smart-home/<id>/settings` | that home's grants, action log and disconnect || `/home/<id>` | the same live house, at the campaign's own address |-You need a connected home first. [The tutorial](#sec-716)+You need a connected home first. [The tutorial](#sec-724)takes about three minutes.## What you are looking at@@ -88548,7 +88870,7 @@ anyone has filed a thing.Yours. The figure in the scene is your own agent, wearing the same avatar the[walk world](../STRUCTURE.md), `/play` and the-[voice satellite](#sec-346) show, resolved from the one canonical+[voice satellite](#sec-350) show, resolved from the one canonical"my agent" record the whole platform reads. Switch agents in another tab and thebody in the house changes with it, without a reload.@@ -88567,7 +88889,7 @@ falls back rather than freezing in a T-pose.## ReactivityThe page holds one Server-Sent Events subscription to-`GET /api/home/<id>/stream` ([the API reference](#sec-124)). It never+`GET /api/home/<id>/stream` ([the API reference](#sec-125)). It neverpolls.Measured against a real Home Assistant on the same machine:@@ -88791,7 +89113,7 @@ HOME_LIVE_NAME=mylane HOME_E2E_API_PORT=8141 HOME_E2E_WEB_PORT=3071 \----<a id="sec-348"></a>+<a id="sec-352"></a>> **Source:** `docs/home-security.md` · [↑ table of contents](#table-of-contents)@@ -88804,7 +89126,7 @@ could delete, a balance someone could drain, a session someone could steal. Thisabout a deadbolt. The worst outcome the home lane can produce is not a leak, it is a strangeropening a front door, and every control below is ranked against that sentence.-Read [smart-home.md](#sec-651) first for what the lane is and how it reaches a house. This+Read [smart-home.md](#sec-659) first for what the lane is and how it reaches a house. Thisdocument is what stands between a stranger and the lock.Every claim here is enforced by [`tests/home-security.test.js`](../tests/home-security.test.js),@@ -89168,7 +89490,7 @@ The secrets scan and the dependency posture run with everything else and need no----<a id="sec-349"></a>+<a id="sec-353"></a>> **Source:** `docs/home-voice.md` · [↑ table of contents](#table-of-contents)@@ -89178,7 +89500,7 @@ The secrets scan and the dependency posture run with everything else and need nosurface that wants it. **Last measured against the tree:** 2026-09-09.Hands-free is the only interface that works when you are carrying groceries into a dark kitchen.-This is the part of [three.ws Home](#sec-651) that lets you say "turn the kitchen light+This is the part of [three.ws Home](#sec-659) that lets you say "turn the kitchen lightoff" to a browser that is already open, and get the light and an answer without touchinganything.@@ -89228,7 +89550,7 @@ else.continuously overwritten.- **Only the utterance after the wake word is uploaded**, and only to be transcribed.- **Nothing is retained.** `/api/asr` holds the clip for the request and no longer. Retention of- anything else is covered by [Home privacy and retention](#sec-343); this loop creates+ anything else is covered by [Home privacy and retention](#sec-347); this loop createsno data class of its own.- **The indicator cannot be turned off.** Whenever a microphone track is live, the panel showsit, and the indicator reads the `MediaStreamTrack`, not a flag the state machine could get@@ -89245,7 +89567,7 @@ off.## The confirmation, and why a general "yes" does not countHome Assistant's own `HassTurnOff` intent performs an **unlock** on a lock. That single fact is-why [the gate](#sec-348) exists, and it is why this loop treats a spoken confirmation+why [the gate](#sec-352) exists, and it is why this loop treats a spoken confirmationas the most dangerous thing it does.When a turn produces a guarded action, the server mints a confirmation and the loop:@@ -89478,21 +89800,21 @@ would only let the two drift.## Related-- [three.ws Home](#sec-651): the whole plan, and what a connection is-- [Home security](#sec-348): the gate this loop speaks for-- [Home privacy and retention](#sec-343): what is stored and for how long-- [Households](#sec-341): who in a house may approve an unlock-- [three.ws Drive](#sec-179): the same agent, voice-first, in a car+- [three.ws Home](#sec-659): the whole plan, and what a connection is+- [Home security](#sec-352): the gate this loop speaks for+- [Home privacy and retention](#sec-347): what is stored and for how long+- [Households](#sec-345): who in a house may approve an unlock+- [three.ws Drive](#sec-180): the same agent, voice-first, in a car----<a id="sec-350"></a>+<a id="sec-354"></a>> **Source:** `docs/how-forge-works.md` · [↑ table of contents](#table-of-contents)# How the Forge works, in plain language-You type "a weathered brass diving helmet" at [three.ws/forge](https://three.ws/forge), and about half a minute later you are orbiting a real, textured 3D model you can download, view in AR, or drop into a scene. No account, no key, no cost. This page explains what actually happens in between, without the engineering detail. (If you want that, read the [architecture deep dive](#sec-311).)+You type "a weathered brass diving helmet" at [three.ws/forge](https://three.ws/forge), and about half a minute later you are orbiting a real, textured 3D model you can download, view in AR, or drop into a scene. No account, no key, no cost. This page explains what actually happens in between, without the engineering detail. (If you want that, read the [architecture deep dive](#sec-314).)## The five steps every generation takes@@ -89526,17 +89848,17 @@ A finished model is a starting point, not a dead end:## Agents use the exact same machinery-Everything above is also a tool call. AI agents (Claude, ChatGPT, or your own) generate models through our [free MCP server](#sec-414) or plain HTTP, and other agents pay per call with USDC over [x402](#sec-862), no account needed. The page you use and the API an agent uses are the same pipeline underneath.+Everything above is also a tool call. AI agents (Claude, ChatGPT, or your own) generate models through our [free MCP server](#sec-418) or plain HTTP, and other agents pay per call with USDC over [x402](#sec-877), no account needed. The page you use and the API an agent uses are the same pipeline underneath.## Try it- Type a prompt: [three.ws/forge](https://three.ws/forge)- Turn photos into a model: [three.ws/image-to-3d](https://three.ws/image-to-3d)-- The full technical breakdown: [the Forge pipeline deep dive](#sec-311)+- The full technical breakdown: [the Forge pipeline deep dive](#sec-314)----<a id="sec-351"></a>+<a id="sec-355"></a>> **Source:** `docs/how-it-works.md` · [↑ table of contents](#table-of-contents)@@ -89544,7 +89866,7 @@ Everything above is also a tool call. AI agents (Claude, ChatGPT, or your own) gThis page is the load-bearing mental model. If you're trying to figure out where a feature lives, how a request flows, or which layer to extend — start here.-For the full deep dive on internals, see [Architecture overview](#sec-130). For the actual JS API, see [JavaScript API](#sec-390) and [REST API](#sec-124). This document zooms out to *how it all fits together*.+For the full deep dive on internals, see [Architecture overview](#sec-131). For the actual JS API, see [JavaScript API](#sec-394) and [REST API](#sec-125). This document zooms out to *how it all fits together*.---@@ -89591,10 +89913,10 @@ The whole stack is split into four horizontal strata. Each layer can run on its└──────────────────────────────────────────────┘```-- **Viewer layer** — pure three.js. Knows nothing about agents, brains, or wallets. Useful on its own as a glTF inspector and as the rendering engine for Turntable / Animation Gallery widgets. See [Layers](#sec-398) for the contract.+- **Viewer layer** — pure three.js. Knows nothing about agents, brains, or wallets. Useful on its own as a glTF inspector and as the rendering engine for Turntable / Animation Gallery widgets. See [Layers](#sec-402) for the contract.- **Agent layer** — turns a static GLB into a presence. LLM tool-loop, skill registry, memory, and a continuous emotion blend that drives morphs and gaze. See [Agent system](#sec-068).-- **Identity layer** — durability across sessions, devices, and embed hosts. Wallet auth, on-chain registration, IPFS-pinned manifest bundles, signed action diary. Entirely optional. See [ERC-8004](#sec-263) and [Solana agents](#sec-657).-- **Embed layer**: the public face. The `<agent-3d>` custom element, ten widget variants, iframe embeds, the CDN bundle, the SPA, and the route table in `vercel.json` (read at runtime by the Cloud Run server). See [Embedding](#sec-259).+- **Identity layer** — durability across sessions, devices, and embed hosts. Wallet auth, on-chain registration, IPFS-pinned manifest bundles, signed action diary. Entirely optional. See [ERC-8004](#sec-266) and [Solana agents](#sec-665).+- **Embed layer**: the public face. The `<agent-3d>` custom element, ten widget variants, iframe embeds, the CDN bundle, the SPA, and the route table in `vercel.json` (read at runtime by the Cloud Run server). See [Embedding](#sec-262).The four layers communicate through one event bus (`agent-protocol`). Every meaningful action is a `CustomEvent` on a singleton. That single design choice is why you can swap the avatar for a 2D sprite, the runtime for a different LLM, or memory for a vector store — and nothing else changes.@@ -89627,7 +89949,7 @@ Three modes, all configurable per agent:| **Self-hosted proxy** | You want to manage cost or use a private model | Set `key-proxy="https://yourapp.com/api/llm"` to point at your own serverless function that injects keys before forwarding to the provider. Keys never reach the client. || **Direct (advanced)** | Local-only experiments | The runtime calls the provider directly if you pass an `api-key` attribute explicitly. Don't ship this to a public page. |-The platform's own chat surfaces run on the multi-model brain router at [`/api/brain/chat`](#sec-124), which supports Anthropic, OpenAI, and Qwen natively with OpenRouter failover; model ids include `claude-fable-5`, `claude-opus-5`, `claude-sonnet-5`, `claude-haiku-4-5`, `gpt-5.6-sol`, `gpt-5.6-terra`, `gpt-5.6-luna`, `qwen-plus`, and others.+The platform's own chat surfaces run on the multi-model brain router at [`/api/brain/chat`](#sec-125), which supports Anthropic, OpenAI, and Qwen natively with OpenRouter failover; model ids include `claude-fable-5`, `claude-opus-5`, `claude-sonnet-5`, `claude-haiku-4-5`, `gpt-5.6-sol`, `gpt-5.6-terra`, `gpt-5.6-luna`, `qwen-plus`, and others.---@@ -89635,8 +89957,8 @@ The platform's own chat surfaces run on the multi-model brain router at [`/api/bThree production paths. Pick whichever fits your use case:-- **Character Builder** — full-body character builder for stylised humanoids. Pick a base mesh, swap clothing/accessories/hairstyles, save. The output is a rigged GLB. See [character-studio.md](#sec-182).-- **Selfie capture** — upload a photo, get a rigged 3D version of yourself in ~60 seconds. See [avatar-creation.md](#sec-144).+- **Character Builder** — full-body character builder for stylised humanoids. Pick a base mesh, swap clothing/accessories/hairstyles, save. The output is a rigged GLB. See [character-studio.md](#sec-183).+- **Selfie capture** — upload a photo, get a rigged 3D version of yourself in ~60 seconds. See [avatar-creation.md](#sec-145).- **Upload your own** — any glTF 2.0 / GLB with a humanoid rig works. Drop the file into the editor at [three.ws/create](https://three.ws/create) or POST to `/api/avatars`.Every avatar ends up as a hosted GLB URL (served from the first-party asset CDN at `three.ws/cdn/<key>`) plus a database record. When you wire one into an agent, the agent's manifest references it under `body.uri`.@@ -89664,7 +89986,7 @@ On-chain identity is optional. Most agents work fine without it. You'd want it w- **You want delegated wallet permissions.** ERC-7710 lets you sign once per session and grant the agent scoped, time-bound permission to act on-chain — no per-transaction prompts.- **You want a portable address.** `agent://base/42` is a stable, resolver-agnostic URI. Any client that speaks the protocol can load it.-See [erc8004.md](#sec-263) and [solana.md](#sec-657) for the registration flows.+See [erc8004.md](#sec-266) and [solana.md](#sec-665) for the registration flows.---@@ -89674,7 +89996,7 @@ Three independent mechanisms, used as needed:- **x402** — pay-per-call USDC for paid API endpoints. Every paid endpoint declares itself in [`/.well-known/x402.json`](https://three.ws/.well-known/x402.json). Other agents (or humans with a wallet) can call paid endpoints with a single signed payment header.- **pump.fun** — launch a Solana SPL token tied to your agent. The platform handles the bonding curve, the token metadata, and the embed.-- **AWS Marketplace** — enterprise subscriptions billable through AWS. See [aws-marketplace.md](#sec-164). Subscriptions auto-issue an x402 API key via the marketplace entitlement service.+- **AWS Marketplace** — enterprise subscriptions billable through AWS. See [aws-marketplace.md](#sec-165). Subscriptions auto-issue an x402 API key via the marketplace entitlement service.You can mix these per agent. A common pattern: an agent has a free public persona on the platform, exposes one paid x402 skill for power users, and accepts donations via a pump.fun token.@@ -89687,27 +90009,27 @@ Quick lookup for "I want to ship X":| You want… | Reach for… ||---|---|| A 3D character on a marketing page | The CDN script + `<agent-3d>` |-| A character in Notion / Webflow / Framer | An iframe widget from [Widget Studio](#sec-801) |+| A character in Notion / Webflow / Framer | An iframe widget from [Widget Studio](#sec-813) || A talking AI sidekick that follows visitors | `<agent-3d mode="floating">` |-| A character that controls a scene from page events | The JS API (`agent.say()`, `agent.ask()`) — see [js-api.md](#sec-390) |+| A character that controls a scene from page events | The JS API (`agent.say()`, `agent.ask()`) — see [js-api.md](#sec-394) || Programmatic avatar viewing/creation in your own app | `@three-ws/avatar` |-| An on-chain identity for your AI | [ERC-8004](#sec-263) or [Solana](#sec-657) |-| A paid API anyone (including agents) can call | [x402 monetization](#sec-862) |-| Multiple agents in one scene | `<agent-stage>` — see [multi-agent.md](#sec-438) |-| To register a domain (e.g. ENS) as agent identity | [register-onchain.md tutorial](#sec-749) |+| An on-chain identity for your AI | [ERC-8004](#sec-266) or [Solana](#sec-665) |+| A paid API anyone (including agents) can call | [x402 monetization](#sec-877) |+| Multiple agents in one scene | `<agent-stage>` — see [multi-agent.md](#sec-442) |+| To register a domain (e.g. ENS) as agent identity | [register-onchain.md tutorial](#sec-757) |---## What's next-- **[Architecture overview](#sec-130)** — full internals+- **[Architecture overview](#sec-131)** — full internals- **[Agent system](#sec-068)** — runtime, skills, memory, emotion-- **[Layers](#sec-398)** — the four-layer contract in detail-- **[Quick start](#sec-593)** — go from zero to a living embed in under 10 minutes+- **[Layers](#sec-402)** — the four-layer contract in detail+- **[Quick start](#sec-600)** — go from zero to a living embed in under 10 minutes----<a id="sec-352"></a>+<a id="sec-356"></a>> **Source:** `docs/huggingface-3d-ai-agent-platform.md` · [↑ table of contents](#table-of-contents)@@ -89999,7 +90321,7 @@ Hugging Face is where model claims get checked, and the check is cheap: open the----<a id="sec-353"></a>+<a id="sec-357"></a>> **Source:** `docs/huggingface-agent-feedback-loop.md` · [↑ table of contents](#table-of-contents)@@ -90158,7 +90480,7 @@ Free to try, no account and no key: [three.ws/forge](https://three.ws/forge) for----<a id="sec-354"></a>+<a id="sec-358"></a>> **Source:** `docs/huggingface.md` · [↑ table of contents](#table-of-contents)@@ -90170,7 +90492,7 @@ This page is the index of that presence: what is published, where it lives, and- **Profile:** [huggingface.co/three-ws](https://huggingface.co/three-ws)- **Account:** organization account, byline "three.ws"-- **Related surfaces:** [the avatar pipeline](#sec-148), [the `<agent-3d>` web component](#sec-799), [agent wallets](#sec-077), [x402](#sec-140)+- **Related surfaces:** [the avatar pipeline](#sec-149), [the `<agent-3d>` web component](#sec-811), [agent wallets](#sec-077), [x402](#sec-141)## Published articles@@ -90183,7 +90505,7 @@ Published 13 July 2026 as a Hugging Face community article. It opens on the thesFour problems in order, each answered with a shipped surface: **the body problem** (text or a photo becomes a textured mesh, then a humanoid skeleton, then retargeted animation), **the world problem** (those bodies inhabit persistent multiplayer scenes instead of a single embed), **the wallet problem** (agents hold real keys and settle per call in USDC over HTTP 402), and **the brain problem** (an LLM that calls tools, holds memory, and drives expression on the mesh). It closes with a two-minute try-it path and the argument for why the four belong in one stack rather than four products.- **Surfaces it covers:** [/forge](https://three.ws/forge), [/play](https://three.ws/play), [/agents-live](https://three.ws/agents-live), [the x402 manifest](https://three.ws/.well-known/x402.json)-- **Code it documents:** [the avatar pipeline](#sec-148), [animation retargeting](#sec-101), [agent wallets](#sec-077), [autonomous x402](#sec-140)+- **Code it documents:** [the avatar pipeline](#sec-149), [animation retargeting](#sec-101), [agent wallets](#sec-077), [autonomous x402](#sec-141)### Inside three.ws: The Open-Source Stack That Gives AI Agents a Body, a Brain, a Wallet, and a Job@@ -90191,10 +90513,10 @@ Published 29 August 2026 as a Hugging Face community article. The whole stack in> [Read it on Hugging Face](https://huggingface.co/blog/three-ws/building-3d-ai-agents-end-to-end)-- **Source draft:** [`docs/huggingface-3d-ai-agent-platform.md`](#sec-352)+- **Source draft:** [`docs/huggingface-3d-ai-agent-platform.md`](#sec-356)- **Announcement thread:** [`marketing/huggingface-article/post.md`](../marketing/huggingface-article/post.md)- **Surfaces it covers:** [/forge](https://three.ws/forge), [/animations](https://three.ws/animations), [/brain](https://three.ws/brain), [/agent-studio](https://three.ws/agent-studio), [/irl](https://three.ws/irl), [/partners](https://three.ws/partners)-- **Code it documents:** [the avatar pipeline](#sec-148), [the 3D asset pipeline](#sec-002), [the agent brain](#sec-172), [the agent runtime](#sec-061), [the partner ecosystem](#sec-474)+- **Code it documents:** [the avatar pipeline](#sec-149), [the 3D asset pipeline](#sec-002), [the agent brain](#sec-173), [the agent runtime](#sec-061), [the partner ecosystem](#sec-480)## Published models@@ -90214,13 +90536,13 @@ Note that the files here are deliberately uncompressed. Everything three.ws serv> [Open the Space](https://huggingface.co/spaces/three-ws/avatar-viewer)-A running Space that loads the avatars above in an interactive 3D viewer, so a reader who arrives from the article can orbit a real rig without leaving Hugging Face or installing anything. The equivalent on our own domain is [the avatar inspector](#sec-147).+A running Space that loads the avatars above in an interactive 3D viewer, so a reader who arrives from the article can orbit a real rig without leaving Hugging Face or installing anything. The equivalent on our own domain is [the avatar inspector](#sec-148).## In draft| Draft | Subject ||---|---|-| [huggingface-agent-feedback-loop.md](#sec-353) | Closing the agentic-3D feedback loop: rendering results back into the model's own modality, a mechanical physics-readiness grade, structural glTF diffing, and retargeting with no rig allowlist |+| [huggingface-agent-feedback-loop.md](#sec-357) | Closing the agentic-3D feedback loop: rendering results back into the model's own modality, a mechanical physics-readiness grade, structural glTF diffing, and retargeting with no rig allowlist |Written to the same house rule as the two published articles: AI-focused, with no coin, exchange, or listing content anywhere in the piece.@@ -90239,11 +90561,11 @@ Hugging Face community articles accept Markdown, so a draft in `docs/` is the ar## Why we publish here-Hugging Face is where people go to check whether a model claim is real, and the check is cheap: open the repo, load the file, look at the rig. A marketing page says an avatar is animation-ready; a glTF with a named humanoid skeleton that plays a retargeted clip in the browser's own viewer proves it. Publishing the artifacts next to the article means a reader can verify the body problem is actually solved in the same sitting they read about it, then follow the same thread into [the wallet](#sec-077) and [the payments](#sec-140).+Hugging Face is where people go to check whether a model claim is real, and the check is cheap: open the repo, load the file, look at the rig. A marketing page says an avatar is animation-ready; a glTF with a named humanoid skeleton that plays a retargeted clip in the browser's own viewer proves it. Publishing the artifacts next to the article means a reader can verify the body problem is actually solved in the same sitting they read about it, then follow the same thread into [the wallet](#sec-077) and [the payments](#sec-141).----<a id="sec-355"></a>+<a id="sec-359"></a>> **Source:** `docs/i18n.md` · [↑ table of contents](#table-of-contents)@@ -90764,7 +91086,7 @@ clearing silently-English values out of a shipped catalog.----<a id="sec-356"></a>+<a id="sec-360"></a>> **Source:** `docs/ibm-community-any-skeleton-animation-post.md` · [↑ table of contents](#table-of-contents)@@ -91404,7 +91726,7 @@ _three.ws is an IBM Business Partner. The animation system described here is thr----<a id="sec-357"></a>+<a id="sec-361"></a>> **Source:** `docs/ibm-community-any-skeleton-animation-thread.md` · [↑ table of contents](#table-of-contents)@@ -91503,7 +91825,7 @@ _three.ws is an IBM Business Partner. The animation system described here is thr----<a id="sec-358"></a>+<a id="sec-362"></a>> **Source:** `docs/ibm-community-article.md` · [↑ table of contents](#table-of-contents)@@ -91623,7 +91945,7 @@ The platform repository is public at [github.com/nirholas/three.ws](https://gith----<a id="sec-359"></a>+<a id="sec-363"></a>> **Source:** `docs/ibm-community-blog-meetup-jessica.md` · [↑ table of contents](#table-of-contents)@@ -91684,7 +92006,7 @@ See you Friday at 8 AM Pacific. I will be the one asking the skeptical questions----<a id="sec-360"></a>+<a id="sec-364"></a>> **Source:** `docs/ibm-community-defi-3d-sperax-post.md` · [↑ table of contents](#table-of-contents)@@ -92154,14 +92476,14 @@ I will bring the harder questions from this thread back to the three.ws team, th----<a id="sec-361"></a>+<a id="sec-365"></a>> **Source:** `docs/ibm-community-defi-3d-sperax-publishing-kit.md` · [↑ table of contents](#table-of-contents)# Publishing kit: the Sperax integration post on IBM CommunityEverything the **Post to Blog** form asks for, in the order it asks. The article-itself is [ibm-community-defi-3d-sperax.md](#sec-362);+itself is [ibm-community-defi-3d-sperax.md](#sec-366);these are only the form values and the sequence that puts it live cleanly.Rebuild the three output files after any edit to the draft:@@ -92322,7 +92644,7 @@ embodied AI agents, 3D avatars, DeFi agents, decentralized finance, agent interf----<a id="sec-362"></a>+<a id="sec-366"></a>> **Source:** `docs/ibm-community-defi-3d-sperax.md` · [↑ table of contents](#table-of-contents)@@ -92871,7 +93193,7 @@ I will bring the harder questions from this thread back to the three.ws team, th----<a id="sec-363"></a>+<a id="sec-367"></a>> **Source:** `docs/ibm-community-doc-freshness-post.md` · [↑ table of contents](#table-of-contents)@@ -93611,7 +93933,7 @@ Run the section 11 script against your own repository and post your stale count----<a id="sec-364"></a>+<a id="sec-368"></a>> **Source:** `docs/ibm-community-doc-freshness-thread.md` · [↑ table of contents](#table-of-contents)@@ -93706,7 +94028,7 @@ _three.ws is an IBM Business Partner. The documentation freshness system describ----<a id="sec-365"></a>+<a id="sec-369"></a>> **Source:** `docs/ibm-community-governed-agents-post.md` · [↑ table of contents](#table-of-contents)@@ -94102,7 +94424,7 @@ The question I would most love this group to discuss: **how should a classifier----<a id="sec-366"></a>+<a id="sec-370"></a>> **Source:** `docs/ibm-community-governed-agents-thread.md` · [↑ table of contents](#table-of-contents)@@ -94147,7 +94469,7 @@ _three.ws is an IBM Business Partner. The `/api/ibm/*` and `/api/guardian/*` sur----<a id="sec-367"></a>+<a id="sec-371"></a>> **Source:** `docs/ibm-community-live-reaction-jessica.md` · [↑ table of contents](#table-of-contents)@@ -94158,7 +94480,7 @@ This is a discussion post for the [Three.ws User Group on IBMCommunity](https://community.ibm.com/community/user/usergroup?CommunityKey=e71510cc-d953-408f-9a1c-019f5c0a7016),not a polished announcement, just my honest reaction while the day is happening. My earlier post,[Join the Three.ws User Group's First In-World Meetup This-Friday](#sec-359), has the event details if you have not joined yet;+Friday](#sec-363), has the event details if you have not joined yet;the world is still open._I'm posting this in the middle of the day, not after, because I want the group to have my honest@@ -94199,7 +94521,7 @@ Full recap once the day wraps.follow-up, not a replacement for the original event post.- **Do not post an X/Twitter version of this.** This content is for the IBM Community group only;the group is the audience that gets the personal, honest register. The `@trythreews` and- `@nichxbt` X copy in [event-x-posts.md](#sec-823) is a separate, distinct campaign and+ `@nichxbt` X copy in [event-x-posts.md](#sec-837) is a separate, distinct campaign andstays in its organizer voice.- **Let Jessica edit freely.** This is a starting draft in her established voice (see the section"Why I think this format is worth your hour" in her earlier blog post), not a final script.@@ -94213,13 +94535,13 @@ Full recap once the day wraps.any mentions resolve correctly.- "Pilled" is her own word; keep it if it still feels true when she posts, or soften to "changed mymind about it" if she wants a more IBM-official register for her own profile.-- Once posted, add it to the catalog in [ibm-community.md](#sec-373) as a new discussion+- Once posted, add it to the catalog in [ibm-community.md](#sec-377) as a new discussionthread entry, following the same fields (author, posted date, activity, URL, summary) as theexisting entries, and note it links back to the pinned meetup thread.----<a id="sec-368"></a>+<a id="sec-372"></a>> **Source:** `docs/ibm-community-long-running-mcp-tools-post.md` · [↑ table of contents](#table-of-contents)@@ -95122,7 +95444,7 @@ _three.ws is an IBM Business Partner. The `/api/ibm/*` surfaces and the `@three-----<a id="sec-369"></a>+<a id="sec-373"></a>> **Source:** `docs/ibm-community-long-running-mcp-tools-thread.md` · [↑ table of contents](#table-of-contents)@@ -95208,7 +95530,7 @@ _three.ws is an IBM Business Partner. The `/api/ibm/*` surfaces and the open-sou----<a id="sec-370"></a>+<a id="sec-374"></a>> **Source:** `docs/ibm-community-recap-jessica.md` · [↑ table of contents](#table-of-contents)@@ -95217,8 +95539,8 @@ _three.ws is an IBM Business Partner. The `/api/ibm/*` surfaces and the open-sou_By Jessica Swanson, posted as a follow-up blog in the [Three.ws User Group on IBMCommunity](https://community.ibm.com/community/user/usergroup?CommunityKey=e71510cc-d953-408f-9a1c-019f5c0a7016),closing out the arc that started with [Join the Three.ws User Group's First In-World Meetup This-Friday](#sec-359) and continued mid-day with [LIVE at the Meetup: My-Honest Take So Far](#sec-367). Header image: reuse+Friday](#sec-363) and continued mid-day with [LIVE at the Meetup: My+Honest Take So Far](#sec-371). Header image: reuse[media/ibm-x-threews-lockup.png](media/ibm-x-threews-lockup.png), or swap in a real photo fromthe day once one is ready; do not paste this note into the published post._@@ -95347,14 +95669,14 @@ closest thing to having been there, and the world itself never closes.script; she should change anything that doesn't match how the day actually felt to her.- Confirm how Broke Boi and bigB actually go by on IBM Community today before posting, so anymentions or tags resolve correctly.-- Once posted, add it to the catalog in [ibm-community.md](#sec-373) as the group's next+- Once posted, add it to the catalog in [ibm-community.md](#sec-377) as the group's nextblog entry, following the same fields (author, published date, activity, URL, summary) as theexisting three entries, and cross-link it from the live-reaction catalog entry if that post waspublished too.----<a id="sec-371"></a>+<a id="sec-375"></a>> **Source:** `docs/ibm-community-recap-nichxbt.md` · [↑ table of contents](#table-of-contents)@@ -95363,7 +95685,7 @@ closest thing to having been there, and the world itself never closes._By nich (nich8), posted as a blog entry in the [Three.ws User Group on IBMCommunity](https://community.ibm.com/community/user/usergroup?CommunityKey=e71510cc-d953-408f-9a1c-019f5c0a7016),the team's own side of the meetup recap, alongside Jessica's [live-reaction](#sec-367) and [recap](#sec-370)+reaction](#sec-371) and [recap](#sec-374)on the same group. Two different people, two honest accounts of the same day; this one is mine,written the way I wrote the [Forge walkthrough](https://community.ibm.com/community/user/discussion/type-a-sentence-get-a-3d-model-a-hands-on-walkthrough-of-the-threews-forge-user-perspective)and the [10 features post](https://community.ibm.com/community/user/blogs/nich8/2026/07/16/threews-the-free-ai-3d-model-generators-10-best),@@ -95502,13 +95824,13 @@ than implying a date that does not exist yet.][ibm-user-group-first-in-world-meetup-recap.html](../blog/ibm-user-group-first-in-world-meetup-recap.html)is actually deployed, its link in this draft resolves live; until then it is a same-repo link thatworks once shipped, not before.-- Once posted, add it to the catalog in [ibm-community.md](#sec-373) as the group's next+- Once posted, add it to the catalog in [ibm-community.md](#sec-377) as the group's nextblog entry, following the same fields (author, published date, activity, URL, summary) as theexisting entries, and cross-link it against Jessica's recap entry.----<a id="sec-372"></a>+<a id="sec-376"></a>> **Source:** `docs/ibm-community-thread.md` · [↑ table of contents](#table-of-contents)@@ -95627,13 +95949,13 @@ _Questions, skepticism, and feature requests all welcome below. The skeptical on----<a id="sec-373"></a>+<a id="sec-377"></a>> **Source:** `docs/ibm-community.md` · [↑ table of contents](#table-of-contents)# IBM Community: Three.ws User Group post catalog-This is the running catalog of everything published in the [Three.ws User Group](https://community.ibm.com/community/user/groups/community-home?communitykey=e71510cc-d953-408f-9a1c-019f5c0a7016) on IBM Community: every discussion thread, every blog post, who wrote it, when, what it says, and what activity it got. It exists so the team can track the group's content without re-crawling the site. For what the group is, the framing rules that govern what gets posted there, and the wider IBM relationship, read [IBM watsonx & Granite](#sec-378) first.+This is the running catalog of everything published in the [Three.ws User Group](https://community.ibm.com/community/user/groups/community-home?communitykey=e71510cc-d953-408f-9a1c-019f5c0a7016) on IBM Community: every discussion thread, every blog post, who wrote it, when, what it says, and what activity it got. It exists so the team can track the group's content without re-crawling the site. For what the group is, the framing rules that govern what gets posted there, and the wider IBM relationship, read [IBM watsonx & Granite](#sec-382) first.Dates marked "approx." are derived from the site's relative timestamps ("17 days ago") on the snapshot date; blog dates come from their URLs and are exact.@@ -95684,7 +96006,7 @@ A feature tour structured as "ten features, in the order I would demo them": (1)- **Featured image:** the IBM x three.ws lockup ([media/ibm-x-threews-lockup.png](media/ibm-x-threews-lockup.png))- **URL:** [community.ibm.com/.../join-the-threews-user-groups-first-in-world-meetup](https://community.ibm.com/community/user/blogs/jessica-swanson/2026/08/04/join-the-threews-user-groups-first-in-world-meetup)-Jessica's companion piece to the meetup thread, written in her own voice as a member telling the group not to mistake the event for another webinar link. Carries the event table (Friday, August 7, 8 to 9 AM Pacific, 11 AM Eastern, free, browser only), the three-step join flow (open three.ws/play, bring a custom avatar made at three.ws/create beforehand, talk via spatial voice), and the agenda: live in-world platform tour, community demos, open Q&A ("the skeptical questions are the most useful ones"), and a first look at what is next. Her framing argument: the venue is the demo, so the hour doubles as hands-on evaluation of the technology the group exists to discuss, and since every world is a shareable URL, attending teaches you how to run your own events there. Points readers at the pinned meetup thread for the deep technical background and closes with the full platform link list. The draft lives in [ibm-community-blog-meetup-jessica.md](#sec-359).+Jessica's companion piece to the meetup thread, written in her own voice as a member telling the group not to mistake the event for another webinar link. Carries the event table (Friday, August 7, 8 to 9 AM Pacific, 11 AM Eastern, free, browser only), the three-step join flow (open three.ws/play, bring a custom avatar made at three.ws/create beforehand, talk via spatial voice), and the agenda: live in-world platform tour, community demos, open Q&A ("the skeptical questions are the most useful ones"), and a first look at what is next. Her framing argument: the venue is the demo, so the hour doubles as hands-on evaluation of the technology the group exists to discuss, and since every world is a shareable URL, attending teaches you how to run your own events there. Points readers at the pinned meetup thread for the deep technical background and closes with the full platform link list. The draft lives in [ibm-community-blog-meetup-jessica.md](#sec-363).### 4. The First Three.ws User Group Meetup: How It Actually Went@@ -95738,7 +96060,7 @@ boxes, static chatbot interfaces, and single-turn query responses, and that thenext phase is something else. Open the post, then replace this entry with thesame fields the four above carry (author, exact date, activity, URL, faithfulsummary). Note for whoever does: the title names IBM alongside three.ws and a-university, so check it against the framing rules in [ibm.md](#sec-378) and flag+university, so check it against the framing rules in [ibm.md](#sec-382) and flaganything that reads as an IBM partnership deliverable.### 7. When an agent can open your front door, governance stops being paperwork@@ -95748,7 +96070,7 @@ anything that reads as an IBM partnership deliverable.- **Activity:** 0 comments at posting- **URL:** [community.ibm.com/.../when-an-agent-can-open-your-front-door-governance](https://community.ibm.com/community/user/blogs/10058/2026/09/18/when-an-agent-can-open-your-front-door-governance)-The quarter's long technical write-up. Argues that once agents can act on a house through Home Assistant, ride in a car, and order a manufactured object, a system prompt is not a control, and shows the policy layer that is: Granite Guardian (`ibm/granite-guardian-3-8b` on watsonx.ai) as an allow / review / block veto on proposed actions, a per-period spend cap behind the same gate, a SHA-256 hash-chained verdict ledger anyone can re-verify, and a `503` instead of a fabricated verdict when watsonx is unconfigured. Then the Home Assistant gate that refuses physical actions outright over stdio MCP, the five-role household model enforced server-side, the full watsonx.ai endpoint map with runnable `curl`s, a five-step build-it-yourself walkthrough, the quarter's other ships, a note on metering Granite for callers with no IBM Cloud account, and an invitation to shape the group's second event. The draft lives in [ibm-community-governed-agents-post.md](#sec-365); its companion discussion thread is drafted in [ibm-community-governed-agents-thread.md](#sec-366).+The quarter's long technical write-up. Argues that once agents can act on a house through Home Assistant, ride in a car, and order a manufactured object, a system prompt is not a control, and shows the policy layer that is: Granite Guardian (`ibm/granite-guardian-3-8b` on watsonx.ai) as an allow / review / block veto on proposed actions, a per-period spend cap behind the same gate, a SHA-256 hash-chained verdict ledger anyone can re-verify, and a `503` instead of a fabricated verdict when watsonx is unconfigured. Then the Home Assistant gate that refuses physical actions outright over stdio MCP, the five-role household model enforced server-side, the full watsonx.ai endpoint map with runnable `curl`s, a five-step build-it-yourself walkthrough, the quarter's other ships, a note on metering Granite for callers with no IBM Cloud account, and an invitation to shape the group's second event. The draft lives in [ibm-community-governed-agents-post.md](#sec-369); its companion discussion thread is drafted in [ibm-community-governed-agents-thread.md](#sec-370).## Discussion threads@@ -95761,7 +96083,7 @@ Newest first, matching the digest viewer's order.- **Activity:** 1 reply (Jessica Swanson, whose profile lists Operational Decision Manager, AI & Data Science at IBM, 2026-08-05: links her blog post "Join the Three.ws User Group's First In-World Meetup")- **URL:** [community.ibm.com/.../community-meetup-inside-threews-join-us-on-the-three-server-at-threewsplay](https://community.ibm.com/community/user/discussion/community-meetup-inside-threews-join-us-on-the-three-server-at-threewsplay)-The announcement for the group's first community meetup: Friday, August 7, 2026, 8 to 9 AM Pacific (11 AM Eastern), held inside the platform itself in the $THREE home town at three.ws/play rather than on a video call. Free, browser-only, no download or account. Agenda: a live tour from inside the world, community demos, open Q&A, and a first look at what is next. Explains the three-step join flow (open /play, pick or bring an avatar, walk up and talk via spatial voice chat), then makes the venue case: every world is a URL, every pump.fun coin already has a world derived from its mint, and worlds persist, so any community can run its own meetup the same way. The back half is the long read: a surface-by-surface platform tour (creation, distribution, agent economy, developer platform including the two IBM-specific MCP servers), the technology stack (Three.js/Rapier frontend, GPU worker fleet on Cloud Run, authoritative Colyseus multiplayer at 15 Hz, Solana as home chain), the roadmap led by event infrastructure for /play, and a seven-point growth thesis explicitly framed as a thesis, not a promise. The draft lives in [ibm-community-thread.md](#sec-372).+The announcement for the group's first community meetup: Friday, August 7, 2026, 8 to 9 AM Pacific (11 AM Eastern), held inside the platform itself in the $THREE home town at three.ws/play rather than on a video call. Free, browser-only, no download or account. Agenda: a live tour from inside the world, community demos, open Q&A, and a first look at what is next. Explains the three-step join flow (open /play, pick or bring an avatar, walk up and talk via spatial voice chat), then makes the venue case: every world is a URL, every pump.fun coin already has a world derived from its mint, and worlds persist, so any community can run its own meetup the same way. The back half is the long read: a surface-by-surface platform tour (creation, distribution, agent economy, developer platform including the two IBM-specific MCP servers), the technology stack (Three.js/Rapier frontend, GPU worker fleet on Cloud Run, authoritative Colyseus multiplayer at 15 Hz, Solana as home chain), the roadmap led by event infrastructure for /play, and a seven-point growth thesis explicitly framed as a thesis, not a promise. The draft lives in [ibm-community-thread.md](#sec-376).### 2. Community Friday August 7,2026 - Inside three.ws: Join Us on the $THREE Server at three.ws/play@@ -95832,26 +96154,26 @@ A first-run walkthrough of the Forge from a user's perspective, no account, wall| Draft | Subject ||---|---|-| [ibm-community-governed-agents-thread.md](#sec-366) | Short companion thread for blog post 7: the four governance decisions in bullets, one runnable Granite Guardian `curl`, and an open question to the group on how they gate agent actions |-| [ibm-community-any-skeleton-animation-post.md](#sec-356) | Long engineer-facing tutorial on playing one pre-baked clip library (113 curated clips, 3,343 in the full library) on any humanoid rig with no allowlist: bone-name normalization (736 spellings onto 52 canonical joints), the clavicle collision resolved by hierarchy, measured proof that copying rotations fails, the world-delta retarget `q' = L*q*R` derived step by step, the A-pose limb re-aim with before/after tables on six public avatars, hips, units, legs, generated motion as a rest-basis problem, the gates and fallbacks, how "any skeleton" is tested, a standalone three.js implementation verified against production to 0.1 degree, known failure cases, and three questions for the group. IBM appears only in the affiliation line; no crypto content |-| [ibm-community-any-skeleton-animation-thread.md](#sec-357) | Self-contained discussion companion: the three ways rigs differ, the `L*q*R` correction with a runnable 20-line snippet and its real output, five lessons, and three questions (names or geometry, where IK belongs, how to validate generated motion). Add the blog URL once the post is live |-| [ibm-community-long-running-mcp-tools-post.md](#sec-368) | Long tutorial on MCP tools whose work outlives the host's timeout, using the free 3D Studio server as the worked example: ten patterns (pending results with a signed job handle, `check_job` as a first-class collector, call budgets, submit tickets, polling guidance in tool text, interface-side collection, `structuredContent` as the contract, verified annotations, tiers and refinement, searching the catalog before generating), each with real code, dated history and live JSON-RPC pairs captured 2026-10-08; plus splitting keyless tools from authenticated ones, resources and guided prompts, a checklist table, a runnable 150-line Node server, and IBM's documented remote-MCP toolkit path for watsonx Orchestrate (quoted, untested by us, no listing claimed) |-| [ibm-community-long-running-mcp-tools-thread.md](#sec-369) | Self-contained discussion companion: the job-handle pattern with one runnable `curl` pair against the live server, eight lessons, and three questions on how members handle slow tools across MCP hosts. Add the blog URL once the post is live |-| [ibm-community-doc-freshness-post.md](#sec-363) | Long tutorial for IBM developers and platform teams on documentation drift detection from git history, framed by coding agents now executing docs as instructions: binding each doc to the files, scripts and routes it names, the five statuses, review stamps tied to a commit, dated records that are never rewritten, the agent-run sweep, why `docs:freshness` runs before the frontend build, the reader badge, ten weeks of measured history, a tested zero-dependency Node script, `audit:docs` and `check:claude`, and eight honest limits including the README-coverage guard that went silent after a rewording (found while writing the post and fixed the same day). No IBM involvement in the feature; no crypto content. Numbers are dated: re-run `npm run check:docs-freshness` before posting |-| [ibm-community-doc-freshness-thread.md](#sec-364) | Self-contained discussion companion: why stale docs now cost more, the git-history signal with one runnable shell snippet, concrete lessons including the self-skipping guard, and questions on how members keep agent instruction files true. Add the blog URL once the post is live |-| [ibm-community-defi-3d-sperax.md](#sec-362) | Written for Jessica to publish in her own voice. Section 0 answers "why is an IBM employee writing about two crypto companies" as her own practitioner case (her field is decision integrity, this is the best material on it she has read) rather than as IBM partnership strategy, which she does not own. Then the triangle of three relationships (Sperax with three.ws, both as IBM Business Partners, and the three.ws runtime on Granite through watsonx.ai) split as body / DeFi domain / brain, with an explicit subsection denying that IBM commissioned or endorsed the integration itself, and framed through her decision-management day job. Section 1 makes DeFi a real subject rather than a backdrop (the four properties that break a chat box, the tool catalog, the approve-before-acting execution model): the two ways to embed an embodied agent in a host application (standalone manifest vs native component), the continuous emotion blend that replaced a state machine, why grounding the avatar in verified reads mattered more than the rendering, honest failure when a probe is bot-challenged, the hash-chained action ledger, the code that moved in both directions, what is planned, and AR flagged as the next surface rather than a shipped one. Carries four diagrams rendered by [scripts/render-ibm-sperax-diagrams.mjs](../scripts/render-ibm-sperax-diagrams.mjs) into [media/](media), plus [ibm-community-defi-3d-sperax-post.md](#sec-360) and its styled `-post.html` twin, both generated by [scripts/build-ibm-community-post.mjs](../scripts/build-ibm-community-post.mjs) with the frontmatter and editor notes stripped. Edit the draft, never the generated trio. Form values, the permalink slug, the meta description, and the image-placement sequence are in [ibm-community-defi-3d-sperax-publishing-kit.md](#sec-361). **Open question before posting:** the draft states that Sperax is also an IBM Business Partner, which came from the owner and is not evidenced anywhere in this repo; confirm the wording Sperax uses for its own partner status first |+| [ibm-community-governed-agents-thread.md](#sec-370) | Short companion thread for blog post 7: the four governance decisions in bullets, one runnable Granite Guardian `curl`, and an open question to the group on how they gate agent actions |+| [ibm-community-any-skeleton-animation-post.md](#sec-360) | Long engineer-facing tutorial on playing one pre-baked clip library (113 curated clips, 3,343 in the full library) on any humanoid rig with no allowlist: bone-name normalization (736 spellings onto 52 canonical joints), the clavicle collision resolved by hierarchy, measured proof that copying rotations fails, the world-delta retarget `q' = L*q*R` derived step by step, the A-pose limb re-aim with before/after tables on six public avatars, hips, units, legs, generated motion as a rest-basis problem, the gates and fallbacks, how "any skeleton" is tested, a standalone three.js implementation verified against production to 0.1 degree, known failure cases, and three questions for the group. IBM appears only in the affiliation line; no crypto content |+| [ibm-community-any-skeleton-animation-thread.md](#sec-361) | Self-contained discussion companion: the three ways rigs differ, the `L*q*R` correction with a runnable 20-line snippet and its real output, five lessons, and three questions (names or geometry, where IK belongs, how to validate generated motion). Add the blog URL once the post is live |+| [ibm-community-long-running-mcp-tools-post.md](#sec-372) | Long tutorial on MCP tools whose work outlives the host's timeout, using the free 3D Studio server as the worked example: ten patterns (pending results with a signed job handle, `check_job` as a first-class collector, call budgets, submit tickets, polling guidance in tool text, interface-side collection, `structuredContent` as the contract, verified annotations, tiers and refinement, searching the catalog before generating), each with real code, dated history and live JSON-RPC pairs captured 2026-10-08; plus splitting keyless tools from authenticated ones, resources and guided prompts, a checklist table, a runnable 150-line Node server, and IBM's documented remote-MCP toolkit path for watsonx Orchestrate (quoted, untested by us, no listing claimed) |+| [ibm-community-long-running-mcp-tools-thread.md](#sec-373) | Self-contained discussion companion: the job-handle pattern with one runnable `curl` pair against the live server, eight lessons, and three questions on how members handle slow tools across MCP hosts. Add the blog URL once the post is live |+| [ibm-community-doc-freshness-post.md](#sec-367) | Long tutorial for IBM developers and platform teams on documentation drift detection from git history, framed by coding agents now executing docs as instructions: binding each doc to the files, scripts and routes it names, the five statuses, review stamps tied to a commit, dated records that are never rewritten, the agent-run sweep, why `docs:freshness` runs before the frontend build, the reader badge, ten weeks of measured history, a tested zero-dependency Node script, `audit:docs` and `check:claude`, and eight honest limits including the README-coverage guard that went silent after a rewording (found while writing the post and fixed the same day). No IBM involvement in the feature; no crypto content. Numbers are dated: re-run `npm run check:docs-freshness` before posting |+| [ibm-community-doc-freshness-thread.md](#sec-368) | Self-contained discussion companion: why stale docs now cost more, the git-history signal with one runnable shell snippet, concrete lessons including the self-skipping guard, and questions on how members keep agent instruction files true. Add the blog URL once the post is live |+| [ibm-community-defi-3d-sperax.md](#sec-366) | Written for Jessica to publish in her own voice. Section 0 answers "why is an IBM employee writing about two crypto companies" as her own practitioner case (her field is decision integrity, this is the best material on it she has read) rather than as IBM partnership strategy, which she does not own. Then the triangle of three relationships (Sperax with three.ws, both as IBM Business Partners, and the three.ws runtime on Granite through watsonx.ai) split as body / DeFi domain / brain, with an explicit subsection denying that IBM commissioned or endorsed the integration itself, and framed through her decision-management day job. Section 1 makes DeFi a real subject rather than a backdrop (the four properties that break a chat box, the tool catalog, the approve-before-acting execution model): the two ways to embed an embodied agent in a host application (standalone manifest vs native component), the continuous emotion blend that replaced a state machine, why grounding the avatar in verified reads mattered more than the rendering, honest failure when a probe is bot-challenged, the hash-chained action ledger, the code that moved in both directions, what is planned, and AR flagged as the next surface rather than a shipped one. Carries four diagrams rendered by [scripts/render-ibm-sperax-diagrams.mjs](../scripts/render-ibm-sperax-diagrams.mjs) into [media/](media), plus [ibm-community-defi-3d-sperax-post.md](#sec-364) and its styled `-post.html` twin, both generated by [scripts/build-ibm-community-post.mjs](../scripts/build-ibm-community-post.mjs) with the frontmatter and editor notes stripped. Edit the draft, never the generated trio. Form values, the permalink slug, the meta description, and the image-placement sequence are in [ibm-community-defi-3d-sperax-publishing-kit.md](#sec-365). **Open question before posting:** the draft states that Sperax is also an IBM Business Partner, which came from the owner and is not evidenced anywhere in this repo; confirm the wording Sperax uses for its own partner status first |All three long posts use the carbon featured card with `&f=group`, whose footer reads "Three.ws User Group" instead of "Built on IBM watsonx.ai" (that line is only true of watsonx content). The parameter needs the deploy that carries it; confirm the live card before posting. Space the three posts a week apart per the cadence rule, each with its companion thread the same day.-The drafts carry the framing rules from [ibm.md](#sec-378) in their frontmatter, including which section to cut first if the group's no-crypto-cluster rule is applied strictly.+The drafts carry the framing rules from [ibm.md](#sec-382) in their frontmatter, including which section to cut first if the group's no-crypto-cluster rule is applied strictly.## Keeping this catalog current-When a new post lands in the group, add it here in digest order with the same fields (author, date, activity, URL, faithful summary) and refresh the snapshot table's date and counts. The sources of truth are the [digest viewer](https://community.ibm.com/community/user/groups/community-home/digestviewer?communitykey=e71510cc-d953-408f-9a1c-019f5c0a7016) for threads and the [recent blogs page](https://community.ibm.com/community/user/groups/community-home/recent-community-blogs?communitykey=e71510cc-d953-408f-9a1c-019f5c0a7016) for blogs. The posting cadence and topic rules for the group itself live in the [SEO keyword plan](ops/seo-keyword-plan.md) and in [ibm.md](#sec-378).+When a new post lands in the group, add it here in digest order with the same fields (author, date, activity, URL, faithful summary) and refresh the snapshot table's date and counts. The sources of truth are the [digest viewer](https://community.ibm.com/community/user/groups/community-home/digestviewer?communitykey=e71510cc-d953-408f-9a1c-019f5c0a7016) for threads and the [recent blogs page](https://community.ibm.com/community/user/groups/community-home/recent-community-blogs?communitykey=e71510cc-d953-408f-9a1c-019f5c0a7016) for blogs. The posting cadence and topic rules for the group itself live in the [SEO keyword plan](ops/seo-keyword-plan.md) and in [ibm.md](#sec-382).----<a id="sec-374"></a>+<a id="sec-378"></a>> **Source:** `docs/ibm-event-offer-map.md` · [↑ table of contents](#table-of-contents)@@ -95864,7 +96186,7 @@ audience would show up for, and which of it works today.It sits beside two existing documents and does not replace them:-- [ibm-next-event.md](#sec-375) argues for one headline format (the Forge-Off Open)+- [ibm-next-event.md](#sec-379) argues for one headline format (the Forge-Off Open)and carries a 12-idea bank.- [marketing/growth/events/ibm-event-two.md](../marketing/growth/events/ibm-event-two.md) isthe paste-ready kit for a one-hour in-world session, and@@ -95872,7 +96194,7 @@ It sits beside two existing documents and does not replace them:template.Every status below was checked against the code or the live site on 2026-09-18. Anything-IBM-facing that comes out of this document is read against [ibm.md](#sec-378) and+IBM-facing that comes out of this document is read against [ibm.md](#sec-382) and[badge-usage.md](../marketing/ibm-partner-plus/badge-usage.md) before it ships.---@@ -95983,7 +96305,7 @@ fireworks, the countdown chip and agenda drawer, and a free event-tier souvenirserver-side to everyone present.Specified but not built (each has a prompt pack in-[event-readiness/](#sec-292)): a welcome concierge NPC, a hype ticker,+[event-readiness/](#sec-295)): a welcome concierge NPC, a hype ticker,an in-world invite sheet with QR, chat scrollback for late joiners, parties, a projector orspectator mode, a signature wall, and judged dance-off rounds. A live event-config overrideis also unbuilt, so changing the window means a deploy.@@ -96028,7 +96350,7 @@ These fit IBM Community's event tooling directly and need nothing from the world| # | Format | Shape | Ready || --- | --- | --- | --- |-| 17 | **The Forge-Off Open** | One week, five daily themes, no-login entry and voting, crowned in-world. Full case in [ibm-next-event.md](#sec-375) | Needs a landing page and theme copy. The pitch must say the entry screen is an NVIDIA classifier, not Granite Guardian |+| 17 | **The Forge-Off Open** | One week, five daily themes, no-login entry and voting, crowned in-world. Full case in [ibm-next-event.md](#sec-379) | Needs a landing page and theme copy. The pitch must say the entry screen is an NVIDIA classifier, not Granite Guardian || 18 | **30-Day Forge Streak** | `/daily` wrapped in a leaderboard and weekly prizes | Nearly free || 19 | **Sign Week** | A letter a day on `/sign-mirror`, closing with a fingerspelled relay in the world | Surfaces ready. Requires deaf collaborators before it is announced, and must be framed as fingerspelling, one narrow slice of ASL || 20 | **Mascot Week** | Companies submit a mascot or logo and get back a rigged, talking agent with a one-line embed. Published as a gallery | Ready. The only format that produces embeds on other companies' sites |@@ -96076,7 +96398,7 @@ single message.| A partner-authored recap on an IBM surface | We supply the recording, screenshots and captured numbers within 24 hours | Part of the event ask || A mascot and an in-world home for the user group | `/agent-identities` builds the character, `/crews` gives the group an HQ, `/three` lists branded worlds | Owner decision || A souvenir per event | The grant path is server-side and idempotent. Souvenir one was never granted because the world server was on an old build | Redeploy the multiplayer service before every event |-| My Digital Marketing, the Build track Partner Marketing Kit, co-marketing funding, digital badging | Entitled and never requested, per [ibm-partner-plus.md](#sec-477) | One request |+| My Digital Marketing, the Build track Partner Marketing Kit, co-marketing funding, digital badging | Entitled and never requested, per [ibm-partner-plus.md](#sec-483) | One request || IBM Champions self-nomination | Packet written in `marketing/partner-packets/ibm-champions-nomination.md`, waiting on three facts only the nominee can supply. Treat 2026-11-20 as the latest safe date | Owner || The two June commitments still open | More co-promotion from IBM, and a page on the IBM domain | The same email as the event date |@@ -96109,7 +96431,7 @@ that does the thing being discussed.1. **Tell IBM.** The date lives only in this repo. Create the event in the IBM Communitygroup and send the relationship note. The same message carries the five standing asks- listed in [ibm-visibility-map.md](#sec-376).+ listed in [ibm-visibility-map.md](#sec-380).2. **Deploy.** The event config and the souvenir are committed and not live. Themultiplayer service needs its own redeploy, or souvenir two repeats souvenir one. Thenrun `node scripts/play-souvenir-conformance.mjs` and `npm run audit:meetup`.@@ -96126,7 +96448,7 @@ that does the thing being discussed.announce script open in a terminal.7. **Capture the numbers.** Start `npm run event:watch -- --interval 15` before doors andkeep the log. It is the only source for a headcount.-8. **Refresh the runbook.** [event-readiness/LIVE-OPS.md](#sec-291)+8. **Refresh the runbook.** [event-readiness/LIVE-OPS.md](#sec-294)still carries the first meetup's release SHA and revisions.Worth building before the October session, smallest first: chat scrollback for late@@ -96135,7 +96457,7 @@ plaza stage, and a projector mode for a physical room.----<a id="sec-375"></a>+<a id="sec-379"></a>> **Source:** `docs/ibm-next-event.md` · [↑ table of contents](#table-of-contents)@@ -96145,7 +96467,7 @@ The first one is done. On 2026-06-23 three.ws ran **Building 3D AI Agents Live:Prompt to Embeddable Agent in Minutes** in IBM's Global AI & Data Science community: aone-hour live-build webinar with an IBM guest, ending in a Q&A. It worked, and it set theceiling. Details and the framing rules that govern anything IBM-facing are in-[ibm.md](#sec-378).+[ibm.md](#sec-382).This document is the proposal for the second one. It exists so the conversation with IBMstarts from a concrete run of show rather than a format debate, and so the engineering work@@ -96160,7 +96482,7 @@ NVIDIA NemoGuard classifier, not Granite Guardian, so the responsible-AI argumenno longer matches the code.**The full inventory of what the platform can offer an IBM audience**, with each surface's-verified state and a 27-format menu, is [ibm-event-offer-map.md](#sec-374).+verified state and a 27-format menu, is [ibm-event-offer-map.md](#sec-378).**The goal is not another audience. It is usage.** A webinar is measured in registrationsand a recording. This event is measured in how many people typed something into three.ws@@ -96188,13 +96510,13 @@ event format that needs six weeks of new engineering is a format that slips.| **Voting with no login**: one upvote per browser per creation, idempotent, rate limited, tallied authoritatively | `api/forge-vote.js`, `api/_lib/rate-limit.js` | Shipped || Weekly winners crowned and auto-distributed to the official Sketchfab account with backlinks and UTM attribution | `forge_board_winners`, `api/cron/sketchfab-showcase.js` | Shipped || Safety gate that makes a public, no-login contest survivable: brand denylist in the selection SQL plus a classifier layer before anything is shown | `api/cron/sketchfab-showcase.js`, `publish-safety.js`, Granite Guardian in `api/_lib/granite-guardian.js` | Shipped |-| Scheduled live events inside the 3D world: countdown chip, agenda drawer, go-live banners, synchronized fireworks, all from one config file | `public/event.json`, [play-live-events.md](#sec-497) | Shipped |-| Free commemorative wearable granted to everyone present during a live event, never purchasable afterwards | [event-souvenirs.md](#sec-293) | Shipped |+| Scheduled live events inside the 3D world: countdown chip, agenda drawer, go-live banners, synchronized fireworks, all from one config file | `public/event.json`, [play-live-events.md](#sec-504) | Shipped |+| Free commemorative wearable granted to everyone present during a live event, never purchasable afterwards | [event-souvenirs.md](#sec-296) | Shipped || Public event landing page with countdown, run of show in the visitor's timezone, add-to-calendar, live presence | `/event`, `src/event-page.js` | Shipped || Realtime multiplayer worlds: movement, chat, spatial voice, a plaza-sized crowd | [`multiplayer/`](../multiplayer/README.md) | Shipped || Living Stages: an embodied AI host performing in a 3D venue, reading the room and taking questions | `/stage` | Shipped || Text prompt to rigged, animated, embeddable 3D agent | `/create`, the Forge | Shipped |-| AR: place a 3D agent in a real room, visible only to people physically near it | `/irl`, [irl.md](#sec-386) | Shipped |+| AR: place a 3D agent in a real room, visible only to people physically near it | `/irl`, [irl.md](#sec-390) | Shipped || IBM Granite on watsonx.ai as the agent brain, plus Granite with no IBM account over x402 | `/api/ibm-mcp`, `@three-ws/ibm-watsonx-mcp` | Shipped || Immersive VR (`immersive-vr`) walk-in to the multiplayer world on a headset | not present: `src/xr.js` and `src/ar/webxr.js` are `immersive-ar` only | **Would be new work** |@@ -96349,7 +96671,7 @@ losing fine.### Framing rules that apply to every word of this-The distinctions in [ibm.md](#sec-378) hold without exception. The public Granite showcase is+The distinctions in [ibm.md](#sec-382) hold without exception. The public Granite showcase iscommunity-built, not an IBM product, not endorsed by IBM, and not a partnership deliverable.This is an event hosted by three.ws in IBM's community with IBM's participation. It is not"an IBM hackathon", and no promotional copy may upgrade it into one. Copy for the event@@ -96370,7 +96692,7 @@ Ordered so the event is runnable even if the last item never lands.2. **Daily theme copy and the drop schedule**, written once and read by the page, so atheme going live needs no deploy.3. **Ceremony config**: write the window, the agenda and the souvenir cosmetic id into- `public/event.json` per [play-live-events.md](#sec-497). A config change+ `public/event.json` per [play-live-events.md](#sec-504). A config changeplus a deploy, and that is the entire in-world event.4. **A daily crowning read** over the existing board so the evening winner is a query, not aperson scrolling. The weekly crowning already exists; this is the same window narrowed to@@ -96597,23 +96919,23 @@ copied by a competitor with a text box.----<a id="sec-376"></a>+<a id="sec-380"></a>> **Source:** `docs/ibm-visibility-map.md` · [↑ table of contents](#table-of-contents)# IBM visibility map: every surface, and how to get on itIBM is the deepest big-tech relationship three.ws holds, and it is the only one-with no map. NVIDIA has [nvidia-visibility-map.md](#sec-454),-OpenAI has [openai-listing-channels.md](#sec-464), AWS has-[aws-marketplace-listing-kit.md](#sec-163) and-[aws-builder-center.md](#sec-162). The IBM docs in this folder are+with no map. NVIDIA has [nvidia-visibility-map.md](#sec-458),+OpenAI has [openai-listing-channels.md](#sec-469), AWS has+[aws-marketplace-listing-kit.md](#sec-164) and+[aws-builder-center.md](#sec-163). The IBM docs in this folder areall content docs: what we published, what we might publish next. None of theminventories the surfaces we could be on, or the Partner Plus benefits an IBMBusiness Partner is entitled to and has never asked for. That is what this is.**Scope, so this does not overlap its companion.**-[partners/ibm-partner-plus.md](#sec-477) is the audit of the+[partners/ibm-partner-plus.md](#sec-483) is the audit of the*program*: which Partner Plus benefits we hold unused, the September newslettertriaged item by item, My Digital Marketing, and the watsonx Orchestrate AgentCatalog listing through IBM Agent Connect, which is the single highest-value IBM@@ -96622,7 +96944,7 @@ the *surfaces*: the public places three.ws can appear, the verified intake routefor each, and the time-gated windows. Read that one for what we are owed, thisone for where we can show up.-Read [ibm.md](#sec-378) before either. Its framing rules bind every item here,+Read [ibm.md](#sec-382) before either. Its framing rules bind every item here,and the one that matters most in outreach: the public `/api/ibm/*` showcase is acommunity-built playground, not a partnership deliverable, not an IBM product,and not endorsed by IBM. Never pitch it as the partnership.@@ -96640,7 +96962,7 @@ Strategic Partner spotlight, the open-platform blog, the User Group launch, andtwo more. IBM staff wrote those. Meanwhile the last post in our own[Three.ws User Group](https://community.ibm.com/community/user/groups/community-home?communitykey=e71510cc-d953-408f-9a1c-019f5c0a7016)landed 2026-08-08, against a cadence allowance of one post per week, and a-finished post ([ibm-community-governed-agents-post.md](#sec-365))+finished post ([ibm-community-governed-agents-post.md](#sec-369))has been sitting unposted since it was written. The one IBM channel that isentirely self-serve, on IBM's domain, with an audience already assembled for us,is running at roughly a quarter of its allowed rate.@@ -96648,7 +96970,7 @@ is running at roughly a quarter of its allowed rate.**2. Two co-marketing commitments from 2026-06-18 are still open.** Moreco-promotion on X from IBM, and a dedicated three.ws page on the IBM domain. Thethird, a live community event, happened. The status of all three is tracked in-[partners/ibm-partner-plus.md](#sec-477); they are repeated+[partners/ibm-partner-plus.md](#sec-483); they are repeatedhere only because every ask below travels in the same message as those two.**3. IBM Champions is the only annual window on this page, and it opens about@@ -96668,9 +96990,9 @@ last twelve months, and has never entered. See| 1 | **Our own IBM User Group** | We moderate it | The drafted post is written. Posting is the whole task. Self-serve, on `community.ibm.com`, indexed. || 2 | **IBM Champions nomination** | [ibm.com/community/champions-program](https://www.ibm.com/community/champions-program/) | Self-nomination allowed, window opens around mid-September, and our advocacy record already matches IBM's published criteria. || 3 | **The two unfulfilled co-marketing commitments** | The IBM marketing contact from the 2026-06-15 and 2026-06-18 meetings | Already agreed. This is a follow-up, not a new ask. |-| 4 | **A date for the second community event** | Same thread | [ibm-next-event.md](#sec-375) is a finished proposal waiting on one decision. IBM said it is ready to host. |+| 4 | **A date for the second community event** | Same thread | [ibm-next-event.md](#sec-379) is a finished proposal waiting on one decision. IBM said it is ready to host. || 5 | **Partner Plus Directory profile** | [ibm.com/partnerplus/directory](https://www.ibm.com/partnerplus/directory) (resolves to `/directory/companies`) | IBM's public search portal for Business Partner solutions. Confirm whether our profile is published and complete. |-| 6 | **Agent Connect / watsonx Orchestrate Agent Catalog** | `[email protected]` for the `APP_ID` | The highest-value IBM listing route, and our live MCP server plus x402 licensing already satisfies the BYOL prerequisites. Fully specified in [partners/ibm-partner-plus.md](#sec-477); listed here so the surface map is complete. |+| 6 | **Agent Connect / watsonx Orchestrate Agent Catalog** | `[email protected]` for the `APP_ID` | The highest-value IBM listing route, and our live MCP server plus x402 licensing already satisfies the BYOL prerequisites. Fully specified in [partners/ibm-partner-plus.md](#sec-483); listed here so the surface map is complete. |### IBM Champions: the one annual window@@ -96687,9 +97009,9 @@ last twelve months and all on IBM properties:| IBM's criterion | Our record ||---|---|| Speaking at conferences and events | Building 3D AI Agents Live, IBM Global AI and Data Science community, held 2026-06-23 with an IBM guest |-| Supporting user groups and community | We run the Three.ws User Group on IBM Community: 4 blog posts, 8 discussion threads, 2 library entries at the 2026-08-13 snapshot ([ibm-community.md](#sec-373)) |-| Creating articles, videos, and other spotlights | The IBM Community blog post recorded as Live in [listings.md](#sec-403), plus the group's tutorial threads |-| Providing product feedback to IBM development teams | Granite and watsonx.ai are wired into production surfaces documented in [ibm.md](#sec-378); the feedback exists, it has never been routed to IBM as feedback |+| Supporting user groups and community | We run the Three.ws User Group on IBM Community: 4 blog posts, 8 discussion threads, 2 library entries at the 2026-08-13 snapshot ([ibm-community.md](#sec-377)) |+| Creating articles, videos, and other spotlights | The IBM Community blog post recorded as Live in [listings.md](#sec-407), plus the group's tutorial threads |+| Providing product feedback to IBM development teams | Granite and watsonx.ai are wired into production surfaces documented in [ibm.md](#sec-382); the feedback exists, it has never been routed to IBM as feedback |Timing, stated honestly: as of 2026-09-09 no class-of-2027 announcement wasfound. The 2026 cycle opened 2025-09-15 and closed 2025-11-21, so the window is@@ -96708,7 +97030,7 @@ Nominate the person, not the company. The program is explicitly for individuals.| Surface | Intake | The gate ||---|---|---|| **IBM Cloud catalog listing** | [cloud.ibm.com/partner-center](https://cloud.ibm.com/partner-center) (resolves to `/partner-center/sell`), docs at [cloud.ibm.com/docs/sell](https://cloud.ibm.com/docs/sell) | The IBM analogue of the AWS Marketplace listing we already built for. Four steps: register the product, define the catalog entry, onboard, publish. It is a real procurement channel, and the closest IBM surface to a self-serve listing. The gate is a product decision about what gets listed (the watsonx MCP connector is the obvious candidate) and validation against IBM's onboarding requirements, not permission. |-| **Partner Plus Build track benefits** | Partner Plus portal | We sit in the Build track. Which benefits it carries, which are unclaimed, and which items in the monthly mailer are reachable at all are audited in [partners/ibm-partner-plus.md](#sec-477). Not re-litigated here. |+| **Partner Plus Build track benefits** | Partner Plus portal | We sit in the Build track. Which benefits it carries, which are unclaimed, and which items in the monthly mailer are reachable at all are audited in [partners/ibm-partner-plus.md](#sec-483). Not re-litigated here. || **TechXchange 2026 presence** | See Tier 3 | Sponsorship and expo are paid routes with real lead times. |---@@ -96735,11 +97057,11 @@ Nominate the person, not the company. The program is explicitly for individuals.## Benefits we are entitled to and have never requested-Audited in full in [partners/ibm-partner-plus.md](#sec-477):+Audited in full in [partners/ibm-partner-plus.md](#sec-483):My Digital Marketing and its 1:1 concierge support, the ready-to-execute PartnerMarketing Kits, co-marketing funding, digital badging, and the Software AccessCatalog, plus a verdict on every item in the September 2026 mailer. The pattern-that audit found is the same one the [NVIDIA map](#sec-454)+that audit found is the same one the [NVIDIA map](#sec-458)found: the program was joined, the benefits were never requested, and nobodynoticed because benefits do not arrive unasked.@@ -96760,10 +97082,10 @@ contacts from the 2026-06-15 and 2026-06-18 meetings, and the IBM Communitystaff who have published about three.ws. One message, five asks, not fivemessages:-1. A date for the second community event, with [ibm-next-event.md](#sec-375) attached as the run of show.+1. A date for the second community event, with [ibm-next-event.md](#sec-379) attached as the run of show.2. The status of the dedicated three.ws page on the IBM domain, agreed 2026-06-18.3. The status of the co-promotion from IBM's own channels, agreed the same day.-4. My Digital Marketing access and the Build track Partner Marketing Kit, with confirmation of our tier ([partners/ibm-partner-plus.md](#sec-477) has the specifics to quote).+4. My Digital Marketing access and the Build track Partner Marketing Kit, with confirmation of our tier ([partners/ibm-partner-plus.md](#sec-483) has the specifics to quote).5. Whether the user-group route into TechXchange 2026 is open to us, given the event is seven weeks out.Ask 5 has the deadline. Asks 2 and 3 are follow-ups on commitments, which is the@@ -96771,7 +97093,7 @@ easiest kind of message to answer and the easiest kind to let lapse.**The Agent Connect `APP_ID` request is a separate message to a separate inbox**(`[email protected]`), specified in-[partners/ibm-partner-plus.md](#sec-477). Do not fold it in+[partners/ibm-partner-plus.md](#sec-483). Do not fold it inhere: it goes to the ecosystem team, not the marketing contacts, and bundling itburies the one ask with a concrete technical unblock.@@ -96788,7 +97110,7 @@ buries the one ask with a concrete technical unblock.seven weeks writing an abstract for it.- **Presenting the `/api/ibm/*` showcase as a partnership deliverable.** Not adead end so much as a prohibition, and it is the easiest mistake to make in an- outreach email. See the framing rules in [ibm.md](#sec-378).+ outreach email. See the framing rules in [ibm.md](#sec-382).---@@ -96803,28 +97125,28 @@ buries the one ask with a concrete technical unblock.| Champion nominations are self-serve and annual | Web search across the last three nomination announcements | Class of 2026 opened 2025-09-15, closed 2025-11-21; self-nomination invited; no class-of-2027 announcement found as of 2026-09-09 || `ibm-champion-nominate` URL is dead | `curl -L` | HTTP 404 || TechXchange 2026 dates, pricing, CFP state | Fetched [ibm.com/events/techxchange](https://www.ibm.com/events/techxchange) | 2026-10-26 to 10-29, Atlanta; early bird USD 1,279 through 2026-09-29; call for sessions closed; sponsorship, Sandbox Expo and colocated user groups listed |-| Our user group's post cadence and last post | Read [ibm-community.md](#sec-373) | Last catalogued post 2026-08-08; cadence allowance is one per week per [ibm.md](#sec-378) |-| A finished group post is unposted | Read [ibm-community.md](#sec-373) drafts table | [ibm-community-governed-agents-post.md](#sec-365), written, not posted |-| The June co-marketing commitments are still open | Read [ibm.md](#sec-378) and [partners/ibm-partner-plus.md](#sec-477) | The event was held; the IBM-domain page and the co-promotion have no recorded delivery |+| Our user group's post cadence and last post | Read [ibm-community.md](#sec-377) | Last catalogued post 2026-08-08; cadence allowance is one per week per [ibm.md](#sec-382) |+| A finished group post is unposted | Read [ibm-community.md](#sec-377) drafts table | [ibm-community-governed-agents-post.md](#sec-369), written, not posted |+| The June co-marketing commitments are still open | Read [ibm.md](#sec-382) and [partners/ibm-partner-plus.md](#sec-483) | The event was held; the IBM-domain page and the co-promotion have no recorded delivery || IBM authored several of our timeline entries | Read [`data/timeline.json`](../data/timeline.json) | Five IBM-sourced entries with live `source_url` values, including the Strategic Partner spotlight |---## Related-- [IBM watsonx and Granite](#sec-378): the integration, the partnership status, and the framing rules that bind everything here-- [IBM Community post catalog](#sec-373): every post in our user group, with authors, dates and activity-- [The second IBM community event](#sec-375): the finished proposal waiting on a date-- [IBM Granite x402 MCP](#sec-377): the pay-per-call Granite path-- [Partnership and listing pipeline](#sec-479): every partner surface as one worklist, IBM's rows included-- [Big-tech recognition dispatch board](#sec-166): this map ranked against OpenAI, NVIDIA and AWS by odds of a published mention-- [NVIDIA visibility map](#sec-454): the same treatment for NVIDIA, and the template this follows-- [Listings and distribution](#sec-403): the canonical program and directory inventory-- [Partners](#sec-474): the independence and no-endorsement language that must survive any rewrite+- [IBM watsonx and Granite](#sec-382): the integration, the partnership status, and the framing rules that bind everything here+- [IBM Community post catalog](#sec-377): every post in our user group, with authors, dates and activity+- [The second IBM community event](#sec-379): the finished proposal waiting on a date+- [IBM Granite x402 MCP](#sec-381): the pay-per-call Granite path+- [Partnership and listing pipeline](#sec-486): every partner surface as one worklist, IBM's rows included+- [Big-tech recognition dispatch board](#sec-167): this map ranked against OpenAI, NVIDIA and AWS by odds of a published mention+- [NVIDIA visibility map](#sec-458): the same treatment for NVIDIA, and the template this follows+- [Listings and distribution](#sec-407): the canonical program and directory inventory+- [Partners](#sec-480): the independence and no-endorsement language that must survive any rewrite----<a id="sec-377"></a>+<a id="sec-381"></a>> **Source:** `docs/ibm-x402-mcp.md` · [↑ table of contents](#table-of-contents)@@ -96846,9 +97168,9 @@ bill itself, in USDC, over [x402](https://x402.org).This is the developer guide for the `@three-ws/ibm-x402-mcp` tool suite. For thebroader IBM integration (the platform showcase, Guardian Trust Layer, the-credentials-based `@three-ws/ibm-watsonx-mcp` connector) see **[docs/ibm.md](#sec-378)**.+credentials-based `@three-ws/ibm-watsonx-mcp` connector) see **[docs/ibm.md](#sec-382)**.For the x402 protocol primitives used elsewhere on the platform see-**[docs/x402.md](#sec-862)**.+**[docs/x402.md](#sec-877)**.---@@ -97166,7 +97488,7 @@ HTTP `status`), `internal_error` (unexpected).## Discovery (x402 Bazaar)Each tool declares an x402 discovery extension, so the suite is browsable in the-[x402 Bazaar](#sec-416) alongside its schema, example input, and+[x402 Bazaar](#sec-420) alongside its schema, example input, andexample output. Agents can find Granite tools by capability and price withoutknowing the server up front.@@ -97187,16 +97509,16 @@ Catalog/listing copy is maintained in## See also-- [docs/ibm.md](#sec-378) — the full IBM Granite / watsonx integration and showcase-- [docs/x402.md](#sec-862) — the x402 payment protocol on three.ws-- [docs/mcp.md](#sec-417) — wiring MCP servers into a client-- [docs/mcp-x402-bazaar.md](#sec-416) — x402 service discovery+- [docs/ibm.md](#sec-382) — the full IBM Granite / watsonx integration and showcase+- [docs/x402.md](#sec-877) — the x402 payment protocol on three.ws+- [docs/mcp.md](#sec-421) — wiring MCP servers into a client+- [docs/mcp-x402-bazaar.md](#sec-420) — x402 service discovery- [packages/ibm-x402-mcp](../packages/ibm-x402-mcp) — the npm package source- npm: [`@three-ws/ibm-x402-mcp`](https://www.npmjs.com/package/@three-ws/ibm-x402-mcp)----<a id="sec-378"></a>+<a id="sec-382"></a>> **Source:** `docs/ibm.md` · [↑ table of contents](#table-of-contents)@@ -97204,9 +97526,9 @@ Catalog/listing copy is maintained inthree.ws agents can think on **IBM Granite** foundation models, served through **IBM watsonx.ai**. This page documents the whole integration for developers and operators: which Granite models run where, how the watsonx client is wired, how to configure it, and the Granite-powered API surfaces (from a Granite avatar brain to on-chain, Guardian-governed forecasts). The live IBM pages on the product are [three.ws/ibm/hello](https://three.ws/ibm/hello) (the partnership page) and [three.ws/ibm/x402-demo](https://three.ws/ibm/x402-demo) (the x402 live demo).-For the broader platform model see [How it works](#sec-351); for the agent brain abstraction see [Agent system](#sec-068); for the standalone connector see [the MCP server](#mcp-server-three-wsibm-watsonx-mcp) below.+For the broader platform model see [How it works](#sec-355); for the agent brain abstraction see [Agent system](#sec-068); for the standalone connector see [the MCP server](#mcp-server-three-wsibm-watsonx-mcp) below.-For what the IBM Partner Plus membership itself entitles us to, which benefits are unused, and the watsonx Orchestrate Agent Catalog listing path, see [IBM Partner Plus](#sec-477).+For what the IBM Partner Plus membership itself entitles us to, which benefits are unused, and the watsonx Orchestrate Agent Catalog listing path, see [IBM Partner Plus](#sec-483).---@@ -97233,7 +97555,7 @@ Do not describe the connector or the public demos as an official IBM release orIBM is ready to host a second event. The formats considered, the recommendation (a one-weekopen creation contest on the existing Forge-Off board, entered with one sentence and noaccount, closing with a crowning ceremony inside the three.ws world), the run of show, the-division of labor, and the engineering plan are in [ibm-next-event.md](#sec-375).+division of labor, and the engineering plan are in [ibm-next-event.md](#sec-379).No date is set: that is the first decision the proposal asks for.### Community event (held 2026-06-23)@@ -97259,7 +97581,7 @@ three.ws runs a public user group on IBM Community for developers and engineers| Library | [Files and assets](https://community.ibm.com/community/user/groups/community-home/librarydocuments?communitykey=e71510cc-d953-408f-9a1c-019f5c0a7016&LibraryFolderKey=&DefaultView=) || Members | [Member list](https://community.ibm.com/community/user/groups/community-home/community-members?communitykey=e71510cc-d953-408f-9a1c-019f5c0a7016&Execute=1) |-Every thread and blog published in the group is cataloged, with authors, dates, activity, and a faithful per-post summary, in the [IBM Community post catalog](#sec-373). Update the catalog whenever a new post lands.+Every thread and blog published in the group is cataloged, with authors, dates, activity, and a faithful per-post summary, in the [IBM Community post catalog](#sec-377). Update the catalog whenever a new post lands.What belongs there, and what does not, is set by the [SEO keyword plan](ops/seo-keyword-plan.md): one post per week maximum, tutorials that stand on their own for an IBM developer who never clicks through, and no crypto-cluster content (that goes on [three.ws/blog](https://three.ws/blog) instead). The user group is also linked from the site's [Community page](https://three.ws/community) and the global footer.@@ -97517,7 +97839,7 @@ Source: [`packages/ibm-watsonx-mcp`](../packages/ibm-watsonx-mcp). Five tools:WATSONX_API_KEY=… WATSONX_PROJECT_ID=… npx @three-ws/ibm-watsonx-mcp```-It reads the same `WATSONX_*` environment variables documented above. See the [MCP guide](#sec-417) for wiring MCP servers into a client.+It reads the same `WATSONX_*` environment variables documented above. See the [MCP guide](#sec-421) for wiring MCP servers into a client.---@@ -97564,18 +97886,18 @@ Unit tests for the same paths live in [`tests/`](../tests) (`granite-oracle`, `a## See also-- [How it works](#sec-351) — the platform mental model+- [How it works](#sec-355) — the platform mental model- [Agent system](#sec-068) — the brain abstraction Granite plugs into-- [IBM Granite x402 MCP](#sec-377) — pay-per-call Granite for agents (USDC, no IBM account)-- [IBM visibility map](#sec-376) - every IBM surface, its verified intake route, and the windows that close on a date-- [IBM Partner Plus](#sec-477) - the program audit: unused benefits, the mailer triaged, and the Agent Catalog listing path-- [MCP](#sec-417) — wiring MCP servers into a client-- [REST API](#sec-124) — the full endpoint reference-- [Configuration](#sec-212) — all environment variables+- [IBM Granite x402 MCP](#sec-381) — pay-per-call Granite for agents (USDC, no IBM account)+- [IBM visibility map](#sec-380) - every IBM surface, its verified intake route, and the windows that close on a date+- [IBM Partner Plus](#sec-483) - the program audit: unused benefits, the mailer triaged, and the Agent Catalog listing path+- [MCP](#sec-421) — wiring MCP servers into a client+- [REST API](#sec-125) — the full endpoint reference+- [Configuration](#sec-213) — all environment variables----<a id="sec-379"></a>+<a id="sec-383"></a>> **Source:** `docs/image-to-3d.md` · [↑ table of contents](#table-of-contents)@@ -97674,14 +97996,14 @@ console.log(job.glb_url);## Related-- [Forge](#sec-313) is the full text-and-image-to-3D surface with every mode and engine.-- [Avatar reconstruction](#sec-149) and [avatar creation](#sec-144) cover the face-to-avatar pipeline behind [/create/selfie](https://three.ws/create/selfie).+- [Forge](#sec-316) is the full text-and-image-to-3D surface with every mode and engine.+- [Avatar reconstruction](#sec-150) and [avatar creation](#sec-145) cover the face-to-avatar pipeline behind [/create/selfie](https://three.ws/create/selfie).- The pipeline internals: [3D asset pipeline](#sec-002), [3D pipeline](#sec-003), [3D API](#sec-001).- Pages: [/create](https://three.ws/create), [/scene](https://three.ws/scene) (Scene Studio), [/gallery](https://three.ws/gallery).----<a id="sec-380"></a>+<a id="sec-384"></a>> **Source:** `docs/in-game-economy.md` · [↑ table of contents](#table-of-contents)@@ -97810,11 +98132,11 @@ primitives.This is **not** the same rail as the USDC cosmetics shop for the standalonecharacter creator, which sells a different catalog through-[x402](#sec-862) and is surfaced publicly at [/fits](https://three.ws/fits).+[x402](#sec-877) and is surfaced publicly at [/fits](https://three.ws/fits).Two catalogs, two currencies, two rails. Do not confuse them.It is also not the only way to own a wardrobe item. A third tier exists that the-boutique deliberately cannot see: **[event souvenirs](#sec-293)** are+boutique deliberately cannot see: **[event souvenirs](#sec-296)** aregranted to everyone present in the world during a live event and are never sold,before, during, or after. They carry no price, so the boutique's listing filter(`tier === 'premium'` **and** `price > 0`) excludes them by construction, and the@@ -97940,16 +98262,16 @@ every number in this system.## Next-- **[Earn and spend in /play](#sec-721)** walks the+- **[Earn and spend in /play](#sec-729)** walks thewhole loop end to end, from your first gathered log to a cosmetic unlock.- **[three.ws/play/economy](https://three.ws/play/economy)** is the live referencewith the current catalogs and odds.-- **[Coin communities](#sec-194)** covers the worlds themselves: how a coin+- **[Coin communities](#sec-195)** covers the worlds themselves: how a coinbecomes a walkable 3D space.----<a id="sec-381"></a>+<a id="sec-385"></a>> **Source:** `docs/inference-billing.md` · [↑ table of contents](#table-of-contents)@@ -98014,9 +98336,9 @@ a per-run pause ends with the run.no automation keeps hitting the ceiling.- The owner gets a `token_budget_paused` notification on every connectedchannel (bell, push, Telegram, Discord, email per the- [notification preferences](#sec-442)) with a link to+ [notification preferences](#sec-446)) with a link to`/spend?agent=<id>`.-- One **extend once** approval opens in the [approval inbox](#sec-126)+- One **extend once** approval opens in the [approval inbox](#sec-127)(venue `token_budget`, never auto-approved). Approving it raises thiswindow's ceiling by the extension (half the cap by default, never under1,000 tokens) and resumes the agent. A second extension for the same window@@ -98248,15 +98570,15 @@ never a value; keys are encrypted at rest.| Variable | Required | Meaning ||---|---|---|-| `THREE_CREDIT_BONUS_BPS` | no | Bonus credits for paying credits in $THREE, in basis points. Default: no bonus. See [hold-to-access.md](#sec-339). |+| `THREE_CREDIT_BONUS_BPS` | no | Bonus credits for paying credits in $THREE, in basis points. Default: no bonus. See [hold-to-access.md](#sec-343). || `CREDITS_DEPOSIT_WALLET_SOLANA` | yes, for deposits | The platform deposit wallet; falls back to the $THREE treasury wallet. |-Related: [Payment sessions](#sec-488), [Approvals](#sec-126),-[Notifications](#sec-442), [STRUCTURE.md](../STRUCTURE.md).+Related: [Payment sessions](#sec-495), [Approvals](#sec-127),+[Notifications](#sec-446), [STRUCTURE.md](../STRUCTURE.md).----<a id="sec-382"></a>+<a id="sec-386"></a>> **Source:** `docs/inference-node-operator.md` · [↑ table of contents](#table-of-contents)@@ -98530,7 +98852,7 @@ signature, and the artifact hash all check out.----<a id="sec-383"></a>+<a id="sec-387"></a>> **Source:** `docs/integrations.md` · [↑ table of contents](#table-of-contents)@@ -98550,7 +98872,7 @@ The platform's agents are only as useful as the places they can appear. Integratis the distribution layer: it turns an agent, a saved widget, or a live token feedinto something a marketer can paste into a CMS, a developer can wire into a framework,or an AI assistant can call as a tool. It is the front page of embedding; the deep-per-method references live in [Embedding](#sec-259) and [Widgets](#sec-802),+per-method references live in [Embedding](#sec-262) and [Widgets](#sec-814),and this doc is the map that points you to the right one.## How it works@@ -98576,7 +98898,7 @@ The catalog covers six integration types:driven by a `data-widget` id and the `pumpfun-feed` type.- **MCP Integration**: the `@three-ws/avatar-agent` server (from the`packages/avatar-agent-mcp` workspace), so Claude, Cursor, or any MCP-compatible- assistant can render, speak, gesture, and emote your agents. See [MCP](#sec-417).+ assistant can render, speak, gesture, and emote your agents. See [MCP](#sec-421).## Walkthrough@@ -98694,15 +99016,15 @@ for the full table.## Related-- [Embedding Guide](#sec-259): the full per-method reference (web component, iframe, oEmbed)-- [Widget Types](#sec-802): every widget type and how to configure one-- [Embody](#sec-260): giving an agent a body in more contexts-- [MCP](#sec-417): the avatar MCP server for AI assistants+- [Embedding Guide](#sec-262): the full per-method reference (web component, iframe, oEmbed)+- [Widget Types](#sec-814): every widget type and how to configure one+- [Embody](#sec-263): giving an agent a body in more contexts+- [MCP](#sec-421): the avatar MCP server for AI assistants- Pages: [/integrations](https://three.ws/integrations), [/widgets](https://three.ws/widgets)----<a id="sec-384"></a>+<a id="sec-388"></a>> **Source:** `docs/introduction.md` · [↑ table of contents](#table-of-contents)@@ -98913,7 +99235,7 @@ To add an AI brain:The `key-proxy` attribute points to a serverless function that injects your API key — the key never touches the client. The `voice` attribute enables microphone input and TTS output.-For a full step-by-step walkthrough, see the [Quick Start guide](#sec-593).+For a full step-by-step walkthrough, see the [Quick Start guide](#sec-600).---@@ -98921,26 +99243,26 @@ For a full step-by-step walkthrough, see the [Quick Start guide](#sec-593).Once you have the basics working, the following guides go deeper:-- **[Quick Start](#sec-593)** — step-by-step from zero to a talking agent-- **[Embedding Guide](#sec-259)** — all attributes, modes, events, and the JS API-- **[Widget Types](#sec-802)**, the five general-purpose widgets in depth (the other five live in [Widget Studio](https://three.ws/studio))+- **[Quick Start](#sec-600)** — step-by-step from zero to a talking agent+- **[Embedding Guide](#sec-262)** — all attributes, modes, events, and the JS API+- **[Widget Types](#sec-814)**, the five general-purpose widgets in depth (the other five live in [Widget Studio](https://three.ws/studio))- **[Agent System Overview](#sec-068)** — runtime, skill registry, memory, emotion system- **[Manifest Reference](#sec-059)** — full JSON schema with examples-- **[REST API](#sec-124)** and **[JavaScript API](#sec-390)** — backend and in-browser surfaces+- **[REST API](#sec-125)** and **[JavaScript API](#sec-394)** — backend and in-browser surfaces- **[Agents vs. avatars](#sec-078)** — the difference, and when to careIf you want to look at what's already in the hosted platform — browsing agents, using Widget Studio, or registering on-chain — visit [https://three.ws](https://three.ws).----<a id="sec-385"></a>+<a id="sec-389"></a>> **Source:** `docs/ios-app.md` · [↑ table of contents](#table-of-contents)# three.ws on iOSthree.ws ships to the App Store as a native iOS app (`ws.three.app`). Like the-[Seeker app](#sec-629), it is a shell around the live web product rather+[Seeker app](#sec-636), it is a shell around the live web product ratherthan a second implementation of it: a Capacitor 8 container whose WKWebView runs`https://three.ws`, wrapped in the native layer a website cannot have. For aWebGL product that is the right shape, and it means the app is never a version@@ -98993,7 +99315,7 @@ Two consequences worth knowing:## Compared with the Android app-The [Seeker app](#sec-629) is a Trusted Web Activity, so it inherits+The [Seeker app](#sec-636) is a Trusted Web Activity, so it inheritsChrome's Web Push and the web manifest's share target and shortcuts. The iOSWebView inherits none of those, so each one is rebuilt natively, and in twoplaces the iOS version goes further:@@ -99098,13 +99420,13 @@ Which surfaces leave, and why, is in## Related-- [three.ws on Solana Seeker](#sec-629): the Android app+- [three.ws on Solana Seeker](#sec-636): the Android app- [`ios/README.md`](../ios/README.md): building and shipping this one- [`STRUCTURE.md`](../STRUCTURE.md): where every surface lives----<a id="sec-386"></a>+<a id="sec-390"></a>> **Source:** `docs/irl.md` · [↑ table of contents](#table-of-contents)@@ -99148,7 +99470,7 @@ Anonymous pins work immediately from a device token and expire after 7 days. Sig/irl also accepts an inbound avatar: opening `/irl?avatar=<glbUrl>` loads thatrigged GLB directly as the companion. This is the **Bring it to life** handoff-from the [AR launch page](#sec-129) (`GET /api/ar?…&kind=avatar`) and the+from the [AR launch page](#sec-130) (`GET /api/ar?…&kind=avatar`) and the`irlUrl` returned by the avatar-producing studio tools, and an explicit`?avatar=` always wins over a saved session.@@ -99163,7 +99485,7 @@ Every discovered agent is alive in the camera view, not a statue: any humanoid aTapping an agent opens its inspect card:- **Talk** opens a live, spoken conversation with the agent standing in front of you. Hold the mic and speak (or type); the reply comes back in the agent's own persona when the pin carries an agent identity, is voiced through its voice (a cloned one when it has it), and the 3D model's mouth moves with the audio on top of its idle. Pressing the mic while it speaks interrupts it, like a real conversation. The opening line of a conversation lands once in the owner's IRL feed as a `talk` interaction; the transcript never does.-- **View in AR** stands that agent, anyone's, on your real floor through the device's native AR stack: iPhone bakes the pin's model into an animated USDZ and opens ARKit Quick Look (the banner inside AR reads "Talk to <name>" and brings you back to the card with the conversation open); Android with ARCore enters a WebXR hit-test session that anchors this agent's already-loaded model to a detected surface, view-only, with pinch to size; everything else opens the device-aware [AR launcher](#sec-129) in a new tab. Nothing is persisted from a view: the durable placement stays the owner's pin.+- **View in AR** stands that agent, anyone's, on your real floor through the device's native AR stack: iPhone bakes the pin's model into an animated USDZ and opens ARKit Quick Look (the banner inside AR reads "Talk to <name>" and brings you back to the card with the conversation open); Android with ARCore enters a WebXR hit-test session that anchors this agent's already-loaded model to a detected surface, view-only, with pinch to size; everything else opens the device-aware [AR launcher](#sec-130) in a new tab. Nothing is persisted from a view: the durable placement stays the owner's pin.- its bio, on-chain reputation tier, and any paid services it offers- **pay via x402** to use a service it sells, settled on-chain in the request- **leave a message** that lands in the owner's IRL feed@@ -99187,9 +99509,9 @@ The **Share** button captures your camera feed and the placed agent as one photoA placement has a **visit link**, `three.ws/irl?pin=<id>`, and a printable sign at `/irl/sign?pin=<id>`. Both come from the pin's **Visit link** action in [/dashboard/irl-placements](/dashboard/irl-placements). Someone who scans the sign lands on /irl with a banner naming the agent they came to meet; the moment the presence-gated nearby read returns that pin, its label flashes and its card opens on its own. Neither link carries a coordinate, and the agent still appears only within range, so a sign can be posted anywhere. `?highlight=<id>` is an older alias of `?pin=`.-The card of a discovered agent also offers **Talk** and **View in AR** (see [Interact and pay](#interact-and-pay)): the visitor can hold the mic and speak with the agent, and stand it on the real floor through Quick Look on iPhone, WebXR on Android, or the [AR launcher](#sec-129) elsewhere.+The card of a discovered agent also offers **Talk** and **View in AR** (see [Interact and pay](#interact-and-pay)): the visitor can hold the mic and speak with the agent, and stand it on the real floor through Quick Look on iPhone, WebXR on Android, or the [AR launcher](#sec-130) elsewhere.-The full street-demo runbook (picking a spot for GPS, printing, what visitors see, on-site troubleshooting) is [Run an IRL street demo](#sec-388).+The full street-demo runbook (picking a spot for GPS, printing, what visitors see, on-site troubleshooting) is [Run an IRL street demo](#sec-392).## Money Drops@@ -99237,7 +99559,7 @@ The rollup is served at `GET /api/irl/analytics` (admin-gated via `x-ops-secret`----<a id="sec-387"></a>+<a id="sec-391"></a>> **Source:** `docs/irl/THREAT-MODEL.md` · [↑ table of contents](#table-of-contents)@@ -99391,7 +99713,7 @@ in a way that drops legitimate discovery, update this file in the same change.----<a id="sec-388"></a>+<a id="sec-392"></a>> **Source:** `docs/irl/street-demo.md` · [↑ table of contents](#table-of-contents)@@ -99495,7 +99817,7 @@ Test the sign with your own phone before you leave: scan it, walk 70 m away, con----<a id="sec-389"></a>+<a id="sec-393"></a>> **Source:** `docs/issue-resolution-2026-09-15.md` · [↑ table of contents](#table-of-contents)@@ -99576,15 +99898,15 @@ does not prove browser CORS behavior end to end.----<a id="sec-390"></a>+<a id="sec-394"></a>> **Source:** `docs/js-api.md` · [↑ table of contents](#table-of-contents)# JavaScript API Reference-This page documents the internal JavaScript classes behind the three.ws viewer: the `App` controller, the Three.js `Viewer`, the glTF `Validator`, and the small components that render around them. It is aimed at developers reading or extending the source (`src/`), and at anyone driving the viewer from the browser console via `window.VIEWER`. If you just want a 3D agent on your page, use the [`<agent-3d>` element](#sec-799) instead.+This page documents the internal JavaScript classes behind the three.ws viewer: the `App` controller, the Three.js `Viewer`, the glTF `Validator`, and the small components that render around them. It is aimed at developers reading or extending the source (`src/`), and at anyone driving the viewer from the browser console via `window.VIEWER`. If you just want a 3D agent on your page, use the [`<agent-3d>` element](#sec-811) instead.-> For the HTTP/REST surface, see [api-reference.md](#sec-124). For the high-level npm SDK, see [sdk.md](#sec-626). For the `<agent-3d>` element attributes, see [web-component.md](#sec-799).+> For the HTTP/REST surface, see [api-reference.md](#sec-125). For the high-level npm SDK, see [sdk.md](#sec-633). For the `<agent-3d>` element attributes, see [web-component.md](#sec-811).---@@ -99923,7 +100245,7 @@ Creates the mini axes viewport:Builds the entire dat.gui panel. On mobile (≤ 700 px), uses 220 px width and starts closed; on desktop, 260 px width and starts open.-See [Architecture overview](#sec-130) for the full folder tree.+See [Architecture overview](#sec-131) for the full folder tree.#### `updateGUI()`@@ -100215,7 +100537,7 @@ window.VIEWER.app.viewer.updateDisplay();----<a id="sec-391"></a>+<a id="sec-395"></a>> **Source:** `docs/knock.md` · [↑ table of contents](#table-of-contents)@@ -100232,7 +100554,7 @@ who genuinely needs you buys thirty seconds of your attention for a nickel. Aspammer cannot buy a million of them.The delivery is the other half. A knock is not a badge on a tab you will get to-later: your [companion](#sec-209) walks on screen wherever you are on+later: your [companion](#sec-210) walks on screen wherever you are onthree.ws, turns to you, and says who is at the door and what they paid.Open yours at **[three.ws/knock](https://three.ws/knock)**.@@ -100240,7 +100562,7 @@ Open yours at **[three.ws/knock](https://three.ws/knock)**.- **The money is yours.** The USDC settles directly to the wallet you name.three.ws never takes custody of it and takes no cut of it.- **Both kinds of visitor.** A person pays with the wallet in their browser. An- agent pays over [x402](#sec-862) with no human in the loop.+ agent pays over [x402](#sec-877) with no human in the loop.- **Nothing lands for free.** Price, daily cap, message length, and a block listare all yours to set. Every refusal happens before any payment, so a knockthat was never going to land is never a knock somebody paid for.@@ -100663,13 +100985,13 @@ and neither can anyone else outside the three outcomes above.## Related-- [The Companion](#sec-209) is what delivers a knock in person.-- [x402](#sec-862) is the payment protocol the priced lane speaks.-- [Notifications](#sec-442) covers the per-category channel matrix; knocks are their own category, and the avatar channel is on for them by default.+- [The Companion](#sec-210) is what delivers a knock in person.+- [x402](#sec-877) is the payment protocol the priced lane speaks.+- [Notifications](#sec-446) covers the per-category channel matrix; knocks are their own category, and the avatar channel is on for them by default.----<a id="sec-392"></a>+<a id="sec-396"></a>> **Source:** `docs/kol-tracker.md` · [↑ table of contents](#table-of-contents)@@ -100807,8 +101129,8 @@ Writes the curated tracked-wallet list that the tracker merges in. Accepts `{ raThe tracker answers "who is making money"; the reputation surfaces answer "should this wallet's record earn trust". They meet at the wallet address:- **`GET /api/intel/wallet/<WALLET_ADDRESS>`** returns one wallet's realized track record from the Smart-Money graph: a 0 to 100 realized score, win rate, average ATH multiple, winners and losers, labels (`smart_money`, `sybil`, `fresh`, and others), and its funder cluster. `computed: false` means no track record exists yet for that address; that is an honest zero, not an error. A string that is not a base58 Solana address is a different case and returns `400 bad_request`, so a typo never reads as a wallet with no history. Any wallet you see on the tracker can be fed straight into it. The same card is served by `GET /api/intel/smart-money?wallet=<WALLET_ADDRESS>`, which applies the identical validation.-- **[Smart Money Radar](#sec-652)** is the sibling leaderboard built from graduation outcomes rather than a KOL universe: reputation earned per wallet from which coins actually graduated. The tracker's footer links to it, and the two boards frequently disagree in instructive ways.-- **[Trust primitives](#sec-700)** wrap the same question for autonomous agents: a paid endpoint that scores any counterparty wallet from real on-chain evidence before an agent transacts with it.+- **[Smart Money Radar](#sec-660)** is the sibling leaderboard built from graduation outcomes rather than a KOL universe: reputation earned per wallet from which coins actually graduated. The tracker's footer links to it, and the two boards frequently disagree in instructive ways.+- **[Trust primitives](#sec-708)** wrap the same question for autonomous agents: a paid endpoint that scores any counterparty wallet from real on-chain evidence before an agent transacts with it.```bash# Take a wallet from the tracker and pull its reputation record@@ -100826,13 +101148,13 @@ curl 'https://three.ws/api/intel/wallet/<WALLET_ADDRESS>?network=mainnet'## Related-- [Smart Money Radar](#sec-652): reputation earned from graduation outcomes, wallet by wallet-- [Trust primitives](#sec-700): the paid cross-chain reputation read for autonomous agents+- [Smart Money Radar](#sec-660): reputation earned from graduation outcomes, wallet by wallet+- [Trust primitives](#sec-708): the paid cross-chain reputation read for autonomous agents- Pages: [/tracker](https://three.ws/tracker) · [/smart-money](https://three.ws/smart-money) · [/leaderboard](https://three.ws/leaderboard)----<a id="sec-393"></a>+<a id="sec-397"></a>> **Source:** `docs/labor-market.md` · [↑ table of contents](#table-of-contents)@@ -100866,7 +101188,7 @@ agreements: `POST /api/labor/post` (escrowing the reward), `POST /api/labor/awar`POST /api/labor/settle` (releasing its own escrow). An account with no currentsignature gets `403 risk_ack_required` and nothing is escrowed, awarded orreleased. Sign once at [/legal/agreements](https://three.ws/legal/agreements);-see [risk acknowledgment](#sec-618). A worker settling a+see [risk acknowledgment](#sec-625). A worker settling adelivered job to collect its own payout is not gated. Called with an API key orOAuth token instead of a session, `post`, `award` and the autonomy-policy write(`PUT /api/labor/policy`, which arms an agent to post and pay on its own) also need@@ -100985,7 +101307,7 @@ economy move:----<a id="sec-394"></a>+<a id="sec-398"></a>> **Source:** `docs/launch-intents.md` · [↑ table of contents](#table-of-contents)@@ -100993,7 +101315,7 @@ economy move:A funded launch intent is a quote you pay once and a coin that launches from it. The agent's own wallet funds the launch, you confirm it from a signed-in browser, and every step is a stage you can poll.-Use it when you want a launch that is priced up front, paid by the agent wallet and replayable without paying twice. For a plain launch with no quote, use the launch tools described in [pump-launcher.md](#sec-561).+Use it when you want a launch that is priced up front, paid by the agent wallet and replayable without paying twice. For a plain launch with no quote, use the launch tools described in [pump-launcher.md](#sec-568).## The flow@@ -101015,7 +101337,7 @@ quote -> paid -> submitted -> confirmed -> indexed- A bearer token (API key or CLI login) can **create** an intent, **read** it, and run a **dry run**.- Only a same-site browser session can **fund** (`pay`) or **confirm** (`confirm`) it. A bearer is refused with `session_required` (403), so a leaked key can never spend.-- Confirming creates a `pump_funded_launch` request in the [approvals inbox](#sec-126). Nothing is submitted until the owner approves it.+- Confirming creates a `pump_funded_launch` request in the [approvals inbox](#sec-127). Nothing is submitted until the owner approves it.## Endpoints@@ -101105,7 +101427,7 @@ Code: [api/pump/pairs.js](../api/pump/pairs.js), [api/pump/launch-intents.js](..----<a id="sec-395"></a>+<a id="sec-399"></a>> **Source:** `docs/launch-lanes.md` · [↑ table of contents](#table-of-contents)@@ -101202,7 +101524,7 @@ curl -X POST https://three.ws/api/agents/$AGENT_ID/uniswap/launch \-d '{"name":"Chip Stack","symbol":"CHIPS","fee_tier":10000,"lock":{"mode":"permanent"}}'```-The paired lane is `POST /api/agents/:id/paired/quote` and `/paired/launch` (see [paired-coins.md](#sec-472)).+The paired lane is `POST /api/agents/:id/paired/quote` and `/paired/launch` (see [paired-coins.md](#sec-477)).Launching needs a signed real-funds agreement on the account. The wizard shows a confirmation table withsender, launcher, chain, amount and every fee, and signs only after an explicit yes. MCP clients get the samesteps as `uniswap_launch_quote`, `uniswap_launch`, `paired_launch_quote`, `paired_launch`, `launch_lanes` and@@ -101246,13 +101568,13 @@ true or the status is `failed`. A record with no transaction that nobody finishe## Related-- [Paired coins](#sec-472)-- [MCP server](#sec-417)+- [Paired coins](#sec-477)+- [MCP server](#sec-421)- [STRUCTURE.md](../STRUCTURE.md)----<a id="sec-396"></a>+<a id="sec-400"></a>> **Source:** `docs/launch-usecases.md` · [↑ table of contents](#table-of-contents)@@ -101413,13 +101735,13 @@ GET /api/pump/launch-studio?action=preview&id=github-fresh-breakouts&limit=6## Related- [Launch use-case engine](../api/_lib/launch/README.md) — internals + how to add a recipe.-- [Coin Launches](#sec-193) — the underlying launch mechanism.+- [Coin Launches](#sec-194) — the underlying launch mechanism.- [Launch a Coin](https://three.ws/launch) — the wizard each recipe hands off to.- Fee sharing & GitHub reward routing — [`public/studio/fees-panel.js`](../public/studio/fees-panel.js).----<a id="sec-397"></a>+<a id="sec-401"></a>> **Source:** `docs/launchpad.md` · [↑ table of contents](#table-of-contents)@@ -101466,7 +101788,7 @@ reaches the browser, so the wallet adds exactly one signature.The launch fee rides in the same transaction and is shown in the cost panel before you sign. No devbuy, no fee. After launch, every trade of the coin made through three.ws (the trade modal, agentwallets, strategies, snipers) carries the same 1% trade fee. Trades made on pump.fun or elsewhere-do not. Details and env vars: [pump-platform-fee.md](#sec-562).+do not. Details and env vars: [pump-platform-fee.md](#sec-569).## Transaction formats@@ -101548,7 +101870,7 @@ Related: [agent tokens](#sec-074), [Launch Studio](https://three.ws/launch-studi----<a id="sec-398"></a>+<a id="sec-402"></a>> **Source:** `docs/layers.md` · [↑ table of contents](#table-of-contents)@@ -101556,7 +101878,7 @@ Related: [agent tokens](#sec-074), [Launch Studio](https://three.ws/launch-studithree.ws is split into four horizontal layers. Each layer can be used on its own. Each layer is independently replaceable as long as its contract with the rest of the system holds. This document describes what each layer owns, what it exports, and where to extend it.-For the overall request flow, see [How three.ws works](#sec-351). For internal module names and paths, see [Architecture overview](#sec-130).+For the overall request flow, see [How three.ws works](#sec-355). For internal module names and paths, see [Architecture overview](#sec-131).---@@ -101646,10 +101968,10 @@ Modules:- **`agent-identity.js`** — the passport + diary. Stable agent ID, owner address, signed action history. Backed by `localStorage` (cache) and `/api/agents/<id>` (canonical). Listens on the protocol bus and POSTs `speak` / `skill-done` / `validate` / `sign` events to `/api/agent-actions`.- **`memory/`** — `local`, `ipfs`, `encrypted-ipfs`, or `none`. Declared on the manifest.- **`erc8004/`** — on-chain registries. `IdentityRegistry` (mints agent token with `tokenURI`), `ReputationRegistry` (signed feedback), `ValidationRegistry` (validation report hashes). Per-chain addresses in `erc8004/abi.js`.-- **`erc8004/solana-deploy.js`**: Solana counterpart. Metaplex Core asset mint; SPL Memo attestations and reputation live server-side (see [Agent Reputation on Solana](#sec-656)).+- **`erc8004/solana-deploy.js`**: Solana counterpart. Metaplex Core asset mint; SPL Memo attestations and reputation live server-side (see [Agent Reputation on Solana](#sec-664)).- **`auth/` + `wallet/`** — SIWE / SIWS for backend mutations; Privy for email/social → embedded wallet onboarding; session cookies after wallet proof.-Per-chain registry addresses, ABIs, and helpers ship as `@three-ws/sdk`. ENS attestations are also handled here — see [register-onchain.md](#sec-749).+Per-chain registry addresses, ABIs, and helpers ship as `@three-ws/sdk`. ENS attestations are also handled here — see [register-onchain.md](#sec-757).---@@ -101662,7 +101984,7 @@ Per-chain registry addresses, ABIs, and helpers ship as `@three-ws/sdk`. ENS attModules:- **`element.js`**: `<agent-3d>` custom element. Lazy-boots via `IntersectionObserver` (unless `eager`). Enforces origin allowlist. Exposes attributes for `body`, `brain`, `agent-id`, `manifest`, `mode` (`inline` / `floating` / `section` / `fullscreen`), `voice`, and more. Public methods: `say()`, `ask()`, `installSkill()`, `expressEmotion()`, `play()`, `lookAt()`, `pause()`, `destroy()`.-- **`stage-element.js`**: `<agent-stage>` for hosting multiple agents in one shared scene. See [multi-agent.md](#sec-438).+- **`stage-element.js`**: `<agent-stage>` for hosting multiple agents in one shared scene. See [multi-agent.md](#sec-442).- **`widget-types.js`**: the ten widget variants: Turntable, Animation Gallery, Talking Agent, ERC-8004 Passport, Hotspot Tour, Pump.fun Live Feed, Smart Money Feed, Live Trades Canvas, Bonding Curve, Walking Avatar.- **`lib.js`** — the CDN entry. Imports the element, registers it, re-exports the public surface (`defineElement`, `Agent3DElement`, `AgentStageElement`, helpers).- **`embed-action-bridge.js`** — the `postMessage` protocol. Iframe widgets and the web component speak the same dialect, so host pages can drive either with the same code.@@ -101697,20 +102019,20 @@ The same source tree produces three independent builds:- **Library**: `npm run build:lib`. `src/lib.js` → `dist-lib/agent-3d.js` (ES module). Add the UMD build (`dist-lib/agent-3d.umd.cjs`) with `npm run build:lib:full`, which is what the production deploy chain runs. Three.js and ethers stay bundled, so the file is intentionally self-contained: a single `<script type="module">` is the only thing a third party needs.- **Artifact** — `vite.config.artifact.js`. A zero-dependency bundle for Claude artifact embeds. Inlined everything, no external script tags, no dynamic imports.-Versioned CDN bundles are published at `/agent-3d/<version>/agent-3d.js`. Use `latest` for auto-updates or pin to a version for stability. See [changelog.md](#sec-180) for release history.+Versioned CDN bundles are published at `/agent-3d/<version>/agent-3d.js`. Use `latest` for auto-updates or pin to a version for stability. See [changelog.md](#sec-181) for release history.---## What's next-- **[Architecture overview](#sec-130)** — module-by-module deep dive+- **[Architecture overview](#sec-131)** — module-by-module deep dive- **[Agent system](#sec-068)** — runtime, skills, memory in detail-- **[Embedding](#sec-259)** — the public face of the embed layer-- **[SDK reference](#sec-626)** — `@three-ws/sdk` and friends+- **[Embedding](#sec-262)** — the public face of the embed layer+- **[SDK reference](#sec-633)** — `@three-ws/sdk` and friends----<a id="sec-399"></a>+<a id="sec-403"></a>> **Source:** `docs/likeness-eval.md` · [↑ table of contents](#table-of-contents)@@ -101908,7 +102230,7 @@ at mean cosine 0.776 while different avatars sat at 0.443, a separation of 0.33rather than 0.035. The production reconstruction lane transfers a face textureonto a fixed template head, and by its own measurement only about 10% of thehead's texels come from the photograph-([avatar fidelity program](#sec-146)). A near-noise-floor+([avatar fidelity program](#sec-147)). A near-noise-flooridentity reading is the number that shape of pipeline should produce, and it isconsistent with the geometry-side ISE result.@@ -101950,8 +102272,8 @@ and reason only.## Related-- [Selfie to avatar](#sec-633): the capture flow being measured-- [Avatar fidelity program](#sec-146): the tracks this+- [Selfie to avatar](#sec-640): the capture flow being measured+- [Avatar fidelity program](#sec-147): the tracks thismetric scores- [Realism quality bench](../data/quality-bench/README.md): the sibling harnessfor photorealism@@ -101959,7 +102281,7 @@ and reason only.----<a id="sec-400"></a>+<a id="sec-404"></a>> **Source:** `docs/lipsync.md` · [↑ table of contents](#table-of-contents)@@ -102054,15 +102376,15 @@ tick();## Related-- [Voice Lab](#sec-796): clone a voice and synthesize it, the audio these demos animate.-- [Voice and lipsync tutorial](#sec-768): the full walkthrough, including wiring visemes to an agent body.-- [Talking Avatar Video](#sec-672): the server-rendered alternative for exporting a talking-head clip.+- [Voice Lab](#sec-807): clone a voice and synthesize it, the audio these demos animate.+- [Voice and lipsync tutorial](#sec-776): the full walkthrough, including wiring visemes to an agent body.+- [Talking Avatar Video](#sec-680): the server-rendered alternative for exporting a talking-head clip.- [Animations](#sec-101): the runtime clip registry that plays alongside lipsync.- Pages: [/lipsync](https://three.ws/lipsync), [/lipsync/mic](https://three.ws/lipsync/mic).----<a id="sec-401"></a>+<a id="sec-405"></a>> **Source:** `docs/liquid-glass.md` · [↑ table of contents](#table-of-contents)@@ -102077,7 +102399,7 @@ and the budget it has to stay inside.It sits under [Design tokens](#sec-005), which stays the source of truth for colour,type, radius, blur, and motion values. Nothing here introduces a value the token file does not-have. Interaction primitives come from [ui-juice](#sec-774).+have. Interaction primitives come from [ui-juice](#sec-782).## What the reference is@@ -102280,13 +102602,13 @@ This look is expensive and it is not allowed to cost us the product.## Related- [Design tokens](#sec-005), the values every rule above resolves to.-- [ui-juice](#sec-774), the shared interaction primitives (damping, reduced-motion contract).-- [Restyle Studio](#sec-616), which already ships a `realGlass` transmissive preset and the+- [ui-juice](#sec-782), the shared interaction primitives (damping, reduced-motion contract).+- [Restyle Studio](#sec-623), which already ships a `realGlass` transmissive preset and the`RoomEnvironment` lighting setup this document depends on.----<a id="sec-402"></a>+<a id="sec-406"></a>> **Source:** `docs/listings-registry.md` · [↑ table of contents](#table-of-contents)@@ -102294,7 +102616,7 @@ This look is expensive and it is not allowed to cost us the product.<!-- Generated by scripts/listings.mjs from data/listings.json. Do not edit by hand. -->-Every place three.ws is listed, submitted to, or known to be absent from. This is the master index; the prose record with announcements and context is [listings.md](#sec-403), and the action list for stuck items is [partners/opportunities.md](#sec-479).+Every place three.ws is listed, submitted to, or known to be absent from. This is the master index; the prose record with announcements and context is [listings.md](#sec-407), and the action list for stuck items is [partners/opportunities.md](#sec-486).**121 tracked surfaces.** 46 live, 17 pr open, 2 submitted, pending, 4 ready to submit, 14 not listed, 22 declined or closed, 16 unverified.@@ -102490,7 +102812,7 @@ A `live` entry is only ever set after the page was fetched and rendered three.ws----<a id="sec-403"></a>+<a id="sec-407"></a>> **Source:** `docs/listings.md` · [↑ table of contents](#table-of-contents)@@ -102498,7 +102820,7 @@ A `live` entry is only ever set after the page was fetched and rendered three.wsthree.ws is open source and self-hostable. It is also distributed through cloud marketplaces (for enterprise procurement) and indexed in ecosystem dApp directories (for community discovery). This page tracks every official listing.-The full machine-checked index of every surface, including awesome-list PRs and aggregators, is the [listings registry](#sec-402).+The full machine-checked index of every surface, including awesome-list PRs and aggregators, is the [listings registry](#sec-406).If you maintain a marketplace, registry, or directory and want three.ws listed, open an issue at [github.com/nirholas/three.ws/issues](https://github.com/nirholas/three.ws/issues) or reach out via the contacts on [three.ws](https://three.ws).@@ -102510,7 +102832,7 @@ Cloud marketplaces are the procurement flow enterprises use to acquire software| Cloud | Status | Links ||---|---|---|-| **AWS** Marketplace | Integration ready, listing not yet created | three.ws is an AWS Partner and the SaaS integration is built, deployed, and conformant with the Concurrent Agreements requirements AWS made mandatory for new products on 2026-06-01. The product itself has not been created in the AWS Marketplace Management Portal yet, so there is nothing to subscribe to on the AWS side: use [x402](/docs/x402) directly in the meantime, which needs no AWS account. Once the listing is public, subscribing consolidates procurement on your AWS account and auto-issues an x402 API key. Re-checked 2026-09-16: AWS Marketplace public search returns no three.ws product, the [/aws](/aws) page says the listing is coming soon, and the production subscription webhook answers `503 not_configured` because no product code exists yet. See [aws-marketplace.md](#sec-164) and the [listing kit](#sec-163). |+| **AWS** Marketplace | Integration ready, listing not yet created | three.ws is an AWS Partner and the SaaS integration is built, deployed, and conformant with the Concurrent Agreements requirements AWS made mandatory for new products on 2026-06-01. The product itself has not been created in the AWS Marketplace Management Portal yet, so there is nothing to subscribe to on the AWS side: use [x402](/docs/x402) directly in the meantime, which needs no AWS account. Once the listing is public, subscribing consolidates procurement on your AWS account and auto-issues an x402 API key. Re-checked 2026-09-16: AWS Marketplace public search returns no three.ws product, the [/aws](/aws) page says the listing is coming soon, and the production subscription webhook answers `503 not_configured` because no product code exists yet. See [aws-marketplace.md](#sec-165) and the [listing kit](#sec-164). || **Alibaba Cloud** International Marketplace | Live (checked 2026-09-16) | [Product listing](https://marketplace.alibabacloud.com/products/56724001/sgcmfw00036800.html) · [Storefront](https://marketplace.alibabacloud.com/store/3247293.html) · [Announcement](/blog/three-ws-on-alibaba-cloud-marketplace.html) · [Marketplace blog feature](https://marketplace.alibabacloud.com/doc/blog/detail/mplace-sgcmfw00036800.html) || **Google Cloud** Marketplace | Open to partnership | three.ws already runs its production stack on Google Cloud Run (`three-ws-api`, us-central1) — a natural fit for Vertex AI and GCP's global CDN. Reach out for co-listing, credits, and joint GTM. || **Microsoft Azure** Marketplace | On roadmap | Targeted alongside the AWS/Alibaba rollout. |@@ -102525,7 +102847,7 @@ Infrastructure programs that back three.ws with credits, tooling, and founder ne|---|---|---|| **Quicknode** Startup Program | Accepted (2026-07) | three.ws is accepted into the Quicknode Startup Program and approved for free infrastructure credits. Quicknode's globally distributed RPC endpoints (Solana first, plus the EVM chains x402 settles on) add capacity and redundancy behind agent wallets, settlement verification, and live market data. Announcement: [three.ws Joins the Quicknode Startup Program](/blog/three-ws-quicknode-startup-program). || **Google Cloud** for Web3 Startups | Member | Production runs on Google Cloud Run; the program backs compute and Vertex AI usage. Announcement: [three.ws Joins Google Cloud for Web3 Startups](/blog/three-ws-google-cloud-partnership). |-| **NVIDIA Inception** | Member (2026-07) | NVIDIA's program for startups building on accelerated computing. Every generation lane runs on NVIDIA: a self-hosted Cloud Run GPU fleet (L4 plus one RTX PRO 6000 Blackwell) behind text-to-3D, rigging, and motion, and a free hosted lane behind chat, vision, embeddings, safety, and speech. Surface: [/nvidia](/nvidia). Docs: [NVIDIA Inception](#sec-449), [NVIDIA models](#sec-450), [visibility map](#sec-454). Listings that run through the membership are in AI Platform Directories below. Membership is a startup program, not a partnership, an investment, or an endorsement. |+| **NVIDIA Inception** | Member (2026-07) | NVIDIA's program for startups building on accelerated computing. Every generation lane runs on NVIDIA: a self-hosted Cloud Run GPU fleet (L4 plus one RTX PRO 6000 Blackwell) behind text-to-3D, rigging, and motion, and a free hosted lane behind chat, vision, embeddings, safety, and speech. Surface: [/nvidia](/nvidia). Docs: [NVIDIA Inception](#sec-453), [NVIDIA models](#sec-454), [visibility map](#sec-458). Listings that run through the membership are in AI Platform Directories below. Membership is a startup program, not a partnership, an investment, or an endorsement. |---@@ -102537,7 +102859,7 @@ Ecosystem directories are the discovery surfaces that L1/L2 communities, chain f|---|---|---|| **BNB Chain · Dappbay** | Live | [dappbay.bnbchain.org/detail/three](https://dappbay.bnbchain.org/detail/three) — categories: *AI Agent Launchpad · AI Data · AI Infra*. Announcement: [three.ws Listed on BNB Chain's Dappbay Directory](/blog/three-ws-on-bnb-chain-dappbay.html). |-Dappbay is BNB Chain's official dApp directory. The listing is about distribution and discovery into BNB Chain's AI dApp audience — three.ws still settles agent payments on Solana, Base, and Polygon via the chain-agnostic [x402 protocol](#sec-862).+Dappbay is BNB Chain's official dApp directory. The listing is about distribution and discovery into BNB Chain's AI dApp audience — three.ws still settles agent payments on Solana, Base, and Polygon via the chain-agnostic [x402 protocol](#sec-877).---@@ -102547,11 +102869,11 @@ The discovery surfaces owned by the AI platforms themselves, where an MCP server| Directory | Status | Listing details ||---|---|---|-| **OpenAI** Plugin Directory (ChatGPT + Codex) | Open to submission | The universal directory shared by ChatGPT and Codex since 2026-07-09, superseding the former App directory. three.ws already meets the gating requirement: a public OAuth 2.1 MCP server at `https://three.ws/api/mcp` ([mcp.md](#sec-417)). Full submission kit, prerequisites, and rejection criteria: [openai-listing-channels.md](#sec-464). |-| **OpenAI** Showcase Gallery | Open to submission | Editorial feature on openai.com for apps, demos, and open-source projects built with OpenAI models, APIs, or Codex. Open web form, no repo gate. See [openai-listing-channels.md](#sec-464). |-| **OpenAI** Cookbook | Submitted, not merged | [PR #2874](https://github.com/openai/openai-cookbook/pull/2874) (a self-correcting 3D collectible pipeline using text-to-3D, function calling, and vision) has been open since 2026-07-21; on 2026-09-16 it was still open, unmerged, and awaiting review, with last activity on 2026-09-14. Root-cause analysis and the revival steps are in [openai-listing-channels.md](#sec-464). |-| **NVIDIA** Accelerated Apps Catalog | Requested; portal completion required | NVIDIA's curated catalog of applications built by Inception members, published at [marketplace.nvidia.com](https://marketplace.nvidia.com/en-us/enterprise/applications/). The request was sent 2026-09-04 and NVIDIA replied 2026-09-14: qualifying Shipping product records with runtime-technology evidence, descriptions, technical details, logo, and brand color are reviewed periodically. There is no separate submission ID or promised review date. On 2026-09-16 three.ws was not among the 1,846 applications in the public catalog. The current record still needs its technology corrections and complete fields; a live catalog URL is the only evidence of publication. See [nvidia-apps-catalog-listing.md](#sec-443) and [nvidia-apps-catalog-request.md](#sec-444). |-| **NVIDIA** NGC Catalog | Prerequisites cleared, submission pending | The one NVIDIA directory with a self-serve intake form, and a real distribution channel: an NVIDIA-hosted listing for the container itself at [catalog.ngc.nvidia.com](https://catalog.ngc.nvidia.com/). Our candidate is the [model-trellis](../workers/model-trellis) image-to-3D server (MIT upstream model, no baked weights, no telemetry). The EULA prerequisite is closed at [/legal/nvidia-ngc-eula](/legal/nvidia-ngc-eula); what remains is one build and the partner legal agreement. Kit: [nvidia-ngc-listing.md](#sec-453). |+| **OpenAI** Plugin Directory (ChatGPT + Codex) | Open to submission | The universal directory shared by ChatGPT and Codex since 2026-07-09, superseding the former App directory. three.ws already meets the gating requirement: a public OAuth 2.1 MCP server at `https://three.ws/api/mcp` ([mcp.md](#sec-421)). Full submission kit, prerequisites, and rejection criteria: [openai-listing-channels.md](#sec-469). |+| **OpenAI** Showcase Gallery | Open to submission | Editorial feature on openai.com for apps, demos, and open-source projects built with OpenAI models, APIs, or Codex. Open web form, no repo gate. See [openai-listing-channels.md](#sec-469). |+| **OpenAI** Cookbook | Submitted, not merged | [PR #2874](https://github.com/openai/openai-cookbook/pull/2874) (a self-correcting 3D collectible pipeline using text-to-3D, function calling, and vision) has been open since 2026-07-21; on 2026-09-16 it was still open, unmerged, and awaiting review, with last activity on 2026-09-14. Root-cause analysis and the revival steps are in [openai-listing-channels.md](#sec-469). |+| **NVIDIA** Accelerated Apps Catalog | Requested; portal completion required | NVIDIA's curated catalog of applications built by Inception members, published at [marketplace.nvidia.com](https://marketplace.nvidia.com/en-us/enterprise/applications/). The request was sent 2026-09-04 and NVIDIA replied 2026-09-14: qualifying Shipping product records with runtime-technology evidence, descriptions, technical details, logo, and brand color are reviewed periodically. There is no separate submission ID or promised review date. On 2026-09-16 three.ws was not among the 1,846 applications in the public catalog. The current record still needs its technology corrections and complete fields; a live catalog URL is the only evidence of publication. See [nvidia-apps-catalog-listing.md](#sec-447) and [nvidia-apps-catalog-request.md](#sec-448). |+| **NVIDIA** NGC Catalog | Prerequisites cleared, submission pending | The one NVIDIA directory with a self-serve intake form, and a real distribution channel: an NVIDIA-hosted listing for the container itself at [catalog.ngc.nvidia.com](https://catalog.ngc.nvidia.com/). Our candidate is the [model-trellis](../workers/model-trellis) image-to-3D server (MIT upstream model, no baked weights, no telemetry). The EULA prerequisite is closed at [/legal/nvidia-ngc-eula](/legal/nvidia-ngc-eula); what remains is one build and the partner legal agreement. Kit: [nvidia-ngc-listing.md](#sec-457). |---@@ -102561,7 +102883,7 @@ Where the three.ws MCP servers are discoverable as installable servers. Most of| Directory | Status | Listing details ||---|---|---|-| **Official MCP Registry** | Live | 72 servers are published under `io.github.nirholas/*`, including `io.github.nirholas/three.ws` 1.0.1 (the hosted `https://three.ws/api/mcp` server), `threews-3d-studio`, `threews-3d-studio-free`, `threews-agent`, `threews-avatar`, `threews-pumpfun`, and `threews-x402-bazaar`. [Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=three.ws). See [mcp.md](#sec-417). |+| **Official MCP Registry** | Live | 72 servers are published under `io.github.nirholas/*`, including `io.github.nirholas/three.ws` 1.0.1 (the hosted `https://three.ws/api/mcp` server), `threews-3d-studio`, `threews-3d-studio-free`, `threews-agent`, `threews-avatar`, `threews-pumpfun`, and `threews-x402-bazaar`. [Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=three.ws). See [mcp.md](#sec-421). || **PulseMCP** | Live | [pulsemcp.com/servers/nirholas-three-ws](https://www.pulsemcp.com/servers/nirholas-three-ws), ingested from the official registry. || **Glama** | Live, unclaimed | Connectors ingested from the official registry, for example [three.ws Avatars & Agents](https://glama.ai/mcp/connectors/io.github.nirholas/three.ws) and [three.ws 3D Studio](https://glama.ai/mcp/connectors/io.github.nirholas/threews-3d-studio). The main connector is not yet claimed and shows a failing health check because Glama holds no OAuth test credentials. The maintainer contact is declared in [`/.well-known/glama.json`](https://three.ws/.well-known/glama.json). || **LobeHub** MCP marketplace | Live | Indexed from GitHub, for example [@three-ws/portal](https://lobehub.com/mcp/nirholas-three-ws-portal) and [@three-ws/avatar-mcp](https://lobehub.com/mcp/nirholas-threews-avatar-mcp). The separate LobeHub chat plugin described by [`/.well-known/lobehub-plugin.json`](https://three.ws/.well-known/lobehub-plugin.json) is not in LobeHub's plugin index. |@@ -102576,7 +102898,7 @@ Where the three.ws MCP servers are discoverable as installable servers. Most of|---|---|---|| **IBM Community** | Live | [Embodied, Intelligent, and Self-Custodied: three.ws and the 3D AI Agent Stack](https://community.ibm.com/community/user/blogs/nich8/2026/06/08/3d-ai-web3-just-converge-threews-shipped-the-whole) — IBM Community blog covering the convergence of 3D, AI agents, and web3 in the three.ws stack. || **HackerNoon** | Author page live, no stories published yet | [hackernoon.com/u/three-ws](https://hackernoon.com/u/three-ws): three.ws posts auto-import from the RSS feed into the HackerNoon drafts queue. As of 2026-09-16 the author page shows no published stories. Announcement: [three.ws Partners with HackerNoon](/news/partnered-with-hackernoon) |-| **Hugging Face** | Live | [huggingface.co/three-ws](https://huggingface.co/three-ws): the [Avatar Viewer Space](https://huggingface.co/spaces/three-ws/avatar-viewer), the [avatars model repo](https://huggingface.co/three-ws/avatars), and two articles, most recently [Inside three.ws](https://huggingface.co/blog/three-ws/building-3d-ai-agents-end-to-end) (2026-08-29). See [huggingface.md](#sec-354). |+| **Hugging Face** | Live | [huggingface.co/three-ws](https://huggingface.co/three-ws): the [Avatar Viewer Space](https://huggingface.co/spaces/three-ws/avatar-viewer), the [avatars model repo](https://huggingface.co/three-ws/avatars), and two articles, most recently [Inside three.ws](https://huggingface.co/blog/three-ws/building-3d-ai-agents-end-to-end) (2026-08-29). See [huggingface.md](#sec-358). || **Alibaba Cloud Marketplace Blog** | Live | [Editorial feature](https://marketplace.alibabacloud.com/doc/blog/detail/mplace-sgcmfw00036800.html) — Alibaba Cloud Marketplace published an editorial introducing three.ws. Announcement: [three.ws Featured on the Alibaba Cloud Marketplace Blog](/blog/three-ws-featured-on-alibaba-cloud-marketplace-blog) || **pump.fun** | Live | [Three Builds With Tech Giants](https://pump.fun/coin/FeMbDoX7R1Psc4GEcvJdsbNbZA3bfztcyDCatJVJpump/article): a feature article published on the official $THREE coin page, profiling the platform's browser-native 3D AI agents with onchain identities, the Animations and Poses Studio, the 3D Studio MCP server, and the AWS and IBM milestones. |@@ -102631,14 +102953,14 @@ Social Boost ranks by visits to a pair page, so every surface that shows a coin| Surface | What it shows ||---|---|| [/three-token](/three-token) | The DEXTools chart widget as the $THREE chart, the Social Boost wins, and the pair page link |-| Every coin chart (`/launches/<mint>`, `/coin/:id`, `/trades`, Mission Control, the Oracle, `/pump-dashboard`) | DEXTools as a chart source in the switcher ([coin pages](#sec-194)) |+| Every coin chart (`/launches/<mint>`, `/coin/:id`, `/trades`, Mission Control, the Oracle, `/pump-dashboard`) | DEXTools as a chart source in the switcher ([coin pages](#sec-195)) || Trading terminal rows (coin pages, the $THREE dashboard, the pump.fun feed widget, Oracle share pages) | DEXTools leads the row ([src/shared/trading-terminals.js](../src/shared/trading-terminals.js)) || [/launch](/launch) success screen | A DEXTools button and the "Rally on DEXTools" Social Boost card, right after a coin goes live || `/launches/<mint>` Take action | The same Social Boost card for any coin |-| `/coin3d` | A DEXTools link in the HUD. A scene embedded by `?pair=` links back to that exact pair ([coin3d embed](#sec-196)) |+| `/coin3d` | A DEXTools link in the HUD. A scene embedded by `?pair=` links back to that exact pair ([coin3d embed](#sec-197)) || `/oracle/coin/<mint>` | A DEXTools button beside the other market links || Agent profiles, character pages, `/gmgn`, `/pumpfun`, the token dashboard | A DEXTools chart link for every coin shown |-| [/dextools](/dextools) | The hub: $THREE as a DEXTools chart and a 3D scene side by side, the live visit totals, an embed builder for any DEXTools pair, and the Social Boost wins ([DEXTools integration](#sec-246)) |+| [/dextools](/dextools) | The hub: $THREE as a DEXTools chart and a 3D scene side by side, the live visit totals, an embed builder for any DEXTools pair, and the Social Boost wins ([DEXTools integration](#sec-247)) || `/embed/dextools-boost?mint=` | The Social Boost card as a framable embed any project can put on its own site, every link counted as `embed-boost` ([DEXTools integration](dextools.md#boost-on-dextools-card-embeddextools-boost)) |**Which page a link opens.** DEXTools files a pump.fun mint as the coin's bonding-curve pair, so a raw-mint link sends a graduated coin to its dead curve page. Links that already know the pair use it. Every other link goes through [`GET /api/coin/dextools`](https://three.ws/api/coin/dextools?address=FeMbDoX7R1Psc4GEcvJdsbNbZA3bfztcyDCatJVJpump&from=docs), which resolves the most-liquid pool, redirects to its pair page, and pins $THREE to the pair its Social Boost wins are credited to. The redirect counts each visit per UTC day, coin and sending surface (no visitor data), and [`GET /api/coin/dextools-stats`](https://three.ws/api/coin/dextools-stats) publishes those totals, so the traffic three.ws sends DEXTools can be checked rather than claimed.@@ -102685,16 +103007,16 @@ Subscribe via RSS to track new listings, integrations, and protocol updates.## Related-- [Partnership and listing pipeline](#sec-479): the same surfaces as an action list, showing what is stuck, on whom, and the single step that unblocks each one+- [Partnership and listing pipeline](#sec-486): the same surfaces as an action list, showing what is stuck, on whom, and the single step that unblocks each one- [AWS Marketplace](/docs/aws-marketplace): the AWS listing and entitlement-issued x402 API keys- [Syndication](/docs/syndication): how announcements flow to HackerNoon and other channels-- [Publishing program, September 2026](#sec-557): the venue matrix, running order, and per-venue rules for the current writing push+- [Publishing program, September 2026](#sec-564): the venue matrix, running order, and per-venue rules for the current writing push- [x402 protocol](/docs/x402): the payment rail behind the paid endpoints these listings distribute- [Introduction](/docs/introduction): the full technical picture of the platform being listed----<a id="sec-404"></a>+<a id="sec-408"></a>> **Source:** `docs/live-docs.md` · [↑ table of contents](#table-of-contents)@@ -102714,7 +103036,7 @@ Press **Edit**, change something, and press <kbd>⌘</kbd>/<kbd>Ctrl</kbd> +## Try it: a live avatar-This is the same embed snippet from the [`<agent-3d>` reference](#sec-799).+This is the same embed snippet from the [`<agent-3d>` reference](#sec-811).Press **Run preview** and it renders. Then press **Edit**, swap `michelle.glb`for `xbot.glb`, and run it again.@@ -102876,14 +103198,14 @@ cached module.## Related-- [`<agent-3d>` Web Component API Reference](#sec-799) — the element most previews render-- [API reference](#sec-124) — the endpoints most `curl` samples call-- [Embed and share](#sec-259) — putting an avatar on your own site-- [MCP tool safety](#sec-412) — the same read/write/irreversible split, applied to agent tools+- [`<agent-3d>` Web Component API Reference](#sec-811) — the element most previews render+- [API reference](#sec-125) — the endpoints most `curl` samples call+- [Embed and share](#sec-262) — putting an avatar on your own site+- [MCP tool safety](#sec-416) — the same read/write/irreversible split, applied to agent tools----<a id="sec-405"></a>+<a id="sec-409"></a>> **Source:** `docs/live-steps.md` · [↑ table of contents](#table-of-contents)@@ -103066,7 +103388,7 @@ Run `npx vitest run tests/live-steps.test.js` after editing the registry; the su----<a id="sec-406"></a>+<a id="sec-410"></a>> **Source:** `docs/make-your-agent.md` · [↑ table of contents](#table-of-contents)@@ -103083,7 +103405,7 @@ This guide walks you through creating a 3D AI agent in the browser — no code,Go to [three.ws/start](/start). This is the new-agent wizard.-You can walk through the whole setup before signing in: the avatar, the name, the brain, and the skills are kept in the tab. The wizard asks you to sign in (or create a free account) at the publish step, then picks up exactly where you left off. See [Do I need crypto?](#sec-248) if you're not sure which sign-in option to choose.+You can walk through the whole setup before signing in: the avatar, the name, the brain, and the skills are kept in the tab. The wizard asks you to sign in (or create a free account) at the publish step, then picks up exactly where you left off. See [Do I need crypto?](#sec-251) if you're not sure which sign-in option to choose.---@@ -103133,7 +103455,7 @@ Once you hit **Publish**, your agent gets a live URL: something like `three.ws/aThe wizard also gives you an **embed snippet**: a few lines of HTML you can paste into any webpage to make the agent appear there. You don't need to know HTML to do this — just copy and paste.-For more on where and how to embed, continue to [Share & embed →](#sec-636)+For more on where and how to embed, continue to [Share & embed →](#sec-643)---@@ -103163,14 +103485,14 @@ Entries expire after two hours so an abandoned setup never hijacks a later, unre## What's next-- **Put it on your website** → [Share & embed](#sec-636)-- **Understand how it all works** → [How it works](#sec-351)-- **Give the agent a custom skill** → [Create a custom skill](#sec-718)-- **Make it yours permanently (on-chain)** → [Register on-chain](#sec-749)+- **Put it on your website** → [Share & embed](#sec-643)+- **Understand how it all works** → [How it works](#sec-355)+- **Give the agent a custom skill** → [Create a custom skill](#sec-726)+- **Make it yours permanently (on-chain)** → [Register on-chain](#sec-757)----<a id="sec-407"></a>+<a id="sec-411"></a>> **Source:** `docs/market-data-api.md` · [↑ table of contents](#table-of-contents)@@ -103295,7 +103617,7 @@ as the single retryable class.----<a id="sec-408"></a>+<a id="sec-412"></a>> **Source:** `docs/marketplace.md` · [↑ table of contents](#table-of-contents)@@ -103426,7 +103748,7 @@ direct-transfer QR for wallets that do not implement transaction requests.and applied at settlement.- Seller proceeds route to the seller's configured payout wallet(`agent_payout_wallets`). A confirmed sale surfaces to the seller as a `sale` /- `payment-earned` notification (see [Money feed](#sec-433)).+ `payment-earned` notification (see [Money feed](#sec-437)).## Access checks@@ -103476,7 +103798,7 @@ sales and zero exhausted trials before it was found. Seeendpoints are complete, but there is not yet a free, paginated "browse allskills for sale" HTTP endpoint with sort/filter; discovery today is per-agent(agents themselves are browsable at `GET /api/marketplace/agents`), and the- paid [`/api/x402/skill-marketplace`](#sec-854) endpoint returns the+ paid [`/api/x402/skill-marketplace`](#sec-869) endpoint returns thelive skill listing catalog with pricing for $0.001 USDC.- **Auto-grant.** A confirmed skill purchase is recorded and the license NFT isminted, but the purchased skill is not automatically attached to the buyer's@@ -103495,12 +103817,12 @@ their chosen `currency_mint`; the platform promotes no coin other than $THREE.## Related- [Agent wallets](#sec-077) — how agent-side purchases are funded and gated.-- [Circulation engine](#sec-189) — manufactured marketplace demand.-- [Skills system](#sec-649), [Coin launches](#sec-193).+- [Circulation engine](#sec-190) — manufactured marketplace demand.+- [Skills system](#sec-657), [Coin launches](#sec-194).----<a id="sec-409"></a>+<a id="sec-413"></a>> **Source:** `docs/materialize.md` · [↑ table of contents](#table-of-contents)@@ -103519,9 +103841,17 @@ surface, and as far as we know this is the first API where an AI agent can payfor manufacturing.**New to three.ws 3D?** Generate something first at-[/forge](https://three.ws/forge) ([Forge](#sec-313)), then come back. You can+[/forge](https://three.ws/forge) ([Forge](#sec-316)), then come back. You canalso print a `.glb` you already have.+**Not sure this is what you want?** Materialize is three.ws's own print+pipeline: you pay three.ws in USDC, we screen the order, submit it to a+fulfillment partner, and issue a certificate. If you would rather shop live+prices across Craftcloud's (All3DP) wider print network and pay a shop+directly with three.ws never touching the money, that is the separate+"Get it printed" flow described in+[Forge: get it printed](forge.md#get-it-printed-live-prices-from-craftcloud).+---## The flow@@ -103951,14 +104281,16 @@ documents the verdict shape and, just as importantly, what the gate cannot do.## Related-- [Forge](#sec-313), where the models come from-- [The Forge pipeline](#sec-311), the generation engineering guide+- [Forge](#sec-316), where the models come from+- [Forge: get it printed](forge.md#get-it-printed-live-prices-from-craftcloud),+ the buyer-pays-direct alternative to this page+- [The Forge pipeline](#sec-314), the generation engineering guide- [specs/PRINT_PIPELINE.md](../specs/PRINT_PIPELINE.md), every wire contract-- [API reference](#sec-124), the `/api/print/*` endpoints+- [API reference](#sec-125), the `/api/print/*` endpoints----<a id="sec-410"></a>+<a id="sec-414"></a>> **Source:** `docs/mcp-3d-studio.md` · [↑ table of contents](#table-of-contents)@@ -103999,7 +104331,7 @@ analyze: inspect_model · optimize_model preview: preview_3d| `text_to_3d(prompt, aspect_ratio?, tier?, path?, backend?)` | Text → reference image → reconstructed GLB. Returns a `job_id` + the intermediate preview image. || `image_to_3d(image_url \| image_urls[], prompt?, tier?, path?, backend?)` | Reconstruct a GLB from 1–4 reference views (multi-view removes back-of-object hallucination). Returns a `job_id`. || `generation_status(job_id)` | Poll any job. When done, returns the GLB URL **and** an inline `<model-viewer>` artifact. Provider-aware: routes geometry/self-host jobs to the right upstream. |-| `cad_generate(prompt, parent_id?, values?)` | Description → **parametric CAD**: a build123d program the OpenCascade kernel has accepted, saved with STEP, STL, GLB (true scale) and an SVG drawing, plus a `/cad/:id` page with dimension sliders. Synchronous, usually 20-90 s. For brackets, enclosures, gears and other functional parts. See [CAD Forge](#sec-177). |+| `cad_generate(prompt, parent_id?, values?)` | Description → **parametric CAD**: a build123d program the OpenCascade kernel has accepted, saved with STEP, STL, GLB (true scale) and an SVG drawing, plus a `/cad/:id` page with dimension sliders. Synchronous, usually 20-90 s. For brackets, enclosures, gears and other functional parts. See [CAD Forge](#sec-178). || `cad_rebuild(id, values)` | Rebuild a CAD Forge design at new parameter values (e.g. `{"WIDTH": 120}`) on the kernel, no model involved. Exact and cached per value set. |### Rig, animate & pose@@ -104034,7 +104366,7 @@ analyze: inspect_model · optimize_model preview: preview_3d| `inspect_model(url)` | Structural stats: meshes, triangles, materials, textures, animations, extensions. || `optimize_model(url)` | Actionable size/perf suggestions: Draco/Meshopt, KTX2, triangle budget. || `preview_3d(glb_url, …)` | Render any public GLB as an interactive `<model-viewer>` artifact (orbit, AR, auto-rotate). |-| `export_ar(glb_url, title?, kind?)` | Read-only: turn any public GLB into the device-aware AR link set (`arLaunchUrl`, `sceneViewerUrl`, `viewerUrl`, plus `irlUrl` when `kind: "avatar"`) and a [Spatial MCP](#sec-659) artifact. Free. See [AR & WebXR](ar.md#one-tap-ar-for-any-glb--get-apiar--export_ar). |+| `export_ar(glb_url, title?, kind?)` | Read-only: turn any public GLB into the device-aware AR link set (`arLaunchUrl`, `sceneViewerUrl`, `viewerUrl`, plus `irlUrl` when `kind: "avatar"`) and a [Spatial MCP](#sec-667) artifact. Free. See [AR & WebXR](ar.md#one-tap-ar-for-any-glb--get-apiar--export_ar). || `getting_started(section?)` | Free, no credentials: an overview of every tool, how to get access, and the useful links. Call it first to orient. || `save_avatar(glb_url, name, visibility?, source_prompt?, tags?)` | Copy a generated GLB into three.ws storage (so it survives the provider URL expiring) and register it as a named avatar you own. Free. || `capture_scene(video_url, mode?, fps?, …)` | Reconstruct a real space from a video walkaround into an explorable 3D point cloud (LingBot-Map streaming reconstructor, drift-corrected across the clip). |@@ -104042,7 +104374,7 @@ analyze: inspect_model · optimize_model preview: preview_3d| `anchor_provenance(glb_url, creator?, prompt?, …)` | Issue a signed content credential for a generated GLB and anchor its hash on Solana, so anyone can later check authenticity for free. || `verify_provenance(glb_url, hash?)` | Free: recompute the model’s content hash, check the signed credential and its on-chain anchor, and answer `verified`, `tampered`, or `unknown`. || `read_resource(uri?, format?)` | Free: read a live `three://` resource (`three://me`, `three://agents`, `three://agents/<id>`, `three://models`, `three://assets/<id>`) for clients that render tools but not MCP resources. Omit `uri` to list what you can read. |-| `validate_spatial_response(artifact)` | Free: check a structured-content payload against the open [Spatial MCP](#sec-659) artifact shape before you ship it. |+| `validate_spatial_response(artifact)` | Free: check a structured-content payload against the open [Spatial MCP](#sec-667) artifact shape before you ship it. || `x402_preflight(origin, network?)` | Read-only, free: fetch an x402 seller's signed payability attestation from `<origin>/.well-known/x402-preflight`, verify its ed25519 signature, expiry, and subject, and answer whether that seller can actually settle before you pay it. An attestation that does not verify is reported as unverified, never as health. Spec: [`specs/x402-preflight.md`](../specs/x402-preflight.md). |Generation, rigging, and most mesh ops are **asynchronous**: the tool returns a@@ -104135,7 +104467,7 @@ self-hosted GCP reconstruction worker when `GCP_RECONSTRUCTION_KEY` andwalk of `/api/forge` (self-host TRELLIS and Hunyuan3D, the HuggingFace Spaceslane, NVIDIA NIM, with failover between them) is not wired into this server, sothe HuggingFace engine is deliberately not selectable here. Free text→3D over-MCP is the `forge_free` tool on the [free 3D Studio](#sec-414)+MCP is the `forge_free` tool on the [free 3D Studio](#sec-418)(`/api/mcp-studio`).**BYOK note:** the geometry backends (Meshy/Tripo) have no platform key. Supply@@ -104254,7 +104586,7 @@ npx @modelcontextprotocol/inspector http://localhost:3000/api/mcp-3d----<a id="sec-411"></a>+<a id="sec-415"></a>> **Source:** `docs/mcp-agent.md` · [↑ table of contents](#table-of-contents)@@ -104326,7 +104658,7 @@ Long or short perpetual futures with USDC collateral from an agent's own Solanawallet, over the same service (`api/_lib/perps/service.js`) as the`/api/v1/agents/:id/perps/*` routes and the `/agents/:id/perps` desk. Everyagent starts in paper mode (live prices, no funds moved); live mode stays off-until the owner turns it on, signed in. Guide: [Agent Perps](#sec-490).+until the owner turns it on, signed in. Guide: [Agent Perps](#sec-497).| Tool | Tier | Scope | What it does ||------|------|-------|--------------|@@ -104342,7 +104674,7 @@ until the owner turns it on, signed in. Guide: [Agent Perps](#sec-490).Research, swap and arbitrage tools over one registry(`api/_lib/trading-tools/registry.js`) that also serves the `/api/v1/trading`REST routes, so both surfaces share the schema and the refusal codes. Guide:-[Solana trading tools](#sec-696).+[Solana trading tools](#sec-704).| Tool | Tier | Scope | What it does ||------|------|-------|--------------|@@ -104578,13 +104910,13 @@ npx @modelcontextprotocol/inspector http://localhost:3000/api/mcp-agent----<a id="sec-412"></a>+<a id="sec-416"></a>> **Source:** `docs/mcp-safety.md` · [↑ table of contents](#table-of-contents)# MCP tool safety-Every tool three.ws publishes over the [Model Context Protocol](#sec-417) carries an+Every tool three.ws publishes over the [Model Context Protocol](#sec-421) carries an`annotations` block. Those hints are not decoration: an MCP client reads them todecide whether a tool can run **without stopping to ask the user**. A tool markedread-only gets executed silently; a tool marked destructive gets a confirmation@@ -104913,7 +105245,7 @@ All four run in `npm run gate`.----<a id="sec-413"></a>+<a id="sec-417"></a>> **Source:** `docs/mcp-solana-memo-media.md` · [↑ table of contents](#table-of-contents)@@ -105053,12 +105385,12 @@ claude mcp add solana-memo-media -e SOLANA_RPC_URL=https://your-rpc.example -- n## Related- [Onchain Viewer](/onchain): the same decoding in a browser page, documented in [Solana on three.ws](solana.md#viewing-files-written-in-a-transaction-memo).-- [MCP overview](#sec-417): every three.ws MCP server.+- [MCP overview](#sec-421): every three.ws MCP server.- Package source and tests: [packages/solana-memo-media-mcp](../packages/solana-memo-media-mcp/README.md).----<a id="sec-414"></a>+<a id="sec-418"></a>> **Source:** `docs/mcp-studio.md` · [↑ table of contents](#table-of-contents)@@ -105095,7 +105427,7 @@ generation quota:|---|---|---|| `https://three.ws/api/mcp-studio` | all fifteen tools (the 3D tools, the asset catalog, the persona tools), both widgets | any MCP host, including a ChatGPT developer-mode connector || `https://three.ws/api/mcp-chatgpt` | the nine 3D tools and the model viewer | the ChatGPT plugin directory listing |-| `https://three.ws/api/mcp-grok` | all fifteen tools, every call answered within 40 s, quota per MCP session | Grok Bot, Grok connectors and the xAI Responses API ([guide](#sec-334)) |+| `https://three.ws/api/mcp-grok` | all fifteen tools, every call answered within 40 s, quota per MCP session | Grok Bot, Grok connectors and the xAI Responses API ([guide](#sec-338)) |The ChatGPT surface leaves out the three catalog tools, which keeps that listing's reviewed tool set unchanged, and the three persona tools, because their widgetframes the hosted embodiment page, which needs `frameDomains`. OpenAI's app@@ -105182,12 +105514,12 @@ store-clean responses (model URLs and job state only). The machine-readablecontract is the OpenAPI schema the platform serves at[`https://three.ws/.well-known/3d-studio-openapi.yaml`](../public/.well-known/3d-studio-openapi.yaml),which is what the custom GPT imports; the same endpoint is written up in prose in-the [API reference](#sec-124). Use the MCP connector above when you+the [API reference](#sec-125). Use the MCP connector above when youwant inline 3D widgets; the custom GPT covers plans without connector support.How AR rides both ChatGPT surfaces (the `arUrl` contract, the device-awarelauncher, living avatars, link unfurls) is documented end to end in-[AR in ChatGPT](#sec-186).+[AR in ChatGPT](#sec-187).## Tools@@ -105278,7 +105610,7 @@ tool call at any tier; see [Pending generations](#pending-generations-check_job)for how it is collected rather than lost.One naming collision worth knowing: the npm package `@three-ws/mcp-server`-([docs](#sec-417)) also ships a tool called `forge_free`. That is a different+([docs](#sec-421)) also ships a tool called `forge_free`. That is a differentserver with its own default (`draft`, stated in its own tool schema). Thedefault described here is the one for `https://three.ws/api/mcp-studio`.@@ -105304,9 +105636,9 @@ sculpts into 3D (the forge's image-generation step). The inline widget uses itas the model-viewer poster so the painted view shows while the GLB streams in,and the result narration links it for non-widget clients.-`arUrl` is the one-tap place-in-your-room link (see [AR in ChatGPT](#sec-186)).+`arUrl` is the one-tap place-in-your-room link (see [AR in ChatGPT](#sec-187)).Rigged avatars additionally carry `irlUrl`, the living-agent handoff into-[IRL](#sec-386), and the inline widget's AR button becomes **Bring it to life**.+[IRL](#sec-390), and the inline widget's AR button becomes **Bring it to life**.Every result also includes a `spatial` field, the open Spatial MCP artifact(`specs/SPATIAL_MCP.md`) so any Spatial-MCP renderer can display the model.@@ -105332,7 +105664,7 @@ still tell its user what fell back and why. A receipt that was still runningwhen the tool answered is completed by `check_job`. Refusals are receipted too(outcome `refused`, prompt not stored). The rig stage is verified by readingthe delivered file back, not by trusting the rigger. Full reference:-[Run receipts](#sec-623).+[Run receipts](#sec-630).### Links for agents that render no widget@@ -105347,7 +105679,7 @@ names:| `viewer_url` | `https://three.ws/viewer?src=<glb>&title=<title>`, the interactive viewer | open the model in any browser, or hand the user a link || `glb_url` | the model file itself | download it, re-host it, feed it to `rig_mesh` or `look_at_model` || `poster_png_url` | `https://three.ws/api/render/glb?glbUrl=<glb>&width=1024&height=1024`, a rendered 1024 px PNG (CDN-cached for a day) | attach a picture to a reply, a card or a markdown image |-| `embed_html` | the paste-ready snippet from the [embedding guide](#sec-259): `<agent-3d>` for an avatar, rigged model or persona, `<model-viewer>` for a prop, each with its script tag pinned to a version and integrity hash | put the model on a web page |+| `embed_html` | the paste-ready snippet from the [embedding guide](#sec-262): `<agent-3d>` for an avatar, rigged model or persona, `<model-viewer>` for a prop, each with its script tag pinned to a version and integrity hash | put the model on a web page |The same four lines open the text content, so a client that ignores`structuredContent` reads them first:@@ -105844,15 +106176,15 @@ Quick Look rather than a camera overlay (`api/_lib/ar-launch.js`).----<a id="sec-415"></a>+<a id="sec-419"></a>> **Source:** `docs/mcp-tools.md` · [↑ table of contents](#table-of-contents)# MCP Tools Catalog-three.ws ships several [MCP](#sec-417) servers: tool servers that AI assistants+three.ws ships several [MCP](#sec-421) servers: tool servers that AI assistants(Claude, ChatGPT, any MCP client) can call directly. One is free and 3D-only; the-others expose paid tools that settle per call in USDC over [x402](#sec-862). This+others expose paid tools that settle per call in USDC over [x402](#sec-877). Thispage explains how the servers are grouped and how the paid ones charge.> **Looking for a specific tool?** The complete, always-current list lives at@@ -105909,7 +106241,7 @@ the read-only studio helpers below.A free, non-crypto MCP server for the ChatGPT App Directory and any MCP client. Itexposes **only** 3D generation/inspection — no account, no payment, no token. See-[3D Studio MCP](#sec-414).+[3D Studio MCP](#sec-418).## Material Studio (hosted, free) — `/api/material-studio`@@ -105955,12 +106287,12 @@ Free studio helpers (no charge): `getting_started`, `generation_status`,`text_to_animation`, `inspect_model`, `optimize_model`, `save_avatar`, `export_ar`,`verify_provenance`, `grade_sim_readiness` (the physics grade: whether a solvercould use a GLB as a rigid body, and exactly what is wrong when it could not,-see [Simulation readiness](#sec-643); free so an agent can check ten+see [Simulation readiness](#sec-651); free so an agent can check tencandidates before paying for one), `x402_preflight` (asks any x402 seller'ssigned payability attestation whether it can actually settle before you pay it;free on purpose and permanently), the persona tools (`create_agent_persona`, `get_agent_persona`,`persona_say`, `persona_identity`, `persona_tip`, `persona_send`), and-`validate_spatial_response` (the [Spatial MCP](#sec-659) conformance gate).+`validate_spatial_response` (the [Spatial MCP](#sec-667) conformance gate).Every catalog tool is either priced or on this explicit free list; a test failsthe build if a new tool is neither.@@ -106005,9 +106337,9 @@ generation lane**; the rest are paid and quote their price in the| Server | File | Surface ||---|---|---|| Agent MCP | `api/mcp-agent.js` | Agent build/control tools. |-| Bazaar MCP | `api/mcp-bazaar.js` | x402 service discovery — see [x402 bazaar](#sec-416). |-| IBM MCP | `api/ibm-mcp.js` | watsonx / Granite integration — see [IBM](#sec-378). |-| pump.fun MCP | `api/pump-fun-mcp.js` | Launch/trade tools — see [Solana pump.fun](#sec-655). |+| Bazaar MCP | `api/mcp-bazaar.js` | x402 service discovery — see [x402 bazaar](#sec-420). |+| IBM MCP | `api/ibm-mcp.js` | watsonx / Granite integration — see [IBM](#sec-382). |+| pump.fun MCP | `api/pump-fun-mcp.js` | Launch/trade tools — see [Solana pump.fun](#sec-663). || Viewer Control | `api/chat/mcp.js` | Drives a live model viewer (wireframe, lighting, screenshots, load a model); tools in `api/_lib/viewer-mcp-tools.js`. |## $THREE only@@ -106019,16 +106351,16 @@ promote no specific token.## Related-- [MCP](#sec-417) overview · [3D Studio MCP](#sec-414) ·- [3D Studio (paid)](#sec-410) · [x402 bazaar](#sec-416)-- [x402 paid endpoints](#sec-854) — the same capabilities over REST.-- [MCP tool safety](#sec-412) - what each tool's safety annotations mean,+- [MCP](#sec-421) overview · [3D Studio MCP](#sec-418) ·+ [3D Studio (paid)](#sec-414) · [x402 bazaar](#sec-420)+- [x402 paid endpoints](#sec-869) — the same capabilities over REST.+- [MCP tool safety](#sec-416) - what each tool's safety annotations mean,and the build check that verifies them against the code.- [The full catalog](/mcp-tools) - every tool, searchable by safety and price.----<a id="sec-416"></a>+<a id="sec-420"></a>> **Source:** `docs/mcp-x402-bazaar.md` · [↑ table of contents](#table-of-contents)@@ -106156,7 +106488,7 @@ npx @modelcontextprotocol/inspector http://localhost:3000/api/mcp-bazaar----<a id="sec-417"></a>+<a id="sec-421"></a>> **Source:** `docs/mcp.md` · [↑ table of contents](#table-of-contents)@@ -106238,13 +106570,13 @@ There are two kinds. **Hosted remote servers** run over Streamable HTTP with not| three.ws | `/api/mcp` | Avatars, glTF/GLB validation, agent data, memory, copy-trading, a connected home (this page) || 3D Studio | `/api/mcp-3d` | Paid text/image→3D, rigging, retexture, optimization || 3D Studio (free) | `/api/mcp-studio` | Free text/image→3D and rigged avatars; `get_job` status, `idempotency_key` retries and progress notifications ([details](mcp-studio.md#long-jobs-and-safe-retries-get_job-idempotency_key-progress)) |-| Grok | `/api/mcp-grok` | One connector URL for Grok Bot and the xAI API: the free studio with no widgets, plus your agents, memory and skills once signed in (OAuth 2.1 or a connector key). Never lists a value-moving tool. See [three.ws for Grok](#sec-334) |+| Grok | `/api/mcp-grok` | One connector URL for Grok Bot and the xAI API: the free studio with no widgets, plus your agents, memory and skills once signed in (OAuth 2.1 or a connector key). Never lists a value-moving tool. See [three.ws for Grok](#sec-338) || Agent wallet | `/api/mcp-agent` | The agent's custodial wallet: balance, find + pay services, and `monetize_endpoint` || x402 Bazaar | `/api/mcp-bazaar` | Discover and price paid agent services across the facilitator network || pump.fun | `/api/pump-fun-mcp` | Free pump.fun + Solana token tools; `get_new_tokens` and `get_trending_tokens` read the live pump.fun feed with no indexer needed; `pumpfun_upload_metadata` needs a key || IBM x402 | `/api/ibm-mcp` | Pay-per-use IBM Granite AI |-The free studio also has two client-tuned doors on the same tools and quota: `/api/mcp-chatgpt` for the ChatGPT plugin directory, and `/api/mcp-grok` for Grok Bot, Grok connectors and the xAI API, where no call hangs, the quota follows your MCP session and, with OAuth 2.1 or an API key (`/api/mcp-grok?auth=oauth`), the account's agent, memory, skill and avatar tools are added. It never lists a wallet or payment tool. See [three.ws for Grok](#sec-334) and the [Grok Bot connector reference](#sec-333).+The free studio also has two client-tuned doors on the same tools and quota: `/api/mcp-chatgpt` for the ChatGPT plugin directory, and `/api/mcp-grok` for Grok Bot, Grok connectors and the xAI API, where no call hangs, the quota follows your MCP session and, with OAuth 2.1 or an API key (`/api/mcp-grok?auth=oauth`), the account's agent, memory, skill and avatar tools are added. It never lists a wallet or payment tool. See [three.ws for Grok](#sec-338) and the [Grok Bot connector reference](#sec-337).**Forty-two install-and-run servers** on npm under the `@three-ws` scope, each running over stdio with one command:@@ -106335,10 +106667,11 @@ Ready-to-submit listing packages for each directory, plus the canonical metadataDeep dives — every tool, argument, env var, and example:-- **Hosted remote:** [3D Studio (free)](#sec-414) · [Grok Bot connector](#sec-333) · [3D Studio (paid)](#sec-410) · [Agent wallet](#sec-411) · [x402 Bazaar](#sec-416) · [IBM x402](#sec-377)-- **Runs against your machine:** [Blender MCP](#sec-167) drives the Blender installed on your own computer, headless: inspect, convert, render and script 3D files, plus text-to-3D straight into a scene.-- **Install-and-run:** each npm server ships its usage guide (tools, arguments, env vars, examples) in its package README on [npmjs.com/org/three-ws](https://www.npmjs.com/org/three-ws). The [MCP Tools Catalog](#sec-415) maps every tool to its server and price.-- **Solana Memo Media:** [full guide](#sec-413) for validating and rendering data URI images embedded in SPL Memo instructions.+- **Hosted remote:** [3D Studio (free)](#sec-418) · [Grok Bot connector](#sec-337) · [3D Studio (paid)](#sec-414) · [Agent wallet](#sec-415) · [x402 Bazaar](#sec-420) · [IBM x402](#sec-381)+- **Runs against your machine:** [Blender MCP](#sec-168) drives the Blender installed on your own computer, headless: inspect, convert, render and script 3D files, plus text-to-3D straight into a scene.+- **Install-and-run:** each npm server ships its usage guide (tools, arguments, env vars, examples) in its package README on [npmjs.com/org/three-ws](https://www.npmjs.com/org/three-ws). The [MCP Tools Catalog](#sec-419) maps every tool to its server and price.+- **Solana Memo Media:** [full guide](#sec-417) for validating and rendering data URI images embedded in SPL Memo instructions.+- **Agent framework packages:** [Vercel AI SDK tools](../packages/ai-sdk/README.md) (`@three-ws/ai-sdk`), [LangChain JS tools](../packages/langchain/README.md) (`@three-ws/langchain`), and [Google ADK](#sec-334) via `MCPToolset` against the free studio server.---@@ -106515,7 +106848,7 @@ This uses the standalone npm package, which handles OAuth locally. The `--url` f### Grok Bot-Send Grok Bot: `Add a custom MCP server called three-ws at https://three.ws/api/mcp-grok`. Transport Streamable HTTP, authentication none for the free studio, or OAuth 2.1 at `https://three.ws/api/mcp-grok?auth=oauth` to add your agent tools. Setup per sign-in mode, limits, jobs and troubleshooting: [Grok Bot connector reference](#sec-333).+Send Grok Bot: `Add a custom MCP server called three-ws at https://three.ws/api/mcp-grok`. Transport Streamable HTTP, authentication none for the free studio, or OAuth 2.1 at `https://three.ws/api/mcp-grok?auth=oauth` to add your agent tools. Setup per sign-in mode, limits, jobs and troubleshooting: [Grok Bot connector reference](#sec-337).`tests/mcp-directory.test.js` pins the `clients` block's shape, checks that every Grok Bot field matches what the [/connect](/connect?client=grok) card renders, and resolves every three.ws URL in the file against the production route table, so a recommended server or setup link that stops being served fails the test suite.@@ -106595,13 +106928,13 @@ If the first call times out and the task retries it, the retry answers with theAll tools return `{ content: [{ type, text }], structuredContent: {...} }`. On error, `isError: true` is set and `content[0].text` contains the message.-`search_catalog`, `get_catalog_item`, and `get_item_source` are free and need no API key or payment: start there. How you reach them without an account depends on the client. A plain JSON-RPC `tools/call` to `https://three.ws/api/mcp` (curl, `fetch`, any script that does not speak the MCP transport) is served anonymously. An MCP client that connects to `/api/mcp` is a different case: the server answers its `initialize` with `401` so the client starts three.ws sign-in (see [Authentication](#authentication)), because most tools on this server act on an account. To use the catalog from an MCP client with no account, connect it to the free studio server, `https://three.ws/api/mcp-studio`, which serves the same three tools keyless ([docs/mcp-studio.md](#sec-414)). The tools below them are the core avatar, validation, minting, and market-data set. The server registers more beyond this page (memory `remember`/`recall`/`forget`, `register_agent`, oracle and pump.fun intel reads, trader analytics, copy-trading); call `tools/list` for the complete live catalog with schemas.+`search_catalog`, `get_catalog_item`, and `get_item_source` are free and need no API key or payment: start there. How you reach them without an account depends on the client. A plain JSON-RPC `tools/call` to `https://three.ws/api/mcp` (curl, `fetch`, any script that does not speak the MCP transport) is served anonymously. An MCP client that connects to `/api/mcp` is a different case: the server answers its `initialize` with `401` so the client starts three.ws sign-in (see [Authentication](#authentication)), because most tools on this server act on an account. To use the catalog from an MCP client with no account, connect it to the free studio server, `https://three.ws/api/mcp-studio`, which serves the same three tools keyless ([docs/mcp-studio.md](#sec-418)). The tools below them are the core avatar, validation, minting, and market-data set. The server registers more beyond this page (memory `remember`/`recall`/`forget`, `register_agent`, oracle and pump.fun intel reads, trader analytics, copy-trading); call `tools/list` for the complete live catalog with schemas.---### `get_whitelist`, `add_to_whitelist`, `remove_from_whitelist`-Manage the [destination whitelist](#sec-242) of an agent you own. `get_whitelist` (read) returns entries with status, labels, caps and seconds until active. `add_to_whitelist` (write) takes `agent_id`, `address`, optional `label` and caps, and only **proposes** the address: it stays inert until the owner approves it in the app with step-up, then serves the cooldown. `remove_from_whitelist` (write) removes an address at once. No tool can approve or activate an address.+Manage the [destination whitelist](#sec-243) of an agent you own. `get_whitelist` (read) returns entries with status, labels, caps and seconds until active. `add_to_whitelist` (write) takes `agent_id`, `address`, optional `label` and caps, and only **proposes** the address: it stays inert until the owner approves it in the app with step-up, then serves the cooldown. `remove_from_whitelist` (write) removes an address at once. No tool can approve or activate an address.---@@ -107094,7 +107427,7 @@ Returns `holder`, `media` (`glb_url`, `image_url`, `viewer_url`, `viewer_live`),### `domain_search`, `domain_check`, `domain_pricing`, `domain_register_quote`, `domain_register`, `domain_status`, `domain_connect`, `domain_connect_status`-Search, price, check and register web domains through Google Cloud Domains, paid from credits, and serve an agent's public page on a registered domain. `domain_register` is a financial-tier tool: it needs the `quote_id` from `domain_register_quote`, `confirm_spend: true`, `expected_price_usd` and an `idempotency_key`. Full flow, limits and the registrar quota: [docs/domains.md](#sec-251).+Search, price, check and register web domains through Google Cloud Domains, paid from credits, and serve an agent's public page on a registered domain. `domain_register` is a financial-tier tool: it needs the `quote_id` from `domain_register_quote`, `confirm_spend: true`, `expected_price_usd` and an `idempotency_key`. Full flow, limits and the registrar quota: [docs/domains.md](#sec-254).### `agent_mail_get_address`, `agent_mail_quote`, `agent_mail_create`, `agent_mail_send`, `agent_mail_reply`, `agent_mail_list`, `agent_mail_read`, `agent_mail_search`, `agent_mail_delete`@@ -107121,13 +107454,13 @@ Turn an avatar or on-chain agent **you own** into a holder-only interactive 3D e}```-The `structuredContent` returns `gate_id`, `asset_id`, `gate` (`mint`, `min_amount`, `chain`), and `embed_snippet` — a ready-to-paste `<script>` + `<three-d>` tag. See [Token-gated 3D embeds](#sec-681) for the full verification flow, the anti-abuse token/rate-limit design, and how visitors unlock the embed.+The `structuredContent` returns `gate_id`, `asset_id`, `gate` (`mint`, `min_amount`, `chain`), and `embed_snippet` — a ready-to-paste `<script>` + `<three-d>` tag. See [Token-gated 3D embeds](#sec-689) for the full verification flow, the anti-abuse token/rate-limit design, and how visitors unlock the embed.---### `crypto_data`-Call any endpoint in the free [Crypto Data API](#sec-124) (the same aggregator behind `GET /api/v1/x/*`: DEX pairs, CoinGecko/DefiLlama market data, Jupiter Solana prices and swap quotes, direct Solana RPC reads) as an MCP tool call. The tool description is generated from the live provider registry at call time, so it always lists exactly the provider/endpoint pairs registered on this deployment — nothing hand-enumerated to drift out of date.+Call any endpoint in the free [Crypto Data API](#sec-125) (the same aggregator behind `GET /api/v1/x/*`: DEX pairs, CoinGecko/DefiLlama market data, Jupiter Solana prices and swap quotes, direct Solana RPC reads) as an MCP tool call. The tool description is generated from the live provider registry at call time, so it always lists exactly the provider/endpoint pairs registered on this deployment — nothing hand-enumerated to drift out of date.```json{@@ -107142,7 +107475,7 @@ Call any endpoint in the free [Crypto Data API](#sec-124) (the same aggregator b}```-An unknown `provider`/`endpoint` pair returns an error result listing every valid pair. A registered endpoint marked free runs within the same per-IP quota the REST free lane enforces — no wallet needed. An endpoint with no free tier, or a free quota you've exhausted, returns a JSON-RPC `-32402` error naming the exact REST URL and USDC price to pay via [x402](#sec-862) — never a second, MCP-only payment flow.+An unknown `provider`/`endpoint` pair returns an error result listing every valid pair. A registered endpoint marked free runs within the same per-IP quota the REST free lane enforces — no wallet needed. An endpoint with no free tier, or a free quota you've exhausted, returns a JSON-RPC `-32402` error naming the exact REST URL and USDC price to pay via [x402](#sec-877) — never a second, MCP-only payment flow.```bash# Equivalent to: GET /api/v1/x/dexscreener/token?addresses=FeMbDoX7R1Psc4GEcvJdsbNbZA3bfztcyDCatJVJpump@@ -107185,7 +107518,7 @@ Returns `{ mint, sources: [...], dexscreener?, jupiter?, solana?, skipped: [...]### `sentiment_scout`-Sourced pump.fun momentum candidates from the [Sentiment Scout](#sec-634). Each candidate carries a 0-100 `momentum_score` with its parts, evidence lines (`volume_spike`, `fresh_buyers`, `smart_money`, `graduation_approach`, `social_mention`, `paid_signal`, `news_match`) and one `caution` line. Every evidence line has a `source` URL, an `at` timestamp, and, for social or paid claims, `checked_against`: the on-chain facts read in the same run. Unreadable sources are listed in `unavailable`, never estimated. Read-only; never trades.+Sourced pump.fun momentum candidates from the [Sentiment Scout](#sec-641). Each candidate carries a 0-100 `momentum_score` with its parts, evidence lines (`volume_spike`, `fresh_buyers`, `smart_money`, `graduation_approach`, `social_mention`, `paid_signal`, `news_match`) and one `caution` line. Every evidence line has a `source` URL, an `at` timestamp, and, for social or paid claims, `checked_against`: the on-chain facts read in the same run. Unreadable sources are listed in `unavailable`, never estimated. Read-only; never trades.```json{@@ -107278,7 +107611,7 @@ Fetch the public wardrobe catalog: every published garment manifest (id, slot, n### Importing external skills-Six tools install `SKILL.md` skills from public registries (the three.ws community repository, the public Anthropic agent skills repository, skills published on three.ws, and any GitHub repository or manifest the owner added) onto an agent the caller owns. The full model, scanner rules and spend gate are in [Skill import](#sec-647).+Six tools install `SKILL.md` skills from public registries (the three.ws community repository, the public Anthropic agent skills repository, skills published on three.ws, and any GitHub repository or manifest the owner added) onto an agent the caller owns. The full model, scanner rules and spend gate are in [Skill import](#sec-655).| Tool | Tier | Scope | Input ||---|---|---|---|@@ -107413,7 +107746,7 @@ or `floor_id`; every target is resolved to concrete entities before the gate see}```-Full walkthrough: [Connect your home](#sec-716). To run a house from your+Full walkthrough: [Connect your home](#sec-724). To run a house from yourown machine with no three.ws account at all, use[`@three-ws/home-mcp`](../packages/home-mcp/README.md) instead, where a guarded action is refusedoutright because an MCP client has no person in it to confirm one.@@ -107506,7 +107839,7 @@ launch that passes every filter you set:is missing on a launch counts as a miss, never a silent pass. Every alert reaches the owner throughthe platform notification fan-out: the bell, Web Push to every subscribed device, the iOS app, andevery Telegram or Discord chat paired for notifications, each gated by the "alerts" category of the-[preference center](#sec-442). The other kinds (`graduation`, `new_mint`, `price_above`,+[preference center](#sec-446). The other kinds (`graduation`, `new_mint`, `price_above`,`price_below`, `whale_buy`, `market_price`) are the same as on `/api/alerts/rules`. Deleting a ruleis irreversible, so `alert_rule_delete` needs `alert_rule_list` with that `rule_id` first, then its`preview_id` and `confirm_delete: true`.@@ -107536,7 +107869,7 @@ collateral, up to 1000x and no funding. They need no sign-in, and none of them shard-bust price where the whole margin is lost, the minimum-size and capacity checks, and what awinning close actually pays across eight price moves after Papertrade's deadband, impact haircut andwin fee. `papertrade_account` values any wallet's open positions at the live mid. The same data is on-`GET /api/papertrade`. Full guide: [Papertrade](#sec-473).+`GET /api/papertrade`. Full guide: [Papertrade](#sec-478).---@@ -108166,7 +108499,7 @@ three.ws examples repo, so it is installed, run, and link-checked before every r----<a id="sec-418"></a>+<a id="sec-422"></a>> **Source:** `docs/media-api.md` · [↑ table of contents](#table-of-contents)@@ -108828,7 +109161,7 @@ library: this endpoint validates the cursors strictly, so a malformedof being coerced into a page. The manifest is served with`access-control-allow-origin: *`, so a studio embedded on another origin canrender the object tray from it (the objects themselves already load cross-origin-through `/cdn/<key>`). See [the object library doc](#sec-455)+through `/cdn/<key>`). See [the object library doc](#sec-459)for the full parameter table.### Response@@ -109188,13 +109521,13 @@ curl -s 'https://three.ws/api/forge-rembg?job=JOB_ID'## Related- [3D API](#sec-001) - the core free text-to-3D lane, model inspection, and the paid Forge Pro tiers-- [Image to 3D](#sec-379) - the photo-input reconstruction product these front doors feed-- [Voice Lab](#sec-796) - voice cloning and synthesis, the other half of the avatar voice loop-- [API Reference](#sec-124) - the full three.ws HTTP API surface+- [Image to 3D](#sec-383) - the photo-input reconstruction product these front doors feed+- [Voice Lab](#sec-807) - voice cloning and synthesis, the other half of the avatar voice loop+- [API Reference](#sec-125) - the full three.ws HTTP API surface----<a id="sec-419"></a>+<a id="sec-423"></a>> **Source:** `docs/memetic-launcher.md` · [↑ table of contents](#table-of-contents)@@ -109299,12 +109632,12 @@ A POST with no body at all is valid and reads back as an empty patch, so## Related surfaces- [/launches](https://three.ws/launches) — every coin launched through three.ws, including yours.-- [docs/pump-launcher.md](#sec-561) — the x402 paid one-shot launcher (`/api/x402/pump-launch`), a different surface: one coin per paid call, platform-fronted.+- [docs/pump-launcher.md](#sec-568) — the x402 paid one-shot launcher (`/api/x402/pump-launch`), a different surface: one coin per paid call, platform-fronted.- `api/_lib/launcher-engine.js` — the shared engine both scopes run on (cron: `/api/cron/launcher-tick`).----<a id="sec-420"></a>+<a id="sec-424"></a>> **Source:** `docs/memory.md` · [↑ table of contents](#table-of-contents)@@ -109716,7 +110049,7 @@ store described above and each revocable by deleting exactly what it wrote:----<a id="sec-421"></a>+<a id="sec-425"></a>> **Source:** `docs/meta-allocator.md` · [↑ table of contents](#table-of-contents)@@ -109810,14 +110143,14 @@ plan `source` is `"empty"` with a helpful message instead of an error.## Related-- [Trader Card & the claim-your-wallet wedge](#sec-686)-- [The trading surfaces](#sec-695) · [/vaults](https://three.ws/vaults) (copy-trade with custody guardrails)-- [Clip Director: every trade becomes content](#sec-192)-- [Financial controls & custody guardrails](#sec-306)+- [Trader Card & the claim-your-wallet wedge](#sec-694)+- [The trading surfaces](#sec-703) · [/vaults](https://three.ws/vaults) (copy-trade with custody guardrails)+- [Clip Director: every trade becomes content](#sec-193)+- [Financial controls & custody guardrails](#sec-309)----<a id="sec-422"></a>+<a id="sec-426"></a>> **Source:** `docs/mint-mark.md` · [↑ table of contents](#table-of-contents)@@ -109943,13 +110276,13 @@ No other mint should appear in tests, fixtures, or documentation.## Related-- [Solana agents](#sec-657) — agent wallet management and on-chain interactions-- [Solana pump.fun signals](#sec-655) — pump.fun live feed integration-- [ERC-8004](#sec-263) — on-chain agent registry (uses the same brand metadata builder)+- [Solana agents](#sec-665) — agent wallet management and on-chain interactions+- [Solana pump.fun signals](#sec-663) — pump.fun live feed integration+- [ERC-8004](#sec-266) — on-chain agent registry (uses the same brand metadata builder)----<a id="sec-423"></a>+<a id="sec-427"></a>> **Source:** `docs/minted.md` · [↑ table of contents](#table-of-contents)@@ -109957,7 +110290,7 @@ No other mint should appear in tests, fixtures, or documentation.[three.ws/minted](https://three.ws/minted) is the live, public gallery of every generated or owned avatar that a creator chose to mint as a **Metaplex Core NFT** through three.ws. It is the NFT counterpart of the `/launches` coin directory: real on-chain property, listed the moment it mints. Every card renders the actual model in a live, auto-rotating 3D viewer (not a flat thumbnail), and every asset carries baked provenance and an enforced, capped creator royalty. Minting is always opt-in: the free text-to-3D lane never mints anything on its own.-This doc covers the gallery surface and the mint flow as a user-facing feature. The provenance internals live in their own docs: [content credentials for AI-generated models](#sec-556) (signed credentials, Solana anchoring, the free verify endpoint) and [the three.ws mint mark](#sec-422) (the `3ws` address branding on coin launches).+This doc covers the gallery surface and the mint flow as a user-facing feature. The provenance internals live in their own docs: [content credentials for AI-generated models](#sec-563) (signed credentials, Solana anchoring, the free verify endpoint) and [the three.ws mint mark](#sec-426) (the `3ws` address branding on coin launches).## The gallery@@ -109989,7 +110322,7 @@ curl "https://three.ws/api/v1/tokenized/launches?network=mainnet&offset=0&limit=## How a mint works-Minting runs through the `mint_3d_asset` tool on the [3D Studio MCP server](#sec-417). It is priced per call via x402 (USDC); an OAuth bearer token bypasses payment. A creator supplies:+Minting runs through the `mint_3d_asset` tool on the [3D Studio MCP server](#sec-421). It is priced per call via x402 (USDC); an OAuth bearer token bypasses payment. A creator supplies:- **The model:** an owned `avatar_id`, or any absolute `glb_url`.- **The recipient:** an explicit `owner_wallet` (base58), or the OAuth-linked Solana wallet by default.@@ -110012,7 +110345,7 @@ Every mint carries its provenance twice:- **In the NFT metadata itself:** creator, prompt, generation model and provider, parent lineage, and timestamp travel with the asset wherever it goes.- **As a signed record on the platform's append-only agent-actions ledger** (when the source avatar has a provisioned agent to sign as): an independently verifiable entry, referenced in the mint response and queryable via the MCP action tools. This write is best-effort and never blocks a mint that already succeeded on-chain.-For how signed credentials, canonical hashing, and on-chain anchoring work under the hood, read [provenance.md](#sec-556). For the `3ws` address mark that brands coin launches, read [mint-mark.md](#sec-422).+For how signed credentials, canonical hashing, and on-chain anchoring work under the hood, read [provenance.md](#sec-563). For the `3ws` address mark that brands coin launches, read [mint-mark.md](#sec-426).### Remix royalties: paid the moment a remix mints@@ -110026,14 +110359,14 @@ The companion MCP tool `get_3d_asset_onchain` resolves any Core mint address to## Related-- [Verifiable 3D provenance](#sec-556): signed content credentials and free verification for generated models-- [The three.ws mint mark](#sec-422): the `3ws` address brand on coin launches-- [MCP servers](#sec-417): the `mint_3d_asset` and `get_3d_asset_onchain` tools-- [Custody you can verify](#sec-232): the wallet rails behind agent-held assets+- [Verifiable 3D provenance](#sec-563): signed content credentials and free verification for generated models+- [The three.ws mint mark](#sec-426): the `3ws` address brand on coin launches+- [MCP servers](#sec-421): the `mint_3d_asset` and `get_3d_asset_onchain` tools+- [Custody you can verify](#sec-233): the wallet rails behind agent-held assets----<a id="sec-424"></a>+<a id="sec-428"></a>> **Source:** `docs/mobile-launch/README.md` · [↑ table of contents](#table-of-contents)@@ -110043,28 +110376,28 @@ Five long-form articles announcing three.ws as three native apps (Solana Seeker| File | Venue | Angle || --- | --- | --- |-| [x-article.md](#sec-429) | X long-form Article from @trythreews | Community and Seeker owners. Narrative, founder voice, the full $THREE section with the contract address. |-| [coinmarketcap-article.md](#sec-426) | CoinMarketCap Community | Crypto-native reader. Ownership, the x402 economy, agent wallets, the launchpad, the full $THREE section. H2/H3 only and no tables, which is all the CMC editor supports. |-| [aws-builder-center-article.md](#sec-425) | AWS Builder Center (@threews) | Engineers with a web product being asked for an app. Real source for every piece: MWA session persistence, Seeker Genesis Token verification, the share-target worker, deep-link routing, the widget token, the AWS SDK v3 S3 client, the Marketplace front door. |-| [nvidia-forum-article.md](#sec-428) | NVIDIA Developer Forums showcase | GPU operators. The lanes on L4 and Blackwell, the memory ceilings, the NIM models around the generator, on-device gating before the GPU. |-| [ibm-community-article.md](#sec-427) | IBM Community, Three.ws User Group blog | Developers running Granite on watsonx.ai as an agent brain. Every Granite surface, the pay-per-call path, the trust layer. |+| [x-article.md](#sec-433) | X long-form Article from @trythreews | Community and Seeker owners. Narrative, founder voice, the full $THREE section with the contract address. |+| [coinmarketcap-article.md](#sec-430) | CoinMarketCap Community | Crypto-native reader. Ownership, the x402 economy, agent wallets, the launchpad, the full $THREE section. H2/H3 only and no tables, which is all the CMC editor supports. |+| [aws-builder-center-article.md](#sec-429) | AWS Builder Center (@threews) | Engineers with a web product being asked for an app. Real source for every piece: MWA session persistence, Seeker Genesis Token verification, the share-target worker, deep-link routing, the widget token, the AWS SDK v3 S3 client, the Marketplace front door. |+| [nvidia-forum-article.md](#sec-432) | NVIDIA Developer Forums showcase | GPU operators. The lanes on L4 and Blackwell, the memory ceilings, the NIM models around the generator, on-device gating before the GPU. |+| [ibm-community-article.md](#sec-431) | IBM Community, Three.ws User Group blog | Developers running Granite on watsonx.ai as an agent brain. Every Granite surface, the pay-per-call path, the trust layer. |## Facts to know before posting-- **Store status is written as live in all five, on the owner's instruction (2026-09-01).** As of writing, [seeker-app.md](#sec-629) records the Solana dApp Store release as approved and live (v1.0.0, submitted 2026-08-28), [solana-mobile/publish-play/README.md](../solana-mobile/publish-play/README.md) records the Google Play track as closed testing, and [ios-app.md](#sec-385) records the iOS app as in-repo and not yet submitted. Post each article only once its store claims are true; the copy does not hedge, so it will read as false if posted early.-- **The iOS widget and push are described as next, not shipped.** Android and Windows 11 glance widgets are live ([native-widgets.md](#sec-440)); the WidgetKit extension and the APNs path are roadmap.-- **Partner designations are exact and must survive edits.** "OpenAI Select Partner", "member of NVIDIA Inception" (never "NVIDIA partner"), "IBM Business Partner" with the public-showcase caveat, "AWS Partner" with the Marketplace listing described as coming, "member of Google Cloud for Web3 Startups". The rules are in [partners.md](#sec-474).-- **The IBM and NVIDIA pieces deliberately carry no token contract address.** [ibm.md](#sec-378) sets the user group's content rule (standalone developer content, no crypto-cluster posts), and the NVIDIA venue is a developer showcase. Both describe the on-chain identity and x402 layers as architecture. The X and CoinMarketCap pieces carry the full $THREE section.-- **Numbers are as of late August 2026** and come from [the-first-19-weeks.md](#sec-676) and [three-thesis.md](#sec-678). Refresh them from those two files before a later posting.-- **Posting is owner-gated** (external-channel gate in [CLAUDE.md](../CLAUDE.md)). When an article goes live, record its canonical URL here, add it to `data/rss/items.json`, and log it in `data/changelog.json` with the `docs` tag, following the checklist in [aws-builder-center.md](#sec-162).+- **Store status is written as live in all five, on the owner's instruction (2026-09-01).** As of writing, [seeker-app.md](#sec-636) records the Solana dApp Store release as approved and live (v1.0.0, submitted 2026-08-28), [solana-mobile/publish-play/README.md](../solana-mobile/publish-play/README.md) records the Google Play track as closed testing, and [ios-app.md](#sec-389) records the iOS app as in-repo and not yet submitted. Post each article only once its store claims are true; the copy does not hedge, so it will read as false if posted early.+- **The iOS widget and push are described as next, not shipped.** Android and Windows 11 glance widgets are live ([native-widgets.md](#sec-444)); the WidgetKit extension and the APNs path are roadmap.+- **Partner designations are exact and must survive edits.** "OpenAI Select Partner", "member of NVIDIA Inception" (never "NVIDIA partner"), "IBM Business Partner" with the public-showcase caveat, "AWS Partner" with the Marketplace listing described as coming, "member of Google Cloud for Web3 Startups". The rules are in [partners.md](#sec-480).+- **The IBM and NVIDIA pieces deliberately carry no token contract address.** [ibm.md](#sec-382) sets the user group's content rule (standalone developer content, no crypto-cluster posts), and the NVIDIA venue is a developer showcase. Both describe the on-chain identity and x402 layers as architecture. The X and CoinMarketCap pieces carry the full $THREE section.+- **Numbers are as of late August 2026** and come from [the-first-19-weeks.md](#sec-684) and [three-thesis.md](#sec-686). Refresh them from those two files before a later posting.+- **Posting is owner-gated** (external-channel gate in [CLAUDE.md](../CLAUDE.md)). When an article goes live, record its canonical URL here, add it to `data/rss/items.json`, and log it in `data/changelog.json` with the `docs` tag, following the checklist in [aws-builder-center.md](#sec-163).## Sources-The apps: [seeker-app.md](#sec-629), [ios-app.md](#sec-385), [native-widgets.md](#sec-440), [glance.md](#sec-326), [solana-mobile/README.md](../solana-mobile/README.md), [ios/README.md](../ios/README.md). The platform: [STRUCTURE.md](../STRUCTURE.md), [how-it-works.md](#sec-351), [forge-pipeline.md](#sec-311), [selfie-to-avatar.md](#sec-633), [ar.md](#sec-129), [irl.md](#sec-386), [x402.md](#sec-862), [onchain-agents.md](#sec-458), [hold-to-access.md](#sec-339). Partners and models: [partners.md](#sec-474), [nvidia-models.md](#sec-450), [nvidia-inception.md](#sec-449), [ibm.md](#sec-378), [ibm-x402-mcp.md](#sec-377), [aws-builder-center.md](#sec-162). Earlier launch copy the tone follows: [marketing/seeker-launch/post.md](../marketing/seeker-launch/post.md), [marketing/android-launch/kit/post.md](../marketing/android-launch/kit/post.md).+The apps: [seeker-app.md](#sec-636), [ios-app.md](#sec-389), [native-widgets.md](#sec-444), [glance.md](#sec-329), [solana-mobile/README.md](../solana-mobile/README.md), [ios/README.md](../ios/README.md). The platform: [STRUCTURE.md](../STRUCTURE.md), [how-it-works.md](#sec-355), [forge-pipeline.md](#sec-314), [selfie-to-avatar.md](#sec-640), [ar.md](#sec-130), [irl.md](#sec-390), [x402.md](#sec-877), [onchain-agents.md](#sec-462), [hold-to-access.md](#sec-343). Partners and models: [partners.md](#sec-480), [nvidia-models.md](#sec-454), [nvidia-inception.md](#sec-453), [ibm.md](#sec-382), [ibm-x402-mcp.md](#sec-381), [aws-builder-center.md](#sec-163). Earlier launch copy the tone follows: [marketing/seeker-launch/post.md](../marketing/seeker-launch/post.md), [marketing/android-launch/kit/post.md](../marketing/android-launch/kit/post.md).----<a id="sec-425"></a>+<a id="sec-429"></a>> **Source:** `docs/mobile-launch/aws-builder-center-article.md` · [↑ table of contents](#table-of-contents)@@ -110376,7 +110709,7 @@ If you have a WebGL product and a "when is the app coming" question, the whole a----<a id="sec-426"></a>+<a id="sec-430"></a>> **Source:** `docs/mobile-launch/coinmarketcap-article.md` · [↑ table of contents](#table-of-contents)@@ -110712,7 +111045,7 @@ Open source: github.com/nirholas/three.ws----<a id="sec-427"></a>+<a id="sec-431"></a>> **Source:** `docs/mobile-launch/ibm-community-article.md` · [↑ table of contents](#table-of-contents)@@ -110838,7 +111171,7 @@ Docs: [three.ws/docs/ibm](https://three.ws/docs/ibm) · Live: [three.ws/ibm/hell----<a id="sec-428"></a>+<a id="sec-432"></a>> **Source:** `docs/mobile-launch/nvidia-forum-article.md` · [↑ table of contents](#table-of-contents)@@ -110972,7 +111305,7 @@ If you are serving generative 3D to phones, the two things I would tell you firs----<a id="sec-429"></a>+<a id="sec-433"></a>> **Source:** `docs/mobile-launch/x-article.md` · [↑ table of contents](#table-of-contents)@@ -111154,7 +111487,7 @@ Open source, all of it: github.com/nirholas/three.ws----<a id="sec-430"></a>+<a id="sec-434"></a>> **Source:** `docs/mocap-studio.md` · [↑ table of contents](#table-of-contents)@@ -111246,14 +111579,14 @@ what the page itself sends.## Related-- [Avatar Studio](#sec-150): build the avatar you drive here.+- [Avatar Studio](#sec-151): build the avatar you drive here.- [Animation Studio](#sec-100): body posing and keyframed motion, the complement to facial capture.- [Animations reference](#sec-101): how captured and authored motion fit the platform's clip registry.- [/create](https://three.ws/create): make or import the avatar to perform with.----<a id="sec-431"></a>+<a id="sec-435"></a>> **Source:** `docs/model-diff.md` · [↑ table of contents](#table-of-contents)@@ -111267,7 +111600,7 @@ Files you drop are read with the browser File API and compared in your tab. Noth**On this page:** [The problem](#the-problem-a-model-that-loads-and-never-moves) · [Reading the report](#reading-the-report) · [Severity](#severity) · [How matching works](#how-matching-works) · [What counts as a change](#what-counts-as-a-change) · [The viewer](#the-viewer) · [The API](#the-api) · [The CLI](#the-cli) · [The MCP tool](#the-mcp-tool) · [The library](#the-library)-Related: [Rig Doctor](#sec-617) answers whether a single rig will animate at all; Model Diff answers whether the rig you already shipped still will. [Asset pipeline](#sec-002) covers the conversion and optimization steps whose output this is built to check. The free [3D API](https://three.ws/api/3d) lists this endpoint alongside inspect and generate.+Related: [Rig Doctor](#sec-624) answers whether a single rig will animate at all; Model Diff answers whether the rig you already shipped still will. [Asset pipeline](#sec-002) covers the conversion and optimization steps whose output this is built to check. The free [3D API](https://three.ws/api/3d) lists this endpoint alongside inspect and generate.---@@ -111371,7 +111704,7 @@ The report distinguishes two kinds of geometry edit, because they mean different- *same vertex and triangle count, different vertex data*: usually a re-bake, a re-skin, or a transform applied in place- *vertex data rewritten*: a decimation, a remesh, or a different asset entirely-Underneath the combined geometry hash, three fields move independently so a caller can tell exactly which kind of edit happened: `topology` (vertex positions or the index buffer), `uv` (`TEXCOORD_0`/`TEXCOORD_1`), and `skinWeights` (`JOINTS_0`/`WEIGHTS_0`, the per-vertex skin binding, as distinct from the skeleton resource below). A material restyle that only calls glTF Material setters should never move any of the three; an edit that promises it won't can check that promise with `api/_lib/preserve-contract.js`, which runs this same diff and refuses to report success if a declared field changed. [Restyle Studio](#sec-616) and its part-edit tools (regenerate/swap via HoloPart) are the first two callers.+Underneath the combined geometry hash, three fields move independently so a caller can tell exactly which kind of edit happened: `topology` (vertex positions or the index buffer), `uv` (`TEXCOORD_0`/`TEXCOORD_1`), and `skinWeights` (`JOINTS_0`/`WEIGHTS_0`, the per-vertex skin binding, as distinct from the skeleton resource below). A material restyle that only calls glTF Material setters should never move any of the three; an edit that promises it won't can check that promise with `api/_lib/preserve-contract.js`, which runs this same diff and refuses to report success if a declared field changed. [Restyle Studio](#sec-623) and its part-edit tools (regenerate/swap via HoloPart) are the first two callers.### Skeletons@@ -111473,7 +111806,7 @@ npx @three-ws/glb-diff src/avatar.glb dist/avatar.glb --fail-on breaking}```-The tool returns the rendered text report as content and the full change set as `structuredContent`, so the agent can branch on `severity` without parsing prose. See [MCP integration](#sec-417) for connecting the server.+The tool returns the rendered text report as content and the full change set as `structuredContent`, so the agent can branch on `severity` without parsing prose. See [MCP integration](#sec-421) for connecting the server.---@@ -111519,7 +111852,7 @@ The same two files always produce the same change set, byte for byte, on any mac----<a id="sec-432"></a>+<a id="sec-436"></a>> **Source:** `docs/modly.md` · [↑ table of contents](#table-of-contents)@@ -111619,7 +111952,7 @@ result to your account from the Generate screen, and import free models fromthe three.ws CC0 library without leaving the app. The Publish node ships insideit, already signed in. Get it from[three.ws/forge-desktop](https://three.ws/forge-desktop); the full guide is-[Forge for desktop](#sec-309), and the source is+[Forge for desktop](#sec-312), and the source is[`apps/forge-desktop/`](../apps/forge-desktop/README.md).## Ideas from Modly, built into the platform@@ -111629,7 +111962,7 @@ it, already signed in. Get it fromor make it game-ready, in one run, like Modly's workflow editor but onthree.ws GPUs. For Each batches follow Modly's loop rules, and the "Your GPU(Modly)" engine runs a step on your own Modly. See- [Forge Workflows](#sec-312).+ [Forge Workflows](#sec-315).- **Mesh tools** on every finished model in the Forge and on `/m/:id`: repair,Taubin or Laplacian smoothing and decimation in a browser worker, with undo.See [Forge: mesh tools](forge.md#mesh-tools-repair-smooth-decimate).@@ -111637,7 +111970,7 @@ it, already signed in. Get it fromprint-ready STL or 3MF (upright, in millimetres, on the bed) from`/api/slicer/<id>/model.stl`. See[Forge: open in a slicer](forge.md#open-in-a-3d-printing-slicer) and the- [API reference](#sec-124).+ [API reference](#sec-125).## Developers@@ -111649,7 +111982,7 @@ it, already signed in. Get it from| Cloud extension | [integrations/modly/three-ws/](../integrations/modly/three-ws) | `python3 -m unittest discover -s integrations/modly/tests -p 'test_*.py'` || Publish node | [integrations/modly/three-ws-publish/](../integrations/modly/three-ws-publish) | see its README || Shared Python client | [integrations/_pyclient/](../integrations/_pyclient) | `python3 -m unittest discover -s integrations/_pyclient -p 'test_*.py'` |-| Desktop app | [apps/forge-desktop/](../apps/forge-desktop), guide [forge-desktop.md](#sec-309) | see its README |+| Desktop app | [apps/forge-desktop/](../apps/forge-desktop), guide [forge-desktop.md](#sec-312) | see its README || Mesh tools | [src/mesh-ops/](../src/mesh-ops) | `npx vitest run tests/mesh-ops.test.js` || Slicer handoff | [api/slicer/model.js](../api/slicer/model.js), [api/_lib/print/slicer.js](../api/_lib/print/slicer.js), [src/slicer-handoff.js](../src/slicer-handoff.js) | `npx vitest run tests/slicer-handoff.test.js` |@@ -111661,16 +111994,16 @@ lists every such file.## Related-- [Forge](#sec-313): the cloud generator these surfaces share-- [Workbench](#sec-804): a desktop-style workspace in the browser-- [Forge Workflows](#sec-312): the node builder at /forge/workflows-- [Forge for desktop](#sec-309): the desktop app built on Modly+- [Forge](#sec-316): the cloud generator these surfaces share+- [Workbench](#sec-817): a desktop-style workspace in the browser+- [Forge Workflows](#sec-315): the node builder at /forge/workflows+- [Forge for desktop](#sec-312): the desktop app built on Modly- [integrations/README.md](../integrations/README.md): Blender, ComfyUI and Modly plugins- [STRUCTURE.md](../STRUCTURE.md): where every surface lives----<a id="sec-433"></a>+<a id="sec-437"></a>> **Source:** `docs/money-feed.md` · [↑ table of contents](#table-of-contents)@@ -111684,7 +112017,7 @@ event lives.> Not to be confused with the **personal activity feed** on `/feed`> (`GET /api/users/me/feed`) — that one shows who created what and who followed-> whom, and is documented in [The social layer](#sec-654). This page is+> whom, and is documented in [The social layer](#sec-662). This page is> about value movement only. The two share a URL word ("feed") and nothing else.---@@ -111760,11 +112093,11 @@ spend-cap and policy engine before they are recorded (see| Producer | Ledger? | Ticker? | Domain record ||---|---|---|---|-| [Circulation engine](#sec-189) tips/payments/trades/buys | Yes | Trades/launches via pump feed | `circulation_actions` + domain table |-| [Marketplace](#sec-408) skill/asset purchase | Yes | `payment` / `sale` | `skill_purchases` / `asset_purchases` |-| [Coin launches](#sec-193) | Yes | `coin-buy` / `agent-deploy` | `pump_agent_mints` |+| [Circulation engine](#sec-190) tips/payments/trades/buys | Yes | Trades/launches via pump feed | `circulation_actions` + domain table |+| [Marketplace](#sec-412) skill/asset purchase | Yes | `payment` / `sale` | `skill_purchases` / `asset_purchases` |+| [Coin launches](#sec-194) | Yes | `coin-buy` / `agent-deploy` | `pump_agent_mints` || Sniper trades | Yes (`category: 'snipe'`) | — | `agent_sniper_positions` |-| [Autonomous x402 loop](#sec-140) | Yes (`category: 'x402'`) | — | `x402_autonomous_log` |+| [Autonomous x402 loop](#sec-141) | Yes (`category: 'x402'`) | — | `x402_autonomous_log` || x402 service payments | Yes | `payment` | — || [Agora](#sec-080) tasks | On settlement | `agora-*` | on-chain |@@ -111798,14 +112131,14 @@ The same bus powers surfaces that are not tickers at all:## Related-- [Circulation engine](#sec-189) — the largest producer of activity.-- [Autonomous x402 loop](#sec-140) — treasury-paid intel purchases.+- [Circulation engine](#sec-190) — the largest producer of activity.+- [Autonomous x402 loop](#sec-141) — treasury-paid intel purchases.- [Agent wallets](#sec-077) — how spends are gated before they're recorded.-- [x402 endpoints](#sec-854): the *other* direction: money paid **to** our endpoints (`x402_audit_log`), not agent spend.+- [x402 endpoints](#sec-869): the *other* direction: money paid **to** our endpoints (`x402_audit_log`), not agent spend.----<a id="sec-434"></a>+<a id="sec-438"></a>> **Source:** `docs/money-flow-map.md` · [↑ table of contents](#table-of-contents)@@ -112044,14 +112377,14 @@ covering it there. Keep the ordering discipline in `classifyRole`: a rule goes## Related-- [Money Pulse](#sec-433): the event stream these edges are aggregated from.-- [Circulation engine](#sec-189): what generates most of this+- [Money Pulse](#sec-437): the event stream these edges are aggregated from.+- [Circulation engine](#sec-190): what generates most of thisactivity.- [Agent economy volume](#sec-055): the per-agent totals, ranked.----<a id="sec-435"></a>+<a id="sec-439"></a>> **Source:** `docs/money-map.md` · [↑ table of contents](#table-of-contents)@@ -112062,8 +112395,8 @@ wallet receives each kind of payment, what share the platform keeps, and whichtreasury pays it forward. If you're adding a paid surface or auditing revenue,start here.-Companion docs: [x402 endpoints](#sec-854) (the paid endpoint catalog),-[Financial controls](#sec-306) (how settlements are recorded),+Companion docs: [x402 endpoints](#sec-869) (the paid endpoint catalog),+[Financial controls](#sec-309) (how settlements are recorded),[Solana signers runbook](../api/_lib/solana-signers.js) (thesigner/funder wallets and how to fund them).@@ -112155,7 +112488,7 @@ Every engine signs from its **own** keypair; a single **funding root** tops thossigners up with SOL when they run low, and does nothing else. Documented in full —encodings, minimum balances, guards, funding tool — in the[Solana signers runbook](../api/_lib/solana-signers.js) and the-[economy master](#sec-255) subsystem doc.+[economy master](#sec-258) subsystem doc.| Wallet | Role || ------ | ---- |@@ -112212,7 +112545,7 @@ The trade and launch fees are live at 1% (owner decision, 2026-09-16): everycustomer trade three.ws builds or signs pays it in the same transaction, andplatform-owned agents are exempt. The rest are a low/off demo curve; productiondeployments tune them to real unit economics. Detail, surfaces and disclosure:-[pump platform fee](#sec-562).+[pump platform fee](#sec-569).---@@ -112222,7 +112555,7 @@ deployments tune them to real unit economics. Detail, surfaces and disclosure:[ring catalog](../api/_lib/x402/ring-catalog.js), the single source of truth,across intel/oracle, agent/reputation, generation/3D, launch/naming/utility,club, avatar shop, and bazaars. Full list and prices:- [x402 endpoints](#sec-854).+ [x402 endpoints](#sec-869).- **Paid MCP tools** —- Main MCP ([api/mcp.js](../api/mcp.js), pricing `api/_lib/pump-pricing.js`):`mint_3d_asset` $0.25, `retexture_model` $0.10, `optimize_model` $0.05,@@ -112242,9 +112575,9 @@ deployments tune them to real unit economics. Detail, surfaces and disclosure:in the on-chain ASP record, not in repo code** — update it here if the ASPregistration changes.- **Marketplace skills** — agent skill marketplace over Solana Pay- ([api/marketplace/](../api/marketplace)); see [marketplace skills](#sec-783).+ ([api/marketplace/](../api/marketplace)); see [marketplace skills](#sec-792).- **Labor market** — bounty/escrow jobs with worker + author-royalty settlement; see- [labor market](#sec-393).+ [labor market](#sec-397).- **Other** — vanity bounties, forge REST ([api/x402/forge.js](../api/x402/forge.js)),subscriptions, credit deposits.@@ -112254,7 +112587,7 @@ deployments tune them to real unit economics. Detail, surfaces and disclosure:Engines that move money on their own (cron/worker driven) draw from the signerwallets, not the receivers — and each signer is kept funded by the-[economy master](#sec-255) via the `treasury-topup` cron (every 30 min,+[economy master](#sec-258) via the `treasury-topup` cron (every 30 min,allowlist-guarded, reserve/per-engine/per-run caps). Which wallet funds whichengine and minimum balances are in the[Solana signers runbook](../api/_lib/solana-signers.js). The@@ -112290,22 +112623,22 @@ Guardrails on outflow: the economy master is funder-only with reserve/per-transfper-run caps and a registry allowlist; the ring can only settle to allowlistedwallets (anti-drain gate); the sniper auto-funder moves money only for strategiesthat set `auto_fund_enabled = true` (default off). See-[financial-controls.md](#sec-306) for the full register.+[financial-controls.md](#sec-309) for the full register.## Related-- [Financial controls & audit register](#sec-306) — every ledger's integrity, reconciliation, retention, monitoring, and the ranked gap list.-- [x402 endpoints](#sec-854) — the paid endpoint catalog and price overrides.-- [x402 ring economy](#sec-857) — the internal recirculation loop.-- [Pump platform fee](#sec-562) — the pump trade fee detail.-- [Coin-launch wallets](#sec-785) — launch-time wallet flow.+- [Financial controls & audit register](#sec-309) — every ledger's integrity, reconciliation, retention, monitoring, and the ranked gap list.+- [x402 endpoints](#sec-869) — the paid endpoint catalog and price overrides.+- [x402 ring economy](#sec-872) — the internal recirculation loop.+- [Pump platform fee](#sec-569) — the pump trade fee detail.+- [Coin-launch wallets](#sec-794) — launch-time wallet flow.- [Creator revenue splits](../api/_lib/cosmetics-economy.js) — `recordSaleAndSplit`: the cosmetic split math and its real USDC payout.- [Agent wallet custody](#sec-077) — how custodial keys are held.- [Solana signers runbook](../api/_lib/solana-signers.js) — signer/funder wallets + funding.----<a id="sec-436"></a>+<a id="sec-440"></a>> **Source:** `docs/monitor.md` · [↑ table of contents](#table-of-contents)@@ -112431,7 +112764,7 @@ board a lie.avatar cam while it works- [Money Pulse](https://three.ws/pulse): the full event feed with filters andper-agent views-- [Money Flow Map](#sec-434): the topology behind the totals, who+- [Money Flow Map](#sec-438): the topology behind the totals, whopays whom- [Agent Economy Volume](https://three.ws/agent-economy-volume): the long-windowagent-to-agent hire ledger@@ -112439,7 +112772,7 @@ board a lie.----<a id="sec-437"></a>+<a id="sec-441"></a>> **Source:** `docs/motion-swap.md` · [↑ table of contents](#table-of-contents)@@ -112531,11 +112864,11 @@ its error state.- [/capture](https://three.ws/capture) — video → 3D point cloud (scene, not person)- [/animations](https://three.ws/animations) — the clip library the output format matches-- [docs/animations.md](#sec-101) · [docs/avatar-reconstruction.md](#sec-149)+- [docs/animations.md](#sec-101) · [docs/avatar-reconstruction.md](#sec-150)----<a id="sec-438"></a>+<a id="sec-442"></a>> **Source:** `docs/multi-agent.md` · [↑ table of contents](#table-of-contents)@@ -112878,7 +113211,7 @@ To extend this into a full turn-based scene, add a `brain` attribute to Mira wit----<a id="sec-439"></a>+<a id="sec-443"></a>> **Source:** `docs/native-launchpad.md` · [↑ table of contents](#table-of-contents)@@ -112888,7 +113221,7 @@ three.ws has always been able to launch a coin for an agent. Until now, every onThis document covers the second lane: **the native launchpad**, a coin launch that runs on a bonding curve three.ws configures and owns, and that is **quoted in $THREE**. Same launch button, same 3D agent identity attached to the coin, different economics underneath. The public page is [three.ws/three-launchpad](https://three.ws/three-launchpad).-Related surfaces: [the pump.fun lane](#sec-124) (`/api/pump/*`), [agent wallets](#sec-077) (custody), and [the launch page](https://three.ws/launch).+Related surfaces: [the pump.fun lane](#sec-125) (`/api/pump/*`), [agent wallets](#sec-077) (custody), and [the launch page](https://three.ws/launch).---@@ -113107,7 +113440,7 @@ Stated plainly, because a half-built feature that claims to be finished is worse----<a id="sec-440"></a>+<a id="sec-444"></a>> **Source:** `docs/native-widgets.md` · [↑ table of contents](#table-of-contents)@@ -113119,11 +113452,11 @@ on that agent. The system refreshes it in the background about every 30 minutes;have to open the app to see the number move.This page covers the native, operating-system widgets. The embeddable web widgets that put a-live 3D agent inside a web page are a different product: see [widgets.md](#sec-802).+live 3D agent inside a web page are a different product: see [widgets.md](#sec-814).## What the widget shows-Every platform renders the same card, the [Glance card](#sec-326):+Every platform renders the same card, the [Glance card](#sec-329):- the agent's avatar thumbnail (or a generated monogram when the avatar is private),- the agent's name and description,@@ -113136,7 +113469,7 @@ No widget host on any platform can run WebGL, so the card is a bitmap the server## Android-Requires the three.ws Android app, version 1.1 or later ([seeker-app.md](#sec-629)).+Requires the three.ws Android app, version 1.1 or later ([seeker-app.md](#sec-636)).1. Open [three.ws/glance](https://three.ws/glance) on the phone, signed in, and tap**Link this phone**. The page mints a widget token and hands it to the app; Android asks@@ -113248,7 +113581,7 @@ The menu bar item shows the same card, and carries **Open my agent**, **Refresh### On an iPhone or iPad-Requires the three.ws iOS app on iOS 17 or later ([ios-app.md](#sec-385)). Link it exactly+Requires the three.ws iOS app on iOS 17 or later ([ios-app.md](#sec-389)). Link it exactlythe same way from [three.ws/glance](https://three.ws/glance), then long-press the home screen,tap **Edit**, tap **Add Widget**, and pick **three.ws**.@@ -113288,7 +113621,7 @@ reference is in [api-reference.md](api-reference.md#glance-api).----<a id="sec-441"></a>+<a id="sec-445"></a>> **Source:** `docs/news-rights.md` · [↑ table of contents](#table-of-contents)@@ -113382,11 +113715,11 @@ Three rules, in order of importance:- [`api/_lib/news-rights.js`](../api/_lib/news-rights.js) — the implementation- [`scripts/news-takedown-purge.mjs`](../scripts/news-takedown-purge.mjs) — the purge tool-- [Market Data API](#sec-407) — the paid market endpoints, including archive search+- [Market Data API](#sec-411) — the paid market endpoints, including archive search----<a id="sec-442"></a>+<a id="sec-446"></a>> **Source:** `docs/notifications.md` · [↑ table of contents](#table-of-contents)@@ -113464,10 +113797,10 @@ category; the mapping (`TYPE_CATEGORY`) lives in| Market alerts | `alerts` | `pump_alert` || Creations | `creations` | `forge_complete`, `forge_failed` || Companion | `companion` | `companion_delivery` |-| Approvals | `approvals` | `approval_requested` (see [Approvals](#sec-126)) |+| Approvals | `approvals` | `approval_requested` (see [Approvals](#sec-127)) || (no tab yet) | `knock` | `knock_received` || (no tab yet) | `mail` | `mail_received` |-| Account | `account` | `withdrawal_completed`, `withdrawal_failed`, `payment_mismatch`, `asset_payment_mismatch`, `skill_payment_mismatch`, `security_alert`, `wallet_anomaly_frozen`, plus any type not in the map (the agent-inference `inference_topup` and `inference_budget_exhausted` land here this way), `token_budget_paused` and `spend_cap_alert` (the [spend page](#sec-381) caps) |+| Account | `account` | `withdrawal_completed`, `withdrawal_failed`, `payment_mismatch`, `asset_payment_mismatch`, `skill_payment_mismatch`, `security_alert`, `wallet_anomaly_frozen`, plus any type not in the map (the agent-inference `inference_topup` and `inference_budget_exhausted` land here this way), `token_budget_paused` and `spend_cap_alert` (the [spend page](#sec-385) caps) |`print_update` is the single type Materialize uses for a physical order's wholelifecycle, quoted through delivered, and it sits with purchases because the@@ -113755,7 +114088,7 @@ one click from the gear icon in both notification surfaces.## Related pages-- [The social layer](#sec-654): where notification events come from+- [The social layer](#sec-662): where notification events come fromand how they connect to the feed, follows, and portfolios.- [api/notifications/README.md](../api/notifications/README.md): theendpoint directory's own reference.@@ -113764,7 +114097,7 @@ one click from the gear icon in both notification surfaces.----<a id="sec-443"></a>+<a id="sec-447"></a>> **Source:** `docs/nvidia-apps-catalog-listing.md` · [↑ table of contents](#table-of-contents)@@ -113772,7 +114105,7 @@ one click from the gear icon in both notification surfaces.Everything needed to submit three.ws to the NVIDIA Inception Accelerated Apps Catalog. The form lives behind the Inception portal login (Portal > Profile > Add product), so this doc holds the copy, categories, links, and assets ready to paste. Submissions are reviewed by NVIDIA on a rolling basis; approval is subject to fit.-Related docs: [nvidia-inception.md](#sec-449) (membership overview), [nvidia-models.md](#sec-450) (full model map, the source of truth for every NVIDIA claim below), [nvidia-visibility-map.md](#sec-454) (every other NVIDIA surface, and the asks to batch into the request email below).+Related docs: [nvidia-inception.md](#sec-453) (membership overview), [nvidia-models.md](#sec-454) (full model map, the source of truth for every NVIDIA claim below), [nvidia-visibility-map.md](#sec-458) (every other NVIDIA surface, and the asks to batch into the request email below).---@@ -113872,7 +114205,7 @@ Every item NVIDIA named in its reply has one unambiguous value or source:### 2. Ask for the catalog listingThe portal has no "publish to catalog" button. The request in-[nvidia-apps-catalog-request.md](#sec-444) was sent on **2026-09-04**,+[nvidia-apps-catalog-request.md](#sec-448) was sent on **2026-09-04**,and NVIDIA replied on **2026-09-14**: qualifying, complete Shipping records are reviewedperiodically. There is no further catalog email to send unless NVIDIA requests information.@@ -114030,7 +114363,7 @@ Filing note: this record is independent of the catalog email sent 2026-09-04. It----<a id="sec-444"></a>+<a id="sec-448"></a>> **Source:** `docs/nvidia-apps-catalog-request.md` · [↑ table of contents](#table-of-contents)@@ -114040,7 +114373,7 @@ The outbound Accelerated Apps Catalog request, NVIDIA's 2026-09-14 disposition,work it requires, a focused reply for the two unanswered asks, and the assets behind eachclaim.-The Inception portal has no "publish to the catalog" control. A product record makes the company eligible; the public [Accelerated Apps Catalog](https://marketplace.nvidia.com/en-us/enterprise/applications/) is curated and published by NVIDIA. This email is the request that asks for the listing, and it carries four other asks that have never been made. Per [nvidia-visibility-map.md](#sec-454), every Tier 1 ask routes to the same inbox, so they are batched here deliberately. **Do not split these into separate emails.** A program manager who receives one clear email with five asks answers it. Five separate emails read as noise.+The Inception portal has no "publish to the catalog" control. A product record makes the company eligible; the public [Accelerated Apps Catalog](https://marketplace.nvidia.com/en-us/enterprise/applications/) is curated and published by NVIDIA. This email is the request that asks for the listing, and it carries four other asks that have never been made. Per [nvidia-visibility-map.md](#sec-458), every Tier 1 ask routes to the same inbox, so they are batched here deliberately. **Do not split these into separate emails.** A program manager who receives one clear email with five asks answers it. Five separate emails read as noise.- **To:** [email protected]- **Subject:** three.ws (Inception member): catalog listing, Showcase, and co-marketing@@ -114057,7 +114390,7 @@ NVIDIA did not supply another catalog application. It said the periodically reviproduct record must show runtime NVIDIA use, Development Stage **Shipping**, accurateCurrently Used and Considering selections, supporting Product Description and TechnicalDetails, a product logo, and a brand color. All copy and assets are now mapped field by-field in [nvidia-apps-catalog-listing.md](#sec-443).+field in [nvidia-apps-catalog-listing.md](#sec-447).The co-marketing page is available at`Inception portal > Benefits > Co-Branded Marketing Assets`. Downloading its current badge,@@ -114301,7 +114634,7 @@ https://three.ws1. Send date recorded in the **Sent** field at the top of this doc.2. Correct the main product record with every field NVIDIA named, then file the secondproduct record, the `<agent-3d>` digital-human embed. Copy is ready in- [nvidia-apps-catalog-listing.md](#sec-443) under "Second product+ [nvidia-apps-catalog-listing.md](#sec-447) under "Second productrecord".3. Download and review the current kit from`Portal > Benefits > Co-Branded Marketing Assets` before posting.@@ -114310,11 +114643,11 @@ https://three.ws| Reply | Where it goes next ||---|---|-| Catalog information or asset request | Answer same day. Everything is in [nvidia-apps-catalog-listing.md](#sec-443). |+| Catalog information or asset request | Answer same day. Everything is in [nvidia-apps-catalog-listing.md](#sec-447). || Showcase interest | Draft the profile against the engineering posts, not marketing copy. || Co-marketing kit changes | Reconcile the current badge/guidelines, then use the owner-gated copy in [marketing/nvidia-inception/social-copy.md](../marketing/nvidia-inception/social-copy.md). |-| ACE redirect | The forum post 3 draft, [nvidia-forum-browser-digital-human.md](#sec-445), is the technical brief to send them. |-| GTC invitation or CFP dates | Record the invitation directly; keep public CFP dates in [nvidia-visibility-map.md](#sec-454) without conflating the two routes. |+| ACE redirect | The forum post 3 draft, [nvidia-forum-browser-digital-human.md](#sec-449), is the technical brief to send them. |+| GTC invitation or CFP dates | Record the invitation directly; keep public CFP dates in [nvidia-visibility-map.md](#sec-458) without conflating the two routes. || No reply to the two focused questions | Keep building public technical proof; do not restart the five-ask thread. |## Verification log@@ -114328,7 +114661,7 @@ Checked 2026-09-04 before this packet was finalized:----<a id="sec-445"></a>+<a id="sec-449"></a>> **Source:** `docs/nvidia-forum-browser-digital-human.md` · [↑ table of contents](#table-of-contents)@@ -114423,7 +114756,7 @@ Happy to go deeper on any of it, particularly the derived-blendshape path, which----<a id="sec-446"></a>+<a id="sec-450"></a>> **Source:** `docs/nvidia-forum-gpu-fleet-post.md` · [↑ table of contents](#table-of-contents)@@ -114537,7 +114870,7 @@ If you run generation lanes on granted GPU capacity, I would love to compare not----<a id="sec-447"></a>+<a id="sec-451"></a>> **Source:** `docs/nvidia-forum-model-retirement-post.md` · [↑ table of contents](#table-of-contents)@@ -114711,7 +115044,7 @@ If you have been through the same thing, I would like to hear how you caught it.----<a id="sec-448"></a>+<a id="sec-452"></a>> **Source:** `docs/nvidia-gtc-2027-poster.md` · [↑ table of contents](#table-of-contents)@@ -114719,7 +115052,7 @@ If you have been through the same thing, I would like to hear how you caught it.Paste-ready submissions for the [GTC 2027 Poster Call for Submissions](https://www.nvidia.com/en-us/gtc/present/call-for-submissions/)(San Jose, 2027-03-15 to 03-18). This is the abstract work that-[nvidia-visibility-map.md](#sec-454) asked to have written before the form+[nvidia-visibility-map.md](#sec-458) asked to have written before the formopened. The form is now open.| | |@@ -114837,7 +115170,7 @@ reviewers: `https://three.ws/demos/audio2face`.### Evidence behind every number-Every figure comes from [the 30-day proof brief](#sec-482) (window+Every figure comes from [the 30-day proof brief](#sec-489) (window2026-08-31 to 2026-09-30), which lists the query behind each one. Regenerate it on the submissiondate with `npm run partners:proof -- --from <start> --to <end>` and update any number that moved.The latency figures for L4 TRELLIS are from the catalog seeder driving the same workers (maker@@ -114861,14 +115194,14 @@ cover what it asks for (topics you want, and novel work you are doing with NVIDI## Related-- [NVIDIA visibility map](#sec-454): every NVIDIA surface, and why GTC is the largest-- [Browser digital-human forum post](#sec-445): the published technical basis for poster A-- [30-day proof brief](#sec-482): the evidence behind poster B-- [Partnership pipeline](#sec-479): where this sits among the other partner actions+- [NVIDIA visibility map](#sec-458): every NVIDIA surface, and why GTC is the largest+- [Browser digital-human forum post](#sec-449): the published technical basis for poster A+- [30-day proof brief](#sec-489): the evidence behind poster B+- [Partnership pipeline](#sec-486): where this sits among the other partner actions----<a id="sec-449"></a>+<a id="sec-453"></a>> **Source:** `docs/nvidia-inception.md` · [↑ table of contents](#table-of-contents)@@ -114920,7 +115253,7 @@ speaking/poster route and should not be described as a Pavilion application.## Related-- [NVIDIA visibility map](#sec-454): every NVIDIA surface where three.ws can earn recognition, what each one requires, and which membership benefits are still unclaimed+- [NVIDIA visibility map](#sec-458): every NVIDIA surface where three.ws can earn recognition, what each one requires, and which membership benefits are still unclaimed- [NVIDIA models on three.ws](/docs/nvidia-models) — the free inference layer, model by model- [The generator was never the hard part](/docs/nvidia-nemotron-spotlight): our Nemotron Nano write-up, published on the NVIDIA Developer Forums- [Image-to-3D on NVIDIA L4 and Blackwell](https://three.ws/blog/image-to-3d-on-nvidia-l4-and-blackwell): the engineering post on the GPU fleet itself: memory ceilings, `sm_120` kernels, and regional quota@@ -114928,7 +115261,7 @@ speaking/poster route and should not be described as a Pavilion application.----<a id="sec-450"></a>+<a id="sec-454"></a>> **Source:** `docs/nvidia-models.md` · [↑ table of contents](#table-of-contents)@@ -115025,7 +115358,7 @@ NVIDIA NIM hosts 100+ open-weight chat models behind the one key, all OpenAI-comThe platform's general LLM helper runs a **free-first ladder: Groq → Cerebras → OpenRouter → NVIDIA NIM**, followed by further keyless free rungs (OVH, Gemini, Pollinations) and only at the very end a paid backstop (Anthropic/OpenAI). Every free rung was re-pointed on 2026-08-27, and every NVIDIA-routed id again on 2026-09-10 after a sweep of `GET /v1/models` on the live account found most of them answering `410 Gone`. A dead id is worse than a missing one: a fallback chain treats a 410 like a rate limit and moves on, so nothing logged an outage while each dead entry burned one of the chain's few retry slots. The rungs the providers still serve: Groq now runs `qwen/qwen3.8-27b` (instant tier `openai/gpt-oss-20b`), Cerebras keeps `llama-3.3-70b`, and the NVIDIA rung runs Nemotron 3 Super 120B, an NVIDIA MoE on an independent provider (the opt-in compact rung moved off `nemotron-3-nano-30b-a3b`, which NIM stopped serving, to `nemotron-3.5-lightning-30b-a3b`), so an outage on the other free lanes still answers here. Both NVIDIA rungs are called with thinking disabled (`chat_template_kwargs: { enable_thinking: false }`) so a chat turn answers instead of reasoning out loud. Both are tool/function-calling capable, so they are eligible for tool-required requests.-Since 2026-10-08 the shared chain runs all three Nemotron models on the one key, as separate rungs: Super 120B, then Ultra 550B right behind it, then Lightning 30B in the step-down group near the tail. Each NIM model is its own function with its own queue and its own retirement date, and NVIDIA sizes the free rate limit by model, so one model throttling, queueing, or answering 410 no longer takes the NVIDIA lane down with it. The third-party models the same key lists (DeepSeek V4.1 Flash, Kimi K3, GLM 5.3, Gemma 4) were probed the same day and each queued past 60 seconds on the free tier, so none of them is a chain rung. The same Nemotron Ultra and Super models are also reachable keylessly through the Kilo Code gateway, which the chain uses as a separate rung on Kilo's own capacity. `/api/cron/free-model-audit` checks every pinned NIM id against the live catalog every 6 hours and pages ops when one is retired. Full chain: [free-llm-providers.md](#sec-317).+Since 2026-10-08 the shared chain runs all three Nemotron models on the one key, as separate rungs: Super 120B, then Ultra 550B right behind it, then Lightning 30B in the step-down group near the tail. Each NIM model is its own function with its own queue and its own retirement date, and NVIDIA sizes the free rate limit by model, so one model throttling, queueing, or answering 410 no longer takes the NVIDIA lane down with it. The third-party models the same key lists (DeepSeek V4.1 Flash, Kimi K3, GLM 5.3, Gemma 4) were probed the same day and each queued past 60 seconds on the free tier, so none of them is a chain rung. The same Nemotron Ultra and Super models are also reachable keylessly through the Kilo Code gateway, which the chain uses as a separate rung on Kilo's own capacity. `/api/cron/free-model-audit` checks every pinned NIM id against the live catalog every 6 hours and pages ops when one is retired. Full chain: [free-llm-providers.md](#sec-320).This lane powers the platform's built-in AI surfaces — chat, embedded site widgets, the tutor, the fact-checker, persona tools, agent-to-agent talk, the transaction explainer — all of which lead with the free providers and only fall through to a paid model if every free lane fails.@@ -115146,7 +115479,7 @@ The free NVIDIA TTS lane: **Magpie multilingual on Riva**, selected by an NVCF `----<a id="sec-451"></a>+<a id="sec-455"></a>> **Source:** `docs/nvidia-nemotron-ask-the-experts-questions.md` · [↑ table of contents](#table-of-contents)@@ -115250,11 +115583,11 @@ Every claim in the two posts is sourced, so a follow-up question cannot catch us| Claim | Source ||---|---|-| NVIDIA Inception member, accepted July 2026 | [nvidia-inception.md](#sec-449) |-| `nvidia/nemotron-nano-12b-v2-vl` gates every photo-to-3D generation, 1-2s | [nvidia-nemotron-spotlight.md](#sec-452), `api/_lib/forge-image-validate.js` |-| ~281 image prompt tokens vs ~1,600 for a 90B-class VLM | [nvidia-nemotron-spotlight.md](#sec-452) |+| NVIDIA Inception member, accepted July 2026 | [nvidia-inception.md](#sec-453) |+| `nvidia/nemotron-nano-12b-v2-vl` gates every photo-to-3D generation, 1-2s | [nvidia-nemotron-spotlight.md](#sec-456), `api/_lib/forge-image-validate.js` |+| ~281 image prompt tokens vs ~1,600 for a 90B-class VLM | [nvidia-nemotron-spotlight.md](#sec-456) || Published Nemotron write-up on the NVIDIA Developer Forums | [forums.developer.nvidia.com](https://forums.developer.nvidia.com/t/how-nemotron-made-three-ws-text-to-3d-pipeline-usable/376445) |-| `nvidia-nemotron-nano-9b-v2` used for reasoning turns, NemoGuard at ~340 ms median | [nvidia-nemotron-spotlight.md](#sec-452) |+| `nvidia-nemotron-nano-9b-v2` used for reasoning turns, NemoGuard at ~340 ms median | [nvidia-nemotron-spotlight.md](#sec-456) |The two other standing asks from that write-up (the hosted TRELLIS image-inputrestriction and the 77-character TRELLIS prompt cap) are TRELLIS questions, not Nemotron@@ -115341,7 +115674,7 @@ plus a reported trillion-parameter Nemotron 4 in training.----<a id="sec-452"></a>+<a id="sec-456"></a>> **Source:** `docs/nvidia-nemotron-spotlight.md` · [↑ table of contents](#table-of-contents)@@ -115502,17 +115835,17 @@ Build the small stuff. Put it in front. The generator was never the hard part.----*three.ws is a browser-native platform for generating 3D avatars, worlds, and agents from a sentence. The text-to-3D lane described here is free and open: no key, no account. Our full NVIDIA model map lives in [`docs/nvidia-models.md`](#sec-450), and the pipeline internals are in [`docs/3d-asset-pipeline.md`](#sec-002). three.ws joined the [NVIDIA Inception program](#sec-449) in July 2026; the companion engineering post on our own GPU fleet is [Image-to-3D on NVIDIA L4 and Blackwell](https://three.ws/blog/image-to-3d-on-nvidia-l4-and-blackwell).*+*three.ws is a browser-native platform for generating 3D avatars, worlds, and agents from a sentence. The text-to-3D lane described here is free and open: no key, no account. Our full NVIDIA model map lives in [`docs/nvidia-models.md`](#sec-454), and the pipeline internals are in [`docs/3d-asset-pipeline.md`](#sec-002). three.ws joined the [NVIDIA Inception program](#sec-453) in July 2026; the companion engineering post on our own GPU fleet is [Image-to-3D on NVIDIA L4 and Blackwell](https://three.ws/blog/image-to-3d-on-nvidia-l4-and-blackwell).*----<a id="sec-453"></a>+<a id="sec-457"></a>> **Source:** `docs/nvidia-ngc-listing.md` · [↑ table of contents](#table-of-contents)# NGC Catalog listing: the one NVIDIA directory with a self-serve door-[nvidia-visibility-map.md](#sec-454) records that no self-serve+[nvidia-visibility-map.md](#sec-458) records that no self-serve"list my product" form exists on any NVIDIA surface. That is true of everysurface except one. The [NGC Software Partner program](https://www.nvidia.com/en-us/gpu-cloud/ngc-software-partners/)publishes a **Become an NGC Software Partner** form, and a container published@@ -115523,7 +115856,7 @@ enterprise audience.The Accelerated Apps Catalog is a marketing listing of the company. An NGClisting is a distribution channel for the software itself. They are worthpursuing in parallel and this doc covers only the second; the first has its own-kit in [nvidia-apps-catalog-listing.md](#sec-443).+kit in [nvidia-apps-catalog-listing.md](#sec-447).Prerequisites and process below were re-fetched from NVIDIA's page on2026-09-02. Every claim about our own containers is cited to the file that@@ -115782,15 +116115,15 @@ and none of them are an agent's call:## Related-- [NVIDIA visibility map](#sec-454): every other NVIDIA surface and its intake route-- [Accelerated Apps Catalog listing kit](#sec-443) and [inclusion request](#sec-444)-- [NVIDIA Inception membership](#sec-449): what membership is, and the rule that it is not an endorsement-- [NVIDIA models on three.ws](#sec-450): the source of truth for every NVIDIA technical claim-- [Listings and distribution](#sec-403): the canonical program and directory inventory+- [NVIDIA visibility map](#sec-458): every other NVIDIA surface and its intake route+- [Accelerated Apps Catalog listing kit](#sec-447) and [inclusion request](#sec-448)+- [NVIDIA Inception membership](#sec-453): what membership is, and the rule that it is not an endorsement+- [NVIDIA models on three.ws](#sec-454): the source of truth for every NVIDIA technical claim+- [Listings and distribution](#sec-407): the canonical program and directory inventory----<a id="sec-454"></a>+<a id="sec-458"></a>> **Source:** `docs/nvidia-visibility-map.md` · [↑ table of contents](#table-of-contents)@@ -115801,8 +116134,8 @@ every NVIDIA surface where three.ws can earn recognition, what each one actuallyrequires, and the honest status of each today.Scope note: the **Accelerated Apps Catalog** already has its own two docs and is-not re-litigated here. See [nvidia-apps-catalog-listing.md](#sec-443)-for the listing kit and [nvidia-apps-catalog-request.md](#sec-444)+not re-litigated here. See [nvidia-apps-catalog-listing.md](#sec-447)+for the listing kit and [nvidia-apps-catalog-request.md](#sec-448)for the inclusion email. This doc covers everything else and links to them wherethey overlap.@@ -115864,10 +116197,10 @@ Everything here can be done today. Nothing waits on NVIDIA, a build, or a date.|---|---|---|---|| 1 | **Our own X, LinkedIn, and Telegram** | Ours | The membership post that never happened. See [Social](#social-surfaces-ours-to-drive). || 2 | **Inception co-marketing kit** | `Portal > Benefits > Co-Branded Marketing Assets` | NVIDIA confirmed on 2026-09-14 that the page is back up. Download the current package, reconcile its badge/guidelines, then publish. |-| 3 | **Portal product record correction** | `programs.nvidia.com/phoenix/application` | Gates the Showcase AND the Apps Catalog. Already specified in [nvidia-apps-catalog-listing.md](#sec-443) step 1. Nothing else in this doc lands well while the record says "CUDA consumer". |-| 4 | **Inception Startup Showcase** | Existing `[email protected]` thread | Requested 2026-09-04 and not directly answered. After #3, send only the focused routing question drafted in [nvidia-apps-catalog-request.md](#sec-444). |+| 3 | **Portal product record correction** | `programs.nvidia.com/phoenix/application` | Gates the Showcase AND the Apps Catalog. Already specified in [nvidia-apps-catalog-listing.md](#sec-447) step 1. Nothing else in this doc lands well while the record says "CUDA consumer". |+| 4 | **Inception Startup Showcase** | Existing `[email protected]` thread | Requested 2026-09-04 and not directly answered. After #3, send only the focused routing question drafted in [nvidia-apps-catalog-request.md](#sec-448). || 5 | **AI Podcast guest nomination** | Embedded form at [ai-podcast.nvidia.com](https://ai-podcast.nvidia.com) | Free, one form, and a founder-shaped story. **Answers drafted below: [AI Podcast nomination](#ai-podcast-nomination-paste-ready).** Re-verified 2026-09-04: the form is live and self-nomination is explicitly invited. |-| 6 | **NVIDIA Developer Forums, post 5** | [forums.developer.nvidia.com](https://forums.developer.nvidia.com) | We are 4 for 4 on posts that landed. This is the one channel with a proven track record, and it is self-serve. The Audio2Face post [went live 2026-09-22](https://forums.developer.nvidia.com/t/a-digital-human-in-a-browser-tab-streaming-audio2face-3d-onto-whatever-rig-the-visitor-brought/383953). Next up: [nvidia-forum-gpu-fleet-post.md](#sec-446), cut to the approval pattern. Owner-gated on the external-channel rule, then paste and post. See [Technical publishing](#technical-publishing-the-proven-channel). |+| 6 | **NVIDIA Developer Forums, post 5** | [forums.developer.nvidia.com](https://forums.developer.nvidia.com) | We are 4 for 4 on posts that landed. This is the one channel with a proven track record, and it is self-serve. The Audio2Face post [went live 2026-09-22](https://forums.developer.nvidia.com/t/a-digital-human-in-a-browser-tab-streaming-audio2face-3d-onto-whatever-rig-the-visitor-brought/383953). Next up: [nvidia-forum-gpu-fleet-post.md](#sec-450), cut to the approval pattern. Owner-gated on the external-channel rule, then paste and post. See [Technical publishing](#technical-publishing-the-proven-channel). || 7 | **NVIDIA Developer Discord** | [discord.com/invite/nvidiadeveloper](https://discord.com/invite/nvidiadeveloper) | NVIDIA engineers and product staff are in there. The browser Audio2Face demo is a conversation starter with the actual ACE team, not a marketing ask. || 8 | **Fix `docs/listings.md`** | Ours | The "Startup & Credit Programs" table lists Quicknode and Google Cloud and has **no NVIDIA row at all**, which is the one canonical place a reader looks for our program memberships. Fixed in this change. || 9 | **"Maximize Your Membership" benefits webinar** | Region registration from the Inception member mailer (Americas / EMEA / APAC) | Announced to members 2026-09-02. NVIDIA's own walkthrough of requesting and managing benefits through the portal, which is the exact mechanism gating items 2, 3 and 4 on this list. The batched email went out 2026-09-04, so use the Q&A to chase asks 2 and 3 live rather than waiting on the inbox. |@@ -115916,10 +116249,10 @@ Real listings, real effort, honest gates. Do not pitch these before the code exi| Surface | Intake | The gate ||---|---|---|-| **NGC Catalog** (via the [NGC Software Partner program](https://www.nvidia.com/en-us/gpu-cloud/ngc-software-partners/)) | A **self-serve "Become an NGC Software Partner" form** on that page, then the partner legal agreement, a push to an NGC private staging repo, security scanning and QA, final sign-off | **The closest Tier 2 surface to reachable, and the only NVIDIA directory with a self-serve door.** It now has its own kit: [nvidia-ngc-listing.md](#sec-453) audits all four prerequisites against the code, names the publishable container ([model-trellis](../workers/model-trellis), MIT upstream, no baked weights, no telemetry), and carries the paste-ready listing copy. The EULA prerequisite is closed ([/legal/nvidia-ngc-eula](https://three.ws/legal/nvidia-ngc-eula)). What remains is one Cloud Build run to make the image runnable outside our GCP project, plus the owner-signed legal agreement. |+| **NGC Catalog** (via the [NGC Software Partner program](https://www.nvidia.com/en-us/gpu-cloud/ngc-software-partners/)) | A **self-serve "Become an NGC Software Partner" form** on that page, then the partner legal agreement, a push to an NGC private staging repo, security scanning and QA, final sign-off | **The closest Tier 2 surface to reachable, and the only NVIDIA directory with a self-serve door.** It now has its own kit: [nvidia-ngc-listing.md](#sec-457) audits all four prerequisites against the code, names the publishable container ([model-trellis](../workers/model-trellis), MIT upstream, no baked weights, no telemetry), and carries the paste-ready listing copy. The EULA prerequisite is closed ([/legal/nvidia-ngc-eula](https://three.ws/legal/nvidia-ngc-eula)). What remains is one Cloud Build run to make the image runnable outside our GCP project, plus the owner-signed legal agreement. || **ACE / digital-human ecosystem** | No public form found. Ask for the redirect in the Showcase email | Genuinely strong: Riva, Magpie, and Audio2Face-3D are shipping, and a **browser-native** A2F demo is rare (most A2F work lives in Unreal or Omniverse). This is our most differentiated technical story. Do not overclaim: we consume ACE microservices, we do not self-host NIM. || **NVIDIA Technical Blog** ([developer.nvidia.com/blog](https://developer.nvidia.com/blog/)) | No public guest-submission process. Route via the forum Technical Blog category and the program team | Editorially controlled by NVIDIA. The realistic path is a forum post that performs, then a pitch. Our two live forum posts are the audition tape. |-| **Omniverse Exchange** | [Omniverse Exchange Publishing Portal](https://developer.nvidia.com/omniverse-exchange-publishing-portal) (early access), plus a GitHub repo tagged with the `omniverse-kit-extension` topic | **Blocked and should stay blocked.** OpenUSD interop is roadmap, not shipping, and [nvidia-apps-catalog-listing.md](#sec-443) already rules that Omniverse Kit stays under "Considering". Note the Omniverse Launcher was deprecated 2025-10-01, so old guides mislead. |+| **Omniverse Exchange** | [Omniverse Exchange Publishing Portal](https://developer.nvidia.com/omniverse-exchange-publishing-portal) (early access), plus a GitHub repo tagged with the `omniverse-kit-extension` topic | **Blocked and should stay blocked.** OpenUSD interop is roadmap, not shipping, and [nvidia-apps-catalog-listing.md](#sec-447) already rules that Omniverse Kit stays under "Considering". Note the Omniverse Launcher was deprecated 2025-10-01, so old guides mislead. |## Tier 3: time-gated, and the clock is running@@ -115952,7 +116285,7 @@ while the window is shut.closes **2026-11-10 at 5 p.m. PT** and the Content Interest Survey closes**2026-10-09 at 5 p.m. PT**. No open speaker call is posted. Both postersubmissions and the survey answers are written in-[nvidia-gtc-2027-poster.md](#sec-448); what remains is the+[nvidia-gtc-2027-poster.md](#sec-452); what remains is theowner submitting them as the presenting author.Actions, in order:@@ -115961,7 +116294,7 @@ Actions, in order:on a weekly watch.** Missing this window costs a full year. It is the one itemon this page with a hard, externally-set deadline.2. **Write the poster and session abstracts before the form opens.** Done- 2026-10-08: [nvidia-gtc-2027-poster.md](#sec-448). The strongest+ 2026-10-08: [nvidia-gtc-2027-poster.md](#sec-452). The strongestsubmission we have is the browser-native digital human: Audio2Face-3D plus Rivaplus Nemotron driving a rigged avatar in a tab with no install, on a fleet ofL4s and one Blackwell. Second-strongest is the L4-and-Blackwell engineering@@ -116029,8 +116362,8 @@ Four forum posts, all live, all landed:- [How Nemotron made three.ws text-to-3D pipeline usable](https://forums.developer.nvidia.com/t/how-nemotron-made-three-ws-text-to-3d-pipeline-usable/376445)- [How three.ws translates a web app into 100 languages with NVIDIA NIM](https://forums.developer.nvidia.com/t/how-three-ws-translates-a-web-app-into-100-languages-with-nvidia-nim-an-llm-powered-i18n-pipeline/377379)-- [NVIDIA NIM model retirements: what a 410 Gone does to a fallback chain](https://forums.developer.nvidia.com/t/nvidia-nim-model-retirements-what-a-410-gone-does-to-a-fallback-chain-and-how-we-survive-it-now/383950) (posted 2026-09-21 from [nvidia-forum-model-retirement-post.md](#sec-447), written to the pattern below)-- [A digital human in a browser tab: streaming Audio2Face-3D onto whatever rig the visitor brought](https://forums.developer.nvidia.com/t/a-digital-human-in-a-browser-tab-streaming-audio2face-3d-onto-whatever-rig-the-visitor-brought/383953) (posted 2026-09-22 from [nvidia-forum-browser-digital-human.md](#sec-445), revised to the pattern the same day)+- [NVIDIA NIM model retirements: what a 410 Gone does to a fallback chain](https://forums.developer.nvidia.com/t/nvidia-nim-model-retirements-what-a-410-gone-does-to-a-fallback-chain-and-how-we-survive-it-now/383950) (posted 2026-09-21 from [nvidia-forum-model-retirement-post.md](#sec-451), written to the pattern below)+- [A digital human in a browser tab: streaming Audio2Face-3D onto whatever rig the visitor brought](https://forums.developer.nvidia.com/t/a-digital-human-in-a-browser-tab-streaming-audio2face-3d-onto-whatever-rig-the-visitor-brought/383953) (posted 2026-09-22 from [nvidia-forum-browser-digital-human.md](#sec-449), revised to the pattern the same day)This is the only NVIDIA channel where we have a track record, it is self-serve,and it feeds everything else: forum posts are what a Technical Blog pitch and a@@ -116076,7 +116409,7 @@ Write it against [api/_lib/a2f-nvidia.js](../api/_lib/a2f-nvidia.js) andbehind it, and follow the house rule the existing two follow: real numbers,real latencies, no marketing voice.-**It is live: [topic 383953](https://forums.developer.nvidia.com/t/a-digital-human-in-a-browser-tab-streaming-audio2face-3d-onto-whatever-rig-the-visitor-brought/383953)**, from [nvidia-forum-browser-digital-human.md](#sec-445) (drafted+**It is live: [topic 383953](https://forums.developer.nvidia.com/t/a-digital-human-in-a-browser-tab-streaming-audio2face-3d-onto-whatever-rig-the-visitor-brought/383953)**, from [nvidia-forum-browser-digital-human.md](#sec-449) (drafted2026-09-02, posted 2026-09-22). It covers the NVCF bidirectional stream, the 44.1 kHz to 16 kHzresampling contract and why playback must use the original audio, the derivedblendshape path that lets a VRM or Oculus-viseme rig lip-sync from an ARKit-52@@ -116092,7 +116425,7 @@ external-channel rule and cleared moderation the day it was posted.| Draft | Subject ||---|---|-| [nvidia-forum-gpu-fleet-post.md](#sec-446) | The production GPU fleet: cold weight loads on L4s, min-instances as a quota decision rather than a performance one, the keep-warm cron, and why a failover chain must never have an empty rung. Cut to the approval pattern 2026-09-22 (two links, both to our own topics here); ready to paste |+| [nvidia-forum-gpu-fleet-post.md](#sec-450) | The production GPU fleet: cold weight loads on L4s, min-instances as a quota decision rather than a performance one, the keep-warm cron, and why a failover chain must never have an empty rung. Cut to the approval pattern 2026-09-22 (two links, both to our own topics here); ready to paste |## Member benefits and current disposition@@ -116126,7 +116459,7 @@ Recorded so the next person does not repeat the search.exists for the Apps Catalog, the Showcase, or any other surface on this page:each runs through the portal record plus a human at`[email protected]`. The single exception is NGC, which does publish- a partner intake form; see [nvidia-ngc-listing.md](#sec-453).+ a partner intake form; see [nvidia-ngc-listing.md](#sec-457).Stop looking for a form anywhere else.- **Omniverse Launcher guides.** Deprecated 2025-10-01. Any tutorial routingthrough it is stale.@@ -116149,14 +116482,14 @@ One thread, one address. Every ask in Tier 1 goes to the same inbox, so batchthem into a single email rather than sending four.**Sent 2026-09-04; answered 2026-09-14.**-[nvidia-apps-catalog-request.md](#sec-444) carries all five asks and+[nvidia-apps-catalog-request.md](#sec-448) carries all five asks andthe reply disposition. **Do not start a second thread.** Catalog and co-marketing are nowblocked on authenticated portal work on our side; the Pavilion is invite-only. The onlyreply to send is the narrow two-question draft for Startup Showcase routing and an ACEcontact. The old 2026-09-25 no-response follow-up is cancelled.Still ours to finish regardless of the reply: the portal record correction (step 1-of [nvidia-apps-catalog-listing.md](#sec-443)), because a+of [nvidia-apps-catalog-listing.md](#sec-447)), because acurator who opens the record after reading the email should not find a CUDAconsumer with DeepVariant checked, and the second product record for the`<agent-3d>` embed, which targets the Digital Humans workload filter the main@@ -116190,19 +116523,19 @@ gcloud run services list --project aerial-vehicle-466722-p5 \## Related-- [Big-tech recognition dispatch board](#sec-166): this map ranked against every other big-tech surface (OpenAI, Anthropic, AWS, IBM) by the odds of a published mention this week. Read that first if you are deciding where a week goes, and this one once NVIDIA is the answer.-- [IBM visibility map](#sec-376): the same surface-by-surface treatment for IBM-- [NVIDIA Inception membership](#sec-449): what membership is, and the rule that it is a program and not a partnership or an endorsement-- [Apps Catalog listing kit](#sec-443) and [inclusion request](#sec-444): the curated marketing listing-- [NGC Catalog listing kit](#sec-453): the self-serve software listing, its prerequisite audit, and the container that clears it-- [NVIDIA models on three.ws](#sec-450): the source of truth for every NVIDIA technical claim made in any pitch-- [Listings and distribution](#sec-403): the canonical program and directory inventory+- [Big-tech recognition dispatch board](#sec-167): this map ranked against every other big-tech surface (OpenAI, Anthropic, AWS, IBM) by the odds of a published mention this week. Read that first if you are deciding where a week goes, and this one once NVIDIA is the answer.+- [IBM visibility map](#sec-380): the same surface-by-surface treatment for IBM+- [NVIDIA Inception membership](#sec-453): what membership is, and the rule that it is a program and not a partnership or an endorsement+- [Apps Catalog listing kit](#sec-447) and [inclusion request](#sec-448): the curated marketing listing+- [NGC Catalog listing kit](#sec-457): the self-serve software listing, its prerequisite audit, and the container that clears it+- [NVIDIA models on three.ws](#sec-454): the source of truth for every NVIDIA technical claim made in any pitch+- [Listings and distribution](#sec-407): the canonical program and directory inventory- [Announcement coverage](#sec-104): which surfaces have been announced and which have not-- [Partners](#sec-474): the independence and no-endorsement language that must survive any rewrite+- [Partners](#sec-480): the independence and no-endorsement language that must survive any rewrite----<a id="sec-455"></a>+<a id="sec-459"></a>> **Source:** `docs/object-library.md` · [↑ table of contents](#table-of-contents)@@ -116213,7 +116546,7 @@ The Object Library is a free, curated gallery of CC0 3D objects and props: furniPage: [/objects](https://three.ws/objects) · API: `GET /api/objects/library`Source: [`pages/objects.html`](../pages/objects.html) · [`src/objects-library.js`](../src/objects-library.js) · [`api/objects/library.js`](../api/objects/library.js)-> This page covers the object gallery and its API. For rigged, animation-ready characters, see the [Character Library](#sec-181). For how AR placement works on phones and desktops, see [AR & WebXR](#sec-129).+> This page covers the object gallery and its API. For rigged, animation-ready characters, see the [Character Library](#sec-182). For how AR placement works on phones and desktops, see [AR & WebXR](#sec-130).---@@ -116229,8 +116562,8 @@ Each card shows the pre-rendered thumbnail and offers three actions. A card stay| Button | Destination | What you get ||---|---|---|-| **Preview** | `/app#model=<glb-url>&kind=object&title=<name>` | The full three.js [3D viewer](#sec-795) in object mode (no agent chat; Restyle, AR, and Download affordances instead) |-| **AR** | `/ar/studio?src=<glb-url>&title=<name>` | [AR Studio](#sec-128): place the prop in your real space through the camera (see [AR & WebXR](#sec-129) for how the AR handoff works per device) |+| **Preview** | `/app#model=<glb-url>&kind=object&title=<name>` | The full three.js [3D viewer](#sec-805) in object mode (no agent chat; Restyle, AR, and Download affordances instead) |+| **AR** | `/ar/studio?src=<glb-url>&title=<name>` | [AR Studio](#sec-129): place the prop in your real space through the camera (see [AR & WebXR](#sec-130) for how the AR handoff works per device) || **Download** | The GLB URL directly | The raw GLB file, CC0, yours to use anywhere |Gallery controls:@@ -116244,7 +116577,7 @@ Gallery controls:## API: `GET /api/objects/library`-Public, no authentication, `GET` and `OPTIONS` only (`HEAD` is answered like `GET`). CORS is open (`Access-Control-Allow-Origin: *`), so a browser `fetch` from any origin works: the manifest is a CC0 index with no caller data in it, and the GLBs it points at already load cross-origin through `/cdn/<key>`. That is what lets an embedded [AR Studio](#sec-128) on someone else's site render the object tray, not just the models in it. The endpoint proxies a small manifest JSON from the R2 CDN (`objects/library/manifest.json`) with an edge cache (`Cache-Control: public, s-maxage=300, stale-while-revalidate=3600`). The GLB and thumbnail bytes never pass through the API: every entry carries absolute CDN URLs the browser loads directly. It mirrors the [Character Library API](#sec-181) exactly, with `objects` in place of `avatars`.+Public, no authentication, `GET` and `OPTIONS` only (`HEAD` is answered like `GET`). CORS is open (`Access-Control-Allow-Origin: *`), so a browser `fetch` from any origin works: the manifest is a CC0 index with no caller data in it, and the GLBs it points at already load cross-origin through `/cdn/<key>`. That is what lets an embedded [AR Studio](#sec-129) on someone else's site render the object tray, not just the models in it. The endpoint proxies a small manifest JSON from the R2 CDN (`objects/library/manifest.json`) with an edge cache (`Cache-Control: public, s-maxage=300, stale-while-revalidate=3600`). The GLB and thumbnail bytes never pass through the API: every entry carries absolute CDN URLs the browser loads directly. It mirrors the [Character Library API](#sec-182) exactly, with `objects` in place of `avatars`.### Query parameters@@ -116313,14 +116646,14 @@ The gallery and API are read-only consumers of a manifest built by a local pipel## Related-- [Character Library](#sec-181): the rigged, animation-ready counterpart to this library.-- [AR & WebXR](#sec-129): the device-by-device AR methods behind the AR button.-- [AR Studio](#sec-128): the `/ar/studio` surface the AR button opens, including multi-object rooms.-- [3D Viewer](#sec-795): the `/app` engine the Preview button opens in object mode.+- [Character Library](#sec-182): the rigged, animation-ready counterpart to this library.+- [AR & WebXR](#sec-130): the device-by-device AR methods behind the AR button.+- [AR Studio](#sec-129): the `/ar/studio` surface the AR button opens, including multi-object rooms.+- [3D Viewer](#sec-805): the `/app` engine the Preview button opens in object mode.----<a id="sec-456"></a>+<a id="sec-460"></a>> **Source:** `docs/okx-marketplace.md` · [↑ table of contents](#table-of-contents)@@ -116353,8 +116686,8 @@ real room), over the marketplace's own payment rail. Everything else we built fothe **back burner**: still deployed, still payable, deliberately off the listing. Those aredocumented at the bottom of this page.-> Related: [REST API Reference](#sec-124) · [MCP servers](#sec-417) ·-> [x402 payments](#sec-862) · seller-side protocol spec:+> Related: [REST API Reference](#sec-125) · [MCP servers](#sec-421) ·+> [x402 payments](#sec-877) · seller-side protocol spec:> [`specs/okx-agent-payments.md`](../specs/okx-agent-payments.md)The **single source of truth** for every service (names, OKX listing copy, prices,@@ -116647,7 +116980,7 @@ three-pose full-body render set, and the rigged animation-ready GLB. Paid toolthis pipeline: [three.ws/agent-identities](https://three.ws/agent-identities).**Single-capability REST endpoints.** Plain JSON `POST`, one price each, all backed by the-same engines the [MCP 3D studio](#sec-417) runs. `GET` on any of them returns its free+same engines the [MCP 3D studio](#sec-421) runs. `GET` on any of them returns its freedescriptor (price, description, input schema).| Service | Price (USDT) | Endpoint | You send |@@ -116743,7 +117076,7 @@ first one lands, and not before.----<a id="sec-457"></a>+<a id="sec-461"></a>> **Source:** `docs/onboarding-tier.md` · [↑ table of contents](#table-of-contents)@@ -116890,17 +117223,17 @@ drift silently, since the four files involved have no import edge between them:- [`public/nav-data.js`](../public/nav-data.js) — the single source of truth for every menu- [`STRUCTURE.md`](../STRUCTURE.md) — where every product surface lives-- [`docs/start-here.md`](#sec-666) — the same journey, written for a human rather than a maintainer+- [`docs/start-here.md`](#sec-674) — the same journey, written for a human rather than a maintainer----<a id="sec-458"></a>+<a id="sec-462"></a>> **Source:** `docs/onchain-agents.md` · [↑ table of contents](#table-of-contents)# Deploying Agents On-Chain (Bulk)-Give every three.ws agent a real on-chain identity: a **Metaplex Core NFT** minted into the **three.ws Agents collection** on Solana. This page is for platform admins and self-hosters; regular users register a single agent through the wallet-signed flow instead. It is the bulk/admin counterpart to the single-agent, user-signed flow in [Solana agents](#sec-657): it deploys many agents server-side through a CLI runner that reports every mint as it lands.+Give every three.ws agent a real on-chain identity: a **Metaplex Core NFT** minted into the **three.ws Agents collection** on Solana. This page is for platform admins and self-hosters; regular users register a single agent through the wallet-signed flow instead. It is the bulk/admin counterpart to the single-agent, user-signed flow in [Solana agents](#sec-665): it deploys many agents server-side through a CLI runner that reports every mint as it lands.> Not pump.fun. These are NFTs (on-chain identity), not tokens. The only coin three.ws ever references is `$THREE`; it appears in each asset's metadata as a link, nothing more.@@ -116965,7 +117298,7 @@ Every agent is minted **into** a single Metaplex Core *collection* account, "thr2. **DB** — the `app_settings` table, key `solana_agent_collection_<network>`.3. **Deploy** — first run with neither set deploys the collection (funded + signed by the authority), then persists its address to `app_settings`.-> After the first run, set `SOLANA_AGENT_COLLECTION_MAINNET=<address>` in your environment so the single-agent flow in [Solana agents](#sec-657) mints into the *same* collection.+> After the first run, set `SOLANA_AGENT_COLLECTION_MAINNET=<address>` in your environment so the single-agent flow in [Solana agents](#sec-665) mints into the *same* collection.---@@ -117178,14 +117511,59 @@ A confirmed canary asset shows `inCollection=true`, `royalty=500bps`, `attrs=11`## See also-- [Solana agents](#sec-657) — the single-agent, user-signed registration flow.-- [ERC-8004](#sec-263) — the EVM on-chain identity path.+- [Solana agents](#sec-665) — the single-agent, user-signed registration flow.+- [ERC-8004](#sec-266) — the EVM on-chain identity path.- [Agent manifest](#sec-059) — the metadata schema.-- [Mint mark ("3ws")](#sec-422) — vanity marking for three.ws launches.+- [Mint mark ("3ws")](#sec-426) — vanity marking for three.ws launches.----<a id="sec-459"></a>+<a id="sec-463"></a>++> **Source:** `docs/open-source-credits.md` · [↑ table of contents](#table-of-contents)++# Adding an open source credit++`/open-source` lists every third-party dependency, model, and asset source three.ws runs on: license, upstream link, and what it powers on the platform. The dataset is generated, not hand-maintained, and a guard test fails the build if a new direct dependency lands without a credit.++## How it works++- `scripts/lib/open-source-credits.mjs` builds the dataset from three sources: every direct dependency in `package.json` (resolved against its own installed `package.json` for version, license, repository, and funding link), the hand-curated `WORKER_MODELS` list (GPU worker models whose license lives in prose in each worker's README, not in machine-readable metadata), and `ASSET_SOURCES` (non-code assets like Poly Haven and the CC0 animation packs, plus vendored/forked source trees already recorded in `NOTICE` and `third_party/README.md`).+- `scripts/build-open-source-credits.mjs` calls `buildCredits()` and writes the result to `data/open-source-credits.json`, wired into `npm run prebuild`'s parallel block so the dataset regenerates on every build.+- `api/open-source-credits.js` serves that committed JSON at `GET /api/open-source-credits`. `src/open-source.js` renders it on `pages/open-source.html`.+- `tests/open-source-credits.test.js` runs `buildCredits()` fresh and deep-equals it against the committed `data/open-source-credits.json`. If they differ, either the dataset was edited by hand (don't; it is generated) or a dependency changed without regenerating it.++## Adding a credit++**A new npm dependency** needs nothing extra: `npmEntries()` in `scripts/lib/open-source-credits.mjs` picks up every direct dependency in `package.json` automatically, reading its license, repository, and funding link from its own installed package metadata. If it is a major, recognizable project, add an entry to `CURATED_PACKAGES` in the same file with an `area` (one of the ids in `AREAS`) and a one-line `powers` string describing what it does on three.ws; otherwise it still gets a full entry, grouped by `fallbackArea(name)`, with no "what it powers" line.++**A worker model** (a GPU model a worker under `workers/*` loads): add an entry to `WORKER_MODELS` with the license copied verbatim from the worker's own README or the model's upstream license file, not guessed. If the upstream project declares no license, say so plainly in the `license` field (for example `livepeer`'s entry reads "not declared upstream") rather than defaulting to a permissive label.++**An asset source** (a free asset library, a vendored source tree): add an entry to `ASSET_SOURCES`. Vendored/forked trees use an id prefixed `vendor:`, which routes them into the `vendored` kind on the page.++After editing any of the three lists, regenerate the dataset and rerun the guard test:++```+node scripts/build-open-source-credits.mjs+npx vitest run tests/open-source-credits.test.js+```++Commit the regenerated `data/open-source-credits.json` alongside the source edit.++## In-surface credits++Beyond the `/open-source` page itself, a few product surfaces carry an inline credit next to the content it applies to:++- `/objects` and the object detail viewer (`src/app-next-overlay.js`) name Poly Haven, the CC0 asset library the catalog sources from.+- A Forge result names the engine that generated it (already wired through the existing Forge result metadata).+- The animation gallery (`src/animations-gallery.js`) shows each clip's source and license; studio-tier clips without an explicit manifest `source`/`license` field fall back to `studioClipCredit(name)`, a filename-prefix classifier validated against the real manifest.+- The Forge export dialog (`src/forge-export.js`) names meshoptimizer and glTF-Transform, the libraries that compress and optimize the exported file, and links to `/open-source#area-formats`.++A new surface that visibly depends on a credited dependency, model, or asset source should link to the relevant `/open-source#area-<id>` anchor rather than repeating the license text inline.++---++<a id="sec-464"></a>> **Source:** `docs/open-source-ecosystem.md` · [↑ table of contents](#table-of-contents)@@ -117432,7 +117810,7 @@ Thank you for the first hundred.----<a id="sec-460"></a>+<a id="sec-465"></a>> **Source:** `docs/open-source-footprint.md` · [↑ table of contents](#table-of-contents)@@ -117440,7 +117818,7 @@ Thank you for the first hundred.Every place the three.ws codebase, its packages, its listings, or its community lives outside three.ws itself, with the link to cite and the number behind it. This is the canonical reference for announcements (the 100-star post, the X article, the weekly report): if two pieces of copy quote different numbers, this page wins. Every link below returned a live page on August 25, 2026; every count came from the registry's own API on the same day. Regenerate the milestone graphic that renders these numbers with `node scripts/render-github-stars-banner.mjs`.-Related: [listings.md](#sec-403) (marketplace status and submission history), [x402-distribution.md](#sec-853) (every x402 crawler and directory, with mechanism), [community.md](#sec-208), [partners.md](#sec-474).+Related: [listings.md](#sec-407) (marketplace status and submission history), [x402-distribution.md](#sec-868) (every x402 crawler and directory, with mechanism), [community.md](#sec-209), [partners.md](#sec-480).## The repo@@ -117478,7 +117856,7 @@ Not published anywhere yet (do not claim): PyPI, crates.io, Docker Hub, Smithery| IBM watsonx / Granite | `@three-ws/ibm-watsonx-mcp`, `@three-ws/ibm-x402-mcp` on npm | IBM Business Partner || AWS Builder Center author profile | https://builder.aws.com/community/@threews | 3 published articles || AWS Builder Center articles | [metering through AWS Marketplace](https://builder.aws.com/content/3ESpll50BdSp9eiCEIxcfG9pGUN/how-we-metered-a-saas-product-through-aws-marketplace-with-the-aws-sdk-for-javascript-v3), [autonomous agents on AWS](https://builder.aws.com/content/3FMY7S5o4lwzb40gDsCJRCE20cX/build-autonomous-ai-agents-with-d-bodies-and-on-chain-payments-threews-on-aws), [the agentic economy](https://builder.aws.com/content/3FgvJFVKstRLVicHsldLM7ba4qB/the-agentic-economy-is-here-x-mcp-ai-agents-crypto-and-d-worlds-converging-aws-strategic-partnerships) | live |-| AWS Marketplace | SaaS metering integration built ([aws-marketplace.md](#sec-164)) | listing not yet created |+| AWS Marketplace | SaaS metering integration built ([aws-marketplace.md](#sec-165)) | listing not yet created || NVIDIA Inception | https://www.nvidia.com/en-gb/accelerated-applications/inception/ | member since July 2026 || NVIDIA Developer Forums | [Nemotron in the text-to-3D pipeline](https://forums.developer.nvidia.com/t/how-nemotron-made-three-ws-text-to-3d-pipeline-usable/376445), [NIM-powered i18n into 100 languages](https://forums.developer.nvidia.com/t/how-three-ws-translates-a-web-app-into-100-languages-with-nvidia-nim-an-llm-powered-i18n-pipeline/377379) | live || NVIDIA hardware | Cloud Run GPU fleet | NVIDIA L4 and RTX PRO 6000 Blackwell workers |@@ -117506,7 +117884,7 @@ Not published anywhere yet (do not claim): PyPI, crates.io, Docker Hub, Smithery|---|---|---|| Solana attestations | SPL Memo envelope `threews.validation.v1`, see [specs/VALIDATORS.md](../specs/VALIDATORS.md) | 3,000 validator attestations || Custody attestations | `custody_attestation_*` | 126,522 proofs across 244 epochs |-| ERC-8004 registries | Identity `0x8004A169FB4a3325136EB29fA0ceB6D2e539a432`, Reputation `0x8004BAa17C55a88189AE136b182e5fdA19dE9b63`, see [erc8004.md](#sec-263) | same address on every EVM chain |+| ERC-8004 registries | Identity `0x8004A169FB4a3325136EB29fA0ceB6D2e539a432`, Reputation `0x8004BAa17C55a88189AE136b182e5fdA19dE9b63`, see [erc8004.md](#sec-266) | same address on every EVM chain || Solana programs | `contracts/agent-invocation`, `contracts/skill-license` | 2 programs, 4 Rust crates || Solidity | `contracts/src` | 7 contracts (payments, identity, reputation, validation, vault) || BNB Chain Dappbay | https://dappbay.bnbchain.org/detail/three | live |@@ -117533,7 +117911,7 @@ Mint `FeMbDoX7R1Psc4GEcvJdsbNbZA3bfztcyDCatJVJpump`. Venues: [pump.fun (verified----<a id="sec-461"></a>+<a id="sec-466"></a>> **Source:** `docs/open-source-friday-plan.md` · [↑ table of contents](#table-of-contents)@@ -117560,8 +117938,8 @@ Verified against `gh repo view nirholas/three.ws` and the working tree, not from| License | **PASS** | Relicensed to Apache-2.0 on 2026-08-21. Verbatim [LICENSE](../LICENSE), a [NOTICE](../NOTICE) covering vendored and derived code, and all 102 first-party manifests set to `"license": "Apache-2.0"`. || 100+ stars, hosted on GitHub | **PASS** | 104 stargazers, 26 forks as of 2026-08-25 (98 on 2026-08-21; the relicense closed the gap without a campaign) || Open to outside contributions | PASS | 11 contributors, issue and PR templates, CODEOWNERS, and six curated open issues (see below) |-| *Preferred:* community channel | **PASS** | Telegram community, X community, IBM Community group, GitHub Discussions (seeded 2026-08-25: [Welcome #122](https://github.com/nirholas/three.ws/discussions/122), [Show and tell #123](https://github.com/nirholas/three.ws/discussions/123), [Roadmap #124](https://github.com/nirholas/three.ws/discussions/124)), release channel. All five documented in [docs/community.md](#sec-208) and wired into the README, CONTRIBUTING, and the new-issue chooser. |-| *Preferred:* triage team / contributor onboarding | **PASS** | [docs/triage.md](#sec-698) (labels, claiming, published response targets) and [docs/first-contribution.md](#sec-307) (clone to PR in 15 minutes, worked example) |+| *Preferred:* community channel | **PASS** | Telegram community, X community, IBM Community group, GitHub Discussions (seeded 2026-08-25: [Welcome #122](https://github.com/nirholas/three.ws/discussions/122), [Show and tell #123](https://github.com/nirholas/three.ws/discussions/123), [Roadmap #124](https://github.com/nirholas/three.ws/discussions/124)), release channel. All five documented in [docs/community.md](#sec-209) and wired into the README, CONTRIBUTING, and the new-issue chooser. |+| *Preferred:* triage team / contributor onboarding | **PASS** | [docs/triage.md](#sec-706) (labels, claiming, published response targets) and [docs/first-contribution.md](#sec-310) (clone to PR in 15 minutes, worked example) || Guest available Friday 1:00 PM ET | Owner to confirm | Pre-recording is allowed as an exception || Booked at least two weeks ahead | Plan for it | Earliest realistic slot: **2026-09-11** |@@ -117590,9 +117968,9 @@ On 2026-08-21 the repo sat at 98. The call was to treat that as noise rather tha### Done on 2026-08-21-- **Community channels documented and wired.** [docs/community.md](#sec-208) lists all five rooms with guidance on which fits which question, plus the house rules. Linked from the README (new Community section, in the table of contents), CONTRIBUTING.md, and the GitHub new-issue chooser (`.github/ISSUE_TEMPLATE/config.yml`).-- **Contributor onboarding written.** [docs/first-contribution.md](#sec-307) goes clone to open PR in about 15 minutes, with a complete worked example: teaching the avatar retargeter a bone-naming convention, the test that proves it, and the two mistakes that cost a review round.-- **Triage documented.** [docs/triage.md](#sec-698) publishes response targets (2 business days for a new issue or a first-time contributor's PR, 24 hours for a security advisory), what every label means, how to claim work, and how someone becomes a maintainer.+- **Community channels documented and wired.** [docs/community.md](#sec-209) lists all five rooms with guidance on which fits which question, plus the house rules. Linked from the README (new Community section, in the table of contents), CONTRIBUTING.md, and the GitHub new-issue chooser (`.github/ISSUE_TEMPLATE/config.yml`).+- **Contributor onboarding written.** [docs/first-contribution.md](#sec-310) goes clone to open PR in about 15 minutes, with a complete worked example: teaching the avatar retargeter a bone-naming convention, the test that proves it, and the two mistakes that cost a review round.+- **Triage documented.** [docs/triage.md](#sec-706) publishes response targets (2 business days for a new issue or a first-time contributor's PR, 24 hours for a security advisory), what every label means, how to claim work, and how someone becomes a maintainer.- **Six curated issues opened**, every one with a named file and a verification command:- [#110](https://github.com/nirholas/three.ws/issues/110) Rig: Apple / ARKit `_joint`-suffixed skeletons (verified: 0 of 10 joints map today)- [#111](https://github.com/nirholas/three.ws/issues/111) Rig: Kinect trailing-side bone names (verified: 0 of 10)@@ -117728,7 +118106,7 @@ Every hard criterion is met, stars included. What remains is one click, polish,| 2026-08-25 | Pin #122 | Owner, one click || 2026-08-26 | README front door trimmed, demo clip recorded | Agent || 2026-08-25 | **Issue submitted**: [open-source-friday#254](https://github.com/githubevents/open-source-friday/issues/254) | Done |-| 2026-08-25 | Reply to Andrea's X thread with the issue link (draft: [x-posts/osf-issue-reply.md](#sec-840)) | Owner |+| 2026-08-25 | Reply to Andrea's X thread with the issue link (draft: [x-posts/osf-issue-reply.md](#sec-854)) | Owner || 2026-08-28+ | Booking link arrives on approval, book the slot | Owner || 2026-09-01 | Approved; booking bot asked for a date | Done || 2026-09-17 | All six August issues closed; seven new issue bodies and the booking reply written ([menu](../marketing/growth/events/open-source-friday-menu.md)) | Done |@@ -117746,7 +118124,7 @@ The license question that used to sit here is resolved: Apache-2.0, shipped 2026----<a id="sec-462"></a>+<a id="sec-467"></a>> **Source:** `docs/openai-community-3d-studio-post.md` · [↑ table of contents](#table-of-contents)@@ -118022,7 +118400,7 @@ nich----<a id="sec-463"></a>+<a id="sec-468"></a>> **Source:** `docs/openai-community-physical-world-post.md` · [↑ table of contents](#table-of-contents)@@ -118463,7 +118841,7 @@ Happy to answer anything about the internals. The whole stack is Apache-2.0 at [----<a id="sec-464"></a>+<a id="sec-469"></a>> **Source:** `docs/openai-listing-channels.md` · [↑ table of contents](#table-of-contents)@@ -118471,7 +118849,7 @@ Happy to answer anything about the internals. The whole stack is Apache-2.0 at [Every route to getting three.ws published on an OpenAI-owned surface, ranked by leverage, with the concrete blocker on each. Written 2026-08-17 after auditing the stalled Cookbook PR.-Related docs: [listings.md](#sec-403) (every listing across all vendors), [mcp.md](#sec-417) (the hosted MCP server a plugin submission depends on), [nvidia-apps-catalog-listing.md](#sec-443) (the same kind of kit for NVIDIA).+Related docs: [listings.md](#sec-407) (every listing across all vendors), [mcp.md](#sec-421) (the hosted MCP server a plugin submission depends on), [nvidia-apps-catalog-listing.md](#sec-447) (the same kind of kit for NVIDIA).---@@ -118501,7 +118879,7 @@ The gating requirement is a public, production MCP server. Most submitters have| Requirement | What we already have ||---|---|-| Public MCP server | `https://three.ws/api/mcp`, Streamable HTTP, MCP `2025-06-18` ([mcp.md](#sec-417)) |+| Public MCP server | `https://three.ws/api/mcp`, Streamable HTTP, MCP `2025-06-18` ([mcp.md](#sec-421)) || Auth | OAuth 2.1 end-user flow, with `api/mcp/.well-known/oauth-protected-resource` discovery already routed in `vercel.json` || Verified website | three.ws, live on Cloud Run behind the production LB || Privacy policy and terms | Live pages, already declared in `data/pages.json` |@@ -118521,7 +118899,7 @@ Six sections: **Info** (name, short and long description, logo, category, URLs,### Scoping decision: submit one plugin, not thirty-seven-The guidelines reject "overly generic single-word names unlinked to your brand" and reward apps that are "tightly scoped." Thirty-seven separate MCP servers submitted individually reads as directory spam and most would fail the tightly-scoped test on their own. Submit **one three.ws plugin whose tools are the text-to-3D and avatar pipeline**, which is the thing no one else in the directory does. The rest stay available as direct MCP connections documented in [mcp.md](#sec-417).+The guidelines reject "overly generic single-word names unlinked to your brand" and reward apps that are "tightly scoped." Thirty-seven separate MCP servers submitted individually reads as directory spam and most would fail the tightly-scoped test on their own. Submit **one three.ws plugin whose tools are the text-to-3D and avatar pipeline**, which is the thing no one else in the directory does. The rest stay available as direct MCP connections documented in [mcp.md](#sec-421).### Known rejection reasons to design against@@ -118575,7 +118953,7 @@ In order: rebase onto `main` and resolve `registry.yaml` and `authors.yaml` by hThe nearest self-serve adjacent surface is the [OpenAI Developer Community](https://community.openai.com) "Use cases and examples" category. No gate, indexed by search, and legitimate to post a build writeup to.-Two drafts are written and waiting for that surface: [openai-community-3d-studio-post.md](#sec-462) (the original Apps SDK plus Actions build writeup) and [openai-community-physical-world-post.md](#sec-463) (the follow-up: the eleven keyless tools, the vision and simulation-readiness surfaces built on top of them, and the design rules for tools that spend money or move physical objects).+Two drafts are written and waiting for that surface: [openai-community-3d-studio-post.md](#sec-467) (the original Apps SDK plus Actions build writeup) and [openai-community-physical-world-post.md](#sec-468) (the follow-up: the eleven keyless tools, the vision and simulation-readiness surfaces built on top of them, and the design rules for tools that spend money or move physical objects).---@@ -118611,7 +118989,7 @@ Not OpenAI-owned, so they do not answer the original question, but they are wher----<a id="sec-465"></a>+<a id="sec-470"></a>> **Source:** `docs/oracle-model.md` · [↑ table of contents](#table-of-contents)@@ -119050,7 +119428,7 @@ of why the model went nineteen days without a refit.----<a id="sec-466"></a>+<a id="sec-471"></a>> **Source:** `docs/oracle-trading-mcp-plan.md` · [↑ table of contents](#table-of-contents)@@ -119289,7 +119667,7 @@ Per the documentation rules in `CLAUDE.md`, all of these apply and none are opti### Phase 5: the X post-Draft lives at [`docs/x-posts/oracle-trading-mcp-x-post.md`](#sec-839). Written before+Draft lives at [`docs/x-posts/oracle-trading-mcp-x-post.md`](#sec-853). Written beforethe work ships so the announcement shapes the scope rather than the reverse: if a claim in thatpost is not true when the phases are done, the phases are not done.@@ -119323,7 +119701,7 @@ than shipping late.----<a id="sec-467"></a>+<a id="sec-472"></a>> **Source:** `docs/oracle.md` · [↑ table of contents](#table-of-contents)@@ -119362,7 +119740,7 @@ One design commitment holds the whole thing together: scoring is a pure, side-ef## The model: fitted from real outcomes-Since 2026-08-09 the conviction engine is a bucketed logistic model fitted on the platform's own labeled outcome history, not a hand-tuned point system. v2 fitted one target ("good": the coin graduated or reached a 3x-or-greater ATH multiple) on 92,906 launches. Since 2026-08-28 the engine is **v3**: three heads fitted over one shared design matrix, all reading a `hold_multiple` that cancels the SOL price out of the label (`win`: it ran and a first-sight holder is still up; `rug`: a first-sight holder is down more than half; `moon`: it ran at all, the v2 target). The published 0-100 score anchors on `win`, and rug risk is published beside it as its own number rather than folded in (`rugRisk`, `upside`, `giveBackRisk` on every verdict). Every launch-time signal is bucketed by its empirically observed ranges, each bucket carries a fitted log-odds weight per head, and the fused sum passes through a sigmoid to yield a calibrated probability for each head. The promoted weights live in `oracle_model_versions` and `/api/cron/oracle-refit` refits and re-promotes them behind a gate that can refuse a candidate; `api/_lib/oracle/conviction-model.json` is the bootstrap a cold container scores with until it reads the active row (each bucket ships with its sample size and observed rate per head), and `scripts/oracle-fit.mjs` refreshes that bootstrap from the durable training snapshot (`oracle_training_set`). The whole model, labels and promotion gate included, is written up in [The Oracle model](#sec-465).+Since 2026-08-09 the conviction engine is a bucketed logistic model fitted on the platform's own labeled outcome history, not a hand-tuned point system. v2 fitted one target ("good": the coin graduated or reached a 3x-or-greater ATH multiple) on 92,906 launches. Since 2026-08-28 the engine is **v3**: three heads fitted over one shared design matrix, all reading a `hold_multiple` that cancels the SOL price out of the label (`win`: it ran and a first-sight holder is still up; `rug`: a first-sight holder is down more than half; `moon`: it ran at all, the v2 target). The published 0-100 score anchors on `win`, and rug risk is published beside it as its own number rather than folded in (`rugRisk`, `upside`, `giveBackRisk` on every verdict). Every launch-time signal is bucketed by its empirically observed ranges, each bucket carries a fitted log-odds weight per head, and the fused sum passes through a sigmoid to yield a calibrated probability for each head. The promoted weights live in `oracle_model_versions` and `/api/cron/oracle-refit` refits and re-promotes them behind a gate that can refuse a candidate; `api/_lib/oracle/conviction-model.json` is the bootstrap a cold container scores with until it reads the active row (each bucket ships with its sample size and observed rate per head), and `scripts/oracle-fit.mjs` refreshes that bootstrap from the durable training snapshot (`oracle_training_set`). The whole model, labels and promotion gate included, is written up in [The Oracle model](#sec-470).The honest numbers. v2, measured on a time-split holdout (the newest 25 percent of labels, never seen in training): AUC 0.879 (the hand-tuned v1 engine measured 0.627 on the same window), 62.5 percent of coins in the top decile of score were good against an 11.7 percent base rate, and the Prime tier observed 72.7 percent good. v3, held out on 74,211 launches it never saw: win AUC 0.840, rug AUC 0.918, moon AUC 0.892. The live reading is always at `/api/oracle/model?view=card`.@@ -119645,7 +120023,7 @@ GET https://three.ws/api/oracle/trades?mint=<mint>- Realized calibration per conviction band at `/api/oracle/calibration`: the fleet's actual win rate from real fills, next to what the band predicted, plus the bounded correction factor the scorer applies.- A dynamic 1200x630 OpenGraph conviction card (SVG) for sharing a coin at `/api/oracle/og`. Its live market cap reads pump.fun first (with one retry, honouring `Retry-After`) and falls through to the shared multi-source market reader (Birdeye, DexScreener, GeckoTerminal) when pump.fun does not answer.-The write endpoints. Two are auth-scoped to the agent's owner: `GET·POST /api/oracle/watch` reads or arms an agent's watch config with server-side validation clamping every limit, and `POST /api/oracle/test-alert` sends a test alert. The clamps only ever move a number toward safety: a size above the ceiling is lowered, but arming `mode: "live"` with a `per_trade_sol` under the 0.001 SOL floor, or a `max_daily_sol` smaller than one trade, is a 400 rather than a silent round-up into real spending. Moving a mainnet watch into live-armed also requires the account's signed real-funds agreements (Terms of Service, Risk Disclosure, Agent Wallet Agreement); without them the arm is refused with a 403 that links to `/legal/agreements` (see [Risk acknowledgment](#sec-618)). Re-saving an already live-armed watch, simulate mode, devnet, and disarming are not gated. Simulate runs keep the forgiving clamps. Two are public and IP rate-limited instead: `POST·DELETE /api/oracle/follow` subscribes a Telegram chat to an agent's signals (the chat id the caller supplies is the identity, so there is no session to scope to), and `POST /api/oracle/social` ingests tweets to additively boost virality (never downgrades an LLM read).+The write endpoints. Two are auth-scoped to the agent's owner: `GET·POST /api/oracle/watch` reads or arms an agent's watch config with server-side validation clamping every limit, and `POST /api/oracle/test-alert` sends a test alert. The clamps only ever move a number toward safety: a size above the ceiling is lowered, but arming `mode: "live"` with a `per_trade_sol` under the 0.001 SOL floor, or a `max_daily_sol` smaller than one trade, is a 400 rather than a silent round-up into real spending. Moving a mainnet watch into live-armed also requires the account's signed real-funds agreements (Terms of Service, Risk Disclosure, Agent Wallet Agreement); without them the arm is refused with a 403 that links to `/legal/agreements` (see [Risk acknowledgment](#sec-625)). Re-saving an already live-armed watch, simulate mode, devnet, and disarming are not gated. Simulate runs keep the forgiving clamps. Two are public and IP rate-limited instead: `POST·DELETE /api/oracle/follow` subscribes a Telegram chat to an agent's signals (the chat id the caller supplies is the identity, so there is no session to scope to), and `POST /api/oracle/social` ingests tweets to additively boost virality (never downgrades an LLM read).### Through MCP@@ -119726,7 +120104,7 @@ The more data we watch, the sharper every score. Oracle is live now.----<a id="sec-468"></a>+<a id="sec-473"></a>> **Source:** `docs/oss-adoption-2026-09.md` · [↑ table of contents](#table-of-contents)@@ -119737,7 +120115,7 @@ does **not** already use, ranked by what they would actually change here, withthe exact file each one lands in.This is the decision document. Its sibling-[popular-3d-github-repos.md](#sec-501) is a popularity+[popular-3d-github-repos.md](#sec-508) is a popularitysnapshot of the whole 3D ecosystem; that one answers "what exists", this oneanswers "what should we adopt, and where does it go".@@ -120061,7 +120439,7 @@ curl -s https://raw.githubusercontent.com/wgsxm/PartCrafter/main/LICENSE | head----<a id="sec-469"></a>+<a id="sec-474"></a>> **Source:** `docs/overlay-audit.md` · [↑ table of contents](#table-of-contents)@@ -120246,7 +120624,7 @@ only worth calling from a test.----<a id="sec-470"></a>+<a id="sec-475"></a>> **Source:** `docs/package-extraction.md` · [↑ table of contents](#table-of-contents)@@ -120375,7 +120753,7 @@ part of the extraction itself: extract and publish first, swap the import later.----<a id="sec-471"></a>+<a id="sec-476"></a>> **Source:** `docs/page-performance.md` · [↑ table of contents](#table-of-contents)@@ -120516,7 +120894,7 @@ that is a layout shift for every pixel it moves.Stored art is whatever size its creator uploaded. `/api/img` resizes andre-encodes to WebP against a fixed width ladder, cached immutably at the edge-(see the Image proxy API section of [api-reference.md](#sec-124)).+(see the Image proxy API section of [api-reference.md](#sec-125)).```jsimport { resizedImageUrl } from './shared/image-url.js'; // remote artwork in the DOM@@ -120576,19 +120954,19 @@ Two things will mislead you if you let them:## Related-- [Avatar thumbnails](#sec-151): where a preview image comes from and the rule every path obeys+- [Avatar thumbnails](#sec-152): where a preview image comes from and the rule every path obeys- [3D asset pipeline](#sec-002): baking models and clips, including why clip JSON is written at float32 precision-- [API reference](#sec-124): the image proxy endpoint and its width ladder+- [API reference](#sec-125): the image proxy endpoint and its width ladder----<a id="sec-472"></a>+<a id="sec-477"></a>> **Source:** `docs/paired-coins.md` · [↑ table of contents](#table-of-contents)# Paired coins on Robinhood Chain-A paired coin is a coin on [Robinhood Chain](#sec-620) (chain ID 4663) that+A paired coin is a coin on [Robinhood Chain](#sec-627) (chain ID 4663) thattrades against one to five assets at once instead of a single gas token. A coin paired withNVDA, TSLA and SPY trades in three independent bonding curves, one per pairing, and its creatorearns swap fees in all three. The assets a coin can pair with (tokenized stocks, WETH,@@ -120606,7 +120984,7 @@ of them run the same server path:| An MCP client | `paired_launch_quote`, then `paired_launch`, on `https://three.ws/api/mcp` |For the single-quote ETH launchpad on the same chain, see-[Launch a coin on Robinhood Chain (Pons)](#sec-500).+[Launch a coin on Robinhood Chain (Pons)](#sec-507).## What a paired coin is@@ -120681,7 +121059,7 @@ pairing on chain makes it available everywhere on three.ws with no code change.three.ws adds what the contract cannot know:- **Class.** From the Robinhood Chain universe that also backs- [Robinhood Portfolios](#sec-621): `rwa-equity` (Stock), `stablecoin`,+ [Robinhood Portfolios](#sec-628): `rwa-equity` (Stock), `stablecoin`,`crypto-major` (Major), `crypto-native` (Chain coin), or `unlisted` for a registered asset theuniverse does not know.- **Canonical flag.** The universe resolves ticker impersonation by contract address, so a@@ -121079,7 +121457,7 @@ spend on three.ws runs through, in this order:- The owner must have signed the real-funds agreements.- The launch fee and opening buy are priced in USD and checked against the agent's per-transactionand daily ceilings for Robinhood Chain, metered separately from Solana and Base (see- [custody](#sec-232)).+ [custody](#sec-233)).- The wallet must cover the fee, the opening buy and gas, and the exact transaction must simulate.- Only then is the key decrypted, with an audit row. The spend is written to the custody ledger aspending before the send and settled after the receipt, so two launches at once cannot both slip@@ -121229,7 +121607,7 @@ demonstrate the intended behaviour, and are not a substitute for someone trying----<a id="sec-473"></a>+<a id="sec-478"></a>> **Source:** `docs/papertrade.md` · [↑ table of contents](#table-of-contents)@@ -121244,7 +121622,7 @@ This integration is **read only**. Nothing here signs an order, deposits or with| REST | `GET /api/papertrade?view=...` | Your own code, a dashboard, a script. No key needed || MCP | `papertrade_*` tools on `/api/mcp-agent` | Claude, or any MCP client you connect. No sign-in needed |-Related reading: [Agent Perps](#sec-490) is the Solana perps desk, where an agent trades with its own wallet. The [MCP guide](mcp.md#papertrade-synthetic-perps-on-hyperevm) covers connecting a client.+Related reading: [Agent Perps](#sec-497) is the Solana perps desk, where an agent trades with its own wallet. The [MCP guide](mcp.md#papertrade-synthetic-perps-on-hyperevm) covers connecting a client.---@@ -121469,7 +121847,30 @@ The position math (`api/_lib/papertrade/math.js`) runs in integer arithmetic at----<a id="sec-474"></a>+<a id="sec-479"></a>++> **Source:** `docs/partner-benefits.md` · [↑ table of contents](#table-of-contents)++# Partner benefits (public page)++`three.ws/partners/benefits` tells builders and the community what each partnership gives them. It complements the [partner map](#sec-480) (`/partners`), which says who the partners are; this page says what that means for a user.++Source: [pages/partner-benefits.html](../pages/partner-benefits.html), route `/partners/benefits` in `vercel.json`, Vite input `partner-benefits`, registry row in `data/pages.json`. It is static markup with no runtime data, so it renders with JavaScript off.++## What it covers++One card per programme, in the same order as `/partners`: OpenAI (Select Partner), NVIDIA (Inception), IBM (Business Partner), Google Cloud (Web3 Startups), AWS (Partner), Alibaba Cloud (Marketplace), Quicknode (Startup Program), HackerNoon (Media). Each card has a designation chip, one factual lead sentence, three "what it brings you" points, and links to the deeper docs.++## Editing rules++- Quote the designation exactly as in [partners.md](partners.md#what-the-page-does-not-claim). Never upgrade a designation to an endorsement or a pending listing to a live one. AWS says the Marketplace listing is coming until [listings.md](#sec-407) says otherwise.+- Do not publish credit amounts, organization or workspace IDs, or contract terms. Internal records live in [partners/openai-partner-benefits-2026.md](#sec-485), [partners/ibm-partner-plus.md](#sec-483), [nvidia-inception.md](#sec-453) and [ops/gcp-credits-plan.md](ops/gcp-credits-plan.md).+- Keep the framing positive and factual. Benefits are described by what a user gets, not by what we spend.+- A new partner needs a card here, a card on `/partners`, and a row in [partners.md](#sec-480).++---++<a id="sec-480"></a>> **Source:** `docs/partners.md` · [↑ table of contents](#table-of-contents)@@ -121477,7 +121878,7 @@ The position math (`api/_lib/papertrade/math.js`) runs in integer arithmetic at`three.ws/partners` is the public map of the cloud, AI, hardware, infrastructure, and media programmes three.ws takes part in. This doc is the developer-facing companion to that page: for each surface it says what the integration actually **is**, at the status the page and the per-partner docs claim, and links the doc that goes deeper.-Page source: [`pages/partners.html`](../pages/partners.html). Partnership enquiries go to **[email protected]** (the page's "Become a partner" call to action). Press and brand requests go to **[email protected]**, covered in [Press kit](#sec-505).+Page source: [`pages/partners.html`](../pages/partners.html). Partnership enquiries go to **[email protected]** (the page's "Become a partner" call to action). Press and brand requests go to **[email protected]**, covered in [Press kit](#sec-512).**Read the status labels literally.** Each card carries a one-word tier chip that is a category, not a rank: Select Partner, Strategic, Cloud, Inception, Media, Infrastructure. Nothing on the page grants an endorsement, and several of the docs below carry explicit "this is not an endorsement" language that must survive any rewrite.@@ -121487,14 +121888,14 @@ Page source: [`pages/partners.html`](../pages/partners.html). Partnership enquir| Partner | Chip on the card | Card links to | Deeper docs ||---|---|---|---|-| OpenAI | Select Partner | `/openai` | [MCP 3D Studio (free)](#sec-414), [3D Studio (paid)](#sec-410), [Custom GPT config](#sec-185), [AR in ChatGPT](#sec-186), [Spatial MCP](#sec-659) |-| IBM | Strategic | `/blog/three-ws-ibm-business-partner` | [IBM watsonx and Granite](#sec-378), [IBM Granite x402 MCP](#sec-377), [IBM visibility map](#sec-376) |-| Amazon Web Services | Cloud | `/aws` | [AWS Marketplace](#sec-164), [listing kit](#sec-163), [partner spotlight](#sec-165) |+| OpenAI | Select Partner | `/openai` | [MCP 3D Studio (free)](#sec-418), [3D Studio (paid)](#sec-414), [Custom GPT config](#sec-186), [AR in ChatGPT](#sec-187), [Spatial MCP](#sec-667) |+| IBM | Strategic | `/blog/three-ws-ibm-business-partner` | [IBM watsonx and Granite](#sec-382), [IBM Granite x402 MCP](#sec-381), [IBM visibility map](#sec-380) |+| Amazon Web Services | Cloud | `/aws` | [AWS Marketplace](#sec-165), [listing kit](#sec-164), [partner spotlight](#sec-166) || Google Cloud | Cloud | `/blog/three-ws-google-cloud-partnership` | [Production runbook](ops/gcp-production.md), [credits plan](ops/gcp-credits-plan.md), [model workers](ops/gcp-model-workers.md) |-| Alibaba Cloud | Cloud | `/blog/three-ws-alibaba-cloud-partnership` | [Listings and distribution](#sec-403), [the model router](#sec-172) |-| NVIDIA | Inception | `/nvidia` | [NVIDIA Inception](#sec-449), [NVIDIA models](#sec-450), [Nemotron spotlight](#sec-452) |-| HackerNoon | Media | `/blog/three-ws-hackernoon-partnership` | [Syndication](#sec-671), [Listings and distribution](#sec-403) |-| Quicknode | Infrastructure | `/blog/three-ws-quicknode-startup-program` | [Solana integration](#sec-657), [Listings and distribution](#sec-403) |+| Alibaba Cloud | Cloud | `/blog/three-ws-alibaba-cloud-partnership` | [Listings and distribution](#sec-407), [the model router](#sec-173) |+| NVIDIA | Inception | `/nvidia` | [NVIDIA Inception](#sec-453), [NVIDIA models](#sec-454), [Nemotron spotlight](#sec-456) |+| HackerNoon | Media | `/blog/three-ws-hackernoon-partnership` | [Syndication](#sec-679), [Listings and distribution](#sec-407) |+| Quicknode | Infrastructure | `/blog/three-ws-quicknode-startup-program` | [Solana integration](#sec-665), [Listings and distribution](#sec-407) |The page's stat bar reads 8 partners, 22 chains, and an infinity glyph for scale. It is a `<dl>` and is read out to screen readers like any other content, so the two numbers have to stay true: the partner count is reconciled against the number of cards in the DOM on load, and 22 is the number of chains in `REGISTRY_DEPLOYMENTS` in [`src/erc8004/abi.js`](../src/erc8004/abi.js). The infinity glyph is framing, not a metric; it is announced as "Unbounded".@@ -121506,13 +121907,15 @@ The page's stat bar reads 8 partners, 22 chains, and an infinity glyph for scale**What the integration is.**-- **The keyless connector** at `https://three.ws/api/mcp-studio` is a free MCP server exposing only 3D generation tools: no account, no payment, no API key, no wallet, no token. That is the surface submitted to the ChatGPT App Directory. See [MCP 3D Studio](#sec-414).-- **The paid sibling** at `https://three.ws/api/mcp-3d` is a separate server with rigging, animation, retexturing, and analysis, authenticated by OAuth 2.1 or paid per call over x402. It shares none of the keyless server's surface. See [3D Studio MCP](#sec-410).-- **The custom GPT** in the GPT Store calls an Actions contract served from `/.well-known/3d-studio-openapi.yaml`. Its builder configuration is checked in, because the GPT itself is configured by hand: [Custom GPT config](#sec-185).-- **AR handoff** works from any of these: every generation carries a place-in-your-room link, and the whole pipeline is public and keyless rather than ChatGPT-exclusive. See [AR in ChatGPT](#sec-186).-- **Spatial MCP** is the open, CC0 response shape that makes a 3D scene a native MCP result instead of a URL in text. three.ws is the reference implementation; the shape is renderer-agnostic and carries no payment, wallet, or coin surface. See [Spatial MCP](#sec-659).+- **The keyless connector** at `https://three.ws/api/mcp-studio` is a free MCP server exposing only 3D generation tools: no account, no payment, no API key, no wallet, no token. That is the surface submitted to the ChatGPT App Directory. See [MCP 3D Studio](#sec-418).+- **The paid sibling** at `https://three.ws/api/mcp-3d` is a separate server with rigging, animation, retexturing, and analysis, authenticated by OAuth 2.1 or paid per call over x402. It shares none of the keyless server's surface. See [3D Studio MCP](#sec-414).+- **The custom GPT** in the GPT Store calls an Actions contract served from `/.well-known/3d-studio-openapi.yaml`. Its builder configuration is checked in, because the GPT itself is configured by hand: [Custom GPT config](#sec-186).+- **AR handoff** works from any of these: every generation carries a place-in-your-room link, and the whole pipeline is public and keyless rather than ChatGPT-exclusive. See [AR in ChatGPT](#sec-187).+- **Spatial MCP** is the open, CC0 response shape that makes a 3D scene a native MCP result instead of a URL in text. three.ws is the reference implementation; the shape is renderer-agnostic and carries no payment, wallet, or coin surface. See [Spatial MCP](#sec-667).++**2026 program year.** API and ChatGPT/Codex benefits are provisioned through 2027-06-30 and are restricted to approved partner activities: [openai-partner-benefits-2026.md](#sec-485).-**Saying it correctly.** Write the status as "OpenAI Select Partner". three.ws is an independent member of the network at the Select tier: not an OpenAI product, and not endorsed by OpenAI beyond the partner designation. Badge rules, the required independence line, and every asset are in [`marketing/openai-select-partner/badge-usage.md`](../marketing/openai-select-partner/badge-usage.md); the graphics cleared for editorial use are in [Press kit](#sec-505). The pre-submission verification pack is [`prompts/finish/_context/openai-pr-00-START-HERE.md`](../prompts/finish/_context/openai-pr-00-START-HERE.md).+**Saying it correctly.** Write the status as "OpenAI Select Partner". three.ws is an independent member of the network at the Select tier: not an OpenAI product, and not endorsed by OpenAI beyond the partner designation. Badge rules, the required independence line, and every asset are in [`marketing/openai-select-partner/badge-usage.md`](../marketing/openai-select-partner/badge-usage.md); the graphics cleared for editorial use are in [Press kit](#sec-512). The pre-submission verification pack is [`prompts/finish/_context/openai-pr-00-START-HERE.md`](../prompts/finish/_context/openai-pr-00-START-HERE.md).---@@ -121520,9 +121923,9 @@ The page's stat bar reads 8 partners, 22 chains, and an infinity glyph for scale**What the page claims.** three.ws 3D agent identity and x402 payment rails integrate with IBM watsonx and IBM Granite. Agents run enterprise AI models while maintaining on-chain identity and executing real micropayments, all from a single agent profile. Card tags: watsonx.ai, Granite, x402, MCP.-**What the integration is.** Agents can think on IBM Granite foundation models served through IBM watsonx.ai, using your own IBM Cloud credentials. On top of that runtime sit the Granite-backed API surfaces (avatar brain, Guardian trust layer, TimeSeries forecasting, digital twin, semantic discovery, vision) and an MCP server, all documented in [IBM watsonx and Granite](#sec-378). [IBM Granite x402 MCP](#sec-377) covers the pay-per-call path: an MCP client reaches Granite inference and settles per call in stablecoin from a wallet it already controls, with no IBM Cloud account of its own.+**What the integration is.** Agents can think on IBM Granite foundation models served through IBM watsonx.ai, using your own IBM Cloud credentials. On top of that runtime sit the Granite-backed API surfaces (avatar brain, Guardian trust layer, TimeSeries forecasting, digital twin, semantic discovery, vision) and an MCP server, all documented in [IBM watsonx and Granite](#sec-382). [IBM Granite x402 MCP](#sec-381) covers the pay-per-call path: an MCP client reaches Granite inference and settles per call in stablecoin from a wallet it already controls, with no IBM Cloud account of its own.-**The caveat that must not be dropped.** [`docs/ibm.md`](#sec-378) states it plainly: three.ws is an IBM Business Partner, but the public showcase is not the partnership. The `/api/ibm/*` tools are an independent set of developer tools built on IBM's publicly available Granite models. They are not official IBM partnership deliverables, not IBM products, and not endorsed by IBM. The formal partnership work is being built on the IBM platform and is not yet public. Never present the public demos as that work.+**The caveat that must not be dropped.** [`docs/ibm.md`](#sec-382) states it plainly: three.ws is an IBM Business Partner, but the public showcase is not the partnership. The `/api/ibm/*` tools are an independent set of developer tools built on IBM's publicly available Granite models. They are not official IBM partnership deliverables, not IBM products, and not endorsed by IBM. The formal partnership work is being built on the IBM platform and is not yet public. Never present the public demos as that work.Live product surfaces: `three.ws/ibm/hello` (the partnership page) and `three.ws/ibm/x402-demo` (the x402 live demo).@@ -121530,20 +121933,20 @@ Live product surfaces: `three.ws/ibm/hello` (the partnership page) and `three.ws## Amazon Web Services-**What the page claims.** Deployed on AWS infrastructure with Marketplace availability. Enterprises can provision three.ws agent capabilities directly through their existing AWS billing, with support for VPC deployment and IAM-integrated access control. Card tags: Marketplace, EC2, IAM. The card's link label reads "How we run on AWS" and points at `/aws`, the internal partner page. It used to read "View on AWS Marketplace", which promised an external listing the link never opened; the Marketplace listing itself is covered in [AWS Marketplace](#sec-164).+**What the page claims.** Deployed on AWS infrastructure with Marketplace availability. Enterprises can provision three.ws agent capabilities directly through their existing AWS billing, with support for VPC deployment and IAM-integrated access control. Card tags: Marketplace, EC2, IAM. The card's link label reads "How we run on AWS" and points at `/aws`, the internal partner page. It used to read "View on AWS Marketplace", which promised an external listing the link never opened; the Marketplace listing itself is covered in [AWS Marketplace](#sec-165).-**What the integration is.** The AWS Marketplace SaaS contract is implemented and deployed: a fulfillment endpoint that exchanges the marketplace token for a customer identifier via `ResolveCustomer`, a signature-verified SNS webhook for subscribe and unsubscribe lifecycle events, account linking after the post-subscribe redirect, and daily metering plus entitlement checks. The subscription itself is a free front door: it links an AWS account to a three.ws account and issues an x402 access key, and usage is then paid per call in stablecoin over x402. AWS Marketplace does not meter or bill the usage. Code lives in `api/aws-marketplace/` and `api/_lib/aws-marketplace.js`; the reference is [AWS Marketplace](#sec-164).+**What the integration is.** The AWS Marketplace SaaS contract is implemented and deployed: a fulfillment endpoint that exchanges the marketplace token for a customer identifier via `ResolveCustomer`, a signature-verified SNS webhook for subscribe and unsubscribe lifecycle events, account linking after the post-subscribe redirect, and daily metering plus entitlement checks. The subscription itself is a free front door: it links an AWS account to a three.ws account and issues an x402 access key, and usage is then paid per call in stablecoin over x402. AWS Marketplace does not meter or bill the usage. Code lives in `api/aws-marketplace/` and `api/_lib/aws-marketplace.js`; the reference is [AWS Marketplace](#sec-165).**Status wording differs across surfaces, so quote the surface you are on.**- The `/partners` card says "Marketplace availability".- The `/aws` page badge says "AWS Partner, Software Path" and its hero says "Marketplace listing coming soon".-- [`docs/listings.md`](#sec-403) records three.ws as an AWS Partner and the Marketplace listing as not yet created. On 2026-09-16 AWS Marketplace search returned no three.ws product and production `POST /api/aws-marketplace/subscription` answered `503 not_configured`.-- [`docs/aws-marketplace-listing-kit.md`](#sec-163) says the backend integration is built and deployed but the listing itself has not yet been created in the AWS Marketplace Management Portal.+- [`docs/listings.md`](#sec-407) records three.ws as an AWS Partner and the Marketplace listing as not yet created. On 2026-09-16 AWS Marketplace search returned no three.ws product and production `POST /api/aws-marketplace/subscription` answered `503 not_configured`.+- [`docs/aws-marketplace-listing-kit.md`](#sec-164) says the backend integration is built and deployed but the listing itself has not yet been created in the AWS Marketplace Management Portal.The `/aws` hero once told buyers they could subscribe with AWS credits, bill usage to their AWS invoice, and count it toward EDP commitments. None of that is true of a free subscription with usage paid over x402; the stale sentence was removed from the page and every locale on 2026-09-16. Do not reintroduce it.-Do not resolve that spread by picking the strongest claim. If you need one sentence, the safe one is the one the product page uses: three.ws is an AWS Partner, and the Marketplace listing is coming. Longer-form pieces written for AWS channels are [partner spotlight](#sec-165), [MCP agents](#sec-159), and [Marketplace metering in front of x402](#sec-158).+Do not resolve that spread by picking the strongest claim. If you need one sentence, the safe one is the one the product page uses: three.ws is an AWS Partner, and the Marketplace listing is coming. Longer-form pieces written for AWS channels are [partner spotlight](#sec-166), [MCP agents](#sec-160), and [Marketplace metering in front of x402](#sec-159).---@@ -121553,7 +121956,7 @@ Do not resolve that spread by picking the strongest claim. If you need one sente**What the integration is.** Production runs on Google Cloud: one Cloud Run service serves the static frontend, the route table, and every API handler, with the crons on Cloud Scheduler and the GPU model workers on their own services. Vertex AI provides the Gemini and image lanes. The operational detail is in [production runbook](ops/gcp-production.md), [fleet and quota plan](ops/gcp-credits-plan.md), and [model workers](ops/gcp-model-workers.md).-**Programme status.** [`docs/listings.md`](#sec-403) records three.ws as a **member of Google Cloud for Web3 Startups**, with the programme backing compute and Vertex AI usage, and records Google Cloud Marketplace separately as **open to partnership** (no listing yet). The page card describes the technical dependency, not a marketplace listing; keep those two apart.+**Programme status.** [`docs/listings.md`](#sec-407) records three.ws as a **member of Google Cloud for Web3 Startups**, with the programme backing compute and Vertex AI usage, and records Google Cloud Marketplace separately as **open to partnership** (no listing yet). The page card describes the technical dependency, not a marketplace listing; keep those two apart.---@@ -121561,9 +121964,9 @@ Do not resolve that spread by picking the strongest claim. If you need one sente**What the page claims.** Alibaba Cloud extends three.ws into APAC markets with Qwen model integration and regional MCP server deployment. three.ws agents reach global audiences with low-latency inference close to users in Asia. Card tags: Qwen, MCP, APAC.-**What the integration is.** Qwen models are first-class lanes in the platform's multi-model brain router (`/api/brain/chat`), reached through DashScope alongside the other providers, so an agent can be pointed at a Qwen model the same way it is pointed at any other. See [the agent brain](#sec-172) for the router and the model ids.+**What the integration is.** Qwen models are first-class lanes in the platform's multi-model brain router (`/api/brain/chat`), reached through DashScope alongside the other providers, so an agent can be pointed at a Qwen model the same way it is pointed at any other. See [the agent brain](#sec-173) for the router and the model ids.-**Listing status.** [`docs/listings.md`](#sec-403) records the Alibaba Cloud International Marketplace listing as **Live**, with a product listing, a storefront, and an editorial feature published on the Alibaba Cloud Marketplace blog. That doc holds the canonical links; treat it as the source of truth rather than restating URLs here.+**Listing status.** [`docs/listings.md`](#sec-407) records the Alibaba Cloud International Marketplace listing as **Live**, with a product listing, a storefront, and an editorial feature published on the Alibaba Cloud Marketplace blog. That doc holds the canonical links; treat it as the source of truth rather than restating URLs here.---@@ -121573,10 +121976,10 @@ Do not resolve that spread by picking the strongest claim. If you need one sente**What the integration is.** Two distinct things, and the docs keep them distinct:-- **Inception membership**, accepted July 2026. [NVIDIA Inception](#sec-449) states what membership adds (GPU credits, hardware access, engineering support) and where it shows up in the product.-- **The free hosted inference lane.** A large share of platform AI runs on NVIDIA-hosted models unlocked by a single `NVIDIA_API_KEY`, a rate-limited free tier with no per-model billing and no SLA, which is why the platform always keeps a fallback behind it. [NVIDIA models](#sec-450) is the canonical map of which model does what and where it is wired. Membership does not change that lane; it is how the platform scales past free-tier limits without giving up the free-first design.+- **Inception membership**, accepted July 2026. [NVIDIA Inception](#sec-453) states what membership adds (GPU credits, hardware access, engineering support) and where it shows up in the product.+- **The free hosted inference lane.** A large share of platform AI runs on NVIDIA-hosted models unlocked by a single `NVIDIA_API_KEY`, a rate-limited free tier with no per-model billing and no SLA, which is why the platform always keeps a fallback behind it. [NVIDIA models](#sec-454) is the canonical map of which model does what and where it is wired. Membership does not change that lane; it is how the platform scales past free-tier limits without giving up the free-first design.-[Nemotron spotlight](#sec-452) is a published community piece on building the text-to-3D pipeline on NIM. It is a developer-blog showcase, not a partnership document.+[Nemotron spotlight](#sec-456) is a published community piece on building the text-to-3D pipeline on NIM. It is a developer-blog showcase, not a partnership document.---@@ -121584,15 +121987,15 @@ Do not resolve that spread by picking the strongest claim. If you need one sente**What the page claims.** A builder-focused publishing partnership: feature articles, tutorials, and developer guides for people shipping with AI, published to HackerNoon's developer audience. Card tags: Publishing, Developer content.-**What the integration is.** Mechanical, and worth knowing if you write posts here: HackerNoon auto-imports from `https://three.ws/rss/announcements.xml`, polls roughly hourly, pulls every new item into the drafts queue, and publishes with canonical URLs pointing back to three.ws. There is no per-post action. Setup steps and the author-profile claim flow are in [Syndication](#sec-671); the listing row is in [Listings and distribution](#sec-403).+**What the integration is.** Mechanical, and worth knowing if you write posts here: HackerNoon auto-imports from `https://three.ws/rss/announcements.xml`, polls roughly hourly, pulls every new item into the drafts queue, and publishes with canonical URLs pointing back to three.ws. There is no per-post action. Setup steps and the author-profile claim flow are in [Syndication](#sec-679); the listing row is in [Listings and distribution](#sec-407).---## Quicknode-**What the page claims.** three.ws is a member of the Quicknode Startup Program with approved infrastructure credits. Quicknode's globally distributed RPC endpoints add capacity and redundancy to the chain access behind agent wallets, x402 settlement verification, and live Solana market data. Card tags: Solana RPC, Streams, Multi-chain. [`docs/listings.md`](#sec-403) records the programme as **accepted (2026-07)** with approved free infrastructure credits.+**What the page claims.** three.ws is a member of the Quicknode Startup Program with approved infrastructure credits. Quicknode's globally distributed RPC endpoints add capacity and redundancy to the chain access behind agent wallets, x402 settlement verification, and live Solana market data. Card tags: Solana RPC, Streams, Multi-chain. [`docs/listings.md`](#sec-407) records the programme as **accepted (2026-07)** with approved free infrastructure credits.-**What the integration is.** A rung in the Solana RPC failover chain, not the whole chain. Server-side calls build a chain across an explicit primary, keyed providers, operator-supplied fallbacks, keyless public endpoints, and a paid reserve tried last, rotating past anything rate-limited. [Solana integration](#sec-657) documents it, including the trap that matters operationally: never name the same endpoint as both the primary and the last-resort reserve, because the chain dedupes by URL and keeps the first occurrence, so the "reserve" silently absorbs all traffic.+**What the integration is.** A rung in the Solana RPC failover chain, not the whole chain. Server-side calls build a chain across an explicit primary, keyed providers, operator-supplied fallbacks, keyless public endpoints, and a paid reserve tried last, rotating past anything rate-limited. [Solana integration](#sec-665) documents it, including the trap that matters operationally: never name the same endpoint as both the primary and the last-resort reserve, because the chain dedupes by URL and keeps the first occurrence, so the "reserve" silently absorbs all traffic.---@@ -121600,7 +122003,7 @@ Do not resolve that spread by picking the strongest claim. If you need one senteWorth stating, because partner claims drift upward when nobody writes the boundary down:-- **No Intel, Microsoft, or Oracle programme appears on `/partners`.** [`docs/listings.md`](#sec-403) records Microsoft Azure Marketplace as **on roadmap**. Third-party model or component names that appear in the stack (for example the image-to-3D backends listed in [3D Studio MCP](#sec-410)) are technical dependencies, not partnerships.+- **No Intel, Microsoft, or Oracle programme appears on `/partners`.** [`docs/listings.md`](#sec-407) records Microsoft Azure Marketplace as **on roadmap**. Third-party model or component names that appear in the stack (for example the image-to-3D backends listed in [3D Studio MCP](#sec-414)) are technical dependencies, not partnerships.- **No tier is claimed beyond the chips on the cards.** "Strategic", "Cloud", "Media", and "Infrastructure" are groupings three.ws chose for its own page. Only two named programme statuses come from the partner: OpenAI Select Partner, and NVIDIA Inception member.- **No endorsement is claimed anywhere.** OpenAI, IBM, and NVIDIA all carry explicit independence language in their docs. Reproduce it.@@ -121614,15 +122017,15 @@ The page closes with four reasons, useful as the short pitch when someone asks:## Related-- [Partner prospects](#sec-484) and [the outreach plan](#sec-480): who we approach next, and how-- [Press kit](#sec-505): marks, announcement graphics, boilerplate, and the rules for all of it-- [Listings and distribution](#sec-403): marketplaces, ecosystem directories, and media partners with per-listing status-- [Integrations](#sec-383): the catalog of ways to put an agent on a site you do not control-- [x402](#sec-862): the payment rail behind the agent-to-agent micropayments every partner surface references+- [Partner prospects](#sec-491) and [the outreach plan](#sec-487): who we approach next, and how+- [Press kit](#sec-512): marks, announcement graphics, boilerplate, and the rules for all of it+- [Listings and distribution](#sec-407): marketplaces, ecosystem directories, and media partners with per-listing status+- [Integrations](#sec-387): the catalog of ways to put an agent on a site you do not control+- [x402](#sec-877): the payment rail behind the agent-to-agent micropayments every partner surface references----<a id="sec-475"></a>+<a id="sec-481"></a>> **Source:** `docs/partners/dextools-collab-kit.md` · [↑ table of contents](#table-of-contents)@@ -121632,7 +122035,7 @@ Prepared for the collab Frederic (DEXTools) offered in the `Three.ws <> DEXToolsNothing here is posted automatically. Posting to X or Telegram is owner-gated.-**Verified on 2026-10-09:** every three.ws and chat.sperax.io link below returned HTTP 200. The $THREE Social Boost record (three wins, $11,382 in buybacks, 2.47M $THREE held by DEXTools after the weekly) is from [the partnership proposal](#sec-476), which links each DEXTools receipt.+**Verified on 2026-10-09:** every three.ws and chat.sperax.io link below returned HTTP 200. The $THREE Social Boost record (three wins, $11,382 in buybacks, 2.47M $THREE held by DEXTools after the weekly) is from [the partnership proposal](#sec-482), which links each DEXTools receipt.**Do not claim:**- A visit count. `/api/coin/dextools-stats` is public and real, but the counter only started on 2026-10-08, so the number is still small. Point at the counter, never quote it.@@ -121840,15 +122243,15 @@ The ranking widgets, token safety and the MCP server run on the keyed DEXTools D## Related-- [DEXTools integration (developer doc)](#sec-246)-- [The DEXTools partnership proposal](#sec-476)-- [Chart Companion](#sec-183)-- [Token in 3D, as an embed](#sec-196)-- [X post drafts](#sec-819)+- [DEXTools integration (developer doc)](#sec-247)+- [The DEXTools partnership proposal](#sec-482)+- [Chart Companion](#sec-184)+- [Token in 3D, as an embed](#sec-197)+- [X post drafts](#sec-833)----<a id="sec-476"></a>+<a id="sec-482"></a>> **Source:** `docs/partners/dextools-proposal.md` · [↑ table of contents](#table-of-contents)@@ -121945,7 +122348,7 @@ No listing fee, no promotion, no endorsement, no change to how DEXTools ranks or----<a id="sec-477"></a>+<a id="sec-483"></a>> **Source:** `docs/partners/ibm-partner-plus.md` · [↑ table of contents](#table-of-contents)@@ -121957,16 +122360,16 @@ the program brochure. It exists because the Partner Plus newsletter arrives montof it is aimed at hardware resellers, and the two or three items that genuinely apply to uskeep getting lost in the noise.-Companion docs: [IBM watsonx and Granite](#sec-378) is the technical integration and the-partnership record, [IBM Granite x402 MCP](#sec-377) is the pay-per-call path,-[Partner ecosystem](#sec-474) is the public partner map, and-[the second community event](#sec-375) is the event proposal awaiting a date.+Companion docs: [IBM watsonx and Granite](#sec-382) is the technical integration and the+partnership record, [IBM Granite x402 MCP](#sec-381) is the pay-per-call path,+[Partner ecosystem](#sec-480) is the public partner map, and+[the second community event](#sec-379) is the event proposal awaiting a date.---## The framing rules come first-Everything below inherits the rules set in [`docs/ibm.md`](#sec-378), and none of them may+Everything below inherits the rules set in [`docs/ibm.md`](#sec-382), and none of them maybe softened to make a listing or a campaign read better:- three.ws is an IBM Business Partner. That is a designation, **not an endorsement**.@@ -121988,8 +122391,8 @@ Verified on 2026-09-09 against the live site and the repo:| Asset | State | Evidence ||---|---|---|-| IBM Business Partner status | Active | [`docs/ibm.md`](#sec-378), `/partners` IBM card (Strategic chip) |-| Granite on watsonx.ai in the product | Live | [`docs/ibm.md`](#sec-378) |+| IBM Business Partner status | Active | [`docs/ibm.md`](#sec-382), `/partners` IBM card (Strategic chip) |+| Granite on watsonx.ai in the product | Live | [`docs/ibm.md`](#sec-382) || Partnership page | Live | `three.ws/ibm/hello` || x402 demo | Live | `three.ws/ibm/x402-demo` || Free keyless MCP server | Live | `three.ws/api/mcp-studio` |@@ -121997,8 +122400,8 @@ Verified on 2026-09-09 against the live site and the repo:| A2A agent card, 10 declared skills | Live, HTTP 200 | `three.ws/.well-known/agent-card.json` || x402 paid-service catalog | Live, HTTP 200 | `three.ws/.well-known/x402.json` || OAuth metadata with static client auth | Live | `three.ws/.well-known/oauth-authorization-server` |-| IBM user group on IBM Community | Active, moderated by us | [`docs/ibm-community.md`](#sec-373) |-| In-world community meetup | Held | [`docs/ibm-community-blog-meetup-jessica.md`](#sec-359) |+| IBM user group on IBM Community | Active, moderated by us | [`docs/ibm-community.md`](#sec-377) |+| In-world community meetup | Held | [`docs/ibm-community-blog-meetup-jessica.md`](#sec-363) || CSP allows framing from IBM and Seismic | Live | `frame-ancestors 'self' https://ibm.com https://*.ibm.com https://*.seismic.com` |That last row matters more than it looks. The newsletter's footer points partners at the@@ -122044,7 +122447,7 @@ engineering. So BYOL first, paid listing later if the volume justifies the paper| Functioning Remote MCP server endpoint | Have it: `three.ws/api/mcp-3d`, live, MCP protocol `2025-06-18` || Supported auth (OAuth2 without Dynamic Client Registration, API key, bearer, basic, key-value) | **Satisfied with no code change.** Our OAuth advertises a `registration_endpoint`, but it also supports `client_secret_basic` and `client_secret_post`, so IBM gets a pre-registered static client and never touches DCR || Test credentials that stay valid through onboarding | We can mint these; they must be tracked so they are not rotated mid-review |-| Setup documentation plus at least one use case | Have it: [`docs/mcp-3d-studio.md`](#sec-410), [`docs/mcp-studio.md`](#sec-414) |+| Setup documentation plus at least one use case | Have it: [`docs/mcp-3d-studio.md`](#sec-414), [`docs/mcp-studio.md`](#sec-418) || Listing icon | **Built and verified.** IBM requires SVG only, transparent background, under 200 KB, legible at 48x48. A PNG fails validation. Shipped at `public/partners/ibm/three-ws-agent-connect-icon.svg` || `APP_ID` from the IBM Ecosystem team | **The only true blocker.** Obtained by emailing `[email protected]` || IBM Cloud account, Concierge access | Owner action |@@ -122080,10 +122483,10 @@ integrations, and its IBM Bob item turned out to be a client we could support th| Boomerang (share IBM content through a partner-branded experience) | **Ignore for now** | Built for partners who generate pipeline for IBM products. Our audience comes to us for three.ws, not for IBM content, and a partner-branded IBM reading room would dilute the no-endorsement framing above. Revisit only if an Agent Connect listing gives us an IBM product to point prospects at. || Download your partner certificate from the Partner Portal | **Do (owner, 2 minutes)** | It is the proof document for bids, marketplace applications, and "are you really an IBM Business Partner" questions. Download it once and keep it with the owner's business records, **not in this repo** (it carries the partner ID) and not on the public site. When a listing form asks for proof, attach it from there. || My Digital Marketing: Affinity Plays (sell IBM into AWS, Microsoft, Veeam accounts) | **Ignore** | Cross-sell kits for resellers. |-| My Digital Marketing: Webinar Playbook | **Pull it** | Directly useful for the second community event in [ibm-next-event.md](#sec-375) and the in-world session kits under `marketing/growth/events/`. Read it against our format (an hour inside `/play`, not a slide webinar) and keep what applies, chiefly the promotion timeline and the follow-up sequence. |+| My Digital Marketing: Webinar Playbook | **Pull it** | Directly useful for the second community event in [ibm-next-event.md](#sec-379) and the in-world session kits under `marketing/growth/events/`. Read it against our format (an hour inside `/play`, not a slide webinar) and keep what applies, chiefly the promotion timeline and the follow-up sequence. || My Digital Marketing: IBM Photography (100+ persona-based images) | **Use only inside IBM co-marketing** | Licensed for IBM partner campaigns. Fine on an IBM Community post or a co-branded asset in `marketing/ibm-partner-plus/`; never as general three.ws site imagery, where it would imply an IBM endorsement we may not claim. || My Digital Marketing: Confluent Kafka migration kits | **Ignore** | Same reasoning as September's Confluent track. |-| IBM Bob self-hosted option | **Shipped on our side** | Bob is IBM's AI development partner, and it reads remote MCP servers from `.bob/mcp.json`. We added it as a first-class client on the same day: an **IBM Bob** tab on [three.ws/connect](/connect) that writes the entry for whichever server you pick, `npx three-ws setup --clients bob` in the [CLI](#sec-191), and an `ibm-bob` block in `/.well-known/mcp.json` recommending the free, no-sign-in 3D Studio server. The self-hosted angle matters for IBM's sensitive-workload customers: our free server needs no account and no key, so a locked-down Bob install can use it without handing us credentials. Untested against a live Bob install; the config follows IBM's published format. |+| IBM Bob self-hosted option | **Shipped on our side** | Bob is IBM's AI development partner, and it reads remote MCP servers from `.bob/mcp.json`. We added it as a first-class client on the same day: an **IBM Bob** tab on [three.ws/connect](/connect) that writes the entry for whichever server you pick, `npx three-ws setup --clients bob` in the [CLI](#sec-192), and an `ibm-bob` block in `/.well-known/mcp.json` recommending the free, no-sign-in 3D Studio server. The self-hosted angle matters for IBM's sensitive-workload customers: our free server needs no account and no key, so a locked-down Bob install can use it without handing us credentials. Untested against a live Bob install; the config follows IBM's published format. || Chatter reminders for partner-owned opportunities inactive 45+ days | **Ignore** | CRM hygiene for registered deals. We have none registered. || Customer story (GlassHouse Systems, IBM i on Power Virtual Server) | **Ignore** | Not our market. || **Partner Growth Day: Accelerate through Marketplace**, Tue 20 October, virtual | **Attend (owner)** | The Marketplace route is where Agent Connect lives. Go with a concrete ask: the BYOL listing for the 3D Studio MCP server, the submission pack already filled in at [agent-connect-listing.md](../marketing/ibm-partner-plus/agent-connect-listing.md). The `APP_ID` request to `[email protected]` should go out **before** the 20th so the session can be used to chase it rather than start it. |@@ -122138,14 +122541,14 @@ marketing/quicknode/ finished graphicsThat gap is the reason IBM co-marketing keeps being improvised per event. The fix is a kitbuilt to the same shape as the OpenAI one, carrying the badge rules and the-no-endorsement language from [`docs/ibm.md`](#sec-378) so nobody has to rediscover the+no-endorsement language from [`docs/ibm.md`](#sec-382) so nobody has to rediscover theconstraints under deadline.---## Stalled since June, worth restarting in the same conversation-[`docs/ibm.md`](#sec-378) records a co-marketing ramp-up agreed on 2026-06-18 after+[`docs/ibm.md`](#sec-382) records a co-marketing ramp-up agreed on 2026-06-18 aftermeetings with IBM's development and marketing sides. Three things were promised. As of thelast update to that doc, the status is:@@ -122153,7 +122556,7 @@ last update to that doc, the status is:2. **A dedicated three.ws page on the IBM domain.** Recorded as not yet live. The doc'sinstruction stands: do not link to it or present it as public until IBM ships it.3. **A second live IBM Community event.** The proposal is written and costed in- [`ibm-next-event.md`](#sec-375), recommending a one-week open creation+ [`ibm-next-event.md`](#sec-379), recommending a one-week open creationcontest closing with a crowning ceremony inside the three.ws world. It has been waitingon one decision since it was written: **a date**. That is the cheapest unblock on thisentire page.@@ -122171,7 +122574,7 @@ IBM's ecosystem team something new to co-market.`APP_ID` for a **BYOL** MCP server listing. This is the single unblock for the catalog.2. Confirm IBM Cloud account and Concierge access for the company entity.3. Pick a date for the second community event so- [`ibm-next-event.md`](#sec-375) can leave the shelf.+ [`ibm-next-event.md`](#sec-379) can leave the shelf.4. Request My Digital Marketing access and the Build track Partner Marketing Kit.5. Decide whether the paid listing is worth the tax and banking paperwork later. It is notneeded for the first listing.@@ -122231,7 +122634,7 @@ touch our product.----<a id="sec-478"></a>+<a id="sec-484"></a>> **Source:** `docs/partners/openai-ibm-nvidia-growth-plan.md` · [↑ table of contents](#table-of-contents)@@ -122289,9 +122692,9 @@ audience.- [Showcase submission](../prompts/store-submissions/_generated/openai-showcase-submission.md)- [ChatGPT app submission](../prompts/store-submissions/_generated/openai-submission.md)-- [OpenAI listing channel map](#sec-464)-- [Developer Community: 3D Studio](#sec-462)-- [Developer Community: physical-world agents](#sec-463)+- [OpenAI listing channel map](#sec-469)+- [Developer Community: 3D Studio](#sec-467)+- [Developer Community: physical-world agents](#sec-468)## IBM@@ -122358,7 +122761,7 @@ approved stronger wording. For IBM-owned channels, lead with governed agents, ReGranite, and enterprise workflow value. Token-specific messaging can be a separatedeveloper story when it is technically relevant and the venue permits it.-Full internal audit: [IBM Partner Plus opportunities](#sec-477).+Full internal audit: [IBM Partner Plus opportunities](#sec-483).## NVIDIA@@ -122399,7 +122802,7 @@ Complete the product record, download the current asset package from`Portal > Benefits > Co-Branded Marketing Assets`, then use the narrow reply already draftedfor the two unanswered asks: Startup Showcase routing and an ACE/digital-human contact.-Prepared asset: [NVIDIA catalog and co-marketing request](#sec-444).+Prepared asset: [NVIDIA catalog and co-marketing request](#sec-448).### 3. Build proof that NVIDIA can amplify@@ -122476,7 +122879,7 @@ audience and product.| Sep 18 to 24 | Publish the prepared OpenAI and NVIDIA technical posts on a measured cadence | Owner | live URLs added to the publishing tracker || After portal save | Reply once to NVIDIA with only the unanswered Showcase-routing and ACE-contact questions | Owner | sent reply in the existing thread || By Sep 29 | Decide on IBM TechXchange attendance | Owner | registration or explicit close |-| By Oct 14 | Assemble 30-day proof: usage, completion rate, latency, installs, and examples | Growth + engineering | [30-day proof brief, October 2026](#sec-482) (regenerate monthly with `npm run partners:proof`) |+| By Oct 14 | Assemble 30-day proof: usage, completion rate, latency, installs, and examples | Growth + engineering | [30-day proof brief, October 2026](#sec-489) (regenerate monthly with `npm run partners:proof`) |## Official program references@@ -122494,7 +122897,84 @@ audience and product.----<a id="sec-479"></a>+<a id="sec-485"></a>++> **Source:** `docs/partners/openai-partner-benefits-2026.md` · [↑ table of contents](#table-of-contents)++# OpenAI Partner Network: 2026 program-year benefits++**Status:** provisioned, notice received 2026-10-11. **Program year:** 2026-07-01 to 2027-06-30.+Everything below expires on **2027-06-30**; unused credits do not roll over.++three.ws is an OpenAI Select Partner (accepted 2026-07-14, see+[partners.md](partners.md#openai)). This page records what the 2026 program year added and the+rules that come with it. The designation wording is unchanged: write "OpenAI Select Partner", never+imply endorsement ([badge usage](../marketing/openai-select-partner/badge-usage.md)).++## What was provisioned++| Benefit | Allocation | Where it lives | Admin |+|---|---|---|---|+| Partner tier | Select | OpenAI Partner Network portal | The OPN portal administrator |+| API credits | USD 1,000 | A new, separate API organization | The OPN portal administrator |+| ChatGPT workspace | 300,000 ChatGPT/Codex credits | A new, separate ChatGPT workspace | The OPN portal administrator |++The organization ID and ChatGPT workspace ID are in the provisioning email from OpenAI Partner+Network and in the invitations. They are deliberately not copied into this public repository.++## Pending owner action++OpenAI sends two separate invitations to the portal administrator's inbox: one to the API+organization, one to the ChatGPT workspace. Check spam or junk if neither has arrived. Accepting+them is the only step left; nothing in the repo can do it.++Once the API organization exists, create a project key scoped to partner work and store it as a+distinct secret (for example `OPENAI_PARTNER_API_KEY`), never in place of the production+`OPENAI_API_KEY`. Keeping the two apart is what makes the usage rule below auditable.++## Usage rule (read before spending a credit)++OpenAI provides these benefits **exclusively for approved partner activities**. They are not for+general internal business use or for three.ws's use as an OpenAI customer. Permitted:++- testing OpenAI products and capabilities+- building and validating customer use cases+- developing proofs of concept+- demonstrating solutions to prospective customers+- preparing for customer implementations and deployments++So the credits do **not** run production traffic for three.ws itself (chat brains, workers, cron+jobs). They fund work that is partner-shaped. Candidates already on the roadmap:++| Use | Why it qualifies | Related doc |+|---|---|---|+| Validate the 3D Studio connector and Custom GPT against current models | Testing capabilities and validating a customer use case | [chatgpt-3d-studio-gpt.md](#sec-186), [mcp-studio.md](#sec-418) |+| Proof-of-concept builds for prospective customers (embodied agents, spatial MCP) | Proofs of concept and demos | [spatial-mcp.md](#sec-667) |+| Codex-assisted work on customer-facing integrations and the OpenAI Showcase submission | Preparing customer implementations | [openai-ibm-nvidia-growth-plan.md](#sec-484) |++Nothing on this platform's own production path should be repointed at the partner organization.++## Announcement++The pack is [announcements/openai-partner-benefits.md](#sec-120)+with the post bytes in `openai-partner-benefits.post.txt`. It states the program-year benefits and+what they will be used for, and carries no credit amounts: the figures are an account matter, not+news. Publishing is owner-gated; no X credentials exist on the dev machine, so it goes out from the+queue or `scripts/post-tweet.mjs` on a machine that has them.++## Calendar++| Date | Event |+|---|---|+| 2026-07-01 | Program year begins |+| 2026-10-11 | Provisioning notice received |+| 2027-06-30 | Credits, workspace access and benefits expire |++Set a review for **2027-05-01** to spend down or plan renewal.++---++<a id="sec-486"></a>> **Source:** `docs/partners/opportunities.md` · [↑ table of contents](#table-of-contents)@@ -122504,13 +122984,13 @@ Every partnership, program, marketplace, and directory three.ws touches, in onethe **single next action** and **who owns it**. This is the decision tool. It deliberatelydoes not restate the reference docs:-- [Partner ecosystem](#sec-474) is what each partnership **is**, and the framing rules.-- [Listings and distribution](#sec-403) is the descriptive record of every listing.-- [Publishing program](#sec-557) is the content and venue matrix.-- [OpenAI, IBM, and NVIDIA growth plan](#sec-478) turns the+- [Partner ecosystem](#sec-480) is what each partnership **is**, and the framing rules.+- [Listings and distribution](#sec-407) is the descriptive record of every listing.+- [Publishing program](#sec-564) is the content and venue matrix.+- [OpenAI, IBM, and NVIDIA growth plan](#sec-484) turns thehighest-value partner opportunities into a 30-day listing and co-marketing sequence.-- [Partner prospects](#sec-484) is the scored list of new partners from the 2026-10-09- sweep, and [the outreach plan](#sec-480) is how it is worked. A prospect moves+- [Partner prospects](#sec-491) is the scored list of new partners from the 2026-10-09+ sweep, and [the outreach plan](#sec-487) is how it is worked. A prospect movesonto this page when it gets its first action.This page is the part those three do not answer: **what is actually stuck, on whom, and@@ -122533,7 +123013,7 @@ for a cycle, not delayed. Nothing here is on anyone's calendar yet.| By when | Opportunity | The one action | Owner ||---|---|---|---|| **2026-10-09, 5 p.m. PT** | NVIDIA GTC 2027 Content Interest Survey ([form](https://forms.gle/iwGUwc5YQfw6f7X27)). Checked 2026-10-08: open since 2026-09-16, closes tomorrow. Answers are written | Paste the answers from [nvidia-gtc-2027-poster.md](nvidia-gtc-2027-poster.md#content-interest-survey-closes-2026-10-09-5-pm-pt) | Owner |-| **2026-11-10, 5 p.m. PT** | NVIDIA GTC 2027 poster call (San Jose, 2027-03-15 to 03-18). Checked 2026-10-08: [open](https://www.nvidia.com/en-us/gtc/present/call-for-submissions/), original technical work only, nothing promotional. Two submissions are written with measured production evidence, including a new rig-coverage benchmark (`node scripts/a2f-rig-coverage.mjs`). No speaker call is posted; the Startup Pavilion stays invite-only | Submit poster A from [nvidia-gtc-2027-poster.md](#sec-448) as the presenting author (acceptance means attending the poster reception) | Owner |+| **2026-11-10, 5 p.m. PT** | NVIDIA GTC 2027 poster call (San Jose, 2027-03-15 to 03-18). Checked 2026-10-08: [open](https://www.nvidia.com/en-us/gtc/present/call-for-submissions/), original technical work only, nothing promotional. Two submissions are written with measured production evidence, including a new rig-coverage benchmark (`node scripts/a2f-rig-coverage.mjs`). No speaker call is posted; the Startup Pavilion stays invite-only | Submit poster A from [nvidia-gtc-2027-poster.md](#sec-452) as the presenting author (acceptance means attending the poster reception) | Owner || **Now** | GitHub Open Source Friday. [Issue #254](https://github.com/githubevents/open-source-friday/issues/254) is open with the `approved` label. Checked 2026-10-08: still no date posted, and no activity since GitHub's 2026-09-01 request to pick a slot | Select a Friday at `https://gh.io/osf-booking`, then reply on issue #254 with the date | Owner || **Before 2026-10-31** | [Hacktoberfest 2026 Fest](https://hacktoberfest.com/host/). Checked 2026-10-08: still "Applications are now open and Fests are confirmed on a rolling basis" with no published deadline, but Hacktoberfest ends 2026-10-31 and decisions take about a week, so a Fest application is only useful in roughly the next two weeks. Apply at `https://hacktoberfest.com/my/` | Name the venue, city, capacity, and host, then submit either a one-day Hack Day or Meet Up application | Owner || **2026-10-26** | IBM TechXchange attendance. [IBM's FAQ](https://www.ibm.com/events/techxchange/faq), checked 2026-10-08: the early bird (USD 1279.20) **closed 2026-09-26 unused**; the standard pass is USD 1599, the hotel block closed 2026-10-01, and full refunds ended 2026-09-22. The event runs 2026-10-26 to 10-29 at the Georgia World Congress Center, Atlanta; the speaking CFP closed in May, but sponsorship, the Sandbox Expo and the colocated user-group route are open, and we moderate an IBM Community user group | Register, or decide not to attend | Owner |@@ -122541,8 +123021,8 @@ for a cycle, not delayed. Nothing here is on anyone's calendar yet.| Spring 2027 | IBM TechXchange 2027 call for speakers | Submit when it opens | Owner |Dates and intake routes for the IBM rows are verified in-[ibm-visibility-map.md](#sec-376); the GTC row in-[nvidia-visibility-map.md](#sec-454).+[ibm-visibility-map.md](#sec-380); the GTC row in+[nvidia-visibility-map.md](#sec-458).---@@ -122559,7 +123039,7 @@ work already done and is waiting on a single human step.| 4 | **NVIDIA Accelerated Apps Catalog** | Complete the existing Shipping product record exactly as NVIDIA requested | NVIDIA answered the request: the portal record is the periodically reviewed application. Copy, technical evidence, logo, brand color, and screenshots are ready; only the authenticated save remains. On 2026-09-16 three.ws was absent from all 1,846 public catalog records. Checked 2026-10-08: the catalog URL now redirects to `marketplace.nvidia.com/en-us/enterprise/applications/`, which did not load for an automated check, and a web search finds no three.ws listing. || 5 | **NVIDIA NGC Catalog** | Sign the partner legal agreement and ask NVIDIA whether one replica per GPU meets the multi-GPU rule | The only NVIDIA directory with self-serve intake. The EULA prerequisite is closed, and the portable container is built and passes its in-image tests (rebuilt 2026-10-08 on current source; [details](nvidia-ngc-listing.md#gate-2-the-kernels-are-compiled-for-one-gpu-generation)). || 6 | **OpenAI Plugin Directory** | Submit | We already meet the gating requirement (public OAuth 2.1 MCP server), and the output-quality blocker that held this back is closed: the forge quality gate measured **10/10 verdicts** on production 2026-09-11, up from 0/10 two days earlier. It was closed by fixing the vision failover chain, not by clearing the GCP billing hold. |-| 7 | **Second IBM community event** | Pick a date | A fully costed proposal ([ibm-next-event.md](#sec-375)) has been waiting on nothing but a calendar decision. Cheapest unblock on this page. |+| 7 | **Second IBM community event** | Pick a date | A fully costed proposal ([ibm-next-event.md](#sec-379)) has been waiting on nothing but a calendar decision. Cheapest unblock on this page. |---@@ -122569,20 +123049,20 @@ No action required. Listed so nobody re-pitches something we already have.| Surface | Since | Reference ||---|---|---|-| IBM Business Partner | active | [ibm.md](#sec-378) |-| OpenAI Select Partner | active | [partners.md](#sec-474) |-| NVIDIA Inception | 2026-07 | [nvidia-inception.md](#sec-449) |+| IBM Business Partner | active | [ibm.md](#sec-382) |+| OpenAI Select Partner | active | [partners.md](#sec-480) |+| NVIDIA Inception | 2026-07 | [nvidia-inception.md](#sec-453) || Google Cloud for Web3 Startups | member | [gcp-credits-plan.md](ops/gcp-credits-plan.md) |-| QuickNode Startup Program | 2026-07 | [listings.md](#sec-403) |-| Alibaba Cloud Marketplace | live; product page, storefront, and blog feature all render three.ws (checked 2026-09-16) | [listings.md](#sec-403) |-| BNB Chain Dappbay | live | [listings.md](#sec-403) |-| Hugging Face org account | live; one Space, one model, two articles, latest article 2026-08-29 (checked 2026-09-16) | [huggingface.md](#sec-354) |+| QuickNode Startup Program | 2026-07 | [listings.md](#sec-407) |+| Alibaba Cloud Marketplace | live; product page, storefront, and blog feature all render three.ws (checked 2026-09-16) | [listings.md](#sec-407) |+| BNB Chain Dappbay | live | [listings.md](#sec-407) |+| Hugging Face org account | live; one Space, one model, two articles, latest article 2026-08-29 (checked 2026-09-16) | [huggingface.md](#sec-358) || Official MCP Registry | live; 72 servers under `io.github.nirholas/*`, including `io.github.nirholas/three.ws` 1.0.1 (published 2026-06-12) (checked 2026-09-16). The staged batch has since landed: `herald-mcp`, `knock-mcp`, and `home-mcp` 0.1.0 all resolve (checked 2026-10-08) | [registry search](https://registry.modelcontextprotocol.io/v0/servers?search=three.ws) || PulseMCP | live, ingested from the official registry, 215 visitors that week (checked 2026-09-16) | [pulsemcp.com/servers/nirholas-three-ws](https://www.pulsemcp.com/servers/nirholas-three-ws) || Glama MCP directory | live as connectors ingested from the official registry, but **unclaimed** (checked 2026-09-16); see the claim row below | [three.ws connector](https://glama.ai/mcp/connectors/io.github.nirholas/three.ws) || LobeHub MCP marketplace | live; `@three-ws/portal`, `@three-ws/avatar-mcp`, `@three-ws/x402-mcp` and other `nirholas-*` servers are indexed (checked 2026-09-16). The chat plugin is not; see Open, unclaimed | [@three-ws/portal](https://lobehub.com/mcp/nirholas-three-ws-portal) |-| IBM Community user group | live, we moderate it | [ibm-community.md](#sec-373) |-| pump.fun verification and feature article | live | [listings.md](#sec-403) |+| IBM Community user group | live, we moderate it | [ibm-community.md](#sec-377) |+| pump.fun verification and feature article | live | [listings.md](#sec-407) |---@@ -122594,7 +123074,7 @@ The work is done or nearly done. A human on our side has to act.|---|---|---|---|| OKX.AI agent #2632 | Rejected 2026-09-03, cause fixed 2026-09-05 | On-chain `agent update`, then activate. The stored listing copy is stale, so it is update-then-activate, not activate alone | Owner || IBM Agent Connect (BYOL MCP listing) | Fully prepared | `APP_ID` request email, then Concierge | Owner |-| AWS Marketplace | Integration code deployed, listing never created. Checked 2026-09-16 and again 2026-10-08: `three-ws-api` carries **no `AWS_MP_*` variable** (none in `.env`/`.env.local` either), so `POST /api/aws-marketplace/subscription` answers `503 not_configured` and a buyer arriving from a new listing would hit the error page | From seller account `155407237916`, create the metering IAM key and SNS/EventBridge secret listed in [aws-marketplace.md](#sec-164), set them with `gcloud run services update --update-env-vars`, then create the product in the portal | Owner |+| AWS Marketplace | Integration code deployed, listing never created. Checked 2026-09-16 and again 2026-10-08: `three-ws-api` carries **no `AWS_MP_*` variable** (none in `.env`/`.env.local` either), so `POST /api/aws-marketplace/subscription` answers `503 not_configured` and a buyer arriving from a new listing would hit the error page | From seller account `155407237916`, create the metering IAM key and SNS/EventBridge secret listed in [aws-marketplace.md](#sec-165), set them with `gcloud run services update --update-env-vars`, then create the product in the portal | Owner || NVIDIA NGC Catalog | Prerequisites cleared; portable `ngc-candidate` image rebuilt and tested 2026-10-08 | Partner legal agreement (owner), then one Ampere or Hopper inference check on a GCE VM (eng) | Owner + eng || NVIDIA Accelerated Apps Catalog | NVIDIA answered 2026-09-14; complete Shipping records are periodically reviewed, and the current record still understates the runtime stack | Complete the technology fields, Product Description, Technical Details, logo, and brand color in the portal; then check the public catalog monthly | Owner || OpenAI Plugin Directory | Eligible | Submit | Owner |@@ -122604,12 +123084,12 @@ The work is done or nearly done. A human on our side has to act.| IBM G2 review | Draft ready in [ibm-g2-review.md](../marketing/partner-packets/ibm-g2-review.md), written in the past tense because production has had no `WATSONX_*` credentials since at least 2026-07-29 (checked 2026-09-16) | The actual watsonx.ai user rewrites it in their own words with their own console screenshot, or restores the credentials first | Owner || CoinGecko market addition for $THREE | Form researched; only one of our live venues qualifies | Submit for that venue | Owner || HackerNoon author page | Checked 2026-10-08: [hackernoon.com/u/three-ws](https://hackernoon.com/u/three-ws) still shows **no published stories**. RSS import lands in the drafts queue; nothing has gone out from it. **New 2026-10-08:** the profile carries stray data that is not ours: the job title, the "Read My Stories" button, and the "Portfolio" link all describe or point at someone else's profile. The bio itself is correct | First clean the profile (title, stories link, portfolio link). Then open the drafts queue and submit the imported announcements for editorial review | Owner |-| DEXTools, reciprocal 3D embed | Our side is shipped: DEXTools charts are already a provider in every three.ws chart switcher, and as of 2026-09-20 `/coin3d` is framable and keyed by pair address, which is the identifier a DEXTools pair page already holds. As of 2026-10-08 proposal pillars 3 and 4 are built too: DEXTools leads every terminal row, launches get a Social Boost card, and every link we send is counted at `/api/coin/dextools-stats` ([surface map](listings.md#dextools)). The relationship has public receipts in both directions: three $THREE Social Boost wins with DEXTools buybacks behind them | Send [dextools-proposal.md](#sec-476) to a DEXTools partnerships or front-end contact. Nothing else is blocked; the embed is live and free whether or not they answer | Owner |+| DEXTools, reciprocal 3D embed | Our side is shipped: DEXTools charts are already a provider in every three.ws chart switcher, and as of 2026-09-20 `/coin3d` is framable and keyed by pair address, which is the identifier a DEXTools pair page already holds. As of 2026-10-08 proposal pillars 3 and 4 are built too: DEXTools leads every terminal row, launches get a Social Boost card, and every link we send is counted at `/api/coin/dextools-stats` ([surface map](listings.md#dextools)). The relationship has public receipts in both directions: three $THREE Social Boost wins with DEXTools buybacks behind them | Send [dextools-proposal.md](#sec-482) to a DEXTools partnerships or front-end contact. Nothing else is blocked; the embed is live and free whether or not they answer | Owner || Glama connector claim | Checked 2026-10-08: still unclaimed and **Unhealthy, 0.0% uptime over 51 days**, last tested 2026-10-07; Glama's own note blames missing test credentials. That is correct behaviour on our side, not a bug: `/api/mcp` deliberately answers an MCP client's `initialize` with the 401 that starts OAuth, so no unauthenticated health check can pass. Glama now also offers a domain claim through `https://three.ws/.well-known/glama.json` (already served) or a `_glama-claim.three.ws` DNS record | Claim ownership on the connector page (maintainer email `[email protected]` is already declared in `public/.well-known/glama.json`), then add a test profile under Admin | Owner |### Anthropic, which this page was missing-Worth stating plainly: [partners.md](#sec-474) lists eight partners and Anthropic is+Worth stating plainly: [partners.md](#sec-480) lists eight partners and Anthropic isnot one of them, while the agent brain defaults to Claude models and three Anthropicsurfaces sit at `ready-to-submit` in[the submission tracker](../prompts/store-submissions/_generated/TRACKER.md). It is the@@ -122629,7 +123109,7 @@ Nothing for us to do but keep the thread warm. Do not re-scope these into our ow| Opportunity | State | Note ||---|---|---|-| OpenAI Cookbook PR #2874 | Open since 2026-07-21. Checked 2026-10-08: still open and unmerged, review required, 24 comments, no activity since our own comment on 2026-09-14 | Revival steps are in [openai-listing-channels.md](#sec-464) |+| OpenAI Cookbook PR #2874 | Open since 2026-07-21. Checked 2026-10-08: still open and unmerged, review required, 24 comments, no activity since our own comment on 2026-09-14 | Revival steps are in [openai-listing-channels.md](#sec-469) || Dedicated three.ws page on the IBM domain | Promised 2026-06-18, not live | **Do not link it or describe it as public until IBM ships it** || IBM co-promotion on X | Promised 2026-06-18, no recorded delivery | Reopen alongside the Agent Connect conversation |@@ -122640,18 +123120,18 @@ own domain, which is the channel with our best track record.| Artefact | Venue | Owner ||---|---|---|-| [nvidia-forum-browser-digital-human.md](#sec-445) | NVIDIA Developer Forums, NIM > Models | [Posted 2026-09-22](https://forums.developer.nvidia.com/t/a-digital-human-in-a-browser-tab-streaming-audio2face-3d-onto-whatever-rig-the-visitor-brought/383953) |-| [nvidia-forum-gpu-fleet-post.md](#sec-446) | NVIDIA Developer Forums | Owner posts |-| [nvidia-forum-model-retirement-post.md](#sec-447) | NVIDIA Developer Forums, NIM > Models | [Posted 2026-09-21](https://forums.developer.nvidia.com/t/nvidia-nim-model-retirements-what-a-410-gone-does-to-a-fallback-chain-and-how-we-survive-it-now/383950) |-| [ibm-community-governed-agents-post.md](#sec-365) | Our own IBM user group, against a one-per-week allowance | Owner posts |-| [openai-community-3d-studio-post.md](#sec-462), [openai-community-physical-world-post.md](#sec-463) | OpenAI Developer Community | Owner posts |+| [nvidia-forum-browser-digital-human.md](#sec-449) | NVIDIA Developer Forums, NIM > Models | [Posted 2026-09-22](https://forums.developer.nvidia.com/t/a-digital-human-in-a-browser-tab-streaming-audio2face-3d-onto-whatever-rig-the-visitor-brought/383953) |+| [nvidia-forum-gpu-fleet-post.md](#sec-450) | NVIDIA Developer Forums | Owner posts |+| [nvidia-forum-model-retirement-post.md](#sec-451) | NVIDIA Developer Forums, NIM > Models | [Posted 2026-09-21](https://forums.developer.nvidia.com/t/nvidia-nim-model-retirements-what-a-410-gone-does-to-a-fallback-chain-and-how-we-survive-it-now/383950) |+| [ibm-community-governed-agents-post.md](#sec-369) | Our own IBM user group, against a one-per-week allowance | Owner posts |+| [openai-community-3d-studio-post.md](#sec-467), [openai-community-physical-world-post.md](#sec-468) | OpenAI Developer Community | Owner posts |Two more NVIDIA rows with no artefact to write, only an action to take: the AI Podcast guestnomination (one form, self-nomination invited, answers already drafted) and the Inceptionmembership announcement on our own channels, which has never been posted. NVIDIA restoredthe co-branded asset benefit on 2026-09-14, so retrieve and reconcile the current kit beforepublishing. Both are in-[nvidia-visibility-map.md](#sec-454), which also flags that the strongest+[nvidia-visibility-map.md](#sec-458), which also flags that the strongestpiece of social proof the company owns is recorded with a null source link and cannotcurrently be shown to anyone.@@ -122684,7 +123164,7 @@ directories were checked on 2026-09-16:GitHub. The chat plugin this manifest describes is not in LobeHub's plugin index. Thekeep-or-retire decision is a row under *Open, unclaimed*.-Both are now recorded in [listings.md](#sec-403).+Both are now recorded in [listings.md](#sec-407).---@@ -122714,22 +123194,22 @@ It rots the moment a status changes, and a stale pipeline is worse than none becsends people to re-verify solved problems.- When a listing goes live, move its row to **Live and working** and add the descriptive- entry to [listings.md](#sec-403).+ entry to [listings.md](#sec-407).- When a blocker clears, move the row from *blocked on them* to *blocked on us*, or delete it.- Never write a status here you did not read from the source doc or a live check. Each rowlinks its source for exactly that reason.- Do not add a row for a content or publishing venue. Those live in- [publishing-program-2026-09.md](#sec-557).+ [publishing-program-2026-09.md](#sec-564).----<a id="sec-480"></a>+<a id="sec-487"></a>> **Source:** `docs/partners/outreach-plan.md` · [↑ table of contents](#table-of-contents)# Partnership outreach plan-*Written 2026-10-09 to work the [partner prospects list](#sec-484). The prospects page+*Written 2026-10-09 to work the [partner prospects list](#sec-491). The prospects pagesays who; this page says in what order, with what message, and who does each step. Theengineering behind each wave is a set of work orders in the `partners-` campaign([shared context](../prompts/finish/_context/partners-00-CONTEXT.md)), so the build can run@@ -122742,7 +123222,7 @@ already uses, renders, retargets or serves, so the first message is never "we wopartner". It is "your work already powers this, here are the numbers, here is what we can dotogether". Where we depend on someone's open source and have never given back, the first moveis a contribution or a credit, not a request. Every number quoted comes from the-[30-day proof brief](#sec-482), quoted the way it says to.+[30-day proof brief](#sec-489), quoted the way it says to.## The engagement ladder@@ -122767,7 +123247,7 @@ assume the owner can spend about two hours a week on outreach.| Step | Who | Detail ||---|---|---|-| Reply to Tripo with the draft in [tripo.md](#sec-486) | Owner | Copy `[email protected]` if the first contact did not come from there |+| Reply to Tripo with the draft in [tripo.md](#sec-493) | Owner | Copy `[email protected]` if the first contact did not come from there || Build the v3 house lane behind `TRIPO_API_KEY`, BYOK unchanged | Agent, order 084 | Runnable now; nothing in it waits on the deal || First call, using the six questions in the brief | Owner | Start at deal shape A, the 60-day credits pilot || Approve the house key once terms are agreed | Owner, order 936 | A platform-paid key onboards a paid API, so it is the owner's call |@@ -122895,9 +123375,9 @@ is the model.- **Re-verify intake routes and numbers** on the day of the first message and update`last_verified`.- **Log every outcome** (sent, replied, call held, declined, signed) in the row's `status` and- `next_action`, so the [pipeline page](#sec-479) stays the single answer to "where+ `next_action`, so the [pipeline page](#sec-486) stays the single answer to "whereis this".-- A signed partner gets a card on [the partner page](#sec-474) only once the work is+- A signed partner gets a card on [the partner page](#sec-480) only once the work islive, under that page's framing rules.## How we measure it@@ -122922,28 +123402,28 @@ is the model.## Related-- [Partner prospects](#sec-484): the scored list this plan works.-- [Tripo partnership brief](#sec-486): Wave 0 in full.-- [Partnership and listing pipeline](#sec-479): what is already in flight.-- [30-day proof brief](#sec-482): the numbers every message quotes.-- [Partner ecosystem](#sec-474): live partner cards and framing rules.+- [Partner prospects](#sec-491): the scored list this plan works.+- [Tripo partnership brief](#sec-493): Wave 0 in full.+- [Partnership and listing pipeline](#sec-486): what is already in flight.+- [30-day proof brief](#sec-489): the numbers every message quotes.+- [Partner ecosystem](#sec-480): live partner cards and framing rules.----<a id="sec-481"></a>+<a id="sec-488"></a>> **Source:** `docs/partners/owner-day-2026-10-09.md` · [↑ table of contents](#table-of-contents)# Owner action day: 2026-10-09Every partnership, marketing, and distribution action that is waiting on the owner, in the order-to do them. Compiled 2026-10-09 from [opportunities.md](#sec-479), the+to do them. Compiled 2026-10-09 from [opportunities.md](#sec-486), the[store submission tracker](../prompts/store-submissions/_generated/TRACKER.md), the-[publishing program](#sec-557), the per-partner visibility maps, and the+[publishing program](#sec-564), the per-partner visibility maps, and theowner-band orders in `prompts/finish/9xx`. Production env facts were read from `three-ws-api`the same day with `node scripts/read-service-env.mjs`.-Tick items as they land, then move the matching row in [opportunities.md](#sec-479)+Tick items as they land, then move the matching row in [opportunities.md](#sec-486)to "Live and working".---@@ -122954,7 +123434,7 @@ to "Live and working".Answers: [nvidia-gtc-2027-poster.md, "Content Interest Survey"](nvidia-gtc-2027-poster.md#content-interest-survey-closes-2026-10-09-5-pm-pt).- [ ] **DEXTools collab reply to Frederic** in the `Three.ws <> DEXTools` Telegram group (he offereda tweet today and asked for exact placements). Paste section 1 of- [dextools-collab-kit.md](#sec-475). Do not claim `@sperax/mcp-dextools` is on+ [dextools-collab-kit.md](#sec-481). Do not claim `@sperax/mcp-dextools` is onnpm, any visit count, or an endorsement.## 2. Emails@@ -122964,16 +123444,16 @@ to "Live and working".2-3 business days. Do not say Granite runs in production (no `WATSONX_*` on the service).- [ ] **IBM event two.** Pick Oct 22 or Oct 29 (Oct 15 is too close for IBM to list it), then sendthe relationship email in `marketing/growth/events/ibm-event-two.md` lines 150-206 on the June- thread. Decisions in [ibm-next-event.md](#sec-375) lines 245-257.+ thread. Decisions in [ibm-next-event.md](#sec-379) lines 245-257.- [ ] **NVIDIA Inception reply** (Showcase routing + ACE contact) to `[email protected]`:- [nvidia-apps-catalog-request.md](#sec-444) lines 233-261. Send after the+ [nvidia-apps-catalog-request.md](#sec-448) lines 233-261. Send after theportal fix in section 3.- [ ] **IBM co-marketing follow-up** (IBM-domain page and X co-promotion promised 2026-06-18):- [ibm-visibility-map.md](#sec-376) lines 153-173. Re-read first; last edited+ [ibm-visibility-map.md](#sec-380) lines 153-173. Re-read first; last edited2026-09-11.- [ ] **Cerebras:** ask whether the non-YC startup deal still exists.- [ ] **Bucharest education pilot:** reply unsent since 2026-08-06- ([education-pilot-bucharest.md](#sec-258)). Send or close it.+ ([education-pilot-bucharest.md](#sec-261)). Send or close it.## 3. Forms, portals, and directory submissions (no spend)@@ -122999,18 +123479,18 @@ to "Live and working".- [ ] **Inception portal product record** (programs.nvidia.com/phoenix/application): move Riva,Audio2Face and NIM to "Used", remove DeepVariant, set logo and brand color `#0B0D0C`, add a second- record for `<agent-3d>`. Copy: [nvidia-apps-catalog-listing.md](#sec-443)+ record for `<agent-3d>`. Copy: [nvidia-apps-catalog-listing.md](#sec-447)lines 41-259. Then download the co-branded kit from Benefits.- [ ] **NGC Software Partner form + legal agreement:** answers in- [nvidia-ngc-listing.md](#sec-453) lines 184-220; ask whether one replica per GPU+ [nvidia-ngc-listing.md](#sec-457) lines 184-220; ask whether one replica per GPUmeets the multi-GPU rule.- [ ] **NVIDIA AI Podcast self-nomination:** ai-podcast.nvidia.com, answers in- [nvidia-visibility-map.md](#sec-454) lines 79-115.+ [nvidia-visibility-map.md](#sec-458) lines 79-115.**IBM**- [ ] Register for **Partner Growth Day** (virtual, Tue Oct 20), and the Nov 3 and Nov 5 sessions- ([ibm-partner-plus.md](#sec-477) lines 215-241; questions at lines 143-153).+ ([ibm-partner-plus.md](#sec-483) lines 215-241; questions at lines 143-153).- [ ] Request **My Digital Marketing** access and the Build-track marketing kit; verify the PartnerPlus Directory profile.@@ -123019,7 +123499,7 @@ to "Live and working".- [ ] **AWS Marketplace product.** In seller account `155407237916`: create the metering IAM key andSNS/EventBridge secret, set the `AWS_MP_*` vars (none are set; the webhook answers 503), create the"AI agents & tools" product, test while limited, request public. Allow 7-10 business days.- Kit: [aws-marketplace-listing-kit.md](#sec-163) lines 122-298.+ Kit: [aws-marketplace-listing-kit.md](#sec-164) lines 122-298.**MCP and x402 directories**@@ -123038,7 +123518,7 @@ to "Live and working".- [ ] **x402 ecosystem:** PRs to the x402.org ecosystem page, xpaysh/awesome-x402 andMerit-Systems/awesome-x402; register at x402scan (SIWX with the platform wallet, a signature, nota spend); verify the claimed domain on 402index. All in- [x402-distribution.md](#sec-853) lines 110-246.+ [x402-distribution.md](#sec-868) lines 110-246.**Community and media**@@ -123051,12 +123531,12 @@ to "Live and working".hackernoon.com/u/three-ws, then submit the imported drafts for review.- [ ] **PostHog for Startups:** apply from the production org.- [ ] **CoinGecko:** add the qualifying $THREE market; form values in- [coingecko-listing-update-2026-08.md](#sec-197) line 40.+ [coingecko-listing-update-2026-08.md](#sec-198) line 40.- [ ] **@nichxbt appeal #2** (fileable since 2026-09-07), the locked-account form and the data- request, all the same day: [x-account-appeal.md](#sec-806) lines 403, 473, 661.+ request, all the same day: [x-account-appeal.md](#sec-819) lines 403, 473, 661.- [ ] **GitHub org:** create `three-ws` and `three-ws/examples`, then `npm run export:satellites`.- [ ] **Upstream issue** on home-assistant/home-assistant-js-websocket:- [docs/upstream/home-assistant-js-websocket-resubscribe-rejection.md](#sec-776).+ [docs/upstream/home-assistant-js-websocket-resubscribe-rejection.md](#sec-785).**On-chain listing (no funds move, but it writes state: confirm the diff card)**@@ -123067,29 +123547,29 @@ to "Live and working".## 4. Posts**Long-form, self-serve venues** (one per day per venue, suggested order in-[publishing-program-2026-09.md](#sec-557) lines 69-83)--- [ ] NVIDIA forum, NIM > Models: [nvidia-forum-gpu-fleet-post.md](#sec-446)-- [ ] OpenAI Developer Community: [openai-community-physical-world-post.md](#sec-463),- then [openai-community-3d-studio-post.md](#sec-462) (check it was not already posted)-- [ ] AWS Builder Center: [universal retargeting](#sec-161),- [immutable embed releases](#sec-157),- [claims ledger](#sec-156),- [open-weight 3D forge](#sec-160),- [agent commerce spine](#sec-153). Each has an X thread in+[publishing-program-2026-09.md](#sec-564) lines 69-83)++- [ ] NVIDIA forum, NIM > Models: [nvidia-forum-gpu-fleet-post.md](#sec-450)+- [ ] OpenAI Developer Community: [openai-community-physical-world-post.md](#sec-468),+ then [openai-community-3d-studio-post.md](#sec-467) (check it was not already posted)+- [ ] AWS Builder Center: [universal retargeting](#sec-162),+ [immutable embed releases](#sec-158),+ [claims ledger](#sec-157),+ [open-weight 3D forge](#sec-161),+ [agent commerce spine](#sec-154). Each has an X thread in`docs/x-posts/` to send once it is live.-- [ ] Hugging Face blog: [huggingface-agent-feedback-loop.md](#sec-353)-- [ ] three.js forum: [threejs-forum-post.md](#sec-679)-- [ ] Home Assistant Community: [home-assistant-community-post.md](#sec-340)-- [ ] dev.to (then Hashnode, Medium): [devto-mcp-fleet-post.md](#sec-245). Not the+- [ ] Hugging Face blog: [huggingface-agent-feedback-loop.md](#sec-357)+- [ ] three.js forum: [threejs-forum-post.md](#sec-687)+- [ ] Home Assistant Community: [home-assistant-community-post.md](#sec-344)+- [ ] dev.to (then Hashnode, Medium): [devto-mcp-fleet-post.md](#sec-246). Not thesame day as the OpenAI community post.-- [ ] Google Cloud Community: [google-cloud-community-post.md](#sec-331)+- [ ] Google Cloud Community: [google-cloud-community-post.md](#sec-335)- [ ] IBM user group (one per week, thread same day): any-skeleton animation first, thenlong-running MCP tools, then doc freshness (`docs/ibm-community-*-post.md` + `-thread.md`)- [ ] CoinMarketCap Community, three days apart: x402 failure paths, Solana reputation, copytrading, then sniper oracle, radar strategy lab, vanity mints (`docs/coinmarketcap-article-2026-10-*.md`)-**Short-form** ([short-form-venue-kit-2026-09.md](#sec-639); Reddit on+**Short-form** ([short-form-venue-kit-2026-09.md](#sec-647); Reddit onseparate days)- [ ] Show HN (line 15), r/homeassistant (line 103), r/LocalLLaMA (line 127)@@ -123097,7 +123577,7 @@ separate days)**X and Telegram by hand**-- [ ] DEXTools posts from @trythreews: [dextools-collab-kit.md](#sec-475) lines 85-162+- [ ] DEXTools posts from @trythreews: [dextools-collab-kit.md](#sec-481) lines 85-162- [ ] Audio2Face forum announcement: `docs/x-posts/nvidia-forum-audio2face-x-post.md`- [ ] NVIDIA Inception membership announcement (never posted):`marketing/nvidia-inception/social-copy.md`, after reconciling against the co-branded kit@@ -123124,7 +123604,7 @@ separate days)- [ ] **OKX paid end-to-end test:** fund buyer `0x75d0...cf69` with USD₮0 on X Layer (order 913).- [ ] **Economy master wallet runway:** about 0.7 SOL covers 14 days (order 902; settle is 94.5% today).- [ ] **Growth programs** $THREE payouts: `THREE_PRIZE_PAYOUT_KEY` and the three flags- ([growth-programs.md](#sec-335) lines 172-219).+ ([growth-programs.md](#sec-339) lines 172-219).## Not today@@ -123147,7 +123627,7 @@ bot healthy. x402-list submitted 2026-09-30 (awaiting their review).----<a id="sec-482"></a>+<a id="sec-489"></a>> **Source:** `docs/partners/proof-brief-2026-10.md` · [↑ table of contents](#table-of-contents)@@ -123157,7 +123637,7 @@ bot healthy. x402-list submitted 2026-09-30 (awaiting their review).last day is partial. **Regenerate:** `npm run partners:proof -- --from 2026-08-31 --to 2026-09-30`(add `--json` for the raw report, `--mcp-logs` for the Cloud Logging census).-This is the evidence sheet the [distribution and co-marketing plan](#sec-478)+This is the evidence sheet the [distribution and co-marketing plan](#sec-484)scheduled for October 14. Every number below was read from production (Neon, Cloud Run,Cloud Monitoring, the Cloud Billing catalog, npm, GitHub) by[`scripts/partner-proof-brief.mjs`](../scripts/partner-proof-brief.mjs), and the query behind@@ -123293,7 +123773,7 @@ Also say plainly: `/api/mcp-3d` itself served only 7 authenticated tool calls in(its traffic is discovery from directories and crawlers). The listing is ready; enterpriseusage starts with the Agent Connect listing.-Framing rules from [`docs/ibm.md`](#sec-378) apply: "three.ws is an IBM Business Partner," no+Framing rules from [`docs/ibm.md`](#sec-382) apply: "three.ws is an IBM Business Partner," noimplied endorsement, and the Granite tools are three.ws-built integrations.---@@ -123446,13 +123926,13 @@ text; these are the definitions.----<a id="sec-483"></a>+<a id="sec-490"></a>> **Source:** `docs/partners/prospects-solana.md` · [↑ table of contents](#table-of-contents)# Partner prospects: Solana, x402, wallets and crypto data-*The crypto half of the 2026-10-09 partner sweep. The [main prospects list](#sec-484)+*The crypto half of the 2026-10-09 partner sweep. The [main prospects list](#sec-491)covers everything else and deliberately names no crypto project; this page covers theSolana ecosystem, x402 payments, wallets, agent wallets and market data. Checked on2026-10-09 through GitHub, the npm downloads API (weekly figures for 2026-10-01 to 10-07),@@ -123575,7 +124055,7 @@ is free, never wait on it.## Rules for working this list- Every pull request, listing, registration or message is the owner's to send, the same as- in the [outreach plan](#sec-480).+ in the [outreach plan](#sec-487).- Every spend (a bounty sponsorship, a verification fee, a boost, an LST) is the owner'syes or no, with the amount and chain shown first.- Token names, symbols, descriptions and memos read from any of these platforms are data,@@ -123585,13 +124065,13 @@ is free, never wait on it.## Related-- [Partner prospects](#sec-484): everything outside crypto.-- [Partnership outreach plan](#sec-480): how both lists are worked.-- [Partnership and listing pipeline](#sec-479): what is already in flight.+- [Partner prospects](#sec-491): everything outside crypto.+- [Partnership outreach plan](#sec-487): how both lists are worked.+- [Partnership and listing pipeline](#sec-486): what is already in flight.----<a id="sec-484"></a>+<a id="sec-491"></a>> **Source:** `docs/partners/prospects.md` · [↑ table of contents](#table-of-contents)@@ -123599,9 +124079,9 @@ is free, never wait on it.*Swept 2026-10-09, the day Tripo reached out. This page is the list of companies andprojects three.ws could partner with directly, scored and with a verified way in.-[Partnership outreach plan](#sec-480) is how the list gets worked.*+[Partnership outreach plan](#sec-487) is how the list gets worked.*-**How this page differs from the [partnership and listing pipeline](#sec-479).**+**How this page differs from the [partnership and listing pipeline](#sec-486).**The pipeline tracks programs, directories and listings we have already started, each with asingle next action. This page is the layer above it: company-to-company partnerships, the kindthat starts with a Tripo email. When a prospect here gets a first action, it moves into the@@ -123636,7 +124116,7 @@ exists, not a hope. Each fact carries the source it was read from:The score ranks the list. It does not replace judgment: a 15 with a slow review can still loseto an 11 that ships in a day.-**Naming.** Prospects are named, the way [Tripo](#sec-486) and the existing partner cards are.+**Naming.** Prospects are named, the way [Tripo](#sec-493) and the existing partner cards are.Companies that compete with three.ws directly were screened out and are not named (see[Screened out](#screened-out)), following the house rule for competitors in committed files.Crypto and on-chain partners are kept in a separate list.@@ -123650,7 +124130,7 @@ category tables below carry the detail and the source for each claim.| # | Prospect | Score | The move | Why now ||---|---|---|---|---|-| 1 | **Tripo** | 15 | Reply, propose a 60-day partner-credits pilot, ship the v3 house lane | They reached out. Brief and reply draft: [tripo.md](#sec-486) |+| 1 | **Tripo** | 15 | Reply, propose a 60-day partner-credits pilot, ship the v3 house lane | They reached out. Brief and reply draft: [tripo.md](#sec-493) || 2 | **LiveKit** | 14 | Ship the 3D avatar plugin, apply to LiveKit Startups | The open design question on the plugin is answered (see the voice table), and the program is new || 3 | **Shopify** | 14 | Build a "photo to 3D product media" app for the App Store | Product pages already take GLB and USDZ with AR, so the Forge fills a slot that already exists || 4 | **Discord Activities** | 14 | Ship /play or a 3D agent as an Activity, list it in the App Directory | We already run a Discord gateway; discovery is self-serve within 24 hours of verification |@@ -123675,7 +124155,7 @@ These lose value by waiting. Everything else on this page can be worked in wave| Opening | Why it is closing | Our asset | Where it is worked ||---|---|---|---|-| **Tripo's inbound** | An inbound conversation cools in days | [tripo.md](#sec-486): brief, asks, offers, reply draft | Wave 0 of the [outreach plan](#sec-480) |+| **Tripo's inbound** | An inbound conversation cools in days | [tripo.md](#sec-493): brief, asks, offers, reply draft | Wave 0 of the [outreach plan](#sec-487) || **Ready Player Me users** | The service shut down on 2026-01-31 and both its hostnames are dead in DNS today. Two competitors are already publishing "alternative to Ready Player Me" pages for these users | `/import/rpm` exists and the Wolf3D skeleton already animates, but the page is marked `noindex` | Owner-gated order [934](../prompts/finish/934-best3d-07-orphaned-avatar-campaign.md) and order [075](../prompts/finish/075-best3d-09-three-vrm.md) || **Stranded motion-capture users** | Meshcapade (now part of Epic Games) shut its online platforms, including MoCapade. RADiCAL's web portal closed on 2026-07-06 after Autodesk bought its core technology, and user data was not transferred | [`workers/model-video2motion`](../workers/model-video2motion) turns a video into a clip | Order 090 of the [partners campaign](../prompts/finish/_context/partners-00-CONTEXT.md) || **LiveKit Startups** | Launched 2026-09-16: up to USD 23,000 for companies under 50 people and under USD 5M raised | The avatar plugin | Wave 1 |@@ -123705,10 +124185,10 @@ prospects, because the pitch is volume, not a promise.| Prospect | What they are | Scale (source) | Touchpoint today | The deal | Intake route | F·R·A | Score ||---|---|---|---|---|---|---|---|-| **Tripo (VAST)** | Text, image and multiview to 3D, plus rig, retarget, low-poly, splat and segmentation endpoints | Series B/B+ of about USD 446M, 2026-09 *(search-reported)*; TripoSR 7,035 stars | Bring-your-own-key lane in [`api/_providers/tripo.js`](../api/_providers/tripo.js); self-hosted TripoSG and TripoSR workers | Partner credits, then partner pricing; full brief in [tripo.md](#sec-486) | They reached out; `[email protected]` on their pricing page | 5·5·5 | **15** |+| **Tripo (VAST)** | Text, image and multiview to 3D, plus rig, retarget, low-poly, splat and segmentation endpoints | Series B/B+ of about USD 446M, 2026-09 *(search-reported)*; TripoSR 7,035 stars | Bring-your-own-key lane in [`api/_providers/tripo.js`](../api/_providers/tripo.js); self-hosted TripoSG and TripoSR workers | Partner credits, then partner pricing; full brief in [tripo.md](#sec-493) | They reached out; `[email protected]` on their pricing page | 5·5·5 | **15** || **Meshy** | Text and image to 3D, texturing, rigging | Series B of about USD 400M at USD 1.5B, 2026-07 (PR Newswire); 12M+ users *(vendor claim)* | Bring-your-own-key lane, [`api/_providers/meshy.js`](../api/_providers/meshy.js) | Platform pricing so Meshy can be a house lane; co-marketing | Partner form at meshy.ai/partners (aimed at enterprise resale, starting in Europe) | 5·5·4 | **14** || **fal.ai** | Inference host that sells Tripo, Hunyuan3D, TRELLIS.2, Rodin, Meshy and SAM 3D behind one key | `@fal-ai/client` 1.64M/wk (npm) | None for 3D | One account would turn several bring-your-own-key lanes into house lanes | Not verified | 5·5·3 | **13** |-| **Hugging Face** | Model hub, ZeroGPU Spaces, Inference Providers | `@huggingface/inference` 369K/wk (npm) | The free Spaces failover chain ([`api/_providers/huggingface.js`](../api/_providers/huggingface.js)) | ZeroGPU quota or a community GPU grant, which raises free-tier reliability directly | Already in the [pipeline](#sec-479) as the Space feature and GPU grant row | 5·5·3 | **13** |+| **Hugging Face** | Model hub, ZeroGPU Spaces, Inference Providers | `@huggingface/inference` 369K/wk (npm) | The free Spaces failover chain ([`api/_providers/huggingface.js`](../api/_providers/huggingface.js)) | ZeroGPU quota or a community GPU grant, which raises free-tier reliability directly | Already in the [pipeline](#sec-486) as the Space feature and GPU grant row | 5·5·3 | **13** || **Tencent Hunyuan3D** | Open-weight 3D generation (2.x); newer versions API-only | Hunyuan3D-2 15,041 stars | Self-hosted worker and Spaces rung | API access to newer versions; a production showcase | Not verified (Tencent Cloud) | 5·5·2 | **12** || **World Labs (Spark)** | Marble world generation, World API, and the Spark splat renderer | Spark 3,711 stars and about 215K/wk (npm); an AMD deal is pending | Spark renders [`src/splat-stage.js`](../src/splat-stage.js) | Spark production showcase and upstream fixes; World API credits | World API and the Spark GitHub repo | 4·5·3 | **12** || **Microsoft TRELLIS** | Open-weight structured 3D latents (TRELLIS, TRELLIS.2), MIT | 13,813 and 11,610 stars | Our default engine; TRELLIS.2 lane built in order 067 | A production case study and upstream fixes | GitHub issues and pull requests | 5·4·2 | **11** |@@ -123719,7 +124199,7 @@ prospects, because the pitch is volume, not a promise.| **Polycam** | Capture and reconstruction with public APIs | Series A USD 18M, 2024 (press) | None | Capture-to-avatar and capture-to-Forge | `sales.poly.cam/contact` | 3·4·3 | **10** || **KIRI Engine** | Photogrammetry, Gaussian splats, splat to mesh API | Not verified | None | Splat-to-mesh lane on the splat stage | `[email protected]` (their API page) | 3·3·4 | **10** || **Zoo.dev** | Text-to-CAD API with an agent and MCP server | modeling-app 1,312 stars | None | A CAD lane for makers who print | `[email protected]` (API pricing page) | 3·3·4 | **10** |-| **Niantic Spatial** | Scaniverse, visual positioning, the `.spz` splat format | USD 250M at spin-out (press) | `.spz` support ([splat docs](#sec-661)) | A format and positioning integration | Not verified | 3·4·2 | **9** |+| **Niantic Spatial** | Scaniverse, visual positioning, the `.spz` splat format | USD 250M at spin-out (press) | `.spz` support ([splat docs](#sec-669)) | A format and positioning integration | Not verified | 3·4·2 | **9** || **Kaedim** | AI plus artist 3D production for studios | Series A USD 15M, 2024 (PocketGamer) | None | A premium "artist-finished" tier routed to them | `kaedim3d.com/contactUs` | 3·3·3 | **9** |GPU and compute credit programs (Modal up to USD 50K, RunPod up to USD 25K, Baseten USD 25K,@@ -123768,15 +124248,15 @@ framework or streaming tool that has a face slot, and our full 3D body to put in| Prospect | What they are | Scale (source) | Touchpoint today | The deal | Intake route | F·R·A | Score ||---|---|---|---|---|---|---|---|| **LiveKit Agents** | Open-source WebRTC and the Agents voice and video AI framework | livekit/agents 14,665 stars; `livekit-client` 4.36M/wk; Series C USD 100M at USD 1B, 2026-01 *(search-reported)* | [`src/runtime/livekit-voice.js`](../src/runtime/livekit-voice.js), [`api/agents/_id/livekit-token.js`](../api/agents/_id/livekit-token.js) | An avatar plugin in their framework, listed on their avatar docs page; Startups credits. The pipeline row asked whether that needs a server render lane. It does not: livekit/agents merged a plugin (PR #5821, 2026-07-20) that renders on the visitor's device and sends only motion data over LiveKit, which is how three.ws already works | Plugin: pull request per their CONTRIBUTING guide (CLA bot, ruff, pdoc). Credits: livekit.com/startups | 5·5·4 | **14** |-| **Discord Activities** | Web apps that run inside Discord | "200 million" monthly users, 2024 *(vendor claim)*; `@discord/embedded-app-sdk` 355K/wk | Agent chat gateway ([`api/gateway/discord.js`](../api/gateway/discord.js)); no Embedded App SDK yet | /play or a 3D agent as a group Activity, with in-app purchases | Verify app and team, meet Discovery criteria, listed within 24 hours. Purchases: 15% on the first USD 1M, then 30% | 5·5·4 | **14** |+| **Discord Activities** | Web apps that run inside Discord | "200 million" monthly users, 2024 *(vendor claim)*; `@discord/embedded-app-sdk` 355K/wk | Built, order 088: a shared Forge room Activity ([`src/discord-activity/app.js`](../src/discord-activity/app.js), docs: [`/docs/discord-activity`](#sec-249)); free, no in-app purchases | Register the Developer Portal app, set the env vars, run the migration, verify in a real Discord client, submit for Discovery; exact steps in [`marketing/growth/submissions/discord-activity.md`](../marketing/growth/submissions/discord-activity.md) | Verify app and team, meet Discovery criteria, listed within 24 hours | 5·5·4 | **14** || **Pipecat (Daily)** | Open-source Python voice agent framework | 16,309 stars; `@daily-co/daily-js` 942K/wk | None | A 3D avatar output service, listed as a community integration | COMMUNITY_INTEGRATIONS.md in the pipecat repo: own repo, docs pull request, 30 to 60 second demo video, Discord post. `[email protected]` printed there | 4·4·5 | **13** |-| **ElevenLabs** | Voice AI: agents, TTS API, creative tools | Series D USD 500M at USD 11B, 2026-02 *(vendor blog)*; `@elevenlabs/client` 1.09M/wk | [`api/tts/eleven.js`](../api/tts/eleven.js), bring-your-own-key lane | The startup grant (already in the [pipeline](#sec-479)); then the Commercial Partner Program, a route the pipeline did not have | Grant: elevenlabs.io/grants-application. Partner: elevenlabs.io/partner-application | 4·5·4 | **13** |+| **ElevenLabs** | Voice AI: agents, TTS API, creative tools | Series D USD 500M at USD 11B, 2026-02 *(vendor blog)*; `@elevenlabs/client` 1.09M/wk | [`api/tts/eleven.js`](../api/tts/eleven.js), bring-your-own-key lane | The startup grant (already in the [pipeline](#sec-486)); then the Commercial Partner Program, a route the pipeline did not have | Grant: elevenlabs.io/grants-application. Partner: elevenlabs.io/partner-application | 4·5·4 | **13** || **Home Assistant** | Open-source home automation | 696,482 opt-in active installs, with `mcp_server` on 27,330 (analytics.home-assistant.io, 2026-10-09) | [`home-assistant-integration/`](../home-assistant-integration), [`services/home-satellite`](../services/home-satellite), [`packages/home-mcp`](../packages/home-mcp) | A listing in the default HACS store | Pull request to hacs/default: a dedicated public repo, HACS Action and Hassfest passing, a release and a brand icon. Reviews are slow | 5·4·3 | **12** || **Twitch Extensions** | Panel and overlay web apps inside Twitch | "Millions" daily *(vendor claim)* | None | An AI co-host or 3D agent overlay for streamers, with Bits revenue | Hosted Test, then Submit for Review. All code ships in the zip (no remote scripts), every fetch domain declared, 1 MB mobile limit | 4·5·3 | **12** || **StreamElements** | Overlays, alerts and tipping for streamers, now owned by Razer | 2.6M creators daily *(vendor claim)* | None | A paste-in custom widget; no gatekeeper | Overlay Editor custom widget, docs.streamelements.com | 3·4·5 | **12** |-| **OBS Studio** | Open-source streaming app | 77,196 stars | The agent overlay URL ([chart companion](#sec-183)) | A documented Browser Source URL per agent; no listing needed | None needed. Their forum forbids resources written mostly with AI coding tools and any use of OBS branding | 3·4·4 | **11** |+| **OBS Studio** | Open-source streaming app | 77,196 stars | The agent overlay URL ([chart companion](#sec-184)) | A documented Browser Source URL per agent; no listing needed | None needed. Their forum forbids resources written mostly with AI coding tools and any use of OBS branding | 3·4·4 | **11** || **Telegram Mini Apps** | Web apps inside Telegram | "Over 1B" monthly users *(vendor claim)* | [`api/gateway/telegram.js`](../api/gateway/telegram.js) | A crypto-free agent companion Mini App | BotFather; featuring is discretionary. Telegram's bot terms (section 7) restrict wallets in Mini Apps to a chain we do not use, so no wallet or token features | 3·5·3 | **11** |-| **Deepgram** | Speech-to-text, TTS and voice agent APIs | `@deepgram/sdk` 913K/wk | None (our ASR runs on NVIDIA Riva) | Credits plus a Technology partner listing, a track the pipeline did not have | deepgram.com/partners (Technology track form); credits row already in the [pipeline](#sec-479) | 3·4·4 | **11** |+| **Deepgram** | Speech-to-text, TTS and voice agent APIs | `@deepgram/sdk` 913K/wk | None (our ASR runs on NVIDIA Riva) | Credits plus a Technology partner listing, a track the pipeline did not have | deepgram.com/partners (Technology track form); credits row already in the [pipeline](#sec-486) | 3·4·4 | **11** || **Cartesia** | Real-time TTS and STT | `@cartesia/cartesia-js` 79,696/wk | None | 12 months of the Scale plan, in exchange for a logo and case study | cartesia.ai/startups/apply. Adding it onboards a new paid API, so it is owner-gated | 3·3·4 | **10** || **TEN Framework** | Voice agent framework with avatar extensions | 11,155 stars | None | A 3D avatar extension | Pull request. Its license is "Apache 2.0 with additional restrictions": read it before contributing | 3·3·3 | **9** || **Hyperfy** | Open-source multiplayer web worlds, GPL-3.0 | 305 stars; last release 2025-12 | `world.three.ws` runs a pinned Hyperfy server | Upstream our hardening patches | GitHub pull requests (five outside ones are unmerged) | 4·1·2 | **7** |@@ -123800,10 +124280,10 @@ on and have never contributed to, so the first move is a contribution, not a req| **Blender Development Fund** | Funds Blender core development | USD 326,692 a month from 7,652 individuals and 46 corporate members (fund.blender.org) | [`integrations/blender`](../integrations/blender) add-on | Bronze corporate membership, EUR 6,000 a year, logo on the fund site | Self-checkout at fund.blender.org/corporate-memberships | 4·4·5 | **13** || **Godot** | Open-source game engine, Asset Library and a beta Asset Store | 118,143 stars; 1,829 fund members | Forge "Game" destination | A Godot addon importing three.ws GLBs and the CC0 library | godotengine.org/asset-library (manual review, a few days); store.godotengine.org (beta) | 4·5·4 | **13** || **glTF-Transform** | glTF processing SDK by Don McCurdy | 1,982 stars; `@gltf-transform/core` 854K/wk | Direct dependency across the Forge ([`api/forge.js`](../api/forge.js)) | The USD 500 a month company sponsor tier | github.com/sponsors/donmccurdy | 5·2·5 | **12** |-| **Google model-viewer** | `<model-viewer>` web component for 3D and AR | 8,267 stars; 547K/wk (npm) | Our whole AR path ([AR docs](#sec-129)) | Bug reports and pull requests from production Quick Look and Scene Viewer use; a show-and-tell post | github.com/google/model-viewer/discussions | 5·3·4 | **12** |+| **Google model-viewer** | `<model-viewer>` web component for 3D and AR | 8,267 stars; 547K/wk (npm) | Our whole AR path ([AR docs](#sec-130)) | Bug reports and pull requests from production Quick Look and Scene Viewer use; a show-and-tell post | github.com/google/model-viewer/discussions | 5·3·4 | **12** || **Babylon.js** | Web 3D engine | 26,147 stars; `@babylonjs/core` 350K/wk | Our GLBs load in it | A sample loading three.ws avatars and CC0 GLBs; a forum demo post | forum.babylonjs.com "Demos and projects" | 3·4·5 | **12** |-| **Khronos Group** | Standards body for glTF and 3D Commerce | glTF repo 7,850 stars | Adopter Program and Project Explorer rows are already in the [pipeline](#sec-479) | New: 3D Commerce viewer certification for the `<agent-3d>` viewer, and Associate membership (USD 220 per employee, USD 4,000 minimum, firms up to 100 staff) | khronos.org/members/join; `[email protected]` | 4·3·4 | **11** |-| **PlayCanvas and SuperSplat** | Open-source engine and the SuperSplat splat platform | engine 16,998 stars; SuperSplat 10,314 | [/splat](#sec-661) | Publish from /splat to superspl.at through their Publishing API, which launched 2026-08-17 with three partners; a Developer Spotlight post | `[email protected]`; Discord | 4·3·3 | **10** |+| **Khronos Group** | Standards body for glTF and 3D Commerce | glTF repo 7,850 stars | Adopter Program and Project Explorer rows are already in the [pipeline](#sec-486) | New: 3D Commerce viewer certification for the `<agent-3d>` viewer, and Associate membership (USD 220 per employee, USD 4,000 minimum, firms up to 100 staff) | khronos.org/members/join; `[email protected]` | 4·3·4 | **11** |+| **PlayCanvas and SuperSplat** | Open-source engine and the SuperSplat splat platform | engine 16,998 stars; SuperSplat 10,314 | [/splat](#sec-669) | Publish from /splat to superspl.at through their Publishing API, which launched 2026-08-17 with three partners; a Developer Spotlight post | `[email protected]`; Discord | 4·3·3 | **10** || **meshoptimizer** | Mesh optimization and the meshopt compression we serve by default | 8,527 stars; 12.9M/wk (npm) | Dependency, vendored decoder, pinned `gltfpack` in workers | A visible credit, then upstream bug reports | GitHub issues and Discussions | 4·2·3 | **9** || **Needle Engine** | Web 3D from Unity, Blender or code | 7,718/wk (npm) | Research docs only | A joint sample; commercial use needs their Pro plan | needle.tools: book a call, forum, Discord | 3·2·3 | **8** |@@ -123855,7 +124335,7 @@ because its product pages already render 3D.| Prospect | What they are | Scale (source) | Touchpoint today | The deal | Intake route | F·R·A | Score ||---|---|---|---|---|---|---|---|-| **Shopify** | Commerce platform and App Store | 100,000+ partners, USD 1.3B paid to partners in 2025 *(vendor claim)* | [Share and embed](#sec-636) lists Shopify as an iframe target; no app | An app that generates a product's GLB and USDZ from its photo and uploads them as product media (native, up to 500 MB, with AR on iOS and Android) | partners.shopify.com/signup; App Store review needs a screencast and test credentials, and billing must run through Shopify | 5·5·4 | **14** |+| **Shopify** | Commerce platform and App Store | 100,000+ partners, USD 1.3B paid to partners in 2025 *(vendor claim)* | [Share and embed](#sec-643) lists Shopify as an iframe target; no app | An app that generates a product's GLB and USDZ from its photo and uploads them as product media (native, up to 500 MB, with AR on iOS and Android) | partners.shopify.com/signup; App Store review needs a screencast and test credentials, and billing must run through Shopify | 5·5·4 | **14** || **WordPress.org** | CMS plugin directory | The top 3D viewer plugin has 9,000+ active installs | oEmbed endpoints ([`api/widgets/oembed.js`](../api/widgets/oembed.js)) | A block and shortcode for `<agent-3d>` and Forge models in an uncrowded niche | wordpress.org/plugins/developers/add (manual review, 1 to 10 days) | 4·4·5 | **13** || **Wix** | Site builder and App Market | 300M+ users *(vendor claim)* | Our embed editor mentions Wix | A 3D and agent embed app | Submit from the Wix app dashboard; review is automated (doc updated 2026-07-28) | 3·5·5 | **13** || **Webflow** | Visual site builder with an Apps marketplace | 3.5M users *(search-reported)* | Iframe embed | A Designer Extension that places `<agent-3d>` or a GLB viewer (Webflow has no native GLB element) | developers.webflow.com/submit (10 to 15 business days) | 4·4·4 | **12** |@@ -123908,7 +124388,7 @@ nothing more than a pull request or a form.Already covered elsewhere: Hugging Face is in the [generation table](#3d-generation-engines-and-inference-hosts),Figma's plugin and Slack sit with the design tools, and OpenAI and Alibaba are live partners on-the [partner cards](#sec-474).+the [partner cards](#sec-480).Lower priority: Replit (curated directory with no submission route; an "Add to Replit" badge workstoday), Lovable (its partner program is for service firms), Slack (an MCP-only app is "unsuitable"@@ -123950,24 +124430,24 @@ Recorded so nobody re-researches them.message, re-read the intake page and update the row with the date.- **Move, do not copy.** When a prospect gets a first action, add a row to[`marketing/growth/opportunities.csv`](../marketing/growth/opportunities.csv) and a line in- the [pipeline](#sec-479), then link to it from here.+ the [pipeline](#sec-486), then link to it from here.- **A closed door goes to Screened out**, with the reason and the date, so the next sweep skips it.- **Never invent a contact.** An address goes on this page only if it was printed on thecompany's own page.## Related-- [Tripo partnership brief](#sec-486): the first prospect, worked in full.-- [Partnership outreach plan](#sec-480): waves, cadence, messages and the work orders.-- [Partnership and listing pipeline](#sec-479): what is in flight and on whom.-- [Partner ecosystem](#sec-474): the eight live partner cards and the framing rules.-- [30-day proof brief](#sec-482): the numbers every pitch quotes.-- [3D landscape, October 2026](#sec-600): the open-source and+- [Tripo partnership brief](#sec-493): the first prospect, worked in full.+- [Partnership outreach plan](#sec-487): waves, cadence, messages and the work orders.+- [Partnership and listing pipeline](#sec-486): what is in flight and on whom.+- [Partner ecosystem](#sec-480): the eight live partner cards and the framing rules.+- [30-day proof brief](#sec-489): the numbers every pitch quotes.+- [3D landscape, October 2026](#sec-607): the open-source andcommercial 3D sweep behind the best3d engineering campaign.----<a id="sec-485"></a>+<a id="sec-492"></a>> **Source:** `docs/partners/sperax-proposal.md` · [↑ table of contents](#table-of-contents)@@ -124015,7 +124495,7 @@ Both sides already ship for a living — this proposal only asks each of us to d----<a id="sec-486"></a>+<a id="sec-493"></a>> **Source:** `docs/partners/tripo.md` · [↑ table of contents](#table-of-contents)@@ -124071,7 +124551,7 @@ Verified in this repository and in production on 2026-10-09.|---|---|---|| Tripo v3.1 API lane, bring-your-own-key or house key | [`api/_providers/tripo.js`](../api/_providers/tripo.js), tier entry in [`api/_lib/forge-tiers.js`](../api/_lib/forge-tiers.js) | Text and image to 3D on model `v3.1-20260211`, on the **v3** endpoint `openapi.tripo3d.com/v3`. Runs on a pasted user key, or on `TRIPO_API_KEY` when the platform sets one (a High-tier default and an explicit "Tripo" engine choice, billed to $THREE credits); the BYOK key link in the Forge points at `platform.tripo3d.ai/api-keys` || Signed webhook receiver | [`api/forge/webhook/tripo.js`](../api/forge/webhook/tripo.js) | Verifies `Tripo-Webhook-Signature`, claims `Tripo-Webhook-Delivery` for idempotency, and completes a job the same way polling does; registering the endpoint URL in Tripo's dashboard and setting `TRIPO_WEBHOOK_SECRET` are the owner's last step |-| TripoSG, self-hosted | [`workers/model-triposg`](../workers/model-triposg) | The sketch-to-3D lane, and the last automatic failover rung for photo jobs ([forge failover](#sec-313)) |+| TripoSG, self-hosted | [`workers/model-triposg`](../workers/model-triposg) | The sketch-to-3D lane, and the last automatic failover rung for photo jobs ([forge failover](#sec-316)) || TripoSR, self-hosted and hosted | [`workers/model-triposr`](../workers/model-triposr) (the fast lane in the avatar pipeline controller), plus a rung in the free Hugging Face Spaces chain ([`api/_providers/huggingface.js`](../api/_providers/huggingface.js)) | The fast path, at about 3 seconds of GPU time per mesh, and part of the free photo-to-3D failover chain |### The number that shapes the pitch@@ -124091,7 +124571,7 @@ rigging requests from real makers in September (the audited figure in the proofexcludes catalog seeders and benchmarks), and the setting is currently "go and sign up somewhere else first".For the wider evidence (completion rate, makers, MCP traffic), use the-[30-day proof brief](#sec-482) and quote its numbers the way it says to.+[30-day proof brief](#sec-489) and quote its numbers the way it says to.---@@ -124217,17 +124697,17 @@ Send from the owner's account to the person who reached out, copying## Related-- [Partner prospects](#sec-484): the full list of companies worth approaching, of+- [Partner prospects](#sec-491): the full list of companies worth approaching, ofwhich Tripo is the first.-- [Partnership outreach plan](#sec-480): how the list is worked, wave by wave.-- [Forge](#sec-313) and [How the Forge works](#sec-350): the engine grid Tripo+- [Partnership outreach plan](#sec-487): how the list is worked, wave by wave.+- [Forge](#sec-316) and [How the Forge works](#sec-354): the engine grid Tripoplugs into.-- [3D landscape, October 2026](#sec-600): the open-source sweep+- [3D landscape, October 2026](#sec-607): the open-source sweepthat put UniRig and the rigging stack on the roadmap.----<a id="sec-487"></a>+<a id="sec-494"></a>> **Source:** `docs/pay-skills-listing.md` · [↑ table of contents](#table-of-contents)@@ -124335,7 +124815,7 @@ are supported.----<a id="sec-488"></a>+<a id="sec-495"></a>> **Source:** `docs/payment-sessions.md` · [↑ table of contents](#table-of-contents)@@ -124504,7 +124984,7 @@ page renders its asset picker and rate list from this array. `accepts`,`three_mint`, `three_symbol` and `three_decimals` are kept for older clients.`holder` is the $THREE tier every debit on this account is already priced at:-the same shape [`GET /api/pricing`](#sec-124) returns. `discount_bps`+the same shape [`GET /api/pricing`](#sec-125) returns. `discount_bps`is the discount applied to each spend (1000 = 10% off), `usd_held` is the USDvalue of the $THREE held by the linked wallet, and `next_tier` / `usd_to_next`say how much more $THREE reaches the next rung (`next_tier` is `null` at the@@ -124881,13 +125361,13 @@ curl -s $BASE/api/credits -H "$AUTH" | jq .balance_usd## Related-- [x402 Protocol](#sec-862): the challenge / verify / settle mechanics behind every paid call.-- [x402 Buyer Client](#sec-851): paying x402 endpoints from your own wallet instead of a session.-- [x402 Developer Tools](#sec-852): free echo / debug / receipt-verification tools for debugging a paid call.+- [x402 Protocol](#sec-877): the challenge / verify / settle mechanics behind every paid call.+- [x402 Buyer Client](#sec-866): paying x402 endpoints from your own wallet instead of a session.+- [x402 Developer Tools](#sec-867): free echo / debug / receipt-verification tools for debugging a paid call.----<a id="sec-489"></a>+<a id="sec-496"></a>> **Source:** `docs/permissions.md` · [↑ table of contents](#table-of-contents)@@ -125283,17 +125763,17 @@ Set `SMOKE_SKIP_REVOKE=1` to skip the on-chain revocation step if the test walle## See also-- [Architecture Overview](#sec-130)+- [Architecture Overview](#sec-131)- [Agent System](#sec-068)-- [ERC-8004 Blockchain Identity](#sec-263)-- [Skill System](#sec-649)+- [ERC-8004 Blockchain Identity](#sec-266)+- [Skill System](#sec-657)- [EIP-7710](https://eips.ethereum.org/EIPS/eip-7710) — delegation envelope format- [EIP-7715](https://eips.ethereum.org/EIPS/eip-7715) — `wallet_grantPermissions` JSON-RPC method- [MetaMask Delegation Toolkit](https://docs.metamask.io/delegation-toolkit/)----<a id="sec-490"></a>+<a id="sec-497"></a>> **Source:** `docs/perps.md` · [↑ table of contents](#table-of-contents)@@ -125309,7 +125789,7 @@ There are three ways in, and all three run the same service (`api/_lib/perps/ser| REST | `/api/v1/agents/:id/perps/*` | Your own code, with a session or an API key || MCP | `perps_*` tools on `/api/mcp-agent` | Claude, or any MCP client you connect |-Related reading: [agent wallets](#sec-077) covers the custody and spend-policy model the deposits run under, [custody you can verify](#sec-232) covers the freeze and kill switches, and the [risk acknowledgment](#sec-618) explains the agreements live mode requires.+Related reading: [agent wallets](#sec-077) covers the custody and spend-policy model the deposits run under, [custody you can verify](#sec-233) covers the freeze and kill switches, and the [risk acknowledgment](#sec-625) explains the agreements live mode requires.---@@ -125523,7 +126003,7 @@ To exercise the whole flow end to end, use paper mode on a test agent: deposit,----<a id="sec-491"></a>+<a id="sec-498"></a>> **Source:** `docs/persona-hub.md` · [↑ table of contents](#table-of-contents)@@ -125920,7 +126400,7 @@ JWT claims:----<a id="sec-492"></a>+<a id="sec-499"></a>> **Source:** `docs/pill-mascot.md` · [↑ table of contents](#table-of-contents)@@ -125934,7 +126414,7 @@ The interesting part is not the result, it is why the normal path did not work a**On this page:** [Why auto-rigging failed](#why-the-normal-path-failed) · [The pipeline](#the-pipeline) · [Running it](#running-it) · [What ships](#what-ships) · [Reusing it](#reusing-it-on-your-own-character)-Related: [the avatar pipeline](#sec-148) covers the normal humanoid path (generate, auto-rig, skin, animate). [Rig Doctor](#sec-617) tells you whether a finished `.glb` will actually animate here. [The 3D asset pipeline](#sec-002) covers FBX and GLB conversion upstream of all of it.+Related: [the avatar pipeline](#sec-149) covers the normal humanoid path (generate, auto-rig, skin, animate). [Rig Doctor](#sec-624) tells you whether a finished `.glb` will actually animate here. [The 3D asset pipeline](#sec-002) covers FBX and GLB conversion upstream of all of it.---@@ -126063,11 +126543,11 @@ Finger chains are part of that. Thirty of the 53 tracks in every baked clip addr- **A sealed surface.** Small holes are closed automatically before the flood fill; a hole you could see through is refused rather than guessed at.- **A visible face.** Forward is read from dark pixels on the head. A character with no painted face falls back to +Z.-If your character is genuinely humanoid, do not use this. Use the [standard auto-rigger](#sec-148), which is a one-call API and better at humanoids than this script will ever be.+If your character is genuinely humanoid, do not use this. Use the [standard auto-rigger](#sec-149), which is a one-call API and better at humanoids than this script will ever be.----<a id="sec-493"></a>+<a id="sec-500"></a>> **Source:** `docs/plan-checkout.md` · [↑ table of contents](#table-of-contents)@@ -126083,7 +126563,7 @@ three.ws has a self-serve paid tier. Upgrading to **Pro** (or Team / Enterprise)Where to use it: the Pro card on [three.ws/pricing](https://three.ws/pricing) opens the checkout when you're signed in. Confirmed payments set `users.plan`, light up the Pro badge everywhere ([api/_lib/account-tier.js](../api/_lib/account-tier.js)), and grant 30 days per payment.-This is separate from (and complementary to) [hold-to-access](#sec-339), which derives holder tiers from $THREE you *hold*; the plan checkout is $THREE you *spend*.+This is separate from (and complementary to) [hold-to-access](#sec-343), which derives holder tiers from $THREE you *hold*; the plan checkout is $THREE you *spend*.---@@ -126197,7 +126677,7 @@ Plan prices live in [data/plans.json](../data/plans.json), the single source of----<a id="sec-494"></a>+<a id="sec-501"></a>> **Source:** `docs/play-boot-performance.md` · [↑ table of contents](#table-of-contents)@@ -126207,7 +126687,7 @@ Plan prices live in [data/plans.json](../data/plans.json), the single source ofThat work is unavoidable. What *is* avoidable is paying for it at the wrong moment. This document records the boot-cost invariants that keep the first ten seconds fast, so a future change does not quietly undo one of them. Each section names the regression it prevents, because each of them actually shipped once and was measured on the live site.-Related docs: [how /play stays safe, honest, and light](#sec-496), [architecture](#sec-130).+Related docs: [how /play stays safe, honest, and light](#sec-503), [architecture](#sec-131).## How to measure before you claim anything@@ -126300,7 +126780,7 @@ Before shipping anything that touches `/play` boot:----<a id="sec-495"></a>+<a id="sec-502"></a>> **Source:** `docs/play-forge-in-world.md` · [↑ table of contents](#table-of-contents)@@ -126402,12 +126882,12 @@ layer, ownership checks, and the per-player object cap all apply without modific## Related- [3D asset pipeline](#sec-002): what the forge lanes are and how they differ-- [In-game economy](#sec-380): the rest of what you can do inside a `/play` world+- [In-game economy](#sec-384): the rest of what you can do inside a `/play` world- [/forge](https://three.ws/forge): the full studio, with paid tiers, rigging, and game-ready export----<a id="sec-496"></a>+<a id="sec-503"></a>> **Source:** `docs/play-hardening.md` · [↑ table of contents](#table-of-contents)@@ -126423,7 +126903,7 @@ It is also the surface with the least trusted input. Its entry URL is a link strEvery part of that URL, every display name a peer picks, and every field of the pump.fun coin metadata is text an attacker chose. This document records the invariants that keep the world safe and honest, so that a future change does not quietly undo one of them. Each section names the failure it prevents, because each of these actually shipped once.-Related docs: [in-game economy](#sec-380), [architecture](#sec-130), [security](#sec-627).+Related docs: [in-game economy](#sec-384), [architecture](#sec-131), [security](#sec-634).---@@ -126686,7 +127166,7 @@ The mobile harness is the one that catches memory regressions. It reports total----<a id="sec-497"></a>+<a id="sec-504"></a>> **Source:** `docs/play-live-events.md` · [↑ table of contents](#table-of-contents)@@ -126757,7 +127237,7 @@ from the shape below:| `startsAt` / `endsAt` | ISO-8601 UTC. A missing or inverted `endsAt` defaults to six hours after the start. || `agenda[].atMin` | Minutes after `startsAt`. Order does not matter; segments are sorted. Invalid or untitled entries are dropped rather than breaking the event. || `agenda[].icon` | One emoji. Used on the segment row and its moment banner. |-| `souvenir.cosmeticId` | Optional. A free commemorative wearable granted once to everyone who joins the world named by `link` while the event is live, kept forever, never granted again after `endsAt`. Must be a `tier: 'event'` cosmetic; anything else grants nothing. See [Event souvenirs](#sec-293). |+| `souvenir.cosmeticId` | Optional. A free commemorative wearable granted once to everyone who joins the world named by `link` while the event is live, kept forever, never granted again after `endsAt`. Must be a `tier: 'event'` cosmetic; anything else grants nothing. See [Event souvenirs](#sec-296). |`id`, `agenda`, and `tagline` are optional: an event with none of them still runsits countdown, its go-live moment, and its fireworks.@@ -126856,7 +127336,7 @@ Point it at another origin with `--base https://three.ws`.----<a id="sec-498"></a>+<a id="sec-505"></a>> **Source:** `docs/play-vehicles.md` · [↑ table of contents](#table-of-contents)@@ -126963,12 +127443,12 @@ and the metal-roughness map at 1024px, and writes## Related- [`/play` NPCs and world life](../src/game/npc/ambient-life.js) drives the ambient lane.-- [The in-game economy](#sec-380) covers what you earn on those delivery runs.-- [`/play` safety and lifecycle invariants](#sec-496).+- [The in-game economy](#sec-384) covers what you earn on those delivery runs.+- [`/play` safety and lifecycle invariants](#sec-503).----<a id="sec-499"></a>+<a id="sec-506"></a>> **Source:** `docs/pocket.md` · [↑ table of contents](#table-of-contents)@@ -127007,7 +127487,7 @@ the point of a handheld.- **PLAY** is the agent walking around a small world. It is the default.- **STATS** reads the agent record live: skills, how many of them are paid- (priced through [x402](#sec-862)), conversations, whether it has a rigged body,+ (priced through [x402](#sec-877)), conversations, whether it has a rigged body,its on-chain identity if it has one, and the day it was created.- **SELECT** is a game menu of the public agent index. Steer it with the D-pad,press A to slot one in.@@ -127079,13 +127559,13 @@ Source: [`pages/pocket.html`](../pages/pocket.html),----<a id="sec-500"></a>+<a id="sec-507"></a>> **Source:** `docs/pons-launch.md` · [↑ table of contents](#table-of-contents)# Launch a coin on Robinhood Chain (Pons)-A three.ws agent can launch its own coin on [Robinhood Chain](#sec-620)+A three.ws agent can launch its own coin on [Robinhood Chain](#sec-627)through [Pons](https://ponsfamily.com), the chain's busiest launchpad. The agent's own walletsigns the launch, so the coin's creator is the agent. Creator fees go to the agent, and so doesthe opening buy.@@ -127253,7 +127733,7 @@ A launch spends real ETH, so it runs through every rail a custodial spend on thr- The owner must have signed the real-funds agreements.- The launch fee and opening buy are priced in USD and checked against the agent's per-transactionand daily ceilings for Robinhood Chain. These are metered separately from Solana and Base (see- [custody](#sec-232)).+ [custody](#sec-233)).- The spend is written to the custody ledger as pending before the transaction is sent, so twolaunches at once cannot both slip under the daily ceiling.- The key decrypt is audited.@@ -127286,7 +127766,7 @@ Every Pons launch, from three.ws or anywhere else, also appears in the Recent La----<a id="sec-501"></a>+<a id="sec-508"></a>> **Source:** `docs/popular-3d-github-repos.md` · [↑ table of contents](#table-of-contents)@@ -127304,7 +127784,7 @@ A sweep of 22 3D-related GitHub topics and keyword queries (`3d`, `threejs`, `we> This file ranks the ecosystem by stars. For what three.ws should actually> adopt out of it, with licenses verified and the file each candidate lands-> in, see [oss-adoption-2026-09.md](#sec-468).+> in, see [oss-adoption-2026-09.md](#sec-473).- **three.js (#1, ~113k)** dwarfs everything else in web 3D — it is the foundation this platform is built on.- The **pmndrs / React ecosystem** dominates the React side: `react-three-fiber` (#5), `drei` (#42), `uikit` (#179). Framework wrappers exist for every stack: `troisjs/trois` + `Tresjs/tres` (Vue), `threlte` (Svelte), `gre/gl-react` (React shaders).@@ -127553,7 +128033,7 @@ Apply a 3D-signal regex filter over `description + topics` and a denylist of non----<a id="sec-502"></a>+<a id="sec-509"></a>> **Source:** `docs/portal.md` · [↑ table of contents](#table-of-contents)@@ -127682,7 +128162,7 @@ Portal is a crawler that runs on a visitor's request, and behaves like one. It i----<a id="sec-503"></a>+<a id="sec-510"></a>> **Source:** `docs/portfolio.md` · [↑ table of contents](#table-of-contents)@@ -127726,7 +128206,7 @@ GET /api/crypto/portfolio?address=<wallet>&chain=solana|ethereum```which builds on the same balance layer as-[`/api/crypto/wallet`](#sec-231) ([`api/_lib/balances.js`](../api/_lib/balances.js)):+[`/api/crypto/wallet`](#sec-232) ([`api/_lib/balances.js`](../api/_lib/balances.js)):- **Solana** (fully keyless): Helius DAS when a key is configured, public RPCotherwise; prices from Jupiter Lite with a pump.fun bonding-curve fallback;@@ -127792,15 +128272,15 @@ responses are cached for about a minute per wallet.## Related surfaces-- [`/wallet`](#sec-777): your own custodial three.ws wallet.+- [`/wallet`](#sec-786): your own custodial three.ws wallet.- `/agent-wallet`: the agent wallet hub, whose Portfolio tab covers an agent'sholdings with FIFO cost basis and PnL attribution.-- [`/api/crypto/wallet`](#sec-231): the raw balances endpoint this page+- [`/api/crypto/wallet`](#sec-232): the raw balances endpoint this pagebuilds on, for agents and scripts.----<a id="sec-504"></a>+<a id="sec-511"></a>> **Source:** `docs/premium.md` · [↑ table of contents](#table-of-contents)@@ -127935,7 +128415,7 @@ tiers that remain free (news feed, digest, archive stats/trending).----<a id="sec-505"></a>+<a id="sec-512"></a>> **Source:** `docs/press-kit.md` · [↑ table of contents](#table-of-contents)@@ -128090,7 +128570,7 @@ Two rules that matter if you are laying out a story or a slide:The two extra OpenAI files inside the zip need more care than the two above. The short-phrasing card exists for one specific post and is not the general-purpose announcement graphic. The two-mark lockup uses OpenAI's logomark rather than the partner badge, which their brand guidelines govern separately, so a co-branded lockup is normally something a partner clears first. The full rules for every OpenAI asset in this repo are in [`marketing/openai-select-partner/badge-usage.md`](../marketing/openai-select-partner/badge-usage.md), with the announcement pack itself at [`marketing/openai-select-partner/README.md`](../marketing/openai-select-partner/README.md).-For the wider programme list and how to describe each one, see [Partner ecosystem](#sec-474).+For the wider programme list and how to describe each one, see [Partner ecosystem](#sec-480).---@@ -128108,14 +128588,14 @@ Use that inbox for anything the page does not cover: a format that is not here (## Related-- [Partner ecosystem](#sec-474): every programme three.ws is in, at the status it actually claims-- [Listings and distribution](#sec-403): marketplaces, directories, and media partners, with per-listing status+- [Partner ecosystem](#sec-480): every programme three.ws is in, at the status it actually claims+- [Listings and distribution](#sec-407): marketplaces, directories, and media partners, with per-listing status- [Brand asset renderer](../marketing/brand/README.md): where the marks come from and how to regenerate them- [Marketing campaigns](../marketing/README.md): announcement packs, social copy, and finished graphics----<a id="sec-506"></a>+<a id="sec-513"></a>> **Source:** `docs/procedural-animation.md` · [↑ table of contents](#table-of-contents)@@ -128288,12 +128768,12 @@ If you hit a rig whose bones do not resolve, the fix is a bone-name mapping in [## Related- [animations.md](#sec-101) — the pre-baked clip library these layers run on top of-- [avatar-pipeline.md](#sec-148) — how avatars are generated and rigged+- [avatar-pipeline.md](#sec-149) — how avatars are generated and rigged- [agent-system.md](#sec-068) — `AgentAvatar`, the protocol, and the emotion layers----<a id="sec-507"></a>+<a id="sec-514"></a>> **Source:** `docs/product-demo.md` · [↑ table of contents](#table-of-contents)@@ -128372,7 +128852,7 @@ selector to stop everything.three things about it.**Real time, not stepped frames.** The Seeker recordings-([`docs/seeker-video.md`](#sec-632)) step one frame at a time to reproduce a phone panel+([`docs/seeker-video.md`](#sec-639)) step one frame at a time to reproduce a phone panelexactly. This does the opposite and uses Playwright's own recorder at 1920x1080, because a productdemo is watched for its motion: 3D scenes streaming in, a model spinning under the cursor, a gridsettling after a search. Stepped frames freeze all of that, and nearly every route here runs WebGL.@@ -128458,7 +128938,7 @@ concatenates all of them into `three-ws-demo.mp4`.----<a id="sec-508"></a>+<a id="sec-515"></a>> **Source:** `docs/prompts.md` · [↑ table of contents](#table-of-contents)@@ -128485,7 +128965,7 @@ once and keep.| Setup | What it means | How ||---|---|---|| **No setup** | The prompt tells your assistant which public endpoint to call. It works anywhere Claude can make an HTTP request or run a command. | Nothing to do. |-| **Free MCP server** | The three.ws 3D Studio as native tools: generate, rig, refine, look at a model, give it a persona. No account, no key, no payment. | `claude mcp add --transport http three-ws-studio https://three.ws/api/mcp-studio`, or add that URL as a custom connector in the Claude apps with authentication set to None. See [MCP Studio](#sec-414). |+| **Free MCP server** | The three.ws 3D Studio as native tools: generate, rig, refine, look at a model, give it a persona. No account, no key, no payment. | `claude mcp add --transport http three-ws-studio https://three.ws/api/mcp-studio`, or add that URL as a custom connector in the Claude apps with authentication set to None. See [MCP Studio](#sec-418). || **Skills pack** | The [Agent Skills](#sec-064) pack, so your assistant already knows the platform's endpoints and rules and your prompts can be one sentence long. | Install the `three-ws-core` plugin, or copy a folder from `.agents/skills/` into your project's `.claude/skills/`. || **Agent wallet** | A funded agent wallet, for the prompts that buy or sell calls in the x402 economy. | Start at [three.ws/start](https://three.ws/start). |@@ -128574,13 +129054,13 @@ spend money, make it stop for a confirmation.- [Agent Skills](#sec-064): the same capabilities as skills yourassistant loads automatically, rather than prompts you paste.-- [MCP Studio](#sec-414): the free 3D MCP server most of these prompts use.+- [MCP Studio](#sec-418): the free 3D MCP server most of these prompts use.- [3D API](#sec-001): the keyless HTTP endpoints behind the no-setup prompts.-- [Embedding](#sec-259): what the web-component prompts are driving.+- [Embedding](#sec-262): what the web-component prompts are driving.----<a id="sec-509"></a>+<a id="sec-516"></a>> **Source:** `docs/prompts/01-cli-setup-login.md` · [↑ table of contents](#table-of-contents)@@ -128640,7 +129120,7 @@ A new package `packages/three-ws-cli/` published as `three-ws` (bin `three-ws`,----<a id="sec-510"></a>+<a id="sec-517"></a>> **Source:** `docs/prompts/03-mcp-tool-policy-skill.md` · [↑ table of contents](#table-of-contents)@@ -128699,7 +129179,7 @@ Walk every tool in every server and package and assign group, tier, confirm flag----<a id="sec-511"></a>+<a id="sec-518"></a>> **Source:** `docs/prompts/04-community-skills-registry.md` · [↑ table of contents](#table-of-contents)@@ -128749,7 +129229,7 @@ Seed it with at least twelve real, useful skills written for our tools: token sa----<a id="sec-512"></a>+<a id="sec-519"></a>> **Source:** `docs/prompts/05-agents-rest-parity.md` · [↑ table of contents](#table-of-contents)@@ -128815,7 +129295,7 @@ Every route above gets a tool on `/api/mcp-agent` under the policy from prompt 0----<a id="sec-513"></a>+<a id="sec-520"></a>> **Source:** `docs/prompts/06-agents-sdk.md` · [↑ table of contents](#table-of-contents)@@ -128875,7 +129355,7 @@ Retries on 5xx, network errors and timeouts with exponential backoff and an idem----<a id="sec-514"></a>+<a id="sec-521"></a>> **Source:** `docs/prompts/07-perps.md` · [↑ table of contents](#table-of-contents)@@ -128933,7 +129413,7 @@ Extend `api/_lib/agent-trade-guards.js` with perps limits: max leverage per agen----<a id="sec-515"></a>+<a id="sec-522"></a>> **Source:** `docs/prompts/08-lending.md` · [↑ table of contents](#table-of-contents)@@ -128985,7 +129465,7 @@ Every fund-moving call goes through the agent wallet signer, `enforceSpendLimit`----<a id="sec-516"></a>+<a id="sec-523"></a>> **Source:** `docs/prompts/09-prediction-markets.md` · [↑ table of contents](#table-of-contents)@@ -129033,7 +129513,7 @@ Guards: per-agent max stake per market and per day in `api/_lib/agent-trade-guar----<a id="sec-517"></a>+<a id="sec-524"></a>> **Source:** `docs/prompts/10-agent-marketplace-bids.md` · [↑ table of contents](#table-of-contents)@@ -129086,7 +129566,7 @@ Under `api/v1/marketplace/agents/` with MCP tools on `/api/mcp-agent` under the----<a id="sec-518"></a>+<a id="sec-525"></a>> **Source:** `docs/prompts/11-agent-mail.md` · [↑ table of contents](#table-of-contents)@@ -129140,7 +129620,7 @@ Under `api/v1/agents/:id/mail/` with MCP tools under the prompt 03 policy:----<a id="sec-519"></a>+<a id="sec-526"></a>> **Source:** `docs/prompts/12-agent-cards.md` · [↑ table of contents](#table-of-contents)@@ -129188,7 +129668,7 @@ Under `api/v1/agents/:id/cards/` with MCP tools under the prompt 03 policy:----<a id="sec-520"></a>+<a id="sec-527"></a>> **Source:** `docs/prompts/13-chat-gateways.md` · [↑ table of contents](#table-of-contents)@@ -129237,7 +129717,7 @@ Notifications from `api/_lib/notify-prefs.js` gain `telegram` and `discord` chan----<a id="sec-521"></a>+<a id="sec-528"></a>> **Source:** `docs/prompts/14-desktop-app-release.md` · [↑ table of contents](#table-of-contents)@@ -129279,7 +129759,7 @@ Grow the companion into "three.ws Desktop": the companion stays as a mode, and t----<a id="sec-522"></a>+<a id="sec-529"></a>> **Source:** `docs/prompts/15-gasless-launch.md` · [↑ table of contents](#table-of-contents)@@ -129322,7 +129802,7 @@ In the CLI from prompt 01: `three-ws launch --name --symbol --description --imag----<a id="sec-523"></a>+<a id="sec-530"></a>> **Source:** `docs/prompts/16-self-funded-inference.md` · [↑ table of contents](#table-of-contents)@@ -129365,7 +129845,7 @@ Model usage is billed to the account's credits (`api/credits/`, `api/billing/`,----<a id="sec-524"></a>+<a id="sec-531"></a>> **Source:** `docs/prompts/17-unified-mcp-endpoint.md` · [↑ table of contents](#table-of-contents)@@ -129396,7 +129876,7 @@ We run seven hosted MCP servers (`docs/mcp.md`): main, 3D, studio, agent wallet,----<a id="sec-525"></a>+<a id="sec-532"></a>> **Source:** `docs/prompts/18-open-model-roster.md` · [↑ table of contents](#table-of-contents)@@ -129424,7 +129904,7 @@ The model roster in `api/brain/chat.js` and `api/_lib/chat-models.js` is Claude,----<a id="sec-526"></a>+<a id="sec-533"></a>> **Source:** `docs/prompts/19-self-custody-and-signers.md` · [↑ table of contents](#table-of-contents)@@ -129454,7 +129934,7 @@ Agent wallets are custodial: keys are generated and encrypted by the platform (`----<a id="sec-527"></a>+<a id="sec-534"></a>> **Source:** `docs/prompts/20-local-agent-runtime-tui.md` · [↑ table of contents](#table-of-contents)@@ -129488,7 +129968,7 @@ A new package `packages/agent-cli/` published as `@three-ws/agent`, reachable as----<a id="sec-528"></a>+<a id="sec-535"></a>> **Source:** `docs/prompts/21-agent-memory-and-self-improvement.md` · [↑ table of contents](#table-of-contents)@@ -129519,7 +129999,7 @@ An agent has a persona and a chat history, and nothing else persists: no memory----<a id="sec-529"></a>+<a id="sec-536"></a>> **Source:** `docs/prompts/22-external-mcp-integrations-for-agents.md` · [↑ table of contents](#table-of-contents)@@ -129547,7 +130027,7 @@ Our agents use our tools. They cannot be connected to the hundreds of third-part----<a id="sec-530"></a>+<a id="sec-537"></a>> **Source:** `docs/prompts/23-distribution-into-agent-frameworks.md` · [↑ table of contents](#table-of-contents)@@ -129576,7 +130056,7 @@ For each of Claude Code, Codex CLI, Gemini CLI, Hermes Agent, OpenHands, Goose,----<a id="sec-531"></a>+<a id="sec-538"></a>> **Source:** `docs/prompts/24-more-gateways-and-voice.md` · [↑ table of contents](#table-of-contents)@@ -129610,7 +130090,7 @@ Extend `workers/agent-gateway/` with adapters behind the same `Gateway` interfac----<a id="sec-532"></a>+<a id="sec-539"></a>> **Source:** `docs/prompts/25-sandboxed-code-execution.md` · [↑ table of contents](#table-of-contents)@@ -129639,7 +130119,7 @@ Runs are tool loops over a read-only registry (`api/agent/run.js`). An agent can----<a id="sec-533"></a>+<a id="sec-540"></a>> **Source:** `docs/prompts/26-tool-gateway-bundle.md` · [↑ table of contents](#table-of-contents)@@ -129667,7 +130147,7 @@ Generation exists in pieces: 3D and image forge lanes, vision, assistant speech,----<a id="sec-534"></a>+<a id="sec-541"></a>> **Source:** `docs/prompts/27-bounties-and-hackathons.md` · [↑ table of contents](#table-of-contents)@@ -129703,7 +130183,7 @@ Agents on three.ws can earn by selling skills and answering x402 calls. They can----<a id="sec-535"></a>+<a id="sec-542"></a>> **Source:** `docs/prompts/28-public-economics-dashboard.md` · [↑ table of contents](#table-of-contents)@@ -129731,7 +130211,7 @@ The flywheel runs (`api/cron/economy-tick.js`, the buyback crons, the launcher c----<a id="sec-536"></a>+<a id="sec-543"></a>> **Source:** `docs/prompts/29-free-tier-and-hosting-plan.md` · [↑ table of contents](#table-of-contents)@@ -129760,7 +130240,7 @@ Plans, quotas, invoices and credits exist under `api/billing/` and `api/credits/----<a id="sec-537"></a>+<a id="sec-544"></a>> **Source:** `docs/prompts/30-trading-tool-parity.md` · [↑ table of contents](#table-of-contents)@@ -129793,7 +130273,7 @@ On the unified endpoint under the prompt 03 policy, and in the SDK from prompt 0----<a id="sec-538"></a>+<a id="sec-545"></a>> **Source:** `docs/prompts/31-human-task-fulfillment.md` · [↑ table of contents](#table-of-contents)@@ -129822,7 +130302,7 @@ An agent can pay other agents and paid APIs. It cannot get something done in the----<a id="sec-539"></a>+<a id="sec-546"></a>> **Source:** `docs/prompts/32-evm-secondary-leg.md` · [↑ table of contents](#table-of-contents)@@ -129851,7 +130331,7 @@ Agent wallets, launches and the flywheel are Solana. EVM surfaces exist in piece----<a id="sec-540"></a>+<a id="sec-547"></a>> **Source:** `docs/prompts/33-account-social-and-sso.md` · [↑ table of contents](#table-of-contents)@@ -129880,7 +130360,7 @@ X posting exists as crons and configuration spread across the announcement lanes----<a id="sec-541"></a>+<a id="sec-548"></a>> **Source:** `docs/prompts/34-localization.md` · [↑ table of contents](#table-of-contents)@@ -129908,7 +130388,7 @@ Every README and doc is English only. Competing open agents ship READMEs in Chin----<a id="sec-542"></a>+<a id="sec-549"></a>> **Source:** `docs/prompts/35-always-on-strategy-loop.md` · [↑ table of contents](#table-of-contents)@@ -129936,7 +130416,7 @@ Prompt 05 gives agents `start` and `stop`, and automations fire on triggers. A "----<a id="sec-543"></a>+<a id="sec-550"></a>> **Source:** `docs/prompts/36-agent-evals-and-replay.md` · [↑ table of contents](#table-of-contents)@@ -129966,7 +130446,7 @@ We ship prompt, model and tool changes with no way to know whether agents got be----<a id="sec-544"></a>+<a id="sec-551"></a>> **Source:** `docs/prompts/README.md` · [↑ table of contents](#table-of-contents)@@ -129980,35 +130460,35 @@ Dependencies flow downward. Rows in the same tier can run in parallel.| Tier | Prompt | Why this order ||---|---|---|-| 1 | [01 CLI setup and login](#sec-509) | Everything else gets installed through it. |-| 1 | [03 MCP tool policy and the model-facing skill](#sec-510) | Every later tool registers under it. |-| 1 | [05 Agents REST parity](#sec-512) | The SDK, gateways and loop all wrap these routes. |-| 1 | [17 One MCP endpoint, one OAuth](#sec-524) | Every later tool mounts here. |-| 1 | [18 Open-model roster and free-tier models](#sec-525) | Needed by the free tier and the local runtime. |-| 1 | [29 Free tier, pricing and rate limits](#sec-536) | Every metered brief prices against `data/plans.json`. |-| 2 | [04 Community skills registry](#sec-511) | Installs through the CLI. |-| 2 | [06 Agents SDK](#sec-513) | Wraps tier 1 routes. |-| 2 | [15 Gasless launch and the launch command](#sec-522) | Adds a CLI subcommand. |-| 2 | [16 Self-funded inference](#sec-523) | Wallet plus credits. |-| 2 | [19 Self-custody, signers, key export, balance history](#sec-526) | Changes the signing contract every financial brief uses. |-| 2 | [30 Trading tool parity](#sec-537) | Exposes existing trading as tools; venue interface for later legs. |-| 2 | [33 Account, X posting policy, Google linking](#sec-540) | Account objects the gateways and status tools read. |-| 3 | [07 Perps](#sec-514), [08 Lending](#sec-515), [09 Prediction markets](#sec-516) | New execution venues under the policy. |-| 3 | [10 Whole-agent marketplace with bids](#sec-517) | Transfers custody; depends on 19. |-| 3 | [11 Agent mail](#sec-518), [12 Agent cards](#sec-519), [31 Human tasks](#sec-538) | Real-world surfaces; provider adapters plus tools. |-| 3 | [21 Memory and self-improvement](#sec-528) | Needs runs (05) and prompt-only skills (04). |-| 3 | [22 External MCP integrations for agents](#sec-529) | Needs the policy (03) and the unified endpoint (17). |-| 3 | [25 Sandboxed code execution](#sec-532), [26 Tool gateway](#sec-533) | New default tools under the policy, metered by 29. |-| 3 | [28 Public economics](#sec-535) | Reads the fee settings the launch brief unifies. |-| 4 | [13 Telegram and Discord](#sec-520), [24 Slack, WhatsApp, Signal, SMS, email, voice](#sec-531) | Uses runs, link codes and mail. |-| 4 | [20 Local agent runtime and TUI](#sec-527) | Uses 17, 25, 26, 21 and the gateway. |-| 4 | [35 Always-on strategy loop](#sec-542) | Uses runs, memory, budgets and guards. |-| 4 | [27 Bounties and hackathons](#sec-534) | Creates runs from bounties; feeds 28. |-| 4 | [32 EVM secondary leg](#sec-539) | Extends the venue interfaces after Solana is complete. |-| 5 | [14 Desktop app release](#sec-521) | Ships the console over everything above. |-| 5 | [23 Distribution into every agent framework](#sec-530) | Packages 01, 03 and 17 for other agents. |-| 5 | [34 Localization](#sec-541) | Translates what exists. |-| 5 | [36 Agent evals and replay](#sec-543) | Measures everything above; smoke suite into the gate. |+| 1 | [01 CLI setup and login](#sec-516) | Everything else gets installed through it. |+| 1 | [03 MCP tool policy and the model-facing skill](#sec-517) | Every later tool registers under it. |+| 1 | [05 Agents REST parity](#sec-519) | The SDK, gateways and loop all wrap these routes. |+| 1 | [17 One MCP endpoint, one OAuth](#sec-531) | Every later tool mounts here. |+| 1 | [18 Open-model roster and free-tier models](#sec-532) | Needed by the free tier and the local runtime. |+| 1 | [29 Free tier, pricing and rate limits](#sec-543) | Every metered brief prices against `data/plans.json`. |+| 2 | [04 Community skills registry](#sec-518) | Installs through the CLI. |+| 2 | [06 Agents SDK](#sec-520) | Wraps tier 1 routes. |+| 2 | [15 Gasless launch and the launch command](#sec-529) | Adds a CLI subcommand. |+| 2 | [16 Self-funded inference](#sec-530) | Wallet plus credits. |+| 2 | [19 Self-custody, signers, key export, balance history](#sec-533) | Changes the signing contract every financial brief uses. |+| 2 | [30 Trading tool parity](#sec-544) | Exposes existing trading as tools; venue interface for later legs. |+| 2 | [33 Account, X posting policy, Google linking](#sec-547) | Account objects the gateways and status tools read. |+| 3 | [07 Perps](#sec-521), [08 Lending](#sec-522), [09 Prediction markets](#sec-523) | New execution venues under the policy. |+| 3 | [10 Whole-agent marketplace with bids](#sec-524) | Transfers custody; depends on 19. |+| 3 | [11 Agent mail](#sec-525), [12 Agent cards](#sec-526), [31 Human tasks](#sec-545) | Real-world surfaces; provider adapters plus tools. |+| 3 | [21 Memory and self-improvement](#sec-535) | Needs runs (05) and prompt-only skills (04). |+| 3 | [22 External MCP integrations for agents](#sec-536) | Needs the policy (03) and the unified endpoint (17). |+| 3 | [25 Sandboxed code execution](#sec-539), [26 Tool gateway](#sec-540) | New default tools under the policy, metered by 29. |+| 3 | [28 Public economics](#sec-542) | Reads the fee settings the launch brief unifies. |+| 4 | [13 Telegram and Discord](#sec-527), [24 Slack, WhatsApp, Signal, SMS, email, voice](#sec-538) | Uses runs, link codes and mail. |+| 4 | [20 Local agent runtime and TUI](#sec-534) | Uses 17, 25, 26, 21 and the gateway. |+| 4 | [35 Always-on strategy loop](#sec-549) | Uses runs, memory, budgets and guards. |+| 4 | [27 Bounties and hackathons](#sec-541) | Creates runs from bounties; feeds 28. |+| 4 | [32 EVM secondary leg](#sec-546) | Extends the venue interfaces after Solana is complete. |+| 5 | [14 Desktop app release](#sec-528) | Ships the console over everything above. |+| 5 | [23 Distribution into every agent framework](#sec-537) | Packages 01, 03 and 17 for other agents. |+| 5 | [34 Localization](#sec-548) | Translates what exists. |+| 5 | [36 Agent evals and replay](#sec-550) | Measures everything above; smoke suite into the gate. |## Rules that apply to every brief@@ -130022,7 +130502,7 @@ Dependencies flow downward. Rows in the same tier can run in parallel.----<a id="sec-545"></a>+<a id="sec-552"></a>> **Source:** `docs/prompts/event-markets/01-core-markets-and-picks.md` · [↑ table of contents](#table-of-contents)@@ -130059,7 +130539,7 @@ Events run on three.ws with no market layer. There is no object that says "this----<a id="sec-546"></a>+<a id="sec-553"></a>> **Source:** `docs/prompts/event-markets/02-market-pages-and-share-cards.md` · [↑ table of contents](#table-of-contents)@@ -130094,7 +130574,7 @@ Both pages in `data/pages.json`, `docs/event-markets.md` section on the pages, `----<a id="sec-547"></a>+<a id="sec-554"></a>> **Source:** `docs/prompts/event-markets/03-auto-resolution.md` · [↑ table of contents](#table-of-contents)@@ -130135,7 +130615,7 @@ Check for the contract in `api/_lib/event-markets/`. If absent, create the minim----<a id="sec-548"></a>+<a id="sec-555"></a>> **Source:** `docs/prompts/event-markets/04-auto-open-for-every-event.md` · [↑ table of contents](#table-of-contents)@@ -130171,7 +130651,7 @@ Check for the contract in `api/_lib/event-markets/`. If absent, create the minim----<a id="sec-549"></a>+<a id="sec-556"></a>> **Source:** `docs/prompts/event-markets/05-announcement-automation.md` · [↑ table of contents](#table-of-contents)@@ -130207,7 +130687,7 @@ Check for the contract in `api/_lib/event-markets/`. If absent, create the minim----<a id="sec-550"></a>+<a id="sec-557"></a>> **Source:** `docs/prompts/event-markets/06-entrant-amplification-kit.md` · [↑ table of contents](#table-of-contents)@@ -130243,7 +130723,7 @@ Check for the contract in `api/_lib/event-markets/`. If absent, create the minim----<a id="sec-551"></a>+<a id="sec-558"></a>> **Source:** `docs/prompts/event-markets/07-pick-leaderboard-and-rewards.md` · [↑ table of contents](#table-of-contents)@@ -130278,7 +130758,7 @@ Check for the contract in `api/_lib/event-markets/`. If absent, create the minim----<a id="sec-552"></a>+<a id="sec-559"></a>> **Source:** `docs/prompts/event-markets/08-live-odds-feed.md` · [↑ table of contents](#table-of-contents)@@ -130313,7 +130793,7 @@ Check for the contract in `api/_lib/event-markets/`. If absent, create the minim----<a id="sec-553"></a>+<a id="sec-560"></a>> **Source:** `docs/prompts/event-markets/09-agents-as-forecasters.md` · [↑ table of contents](#table-of-contents)@@ -130348,7 +130828,7 @@ Check for the contract in `api/_lib/event-markets/`. If absent, create the minim----<a id="sec-554"></a>+<a id="sec-561"></a>> **Source:** `docs/prompts/event-markets/10-staked-markets-solana.md` · [↑ table of contents](#table-of-contents)@@ -130391,7 +130871,7 @@ Check for the contract in `api/_lib/event-markets/`. If absent, create the minim----<a id="sec-555"></a>+<a id="sec-562"></a>> **Source:** `docs/prompts/event-markets/README.md` · [↑ table of contents](#table-of-contents)@@ -130434,20 +130914,20 @@ All briefs agree on one seam. The first brief to run creates it; every later bri| # | Brief | What it ships ||---|---|---|-| 01 | [Core markets and picks API](#sec-545) | The contract above, REST reads and writes, MCP tools |-| 02 | [Market pages and share cards](#sec-546) | `/event-markets`, market detail, OG card |-| 03 | [Auto-resolution from our own data](#sec-547) | Resolvers per source kind, lock and settle cron |-| 04 | [Auto-open a market for every event](#sec-548) | Cron that creates and populates markets |-| 05 | [Announcement automation](#sec-549) | Draft queue, entrant tagging, owner-approved posting |-| 06 | [Entrant amplification kit](#sec-550) | Per-entrant share kit, embed widget, notifications |-| 07 | [Pick leaderboard, streaks and rewards](#sec-551) | Forecaster rankings, streaks, reward rail |-| 08 | [Live odds feed and ticker](#sec-552) | Streaming odds, pulse integration, activity ticker |-| 09 | [Agents as forecasters](#sec-553) | Agent picks, reasoning, public track record |-| 10 | [Staked markets on Solana](#sec-554) | Escrow design, program, devnet, stops at the gate |+| 01 | [Core markets and picks API](#sec-552) | The contract above, REST reads and writes, MCP tools |+| 02 | [Market pages and share cards](#sec-553) | `/event-markets`, market detail, OG card |+| 03 | [Auto-resolution from our own data](#sec-554) | Resolvers per source kind, lock and settle cron |+| 04 | [Auto-open a market for every event](#sec-555) | Cron that creates and populates markets |+| 05 | [Announcement automation](#sec-556) | Draft queue, entrant tagging, owner-approved posting |+| 06 | [Entrant amplification kit](#sec-557) | Per-entrant share kit, embed widget, notifications |+| 07 | [Pick leaderboard, streaks and rewards](#sec-558) | Forecaster rankings, streaks, reward rail |+| 08 | [Live odds feed and ticker](#sec-559) | Streaming odds, pulse integration, activity ticker |+| 09 | [Agents as forecasters](#sec-560) | Agent picks, reasoning, public track record |+| 10 | [Staked markets on Solana](#sec-561) | Escrow design, program, devnet, stops at the gate |----<a id="sec-556"></a>+<a id="sec-563"></a>> **Source:** `docs/provenance.md` · [↑ table of contents](#table-of-contents)@@ -130472,7 +130952,7 @@ Generate a model through Forge (any lane) or buy one through the asset bazaar anThe owner can turn this off platform-wide with `PROVENANCE_AUTO_DISABLE=true`; there's no per-asset opt-out, and turning it off never touches `verify_provenance`, `GET /api/provenance`, or `anchor_provenance`, which keep working on whatever was already issued.-> **v2 credentials also carry a signed physics grade.** Alongside authorship, a credential can assert what a rigid-body solver would make of the mesh: watertight or not, real meters or a generator's unit box, its exact volume and inertia tensor. An unsigned grade is a claim anyone can forge; this one is not. See [Simulation readiness](#sec-643). Credentials signed under v1, before the field existed, keep verifying byte for byte, permanently.+> **v2 credentials also carry a signed physics grade.** Alongside authorship, a credential can assert what a rigid-body solver would make of the mesh: watertight or not, real meters or a generator's unit box, its exact volume and inertia tensor. An unsigned grade is a claim anyone can forge; this one is not. See [Simulation readiness](#sec-651). Credentials signed under v1, before the field existed, keep verifying byte for byte, permanently.## Verify a model (free, public)@@ -130544,7 +131024,7 @@ Real hashing, real ed25519 signature, real on-chain write. Requires the issuer k----<a id="sec-557"></a>+<a id="sec-564"></a>> **Source:** `docs/publishing-program-2026-09.md` · [↑ table of contents](#table-of-contents)@@ -130571,18 +131051,18 @@ Two rules that apply to every entry, because both have burned publishing program| # | Venue | Draft | Angle | Length | Unblocked by ||---|---|---|---|---|---|-| 1 | OpenAI Developer Community | [openai-community-physical-world-post.md](#sec-463) | The follow-up to the 3D Studio connector: tools that spend money or move matter, the vision loop, the 72-server fleet problem | ~5,650 words | Owner approval |-| 2 | AWS Builder Center | [aws-builder-center-agent-commerce-spine.md](#sec-153) | The authorization spine for autonomous commerce: Concurrent Agreements, budgets instead of credentials, preflight, receipts, physical fulfillment | ~4,000 words | Owner approval |-| 3 | IBM Community (Three.ws User Group) | [ibm-community-governed-agents-post.md](#sec-365) | Granite Guardian as an action veto once agents touch homes, cars and manufacturing, plus the full watsonx.ai surface and a build-it-yourself walkthrough | ~4,900 words | Owner approval |-| 4 | CoinMarketCap Community | [coinmarketcap-article-2026-09-agent-economy.md](#sec-198) | What an agent can actually buy now, with the on-chain and payment infrastructure behind it and the honest numbers | ~7,850 words | Owner approval, plus the other-coin commit gate |-| 5 | Home Assistant Community | [home-assistant-community-post.md](#sec-340) | A HACS integration that dials out, an MCP server whose lock tools refuse over stdio, household roles enforced server-side | ~1,750 words | Owner approval |-| 6 | three.js Forum | [threejs-forum-post.md](#sec-679) | Five open-sourced pieces: retargeting with no rig allowlist, progressive GLB, glTF diffing, physics grade, terminal renderer | ~1,470 words | Owner approval |-| 7 | NVIDIA Developer Forums | [nvidia-forum-gpu-fleet-post.md](#sec-446) | The production GPU fleet: cold weight loads, min-instances as a quota decision, keep-warm crons, chains with no empty rung | ~1,480 words | Owner approval |-| 8 | Hugging Face community article | [huggingface-agent-feedback-loop.md](#sec-353) | Closing the agentic-3D feedback loop: perceive, grade, diff, retarget, on open models | ~1,690 words | Owner approval |-| 9 | dev.to (canonical back to three.ws) | [devto-mcp-fleet-post.md](#sec-245) | 72 MCP servers, four traps, four rules, and the one change that mattered more than the fleet | ~1,290 words | Owner approval |-| 10 | Google Cloud Community | [google-cloud-community-post.md](#sec-331) | One container, 115 scheduled jobs, a GPU fleet that sleeps, and three deploy gates each written the day after an outage | ~1,530 words | Owner approval |-| 11 | NVIDIA Developer Forums | [nvidia-forum-browser-digital-human.md](#sec-445) | Audio2Face-3D streamed onto a rig the visitor generated ninety seconds ago | ~1,570 words | [Posted 2026-09-22](https://forums.developer.nvidia.com/t/a-digital-human-in-a-browser-tab-streaming-audio2face-3d-onto-whatever-rig-the-visitor-brought/383953) |-| 12 | NVIDIA Developer Forums | [nvidia-forum-model-retirement-post.md](#sec-447) | Both models our live posts featured were retired within weeks: why a 410 is invisible to a fallback chain, vector tags that survive an embedder retirement, three lifecycle asks of NVIDIA | ~2,300 words | [Posted 2026-09-21](https://forums.developer.nvidia.com/t/nvidia-nim-model-retirements-what-a-410-gone-does-to-a-fallback-chain-and-how-we-survive-it-now/383950) |+| 1 | OpenAI Developer Community | [openai-community-physical-world-post.md](#sec-468) | The follow-up to the 3D Studio connector: tools that spend money or move matter, the vision loop, the 72-server fleet problem | ~5,650 words | Owner approval |+| 2 | AWS Builder Center | [aws-builder-center-agent-commerce-spine.md](#sec-154) | The authorization spine for autonomous commerce: Concurrent Agreements, budgets instead of credentials, preflight, receipts, physical fulfillment | ~4,000 words | Owner approval |+| 3 | IBM Community (Three.ws User Group) | [ibm-community-governed-agents-post.md](#sec-369) | Granite Guardian as an action veto once agents touch homes, cars and manufacturing, plus the full watsonx.ai surface and a build-it-yourself walkthrough | ~4,900 words | Owner approval |+| 4 | CoinMarketCap Community | [coinmarketcap-article-2026-09-agent-economy.md](#sec-199) | What an agent can actually buy now, with the on-chain and payment infrastructure behind it and the honest numbers | ~7,850 words | Owner approval, plus the other-coin commit gate |+| 5 | Home Assistant Community | [home-assistant-community-post.md](#sec-344) | A HACS integration that dials out, an MCP server whose lock tools refuse over stdio, household roles enforced server-side | ~1,750 words | Owner approval |+| 6 | three.js Forum | [threejs-forum-post.md](#sec-687) | Five open-sourced pieces: retargeting with no rig allowlist, progressive GLB, glTF diffing, physics grade, terminal renderer | ~1,470 words | Owner approval |+| 7 | NVIDIA Developer Forums | [nvidia-forum-gpu-fleet-post.md](#sec-450) | The production GPU fleet: cold weight loads, min-instances as a quota decision, keep-warm crons, chains with no empty rung | ~1,480 words | Owner approval |+| 8 | Hugging Face community article | [huggingface-agent-feedback-loop.md](#sec-357) | Closing the agentic-3D feedback loop: perceive, grade, diff, retarget, on open models | ~1,690 words | Owner approval |+| 9 | dev.to (canonical back to three.ws) | [devto-mcp-fleet-post.md](#sec-246) | 72 MCP servers, four traps, four rules, and the one change that mattered more than the fleet | ~1,290 words | Owner approval |+| 10 | Google Cloud Community | [google-cloud-community-post.md](#sec-335) | One container, 115 scheduled jobs, a GPU fleet that sleeps, and three deploy gates each written the day after an outage | ~1,530 words | Owner approval |+| 11 | NVIDIA Developer Forums | [nvidia-forum-browser-digital-human.md](#sec-449) | Audio2Face-3D streamed onto a rig the visitor generated ninety seconds ago | ~1,570 words | [Posted 2026-09-22](https://forums.developer.nvidia.com/t/a-digital-human-in-a-browser-tab-streaming-audio2face-3d-onto-whatever-rig-the-visitor-brought/383953) |+| 12 | NVIDIA Developer Forums | [nvidia-forum-model-retirement-post.md](#sec-451) | Both models our live posts featured were retired within weeks: why a 410 is invisible to a fallback chain, vector tags that survive an embedder retirement, three lifecycle asks of NVIDIA | ~2,300 words | [Posted 2026-09-21](https://forums.developer.nvidia.com/t/nvidia-nim-model-retirements-what-a-410-gone-does-to-a-fallback-chain-and-how-we-survive-it-now/383950) |## CoinMarketCap niche series, October 2026@@ -130590,16 +131070,16 @@ Six long-form deep-dives (each with a friendly opening, the technical depth afte| # | Draft | Angle | Length | Unblocked by ||---|---|---|---|---|-| 13 | [coinmarketcap-article-2026-10-x402-failure-paths.md](#sec-204) | How three.ws makes agent payments on Solana reliable and verifiable: preflight, careful retries, verify-before-settle, clear pending states, signed receipts | ~6,400 words | Owner approval, plus the other-coin commit gate |-| 14 | [coinmarketcap-article-2026-10-solana-reputation.md](#sec-202) | Agent identity as a Metaplex Core asset, memo attestations anyone can re-crawl, the staking market, skill licenses and royalties, and skill royalties | ~6,500 words | Owner approval, plus the other-coin commit gate |-| 15 | [coinmarketcap-article-2026-10-copy-trading.md](#sec-199) | Copy trading where the track record is the product: losses kept, self-dealing excluded, alpha-drip delays the reveal and never the record | ~7,050 words | Owner approval, plus the other-coin commit gate |-| 16 | [coinmarketcap-article-2026-10-sniper-oracle.md](#sec-201) | The sniper fleet trading from its own wallets, the Oracle model published with its weights, and health checks that confirm an agent can act | ~7,250 words | Owner approval, plus the other-coin commit gate |-| 17 | [coinmarketcap-article-2026-10-radar-strategy-lab.md](#sec-200) | Coin radar, fade radar, strategies as data, and backtests built on real launch history | ~6,200 words | Owner approval, plus the other-coin commit gate |-| 18 | [coinmarketcap-article-2026-10-vanity-mints.md](#sec-203) | Why every launch mint starts with 3ws: the WebAssembly grinder, the exact Base58 odds, where the secret key lives, and how launch records confirm it | ~5,700 words | Owner approval, plus the other-coin commit gate |+| 13 | [coinmarketcap-article-2026-10-x402-failure-paths.md](#sec-205) | How three.ws makes agent payments on Solana reliable and verifiable: preflight, careful retries, verify-before-settle, clear pending states, signed receipts | ~6,400 words | Owner approval, plus the other-coin commit gate |+| 14 | [coinmarketcap-article-2026-10-solana-reputation.md](#sec-203) | Agent identity as a Metaplex Core asset, memo attestations anyone can re-crawl, the staking market, skill licenses and royalties, and skill royalties | ~6,500 words | Owner approval, plus the other-coin commit gate |+| 15 | [coinmarketcap-article-2026-10-copy-trading.md](#sec-200) | Copy trading where the track record is the product: losses kept, self-dealing excluded, alpha-drip delays the reveal and never the record | ~7,050 words | Owner approval, plus the other-coin commit gate |+| 16 | [coinmarketcap-article-2026-10-sniper-oracle.md](#sec-202) | The sniper fleet trading from its own wallets, the Oracle model published with its weights, and health checks that confirm an agent can act | ~7,250 words | Owner approval, plus the other-coin commit gate |+| 17 | [coinmarketcap-article-2026-10-radar-strategy-lab.md](#sec-201) | Coin radar, fade radar, strategies as data, and backtests built on real launch history | ~6,200 words | Owner approval, plus the other-coin commit gate |+| 18 | [coinmarketcap-article-2026-10-vanity-mints.md](#sec-204) | Why every launch mint starts with 3ws: the WebAssembly grinder, the exact Base58 odds, where the secret key lives, and how launch records confirm it | ~5,700 words | Owner approval, plus the other-coin commit gate |## Short-form entries-All in [short-form-venue-kit-2026-09.md](#sec-639), paste-ready with each venue's constraints applied:+All in [short-form-venue-kit-2026-09.md](#sec-647), paste-ready with each venue's constraints applied:| Venue | Entry | Constraint the copy was written against ||---|---|---|@@ -130638,7 +131118,7 @@ Sequencing matters because several of these link to each other, and because theThe same five steps every time, because a published article that nothing points at is half a publication:-1. **Record the canonical URL** in the venue's index page in this repo: [aws-builder-center.md](#sec-162), [ibm-community.md](#sec-373), [huggingface.md](#sec-354), [openai-listing-channels.md](#sec-464), or [listings.md](#sec-403) for a venue with no index of its own.+1. **Record the canonical URL** in the venue's index page in this repo: [aws-builder-center.md](#sec-163), [ibm-community.md](#sec-377), [huggingface.md](#sec-358), [openai-listing-channels.md](#sec-469), or [listings.md](#sec-407) for a venue with no index of its own.2. **Add the news item** to the curated feed so it becomes a page under `/news/<slug>` and enters RSS, which is also how it reaches HackerNoon (their import is automatic and needs no per-post action).3. **Log a `data/changelog.json` entry** with the `docs` tag.4. **Answer the thread.** Every draft here ends with a real question, and the value of these venues is in the replies rather than the post.@@ -130661,14 +131141,14 @@ Written down so the next person does not re-derive it:## Related-- [Syndication](#sec-671): how the RSS feed reaches HackerNoon and any other subscriber, with no per-post action-- [Listings and distribution](#sec-403): every marketplace, directory and media partner with its per-listing status-- [Partner ecosystem](#sec-474): the eight partner programmes and the exact wording each one requires-- [Press kit](#sec-505): marks, boilerplate at four lengths, and the rules for both+- [Syndication](#sec-679): how the RSS feed reaches HackerNoon and any other subscriber, with no per-post action+- [Listings and distribution](#sec-407): every marketplace, directory and media partner with its per-listing status+- [Partner ecosystem](#sec-480): the eight partner programmes and the exact wording each one requires+- [Press kit](#sec-512): marks, boilerplate at four lengths, and the rules for both----<a id="sec-558"></a>+<a id="sec-565"></a>> **Source:** `docs/pump-claims-channel.md` · [↑ table of contents](#table-of-contents)@@ -130833,7 +131313,7 @@ built yet.----<a id="sec-559"></a>+<a id="sec-566"></a>> **Source:** `docs/pump-fun-mcp-edge.md` · [↑ table of contents](#table-of-contents)@@ -130897,7 +131377,7 @@ Both runtimes import `TOOLS` from `src/pump/mcp-tools.js`, so the tool list expo----<a id="sec-560"></a>+<a id="sec-567"></a>> **Source:** `docs/pump-launch-repos.md` · [↑ table of contents](#table-of-contents)@@ -130996,7 +131476,7 @@ rate-limits under the ~450 txs a full run makes. Pass a dedicated `--rpc`----<a id="sec-561"></a>+<a id="sec-568"></a>> **Source:** `docs/pump-launcher.md` · [↑ table of contents](#table-of-contents)@@ -131005,7 +131485,7 @@ rate-limits under the ~450 txs a full run makes. Pass a dedicated `--rpc``POST /api/x402/pump-launch` launches a brand-new [pump.fun](https://pump.fun)token for an autonomous agent in a single paid request. The agent needs **noSOL, no wallet, and no three.ws account** — it pays a flat USDC fee over the-[x402](#sec-862) rail and the platform does the rest:+[x402](#sec-877) rail and the platform does the rest:- fronts the ~0.022 SOL bonding-curve deploy cost from a funded launcher keypair,- optionally grinds a **vanity mint address**,@@ -131032,7 +131512,7 @@ current figure — read it, don't hardcode.## The free → paid funnel-The paid launch sits between two **free, keyless** [Crypto Data API](#sec-248)+The paid launch sits between two **free, keyless** [Crypto Data API](#sec-251)endpoints. Use them to make the launch land well:1. **Before you launch — check the ticker.**@@ -131097,7 +131577,7 @@ curl -X POST https://three.ws/api/x402/pump-launch \curl "https://three.ws/api/crypto/launches"```-See [x402 buyer client](#sec-851) for how to satisfy the 402 challenge in+See [x402 buyer client](#sec-866) for how to satisfy the 402 challenge incode.## Output@@ -131147,16 +131627,16 @@ token itself always deploys on **Solana mainnet** — pump.fun is mainnet-only.## Related-- [x402 paid endpoints](#sec-854) — the full catalog and pricing.-- [Crypto Data API](#sec-248) — the free `symbol` and `launches`+- [x402 paid endpoints](#sec-869) — the full catalog and pricing.+- [Crypto Data API](#sec-251) — the free `symbol` and `launches`endpoints that bookend a launch.-- [Repo → Coin Launcher](#sec-560) — the batch/CLI launcher that+- [Repo → Coin Launcher](#sec-567) — the batch/CLI launcher thatroutes 100% of creator rewards to a GitHub identity (shares the same engine).-- [x402 protocol](#sec-862) — challenge/settle mechanics.+- [x402 protocol](#sec-877) — challenge/settle mechanics.----<a id="sec-562"></a>+<a id="sec-569"></a>> **Source:** `docs/pump-platform-fee.md` · [↑ table of contents](#table-of-contents)@@ -131236,7 +131716,7 @@ carry a separate **launch fee on the dev buy**, set by the owner at 1%.----<a id="sec-563"></a>+<a id="sec-570"></a>> **Source:** `docs/pumpfun-program/README.md` · [↑ table of contents](#table-of-contents)@@ -131327,7 +131807,7 @@ tracked in `tasks/pumpfun-upstream/01-v2-trade-instructions-usdc-audit.md`.----<a id="sec-564"></a>+<a id="sec-571"></a>> **Source:** `docs/pumpfun-program/UPSTREAM-buy-sell-v2-announcement.md` · [↑ table of contents](#table-of-contents)@@ -131406,32 +131886,32 @@ Currently, no quote mint other than native SOL can be used to create or trade co- RUST crate: https://crates.io/crates/pump-rust-client## New docs-- Fee recipients: [docs/FEE_RECIPIENTS.md](#sec-571)-- Coin creation: [docs/instructions/COIN_CREATION.md](#sec-584)-- Buy: [docs/instructions/BUY.md](#sec-582)-- Sell: [docs/instructions/SELL.md](#sec-590)-- Claim cashback: [docs/instructions/CLAIM_CASHBACK.md](#sec-583)-- Collect creator fee: [docs/instructions/COLLECT_CREATOR_FEE.md](#sec-585)-- Creator fee sharing: [docs/instructions/CREATOR_FEE_SHARING.md](#sec-587)+- Fee recipients: [docs/FEE_RECIPIENTS.md](#sec-578)+- Coin creation: [docs/instructions/COIN_CREATION.md](#sec-591)+- Buy: [docs/instructions/BUY.md](#sec-589)+- Sell: [docs/instructions/SELL.md](#sec-597)+- Claim cashback: [docs/instructions/CLAIM_CASHBACK.md](#sec-590)+- Collect creator fee: [docs/instructions/COLLECT_CREATOR_FEE.md](#sec-592)+- Creator fee sharing: [docs/instructions/CREATOR_FEE_SHARING.md](#sec-594)## Other documentation-- [Pump Program](#sec-576)-- [PumpSwap](#sec-578)-- [PumpSwap SDK](#sec-579)-- [Pump Program creator fee update](#sec-575)-- [PumpSwap creator fee update](#sec-577)-- [FAQ](#sec-569)-- [Pump fee program docs](#sec-570)+- [Pump Program](#sec-583)+- [PumpSwap](#sec-585)+- [PumpSwap SDK](#sec-586)+- [Pump Program creator fee update](#sec-582)+- [PumpSwap creator fee update](#sec-584)+- [FAQ](#sec-576)+- [Pump fee program docs](#sec-577)-------<a id="sec-565"></a>+<a id="sec-572"></a>> **Source:** `docs/pumpfun-program/UPSTREAM-pumpswap-virtual-quote-reserves.md` · [↑ table of contents](#table-of-contents)@@ -131640,18 +132120,18 @@ Upstream: <https://github.com/pump-fun/pump-public-docs#pumpswap-update-virtual-----<a id="sec-566"></a>+<a id="sec-573"></a>> **Source:** `docs/pumpfun-program/UPSTREAM-v3-trades-fee-sweeps-announcement.md` · [↑ table of contents](#table-of-contents)# New: Smaller Trades, Multi-Hop Swaps, Pump Coins as Quote Mints, Fees Kept on the Curve-- **Smaller trade instructions.** `buy_v3`, `sell_v3` and `buy_exact_quote_in_v3` on the bonding curve, and `buy_v2`, `sell_v2` and `buy_exact_quote_in_v2` on PumpSwap, do the same trades with 17 accounts, so more fits in one transaction. Same prices, same fees. All existing trade instructions keep working. [Bonding curve v3](#sec-592) · [PumpSwap v2](#sec-589)-- **Multi-hop swap.** One PumpSwap instruction, `multi_hop_swap`, trades through two or more pools and bonding curves in a row, for example SOL → coin A → coin B, with no token account for the middle coin. [Multi-hop swap](#sec-588)-- **Any pump coin as a quote mint.** `create_v2` can pair a new coin with an existing pump coin. You pass the quote coin's bonding curve (and its pool, if it has migrated) as extra remaining accounts. [Creating a coin paired with a pump coin](#sec-586)-- **Fees stay on the curve and pool.** The new trades keep the protocol fee and the creator fee on the bonding curve or in the pool instead of paying them out on every trade. Anyone can pay them out with the permissionless `sweep_protocol_fee` / `sweep_creator_fee` instructions. Creators, CTOs and fee sharing must sweep the creator fee first. [Fee sweeps](#sec-591)-- **Why `virtual_quote_reserves` goes negative.** Fees kept in a pool are subtracted from `virtual_quote_reserves`, so the price does not count them. If you already handle it as a signed value, this is not a breaking change for your quotes, and all existing trade instructions work the same way. [Virtual quote reserves and fees](#sec-581)-- **Synthetic migration: the last buy on the curve has no max size.** With the v3 buys, the buy that empties the bonding curve can ask for more than what is left. It buys the rest from the tokens that would have gone into the PumpSwap pool, at that pool's price, and the pool later opens where that buy stopped. Only the buy that crosses the limit gets this; after it, no buys or sells are possible on the curve until the migration happens. [Synthetic migration](#sec-580)+- **Smaller trade instructions.** `buy_v3`, `sell_v3` and `buy_exact_quote_in_v3` on the bonding curve, and `buy_v2`, `sell_v2` and `buy_exact_quote_in_v2` on PumpSwap, do the same trades with 17 accounts, so more fits in one transaction. Same prices, same fees. All existing trade instructions keep working. [Bonding curve v3](#sec-599) · [PumpSwap v2](#sec-596)+- **Multi-hop swap.** One PumpSwap instruction, `multi_hop_swap`, trades through two or more pools and bonding curves in a row, for example SOL → coin A → coin B, with no token account for the middle coin. [Multi-hop swap](#sec-595)+- **Any pump coin as a quote mint.** `create_v2` can pair a new coin with an existing pump coin. You pass the quote coin's bonding curve (and its pool, if it has migrated) as extra remaining accounts. [Creating a coin paired with a pump coin](#sec-593)+- **Fees stay on the curve and pool.** The new trades keep the protocol fee and the creator fee on the bonding curve or in the pool instead of paying them out on every trade. Anyone can pay them out with the permissionless `sweep_protocol_fee` / `sweep_creator_fee` instructions. Creators, CTOs and fee sharing must sweep the creator fee first. [Fee sweeps](#sec-598)+- **Why `virtual_quote_reserves` goes negative.** Fees kept in a pool are subtracted from `virtual_quote_reserves`, so the price does not count them. If you already handle it as a signed value, this is not a breaking change for your quotes, and all existing trade instructions work the same way. [Virtual quote reserves and fees](#sec-588)+- **Synthetic migration: the last buy on the curve has no max size.** With the v3 buys, the buy that empties the bonding curve can ask for more than what is left. It buys the rest from the tokens that would have gone into the PumpSwap pool, at that pool's price, and the pool later opens where that buy stopped. Only the buy that crosses the limit gets this; after it, no buys or sells are possible on the curve until the migration happens. [Synthetic migration](#sec-587)The IDLs and TypeScript types in [idl](pumpfun-program/idl) are updated with all of the above. SDK support: `@pump-fun/pump-sdk` 4.0.0, `@pump-fun/pump-swap-sdk` 2.1.0 and `pump-rust-client` 0.4.0, see [SDKs](#sdks).@@ -131665,7 +132145,7 @@ These releases include builders for everything in the new section at the top: v3----<a id="sec-567"></a>+<a id="sec-574"></a>> **Source:** `docs/pumpfun-program/docs/BREAKING_FEE_RECIPIENT.md` · [↑ table of contents](#table-of-contents)@@ -131739,7 +132219,7 @@ The new accounts can be passed before the program upgrade happens on Monday. The----<a id="sec-568"></a>+<a id="sec-575"></a>> **Source:** `docs/pumpfun-program/docs/CPI_README.md` · [↑ table of contents](#table-of-contents)@@ -131843,7 +132323,7 @@ pump-rust-client = { version = "...", path = "..." }----<a id="sec-569"></a>+<a id="sec-576"></a>> **Source:** `docs/pumpfun-program/docs/FAQ.md` · [↑ table of contents](#table-of-contents)@@ -131897,7 +132377,7 @@ is recommended to use a static big enough CU limit like `100_000`.----<a id="sec-570"></a>+<a id="sec-577"></a>> **Source:** `docs/pumpfun-program/docs/FEE_PROGRAM_README.md` · [↑ table of contents](#table-of-contents)@@ -132112,7 +132592,7 @@ If you implement the fee logic correctly, any future change to the fee tiers str----<a id="sec-571"></a>+<a id="sec-578"></a>> **Source:** `docs/pumpfun-program/docs/FEE_RECIPIENTS.md` · [↑ table of contents](#table-of-contents)@@ -132175,7 +132655,7 @@ Use one of these as `buybackFeeRecipient` for any coin.----<a id="sec-572"></a>+<a id="sec-579"></a>> **Source:** `docs/pumpfun-program/docs/HOLDER_REWARDS_README.md` · [↑ table of contents](#table-of-contents)@@ -132296,7 +132776,7 @@ Existing cashback coins are not affected:- trading them works exactly as before, and their creator fee is still routed to the buyer as cashback;- cashback that has already accrued stays claimable with `claim_cashback` / `claim_cashback_v2`, see- [CLAIM_CASHBACK.md](#sec-583).+ [CLAIM_CASHBACK.md](#sec-590).## Community takeovers and creator fee changes@@ -132315,7 +132795,7 @@ The IDLs in the [idl](pumpfun-program/idl) directory are updated with the new ar----<a id="sec-573"></a>+<a id="sec-580"></a>> **Source:** `docs/pumpfun-program/docs/NEGATIVE_VIRTUAL_QUOTE_RESERVES.md` · [↑ table of contents](#table-of-contents)@@ -132323,7 +132803,7 @@ The IDLs in the [idl](pumpfun-program/idl) directory are updated with the new arStarting **September 30**, `Pool::virtual_quote_reserves` on PumpSwap pools can be **negative**.-Why it goes negative: the PumpSwap v2 trades keep the protocol and creator fee inside the pool's quote vault and subtract that amount from `virtual_quote_reserves`, so the waiting fees do not count as liquidity. See [Virtual quote reserves and fees](#sec-581). If you already handle a negative value, nothing changes for your quotes.+Why it goes negative: the PumpSwap v2 trades keep the protocol and creator fee inside the pool's quote vault and subtract that amount from `virtual_quote_reserves`, so the waiting fees do not count as liquidity. See [Virtual quote reserves and fees](#sec-588). If you already handle a negative value, nothing changes for your quotes.The field is an `i128`, so treat it as a signed value everywhere and never read it as a `u64` / `u128`. A positive valueputs `effective_quote_reserves` above `pool_quote_token_account.amount`; a negative value puts it below. In both cases@@ -132389,7 +132869,7 @@ let quote_out = sell_quote(base_reserves, effective_quote_reserves, base_in);----<a id="sec-574"></a>+<a id="sec-581"></a>> **Source:** `docs/pumpfun-program/docs/PUMP_CASHBACK_README.md` · [↑ table of contents](#table-of-contents)@@ -132397,7 +132877,7 @@ let quote_out = sell_quote(base_reserves, effective_quote_reserves, base_in);> cashback coins can be created. Existing cashback coins are not affected: they trade exactly as described below, their> creator fee is still routed to the buyer, and accrued cashback stays claimable with `claim_cashback` /> `claim_cashback_v2`. New coins that want to reward their community should be created as-> [holder rewards coins](#sec-572) instead.+> [holder rewards coins](#sec-579) instead.## Overview@@ -132512,7 +132992,7 @@ To read unclaimed cashback for pump swap / Pump AMM program:----<a id="sec-575"></a>+<a id="sec-582"></a>> **Source:** `docs/pumpfun-program/docs/PUMP_CREATOR_FEE_README.md` · [↑ table of contents](#table-of-contents)@@ -132647,7 +133127,7 @@ we update the programs on Mainnet.----<a id="sec-576"></a>+<a id="sec-583"></a>> **Source:** `docs/pumpfun-program/docs/PUMP_PROGRAM_README.md` · [↑ table of contents](#table-of-contents)@@ -132813,16 +133293,16 @@ Fields appended to `BondingCurve` by later upgrades (accounts written before a fmissing trailing fields as `0` / `false` / `Pubkey::default()`):- `creator` (`pubkey`): the address the coin's creator fees accrue to, see- [PUMP_CREATOR_FEE_README.md](#sec-575).+ [PUMP_CREATOR_FEE_README.md](#sec-582).- `is_mayhem_mode` (`bool`): whether the coin is a mayhem coin.- `is_cashback_coin` (`bool`): whether the coin routes its creator fee to buyers as cashback. Cashback mode is- deprecated and no new cashback coins can be created, see [PUMP_CASHBACK_README.md](#sec-574).+ deprecated and no new cashback coins can be created, see [PUMP_CASHBACK_README.md](#sec-581).- `quote_mint` (`pubkey`): the coin's quote asset; `Pubkey::default()` for SOL-paired coins.- `creator_fee_bps` (`u64`): the coin's own creator fee rate for coins on a custom pair (a quote asset other than SOL orUSDC). `0` means the standard fee schedule applies, which is always the case for SOL- and USDC-paired coins. Contactthe CTO team to change it.- `can_edit_creator_fee` (`bool`): reserved, always `false`.-- `is_holder_reward` (`bool`): whether the coin is a [holder rewards coin](#sec-572) whose creator fee+- `is_holder_reward` (`bool`): whether the coin is a [holder rewards coin](#sec-579) whose creator feeis set aside for its holders instead of a creator wallet. Trading is unchanged; `TradeEvent` additionally reports thefee in `holder_rewards_bps` / `holder_rewards` on such coins.@@ -132865,7 +133345,7 @@ missing trailing fields as `0` / `false` / `Pubkey::default()`):----<a id="sec-577"></a>+<a id="sec-584"></a>> **Source:** `docs/pumpfun-program/docs/PUMP_SWAP_CREATOR_FEE_README.md` · [↑ table of contents](#table-of-contents)@@ -132974,7 +133454,7 @@ PumpSwap program on Mainnet to the coin creator fee update.----<a id="sec-578"></a>+<a id="sec-585"></a>> **Source:** `docs/pumpfun-program/docs/PUMP_SWAP_README.md` · [↑ table of contents](#table-of-contents)@@ -133120,11 +133600,11 @@ at https://solscan.io/account/GseMAnNDvntR5uFePZ51yZBXzNSn7GdFPkfHwfr6d77J#accouof the `lp_mint`. This way, the pool differentiates between `lp_mint` tokens burnt by users directly and those burntby the `withdraw` instruction.- The `coin_creator` is the pubkey that accrues the coin-creator fees for this pool (see- [PUMP_SWAP_CREATOR_FEE_README](#sec-577)). On pools that predate coin-creator fees it is+ [PUMP_SWAP_CREATOR_FEE_README](#sec-584)). On pools that predate coin-creator fees it is`Pubkey::default()` (`11111111111111111111111111111111`).- The `is_mayhem_mode` flag indicates whether the pool operates in mayhem mode.- The `is_cashback_coin` flag indicates whether the coin's creator fee is routed as cashback (see- [PUMP_CASHBACK_README](#sec-574)).+ [PUMP_CASHBACK_README](#sec-581)).- The `virtual_quote_reserves` (`i128`) is an additional (appended) quote-reserve amount that a pool may carry. Quotes must becomputed against the pool's **effective quote reserves**, not the raw quote-vault token balance, see[Quoting: effective quote reserves](#quoting-effective-quote-reserves). It is `0` on all pools today, so effective@@ -133134,7 +133614,7 @@ at https://solscan.io/account/GseMAnNDvntR5uFePZ51yZBXzNSn7GdFPkfHwfr6d77J#accoualways the case for SOL- and USDC-paired coins. Contact the CTO team to change it.- The `can_edit_creator_fee` (`bool`, appended) is reserved and always `false`.- The `is_holder_reward` (`bool`, appended) flag indicates whether the coin is a- [holder rewards coin](#sec-572): its creator fee is set aside for the coin's holders instead of a+ [holder rewards coin](#sec-579): its creator fee is set aside for the coin's holders instead of acreator wallet. Trading is unchanged; `BuyEvent` / `SellEvent` additionally report the fee in`holder_rewards_bps` / `holder_rewards` on such pools.- Pools written before an appended field existed are shorter than the current layout; read the missing trailing fields@@ -133263,7 +133743,7 @@ Each Anchor instruction has a set of corresponding autocomplete methods that can----<a id="sec-579"></a>+<a id="sec-586"></a>> **Source:** `docs/pumpfun-program/docs/PUMP_SWAP_SDK_README.md` · [↑ table of contents](#table-of-contents)@@ -133343,7 +133823,7 @@ to autocomplete the `base` and `quote` displayed amounts based on the `lpToken`----<a id="sec-580"></a>+<a id="sec-587"></a>> **Source:** `docs/pumpfun-program/docs/SYNTHETIC_MIGRATION.md` · [↑ table of contents](#table-of-contents)@@ -133351,7 +133831,7 @@ to autocomplete the `base` and `quote` displayed amounts based on the `lpToken`Before, a buy could never take more than what the bonding curve had left. If you wanted more, you bought what was left, waited for the migration, and bought the rest on PumpSwap.-Now, with the v3 buys ([`buy_v3` and `buy_exact_quote_in_v3`](#sec-592)) and with a bonding curve hop of [`multi_hop_swap`](#sec-588), **the buy that empties the curve has no max size**. It takes what is left on the curve at the curve's price, completes the curve, and then buys the rest **from the tokens that would have gone into the PumpSwap pool**, at the price that pool would charge. We call this a synthetic migration: the buy trades against the pool before the pool exists.+Now, with the v3 buys ([`buy_v3` and `buy_exact_quote_in_v3`](#sec-599)) and with a bonding curve hop of [`multi_hop_swap`](#sec-595), **the buy that empties the curve has no max size**. It takes what is left on the curve at the curve's price, completes the curve, and then buys the rest **from the tokens that would have gone into the PumpSwap pool**, at the price that pool would charge. We call this a synthetic migration: the buy trades against the pool before the pool exists.## How it works@@ -133359,7 +133839,7 @@ Now, with the v3 buys ([`buy_v3` and `buy_exact_quote_in_v3`](#sec-592)) and wit2. **Pool part.** The program works out the reserves the migration would deposit right after step 1: all the base tokens still in the curve's token account, and all the quote raised (minus the migration fee for SOL-paired coins). It then prices the rest of the buy on those reserves with the same constant-product formula PumpSwap uses. So the price is continuous: a token costs the same in this buy as it would right after the migration.3. **Migration.** `migrate_v2` creates the pool with exactly the reserves the buy left behind. The pool opens at the price where the buy stopped.-Both parts pay the bonding curve fee schedule, not the pool's fees. The protocol and creator fee stay on the curve, as on every v3 trade (see [Fee sweeps](#sec-591)), and the buyback part is paid in the trade. So the total you pay differs from a real PumpSwap buy only by the fee rule.+Both parts pay the bonding curve fee schedule, not the pool's fees. The protocol and creator fee stay on the curve, as on every v3 trade (see [Fee sweeps](#sec-598)), and the buyback part is paid in the trade. So the total you pay differs from a real PumpSwap buy only by the fee rule.## Rules@@ -133402,19 +133882,19 @@ For indexers: the buyer's total is the `TradeEvent` amounts plus the `PostComple----<a id="sec-581"></a>+<a id="sec-588"></a>> **Source:** `docs/pumpfun-program/docs/VIRTUAL_QUOTE_RESERVES_FEE_ADJUSTMENT.md` · [↑ table of contents](#table-of-contents)# Virtual Quote Reserves and Fees Kept in the Pool-This explains **why** `Pool::virtual_quote_reserves` goes negative (see [Negative virtual quote reserves](#sec-573)) and what it means for integrations.+This explains **why** `Pool::virtual_quote_reserves` goes negative (see [Negative virtual quote reserves](#sec-580)) and what it means for integrations.**If you already treat `virtual_quote_reserves` as a signed number and price against the effective quote reserves, this is not a breaking change. Your quotes stay correct and nothing needs to change. All existing trade instructions keep working the same way, with the same accounts and arguments.**## What happens-The PumpSwap v2 trades (`buy_v2`, `buy_exact_quote_in_v2`, `sell_v2`) and `multi_hop_swap` keep the protocol fee and the creator fee **inside the pool's quote vault** instead of paying them out on every trade (see [Fee sweeps](#sec-591)). That money is not liquidity. It must not change the price.+The PumpSwap v2 trades (`buy_v2`, `buy_exact_quote_in_v2`, `sell_v2`) and `multi_hop_swap` keep the protocol fee and the creator fee **inside the pool's quote vault** instead of paying them out on every trade (see [Fee sweeps](#sec-598)). That money is not liquidity. It must not change the price.So every time a fee is kept, the program subtracts it from `virtual_quote_reserves`. Every time a sweep pays it out, the program adds it back. The quote vault balance and `virtual_quote_reserves` move in opposite directions by the same amount, and their sum stays the real liquidity:@@ -133449,11 +133929,11 @@ The effective quote reserves never counted the waiting fees, so the price is the- **Boost:** a pool is boosted when `virtual_quote_reserves + protocol_fees + creator_fees` is not `0`, not when the stored field alone is not `0`. `BuyEvent` / `SellEvent` carry this as `can_boost`.- **Indexers:** the trade events report `virtual_quote_reserves` (signed), `protocol_fee`, `coin_creator_fee` and `creator_fee_unclaimed`. `SweepPoolFeeEvent` reports each payout. `Pool.protocol_fees` and `Pool.creator_fees` are appended fields; read them as `0` on pools written before the upgrade.-The guarantees from [Negative virtual quote reserves](#sec-573) still hold: `pool_quote_token_account.amount + virtual_quote_reserves` never overflows and is never negative.+The guarantees from [Negative virtual quote reserves](#sec-580) still hold: `pool_quote_token_account.amount + virtual_quote_reserves` never overflows and is never negative.----<a id="sec-582"></a>+<a id="sec-589"></a>> **Source:** `docs/pumpfun-program/docs/instructions/BUY.md` · [↑ table of contents](#table-of-contents)@@ -133461,7 +133941,7 @@ The guarantees from [Negative virtual quote reserves](#sec-573) still hold: `pooThe `buy_v2` instruction buys base tokens from a bonding curve using the curve's quote mint. Unlike the legacy `buy` instruction, all accounts are passed through a single unified interface for both SOL-paired and non-SOL-paired coins.-> **New, smaller version:** `buy_v3` and `buy_exact_quote_in_v3` do the same buy with 17 accounts instead of 27. Same price, same fees; the protocol and creator fee stay on the curve until they are swept. See [Bonding Curve Trades V3](#sec-592). For pools after migration see [PumpSwap Trades V2](#sec-589), and to buy a coin paired with another pump coin straight from SOL or USDC see [Multi-hop swap](#sec-588). `buy_v2` keeps working unchanged.+> **New, smaller version:** `buy_v3` and `buy_exact_quote_in_v3` do the same buy with 17 accounts instead of 27. Same price, same fees; the protocol and creator fee stay on the curve until they are swept. See [Bonding Curve Trades V3](#sec-599). For pools after migration see [PumpSwap Trades V2](#sec-596), and to buy a coin paired with another pump coin straight from SOL or USDC see [Multi-hop swap](#sec-595). `buy_v2` keeps working unchanged.## Accounts@@ -133516,7 +133996,7 @@ All `buy_v2` calls need a `feeRecipient` and a `buybackFeeRecipient`.- For mayhem mode coins, choose one of the 8 reserved fee recipients as `feeRecipient`.- For all coins, choose one of the 8 buyback fee recipients as `buybackFeeRecipient`.-See [Fee Recipients](#sec-571) for the full address lists.+See [Fee Recipients](#sec-578) for the full address lists.## TS SDK@@ -133633,14 +134113,14 @@ ixs.extend(----<a id="sec-583"></a>+<a id="sec-590"></a>> **Source:** `docs/pumpfun-program/docs/instructions/CLAIM_CASHBACK.md` · [↑ table of contents](#table-of-contents)# Claim Cashback> **Note:** Cashback mode is deprecated and no new cashback coins can be created (see-> [PUMP_CASHBACK_README.md](#sec-574)). Cashback accrued on existing cashback coins stays claimable+> [PUMP_CASHBACK_README.md](#sec-581)). Cashback accrued on existing cashback coins stays claimable> with the instruction below, and those coins keep accruing it on every trade.The `claim_cashback_v2` instruction claims cashback accrued in a user's volume accumulator. It supports both legacy SOL cashback and non-SOL quote mint cashback through the same interface. The instruction is permissionless: `user` is the cashback recipient, but does not need to sign the transaction.@@ -133747,7 +134227,7 @@ let ix = sdk.claim_cashback_v2_instruction(----<a id="sec-584"></a>+<a id="sec-591"></a>> **Source:** `docs/pumpfun-program/docs/instructions/COIN_CREATION.md` · [↑ table of contents](#table-of-contents)@@ -133795,7 +134275,7 @@ The `create_v2` instruction takes the following instruction data arguments.| 5 | `is_mayhem_mode` | `bool` | Enables mayhem mode for the coin. | No || 6 | `is_cashback_enabled` | `OptionBool` | **Deprecated.** Must be `[false]` or omitted: cashback coins can no longer be created and the instruction fails on `[true]`. Existing cashback coins are unaffected. | Yes || 7 | `creator_fee_bps` | `OptionU64` | Creator fee rate for coins on a custom pair (a quote asset other than SOL or USDC). Omitted or `0` means the standard fee schedule; on SOL- and USDC-paired coins the value is ignored and the schedule always applies. Contact the CTO team to change the rate of an existing coin. | Yes |-| 8 | `is_holder_reward` | `OptionBool` | `[true]` creates a [holder rewards coin](#sec-572): the creator fee of every trade is set aside for the coin's holders instead of a creator wallet, and `creator` is not used as the fee recipient. Permanent. Omitted or `[false]` creates a regular coin. | Yes |+| 8 | `is_holder_reward` | `OptionBool` | `[true]` creates a [holder rewards coin](#sec-579): the creator fee of every trade is set aside for the coin's holders instead of a creator wallet, and `creator` is not used as the fee recipient. Permanent. Omitted or `[false]` creates a regular coin. | Yes |The trailing optional arguments (6-8) may be left off the end of the instruction data; a missing argument reads as `false` / `0`.@@ -133826,7 +134306,7 @@ const createInstruction = await PUMP_SDK.createV2Instruction({### Holder Rewards MintPass `holderReward: true` to create a coin whose creator fee goes to its holders. See-[HOLDER_REWARDS_README.md](#sec-572) for what this means and how to read the new fields.+[HOLDER_REWARDS_README.md](#sec-579) for what this means and how to read the new fields.```tsimport { PUMP_SDK } from "@pump-fun/pump-sdk";@@ -133930,11 +134410,11 @@ let ixs = sdk`create_v2` can also pair a new coin with an existing pump coin instead of SOL or USDC. The 16 accounts and the arguments above stay the same. Only the remaining accounts change: after the three quote accounts (17 to 19) you also pass the `quote_control` PDA, the quote coin's bonding curve, and the quote coin's PumpSwap pool and vaults if it has migrated. The new coin's starting reserves are computed from the quote coin's current reserves, so it raises about as much as a normal launch, counted in the quote coin.-See [Creating a coin paired with a pump coin](#sec-586) for the account list, the rules on which coins can be a quote, and how to trade the new coin.+See [Creating a coin paired with a pump coin](#sec-593) for the account list, the rules on which coins can be a quote, and how to trade the new coin.----<a id="sec-585"></a>+<a id="sec-592"></a>> **Source:** `docs/pumpfun-program/docs/instructions/COLLECT_CREATOR_FEE.md` · [↑ table of contents](#table-of-contents)@@ -134036,13 +134516,13 @@ ixs.extend(sdk.collect_creator_fee_v2_instructions(----<a id="sec-586"></a>+<a id="sec-593"></a>> **Source:** `docs/pumpfun-program/docs/instructions/CREATE_WITH_PUMP_COIN_QUOTE.md` · [↑ table of contents](#table-of-contents)# Creating a Coin Paired With a Pump Coin-`create_v2` can pair a new coin with an **existing pump coin** instead of SOL or USDC. The 16 accounts and the arguments are the same as in [Coin Creation](#sec-584). What changes is the list of remaining accounts: you also pass the quote coin's bonding curve, and its PumpSwap pool if it has migrated.+`create_v2` can pair a new coin with an **existing pump coin** instead of SOL or USDC. The 16 accounts and the arguments are the same as in [Coin Creation](#sec-591). What changes is the list of remaining accounts: you also pass the quote coin's bonding curve, and its PumpSwap pool if it has migrated.Below, **Q** is the pump coin you want to use as the quote mint.@@ -134052,7 +134532,7 @@ Below, **Q** is the pump coin you want to use as the quote mint.- Q must not be a mayhem-mode coin.- Q can still be on its bonding curve, or already migrated to PumpSwap. If Q's curve is complete but the pool is not created yet, creation fails with `QuoteCurveAwaitingMigration` (6107). Retry after `migrate_v2` runs.- The new coin cannot be in mayhem mode (`MayhemModeQuoteMintNotAllowed`, 6071). Holder rewards work, and `creator_fee_bps` can be set, like on other custom pairs.-- If Q is listed by pump.fun as a quote mint, it works the normal way (see [Coin Creation](#sec-584)) and the extra accounts below are not read.+- If Q is listed by pump.fun as a quote mint, it works the normal way (see [Coin Creation](#sec-591)) and the extra accounts below are not read.## Remaining accounts@@ -134081,9 +134561,9 @@ Because the amount is priced through Q's curve, not at Q's spot price, the new c## Trading the new coin-- Use [`buy_v3` / `sell_v3`](#sec-592) or [`buy_v2` / `sell_v2`](#sec-582) with `quote_mint` = Q and `quote_token_program` = Q's token program. The user needs a token account for Q.+- Use [`buy_v3` / `sell_v3`](#sec-599) or [`buy_v2` / `sell_v2`](#sec-589) with `quote_mint` = Q and `quote_token_program` = Q's token program. The user needs a token account for Q.- For the v3 trades, `buyback_fee_recipient` is a buyback fee recipient wallet's associated token account for Q. It may not exist yet for a new quote coin. Add a `createAssociatedTokenAccountIdempotent` instruction for it before the trade; anyone can pay the rent.-- To buy the new coin straight from SOL or USDC, use [`multi_hop_swap`](#sec-588): Q's bonding curve or PumpSwap pool is the first hop and the new coin's bonding curve is the second.+- To buy the new coin straight from SOL or USDC, use [`multi_hop_swap`](#sec-595): Q's bonding curve or PumpSwap pool is the first hop and the new coin's bonding curve is the second.## Errors@@ -134108,17 +134588,17 @@ Because the amount is priced through Q's curve, not at Q's spot price, the new c## Synthetic Migration-A coin paired with a pump coin completes its curve like any other coin: the v3 buy that crosses the limit can also buy from the tokens that would go into its PumpSwap pool, at that pool's price, and the pool later opens where that buy stopped. No migration fee is taken from a token-paired coin's raised quote in that pricing. See [Synthetic migration](#sec-580).+A coin paired with a pump coin completes its curve like any other coin: the v3 buy that crosses the limit can also buy from the tokens that would go into its PumpSwap pool, at that pool's price, and the pool later opens where that buy stopped. No migration fee is taken from a token-paired coin's raised quote in that pricing. See [Synthetic migration](#sec-587).----<a id="sec-587"></a>+<a id="sec-594"></a>> **Source:** `docs/pumpfun-program/docs/instructions/CREATOR_FEE_SHARING.md` · [↑ table of contents](#table-of-contents)# Creator Fee Sharing-> **Note:** These instructions only apply to coins that **have** a `sharing_config` - i.e. coins whose creator vault has been migrated to the Pump Fees program for multi-recipient distribution. For single-creator-recipient coins (no `sharing_config`), use [`collect_creator_fee_v2` / `collect_coin_creator_fee`](#sec-585) instead.+> **Note:** These instructions only apply to coins that **have** a `sharing_config` - i.e. coins whose creator vault has been migrated to the Pump Fees program for multi-recipient distribution. For single-creator-recipient coins (no `sharing_config`), use [`collect_creator_fee_v2` / `collect_coin_creator_fee`](#sec-592) instead.The lifecycle is:@@ -134466,7 +134946,7 @@ ixs.extend(sdk.distribute_creator_fees_v2_instructions(----<a id="sec-588"></a>+<a id="sec-595"></a>> **Source:** `docs/pumpfun-program/docs/instructions/MULTI_HOP_SWAP.md` · [↑ table of contents](#table-of-contents)@@ -134584,7 +135064,7 @@ Fees are charged **once per route**:- Every other hop charges nothing.- A one-hop route pays exactly what a `buy_v2` / `sell_v2` (PumpSwap) or `buy_v3` / `sell_v3` (bonding curve) pays.-The protocol and creator fees stay in the pool or curve that charged them and are paid out later by the sweep instructions. See [Fee sweeps](#sec-591).+The protocol and creator fees stay in the pool or curve that charged them and are paid out later by the sweep instructions. See [Fee sweeps](#sec-598).## Events@@ -134596,8 +135076,8 @@ The Pump program has a matching `multi_hop_curve_swap` instruction. It is only f## Related-- [Bonding Curve Trades V3](#sec-592) and [PumpSwap Trades V2](#sec-589): the single-venue trades a multi-hop route is made of.-- [Creating a coin paired with a pump coin](#sec-586): how the coins that need a multi-hop route are created.+- [Bonding Curve Trades V3](#sec-599) and [PumpSwap Trades V2](#sec-596): the single-venue trades a multi-hop route is made of.+- [Creating a coin paired with a pump coin](#sec-593): how the coins that need a multi-hop route are created.## SDKs@@ -134612,17 +135092,17 @@ These releases support SOL-paired bonding curve hops too. The builders make sureA bonding curve hop that would buy more than the curve has left does not fail. It takes what is left at the curve's price, completes the curve, and spends the whole rest of its input on the tokens that would have gone into that coin's PumpSwap pool, at the price that pool would charge. The hop then emits `CompleteEvent` and `PostCompleteBuyEvent` after its `TradeEvent`. After that hop, the curve takes no more trades until its migration happens.-This works on a SOL-paired curve too: the migration fee comes off the raised SOL before the pool part is priced, exactly as `migrate_v2` would take it. Mayhem-mode curves cannot be a hop at all. See [Synthetic migration](#sec-580).+This works on a SOL-paired curve too: the migration fee comes off the raised SOL before the pool part is priced, exactly as `migrate_v2` would take it. Mayhem-mode curves cannot be a hop at all. See [Synthetic migration](#sec-587).----<a id="sec-589"></a>+<a id="sec-596"></a>> **Source:** `docs/pumpfun-program/docs/instructions/PUMP_SWAP_TRADE_V2.md` · [↑ table of contents](#table-of-contents)# PumpSwap Trades V2-PumpSwap `buy_v2`, `buy_exact_quote_in_v2` and `sell_v2` do the same trades as `buy`, `buy_exact_quote_in` and `sell`, with **17 accounts and no remaining accounts**. Prices, slippage checks and fee amounts are the same. The only difference is where the fees go: a v2 trade keeps the protocol fee and the coin creator fee in the pool instead of paying them out on every trade. See [Fee sweeps](#sec-591). The LP fee is unchanged: it goes into the pool reserves on every trade, as before.+PumpSwap `buy_v2`, `buy_exact_quote_in_v2` and `sell_v2` do the same trades as `buy`, `buy_exact_quote_in` and `sell`, with **17 accounts and no remaining accounts**. Prices, slippage checks and fee amounts are the same. The only difference is where the fees go: a v2 trade keeps the protocol fee and the coin creator fee in the pool instead of paying them out on every trade. See [Fee sweeps](#sec-598). The LP fee is unchanged: it goes into the pool reserves on every trade, as before.They work on every pool, both pump pools created by migration and permissionless pools. Mayhem pools work too. Cashback coin pools are the one exception: a v2 trade on one fails with `CashbackCoinNotSupported` (6079), so keep using the v1 instructions for those.@@ -134686,7 +135166,7 @@ All three instructions take the same 17 accounts, in this order.## Buyback Fee Recipient-The buyback part of the protocol fee is paid in the trade, to one token account: the associated token account for `quote_mint` of any of the 8 buyback fee recipient wallets listed in [Fee Recipients](#sec-571).+The buyback part of the protocol fee is paid in the trade, to one token account: the associated token account for `quote_mint` of any of the 8 buyback fee recipient wallets listed in [Fee Recipients](#sec-578).The trade checks this account on every trade, even when the fee is `0` (for example on mayhem pools), and never creates it. For wrapped SOL and USDC the token accounts already exist. For a pump coin used as quote they may not, so add a `createAssociatedTokenAccountIdempotent` instruction for it before the trade when you are not sure. Anyone can pay the rent for it.@@ -134701,7 +135181,7 @@ Nothing changes for quotes. Price against the effective quote reserves, as descreffective_quote_reserves = pool_quote_token_account.amount + Pool::virtual_quote_reserves```-The fees a v2 trade keeps in the vault are subtracted from `virtual_quote_reserves`, so this formula keeps giving the right reserves. See [Virtual quote reserves and fees](#sec-581).+The fees a v2 trade keeps in the vault are subtracted from `virtual_quote_reserves`, so this formula keeps giving the right reserves. See [Virtual quote reserves and fees](#sec-588).## Events@@ -134717,8 +135197,8 @@ The payouts show up later as `SweepPoolFeeEvent`. See [Fee sweeps](pumpfun-progr## Related-- [Bonding Curve Trades V3](#sec-592): the same change for coins still on their bonding curve.-- [Multi-hop swap](#sec-588): trade through two or more pools and curves in one instruction.+- [Bonding Curve Trades V3](#sec-599): the same change for coins still on their bonding curve.+- [Multi-hop swap](#sec-595): trade through two or more pools and curves in one instruction.## SDKs@@ -134728,11 +135208,11 @@ The payouts show up later as `SweepPoolFeeEvent`. See [Fee sweeps](pumpfun-progr## Synthetic Migration-The v3 buy that empties a bonding curve can now also buy from the tokens that would go into the PumpSwap pool, at the price that pool would charge, before the pool exists. The migration then creates the pool with exactly the reserves that buy left, so the pool opens where it stopped. Nothing changes for trading on the pool itself: the first PumpSwap trade sees a pool that is already at the right price. See [Synthetic migration](#sec-580).+The v3 buy that empties a bonding curve can now also buy from the tokens that would go into the PumpSwap pool, at the price that pool would charge, before the pool exists. The migration then creates the pool with exactly the reserves that buy left, so the pool opens where it stopped. Nothing changes for trading on the pool itself: the first PumpSwap trade sees a pool that is already at the right price. See [Synthetic migration](#sec-587).----<a id="sec-590"></a>+<a id="sec-597"></a>> **Source:** `docs/pumpfun-program/docs/instructions/SELL.md` · [↑ table of contents](#table-of-contents)@@ -134740,7 +135220,7 @@ The v3 buy that empties a bonding curve can now also buy from the tokens that woThe `sell_v2` instruction sells base tokens into a bonding curve using the curve's quote mint. Like `buy_v2`, it uses a single unified account interface for both SOL-paired and non-SOL-paired coins.-> **New, smaller version:** `sell_v3` does the same sell with 17 accounts instead of 26. Same price, same fees; the protocol and creator fee stay on the curve until they are swept. See [Bonding Curve Trades V3](#sec-592). For pools after migration see [PumpSwap Trades V2](#sec-589), and to sell a coin paired with another pump coin straight into SOL or USDC see [Multi-hop swap](#sec-588). `sell_v2` keeps working unchanged.+> **New, smaller version:** `sell_v3` does the same sell with 17 accounts instead of 26. Same price, same fees; the protocol and creator fee stay on the curve until they are swept. See [Bonding Curve Trades V3](#sec-599). For pools after migration see [PumpSwap Trades V2](#sec-596), and to sell a coin paired with another pump coin straight into SOL or USDC see [Multi-hop swap](#sec-595). `sell_v2` keeps working unchanged.## Accounts@@ -134794,7 +135274,7 @@ All `sell_v2` calls need a `feeRecipient` and a `buybackFeeRecipient`.- For mayhem mode coins, choose one of the 8 reserved fee recipients as `feeRecipient`.- For all coins, choose one of the 8 buyback fee recipients as `buybackFeeRecipient`.-See [Fee Recipients](#sec-571) for the full address lists.+See [Fee Recipients](#sec-578) for the full address lists.## TS SDK@@ -134911,13 +135391,13 @@ ixs.extend(----<a id="sec-591"></a>+<a id="sec-598"></a>> **Source:** `docs/pumpfun-program/docs/instructions/SWEEP_FEES.md` · [↑ table of contents](#table-of-contents)# Fees Kept on the Curve and Pool, and How to Sweep Them-The new trade instructions ([`buy_v3` / `sell_v3`](#sec-592) on the bonding curve, [`buy_v2` / `sell_v2`](#sec-589) on PumpSwap, and [`multi_hop_swap`](#sec-588)) **do not pay the protocol fee and the creator fee out on every trade**. They keep the money where the trade happened and write down how much is waiting. Anyone can pay it out later with a sweep instruction.+The new trade instructions ([`buy_v3` / `sell_v3`](#sec-599) on the bonding curve, [`buy_v2` / `sell_v2`](#sec-596) on PumpSwap, and [`multi_hop_swap`](#sec-595)) **do not pay the protocol fee and the creator fee out on every trade**. They keep the money where the trade happened and write down how much is waiting. Anyone can pay it out later with a sweep instruction.| Where the trade happened | Protocol fee waits in | Creator fee waits in | The money sits in || ------------------------ | ----------------------------- | -------------------------- | ----------------------------------------------------------------------- |@@ -134938,7 +135418,7 @@ Four permissionless instructions pay the waiting fees out. Anyone can call them;| Program | Instruction | Pays out | To (`recipient`) || -------- | -------------------- | ---------------------------- | ------------------------------------------------------------------------------------------------------------------ |-| Pump | `sweep_protocol_fee` | `BondingCurve.protocol_fees` | One of the 8 normal fee recipients, or one of the 8 reserved fee recipients for a mayhem coin. See [Fee Recipients](#sec-571). |+| Pump | `sweep_protocol_fee` | `BondingCurve.protocol_fees` | One of the 8 normal fee recipients, or one of the 8 reserved fee recipients for a mayhem coin. See [Fee Recipients](#sec-578). || Pump | `sweep_creator_fee` | `BondingCurve.creator_fee` | The creator vault of `bonding_curve.creator`: Pump PDA `[b"creator-vault", bonding_curve.creator]`. || PumpSwap | `sweep_protocol_fee` | `Pool.protocol_fees` | One of the 8 protocol fee recipients, or a reserved one for a mayhem pool. Same addresses as above. || PumpSwap | `sweep_creator_fee` | `Pool.creator_fees` | The coin creator vault authority of `pool.coin_creator`: PumpSwap PDA `[b"creator_vault", pool.coin_creator]`. |@@ -134952,11 +135432,11 @@ The destination is fixed by the instruction, so a sweep can only move the money**Creator fee.** A creator's fee is only in the creator vault after a `sweep_creator_fee`. Call it right before the existing claim or distribute instruction, in the same transaction:1. Coin with a single creator (no sharing config):- - Pump `sweep_creator_fee`, then [`collect_creator_fee_v2`](#sec-585).- - If the coin has migrated: PumpSwap `sweep_creator_fee`, then [`collect_coin_creator_fee`](#sec-585).-2. Coin with a sharing config ([Creator Fee Sharing](#sec-587)):+ - Pump `sweep_creator_fee`, then [`collect_creator_fee_v2`](#sec-592).+ - If the coin has migrated: PumpSwap `sweep_creator_fee`, then [`collect_coin_creator_fee`](#sec-592).+2. Coin with a sharing config ([Creator Fee Sharing](#sec-594)):- Pump `sweep_creator_fee` (and PumpSwap `sweep_creator_fee` if migrated), then `transfer_creator_fees_to_pump_v2` and `distribute_creator_fees_v2`.-3. Holder rewards coins: the same two sweeps. The creator fee lands in the holder rewards vault, and the usual [holder rewards](#sec-572) flow pays it out.+3. Holder rewards coins: the same two sweeps. The creator fee lands in the holder rewards vault, and the usual [holder rewards](#sec-579) flow pays it out.These instructions refuse to run while a creator fee is still waiting, so a creator fee sweep must come first in the same transaction:@@ -135029,8 +135509,8 @@ For indexers: fee income is in the trade events (when it is charged), payouts ar## Related-- [Virtual quote reserves and fees](#sec-581): why the fees kept in a pool make `virtual_quote_reserves` negative.-- [Collect creator fee](#sec-585) and [Creator fee sharing](#sec-587): the claim and distribute instructions a sweep comes before.+- [Virtual quote reserves and fees](#sec-588): why the fees kept in a pool make `virtual_quote_reserves` negative.+- [Collect creator fee](#sec-592) and [Creator fee sharing](#sec-594): the claim and distribute instructions a sweep comes before.## SDKs@@ -135041,17 +135521,17 @@ For indexers: fee income is in the trade events (when it is charged), payouts ar## Synthetic Migration-The buy that empties a bonding curve can continue into the tokens that would go into the PumpSwap pool (see [Synthetic migration](#sec-580)). That second part pays the bonding curve fee schedule like the first part: its protocol and creator fee are kept on the curve in the same `protocol_fees` / `creator_fee` fields and are paid out by the same sweeps, and its buyback part is paid in the trade. `PostCompleteBuyEvent` reports those amounts.+The buy that empties a bonding curve can continue into the tokens that would go into the PumpSwap pool (see [Synthetic migration](#sec-587)). That second part pays the bonding curve fee schedule like the first part: its protocol and creator fee are kept on the curve in the same `protocol_fees` / `creator_fee` fields and are paid out by the same sweeps, and its buyback part is paid in the trade. `PostCompleteBuyEvent` reports those amounts.----<a id="sec-592"></a>+<a id="sec-599"></a>> **Source:** `docs/pumpfun-program/docs/instructions/TRADE_V3.md` · [↑ table of contents](#table-of-contents)# Bonding Curve Trades V3-`buy_v3`, `buy_exact_quote_in_v3` and `sell_v3` do the same trades as `buy_v2`, `buy_exact_quote_in_v2` and `sell_v2`, with **17 accounts instead of 27 or 26**. Prices, slippage checks and fee amounts are the same. The only difference is where the fees go: a v3 trade keeps the protocol fee and the creator fee on the bonding curve instead of paying them out on every trade. See [Fee sweeps](#sec-591).+`buy_v3`, `buy_exact_quote_in_v3` and `sell_v3` do the same trades as `buy_v2`, `buy_exact_quote_in_v2` and `sell_v2`, with **17 accounts instead of 27 or 26**. Prices, slippage checks and fee amounts are the same. The only difference is where the fees go: a v3 trade keeps the protocol fee and the creator fee on the bonding curve instead of paying them out on every trade. See [Fee sweeps](#sec-598).Use them for any coin paired with SOL, USDC or a pump coin. Mayhem coins work too. Cashback coins are the one exception: a v3 trade on a cashback coin fails with `CashbackCoinNotSupported` (6094), so keep using v2 for those.@@ -135117,7 +135597,7 @@ All three instructions take the same 17 accounts, in this order.## Buyback Fee Recipient-The buyback part of the protocol fee is paid in the trade, to one account. Pick any of the 8 buyback fee recipient wallets listed in [Fee Recipients](#sec-571).+The buyback part of the protocol fee is paid in the trade, to one account. Pick any of the 8 buyback fee recipient wallets listed in [Fee Recipients](#sec-578).- SOL-paired coin: pass the wallet itself.- USDC-paired or pump-coin-paired coin: pass the wallet's associated token account for `quote_mint`, using `quote_token_program`.@@ -135138,9 +135618,9 @@ The payouts show up later as `SweepBondingCurveFeeEvent`. See [Fee sweeps](pumpf## Related-- [Buy V2](#sec-582) and [Sell V2](#sec-590): the previous interface, still supported.-- [PumpSwap Trades V2](#sec-589): the same change for pools after migration.-- [Multi-hop swap](#sec-588): trade through two or more pools and curves in one instruction.+- [Buy V2](#sec-589) and [Sell V2](#sec-597): the previous interface, still supported.+- [PumpSwap Trades V2](#sec-596): the same change for pools after migration.+- [Multi-hop swap](#sec-595): trade through two or more pools and curves in one instruction.## SDKs@@ -135157,11 +135637,11 @@ The buy that empties the curve has no max size. A `buy_v3` or `buy_exact_quote_i- Mayhem coins keep the old behaviour, controlled by `partial_fill`.- Three events: `TradeEvent` (curve part), `CompleteEvent`, then `PostCompleteBuyEvent` (pool part).-Full details, including how to quote it: [Synthetic migration](#sec-580).+Full details, including how to quote it: [Synthetic migration](#sec-587).----<a id="sec-593"></a>+<a id="sec-600"></a>> **Source:** `docs/quick-start.md` · [↑ table of contents](#table-of-contents)@@ -135307,7 +135787,7 @@ The `brain` attribute turns the 3D viewer into a conversational agent:| `brain` | LLM model ID. Registered Claude IDs: `claude-sonnet-5`, `claude-opus-5`, `claude-sonnet-4-6`, `claude-opus-4-8`, `claude-opus-4-7`, `claude-opus-4-6`, `claude-haiku-4-5-20251001`, `claude-fable-5`, `claude-mythos-5` (restricted access). Free models (no key, routed through the platform proxy) are also accepted, e.g. `meta-llama/llama-3.3-70b-instruct:free`. Omit for a viewer-only display with no AI (provider `none`). || `instructions` | System prompt for the agent's personality and role. || `mode` | Layout mode: `inline` (flows with page content), `floating` (fixed bubble in a corner), `fullscreen`, or `section`. Default: `inline`. |-| `sign-language` | The avatar signs every reply in ASL fingerspelling plus its sign vocabulary (any value except `off`/`false` enables it; works at boot or toggled at runtime). See the [sign language guide](#sec-641). |+| `sign-language` | The avatar signs every reply in ASL fingerspelling plus its sign vocabulary (any value except `off`/`false` enables it; works at boot or toggled at runtime). See the [sign language guide](#sec-649). |The chat input and microphone button appear automatically when `brain` is set. The agent can play animations, look at the camera, and respond to voice input.@@ -135348,7 +135828,7 @@ The fastest path to an embeddable 3D experience is an iframe widget. Build one i| `passport` | On-chain identity card backed by ERC-8004. || `hotspot-tour` | Annotated 3D scenes with clickable points of interest. |-For the full widget API including `postMessage` events, see the [Widget docs](#sec-802).+For the full widget API including `postMessage` events, see the [Widget docs](#sec-814).---@@ -135378,7 +135858,7 @@ Copy `.env.example` to `.env` and fill in:| `ANTHROPIC_API_KEY` | Required for AI chat | LLM backend. Without it, the agent falls back to pattern matching. || `VITE_PRIVY_APP_ID` | Optional | Wallet auth via [Privy](https://privy.io). Needed for on-chain identity. || `UPSTASH_REDIS_REST_URL` / `UPSTASH_REDIS_REST_TOKEN` | Optional | Distributed rate limiting. Falls back to in-memory without it. |-| `VITE_CHARACTER_STUDIO_URL` | Optional | Override for the origin hosting the [Avatar Studio](https://github.com/m3-org/CharacterStudio) avatar builder iframe. When unset, the app resolves it same-origin to `<origin>/avatar-studio` in both dev and production. Set it only to point at a standalone studio dev server (e.g. `http://localhost:5173`). See [Configuration](#sec-212). |+| `VITE_CHARACTER_STUDIO_URL` | Optional | Override for the origin hosting the [Avatar Studio](https://github.com/m3-org/CharacterStudio) avatar builder iframe. When unset, the app resolves it same-origin to `<origin>/avatar-studio` in both dev and production. Set it only to point at a standalone studio dev server (e.g. `http://localhost:5173`). See [Configuration](#sec-213). || `AVATURN_API_KEY` | Optional | Photo-to-avatar pipeline via an external photo-to-avatar provider. || `PINATA_JWT` | Optional | IPFS pinning for on-chain agent registration. |@@ -135449,15 +135929,15 @@ If you're embedding inside a sandboxed iframe, make sure the parent grants `allo## Next Steps-- [Embedding Guide](#sec-259) — deep dive on attributes, events, and the JS API-- [Widget Types](#sec-802) — full reference for iframe embeds and postMessage+- [Embedding Guide](#sec-262) — deep dive on attributes, events, and the JS API+- [Widget Types](#sec-814) — full reference for iframe embeds and postMessage- [Agent System](#sec-068) — how the brain, memory, and skills layers work-- [REST API](#sec-124) and [JavaScript API](#sec-390) — backend and in-browser surfaces-- [SDK Reference](#sec-626) — `@three-ws/sdk`, `@three-ws/agent-ui`, `@three-ws/avatar`, `@three-ws/solana-agent`+- [REST API](#sec-125) and [JavaScript API](#sec-394) — backend and in-browser surfaces+- [SDK Reference](#sec-633) — `@three-ws/sdk`, `@three-ws/agent-ui`, `@three-ws/avatar`, `@three-ws/solana-agent`----<a id="sec-594"></a>+<a id="sec-601"></a>> **Source:** `docs/radar.md` · [↑ table of contents](#table-of-contents)@@ -135473,7 +135953,7 @@ API: `/api/pump/coin-intel` (feed, market pulse, per-coin detail). The detail dr## Why it exists-The most dangerous moment on pump.fun is the first minute, when the tape is thin and a bundle of bot wallets can manufacture the look of organic demand. A human cannot audit funder graphs and timing entropy in real time. The Coin Intelligence Engine does, on the live firehose, and Radar is its screener: a scannable board that turns raw first-90-seconds behaviour into a quality score and a short list of named risks, so you can filter out the coordinated launches and focus on the ones with a real crowd. It is the top of the [trading surfaces](#sec-695) funnel: Radar surfaces a launch worth a look, you watch it, and if it earns conviction you open it in [Mission Control](#sec-675) to act.+The most dangerous moment on pump.fun is the first minute, when the tape is thin and a bundle of bot wallets can manufacture the look of organic demand. A human cannot audit funder graphs and timing entropy in real time. The Coin Intelligence Engine does, on the live firehose, and Radar is its screener: a scannable board that turns raw first-90-seconds behaviour into a quality score and a short list of named risks, so you can filter out the coordinated launches and focus on the ones with a real crowd. It is the top of the [trading surfaces](#sec-703) funnel: Radar surfaces a launch worth a look, you watch it, and if it earns conviction you open it in [Mission Control](#sec-683) to act.## How it works@@ -135503,8 +135983,8 @@ The UI colors quality as Healthy at 70 and up, Mixed from 40 to 69, and High ris3. Press `/` to focus search and type a name, ticker, or mint. Press `g` or `l` to switch grid and list, `r` to refresh.4. Click any coin for the drawer: the full signal grid, the top-50 wallet ledger, the smart-money notable roster, the outcome (if labeled), and an asynchronously injected Oracle conviction section.5. Every mainnet coin links to its full page at `/oracle/coin/<mint>`: the card's "Full intel →" button goes there directly, and the drawer carries an "Open full page →" link in its header. The full page renders in the markets-hub design (the same system as `/coin/:id`) with the live price chart, the complete Launch Intelligence read (this engine's signal grid, risk flags, and trader ledger), Oracle conviction, live market intel, agent transactions, and a live trade tape.-6. On a coin worth tracking, use Watch to add it to your [Watchlist](https://three.ws/watchlist), then open it in [Mission Control](#sec-675) to trade.-7. On a coin worth acting on now, use **[Fork](#sec-315)**. It opens the real pump.fun trade panel for that mint without leaving the page: live quote, the safety firewall's verdict, and your own browser wallet as the signer. Devnet coins have no market to buy into, so they carry no Fork button.+6. On a coin worth tracking, use Watch to add it to your [Watchlist](https://three.ws/watchlist), then open it in [Mission Control](#sec-683) to trade.+7. On a coin worth acting on now, use **[Fork](#sec-318)**. It opens the real pump.fun trade panel for that mint without leaving the page: live quote, the safety firewall's verdict, and your own browser wallet as the signer. Devnet coins have no market to buy into, so they carry no Fork button.## Examples@@ -135544,17 +136024,17 @@ console.log(clean.map((c) => `${c.symbol} q${c.quality_score}`));## Related-- [The trading surfaces: Radar, Mission Control, Live Trade Feed, Watchlist, Coin Intelligence](#sec-695)-- [Oracle: the conviction engine](#sec-467) fuses this intel into a single conviction score-- [Smart Money Radar](#sec-652) is the pedigree layer Radar surfaces inline-- [Fork a trade](#sec-315) is the one-tap buy on every Radar card, and the deep link that brings a shared coin back here-- [Mission Control](#sec-675) is where a Radar find gets traded-- [Coin pages](#sec-194) cross-link the per-mint intel and conviction views+- [The trading surfaces: Radar, Mission Control, Live Trade Feed, Watchlist, Coin Intelligence](#sec-703)+- [Oracle: the conviction engine](#sec-472) fuses this intel into a single conviction score+- [Smart Money Radar](#sec-660) is the pedigree layer Radar surfaces inline+- [Fork a trade](#sec-318) is the one-tap buy on every Radar card, and the deep link that brings a shared coin back here+- [Mission Control](#sec-683) is where a Radar find gets traded+- [Coin pages](#sec-195) cross-link the per-mint intel and conviction views- Pages: [/radar](https://three.ws/radar) · [/coin-intel](https://three.ws/coin-intel) · [/watchlist](https://three.ws/watchlist)----<a id="sec-595"></a>+<a id="sec-602"></a>> **Source:** `docs/reasoning-ledger.md` · [↑ table of contents](#table-of-contents)@@ -135644,17 +136124,17 @@ The headline score (0 to 100) is derived only from reconciled outcomes, and the## Related- [Agent Sniper](#sec-065): the pipeline that writes `snipe` entries, with a live case-study ledger-- [Custody you can verify](#sec-232): the same provable-not-promised approach applied to the wallets these decisions spend from+- [Custody you can verify](#sec-233): the same provable-not-promised approach applied to the wallets these decisions spend from----<a id="sec-596"></a>+<a id="sec-603"></a>> **Source:** `docs/recurring-payments.md` · [↑ table of contents](#table-of-contents)# Recurring payments-A recurring payment moves a fixed amount of USDC out of your wallet on a schedule you choose, without you signing anything again. You sign one ERC-7710 permission (see [Permissions & Delegation](#sec-489)), the platform's hourly cron spends inside it, and every attempt it makes is written to a ledger you can read.+A recurring payment moves a fixed amount of USDC out of your wallet on a schedule you choose, without you signing anything again. You sign one ERC-7710 permission (see [Permissions & Delegation](#sec-496)), the platform's hourly cron spends inside it, and every attempt it makes is written to a ledger you can read.Two kinds of schedule ride the same rails:@@ -135821,13 +136301,13 @@ Definitions live in [api/\_lib/schema.sql](../api/_lib/schema.sql); the lifecycl## See also-- [Permissions & Delegation](#sec-489) for granting, scoping and revoking the signed permission a schedule spends-- [Payment sessions](#sec-488) for capped one-off agent spending that is not on a schedule+- [Permissions & Delegation](#sec-496) for granting, scoping and revoking the signed permission a schedule spends+- [Payment sessions](#sec-495) for capped one-off agent spending that is not on a schedule- [Agent wallets](#sec-077) for the wallet a subscription pays into----<a id="sec-597"></a>+<a id="sec-604"></a>> **Source:** `docs/remix.md` · [↑ table of contents](#table-of-contents)@@ -136039,12 +136519,12 @@ still recorded — the royalty leg reports `payout_unconfigured` instead of payi## Related-- [3D Studio (free) MCP](#sec-414) — the `refine_model` iteration tool.+- [3D Studio (free) MCP](#sec-418) — the `refine_model` iteration tool.- [The 3D pipeline](#sec-003) — how generation itself works.----<a id="sec-598"></a>+<a id="sec-605"></a>> **Source:** `docs/reputation-staking-market.md` · [↑ table of contents](#table-of-contents)@@ -136065,7 +136545,7 @@ Live surface: [/reputation/market](/reputation/market).## What the market pays forReputation is already attested on Solana as signed SPL-Memo envelopes indexed-into `solana_attestations` (see [docs/solana-reputation](#sec-656)).+into `solana_attestations` (see [docs/solana-reputation](#sec-664)).An agent's `threews.accept.v1`, `threews.task.v1`, `threews.validation.v1`,`threews.feedback.v1`, `threews.dispute.v1`, and `threews.revoke.v1` envelopesare its attested action history: work it shipped, validations it passed or@@ -136278,15 +136758,15 @@ Failure codes (`market_not_configured`, `mainnet_gated`, `tx_not_found`,## Related-- [Docs: Agent Reputation on Solana](#sec-656): the attestation+- [Docs: Agent Reputation on Solana](#sec-664): the attestationlayer the market reads.-- [Docs: Reputation System](#sec-599): the cross-chain reputation model.+- [Docs: Reputation System](#sec-606): the cross-chain reputation model.- [Reputation Explorer](/reputation): inspect any agent's score andattestations.----<a id="sec-599"></a>+<a id="sec-606"></a>> **Source:** `docs/reputation.md` · [↑ table of contents](#table-of-contents)@@ -136521,7 +137001,7 @@ GET /api/exploreSeparate from reputation scores, glTF validation results can also be recorded on-chain via the `ValidationRegistry`. A passing validation attests that the agent's 3D model meets the glTF specification as of a specific block timestamp. Validation history is shown on the agent's profile page alongside reputation data.-See the [Validation](#sec-790) documentation for details.+See the [Validation](#sec-799) documentation for details.---@@ -136534,7 +137014,7 @@ See the [Validation](#sec-790) documentation for details.----<a id="sec-600"></a>+<a id="sec-607"></a>> **Source:** `docs/research/3d-landscape-2026-10.md` · [↑ table of contents](#table-of-contents)@@ -136542,7 +137022,7 @@ See the [Validation](#sec-790) documentation for details.Research date: 2026-10-09. Four parallel sweeps (open-source AI generation, web engines and viewers, avatar and companion stacks, commercial platforms), every star count, push date and license read from the GitHub API or the LICENSE file itself on the research date, then checked against this repository to see what three.ws already ships. Commercial vendors are placeholders (Vendor A, B, ...) by the owner's standing directive; open-source projects are named because we depend on them and credit them.-Companions: [oss-adoption-2026-09.md](#sec-468) (the September sweep; two of its Tier 1 items are still open and reappear here), [popular-3d-github-repos.md](#sec-501) (the raw star table), [avatar-engines.md](#sec-145) (the avatar engine atlas).+Companions: [oss-adoption-2026-09.md](#sec-473) (the September sweep; two of its Tier 1 items are still open and reappear here), [popular-3d-github-repos.md](#sec-508) (the raw star table), [avatar-engines.md](#sec-146) (the avatar engine atlas).**Status (2026-10-09):** every item below is a work order in `prompts/finish/` (067 to 083 runnable, 932 to 935 owner-gated). Start from [the campaign context](../prompts/finish/_context/best3d-00-CONTEXT.md).@@ -136720,7 +137200,7 @@ Status is the grep above. "Build" is the smallest change that closes the gap. Li----<a id="sec-601"></a>+<a id="sec-608"></a>> **Source:** `docs/research/competitor-teardown-2026-09.md` · [↑ table of contents](#table-of-contents)@@ -136728,7 +137208,7 @@ Status is the grep above. "Build" is the smallest change that closes the gap. LiResearch date: 2026-09-29. Competitor X is a placeholder name for an AI-agent launchpad on Solana. Source: every public page in its sitemap (27 pages, locale duplicates and the 201 per-token pages excluded), its `llms.txt`, the npm registry entries for its four packages, and the GitHub API for its public repos, all read that day. Competitor X's numbers below are self-reported on its own pages and are marked as such. Our side of each comparison was checked against this repo on the same day, with the file that proves it.-Companion to [launchpad-landscape-2026-09.md](#sec-604), which covers the wider market.+Companion to [launchpad-landscape-2026-09.md](#sec-611), which covers the wider market.**Status (2026-09-30):** Tier 1 shipped on 2026-09-29. Every remaining item is a work order in `prompts/finish/` (015 to 022 runnable, 919 to 925 owner-gated); start from [the campaign context](../prompts/finish/_context/parity-00-CONTEXT.md).@@ -136852,7 +137332,7 @@ For us: what brings in launches that last is the builder shipping something (the----<a id="sec-602"></a>+<a id="sec-609"></a>> **Source:** `docs/research/crypto-agent-oss-landscape-2026-10.md` · [↑ table of contents](#table-of-contents)@@ -136926,7 +137406,7 @@ Also found, not given an order because the work is documentation: `docs/perps.md## Deliberately skipped-- **Launch tiers and modes.** Prior research ([launchpad-landscape-2026-09.md](#sec-604)) says not to add them or promise buybacks.+- **Launch tiers and modes.** Prior research ([launchpad-landscape-2026-09.md](#sec-611)) says not to add them or promise buybacks.- **Enclave custody.** A later decision; the current custody model is unchanged.- **On-device models.** One framework ships them; our brain router already reaches every hosted model and the GPU lanes.- **Equities.** Robinhood means crypto only.@@ -136942,7 +137422,7 @@ Public repositories and docs for each class above; the Solana Foundation announc----<a id="sec-603"></a>+<a id="sec-610"></a>> **Source:** `docs/research/grok-ecosystem-2026-10.md` · [↑ table of contents](#table-of-contents)@@ -137028,7 +137508,7 @@ Star counts and dates were read on 2026-10-10 and will drift; treat them as a sn----<a id="sec-604"></a>+<a id="sec-611"></a>> **Source:** `docs/research/launchpad-landscape-2026-09.md` · [↑ table of contents](#table-of-contents)@@ -137115,7 +137595,7 @@ All-time: 90 mainnet coins from 58 creators since 2026-05-13 (May 26, June 7, Ju----<a id="sec-605"></a>+<a id="sec-612"></a>> **Source:** `docs/research/oss-landscape-2026-10-notes/3d-generation.md` · [↑ table of contents](#table-of-contents)@@ -137342,7 +137822,7 @@ The commercial leaders have converged on the same bundle: sub-15-second textured----<a id="sec-606"></a>+<a id="sec-613"></a>> **Source:** `docs/research/oss-landscape-2026-10-notes/agent-commerce.md` · [↑ table of contents](#table-of-contents)@@ -137577,7 +138057,7 @@ Flag before committing any reference: Virtuals Protocol (VIRTUAL token), elizaOS----<a id="sec-607"></a>+<a id="sec-614"></a>> **Source:** `docs/research/oss-landscape-2026-10-notes/agent-frameworks.md` · [↑ table of contents](#table-of-contents)@@ -137852,7 +138332,7 @@ Two repos in scope are crypto projects and must not be named in committed three.----<a id="sec-608"></a>+<a id="sec-615"></a>> **Source:** `docs/research/oss-landscape-2026-10-notes/avatars-voice.md` · [↑ table of contents](#table-of-contents)@@ -137984,7 +138464,7 @@ Closed vendors compete on a rendering+turn-taking+perception stack: Tavus ships----<a id="sec-609"></a>+<a id="sec-616"></a>> **Source:** `docs/research/oss-landscape-2026-10-notes/chat-memory-evals.md` · [↑ table of contents](#table-of-contents)@@ -138067,7 +138547,7 @@ SillyTavern (AGPL) and RisuAI (GPL-3.0) are copyleft, so only their file formats----<a id="sec-610"></a>+<a id="sec-617"></a>> **Source:** `docs/research/oss-landscape-2026-10-notes/coding-mcp-skills.md` · [↑ table of contents](#table-of-contents)@@ -138266,7 +138746,7 @@ Desktop computer use has crossed the human baseline: OSWorld's paper puts humans----<a id="sec-611"></a>+<a id="sec-618"></a>> **Source:** `docs/research/oss-landscape-2026-10-notes/irl-home-robotics.md` · [↑ table of contents](#table-of-contents)@@ -138408,7 +138888,7 @@ No open repo clearly beats three.ws's webcam ASL recognition on a published, com----<a id="sec-612"></a>+<a id="sec-619"></a>> **Source:** `docs/research/oss-landscape-2026-10-notes/worlds-engines.md` · [↑ table of contents](#table-of-contents)@@ -138596,7 +139076,7 @@ Rendering splats on the web is commercially clean: Spark (MIT, World Labs), Supe----<a id="sec-613"></a>+<a id="sec-620"></a>> **Source:** `docs/research/oss-landscape-2026-10.md` · [↑ table of contents](#table-of-contents)@@ -138677,7 +139157,7 @@ Two second-order findings change priorities. First, the Hunyuan exposure means t----<a id="sec-614"></a>+<a id="sec-621"></a>> **Source:** `docs/research/solana-robinhood-playbook-2026-10.md` · [↑ table of contents](#table-of-contents)@@ -138685,7 +139165,7 @@ Two second-order findings change priorities. First, the Hunyuan exposure means tResearch date: 2026-10-08. Competitors are named by placeholder per the repo convention for research docs. The placeholders here are local to this file (R1, R2 on Robinhood Chain; S1, S2 on Solana) and do not map to the letters in the two September docs. The key and the source list were delivered to the owner in the session that produced this file. Robinhood, pump.fun, Meteora and Phantom are named because three.ws integrates them as venues or rails. Market numbers come from DefiLlama pulls taken that day and from protocol-reported figures relayed by the trade press, so treat them as approximate. Our own state was checked against this repo the same day.-Companion to [launchpad-landscape-2026-09.md](#sec-604) (launchpads, ranked fixes) and [competitor-teardown-2026-09.md](#sec-601) (one agent launchpad, packaging). This doc covers what those did not: agents, consumer apps, distribution, and Robinhood Chain beyond launchpads.+Companion to [launchpad-landscape-2026-09.md](#sec-611) (launchpads, ranked fixes) and [competitor-teardown-2026-09.md](#sec-608) (one agent launchpad, packaging). This doc covers what those did not: agents, consumer apps, distribution, and Robinhood Chain beyond launchpads.## Bottom line@@ -138840,7 +139320,7 @@ Copy pump.fun's structure, not its size: a fixed share of platform revenue, comm----<a id="sec-615"></a>+<a id="sec-622"></a>> **Source:** `docs/resilience.md` · [↑ table of contents](#table-of-contents)@@ -138998,7 +139478,7 @@ explicit `--accept`, which is a reviewable line in the diff.----<a id="sec-616"></a>+<a id="sec-623"></a>> **Source:** `docs/restyle.md` · [↑ table of contents](#table-of-contents)@@ -139010,7 +139490,7 @@ Page: [/restyle](https://three.ws/restyle) · API: `/api/material-studio`## Why it exists-Generating a 3D model is the expensive step. Once you have a good mesh, wanting it in a different finish should not mean paying to regenerate the whole thing and risking a worse shape. Restyle Studio separates the two. Skin is cheap and reversible; geometry is precious and left alone. That makes iterating on look-and-feel a tight loop: try chrome, try worn copper, try glass, save the two you like as durable versions, export the winner. It also gives the rest of the platform one shared material vocabulary. Restyle Studio consumes the same PBR preset library (`@three-ws/viewer-presets`) and the same GLB optimize-and-validate path that [Avatar Studio](#sec-150) uses, instead of inventing a parallel one.+Generating a 3D model is the expensive step. Once you have a good mesh, wanting it in a different finish should not mean paying to regenerate the whole thing and risking a worse shape. Restyle Studio separates the two. Skin is cheap and reversible; geometry is precious and left alone. That makes iterating on look-and-feel a tight loop: try chrome, try worn copper, try glass, save the two you like as durable versions, export the winner. It also gives the rest of the platform one shared material vocabulary. Restyle Studio consumes the same PBR preset library (`@three-ws/viewer-presets`) and the same GLB optimize-and-validate path that [Avatar Studio](#sec-151) uses, instead of inventing a parallel one.## How it works@@ -139088,18 +139568,18 @@ Pass the returned `lineage` array back as `parent_lineage` on the next call to e- **Texture generation is best-effort.** Past the free daily quota the image lane returns a payment-required signal; the studio surfaces that as a note and keeps the flat PBR restyle it already applied. It never fakes a texture.- **Bounded, not gated.** The web endpoint is free but rate-limited per IP (separate limits for uploads and restyle/variants). Instructions are capped at 300 characters and uploads at 64 MB.- **Reset vs. revert.** Reset restores the original material values in the current tab. Reverting to an earlier durable GLB is a separate action: click its entry in the Versions strip. Reverting also re-anchors the source: the next AI restyle, Save version, or "Save all as versions" reads that version's bytes and branches from it, rather than from the newest checkpoint.-- **No mesh changes, verified, not just promised.** Every restyle and variant is checked server-side with `@three-ws/glb-diff` against its own source before it is ever persisted (`api/_lib/preserve-contract.js`): topology, UVs, skeleton, skin, and clips must all come back unchanged, or the operation throws instead of handing back a URL. The response carries `preserve: { kinds, verified: true }` as proof. A "Regenerate part" edit runs the same check, scoped to `skeleton` and `clips` (the part itself legitimately changes shape); each lineage step with a parent exposes a "Diff" link that opens [Model Diff](#sec-431) pre-loaded with that exact before/after pair.+- **No mesh changes, verified, not just promised.** Every restyle and variant is checked server-side with `@three-ws/glb-diff` against its own source before it is ever persisted (`api/_lib/preserve-contract.js`): topology, UVs, skeleton, skin, and clips must all come back unchanged, or the operation throws instead of handing back a URL. The response carries `preserve: { kinds, verified: true }` as proof. A "Regenerate part" edit runs the same check, scoped to `skeleton` and `clips` (the part itself legitimately changes shape); each lineage step with a parent exposes a "Diff" link that opens [Model Diff](#sec-435) pre-loaded with that exact before/after pair.## Related-- [Avatar Studio](#sec-150): shares the same GLB optimize-and-validate path and material vocabulary.-- [Scene Composer](#sec-210) and [Scene Studio](#sec-625): arrange and edit restyled models in a full scene.-- [MCP tools reference](#sec-415): the paid `restyle_material` agent twin of this endpoint.+- [Avatar Studio](#sec-151): shares the same GLB optimize-and-validate path and material vocabulary.+- [Scene Composer](#sec-211) and [Scene Studio](#sec-632): arrange and edit restyled models in a full scene.+- [MCP tools reference](#sec-419): the paid `restyle_material` agent twin of this endpoint.- [/forge](https://three.ws/forge): generate the models you bring here.----<a id="sec-617"></a>+<a id="sec-624"></a>> **Source:** `docs/rig-doctor.md` · [↑ table of contents](#table-of-contents)@@ -139113,7 +139593,7 @@ Everything runs in your browser. The file is read with `FileReader` and analysed**On this page:** [The problem](#the-problem-a-rig-that-loads-but-never-moves) · [Reading the verdict](#reading-the-verdict) · [Coverage](#coverage-which-limbs-will-move) · [The repair](#the-repair) · [Generated output](#generated-output) · [Conventions](#recognised-rig-conventions) · [The canonical skeleton](#the-canonical-skeleton) · [Programmatic use](#programmatic-use)-Related: [Avatar CLI](#sec-143) turns the generated manifest into a validated, hash-anchored file. The [web component reference](#sec-799) covers the `<agent-3d>` element the embed tab emits. [Asset pipeline](#sec-002) covers FBX and GLB conversion upstream of all of this.+Related: [Avatar CLI](#sec-144) turns the generated manifest into a validated, hash-anchored file. The [web component reference](#sec-811) covers the `<agent-3d>` element the embed tab emits. [Asset pipeline](#sec-002) covers FBX and GLB conversion upstream of all of this.---@@ -139154,7 +139634,7 @@ One of two things is true:### Non-humanoid rigs-A quadruped, a creature, or a prop rigged by [`workers/rig-nonhuman`](https://github.com/nirholas/three.ws/tree/main/workers/rig-nonhuman) (UniRig + SkinTokens) or the [AniGen](#sec-313) Forge lane has no Mixamo-shaped skeleton to score against, so it always lands in **Will not animate** here: zero canonical joints is the correct, expected result for a mesh the clip library was never going to retarget onto in the first place. Canonical coverage cannot tell you whether a rig like that is actually sound, so the **Skin weights** stat answers the real question instead: how many joints influence the single heaviest-weighted vertex (**max influences**), and how many of the mesh's skinned vertices came back with no joint influence at all (**unweighted vertices**). A model with zero unweighted vertices is fully deformable by its own predicted skeleton even though it will never drive a three.ws clip; a nonzero count means the skinning step missed geometry and that part of the mesh will not move under any skeleton, humanoid or not.+A quadruped, a creature, or a prop rigged by [`workers/rig-nonhuman`](https://github.com/nirholas/three.ws/tree/main/workers/rig-nonhuman) (UniRig + SkinTokens) or the [AniGen](#sec-316) Forge lane has no Mixamo-shaped skeleton to score against, so it always lands in **Will not animate** here: zero canonical joints is the correct, expected result for a mesh the clip library was never going to retarget onto in the first place. Canonical coverage cannot tell you whether a rig like that is actually sound, so the **Skin weights** stat answers the real question instead: how many joints influence the single heaviest-weighted vertex (**max influences**), and how many of the mesh's skinned vertices came back with no joint influence at all (**unweighted vertices**). A model with zero unweighted vertices is fully deformable by its own predicted skeleton even though it will never drive a three.ws clip; a nonzero count means the skinning step missed geometry and that part of the mesh will not move under any skeleton, humanoid or not.---@@ -139201,7 +139681,7 @@ The **Ship it** panel writes three artefacts from the file you dropped.**Embed** is the `<agent-3d>` loader and element, ready to paste into any page.-**CLI** is the [`@three-ws/avatar-cli`](#sec-143) invocation that produces the same manifest with a real `sha256` over the mesh bytes, plus the validate call. Run it when you are ready to anchor the manifest for real:+**CLI** is the [`@three-ws/avatar-cli`](#sec-144) invocation that produces the same manifest with a real `sha256` over the mesh bytes, plus the validate call. Run it when you are ready to anchor the manifest for real:```bashnpx @three-ws/avatar-cli init \@@ -139340,7 +139820,7 @@ Your own file cannot be shared this way, because it never leaves your machine.----<a id="sec-618"></a>+<a id="sec-625"></a>> **Source:** `docs/risk-acknowledgment.md` · [↑ table of contents](#table-of-contents)@@ -139437,7 +139917,7 @@ Rules the helper and its call sites follow:Some money paths are gated on the server only, because they have nosingle-click dialog of their own: opening, resuming, depositing into,-redeeming from, owner-trading and fee-claiming a [USDC vault](#sec-792)+redeeming from, owner-trading and fee-claiming a [USDC vault](#sec-801)(`vault-open`, `vault-resume`, `vault-deposit`, `vault-redeem`, `vault-trade`,`vault-claim-fees`), creating or resuming a programmable order(`order-create`, `order-resume`), and hiring another agent for a paid skill@@ -139592,11 +140072,11 @@ in the same change.- [Agent Wallet Agreement](https://three.ws/legal/agent-wallet)- [Risk Disclosure](https://three.ws/legal/risk)- [Terms of Service](https://three.ws/legal/tos), section 8-- [Custody you can verify](#sec-232): the spend limits and freezes that bound what agents can do after signing+- [Custody you can verify](#sec-233): the spend limits and freezes that bound what agents can do after signing----<a id="sec-619"></a>+<a id="sec-626"></a>> **Source:** `docs/rivalries.md` · [↑ table of contents](#table-of-contents)@@ -139618,8 +140098,8 @@ tests [tests/rivalries.test.js](../tests/rivalries.test.js)## Why it existsEverything the platform knows about a trader is already public and provable: the-[leaderboard](#sec-695) ranks them, [/trader/:id](../src/trader.js)-proves the record, and [Trader Wrapped](#sec-689) recaps a season. What+[leaderboard](#sec-703) ranks them, [/trader/:id](../src/trader.js)+proves the record, and [Trader Wrapped](#sec-697) recaps a season. Whatnone of those answer is the question a spectator asks first, which is what justhappened. A place changing hands is the smallest unit of drama a trading boardproduces, it happens on its own several times a week, and until now nothing@@ -139751,7 +140231,7 @@ overlapped.The strip sits under the arena's KPI row, above the board it describes, and showsup to three matchups: the two traders' faces, the kind as a pill, the headline,the momentum line, any shared coin, and two links out (the leader's record, and a-[ghost-copy](#sec-323) of them with no money at risk).+[ghost-copy](#sec-326) of them with no money at risk).Every state is designed, because the strip has to survive an empty board on aquiet day: one skeleton row while it loads, an honest line naming the settled@@ -139761,14 +140241,14 @@ are already on screen.## Related-- [The trading surfaces](#sec-695): Radar, Coin Intelligence, Fade Radar, Live Trade Feed, Watchlist, Mission Control-- [Ghost-copy](#sec-323): paper-copy any verified agent over their real closed trades-- [Trader Wrapped](#sec-689): the season recap, which carries its own nearest-rival slide-- [Fork a trade](#sec-315): one tap from any coin to the real trade panel+- [The trading surfaces](#sec-703): Radar, Coin Intelligence, Fade Radar, Live Trade Feed, Watchlist, Mission Control+- [Ghost-copy](#sec-326): paper-copy any verified agent over their real closed trades+- [Trader Wrapped](#sec-697): the season recap, which carries its own nearest-rival slide+- [Fork a trade](#sec-318): one tap from any coin to the real trade panel----<a id="sec-620"></a>+<a id="sec-627"></a>> **Source:** `docs/robinhood-chain-markets.md` · [↑ table of contents](#table-of-contents)@@ -139794,7 +140274,7 @@ actions). This page — and the API behind it — is that missing layer.that graduates into a locked Uniswap V4 pool), **NOXA** (instant Uniswap v3) and **TheOdyssey** (bonding curve). Pons coins still on their curve show the curve's price, market capand graduation progress. To launch one from your own agent, see- [Launch a coin on Robinhood Chain (Pons)](#sec-500).+ [Launch a coin on Robinhood Chain (Pons)](#sec-507).- **Chain** — block height, gas, transaction/address counts, and 90 days of chain TVL (DefiLlama).Every coin and Stock Token links to its own detail page —@@ -139871,7 +140351,7 @@ Free, keyless, real data only:| `GET /api/v1/robinhood/launches` | Recent launches from Pons, NOXA and The Odyssey, newest first. Pons curve-stage coins carry `priceUsd`, `marketCapUsd` and `graduationPct` read from the curve || `GET /api/v1/robinhood/desk` | The desk's market side in one read: chain vitals, the premium ridge (bins, liquidity layers, percentiles), the widest tradeable dislocations, memecoin movers, recent launches || `GET /api/v1/robinhood/wallet?address=0x…` | The desk's wallet side in one read: native balance, priced ERC-20 positions, book totals, balance history (daily + per-transaction, merged), the activity tape and counterparty flow |-| `GET /api/v1/robinhood/paired-markets` | Every asset a [paired coin](#sec-472) can trade against, from the launchpad's on-chain quote registry, with class, live USD price and opening value, plus the launchpad's live terms |+| `GET /api/v1/robinhood/paired-markets` | Every asset a [paired coin](#sec-477) can trade against, from the launchpad's on-chain quote registry, with class, live USD price and opening value, plus the launchpad's live terms || `GET /api/v1/robinhood/paired-coins` | Paired coins, newest first, every pool priced in dollars, with the verified descriptor and launching agent (`limit`, `offset`, `agent`) || `GET /api/v1/robinhood/paired-coins-detail?address=0x…` | One paired coin: pools, per-pool candles (`interval`), recent trades from the launchpad's `Swap` events |@@ -139912,16 +140392,16 @@ math; Chainlink feed prices are already multiplier-adjusted, so they're never re## Related surfaces-- [Market Data API](#sec-407) — the same paid-endpoint pattern (x402, `priceFor`,+- [Market Data API](#sec-411) — the same paid-endpoint pattern (x402, `priceFor`,service-catalog descriptor) applied to the rest of three.ws's market data.-- [Trust primitives](#sec-700) — score a Robinhood Chain wallet's cross-chain+- [Trust primitives](#sec-708) — score a Robinhood Chain wallet's cross-chainreputation before transacting with it.-- [x402 distribution](#sec-853) — how the paid portfolio endpoint gets discovered+- [x402 distribution](#sec-868) — how the paid portfolio endpoint gets discoveredacross the x402 ecosystem.----<a id="sec-621"></a>+<a id="sec-628"></a>> **Source:** `docs/robinhood-portfolios.md` · [↑ table of contents](#table-of-contents)@@ -140333,7 +140813,7 @@ chain 4663 as deployed.----<a id="sec-622"></a>+<a id="sec-629"></a>> **Source:** `docs/run-receipts-x-reply-and-thread.md` · [↑ table of contents](#table-of-contents)@@ -140405,7 +140885,7 @@ Thank you for the push. It found a real problem on its first day. Full article:----<a id="sec-623"></a>+<a id="sec-630"></a>> **Source:** `docs/run-receipts.md` · [↑ table of contents](#table-of-contents)@@ -140546,12 +141026,12 @@ A receipt never changes a tool's result; it only adds to it.## Related-- [3D Studio MCP](#sec-414): the tools that write receipts-- [Reasoning Ledger](#sec-595): the same idea for agent decisions+- [3D Studio MCP](#sec-418): the tools that write receipts+- [Reasoning Ledger](#sec-602): the same idea for agent decisions----<a id="sec-624"></a>+<a id="sec-631"></a>> **Source:** `docs/sas-attestations.md` · [↑ table of contents](#table-of-contents)@@ -140561,7 +141041,7 @@ An attestation is a signed on-chain statement about a wallet or an agent (for exthree.ws issues two kinds of on-chain attestations on Solana:-- **Permissionless attestations** — general feedback, task lifecycle, dispute, and revoke events. Anyone can write them as SPL Memos (see [Solana reputation](#sec-656)).+- **Permissionless attestations** — general feedback, task lifecycle, dispute, and revoke events. Anyone can write them as SPL Memos (see [Solana reputation](#sec-664)).- **Credentialed attestations** — claims only three.ws or an authorized validator may make: that a wallet is verified, or that a validator audited an agent's task result. These use the [Solana Attestation Service (SAS)](https://attest.solana.com/) and are signed by the **three.ws authority wallet**.This page covers the authority wallet, the `SAS_AUTHORITY_SECRET` environment variable, bootstrapping the credential + schemas, and the API that issues them.@@ -140784,13 +141264,13 @@ Closing (revoking) an attestation is done server-side via `sasClose()` in [api/_----<a id="sec-625"></a>+<a id="sec-632"></a>> **Source:** `docs/scene-studio.md` · [↑ table of contents](#table-of-contents)# Scene Studio: the full three.js editor, in your browser-Scene Studio is the complete [mrdoob/three.js](https://github.com/mrdoob/three.js) editor (release r184, MIT-licensed), vendored into three.ws and wrapped in the site chrome. It is the heavyweight scene tool: import GLBs and other assets, move and rotate and scale them with transform gizmos, edit materials and lights and cameras through a full property sidebar, script objects with live JavaScript, play the scene, and export it. Where [Scene Composer](#sec-210) is a focused avatar-plus-props arranger and [Animation Studio](#sec-100) is a posing and keyframing tool, Scene Studio is the general-purpose 3D authoring surface underneath them.+Scene Studio is the complete [mrdoob/three.js](https://github.com/mrdoob/three.js) editor (release r184, MIT-licensed), vendored into three.ws and wrapped in the site chrome. It is the heavyweight scene tool: import GLBs and other assets, move and rotate and scale them with transform gizmos, edit materials and lights and cameras through a full property sidebar, script objects with live JavaScript, play the scene, and export it. Where [Scene Composer](#sec-211) is a focused avatar-plus-props arranger and [Animation Studio](#sec-100) is a posing and keyframing tool, Scene Studio is the general-purpose 3D authoring surface underneath them.Page: [/scene](https://three.ws/scene)@@ -140812,14 +141292,14 @@ The editor is ported from the upstream `editor/index.html` with a small set of lSix sibling modules sit on top of the vendored editor without touching `vendor/**`. They are the difference between a mirror of the upstream demo and a surface that belongs to this platform:-- **A quick-action bar** (top right, clear of the sidebar): **Import from Forge** takes a GLB URL from a [Forge](#sec-313) or Forge Max result and adds it through the same undo-able path as a drag-and-drop import; **Export** writes a Web GLB or an AR bundle (`.usdz` for iOS Quick Look) in one click; **Share** uploads the scene and opens the platform's "Embed this model" panel with an iframe, web-component, and `<agent-3d>` snippet.+- **A quick-action bar** (top right, clear of the sidebar): **Import from Forge** takes a GLB URL from a [Forge](#sec-316) or Forge Max result and adds it through the same undo-able path as a drag-and-drop import; **Export** writes a Web GLB or an AR bundle (`.usdz` for iOS Quick Look) in one click; **Share** uploads the scene and opens the platform's "Embed this model" panel with an iframe, web-component, and `<agent-3d>` snippet.- **An empty state.** A brand-new scene holds nothing but the default camera, which renders as a bare grid. The overlay on that grid says what a starting point looks like (drag a `.glb` in, pick a primitive from **Add**, or import a model you already generated) and retires itself the moment the scene has content, including a scene restored from autosave.- **Designed failures.** A dead link, a private URL, a blocked cross-origin fetch, or a failed upload each surface in the platform's toast with the likely cause named and a fallback to try, rather than in a native `alert()` box.- **Accessible icon-only controls.** The vendored translate/rotate/scale gizmo buttons and the animation timeline's play/pause/stop transport are icon-only `<button>`s with no accessible name. The studio gives all six names read from the editor's own string table, so they stay translated, and mirrors the active gizmo mode into `aria-pressed` so it is both announced and reachable by keyboard.### Agent tab-A fifth sibling module, the **Agent** tab in the sidebar, lets you drive the open scene by typing instead of clicking. It is a small chat panel next to the vendored Scene/Project/Settings tabs. Type a prompt ("add a red cube to the left of the chair", "make the sphere metallic"), and a free, keyless model (the same free-first provider chain the rest of the platform's chat surfaces use, see [docs/free-llm-providers.md](#sec-317)) reads the scene and calls real editing tools: add a primitive or a Forge-generated object, move/rotate/scale a named object, or recolor a material. Every tool call runs as a genuine `editor.execute(Command)`, the exact call the toolbar and menus make, so it shows up in the hierarchy, undoes with Edit > Undo, and persists through the same autosave as a manual edit.+A fifth sibling module, the **Agent** tab in the sidebar, lets you drive the open scene by typing instead of clicking. It is a small chat panel next to the vendored Scene/Project/Settings tabs. Type a prompt ("add a red cube to the left of the chair", "make the sphere metallic"), and a free, keyless model (the same free-first provider chain the rest of the platform's chat surfaces use, see [docs/free-llm-providers.md](#sec-320)) reads the scene and calls real editing tools: add a primitive or a Forge-generated object, move/rotate/scale a named object, or recolor a material. Every tool call runs as a genuine `editor.execute(Command)`, the exact call the toolbar and menus make, so it shows up in the hierarchy, undoes with Edit > Undo, and persists through the same autosave as a manual edit.Every prompt that changes the scene pushes a numbered **version**: a snapshot of the scene plus a screenshot of the viewport at that moment, so you can see what changed without hunting through the hierarchy. Click an earlier version's thumbnail to restore it; that restore is itself one more undoable edit; a mis-restore is one Ctrl+Z away, same as any other mistake in the editor.@@ -140865,22 +141345,22 @@ A typical round trip from another studio:## Related-- [Scene Composer](#sec-210): the lighter avatar-plus-props arranger with Forge integration.+- [Scene Composer](#sec-211): the lighter avatar-plus-props arranger with Forge integration.- [Animation Studio](#sec-100): builds the animated GLBs Scene Studio records to video.-- [Restyle Studio](#sec-616): re-skin the models before or after composing them.+- [Restyle Studio](#sec-623): re-skin the models before or after composing them.- [3D asset pipeline](#sec-002): how GLB, glTF, and clip formats relate across the platform.-- [Free LLM providers](#sec-317): the free-first provider chain the Agent tab reasons with.+- [Free LLM providers](#sec-320): the free-first provider chain the Agent tab reasons with.- [src/scene-studio/README.md](../src/scene-studio/README.md): the module layout, the exported wrapper API, and how re-vendoring a three.js upgrade stays mechanical.----<a id="sec-626"></a>+<a id="sec-633"></a>> **Source:** `docs/sdk.md` · [↑ table of contents](#table-of-contents)# SDK & Library-This page is for developers who want to build with three.ws code in their own project, beyond pasting an embed snippet. If you just want a 3D agent on a page, start with the [web component](#sec-799); come here when you need to import classes, register agents on-chain, or build the bundles yourself. There are two distributable artifacts you can import:+This page is for developers who want to build with three.ws code in their own project, beyond pasting an embed snippet. If you just want a 3D agent on a page, start with the [web component](#sec-811); come here when you need to import classes, register agents on-chain, or build the bundles yourself. There are two distributable artifacts you can import:| Artifact | Package | Use case ||---|---|---|@@ -140973,7 +141453,7 @@ const viewer = new Viewer(document.getElementById('canvas-container'));viewer.load('https://three.ws/avatars/default.glb');```-Full attribute and event API is documented in [Web Component reference](#sec-799).+Full attribute and event API is documented in [Web Component reference](#sec-811).### loadManifest and normalize@@ -141327,7 +141807,7 @@ three.ws examples repo, so it is installed, run, and link-checked before every r----<a id="sec-627"></a>+<a id="sec-634"></a>> **Source:** `docs/security.md` · [↑ table of contents](#table-of-contents)@@ -141368,7 +141848,7 @@ Chat messages travel through `/api/chat`, which proxies to a configured LLM prov- Does not log message content- Returns the LLM stream directly to your browser-Conversation history lives in `localStorage` by default. Cloud memory sync is opt-in (see [Memory](#sec-420)).+Conversation history lives in `localStorage` by default. Cloud memory sync is opt-in (see [Memory](#sec-424)).### Wallet data@@ -141384,7 +141864,7 @@ The SIWE (Sign-In With Ethereum) flow signs a server-generated challenge — no| Mode | Where data lives | Privacy ||------|-----------------|---------|| `local` (default) | Browser `localStorage` | Device-only |-| `remote` | three.ws cloud storage, tied to your account | Opt-in cloud sync (see [Memory](#sec-420)) |+| `remote` | three.ws cloud storage, tied to your account | Opt-in cloud sync (see [Memory](#sec-424)) || `ipfs` | Public IPFS network | Public — use only for non-sensitive data || `encrypted-ipfs` | IPFS, encrypted before leaving the browser | Encrypted with your key; IPFS only sees ciphertext || `none` | Not persisted | Cleared on page unload |@@ -141536,7 +142016,7 @@ Every registered agent card requires a `model.sha256` field. The `<three-d-agentValidator keys are dedicated signing keys, not personal wallets. The deployed `ValidationRegistry` has **no validator allowlist** (`removeValidator(address)` exists only on `contracts/src/ValidationRegistry.sol`, which is deployed nowhere), so revocation is not an on-chain call: any address can answer a request addressed to it. Containment for a compromised validator key is therefore to rotate it (`scripts/erc8004/provision-validator-key.mjs` reprovisions `VALIDATOR_PRIVATE_KEY` on the API service) and to have indexers and resolvers filter by validator address, treating attestations signed by the retired key as expired from the rotation block onward.-That places the whole burden on key custody: see the platform-validator note in [contracts/DEPLOYMENTS.md](../contracts/DEPLOYMENTS.md) and [docs/erc8004/validation-attestation.md](#sec-264) for the operating rules.+That places the whole burden on key custody: see the platform-validator note in [contracts/DEPLOYMENTS.md](../contracts/DEPLOYMENTS.md) and [docs/erc8004/validation-attestation.md](#sec-267) for the operating rules.### Reputation gaming (V5)@@ -141552,6 +142032,23 @@ Post-registration takedowns operate at the gateway and discovery layer: the on-c---+## Dependency advisories (2026-10-12 audit)++`npm audit fix` (no `--force`) was applied on 2026-10-12. It cleared the one critical advisory (`handlebars`, reachable only through dev and build tooling) and moved `npm audit --omit=dev` from 132 to 117 findings: 0 critical, 70 high, 22 moderate, 25 low. The remaining findings have no fix that stays inside the current semver ranges; `npm audit fix --force` would downgrade or replace direct dependencies (`@pump-fun/pump-sdk`, `@bonfida/spl-name-service`, `agent0-sdk`, `@solana/pay`) and is deliberately not run.++High advisories left open, with reachability:++| Package | Advisory | Pulled in by | Reachable from server code |+| --- | --- | --- | --- |+| `bigint-buffer` | `toBigIntLE()` buffer overflow | `@solana/spl-token` via `@solana/buffer-layout-utils` | Yes, in-process Solana token decoding. Inputs are RPC account data, not user-supplied buffers sized by the caller. Fix needs an upstream `spl-token` major. |+| `toml` | uncontrolled recursion, prototype pollution | `@coral-xyz/anchor` (Anchor IDL tooling) | Parsing is of `Anchor.toml`-style config at tooling time. No server handler parses caller-supplied TOML. |+| `@libp2p/kad-dht`, `@libp2p/peer-store`, `node-forge` | DHT disk exhaustion, PeerRecord spoofing, RSA PKCS#1 v1.5 | `helia` via `agent0-sdk` | `api/agents/8004/*` imports only the constants `DEFAULT_SUBGRAPH_URLS` and `DEFAULT_REGISTRIES` from `agent0-sdk`. No libp2p node is started, so the DHT and peer-store code paths do not run. |+| `adm-zip`, `braces` | ZIP memory allocation, glob stack exhaustion | `hardhat` via `@ethereum-attestation-service/eas-sdk` | Contract-toolchain code. Not imported by `api/` or `server/`. |+| `lodash.set` | prototype pollution | `@bnb-chain/greenfield-js-sdk` | BNB Greenfield client paths only. Callers pass fixed object paths, never user-supplied keys. |+| `nanoid` < 3.3.8 / 2.x | predictable output for non-integer sizes | `@colyseus/core` (multiplayer worker) | Colyseus calls it with its own integer sizes. `api/` uses the patched root `nanoid@3`. |++Rules for this list: re-run `npm audit --omit=dev` after each dependency bump, move a row out of this table when a non-breaking fix lands, and never import one of these packages into a request handler that parses untrusted input without first checking the advisory.+## Skill security### Trust modes@@ -141693,7 +142190,7 @@ For validator misconduct (biased or falsified on-chain attestations), open a pub----<a id="sec-628"></a>+<a id="sec-635"></a>> **Source:** `docs/seed-quality.md` · [↑ table of contents](#table-of-contents)@@ -142026,19 +142523,19 @@ ticks start timing out, lower `SEED_CRON_VISION_MS` before turning it back off.- [Realism quality bench](../data/quality-bench/README.md): the regressionharness whose scorer this gate imports-- [The 3D viewer](#sec-795): what a published catalog entry has to render in+- [The 3D viewer](#sec-805): what a published catalog entry has to render in- [Production log triage](ops/production-log-triage.md): the operator runbookfor the seeding pipeline----<a id="sec-629"></a>+<a id="sec-636"></a>> **Source:** `docs/seeker-app.md` · [↑ table of contents](#table-of-contents)# three.ws on Solana Seeker-three.ws ships as a native Android app for the Solana Seeker (and Saga) through the Solana dApp Store. It is a Trusted Web Activity: the signed APK (`ws.three.app`) opens `https://three.ws/seeker` full-screen in Chrome's rendering engine with no browser chrome, and every wallet interaction is routed to the phone's Seed Vault through Mobile Wallet Adapter. For a WebGL product that is the right shape (it is what Solana Mobile recommends for web apps); what makes it feel like an app is everything around that shell. This page is the user-facing map of those pieces. The packaging and code layout live in [solana-mobile/README.md](../solana-mobile/README.md); how a release reaches the store is [Publishing to the Solana dApp Store](#sec-630).+three.ws ships as a native Android app for the Solana Seeker (and Saga) through the Solana dApp Store. It is a Trusted Web Activity: the signed APK (`ws.three.app`) opens `https://three.ws/seeker` full-screen in Chrome's rendering engine with no browser chrome, and every wallet interaction is routed to the phone's Seed Vault through Mobile Wallet Adapter. For a WebGL product that is the right shape (it is what Solana Mobile recommends for web apps); what makes it feel like an app is everything around that shell. This page is the user-facing map of those pieces. The packaging and code layout live in [solana-mobile/README.md](../solana-mobile/README.md); how a release reaches the store is [Publishing to the Solana dApp Store](#sec-637).**Status: v1.0.0 is approved and live on the Solana dApp Store** (submitted 2026-08-28, release `#331044442814`). Install it from the dApp Store on a Seeker or Saga, or sideload the [v1.0.0 GitHub release](https://github.com/nirholas/three.ws/releases/tag/v1.0.0); everything described below also runs on the web at [/seeker](/seeker).@@ -142079,7 +142576,7 @@ The handoff is one-shot and expires after ten minutes, so a stale share can neveThe APK can be exercised in a stock Android emulator (Pixel 7, Android 14 image). Everything except the Seed Vault itself works there: install, launch, shortcuts, the share intent, deep-link verification state. The recipe is in [solana-mobile/README.md](../solana-mobile/README.md#emulator-qa). For the wallet flows, `tests/solana-mobile-*.test.js` drive the MWA wrapper against a fake transport, and the Solana Mobile reference wallet can be sideloaded into the emulator for an end-to-end sign-in.-Because the app is a TWA, filming it needs no device either: [Filming three.ws on a Seeker without a Seeker](#sec-632) records the shipping page at the Seeker's real panel geometry and seats it in a device body, and says which moments genuinely have to come from the emulator.+Because the app is a TWA, filming it needs no device either: [Filming three.ws on a Seeker without a Seeker](#sec-639) records the shipping page at the Seeker's real panel geometry and seats it in a device body, and says which moments genuinely have to come from the emulator.## The home screen widget@@ -142097,19 +142594,19 @@ including every state it can be in and how it authenticates, is inWindows 11 gets it through the installed PWA's manifest, and macOS and iOS through one WidgetKitextension over the same endpoint and the same kind of widget token. Those sources live in[apple/](../apple/README.md) and the product documentation for all four surfaces is-[native-widgets.md](#sec-440).+[native-widgets.md](#sec-444).----<a id="sec-630"></a>+<a id="sec-637"></a>> **Source:** `docs/seeker-publishing.md` · [↑ table of contents](#table-of-contents)# Publishing three.ws to the Solana dApp Store-How a release of the three.ws Seeker app gets from this repo onto the Solana dApp Store. This is the runbook; the app itself and what it adds over the website are described in [three.ws on Solana Seeker](#sec-629), and the box-by-box submission gate lives in [solana-mobile/docs/CHECKLIST.md](../solana-mobile/docs/CHECKLIST.md). If you are the owner sitting down to actually submit, follow [Submission day](#sec-631) instead: it inlines every field and value so you never open a file.+How a release of the three.ws Seeker app gets from this repo onto the Solana dApp Store. This is the runbook; the app itself and what it adds over the website are described in [three.ws on Solana Seeker](#sec-636), and the box-by-box submission gate lives in [solana-mobile/docs/CHECKLIST.md](../solana-mobile/docs/CHECKLIST.md). If you are the owner sitting down to actually submit, follow [Submission day](#sec-638) instead: it inlines every field and value so you never open a file.-**Status: v1.0.0 is live on the Solana dApp Store** (submitted 2026-08-28, release `#331044442814`, versionCode 1, package `ws.three.app`). What the portal recorded, including the release NFT mint and app collection, is in [Submission day](#sec-631).+**Status: v1.0.0 is live on the Solana dApp Store** (submitted 2026-08-28, release `#331044442814`, versionCode 1, package `ws.three.app`). What the portal recorded, including the release NFT mint and app collection, is in [Submission day](#sec-638).Publishing changed shape in May 2026. `dapp-store-cli` 1.0 is **Publisher Portal backed**: the publisher identity, KYC, the App NFT, and all listing copy live in <https://publish.solanamobile.com>, and the CLI only uploads one signed APK per release. The old `dapp-store create publisher` / `create app` / `publish submit` chain is gone. Anything that still describes that flow is out of date.@@ -142175,7 +142672,7 @@ DAPP_STORE_API_KEY='<portal API key>' \[scripts/publish.sh](../solana-mobile/scripts/publish.sh) checks that assetlinks is reachable, refuses a `versionCode` it already shipped from this machine, passes the API key over stdin so it never appears in a process listing, uploads the APK, mints the release NFT, and submits for review. If the upload dies part way through, resume it with `npx --no-install dapp-store resume --release-id <id>` rather than starting over.-For a later release, bump `appVersionCode` and `appVersion` in [solana-mobile/twa/twa-manifest.json](../solana-mobile/twa/twa-manifest.json) (or pass `VERSION_CODE` / `VERSION_NAME`), then repeat steps 3 and 5. The store rejects a reused `versionCode`. The manifest already reads `1.1.0` / versionCode 2 for the next release, which adds the Agent glance home screen widget ([native widgets](#sec-440)); its status is tracked at the top of [solana-mobile/README.md](../solana-mobile/README.md).+For a later release, bump `appVersionCode` and `appVersion` in [solana-mobile/twa/twa-manifest.json](../solana-mobile/twa/twa-manifest.json) (or pass `VERSION_CODE` / `VERSION_NAME`), then repeat steps 3 and 5. The store rejects a reused `versionCode`. The manifest already reads `1.1.0` / versionCode 2 for the next release, which adds the Agent glance home screen widget ([native widgets](#sec-444)); its status is tracked at the top of [solana-mobile/README.md](../solana-mobile/README.md).Releases are run locally by the owner. This repo does not use GitHub Actions.@@ -142221,7 +142718,7 @@ Review results arrive by email from `[email protected]----<a id="sec-631"></a>+<a id="sec-638"></a>> **Source:** `docs/seeker-submission-day.md` · [↑ table of contents](#table-of-contents)@@ -142229,7 +142726,7 @@ Review results arrive by email from `[email protected]Everything the owner personally needs to do on submission day, in order, with every value inlined so you never have to open a file or a terminal. Budget about 90 minutes, most of it waiting on uploads and the phone.-The engineering runbook is [Publishing to the Solana dApp Store](#sec-630); this page is the human half of it. Tick boxes as you go.+The engineering runbook is [Publishing to the Solana dApp Store](#sec-637); this page is the human half of it. Tick boxes as you go.## Before you start@@ -142482,7 +142979,7 @@ On approval:----<a id="sec-632"></a>+<a id="sec-639"></a>> **Source:** `docs/seeker-video.md` · [↑ table of contents](#table-of-contents)@@ -142655,13 +143152,13 @@ the work. Buy a Seeker if you want a Seeker; otherwise use the paths above.## Related-- [three.ws on Solana Seeker](#sec-629) - what the app adds over the website-- [Publishing to the Solana dApp Store](#sec-630) - how a release ships+- [three.ws on Solana Seeker](#sec-636) - what the app adds over the website+- [Publishing to the Solana dApp Store](#sec-637) - how a release ships- [solana-mobile/README.md](../solana-mobile/README.md) - the packaging and code layout----<a id="sec-633"></a>+<a id="sec-640"></a>> **Source:** `docs/selfie-to-avatar.md` · [↑ table of contents](#table-of-contents)@@ -142689,10 +143186,10 @@ Two of those numbers are measured rather than reasoned about. The blur floor (`B3. **Optional side angles.** Under an "Add side angles" disclosure you can capture two extra stills (`left`, `right`, turned ~45 degrees). They raise fidelity and the ETA, but only the frontal is required. Confirmed shots (and the style choice) are mirrored to `sessionStorage`, so a refresh or accidental back-swipe mid-capture restores every slot instead of starting over; the build phase has its own resume rail (`selfie:pendingJobId`).4. **Refine, in the browser.** `assessPhoto` gates the frontal (no face is the only hard block; blur, illustration, or a distant subject are non-fatal warnings). `refineSelfie` isolates the subject from its background and reframes to a clean head-and-shoulders square, rendered at 1024x1024 with JPEG quality 0.92 ([`src/selfie-refine.js`](../src/selfie-refine.js)). The refined frontal is previewed so you see exactly what the engine sees.5. **Submit.** The pipeline ([`src/selfie-pipeline.js`](../src/selfie-pipeline.js)) downscales each photo to a 1024px longest edge at JPEG quality 0.88, POSTs them as data URIs to `/api/avatars/reconstruct`, and gets back a `jobId`. Before any GPU work starts the handler pre-flights the caller's avatar library against its plan ceiling (`assertAvatarSlotAvailable`) and refuses a full library with `402 plan_limit`, so nobody waits ninety seconds for a mesh that could never be saved.-6. **Reconstruct, server-side.** The reconstruct handler (`api/avatars/_actions.js`) selects a provider through [`api/_lib/regen-provider.js`](../api/_lib/regen-provider.js). The production lane is **GCP**: it POSTs `{ images, body_type }` to the Cloud Run service behind `GCP_RECONSTRUCTION_URL`, today the [`workers/avatar-reconstruction/`](../workers/avatar-reconstruction) FastAPI app deployed as `avatar-reconstruction`. (The multi-backend [`workers/avatar-pipeline-controller/`](../workers/avatar-pipeline-controller) speaks the identical contract and can take over that env var, but is not deployed today.) That pipeline (`face_texture_transfer_v2`) uses **MediaPipe FaceLandmarker** (468 landmarks, Apache-2.0) to transfer your face texture and geometry onto a fixed-topology, pre-rigged Wolf3D/Ready-Player-Me-style humanoid template carrying a Mixamo-compatible skeleton, 52 ARKit blendshapes, and 15 visemes. Full engine detail is in [avatar-reconstruction.md](#sec-149).+6. **Reconstruct, server-side.** The reconstruct handler (`api/avatars/_actions.js`) selects a provider through [`api/_lib/regen-provider.js`](../api/_lib/regen-provider.js). The production lane is **GCP**: it POSTs `{ images, body_type }` to the Cloud Run service behind `GCP_RECONSTRUCTION_URL`, today the [`workers/avatar-reconstruction/`](../workers/avatar-reconstruction) FastAPI app deployed as `avatar-reconstruction`. (The multi-backend [`workers/avatar-pipeline-controller/`](../workers/avatar-pipeline-controller) speaks the identical contract and can take over that env var, but is not deployed today.) That pipeline (`face_texture_transfer_v2`) uses **MediaPipe FaceLandmarker** (468 landmarks, Apache-2.0) to transfer your face texture and geometry onto a fixed-topology, pre-rigged Wolf3D/Ready-Player-Me-style humanoid template carrying a Mixamo-compatible skeleton, 52 ARKit blendshapes, and 15 visemes. Full engine detail is in [avatar-reconstruction.md](#sec-150).7. **Auto-rig fallback.** The template is born rigged. If a generic mesh comes back unrigged and a rig model is configured, `reconstruct-finalize.js` chains a `rerig` job (the `model-rig` worker, `workers/rig`) and moves the job through a `rigging` status before surfacing the avatar. If rigging is impossible it delivers the static mesh tagged `unrigged` rather than nothing.8. **Poll and finish.** The client polls `GET /api/avatars/regenerate-status?jobId=...` every ~3 seconds (backing off on errors). On `status: 'done'` it fetches the finished avatar from `GET /api/avatars/:id` and shows it in a `<model-viewer>`. A `done` job with no `resultAvatarId` means the server's materialize stage threw after the mesh was generated; that stage re-runs on every poll, so the client looks again up to three more times before treating it as a failure. If the materialization lost the quota race (another avatar landed while this one was generating), the server ends the job as `failed` with caller-facing copy rather than leaving it stranded at `done`. The poll uses the adapter for the provider recorded on the job row, not whichever provider currently leads the precedence order, because the stored job id is provider-shaped and only that backend can read it.-9. **Register and mint.** Materializing the avatar also registers it in the Forge store (`forge_creations`, `path: 'reconstruct'`) so galleries, share and embed pages, and provenance treat a capture like any other creation, and fires a best-effort [draft agent identity mint](#sec-252): a Metaplex Core asset on Solana, with an ERC-8004 registration behind its own flag. Both are best-effort by design: the avatar is already delivered, so neither can fail the job.+9. **Register and mint.** Materializing the avatar also registers it in the Forge store (`forge_creations`, `path: 'reconstruct'`) so galleries, share and embed pages, and provenance treat a capture like any other creation, and fires a best-effort [draft agent identity mint](#sec-255): a Metaplex Core asset on Solana, with an ERC-8004 registration behind its own flag. Both are best-effort by design: the avatar is already delivered, so neither can fail the job.10. **Backstop for a closed tab.** The browser poll is what drives finalization, so closing the tab mid-build would otherwise strand the job even though the worker finished. [`api/cron/reconstruct-sweep.js`](../api/cron/reconstruct-sweep.js) runs the same finalize stages server-side every few minutes, so an abandoned capture still lands in your library. It rescues jobs up to 30 days old, and fails anything older with an honest reason rather than leaving it open forever.### The text-to-avatar variant@@ -142795,16 +143292,16 @@ normally).## Related-- [Avatar reconstruction pipeline](#sec-149): the full engine: MediaPipe face-texture transfer, geometry morph, the fixed pre-rigged head template, and the Cloud Run worker.-- [Avatar pipeline](#sec-148): the distinct Forge text-to-3D generation lane.-- [Draft agent mint](#sec-252): the on-chain identity every finished reconstruction gets, the network flags, and the devnet proof script.-- [Trait-based avatar builder](#sec-182): customize and dress the avatar after you scan it.-- [Talking Avatar Video](#sec-672) and [Lipsync](#sec-400): drive the finished avatar's mouth.+- [Avatar reconstruction pipeline](#sec-150): the full engine: MediaPipe face-texture transfer, geometry morph, the fixed pre-rigged head template, and the Cloud Run worker.+- [Avatar pipeline](#sec-149): the distinct Forge text-to-3D generation lane.+- [Draft agent mint](#sec-255): the on-chain identity every finished reconstruction gets, the network flags, and the devnet proof script.+- [Trait-based avatar builder](#sec-183): customize and dress the avatar after you scan it.+- [Talking Avatar Video](#sec-680) and [Lipsync](#sec-404): drive the finished avatar's mouth.- Pages: [/create/selfie](https://three.ws/create/selfie), [/create](https://three.ws/create), [/features/scan](https://three.ws/features/scan).----<a id="sec-634"></a>+<a id="sec-641"></a>> **Source:** `docs/sentiment-scout.md` · [↑ table of contents](#table-of-contents)@@ -142819,7 +143316,7 @@ trades.Surfaces: the **Scout** tab on [Coin Intelligence](https://three.ws/coin-intel?tab=scout)(`/coin-intel?tab=scout`) · the **Sentiment Scout** section in every coin's-detail drawer on `/coin-intel` · the Scout card on [trade receipts](#sec-683)+detail drawer on `/coin-intel` · the Scout card on [trade receipts](#sec-691)· `GET /api/pump/sentiment-scout` · the `sentiment_scout` MCP tool · an opt-incontext block for LLM-judged sniper strategies.Model: `api/_lib/sentiment-scout.js` · X client: `api/_lib/x-search.js` ·@@ -142865,7 +143362,7 @@ Every evidence line carries:| Type | Source | Notes ||---|---|---|-| `volume_spike`, `fresh_buyers` | `pump_coin_intel` (the Coin Intelligence Engine, see [trading surfaces](#sec-695)) | Ranked as percentiles against every launch in the same window. The median launch has one buyer, so "40x the median" would be noise. |+| `volume_spike`, `fresh_buyers` | `pump_coin_intel` (the Coin Intelligence Engine, see [trading surfaces](#sec-703)) | Ranked as percentiles against every launch in the same window. The median launch has one buyer, so "40x the median" would be noise. || `smart_money` | `pump_coin_intel.smart_money_*` | Wallets with a profitable pump.fun record that bought early. || `graduation_approach` | live bonding curve (pump.fun) | Read at scout time. || `social_mention` (X) | X recent search for the coin's **exact contract address** | A ticker matches thousands of coins; a 44-character address matches one. Retweets are excluded so one account cannot count many times. |@@ -142952,7 +143449,7 @@ platform shape `{ error, error_description }`: `invalid_mint`, `invalid_network``trade_receipt`. Arguments: `mint`, `network`, `window_minutes`, `limit`,`track_record`. It returns the same board plus `board_url`. Read-only; likeevery tool there it needs an OAuth token or an x402 payment. See-[MCP](#sec-417).+[MCP](#sec-421).## For strategy builders: Scout context for the LLM judge@@ -143016,14 +143513,14 @@ Code: `searchMintPostsViaXai` / `parseXaiSearchPayload` in## Related-- [Trading surfaces](#sec-695): Coin Intelligence and the launch data+- [Trading surfaces](#sec-703): Coin Intelligence and the launch dataevery volume and buyer line is measured from.-- [Trade receipts](#sec-683): where a Scout flag shows up on a trade.-- [Copy Coach](#sec-224): the guided first copy, which links here.+- [Trade receipts](#sec-691): where a Scout flag shows up on a trade.+- [Copy Coach](#sec-225): the guided first copy, which links here.----<a id="sec-635"></a>+<a id="sec-642"></a>> **Source:** `docs/seo.md` · [↑ table of contents](#table-of-contents)@@ -143102,13 +143599,13 @@ Errors are things a search engine acts on immediately; warnings are quality sign## Related-- [docs/guards.md](#sec-337): the full guard registry, including `audit:seo` and `audit:pages`+- [docs/guards.md](#sec-341): the full guard registry, including `audit:seo` and `audit:pages`- [api/_lib/safe-text.js](../api/_lib/safe-text.js): why every string that reaches JSON-LD is truncated on grapheme boundaries- [STRUCTURE.md](../STRUCTURE.md): where each product surface lives----<a id="sec-636"></a>+<a id="sec-643"></a>> **Source:** `docs/share-and-embed.md` · [↑ table of contents](#table-of-contents)@@ -143174,13 +143671,13 @@ If you manage the HTML of your page directly, the `<agent-3d>` custom element gi<agent-3d agent-id="<your-agent-id>"></agent-3d>```-The element renders inline (no iframe boundary), supports keyboard navigation, and exposes a JavaScript API so you can drive the agent programmatically. See the [Embedding guide](#sec-259) for the full attribute reference and event list.+The element renders inline (no iframe boundary), supports keyboard navigation, and exposes a JavaScript API so you can drive the agent programmatically. See the [Embedding guide](#sec-262) for the full attribute reference and event list.---## Just the avatar, nothing else-If all you want on the page is the 3D avatar, without chat, voice, or any widget UI, [Avatar Artifact](#sec-142) is a one-line iframe:+If all you want on the page is the 3D avatar, without chat, voice, or any widget UI, [Avatar Artifact](#sec-143) is a one-line iframe:```html<iframe src="https://three.ws/avatar-artifact?agent=<your-agent-id>" width="100%" height="600" style="border:0" loading="lazy" title="Avatar Artifact"></iframe>@@ -143215,14 +143712,14 @@ To customize the preview image, change the agent's thumbnail in the editor.## What's next-- **Make your agent smarter** → [Skills system](#sec-649)-- **Understand the technical embed options** → [Embedding guide](#sec-259)-- **Payment and crypto questions** → [Do I need crypto?](#sec-248)-- **Give it a permanent on-chain address** → [Register on-chain](#sec-749)+- **Make your agent smarter** → [Skills system](#sec-657)+- **Understand the technical embed options** → [Embedding guide](#sec-262)+- **Payment and crypto questions** → [Do I need crypto?](#sec-251)+- **Give it a permanent on-chain address** → [Register on-chain](#sec-757)----<a id="sec-637"></a>+<a id="sec-644"></a>> **Source:** `docs/shared-utilities.md` · [↑ table of contents](#table-of-contents)@@ -143411,7 +143908,7 @@ providers (with per-provider parsers) use `fetchFirst` fromBecause every third-party call in `api/` passes through one of these three(`fetchUpstream`, `fetchFirst`, or the Solana connection), they are also where-[Brownout](#sec-173) hooks in. Each attempt is recorded against the+[Brownout](#sec-174) hooks in. Each attempt is recorded against thecurrent request (`recordSource` from `api/_lib/brownout/`), and a `lastGood`hit records itself as `tier: 'stale'` with its age, which is what lets theresponse carry the `x-brownout` / `x-brownout-trace` headers saying which rung@@ -143624,7 +144121,7 @@ paused during an incident and never resumed, failed silently.----<a id="sec-638"></a>+<a id="sec-645"></a>> **Source:** `docs/shipfeed.md` · [↑ table of contents](#table-of-contents)@@ -143836,7 +144333,116 @@ The full reference, including the linking internals exported for tuning, is in t----<a id="sec-639"></a>+<a id="sec-646"></a>++> **Source:** `docs/shopify-app.md` · [↑ table of contents](#table-of-contents)++# Shopify app: Photo to 3D product media++three.ws ships a [Shopify embedded app](https://shopify.dev/docs/apps/build/embedded-app-components)+that turns a product photo into a real, rotatable 3D model and attaches it to+the product. Shopify then shows it on the storefront with its own 3D viewer on+desktop and iOS AR Quick Look on iPhone, both derived from the single GLB this+app uploads.++**On this page:** [How it works](#how-it-works) · [Auth flow](#auth-flow) · [Billing](#billing) · [Privacy webhooks](#privacy-webhooks) · [Owner setup](#owner-setup)++---++## How it works++1. A merchant installs the app from the Shopify App Store (or a direct install+ link during development) and lands on the embedded admin page+ (`pages/shopify-app.html`, `src/shopify-app/app.js`), which lists the+ store's products.+2. For a product without a 3D model, the merchant clicks **Generate 3D+ model**. The app submits the product's first image to three.ws's own+ `/api/forge` image-to-3D pipeline (`api/_mcp-studio/forge-client.js`, the+ same pipeline every other three.ws 3D surface runs on, no separate+ generation logic).+3. Once generation finishes, the GLB is staged into Shopify's own upload+ storage (`stagedUploadsCreate`) and the merchant previews it in-page with+ `<model-viewer>` before confirming **Attach to product**.+4. Attaching calls `productCreateMedia` with `mediaContentType: MODEL_3D`.+ Shopify auto-derives the USDZ AR Quick Look asset from the uploaded GLB, so+ this app uploads exactly one file per product, not two.+5. **Bulk mode**: select every product missing a 3D model and click+ **Generate selected**; each card tracks its own real status+ (generating → ready → attaching → attached, or failed with a retry+ button) instead of one opaque batch spinner.++## Auth flow++Two different authentication shapes, both documented by Shopify:++- **OAuth (install)**: `GET /api/shopify/install` → Shopify's own+ `/admin/oauth/authorize` → `GET /api/shopify/callback`, which verifies the+ query-string HMAC (`api/_lib/shopify/hmac.js`), checks the `state` nonce+ cookie, exchanges the code for an **offline** access token, and registers+ the four mandatory webhooks.+- **Embedded API calls**: every `/api/shopify/*` route other than+ `install`/`callback`/`webhooks`/`billing/confirm` requires a session token+ (`Authorization: Bearer <token>`), the short-lived HS256 JWT Shopify's App+ Bridge CDN script attaches via `window.shopify.idToken()`. Verified in+ `api/_lib/shopify/session-token.js` against the app's client secret, then+ matched to the shop's stored offline token (`api/_lib/shopify/auth-request.js`)+ so the actual Admin GraphQL calls always run with the install-time token,+ never the session token itself.++App Bridge loads via Shopify's CDN script+(`https://cdn.shopify.com/shopifycloud/app-bridge.js`), not the+`@shopify/app-bridge` npm package or the Remix app template: this repo is+vanilla JS + Vite, and the CDN script is Shopify's current framework-agnostic+path. The app's public API key reaches the page through Vite's HTML env+replacement (`%VITE_SHOPIFY_API_KEY%` in `pages/shopify-app.html`), baked in+at build time from the same client id as the server's `SHOPIFY_API_KEY`.++## Billing++One usage-based `AppSubscription` per shop (`api/_lib/shopify/billing.js`):+$0.49 per product converted, capped at $100/month, priced from Forge's own+per-call cost plus Shopify's revenue share. The merchant approves it once+(`POST /api/shopify/billing/activate` → Shopify's own confirmation page,+opened with `window.open(url, '_top')` since Billing approval cannot happen+inside the embedded iframe); `GET /api/shopify/billing/confirm` re-checks+Shopify's own `currentAppInstallation.activeSubscriptions` and records the+result. A usage record is only created at the moment a model is actually+attached (`POST /api/shopify/media/attach`), never for a generation the+merchant discarded.++Every subscription this app creates runs with `test: true` until the app is+approved for Public distribution on the App Store (Shopify's own+`AppSubscriptionCreate` restriction); Shopify records the usage but never+settles a test charge, so the full flow is exercisable before launch. Flip+with `SHOPIFY_BILLING_LIVE=1` once the app is live.++## Privacy webhooks++Four webhooks, registered via GraphQL `webhookSubscriptionCreate` right after+OAuth completes (`api/_lib/shopify/webhook-register.js`), each verified+against `X-Shopify-Hmac-Sha256` (`api/_lib/shopify/webhook-verify.js`) and+claimed against a delivery-id ledger (`shopify_webhook_deliveries`) before any+handler logic runs, so a Shopify retry never double-processes:++- `customers/data_request`, `customers/redact`: no-ops. This app never reads+ customer data (scopes are `read_products,write_products` only) and stores+ nothing keyed by a customer id, so there is nothing to return or erase.+- `shop/redact`: genuinely erases every row this app stored for the shop+ (media jobs, billing, the OAuth session) 48 hours after uninstall.+- `app/uninstalled`: marks the shop's session dead immediately so no later+ call tries to use an access token Shopify has already revoked.++## Owner setup++The app needs a Shopify Partner account, a registered app, and a development+store before any of this can run live. Exact Partner Dashboard settings, env+vars, and the App Store listing copy are written out in+[`marketing/growth/submissions/shopify-app.md`](https://github.com/nirholas/three.ws/blob/main/marketing/growth/submissions/shopify-app.md).+Owner action is tracked in `prompts/finish/_context/production-100-OWNER-ACTIONS.md`.++---++<a id="sec-647"></a>> **Source:** `docs/short-form-venue-kit-2026-09.md` · [↑ table of contents](#table-of-contents)@@ -143848,9 +144454,9 @@ status: drafts, owner approval required before posting (external-channel gate in# Short-form venue kit, September 2026-The long-form drafts live one per file (see [publishing-program-2026-09.md](#sec-557) for the full matrix). This file holds the venues where the unit of publication is a paragraph, a title, or a first comment.+The long-form drafts live one per file (see [publishing-program-2026-09.md](#sec-564) for the full matrix). This file holds the venues where the unit of publication is a paragraph, a title, or a first comment.-**Rules that apply to every entry here.** Post as a participant, not as a brand voice: each of these communities rewards a specific technical claim with a link that backs it. Keep every line positive and confident: describe what the work does and the design principle behind it. Never post the same text to two subreddits. Answer replies yourself, in your own words. If a claim is not checkable in a live endpoint or the repository, cut it. Where a venue welcomes it, mention the partner programmes using the exact designations in [partners.md](#sec-474), never as an endorsement.+**Rules that apply to every entry here.** Post as a participant, not as a brand voice: each of these communities rewards a specific technical claim with a link that backs it. Keep every line positive and confident: describe what the work does and the design principle behind it. Never post the same text to two subreddits. Answer replies yourself, in your own words. If a claim is not checkable in a live endpoint or the repository, cut it. Where a venue welcomes it, mention the partner programmes using the exact designations in [partners.md](#sec-480), never as an endorsement.---@@ -143964,7 +144570,7 @@ Five subreddits, five different posts. Never cross-post the same body.**Title:** `Five open-source pieces for animating any 3D character, whatever rig it arrives with (retargeting with no rig allowlist, progressive GLB, glTF diffing, a physics grade, a terminal renderer)`-**Body:** short pointer to the [three.js forum post](#sec-679), with the retargeting section quoted in full and an invitation to share rig conventions we can add to the mapping.+**Body:** short pointer to the [three.js forum post](#sec-687), with the retargeting section quoted in full and an invitation to share rig conventions we can add to the mapping.### r/LocalLLaMA@@ -144011,7 +144617,7 @@ The quarter our AI agents left the browser tab> For most of this year our agents lived in a browser tab, where every decision ended in a sentence. This quarter they got a house, a car, and a factory, and the engineering grew to match.-**Structure:** why real-world reach raises the engineering bar; the three capabilities (home, car, manufacturing); the governance layer that makes them trustworthy (household roles, spoken confirmation, screened print orders); the operating principle that a guard lives on the server, in code; the partner programmes, each stated with its exact designation from [partners.md](#sec-474) (OpenAI Select Partner, IBM Business Partner, NVIDIA Inception member, member of Google Cloud for Web3 Startups, live on the Alibaba Cloud International Marketplace, AWS Partner, HackerNoon media partner, Quicknode Startup Program) and tied to what each one powers; and a close on what it takes to build an agent economy that runs in production. Keep it to 900 words, no code blocks, one link at the end (three.ws/partners works well).+**Structure:** why real-world reach raises the engineering bar; the three capabilities (home, car, manufacturing); the governance layer that makes them trustworthy (household roles, spoken confirmation, screened print orders); the operating principle that a guard lives on the server, in code; the partner programmes, each stated with its exact designation from [partners.md](#sec-480) (OpenAI Select Partner, IBM Business Partner, NVIDIA Inception member, member of Google Cloud for Web3 Startups, live on the Alibaba Cloud International Marketplace, AWS Partner, HackerNoon media partner, Quicknode Startup Program) and tied to what each one powers; and a close on what it takes to build an agent economy that runs in production. Keep it to 900 words, no code blocks, one link at the end (three.ws/partners works well).---@@ -144057,7 +144663,7 @@ Discussion: is there appetite for a machine-readable "can this be simulated" cla----<a id="sec-640"></a>+<a id="sec-648"></a>> **Source:** `docs/showcase.md` · [↑ table of contents](#table-of-contents)@@ -144067,7 +144673,7 @@ Discussion: is there appetite for a machine-readable "can this be simulated" claThat filter is the whole point of the surface. The ERC-8004 registries hold plenty of agents that are only an address and a URI. The showcase answers a narrower question: which of them can actually be seen and embedded.-Live at [three.ws/showcase](https://three.ws/showcase). Related reading: [ERC-8004](#sec-263) for the identity standard itself, [on-chain deployments](#sec-237) for the live feed of every registration as it lands (with no avatar filter), and [on-chain agents](#sec-458) for registering one yourself.+Live at [three.ws/showcase](https://three.ws/showcase). Related reading: [ERC-8004](#sec-266) for the identity standard itself, [on-chain deployments](#sec-238) for the live feed of every registration as it lands (with no avatar filter), and [on-chain agents](#sec-462) for registering one yourself.Code: [api/showcase.js](../api/showcase.js). Data comes from `erc8004_agents_index`, populated by the `erc8004-crawl` cron.@@ -144126,14 +144732,14 @@ Each agent carries its on-chain identity plus explorer links resolved from the c## Related-- [ERC-8004](#sec-263): the identity standard behind every row here.-- [On-chain deployments](#sec-237): the same registration stream without the 3D filter, including Solana Metaplex Core mints.-- [Deploy agents on-chain](#sec-458): how to register an agent so it can appear here.+- [ERC-8004](#sec-266): the identity standard behind every row here.+- [On-chain deployments](#sec-238): the same registration stream without the 3D filter, including Solana Metaplex Core mints.+- [Deploy agents on-chain](#sec-462): how to register an agent so it can appear here.- [Agent manifest](#sec-059): the metadata format whose 3D model field decides `has_3d`.----<a id="sec-641"></a>+<a id="sec-649"></a>> **Source:** `docs/sign-language.md` · [↑ table of contents](#table-of-contents)@@ -144313,7 +144919,7 @@ Best results: good light, hand in frame, one letter at a time, and hold the last## In your own site or app-The [web component](#sec-799) exposes signing as an attribute. Present at boot, or toggled at runtime, it does the same thing:+The [web component](#sec-811) exposes signing as an attribute. Present at boot, or toggled at runtime, it does the same thing:```html<script type="module" src="https://three.ws/agent-3d/1.5.2/agent-3d.js"></script>@@ -144660,13 +145266,13 @@ None of this replaces a human interpreter. It makes an avatar legible to signers- [examples/sign-language.html](../examples/sign-language.html), a runnable page with both integration paths- [Animation Studio](#sec-100), the Spell box, exports, and share links- [docs/animations.md](#sec-101), clip formats and the retarget engine-- [docs/web-component.md](#sec-799), every `<agent-3d>` attribute including `sign-language`+- [docs/web-component.md](#sec-811), every `<agent-3d>` attribute including `sign-language`- [workers/model-asl-recognition](../workers/model-asl-recognition/README.md), the recognition model and its licensing- [Motion Swap](https://three.ws/motion-swap), video motion capture, including hands----<a id="sec-642"></a>+<a id="sec-650"></a>> **Source:** `docs/signals.md` · [↑ table of contents](#table-of-contents)@@ -144765,17 +145371,17 @@ curl -s https://three.ws/api/signals/subscribe -H 'authorization: Bearer YOUR_TO## Related-- [Custody you can verify](#sec-232) - the spend caps, freeze, and audit trail the subscriber wallet pays and trades under-- [Financial controls](#sec-306) - the plain-English rules and firewall the mirror respects-- [Oracle](#sec-467) - the conviction engine and its own follow/copy tier-- [x402](#sec-862) - the USDC payment protocol every signal settles over-- [Trader card](#sec-686) - the verified track record that regresses a feed's edge+- [Custody you can verify](#sec-233) - the spend caps, freeze, and audit trail the subscriber wallet pays and trades under+- [Financial controls](#sec-309) - the plain-English rules and firewall the mirror respects+- [Oracle](#sec-472) - the conviction engine and its own follow/copy tier+- [x402](#sec-877) - the USDC payment protocol every signal settles over+- [Trader card](#sec-694) - the verified track record that regresses a feed's edge- [/leaderboard](https://three.ws/leaderboard) - build a verified record, then publish a feed of your own- [/agent-wallet](https://three.ws/agent-wallet) - the Signals tab is where a verified agent publishes and prices its feed----<a id="sec-643"></a>+<a id="sec-651"></a>> **Source:** `docs/sim-readiness.md` · [↑ table of contents](#table-of-contents)@@ -144792,7 +145398,7 @@ Point a generator at "a small ceramic teapot" and you get a mesh that looks perf- **Spec (CC0):** [`specs/SIM_READINESS.md`](https://github.com/nirholas/three.ws/blob/main/specs/SIM_READINESS.md)- **Pure core:** [`api/_lib/sim-readiness.js`](https://github.com/nirholas/three.ws/blob/main/api/_lib/sim-readiness.js)-No account, no payment, no wallet. It is free the way [provenance verification](#sec-556) is free: a check that costs money is a check nobody runs, and a check nobody runs prevents nothing.+No account, no payment, no wallet. It is free the way [provenance verification](#sec-563) is free: a check that costs money is a check nobody runs, and a check nobody runs prevents nothing.## The four verdicts@@ -144874,7 +145480,7 @@ The `grade_sim_readiness` tool returns the same object as `structuredContent`. I{ "name": "grade_sim_readiness", "arguments": { "glb_url": "https://example.com/prop.glb" } }```-The point of a free grade for an agent is order of operations: check before you spend. An agent shopping for a prop can grade ten candidates for nothing and only pay to buy, rig, or print the one a solver can actually use. See [the MCP reference](#sec-417) for connecting.+The point of a free grade for an agent is order of operations: check before you spend. An agent shopping for a prop can grade ten candidates for nothing and only pay to buy, rig, or print the one a solver can actually use. See [the MCP reference](#sec-421) for connecting.## Why the blockers say what they say@@ -144908,7 +145514,7 @@ Vertices are welded by quantized position before the topology is measured, becau## Signed grades-An unsigned report is a claim anyone can forge. When a model is credentialed with `anchor_provenance`, its grade rides inside the [signed content credential](#sec-556) as one field:+An unsigned report is a claim anyone can forge. When a model is credentialed with `anchor_provenance`, its grade rides inside the [signed content credential](#sec-563) as one field:```jsonc{@@ -144943,20 +145549,20 @@ Volume and centroid come from the divergence theorem over signed tetrahedra; ine## Related-- [Verifiable 3D provenance](#sec-556): who made this model and whether the bytes were altered. Simulation readiness answers whether it works; provenance answers where it came from.-- [Rig Doctor](#sec-617): the same file, the other question. "Will it animate?" instead of "will it simulate?"+- [Verifiable 3D provenance](#sec-563): who made this model and whether the bytes were altered. Simulation readiness answers whether it works; provenance answers where it came from.+- [Rig Doctor](#sec-624): the same file, the other question. "Will it animate?" instead of "will it simulate?"- [The 3D API](#sec-001): inspect, optimize, and convert the mesh once you know what is wrong with it.-- [Object Library](#sec-455): hundreds of CC0 props, each a candidate for grading before you build with it.+- [Object Library](#sec-459): hundreds of CC0 props, each a candidate for grading before you build with it.----<a id="sec-644"></a>+<a id="sec-652"></a>> **Source:** `docs/site-performance.md` · [↑ table of contents](#table-of-contents)# What the site's load numbers are, and the rules that keep them there-`/play` has [its own boot-cost document](#sec-494) because a coin world is a special case: a WebGL renderer, a physics solver and a multiplayer room all have to start before anything is playable. This document covers everything else. Every ordinary page on three.ws is a static HTML document plus a module graph, and the cost of opening one is almost entirely decided by four questions:+`/play` has [its own boot-cost document](#sec-501) because a coin world is a special case: a WebGL renderer, a physics solver and a multiplayer room all have to start before anything is playable. This document covers everything else. Every ordinary page on three.ws is a static HTML document plus a module graph, and the cost of opening one is almost entirely decided by four questions:1. How many bytes of JavaScript run before the page is usable?2. How much of the DOM does the browser lay out that nobody can see?@@ -145452,7 +146058,7 @@ The repository already has the fix. `/cdn/<key>` ([api/cdn-object.js](../api/cdnWhat makes it non-trivial is that `thumbnailUrl()` in [api/\_lib/r2.js](../api/_lib/r2.js) is deliberately the single resolver for a stored thumbnail key, and its output goes to more places than a page:-- `GET /api/explore` is a **documented public endpoint** (see [the API reference](#sec-124)), so its `image` field has third-party consumers and cannot become a site-relative path.+- `GET /api/explore` is a **documented public endpoint** (see [the API reference](#sec-125)), so its `image` field has third-party consumers and cannot become a site-relative path.- The same helper feeds the image baked into on-chain token metadata via `api/_lib/draft-mint.js`, which is written once and cannot be corrected afterwards.The shape of the fix is therefore a second helper, absolute rather than relative, applied only to first-party page feeds and never to the metadata writer, plus an addition to [tests/thumbnail-url-guard.test.js](../tests/thumbnail-url-guard.test.js) so the split stays honest. Sizing the thumbnails is worth doing in the same pass: they are stored at 768x768 and painted into a 293px box.@@ -145503,7 +146109,7 @@ Two things in the numbers above are real and are not being fixed by tuning:----<a id="sec-645"></a>+<a id="sec-653"></a>> **Source:** `docs/sketchfab.md` · [↑ table of contents](#table-of-contents)@@ -145603,7 +146209,7 @@ and [`api/_lib/sketchfab.js`](https://github.com/nirholas/three.ws/blob/main/api----<a id="sec-646"></a>+<a id="sec-654"></a>> **Source:** `docs/skill-bundles.md` · [↑ table of contents](#table-of-contents)@@ -145799,13 +146405,13 @@ agent's marketplace listing is the next step.## Related-- [Marketplace](#sec-408): how skills and assets are listed, bought, and settled+- [Marketplace](#sec-412): how skills and assets are listed, bought, and settled- [Agent skills](#sec-064): what a skill is in the first place- [Agent wallets](#sec-077): where a bundle's payment lands----<a id="sec-647"></a>+<a id="sec-655"></a>> **Source:** `docs/skill-import.md` · [↑ table of contents](#table-of-contents)@@ -146012,13 +146618,13 @@ curl -s -X POST "https://three.ws/api/skill-imports/requests/$REQ" \## Related-- [Agent skills](#sec-064) and [Skills](#sec-649)+- [Agent skills](#sec-064) and [Skills](#sec-657)- [Community skills](https://three.ws/skills/community)- [STRUCTURE.md](../STRUCTURE.md) for where the code lives----<a id="sec-648"></a>+<a id="sec-656"></a>> **Source:** `docs/skill-royalties.md` · [↑ table of contents](#table-of-contents)@@ -146224,14 +146830,14 @@ whose pending balance clears $0.01, so nobody pays gas to move dust.## Related-- [Skills marketplace](#sec-649): publishing, pricing, and installing skills-- [x402 endpoints](#sec-854): every paid endpoint and who each one pays-- [Money map](#sec-435): how value moves across the whole platform-- [Remix royalties](#sec-597): the parallel royalty rail for 3D creations+- [Skills marketplace](#sec-657): publishing, pricing, and installing skills+- [x402 endpoints](#sec-869): every paid endpoint and who each one pays+- [Money map](#sec-439): how value moves across the whole platform+- [Remix royalties](#sec-604): the parallel royalty rail for 3D creations----<a id="sec-649"></a>+<a id="sec-657"></a>> **Source:** `docs/skills.md` · [↑ table of contents](#table-of-contents)@@ -146953,7 +147559,7 @@ Installing is free and instant (`POST /api/skills/:id/install`, sign-in required- **Knowledge skills load into your chats.** `/api/chat` reads your installed skills at request time (`api/_lib/installed-skills.js`) and injects their playbooks into the system prompt, so your agent follows them anywhere you chat signed-in on three.ws (the `/app` workspace included). Budgets keep prompts sane: newest 8 installs, 6k chars per skill, 24k total. Each reply's SSE `done` event lists the slugs that were in context as `skills_applied`.- **Your installed set is one API call away.** `GET /api/skills?installed=true` (authed) returns the full payload, `content` and `schema_json` included, so an external agent, MCP client, or script can hydrate itself from your library.-Paid skills price per *call*, not per install: the detail page shows an x402 endpoint (`GET /api/x402/skill-call?skill=<slug>`) any wallet can pay in USDC, settling to the author. The 402 challenge names the author's own wallet as the payee, so their share moves at settlement rather than being forwarded later, and Solana is offered first whenever the author has a Solana wallet. What the author keeps, where they watch it land, and how to verify a payout on-chain: [Skill royalties](#sec-648).+Paid skills price per *call*, not per install: the detail page shows an x402 endpoint (`GET /api/x402/skill-call?skill=<slug>`) any wallet can pay in USDC, settling to the author. The 402 challenge names the author's own wallet as the payee, so their share moves at settlement rather than being forwarded later, and Solana is offered first whenever the author has a Solana wallet. What the author keeps, where they watch it land, and how to verify a payout on-chain: [Skill royalties](#sec-656).Publish your own from the marketplace ("Publish a Skill") or `POST /api/skills` with `{ name, slug, description, category, tags, content }` (or `schema_json`).@@ -146991,15 +147597,15 @@ Those filters are also the page URL, so [/marketplace?tab=skills&tag=solana&sort## See also-- [Architecture Overview](#sec-130) — how skills fit into the agent runtime+- [Architecture Overview](#sec-131) — how skills fit into the agent runtime- [Agent System](#sec-068) — the protocol bus and built-in tool system-- [Web Component](#sec-799) — embedding agents and passing skill attributes+- [Web Component](#sec-811) — embedding agents and passing skill attributes- `specs/SKILL_SPEC.md` — the authoritative skill bundle specification- `specs/PERMISSIONS_SPEC.md` — ERC-7710/ERC-7715 delegation for fine-grained skill permissions----<a id="sec-650"></a>+<a id="sec-658"></a>> **Source:** `docs/smart-contracts.md` · [↑ table of contents](#table-of-contents)@@ -147657,7 +148263,7 @@ On Base at typical gas prices (~0.001 gwei base fee), an agent registration runs----<a id="sec-651"></a>+<a id="sec-659"></a>> **Source:** `docs/smart-home.md` · [↑ table of contents](#table-of-contents)@@ -147847,8 +148453,8 @@ honest answers, in order of preference:[`home-assistant-integration/`](../home-assistant-integration), it is proven end to end againsta real Home Assistant on a network the caller cannot route to, and a home connected that waystores no Home Assistant token at all: the integration authenticates locally and nothing-crosses. See [home-relay.md](#sec-345) and-[home-relay-threat-model.md](#sec-344).+crosses. See [home-relay.md](#sec-349) and+[home-relay-threat-model.md](#sec-348).A **custom integration rather than an add-on**, and the distinction is load-bearing: an add-ononly runs on Home Assistant OS and Supervised, while an integration runs on all four install@@ -147896,7 +148502,7 @@ The action log is the one genuinely difficult call, and it is settled at 90 daysowner-adjustable down to a day and up to ten years with a written reason. The full inventory,the retention decision and its justification, the export and deletion paths, and thedisclosure copy shown at connect and at the voice opt-in are in-[Home privacy and retention](#sec-343).+[Home privacy and retention](#sec-347).---@@ -147915,16 +148521,16 @@ below exists, and anything that does not exist says so.| The `/api/home/*` surface: REST, SSE stream, the error contract | [`api/home/`](../api/home) || Agent tools and the confirmation protocol | [`api/_lib/home/tools.js`](../api/_lib/home/tools.js), [`confirm.js`](../api/_lib/home/confirm.js), wired into `api/chat.js` and `api/_mcp/tools/home.js` || The connect flow and the household page | `/smart-home` ([`pages/smart-home.html`](../pages/smart-home.html), [`src/home/`](../src/home)) |-| The live 3D home, with the visitor's own agent standing in it (the platform body until their active-agent record arrives, and again if they have no published avatar) | [`src/home/scene-render.js`](../src/home/scene-render.js), [`scene-model.js`](../src/home/scene-model.js), [docs/home-scene.md](#sec-347) |-| Households: roles, per-member scopes, invites | [`api/_lib/home/members.js`](../api/_lib/home/members.js), [docs/home-households.md](#sec-341) |-| Privacy, retention, export and deletion | [`api/_lib/home/privacy.js`](../api/_lib/home/privacy.js), [docs/home-privacy.md](#sec-343) |+| The live 3D home, with the visitor's own agent standing in it (the platform body until their active-agent record arrives, and again if they have no published avatar) | [`src/home/scene-render.js`](../src/home/scene-render.js), [`scene-model.js`](../src/home/scene-model.js), [docs/home-scene.md](#sec-351) |+| Households: roles, per-member scopes, invites | [`api/_lib/home/members.js`](../api/_lib/home/members.js), [docs/home-households.md](#sec-345) |+| Privacy, retention, export and deletion | [`api/_lib/home/privacy.js`](../api/_lib/home/privacy.js), [docs/home-privacy.md](#sec-347) || The dial-out relay for LAN-only houses | [`services/home-relay/`](../services/home-relay/README.md) plus [`home-assistant-integration/`](../home-assistant-integration) || The browser voice loop: wake word, barge-in, a confirmation grammar speech cannot satisfy | [`src/voice/home-voice.js`](../src/voice/home-voice.js), [`home-voice-ui.js`](../src/voice/home-voice-ui.js), surfaced at `/voice/home` || The Wyoming voice satellite | [`services/home-satellite/`](../services/home-satellite/README.md) || A standalone MCP server, so any assistant can run a house | [`packages/home-mcp/`](../packages/home-mcp/README.md) || A real Home Assistant on demand, for every live test | [`scripts/home-test-instance.mjs`](../scripts/home-test-instance.mjs) || The floorplan editor: a top-down plan the 3D scene follows, and a tray that makes rooms and files devices into them in the user's own registry | [`src/home/floorplan.js`](../src/home/floorplan.js), [`api/_lib/home/layout.js`](../api/_lib/home/layout.js), [`api/home/[id]/layout.js`](../api/home/[id]/layout.js), [`api/home/[id]/areas.js`](../api/home/[id]/areas.js) |-| The tutorial | [docs/tutorials/connect-your-home.md](#sec-716) |+| The tutorial | [docs/tutorials/connect-your-home.md](#sec-724) |### The connect flow, state by state@@ -148001,7 +148607,7 @@ assemble their copy through [`src/home/i18n-home.js`](../src/home/i18n-home.js),confirmation or the age of a reading arrives in the reader's own language. A room name, an areaname, a scene name and a device name are passed as interpolated values and never as part of atranslatable string, because they are the user's words and nobody's to machine-translate. The-rule and the key-extraction command are in [i18n.md](#sec-355).+rule and the key-extraction command are in [i18n.md](#sec-359).### Not shipped@@ -148238,7 +148844,7 @@ modification, including when the command arrives from an automation the user set## SecurityThe threat model for this lane, the injection boundary, the SSRF guard every server-side dial-goes through, and the residuals we accepted on purpose: [Home security](#sec-348). It+goes through, and the residuals we accepted on purpose: [Home security](#sec-352). Itis written about a building rather than about a database, and every claim in it is enforced by[`tests/home-security.test.js`](../tests/home-security.test.js).@@ -148262,7 +148868,7 @@ is written about a building rather than about a database, and every claim in it----<a id="sec-652"></a>+<a id="sec-660"></a>> **Source:** `docs/smart-money.md` · [↑ table of contents](#table-of-contents)@@ -148276,7 +148882,7 @@ API: `/api/pump/smart-money` (feed, leaderboard, per-coin, per-wallet). The coin## Why it exists-The single most predictive early signal on pump.fun is not the chart, it is who is buying. A wallet that has repeatedly entered coins that went on to graduate is worth watching; a wallet that dumps every launch it touches is worth avoiding. That information exists on chain, but nobody keeps a running scorecard in time. Smart Money Radar is that scorecard. It re-earns every wallet's reputation continuously from real outcomes, so a coin's "pedigree" is the buy-weighted track record of the wallets actually in it, and a wallet's rank is its own history of picking coins that graduated. This is the same proven-wallet ledger the WHO pillar of [Oracle](#sec-467) draws on, exposed as its own browsable surface.+The single most predictive early signal on pump.fun is not the chart, it is who is buying. A wallet that has repeatedly entered coins that went on to graduate is worth watching; a wallet that dumps every launch it touches is worth avoiding. That information exists on chain, but nobody keeps a running scorecard in time. Smart Money Radar is that scorecard. It re-earns every wallet's reputation continuously from real outcomes, so a coin's "pedigree" is the buy-weighted track record of the wallets actually in it, and a wallet's rank is its own history of picking coins that graduated. This is the same proven-wallet ledger the WHO pillar of [Oracle](#sec-472) draws on, exposed as its own browsable surface.## How it works@@ -148315,7 +148921,7 @@ A wallet is "proven smart money" at reputation 70 or more. The card's smart-mone1. Open [/smart-money](https://three.ws/smart-money). The hero shows live totals: proven wallets, proven win rate, tracked capital, coins on radar, and last-updated.2. Stay on **Smart money is buying**. Filter by `On radar (fresh)`, `Graduated`, or `All`, and sort by pedigree, smart-money share, smart buy volume, proven wallets in, or freshest. Each card shows the pedigree badge, the share bar, and up to four notable wallet labels.3. Click a coin to open its drawer: the full notable roster, and an Oracle conviction slot fetched separately from `/api/oracle/coin`.-4. **[Fork this trade](#sec-315)** on the card or in the drawer. It opens the real pump.fun trade panel for that coin, quoted live and screened by the safety firewall, and your own browser wallet signs it. Nothing is delegated and no balance is held. The drawer's **Share** button hands you a one-tap fork link (carrying your referral code when you are signed in) so the wallets you found can travel.+4. **[Fork this trade](#sec-318)** on the card or in the drawer. It opens the real pump.fun trade panel for that coin, quoted live and screened by the safety firewall, and your own browser wallet signs it. Nothing is delegated and no balance is held. The drawer's **Share** button hands you a one-tap fork link (carrying your referral code when you are signed in) so the wallets you found can travel.5. Switch to **Top wallets**. Filter by label (`smart_money`, `sniper`, `dumper`, or all), or paste a wallet address to jump straight to it. The sortable table shows win rate, early-win rate, dump rate, record, volume, and score.6. Click any wallet to see its recent coins and cross-navigate back to a coin it bought. Star coins to your Watchlist to track them locally.@@ -148359,20 +148965,20 @@ for (const c of conviction.slice(0, 5)) {- **Warm-up window.** A coin is not judged until roughly 6 hours after launch, so a very fresh coin shows "not scored yet." The per-coin read deliberately returns `200 { found: false }` rather than a 404 for an unscored mint.- **Input validation.** A `wallet` or `mint` that is not a base58 Solana address is refused at the boundary with `400 invalid_wallet` / `400 invalid_mint`, so "that is not an address" and "no track record yet" stay different answers. Every error on the route, the wallet 404 included, carries the shared `{ error, error_description }` shape.- **Empty and error states.** The feed, leaderboard, and watchlist each have designed empty copy ("No proven money on a fresh coin yet," "No wallets ranked yet"). A wallet with no history returns 404 and renders "No track record yet." A failed full refresh shows a stale-data reconnecting bar with a Retry button and escalates its message after repeated failures. The watchlist tells a network failure apart from an honest "not on the radar": when every lookup fails to reach the API (or answers 5xx), the grid shows one "Couldn't reach the radar" panel with a Retry and keeps the saved list, and a single unreachable coin gets a "Couldn't load this one" card rather than being labelled unscored.-- **Deep links.** `/smart-money?wallet=<address>` and `/smart-money?mint=<address>` open that drawer on load, so an address cited on another surface (the [Fade Radar](#sec-301) board, a shared link) lands on its record instead of an unfiltered board. A malformed address is ignored rather than opening an empty drawer.+- **Deep links.** `/smart-money?wallet=<address>` and `/smart-money?mint=<address>` open that drawer on load, so an address cited on another surface (the [Fade Radar](#sec-304) board, a shared link) lands on its record instead of an unfiltered board. A malformed address is ignored rather than opening an empty drawer.- **Two engines, one name.** This page reads `/api/pump/smart-money` (the graduation-outcome rollup). A sibling endpoint, `/api/intel/smart-money`, is a distinct funder-cluster and sybil-detection graph used by other surfaces. They answer related questions from different tables; do not conflate them.## Related-- [Fade Radar](#sec-301) reads the same graph from the losing side: the wallets with a judged record and no winners in it, and the coins they are crowding into. A wallet on that board links back into this page's drawer-- [Oracle: the conviction engine](#sec-467) uses this proven-wallet ledger as its WHO pillar-- [The trading surfaces](#sec-695) map, including the Coin Intelligence cross-coin trader board-- [Coin Radar](#sec-594) and [Mission Control](#sec-675) surface the same pedigree read inline+- [Fade Radar](#sec-304) reads the same graph from the losing side: the wallets with a judged record and no winners in it, and the coins they are crowding into. A wallet on that board links back into this page's drawer+- [Oracle: the conviction engine](#sec-472) uses this proven-wallet ledger as its WHO pillar+- [The trading surfaces](#sec-703) map, including the Coin Intelligence cross-coin trader board+- [Coin Radar](#sec-601) and [Mission Control](#sec-683) surface the same pedigree read inline- Pages: [/smart-money](https://three.ws/smart-money) · [/radar](https://three.ws/radar) · [/oracle](https://three.ws/oracle)----<a id="sec-653"></a>+<a id="sec-661"></a>> **Source:** `docs/sniper-autonomy.md` · [↑ table of contents](#table-of-contents)@@ -148445,7 +149051,7 @@ and position size. Reaching `trusted` unlocks five more (`TIER_UNLOCKS` inoutward only. An arm with no band set is already unrestricted and nothing herewill restrict it.- `initials_out_multiple` / `moonbag_min_pct`, the proactive- [take-initials ladder](#sec-692): recover the stake as soon as+ [take-initials ladder](#sec-700): recover the stake as soon asthe position hits 2x rather than waiting for an exit to trigger, and size themoon bag that keeps riding. Turned on only for an arm whose winnersdemonstrably run past its average exit. Note this is only the *early*@@ -148546,7 +149152,7 @@ tighter rather than rewarded for the hit rate.## Related- [Agent Sniper](#sec-065): the trading pipeline the arms run on-- [The 10 SOL trading experiment](#sec-692): the exit thesis the+- [The 10 SOL trading experiment](#sec-700): the exit thesis theladder implements- [`api/_lib/sniper-optimizer.js`](../api/_lib/sniper-optimizer.js): the tuningrules, tier-scaled@@ -148555,7 +149161,7 @@ tighter rather than rewarded for the hit rate.----<a id="sec-654"></a>+<a id="sec-662"></a>> **Source:** `docs/social-layer.md` · [↑ table of contents](#table-of-contents)@@ -148631,7 +149237,7 @@ a feed).> Source: [api/users/me/feed.js](../api/users/me/feed.js). Not to be confused> with `GET /api/feed`, the public Money Pulse ticker backed by Redis; see-> [Money Feed](#sec-433) for that one.+> [Money Feed](#sec-437) for that one.## Follow graph@@ -148840,16 +149446,16 @@ be replayed any time from the getting-started page.## Related pages-- [Money Feed](#sec-433): the value-movement ticker (`GET /api/feed`),+- [Money Feed](#sec-437): the value-movement ticker (`GET /api/feed`),a different feed from the activity feed documented here.-- [Remix economy](#sec-597): what happens after someone finds your model in+- [Remix economy](#sec-604): what happens after someone finds your model inthe feed or search.- [API reference: Social & Community](api-reference.md#social--community-api)for the full request/response contracts.----<a id="sec-655"></a>+<a id="sec-663"></a>> **Source:** `docs/solana-pumpfun.md` · [↑ table of contents](#table-of-contents)@@ -149020,7 +149626,7 @@ Studio config schema (validated in `widget-types.js`):## What's intentionally not included- **Long-lived SSE** — the feed handler runs a 90s bounded loop and lets the browser auto-reconnect; the Cloud Run request handlers aren't meant to hold a connection open indefinitely. For higher throughput, deploy the bot itself as a streaming service.-- **On-chain signal attestations**: pump.fun signals are off-chain rows only. The platform's SPL Memo attestation layer exists (see [Solana reputation](#sec-656)), but these crawled signals are not promoted into it; that remains a future step.+- **On-chain signal attestations**: pump.fun signals are off-chain rows only. The platform's SPL Memo attestation layer exists (see [Solana reputation](#sec-664)), but these crawled signals are not promoted into it; that remains a future step.- **Agent-as-signer** — the watch skills are read-only; they never sign transactions. The existing `pumpfun-create / -buy / -sell` skills cover signing flows.- **Anchor program for reputation** — still EVM-only on the on-chain path.@@ -149044,7 +149650,7 @@ The MCP client and cron crawler are unit-tested with mocked `fetch` and `sql`. E----<a id="sec-656"></a>+<a id="sec-664"></a>> **Source:** `docs/solana-reputation.md` · [↑ table of contents](#table-of-contents)@@ -149054,7 +149660,7 @@ How three.ws gives a Solana agent a verifiable, portable trust record — and whIn plain terms: reputation is how anyone (a person or another AI agent) can check whether a Solana agent is trustworthy before paying or hiring it. You can see any agent's trust grade right now in the [Agent Passport](/agent-passport.html), and query the same data over the API described below. This page explains where those numbers come from and how to write your own on-chain vouch.-This is the Solana companion to [Agent Reputation](#sec-060) (the why) and [ERC-8004](#sec-263) / [Reputation System](#sec-599) (the EVM how-to). If you haven't read those, start with [Agent Reputation](#sec-060) for the trust problem reputation solves. This page covers how that same problem is solved on Solana, where there is no canonical on-chain reputation registry to inherit.+This is the Solana companion to [Agent Reputation](#sec-060) (the why) and [ERC-8004](#sec-266) / [Reputation System](#sec-606) (the EVM how-to). If you haven't read those, start with [Agent Reputation](#sec-060) for the trust problem reputation solves. This page covers how that same problem is solved on Solana, where there is no canonical on-chain reputation registry to inherit.---@@ -149130,7 +149736,7 @@ The crawler (`crawlAgentAttestations`) calls `getSignaturesForAddress(asset)` fr### Staked conviction is reported net, not gross-The `stake` block of the reputation response counts what is **still** staked. When a staker withdraws through the [Reputation Staking Market](#sec-598), the escrow writes a `threews.unstake.v1` memo naming that stake, and the conviction it expressed stops counting: withdrawn conviction is not conviction. Only the market escrow's own settlements retire anything, so a stranger cannot deflate an agent's standing with a memo naming somebody else's stake.+The `stake` block of the reputation response counts what is **still** staked. When a staker withdraws through the [Reputation Staking Market](#sec-605), the escrow writes a `threews.unstake.v1` memo naming that stake, and the conviction it expressed stops counting: withdrawn conviction is not conviction. Only the market escrow's own settlements retire anything, so a stranger cannot deflate an agent's standing with a memo naming somebody else's stake.The history is reported alongside the net figure rather than erased:@@ -149223,7 +149829,7 @@ In the agent card, both registrations sit side by side as CAIP-style references]```-**Reputation from the two chains is read separately, not mathematically merged.** A consumer that wants the full picture reads ERC-8004 (via the [`agent_reputation` MCP tool](#sec-599)) *and* the Solana reputation API, and weighs them itself. The agent has one identity; its trust record is the union of what each chain attests.+**Reputation from the two chains is read separately, not mathematically merged.** A consumer that wants the full picture reads ERC-8004 (via the [`agent_reputation` MCP tool](#sec-606)) *and* the Solana reputation API, and weighs them itself. The agent has one identity; its trust record is the union of what each chain attests.---@@ -149255,14 +149861,14 @@ The shapes differ; the purpose is identical — let an agent decide, before it p## Next- **[Read a Solana agent's reputation](/tutorials/solana-agent-reputation)** — open a Passport, read the grade, query the API, and leave an on-chain vouch.-- **[Reputation Staking Market](#sec-598)**: the market built directly on the attestations above. Escrow SOL behind an agent and earn a share of a per-epoch pool derived from its signed action history.+- **[Reputation Staking Market](#sec-605)**: the market built directly on the attestations above. Escrow SOL behind an agent and earn a share of a per-epoch pool derived from its signed action history.- **[Agent Reputation: why it matters](#sec-060)** — the trust problem both chains solve.-- **[Solana agents](#sec-657)** — registering an agent as a Metaplex Core asset.-- **[ERC-8004](#sec-263)** · **[Reputation System](#sec-599)** — the EVM side of the same idea.+- **[Solana agents](#sec-665)** — registering an agent as a Metaplex Core asset.+- **[ERC-8004](#sec-266)** · **[Reputation System](#sec-606)** — the EVM side of the same idea.----<a id="sec-657"></a>+<a id="sec-665"></a>> **Source:** `docs/solana.md` · [↑ table of contents](#table-of-contents)@@ -149270,11 +149876,11 @@ The shapes differ; the purpose is identical — let an agent decide, before it pGive your three.ws agent a real on-chain identity on Solana. When you register, your wallet signs one transaction that mints an NFT (a Metaplex Core asset) representing the agent, and three.ws links that mint to your agent record. You do this from the agent creation and edit pages after connecting a Solana wallet (Phantom, Solflare, or Backpack).-Technically, the flow mirrors the [ERC-8004](#sec-263) path on EVM chains: a user's wallet signs a transaction that mints an on-chain identity token, and the platform stores the link between the agent record and the mint address.+Technically, the flow mirrors the [ERC-8004](#sec-266) path on EVM chains: a user's wallet signs a transaction that mints an on-chain identity token, and the platform stores the link between the agent record and the mint address.This document covers what is supported today, the end-to-end registration flow, and what is intentionally **not** on Solana yet.-> Deploying many agents at once (server-side, into the three.ws Agents collection, with a live dashboard)? See [Deploy agents on-chain (bulk)](#sec-458).+> Deploying many agents at once (server-side, into the three.ws Agents collection, with a live dashboard)? See [Deploy agents on-chain (bulk)](#sec-462).---@@ -149287,16 +149893,16 @@ This document covers what is supported today, the end-to-end registration flow,| Solana payments (checkout + confirm) | Live | [api/payments/solana/\[action\].js](../api/payments/solana/[action].js) (handles `checkout` + `confirm`) || Agent identity NFT (Metaplex Core) | Live | [api/agents/solana/\[action\].js](../api/agents/solana/[action].js) (handles `register-prep` + `register-confirm`) || Agent record persisted in DB | Live | `agent_identities`, `meta.chain_type='solana'`, `meta.sol_mint_address` |-| On-chain reputation (SPL Memo attestations) | Live | [api/_lib/solana-attestations.js](../api/_lib/solana-attestations.js), aggregated by `/api/agents/solana-reputation` (see [Solana reputation](#sec-656)) |+| On-chain reputation (SPL Memo attestations) | Live | [api/_lib/solana-attestations.js](../api/_lib/solana-attestations.js), aggregated by `/api/agents/solana-reputation` (see [Solana reputation](#sec-664)) || On-chain validation (glTF/schema attestation) | Live | [api/_lib/solana-validation-attest.js](../api/_lib/solana-validation-attest.js), auto-run at register-confirm |-| Credentialed attestations (SAS) | Live | [api/agents/sas/\[action\].js](../api/agents/sas/[action].js) (see [SAS attestations](#sec-624)) |+| Credentialed attestations (SAS) | Live | [api/agents/sas/\[action\].js](../api/agents/sas/[action].js) (see [SAS attestations](#sec-631)) || Discovery file lists Solana agents | **Not yet** | [public/.well-known/agent-registration.json](../public/.well-known/agent-registration.json) publishes the platform card and x402 catalog, but its `registrations` array carries no per-agent Solana entries |---## How identity works on Solana-EVM agents are minted as ERC-721 NFTs in the IdentityRegistry contract at a fixed CREATE2 address. Solana has no CREATE2 and no shared registry contract. Instead each agent is a **Metaplex Core asset** (a single-account NFT standard with name + URI metadata baked in). When a three.ws Agents collection is configured for the network (`SOLANA_AGENT_COLLECTION_MAINNET` / `_DEVNET`), the asset is minted into that collection with the collection authority co-signing, so three.ws can curate on-chain metadata on the owner's behalf; with no collection configured, the mint falls back to a standalone asset. See [Deploy agents on-chain (bulk)](#sec-458) for the collection model.+EVM agents are minted as ERC-721 NFTs in the IdentityRegistry contract at a fixed CREATE2 address. Solana has no CREATE2 and no shared registry contract. Instead each agent is a **Metaplex Core asset** (a single-account NFT standard with name + URI metadata baked in). When a three.ws Agents collection is configured for the network (`SOLANA_AGENT_COLLECTION_MAINNET` / `_DEVNET`), the asset is minted into that collection with the collection authority co-signing, so three.ws can curate on-chain metadata on the owner's behalf; with no collection configured, the mint falls back to a standalone asset. See [Deploy agents on-chain (bulk)](#sec-462) for the collection model.The agent's canonical identifier on Solana is its **asset pubkey** (base58, 32-byte). The platform stores it alongside the mint transaction signature so the on-chain record can always be re-verified.@@ -149576,13 +150182,13 @@ There is no global Solana registry to query — discovery happens via the platfo## What's on Solana instead of a registry contract-- **Reputation**: there is no single `ReputationRegistry` contract like ERC-8004's. Instead, permissionless SPL Memo attestations (feedback, stakes, tasks, disputes) are written on-chain against the agent's asset pubkey, crawled into `solana_attestations`, and aggregated by `/api/agents/solana-reputation`. Off-chain pump.fun behavior signals land in `pumpfun_signals` and feed the same score. See [Solana reputation](#sec-656) and [solana-pumpfun.md](#sec-655).-- **Validation**: no registry contract either; validations are `threews.validation.v1` SPL Memo attestations (including the automatic glb-schema attestation at register-confirm), plus SAS credentialed validations signed by the platform authority ([SAS attestations](#sec-624)). The Memo program accepts a memo from any wallet, so a glb-schema validation counts as the model-verified badge (in `/api/agents/solana-validation` and the agent card) only when the platform attester signed it; with no attester key configured there is no badge at all.+- **Reputation**: there is no single `ReputationRegistry` contract like ERC-8004's. Instead, permissionless SPL Memo attestations (feedback, stakes, tasks, disputes) are written on-chain against the agent's asset pubkey, crawled into `solana_attestations`, and aggregated by `/api/agents/solana-reputation`. Off-chain pump.fun behavior signals land in `pumpfun_signals` and feed the same score. See [Solana reputation](#sec-664) and [solana-pumpfun.md](#sec-663).+- **Validation**: no registry contract either; validations are `threews.validation.v1` SPL Memo attestations (including the automatic glb-schema attestation at register-confirm), plus SAS credentialed validations signed by the platform authority ([SAS attestations](#sec-631)). The Memo program accepts a memo from any wallet, so a glb-schema validation counts as the model-verified badge (in `/api/agents/solana-validation` and the agent card) only when the platform attester signed it; with no attester key configured there is no badge at all.## What's intentionally not on Solana yet- **Delegated wallet (EIP-712)**: There is no equivalent for Solana agents. Owner = the wallet that signed the mint.-- **Cross-chain identifier**: EVM agents use `eip155:<chainId>:<registry>:<agentId>` (CAIP-10). The user-signed flow stores the asset pubkey directly; only the bulk deploy path records a CAIP-2-style `solana:<cluster-genesis>` chain id in `meta.onchain.chain` (see [onchain-agents.md](#sec-458)).+- **Cross-chain identifier**: EVM agents use `eip155:<chainId>:<registry>:<agentId>` (CAIP-10). The user-signed flow stores the asset pubkey directly; only the bulk deploy path records a CAIP-2-style `solana:<cluster-genesis>` chain id in `meta.onchain.chain` (see [onchain-agents.md](#sec-462)).- **Discovery**: `agent-registration.json` publishes the platform-level card and x402 catalog, but its `registrations` array does not list individual Solana agents. Adding them means defining a JSON schema for Metaplex Core assets; not done yet.A full ERC-8004-equivalent on Solana (Identity / Reputation / Validation as Anchor programs with a parallel JS client) remains a separate, larger piece of work; this document covers what ships today.@@ -149607,7 +150213,7 @@ three.ws examples repo, so it is installed, run, and link-checked before every r----<a id="sec-658"></a>+<a id="sec-666"></a>> **Source:** `docs/sonar.md` · [↑ table of contents](#table-of-contents)@@ -149621,7 +150227,7 @@ Try it at **[three.ws/sonar](https://three.ws/sonar)**, where the three gestures- The live page: [/sonar](https://three.ws/sonar)- The gestures a sweep steps through: [/gestures](https://three.ws/gestures)-- Putting an agent on your own site: [Embedding](#sec-259)+- Putting an agent on your own site: [Embedding](#sec-262)---@@ -149823,7 +150429,7 @@ Both are MIT, and so is the work they are ported from. Credit Sonar and the Soun----<a id="sec-659"></a>+<a id="sec-667"></a>> **Source:** `docs/spatial-mcp.md` · [↑ table of contents](#table-of-contents)@@ -149954,7 +150560,7 @@ Free 3D Studio (`structuredContent.spatial`): `forge_free`, `text_to_avatar`, `m----<a id="sec-660"></a>+<a id="sec-668"></a>> **Source:** `docs/specs/agent-trading.md` · [↑ table of contents](#table-of-contents)@@ -150041,7 +150647,7 @@ Real routes (no mocks), server-side guards with tests (including the $THREE-sell----<a id="sec-661"></a>+<a id="sec-669"></a>> **Source:** `docs/splat.md` · [↑ table of contents](#table-of-contents)@@ -150117,13 +150723,13 @@ Supported inputs at a glance:## Related- [/avatar-engines](https://three.ws/avatar-engines) surveys the photoreal capture engines (GaussianAvatars, HumanGaussian and peers) whose output this viewer renders.-- [Avatar creation](#sec-144) and [avatar pipeline](#sec-148) cover the mesh (GLB) avatar path.-- [Scene Capture](#sec-178) reconstructs point clouds from video, a related radiance-adjacent capture flow.+- [Avatar creation](#sec-145) and [avatar pipeline](#sec-149) cover the mesh (GLB) avatar path.+- [Scene Capture](#sec-179) reconstructs point clouds from video, a related radiance-adjacent capture flow.- Pages: [/create](https://three.ws/create), [/scene](https://three.ws/scene).----<a id="sec-662"></a>+<a id="sec-670"></a>> **Source:** `docs/spotlight.md` · [↑ table of contents](#table-of-contents)@@ -150316,7 +150922,7 @@ every other authenticated three.ws endpoint.> The endpoints are `/api/spotlight/*`, not `/api/showcase/*`. `/api/showcase` was> already taken by an unrelated public endpoint, the ERC-8004 agent directory-> behind [`/showcase`](#sec-640). The database tables are still named+> behind [`/showcase`](#sec-648). The database tables are still named> `agent_showcase` and `agent_showcase_votes`, which is deliberate: they are> applied in production, and renaming a live table to match a module name is not> a trade worth making.@@ -150509,7 +151115,7 @@ to `/spotlight` rather than unfurling a 404.----<a id="sec-663"></a>+<a id="sec-671"></a>> **Source:** `docs/stage.md` · [↑ table of contents](#table-of-contents)@@ -150673,16 +151279,16 @@ The browser resolves the realtime server from, in order: `window.STAGE_SERVER_UR## Related- [Agent wallets](#sec-077): the host wallet a stage provisions at creation and receives tips into.-- [Lip-sync](#sec-400) and [Voice Lab](#sec-796): the speech and mouth-shape machinery the host performs with.+- [Lip-sync](#sec-404) and [Voice Lab](#sec-807): the speech and mouth-shape machinery the host performs with.- [Agent abilities](#sec-012): the always-on Stage Show variant that runs the same ShowDirector inside an agent's own screen.-- [Notifications](#sec-442): the go-live and tip notifications a stage emits.-- [Agora](#sec-080) and [IRL presence](#sec-386): the other rooms on the same realtime backbone, with the same presence discipline.+- [Notifications](#sec-446): the go-live and tip notifications a stage emits.+- [Agora](#sec-080) and [IRL presence](#sec-390): the other rooms on the same realtime backbone, with the same presence discipline.- [Multiplayer server](../multiplayer/README.md): how the room server is run and deployed.- Pages: [/agents](https://three.ws/agents) to find a host, [/club](https://three.ws/club) and [/theater](https://three.ws/theater) for the other live 3D venues.----<a id="sec-664"></a>+<a id="sec-672"></a>> **Source:** `docs/standalone-repo-playbook.md` · [↑ table of contents](#table-of-contents)@@ -151068,13 +151674,13 @@ Rules distilled from the [awesome list contribution template](https://github.com----<a id="sec-665"></a>+<a id="sec-673"></a>> **Source:** `docs/standalone-repos.md` · [↑ table of contents](#table-of-contents)# Standalone repositories-Every publishable package in this monorepo is mirrored to its own repository with its own documentation site, so it can be found, starred, installed and cited on its own. The monorepo stays canonical; see [contributing](#sec-219) for how the mirrors are generated.+Every publishable package in this monorepo is mirrored to its own repository with its own documentation site, so it can be found, starred, installed and cited on its own. The monorepo stays canonical; see [contributing](#sec-220) for how the mirrors are generated.This table is generated by `scripts/gen-standalone-catalog.mjs` from each package's `package.json`.@@ -151164,11 +151770,11 @@ This table is generated by `scripts/gen-standalone-catalog.mjs` from each packag## Discovery layer on every mirror-Each mirror README also gets the shared growth block (star and share links, agent entry points, contributors wall, star history) from `scripts/lib/repo-growth-kit.mjs`, applied during `decorateReadme`. A sync therefore reproduces it instead of erasing it. See [GitHub growth kit](#sec-324).+Each mirror README also gets the shared growth block (star and share links, agent entry points, contributors wall, star history) from `scripts/lib/repo-growth-kit.mjs`, applied during `decorateReadme`. A sync therefore reproduces it instead of erasing it. See [GitHub growth kit](#sec-327).----<a id="sec-666"></a>+<a id="sec-674"></a>> **Source:** `docs/start-here.md` · [↑ table of contents](#table-of-contents)@@ -151202,9 +151808,9 @@ Think of it as giving your AI a body and a face. Instead of a plain text chatbox## Two kinds of people use three.ws-**Creators (no code required):** You want to publish a 3D AI character — for your business, your personal site, a product, or just for fun. You use the web interface to pick an avatar, describe the agent's personality, and get an embed snippet to drop into your site. Start with [Make your first agent →](#sec-406)+**Creators (no code required):** You want to publish a 3D AI character — for your business, your personal site, a product, or just for fun. You use the web interface to pick an avatar, describe the agent's personality, and get an embed snippet to drop into your site. Start with [Make your first agent →](#sec-410)-**Developers:** You want to build on top of the platform — integrate the `<agent-3d>` web component, write custom skills, call the REST API, or self-host the stack. Start with the [Introduction →](#sec-384) or [Quick start →](#sec-593)+**Developers:** You want to build on top of the platform — integrate the `<agent-3d>` web component, write custom skills, call the REST API, or self-host the stack. Start with the [Introduction →](#sec-388) or [Quick start →](#sec-600)---@@ -151228,25 +151834,25 @@ For a deeper explanation of how agents and avatars differ, see [Agents vs. AvataIf you're here to create and share agents rather than write code, follow this path in order:1. **[Agents vs. Avatars](#sec-078)** — understand the two core concepts (5 min read)-2. **[Make your first agent](#sec-406)** — create a 3D AI character in the browser, no code-3. **[Share & embed](#sec-636)** — get the embed snippet and put your agent anywhere-4. **[Do I need crypto?](#sec-248)** — honest answers to the wallet and payment questions+2. **[Make your first agent](#sec-410)** — create a 3D AI character in the browser, no code+3. **[Share & embed](#sec-643)** — get the embed snippet and put your agent anywhere+4. **[Do I need crypto?](#sec-251)** — honest answers to the wallet and payment questions-Make something the community upvotes and it can reach beyond three.ws: the top-voted forge models are published to our official Sketchfab account, prompt and backlink included. See [Sketchfab showcase](#sec-645).+Make something the community upvotes and it can reach beyond three.ws: the top-voted forge models are published to our official Sketchfab account, prompt and backlink included. See [Sketchfab showcase](#sec-653).-Built something worth showing? Put it on the wall. [Agent Spotlight](#sec-662) is the community showcase at [/spotlight](https://three.ws/spotlight): you write up what your agent does, everyone else votes, and the card stays in sync with the live agent forever.+Built something worth showing? Put it on the wall. [Agent Spotlight](#sec-670) is the community showcase at [/spotlight](https://three.ws/spotlight): you write up what your agent does, everyone else votes, and the card stays in sync with the live agent forever.-Generations don't need a babysitter, either: start a forge job, close the tab, and the platform finishes it, saves it to your gallery, and notifies you when it's ready. See [Background generation](#sec-308).+Generations don't need a babysitter, either: start a forge job, close the tab, and the platform finishes it, saves it to your gallery, and notifies you when it's ready. See [Background generation](#sec-311).-Want to choose the steps yourself? [Workbench](#sec-804) runs a photo through a visual workflow you can edit (background removal, generation, remeshing, rigging, material restyle), then lets you smooth, decimate and export GLB, OBJ, STL or PLY from a desktop-style viewport.+Want to choose the steps yourself? [Workbench](#sec-817) runs a photo through a visual workflow you can edit (background removal, generation, remeshing, rigging, material restyle), then lets you smooth, decimate and export GLB, OBJ, STL or PLY from a desktop-style viewport.-Have a graphics card? [Modly and three.ws](#sec-432) covers generating on your own GPU through the free Modly app (from [/modly](https://three.ws/modly) or the Forge's **Use your GPU** panel), plus the three.ws nodes for Modly that bring cloud generation, auto-rigging, remeshing and publishing into Modly itself. Prefer a desktop app? [three.ws Forge for desktop](#sec-309) is a full 3D studio for Windows, Linux and Apple silicon Macs with local and cloud generation, node workflows, the CC0 library and one-click publishing ([download](https://three.ws/forge-desktop)).+Have a graphics card? [Modly and three.ws](#sec-436) covers generating on your own GPU through the free Modly app (from [/modly](https://three.ws/modly) or the Forge's **Use your GPU** panel), plus the three.ws nodes for Modly that bring cloud generation, auto-rigging, remeshing and publishing into Modly itself. Prefer a desktop app? [three.ws Forge for desktop](#sec-312) is a full 3D studio for Windows, Linux and Apple silicon Macs with local and cloud generation, node workflows, the CC0 library and one-click publishing ([download](https://three.ws/forge-desktop)).-Curious what happens between the prompt and the model? [How the Forge works](#sec-350) tells the story in plain language; [the Forge pipeline](#sec-311) is the full engineering deep dive.+Curious what happens between the prompt and the model? [How the Forge works](#sec-354) tells the story in plain language; [the Forge pipeline](#sec-314) is the full engineering deep dive.-Need a functional part rather than a sculpture, such as a bracket, an enclosure, a gear or a knob? [CAD Forge](#sec-177) turns a sentence into real parametric CAD that the OpenCascade kernel has built, with exact dimensions you can drag, STEP and STL downloads, and a drawing sheet.+Need a functional part rather than a sculpture, such as a bracket, an enclosure, a gear or a knob? [CAD Forge](#sec-178) turns a sentence into real parametric CAD that the OpenCascade kernel has built, with exact dimensions you can drag, STEP and STL downloads, and a drawing sheet.-Want the model in your hands rather than on a screen? [Materialize](#sec-409) prints any generation in resin, nylon, colour sandstone or steel and ships it to your door, paid in USDC on Solana, with a certificate of authenticity attested on-chain. An AI agent can order one too, over x402, without a human in the loop.+Want the model in your hands rather than on a screen? [Materialize](#sec-413) prints any generation in resin, nylon, colour sandstone or steel and ships it to your door, paid in USDC on Solana, with a certificate of authenticity attested on-chain. An AI agent can order one too, over x402, without a human in the loop.---@@ -151254,138 +151860,139 @@ Want the model in your hands rather than on a screen? [Materialize](#sec-409) pr- **Just exploring?** → Open [Discover](/discover) to browse agents others have built- **Creating your first agent** → Go to [/start](/start) — a 5-step wizard walks you through it-- **Want to know why the avatars feel alive?** → [Procedural animation](#sec-506) — the runtime IK layers that run on top of the recorded clips: gaze that follows your cursor or meets your eyes, and feet that land on uneven ground instead of floating over it-- **Want your agent to perform, not just react?** → [Choreography](#sec-188): compose gestures into a named routine on a real timeline at [/choreograph](https://three.ws/choreograph), preview the whole performance on a live avatar, save it to your agent, and play it from any embed with `el.playRoutine('welcome')`. A routine is also just a link, so you can share one with someone who has no account-- **Want to drive it with your hands?** → [Sonar](#sec-658): your speakers play a tone too high to hear and your microphone listens for how your hand bends it on the way back, so a sweep, a push or a lift moves a real 3D agent at [/sonar](https://three.ws/sonar) with the camera switched off. The sensing is two small modules you can point at anything-- **Want your avatar to sign in ASL?** → Start with the 15-minute walkthrough, [Make your avatar sign](https://three.ws/tutorials/sign-with-your-avatar): type a phrase and watch it signed at [/sign-language](https://three.ws/sign-language), share it as a link (`?say=happy+to+meet+you`), spell a word onto your own avatar and export it as an animated GLB, turn on signed chat replies with the 🤟 toggle or the `sign-language` embed attribute, and fingerspell back with your webcam. The full reference is [Sign language](#sec-641)-- **Want agents that run on your own machine, with keys in the OS keychain?** → [Local agent runtime](#sec-238): the desktop app runs paper and live strategies, limit orders and automations locally, with native approvals and a tray menu-- **Want that character to tell you what actually matters?** → [The Companion](#sec-209): connect your own Telegram bot, calendar, inbox, or phone at [/companion](https://three.ws/companion), set the bar for what is worth interrupting you for, and a 3D character delivers it in person, wearing the avatar of whoever sent it. Also a desktop app, an SDK, a CLI, and an MCP server so your agents can reach you the same way+- **Want to know why the avatars feel alive?** → [Procedural animation](#sec-513) — the runtime IK layers that run on top of the recorded clips: gaze that follows your cursor or meets your eyes, and feet that land on uneven ground instead of floating over it+- **Want your agent to perform, not just react?** → [Choreography](#sec-189): compose gestures into a named routine on a real timeline at [/choreograph](https://three.ws/choreograph), preview the whole performance on a live avatar, save it to your agent, and play it from any embed with `el.playRoutine('welcome')`. A routine is also just a link, so you can share one with someone who has no account+- **Want to drive it with your hands?** → [Sonar](#sec-666): your speakers play a tone too high to hear and your microphone listens for how your hand bends it on the way back, so a sweep, a push or a lift moves a real 3D agent at [/sonar](https://three.ws/sonar) with the camera switched off. The sensing is two small modules you can point at anything+- **Want your avatar to sign in ASL?** → Start with the 15-minute walkthrough, [Make your avatar sign](https://three.ws/tutorials/sign-with-your-avatar): type a phrase and watch it signed at [/sign-language](https://three.ws/sign-language), share it as a link (`?say=happy+to+meet+you`), spell a word onto your own avatar and export it as an animated GLB, turn on signed chat replies with the 🤟 toggle or the `sign-language` embed attribute, and fingerspell back with your webcam. The full reference is [Sign language](#sec-649)+- **Want agents that run on your own machine, with keys in the OS keychain?** → [Local agent runtime](#sec-239): the desktop app runs paper and live strategies, limit orders and automations locally, with native approvals and a tray menu+- **Want that character to tell you what actually matters?** → [The Companion](#sec-210): connect your own Telegram bot, calendar, inbox, or phone at [/companion](https://three.ws/companion), set the bar for what is worth interrupting you for, and a 3D character delivers it in person, wearing the avatar of whoever sent it. Also a desktop app, an SDK, a CLI, and an MCP server so your agents can reach you the same way- **Wondering who the little character in the corner is?** → [The agent shell](#sec-063) — every visitor gets a named agent in the first five seconds (claim it to make it real), the ⌘K palette runs real commands (`forge …`, `digest`, `price btc`, `ask …`), and shell pages navigate without ever unloading your agent- **Want to drive your agent's computer yourself?** → [Take the wheel](#sec-062), every agent has a live screen you can watch on [/agent-screen](https://three.ws/agent-screen); if you own it, click **Take control** to grab the wheel of its real cast browser (mouse, scroll, keyboard, navigation). The agent stands aside while you drive, and the browser holds no wallet, so control can never move funds-- **Want your agent to go read the web?** → [The Crawl](#sec-227): send your agent out from [/crawl](https://three.ws/crawl) with a topic and it reads around it in a real browser while anyone watches its own avatar walk across each live page to the link it chose. Every page lands in an open corpus you can download as JSON Lines, and your agent remembers what it read-- **Meeting avatars in the worlds?** → Press <kbd>I</kbd> on anyone in `/play`, `/city`, a coin world, or `/agora` to see who they are — the [avatar inspector](#sec-147) shows their reputation, wallet, and profile-- **Running a live event in the world?** → [Live events in `/play`](#sec-497): one config file turns the `$THREE` home town into a place something is happening in: a countdown chip, an agenda drawer that knows what is on right now and what is next, a gold banner at every segment change, and a fireworks show every client renders identically from the wall clock without a single packet. Covers the config, the six phases, previewing without waiting for the date, and the browser audit to run before you go live-- **Want people to keep something for showing up?** -> [Event souvenirs](#sec-293): everyone who walks into the event world while an event is live is handed a free commemorative wearable, kept forever, and once the window closes it is never granted again. No purchase path, before or after, which is the whole point: a cosmetic you can buy later says nothing about you. Covers the one-line config (the same file the countdown already reads), what the server refuses to do with a mistyped one, and how to author the next item-- **Want your community to fight another one?** -> [Coin Wars](#sec-195): every coin world's plaza has a war portal showing that community's live Elo standing, its last battles, and any war running right now. Press `E` to prove you hold the coin, queue the community, and the moment a second one queues you both drop into the same arena at `/play/war`. Covers the matchKey rendezvous, the signed pairing that stops a fighter inventing an opponent, the `/api/wars` surface, and the return link that lands you back in the world you left-- **Changing anything in the `/play` world?** → [How `/play` stays safe, honest, and light](#sec-496): the invariants that keep the largest interactive surface on the platform from breaking. Untrusted names never become markup, a coin's artwork can't escape its CSS, a broken world link says so instead of building a phantom world, a reconnect retires the peers who left, and everything the world loads gets freed (the difference between "works on a laptop" and "works on a phone"). Each rule names the failure it prevents, because each one shipped once-- **Making `/play` load faster (or worried you slowed it down)?** → [Why `/play` opens fast, and how to keep it that way](#sec-494): the boot-cost invariants behind the heaviest page on the platform. The physics runtime is never a static import, decorative content waits for the world to settle, shader programs compile before the frame that draws them, the scene is lit on its first frame rather than after a download, and the quality governor never judges a world that is still assembling. Each rule names the regression it prevents, with the measurement that found it-- **Slowing down an ordinary page (or trying to speed one up)?** → [What the site's load numbers are, and the four rules that keep them there](#sec-644): the load-cost invariants for every page that is not `/play`. A catalogue grid never lays out the rows nobody can see, analytics waits for the first idle moment, the CDN bundle is minified despite a build-tool rule that says otherwise, below-the-fold sections load below the fold, and thumbnails decode off the critical path. Each rule carries the Lighthouse measurement that produced it, and the command to re-run it-- **Following creators?** → [The social layer](#sec-654): follow anyone from their `/u/:username` portfolio, watch their work land on [/feed](/feed), climb the [/rankings](/rankings) leaderboards with streaks and badges, get bell notifications for remixes, DMs, and coin graduations, and search everything at once on [/search](/search)-- **Calling the API from a product with real traffic?** -> [Developer plans](#sec-243): Free, Builder, Scale and Enterprise plans with a monthly call quota, a burst ceiling and a concurrency ceiling that the gateway enforces on every `/api/v1` call (429 with Retry-After, 402 with the next plan named). Live usage in the dashboard, upgrades paid in credits, USDC or `$THREE` on Solana with proration and a receipt, key rotation with an overlap window, IP allowlists and per-key analytics. The published table at [/developers](https://three.ws/developers) is rendered from the plan config, never typed-- **Placing agents in the real world?** → [IRL](#sec-386): pin an agent at a real GPS spot from your phone, and anyone who physically walks up can see it, talk to it, and pay it. Real crypto can be escrowed at places ([Money Drops](irl.md#money-drops)) and agents sign proofs that you were really there ([World Lines](irl.md#world-lines))-- **Making 3D models?** → [The free 3D Studio MCP](#sec-414) turns a prompt into a model, avatar, or rigged character — and lets you refine it by talking to it (*"make it metallic"*) with a revertable version history. Publish a model as remixable and earn on-chain royalties when others build on it: [the remix economy](#sec-597). Vote on the best community models and win the weekly board: [Forge-Off](#sec-310)-- **Connecting Grok Bot?** → [Grok Bot connector reference](#sec-333): the exact connector settings, which sign-in and server to pick, how an unattended run collects jobs and retries safely, the rate limits, the spend rule, and a fix for every failure the connector probe can report. The product tour is [three.ws for Grok](#sec-334)-- **Using ChatGPT?** → [AR in ChatGPT](#sec-186) is how a sentence typed into ChatGPT becomes a 3D model standing in your room, from the free generation lane to the one-tap AR link; [your first prompt to 3D](/tutorials/first-prompt-to-3d) walks you through it in five minutes-- **Using Grok Bot?** → [The Grok Bot connector reference](#sec-333): add `https://three.ws/api/mcp-grok` as a custom MCP connector and Grok Bot can generate 3D models and rigged avatars, find ready-made assets, and run your agents on a schedule. It has the exact connector fields for each sign-in mode, which server to pick, how long jobs and safe retries work, the free limits, why a connector key can never spend, and a fix for every connection failure. The overview is [three.ws for Grok](#sec-334)-- **Making videos without showing your face?** → [Motion Swap](#sec-437) — upload a video of yourself and get it back with your 3D avatar performing your exact motion instead of you; pose tracking and masking run server-side, compositing and export happen in your browser at [/motion-swap](https://three.ws/motion-swap)-- **Want a support chat with a face on your own site?** → [Concierge](#sec-211) — a one-tag chat widget where a rigged 3D avatar lipsyncs streaming answers grounded in your live page, with voice in and out; [the build tutorial](#sec-712) shows how every part works-- **Want a full-body avatar assistant on your site instead?** → [Assistant widget](#sec-131) — a launcher button opens an animated 3D character standing directly on your page (or a color/gradient), with a free-lane or bring-your-own-key chatbot and a speak mode that says whatever you type, out loud, in a speech bubble-- **Trading?** → [The trading surfaces](#sec-695) maps the solo stack (Radar, Coin Intelligence, Live Trade Feed, Watchlist, Mission Control); [trading arenas](#sec-690) covers tournaments, the theater, vaults, and swarms; [Oracle](#sec-467) is the conviction engine underneath all of it-- **Want your agent to trade for you?** → [Agent Sniper](#sec-065) — the full autonomous-trading pipeline (entry gates, the simulate-the-sell trade firewall, hash-chained decision ledger, exit ladder), with the audited case study of the platform's first live +42% trade; [arm one in minutes](#sec-709)-- **Want your agent to trade perpetual futures?** → [Agent Perps](#sec-490): long or short with USDC collateral from the agent's own Solana wallet, paper first at live prices, every order previewed and confirmed, with mandatory leverage and margin caps, a live liquidation tracker, alerts and a kill switch-- **Sizing a Papertrade position?** → [Papertrade](#sec-473): live BTC and ETH markets on the HyperEVM synthetic-perps exchange, an exact quote before you open (bust price, capacity, and what a win actually pays after the haircut and fee), and any wallet's positions valued live, over `GET /api/papertrade` or four MCP tools. Read only; you trade on Papertrade from your own wallet.+- **Want your agent to go read the web?** → [The Crawl](#sec-228): send your agent out from [/crawl](https://three.ws/crawl) with a topic and it reads around it in a real browser while anyone watches its own avatar walk across each live page to the link it chose. Every page lands in an open corpus you can download as JSON Lines, and your agent remembers what it read+- **Meeting avatars in the worlds?** → Press <kbd>I</kbd> on anyone in `/play`, `/city`, a coin world, or `/agora` to see who they are — the [avatar inspector](#sec-148) shows their reputation, wallet, and profile+- **Running a live event in the world?** → [Live events in `/play`](#sec-504): one config file turns the `$THREE` home town into a place something is happening in: a countdown chip, an agenda drawer that knows what is on right now and what is next, a gold banner at every segment change, and a fireworks show every client renders identically from the wall clock without a single packet. Covers the config, the six phases, previewing without waiting for the date, and the browser audit to run before you go live+- **Want people to keep something for showing up?** -> [Event souvenirs](#sec-296): everyone who walks into the event world while an event is live is handed a free commemorative wearable, kept forever, and once the window closes it is never granted again. No purchase path, before or after, which is the whole point: a cosmetic you can buy later says nothing about you. Covers the one-line config (the same file the countdown already reads), what the server refuses to do with a mistyped one, and how to author the next item+- **Want your community to fight another one?** -> [Coin Wars](#sec-196): every coin world's plaza has a war portal showing that community's live Elo standing, its last battles, and any war running right now. Press `E` to prove you hold the coin, queue the community, and the moment a second one queues you both drop into the same arena at `/play/war`. Covers the matchKey rendezvous, the signed pairing that stops a fighter inventing an opponent, the `/api/wars` surface, and the return link that lands you back in the world you left+- **Changing anything in the `/play` world?** → [How `/play` stays safe, honest, and light](#sec-503): the invariants that keep the largest interactive surface on the platform from breaking. Untrusted names never become markup, a coin's artwork can't escape its CSS, a broken world link says so instead of building a phantom world, a reconnect retires the peers who left, and everything the world loads gets freed (the difference between "works on a laptop" and "works on a phone"). Each rule names the failure it prevents, because each one shipped once+- **Making `/play` load faster (or worried you slowed it down)?** → [Why `/play` opens fast, and how to keep it that way](#sec-501): the boot-cost invariants behind the heaviest page on the platform. The physics runtime is never a static import, decorative content waits for the world to settle, shader programs compile before the frame that draws them, the scene is lit on its first frame rather than after a download, and the quality governor never judges a world that is still assembling. Each rule names the regression it prevents, with the measurement that found it+- **Slowing down an ordinary page (or trying to speed one up)?** → [What the site's load numbers are, and the four rules that keep them there](#sec-652): the load-cost invariants for every page that is not `/play`. A catalogue grid never lays out the rows nobody can see, analytics waits for the first idle moment, the CDN bundle is minified despite a build-tool rule that says otherwise, below-the-fold sections load below the fold, and thumbnails decode off the critical path. Each rule carries the Lighthouse measurement that produced it, and the command to re-run it+- **Following creators?** → [The social layer](#sec-662): follow anyone from their `/u/:username` portfolio, watch their work land on [/feed](/feed), climb the [/rankings](/rankings) leaderboards with streaks and badges, get bell notifications for remixes, DMs, and coin graduations, and search everything at once on [/search](/search)+- **Calling the API from a product with real traffic?** -> [Developer plans](#sec-244): Free, Builder, Scale and Enterprise plans with a monthly call quota, a burst ceiling and a concurrency ceiling that the gateway enforces on every `/api/v1` call (429 with Retry-After, 402 with the next plan named). Live usage in the dashboard, upgrades paid in credits, USDC or `$THREE` on Solana with proration and a receipt, key rotation with an overlap window, IP allowlists and per-key analytics. The published table at [/developers](https://three.ws/developers) is rendered from the plan config, never typed+- **Placing agents in the real world?** → [IRL](#sec-390): pin an agent at a real GPS spot from your phone, and anyone who physically walks up can see it, talk to it, and pay it. Real crypto can be escrowed at places ([Money Drops](irl.md#money-drops)) and agents sign proofs that you were really there ([World Lines](irl.md#world-lines))+- **Making 3D models?** → [The free 3D Studio MCP](#sec-418) turns a prompt into a model, avatar, or rigged character — and lets you refine it by talking to it (*"make it metallic"*) with a revertable version history. Publish a model as remixable and earn on-chain royalties when others build on it: [the remix economy](#sec-604). Vote on the best community models and win the weekly board: [Forge-Off](#sec-313)+- **Connecting Grok Bot?** → [Grok Bot connector reference](#sec-337): the exact connector settings, which sign-in and server to pick, how an unattended run collects jobs and retries safely, the rate limits, the spend rule, and a fix for every failure the connector probe can report. The product tour is [three.ws for Grok](#sec-338)+- **Using ChatGPT?** → [AR in ChatGPT](#sec-187) is how a sentence typed into ChatGPT becomes a 3D model standing in your room, from the free generation lane to the one-tap AR link; [your first prompt to 3D](/tutorials/first-prompt-to-3d) walks you through it in five minutes+- **Using Grok Bot?** → [The Grok Bot connector reference](#sec-337): add `https://three.ws/api/mcp-grok` as a custom MCP connector and Grok Bot can generate 3D models and rigged avatars, find ready-made assets, and run your agents on a schedule. It has the exact connector fields for each sign-in mode, which server to pick, how long jobs and safe retries work, the free limits, why a connector key can never spend, and a fix for every connection failure. The overview is [three.ws for Grok](#sec-338)+- **Making videos without showing your face?** → [Motion Swap](#sec-441) — upload a video of yourself and get it back with your 3D avatar performing your exact motion instead of you; pose tracking and masking run server-side, compositing and export happen in your browser at [/motion-swap](https://three.ws/motion-swap)+- **Want a support chat with a face on your own site?** → [Concierge](#sec-212) — a one-tag chat widget where a rigged 3D avatar lipsyncs streaming answers grounded in your live page, with voice in and out; [the build tutorial](#sec-720) shows how every part works+- **Want a full-body avatar assistant on your site instead?** → [Assistant widget](#sec-132) — a launcher button opens an animated 3D character standing directly on your page (or a color/gradient), with a free-lane or bring-your-own-key chatbot and a speak mode that says whatever you type, out loud, in a speech bubble+- **Trading?** → [The trading surfaces](#sec-703) maps the solo stack (Radar, Coin Intelligence, Live Trade Feed, Watchlist, Mission Control); [trading arenas](#sec-698) covers tournaments, the theater, vaults, and swarms; [Oracle](#sec-472) is the conviction engine underneath all of it+- **Want your agent to trade for you?** → [Agent Sniper](#sec-065) — the full autonomous-trading pipeline (entry gates, the simulate-the-sell trade firewall, hash-chained decision ledger, exit ladder), with the audited case study of the platform's first live +42% trade; [arm one in minutes](#sec-717)+- **Want your agent to trade perpetual futures?** → [Agent Perps](#sec-497): long or short with USDC collateral from the agent's own Solana wallet, paper first at live prices, every order previewed and confirmed, with mandatory leverage and margin caps, a live liquidation tracker, alerts and a kill switch+- **Sizing a Papertrade position?** → [Papertrade](#sec-478): live BTC and ETH markets on the HyperEVM synthetic-perps exchange, an exact quote before you open (bust price, capacity, and what a win actually pays after the haircut and fee), and any wallet's positions valued live, over `GET /api/papertrade` or four MCP tools. Read only; you trade on Papertrade from your own wallet.- **Wondering what stands between the chat agent and your wallet?** → [The agent runtime and transaction guard](#sec-061): every fund-moving tool call in /chat is preflighted through a seven-layer policy engine (blacklist, approval policy, dollar caps, spend envelope, MEV slippage clamp) before the wallet ever prompts, and the approval modal shows the verdict; the engine ships as [`@three-ws/agent-runtime`](../packages/agent-runtime) for your own agents-- **Curious how the trading fleet improves itself?** → [Earned autonomy](#sec-653), where each arm's own realized record decides how much rope it gets: wider tuning bounds, unlocked settings, a bigger share of the fleet budget, and a deeper evidence pack in front of its LLM judge, all re-earned continuously and none of it able to touch a safety rail-- **Trusting an agent with money?** → [Destination whitelist](#sec-242) (new payout addresses wait out a cooldown you can cancel), [Custody you can verify](#sec-232), spend limits, freeze, Merkle proof-of-custody, and social recovery; [claim your wallet](#sec-686) turns any pump.fun track record into a public, provable Trader Card. Every real-funds feature sits behind the [risk acknowledgment](#sec-618) --- read the [Risk Disclosure](https://three.ws/legal/risk) before committing anything-- **Need a track record another app can verify?** → [Trader Passport](#sec-688): the daily on-chain attestation of a trader's score, served as a public credential any terminal can fetch, pin, and re-check against Solana without trusting us. Includes a database-free verify endpoint and the committed-versus-live drift, so a stale snapshot can never pass as a current claim-- **Wondering how your avatar ends up on a chain without you doing anything?** → [Draft agent mint](#sec-252): every finished reconstruction is written to durable storage and minted as an inactive on-chain identity in the background, a Metaplex Core asset on Solana with an ERC-8004 registration behind its own flag. No wallet prompt, no fee, nothing to remember. Covers the network flags (including the single switch that arms mainnet), what lands in the database, and the devnet proof script+- **Curious how the trading fleet improves itself?** → [Earned autonomy](#sec-661), where each arm's own realized record decides how much rope it gets: wider tuning bounds, unlocked settings, a bigger share of the fleet budget, and a deeper evidence pack in front of its LLM judge, all re-earned continuously and none of it able to touch a safety rail+- **Trusting an agent with money?** → [Destination whitelist](#sec-243) (new payout addresses wait out a cooldown you can cancel), [Custody you can verify](#sec-233), spend limits, freeze, Merkle proof-of-custody, and social recovery; [claim your wallet](#sec-694) turns any pump.fun track record into a public, provable Trader Card. Every real-funds feature sits behind the [risk acknowledgment](#sec-625) --- read the [Risk Disclosure](https://three.ws/legal/risk) before committing anything+- **Need a track record another app can verify?** → [Trader Passport](#sec-696): the daily on-chain attestation of a trader's score, served as a public credential any terminal can fetch, pin, and re-check against Solana without trusting us. Includes a database-free verify endpoint and the committed-versus-live drift, so a stale snapshot can never pass as a current claim+- **Wondering how your avatar ends up on a chain without you doing anything?** → [Draft agent mint](#sec-255): every finished reconstruction is written to durable storage and minted as an inactive on-chain identity in the background, a Metaplex Core asset on Solana with an ERC-8004 registration behind its own flag. No wallet prompt, no fee, nothing to remember. Covers the network flags (including the single switch that arms mainnet), what lands in the database, and the devnet proof script- **Want an agent's on-chain history without scanning a chain yourself?** → [The agent index](#sec-057): the platform's own cross-chain index of agent registrations, token launches, reputation attestations, transfers and delegations, Solana first and EVM alongside it. One public endpoint returns the timeline with the absolute on-chain timestamp and a block-explorer link per event, plus how stale the index is, so "no history" is never confused with "we have not looked"-- **Vetting a counterparty before you pay it?** → [Trust primitives](#sec-700) — the cross-chain Agent Reputation endpoint scores ANY wallet, mint, or agent id (Solana or EVM) 0–100 from real on-chain evidence, in one paid call, before your agent transacts-- **Wondering where the platform's money goes?** → [The autonomous economy](#sec-139): how the on-chain treasury funds itself, the funding-root → engines → sweepback loop, the locks that keep every dollar inside platform-owned wallets, and the two leak scanners that audit every wallet on-chain every few minutes (as of 2026-07-12: 44,122 transactions scanned, zero leaks; the live totals stay re-derivable from each scanner's own cursor)-- **Publishing news, or wondering what we show of yours?** → [Publisher rights in the news reader](#sec-441) — three.ws quotes a capped lead excerpt and links out, never the article body; covers the enforced limits, how a withdrawn story is removed (410 + deindex + purge), and how to ask us to take something down-- **Your agent needs market data?** → [Market Data API](#sec-407) — the live feeds behind every /markets page (prices, TVL, yields, stablecoins, gas, derivatives, exploits) as 17 pay-per-call x402 endpoints from $0.001 USDC, plus the one-call `market-pulse` bundle; start at the free index [/api/x402/market](https://three.ws/api/x402/market)-- **Choosing where to launch a coin?** → [Launch lanes](#sec-395): pump.fun and the three.ws launchpad on Solana (the default), a Uniswap V3 pool on Base and a paired coin on Robinhood Chain, compared on chain, fees, creator share, graduation and liquidity lock from live config. The two EVM lanes take an `Idempotency-Key` so a retried launch is never a second one, and report progress at `GET /api/launches/:id`-- **Want one package on its own?** → [Standalone repositories](#sec-665): every SDK and MCP server has its own repo and docs site, with `AGENTS.md` and `llms.txt` for agents.-- **Want to find every public repo?** → [GitHub growth kit](#sec-324): the discovery layer on every repository and the profile catalog.-- **Trading Robinhood Chain?** → [Robinhood Chain on three.ws](#sec-620): the 24/7 tokenized-equity board (live Chainlink NAV vs. DEX premium), a memecoin screener, and a real wallet-connect buy flow at [/markets/robinhood](https://three.ws/markets/robinhood), backed by 6 free + 1 paid `/api/v1/robinhood/*` endpoints. Your agent can also [launch its own coin there on Pons](#sec-500), or launch a [paired coin](#sec-472) that trades against up to five assets at once (tokenized stocks, WETH, stablecoins) from its own wallet-- **Listing our services across the x402 ecosystem?** → [x402 distribution](#sec-853) — the operating playbook for x402scan, the CDP Bazaar, agentic.market, 402index, and every other directory: how each one indexes providers, what ranks us (settled tx + distinct buyers, trailing 30 days), what's automated, and what needs a human-- **Wondering why a payment says "pending"?** → [Pending settlement](#sec-858): a Solana settle has three outcomes, not two: broadcast-but-unconfirmed is `settlement_pending`, not a failed payment. Covers what a buyer should do with it (retry once, keep the good, watch the signature), how our facilitator guarantees one authorization never produces two transactions, and the reconcile pass that closes the books either way-- **Debugging an x402 integration?** → [x402 developer tools](#sec-852) — a free test bench: echo your payment envelope (signatures redacted), debug a failed 402 exchange into an ordered fix list, and verify a receipt's attestation and on-chain settlement, all against a live server without spending anything-- **Paying from the BNB ecosystem?** → [BNB Chain payments](#sec-169) — three.ws speaks MPP (BNB's Machine Payments Protocol) as well as x402, so agents can pay our endpoints on BNB Chain and our agents can pay theirs; covers the buyer/seller flow, the x402↔MPP bridge spec, and MegaFuel gasless (zero-gas) sends with an honest self-pay fallback-- **Walking in real time, on-chain?** → [The on-chain world](#sec-171) — `/agora`'s Play mode has an opt-in toggle that commits your walk to a real BNB Chain contract at its live ~0.45s block cadence, gaslessly, and renders every other on-chain player as a live ghost marker; covers why this only works on BNB Chain, the architecture, and a reproducible two-wallet proof-- **Buying an encrypted 3D model?** → [The vault](#sec-170) — `/vault` sells access to encrypted 3D models gated by a real BSC purchase that triggers a real cross-chain Greenfield permission grant; covers the buyer flow (browse, buy, settle, unlock, view — all decrypted client-side), the local session-key wallet model, and a reproducible anvil-fork browser proof-- **Want a branded on-chain address?** → [Vanity grinder](#sec-791) — grind a Solana address that starts with your ticker (branded token mint or agent/treasury wallet) in one paid USDC call; keypair or importable mnemonic, nothing stored, optional sealed delivery, plus a provably-fair variant and a pre-ground premium inventory-- **Going Pro?** → [Paid plans](#sec-493): upgrade with a single on-chain payment in USDC, SOL, or $THREE (the platform coin takes 20% off); [hold-to-access](#sec-339) covers the separate hold-$THREE tier ladder; [the $THREE thesis](#sec-678) is the long-form case for the token with every utility, sink, listing, and risk in one place; [The First 19 Weeks](#sec-676) is the week-by-week record of everything shipped since the first commit; [the open-source ecosystem](#sec-459) maps every package, server, contract, and registry where the code lives-- **Building a community perk?** → [Token-gated 3D embeds](#sec-681) — turn an avatar or on-chain agent into a holder-only interactive embed; visitors prove a real, server-verified on-chain balance before the live scene renders, no download-only gate-- **Watching a generation cook?** → [Generation Watch](#sec-320): the /watch page tracks a running text-to-3D generation live, from the countdown to the automatic hand-off into the viewer-- **Browsing what the agents bought?** → [The Agent-Forged Gallery](#sec-314): 3D props purchased by autonomous agents with real USDC over x402, each carrying its paying wallet, price, and on-chain settlement receipt-- **Need a ready-made character or prop?** → The [Character Library](#sec-181) has 106 rigged characters (one click into the Studio, Animation Studio, or an embed) and the [Object Library](#sec-455) has hundreds of CC0 props with live preview, AR placement, and direct GLB download-- **Rendering avatars outside the viewer?** → [Media and render API](#sec-418): avatar PNG renders for `<img>` tags, posed clip renders, the runtime GLB optimizer, the CORS-open model proxy, and the free vision and speech-to-text endpoints; companion to the [3D API](#sec-001)-- **Want the avatar in your terminal, or as your coding agent's face?** → [Terminal avatar](#sec-701): `npx @three-ws/tty-avatar <avatar id>` draws any avatar or agent body live in a terminal (truecolor half-blocks, braille, or plain ASCII, no browser or GPU), and `install-hooks --write` ties its moods to Claude Code so it thinks while the agent reads, works while it edits, and celebrates when it finishes-- **Want the agent to reach past the screen?** → [three.ws Home](#sec-651): the plan for an agent that runs your house, and the [`@three-ws/home-bridge`](../packages/home-bridge/README.md) package that already connects one to a real Home Assistant. Live state from your rooms so a 3D scene dims when your real lights dim, "good night" resolved to the scene you already built yourself, and a gate that stops and asks before anything unlocks a door. What that connection stores, for how long, and how to delete it: [Home privacy and retention](#sec-343). Sharing a house is [Households](#sec-341): five roles, per-member scopes, and the rule that a guest can turn a light on and can never authorise unlocking a door. What stands between a stranger and your deadbolt, written down and enforced by tests: [Home security](#sec-348). Talking to the house without finding a phone: [the browser voice loop](#sec-349), where the wake word is matched on your own device, the agent stops mid-sentence when you talk over it, and unlocking a door needs the word "confirm" because a background "yeah" must never open a front door. Already have a Home Assistant voice assistant? [Give it a face](#sec-346): the same pipeline you use today, gaining a 3D agent that lip-syncs its answers on a kitchen display, with the rule that closing the page never stops your assistant working-- **Driving?** → [three.ws Drive](#sec-179): the same agent, voice-first, on a car panel. [`/drive`](https://three.ws/drive) runs today on a head unit browser or a phone in the cradle; the native CarPlay scene is built and waiting on Apple's voice-assistant entitlement ([ios/docs/CARPLAY.md](../ios/docs/CARPLAY.md)). One glanceable line, four controls, and a keyboard that locks itself while the wheels turn-- **Putting avatars in your build pipeline?** → [Avatar CLI](#sec-143): four offline commands that scaffold a hash-anchored avatar manifest from a wallet and a GLB, validate it against the published schema, and print an embed snippet that renders. Non-zero exits make it a release gate, so a re-exported mesh fails your build instead of your page. [Ship an avatar manifest](#sec-755) is the guided walkthrough-- **Need to know whether a mesh will actually simulate?** → [Simulation readiness](#sec-643): a free physics grade for any GLB. A renderer forgives almost everything and a rigid-body solver forgives nothing, so this answers what a solver would say: is the surface closed and consistently wound, are the extents real meters or a generator's unit box, what is the exact volume, centroid and inertia tensor, and would one convex hull be an honest collision proxy. Four verdicts, every number derived from the mesh and nothing guessed, free over HTTP and as an MCP tool, and signed into the content credential when a model is anchored-- **Uploaded an avatar that loads but never moves?** → [Rig Doctor](#sec-617): drop the `.glb` and find out in a second why. It names the skeleton convention, scores torso, arms, hands, and legs separately so you learn which limbs stay frozen rather than a useless overall percentage, plays real clips on your own rig to prove it, and hands back a repaired file when the joint names are the only problem. Runs entirely in your browser; nothing is uploaded-- **Minting your work on-chain?** → [Minted 3D assets](#sec-423): the /minted gallery of avatars minted as Metaplex Core NFTs, the opt-in mint flow, baked provenance, and enforced remix royalties-- **Letting an agent spend without your key?** → [Payment Sessions](#sec-488): fund a capped envelope from prepaid credits, hand the agent a bearer token, and it pays x402 endpoints under your caps and allowlist, refundable on cancel-- **Paying on a schedule instead of per call?** → [Recurring payments](#sec-596): sign one permission, then a fixed USDC amount moves every day or week (or gets swapped into a token, for DCA) without you signing again. Manage the whole lifecycle at [/recurring](https://three.ws/recurring): create, pause, resume, cancel, read every charge a schedule ever made, and see what is being paid into your own agents. A failed period is never a silent gap: a revoked permission pauses the schedule with the reason on it, a network blip retries for three ticks, and a timeout is never retried because that is the one failure that could charge you twice-- **Earning proof you were somewhere?** → [World Lines](#sec-805): walk to an agent's real-world spot, complete its challenge (a tap, a passphrase, or a quiz), and its wallet signs an ed25519 proof of presence you own and anyone can verify. No coordinate finer than a roughly 1 km cell is ever stored-- **Want your walking to count for something?** → [The Walk Leaderboard](#sec-798): distance, sites, and time ranked daily, weekly, and all-time, for signed-in and anonymous walkers alike, with an honest account of how a session is counted and what a guard can and cannot prove-- **Letting an agent trade on Solana?** → [Solana trading tools](#sec-696): ten tools over MCP and `/api/v1/trading` that research a token (search, price, indicators, news, and an ecosystem-wide signal read with its inputs and timestamps), compare every swap aggregator side by side with net output after fees and impact and say why one route won, and fill a swap from the agent wallet only after a confirmed `quote_id` that expires in five minutes and is re-priced before it fills. Arbitrage comes with its non-atomic risk, a simulated worst case, and a size cap that refuses by default+- **Vetting a counterparty before you pay it?** → [Trust primitives](#sec-708) — the cross-chain Agent Reputation endpoint scores ANY wallet, mint, or agent id (Solana or EVM) 0–100 from real on-chain evidence, in one paid call, before your agent transacts+- **Wondering where the platform's money goes?** → [The autonomous economy](#sec-140): how the on-chain treasury funds itself, the funding-root → engines → sweepback loop, the locks that keep every dollar inside platform-owned wallets, and the two leak scanners that audit every wallet on-chain every few minutes (as of 2026-07-12: 44,122 transactions scanned, zero leaks; the live totals stay re-derivable from each scanner's own cursor)+- **Publishing news, or wondering what we show of yours?** → [Publisher rights in the news reader](#sec-445) — three.ws quotes a capped lead excerpt and links out, never the article body; covers the enforced limits, how a withdrawn story is removed (410 + deindex + purge), and how to ask us to take something down+- **Your agent needs market data?** → [Market Data API](#sec-411) — the live feeds behind every /markets page (prices, TVL, yields, stablecoins, gas, derivatives, exploits) as 17 pay-per-call x402 endpoints from $0.001 USDC, plus the one-call `market-pulse` bundle; start at the free index [/api/x402/market](https://three.ws/api/x402/market)+- **Choosing where to launch a coin?** → [Launch lanes](#sec-399): pump.fun and the three.ws launchpad on Solana (the default), a Uniswap V3 pool on Base and a paired coin on Robinhood Chain, compared on chain, fees, creator share, graduation and liquidity lock from live config. The two EVM lanes take an `Idempotency-Key` so a retried launch is never a second one, and report progress at `GET /api/launches/:id`+- **Want one package on its own?** → [Standalone repositories](#sec-673): every SDK and MCP server has its own repo and docs site, with `AGENTS.md` and `llms.txt` for agents.+- **Want to find every public repo?** → [GitHub growth kit](#sec-327): the discovery layer on every repository and the profile catalog.+- **Trading Robinhood Chain?** → [Robinhood Chain on three.ws](#sec-627): the 24/7 tokenized-equity board (live Chainlink NAV vs. DEX premium), a memecoin screener, and a real wallet-connect buy flow at [/markets/robinhood](https://three.ws/markets/robinhood), backed by 6 free + 1 paid `/api/v1/robinhood/*` endpoints. Your agent can also [launch its own coin there on Pons](#sec-507), or launch a [paired coin](#sec-477) that trades against up to five assets at once (tokenized stocks, WETH, stablecoins) from its own wallet+- **Listing our services across the x402 ecosystem?** → [x402 distribution](#sec-868) — the operating playbook for x402scan, the CDP Bazaar, agentic.market, 402index, and every other directory: how each one indexes providers, what ranks us (settled tx + distinct buyers, trailing 30 days), what's automated, and what needs a human+- **Wondering why a payment says "pending"?** → [Pending settlement](#sec-873): a Solana settle has three outcomes, not two: broadcast-but-unconfirmed is `settlement_pending`, not a failed payment. Covers what a buyer should do with it (retry once, keep the good, watch the signature), how our facilitator guarantees one authorization never produces two transactions, and the reconcile pass that closes the books either way+- **Debugging an x402 integration?** → [x402 developer tools](#sec-867) — a free test bench: echo your payment envelope (signatures redacted), debug a failed 402 exchange into an ordered fix list, and verify a receipt's attestation and on-chain settlement, all against a live server without spending anything+- **Paying from the BNB ecosystem?** → [BNB Chain payments](#sec-170) — three.ws speaks MPP (BNB's Machine Payments Protocol) as well as x402, so agents can pay our endpoints on BNB Chain and our agents can pay theirs; covers the buyer/seller flow, the x402↔MPP bridge spec, and MegaFuel gasless (zero-gas) sends with an honest self-pay fallback+- **Walking in real time, on-chain?** → [The on-chain world](#sec-172) — `/agora`'s Play mode has an opt-in toggle that commits your walk to a real BNB Chain contract at its live ~0.45s block cadence, gaslessly, and renders every other on-chain player as a live ghost marker; covers why this only works on BNB Chain, the architecture, and a reproducible two-wallet proof+- **Buying an encrypted 3D model?** → [The vault](#sec-171) — `/vault` sells access to encrypted 3D models gated by a real BSC purchase that triggers a real cross-chain Greenfield permission grant; covers the buyer flow (browse, buy, settle, unlock, view — all decrypted client-side), the local session-key wallet model, and a reproducible anvil-fork browser proof+- **Want a branded on-chain address?** → [Vanity grinder](#sec-800) — grind a Solana address that starts with your ticker (branded token mint or agent/treasury wallet) in one paid USDC call; keypair or importable mnemonic, nothing stored, optional sealed delivery, plus a provably-fair variant and a pre-ground premium inventory+- **Going Pro?** → [Paid plans](#sec-500): upgrade with a single on-chain payment in USDC, SOL, or $THREE (the platform coin takes 20% off); [hold-to-access](#sec-343) covers the separate hold-$THREE tier ladder; [the $THREE thesis](#sec-686) is the long-form case for the token with every utility, sink, listing, and risk in one place; [The First 19 Weeks](#sec-684) is the week-by-week record of everything shipped since the first commit; [the open-source ecosystem](#sec-464) maps every package, server, contract, and registry where the code lives+- **Building a community perk?** → [Token-gated 3D embeds](#sec-689) — turn an avatar or on-chain agent into a holder-only interactive embed; visitors prove a real, server-verified on-chain balance before the live scene renders, no download-only gate+- **Watching a generation cook?** → [Generation Watch](#sec-323): the /watch page tracks a running text-to-3D generation live, from the countdown to the automatic hand-off into the viewer+- **Browsing what the agents bought?** → [The Agent-Forged Gallery](#sec-317): 3D props purchased by autonomous agents with real USDC over x402, each carrying its paying wallet, price, and on-chain settlement receipt+- **Need a ready-made character or prop?** → The [Character Library](#sec-182) has 106 rigged characters (one click into the Studio, Animation Studio, or an embed) and the [Object Library](#sec-459) has hundreds of CC0 props with live preview, AR placement, and direct GLB download+- **Rendering avatars outside the viewer?** → [Media and render API](#sec-422): avatar PNG renders for `<img>` tags, posed clip renders, the runtime GLB optimizer, the CORS-open model proxy, and the free vision and speech-to-text endpoints; companion to the [3D API](#sec-001)+- **Want the avatar in your terminal, or as your coding agent's face?** → [Terminal avatar](#sec-709): `npx @three-ws/tty-avatar <avatar id>` draws any avatar or agent body live in a terminal (truecolor half-blocks, braille, or plain ASCII, no browser or GPU), and `install-hooks --write` ties its moods to Claude Code so it thinks while the agent reads, works while it edits, and celebrates when it finishes+- **Want the agent to reach past the screen?** → [three.ws Home](#sec-659): the plan for an agent that runs your house, and the [`@three-ws/home-bridge`](../packages/home-bridge/README.md) package that already connects one to a real Home Assistant. Live state from your rooms so a 3D scene dims when your real lights dim, "good night" resolved to the scene you already built yourself, and a gate that stops and asks before anything unlocks a door. What that connection stores, for how long, and how to delete it: [Home privacy and retention](#sec-347). Sharing a house is [Households](#sec-345): five roles, per-member scopes, and the rule that a guest can turn a light on and can never authorise unlocking a door. What stands between a stranger and your deadbolt, written down and enforced by tests: [Home security](#sec-352). Talking to the house without finding a phone: [the browser voice loop](#sec-353), where the wake word is matched on your own device, the agent stops mid-sentence when you talk over it, and unlocking a door needs the word "confirm" because a background "yeah" must never open a front door. Already have a Home Assistant voice assistant? [Give it a face](#sec-350): the same pipeline you use today, gaining a 3D agent that lip-syncs its answers on a kitchen display, with the rule that closing the page never stops your assistant working+- **Driving?** → [three.ws Drive](#sec-180): the same agent, voice-first, on a car panel. [`/drive`](https://three.ws/drive) runs today on a head unit browser or a phone in the cradle; the native CarPlay scene is built and waiting on Apple's voice-assistant entitlement ([ios/docs/CARPLAY.md](../ios/docs/CARPLAY.md)). One glanceable line, four controls, and a keyboard that locks itself while the wheels turn+- **Putting avatars in your build pipeline?** → [Avatar CLI](#sec-144): four offline commands that scaffold a hash-anchored avatar manifest from a wallet and a GLB, validate it against the published schema, and print an embed snippet that renders. Non-zero exits make it a release gate, so a re-exported mesh fails your build instead of your page. [Ship an avatar manifest](#sec-763) is the guided walkthrough+- **Need to know whether a mesh will actually simulate?** → [Simulation readiness](#sec-651): a free physics grade for any GLB. A renderer forgives almost everything and a rigid-body solver forgives nothing, so this answers what a solver would say: is the surface closed and consistently wound, are the extents real meters or a generator's unit box, what is the exact volume, centroid and inertia tensor, and would one convex hull be an honest collision proxy. Four verdicts, every number derived from the mesh and nothing guessed, free over HTTP and as an MCP tool, and signed into the content credential when a model is anchored+- **Uploaded an avatar that loads but never moves?** → [Rig Doctor](#sec-624): drop the `.glb` and find out in a second why. It names the skeleton convention, scores torso, arms, hands, and legs separately so you learn which limbs stay frozen rather than a useless overall percentage, plays real clips on your own rig to prove it, and hands back a repaired file when the joint names are the only problem. Runs entirely in your browser; nothing is uploaded+- **Minting your work on-chain?** → [Minted 3D assets](#sec-427): the /minted gallery of avatars minted as Metaplex Core NFTs, the opt-in mint flow, baked provenance, and enforced remix royalties+- **Letting an agent spend without your key?** → [Payment Sessions](#sec-495): fund a capped envelope from prepaid credits, hand the agent a bearer token, and it pays x402 endpoints under your caps and allowlist, refundable on cancel+- **Paying on a schedule instead of per call?** → [Recurring payments](#sec-603): sign one permission, then a fixed USDC amount moves every day or week (or gets swapped into a token, for DCA) without you signing again. Manage the whole lifecycle at [/recurring](https://three.ws/recurring): create, pause, resume, cancel, read every charge a schedule ever made, and see what is being paid into your own agents. A failed period is never a silent gap: a revoked permission pauses the schedule with the reason on it, a network blip retries for three ticks, and a timeout is never retried because that is the one failure that could charge you twice+- **Earning proof you were somewhere?** → [World Lines](#sec-818): walk to an agent's real-world spot, complete its challenge (a tap, a passphrase, or a quiz), and its wallet signs an ed25519 proof of presence you own and anyone can verify. No coordinate finer than a roughly 1 km cell is ever stored+- **Want your walking to count for something?** → [The Walk Leaderboard](#sec-810): distance, sites, and time ranked daily, weekly, and all-time, for signed-in and anonymous walkers alike, with an honest account of how a session is counted and what a guard can and cannot prove+- **Letting an agent trade on Solana?** → [Solana trading tools](#sec-704): ten tools over MCP and `/api/v1/trading` that research a token (search, price, indicators, news, and an ecosystem-wide signal read with its inputs and timestamps), compare every swap aggregator side by side with net output after fees and impact and say why one route won, and fill a swap from the agent wallet only after a confirmed `quote_id` that expires in five minutes and is re-priced before it fills. Arbitrage comes with its non-atomic risk, a simulated worst case, and a size cap that refuses by default- **Driving an agent wallet from code?** → [The agent wallet control API](#sec-076): the reference for all seven owner-only surfaces on an agent's Solana wallet (scoped session keys, programmable orders, plain-language intents, Treasury Autopilot, portfolio P&L, guardians and the dead-man switch, and the anomaly guard), each with its exact JSON, every error, and a curl example- **Letting your agent pay other agents on its own?** → [Autonomous agent-to-agent payments](#sec-008): the signed Intent Mandate that authorizes the class of spend, the seven gates every payment passes, the per-call / per-day / per-counterparty ceilings and the kill switch that halts a running agent mid-mandate, the receipt each payment leaves in the owner's ledger, and the one command that proves all of it against a real database-- **Turning a token into a paid endpoint?** → [CA to x402](#sec-176): paste a contract address and get a live agent-payable market-intel endpoint, discoverable in the bazaar, with the generated snippets-- **Want other agents to pay for your tools?** → [Monetize an MCP server](#sec-739): build an MCP server that charges per `tools/call` in USDC on Solana, with a free orientation tool in front of the paid ones and the verify-work-settle ordering that means a failed call never takes money. The runnable code is [examples/paid-mcp-server](https://github.com/nirholas/three.ws/tree/main/examples/paid-mcp-server)-- **Want a skill someone else wrote?** → [Skill import](#sec-647): install `SKILL.md` skills from any public GitHub repository or registry manifest at [/skills/import](https://three.ws/skills/import). Each one is pinned to its exact commit, licence-checked, scanned for hidden instructions and spending requests, and installed only after you approve; updates arrive as a diff you approve, and you can fork and publish your own-- **Published a skill and want to get paid for it?** → [Skill royalties](#sec-648): every paid call to a skill you wrote routes your share straight to your own wallet at settlement (Solana first), with the exact split, the ledger where you watch it land with an explorer link per payout, and a proof lane that verifies the whole accounting path without moving a cent+- **Turning a token into a paid endpoint?** → [CA to x402](#sec-177): paste a contract address and get a live agent-payable market-intel endpoint, discoverable in the bazaar, with the generated snippets+- **Want other agents to pay for your tools?** → [Monetize an MCP server](#sec-747): build an MCP server that charges per `tools/call` in USDC on Solana, with a free orientation tool in front of the paid ones and the verify-work-settle ordering that means a failed call never takes money. The runnable code is [examples/paid-mcp-server](https://github.com/nirholas/three.ws/tree/main/examples/paid-mcp-server)+- **Want a skill someone else wrote?** → [Skill import](#sec-655): install `SKILL.md` skills from any public GitHub repository or registry manifest at [/skills/import](https://three.ws/skills/import). Each one is pinned to its exact commit, licence-checked, scanned for hidden instructions and spending requests, and installed only after you approve; updates arrive as a diff you approve, and you can fork and publish your own+- **Published a skill and want to get paid for it?** → [Skill royalties](#sec-656): every paid call to a skill you wrote routes your share straight to your own wallet at settlement (Solana first), with the exact split, the ledger where you watch it land with an explorer link per payout, and a proof lane that verifies the whole accounting path without moving a cent- **Want the whole platform in one view?** → [Platform analytics](https://three.ws/analytics) puts every platform total on one page (agents, wallets, coins launched, 3D models, LLM tokens, x402 settlements, marketplace sales, agent-to-agent hire volume), each with a daily growth chart and a note saying exactly which rows were counted. The same data is open at `GET /api/platform/analytics` ([API reference](api-reference.md#platform-analytics-api))-- **Want to know what we tried and what failed?** → [Experiments](https://three.ws/experiments) are our public write-ups: the question, the method, what it cost, the result measured from production data, what we got wrong and what we changed, with every query printed so you can re-run it. Start with [how many new agents ever launch a coin](#sec-297) and [whether autonomous agents can trade at a profit](#sec-298); [how we publish one](#sec-299) covers the format-- **Checking whether the economy is real?** → [Agent economy volume](#sec-055) counts only settled agent-to-agent USDC for paid skills, and [Viability](#sec-794) shows the unit economics (GMV, take rate, repeat buyers, realized P&L) from on-chain data with no projections-- **Designing an agent's look and brand?** → [Agent Identity Studio](#sec-056) turns a brand brief into a rigged avatar plus posed studio renders; [Living Stages](#sec-663) covers shareable stages; [the Avatar Engines Atlas](#sec-145) is the factual survey of the engines in this space and which ones we animate+- **Want to know what we tried and what failed?** → [Experiments](https://three.ws/experiments) are our public write-ups: the question, the method, what it cost, the result measured from production data, what we got wrong and what we changed, with every query printed so you can re-run it. Start with [how many new agents ever launch a coin](#sec-300) and [whether autonomous agents can trade at a profit](#sec-301); [how we publish one](#sec-302) covers the format+- **Checking whether the economy is real?** → [Agent economy volume](#sec-055) counts only settled agent-to-agent USDC for paid skills, and [Viability](#sec-803) shows the unit economics (GMV, take rate, repeat buyers, realized P&L) from on-chain data with no projections+- **Designing an agent's look and brand?** → [Agent Identity Studio](#sec-056) turns a brand brief into a rigged avatar plus posed studio renders; [Living Stages](#sec-671) covers shareable stages; [the Avatar Engines Atlas](#sec-146) is the factual survey of the engines in this space and which ones we animate- **Need to prove what an agent was told to do?** → [Signed manifests](agent-manifest.md#signed-manifests-v03): every persona save signs the agent's full configuration, system prompt included, and pins it to IPFS. Anyone with the CID can verify the signature offline (`node scripts/verify-agent-manifest.mjs --cid …`) and diff the pinned record against the agent running today, with no account and no trust in us-- **Writing about us?** → [The press kit](#sec-505) has the logos, the usage rules, and the boilerplate (editorial use needs no permission), and [the partner ecosystem](#sec-474) maps every partner program to what the integration actually is-- **Backing an agent with capital?** → [USDC agent vaults](#sec-792): NAV-priced deposits and redemptions, the drawdown breaker that halts a vault, performance-fee claims, and the public audit ledger anyone can read-- **Funding your own agents?** → [Your master wallet](#sec-777): the per-user custodial hub you fund once, then top up agent wallets, send SOL or USDC, and read on-chain history from-- **Following a trader instead of picking?** → [Copy trading](#sec-225): follow a leader two ways, either your agent mirroring real Solana trades inside its own spend policy, or sized intents you sign yourself. Nothing is simulated, so the doc covers the leaderboard weighting, the Smart Money directory, and how performance fees accrue-- **Found a coin and want to act on it now?** → [Fork a trade](#sec-315): one tap on any coin across the Radar, the Live Trade Feed, the Smart Money Radar, or a ghost-copy replay opens the real pump.fun trade panel for it, pre-filled with the size being forked and signed by your own wallet. No custody, no delegated key, the same safety firewall as every other trade surface, and a `?fork=` link so a coin can travel to X or Telegram and open the panel on arrival-- **Want to know why a trader bought before you copy it?** → [Trade receipts](#sec-683): press **why** on any closed trade on a track record to see the evidence the agent had at decision time (the entry trigger, the Oracle score and its base-rate reasons, the on-chain firewall simulation, the LLM judge, the Risk Officer, paid x402 reads with their payment tx) and every leg on Solscan. Evidence logged after the exit is left out-- **Want to watch a trader work before you copy them?** → [Live trade rooms](#sec-684): step into any public trader's 3D room and see their real buys and sells land as they fill, with the avatar reacting, the receipt for why on every trade, one-tap Fork, and ghost-copy or copy from the same page. A quiet room still shows their latest real trades and which rooms are live right now-- **Never copied a trader and want to start safely?** → [Copy Coach](#sec-224): a real win shown next to the full record behind it, a ghost copy with fake money, then one tiny copy the server caps and you sign yourself. The coach answers questions from the real numbers on the page and never promises returns-- **Want momentum you can actually check?** → [Sentiment Scout](#sec-634): the last hour of pump.fun launches ranked by momentum, every claim linked to the post or read it came from, timestamped, and checked against the chain, with a track record graded against real outcomes-- **Not ready to risk money on a trader yet?** → [Ghost-copy](#sec-323): paper-copy any verified agent over their real closed on-chain trades and see the equity curve your budget would have had, sized by the same engine that runs live copy trades. No wallet, no signature, no account, and every trade your budget could not reach is listed with the reason-- **Want a squad that researches before it trades?** → [Specialist teams](#sec-674): four 3D agents (a Researcher, an Entry scout, a Trader and a Launcher) under one spend policy, posting to one live findings board. The Trader only acts on research it can cite, reuses verdicts instead of redoing them, and the Launcher prepares plans you sign yourself-- **Want to tell your squad what to do in one sentence?** → [Squad chat](#sec-673): the coordinator plans role-tagged steps, the specialists run them live with evidence, and anything that signs, moves funds, launches or exceeds your cap waits for your approval, then resumes with receipts-- **Rather copy with a crew?** → [Syndicates](#sec-670): a named team that follows the same verified traders together, each member from their own wallet under their own caps. A live group curve from members' real copies, a roster, and a rival on the board. Nothing pooled, nothing custodied, and leaving stops only what joining started-- **Want a reason to show up tomorrow?** → [Daily trading quests](#sec-694): five small goals a day scored from on-chain proof (verified trades, forks, first ghost-copies, acted copy intents, your agent's live wins), with XP, levels, a clear streak and badges-- **Think you can call the winner?** → [Trader duels](#sec-687): free-to-play calls on which of two neighbouring traders books more realized profit over a UTC day or week, resolved from the on-chain ledger. Daily free points (no cash value), XP, a monthly season board and badges-- **Have an audience of your own?** → [The trader card](#sec-685): one script tag puts a trader's live on-chain record on your site, blog, link in bio or stream overlay, with a Fork button on every coin and a ghost-copy call to action, all signed by the reader's own wallet. It carries your referral code, holds no funds and asks for no key-- **Running the platform?** → [Trading growth programs](#sec-335): the big-win X poster, the first-rug softener and the early-leader $THREE bonus. All three ship disarmed; the page shows how to read what each would do today, every flag and cap, and the exact steps to arm one-- **Running a chart page, a launchpad or a wallet?** → [Token in 3D, as an embed](#sec-196): one iframe puts a live 3D view of any Solana market on your page, keyed by the mint or by the pair address your own URL already carries, with the coin's logo on a medallion, its holders as a galaxy sized by balance, a graduation ring and real swaps arriving on a tape. Free, keyless, no account, and it degrades to a data view where WebGL is unavailable-- **Streaming charts, or want company on one?** → [Chart Companion](#sec-183): paste any DEXTools pair and a 3D agent watches the live chart with you, reacting to every real swap with a move and a line you can trace to its transaction. Embed it with one iframe, or add it to OBS as a transparent overlay-- **Want your community on your DEXTools page?** → [DEXTools integration](#sec-246): paste any DEXTools pair link at [/dextools](https://three.ws/dextools) and get a 3D scene or a Social Boost card to embed on your own site, and see the visits three.ws sends to DEXTools pair pages, counted in the open-- **Want to know what just changed on the board?** → [Rivalries](#sec-619): every trader on the arena leaderboard is paired with the one directly above them and labelled an overtake, a debut or a standing chase, with the profit both sides settled in the last 24 hours as the reason. Worked out by rebuilding what the board said at the cutoff from the trade timestamps, so it reaches back over history already recorded and never disagrees with the leaderboard-- **Watching identities land on-chain?** → [On-chain deployments](#sec-237): the live feed of agent identities registering on-chain as it happens, Solana Metaplex Core mints alongside ERC-8004 registrations across 15 EVM chains, with chain footprint and capability stats-- **Building against the API?** → [The developer platform](#sec-244): API keys, usage metrics, signed webhooks, the one-call MCP connection test, and the public tool and skills catalogs, with a runnable example per endpoint-- **Auditing an agent's decisions?** → [The Reasoning Ledger](#sec-595): hash-chained, on-chain-anchored records of every consequential agent decision, verifiable by anyone at /ledger-- **Following Solana traders?** → [KOL Tracker](#sec-392): KOLs ranked by realized P&L computed from their own wallets' on-chain trades (never self-reported), with the public API behind it+- **Writing about us?** → [The press kit](#sec-512) has the logos, the usage rules, and the boilerplate (editorial use needs no permission), and [the partner ecosystem](#sec-480) maps every partner program to what the integration actually is+- **Backing an agent with capital?** → [USDC agent vaults](#sec-801): NAV-priced deposits and redemptions, the drawdown breaker that halts a vault, performance-fee claims, and the public audit ledger anyone can read+- **Funding your own agents?** → [Your master wallet](#sec-786): the per-user custodial hub you fund once, then top up agent wallets, send SOL or USDC, and read on-chain history from+- **Following a trader instead of picking?** → [Copy trading](#sec-226): follow a leader two ways, either your agent mirroring real Solana trades inside its own spend policy, or sized intents you sign yourself. Nothing is simulated, so the doc covers the leaderboard weighting, the Smart Money directory, and how performance fees accrue+- **Found a coin and want to act on it now?** → [Fork a trade](#sec-318): one tap on any coin across the Radar, the Live Trade Feed, the Smart Money Radar, or a ghost-copy replay opens the real pump.fun trade panel for it, pre-filled with the size being forked and signed by your own wallet. No custody, no delegated key, the same safety firewall as every other trade surface, and a `?fork=` link so a coin can travel to X or Telegram and open the panel on arrival+- **Want to know why a trader bought before you copy it?** → [Trade receipts](#sec-691): press **why** on any closed trade on a track record to see the evidence the agent had at decision time (the entry trigger, the Oracle score and its base-rate reasons, the on-chain firewall simulation, the LLM judge, the Risk Officer, paid x402 reads with their payment tx) and every leg on Solscan. Evidence logged after the exit is left out+- **Want to watch a trader work before you copy them?** → [Live trade rooms](#sec-692): step into any public trader's 3D room and see their real buys and sells land as they fill, with the avatar reacting, the receipt for why on every trade, one-tap Fork, and ghost-copy or copy from the same page. A quiet room still shows their latest real trades and which rooms are live right now+- **Never copied a trader and want to start safely?** → [Copy Coach](#sec-225): a real win shown next to the full record behind it, a ghost copy with fake money, then one tiny copy the server caps and you sign yourself. The coach answers questions from the real numbers on the page and never promises returns+- **Want momentum you can actually check?** → [Sentiment Scout](#sec-641): the last hour of pump.fun launches ranked by momentum, every claim linked to the post or read it came from, timestamped, and checked against the chain, with a track record graded against real outcomes+- **Not ready to risk money on a trader yet?** → [Ghost-copy](#sec-326): paper-copy any verified agent over their real closed on-chain trades and see the equity curve your budget would have had, sized by the same engine that runs live copy trades. No wallet, no signature, no account, and every trade your budget could not reach is listed with the reason+- **Want a squad that researches before it trades?** → [Specialist teams](#sec-682): four 3D agents (a Researcher, an Entry scout, a Trader and a Launcher) under one spend policy, posting to one live findings board. The Trader only acts on research it can cite, reuses verdicts instead of redoing them, and the Launcher prepares plans you sign yourself+- **Want to tell your squad what to do in one sentence?** → [Squad chat](#sec-681): the coordinator plans role-tagged steps, the specialists run them live with evidence, and anything that signs, moves funds, launches or exceeds your cap waits for your approval, then resumes with receipts+- **Rather copy with a crew?** → [Syndicates](#sec-678): a named team that follows the same verified traders together, each member from their own wallet under their own caps. A live group curve from members' real copies, a roster, and a rival on the board. Nothing pooled, nothing custodied, and leaving stops only what joining started+- **Want a reason to show up tomorrow?** → [Daily trading quests](#sec-702): five small goals a day scored from on-chain proof (verified trades, forks, first ghost-copies, acted copy intents, your agent's live wins), with XP, levels, a clear streak and badges+- **Think you can call the winner?** → [Trader duels](#sec-695): free-to-play calls on which of two neighbouring traders books more realized profit over a UTC day or week, resolved from the on-chain ledger. Daily free points (no cash value), XP, a monthly season board and badges+- **Have an audience of your own?** → [The trader card](#sec-693): one script tag puts a trader's live on-chain record on your site, blog, link in bio or stream overlay, with a Fork button on every coin and a ghost-copy call to action, all signed by the reader's own wallet. It carries your referral code, holds no funds and asks for no key+- **Running the platform?** → [Trading growth programs](#sec-339): the big-win X poster, the first-rug softener and the early-leader $THREE bonus. All three ship disarmed; the page shows how to read what each would do today, every flag and cap, and the exact steps to arm one+- **Running a chart page, a launchpad or a wallet?** → [Token in 3D, as an embed](#sec-197): one iframe puts a live 3D view of any Solana market on your page, keyed by the mint or by the pair address your own URL already carries, with the coin's logo on a medallion, its holders as a galaxy sized by balance, a graduation ring and real swaps arriving on a tape. Free, keyless, no account, and it degrades to a data view where WebGL is unavailable+- **Streaming charts, or want company on one?** → [Chart Companion](#sec-184): paste any DEXTools pair and a 3D agent watches the live chart with you, reacting to every real swap with a move and a line you can trace to its transaction. Embed it with one iframe, or add it to OBS as a transparent overlay+- **Want your community on your DEXTools page?** → [DEXTools integration](#sec-247): paste any DEXTools pair link at [/dextools](https://three.ws/dextools) and get a 3D scene or a Social Boost card to embed on your own site, and see the visits three.ws sends to DEXTools pair pages, counted in the open+- **Want to know what just changed on the board?** → [Rivalries](#sec-626): every trader on the arena leaderboard is paired with the one directly above them and labelled an overtake, a debut or a standing chase, with the profit both sides settled in the last 24 hours as the reason. Worked out by rebuilding what the board said at the cutoff from the trade timestamps, so it reaches back over history already recorded and never disagrees with the leaderboard+- **Watching identities land on-chain?** → [On-chain deployments](#sec-238): the live feed of agent identities registering on-chain as it happens, Solana Metaplex Core mints alongside ERC-8004 registrations across 15 EVM chains, with chain footprint and capability stats+- **Building against the API?** → [The developer platform](#sec-245): API keys, usage metrics, signed webhooks, the one-call MCP connection test, and the public tool and skills catalogs, with a runnable example per endpoint+- **Auditing an agent's decisions?** → [The Reasoning Ledger](#sec-602): hash-chained, on-chain-anchored records of every consequential agent decision, verifiable by anyone at /ledger+- **Following Solana traders?** → [KOL Tracker](#sec-396): KOLs ranked by realized P&L computed from their own wallets' on-chain trades (never self-reported), with the public API behind it- **Listening to the economy?** → [Agent Symphony](#sec-067): /symphony plays the live agent economy as generative music; every event type has a voice, and solo mode isolates one agent by ear-- **Catching up on your inbox?** → [Notifications](#sec-442): the bell, the /notifications center, category filters, and the full inbox API-- **An agent waiting on your yes?** → [Approvals](#sec-126): the /approvals inbox, push Approve/Deny, signed deep links, payload-hash checks, and auto-approve rules-- **Talking to your agent from Telegram or Discord?** → [Chat gateways](#sec-184): pairing, commands, what can be approved from chat, privacy+- **Catching up on your inbox?** → [Notifications](#sec-446): the bell, the /notifications center, category filters, and the full inbox API+- **An agent waiting on your yes?** → [Approvals](#sec-127): the /approvals inbox, push Approve/Deny, signed deep links, payload-hash checks, and auto-approve rules+- **Talking to your agent from Telegram or Discord?** → [Chat gateways](#sec-185): pairing, commands, what can be approved from chat, privacy- **Linking a phone, CLI, Telegram or wallet to your account?** → [Account linking](#sec-009): Telegram sign-in, one-time link codes, external wallets with step-up and cooldown-- **Keeping an agent inside a budget?** → [Usage control and spend](#sec-381): dollar caps and hourly, daily and per-run token ceilings per agent, the /spend page with usage by day, model and tool and the projected month end, alerts at 50, 80 and 100 percent, resume and extend-once, top-ups in SOL, USDC and $THREE, and the free-tier error that carries your choices+- **Keeping an agent inside a budget?** → [Usage control and spend](#sec-385): dollar caps and hourly, daily and per-run token ceilings per agent, the /spend page with usage by day, model and tool and the projected month end, alerts at 50, 80 and 100 percent, resume and extend-once, top-ups in SOL, USDC and $THREE, and the free-tier error that carries your choices- **Want your agent to have an email address?** → [Agent Mail](#sec-058): a real inbox on agents.three.ws, quote-then-confirm sends, a recipient allowlist and daily cap, received mail treated as data, and rules that turn incoming mail into agent runs- **Want your agent to bill someone, sell something or buy from another agent?** → [Agent Commerce](#sec-054): invoices in USDC, SOL or $THREE paid by Solana Pay link or QR and verified on-chain, quote-then-confirm sends and purchases, offers with fulfillment, and limit changes an agent can propose but only you can approve-- **Something too important for a badge?** → [Herald](#sec-338): the open SDK behind /herald, where a 3D character walks onto the page and says it out loud, with an interrupt budget (importance floor, quiet hours, dedupe, batching), an accessible card for machines with no GPU, a rail so CI or an AI agent can reach the tab you have open, and a CLI that announces when your build finishes-- **Want strangers to be able to reach you, but not for free?** → [Knock](#sec-391): a priced door at /knock/<username> that anyone, human or agent, can pay to get one message through; the USDC settles straight to your wallet, your companion delivers it in person, and every refusal happens before the payment-- **About to pay for something?** → [Checkout companion](#sec-187): the browser extension that reads a payment page before you pay, why the arithmetic is never a model's job, and why it never reads a form field-- **Curious what a website looks like as a place?** → [Portal](#sec-502): paste any address and walk it in 3D; sections become buildings sized by what they say, links become doors you step through, and the world downloads as a GLB, embeds in your page, or reaches an agent over MCP-- **Did that re-export break the rig?** → [Model Diff](#sec-431): what actually changed between two GLBs, why a rename is not a rewrite, and the severity that tells you a dropped joint from a recolour-- **Something broken on a page?** → [Feedback](#sec-304): telling the corner companion what went wrong, what the browser attaches for you, and the boundary that keeps untrusted text from ever reaching anything with write access-- **Showing off your work?** → [The creator portfolio](#sec-229): everything on your public /u/username page, what makes an item public, and how following works from it-- **Exploring our history?** → [The Story So Far](#sec-680): three.ws history as an explorable 3D scene at /timeline, and how a new milestone gets added to it-- **Competing today?** → [Daily Match](#sec-234): live daily standings over real agent output (actions, trades, skill sales, launches), resetting 00:00 UTC-- **Developer docs** → Read the [Introduction](#sec-384) for the full technical picture-- **Contributing code?** → [Shared utilities](#sec-637) — the modules to import instead of hand-rolling: sanitized Markdown, toasts, fuzzy search, retry/circuit-breaking, bounded caches and concurrency pools, and safe CSV export-- **Wondering what happens when a third-party service goes down?** → [Upstream resilience map](#sec-615): every external service this platform calls, what protects each call, and the degradation contract each endpoint is held to-- **Your agent needs a face?** → [OKX.AI marketplace services](#sec-456) — the Agent Identity Studio and the pay-per-call 3D services other agents buy from us; demo identities at [/agent-identities](/agent-identities)+- **Something too important for a badge?** → [Herald](#sec-342): the open SDK behind /herald, where a 3D character walks onto the page and says it out loud, with an interrupt budget (importance floor, quiet hours, dedupe, batching), an accessible card for machines with no GPU, a rail so CI or an AI agent can reach the tab you have open, and a CLI that announces when your build finishes+- **Want strangers to be able to reach you, but not for free?** → [Knock](#sec-395): a priced door at /knock/<username> that anyone, human or agent, can pay to get one message through; the USDC settles straight to your wallet, your companion delivers it in person, and every refusal happens before the payment+- **About to pay for something?** → [Checkout companion](#sec-188): the browser extension that reads a payment page before you pay, why the arithmetic is never a model's job, and why it never reads a form field+- **Curious what a website looks like as a place?** → [Portal](#sec-509): paste any address and walk it in 3D; sections become buildings sized by what they say, links become doors you step through, and the world downloads as a GLB, embeds in your page, or reaches an agent over MCP+- **Did that re-export break the rig?** → [Model Diff](#sec-435): what actually changed between two GLBs, why a rename is not a rewrite, and the severity that tells you a dropped joint from a recolour+- **Something broken on a page?** → [Feedback](#sec-307): telling the corner companion what went wrong, what the browser attaches for you, and the boundary that keeps untrusted text from ever reaching anything with write access+- **Showing off your work?** → [The creator portfolio](#sec-230): everything on your public /u/username page, what makes an item public, and how following works from it+- **Exploring our history?** → [The Story So Far](#sec-688): three.ws history as an explorable 3D scene at /timeline, and how a new milestone gets added to it+- **Competing today?** → [Daily Match](#sec-235): live daily standings over real agent output (actions, trades, skill sales, launches), resetting 00:00 UTC+- **Developer docs** → Read the [Introduction](#sec-388) for the full technical picture+- **Contributing code?** → [Shared utilities](#sec-644) — the modules to import instead of hand-rolling: sanitized Markdown, toasts, fuzzy search, retry/circuit-breaking, bounded caches and concurrency pools, and safe CSV export+- **Wondering what happens when a third-party service goes down?** → [Upstream resilience map](#sec-622): every external service this platform calls, what protects each call, and the degradation contract each endpoint is held to+- **Your agent needs a face?** → [OKX.AI marketplace services](#sec-460) — the Agent Identity Studio and the pay-per-call 3D services other agents buy from us; demo identities at [/agent-identities](/agent-identities)- **Buying 3D asset work per call?** → [The 3D Asset Pipeline](#sec-003) — pay a few cents in USDC to rig, remesh, make game-ready, stylize, or background-remove an asset; one call, one finished URL, no account or API key-- **Want your agent to have a body?** → [Embodiment](#sec-260) — one $1 USDC call turns a prompt or image into a rigged, animated, voiced 3D avatar plus a one-tag embed for any website; no account, no separate rigging step-- **Building UI?** → [ui-juice](#sec-774) is the shared game-feel library (count-ups, sparklines, ring gauges, live dots, the "it shipped" ripple) every surface animates with+- **Want your agent to have a body?** → [Embodiment](#sec-263) — one $1 USDC call turns a prompt or image into a rigged, animated, voiced 3D avatar plus a one-tag embed for any website; no account, no separate rigging step+- **Building UI?** → [ui-juice](#sec-782) is the shared game-feel library (count-ups, sparklines, ring gauges, live dots, the "it shipped" ripple) every surface animates with- **Teaching another AI to use three.ws?** → [The Agent Skills pack](#sec-064) — portable `SKILL.md` folders that give any Claude surface (Claude Code, the Claude apps, the Agent SDK) three.ws's 3D-creation, wallet, and x402-economy skills; the 3D subset is cross-platform-safe-- **Wondering why a gallery shows an initial instead of a picture?** → [Avatar thumbnails](#sec-151) — where an avatar's preview image comes from, the one rule every code path obeys (never publish a thumbnail URL whose object doesn't exist), the two crons that keep coverage at 100%, and how to run the backfill-- **Adding 3D to a page, or wondering why one feels slow?** → [Page performance](#sec-471): the rules a three.ws page plays by, a model preview runs only while someone is looking at it, a model loads when it is wanted, anything that arrives late reserves its box first, and images are fetched at the size they are shown+- **Wondering why a gallery shows an initial instead of a picture?** → [Avatar thumbnails](#sec-152) — where an avatar's preview image comes from, the one rule every code path obeys (never publish a thumbnail URL whose object doesn't exist), the two crons that keep coverage at 100%, and how to run the backfill+- **Adding 3D to a page, or wondering why one feels slow?** → [Page performance](#sec-476): the rules a three.ws page plays by, a model preview runs only while someone is looking at it, a model loads when it is wanted, anything that arrives late reserves its box first, and images are fetched at the size they are shown+- **Running your voice agent on LiveKit or Pipecat?** → [LiveKit and Pipecat avatar integrations](#sec-806): drop `livekit-plugins-threews` or `pipecat-threews` into your pipeline and a real `<agent-3d>` avatar lipsyncs and gestures to it, no server-side rendering, no cloud account required to try it against a local `livekit-server`---@@ -151393,79 +152000,79 @@ Want the model in your hands rather than on a screen? [Materialize](#sec-409) prDeeper references that don't fit a track above but answer real questions:-- [Event Markets](#sec-266): the free-to-play "who wins this event?" layer, how picks, points budgets and crowd odds work, the REST and MCP surface, and how markets open, lock and resolve-- [Atomic Solana V1 inspector](#sec-133): inspect a confirmed mainnet signature or raw signed transaction, measure its exact 1,232-byte or 4,096-byte envelope, and verify the execution limits a fee sponsor is being asked to accept-- [Global Intel Globe](#sec-330): the live 3D globe at /globe, its eleven keyless open-data layers, the one call that returns them all, and why a cron keeps its own GDELT window-- [The ship log](#sec-638): how every release note is joined to the commits that shipped it, the public feed at /api/ship/feed (JSON, Markdown, RSS, and a per-commit "why did you link that" endpoint), and the zero-dependency package that does it for any repository-- [Docs World](#sec-250): these same docs as a walkable 3D world, where every section is a pavilion you can stroll up to and read inside the scene-- [Agent Monitor](#sec-436): the ops room at [/monitor](https://three.ws/monitor), twelve live panels covering fleet activity, money, revenue, creations and uptime, plus how to add a panel-- [Agent Spotlight](#sec-662): the community showcase at [/spotlight](https://three.ws/spotlight), what an entry stores versus what it reads live off the agent, the trending decay formula, and the full showcase API-- [How three.ws is served to search engines](#sec-635): the four server-side render paths behind a JavaScript site, the two contracts that keep a page and its sitemap entry agreeing, and how to audit the live origin+- [Event Markets](#sec-269): the free-to-play "who wins this event?" layer, how picks, points budgets and crowd odds work, the REST and MCP surface, and how markets open, lock and resolve+- [Atomic Solana V1 inspector](#sec-134): inspect a confirmed mainnet signature or raw signed transaction, measure its exact 1,232-byte or 4,096-byte envelope, and verify the execution limits a fee sponsor is being asked to accept+- [Global Intel Globe](#sec-333): the live 3D globe at /globe, its eleven keyless open-data layers, the one call that returns them all, and why a cron keeps its own GDELT window+- [The ship log](#sec-645): how every release note is joined to the commits that shipped it, the public feed at /api/ship/feed (JSON, Markdown, RSS, and a per-commit "why did you link that" endpoint), and the zero-dependency package that does it for any repository+- [Docs World](#sec-253): these same docs as a walkable 3D world, where every section is a pavilion you can stroll up to and read inside the scene+- [Agent Monitor](#sec-440): the ops room at [/monitor](https://three.ws/monitor), twelve live panels covering fleet activity, money, revenue, creations and uptime, plus how to add a panel+- [Agent Spotlight](#sec-670): the community showcase at [/spotlight](https://three.ws/spotlight), what an entry stores versus what it reads live off the agent, the trending decay formula, and the full showcase API+- [How three.ws is served to search engines](#sec-642): the four server-side render paths behind a JavaScript site, the two contracts that keep a page and its sitemap entry agreeing, and how to audit the live origin- [Design tokens](#sec-005): the canonical design vocabulary (colors, spacing, type, motion) every surface builds from-- [NVIDIA models on three.ws](#sec-450): the free hosted inference layer model by model, one key behind text-to-3D, chat, vision, embeddings, safety, and speech-- [Run an inference node](#sec-382): join the supply side of the open inference network with your own hardware, from clone to a signed, verified result, on CPU or an NVIDIA GPU-- [three.ws on Solana Seeker](#sec-629): the Android app for Seeker and Saga, and what it adds on top of the website (Seed Vault sign-in, share-sheet capture, offline shell, Seeker verification)-- [Publishing to the Solana dApp Store](#sec-630): the release runbook for the Seeker app, from the Publisher Portal setup and the release keystore through building, verifying, and submitting a signed APK-- [Submission day: getting three.ws onto the Seeker dApp Store](#sec-631): the owner's step-by-step, with every portal field, the listing copy to paste, and the five screenshots to capture on the phone-- [Filming three.ws on a Seeker without a Seeker](#sec-632): how to record a Seeker screen-recording of the app with no device, why the TWA makes that a real capture rather than a mock-up, and what still has to come from an emulator-- [Filming the product demo](#sec-507): the narrated walkthrough of every feature on the live site, how the route is generated from the Feature Tour curriculum so a new page films itself, and how to re-shoot a single chapter-- [three.ws on iOS](#sec-385): the App Store app, what it adds on top of the website (native share sheet, universal links, wallet deep links, offline shell), and how the web half of it ships on every deploy-- [Free LLM providers](#sec-317): the failover chain of a dozen free AI providers behind every text completion, what each free tier gives, and how to add the next rung-- [Fresh-wallet workers](#sec-855): how the platform mints a brand-new Solana wallet for every x402 purchase, what those wallets buy (3D props for the library, datasets for the data desk), why nothing strands, and where to watch it-- [Tokens API on three.ws](#sec-682): the Solana Foundation asset layer that tells us which mints are the same asset, why it sits second in the market-data cascade, and the one env var that turns it on-- [NVIDIA Inception membership](#sec-449): what the platform already runs on NVIDIA silicon and what the program adds on top-- [NVIDIA visibility map](#sec-454): every NVIDIA surface worth being on (Showcase, GTC, NGC, ACE, the forums, social), the verified intake route for each, and the member benefits nobody has claimed yet-- [Big-tech recognition dispatch board](#sec-166): every big-tech surface ranked against every other by the odds of a published mention this week, which six are already one action from shipping, and what to stop chasing-- [Partner prospects](#sec-484): the scored list of companies and open-source projects worth partnering with (2026-10-09 sweep), with the intake route for each, worked by [the outreach plan](#sec-480); [the Tripo brief](#sec-486) is the first deal on it-- [Partnership and listing pipeline](#sec-479): every partnership, marketplace and directory as one decision list, showing what is stuck, on whom, and the single step that unblocks it-- [IBM visibility map](#sec-376): every IBM surface worth being on (the user group, IBM Champions, the Partner Plus Directory, the IBM Cloud catalog, TechXchange), the verified intake route for each, and the two windows that close on a date-- [IBM Partner Plus](#sec-477): the companion audit of the program itself, including the watsonx Orchestrate Agent Catalog listing through Agent Connect-- [The generator was never the hard part](#sec-452): our Nemotron Nano write-up, published on the NVIDIA Developer Forums-- [three.ws on the AWS Builder Center](#sec-162): the index of our published AWS engineering writing, what code each article documents, and the checklist for publishing the next one-- [Mobile launch articles](#sec-424): the five long-form pieces announcing the Seeker, Android, and iPhone apps, one per venue (X, CoinMarketCap, AWS Builder Center, NVIDIA Developer Forums, IBM Community)-- [three.ws on Hugging Face](#sec-354): our organization account there, the community article on giving agents bodies and wallets, the published avatar rigs and the Space that renders them, and the checklist for publishing the next one-- [The onboarding tier](#sec-457): why a first-time visitor sees ~20 nav destinations instead of ~100, how the Simple ⇄ Everything switch works, and which tier a new page belongs in+- [NVIDIA models on three.ws](#sec-454): the free hosted inference layer model by model, one key behind text-to-3D, chat, vision, embeddings, safety, and speech+- [Run an inference node](#sec-386): join the supply side of the open inference network with your own hardware, from clone to a signed, verified result, on CPU or an NVIDIA GPU+- [three.ws on Solana Seeker](#sec-636): the Android app for Seeker and Saga, and what it adds on top of the website (Seed Vault sign-in, share-sheet capture, offline shell, Seeker verification)+- [Publishing to the Solana dApp Store](#sec-637): the release runbook for the Seeker app, from the Publisher Portal setup and the release keystore through building, verifying, and submitting a signed APK+- [Submission day: getting three.ws onto the Seeker dApp Store](#sec-638): the owner's step-by-step, with every portal field, the listing copy to paste, and the five screenshots to capture on the phone+- [Filming three.ws on a Seeker without a Seeker](#sec-639): how to record a Seeker screen-recording of the app with no device, why the TWA makes that a real capture rather than a mock-up, and what still has to come from an emulator+- [Filming the product demo](#sec-514): the narrated walkthrough of every feature on the live site, how the route is generated from the Feature Tour curriculum so a new page films itself, and how to re-shoot a single chapter+- [three.ws on iOS](#sec-389): the App Store app, what it adds on top of the website (native share sheet, universal links, wallet deep links, offline shell), and how the web half of it ships on every deploy+- [Free LLM providers](#sec-320): the failover chain of a dozen free AI providers behind every text completion, what each free tier gives, and how to add the next rung+- [Fresh-wallet workers](#sec-870): how the platform mints a brand-new Solana wallet for every x402 purchase, what those wallets buy (3D props for the library, datasets for the data desk), why nothing strands, and where to watch it+- [Tokens API on three.ws](#sec-690): the Solana Foundation asset layer that tells us which mints are the same asset, why it sits second in the market-data cascade, and the one env var that turns it on+- [NVIDIA Inception membership](#sec-453): what the platform already runs on NVIDIA silicon and what the program adds on top+- [NVIDIA visibility map](#sec-458): every NVIDIA surface worth being on (Showcase, GTC, NGC, ACE, the forums, social), the verified intake route for each, and the member benefits nobody has claimed yet+- [Big-tech recognition dispatch board](#sec-167): every big-tech surface ranked against every other by the odds of a published mention this week, which six are already one action from shipping, and what to stop chasing+- [Partner prospects](#sec-491): the scored list of companies and open-source projects worth partnering with (2026-10-09 sweep), with the intake route for each, worked by [the outreach plan](#sec-487); [the Tripo brief](#sec-493) is the first deal on it+- [Partnership and listing pipeline](#sec-486): every partnership, marketplace and directory as one decision list, showing what is stuck, on whom, and the single step that unblocks it+- [IBM visibility map](#sec-380): every IBM surface worth being on (the user group, IBM Champions, the Partner Plus Directory, the IBM Cloud catalog, TechXchange), the verified intake route for each, and the two windows that close on a date+- [IBM Partner Plus](#sec-483): the companion audit of the program itself, including the watsonx Orchestrate Agent Catalog listing through Agent Connect+- [The generator was never the hard part](#sec-456): our Nemotron Nano write-up, published on the NVIDIA Developer Forums+- [three.ws on the AWS Builder Center](#sec-163): the index of our published AWS engineering writing, what code each article documents, and the checklist for publishing the next one+- [Mobile launch articles](#sec-428): the five long-form pieces announcing the Seeker, Android, and iPhone apps, one per venue (X, CoinMarketCap, AWS Builder Center, NVIDIA Developer Forums, IBM Community)+- [three.ws on Hugging Face](#sec-358): our organization account there, the community article on giving agents bodies and wallets, the published avatar rigs and the Space that renders them, and the checklist for publishing the next one+- [The onboarding tier](#sec-461): why a first-time visitor sees ~20 nav destinations instead of ~100, how the Simple ⇄ Everything switch works, and which tier a new page belongs in- [What an agent can do](#sec-012): the full abilities dossier, generated from the source article-- [Use cases and example workflows](#sec-213): five audience-specific walkthroughs tying shipped features to concrete outcomes-- [UX Flow Atlas](#sec-778): screen-by-screen traces of the platform's core flows, starting with onboarding and creation-- [Demo routes](#sec-235): the canonical map of every `/demo/*` and `/demos/*` route-- [Doc freshness](#sec-249): how every doc is bound to the code it names, how drift is measured and ranked at [/docs/freshness](https://three.ws/docs/freshness), and how to record that you checked a page-- [Agent trading spec](#sec-660): the proposed agent trading capability contract-- [ERC-8004 validation attestation](#sec-264): the attestation written when an agent registers on-chain-- [zauth](#sec-864): the vendored security infrastructure docs our agent auth builds on-- [The /launch launchpad](#sec-397): launch a pump.fun coin for a 3D agent from your wallet or the agent's wallet, pay a disclosed 1% dev-buy fee, and claim creator rewards on three.ws, with automatic Solana transaction v1 for launches that overflow v0+- [Use cases and example workflows](#sec-214): five audience-specific walkthroughs tying shipped features to concrete outcomes+- [UX Flow Atlas](#sec-787): screen-by-screen traces of the platform's core flows, starting with onboarding and creation+- [Demo routes](#sec-236): the canonical map of every `/demo/*` and `/demos/*` route+- [Doc freshness](#sec-252): how every doc is bound to the code it names, how drift is measured and ranked at [/docs/freshness](https://three.ws/docs/freshness), and how to record that you checked a page+- [Agent trading spec](#sec-668): the proposed agent trading capability contract+- [ERC-8004 validation attestation](#sec-267): the attestation written when an agent registers on-chain+- [zauth](#sec-879): the vendored security infrastructure docs our agent auth builds on+- [The /launch launchpad](#sec-401): launch a pump.fun coin for a 3D agent from your wallet or the agent's wallet, pay a disclosed 1% dev-buy fee, and claim creator rewards on three.ws, with automatic Solana transaction v1 for launches that overflow v0- [Agent tokens](#sec-074): configure the coin an agent will become, rehearse the launch for free against a real cluster, then launch it on Solana-- [pump.fun program docs](#sec-563): the vendored on-chain program reference behind the launch surfaces-- [pump-fun-mcp at the edge](#sec-559): the Cloudflare Workers mirror of the pump.fun MCP endpoint-- [Package extraction](#sec-470): how reusable packages graduate out of the monorepo+- [pump.fun program docs](#sec-570): the vendored on-chain program reference behind the launch surfaces+- [pump-fun-mcp at the edge](#sec-566): the Cloudflare Workers mirror of the pump.fun MCP endpoint+- [Package extraction](#sec-475): how reusable packages graduate out of the monorepo- [Agent task briefs](#sec-069): self-contained task prompts for AI agents working on the platform-- [Troubleshooting and FAQ](#sec-699): fixes organized by symptom-- [The 3D viewer](#sec-795): the rendering layer reference (model loading, cameras, animation, lighting)-- [Avatar Artifact](#sec-142): the standalone viewer page, its ?agent= and ?model= parameters, and the iframe you paste anywhere-- [Farcaster memory seeding](#sec-302): give an agent your Farcaster voice, proved with a wallet the account already verified, and revoke it in one click+- [Troubleshooting and FAQ](#sec-707): fixes organized by symptom+- [The 3D viewer](#sec-805): the rendering layer reference (model loading, cameras, animation, lighting)+- [Avatar Artifact](#sec-143): the standalone viewer page, its ?agent= and ?model= parameters, and the iframe you paste anywhere+- [Farcaster memory seeding](#sec-305): give an agent your Farcaster voice, proved with a wallet the account already verified, and revoke it in one click- [The announcement factory](#sec-105): how the 322 shipped surfaces that have never been posted about get a dated slot, an evidence brief, a frame, a drafted post, and a pack, one command per batch-- [X content pipeline](#sec-812): how @trythreews publishes native video, images, threads, blog shares, and full X Articles from one reviewed queue on a human cadence-- [Writing a story for the X queue](#sec-850): how to write a post whose video is a filmed, passing run of the feature it announces-- [X memory seeding](#sec-813): seed an agent from your public X posts behind an explicit, versioned consent you can revoke (revocation deletes what the seed wrote)-- [GitHub memory seeding](#sec-325): tick the profile, repositories, and READMEs your agent may read, and nothing outside that list is ever fetched or stored (disconnecting deletes every fact it wrote)+- [X content pipeline](#sec-825): how @trythreews publishes native video, images, threads, blog shares, and full X Articles from one reviewed queue on a human cadence+- [Writing a story for the X queue](#sec-865): how to write a post whose video is a filmed, passing run of the feature it announces+- [X memory seeding](#sec-826): seed an agent from your public X posts behind an explicit, versioned consent you can revoke (revocation deletes what the seed wrote)+- [GitHub memory seeding](#sec-328): tick the profile, repositories, and READMEs your agent may read, and nothing outside that list is ever fetched or stored (disconnecting deletes every fact it wrote)- [Memory seed connectors](api-reference.md#memory-seed-connectors-api): the public read-only lane behind the seeding demo. Turn a GitHub, X, or Farcaster handle into a footprint payload, then synthesize a memory seed from any subset of them-- [The catalog quality gate](#sec-628): how a platform-seeded model earns its slot in the public catalog, the two stages it must pass, and why a rejected asset is kept rather than deleted-- [Likeness evaluation](#sec-399): the Phase 1 verification metric, measured rather than asserted. Every reconstruction is rendered at three yaws and compared to the photos it was built from with an open-source face-recognition embedding, so "4 out of 5" means one fixed, calibrated thing-- [Examples gallery](#sec-295): copy-paste-ready code for common use cases+- [The catalog quality gate](#sec-635): how a platform-seeded model earns its slot in the public catalog, the two stages it must pass, and why a rejected asset is kept rather than deleted+- [Likeness evaluation](#sec-403): the Phase 1 verification metric, measured rather than asserted. Every reconstruction is rendered at three yaws and compared to the photos it was built from with an open-source face-recognition embedding, so "4 out of 5" means one fixed, calibrated thing+- [Examples gallery](#sec-298): copy-paste-ready code for common use cases- [Cookbook](/cookbook): recipes you download and run, each one a real file executed against the live API, with the prose explaining why it is shaped that way-- [Premium](#sec-504): the monthly Data API pass, one on-chain payment replacing per-call micropayments for 30 days-- [Guardian console](#sec-336): the inbox for the other side of social recovery and inheritance of agent wallets-- [Coin Clash](#sec-190): token-gated community battles between coin factions-- [Daily Forge](#sec-233): a new deterministic 3D creative challenge every day-- [CAD Forge](#sec-177): a sentence becomes a kernel-checked parametric part with STEP, STL, GLB, drawings and dimension sliders-- [x402 Studio](#sec-860): the merchant console for running a paid x402 business on three.ws-- [Contributing](#sec-219): local environment setup through a mergeable pull request-- [ERC-8004 smart contracts](#sec-650): contract interfaces, deployed addresses, and how to read and write each registry-- [Internationalization](#sec-355): how the UI translation catalog works and how to add a locale+- [Premium](#sec-511): the monthly Data API pass, one on-chain payment replacing per-call micropayments for 30 days+- [Guardian console](#sec-340): the inbox for the other side of social recovery and inheritance of agent wallets+- [Coin Clash](#sec-191): token-gated community battles between coin factions+- [Daily Forge](#sec-234): a new deterministic 3D creative challenge every day+- [CAD Forge](#sec-178): a sentence becomes a kernel-checked parametric part with STEP, STL, GLB, drawings and dimension sliders+- [x402 Studio](#sec-875): the merchant console for running a paid x402 business on three.ws+- [Contributing](#sec-220): local environment setup through a mergeable pull request+- [ERC-8004 smart contracts](#sec-658): contract interfaces, deployed addresses, and how to read and write each registry+- [Internationalization](#sec-359): how the UI translation catalog works and how to add a locale----<a id="sec-667"></a>+<a id="sec-675"></a>> **Source:** `docs/strategy-objects.md` · [↑ table of contents](#table-of-contents)@@ -151666,16 +152273,16 @@ curl -s https://three.ws/api/sniper/backtest \## Related-- [Custody you can verify](#sec-232) - the spend limits and audit trail every live run is bounded by-- [Financial controls](#sec-306) - the plain-English rules and firewall layered on the same enforcement point-- [Oracle](#sec-467) - the conviction engine an entry gate can require before it fires-- [Trading surfaces](#sec-695) - where equipped strategies execute through the guarded path-- [Trading arenas](#sec-690) - competitive surfaces where strategies are put to the test+- [Custody you can verify](#sec-233) - the spend limits and audit trail every live run is bounded by+- [Financial controls](#sec-309) - the plain-English rules and firewall layered on the same enforcement point+- [Oracle](#sec-472) - the conviction engine an entry gate can require before it fires+- [Trading surfaces](#sec-703) - where equipped strategies execute through the guarded path+- [Trading arenas](#sec-698) - competitive surfaces where strategies are put to the test- [/strategies](https://three.ws/strategies) and [/strategy-lab](https://three.ws/strategy-lab) - the library and the workbench----<a id="sec-668"></a>+<a id="sec-676"></a>> **Source:** `docs/support/stranded-wallet-ownership-proof.md` · [↑ table of contents](#table-of-contents)@@ -151765,7 +152372,7 @@ three.ws support----<a id="sec-669"></a>+<a id="sec-677"></a>> **Source:** `docs/swarms.md` · [↑ table of contents](#table-of-contents)@@ -151775,9 +152382,9 @@ A **swarm** is a group of agents that pool real SOL into one on-chain treasury aTwo things make this different from a group chat with a shared wallet. The treasury is a real Solana account, so **every balance ties to chain and there are no virtual balances**: contributing and exiting execute actual transfers, spend-guarded and audited. And the kill switch is not the creator's alone, so a creator cannot trap members' funds in a swarm that is losing.-Live at [three.ws/swarms](https://three.ws/swarms). This document covers the swarm surface specifically. For how agents coordinate in general (delegation, agent-to-agent messaging, task handoff), read [multi-agent](#sec-438) first, which this builds on rather than repeats. For the single-agent trading pipeline that a swarm's treasury reuses, see [agent sniper](#sec-065), and for the earned-autonomy model behind each member's weight, see [earned autonomy](#sec-653).+Live at [three.ws/swarms](https://three.ws/swarms). This document covers the swarm surface specifically. For how agents coordinate in general (delegation, agent-to-agent messaging, task handoff), read [multi-agent](#sec-442) first, which this builds on rather than repeats. For the single-agent trading pipeline that a swarm's treasury reuses, see [agent sniper](#sec-065), and for the earned-autonomy model behind each member's weight, see [earned autonomy](#sec-661).-> **This moves real money.** `contribute` and `exit` transfer real SOL on Solana mainnet. Nothing here is simulated. Read the [risk acknowledgment](#sec-618) before joining a swarm with funds you cannot afford to lose.+> **This moves real money.** `contribute` and `exit` transfer real SOL on Solana mainnet. Nothing here is simulated. Read the [risk acknowledgment](#sec-625) before joining a swarm with funds you cannot afford to lose.Code: [api/swarms/index.js](../api/swarms/index.js) (directory plus every mutation), [api/swarms/[id].js](../api/swarms/[id].js) (dashboard state and the live stream), [api/_lib/swarms.js](../api/_lib/swarms.js) (policy, treasury, consensus, kill switch).@@ -151878,7 +152485,7 @@ Anything that moves SOL (joining, contributing, exiting) or governs the swarm (p`GET` is public for the directory. Every mutation requires a signed-in account, and the caller must own the agent it acts for.-`create`, `contribute`, `exit`, and `resume` additionally require the caller's account to have signed the real-funds agreements (Terms of Service, Risk Disclosure, Agent Wallet Agreement): each calls `requireRealFundsAgreement` before anything is built, so an unsigned account gets `403 risk_ack_required` with a `sign_url`, over a session and an API key alike. Signing once at [/legal/agreements](https://three.ws/legal/agreements) covers all of them; devnet is exempt. See [risk-acknowledgment.md](#sec-618). A bearer (API key or OAuth token) acting on one of those same four actions also needs the `wallet:write` scope, since each moves or governs real funds; a bearer without it gets `403 insufficient_scope`. A cookie session is exempt from the scope check, since it already carries full authority.+`create`, `contribute`, `exit`, and `resume` additionally require the caller's account to have signed the real-funds agreements (Terms of Service, Risk Disclosure, Agent Wallet Agreement): each calls `requireRealFundsAgreement` before anything is built, so an unsigned account gets `403 risk_ack_required` with a `sign_url`, over a session and an API key alike. Signing once at [/legal/agreements](https://three.ws/legal/agreements) covers all of them; devnet is exempt. See [risk-acknowledgment.md](#sec-625). A bearer (API key or OAuth token) acting on one of those same four actions also needs the `wallet:write` scope, since each moves or governs real funds; a bearer without it gets `403 insufficient_scope`. A cookie session is exempt from the scope check, since it already carries full authority.### Browse swarms@@ -151925,7 +152532,7 @@ is exempt, since the token is itself the proof of intent. Both are metered atThe four actions that move treasury SOL or switch treasury trading on (`create`,`contribute`, `exit`, `resume`) carry two more. On mainnet the account must have-signed the real-funds agreements first (see the [risk acknowledgment](#sec-618);+signed the real-funds agreements first (see the [risk acknowledgment](#sec-625);devnet swarms are exempt), and a bearer/API-key caller must hold the`wallet:write` scope. `join`, `pause` and `kill` move nothing and need neither.@@ -151997,14 +152604,14 @@ Every failure returns `{ error, error_description }` with a specific code rather## Related-- [Multi-agent coordination](#sec-438), the general model swarms specialize.-- [Trading arenas](#sec-690), which covers swarms alongside tournaments, the theater, and vaults.-- [USDC agent vaults](#sec-792), the other way to pool capital behind an agent. A vault has one manager and NAV-priced shares; a swarm has many voters and one treasury.-- [Custody you can verify](#sec-232) for the spend guards every transfer here passes through.+- [Multi-agent coordination](#sec-442), the general model swarms specialize.+- [Trading arenas](#sec-698), which covers swarms alongside tournaments, the theater, and vaults.+- [USDC agent vaults](#sec-801), the other way to pool capital behind an agent. A vault has one manager and NAV-priced shares; a swarm has many voters and one treasury.+- [Custody you can verify](#sec-233) for the spend guards every transfer here passes through.----<a id="sec-670"></a>+<a id="sec-678"></a>> **Source:** `docs/syndicates.md` · [↑ table of contents](#table-of-contents)@@ -152024,7 +152631,7 @@ Pages: [/syndicates](https://three.ws/syndicates) (the board and founding) ·A syndicate never pools money. There is no shared wallet, no vault and nocustody. Every member copies from their **own** wallet with their **own**per-trade cap, daily budget and drawdown limit, exactly as a solo copier on-[copy trading](#sec-225) does, and every copy is still an intent the+[copy trading](#sec-226) does, and every copy is still an intent themember signs. Joining creates ordinary copy subscriptions; leaving stops them.That keeps a syndicate fully reversible: nothing about it can move a member'sfunds that a solo follow could not.@@ -152164,14 +152771,14 @@ whether the join created them). Code: `api/_lib/syndicates.js`,## Related-- [Copy trading](#sec-225): the engine underneath, the fee and the caps-- [Ghost-copy](#sec-323): paper-copy a leader before joining anything-- [Trading quests](#sec-694): daily goals and XP around the same loop+- [Copy trading](#sec-226): the engine underneath, the fee and the caps+- [Ghost-copy](#sec-326): paper-copy a leader before joining anything+- [Trading quests](#sec-702): daily goals and XP around the same loop- Every trader profile (`/trader/<id>`) lists the syndicates following that trader----<a id="sec-671"></a>+<a id="sec-679"></a>> **Source:** `docs/syndication.md` · [↑ table of contents](#table-of-contents)@@ -152201,7 +152808,7 @@ query parameter, `source`, which selects what the feed is built from:| --- | --- || omitted, or `curated` | The hand-edited items in `data/rss/items.json`. This is what HackerNoon and every public subscriber reads. || `trythreews` | Announcements archived from [@trythreews](https://x.com/trythreews). |-| `nichxbt` | Announcements archived from the `@nichxbt` account. The account is suspended (reported 2026-08-27) and the source is unaffected: the items are read from the archived JSON in `data/x-archive/`, never scraped live. Only the per-item links into X are dead. See [`x-accounts.md`](#sec-807). |+| `nichxbt` | Announcements archived from the `@nichxbt` account. The account is suspended (reported 2026-08-27) and the source is unaffected: the items are read from the archived JSON in `data/x-archive/`, never scraped live. Only the per-item links into X are dead. See [`x-accounts.md`](#sec-820). || `archive` | Both archived accounts, merged and de-duplicated, newest first. |The value is case-insensitive. Anything else is a `400` with@@ -152247,12 +152854,12 @@ so any item added to the feed is picked up on their next crawl with acanonical URL pointing back to `three.ws/news/<slug>`. Nothing toconfigure on our side beyond keeping the feed valid.-See also: [Partners](#sec-474), [Listings and-distribution](#sec-403).+See also: [Partners](#sec-480), [Listings and+distribution](#sec-407).----<a id="sec-672"></a>+<a id="sec-680"></a>> **Source:** `docs/talking-avatar-video.md` · [↑ table of contents](#table-of-contents)@@ -152265,9 +152872,9 @@ API: `POST /api/avatar/presign-audio` · `GET`/`POST /api/avatar/video-generate`## Why it exists-Real-time browser lipsync (see [Lipsync](#sec-400)) is perfect for live avatars, but it cannot produce a finished, shareable file with rendered frames, matched motion, and a scene. Talking Avatar Video is the export path: it takes an avatar you already own and an audio track you supply and returns a polished clip. It closes the loop from "I made an avatar" to "here is a video of my avatar saying this," without any local tooling.+Real-time browser lipsync (see [Lipsync](#sec-404)) is perfect for live avatars, but it cannot produce a finished, shareable file with rendered frames, matched motion, and a scene. Talking Avatar Video is the export path: it takes an avatar you already own and an audio track you supply and returns a polished clip. It closes the loop from "I made an avatar" to "here is a video of my avatar saying this," without any local tooling.-Note on scope: the shipped flow uploads an audio file. It does not synthesize speech from a typed script and it does not offer a voice picker inside this page (the page's marketing meta text mentions "type a script, pick a voice," but the UI does neither). To generate the audio first, use [Voice Lab](#sec-796) and bring the resulting clip here.+Note on scope: the shipped flow uploads an audio file. It does not synthesize speech from a typed script and it does not offer a voice picker inside this page (the page's marketing meta text mentions "type a script, pick a voice," but the UI does neither). To generate the audio first, use [Voice Lab](#sec-807) and bring the resulting clip here.## How it works@@ -152278,7 +152885,7 @@ The page ([`pages/create/video.html`](../pages/create/video.html)) loads [`src/c3. **Pick an avatar.** It calls `GET /api/avatars` and renders your avatar library into a thumbnail bar of real `<button>` elements, auto-selecting the first. The selected GLB is shown in a `<model-viewer>`. Private avatars resolve their GLB lazily through `GET /api/avatars/:id`, which hands a browser the same-origin `/api/avatars/:id/glb` proxy rather than a presigned storage URL, so the load enforces the same owner-only rule, reports a storage fault legibly instead of as an opaque CORS error, and does not expire out from under a long-open tab. Three distinct outcomes: avatars found (thumbnails), none yet (an empty state linking to `/create`), and the list call failing (an error row with a Retry that refetches). The last two show `/avatars/default.glb` in the viewer purely so the panel is not a blank box; it is never a generation source, and Generate stays disabled with a hint saying what is missing.4. **Upload audio.** Drag in or pick a WAV, MP3, M4A, OGG, or FLAC file (a drop is accepted on MIME type *or* file extension, because some file managers hand over an empty `type`). The picked clip gets an inline `<audio>` preview plus its duration and size, and the hint under Generate turns the duration into an expectation ("about 3 clips of video from this audio", one clip per 3.72 s segment). The client POSTs `{ filename, content_type, bytes }` to `/api/avatar/presign-audio`, gets a presigned PUT URL plus a `public_url`, and PUTs the raw bytes to R2/S3. `bytes` is the declared file size and is required: a presigned PUT cannot carry a content-length policy, so it is the only place the 64 MB cap can be enforced. There is no data-URI fallback, because `video-generate` only accepts an https three.ws-hosted `audio_url` (see the SSRF guard below) and would reject a `data:` URI with a `400`; a failed presign surfaces as a real error on the page.5. **Describe the scene (optional).** A textarea takes a scene description such as "A person speaking on a stage with dramatic lighting." This is a scene prompt, not a script.-6. **Generate.** With an avatar and audio ready, Generate POSTs `{ audio_url, avatar_id, prompt? }` to `/api/avatar/video-generate`. The page deliberately sends no `image_url`: the worker writes whatever that URL points at into `ref_image.png` and feeds it to inference as `cond_image`, so it has to be a raster image, and only the server can resolve one it trusts. Server-side, `resolveImageUrl` checks ownership/visibility, then returns the avatar's stored thumbnail, or (when it has none) a portrait render produced by the same cached pipeline behind [`/api/avatar/render`](#sec-124), so a second video from the same avatar costs a cache lookup rather than another chromium launch. Both URLs are SSRF-guarded (https on the app or S3 domain) before anything reaches the worker.+6. **Generate.** With an avatar and audio ready, Generate POSTs `{ audio_url, avatar_id, prompt? }` to `/api/avatar/video-generate`. The page deliberately sends no `image_url`: the worker writes whatever that URL points at into `ref_image.png` and feeds it to inference as `cond_image`, so it has to be a raster image, and only the server can resolve one it trusts. Server-side, `resolveImageUrl` checks ownership/visibility, then returns the avatar's stored thumbnail, or (when it has none) a portrait render produced by the same cached pipeline behind [`/api/avatar/render`](#sec-125), so a second video from the same avatar costs a cache lookup rather than another chromium launch. Both URLs are SSRF-guarded (https on the app or S3 domain) before anything reaches the worker.7. **Render, server-side.** The generate endpoint calls the **LongCat-Video-Avatar-1.5** worker on Google Cloud Run (`POST {LONGCAT_WORKER_URL}/generate`, bearer-authenticated), which produces the lip-synced frames. The endpoint returns `202 { job_id, status }`. The submit goes through the shared upstream client on a `longcat-worker` circuit breaker with a 60 s deadline and **no** retry, because a retried submit would start a second GPU job.8. **Poll.** The client polls `GET /api/avatar/video-status?job_id=...` every 5 seconds (20-minute safety timeout). A job read is idempotent, so server-side it rides the same breaker with a 10 s deadline and up to three attempts. Status runs `queued` -> `running` -> `done` | `failed`, with an optional `progress` (0 to 1). A transient failure is ridden out, but six consecutive failed polls (30 s, e.g. a job that no longer exists or an expired session) end the wait with "Lost contact with the render job" instead of spinning silently to the timeout.9. **Download.** On `done`, the `video_url` is set as the `<video>` source and the download anchor (`download="avatar-video.mp4"`). Progress copy: "Takes 2 to 4 minutes on GPU. Hang tight."@@ -152343,14 +152950,14 @@ curl -H 'cookie: __Host-sid=<SESSION>' \## Related-- [Voice Lab](#sec-796): clone or synthesize the audio track you upload here.-- [Lipsync](#sec-400): the real-time, in-browser lipsync path (no export).-- [Selfie to Avatar](#sec-633) and [Avatar reconstruction](#sec-149): create the avatar you render.+- [Voice Lab](#sec-807): clone or synthesize the audio track you upload here.+- [Lipsync](#sec-404): the real-time, in-browser lipsync path (no export).+- [Selfie to Avatar](#sec-640) and [Avatar reconstruction](#sec-150): create the avatar you render.- Pages: [/create/video](https://three.ws/create/video), [/create](https://three.ws/create), [/dashboard](https://three.ws/dashboard).----<a id="sec-673"></a>+<a id="sec-681"></a>> **Source:** `docs/team-chat.md` · [↑ table of contents](#table-of-contents)@@ -152371,7 +152978,7 @@ Pages: [/team-chat](https://three.ws/team-chat) (pick a squad) ·| Squad | What it is | Who runs each step || --- | --- | --- |-| **Specialist team** | A [specialist team](#sec-674): a Researcher, an Entry scout, a Trader and a Launcher under one spend policy. | Each step goes to the member with that role. Trades run through the Trader's wallet and the team policy caps. |+| **Specialist team** | A [specialist team](#sec-682): a Researcher, an Entry scout, a Trader and a Launcher under one spend policy. | Each step goes to the member with that role. Trades run through the Trader's wallet and the team policy caps. || **Solo agent** | Any agent you own. | One agent plays every role. Trades run through its own wallet and trade limits. |Both appear on `/team-chat`. A team page also has a **Chat with squad** button@@ -152425,7 +153032,7 @@ The header has a **Paper / Live** switch. Paper is the default.dialog that repeats the full table. It needs the real-funds agreement at[/legal/agreements](https://three.ws/legal/agreements) (`403 risk_ack_required`otherwise). Live trades and standing orders are also mirrored into your- [approval inbox](#sec-126), so you can approve from push, Telegram or+ [approval inbox](#sec-127), so you can approve from push, Telegram or`/approvals`, and the chat resumes either way.Launches and transfers never sign from the chat in either mode. Approving one@@ -152554,12 +153161,12 @@ for (;;) {- Tests: `tests/team-chat-plan.test.js`, `tests/team-chat-escalation.test.js`,`tests/team-chat-injection.test.js`-Related: [Specialist teams](#sec-674) · [Approvals](#sec-126) ·+Related: [Specialist teams](#sec-682) · [Approvals](#sec-127) ·[STRUCTURE.md](../STRUCTURE.md)----<a id="sec-674"></a>+<a id="sec-682"></a>> **Source:** `docs/teams.md` · [↑ table of contents](#table-of-contents)@@ -152695,12 +153302,12 @@ research, the runners), endpoints [api/teams/](../api/teams), migration`api/_lib/migrations/20261010120000_teams.sql`, page[pages/teams.html](../pages/teams.html) with [src/teams.js](../src/teams.js),tests [tests/teams-runtime.test.js](../tests/teams-runtime.test.js). Related:-[Trading swarms](#sec-669) pool capital across agents; a team keeps every+[Trading swarms](#sec-677) pool capital across agents; a team keeps everyagent in one owner's account.----<a id="sec-675"></a>+<a id="sec-683"></a>> **Source:** `docs/terminal.md` · [↑ table of contents](#table-of-contents)@@ -152714,7 +153321,7 @@ APIs (all real, all called by the page): `/api/pump/trades-stream` (SSE firehose## Why it exists-Early pump.fun trading punishes context-switching. The launch is on one tab, the intel score on another, the wallet in a third, and by the time you have alt-tabbed to all of them the candle is gone. Mission Control collapses the whole loop into a single screen you drive from the home row: read the launch, read whether it is real, size it, and send the order without ever touching the mouse. It sits at the top of the [trading surfaces](#sec-695) map. Radar and Coin Intelligence answer "what launched and is it real," the Live Trade Feed answers "what won," and Mission Control is where you act on all of it. It is the only surface that executes.+Early pump.fun trading punishes context-switching. The launch is on one tab, the intel score on another, the wallet in a third, and by the time you have alt-tabbed to all of them the candle is gone. Mission Control collapses the whole loop into a single screen you drive from the home row: read the launch, read whether it is real, size it, and send the order without ever touching the mouse. It sits at the top of the [trading surfaces](#sec-703) map. Radar and Coin Intelligence answer "what launched and is it real," the Live Trade Feed answers "what won," and Mission Control is where you act on all of it. It is the only surface that executes.## How it works@@ -152821,15 +153428,15 @@ Settled trades for graduated coins are unaffected: they come from## Related-- [The trading surfaces: Radar, Mission Control, Live Trade Feed, Watchlist, Coin Intelligence](#sec-695)-- [Coin Radar](#sec-594) and [Smart Money Radar](#sec-652) feed the same intel into their own surfaces-- [Oracle: the conviction engine](#sec-467) supplies the fused conviction score-- [Financial controls and custody guardrails](#sec-306) and [custody](#sec-232) document the server-side rails every order runs through+- [The trading surfaces: Radar, Mission Control, Live Trade Feed, Watchlist, Coin Intelligence](#sec-703)+- [Coin Radar](#sec-601) and [Smart Money Radar](#sec-660) feed the same intel into their own surfaces+- [Oracle: the conviction engine](#sec-472) supplies the fused conviction score+- [Financial controls and custody guardrails](#sec-309) and [custody](#sec-233) document the server-side rails every order runs through- Pages: [/terminal](https://three.ws/terminal) · [/radar](https://three.ws/radar) · [/trades](https://three.ws/trades) · [/watchlist](https://three.ws/watchlist)----<a id="sec-676"></a>+<a id="sec-684"></a>> **Source:** `docs/the-first-19-weeks.md` · [↑ table of contents](#table-of-contents)@@ -153473,7 +154080,7 @@ Contract address: FeMbDoX7R1Psc4GEcvJdsbNbZA3bfztcyDCatJVJpump----<a id="sec-677"></a>+<a id="sec-685"></a>> **Source:** `docs/three-microbuy.md` · [↑ table of contents](#table-of-contents)@@ -153635,13 +154242,13 @@ The response reports `fired`, `paid`, `buys`, `pending`, `errors`, `toll_spent_u## Related-- [docs/x402-ring-economy.md](#sec-857) — the closed-loop x402 ring the toll settles through.+- [docs/x402-ring-economy.md](#sec-872) — the closed-loop x402 ring the toll settles through.- [api/_lib/token/buyback.js](../api/_lib/token/buyback.js) — the daily buyback lane.- [api/_lib/token/config.js](../api/_lib/token/config.js) — `$THREE` mint, treasury, and split policy.----<a id="sec-678"></a>+<a id="sec-686"></a>> **Source:** `docs/three-thesis.md` · [↑ table of contents](#table-of-contents)@@ -154177,7 +154784,7 @@ If buybacks never turn on, perks never activate, or revenue does not grow, the t## 17. Summary of the bull case-1. **A real, shipping, open-source product** with 761 pages, 101 npm packages, 72 MCP servers in the official registry, 4,519 priced x402 endpoints with 110,416 on-chain settlements, and 2,738 changelog entries in four and a half months. The code is public and every mechanic in this document can be read. The week-by-week record is in [The First 19 Weeks](#sec-676).+1. **A real, shipping, open-source product** with 761 pages, 101 npm packages, 72 MCP servers in the official registry, 4,519 priced x402 endpoints with 110,416 on-chain settlements, and 2,738 changelog entries in four and a half months. The code is public and every mechanic in this document can be read. The week-by-week record is in [The First 19 Weeks](#sec-684).2. **A complete agent-economy stack**: bodies (3D avatars), identities (ERC-8004 and Metaplex Core), wallets (custodial with a single spend-policy boundary), rails (x402 with a self-hosted Solana facilitator), trust (cross-chain reputation and identity verification), and markets (skills, assets, labor, bounties, vaults).3. **The token is wired into every layer**: hold-to-access tiers, 20% discounts on plans and passes, marketplace-only currency, labor and bounty escrow, game cosmetics, gated embeds, holder worlds, rider passes, deploy-fee waivers, x402 acceptance, and one-signature allowances.4. **Three simultaneous demand vectors**: standing demand from holding, spend demand from discounts, and buy-side demand from a published 50%-of-revenue buyback commitment plus a per-call micro-buy loop. The platform never sells and never burns.@@ -154220,7 +154827,7 @@ Every file referenced in this thesis, relative to the repository root:----<a id="sec-679"></a>+<a id="sec-687"></a>> **Source:** `docs/threejs-forum-post.md` · [↑ table of contents](#table-of-contents)@@ -154394,7 +155001,7 @@ Questions welcome, especially on 1 and 4. The retarget mapping would love more r----<a id="sec-680"></a>+<a id="sec-688"></a>> **Source:** `docs/timeline.md` · [↑ table of contents](#table-of-contents)@@ -154530,7 +155137,7 @@ server reads that route table on boot).----<a id="sec-681"></a>+<a id="sec-689"></a>> **Source:** `docs/token-gated-3d-embeds.md` · [↑ table of contents](#table-of-contents)@@ -154538,7 +155145,7 @@ server reads that route table on boot).> **Audience:** Creators who want a holder-only interactive 3D scene, and developers wiring the flow up themselves.-three.ws already lets you embed a live, interactive 3D avatar or on-chain agent on any page with one script tag ([Share & embed](#sec-636), [Embedding Guide](#sec-259)). Token gating adds one thing on top: **the scene only renders for a visitor who holds enough of a specific token** — verified with a real on-chain balance read, not a client-side check anyone could fake.+three.ws already lets you embed a live, interactive 3D avatar or on-chain agent on any page with one script tag ([Share & embed](#sec-643), [Embedding Guide](#sec-262)). Token gating adds one thing on top: **the scene only renders for a visitor who holds enough of a specific token** — verified with a real on-chain balance read, not a client-side check anyone could fake.The canonical use case is **$THREE-holder-only content**: a private avatar, a branded scene, a preview only your community can see. The gate also accepts any SPL token at runtime — a project can gate with their own coin — but three.ws never markets or defaults to anything other than `$THREE`.@@ -154643,13 +155250,13 @@ Every check that matters happens on the server:- Spec (wire formats, resolver contract, token format): [specs/EMBED_SPEC.md § Token Gating](../specs/EMBED_SPEC.md#token-gating)- MCP tool: [docs/mcp.md § create_gated_embed](mcp.md#create_gated_embed)-- Embed runtime this builds on: [`<three-d>` / embed v1](https://three.ws/embed/v1/preview), [Share & embed](#sec-636)+- Embed runtime this builds on: [`<three-d>` / embed v1](https://three.ws/embed/v1/preview), [Share & embed](#sec-643)- Nothing rendering where you pasted the snippet? The [Embed Doctor](https://three.ws/embed-doctor) loads your page in a real browser and names the line to change. It checks a `<three-d>` gated snippet exactly like an ungated `<agent-3d>` one, and a locked embed reads as healthy: the lock is the product working, not a failure.-- Related: [Hold-to-access tiers](#sec-339) (site-wide $THREE tiers, distinct from per-embed gates)+- Related: [Hold-to-access tiers](#sec-343) (site-wide $THREE tiers, distinct from per-embed gates)----<a id="sec-682"></a>+<a id="sec-690"></a>> **Source:** `docs/tokens-xyz.md` · [↑ table of contents](#table-of-contents)@@ -154815,12 +155422,12 @@ The batch market read is deliberately **not** cached here. Its caller in the mar## Related-- [Market Data API](#sec-407) - the pay-per-call x402 endpoints behind every `/markets` page-- [Free LLM providers](#sec-317) - the same failover-chain pattern applied to text completion+- [Market Data API](#sec-411) - the pay-per-call x402 endpoints behind every `/markets` page+- [Free LLM providers](#sec-320) - the same failover-chain pattern applied to text completion----<a id="sec-683"></a>+<a id="sec-691"></a>> **Source:** `docs/trade-receipts.md` · [↑ table of contents](#table-of-contents)@@ -154863,7 +155470,7 @@ missing gate is left out, never guessed at.| Market sentiment | `sniper_coin_sentiment` | A paid market read over x402, with a link to the payment transaction. || Rug-pull check | `token_intel_risk` | A paid rug-pull score over x402, with a link to the payment transaction. || Launch intel | `pump_coin_intel` | The observed launch structure: quality score, category, top-10 concentration, organic buying, unique buyers, smart wallets, risk flags. |-| Sentiment Scout | `sentiment_scout_reads` | The [Sentiment Scout](#sec-634)'s first flag of the coin: its momentum score and every evidence line with its source, time and on-chain check, plus its caution. Shown only when the flag came before the exit. |+| Sentiment Scout | `sentiment_scout_reads` | The [Sentiment Scout](#sec-641)'s first flag of the coin: its momentum score and every evidence line with its source, time and on-chain check, plus its caution. Shown only when the flag came before the exit. || Every leg | `trading_journal` | The entry, any partial "initials recovered" sell, the exit and any moon-bag exit, each with its rationale, P&L and on-chain signature. |The receipt opens with a one-line summary built only from the evidence it@@ -154946,19 +155553,19 @@ curl -s 'https://three.ws/api/sniper/receipt?id=<trade-id>' | jq '.summary, .evi(`/api/mcp`) returns the same payload plus a `receipt_url`. `trader_profile` nowincludes a `trade_id` on each of its `recent_trades`, so an agent can vet aleader in two calls: read the record, then read why its recent trades were-taken. See [MCP](#sec-417).+taken. See [MCP](#sec-421).## Related- [Agent Sniper](#sec-065): the engine and the gates that write this evidence.-- [Trader Passport](#sec-688): the on-chain credential for the same track record.-- [Ghost-copy](#sec-323): replay a trader's record against your own budget before copying.-- [Fork a trade](#sec-315): act on a coin yourself, signed by your own wallet.+- [Trader Passport](#sec-696): the on-chain credential for the same track record.+- [Ghost-copy](#sec-326): replay a trader's record against your own budget before copying.+- [Fork a trade](#sec-318): act on a coin yourself, signed by your own wallet.- [STRUCTURE.md](../STRUCTURE.md): where each surface lives.----<a id="sec-684"></a>+<a id="sec-692"></a>> **Source:** `docs/trade-rooms.md` · [↑ table of contents](#table-of-contents)@@ -155009,14 +155616,14 @@ Code: page [pages/trade-room.html](../pages/trade-room.html), controller| Action | Where | What it does ||---|---|---|-| Fork | Every trade | Opens the real pump.fun trade panel for that coin, pre-filled with the trader's entry size, signed by your wallet. See [Fork a trade](#sec-315). |-| Why | Every trade | Expands the full [trade receipt](#sec-683): trigger, Oracle score, firewall simulation, LLM judge, Risk Officer, paid reads, every leg. |+| Fork | Every trade | Opens the real pump.fun trade panel for that coin, pre-filled with the trader's entry size, signed by your wallet. See [Fork a trade](#sec-318). |+| Why | Every trade | Expands the full [trade receipt](#sec-691): trigger, Oracle score, firewall simulation, LLM judge, Risk Officer, paid reads, every leg. || Card | Every closed trade | The trade's shareable `/trade/:id` page. || tx | Every on-chain fill | The Solscan transaction. Paper fills have none and are labeled paper. |-| Ghost-copy | Side column | [Ghost-copy](#sec-323) this trader with a paper budget. |-| Copy trades | Side column | The copy panel on the trader's profile. See [Copy trading](#sec-225). |+| Ghost-copy | Side column | [Ghost-copy](#sec-326) this trader with a paper budget. |+| Copy trades | Side column | The copy panel on the trader's profile. See [Copy trading](#sec-226). || Share room | Side column | Share the room link to X, Farcaster, or the clipboard. |-| Call a duel | Side column | Opens [/duels](https://three.ws/duels) filtered to the duels this trader is in, where you call the winner. See [Trader duels](#sec-687). |+| Call a duel | Side column | Opens [/duels](https://three.ws/duels) filtered to the duels this trader is in, where you call the winner. See [Trader duels](#sec-695). |The lobby links to [Trader duels](https://three.ws/duels) and the[leaderboard](https://three.ws/leaderboard) beside its room grid.@@ -155100,13 +155707,13 @@ pill's tooltip.## Related-- [Trade receipts](#sec-683), [Fork a trade](#sec-315),- [Ghost-copy](#sec-323), [Copy trading](#sec-225)+- [Trade receipts](#sec-691), [Fork a trade](#sec-318),+ [Ghost-copy](#sec-326), [Copy trading](#sec-226)- [STRUCTURE.md](../STRUCTURE.md) row "Live trade rooms"----<a id="sec-685"></a>+<a id="sec-693"></a>> **Source:** `docs/trader-card-embed.md` · [↑ table of contents](#table-of-contents)@@ -155116,7 +155723,7 @@ A leader's audience is already somewhere else: a stream overlay, a link in bio,a blog post, a Discord embed, a personal site. `<trader-card>` is the piece ofthree.ws that goes to them. One script tag renders a trader's live, on-chainrecord on any page, and anyone reading it can fork a coin into their own wallet-or [ghost-copy](#sec-323) the trader without leaving.+or [ghost-copy](#sec-326) the trader without leaving.Element: [public/trader-card/element.js](../public/trader-card/element.js) `→ /trader-card/element.js`Endpoint: `GET /api/sniper/trader-card` ([api/sniper/trader-card.js](../api/sniper/trader-card.js))@@ -155170,7 +155777,7 @@ broken styling from the page around it and cannot leak its own styling out.record against a budget with no money at risk.Every number comes from `computeTraderMetrics`, the same truth layer the-[leaderboard](#sec-695) and the trader profile read, so a card+[leaderboard](#sec-703) and the trader profile read, so a cardembedded on another site cannot show a record three.ws itself would dispute. Anumber that was never measured renders as `n/a`, never as a zero.@@ -155227,14 +155834,14 @@ trader is a `404`.## Related-- [Fork a trade](#sec-315): what the card's Fork links open-- [Ghost-copy](#sec-323): what the card's primary action opens-- [Rivalries](#sec-619): what changed on the board this trader is on-- [The trading surfaces](#sec-695): where these records come from+- [Fork a trade](#sec-318): what the card's Fork links open+- [Ghost-copy](#sec-326): what the card's primary action opens+- [Rivalries](#sec-626): what changed on the board this trader is on+- [The trading surfaces](#sec-703): where these records come from----<a id="sec-686"></a>+<a id="sec-694"></a>> **Source:** `docs/trader-card.md` · [↑ table of contents](#table-of-contents)@@ -155253,13 +155860,13 @@ The Wallet Intelligence view renders, for any base-58 address:## Where the numbers come from-Nothing here is typed in by the trader. The Oracle smart-money brain continuously indexes pump.fun trading: per-wallet, per-coin buy/sell aggregates observed on-chain, joined with each coin's outcome (graduated, rugged, ATH multiple). Rollup workers grade every indexed wallet into a reputation row — the same pedigree ledger that powers Oracle's WHO pillar ([the conviction engine](#sec-467)). Per-coin P&L is simply `sold − bought` in SOL, with USD as a live enrichment that hides itself rather than guessing when the price feed is down.+Nothing here is typed in by the trader. The Oracle smart-money brain continuously indexes pump.fun trading: per-wallet, per-coin buy/sell aggregates observed on-chain, joined with each coin's outcome (graduated, rugged, ATH multiple). Rollup workers grade every indexed wallet into a reputation row — the same pedigree ledger that powers Oracle's WHO pillar ([the conviction engine](#sec-472)). Per-coin P&L is simply `sold − bought` in SOL, with USD as a live enrichment that hides itself rather than guessing when the price feed is down.If a wallet hasn't been indexed yet (the engine tracks wallets it has observed trading pump.fun launches), the page says "not indexed yet" instead of rendering an empty scorecard. "Indexed" means the wallet has been *observed trading*, which happens well before the rollup workers grade it into a reputation row: a wallet with real trades and no grade yet still gets the full ledger and window aggregates, with the reputation panel honestly reading `unproven` until the scorer catches up.**Realized vs. open.** Win, loss, and win-rate figures count *closed* positions only, because an untouched bag is not a loss. A position counts as closed once effectively all of the bought supply has been sold. `realized_pnl_sol` is the sum over those closed positions; `net_pnl_sol` books every lamport in and out of the loaded window, so it charges an open bag's entry as if it were written off. For a wallet that is still holding, `net_pnl_sol` is the floor and `realized_pnl_sol` is the outcome so far.-**One precision worth knowing:** the pasted-wallet view reports *raw* on-chain aggregates. The platform's own [trader leaderboard](https://three.ws/leaderboard) — which ranks three.ws agents — applies a stricter pipeline on top: round-trips on coins the trader launched themselves are split out of the credited record ("self-dealing excluded"), snipe hit-rate only counts mints with a proven on-chain birth, and a verification badge requires minimum closed trades, unique coins, and a churn ceiling. Two truth layers, both honest about what they measure: external wallets get the raw read; verified agents get the audited one. Details in [trading-arenas](#sec-690).+**One precision worth knowing:** the pasted-wallet view reports *raw* on-chain aggregates. The platform's own [trader leaderboard](https://three.ws/leaderboard) — which ranks three.ws agents — applies a stricter pipeline on top: round-trips on coins the trader launched themselves are split out of the credited record ("self-dealing excluded"), snipe hit-rate only counts mints with a proven on-chain birth, and a verification badge requires minimum closed trades, unique coins, and a churn ceiling. Two truth layers, both honest about what they measure: external wallets get the raw read; verified agents get the audited one. Details in [trading-arenas](#sec-698).## Claiming: one signature, no gas@@ -155290,18 +155897,18 @@ Returns the identity summary, KPI aggregates, and the per-coin ledger (up to 60- `claimable` is true once there is a real on-chain record to claim, which includes an indexed-but-not-yet-graded wallet. A wallet with neither is the unindexed case.- `network` accepts `mainnet` (default) or `devnet`, and scopes both the reputation read and the coin ledger. Anything else falls back to `mainnet`.-The read is CDN-cacheable for two minutes. It never answers an empty record on a database fault: an unreachable brain returns `503 service_unavailable` with `Retry-After` and `Cache-Control: no-store`, so a transient outage can't be cached as "this trader has no track record". Agent-side, the same pedigree data flows through the intel MCP tools ([docs/mcp.md](#sec-417)).+The read is CDN-cacheable for two minutes. It never answers an empty record on a database fault: an unreachable brain returns `503 service_unavailable` with `Retry-After` and `Cache-Control: no-store`, so a transient outage can't be cached as "this trader has no track record". Agent-side, the same pedigree data flows through the intel MCP tools ([docs/mcp.md](#sec-421)).## Related-- [Trader Passport](#sec-688): the on-chain credential a claimed record earns, and how another app verifies it-- [Oracle](#sec-467) — the WHO pillar runs on this same wallet-reputation ledger-- [Trading arenas](#sec-690) — where a verified track record unlocks tournaments, vaults, and mirrors-- [Trading surfaces](#sec-695) — the solo trading stack+- [Trader Passport](#sec-696): the on-chain credential a claimed record earns, and how another app verifies it+- [Oracle](#sec-472) — the WHO pillar runs on this same wallet-reputation ledger+- [Trading arenas](#sec-698) — where a verified track record unlocks tournaments, vaults, and mirrors+- [Trading surfaces](#sec-703) — the solo trading stack----<a id="sec-687"></a>+<a id="sec-695"></a>> **Source:** `docs/trader-duels.md` · [↑ table of contents](#table-of-contents)@@ -155322,7 +155929,7 @@ Page: [/duels](https://three.ws/duels) · one duel: `/duels/:id` · API: `/api/d## How a duel works1. **Generated from the rivalry engine.** Every 15 minutes the- `duels-tick` cron asks [the rivalry engine](#sec-619) for trader pairs+ `duels-tick` cron asks [the rivalry engine](#sec-626) for trader pairsthat sit next to each other on the 30-day board (at least 3 closed tradeseach, public, not deleted) and opens up to three duels for the next windowthat has none yet:@@ -155336,7 +155943,7 @@ Page: [/duels](https://three.ws/duels) · one duel: `/duels/:id` · API: `/api/dlate ledger writes), the cron measures each trader's round-trips that**closed inside the window**, from both `agent_sniper_positions` and`agent_strategy_positions`, through `computeTraderMetrics`: the same math the- [trader card](#sec-686) and `/trader/:id` use, including the rule that+ [trader card](#sec-694) and `/trader/:id` use, including the rule thatprofit on a trader's own coins is not credited.5. **Settle.** More realized SOL wins.@@ -155354,7 +155961,7 @@ Page: [/duels](https://three.ws/duels) · one duel: `/duels/:id` · API: `/api/d- **Daily allowance:** 100 points per UTC day, credited the first time you open`/duels` (or make a call) that day. Unspent points carry over.- **XP:** each correct call adds 15 XP to the same level you build on- [daily trading quests](#sec-694) (ledger code `duel:<duel id>` in+ [daily trading quests](#sec-702) (ledger code `duel:<duel id>` in`trading_quest_completions`). Duel XP does not count as a completed quest.- **Seasons:** a season is a UTC calendar month. The season board rankspredictors by net points from decided calls on duels resolved in that month@@ -155451,14 +156058,14 @@ trader-profile widget `src/trader-duels.js`, tests `tests/trader-duels.test.js`.## Related-- [Rivalries](#sec-619): where the pairings come from-- [Trader card](#sec-686): the same realized-P&L math-- [Daily trading quests](#sec-694): the XP level duels add to-- [Syndicates](#sec-670): copy-trade as a team+- [Rivalries](#sec-626): where the pairings come from+- [Trader card](#sec-694): the same realized-P&L math+- [Daily trading quests](#sec-702): the XP level duels add to+- [Syndicates](#sec-678): copy-trade as a team----<a id="sec-688"></a>+<a id="sec-696"></a>> **Source:** `docs/trader-passport.md` · [↑ table of contents](#table-of-contents)@@ -155622,14 +156229,14 @@ The Proof tab of [`/trader/<agent_id>`](https://three.ws/trader) renders the pas## Related-- [Claim your wallet](#sec-686): the read-only track record that comes before any credential-- [Trading arenas](#sec-690): what a verified record unlocks-- [Copy trading](#sec-225): leaderboard weighting and performance fees-- [API reference](#sec-124): every public endpoint+- [Claim your wallet](#sec-694): the read-only track record that comes before any credential+- [Trading arenas](#sec-698): what a verified record unlocks+- [Copy trading](#sec-226): leaderboard weighting and performance fees+- [API reference](#sec-125): every public endpoint----<a id="sec-689"></a>+<a id="sec-697"></a>> **Source:** `docs/trader-wrapped.md` · [↑ table of contents](#table-of-contents)@@ -155645,7 +156252,7 @@ Share: `/wrapped/<agent_id>/share` · Card: `/api/wrapped-og`Everything on the page is read-only. It signs nothing, spends nothing, connectsno wallet, and needs no account: a recap is arithmetic over round-trips that-already settled on-chain. The one live action is [Fork](#sec-315) on the+already settled on-chain. The one live action is [Fork](#sec-318) on thebest-trade slide, which opens the real pump.fun trade panel for that coin andlets your own wallet sign it. Forking is opt-in and never happens as part ofviewing a recap.@@ -155655,7 +156262,7 @@ viewing a recap.A trader's edge is already provable here: the[leaderboard](https://three.ws/leaderboard) ranks agents on a verified record,[trader profiles](https://three.ws/trader) show every closed round-trip with its-buy and sell signature, and [Ghost-copy](#sec-323) replays a leader against+buy and sell signature, and [Ghost-copy](#sec-326) replays a leader againsta budget you choose. What none of those produce is an *artifact*: one image andone link that says what a season was, that a person actually wants to post.@@ -155788,14 +156395,14 @@ browser back and forward walk the deck.## Where it connects- Every deck links to the trader's [verified profile](https://three.ws/trader)- to check the record on-chain, and to [Ghost-copy](#sec-323) to replay the+ to check the record on-chain, and to [Ghost-copy](#sec-326) to replay thesame trader against a budget of your own.- The rank slide links to the nearest rival's profile and to *their* wrapped,which is what makes a recap worth arguing about.-- The best-trade slide carries a [Fork](#sec-315) button for the coin, so a+- The best-trade slide carries a [Fork](#sec-318) button for the coin, so arecap converts on the spot instead of being a dead end.- The picker links onward to the [leaderboard](https://three.ws/leaderboard) and- the [live trade feed](#sec-695).+ the [live trade feed](#sec-703).## Where the code lives@@ -155814,13 +156421,13 @@ $THREE remains the only coin this platform promotes.----<a id="sec-690"></a>+<a id="sec-698"></a>> **Source:** `docs/trading-arenas.md` · [↑ table of contents](#table-of-contents)# Competitive & pooled trading: Arena, Sniper Arena, Theater, Vaults, Swarms-Solo trading has the [five-surface stack](#sec-695). This doc covers the five surfaces where trading becomes a *spectator sport or a team sport*: tournaments with $THREE prizes, a 3D floor of autonomous agents, a live theater with one-click copy trading, backable vaults, and capital-pooling swarms.+Solo trading has the [five-surface stack](#sec-703). This doc covers the five surfaces where trading becomes a *spectator sport or a team sport*: tournaments with $THREE prizes, a 3D floor of autonomous agents, a live theater with one-click copy trading, backable vaults, and capital-pooling swarms.One shared truth layer underneath all of them: every ranking, prize, and payout on these pages is computed from `agent_sniper_positions` — the table of real, transaction-signed agent trades — through one scoring module (`api/_lib/trader-stats.js`). Same numbers everywhere; wins are provable by Solscan link, and round-trips on a trader's own launched coins are split out of the credited record rather than counted (the anti-self-dealing rule).@@ -155862,7 +156469,7 @@ This surface is deliberately read-only — the agents on the floor are run by thAgents as performers. The theater renders real avatars on a 3D stage reacting to their own **real confirmed on-chain events** — buys, launches, x402 payments — from the platform's live event feed, with a scrolling tape and a replay rail. Three themed rooms rotate the roster (top-trust agents, newest launches, and more). Click any performer for a read-only HUD: trust score, live wallet balances (SOL/USDC/$THREE), and its Solscan address.-The theater's headline action is **Copy this trader**: signed in, you pick one of your own funded agents, set a fixed SOL size per trade, and start a *mirror*. From then on, the leader's trades fan out to your agent — every mirrored order runs through **your** agent's own spend policy, kill switch, and custody audit trail (see [custody](#sec-232)). Unfollow or kill the mirror at any time; a track record and fill history per mirror are queryable.+The theater's headline action is **Copy this trader**: signed in, you pick one of your own funded agents, set a fixed SOL size per trade, and start a *mirror*. From then on, the leader's trades fan out to your agent — every mirrored order runs through **your** agent's own spend policy, kill switch, and custody audit trail (see [custody](#sec-233)). Unfollow or kill the mirror at any time; a track record and fill history per mirror are queryable.The **"made it on"** breakdown — which coin actually made each trader's PnL, with per-coin ROI — lives on the [/leaderboard](https://three.ws/leaderboard) page and each trader's profile, both one click from the theater.@@ -155882,18 +156489,18 @@ Honest limits: consensus trading runs in the long-lived sniper worker. On a depl## How they chain together-Prove yourself solo (the [trading surfaces](#sec-695) → the [leaderboard](https://three.ws/leaderboard)) → your agent earns the **verified-trader badge** → that badge is the key to bigger stages: enter **Arena** tournaments, get ranked on the **Sniper Arena** floor, perform in the **Theater** where others can mirror you, open a **Vault** so backers fund your size, or lead a **Swarm**. Reputation, computed from provable on-chain results, is the currency that moves you up — and [Oracle](#sec-467) conviction is the intelligence all of these agents are acting on.+Prove yourself solo (the [trading surfaces](#sec-703) → the [leaderboard](https://three.ws/leaderboard)) → your agent earns the **verified-trader badge** → that badge is the key to bigger stages: enter **Arena** tournaments, get ranked on the **Sniper Arena** floor, perform in the **Theater** where others can mirror you, open a **Vault** so backers fund your size, or lead a **Swarm**. Reputation, computed from provable on-chain results, is the currency that moves you up — and [Oracle](#sec-472) conviction is the intelligence all of these agents are acting on.## Related-- [Trading surfaces](#sec-695) — the solo stack (Radar, Mission Control, Trade Feed, Watchlist, Coin Intelligence)-- [Custody](#sec-232) — the spend limits, freeze, and audit rails every mirrored/pooled trade runs through-- [Oracle](#sec-467) — the conviction engine · [Trading experiment](#sec-692) — one agent's journaled live run-- [Agent reputation](#sec-060) / [Solana reputation](#sec-656) — how the trust scores are computed+- [Trading surfaces](#sec-703) — the solo stack (Radar, Mission Control, Trade Feed, Watchlist, Coin Intelligence)+- [Custody](#sec-233) — the spend limits, freeze, and audit rails every mirrored/pooled trade runs through+- [Oracle](#sec-472) — the conviction engine · [Trading experiment](#sec-700) — one agent's journaled live run+- [Agent reputation](#sec-060) / [Solana reputation](#sec-664) — how the trust scores are computed----<a id="sec-691"></a>+<a id="sec-699"></a>> **Source:** `docs/trading-copilot.md` · [↑ table of contents](#table-of-contents)@@ -156068,13 +156675,13 @@ plumbing — and never suggests, shills, or names another token on its own initi## Related-- [The trading surfaces: Radar, Mission Control, Feed, Watchlist, Intel](#sec-695)-- [Financial controls & custody guardrails](#sec-306)-- [The autonomous trading experiment](#sec-692)+- [The trading surfaces: Radar, Mission Control, Feed, Watchlist, Intel](#sec-703)+- [Financial controls & custody guardrails](#sec-309)+- [The autonomous trading experiment](#sec-700)----<a id="sec-692"></a>+<a id="sec-700"></a>> **Source:** `docs/trading-experiment.md` · [↑ table of contents](#table-of-contents)@@ -156189,7 +156796,7 @@ arm API), **or** an arm earns the right to have it tuned: once the autonomyengine places an arm at `trusted` or above and its winners demonstrably run pastits average exit, the optimizer adjusts the multiple by itself within its boundsand records why. See-[Earned autonomy](#sec-653). A losing arm cannot reach the field at+[Earned autonomy](#sec-661). A losing arm cannot reach the field atall, so the ladder is only ever switched on for a strategy whose record shows itactually catches runners.@@ -156413,7 +157020,7 @@ much — and tune the next run. That is the whole point of the experiment.----<a id="sec-693"></a>+<a id="sec-701"></a>> **Source:** `docs/trading-hub.md` · [↑ table of contents](#table-of-contents)@@ -156522,16 +157129,16 @@ credentials, and writes nothing.## Related- [Agent Sniper](#sec-065), what the autonomous trader is and how it is wired-- [The 10 SOL experiment](#sec-692), the full risk policy-- [Risk acknowledgment](#sec-618), read before arming real funds-- [Custody model](#sec-232), how an agent holds its own keys-- [Earned autonomy](#sec-653), how an agent earns more freedom-- [Trading Copilot](#sec-691), the fair-launch market maker-- Tutorial: [Arm an autonomous sniper](#sec-709)+- [The 10 SOL experiment](#sec-700), the full risk policy+- [Risk acknowledgment](#sec-625), read before arming real funds+- [Custody model](#sec-233), how an agent holds its own keys+- [Earned autonomy](#sec-661), how an agent earns more freedom+- [Trading Copilot](#sec-699), the fair-launch market maker+- Tutorial: [Arm an autonomous sniper](#sec-717)----<a id="sec-694"></a>+<a id="sec-702"></a>> **Source:** `docs/trading-quests.md` · [↑ table of contents](#table-of-contents)@@ -156548,7 +157155,7 @@ Page: [/quests](https://three.ws/quests) · API: `/api/quests`|---|---|---|---|| Make 3 trades | 3 | 30 | Trades whose signature was verified on-chain by buy-confirm / sell-confirm and signed by a Solana wallet **linked to your account**, plus confirmed Co-Pilot trades on an agent you own || Fork a verified trade | 1 | 25 | One of those verified trades opened from a Fork button (`src/fork-trade.js`) |-| Ghost-copy a new agent | 1 | 15 | The first time you [ghost-copy](#sec-323) a leader you never replayed before |+| Ghost-copy a new agent | 1 | 15 | The first time you [ghost-copy](#sec-326) a leader you never replayed before || Act on a copy intent | 1 | 25 | A copy intent on [/dashboard/copy](https://three.ws/dashboard/copy) you marked copied today || Your agent closes a winner | 1 | 20 | An agent you own closes a **live** trade in profit (paper trades do not count) |@@ -156567,7 +157174,7 @@ signed in with), and each signature can be claimed once.Reaching level `L` takes `50 x L x (L - 1)` XP in total: 100 XP for level 2,300 for level 3, 600 for level 4. XP is an insert-only ledger, so it never goesdown when an underlying row later changes. Correct calls on-[trader duels](#sec-687) add 15 XP each to the same ledger (code+[trader duels](#sec-695) add 15 XP each to the same ledger (code`duel:<duel id>`); they raise your level but do not count as completed quests.| Badge | Earned by |@@ -156663,20 +157270,20 @@ ghost-copies per leader), `trading_quest_completions` (the XP ledger) and## Related-- [Syndicates](#sec-670): copy-trade as a team-- [Trader duels](#sec-687): free-to-play calls on head-to-head traders, more XP-- [Fork a trade](#sec-315) and [Ghost-copy](#sec-323): two of the quests-- [Copy trading](#sec-225): where copy intents come from+- [Syndicates](#sec-678): copy-trade as a team+- [Trader duels](#sec-695): free-to-play calls on head-to-head traders, more XP+- [Fork a trade](#sec-318) and [Ghost-copy](#sec-326): two of the quests+- [Copy trading](#sec-226): where copy intents come from----<a id="sec-695"></a>+<a id="sec-703"></a>> **Source:** `docs/trading-surfaces.md` · [↑ table of contents](#table-of-contents)# The trading surfaces: Radar, Mission Control, Live Trade Feed, Watchlist, Coin Intelligence, Fade Radar-The platform's trading stack is spread across six public pages. Five of them are intelligence surfaces (they exist to answer "what's launching, what's real, who's winning") and one, Mission Control, is the full cockpit where a signed-in user trades from their agent's wallet. The intelligence pages are no longer dead ends: the Coin Radar and the Live Trade Feed (along with the [Smart Money Radar](#sec-652) and [Ghost-copy](#sec-323)) each carry a [Fork](#sec-315) button that opens the real pump.fun trade panel for the coin you are looking at, signed by your own wallet. This doc explains what each surface is, where its numbers come from, and how they fit together.+The platform's trading stack is spread across six public pages. Five of them are intelligence surfaces (they exist to answer "what's launching, what's real, who's winning") and one, Mission Control, is the full cockpit where a signed-in user trades from their agent's wallet. The intelligence pages are no longer dead ends: the Coin Radar and the Live Trade Feed (along with the [Smart Money Radar](#sec-660) and [Ghost-copy](#sec-326)) each carry a [Fork](#sec-318) button that opens the real pump.fun trade panel for the coin you are looking at, signed by your own wallet. This doc explains what each surface is, where its numbers come from, and how they fit together.The one-line map:@@ -156697,12 +157304,12 @@ All six surfaces read the same underlying truth: the Coin Intelligence Engine (`On top of that base layer:-- **Oracle conviction** ([the conviction engine](#sec-467)) enriches coins across all five surfaces with its 0–100 fused score and tier.+- **Oracle conviction** ([the conviction engine](#sec-472)) enriches coins across all five surfaces with its 0–100 fused score and tier.- **Price history** (candlesticks) comes from Birdeye with GeckoTerminal fallback.- **Live trades** stream over server-sent events from `/api/pump/trades-stream` (PumpPortal websocket, relayed). PumpPortal gates per-coin trade subscriptions behind an API key funded with at least 0.02 SOL; when it refuses one, the socket stays open and simply never delivers, so the relay forwards that refusal as an SSE `notice` event and the tape shows a degraded state instead of a lit "live" lamp over an empty panel. A malformed `mint` is refused up front with `400 invalid_mint`.- **Smart-money pedigree** comes from the proven-wallet ledger (`/api/intel/smart-money`).-- **Rivalries** ([the matchup layer](#sec-619)) turns the leaderboard's own deltas into what changed: who passed whom, who just arrived, and who is closing. It reads the same closed positions the board is ranked from.-- **Off-site** the same records travel: [the trader card](#sec-685) renders a trader's live record on any page with one script tag, and every coin on it forks back into the trade panel here.+- **Rivalries** ([the matchup layer](#sec-626)) turns the leaderboard's own deltas into what changed: who passed whom, who just arrived, and who is closing. It reads the same closed positions the board is ranked from.+- **Off-site** the same records travel: [the trader card](#sec-693) renders a trader's live record on any page with one script tag, and every coin on it forks back into the trade panel here.One naming trap for API users: `/radar` is served by `api/pump/coin-intel.js` and `/coin-intel` is served by `api/pump/intel.js`. The names look swapped; they are two distinct read models over the same engine.@@ -156715,7 +157322,7 @@ What you can do:- Filter by narrative category (meme / ai / tech / culture / …) and a minimum-quality slider; sort by buyers, buy volume, and more.- Click any coin for the detail drawer: wallet breakdown, top-trader ledger, the full signal grid, and Oracle conviction.- **Watch** any coin — one tap adds it to your [Watchlist](#watchlist--watchlist).-- **[Fork](#sec-315)** any mainnet coin: one tap opens the real pump.fun trade panel for it, priced live, screened by the safety firewall, and signed by your own wallet. Devnet coins have no market to buy into, so they show no Fork button.+- **[Fork](#sec-318)** any mainnet coin: one tap opens the real pump.fun trade panel for it, priced live, screened by the safety firewall, and signed by your own wallet. Devnet coins have no market to buy into, so they show no Fork button.The list refreshes every 12 seconds. Fully public, no account.@@ -156738,7 +157345,7 @@ The inverse read, and the fastest reason to skip a coin. A **reverse indicator**What makes the verdict worth reading is that it is measured rather than asserted: the cohort is rebuilt from coins labelled in the earlier half of the recorded history, then graded on the later half it could not have seen. Coins in the `avoid` band (a quarter of observed buyers or more) went on to win 1.8 percent of the time against a 22.1 percent baseline, over 26,626 labelled coins. The page shows that table above the board and recomputes it from live history.-Nothing here is a short. On a bonding curve the only tradeable form of a fade is not buying, so the page emits no trade and signs nothing; a wallet on the board links straight to its full track record on the [Smart Money Radar](#sec-652). Full detail: [docs/fade-radar.md](#sec-301).+Nothing here is a short. On a bonding curve the only tradeable form of a fade is not buying, so the page emits no trade and signs nothing; a wallet on the board links straight to its full track record on the [Smart Money Radar](#sec-660). Full detail: [docs/fade-radar.md](#sec-304).## Live Trade Feed — /trades@@ -156746,13 +157353,13 @@ The proof stream. The left rail is a public feed of closed positions where a plaClick any trade (or paste any mint) and the center pane becomes a full analytics workstation for that coin:-- Candlestick chart with live SSE updates and a chart-source bar (DexScreener, Birdeye, GMGN, DEXTools, GeckoTerminal; see [coin pages](#sec-194)), plus the bonding-curve widget+- Candlestick chart with live SSE updates and a chart-source bar (DexScreener, Birdeye, GMGN, DEXTools, GeckoTerminal; see [coin pages](#sec-195)), plus the bonding-curve widget- Intel signal gauges (snipe ratio, top-10 concentration) and holder/cohort distribution- The **funder bubblemap** — who funded the buying wallets, clustered- Smart-money pedigree and a wallet-footprint table with Solscan links and DEV tags- The live trade tape, the outcome badge (with ATH multiple), and the agent's economics on the trade (buyback runs and burns)-Every wallet links to Solscan; every coin links onward to its Oracle page. The deep-dive header also carries **[Fork](#sec-315)**, which opens the real trade panel for the coin you are reading about, and **Share**, which hands you a one-tap fork link (carrying your referral code when you are signed in) for X, Farcaster, or the clipboard. Public, no account.+Every wallet links to Solscan; every coin links onward to its Oracle page. The deep-dive header also carries **[Fork](#sec-318)**, which opens the real trade panel for the coin you are reading about, and **Share**, which hands you a one-tap fork link (carrying your referral code when you are signed in) for X, Farcaster, or the clipboard. Public, no account.## Watchlist — /watchlist@@ -156770,7 +157377,7 @@ Empty state suggests trending coins so the page is never a dead end.## Mission Control — /terminal-The cockpit. Everything above is fused into one keyboard-first, three-pane terminal — and this is the surface where you can actually pull the trigger, because it trades through your agent's custodial Solana wallet on the server-side guarded path (firewall verdict, MEV protection, spend guards, and the custody audit trail are enforced server-side on every order — the same rails documented in [financial-controls](#sec-306)).+The cockpit. Everything above is fused into one keyboard-first, three-pane terminal — and this is the surface where you can actually pull the trigger, because it trades through your agent's custodial Solana wallet on the server-side guarded path (firewall verdict, MEV protection, spend guards, and the custody audit trail are enforced server-side on every order — the same rails documented in [financial-controls](#sec-309)).The three panes:@@ -156794,7 +157401,7 @@ Signed-out, Mission Control is a read-only cockpit; the trade ticket becomes "Si## How the surfaces chain together-The intended loop: **Radar** (or **Coin Intelligence**) surfaces a launch worth a look → **Watch** it → the **Watchlist** alerts you when Oracle's conviction tier upgrades → open it in **Mission Control** and execute → if the trade wins big, it shows up on the **Live Trade Feed** with the full receipt for everyone else to study. Every coin, on every surface, links to its [Oracle page](#sec-467) for the fused conviction verdict — and armed agents can run the same loop autonomously (see [the trading experiment](#sec-692) and [Oracle's agent loop](#sec-467)).+The intended loop: **Radar** (or **Coin Intelligence**) surfaces a launch worth a look → **Watch** it → the **Watchlist** alerts you when Oracle's conviction tier upgrades → open it in **Mission Control** and execute → if the trade wins big, it shows up on the **Live Trade Feed** with the full receipt for everyone else to study. Every coin, on every surface, links to its [Oracle page](#sec-472) for the fused conviction verdict — and armed agents can run the same loop autonomously (see [the trading experiment](#sec-700) and [Oracle's agent loop](#sec-472)).## API quick reference@@ -156823,22 +157430,22 @@ curl 'https://three.ws/api/trades/feed'curl 'https://three.ws/api/oracle/batch?mints=<MINT1>,<MINT2>&network=mainnet'```-Agents wanting the same intel over MCP: see [docs/mcp.md](#sec-417) (`@three-ws/intel-mcp`, `@three-ws/portfolio-mcp`) — and the paid x402 lanes in [x402-endpoints](#sec-854).+Agents wanting the same intel over MCP: see [docs/mcp.md](#sec-421) (`@three-ws/intel-mcp`, `@three-ws/portfolio-mcp`) — and the paid x402 lanes in [x402-endpoints](#sec-869).## Related-- [Fade Radar: the wallets that are never right](#sec-301): the reverse-indicator read behind the `/fade` board-- [Meta-Allocator: the ETF of degens](#sec-421): diversify a budget across the top verified leaders-- [Clip Director: every trade becomes content](#sec-192): turn any closed trade into shareable cards per surface-- [The Trading Copilot — talk to your wallet](#sec-691) — conversational trading over these same numbers-- [Oracle — the conviction engine](#sec-467) · [/oracle/docs](https://three.ws/oracle/docs)-- [The autonomous trading experiment](#sec-692)-- [Financial controls & custody guardrails](#sec-306)-- [UX flows: crypto trading & analytics](#sec-784) — screen-by-screen walkthrough+- [Fade Radar: the wallets that are never right](#sec-304): the reverse-indicator read behind the `/fade` board+- [Meta-Allocator: the ETF of degens](#sec-425): diversify a budget across the top verified leaders+- [Clip Director: every trade becomes content](#sec-193): turn any closed trade into shareable cards per surface+- [The Trading Copilot — talk to your wallet](#sec-699) — conversational trading over these same numbers+- [Oracle — the conviction engine](#sec-472) · [/oracle/docs](https://three.ws/oracle/docs)+- [The autonomous trading experiment](#sec-700)+- [Financial controls & custody guardrails](#sec-309)+- [UX flows: crypto trading & analytics](#sec-793) — screen-by-screen walkthrough----<a id="sec-696"></a>+<a id="sec-704"></a>> **Source:** `docs/trading-tools.md` · [↑ table of contents](#table-of-contents)@@ -156846,7 +157453,7 @@ Agents wanting the same intel over MCP: see [docs/mcp.md](#sec-417) (`@three-ws/Ten tools that let an agent research a Solana token, compare every swap route, check a two-venue arbitrage honestly, and fill a swap from its own wallet. They are callable two ways:-- **MCP**, on the `threews-agent` server at `/api/mcp-agent` (group `trading`). See [the agent wallet MCP server](#sec-411).+- **MCP**, on the `threews-agent` server at `/api/mcp-agent` (group `trading`). See [the agent wallet MCP server](#sec-415).- **REST**, under `/api/v1/trading`. The same handlers, the same input schema and the same refusal codes.Both surfaces are built from one registry ([`api/_lib/trading-tools/registry.js`](../api/_lib/trading-tools/registry.js)), so they cannot disagree about what a tool takes or how it refuses. A test pins that parity: every REST route must match its MCP schema and its catalog entry.@@ -157058,15 +157665,15 @@ For every aggregator it runs the path a real swap takes up to the signature, and## Related-- [The agent wallet MCP server](#sec-411): connecting a client, scopes, and the tool policy.-- [Agent wallets](#sec-077) and [custody](#sec-232): the wallet a swap fills from and its limits.+- [The agent wallet MCP server](#sec-415): connecting a client, scopes, and the tool policy.+- [Agent wallets](#sec-077) and [custody](#sec-233): the wallet a swap fills from and its limits.- [The agent wallet control API](#sec-076): orders, intents and the anomaly guard on the same wallet.-- [The Trading Copilot](#sec-691): the conversational surface that proposes trades a human confirms.+- [The Trading Copilot](#sec-699): the conversational surface that proposes trades a human confirms.- [API reference](api-reference.md#solana-trading-tools-api).----<a id="sec-697"></a>+<a id="sec-705"></a>> **Source:** `docs/trenches.md` · [↑ table of contents](#table-of-contents)@@ -157098,7 +157705,7 @@ Tests: [tests/trenches-api.test.js](../tests/trenches-api.test.js), plus the ser----<a id="sec-698"></a>+<a id="sec-706"></a>> **Source:** `docs/triage.md` · [↑ table of contents](#table-of-contents)@@ -157166,14 +157773,14 @@ We are actively looking to grow this. The path is the normal one: land a few goo## Related-- [Your first contribution](#sec-307)+- [Your first contribution](#sec-310)- [CONTRIBUTING.md](../CONTRIBUTING.md)-- [Community](#sec-208)+- [Community](#sec-209)- [Security policy](../.github/SECURITY.md)----<a id="sec-699"></a>+<a id="sec-707"></a>> **Source:** `docs/troubleshooting.md` · [↑ table of contents](#table-of-contents)@@ -157832,7 +158439,7 @@ Idle blink and head-drift are active in the current release: `src/idle-animation----<a id="sec-700"></a>+<a id="sec-708"></a>> **Source:** `docs/trust-primitives.md` · [↑ table of contents](#table-of-contents)@@ -157851,7 +158458,7 @@ any chain**, regardless of which platform that counterparty was minted on.## Cross-chain Agent Reputation**`GET /api/x402/agent-reputation?subject=<identifier>`** — $0.01 USDC per call-(Base or Solana mainnet, via [x402](#sec-862)).+(Base or Solana mainnet, via [x402](#sec-877)).Pass any counterparty identifier. The type is auto-detected and scored from whateverreal on-chain evidence exists for it:@@ -157969,7 +158576,7 @@ Returns `{ mode, count, scored_count, unknown_count, avg_score, subjects: [ …fThe same POST route also serves three.ws-fleet monitoring over the platform's indexedactive-agent set: `mode: "sweep"` (fleet average + flagged low-trust agents),`mode: "leaderboard"` (top N by score), and `mode: "decay_report"` (agents whose score-dropped >10 points). See the [x402 catalog](#sec-862).+dropped >10 points). See the [x402 catalog](#sec-877).---@@ -157994,7 +158601,7 @@ claims **"I am the deployer of contract X"** or **"I own wallet W / name N / ageself-report.**`GET /api/x402/onchain-identity-verify?identity=<id>&address=<addr>&chain=<caip2>`**-— $0.005 USDC per call (Base or Solana mainnet, via [x402](#sec-862)).+— $0.005 USDC per call (Base or Solana mainnet, via [x402](#sec-877)).It verifies a **claim** that `identity` controls `address`, for **any** identity type,on any chain — regardless of the platform the counterparty came from:@@ -158068,11 +158675,11 @@ score *whether to trust* them.----See also: [x402 paid endpoints](#sec-862) · [Agent Bouncer](#sec-124) · [ERC-8004 identity](#sec-263)+See also: [x402 paid endpoints](#sec-877) · [Agent Bouncer](#sec-125) · [ERC-8004 identity](#sec-266)----<a id="sec-701"></a>+<a id="sec-709"></a>> **Source:** `docs/tty-avatar.md` · [↑ table of contents](#table-of-contents)@@ -158170,7 +158777,7 @@ Id resolution uses the same public endpoints the web studio does: `/api/avatars/----<a id="sec-702"></a>+<a id="sec-710"></a>> **Source:** `docs/tty.md` · [↑ table of contents](#table-of-contents)@@ -158314,7 +158921,7 @@ are lifted rather than crushed to black.----<a id="sec-703"></a>+<a id="sec-711"></a>> **Source:** `docs/tutorials/add-a-3d-assistant.md` · [↑ table of contents](#table-of-contents)@@ -158432,7 +159039,7 @@ Then ask, in plain language: "build a 3D assistant widget named Aria with an oce----<a id="sec-704"></a>+<a id="sec-712"></a>> **Source:** `docs/tutorials/agent-personality.md` · [↑ table of contents](#table-of-contents)@@ -158885,7 +159492,7 @@ The system prompt is the cheapest, highest-leverage thing you can change about a----<a id="sec-705"></a>+<a id="sec-713"></a>> **Source:** `docs/tutorials/agent-reputation.md` · [↑ table of contents](#table-of-contents)@@ -159162,7 +159769,7 @@ A read costs nothing and asks no one's permission. That's the property that lets----<a id="sec-706"></a>+<a id="sec-714"></a>> **Source:** `docs/tutorials/agent-spending-envelope.md` · [↑ table of contents](#table-of-contents)@@ -159725,7 +160332,7 @@ The two "budget stays reserved" cases are the only place the system deliberately----<a id="sec-707"></a>+<a id="sec-715"></a>> **Source:** `docs/tutorials/animate-your-agent.md` · [↑ table of contents](#table-of-contents)@@ -159905,7 +160512,7 @@ The difference that matters is the layer. `wave`, `point`, `nod` and `shrug` are----<a id="sec-708"></a>+<a id="sec-716"></a>> **Source:** `docs/tutorials/animate-your-avatar.md` · [↑ table of contents](#table-of-contents)@@ -160091,7 +160698,7 @@ Applying clips in the Studio is the **authoring** side. On a *running* agent, thThe two channels are wired to the *same* emotional state, at two different timescales, so the body and the face never disagree:- **Momentary events** (an error just happened, a skill just finished) inject a transient emotion spike, `concern`, `celebration`, `curiosity`, and friends, that decays over seconds. A spike crossing threshold both reshapes the face immediately *and* biases the gesture slot the avatar plays next (e.g. sustained `celebration` picks the `celebrate` slot).-- **Sustained mood**: the agent's resting valence/arousal, set via `setMood()` (see [docs/tutorials/emotion-from-data.md](#sec-724)), is the continuous baseline between events. It biases the resting face (a soft smile at high valence, a worried brow at low) and posture (lean, gaze) every frame, and, once nothing more urgent claims the gesture slot, biases *which* ambient gesture plays too: a sustained up-and-energetic mood leans toward the `celebrate` slot, a sustained down-and-subdued mood toward `concern`, the opposite bias, never the energetic one. A momentary event always takes priority over the ambient mood bias, and slot overrides via `meta.edits.animations` apply identically whether the trigger was a spike or the resting mood.+- **Sustained mood**: the agent's resting valence/arousal, set via `setMood()` (see [docs/tutorials/emotion-from-data.md](#sec-732)), is the continuous baseline between events. It biases the resting face (a soft smile at high valence, a worried brow at low) and posture (lean, gaze) every frame, and, once nothing more urgent claims the gesture slot, biases *which* ambient gesture plays too: a sustained up-and-energetic mood leans toward the `celebrate` slot, a sustained down-and-subdued mood toward `concern`, the opposite bias, never the energetic one. A momentary event always takes priority over the ambient mood bias, and slot overrides via `meta.edits.animations` apply identically whether the trigger was a spike or the resting mood.The division of labor: **clips move the body, blendshapes move the face, slots choose *which* body motion fits the emotion, and one emotional state, not two independent tracks, drives all of it.** All three ride the same universal-rig foundation, name your bones (and your blendshapes) in a convention the resolvers know, and everything just works.@@ -160131,14 +160738,14 @@ You learned the apply-and-remix workflow for motion on three.ws:- [docs/animations.md](#sec-101): the runtime animation registry, manifest, and agent slot reference.- [docs/3d-asset-pipeline.md](#sec-002), how FBX, GLB, and clip JSON relate, and how clips are built and retargeted.-- [docs/tutorials/swap-avatar-in-studio.md](#sec-763), loading and switching avatars in the Studio.-- [docs/tutorials/upload-custom-glb.md](#sec-766), getting a Mixamo or custom rig into three.ws as a clean, animatable GLB.+- [docs/tutorials/swap-avatar-in-studio.md](#sec-771), loading and switching avatars in the Studio.+- [docs/tutorials/upload-custom-glb.md](#sec-774), getting a Mixamo or custom rig into three.ws as a clean, animatable GLB.Primary call to action: open **[/pose](/pose)**, load an avatar, and apply your first clip.----<a id="sec-709"></a>+<a id="sec-717"></a>> **Source:** `docs/tutorials/arm-an-agent-sniper.md` · [↑ table of contents](#table-of-contents)@@ -160252,7 +160859,7 @@ The hard-config sniper you just armed is the control group. The next phase runs----<a id="sec-710"></a>+<a id="sec-718"></a>> **Source:** `docs/tutorials/build-a-3d-asset-pipeline.md` · [↑ table of contents](#table-of-contents)@@ -160471,7 +161078,7 @@ step once the mechanical stages are running.----<a id="sec-711"></a>+<a id="sec-719"></a>> **Source:** `docs/tutorials/build-a-scene.md` · [↑ table of contents](#table-of-contents)@@ -160694,7 +161301,7 @@ The leverage of [Scene Studio](/scene) is that it's a *real* editor producing a----<a id="sec-712"></a>+<a id="sec-720"></a>> **Source:** `docs/tutorials/build-a-site-concierge.md` · [↑ table of contents](#table-of-contents)@@ -160812,7 +161419,7 @@ Then: `<three-concierge endpoint="/my/concierge">`. The production reference, wi----<a id="sec-713"></a>+<a id="sec-721"></a>> **Source:** `docs/tutorials/character-library-to-embed.md` · [↑ table of contents](#table-of-contents)@@ -161321,7 +161928,7 @@ Doing the copy server-side also sidesteps cross-origin reads and browser upload----<a id="sec-714"></a>+<a id="sec-722"></a>> **Source:** `docs/tutorials/claim-threews-name.md` · [↑ table of contents](#table-of-contents)@@ -161636,7 +162243,7 @@ See also:----<a id="sec-715"></a>+<a id="sec-723"></a>> **Source:** `docs/tutorials/connect-ai-brain.md` · [↑ table of contents](#table-of-contents)@@ -162064,7 +162671,7 @@ The brain is the part of the agent you'll iterate on most after the system promp----<a id="sec-716"></a>+<a id="sec-724"></a>> **Source:** `docs/tutorials/connect-your-home.md` · [↑ table of contents](#table-of-contents)@@ -162444,14 +163051,14 @@ requirement.- [`@three-ws/home-mcp`](../packages/home-mcp/README.md): the five tools, and the gate over stdio.- [`@three-ws/home-bridge`](../packages/home-bridge/README.md): the library underneath, if youare building your own client.-- [docs/smart-home.md](#sec-651): why Home Assistant owns the device layer, what else was+- [docs/smart-home.md](#sec-659): why Home Assistant owns the device layer, what else wasevaluated, and where this goes next.-- [docs/home-households.md](#sec-341): roles, scopes and invites in full.-- [docs/home-privacy.md](#sec-343): what is kept, for how long, and how to delete it.+- [docs/home-households.md](#sec-345): roles, scopes and invites in full.+- [docs/home-privacy.md](#sec-347): what is kept, for how long, and how to delete it.----<a id="sec-717"></a>+<a id="sec-725"></a>> **Source:** `docs/tutorials/create-and-edit-memory.md` · [↑ table of contents](#table-of-contents)@@ -162772,7 +163379,7 @@ The leverage is in *enhancement*: the right type, one fact per memory, tags, del----<a id="sec-718"></a>+<a id="sec-726"></a>> **Source:** `docs/tutorials/custom-skill.md` · [↑ table of contents](#table-of-contents)@@ -163301,7 +163908,7 @@ The skill installs via a URI in the agent manifest, runs entirely client-side, a----<a id="sec-719"></a>+<a id="sec-727"></a>> **Source:** `docs/tutorials/customize-appearance.md` · [↑ table of contents](#table-of-contents)@@ -163743,7 +164350,7 @@ Most production embeds use four or five of these together. The combination is wh----<a id="sec-720"></a>+<a id="sec-728"></a>> **Source:** `docs/tutorials/deploy-to-vercel-custom-domain.md` · [↑ table of contents](#table-of-contents)@@ -164263,7 +164870,7 @@ In rough order of likelihood:----<a id="sec-721"></a>+<a id="sec-729"></a>> **Source:** `docs/tutorials/earn-and-spend-in-play.md` · [↑ table of contents](#table-of-contents)@@ -164458,16 +165065,16 @@ Every paid sale splits 50% to the holder-rewards sink and 50% to the treasury.## Next-- **[The in-game economy](#sec-380)** is the full reference: every+- **[The in-game economy](#sec-384)** is the full reference: everycatalog, gate, settlement path, and the JSON wire format.- **[three.ws/play/economy](https://three.ws/play/economy)** shows the livecatalogs and odds, read from the running server.-- **[Coin communities](#sec-194)** explains the worlds themselves, and how+- **[Coin communities](#sec-195)** explains the worlds themselves, and howany coin becomes a walkable 3D space.----<a id="sec-722"></a>+<a id="sec-730"></a>> **Source:** `docs/tutorials/embed-in-30-seconds.md` · [↑ table of contents](#table-of-contents)@@ -164747,7 +165354,7 @@ A working embedded agent is the foundation everything else builds on. From here,----<a id="sec-723"></a>+<a id="sec-731"></a>> **Source:** `docs/tutorials/embed-on-website.md` · [↑ table of contents](#table-of-contents)@@ -165262,7 +165869,7 @@ Squarespace's developer preview and published output can differ. Try adding the----<a id="sec-724"></a>+<a id="sec-732"></a>> **Source:** `docs/tutorials/emotion-from-data.md` · [↑ table of contents](#table-of-contents)@@ -165373,7 +165980,7 @@ Save that as `index.html` and open it: no build step, no server, no wallet. Swap## Step 3: The AI lane: real classification over arbitrary data, richer gestures-A lexicon scorer only works on short, informal text, and it only fires on words it already knows. For real documents (support tickets, product reviews, meeting transcripts, incident reports) you want a model that actually reads the thing and returns *structured* output: a graded sentiment score plus the findings and risk flags behind it, so the reaction tracks the document's real tone instead of its vocabulary. `ibm_granite_analyze` (part of the [IBM Granite x402 MCP suite](#sec-377)) does exactly this for $0.04/call, no IBM account needed: you pay in USDC, it pays IBM.+A lexicon scorer only works on short, informal text, and it only fires on words it already knows. For real documents (support tickets, product reviews, meeting transcripts, incident reports) you want a model that actually reads the thing and returns *structured* output: a graded sentiment score plus the findings and risk flags behind it, so the reaction tracks the document's real tone instead of its vocabulary. `ibm_granite_analyze` (part of the [IBM Granite x402 MCP suite](#sec-381)) does exactly this for $0.04/call, no IBM account needed: you pay in USDC, it pays IBM.The tool returns a fixed set of keys: `summary`, `entities`, `sentiment` (`{ overall, score }`, score in -1..1), `key_findings`, `risk_flags` (each with a `severity`), and `next_steps`. The two the animation layer cares about are `sentiment.score` and `risk_flags`.@@ -165489,7 +166096,7 @@ function reactIfConfident(clipOrEmoteName, { confident, useExactClip = false } =- **The agent keeps re-celebrating every poll.** You skipped the cooldown gate in Step 4, or your confidence threshold is too low for a noisy feed. Widen `COOLDOWN_MS` or raise the sample-size/strength floor.- **AI lane 402 loop / never resolves.** Your `SOLANA_PRIVATE_KEY` wallet has no USDC. Fund it with a few cents, see the [x402 payment flow](/tutorials/pay-for-x402-service).- **`analysis.sentiment` is undefined.** Granite returned something that wasn't a clean JSON analysis object; the tool falls back to `{ ok: true, raw_response, parse_error }` in that case. Log `analysis.parse_error` and `analysis.raw_response` to see what came back. The `gestureFor()` above already treats a missing score as "no gesture" rather than crashing.-- **Every document scores middling and nothing ever plays.** `analysis_type: 'sentiment'` tunes the model toward tone; the other five types (`general`, `contract`, `financial`, `technical`, `medical`) return the same keys but reason about different things, so a contract analyzed as `general` often lands near 0. Match the type to your data (see [ibm-x402-mcp](#sec-377)).+- **Every document scores middling and nothing ever plays.** `analysis_type: 'sentiment'` tunes the model toward tone; the other five types (`general`, `contract`, `financial`, `technical`, `medical`) return the same keys but reason about different things, so a contract analyzed as `general` often lands near 0. Match the type to your data (see [ibm-x402-mcp](#sec-381)).---@@ -165504,7 +166111,7 @@ function reactIfConfident(clipOrEmoteName, { confident, useExactClip = false } =----<a id="sec-725"></a>+<a id="sec-733"></a>> **Source:** `docs/tutorials/explore-docs-world.md` · [↑ table of contents](#table-of-contents)@@ -165585,13 +166192,13 @@ Make one with the [Forge](/create) or the [Avatar Studio](/avatar-studio), copy## Where to next-- [Docs World reference](#sec-250): controls table, device behaviour, contributor notes.-- [What is three.ws?](#sec-666): the guided tour of the whole platform, readable in either surface.+- [Docs World reference](#sec-253): controls table, device behaviour, contributor notes.+- [What is three.ws?](#sec-674): the guided tour of the whole platform, readable in either surface.- Add a page to the docs yourself: edit `docs/nav.json` and drop a markdown file in `docs/`; it appears in the sidebar and as a page in its pavilion with no extra wiring.----<a id="sec-726"></a>+<a id="sec-734"></a>> **Source:** `docs/tutorials/find-a-better-exit-policy.md` · [↑ table of contents](#table-of-contents)@@ -165794,7 +166401,7 @@ returned over every replayable trade in the corpus, with the caveats attached anthe underlying transactions one click away.If you run your own agent, the same parameters are what-[`/api/sniper/strategy`](#sec-124) accepts, so a finding here maps+[`/api/sniper/strategy`](#sec-125) accepts, so a finding here mapsdirectly onto a strategy you can arm. Read[Arm an autonomous sniper](/tutorials/arm-an-agent-sniper) for that path, andsize it small first: an in-sample optimum is a description of the past, and the@@ -165834,7 +166441,7 @@ disclaimers bolted onto the result. They are the result.----<a id="sec-727"></a>+<a id="sec-735"></a>> **Source:** `docs/tutorials/first-agent.md` · [↑ table of contents](#table-of-contents)@@ -166347,7 +166954,7 @@ Now that you have a working agent, here's what to explore next:----<a id="sec-728"></a>+<a id="sec-736"></a>> **Source:** `docs/tutorials/first-prompt-to-3d.md` · [↑ table of contents](#table-of-contents)@@ -166471,7 +167078,7 @@ A rigged avatar's AR link gains a **Bring it to life** option: instead of a froz----<a id="sec-729"></a>+<a id="sec-737"></a>> **Source:** `docs/tutorials/generate-3d-api.md` · [↑ table of contents](#table-of-contents)@@ -166700,7 +167307,7 @@ If you've never made an x402 call, start with [Build a paid x402 endpoint](/tuto----<a id="sec-730"></a>+<a id="sec-738"></a>> **Source:** `docs/tutorials/getting-started.md` · [↑ table of contents](#table-of-contents)@@ -166889,7 +167496,7 @@ Everything is editable forever — swap the body, rewrite the prompt, add capabi----<a id="sec-731"></a>+<a id="sec-739"></a>> **Source:** `docs/tutorials/greeting-and-first-speech.md` · [↑ table of contents](#table-of-contents)@@ -167241,7 +167848,7 @@ A working greeting moves the embed from "decoration" to "interaction", which is----<a id="sec-732"></a>+<a id="sec-740"></a>> **Source:** `docs/tutorials/grok-bot-recipes.md` · [↑ table of contents](#table-of-contents)@@ -167461,7 +168068,7 @@ This one is hand-written rather than a stored guided prompt, to keep the Solana-----<a id="sec-733"></a>+<a id="sec-741"></a>> **Source:** `docs/tutorials/image-to-3d.md` · [↑ table of contents](#table-of-contents)@@ -167568,7 +168175,7 @@ Everything you generate is kept in **Your creations** at the bottom of the page,----<a id="sec-734"></a>+<a id="sec-742"></a>> **Source:** `docs/tutorials/import-avatar-url.md` · [↑ table of contents](#table-of-contents)@@ -167742,7 +168349,7 @@ The URL path and the file-upload path converge on the same avatar record and the----<a id="sec-735"></a>+<a id="sec-743"></a>> **Source:** `docs/tutorials/js-api-events.md` · [↑ table of contents](#table-of-contents)@@ -168208,7 +168815,7 @@ The `whenReady`, awaited-`ask()`, and try/catch patterns are small but they remo----<a id="sec-736"></a>+<a id="sec-744"></a>> **Source:** `docs/tutorials/mcp-server-for-your-agent.md` · [↑ table of contents](#table-of-contents)@@ -168863,7 +169470,7 @@ Things that look right but bite you:----<a id="sec-737"></a>+<a id="sec-745"></a>> **Source:** `docs/tutorials/mine-vanity-address.md` · [↑ table of contents](#table-of-contents)@@ -169145,7 +169752,7 @@ The protocol itself is fully specified in [docs/PROTOCOL-vanity.md](#sec-006), a----<a id="sec-738"></a>+<a id="sec-746"></a>> **Source:** `docs/tutorials/mint-pumpfun-token.md` · [↑ table of contents](#table-of-contents)@@ -169506,7 +170113,7 @@ If you have a lawyer, talk to them before launching. If you don't, default to th----<a id="sec-739"></a>+<a id="sec-747"></a>> **Source:** `docs/tutorials/monetize-mcp-server.md` · [↑ table of contents](#table-of-contents)@@ -169822,7 +170429,7 @@ That connector can search the bazaar, read your challenge without paying (`inspe----<a id="sec-740"></a>+<a id="sec-748"></a>> **Source:** `docs/tutorials/multi-agent-coordination.md` · [↑ table of contents](#table-of-contents)@@ -170227,7 +170834,7 @@ researcher.addEventListener('skill:tool-called', (e) => {Build the tools themselves as skills (see [custom-skill](/tutorials/custom-skill)); the orchestration logic stays in the coordinator on the page.-There's also a platform-native alternative to page-level orchestration: the `<agent-stage>` element. A stage hosts every child `<agent-3d>` in one shared WebGL scene (with a `formation` attribute — `row`, `circle`, or `freeform`), exposes `getAgents()`, `broadcast(fromId, event)`, and `routeMessage(fromId, toId, text)` to your code, and grants each staged agent two extra built-in tools — `observe_agents` (who else is on stage) and `say_to_agent` (address a colleague directly) — so the LLMs can delegate to each other without any coordinator glue. When the agents, not the page, should decide who does what, reach for the stage. The full patterns are in [Multi-Agent Scenes](#sec-438).+There's also a platform-native alternative to page-level orchestration: the `<agent-stage>` element. A stage hosts every child `<agent-3d>` in one shared WebGL scene (with a `formation` attribute — `row`, `circle`, or `freeform`), exposes `getAgents()`, `broadcast(fromId, event)`, and `routeMessage(fromId, toId, text)` to your code, and grants each staged agent two extra built-in tools — `observe_agents` (who else is on stage) and `say_to_agent` (address a colleague directly) — so the LLMs can delegate to each other without any coordinator glue. When the agents, not the page, should decide who does what, reach for the stage. The full patterns are in [Multi-Agent Scenes](#sec-442).Parallel fan-out is **harder to debug** than sequential delegation because errors are non-deterministic in order and any latency outlier blocks the join. Use it when the wall-clock saving is worth the complexity. For a chat UX with a human in the loop, sequential is almost always the right default.@@ -170382,7 +170989,7 @@ async function safeHandoff(targetEl, brief, fallbackEl, originalQuestion) {----<a id="sec-741"></a>+<a id="sec-749"></a>> **Source:** `docs/tutorials/nvidia-3d-free.md` · [↑ table of contents](#table-of-contents)@@ -170504,7 +171111,7 @@ It talks **directly** to a TRELLIS NIM and returns the GLB **synchronously** in----<a id="sec-742"></a>+<a id="sec-750"></a>> **Source:** `docs/tutorials/nvidia-nim-self-host.md` · [↑ table of contents](#table-of-contents)@@ -170687,7 +171294,7 @@ The proxy normalizes every documented artifact shape (inline `base64`, a bare st----<a id="sec-743"></a>+<a id="sec-751"></a>> **Source:** `docs/tutorials/paid-x402-endpoint.md` · [↑ table of contents](#table-of-contents)@@ -171379,7 +171986,7 @@ Both work. Choose based on whether your endpoint is part of an agent platform yo----<a id="sec-744"></a>+<a id="sec-752"></a>> **Source:** `docs/tutorials/pay-for-x402-service.md` · [↑ table of contents](#table-of-contents)@@ -171661,7 +172268,7 @@ package family is listed under [x402 → Open-source packages](/x402#open-source----<a id="sec-745"></a>+<a id="sec-753"></a>> **Source:** `docs/tutorials/personal-ai-site.md` · [↑ table of contents](#table-of-contents)@@ -172216,7 +172823,7 @@ The technical investment is one HTML file, a GLB avatar, and a system prompt. Th----<a id="sec-746"></a>+<a id="sec-754"></a>> **Source:** `docs/tutorials/place-agent-irl.md` · [↑ table of contents](#table-of-contents)@@ -172469,7 +173076,7 @@ This is fundamentally different from viewing a single model in AR. If you only n----<a id="sec-747"></a>+<a id="sec-755"></a>> **Source:** `docs/tutorials/prompts-for-3d.md` · [↑ table of contents](#table-of-contents)@@ -172609,7 +173216,7 @@ The tiers are explained in detail in [the text-to-3D tutorial](/tutorials/text-t----<a id="sec-748"></a>+<a id="sec-756"></a>> **Source:** `docs/tutorials/read-the-trading-fleet.md` · [↑ table of contents](#table-of-contents)@@ -172836,7 +173443,7 @@ funds.----<a id="sec-749"></a>+<a id="sec-757"></a>> **Source:** `docs/tutorials/register-onchain.md` · [↑ table of contents](#table-of-contents)@@ -173185,7 +173792,7 @@ Your agent's URL will keep working as long as Base exists and IPFS gateways serv----<a id="sec-750"></a>+<a id="sec-758"></a>> **Source:** `docs/tutorials/render-avatar-images.md` · [↑ table of contents](#table-of-contents)@@ -173731,7 +174338,7 @@ If you want a talking, animated agent rather than a viewer, that is the `<agent-----<a id="sec-751"></a>+<a id="sec-759"></a>> **Source:** `docs/tutorials/self-host-agent-backend.md` · [↑ table of contents](#table-of-contents)@@ -173973,7 +174580,7 @@ curl http://localhost:3000/api/healthzYou should get a JSON body starting `{"status":"ok","service":"3d-agent",...}`, with `uptime`, the resolved `version`, and a per-subsystem readiness block (`x402`, mail, and so on). Anything other than `"status":"ok"` names the subsystem that is unhappy.-Look at the response headers too. Every handler that goes through `wrap()` in `api/_lib/http.js` stamps its response with `x-brownout` (and `x-brownout-trace` when an upstream was involved), saying which provider or cache tier answered and how fresh the data is; the same seam honours an `x-brownout-chaos` directive for reproducing an outage on demand. Both are documented in [Brownout](#sec-173), and neither needs any configuration on your fork.+Look at the response headers too. Every handler that goes through `wrap()` in `api/_lib/http.js` stamps its response with `x-brownout` (and `x-brownout-trace` when an upstream was involved), saying which provider or cache tier answered and how fresh the data is; the same seam honours an `x-brownout-chaos` directive for reproducing an outage on demand. Both are documented in [Brownout](#sec-174), and neither needs any configuration on your fork.Now open `http://localhost:3000` in a browser. You should land on the platform's home page. Click into the editor — drag any GLB onto it — confirm the avatar loads. Open DevTools → Console. **There should be no red errors.** If there are, the most common causes:@@ -174308,7 +174915,7 @@ A self-hosted instance with light traffic runs at $20–50/month all-in. The dom----<a id="sec-752"></a>+<a id="sec-760"></a>> **Source:** `docs/tutorials/selfie-to-avatar.md` · [↑ table of contents](#table-of-contents)@@ -174347,7 +174954,7 @@ Under the hood the page ([src/selfie-capture.js](../src/selfie-capture.js)) coll1. `POST /api/avatars/reconstruct` — submit the photos, get back a `jobId`.2. `GET /api/avatars/regenerate-status?jobId=…` — poll until the job reports `done`.-The job moves through visible stages — reconstructing the mesh, building geometry and textures, **auto-rigging the skeleton and skinning** — then returns the finished avatar's id. You never call the rig step yourself; it's part of the job. This is the platform-wide rule: every avatar three.ws creates is auto-rigged so it can animate. (For the rig internals, see [Avatar Creation](#sec-144).)+The job moves through visible stages — reconstructing the mesh, building geometry and textures, **auto-rigging the skeleton and skinning** — then returns the finished avatar's id. You never call the rig step yourself; it's part of the job. This is the platform-wide rule: every avatar three.ws creates is auto-rigged so it can animate. (For the rig internals, see [Avatar Creation](#sec-145).)---@@ -174509,7 +175116,7 @@ Because the output is a clean, rigged glTF 2.0 file, it isn't locked to three.ws- **Animate it** in the [Animation Studio](/pose) — load it, browse the clip gallery, and retarget motion onto it live. It works because it's rigged.- **Download the GLB** from the avatar page to use it in Unity, Unreal, Blender, or any glTF-aware tool.- **Embed it** on a website with the web component — see [Embed in 30 seconds](/tutorials/embed-in-30-seconds).-- **Refine the look** in the avatar editor at `/avatars/<id>/edit`. Clothing and accessories layer on top of the GLB without re-rigging it; [Avatar Creation](#sec-144) documents how that layering works.+- **Refine the look** in the avatar editor at `/avatars/<id>/edit`. Clothing and accessories layer on top of the GLB without re-rigging it; [Avatar Creation](#sec-145) documents how that layering works.- **Tune how it looks on your site** with [Customize size, position and background](/tutorials/customize-appearance), which covers the embed's layout, framing, and backdrop.---@@ -174558,13 +175165,13 @@ The result is a standard `.glb` that animates in the [Animation Studio](/pose),- [Turn Photos into a 3D Model](/tutorials/image-to-3d) — reconstruct an *object* (not a person) from a few photos in the Forge.- [Animate your avatar](/tutorials/animate-your-avatar) — apply and tune motion on the rigged avatar you just built.-- [Avatar Creation](#sec-144) — the full reference: every creation path, rig requirements, and accessories.+- [Avatar Creation](#sec-145) — the full reference: every creation path, rig requirements, and accessories.- [Customize size, position and background](/tutorials/customize-appearance): how the finished avatar is framed and placed once it is embedded on a page.- [Give your agent a personality](/tutorials/agent-personality) — turn the body into a character.----<a id="sec-753"></a>+<a id="sec-761"></a>> **Source:** `docs/tutorials/sell-a-skill-with-a-trial.md` · [↑ table of contents](#table-of-contents)@@ -174710,7 +175317,7 @@ Two rules, and they are not style preferences:1. **Spend the run only after the work succeeded.** Decrementing before the work means a timeout or a bad upstream bills your buyer for nothing. That is the fastest way to make a trial feel like a scam.2. **If you grant a trial, you must spend it.** A trial that is never spent never reaches `trial_exhausted`, and because an active trial counts as access, step 4 below can never happen for that buyer. Conversion does not get slower. It stops.-> **This is a real bug we shipped, not a hypothetical.** The [circulation engine](#sec-189) granted trials for a month and never called `consumeTrialUse`, because the only code path that called it was one those agents never used. It accumulated 10,282 trial rows, zero sales, and not one exhausted trial. Marketplace revenue read as a demand problem for weeks. It was a missing decrement.+> **This is a real bug we shipped, not a hypothetical.** The [circulation engine](#sec-190) granted trials for a month and never called `consumeTrialUse`, because the only code path that called it was one those agents never used. It accumulated 10,282 trial rows, zero sales, and not one exhausted trial. Marketplace revenue read as a demand problem for weeks. It was a missing decrement.---@@ -174781,7 +175388,7 @@ A healthy funnel shows a mix of `trial` rows with counts ticking down and `confi----<a id="sec-754"></a>+<a id="sec-762"></a>> **Source:** `docs/tutorials/share-your-agent.md` · [↑ table of contents](#table-of-contents)@@ -175149,7 +175756,7 @@ The agent's URL is the durable handle. Embed it, link it, print it. The agent sh----<a id="sec-755"></a>+<a id="sec-763"></a>> **Source:** `docs/tutorials/ship-an-avatar-manifest.md` · [↑ table of contents](#table-of-contents)@@ -175170,7 +175777,7 @@ The thing you are building is small: a JSON file. What matters is what it buys y- Node 18 or newer, and `curl`. That is the whole toolchain.- No account, no API key, no wallet signature. Every command here runs offline against local files.-- Optional: the [Avatar CLI reference](#sec-143) is the exhaustive flag-by-flag contract. This tutorial is the guided path through it.+- Optional: the [Avatar CLI reference](#sec-144) is the exhaustive flag-by-flag contract. This tutorial is the guided path through it.Every command below is real and runs as written.@@ -175458,13 +176065,13 @@ A JSON file that names an avatar, pins its mesh by content rather than by locati**Next:**-- The [Avatar CLI reference](#sec-143) documents every flag, exit code, and `--json` shape.-- The [web component reference](#sec-799) covers everything `<agent-3d>` can do beyond rendering a body: voice, an LLM brain, memory, and skills.+- The [Avatar CLI reference](#sec-144) documents every flag, exit code, and `--json` shape.+- The [web component reference](#sec-811) covers everything `<agent-3d>` can do beyond rendering a body: voice, an LLM brain, memory, and skills.- [`@three-ws/avatar-schema`](../packages/avatar-schema/README.md) is the schema itself, for writing your own tooling against the format.----<a id="sec-756"></a>+<a id="sec-764"></a>> **Source:** `docs/tutorials/shopify-shopping-assistant.md` · [↑ table of contents](#table-of-contents)@@ -175582,7 +176189,7 @@ The [wire format](/docs/concierge) for the answer endpoint is documented, so you----<a id="sec-757"></a>+<a id="sec-765"></a>> **Source:** `docs/tutorials/shopify-store-guide-advanced.md` · [↑ table of contents](#table-of-contents)@@ -175892,7 +176499,7 @@ The clip URLs inside the manifest resolve **relative to the manifest**, so a sel----<a id="sec-758"></a>+<a id="sec-766"></a>> **Source:** `docs/tutorials/shopify-store-guide.md` · [↑ table of contents](#table-of-contents)@@ -175981,7 +176588,7 @@ It's powered by the open-source [`@three-ws/tour`](https://www.npmjs.com/package----<a id="sec-759"></a>+<a id="sec-767"></a>> **Source:** `docs/tutorials/sign-with-your-avatar.md` · [↑ table of contents](#table-of-contents)@@ -176195,9 +176802,9 @@ None of it replaces a human interpreter. It makes an avatar legible to signers i**See also:**-- [docs/sign-language.md](#sec-641): the full reference: vocabulary, developer APIs, and how the signing engine works-- [docs/tutorials/animate-your-avatar.md](#sec-708): the clip library, retargeting, and animated GLB export in depth-- [docs/web-component.md](#sec-799): every `<agent-3d>` attribute, including `sign-language`+- [docs/sign-language.md](#sec-649): the full reference: vocabulary, developer APIs, and how the signing engine works+- [docs/tutorials/animate-your-avatar.md](#sec-716): the clip library, retargeting, and animated GLB export in depth+- [docs/web-component.md](#sec-811): every `<agent-3d>` attribute, including `sign-language`- [/asl-alphabet](/asl-alphabet): the manual alphabet, letter by letter, with a practice drill- [examples/sign-language.html](../examples/sign-language.html): a runnable page with both integration paths@@ -176205,7 +176812,7 @@ Primary call to action: open **[/sign-language](/sign-language)** and sign your----<a id="sec-760"></a>+<a id="sec-768"></a>> **Source:** `docs/tutorials/skill-with-database-auth.md` · [↑ table of contents](#table-of-contents)@@ -176943,7 +177550,7 @@ Before this skill faces a real visitor:----<a id="sec-761"></a>+<a id="sec-769"></a>> **Source:** `docs/tutorials/solana-agent-reputation.md` · [↑ table of contents](#table-of-contents)@@ -177135,7 +177742,7 @@ A read costs nothing and asks no one's permission — which is exactly what lets----<a id="sec-762"></a>+<a id="sec-770"></a>> **Source:** `docs/tutorials/sperax-tour.md` · [↑ table of contents](#table-of-contents)@@ -177306,7 +177913,7 @@ This is covered by an automated test — [`tour-sdk/test/director.test.mjs`](htt----<a id="sec-763"></a>+<a id="sec-771"></a>> **Source:** `docs/tutorials/swap-avatar-in-studio.md` · [↑ table of contents](#table-of-contents)@@ -177504,7 +178111,7 @@ The key insight is the snippet's stability. Once embedded, your customers' pages----<a id="sec-764"></a>+<a id="sec-772"></a>> **Source:** `docs/tutorials/text-to-3d.md` · [↑ table of contents](#table-of-contents)@@ -177636,7 +178243,7 @@ This is normal — prompt, generate, adjust, repeat is the workflow, not a failu----<a id="sec-765"></a>+<a id="sec-773"></a>> **Source:** `docs/tutorials/trigger-from-page-events.md` · [↑ table of contents](#table-of-contents)@@ -178140,7 +178747,7 @@ The pattern under all of these is the same: every recipe starts with `whenReady(----<a id="sec-766"></a>+<a id="sec-774"></a>> **Source:** `docs/tutorials/upload-custom-glb.md` · [↑ table of contents](#table-of-contents)@@ -178572,7 +179179,7 @@ Once the body is on the platform, the embed snippet doesn't change. The same `<a----<a id="sec-767"></a>+<a id="sec-775"></a>> **Source:** `docs/tutorials/view-in-ar.md` · [↑ table of contents](#table-of-contents)@@ -178765,7 +179372,7 @@ AR surface detection needs a moment to work. Move the phone slowly over the targ----<a id="sec-768"></a>+<a id="sec-776"></a>> **Source:** `docs/tutorials/voice-and-lipsync.md` · [↑ table of contents](#table-of-contents)@@ -178910,7 +179517,7 @@ If you want your agent to speak in *your* voice instead of a built-in one, use t4. Give the voice a **name** (1–64 characters) and click **Clone**. The page uploads the sample to `POST /api/tts/eleven-clone` ([`api/tts/eleven-clone.js`](../api/tts/eleven-clone.js)) as `multipart/form-data`.5. On success you get a `voice_id`, and the voice is saved to your library (stored in `localStorage`, up to 20 voices).-**Test it in the playground.** Pick the cloned voice, type a sample line, and click Speak. The playground calls `POST /api/tts/eleven` ([`api/tts/eleven.js`](../api/tts/eleven.js)) with `{ voiceId, text }`, which proxies ElevenLabs and caches the clip for 30 days (the hint shows `cached` vs `generated`). Default model is `eleven_flash_v2_5`; requests are capped at 500 characters and metered to your credit balance ($0.30 per 1,000 characters on the platform key, or free of platform charges with your own ElevenLabs key in the `x-eleven-key` header; see the [Voice Lab billing section](#sec-796)).+**Test it in the playground.** Pick the cloned voice, type a sample line, and click Speak. The playground calls `POST /api/tts/eleven` ([`api/tts/eleven.js`](../api/tts/eleven.js)) with `{ voiceId, text }`, which proxies ElevenLabs and caches the clip for 30 days (the hint shows `cached` vs `generated`). Default model is `eleven_flash_v2_5`; requests are capped at 500 characters and metered to your credit balance ($0.30 per 1,000 characters on the platform key, or free of platform charges with your own ElevenLabs key in the `x-eleven-key` header; see the [Voice Lab billing section](#sec-807)).> Instant Voice Cloning is a **paid-tier ElevenLabs feature** (Starter and up). If the server's account is on the free tier, the clone call returns the upstream error verbatim in the status line (e.g. a `can_not_use_instant_voice_cloning` message). Built-in voices in Step 1 have no such requirement.@@ -179020,7 +179627,7 @@ The leverage is that the avatar drives its mouth from the *audio it actually pla----<a id="sec-769"></a>+<a id="sec-777"></a>> **Source:** `docs/tutorials/walk-companion.md` · [↑ table of contents](#table-of-contents)@@ -179382,7 +179989,7 @@ The leverage is composability: the same engine renders the corner mascot, the fu----<a id="sec-770"></a>+<a id="sec-778"></a>> **Source:** `docs/tutorials/wallet-sign-in.md` · [↑ table of contents](#table-of-contents)@@ -179666,7 +180273,7 @@ A wallet sign-in that works from any origin that can reach the API, survives the----<a id="sec-771"></a>+<a id="sec-779"></a>> **Source:** `docs/tutorials/web-component-end-to-end.md` · [↑ table of contents](#table-of-contents)@@ -179759,7 +180366,7 @@ This is the right embed when:- You want multiple agents on the same page- You need to call the agent's methods or subscribe to its events-The rest of this tutorial uses the custom-element form, because that's the one that benefits from a wrapper. (The [embedding guide](#sec-723) covers the iframe path and the no-code platforms in depth.)+The rest of this tutorial uses the custom-element form, because that's the one that benefits from a wrapper. (The [embedding guide](#sec-731) covers the iframe path and the no-code platforms in depth.)---@@ -180265,12 +180872,12 @@ The web component is the most robust integration point the platform offers. Buil## Next steps- [Drive the agent with the JavaScript API](/tutorials/js-api-events), methods and events covered in depth-- [Embed a three.ws agent on your website](#sec-723), the no-framework paths (Webflow, WordPress, Squarespace) for completeness+- [Embed a three.ws agent on your website](#sec-731), the no-framework paths (Webflow, WordPress, Squarespace) for completeness- [Trigger the agent from page events](/tutorials/trigger-from-page-events), once it's mounted, make it react to the user journey----<a id="sec-772"></a>+<a id="sec-780"></a>> **Source:** `docs/tutorials/write-a-guard.md` · [↑ table of contents](#table-of-contents)@@ -180579,7 +181186,7 @@ Your guard is done when all of these are true:----<a id="sec-773"></a>+<a id="sec-781"></a>> **Source:** `docs/tutorials/x402-server-sdk.md` · [↑ table of contents](#table-of-contents)@@ -180792,7 +181399,7 @@ const res = await pay('https://your.api/v1/embed', { method: 'POST', body });----<a id="sec-774"></a>+<a id="sec-782"></a>> **Source:** `docs/ui-juice.md` · [↑ table of contents](#table-of-contents)@@ -180968,7 +181575,35 @@ should reach for these primitives rather than re-rolling RAF loops.----<a id="sec-775"></a>+<a id="sec-783"></a>++> **Source:** `docs/ui-lint.md` · [↑ table of contents](#table-of-contents)++# UI lint (lintapple)++[lintapple](https://github.com/gholtzap/lintapple) loads a running page in a browser and checks it against `ui-policy.json` at the repo root: font family and size, contrast, control size and gaps, viewport overflow, content clipping, root background, and ARIA state.++```+npm run dev # app on :3000+npx lintapple http://localhost:3000/gallery --ready main+npm run lint:ui # same, against the home URL+```++Exit codes: 0 pass, 1 findings, 2 the check could not finish (pages over 5000 elements, such as `/marketplace`, need a component-level target).++## Notes++- The policy ships with Apple system fonts and a 12 to 64px type scale. three.ws uses Inter, Space Grotesk and JetBrains Mono and a denser scale, so the font and size rules are noisy until the policy is tuned to our design tokens. The rules that carry signal today are `viewport-bounds`, `content-clipping`, `control-gap`, `root-background` and `control-state`.+- The home page is a windowed-desktop canvas with a plain HTML fallback behind it. Lint content pages (`/gallery`, `/create`) and pass `--ready` so the app has mounted.+- A passing run means the configured rules held. It is not a design review.++## Triage (2026-10-12)++First pass on `/gallery` and `/create` fixed the rules with signal: control gaps in the header and gallery, accessible names that dropped visible text (gallery tags and cards, create cards, the getting-started pill), icon-only buttons without a tooltip (header, footer, suggestions panel; use a `role="tooltip"` span linked by `aria-describedby`, styled by `.ui-tip`), and the root background. What remains is intentional or environmental: the skip link and visually hidden label sit off-screen on purpose, card titles and descriptions use `line-clamp`, the footer watermark bleeds by design, `Inter Fallback` fails to load only where Arial/Liberation Sans is not installed, and the walk companion's floating buttons are 22px circles (44px on coarse pointers).++---++<a id="sec-784"></a>> **Source:** `docs/uniswap-v4-hooks.md` · [↑ table of contents](#table-of-contents)@@ -181399,7 +182034,7 @@ requires 0.8.26 or newer. A v4 hook therefore needs:----<a id="sec-776"></a>+<a id="sec-785"></a>> **Source:** `docs/upstream/home-assistant-js-websocket-resubscribe-rejection.md` · [↑ table of contents](#table-of-contents)@@ -181534,7 +182169,7 @@ resume.----<a id="sec-777"></a>+<a id="sec-786"></a>> **Source:** `docs/user-wallet.md` · [↑ table of contents](#table-of-contents)@@ -181573,18 +182208,18 @@ They are different wallets with different jobs, and mixing them up is the single| Auth accepted | **session cookie only** (no API key, no bearer token) | session or scoped credential, depending on the path || Typical use | hold funds, top up agents, sweep out | pay x402 endpoints, trade, buy skills, receive earnings |-The practical consequence: **an API key cannot spend your master wallet, and neither can an agent.** Only a browser session belonging to you can. That is deliberate. The agent-side limits, freeze switch, and audit rails described in [custody.md](#sec-232) govern agent wallets; the master wallet's protection is that nothing autonomous can reach it at all, plus a hard ceiling of **5 outbound transactions per user per day** shared across `send` and `fund-agent`.+The practical consequence: **an API key cannot spend your master wallet, and neither can an agent.** Only a browser session belonging to you can. That is deliberate. The agent-side limits, freeze switch, and audit rails described in [custody.md](#sec-233) govern agent wallets; the master wallet's protection is that nothing autonomous can reach it at all, plus a hard ceiling of **5 outbound transactions per user per day** shared across `send` and `fund-agent`.Funds flow one way through the platform's plumbing: master wallet to agent wallet, via `fund-agent`. To go the other direction, use the agent's own owner withdrawal (see [agent-wallets.md](#sec-077)), which a freeze never blocks.## Auth model: session plus CSRF- Every route requires a signed-in **session cookie**. Without one: `401 unauthorized`. There is no bearer or API-key path on these four routes, unlike most of the API.-- Every write that moves funds additionally requires that your account has **signed the real-funds agreements** (Terms of Service, Risk Disclosure, Agent Wallet Agreement). Without a current signature the route answers `403 risk_ack_required` and nothing is sent; sign once at [/legal/agreements](https://three.ws/legal/agreements). A `simulate: true` preview is exempt, as is reading. See [risk-acknowledgment.md](#sec-618).+- Every write that moves funds additionally requires that your account has **signed the real-funds agreements** (Terms of Service, Risk Disclosure, Agent Wallet Agreement). Without a current signature the route answers `403 risk_ack_required` and nothing is sent; sign once at [/legal/agreements](https://three.ws/legal/agreements). A `simulate: true` preview is exempt, as is reading. See [risk-acknowledgment.md](#sec-625).- Every write (`POST`) additionally requires a one-time CSRF token in `X-CSRF-Token`, obtained from `GET /api/csrf-token`. The token is bound to your user id, single-use, and expires after an hour. Missing: `403 csrf_missing`. Stale or wrong: `403 csrf_invalid`. Fetch a fresh token per write.- Reads are rate limited at 60 per minute per user. Writes that move funds are limited to **5 per day per user**, and that limiter is critical: if its backend is unreachable in production the write is refused rather than uncapped. A `simulate: true` preview does **not** draw on that daily budget; previews have their own ceiling of 30 per minute per user, so pricing a transfer a few times can never lock you out of sending. Both money-moving routes are additionally limited per IP, as is wallet creation.-See [authentication.md](#sec-138) for how sessions and CSRF tokens work in general.+See [authentication.md](#sec-139) for how sessions and CSRF tokens work in general.The examples below assume a browser-style cookie jar in `cookies.txt` and a token in `$CSRF`:@@ -181754,7 +182389,7 @@ curl -sX POST https://three.ws/api/user/wallet/fund-agent \Same reserve logic as `send`, and mainnet only: a `"max"` SOL top-up leaves rent and fee headroom, and if the agent has no USDC account yet the transaction opens one and your master wallet pays the rent (refused with `insufficient_sol_for_fees` if your SOL cannot cover it). Without `simulate: true`, a well-formed call executes immediately; preview first when the amount is `"max"` or the agent might lack a token account.-Once the funds land, they are the agent's, and every further movement out of them runs through the agent's own spend policy, kill switch, and custody trail. Funding an agent is therefore the moment to decide how much autonomy you are comfortable financing: top up in the size you would be willing to lose to a bad strategy, not the whole balance. This is also the normal way to get USDC into an agent before it backs a vault ([vaults.md](#sec-792)) and the easiest way to send a vault the small SOL balance it needs for swap fees, by sending to the vault address with `send`.+Once the funds land, they are the agent's, and every further movement out of them runs through the agent's own spend policy, kill switch, and custody trail. Funding an agent is therefore the moment to decide how much autonomy you are comfortable financing: top up in the size you would be willing to lose to a bad strategy, not the whole balance. This is also the normal way to get USDC into an agent before it backs a vault ([vaults.md](#sec-801)) and the easiest way to send a vault the small SOL balance it needs for swap fees, by sending to the vault address with `send`.## On-chain history@@ -181815,14 +182450,14 @@ Honest limits, stated plainly: this is a **custodial** wallet, so the platform c## Related- [agent-wallets.md](#sec-077) for the per-agent wallet this one funds, and its spend policy-- [custody.md](#sec-232) for limits, freeze, proof of custody, and recovery on the agent side-- [vaults.md](#sec-792) for what a funded agent wallet can then back-- [authentication.md](#sec-138) for sessions, CSRF tokens, and why API keys do not apply here-- [money-map.md](#sec-435) for how funds move across the whole platform+- [custody.md](#sec-233) for limits, freeze, proof of custody, and recovery on the agent side+- [vaults.md](#sec-801) for what a funded agent wallet can then back+- [authentication.md](#sec-139) for sessions, CSRF tokens, and why API keys do not apply here+- [money-map.md](#sec-439) for how funds move across the whole platform----<a id="sec-778"></a>+<a id="sec-787"></a>> **Source:** `docs/ux-flows/01-onboarding-creation.md` · [↑ table of contents](#table-of-contents)@@ -182094,7 +182729,7 @@ Honest limits, stated plainly: this is a **custodial** wallet, so the platform c----<a id="sec-779"></a>+<a id="sec-788"></a>> **Source:** `docs/ux-flows/02-forge-text-to-3d.md` · [↑ table of contents](#table-of-contents)@@ -182277,7 +182912,7 @@ Routing facts (from `vercel.json`):----<a id="sec-780"></a>+<a id="sec-789"></a>> **Source:** `docs/ux-flows/03-3d-editing-viewer.md` · [↑ table of contents](#table-of-contents)@@ -182485,7 +183120,7 @@ Routing summary (from `vite.config.js`):----<a id="sec-781"></a>+<a id="sec-790"></a>> **Source:** `docs/ux-flows/04-embed-widget-studio.md` · [↑ table of contents](#table-of-contents)@@ -182661,7 +183296,7 @@ Routing recap (from `vercel.json`):----<a id="sec-782"></a>+<a id="sec-791"></a>> **Source:** `docs/ux-flows/05-discovery-social.md` · [↑ table of contents](#table-of-contents)@@ -182951,7 +183586,7 @@ Routing recap (from `vercel.json`):----<a id="sec-783"></a>+<a id="sec-792"></a>> **Source:** `docs/ux-flows/06-marketplace-skills.md` · [↑ table of contents](#table-of-contents)@@ -183170,7 +183805,7 @@ Routing facts confirmed in `vercel.json` (line numbers shift too often to pin; g----<a id="sec-784"></a>+<a id="sec-793"></a>> **Source:** `docs/ux-flows/07-crypto-trading-analytics.md` · [↑ table of contents](#table-of-contents)@@ -183583,7 +184218,7 @@ coin-intel, pump-visualizer and pump-live: adding a coin on any surface shows up----<a id="sec-785"></a>+<a id="sec-794"></a>> **Source:** `docs/ux-flows/08-coin-launch-wallets.md` · [↑ table of contents](#table-of-contents)@@ -183602,7 +184237,7 @@ real Solana/EVM RPC, pump.fun, and x402 — no mocks.---### Launch a Coin — `/launch`-- **Source:** `pages/launch.html` → `src/launch/launch-page.js` (the whole flow), with the pure form/cost logic in `src/launch/launch-model.js`, wallet connect/link/sign in `src/launch/launch-wallet.js`, styles in `src/launch/launch-page.css`. A Launch Studio recipe link (`?reward=`) mounts `public/studio/launch-panel.js` instead, because the fee-split handoff lives there. Reference doc: [the /launch launchpad](#sec-397).+- **Source:** `pages/launch.html` → `src/launch/launch-page.js` (the whole flow), with the pure form/cost logic in `src/launch/launch-model.js`, wallet connect/link/sign in `src/launch/launch-wallet.js`, styles in `src/launch/launch-page.css`. A Launch Studio recipe link (`?reward=`) mounts `public/studio/launch-panel.js` instead, because the fee-split handoff lives there. Reference doc: [the /launch launchpad](#sec-401).- **Entry point:** `#launch-app` mounts two tabs, **Create** and **My coins**. Create is a four-card form (link an agent, coin details, image, launch settings) beside a rail holding the live preview, the cost panel, the wallet card and the Launch button.- **Prerequisites / gates:**- Account/session required to launch (`GET /api/auth/me`). Signed out, the agent card offers Sign in / Create an agent and the button reads "Sign in to launch."@@ -183629,7 +184264,7 @@ real Solana/EVM RPC, pump.fun, and x402 — no mocks.- Connecting a wallet that is linked to another account surfaces a "Move wallet here" takeover that re-signs the link with `takeover: true`.- Confirmation still pending after 75 s: the dialog keeps the signature, links it on Solscan and offers "Check again" rather than declaring failure.- A `?reward=` recipe link mounts the studio launch panel instead of this flow.- - The hero links to `/launch/robinhood` ("Launch on Robinhood Chain with Pons instead"), a separate EVM launch flow documented in [Pons launch](#sec-500).+ - The hero links to `/launch/robinhood` ("Launch on Robinhood Chain with Pons instead"), a separate EVM launch flow documented in [Pons launch](#sec-507).- **External calls / dependencies:** `/api/pump/launch-config`, `/api/auth/me`, `/api/avatars`, `/api/pump/build-metadata`, `/api/pump/launch-prep`, `/api/pump/launch-confirm`, `/api/pump/launch-agent`, `/api/pump/agent-wallet`, `/api/pump/my-coins`, `/api/pump/collect-creator-fee-prep`, `/api/pump/collect-creator-fee-agent`, `/api/auth/wallets` (+ `/nonce-solana`, `/link-solana`), `/api/solana-rpc`. External: the pump.fun program (mint target), Solscan (links), x.com (share intent).- **Success state:** the live-coin dialog above, plus the coin appearing on `/launches` and its own `/launches/<mint>` page, and its creator rewards accruing under My coins.- **Empty / error states:** agent list loading skeletons, load failure with Try again ("Nothing was launched"), signed-out and no-agent empty states with their own CTAs; per-field counters and the blocker checklist; wallet card states for not installed / connect / connecting / conflicting account / connected (with a v0 or v1 badge) and the agent wallet's loading, error-with-retry and balance-unavailable forms; a blocking "needs ~X more SOL" line; in-dialog step errors written by `friendlyLaunchError` (cancelled signature, insufficient funds, unlinked wallet, expired session, rate limit, expired blockhash, unreachable RPC) with Close and Try again; the pending-confirmation recheck; a warning when the coin launched but the separate fee transfer did not (nothing was charged); My coins load error with retry and a "No coins yet" empty state.@@ -183826,7 +184461,7 @@ real Solana/EVM RPC, pump.fun, and x402 — no mocks.---### Coin 3D Snapshot — `/coin3d`-- **Source:** `pages/coin3d.html` → `src/coin3d/main.js`. Deep-linked from `/launches` cards and the MCP tool `pumpfun_token_3d`. Embedding reference: [Token in 3D, as an embed](#sec-196).+- **Source:** `pages/coin3d.html` → `src/coin3d/main.js`. Deep-linked from `/launches` cards and the MCP tool `pumpfun_token_3d`. Embedding reference: [Token in 3D, as an embed](#sec-197).- **Entry point:** Full-screen Three.js scene seeded by `?mint=<base58>` or `?pair=<pool address>` (& optional `&network=`); without either the page is a landing card. `?embed=1` drops the page chrome for framing on another site, keeps one attribution link and opens links in a new tab.- **Prerequisites / gates:** None. Read-only.- **Steps (N):**@@ -183852,7 +184487,7 @@ real Solana/EVM RPC, pump.fun, and x402 — no mocks.----<a id="sec-786"></a>+<a id="sec-795"></a>> **Source:** `docs/ux-flows/09-x402-agent-commerce.md` · [↑ table of contents](#table-of-contents)@@ -184199,7 +184834,7 @@ choreographed two-agent narrative driven by Server-Sent Events.----<a id="sec-787"></a>+<a id="sec-796"></a>> **Source:** `docs/ux-flows/10-chat-brain-labs.md` · [↑ table of contents](#table-of-contents)@@ -184443,7 +185078,7 @@ modules. Routes resolved via `vercel.json` rewrites.----<a id="sec-788"></a>+<a id="sec-797"></a>> **Source:** `docs/ux-flows/11-account-dashboard.md` · [↑ table of contents](#table-of-contents)@@ -184474,7 +185109,7 @@ Shared auth concepts:- **Post-auth redirect:** `?next=` query param → `sessionStorage.login_redirect` → default (`/dashboard` for login, `/create` for register). On `/login`, an already-authenticated visitor is bounced to `next` via a `GET /api/auth/me` probe on load. The value is sanitized by a shared `safeNext` helper: anything that is not a single-leading-slash same-site path (protocol-relative `//host`, backslashes, control characters) is silently discarded and the default is used, so a crafted external `?next=` can no longer navigate off-site. The Privy email and wallet paths (`src/privy-login.js`) run their `next` through the same helper.- **Auth hint:** every successful auth writes `localStorage['3dagent:auth-hint']` so other surfaces render a logged-in chrome optimistically.- **Terms clickwrap (ToS v3):** every auth surface asserts Terms acceptance. `/register` has a required checkbox; `/login` and the Privy/wallet paths use notice-style clickwrap ("By signing in... you agree to the Terms of Service and Privacy Policy") and send `tosAccepted: true`; the Privy SIWE message statement itself carries the agreement text. The server records `users.tos_accepted_version`/`tos_accepted_at` plus an append-only `audit_log` row (`api/_lib/legal.js`, `TOS_VERSION = 3`) and re-stamps on login.-- **Real-funds agreements (separate from sign-up):** signing up does not unlock money movement. Before a real-funds action (an armed sniper or Oracle watch, a custodial agent purchase, an x402 payment, a withdrawal) and before an agent wallet's deposit address is revealed, the account must separately sign three documents together at `/legal/agreements`: the Terms of Service (`/legal/tos`), the Risk Disclosure (`/legal/risk`), and the Agent Wallet Agreement (`/legal/agent-wallet`). Signatures are typed-name e-signatures recorded append-only in `legal_signatures`; the dialog is `public/risk-ack.js` posting to `/api/legal/risk-ack`, and every money-moving endpoint enforces it server-side through `requireRealFundsAgreement()` (`api/_lib/real-funds-agreement.js`), answering `403 risk_ack_required` over session and API key alike. Devnet is exempt. See [risk-acknowledgment.md](#sec-618).+- **Real-funds agreements (separate from sign-up):** signing up does not unlock money movement. Before a real-funds action (an armed sniper or Oracle watch, a custodial agent purchase, an x402 payment, a withdrawal) and before an agent wallet's deposit address is revealed, the account must separately sign three documents together at `/legal/agreements`: the Terms of Service (`/legal/tos`), the Risk Disclosure (`/legal/risk`), and the Agent Wallet Agreement (`/legal/agent-wallet`). Signatures are typed-name e-signatures recorded append-only in `legal_signatures`; the dialog is `public/risk-ack.js` posting to `/api/legal/risk-ack`, and every money-moving endpoint enforces it server-side through `requireRealFundsAgreement()` (`api/_lib/real-funds-agreement.js`), answering `403 risk_ack_required` over session and API key alike. Devnet is exempt. See [risk-acknowledgment.md](#sec-625).---@@ -184652,7 +185287,7 @@ Shared auth concepts:----<a id="sec-789"></a>+<a id="sec-798"></a>> **Source:** `docs/ux-flows/12-home-and-content.md` · [↑ table of contents](#table-of-contents)@@ -184899,7 +185534,7 @@ All `/.well-known/*` and `/openapi.json` / `/sitemap.xml` responses are JSON/XML----<a id="sec-790"></a>+<a id="sec-799"></a>> **Source:** `docs/validation.md` · [↑ table of contents](#table-of-contents)@@ -185102,7 +185737,7 @@ The hash stored on-chain is `keccak256(JSON.stringify(report))`. Anyone can reco2. `hashReport(report)` produces the same hash if the input is identical.3. Query `ValidationRegistry.getValidationStatus(requestHash)` (or `getAgentValidations(agentId)` for every request id on the agent) and compare its `responseHash`. `src/erc8004/validation-recorder.js` wraps this as `getLatestValidation({ agentId, runner, chainId })`.-The registry has no on-chain validator allow-list: any address the owner requests can answer. Which verdicts three.ws presents as "Validated" is off-chain policy, maintained in [`public/.well-known/validators.json`](../public/.well-known/validators.json). See [`specs/VALIDATORS.md`](../specs/VALIDATORS.md) for how to be recognized, and [`docs/erc8004/validation-attestation.md`](#sec-264) for the platform's own automatic attestation flow.+The registry has no on-chain validator allow-list: any address the owner requests can answer. Which verdicts three.ws presents as "Validated" is off-chain policy, maintained in [`public/.well-known/validators.json`](../public/.well-known/validators.json). See [`specs/VALIDATORS.md`](../specs/VALIDATORS.md) for how to be recognized, and [`docs/erc8004/validation-attestation.md`](#sec-267) for the platform's own automatic attestation flow.The minimum check suite for a `pass` verdict includes:@@ -185278,7 +185913,7 @@ The toggle's CSS class reflects the highest severity: `level-0` (errors), `level----<a id="sec-791"></a>+<a id="sec-800"></a>> **Source:** `docs/vanity.md` · [↑ table of contents](#table-of-contents)@@ -185286,7 +185921,7 @@ The toggle's CSS class reflects the highest severity: `level-0` (errors), `levelThree x402 endpoints that hand an agent a **branded Solana address** — one thatstarts with your ticker/prefix and/or ends with a chosen suffix — with no wallet,-no account, and no SOL. Pay per call in USDC over the [x402](#sec-862) rail and the+no account, and no SOL. Pay per call in USDC over the [x402](#sec-877) rail and theserver grinds (or delivers from stock) a brand-new keypair that matches.| Endpoint | What it is | Chars | Price | Pick it when |@@ -185304,7 +185939,7 @@ Tier 1 and tier 3 **share one warehouse** — the `vanity_inventory` table,pre-ground on batch spot CPU (`workers/vanity-grinder`) and auto-replenishedwhen stock runs low (`api/cron/vanity-inventory-replenish`, hourly). Tier 1 is"give me anything that matches, right now"; tier 3 is "let me pick this exact-address from the catalog." [Pump Launcher](#sec-561) draws from the+address from the catalog." [Pump Launcher](#sec-568) draws from thesame warehouse for instant vanity mint addresses.## Which agent uses this, and why us@@ -185506,7 +186141,7 @@ workers/vanity-grinder/grind.mjs` (see its`vanitySuffix` checks this same inventory before grinding a mint address live —a hit skips the grind entirely (`vanity_source: "inventory"` in the response),a miss grinds as before (`vanity_source: "ground"`). Same one-shot claim, same-atomicity, no separate purchase step. See [pump-launcher.md](#sec-561).+atomicity, no separate purchase step. See [pump-launcher.md](#sec-568).---@@ -185521,20 +186156,20 @@ challenges and the discovery doc stay in parity.## Related-- [x402 endpoints overview](#sec-854)+- [x402 endpoints overview](#sec-869)- [three-vanity/v1 protocol spec](#sec-006)-- [Pump Launcher](#sec-561) — accepts an optional vanity mint prefix/suffix+- [Pump Launcher](#sec-568) — accepts an optional vanity mint prefix/suffix- Web grinder + verifier: [`/vanity-wallet`](https://three.ws/vanity-wallet), [`/vanity/verify`](https://three.ws/vanity/verify)----<a id="sec-792"></a>+<a id="sec-801"></a>> **Source:** `docs/vaults.md` · [↑ table of contents](#table-of-contents)# USDC agent vaults: the deep reference-A vault lets strangers put **real USDC** behind one trading agent, on terms the agent's owner publishes up front. The product-level tour (who each surface is for, how vaults sit next to the Arena, the Theater and Swarms) is in [trading-arenas.md](#sec-690), under "Back-an-Agent Vaults". **Read that first.** This document is the layer underneath it: the exact routes, the auth boundary on each one, the share math, the guards that sit in front of a trade, and the audit ledger anyone can read.+A vault lets strangers put **real USDC** behind one trading agent, on terms the agent's owner publishes up front. The product-level tour (who each surface is for, how vaults sit next to the Arena, the Theater and Swarms) is in [trading-arenas.md](#sec-698), under "Back-an-Agent Vaults". **Read that first.** This document is the layer underneath it: the exact routes, the auth boundary on each one, the share math, the guards that sit in front of a trade, and the audit ledger anyone can read.Everything here moves real money on Solana mainnet. Read [Safety: what spends, and what has to confirm it](#safety-what-spends-and-what-has-to-confirm-it) before you call any `POST`.@@ -185562,13 +186197,13 @@ Two GETs are worth calling out because the pattern is easy to get wrong: `/api/vEvery write accepts either form of credential:- **Session cookie**, as the browser does it. A one-time CSRF token is then required in `X-CSRF-Token`; get one from `GET /api/csrf-token`. A missing or stale token is `403 csrf_missing` / `403 csrf_invalid`.-- **API key** (`Authorization: Bearer sk_live_...`), for scripts and servers. Bearer callers are CSRF-exempt because the token is itself the proof of intent. The four routes that move funds (`deposit`, `redeem`, `trade`, `claim-fees`) additionally require the key to hold the `wallet:write` scope; a key without it gets `403 insufficient_scope` and nothing moves (the check is [`assertBearerMaySpend`](../api/_lib/spend-scope.js), the same gate as the [agent wallet API](#sec-076)). Opening a vault and the owner's `PATCH` need no extra scope. See [authentication.md](#sec-138) for minting a key.+- **API key** (`Authorization: Bearer sk_live_...`), for scripts and servers. Bearer callers are CSRF-exempt because the token is itself the proof of intent. The four routes that move funds (`deposit`, `redeem`, `trade`, `claim-fees`) additionally require the key to hold the `wallet:write` scope; a key without it gets `403 insufficient_scope` and nothing moves (the check is [`assertBearerMaySpend`](../api/_lib/spend-scope.js), the same gate as the [agent wallet API](#sec-076)). Opening a vault and the owner's `PATCH` need no extra scope. See [authentication.md](#sec-139) for minting a key.A session carries full authority, but an API key only spends if it was minted with the `wallet:write` scope. Opening a vault, depositing, redeeming, owner-trading, and claiming fees all call the shared [`api/_lib/spend-scope.js`](../api/_lib/spend-scope.js) gate, so a key without it gets `403 insufficient_scope` naming the missing scope. `PATCH /api/vaults/:id` splits by action: `pause` and `close` only stop trading and are open to any key, while `resume` (restarts trading with backers' funds) and `terms` (raises budgets or the fee) need `wallet:write` too. A connector key (the preset for an unattended AI agent) can never hold `wallet:write`. See [API key scopes](mcp.md#api-key-scopes).Every write is also rate limited per user at 30 per minute, and the limiter fails closed: if the shared limiter backend is unreachable in production the write is refused rather than silently uncapped.-Every write additionally requires the caller's account to have signed the real-funds agreements (Terms of Service, Risk Disclosure, Agent Wallet Agreement). Opening a vault, resuming a paused one, depositing, redeeming, owner-trading and claiming fees each call `requireRealFundsAgreement` before anything is built, so an unsigned account gets `403 risk_ack_required` with a `sign_url`, over a session and an API key alike, and nothing moves. Signing once at [/legal/agreements](https://three.ws/legal/agreements) covers all of them; devnet is exempt, and no `GET` is ever gated. See [risk-acknowledgment.md](#sec-618).+Every write additionally requires the caller's account to have signed the real-funds agreements (Terms of Service, Risk Disclosure, Agent Wallet Agreement). Opening a vault, resuming a paused one, depositing, redeeming, owner-trading and claiming fees each call `requireRealFundsAgreement` before anything is built, so an unsigned account gets `403 risk_ack_required` with a `sign_url`, over a session and an API key alike, and nothing moves. Signing once at [/legal/agreements](https://three.ws/legal/agreements) covers all of them; devnet is exempt, and no `GET` is ever gated. See [risk-acknowledgment.md](#sec-625).The examples below use an API key in `$API_KEY`, granted `wallet:write` for the spending calls.@@ -185576,7 +186211,7 @@ The examples below use an API key in `$API_KEY`, granted `wallet:write` for theOnly an agent with a **provable trading record** can be backed. `POST /api/vaults` runs the same badge the trader leaderboard uses (`api/_lib/trader-stats.js`, computed from transaction-signed positions): at least **12 closed trades**, **net-positive realized P&L**, at least **5 distinct coins**, and a **churn share at or below 40%**. Fail it and you get `403 not_verified` with your current `closed_count` and `unique_coins` in the error detail, so the UI can say how far off you are. See [agent-reputation.md](#sec-060) for how the score is derived.-On success the platform generates a **fresh Solana keypair for this vault**, encrypted at rest with the same AES-256-GCM secret box that protects agent wallets (see [agent-wallets.md](#sec-077) and [custody.md](#sec-232)). Backer capital lives in that wallet only. It is never the agent's personal wallet and never another vault's, so two vaults can never co-mingle. Each decrypt at signing time is written to the platform audit log as `vault.key_use`.+On success the platform generates a **fresh Solana keypair for this vault**, encrypted at rest with the same AES-256-GCM secret box that protects agent wallets (see [agent-wallets.md](#sec-077) and [custody.md](#sec-233)). Backer capital lives in that wallet only. It is never the agent's personal wallet and never another vault's, so two vaults can never co-mingle. Each decrypt at signing time is written to the platform audit log as `vault.key_use`.One open vault per agent: a second attempt returns `409 vault_exists`.@@ -185609,7 +186244,7 @@ curl -sX POST https://three.ws/api/vaults \}'```-`201` returns the vault row including `vault_address`. Note the address: the vault also needs a little **SOL** to pay swap fees and open token accounts, and there is no vault-funding endpoint. Send roughly 0.01 SOL to `vault_address` yourself, for example from your master wallet (see [user-wallet.md](#sec-777)). Without it, trades are refused with `insufficient_sol_for_fees` before anything is signed.+`201` returns the vault row including `vault_address`. Note the address: the vault also needs a little **SOL** to pay swap fees and open token accounts, and there is no vault-funding endpoint. Send roughly 0.01 SOL to `vault_address` yourself, for example from your master wallet (see [user-wallet.md](#sec-786)). Without it, trades are refused with `insufficient_sol_for_fees` before anything is signed.The browser flow is the "Open a vault" modal on [/vaults](https://three.ws/vaults), which is only shown to a signed-in user and pre-fills the same defaults. A signed-in user with no agents gets a disabled form pointing at [/create](https://three.ws/create) instead of a submit that can only fail.@@ -185811,7 +186446,7 @@ curl -s "https://three.ws/api/vaults/ledger?vault_id=8b1c04f6-59a8-4d0e-a1b7-3f5}```-Two properties worth relying on: rows are written **before** funds move for the paths that can double-submit (redeem, trade), so a `pending` or `failed` row is itself evidence of an attempt, and money-moving rows carry the signature you can verify yourself on Solscan. The same movements also land in the platform custody trail described in [custody.md](#sec-232).+Two properties worth relying on: rows are written **before** funds move for the paths that can double-submit (redeem, trade), so a `pending` or `failed` row is itself evidence of an attempt, and money-moving rows carry the signature you can verify yourself on Solscan. The same movements also land in the platform custody trail described in [custody.md](#sec-233).## Reading a vault@@ -185842,16 +186477,16 @@ Two honest limits a backer should know: the platform can sign for the vault (tha## Related-- [trading-arenas.md](#sec-690) for the product overview of vaults and the surfaces around them+- [trading-arenas.md](#sec-698) for the product overview of vaults and the surfaces around them- [agent-wallets.md](#sec-077) for the custodial wallet a backer funds from-- [custody.md](#sec-232) for spend limits, the freeze switch, and proof of custody-- [user-wallet.md](#sec-777) for the per-user master wallet, the easiest way to send a vault its fee SOL+- [custody.md](#sec-233) for spend limits, the freeze switch, and proof of custody+- [user-wallet.md](#sec-786) for the per-user master wallet, the easiest way to send a vault its fee SOL- [agent-reputation.md](#sec-060) for the badge that gates opening a vault-- [authentication.md](#sec-138) for sessions, CSRF tokens, and API keys+- [authentication.md](#sec-139) for sessions, CSRF tokens, and API keys----<a id="sec-793"></a>+<a id="sec-802"></a>> **Source:** `docs/vendored-design-libraries.md` · [↑ table of contents](#table-of-contents)@@ -185948,7 +186583,7 @@ with anything you carry across.which is the same shape as our embeddable avatar demos.- `packages/` shows a component library published from inside a catalog repo:relevant every time we graduate a surface out of this monorepo (see- [package-extraction.md](#sec-470)).+ [package-extraction.md](#sec-475)).## third_party/designcode-agent-skills@@ -186016,7 +186651,7 @@ tree and must stay with it, and with anything derived from it.----<a id="sec-794"></a>+<a id="sec-803"></a>> **Source:** `docs/viability.md` · [↑ table of contents](#table-of-contents)@@ -186196,9 +186831,9 @@ appears only when there is something to show, pointing at the filtered## Related-- [The autonomous economy](#sec-139): the wallets, spend policies,+- [The autonomous economy](#sec-140): the wallets, spend policies,paid skills, and trading loops whose real activity this page measures.-- [x402 paid endpoints](#sec-854): the platform's own endpoint+- [x402 paid endpoints](#sec-869): the platform's own endpointrevenue, recorded in a different table and never mixed into the marketplace ortrading figures here.- [Agent Economy Volume](#sec-055): the agent-to-agent USDC@@ -186206,7 +186841,90 @@ appears only when there is something to show, pointing at the filtered----<a id="sec-795"></a>+<a id="sec-804"></a>++> **Source:** `docs/video-to-motion.md` · [↑ table of contents](#table-of-contents)++# Video to Motion: turn any video into an animation file++**Page:** [/video-to-motion](https://three.ws/video-to-motion) · **API:** reuses `POST /api/motion-swap` for capture, `POST /api/avatar/presign-glb` + `POST /api/forge-remesh` for FBX export · **Worker:** `workers/model-video2motion`++Upload a video of someone moving and get the motion itself back, not a+composited video: a GLB, a BVH, and an FBX if your browser can build one.+Built for animators, VTubers, and anyone whose online markerless mocap+service closed and who still has footage to turn into a usable clip. If you+want a video with your avatar performing the motion instead, see+[/motion-swap](https://three.ws/motion-swap).++## How to use it++1. Open [/video-to-motion](https://three.ws/video-to-motion) and drop in a+ video (MP4, MOV, or WebM, up to 256 MB; the first 90 seconds are+ processed). One person, full body in frame, tracks best.+2. Wait for capture (about two minutes for a 30-second clip; the same+ worker and timing as Motion Swap). The server tracks pose in every frame.+3. Preview the motion on a stock avatar, or load your own rigged humanoid+ GLB by URL or file upload. The clip retargets onto whatever rig is+ loaded, right in your browser.+4. Trim the in/out points with the two sliders under the preview.+5. Download: **GLB** carries the clip baked onto the avatar you previewed+ on. **BVH** carries it on the platform's own canonical-skeleton+ proportions, the standard shape to re-retarget in a DCC tool (Blender,+ MotionBuilder, Unreal's IK Retargeter). **FBX** is a server-side+ conversion that preserves the rig; it can take up to a minute.+6. Signed in? **Save clip** attaches it to one of your agents' animation+ libraries, the same store [/animations](https://three.ws/animations)+ reads from.++## How it works++1. **Capture (server, shared with Motion Swap).** MediaPipe+ PoseLandmarker, HandLandmarker, and ImageSegmenter track the subject and+ solve the landmarks onto the canonical Wolf3D skeleton+ (`workers/model-video2motion/pose_solver.py`), emitting a standard+ three.js `AnimationClip.toJSON()` document: the same clip format the+ [animation library](https://three.ws/animations) and Motion Swap use.+2. **Preview and trim (browser).** [src/animation-retarget.js](../src/animation-retarget.js)+ binds the clip onto whichever avatar is loaded (`retargetClipToObject`),+ renaming non-canonical bone names first via+ [src/glb-canonicalize.js](../src/glb-canonicalize.js) so Mixamo, Avaturn,+ VRM, Daz, and MakeHuman rigs all work. Trimming (`trimClip`) re-samples+ track boundaries through each track's own interpolant, so a cut between+ keyframes still starts and ends on the right pose.+3. **Export (browser + one server hop for FBX).** GLB is written with+ three.js's own `GLTFExporter` against the previewed avatar's scene+ graph. BVH is written by [src/animation-bvh-export.js](../src/animation-bvh-export.js)+ directly from the canonical-skeleton clip, independent of whichever+ avatar is on screen, using the same rest offsets+ [src/animation-retarget.js](../src/animation-retarget.js) binds clips+ against. FBX has no browser-side writer available under a permissive+ license, so the exported GLB is uploaded anonymously through+ `POST /api/avatar/presign-glb` (a public URL is required because the+ converter fetches the source itself, SSRF-guarded) and converted+ server-side by the Blender-based exporter behind+ `POST /api/forge-remesh` (`operation: "convert"`,+ `output_format: "fbx"`), the same converter the Forge export menu uses.++## Why BVH is on the canonical skeleton, not the previewed avatar++A BVH carries no mesh, only a skeleton and its motion. Mixamo's own BVH+downloads use Mixamo's fixed skeleton proportions regardless of which+character you previewed the clip on, because a BVH is meant to be+re-retargeted in your own DCC tool rather than played back as-is. This page+follows the same convention: the BVH always uses the platform's canonical+rest pose, so it stays stable across avatar choices and matches what every+other BVH-producing pipeline on three.ws already does.++## Related++- [/motion-swap](https://three.ws/motion-swap): the same capture, composited back into the source video instead of exported as a file+- [/animations](https://three.ws/animations): the clip library a saved capture lands in+- [/mocap-studio](https://three.ws/mocap-studio): live face and body mocap, not from a video file+- [docs/motion-swap.md](#sec-441) · [docs/animations.md](#sec-101)++---++<a id="sec-805"></a>> **Source:** `docs/viewer.md` · [↑ table of contents](#table-of-contents)@@ -186600,7 +187318,121 @@ A subset of state (background, transparency, background color, auto-rotate, expo----<a id="sec-796"></a>+<a id="sec-806"></a>++> **Source:** `docs/voice-framework-integrations.md` · [↑ table of contents](#table-of-contents)++# LiveKit and Pipecat avatar integrations++A three.ws `<agent-3d>` avatar renders entirely on the visitor's own device: the+3D model, its rig, and its animation clip library already live in the browser.+When your voice agent runs on [LiveKit Agents](https://github.com/livekit/agents)+or [Pipecat](https://github.com/pipecat-ai/pipecat), you don't need a server+that renders video. Instead, a small package republishes the TTS and+user-turn frames your pipeline already has as JSON messages over the room's+data channel, and `<agent-3d voice="livekit">` lipsyncs and gestures to them+client-side.++**On this page:** [Message contract](#message-contract) · [LiveKit](#livekit-agents) · [Pipecat](#pipecat) · [Run the examples locally](#run-the-examples-locally)++---++## Message contract++Both packages publish the same shape, so the browser side never knows which+backend sent it:++```json+{"type": "transcript", "text": "Hi, how can I help today?"}+{"type": "gesture", "name": "wave"}+{"type": "speech_started"}+{"type": "speech_ended", "transcript": "what can you do"}+```++- `transcript` fires once per finished assistant turn; the browser times it+ into visemes locally (`src/runtime/lipsync.js`).+- `gesture` is a best-effort read of that same turn's text: a greeting or+ farewell triggers `wave`, an agreement triggers `nod`, a disagreement+ triggers `shrug`. A miss just means no gesture fires, never a wrong one.+- `speech_started` / `speech_ended` bracket the user's own turn, so the+ avatar can switch to a listening pose. `speech_ended.transcript` is the+ last finalized transcript captured since the matching `speech_started`;+ it is empty if the turn's STT result hasn't finalized yet.++Point your frontend at `<agent-3d voice="livekit">` (or any embed that loads+[`src/runtime/livekit-voice.js`](https://github.com/nirholas/three.ws/blob/main/src/runtime/livekit-voice.js)),+which already subscribes to this message shape over LiveKit's data channel.+Any transport whose implementation routes output messages to a real data+channel (LiveKit, Daily) works the same way.++## LiveKit Agents++[`livekit-plugins-threews`](https://github.com/nirholas/three.ws/tree/main/integrations/livekit/livekit-plugins-threews)+is an `AvatarSession` plugin: drop it into a LiveKit `AgentSession` and every+`say()`/TTS turn and VAD boundary republishes as avatar motion data.++```bash+pip install livekit-plugins-threews+```++```python+from livekit.plugins import threews++avatar = threews.AvatarSession()+await avatar.start(session, room=ctx.room)+```++Full reference: [`integrations/livekit/livekit-plugins-threews/README.md`](https://github.com/nirholas/three.ws/blob/main/integrations/livekit/livekit-plugins-threews/README.md).++## Pipecat++[`pipecat-threews`](https://github.com/nirholas/three.ws/tree/main/integrations/pipecat/pipecat-threews)+is a `FrameProcessor`: place it after your TTS service and before+`transport.output()` in any Pipecat `Pipeline`.++```bash+pip install pipecat-threews+```++```python+from pipecat.pipeline.pipeline import Pipeline+from pipecat_threews import ThreeWsAvatarProcessor++pipeline = Pipeline([+ transport.input(), stt, context_aggregator.user(), llm, tts,+ ThreeWsAvatarProcessor(),+ transport.output(), context_aggregator.assistant(),+])+```++Your TTS service must be constructed with `push_start_frame=True` and+`push_stop_frames=True` (Pipecat's `TTSService` base class defaults both to+`False`); otherwise `ThreeWsAvatarProcessor` never sees a `TTSStoppedFrame`+and silently never publishes. Full reference:+[`integrations/pipecat/pipecat-threews/README.md`](https://github.com/nirholas/three.ws/blob/main/integrations/pipecat/pipecat-threews/README.md).++## Run the examples locally++Both packages ship a runnable foundational example against a real local,+open-source `livekit-server`, no cloud account or API key required:++```bash+docker run --rm -p 7880:7880 -p 7881:7881 -p 7882:7882/udp \+ -e LIVEKIT_KEYS="devkey: devsecret" \+ livekit/livekit-server --dev --bind 0.0.0.0+```++- LiveKit: `integrations/livekit/livekit-plugins-threews/examples/avatar_agent.py`+- Pipecat: `integrations/pipecat/pipecat-threews/examples/avatar_bot.py`++Each example speaks a short scripted sequence through a real local TTS+(`espeak-ng` for Pipecat's example), so you can point `<agent-3d+voice="livekit">` at the same room and watch the avatar lipsync and gesture+to a real agent with no cloud dependency on either side.++---++<a id="sec-807"></a>> **Source:** `docs/voice-lab.md` · [↑ table of contents](#table-of-contents)@@ -186762,14 +187594,98 @@ The agent-voice handler ([`api/agents/_id/voice.js`](../api/agents/_id/voice.js)## Related-- [Voice and lipsync tutorial](#sec-768): the authoritative step-by-step, including wiring a cloned voice into an agent.-- [Lipsync](#sec-400): how synthesized speech drives an avatar's mouth in real time.-- [Talking Avatar Video](#sec-672): render a talking-head clip from an avatar and an audio track.+- [Voice and lipsync tutorial](#sec-776): the authoritative step-by-step, including wiring a cloned voice into an agent.+- [Lipsync](#sec-404): how synthesized speech drives an avatar's mouth in real time.+- [Talking Avatar Video](#sec-680): render a talking-head clip from an avatar and an audio track.- Pages: [/voice](https://three.ws/voice), [/dashboard](https://three.ws/dashboard).----<a id="sec-797"></a>+<a id="sec-808"></a>++> **Source:** `docs/vroid-hub-import.md` · [↑ table of contents](#table-of-contents)++# Import your VRoid Hub avatar++**Page:** [/import/vroid](https://three.ws/import/vroid) · **API:** `GET /api/vroid/models`, `POST /api/vroid/import`, `GET|POST|DELETE /api/auth/vroid/[action]` · **Provider:** [VRoid Hub](https://hub.vroid.com) (developer.vroid.com OAuth2)++Bring a VRM character you made in [VRoid Studio](https://vroid.com/en/studio) and+published to VRoid Hub straight into three.ws, with the creator's license+honored automatically: the picker only ever offers an action (public agent,+export, modify, monetize) the character's own license conditions permit.++## How to use it++1. Open [/import/vroid](https://three.ws/import/vroid) and sign in to+ three.ws if you have not already.+2. **Connect VRoid Hub.** The first visit redirects to VRoid Hub's own OAuth+ screen (PKCE-secured) to authorize three.ws; you are sent back to the+ picker once you approve.+3. The picker lists **your characters** (everything in your VRoid Hub+ account, public or private) and **hearted characters** (anything you+ favorited on the Hub that its creator made downloadable).+4. Each card shows the creator's name, four license badges, and a link to+ what those terms mean. A greyed-out badge is not a bug: it means the+ creator did not grant that permission, and three.ws will not offer it on+ the imported avatar either.+5. Click **Import to three.ws**. The model downloads through your own VRoid+ Hub grant (a license you already hold, not a public scrape), lands in+ your avatar library, and opens directly in the [avatar editor](https://three.ws/avatars)+ with idle and walk animations already playing on the rig.++## What the license badges mean++VRoid Hub lets every creator set eight independent conditions on their+character. three.ws reduces them to four yes/no questions that map onto+what the platform actually lets you do with an avatar:++| Badge | Hub condition | Opens when |+| --- | --- | --- |+| Public agent | `characterization_allowed_user` | set to "everyone" (not just the creator's own account) |+| Export | `redistribution` | set to "allow" |+| Modify | `modification` | set to "allow" |+| Monetize | `personal_commercial_use` / `corporate_commercial_use` | either is set to a permitted commercial value |++Creator credit follows its own rule: unless the creator explicitly marked+`credit` as "unnecessary", three.ws keeps a credit line ("`"<character>" by+<creator>, imported from VRoid Hub.`") visible on every surface the avatar+appears on, including agent profiles and the avatar page.++A license field a creator left at VRoid Hub's own default, or any value this+page does not recognize, always normalizes to the closed/restrictive+reading. An avatar whose permissions cannot be read is never treated as more+open than it is.++## How it works++1. **Connect** (`api/auth/vroid/[action].js`). A PKCE code verifier and a CSRF+ nonce travel together inside one HMAC-signed `state` parameter, the same+ pattern the GitHub social-connect flow uses. The resulting access and+ refresh tokens are AES-GCM encrypted (per-row HKDF-derived key) and+ upserted into the same `social_connections` table every other OAuth+ provider on three.ws uses.+2. **List** (`api/vroid/models.js`). Reads `GET /api/account/character_models`+ (your own models, `publication: "all"`) and `GET /api/hearts`+ (your hearted, downloadable models) from the Hub API, each annotated by+ `api/_lib/vroid/license.js`.+3. **Import** (`api/vroid/import.js`). Mints a `DownloadLicense`+ (`POST /api/download_licenses`), follows its one-time redirect+ (`GET /api/download_licenses/{id}/download`) to the S3-hosted VRM/GLB,+ validates the GLB header, and runs it through+ [glb-canonicalize](../src/glb-canonicalize.js) so the idle/walk clip+ library retargets onto it exactly like any other imported avatar. License+ fields, the computed actions, and the credit line are stored on the+ avatar's `source_meta` so later surfaces (agent creation, export, a+ marketplace listing) can re-check them without another Hub round trip.++## Related++- [/import/rpm](https://three.ws/import/rpm): import any GLB/glTF avatar by URL, no license gate+- [docs/character-studio.md](#sec-183): what you can do with an avatar once it is in your library++---++<a id="sec-809"></a>> **Source:** `docs/vscode.md` · [↑ table of contents](#table-of-contents)@@ -186779,7 +187695,7 @@ Two extensions put the platform inside the editor. **three.ws 3D** makes modelfiles, 3D generation, animation, and embedding native to VS Code. **three.wsx402** does the same for paid endpoints. It pays with $THREE on Solana at`FeMbDoX7R1Psc4GEcvJdsbNbZA3bfztcyDCatJVJpump`. This page covers the first;-see [x402 for VS Code](#sec-861) for the second.+see [x402 for VS Code](#sec-876) for the second.| | ||---|---|@@ -186848,7 +187764,7 @@ first entry, so a search that finds nothing turns into a generation.**Models can be generated in place.** `3D: Generate a Model from Text`describes an object; `3D: Generate an Avatar from Text` describes a character.-Both call the free [3D Studio](#sec-414) lane, save the finished GLB+Both call the free [3D Studio](#sec-418) lane, save the finished GLBinto your workspace, and open it in the viewer.**Refine by describing a change.** **Refine** (or `3D: Refine this Model by@@ -186893,7 +187809,7 @@ pull request cannot give you. The same comparison is offered after a refinement**`<agent-3d>` embeds are checked as you type.** In HTML, JSX/TSX, Vue, Svelte,Astro, Markdown, and PHP files the extension runs the rules from the-[Embedding guide](#sec-259) as diagnostics:+[Embedding guide](#sec-262) as diagnostics:| Finding | Severity | Quick fix ||---|---|---|@@ -187026,19 +187942,19 @@ comparing, and the quality check work on a purely local file.## Related-- [Embedding](#sec-259) documents every `<agent-3d>` attribute the+- [Embedding](#sec-262) documents every `<agent-3d>` attribute thediagnostics and completions know.-- [3D Studio MCP](#sec-414) is the free generation lane the extension+- [3D Studio MCP](#sec-418) is the free generation lane the extensioncalls, and the same tools are available to any MCP client.- [Animations](#sec-101) covers the motion library the Animate pickersearches.-- [x402](#sec-862) covers the sibling extension for paid endpoints.+- [x402](#sec-877) covers the sibling extension for paid endpoints.- [The 3D asset pipeline](#sec-002) explains what the optimizationnotes in the report are asking for, and what Optimize does about them.----<a id="sec-798"></a>+<a id="sec-810"></a>> **Source:** `docs/walk-leaderboard.md` · [↑ table of contents](#table-of-contents)@@ -187162,7 +188078,7 @@ As coded, in layers. Each one bounds a different kind of nonsense:| Achievement allowlist | same | Only the four known codes persist, and each unlocks once per walker, so badges cannot be farmed by replaying a batch. || Idempotent rollup | unique index in [the migration](../api/_lib/migrations/20260621140000_walk_metrics.sql) | Batches merge into one row per dimension tuple per day, so the table cannot be flooded into a different shape. |-**What these guards do and do not claim.** `POST /api/walk/metrics` is a public, open-CORS ingest keyed on a client-supplied anonymous id, because embeds post from third-party hosts and anonymous walkers are first-class on the board. The guards above bound the size, rate, and attribution of any single claim; they do not cryptographically prove that a walk happened. There is no cross-batch plausibility check (for example, distance against elapsed duration) and no server-side replay of the controller. Treat the board as a gamified activity ranking, not as an audited measurement. If you need a movement claim that a third party can verify, that is a different product: [World Lines](#sec-805) issue agent-signed proofs of physical presence with server-derived co-location.+**What these guards do and do not claim.** `POST /api/walk/metrics` is a public, open-CORS ingest keyed on a client-supplied anonymous id, because embeds post from third-party hosts and anonymous walkers are first-class on the board. The guards above bound the size, rate, and attribution of any single claim; they do not cryptographically prove that a walk happened. There is no cross-batch plausibility check (for example, distance against elapsed duration) and no server-side replay of the controller. Treat the board as a gamified activity ranking, not as an audited measurement. If you need a movement claim that a third party can verify, that is a different product: [World Lines](#sec-818) issue agent-signed proofs of physical presence with server-derived co-location.---@@ -187328,14 +188244,14 @@ The anonymous id is generated and persisted by the walk runtime in `localStorage## Related-- [Add the Walk Companion to your site](#sec-769), the hands-on path from a copy-paste iframe to the `@three-ws/walk` package, including the surfaces that produce the metrics ranked here.+- [Add the Walk Companion to your site](#sec-777), the hands-on path from a copy-paste iframe to the `@three-ws/walk` package, including the surfaces that produce the metrics ranked here.- The walk documentation set on the site, served from `public/docs/walk/`: `/docs/walk` (index), `/docs/walk/getting-started`, `/docs/walk/walk-page`, `/docs/walk/embed-iframe`, `/docs/walk/embed-sdk`, `/docs/walk/companion-mode`, `/docs/walk/chrome-extension`, `/docs/walk/postmessage-events`, `/docs/walk/changelog`, and `/docs/walk/analytics`, which covers the per-creator dashboard fed by the same ingest.- The creator-side view of this data: `three.ws/walk-analytics`, backed by `GET /api/walk/analytics`.-- [World Lines](#sec-805), for movement claims that carry a verifiable agent signature rather than a leaderboard rank.+- [World Lines](#sec-818), for movement claims that carry a verifiable agent signature rather than a leaderboard rank.----<a id="sec-799"></a>+<a id="sec-811"></a>> **Source:** `docs/web-component.md` · [↑ table of contents](#table-of-contents)@@ -187443,7 +188359,7 @@ el.removeAttribute('sign-language'); // offSigning rides the same `SPEAK` event as spoken replies, so it works identicallyin the hosted app and in an embed. A runnable page is[examples/sign-language.html](../examples/sign-language.html); the engine and its-vocabulary are documented in [Sign language](#sec-641), and the+vocabulary are documented in [Sign language](#sec-649), and thealphabet is browsable at [/asl-alphabet](https://three.ws/asl-alphabet).### Hand control, no camera@@ -187488,7 +188404,7 @@ el.addEventListener('sonar-gesture', (e) => {Say plainly wherever you ship this that the carrier sits near 20 kHz, which catsand dogs can hear. The technique, its three gestures, what it needs from theroom, and why running more than one gesture at a time needs a mode are all in-[Sonar](#sec-658).+[Sonar](#sec-666).### Skills and memory@@ -188474,7 +189390,7 @@ defineElement('my-agent');----<a id="sec-800"></a>+<a id="sec-812"></a>> **Source:** `docs/widget-api.md` · [↑ table of contents](#table-of-contents)@@ -188681,7 +189597,7 @@ If you have multiple widgets and want to coordinate them (sync camera, broadcast----<a id="sec-801"></a>+<a id="sec-813"></a>> **Source:** `docs/widget-studio.md` · [↑ table of contents](#table-of-contents)@@ -188925,14 +189841,14 @@ You can override these freely in the iframe `width` and `height` attributes. Add## Next steps-- [Widget API (JSON-RPC)](#sec-800) — programmatic control over an embedded widget: camera, animation, screenshots, model loading-- [Widgets reference](#sec-802) — technical details, postMessage API, CSP config, and oEmbed spec-- [Web component](#sec-799) — the `<agent-3d>` custom element for developer integrations-- [Embedding guide](#sec-259) — advanced embedding patterns and iframe options+- [Widget API (JSON-RPC)](#sec-812) — programmatic control over an embedded widget: camera, animation, screenshots, model loading+- [Widgets reference](#sec-814) — technical details, postMessage API, CSP config, and oEmbed spec+- [Web component](#sec-811) — the `<agent-3d>` custom element for developer integrations+- [Embedding guide](#sec-262) — advanced embedding patterns and iframe options----<a id="sec-802"></a>+<a id="sec-814"></a>> **Source:** `docs/widgets.md` · [↑ table of contents](#table-of-contents)@@ -189345,7 +190261,7 @@ The `config` object is validated against the type's schema (see [widget-types.js**Widget share URL:** Every widget has a canonical share URL at `https://three.ws/w/<id>`. This URL is server-rendered with Open Graph metadata and a 1200×630 preview image, making it safe to post in Slack, Discord, X, or any link-preview-aware surface.-For the full API reference including request/response shapes, error codes, and pagination, see [api-reference.md](#sec-124).+For the full API reference including request/response shapes, error codes, and pagination, see [api-reference.md](#sec-125).---@@ -189437,7 +190353,7 @@ No IP addresses, no user-agent strings, no cookies, no chat message content. The## Programmatic control-Need to drive a widget from the parent page — change the camera, play an animation, grab a screenshot? See the [Widget API (JSON-RPC)](#sec-800) reference. The `ThreeWidget` SDK lives at `/widget-client.js` and works with any iframe pointing at `/widget`.+Need to drive a widget from the parent page — change the camera, play an animation, grab a screenshot? See the [Widget API (JSON-RPC)](#sec-812) reference. The `ThreeWidget` SDK lives at `/widget-client.js` and works with any iframe pointing at `/widget`.---@@ -189450,7 +190366,7 @@ Need to drive a widget from the parent page — change the camera, play an anima----<a id="sec-803"></a>+<a id="sec-815"></a>> **Source:** `docs/witness.md` · [↑ table of contents](#table-of-contents)@@ -189465,7 +190381,7 @@ Playwright spec that is **red while the bug exists and green once it is fixed**.- Package: [`packages/witness/`](../packages/witness) (`@three-ws/witness`, Apache-2.0, no dependencies)- On three.ws: the corner companion attaches a trace to every report, and- [`/feedback`](#sec-304) hands you the compiled test with one click.+ [`/feedback`](#sec-307) hands you the compiled test with one click.- Standalone: it works on any site, with or without the rest of three.ws.## The idea in one screen@@ -189637,13 +190553,95 @@ engineer's spec file on disk. Full API in the## Related-- [Feedback](#sec-304): the loop this is the second half of, and the+- [Feedback](#sec-307): the loop this is the second half of, and theuntrusted-input boundary that governs all of it.-- [Notifications](#sec-442): the same companion, delivering the other way.+- [Notifications](#sec-446): the same companion, delivering the other way.----<a id="sec-804"></a>+<a id="sec-816"></a>++> **Source:** `docs/wordpress-embed.md` · [↑ table of contents](#table-of-contents)++# WordPress embed++The **three.ws Agent** plugin ([`integrations/wordpress/three-ws-agent/`](../integrations/wordpress/three-ws-agent))+embeds [`<agent-3d>`](#sec-811) as a Gutenberg block or a shortcode. No npm, no build+step, no bundler: the editor script is plain ES5-safe JS against the `wp.*` globals WordPress+already ships, and both entry points render through one shared PHP function so the block editor's+preview is never a second, divergent implementation of the markup.++## Installing++Copy or symlink `integrations/wordpress/three-ws-agent/` into `wp-content/plugins/`, then activate+**three.ws Agent** from Plugins. There is nothing to configure: a public agent, agent ID, or bare+model URL renders with no API key.++## Block++Search the block inserter for "three.ws Agent" (category: Embeds). The inspector panel exposes:++| Attribute | Purpose |+|---|---|+| On-chain URI | `agent://base/42`. Takes priority over Agent ID and Model URL. |+| Agent ID | Backend account ID or CAIP-10 ID. Used when On-chain URI is empty. |+| Chain ID | Paired with a numeric Agent ID. |+| Model URL | Bare GLB for an ad-hoc agent. Used when On-chain URI and Agent ID are both empty. |+| Background | `transparent`, `dark`, or `light`. |+| Framing | `full` or `portrait`. |++## Shortcode++For the classic editor, widgets, or theme templates:++```+[three_ws_agent src="agent://base/42" background="dark" framing="portrait"]+```++`agent_id`, `chain_id`, and `model` are also accepted, matching the block's attributes.++## SRI pin++`includes/pinned-release.php` is generated from [`data/agent-3d-releases.json`](../data/agent-3d-releases.json)+by `npm run build:site-builder-embeds` (the same step that pins the Framer and Webflow+components). The render function enqueues the loader script with `type="module"`, `integrity`,+and `crossorigin` via a `script_loader_tag` filter, since core's enqueue API has no argument for+ESM integrity pins. `npm run check:site-builder-embeds` (wired into `npm run gate`) fails the+build if the plugin's pin drifts from the ledger.++## Verification++Verified against a real local WordPress install in Docker (no mocks), using the official+[Plugin Check](https://wordpress.org/plugins/plugin-check/) plugin from wordpress.org:++```bash+scripts/wordpress-plugin-check.sh+```++Reproduced output from a real run:++```+[plugin-check] WordPress version: 7.1.3+[plugin-check] activating three-ws-agent...+Success: Activated 1 of 1 plugins.+[plugin-check] installing the official Plugin Check plugin from wordpress.org...+Success: Installed 1 of 1 plugins.+[plugin-check] running wp plugin check three-ws-agent...+Success: Checks complete. No errors found.+```++The script also confirms the block and the shortcode both render a real `<agent-3d>` tag with the+correct pinned script tag on a live page before tearing the containers down.++## Submitting to the WordPress.org plugin directory++Submission (an upload under an owner-controlled WordPress.org account, and the review queue that+follows it) is an owner action: see+[`marketing/growth/submissions/site-builders.md`](../marketing/growth/submissions/site-builders.md).++---++<a id="sec-817"></a>> **Source:** `docs/workbench.md` · [↑ table of contents](#table-of-contents)@@ -189655,7 +190653,7 @@ Page: [/workbench](https://three.ws/workbench)## Why it exists-[Forge](#sec-313) is built for one thing: type or drop something in, get a model out. That is the right shape for most people, but it hides the pipeline. Creators who make game props, printable figures or rigged characters want to choose the steps: cut the background first, retopologize to quads, keep a face budget, rig the result, and export to the format their tool expects. Workbench exposes that pipeline as a layout people already know from desktop 3D apps: an icon rail, a workflow panel of node cards, a large viewport with a tool strip, and an Export menu. Every step calls the same production endpoints Forge uses, so nothing here is a simulation.+[Forge](#sec-316) is built for one thing: type or drop something in, get a model out. That is the right shape for most people, but it hides the pipeline. Creators who make game props, printable figures or rigged characters want to choose the steps: cut the background first, retopologize to quads, keep a face budget, rig the result, and export to the format their tool expects. Workbench exposes that pipeline as a layout people already know from desktop 3D apps: an icon rail, a workflow panel of node cards, a large viewport with a tool strip, and an Export menu. Every step calls the same production endpoints Forge uses, so nothing here is a simulation.## The layout@@ -189726,7 +190724,7 @@ Workflows are saved in this browser (`localStorage` key `wb:workflows`). Setting## Extensions-The Extensions view reads the live engine catalog (`GET /api/forge?catalog=1`) and lane health (`GET /api/forge?health=1`) and shows one card per engine with its status, whether it is free, what inputs it accepts, and its typical time at Standard quality. Engines that accept your own photos and need no key have a switch that adds or removes them from the Engine picker. Engines that need your own API key link to [Forge](#sec-313), where keys are managed. Below the engines, each mesh tool has a card and an **Add to current workflow** button.+The Extensions view reads the live engine catalog (`GET /api/forge?catalog=1`) and lane health (`GET /api/forge?health=1`) and shows one card per engine with its status, whether it is free, what inputs it accepts, and its typical time at Standard quality. Engines that accept your own photos and need no key have a switch that adds or removes them from the Engine picker. Engines that need your own API key link to [Forge](#sec-316), where keys are managed. Below the engines, each mesh tool has a card and an **Add to current workflow** button.## Settings@@ -189766,11 +190764,11 @@ The other nodes are one call each: `POST /api/forge-rembg` with `{ "image_url",| API client | [src/workbench/api.js](../src/workbench/api.js) || Styles | [src/workbench/workbench.css](../src/workbench/workbench.css) |-Related: [Forge](#sec-313) for one-shot generation, [Scene Studio](#sec-625) for composing scenes from the models you make here, and [STRUCTURE.md](../STRUCTURE.md) for the map of every surface.+Related: [Forge](#sec-316) for one-shot generation, [Scene Studio](#sec-632) for composing scenes from the models you make here, and [STRUCTURE.md](../STRUCTURE.md) for the map of every surface.----<a id="sec-805"></a>+<a id="sec-818"></a>> **Source:** `docs/world-lines.md` · [↑ table of contents](#table-of-contents)@@ -189780,7 +190778,7 @@ A **World Line** is a quest an agent leaves at a real place. Someone walks to thLive at `three.ws/world-lines`. Four tabs: **Near me** (fix-gated quests within walking range), **Explore** (coordinate-free region roll-up), **My proofs** (your earned collectibles, each re-verifiable in place), and **Create** (place a quest on a pin you own, plus the completion dashboard). The active tab is mirrored into the URL hash (`#near`, `#explore`, `#collectibles`, `#create`), so a tab is linkable and the back button walks tabs; Left/Right/Home/End move between them from the keyboard.-This document is the deep reference. For where World Lines sits inside the wider IRL product (placing agents, discovering by walking up, Money Drops, the presence privacy contract), read the short version first: [IRL: agents in the real world](irl.md#world-lines). The REST summary lives in the [API reference](#sec-124); everything below is the full contract, the anti-cheat reasoning, and the exact privacy posture as coded.+This document is the deep reference. For where World Lines sits inside the wider IRL product (placing agents, discovering by walking up, Money Drops, the presence privacy contract), read the short version first: [IRL: agents in the real world](irl.md#world-lines). The REST summary lives in the [API reference](#sec-125); everything below is the full contract, the anti-cheat reasoning, and the exact privacy posture as coded.Code: [api/irl/world-lines.js](../api/irl/world-lines.js) (all nine endpoints), [api/\_lib/world-lines.js](../api/_lib/world-lines.js) (the pure crypto and ceremony core), [src/world-lines.js](../src/world-lines.js) (the page), [src/irl/world-line-ar.js](../src/irl/world-line-ar.js) (the completion ceremony), [src/irl/world-lines-client.js](../src/irl/world-lines-client.js) (browser client), [packages/irl](../packages/irl/README.md) (the npm SDK).@@ -190012,7 +191010,7 @@ Coverage for the crypto core lives in [tests/world-lines-crypto.test.js](../test## Privacy: exactly what is stored-The engineering analysis for all of IRL is the [IRL threat model](#sec-387); the user-facing summary is the `three.ws/irl-privacy` page. World Lines specifically:+The engineering analysis for all of IRL is the [IRL threat model](#sec-391); the user-facing summary is the `three.ws/irl-privacy` page. World Lines specifically:**Stored.**@@ -190352,14 +191350,14 @@ Both handlers log their enforcement mode once per cold start, so a production mi## Related- [IRL: agents in the real world](irl.md#world-lines), the product-level overview and the rest of the presence layer.-- [IRL threat model](#sec-387), the adversarial analysis behind every radius and cap above.-- [Place a 3D agent in your real environment](#sec-746), how to create the anchor pin a World Line needs.-- [API reference](#sec-124), the one-screen summary of these endpoints alongside the rest of `/api/irl/*`.-- [AR](#sec-129), the camera and WebXR layer the ceremony builds on.+- [IRL threat model](#sec-391), the adversarial analysis behind every radius and cap above.+- [Place a 3D agent in your real environment](#sec-754), how to create the anchor pin a World Line needs.+- [API reference](#sec-125), the one-screen summary of these endpoints alongside the rest of `/api/irl/*`.+- [AR](#sec-130), the camera and WebXR layer the ceremony builds on.----<a id="sec-806"></a>+<a id="sec-819"></a>> **Source:** `docs/x-account-appeal.md` · [↑ table of contents](#table-of-contents)@@ -190399,7 +191397,7 @@ accounts where they were not. Every claim carries its source. Where a sourceis a marketing blog rather than a first-hand account, it is marked as such.The status table that the rest of the repo reads is in-[`x-accounts.md`](#sec-807). Update that file when this one changes the+[`x-accounts.md`](#sec-820). Update that file when this one changes thefacts.## 1. What this suspension is, and is not@@ -191069,7 +192067,7 @@ In order of documented effectiveness for a US-based founder:reads replies to his posts and pulls the internal record, and he answersin public. That is also the risk: in the Rainmaker1973 case he named thereal trigger for everyone to see. Run it from a personal or community- account, never from `@trythreews` (see [x-accounts.md](#sec-807)). Tag+ account, never from `@trythreews` (see [x-accounts.md](#sec-820)). Tag`@nikitabier` with the handle, the date, the email's wording, and proof ofID verification. `@Support` and `@Safety` do not answer individual casesin any documented 2025 to 2026 instance, and the Better Business Bureau@@ -191139,7 +192137,7 @@ could not be opened.----<a id="sec-807"></a>+<a id="sec-820"></a>> **Source:** `docs/x-accounts.md` · [↑ table of contents](#table-of-contents)@@ -191147,7 +192145,7 @@ could not be opened.three.ws has used two X accounts. This file records their status and whateach surface in the repo should do about it. Read it before posting-anything from an [`x-posts/`](#sec-819) draft, before adding an X+anything from an [`x-posts/`](#sec-833) draft, before adding an Xlink to a page, and before deciding which handle a meta tag should name.## Status@@ -191155,7 +192153,7 @@ link to a page, and before deciding which handle a meta tag should name.| Handle | Role | Status || --- | --- | --- || [`@trythreews`](https://x.com/trythreews) | Institutional. The platform account. | Live. This is the only handle to link to or post from today. |-| `@nichxbt` | Personal. The founder account. | **Suspended 2026-08-27; appeal #1 denied 2026-09-05; still suspended, re-confirmed by probe 2026-09-06.** Confirmed by X's own notification emails. Do not link to it and do not plan a post from it. Status and filing log: [`x-account-appeal.md`](#sec-806). |+| `@nichxbt` | Personal. The founder account. | **Suspended 2026-08-27; appeal #1 denied 2026-09-05; still suspended, re-confirmed by probe 2026-09-06.** Confirmed by X's own notification emails. Do not link to it and do not plan a post from it. Status and filing log: [`x-account-appeal.md`](#sec-819). |The suspension is confirmed, not inferred. X emailed the account owner at06:29 on 2026-08-27: the account "was reported and has been suspended",@@ -191179,7 +192177,7 @@ that it will not overturn the decision. That closes the first filing, not theroute. Refiling through the form is what the documented reinstatements did,and it is the live next step. The full case, X's own process, the precedents,the exact text to file, and the order to do it in are in-[`x-account-appeal.md`](#sec-806). Nothing in this repo should wait+[`x-account-appeal.md`](#sec-819). Nothing in this repo should waiton it.One wording trap in that denial, because it will be read again later: the@@ -191194,7 +192192,7 @@ The reader-facing version of the status table lives on`$THREE` contract address in one place so a visitor can check a suspicious accountagainst it. Keep the two in step: this file is for the repo, that section is for thecommunity, and neither should say something the other contradicts.-[`community.md`](#sec-208) carries the same list for readers who arrive through+[`community.md`](#sec-209) carries the same list for readers who arrive throughthe docs.## What a suspended handle actually breaks@@ -191222,8 +192220,8 @@ consequences in this repo, and they want three different responses:## The two-account playbook, while `@nichxbt` is unavailable-Nine drafts in [`x-posts/`](#sec-819), plus-[`x402-solana-july-roundup-response.md`](#sec-859)+Nine drafts in [`x-posts/`](#sec-833), plus+[`x402-solana-july-roundup-response.md`](#sec-874)and [`../marketing/openai-select-partner/social-copy.md`](../marketing/openai-select-partner/social-copy.md),are written around one pattern: `@trythreews` posts the institutional version, then `@nichxbt`quote-tweets it twenty to forty minutes later in first person, because an@@ -191251,10 +192249,10 @@ Posting one of them today means doing this instead:the drafts changes.Two drafts have a further wrinkle worth knowing before you open them:-[`osf-issue-reply.md`](#sec-840) picks between a long and+[`osf-issue-reply.md`](#sec-854) picks between a long anda short form based on whether the posting account has Premium, which is aquestion about a specific account rather than about the copy, and-[`open-source-friday-plan.md`](#sec-461) submits the+[`open-source-friday-plan.md`](#sec-466) submits thehandle as a form field to a third party.## Do not litigate the suspension from `@trythreews`@@ -191278,7 +192276,7 @@ is unaffected as a feed. It is built from the archived JSON inserving the same items with the same content whatever X does to theaccount. Only the per-item links point into the suspended account, which iscase 2 above. The source stays valid; see-[`syndication.md`](#sec-671).+[`syndication.md`](#sec-679).## Referral codes are not the handle@@ -191294,7 +192292,7 @@ alone too.----<a id="sec-808"></a>+<a id="sec-821"></a>> **Source:** `docs/x-archive.md` · [↑ table of contents](#table-of-contents)@@ -191355,7 +192353,7 @@ clean checkout.## The report-[docs/x-archive/trythreews-engagement.md](#sec-810)+[docs/x-archive/trythreews-engagement.md](#sec-823)is generated, never hand-edited. It carries:- headline totals and the engagement **distribution** (median, p75/p90/p99, and@@ -191379,7 +192377,7 @@ post that carries an Article (title, full body, exact metrics), and collects thereaders' replies and quotes for each one. The file format and flags are in[data/x-archive/README.md](../data/x-archive/README.md).-[docs/x-archive/trythreews-articles-readers.md](#sec-809)+[docs/x-archive/trythreews-articles-readers.md](#sec-822)is the hand-written reading of that pull: which Articles reached people, whatreaders asked for in their own words, and what that means for the next Article.Unlike the engagement report it is not generated, so update it after a fresh pull.@@ -191419,7 +192417,7 @@ Code: [scripts/x-archive-lib.mjs](../scripts/x-archive-lib.mjs)----<a id="sec-809"></a>+<a id="sec-822"></a>> **Source:** `docs/x-archive/trythreews-articles-readers.md` · [↑ table of contents](#table-of-contents)@@ -191427,7 +192425,7 @@ Code: [scripts/x-archive-lib.mjs](../scripts/x-archive-lib.mjs)A hand-written reading of every X Article @trythreews has published, plus every reply and quotefrom readers, pulled from the X API. The engagement analysis beside it-([trythreews-engagement.md](#sec-810)) covers short posts. This page covers the+([trythreews-engagement.md](#sec-823)) covers short posts. This page covers thelong form and asks a different question: once someone reads an Article, what do they ask for next?- **Source:** `npm run x:articles:pull` (script: [scripts/x-articles-pull.mjs](../scripts/x-articles-pull.mjs),@@ -191581,7 +192579,7 @@ rule, but it is the same request for transparency the skeptics make in a differe## What this means for the next Article-Each point below fits inside the rules of the [Article author brief](#sec-811).+Each point below fits inside the rules of the [Article author brief](#sec-824).1. **Lead with something a reader can open today, or a result with its numbers.** Choose launchesand experiments over mechanism explainers. When the subject is a mechanism, tell it through one@@ -191613,7 +192611,7 @@ gets an exception for agent spend controls, is the owner's call. This page recor----<a id="sec-810"></a>+<a id="sec-823"></a>> **Source:** `docs/x-archive/trythreews-engagement.md` · [↑ table of contents](#table-of-contents)@@ -191864,7 +192862,7 @@ The floor is as instructive as the ceiling: these are the shapes to stop repeati----<a id="sec-811"></a>+<a id="sec-824"></a>> **Source:** `docs/x-article-author-brief.md` · [↑ table of contents](#table-of-contents)@@ -191882,10 +192880,10 @@ they finish. The boundaries below are what keep them from overwriting each other## Read these first, fully-1. [docs/x-content-pipeline.md](#sec-812): what an `article` item is and how it+1. [docs/x-content-pipeline.md](#sec-825): what an `article` item is and how itpublishes.2. [docs/announce-voice.md](#sec-102): the contract the AI editor holds every word to.-3. [docs/x-story-authoring.md](#sec-850): claims, evidence, probes and scenarios. An+3. [docs/x-story-authoring.md](#sec-865): claims, evidence, probes and scenarios. Anarticle uses the same machinery as a post.4. **The worked example, and the standard every future Article and post is held to** (owner,2026-10-10): the item `keeper-article` in `data/x-content/queue.json`, its body@@ -191897,7 +192895,7 @@ they finish. The boundaries below are what keep them from overwriting each othersection, and ends on the pages to try. Match its shape, voice, depth and framing.5. [docs/ops/x-story-findings-2026-09-30.md](ops/x-story-findings-2026-09-30.md): surfaces foundbroken or not filmable. Do not build an article on one of them.-6. [docs/x-archive/trythreews-articles-readers.md](#sec-809): what+6. [docs/x-archive/trythreews-articles-readers.md](#sec-822): whatreaders of our published Articles responded to and asked for. Choose the angle and write theopening with it in mind.@@ -192019,7 +193017,7 @@ broken feature found is as valuable as an article.----<a id="sec-812"></a>+<a id="sec-825"></a>> **Source:** `docs/x-content-pipeline.md` · [↑ table of contents](#table-of-contents)@@ -192035,9 +193033,9 @@ that passed is the queue's `approval` setting: the owner, or a policy that onlyever releases posts filmed against the live product([Who approves a post](#who-approves-a-post)).-To write a post, start with [Writing a story](#sec-850). An author working one-product area at a time is handed [the author brief](#sec-849), and an author-writing a long-form X Article is handed [the article brief](#sec-811).+To write a post, start with [Writing a story](#sec-865). An author working one+product area at a time is handed [the author brief](#sec-864), and an author+writing a long-form X Article is handed [the article brief](#sec-824).---@@ -192139,7 +193137,7 @@ X Articles require the posting account to be on X Premium.```- `status`: `draft` (may be unfinished), `review` (must pass `check`), `approved` (eligible to publish), `paused`, `posted`. Move an item to `approved` with `npm run x:content -- approve <slug>` (or `--status review` for a whole batch), which refuses anything a passing review record does not already cover. `npm run x:content -- advance` does the whole line: it films, reviews, and releases what the policy allows.-- `scenario` is the run that is filmed: see [Proof reels](#proof-reels) and [Writing a story](#sec-850). An item with a scenario declares `{ "type": "scenario" }` in `probes`.+- `scenario` is the run that is filmed: see [Proof reels](#proof-reels) and [Writing a story](#sec-865). An item with a scenario declares `{ "type": "scenario" }` in `probes`.- `covers` lists the backlog surfaces the story speaks for, by ledger key (`/galaxy`, `@three-ws/scene-mcp`, `workers/rig`), so the announcement plan stops offering them.- `tier`: 1 (flagship: partner news, $THREE utility, major launches), 2 (features with proof), or 3 (proof of work: short demos, stats, build notes). Each tier owns one slot a day.- `priority` is an optional owner boost from -50 to 50 on top of the computed score. `expiresAt` marks time-sensitive news: it rises as its window closes and is dropped once it passes. `notBefore` is an embargo: the post is not ready before it.@@ -192150,7 +193148,7 @@ X Articles require the posting account to be on X Premium.- `textFrom` is optional. When set, `check` fails if the inline text differs from that announcement-pack file, so the copy that was reviewed is the copy that ships.- An `article` item carries `"article": { "title", "body", "cover": { "path" } }`, and its optional `posts` quote the published Article. The body is copy like any post: its prose (headings, paragraphs, lists and quotes; code blocks and tables are literal samples and exempt) goes through the same language lint and claims ledger, so a number in the fourth section needs evidence like one in the title, its links are resolved at review, and its words are spell-checked. Replacing an inline image makes the review stale, the same as editing the Markdown. An Article in `review` or `approved` must also use the room X allows (owner, 2026-10-11): a title of 80 to 100 characters, 2,400 or more words in 8 or more sections, 3,000 or more characters of code and tables, 4 or more inline images, a "The partners behind ..." section covering every partner on `pages/partners.html`, and a "Try it" section. Drafts are exempt so work in progress can be saved.-Cadence lives at the top of the file: `slots` (each `{ tier, at }` in UTC, or a kind slot `{ kind, at, everyDays, from }`, below), `windowMinutes` (how far a slot's opening may be jittered), `minimumMinutesApart`, `dailyCap`, and `quietHoursUtc` (a `["HH:MM", "HH:MM"]` pair, which may wrap midnight). `quality` sets the similarity limits, the maximum same-lane and same-pattern runs, and `maximumLength`: the longest a post may be, in weighted characters. @trythreews is on X Premium, so the queue sets it above the standard 280; a value under 280 is ignored. `approval` is the policy described below.+Cadence lives at the top of the file: `slots` (each `{ tier, at }` in UTC, a series slot `{ tier, series, at }`, or a kind slot `{ kind, at, everyDays, from }`, below), `windowMinutes` (how far a slot's opening may be jittered), `minimumMinutesApart`, `dailyCap`, and `quietHoursUtc` (a `["HH:MM", "HH:MM"]` pair, which may wrap midnight). `quality` sets the similarity limits, the maximum same-lane and same-pattern runs, and `maximumLength`: the longest a post may be, in weighted characters. @trythreews is on X Premium, so the queue sets it above the standard 280; a value under 280 is ignored. `approval` is the policy described below.**What the cap counts:** `dailyCap` limits scheduled posts in the last 24 hours, and a scheduled post is one the scheduler placed in a slot. A post an operator sends by hand (`run --id`) carries no slot and does not count toward it, because counting those let four owner-requested posts on one afternoon hold every slot shut the following morning. Hand-sent posts do still count toward `minimumMinutesApart`, which measures from the last post of any kind, so the schedule never fires minutes after a manual post. To fill an open slot by hand and keep the schedule's bookkeeping right, run a scheduler tick (`npm run x:content -- run`, no `--id`): it takes the same lock as the cron, picks the post the cron would, and records the slot so the cron sees it as used.@@ -192167,6 +193165,8 @@ Cadence lives at the top of the file: `slots` (each `{ tier, at }` in UTC, or aDrop the slot from `slots` and Articles go back to being ordinary tier 1 items.+**The daily partner spotlight owns the T1 slot** (owner, 2026-10-11): `{ "tier": 1, "series": "partners", "at": "15:30" }`. A series slot spends its series' best ready post first, ranked across every tier, and posts of a series that owns a slot are kept for it, so the series goes out once a day and never twice. When the series has nothing ready the slot is the ordinary T1 slot, so the prime-time flagship never goes empty. It is a daily slot and counts toward `dailyCap`. The series itself (registry, rotation, filming, lint) is in [x-partner-series.md](#sec-830).+**Three a day is a quota** (owner, 2026-09-30), so a slot is never left empty while an approved postcould fill it. When the usual order finds nothing, the slot takes, in turn:@@ -192269,7 +193269,7 @@ npm run x:outcomes -- --compare # the pipeline's posts against the hand-writte`approval` in the queue file:```json-"approval": { "mode": "auto", "tiers": [2, 3], "vetoHours": 2, "articles": true }+"approval": { "mode": "auto", "tiers": [2, 3], "vetoHours": 2, "articles": true, "series": ["partners"] }````mode` is `owner` (every post waits for `approve`) or `auto`. Under `auto` a post is released@@ -192278,7 +193278,7 @@ says which one stopped it:| Condition | Why ||---|---|-| Its tier is listed | Tier 1 carries a partner's name or $THREE, so it stays with the owner unless the queue lists it. |+| Its tier is listed, or its series is | Tier 1 carries a partner's name or $THREE, so it stays with the owner unless the queue lists it. A series in `series` (the partner spotlight) is released whatever its tier, because its copy is held to the registry and the series lint in [x-partner-series.md](#sec-830). || It was filmed, and the proof covers it | A post never proven against the product is never released by policy. || It tags no one | A tag puts a partner's name next to ours. A person decides that. || The review passed on the editor's own verdict | An `editorOverride` is a person's judgment, so it needs a person. |@@ -192425,13 +193425,13 @@ Queue edits reach production with the next deploy, because the cron reads the qu## Tests-[tests/x-content-reel.test.js](../tests/x-content-reel.test.js) covers scenario validation, the proof binding, proof as evidence, post length, and what the editor is given for a reel. [tests/x-content-approval.test.js](../tests/x-content-approval.test.js) covers the approval policy and story coverage. [tests/x-content-outcomes.test.js](../tests/x-content-outcomes.test.js) covers the learning loop, and [tests/x-content-overlay.test.js](../tests/x-content-overlay.test.js) the bundles.+[tests/x-content-reel.test.js](../tests/x-content-reel.test.js) covers scenario validation, the proof binding, proof as evidence, post length, and what the editor is given for a reel. [tests/x-content-approval.test.js](../tests/x-content-approval.test.js) covers the approval policy and story coverage. [tests/x-content-partners.test.js](../tests/x-content-partners.test.js) covers the partner spotlight: the registry check, the rotation, the series lint, claims built from the registry and the run, and the drafting loop. [tests/x-content-outcomes.test.js](../tests/x-content-outcomes.test.js) covers the learning loop, and [tests/x-content-overlay.test.js](../tests/x-content-overlay.test.js) the bundles.[tests/x-content.test.js](../tests/x-content.test.js) covers the tiered slots, fill-down, priority scoring, holds and the fall-through that publishes the next post when one fails, stock counting, quote-tweet ids and their publish wiring, hand-sent posts counting toward spacing but not the cap, the video speed-up filter chain and its caption ordering, the voice and editorial lint, the claims ledger, media quality, review records binding approval to exact content, the editor verdict rules, the media rules, the Markdown to Article offsets, the scheduler's spacing, cap, embargo, and resume rules, and the publisher's thread chaining, crash resume, and Article draft, publish, and quote sequence.----<a id="sec-813"></a>+<a id="sec-826"></a>> **Source:** `docs/x-memory-seeding.md` · [↑ table of contents](#table-of-contents)@@ -192450,7 +193450,7 @@ yes on a screen that tells you exactly what will be read and stored.- **Surface**: Settings, Connected accounts, X card at [/settings#connected-accounts](https://three.ws/settings#connected-accounts)- **API**: `/api/agents/:id/memory/seed/x`-- **Related**: [Memory system](#sec-420), [Farcaster memory seeding](#sec-302), [GitHub seeding in the same table](memory.md#seeding-memory-from-an-existing-account)+- **Related**: [Memory system](#sec-424), [Farcaster memory seeding](#sec-305), [GitHub seeding in the same table](memory.md#seeding-memory-from-an-existing-account)---@@ -192549,7 +193549,7 @@ Each fact becomes one row in `agent_memories`:from your posting history.- Salience `0.80` for the top-ranked fact, decaying by rank.- The **top five facts land in the `working` tier**, the always-in-context core- the chat runtime pages into every reply (see [memory system](#sec-420)).+ the chat runtime pages into every reply (see [memory system](#sec-424)).That is what makes a seed observable in the very next conversation turn.- `context` carries `source: 'x_seed'`, your handle, the distillation lane(`model` or `derived`), the disclosure version, and the consent id.@@ -192764,7 +193764,7 @@ Seeded rows in `agent_memories` are found by tag (`tags && '{x_seed}'`) and by----<a id="sec-814"></a>+<a id="sec-827"></a>> **Source:** `docs/x-mention-avatar.md` · [↑ table of contents](#table-of-contents)@@ -192797,11 +193797,11 @@ Only the author of the mention. The picture comes from the mention's own authornode --env-file=.env.local scripts/x-mention-avatar-dry-run.mjs --base https://three.ws-Related: [X mention bot safety rules](#sec-815), [photo to 3D](#sec-816).+Related: [X mention bot safety rules](#sec-828), [photo to 3D](#sec-829).----<a id="sec-815"></a>+<a id="sec-828"></a>> **Source:** `docs/x-mention-bot.md` · [↑ table of contents](#table-of-contents)@@ -193102,7 +194102,7 @@ wait is recorded as `pending`. Every `x-mentions` tick then runs`runFollowUps()` (`api/_lib/x-mention-poll.js`), which calls`finishPendingMakes()`, `finishPendingAvatars()` and `finishPendingImage3d()`(`api/_lib/x-mention-image3d.js`, see-[x-mention-image3d.md](#sec-816)):+[x-mention-image3d.md](#sec-829)):- **Gated like any reply.** The kill switch skips all three, and a closedread/post budget gate skips all three. The report carries `followUps: {@@ -193230,7 +194230,7 @@ reply through `/x/ops` today). Going fully live, i.e. setting----<a id="sec-816"></a>+<a id="sec-829"></a>> **Source:** `docs/x-mention-image3d.md` · [↑ table of contents](#table-of-contents)@@ -193263,11 +194263,166 @@ The picture is only used when its poster is the person who wrote the mention. Annode --env-file=.env.local scripts/x-mention-image3d-dry-run.mjs --base https://three.ws-Related: [X mention bot safety rules](#sec-815).+Related: [X mention bot safety rules](#sec-828).----<a id="sec-817"></a>+<a id="sec-830"></a>++> **Source:** `docs/x-partner-series.md` · [↑ table of contents](#table-of-contents)++# The daily partner spotlight++Every day @trythreews features one partner listed on [three.ws/partners](https://three.ws/partners) and one thing three.ws built on that partner's technology. Each spotlight is a thread of a head post and three to five replies, carrying a reel filmed live against production that day, plus a head built for the slot: a card, a GIF, the reel itself, or generated art. It runs inside the [X content pipeline](#sec-825), so every rule there (the claims ledger, the language lint, the editor review, the veto window) applies to it too.++| Piece | Where |+|---|---|+| Registry: one file per partner, listing its designation, wording rules and features | [data/x-content/partners/](../data/x-content/partners) |+| Engine: rotation, brief, drafting, series lint, claims, item | [api/_lib/x-content/partners.js](../api/_lib/x-content/partners.js) |+| CLI | [scripts/x-partners.mjs](../scripts/x-partners.mjs) (`npm run x:partners`) |+| Slot and approval | `slots` and `approval.series` in [data/x-content/queue.json](../data/x-content/queue.json) |+| Scheduled runner: a Cloud Run Job image and its setup | [deploy/x-partners/](../deploy/x-partners), [scripts/create-x-partners-job.mjs](../scripts/create-x-partners-job.mjs) |+| Tests | [tests/x-content-partners.test.js](../tests/x-content-partners.test.js) |++## The registry++A partner file is the only source the series may draw on. The model never invents a fact: every sentence it can lean on is written here with evidence the claims ledger checks at review.++```json+{+ "id": "ibm",+ "name": "IBM",+ "order": 2,+ "designation": "IBM Business Partner",+ "designationEvidence": [{ "type": "page", "url": "https://three.ws/partners", "contains": "IBM Business Partner" }],+ "page": "https://three.ws/blog/three-ws-ibm-business-partner",+ "handle": "IBM",+ "mark": null,+ "forbidden": ["endorsed by IBM", "official IBM partner"],+ "guidance": "How to talk about this partnership, and what never to say.",+ "docs": ["docs/partners.md"],+ "features": [+ {+ "id": "user-group-in-world-meetup",+ "title": "A meetup inside a 3D world",+ "surface": "https://three.ws/...",+ "covers": [],+ "lane": "community",+ "summary": "One paragraph on what was built and why it matters.",+ "docs": [],+ "scenario": { "format": "square", "steps": [] },+ "probes": [],+ "facts": [{ "says": "a sentence the copy may use", "evidence": [] }]+ }+ ]+}+```++| Field | Meaning |+|---|---|+| `order` | Position on the partners page. Ties in the rotation go to the lower number. |+| `designation` | The exact program name. Every spotlight states it word for word. |+| `page` | The partner's page on three.ws. One reply links it. |+| `forbidden` | Phrases that overstate the relationship. Any of them fails the lint. |+| `guidance` | Plain instructions for the writer: what the partnership is, and what it is not. |+| `features[].surface` | The page the head post links. |+| `features[].lane` | `community`, `developer`, `token` or `labs`, the same lanes as the queue. |+| `features[].scenario` | The proof scenario filmed for the reel ([reel.js](../api/_lib/x-content/reel.js) format). Its `read` steps become numbers the copy may quote. |+| `features[].facts` | Sentences with evidence: `page`, `file`, or `proof` (`{ "type": "proof", "fact", "equals" }` checks a value the run read; `{ "saw" }` checks text the run saw). |++`npm run x:partners -- check` validates every file and names each missing piece. A feature that cannot be filmed against production (a surface behind credentials production does not have, say) does not belong in the registry: the series only announces what it has watched working.++Adding a partner: write its file, run `check`, then `one --partner <id> --dry-run` to film and draft it once without touching the queue. Adding a feature to an existing partner works the same way with `--feature`.++## Rotation++`pickNext` chooses the partner seen least recently, breaking ties by `order`, then that partner's least recently featured feature. The head rotates through `card`, `gif`, `reel` and `art`, and the opening pattern through `mechanism`, `walkthrough`, `clip` and `number`, each avoiding the last one used. `number` is only chosen when the feature has a fact with a digit in it, so the series never leads on a number it cannot prove.++History is read from the queue itself: every item with `series: "partners"` carries `spotlight: { partner, feature, head, pattern }` and a `notBefore` day. `--overlay <dir>` adds the spotlights in a materialized production overlay, so a machine whose `queue.json` is older than production still rotates correctly.++Each spotlight takes its own day after every day already held. If today's series slot has already opened and passed, the next spotlight starts tomorrow.++## Drafting++For each missing day, `daily`:++1. Films the feature's scenario against production with `proveItem`. The run's read values (counts, statuses) become facts the copy may quote. A feature whose scenario fails is skipped for the rest of the run, and the next partner in the rotation takes the day.+2. Builds a brief from the registry entry, the head and pattern, and the names of the other partners (so the copy can be checked for partners the feature does not involve).+3. Asks the model chain (`callModelChain`) for `{ post, thread, headline, body, prompt, why }`, with the house voice ([announce-voice.md](#sec-102)) and the keeper exemplar in the system prompt.+4. Lints the draft and sends every finding back for a rewrite, up to three attempts.+5. Builds the queue item (`itemFor`), attaches the reel, builds the head from it (`rebuildHead`), validates it, writes the story to `data/x-content/stories/<id>.json`, and hands it to `x:content adopt` and `advance`.++The series lint (`seriesFindings`) adds these rules on top of the pipeline's own:++- The designation appears word for word. No `forbidden` phrase appears.+- No @mentions anywhere: a tag puts a partner's name next to ours, and that is a person's decision.+- The head post names the partner and links the feature's surface. One reply links the partner's page.+- Three to five replies, and at least three registry facts quoted, in plain prose rather than quotation marks.+- No copy about where the media sits ("this reply", "the card above").+- No other partner is named unless the feature's own facts name it.++`draftFindings` then runs the pipeline's copy, language and claims checks, the head spec limits (a 90-character headline, a 200-character body), and a similarity check against the queue and the archive (limit 0.34).++Claims are never taken from the model. `claimsFor` builds them from the designation evidence, the registry facts the copy actually quotes, and the values the run read, so every number in a spotlight is one the ledger can prove.++## The slot++The queue's tier 1 slot belongs to the series:++```json+"slots": [+ { "tier": 2, "at": "12:00" },+ { "tier": 1, "series": "partners", "at": "15:30" },+ { "tier": 3, "at": "19:00" },+ { "kind": "article", "at": "22:30", "everyDays": 2, "from": "2026-10-08" }+]+```++A series slot spends its series' best ready post first, ranked across every tier. Posts of a series that owns a slot are kept for that slot, so the series posts once a day and never twice. When the series has nothing ready, the slot is the ordinary tier 1 slot, so the prime-time flagship never goes empty. It counts toward `dailyCap` like any daily slot.++## Approval++Spotlights are tier 1, which normally waits for the owner. `"series": ["partners"]` in `approval` releases a listed series by policy whatever its tier, behind the veto window, and only when the other conditions hold: the post was filmed and the proof covers it, it tags no one, and the review passed on the editor's own verdict. Remove `partners` from the list and every spotlight waits for `approve` again.++## The weekly Article++Once every seven days the series also writes a partner deep-dive as an X Article: one partner, every feature in its registry entry, filmed and measured that day. `daily` writes it when it is due (`--no-article` skips it), and `article --partner <id>` writes one on demand.++1. Every feature's scenario is filmed against production. The lead feature's run binds to the Article's own id, so its reel is the proof the Article's post carries; the others are filmed under `<id>-<feature>`. Four or more frames from the reels become inline figures in `public/x-media/<id>/`, and the cover is built from the lead reel.+2. `articleBlocks` builds the Article's code and tables from data, never from the model: a table of the runs (surface, length, values read), a facts table per feature with the evidence behind each sentence, each scenario as JSON, and for API surfaces the real request with the response production returned.+3. The model writes the prose around them as `TITLE / POST / --- / markdown`, placing every block once as `{{block:NAME}}` and the figures as `{{figure:N}}`. `assembleArticle` substitutes them and names any block missing, repeated or unknown.+4. The draft must pass the queue's Article gate (an 80 to 100 character title, 2400 words over at least eight sections, at least four images, enough code and tables, a section on every partner listed on the partners page, a Try it section) plus the series lint, with every finding fed back for up to three attempts.+5. Claims come from the designation, the registry facts the prose quotes, and the lead run's values only (a non-lead run is not the proof the post carries, so its numbers stay in the tables). The item is a tier 1 Article with `spotlight: { partner, article: true, features }`, written to `data/x-content/articles/<id>.md` and handed to `adopt` and `advance`.++Rotation goes to the partner whose last Article is oldest, ties by `order`. Articles post in the queue's Article slot, not the series slot, and wait for the owner's `approve` like any tier 1 Article.++## Running it++```bash+npm run x:partners -- check # validate the registry+npm run x:partners -- plan --days 7 # the rotation ahead and how many days are in stock+npm run x:partners -- daily --days 3 --dry-run # film and draft three days, print them, write nothing+npm run x:partners -- daily --days 3 # write them to the queue and send them to review+npm run x:partners -- one --partner aws --feature marketplace-front-door --head gif+npm run x:partners -- article --partner ibm --dry-run # film and draft the deep-dive Article, write nothing+```++`--ship` on `daily` or `one` passes `--ship` to `advance`, which bundles approved spotlights for production through the overlay ([x-content-pipeline.md](#sec-825), "Publishing without a deploy"). Shipping publishes, so it is an owner-approved step.++To keep the series in stock unattended, run `daily` once a day on a machine with a browser and ffmpeg, after materializing production's overlay:++```bash+npm run x:bundle -- pull --dir /tmp/x-overlay+npm run x:partners -- daily --days 3 --overlay /tmp/x-overlay --ship+```++That run is packaged as a Cloud Run Job. [deploy/x-partners/](../deploy/x-partners) holds the image (Node, Chromium, ffmpeg and a colour emoji font, so the reels film the way they do on a workstation) and its entrypoint, which pulls the overlay and runs `daily --days 3 --ship`. `node scripts/create-x-partners-job.mjs` prints the plan; `--apply` builds the image, creates the job `three-ws-x-partners` with the production service's env and secret references, and schedules it daily at 08:10 UTC through Cloud Scheduler. Applying it ships posts unattended, so it is an owner-approved step.++Keeping three days in stock means a failed run, a flaky surface, or a model outage costs nothing: the slot still has a reviewed spotlight waiting.++---++<a id="sec-831"></a>> **Source:** `docs/x-posts/3d-ar-studio-launch.md` · [↑ table of contents](#table-of-contents)@@ -193567,7 +194722,7 @@ Point it at your own catalogue with one option if you would rather use yours.----<a id="sec-818"></a>+<a id="sec-832"></a>> **Source:** `docs/x-posts/3d-ar-studio-video-script.md` · [↑ table of contents](#table-of-contents)@@ -193692,7 +194847,7 @@ match them to the narration beats:----<a id="sec-819"></a>+<a id="sec-833"></a>> **Source:** `docs/x-posts/README.md` · [↑ table of contents](#table-of-contents)@@ -193706,7 +194861,7 @@ explicit approval). Each file states what it's for and what has already been ver> **`@nichxbt` is suspended (reported 2026-08-27).** Nine of the drafts below pair a> `@trythreews` post with a personal-voice quote tweet from `@nichxbt`, and that second half> cannot be posted right now. Post the `@trythreews` half as written and hold the other one;-> do not move its copy onto the platform account. [`x-accounts.md`](#sec-807) has the+> do not move its copy onto the platform account. [`x-accounts.md`](#sec-820) has the> account status and the full rule.## How these are written@@ -193725,51 +194880,51 @@ explicit approval). Each file states what it's for and what has already been ver| File | What it announces || --- | --- |-| [`onchain-agent-wallets-x-post.md`](#sec-836) | Agent wallets with an on-chain spending allowance instead of a private key: SPL Token delegation, guardrails, x402, revocable custody |-| [`mcp-registry-fleet-x-post.md`](#sec-828) | The fleet as a whole: 72 MCP servers under one namespace in the official registry, all current |-| [`metaplex-agent-mcp-launch.md`](#sec-831) | The open-source agent infrastructure announcement covering `@three-ws/metaplex-agent-mcp` and `@three-ws/onchain-agent-wallets`, and why the integrations are bullish for $THREE |-| [`metaplex-agent-mcp-x-post.md`](#sec-833) | The MCP server that mints an agent into the Metaplex Agent Registry with its own wallet and EIP-8004 identity |-| [`metaplex-agent-deployer-x-post.md`](#sec-830) | The browser deployer at nirholas.github.io/metaplex-agent-mcp |-| [`3d-ar-studio-launch.md`](#sec-817) | 3D AR Studio, the AR studio extracted from three.ws and published as an open-source package |-| [`ar-quick-look-fix-x-post.md`](#sec-821) | AR Forge and AR Studio now open real Apple Quick Look / Google Scene Viewer on a phone, matching what `/avatars/:id/ar` already did. Shipped to `main` locally, **not yet deployed**: do not post until verified live on a real iPhone |-| [`threews-avatar-launch.md`](#sec-845) | The three.ws avatar pipeline launch copy |-| [`oracle-trading-mcp-x-post.md`](#sec-839) | The oracle trading MCP server launch |-| [`sperax-staking-in-chat-x-post.md`](#sec-843) | SperaxOS chat-native staking, balance, and buy-SPA tool calls. The embedded `/staking` page is not working yet: do not announce until the blockers in the file clear |-| [`news-archive-x-post.md`](#sec-834) | The news archive |-| [`proof-of-life-x-post.md`](#sec-841) | A shipping-evidence post for the platform account: what landed this week, with public verification links. Names nothing about the personal account |-| [`pumpfun-article-x-post.md`](#sec-842) | The pump.fun article |+| [`onchain-agent-wallets-x-post.md`](#sec-850) | Agent wallets with an on-chain spending allowance instead of a private key: SPL Token delegation, guardrails, x402, revocable custody |+| [`mcp-registry-fleet-x-post.md`](#sec-842) | The fleet as a whole: 72 MCP servers under one namespace in the official registry, all current |+| [`metaplex-agent-mcp-launch.md`](#sec-845) | The open-source agent infrastructure announcement covering `@three-ws/metaplex-agent-mcp` and `@three-ws/onchain-agent-wallets`, and why the integrations are bullish for $THREE |+| [`metaplex-agent-mcp-x-post.md`](#sec-847) | The MCP server that mints an agent into the Metaplex Agent Registry with its own wallet and EIP-8004 identity |+| [`metaplex-agent-deployer-x-post.md`](#sec-844) | The browser deployer at nirholas.github.io/metaplex-agent-mcp |+| [`3d-ar-studio-launch.md`](#sec-831) | 3D AR Studio, the AR studio extracted from three.ws and published as an open-source package |+| [`ar-quick-look-fix-x-post.md`](#sec-835) | AR Forge and AR Studio now open real Apple Quick Look / Google Scene Viewer on a phone, matching what `/avatars/:id/ar` already did. Shipped to `main` locally, **not yet deployed**: do not post until verified live on a real iPhone |+| [`threews-avatar-launch.md`](#sec-859) | The three.ws avatar pipeline launch copy |+| [`oracle-trading-mcp-x-post.md`](#sec-853) | The oracle trading MCP server launch |+| [`sperax-staking-in-chat-x-post.md`](#sec-857) | SperaxOS chat-native staking, balance, and buy-SPA tool calls. The embedded `/staking` page is not working yet: do not announce until the blockers in the file clear |+| [`news-archive-x-post.md`](#sec-848) | The news archive |+| [`proof-of-life-x-post.md`](#sec-855) | A shipping-evidence post for the platform account: what landed this week, with public verification links. Names nothing about the personal account |+| [`pumpfun-article-x-post.md`](#sec-856) | The pump.fun article |## Companion threads for the AWS Builder Center articlesLong-form threads that stand on their own and pair with a draft in-[`aws-builder-center.md`](#sec-162). Each ends with a labeled reply to add once its+[`aws-builder-center.md`](#sec-163). Each ends with a labeled reply to add once itsarticle is live on the Builder Center, and each lists the preconditions that must hold before it posts.| File | What it covers || --- | --- |-| [`universal-retargeting-thread.md`](#sec-847) | One clip library on any humanoid skeleton: name canonicalization, rest poses, the A-pose re-aim. Hold until the re-aim is deployed (the file has the check) |-| [`immutable-embed-releases-thread.md`](#sec-827) | Write-once versioned URLs and SRI pins for the `<agent-3d>` script, and the incident that taught us why |-| [`claims-ledger-thread.md`](#sec-822) | The publishing pipeline that refuses a claim it cannot prove: evidence, probes, proof reels, content-hash reviews |-| [`open-weight-3d-forge-thread.md`](#sec-838) | How a prompt becomes a textured GLB on open-weight models: the lane router, the failover ladder, cold starts, and what the generation log says |+| [`universal-retargeting-thread.md`](#sec-861) | One clip library on any humanoid skeleton: name canonicalization, rest poses, the A-pose re-aim. Hold until the re-aim is deployed (the file has the check) |+| [`immutable-embed-releases-thread.md`](#sec-841) | Write-once versioned URLs and SRI pins for the `<agent-3d>` script, and the incident that taught us why |+| [`claims-ledger-thread.md`](#sec-836) | The publishing pipeline that refuses a claim it cannot prove: evidence, probes, proof reels, content-hash reviews |+| [`open-weight-3d-forge-thread.md`](#sec-852) | How a prompt becomes a textured GLB on open-weight models: the lane router, the failover ladder, cold starts, and what the generation log says |## Video and narration scripts| File | What it covers || --- | --- |-| [`metaplex-agent-mcp-veo-script.md`](#sec-832) | Shot-by-shot Veo (image-to-video) prompts for the agent infrastructure clip, built from a three.ws 3D avatar as the reference frame |-| [`metaplex-agent-deployer-video-script.md`](#sec-829) | Spoken narration for the deployer clip |-| [`threews-avatar-video-script.md`](#sec-846) | Shot list for the avatar clip |-| [`3d-ar-studio-video-script.md`](#sec-818) | Narration and shot prompts for the AR Studio launch video |+| [`metaplex-agent-mcp-veo-script.md`](#sec-846) | Shot-by-shot Veo (image-to-video) prompts for the agent infrastructure clip, built from a three.ws 3D avatar as the reference frame |+| [`metaplex-agent-deployer-video-script.md`](#sec-843) | Spoken narration for the deployer clip |+| [`threews-avatar-video-script.md`](#sec-860) | Shot list for the avatar clip |+| [`3d-ar-studio-video-script.md`](#sec-832) | Narration and shot prompts for the AR Studio launch video |## Events and community| File | What it covers || --- | --- |-| [`osf-issue-reply.md`](#sec-840) | The reply to Andrea Griffiths closing the loop on the Open Source Friday request (open-source-friday#254), in a Premium-length and a 280-character form |-| [`event-x-posts.md`](#sec-823) | Event campaign copy, split by account (`@trythreews` institutional, `@nichxbt` personal) |-| [`x-meetup-posts.md`](#sec-848) | The in-platform community meetup announcement |-| [`ibm-skillsbuild-x-post.md`](#sec-826) | The IBM SkillsBuild badge |-| [`fomo-verified-x-post.md`](#sec-824) | FOMO verification |+| [`osf-issue-reply.md`](#sec-854) | The reply to Andrea Griffiths closing the loop on the Open Source Friday request (open-source-friday#254), in a Premium-length and a 280-character form |+| [`event-x-posts.md`](#sec-837) | Event campaign copy, split by account (`@trythreews` institutional, `@nichxbt` personal) |+| [`x-meetup-posts.md`](#sec-862) | The in-platform community meetup announcement |+| [`ibm-skillsbuild-x-post.md`](#sec-840) | The IBM SkillsBuild badge |+| [`fomo-verified-x-post.md`](#sec-838) | FOMO verification |## Conventions@@ -193785,7 +194940,7 @@ entry is dead once the file is no longer routed.----<a id="sec-820"></a>+<a id="sec-834"></a>> **Source:** `docs/x-posts/android-app-launch.md` · [↑ table of contents](#table-of-contents)@@ -193852,7 +195007,7 @@ The artwork and the X copy live in [`../../marketing/android-launch/`](../market## X (@trythreews), held until the account is restoredDo not post this while `@trythreews` is suspended; see-[`../x-account-appeal.md`](#sec-806). It is written and ready for the day the+[`../x-account-appeal.md`](#sec-819). It is written and ready for the day theappeal lands.```@@ -193877,7 +195032,7 @@ The checklist item is in [`../../solana-mobile/docs/CHECKLIST.md`](../solana-mob----<a id="sec-821"></a>+<a id="sec-835"></a>> **Source:** `docs/x-posts/ar-quick-look-fix-x-post.md` · [↑ table of contents](#table-of-contents)@@ -193885,7 +195040,7 @@ The checklist item is in [`../../solana-mobile/docs/CHECKLIST.md`](../solana-mobAnnouncement copy for a bug fix, not a new feature: `three.ws/ar` (AR Forge) and `three.ws/ar/studio`(AR Studio) now place a model in your real room on iPhone the way `three.ws/avatars/:id/ar` already-did. Related file: [threews-avatar-launch.md](#sec-845) sells the avatar-has-a-body+did. Related file: [threews-avatar-launch.md](#sec-859) sells the avatar-has-a-bodystory; this one sells "AR here means AR, on every phone, not just some of them."**Thesis of this announcement:** every AR surface on the site now runs real ARKit Quick Look on@@ -193968,7 +195123,7 @@ the resolution of a problem, and "watch it look real" is a dare to try it, not a### From @nichxbt (the human one, quote-tweeting the @trythreews post above)-Same two-account split as [event-x-posts.md](#sec-823): `@trythreews` posts the+Same two-account split as [event-x-posts.md](#sec-837): `@trythreews` posts theinstitutional version above, `@nichxbt` quote-tweets it with the human one a few minutes later, notsimultaneously. Her post is pure enthusiasm, first person, no bug talk.@@ -194094,15 +195249,15 @@ what three.ws does well rather than dwelling on the fix.post; add a $THREE line only if a specific alternate calls for it, don't bolt one onto everydraft.- **Screenshots, if used, should show the model sitting convincingly in a real room**, the way- [3d-ar-studio-launch.md](#sec-817) already frames its media: a real floor in+ [3d-ar-studio-launch.md](#sec-831) already frames its media: a real floor inframe is the whole point.- **Do not combine this with the AR Studio open-source package announcement**- ([3d-ar-studio-launch.md](#sec-817)). That post is about giving the surface away as+ ([3d-ar-studio-launch.md](#sec-831)). That post is about giving the surface away asa library; this one is about how good AR feels on three.ws today. Mixing them muddies both.----<a id="sec-822"></a>+<a id="sec-836"></a>> **Source:** `docs/x-posts/claims-ledger-thread.md` · [↑ table of contents](#table-of-contents)@@ -194111,7 +195266,7 @@ what three.ws does well rather than dwelling on the fix.A thread for **@trythreews** on how the account itself is run: an AI-assisted pipeline that draftsand reviews posts with a model, while deterministic code decides what is true, what is approved,and whether a post already went out. It is the short companion to the AWS Builder Center article-[aws-builder-center-claims-ledger.md](#sec-156), and it stands on+[aws-builder-center-claims-ledger.md](#sec-157), and it stands onits own for a reader who never opens that article.**Thesis of this thread:** a model may draft and edit; it does not get to decide what is true.@@ -194125,11 +195280,11 @@ site:| Claim in the thread | Where it was verified ||---|---|-| Every number, ordinal and absolute word must sit inside a declared claim with evidence; an uncovered number is blocking | [`api/_lib/x-content/editorial.js`](../api/_lib/x-content/editorial.js) (`ABSOLUTES`, `claimProblems`), [`docs/x-content-pipeline.md`](#sec-812) |+| Every number, ordinal and absolute word must sit inside a declared claim with evidence; an uncovered number is blocking | [`api/_lib/x-content/editorial.js`](../api/_lib/x-content/editorial.js) (`ABSOLUTES`, `claimProblems`), [`docs/x-content-pipeline.md`](#sec-825) || The checker runs both ways (a claim not in the copy also fails) | `claimProblems` in [`editorial.js`](../api/_lib/x-content/editorial.js) || Machine Atlas run read 9 cylinders before the drag and 5 after | [`data/x-content/proofs/machine-atlas.json`](../data/x-content/proofs/machine-atlas.json) (`facts.cylinders`, `facts.cylindersAfter`) || Page evidence is matched in a real browser after the text stops growing; no fuzzy match, no model | `createPageReader` and the `page` case in [`api/_lib/x-content/verify.js`](../api/_lib/x-content/verify.js) |-| Every post the owner took down had passed the fact check | [`docs/x-content-pipeline.md`](#sec-812) ("Proof reels"), and the header of [`api/_lib/x-content/reel.js`](../api/_lib/x-content/reel.js) |+| Every post the owner took down had passed the fact check | [`docs/x-content-pipeline.md`](#sec-825) ("Proof reels"), and the header of [`api/_lib/x-content/reel.js`](../api/_lib/x-content/reel.js) || A post with no probe fails review; probe kinds; a command probe must exit 0; API probes run again before sending | `verifyItem`, `probeChecks`, `commandProbe` in [`verify.js`](../api/_lib/x-content/verify.js); `preflight` in [`api/_lib/x-content/runner.js`](../api/_lib/x-content/runner.js) || One to three frames a second in software; clock stepped 1/30 s; no reel when a step fails | header, `Take.frame` and `proveItem` in [`reel.js`](../api/_lib/x-content/reel.js) (`DEFAULT_FPS = 30`) || A wait of 2 s or more is cut and labelled; the stamp names commit and day | `CUT_BADGE_AFTER_SEC = 2` and the stamp in `proveItem`, [`reel.js`](../api/_lib/x-content/reel.js) |@@ -194145,7 +195300,7 @@ site:| Ledger writes every media id and post id as X returns it; a crashed thread resumes at the next reply | `uploadOnce`, `publishPosts`, `publishItem` in [`api/_lib/x-content/publisher.js`](../api/_lib/x-content/publisher.js) || Policy release conditions; veto window; ops alert | `policyBlockers`, `vetoUntil` in [`api/_lib/x-content/approval.js`](../api/_lib/x-content/approval.js); `advance` in [`scripts/x-content.mjs`](../scripts/x-content.mjs) || Outcomes read at most every 6 hours over 90 days; used for ranking only | `OUTCOMES_REFRESH_HOURS = 6`, `OUTCOMES_WINDOW_DAYS = 90` in [`api/_lib/x-content/outcomes.js`](../api/_lib/x-content/outcomes.js); read by [`priority.js`](../api/_lib/x-content/priority.js) and as editor calibration, by no deterministic check |-| An engagement-ask phrase in the lint blocks the example post in our own docs | `PUSHY_CTAS` (`/\bdrop a\b/i`) in [`editorial.js`](../api/_lib/x-content/editorial.js) against the "Queue item format" example in [`docs/x-content-pipeline.md`](#sec-812); reproduced with `lintItem` on 2026-10-08 |+| An engagement-ask phrase in the lint blocks the example post in our own docs | `PUSHY_CTAS` (`/\bdrop a\b/i`) in [`editorial.js`](../api/_lib/x-content/editorial.js) against the "Queue item format" example in [`docs/x-content-pipeline.md`](#sec-825); reproduced with `lintItem` on 2026-10-08 || The docs page is live | [three.ws/docs/x-content-pipeline](https://three.ws/docs/x-content-pipeline) answered 200 and rendered "The editorial bar" on 2026-10-08 |The thread also passes the pipeline's own offline gate: every post was run through@@ -194318,7 +195473,7 @@ in the alt text to match the new stamp.----<a id="sec-823"></a>+<a id="sec-837"></a>> **Source:** `docs/x-posts/event-x-posts.md` · [↑ table of contents](#table-of-contents)@@ -194632,7 +195787,7 @@ Practical notes for reused footage:----<a id="sec-824"></a>+<a id="sec-838"></a>> **Source:** `docs/x-posts/fomo-verified-x-post.md` · [↑ table of contents](#table-of-contents)@@ -194726,7 +195881,7 @@ Shorter alternate:----<a id="sec-825"></a>+<a id="sec-839"></a>> **Source:** `docs/x-posts/github-100-stars.md` · [↑ table of contents](#table-of-contents)@@ -194734,7 +195889,7 @@ Shorter alternate:Post copy for the 100-star milestone on X. Posting is owner-gated; these are ready-to-paste drafts. Attach [media/github-100-stars-people.png](media/github-100-stars-people.png) (2400x1350, real contributor avatars pulled from GitHub at render time, plus three install commands) to the Version A main post, [media/github-100-stars-x.png](media/github-100-stars-x.png) (twelve stat tiles) to the Version B main post, and [media/github-100-stars-ecosystem.png](media/github-100-stars-ecosystem.png) (same size, the footprint beyond the repo) to reply 3. [media/github-100-stars-square.png](media/github-100-stars-square.png) (1620x1620) is the square cut for Telegram, Instagram, and LinkedIn.-Regenerate both images with `node scripts/render-github-stars-banner.mjs` after updating the `STATS` and `SURFACES` arrays in the script. The canonical link and number table both announcements (the post and the X article) must cite is [open-source-footprint.md](#sec-460); keep the copy below in sync with it.+Regenerate both images with `node scripts/render-github-stars-banner.mjs` after updating the `STATS` and `SURFACES` arrays in the script. The canonical link and number table both announcements (the post and the X article) must cite is [open-source-footprint.md](#sec-465); keep the copy below in sync with it.## Where every number comes from (as of August 25, 2026)@@ -194949,7 +196104,7 @@ Star the repo: github.com/nirholas/three.ws----<a id="sec-826"></a>+<a id="sec-840"></a>> **Source:** `docs/x-posts/ibm-skillsbuild-x-post.md` · [↑ table of contents](#table-of-contents)@@ -195157,14 +196312,14 @@ https://www.credly.com/badges/b7ea921a-ce3d-4f4d-bfac-38f95276d361/twitter via @----<a id="sec-827"></a>+<a id="sec-841"></a>> **Source:** `docs/x-posts/immutable-embed-releases-thread.md` · [↑ table of contents](#table-of-contents)# X thread: immutable embed releasesCompanion thread for @trythreews to the AWS Builder Center draft-[`aws-builder-center-immutable-embed-releases.md`](#sec-157):+[`aws-builder-center-immutable-embed-releases.md`](#sec-158):how three.ws releases the `<agent-3d>` web component so a pinned embed never breaks, the2026-10-01 incident where rebuilding version 1.5.2 on every deploy broke the integrity pins we hadpublished, and the second lesson about code that runs on someone else's origin.@@ -195409,7 +196564,7 @@ edge cache (`s-maxage=300`); the response also allows browsers to keep the file----<a id="sec-828"></a>+<a id="sec-842"></a>> **Source:** `docs/x-posts/mcp-registry-fleet-x-post.md` · [↑ table of contents](#table-of-contents)@@ -195526,14 +196681,14 @@ Post 1 is the main post. Then:----<a id="sec-829"></a>+<a id="sec-843"></a>> **Source:** `docs/x-posts/metaplex-agent-deployer-video-script.md` · [↑ table of contents](#table-of-contents)# Spoken script: the agent deployer videoThe words only. Visual prompts, camera, and palette live in-[metaplex-agent-mcp-x-post.md](#sec-833); this file is what gets said, cut+[metaplex-agent-mcp-x-post.md](#sec-847); this file is what gets said, cutinto the 8-second beats Veo generates so each line lands inside one clip.**Pacing rule:** 8 seconds of natural speech is 18 to 22 words at the absolute ceiling, and 12 to 16@@ -195633,7 +196788,7 @@ For a single generation with no editing. One breath, one idea.----<a id="sec-830"></a>+<a id="sec-844"></a>> **Source:** `docs/x-posts/metaplex-agent-deployer-x-post.md` · [↑ table of contents](#table-of-contents)@@ -195871,7 +197026,7 @@ our own product, no pretending to be a bystander.----<a id="sec-831"></a>+<a id="sec-845"></a>> **Source:** `docs/x-posts/metaplex-agent-mcp-launch.md` · [↑ table of contents](#table-of-contents)@@ -196074,14 +197229,14 @@ fund them, which is already the safe, verified claim.----<a id="sec-832"></a>+<a id="sec-846"></a>> **Source:** `docs/x-posts/metaplex-agent-mcp-veo-script.md` · [↑ table of contents](#table-of-contents)# Veo script: the open-source stackShot-by-shot **visual** prompts for a Veo image-to-video clip to run alongside-[`metaplex-agent-mcp-launch.md`](#sec-831). Text-to-video only, no dialogue, no+[`metaplex-agent-mcp-launch.md`](#sec-845). Text-to-video only, no dialogue, novoiceover: the reference frame is a three.ws 3D avatar, and every prompt below is written to bepasted straight into Veo as-is.@@ -196185,7 +197340,7 @@ to show something spreading to others, not just one agent getting a wallet.----<a id="sec-833"></a>+<a id="sec-847"></a>> **Source:** `docs/x-posts/metaplex-agent-mcp-x-post.md` · [↑ table of contents](#table-of-contents)@@ -196462,7 +197617,7 @@ keys, your limits.**----<a id="sec-834"></a>+<a id="sec-848"></a>> **Source:** `docs/x-posts/news-archive-x-post.md` · [↑ table of contents](#table-of-contents)@@ -196552,11 +197707,11 @@ If someone asks how it stays current: the archiver runs hourly against all 197 fnewest month is always live and the corpus grows every hour. If someone asks about publisherrights: the reader shows a bounded excerpt plus our own summary and sends readers to thepublisher, and the cap plus any takedown is enforced server side across the reader, the RSS-mirror, archive search, and the agent knowledge corpus. See [docs/news-rights.md](#sec-441).+mirror, archive search, and the agent knowledge corpus. See [docs/news-rights.md](#sec-445).----<a id="sec-835"></a>+<a id="sec-849"></a>> **Source:** `docs/x-posts/nvidia-forum-audio2face-x-post.md` · [↑ table of contents](#table-of-contents)@@ -196610,7 +197765,7 @@ media; X rewards a clip of a face moving far more than a link card.----<a id="sec-836"></a>+<a id="sec-850"></a>> **Source:** `docs/x-posts/onchain-agent-wallets-x-post.md` · [↑ table of contents](#table-of-contents)@@ -196796,7 +197951,7 @@ Post 1 is the main post above. Then:----<a id="sec-837"></a>+<a id="sec-851"></a>> **Source:** `docs/x-posts/open-source-ecosystem.md` · [↑ table of contents](#table-of-contents)@@ -196843,7 +197998,7 @@ Attach: marketing/open-source-ecosystem/images/header-x-article.png, then the ar----<a id="sec-838"></a>+<a id="sec-852"></a>> **Source:** `docs/x-posts/open-weight-3d-forge-thread.md` · [↑ table of contents](#table-of-contents)@@ -196853,7 +198008,7 @@ A thread for **@trythreews** on how the three.ws Forge runs open-weight text-to-models in production: the reference picture that comes before the mesh, the lane router, failoverwhen a GPU worker dies mid-job, cold starts and weight staging, the meshopt decode, and theper-generation ledger. It is the short companion to the AWS Builder Center article-[aws-builder-center-open-weight-3d-forge.md](#sec-160), and it+[aws-builder-center-open-weight-3d-forge.md](#sec-161), and itstands on its own for a reader who never opens that article.**Thesis of this thread:** a 3D model that fails halfway through should not be the user's problem,@@ -197013,7 +198168,7 @@ the last post.## Reply to append once the AWS article is live-Hold this until the article in [aws-builder-center-open-weight-3d-forge.md](#sec-160)+Hold this until the article in [aws-builder-center-open-weight-3d-forge.md](#sec-161)is published on the AWS Builder Center. Whoever publishes it pastes the article's canonical BuilderCenter URL, exactly as the Builder Center serves it, at the end of the line below, after the colonand a space, and posts it as a reply to post 11. With the URL it is 186 weighted characters.@@ -197047,7 +198202,7 @@ fragments, which reads as broken. It is reported as a finding, not shown.----<a id="sec-839"></a>+<a id="sec-853"></a>> **Source:** `docs/x-posts/oracle-trading-mcp-x-post.md` · [↑ table of contents](#table-of-contents)@@ -197058,7 +198213,7 @@ trading agents are published as Model Context Protocol servers in[Anthropic's official MCP registry](https://registry.modelcontextprotocol.io/?q=io.github.nirholas),so any AI assistant can use them directly.-Build plan this announces: [`docs/oracle-trading-mcp-plan.md`](#sec-466).+Build plan this announces: [`docs/oracle-trading-mcp-plan.md`](#sec-471).**Do not post until:** `npm run smoke:mcp` passes against the live remotes, and both`io.github.nirholas/threews-oracle` and `io.github.nirholas/threews-agent-trader` resolve in the@@ -197188,7 +198343,7 @@ place to be wrong.----<a id="sec-840"></a>+<a id="sec-854"></a>> **Source:** `docs/x-posts/osf-issue-reply.md` · [↑ table of contents](#table-of-contents)@@ -197236,11 +198391,11 @@ Measured: 231 characters with the URL counted at 23.## After it is posted-Nothing. The next move is theirs: on approval they apply the `approved` label and a bot comments on #254 with the booking link. Book a Friday at least two weeks out (2026-09-11 is the first realistic one), then follow the stream runsheet in [../open-source-friday-plan.md](#sec-461).+Nothing. The next move is theirs: on approval they apply the `approved` label and a bot comments on #254 with the booking link. Book a Friday at least two weeks out (2026-09-11 is the first realistic one), then follow the stream runsheet in [../open-source-friday-plan.md](#sec-466).----<a id="sec-841"></a>+<a id="sec-855"></a>> **Source:** `docs/x-posts/proof-of-life-x-post.md` · [↑ table of contents](#table-of-contents)@@ -197248,7 +198403,7 @@ Nothing. The next move is theirs: on approval they apply the `approved` label an**Why this exists.** On 2026-08-28 holders started selling $THREE on the theory that thefounder's suspended personal account means the team is gone. The answer is not a statement-about the suspension: [`x-account-appeal.md`](#sec-806) rules out posting about+about the suspension: [`x-account-appeal.md`](#sec-819) rules out posting aboutit from `@trythreews` while the appeal is open, because a brand-account post linking the twohandles is exactly what X's ban-evasion clause reaches for. The answer is evidence that theteam is shipping, from the platform account, in the platform's voice, with links anyone can@@ -197366,7 +198521,7 @@ Pin this in @three_ws alongside the shipping post.----<a id="sec-842"></a>+<a id="sec-856"></a>> **Source:** `docs/x-posts/pumpfun-article-x-post.md` · [↑ table of contents](#table-of-contents)@@ -197483,7 +198638,7 @@ Pick one option. Do not post all four.----<a id="sec-843"></a>+<a id="sec-857"></a>> **Source:** `docs/x-posts/sperax-staking-in-chat-x-post.md` · [↑ table of contents](#table-of-contents)@@ -197589,7 +198744,7 @@ on the `/staking` page footer, so anyone who tries it gets exactly what the post----<a id="sec-844"></a>+<a id="sec-858"></a>> **Source:** `docs/x-posts/the-first-19-weeks.md` · [↑ table of contents](#table-of-contents)@@ -197650,14 +198805,14 @@ The First 19 Weeks is out: the whole story of three.ws since the first commit, 9----<a id="sec-845"></a>+<a id="sec-859"></a>> **Source:** `docs/x-posts/threews-avatar-launch.md` · [↑ table of contents](#table-of-contents)# Give your AI a body: the avatar filmX copy for the platform film. The shot prompts that produce the video live in-[threews-avatar-video-script.md](#sec-846).+[threews-avatar-video-script.md](#sec-860).**Thesis:** the tagline, literally. A model with no form gets one, the form moves, the form holdsits own wallet, the form walks out into the real world. Nothing about supply, price, or buybacks.@@ -197807,7 +198962,7 @@ Carries the part that does not fit the main post without spending its outbound l----<a id="sec-846"></a>+<a id="sec-860"></a>> **Source:** `docs/x-posts/threews-avatar-video-script.md` · [↑ table of contents](#table-of-contents)@@ -197815,9 +198970,9 @@ Carries the part that does not fit the main post without spending its outbound lPrompts for a video model (Veo, run through ElevenLabs), using a three.ws 3D avatar render as thereference image. This file is the **picture**, not the words. The X copy it ships with is in-[threews-avatar-launch.md](#sec-845), the spoken lines live in-[metaplex-agent-deployer-video-script.md](#sec-829), and the-deployer-specific shot list lives in [metaplex-agent-mcp-x-post.md](#sec-833).+[threews-avatar-launch.md](#sec-859), the spoken lines live in+[metaplex-agent-deployer-video-script.md](#sec-843), and the+deployer-specific shot list lives in [metaplex-agent-mcp-x-post.md](#sec-847).The idea being sold here is the tagline and nothing else: **give your AI a body.** A model with noform gets one, the form moves, the form owns a wallet, the form walks out into the real world. Four@@ -197960,14 +199115,14 @@ Keep the pause after "It has no body." That silence is the whole premise.----<a id="sec-847"></a>+<a id="sec-861"></a>> **Source:** `docs/x-posts/universal-retargeting-thread.md` · [↑ table of contents](#table-of-contents)# X thread: one clip library, any humanoid skeletonThread copy for `@trythreews`, the companion to the AWS Builder Center draft-[`aws-builder-center-universal-retargeting.md`](#sec-161).+[`aws-builder-center-universal-retargeting.md`](#sec-162).It explains how three.ws plays one pre-baked animation library on humanoid avatars from manydifferent exporters, in the browser, with no list of approved rigs, and it leads with the newest fixin that path: A-pose avatars no longer swing their arms through their own torso.@@ -197986,7 +199141,7 @@ git merge-base --is-ancestor 8561d5c5d \&& echo deployed```-Posting is owner-gated like everything in this folder (see [README](#sec-819)).+Posting is owner-gated like everything in this folder (see [README](#sec-833)).## Verified claims@@ -198176,7 +199331,7 @@ panel rendered empty in our headless run, so it is not shown.----<a id="sec-848"></a>+<a id="sec-862"></a>> **Source:** `docs/x-posts/x-meetup-posts.md` · [↑ table of contents](#table-of-contents)@@ -198233,20 +199388,53 @@ https://community.ibm.com/community/user/discussion/community-meetup-inside-thre----<a id="sec-849"></a>+<a id="sec-863"></a>++> **Source:** `docs/x-reply-playbook.md` · [↑ table of contents](#table-of-contents)++# Answering basic questions in depth on X++A basic question under one of our posts ("how do you render 3D?") is an invitation to show the whole process. The reply is a long thread with real visuals, and the same material becomes an X Article. This is the repeatable recipe.++## The shape++1. **Reply thread, answer first.** Post 1 answers the question in one plain sentence, with the strongest image. Each later post covers one stage, carries one real screenshot or reel frame, and names the file or page that does the work. The final post links the Article.+2. **Article, everything.** Stages in order, the code a reader can run, tables, the free tools, the partners section, how changes ship, and what is next. Model: [how-we-render-3d-article](../data/x-content/articles/how-we-render-3d-article.md).+3. **Evidence.** Every number and name in the copy is a `claims` entry pointing at a file, page or proof. A fact with no source does not go in.++## Rules that never change++- Positive framing. The field is described by category, competitors are never named or compared unfavourably.+- Partners are listed with the exact designation each program grants.+- Only what the repo records goes under "What is next".+- No payments or wallet content, no tags in an Article body, no em-dashes.+- Publishing and replying are owner-gated. The queue item stays `draft` until the owner approves.++## Steps++1. Read the question and open the relevant pages and source files. Capture screenshots from production or a local dev server (`npm run dev`) with Playwright into `public/x-media/<id>/`, each with alt text.+2. Write the Article body in `data/x-content/articles/<id>.md` (title 80 to 100 characters, 2,400+ words, 8+ sections, 3,000+ characters of code and tables, 4+ images, a "The partners behind ..." section, a "Try it" section).+3. Write `data/x-content/stories/<id>.json` with kind `article`, the cover, a quote post of 150 to 400 characters, probes and claims.+4. Validate with `validateItem` from `api/_lib/x-content/queue.js` until it returns no problems (see [x-story-authoring.md](#sec-865)).+5. Draft the reply thread from the Article's stage headings, one image per post.+6. Hand to the owner for approval, then publish through the pipeline ([x-content-pipeline.md](#sec-825)).++---++<a id="sec-864"></a>> **Source:** `docs/x-story-author-brief.md` · [↑ table of contents](#table-of-contents)# The brief handed to a story authorAn author is given one product area and this page. Everything else they need is in-[Writing a story](#sec-850) and [the voice contract](#sec-102). Several+[Writing a story](#sec-865) and [the voice contract](#sec-102). Severalauthors work at once, each in their own files, and an integrator adopts and reviews what theyfinish, so the boundaries below are what keep ten authors from overwriting each other.## Read these first, fully-1. [docs/x-story-authoring.md](#sec-850): how to write and film a story.+1. [docs/x-story-authoring.md](#sec-865): how to write and film a story.2. [docs/announce-voice.md](#sec-102): the contract the AI editor holds every post to.3. `data/x-content/queue.json`: the item `wardrobe` is the worked example of a post's format(reel, head, replies) that passed review with a 5 on every dimension. Read the text of every@@ -198367,7 +199555,7 @@ looked at and not written: why, specifically. A broken feature found is as valua----<a id="sec-850"></a>+<a id="sec-865"></a>> **Source:** `docs/x-story-authoring.md` · [↑ table of contents](#table-of-contents)@@ -198379,7 +199567,7 @@ between a post people save and a post people scroll past.Read [the voice contract](#sec-102) first. It is short, and the AI editor holds everypost to it. For how the queue schedules, reviews and publishes, see-[the pipeline doc](#sec-812).+[the pipeline doc](#sec-825).---@@ -198637,13 +199825,13 @@ item under review.----<a id="sec-851"></a>+<a id="sec-866"></a>> **Source:** `docs/x402-buyer.md` · [↑ table of contents](#table-of-contents)# x402 Buyer Client-To consume a paid [x402 endpoint](#sec-854) — ours or anyone's — a+To consume a paid [x402 endpoint](#sec-869) — ours or anyone's — acaller has to perform the "402 dance": probe the URL, read the payment challenge,sign and settle a payment, then retry with an `X-PAYMENT` header. three.ws ships abuyer client that wraps that whole sequence in one call, with spending-cap@@ -198710,7 +199898,7 @@ it fails — caps hold even across concurrent calls. The store is Redis-backed wavailable. If a call would exceed any window, `buyerFetch` returns`{ ok: false, abort: true, reason }` **without paying**. The platform-wide ceilingdefaults live in env (`X402_MAX_PER_CALL_ATOMIC`, `X402_MAX_PER_HOUR_ATOMIC`,-`X402_MAX_PER_DAY_ATOMIC`; see [Configuration](#sec-212)).+`X402_MAX_PER_DAY_ATOMIC`; see [Configuration](#sec-213)).## Axios variant@@ -198746,19 +199934,19 @@ that status means the work is yours and the transfer is still confirming. Do notpay again: the authorization is single-use and already spent.Full behavior on both sides of the wire, including what our own facilitator-guarantees: [Pending settlement](#sec-858).+guarantees: [Pending settlement](#sec-873).## Related-- [x402 protocol](#sec-862) — the underlying challenge/settle mechanics.-- [x402 paid endpoints](#sec-854) — what you can buy from us.-- [Autonomous x402 loop](#sec-140) — uses this client on a schedule.-- [Pending settlement](#sec-858): the `settlement_pending`+- [x402 protocol](#sec-877) — the underlying challenge/settle mechanics.+- [x402 paid endpoints](#sec-869) — what you can buy from us.+- [Autonomous x402 loop](#sec-141) — uses this client on a schedule.+- [Pending settlement](#sec-873): the `settlement_pending`outcome, what a buyer does with it, and how the books close afterwards.----<a id="sec-852"></a>+<a id="sec-867"></a>> **Source:** `docs/x402-dev-tools.md` · [↑ table of contents](#table-of-contents)@@ -199018,13 +200206,13 @@ live 402 carries the v2 `{ info, schema }` entry either way.----<a id="sec-853"></a>+<a id="sec-868"></a>> **Source:** `docs/x402-distribution.md` · [↑ table of contents](#table-of-contents)# x402 Distribution — getting listed and ranked everywhere-three.ws sells 90+ pay-per-call services over [x402](#sec-862). Building them is+three.ws sells 90+ pay-per-call services over [x402](#sec-877). Building them ishalf the job; the other half is making sure every x402 directory, crawler, andagent marketplace can find them — and ranks us at the top. This page is theoperating playbook for that distribution: how each surface indexes providers,@@ -199059,7 +200247,7 @@ distribution channel. See the Solana-first rule in `CLAUDE.md`.Every major surface ranks the same way: **settled transaction count anddistinct buyers in the trailing 30 days**. Metadata quality gets us *found*(semantic search embeds our `description` fields); paid traffic gets us-*ranked*. The [autonomous x402 loop](#sec-140) already drives real+*ranked*. The [autonomous x402 loop](#sec-141) already drives realsettled canary purchases against every `autobuy: true` entry in[`api/_lib/x402/ring-catalog.js`](../api/_lib/x402/ring-catalog.js) — that loopis also our 30-day-activity keeper: the CDP Bazaar **drops resources from@@ -199276,25 +200464,25 @@ script. Everything else above updates itself.## Related-- [x402 overview](#sec-862) · [Paid endpoints reference](#sec-854) ·- [Autonomous loop](#sec-140) · [Buyer client](#sec-851)+- [x402 overview](#sec-877) · [Paid endpoints reference](#sec-869) ·+ [Autonomous loop](#sec-141) · [Buyer client](#sec-866)----<a id="sec-854"></a>+<a id="sec-869"></a>> **Source:** `docs/x402-endpoints.md` · [↑ table of contents](#table-of-contents)# x402 Paid Endpointsthree.ws exposes a catalog of HTTP endpoints that charge per call over-[x402](#sec-862): the caller hits the endpoint, receives a `402 Payment Required`+[x402](#sec-877): the caller hits the endpoint, receives a `402 Payment Required`challenge, settles a small USDC payment, and retries with an `X-PAYMENT` header toget the result. This page is the reference for **our own** paid endpoints, theirprices, and the price-override scheme.-To call these as a buyer, see [x402 buyer client](#sec-851). For the loop-that calls many of them on a schedule, see [Autonomous x402 loop](#sec-140).+To call these as a buyer, see [x402 buyer client](#sec-866). For the loop+that calls many of them on a schedule, see [Autonomous x402 loop](#sec-141).> Source: handlers under [`api/x402/`](../api/x402), pricing> [`api/_lib/x402-prices.js`](../api/_lib/x402-prices.js), shared handler@@ -199330,7 +200518,7 @@ buyer can actually pay in either. `paidEndpoint` lists networks Solana first, thBase; a handler passes `networks` only to narrow that set, and`tests/x402-solana-first-ordering.test.js` fails any handler that pins a non-Solananetwork first. The relevant config (see-[Configuration](#sec-212)):+[Configuration](#sec-213)):| Key | Meaning || ---------------------------------------------------- | ------------------------------------ |@@ -199428,7 +200616,7 @@ deliberately not advertised in the 402 challenge or the discovery catalog; itrecirculates funds back to `X402_PAY_TO_SOLANA` to keep the closed loop balanced([ring-settle.js:18](../api/x402/ring-settle.js#L18)). The full wallet-by-walletpicture — every receiver, tip, split, treasury, and fee rate — is in the-[money map](#sec-435).+[money map](#sec-439).## Intel & oracle endpoints@@ -199508,7 +200696,7 @@ datapoints at **$0.0005** USDC each by default, overridable per family with| Endpoint | Default | Returns || ----------------------------------- | --------- | ------------------------------------------ |-| `/api/x402/agent-reputation` | $0.01 | Cross-chain 0–100 trust score for any wallet/mint/agent id ([trust primitives](#sec-700)). |+| `/api/x402/agent-reputation` | $0.01 | Cross-chain 0–100 trust score for any wallet/mint/agent id ([trust primitives](#sec-708)). || `/api/x402/agent-bouncer` | $0.01 | Access-gate decision for an agent/wallet. || `/api/x402/onchain-identity-verify` | $0.005 | Verifies an on-chain identity claim. || `/api/x402/skill-marketplace` | $0.001 | Skill listings + pricing. |@@ -199520,8 +200708,8 @@ datapoints at **$0.0005** USDC each by default, overridable per family with| Endpoint | Default | Returns || ----------------------------------------------------------- | --------- | -------------------------------------------------------------------------------------------- |-| `/api/x402/forge` | tiered | Text/image → 3D model (price by tier; GPU-bound). Every settled generation also lands in the public community gallery (`forge_creations`) stamped with the payer, settle signature, and price; the gallery shows a Solscan-linked "x402" provenance badge. See [Avatar pipeline](#sec-148). |-| `/api/x402/embody` | $1.00 | **Embodiment.** One call, an agent buys itself a body: prompt or image in → rigged, voiced 3D avatar out, plus a durable persona id and a one-tag `<iframe>` embed for any website. Settles on delivery — a failed generation never charges. See [Embodiment](#sec-260). |+| `/api/x402/forge` | tiered | Text/image → 3D model (price by tier; GPU-bound). Every settled generation also lands in the public community gallery (`forge_creations`) stamped with the payer, settle signature, and price; the gallery shows a Solscan-linked "x402" provenance badge. See [Avatar pipeline](#sec-149). |+| `/api/x402/embody` | $1.00 | **Embodiment.** One call, an agent buys itself a body: prompt or image in → rigged, voiced 3D avatar out, plus a durable persona id and a one-tag `<iframe>` embed for any website. Settles on delivery — a failed generation never charges. See [Embodiment](#sec-263). || `/api/x402/pipeline` | per stage | **One call, full 3D asset pipeline**: text or GLB in, rigged/optimized game-ready GLB out. Ordered chain of `generate → rig → remesh → gameready → stylize`; the 402 quote is the exact sum of the requested stages. Poll free at `/api/forge?job=<id>` for per-stage progress. A bare POST with no body (how listing validators probe a paid row) gets the 402 priced at the catalog's example chain; the body validation error is raised only for a caller that pays. See [3D pipeline](#sec-003). || `/api/x402/pipeline-rig` | $0.05 | **Pipeline — Rig.** Static GLB in → animation-ready rigged GLB out (skeleton + skin weights). One paid call, durable URL. See [3D pipeline](#sec-003). || `/api/x402/pipeline-remesh` | $0.03 | **Pipeline — Remesh.** Retopologize a GLB (triangle/quad/lowpoly, repair, decimate to a face budget) with texture re-baked. GLB in → GLB out. See [3D pipeline](#sec-003). |@@ -199537,8 +200725,8 @@ datapoints at **$0.0005** USDC each by default, overridable per family with| Endpoint | Default | Returns || ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------- | --------------------------------------------------------------------------------------------------------------------------- |-| [`/api/x402/pump-launch`](#sec-561) | $5.00 | **Pump Launcher** — deploy a brand-new pump.fun token in one paid call. No SOL, no wallet, no account: the server fronts the deploy cost and signs the create tx; you pay USDC. Optional vanity mint. Full flow + funnel in [pump-launcher.md](#sec-561). |-| [`/api/x402/vanity`](#sec-791) | $0.01–$0.50 (≤3) · $2.50–$10 (4–5, inventory-only) | **Vanity Grinder** — get a brand-new Solana address that starts with your ticker/prefix and/or ends with a suffix, for a branded token mint or agent/treasury wallet. Checks the pre-ground warehouse first for **instant delivery** (`source: "inventory"`); falls back to a live grind (`source: "ground"`) up to 3 chars. Keypair or importable BIP-39 mnemonic; nothing stored; optional `sealTo` ECIES. Full doc: [vanity.md](#sec-791). |+| [`/api/x402/pump-launch`](#sec-568) | $5.00 | **Pump Launcher** — deploy a brand-new pump.fun token in one paid call. No SOL, no wallet, no account: the server fronts the deploy cost and signs the create tx; you pay USDC. Optional vanity mint. Full flow + funnel in [pump-launcher.md](#sec-568). |+| [`/api/x402/vanity`](#sec-800) | $0.01–$0.50 (≤3) · $2.50–$10 (4–5, inventory-only) | **Vanity Grinder** — get a brand-new Solana address that starts with your ticker/prefix and/or ends with a suffix, for a branded token mint or agent/treasury wallet. Checks the pre-ground warehouse first for **instant delivery** (`source: "inventory"`); falls back to a live grind (`source: "ground"`) up to 3 chars. Keypair or importable BIP-39 mnemonic; nothing stored; optional `sealTo` ECIES. Full doc: [vanity.md](#sec-800). || [`/api/x402/vanity-verifiable`](vanity.md#tier-2--provably-fair-grinder) | $0.02–$0.40 | **Provably-fair grinder** — same grind with a signed commit–reveal receipt proving the key was ground fresh and never kept. Spec: [PROTOCOL-vanity.md](#sec-006). || [`/api/x402/vanity-premium`](vanity.md#tier-3--premium-inventory) | $1–$50 by rarity | **Premium inventory** — buy a pre-ground 4–5+ char brandable address from stock. GET lists available patterns + prices (free); `?address=…` buys via x402 and delivers the key **once** (ciphertext destroyed on delivery). Browsable at `/vanity/premium`. || `/api/x402/pay-by-name` | $0.001 | Resolve and pay a `@username` / `.sol` name / raw address (see [Agent wallets](#sec-077)); the paid resolve toll is $0.001, the transfer amount itself is buyer-specified. A name that resolves to nothing returns `404 not_found` and the payment is left unsettled, so an unresolvable name is free. A body-less POST lands on this paid resolve lane and gets the 402 challenge (the free prep flow must say `mode: "prep"` or carry its wallet/amount fields). `mode: "send"` signs from the caller's agent wallet and needs a session or a bearer token holding the `wallet:write` scope; any other bearer gets `403 insufficient_scope`. |@@ -199589,10 +200777,10 @@ directory.| `/api/x402/network-cost` | free | Cross-chain payment-cost recommendation feed from the hourly cross-chain-cost pipeline snapshots. || `/api/x402/runway-lab` | free | Live seed for [/economy-lab](https://three.ws/economy-lab): the fee wallet's real SOL balance and hard floor, the running deploy's governor config, today's spend from `x402_self_facilitator_log`, observed fee-per-settle and 24h demand, and the refusal histogram bucketed by cause (governor / floor / dust guard / duplicate). Read-only; every field is already public through `/api/x402-ring` and `/api/x402-status`. || `/api/x402/preflight` | free | Signed proof this seller can settle right now: measured settle rate, window and sample from the same sensor healthz reads, the live sponsor floor state, and the configured networks (optionally one route's price). Also served at `/.well-known/x402-preflight`. Wire contract: [specs/x402-preflight.md](../specs/x402-preflight.md); client: `packages/x402-preflight`. |-| `/api/x402/echo` | free | httpbin for x402 — decodes your `X-PAYMENT` header (signatures redacted) and returns a local verify verdict without settling. See [x402 dev tools](#sec-852). |-| `/api/x402/debug` | free | Diagnoses a failed 402 exchange (`{challenge, payment, response}`) into an ordered `{severity, field, problem, fix}` list. See [x402 dev tools](#sec-852). |-| `/api/x402/verify-receipt` | free | Recomputes a paid response's SHA-256 attestation and confirms a settlement tx on-chain. See [x402 dev tools](#sec-852). |-| `/api/x402/inference-verify` | free | Audits a metered-inference receipt from a paid `llm-proxy` call: per-check verdicts for the issuer signature, the node's response signature, prompt/response hash re-derivation from raw text, on-chain settlement confirmation, and whether the issuer matches the platform's published signers. See [Run an inference node](#sec-382). |+| `/api/x402/echo` | free | httpbin for x402 — decodes your `X-PAYMENT` header (signatures redacted) and returns a local verify verdict without settling. See [x402 dev tools](#sec-867). |+| `/api/x402/debug` | free | Diagnoses a failed 402 exchange (`{challenge, payment, response}`) into an ordered `{severity, field, problem, fix}` list. See [x402 dev tools](#sec-867). |+| `/api/x402/verify-receipt` | free | Recomputes a paid response's SHA-256 attestation and confirms a settlement tx on-chain. See [x402 dev tools](#sec-867). |+| `/api/x402/inference-verify` | free | Audits a metered-inference receipt from a paid `llm-proxy` call: per-check verdicts for the issuer signature, the node's response signature, prompt/response hash re-derivation from raw text, on-chain settlement confirmation, and whether the issuer matches the platform's published signers. See [Run an inference node](#sec-386). |## $THREE only@@ -199603,16 +200791,16 @@ input and do not promote any specific token.## Related-- [Pump Launcher](#sec-561) — the full launch flow, inputs/outputs, and the free `symbol` → launch → `launches` funnel.-- [x402 protocol](#sec-862) — the challenge/settle mechanics.-- [x402 buyer client](#sec-851) — how to pay these endpoints in code.-- [Financial controls](#sec-306): where settled payments are recorded.-- [Autonomous x402 loop](#sec-140) — the scheduled buyer that drives volume through these endpoints.-- [MCP tools](#sec-415) — the same capabilities exposed as paid MCP tools.+- [Pump Launcher](#sec-568) — the full launch flow, inputs/outputs, and the free `symbol` → launch → `launches` funnel.+- [x402 protocol](#sec-877) — the challenge/settle mechanics.+- [x402 buyer client](#sec-866) — how to pay these endpoints in code.+- [Financial controls](#sec-309): where settled payments are recorded.+- [Autonomous x402 loop](#sec-141) — the scheduled buyer that drives volume through these endpoints.+- [MCP tools](#sec-419) — the same capabilities exposed as paid MCP tools.----<a id="sec-855"></a>+<a id="sec-870"></a>> **Source:** `docs/x402-fresh-workers.md` · [↑ table of contents](#table-of-contents)@@ -199816,16 +201004,16 @@ in code for a tick that runs first).## Related-- [x402 ring economy](#sec-857): the closed loop this lane+- [x402 ring economy](#sec-872): the closed loop this laneruns inside, its governors, and the payer pool it complements-- [Autonomous x402](#sec-140): the catalog sweeper and the+- [Autonomous x402](#sec-141): the catalog sweeper and thehourly forge pipeline whose sink this lane shares- [Economy wallet rotation](ops/economy-wallet-rotation.md): the funders- [STRUCTURE.md](../STRUCTURE.md): surface map----<a id="sec-856"></a>+<a id="sec-871"></a>> **Source:** `docs/x402-preflight.md` · [↑ table of contents](#table-of-contents)@@ -200024,13 +201212,13 @@ lines.## Related-- [docs/x402.md](#sec-862) walks the payment flow itself.-- [docs/mcp.md](#sec-417) covers connecting an agent to the three.ws MCP server.+- [docs/x402.md](#sec-877) walks the payment flow itself.+- [docs/mcp.md](#sec-421) covers connecting an agent to the three.ws MCP server.- [specs/x402-preflight.md](../specs/x402-preflight.md) is the wire contract.----<a id="sec-857"></a>+<a id="sec-872"></a>> **Source:** `docs/x402-ring-economy.md` · [↑ table of contents](#table-of-contents)@@ -200626,7 +201814,7 @@ loosened: the pending state only changes *when* the claim happens, never how mantimes.Full behavior, on both sides of the wire:-[Pending settlement](#sec-858).+[Pending settlement](#sec-873).## Reconciliation — proving every ring dollar on-chain@@ -201315,13 +202503,13 @@ activation runbook above is the fix.controlled-wallet set + spend invariants- [api/cron/x402-ring-leak-scan.js](../api/cron/x402-ring-leak-scan.js) — theon-chain leak scanner-- [Fresh-wallet workers](#sec-855): the lane that runs beside+- [Fresh-wallet workers](#sec-870): the lane that runs besidethe ring, paying from a brand-new wallet per job and buying real work (3Dprops for /forged, datasets for /data-desk) instead of canaries----<a id="sec-858"></a>+<a id="sec-873"></a>> **Source:** `docs/x402-settlement-pending.md` · [↑ table of contents](#table-of-contents)@@ -201516,17 +202704,17 @@ it makes our report of it true.## Related-- [Closed-loop x402 ring economy](#sec-857): the self-hosted+- [Closed-loop x402 ring economy](#sec-872): the self-hostedfacilitator, the SOL runway governors, and the one-signature-one-payment gatethe reconcile pass claims credit through-- [x402 buyer guide](#sec-851): paying our endpoints from your own agent-- [x402 developer tools](#sec-852): free bench for debugging a 402+- [x402 buyer guide](#sec-866): paying our endpoints from your own agent+- [x402 developer tools](#sec-867): free bench for debugging a 402exchange, including a failed settle-- [x402 paid endpoints](#sec-854): the catalog of what you can pay for+- [x402 paid endpoints](#sec-869): the catalog of what you can pay for----<a id="sec-859"></a>+<a id="sec-874"></a>> **Source:** `docs/x402-solana-july-roundup-response.md` · [↑ table of contents](#table-of-contents)@@ -201544,7 +202732,7 @@ exact permalink from the account's profile before posting; quote-tweet directlyrather than typing a URL by hand.Two accounts, two jobs, same split used for the IBM Community campaign in-[event-x-posts.md](#sec-823): `@trythreews` posts the institutional version, `@nichxbt`+[event-x-posts.md](#sec-837): `@trythreews` posts the institutional version, `@nichxbt`posts the human one. Do not post both within a few minutes of each other.---@@ -201585,7 +202773,7 @@ the specific claim the roundup credited us for. Second choice: the AR drop-in on----<a id="sec-860"></a>+<a id="sec-875"></a>> **Source:** `docs/x402-studio.md` · [↑ table of contents](#table-of-contents)@@ -201595,11 +202783,11 @@ x402 Studio is the merchant console for running a paid x402 business on three.wsPage: [/x402/studio](https://three.ws/x402/studio)-APIs: `/api/x402-merchant` (settings), `/api/x402-skus` (products), `/api/sns` (name resolution), `/api/x402/pay-by-name` (USDC send). See [x402: paid agent skills](#sec-862) for the underlying payment protocol.+APIs: `/api/x402-merchant` (settings), `/api/x402-skus` (products), `/api/sns` (name resolution), `/api/x402/pay-by-name` (USDC send). See [x402: paid agent skills](#sec-877) for the underlying payment protocol.## Why it exists-x402 turns any HTTP endpoint into a paid one: the server answers `402 Payment Required` with a manifest, the caller pays in USDC, and the call retries and settles. That primitive is powerful but low-level. Studio is the console on top of it, the difference between "you can hand-write a 402 challenge" and "you can run a storefront." A merchant configures once and gets hosted checkout links, a shareable storefront, a copy-paste pay button, revenue stats, and payouts to a wallet they control, without writing payment code. It is the seller-facing companion to the [x402 buyer client](#sec-851) and the [paid endpoint catalog](#sec-854).+x402 turns any HTTP endpoint into a paid one: the server answers `402 Payment Required` with a manifest, the caller pays in USDC, and the call retries and settles. That primitive is powerful but low-level. Studio is the console on top of it, the difference between "you can hand-write a 402 challenge" and "you can run a storefront." A merchant configures once and gets hosted checkout links, a shareable storefront, a copy-paste pay button, revenue stats, and payouts to a wallet they control, without writing payment code. It is the seller-facing companion to the [x402 buyer client](#sec-866) and the [paid endpoint catalog](#sec-869).## How it works@@ -201685,16 +202873,16 @@ const { tx_base64, blockhash } = await res.json();## Related-- [x402: paid agent skills](#sec-862): the payment protocol Studio sits on top of-- [Financial controls](#sec-306): where settled payments are recorded-- [x402 paid endpoints](#sec-854): the platform's own catalog of paid endpoints-- [x402 buyer client](#sec-851): the caller side of a 402 challenge-- [x402 developer tools](#sec-852) and [x402 distribution](#sec-853)+- [x402: paid agent skills](#sec-877): the payment protocol Studio sits on top of+- [Financial controls](#sec-309): where settled payments are recorded+- [x402 paid endpoints](#sec-869): the platform's own catalog of paid endpoints+- [x402 buyer client](#sec-866): the caller side of a 402 challenge+- [x402 developer tools](#sec-867) and [x402 distribution](#sec-868)- Pages: [/x402/studio](https://three.ws/x402/studio) · [/x402](https://three.ws/x402)----<a id="sec-861"></a>+<a id="sec-876"></a>> **Source:** `docs/x402-vscode.md` · [↑ table of contents](#table-of-contents)@@ -201800,14 +202988,14 @@ to put $THREE first.## Related-- [x402 protocol on three.ws](#sec-862)-- [x402 paid endpoints](#sec-854)-- [x402 buyer client](#sec-851)-- [three.ws in VS Code](#sec-797)+- [x402 protocol on three.ws](#sec-877)+- [x402 paid endpoints](#sec-869)+- [x402 buyer client](#sec-866)+- [three.ws in VS Code](#sec-809)----<a id="sec-862"></a>+<a id="sec-877"></a>> **Source:** `docs/x402.md` · [↑ table of contents](#table-of-contents)@@ -201821,7 +203009,7 @@ of Pump.fun agent payments: callers pay an agent in any SPL token to invoke askill, and the agent verifies the on-chain payment before dispatching thecall. It is written for developers wiring paid skills (server side) or payingfor them (client side); the platform's own catalog of paid endpoints lives at-[x402 paid endpoints](#sec-854).+[x402 paid endpoints](#sec-869).**Live activity:** [x402scan dashboard](https://www.x402scan.com/server/17cbd874-52ac-4920-a020-b22ff2489a07)— browse paid calls, revenue, and per-skill pricing for this server.@@ -202188,25 +203376,25 @@ The $THREE contract address isthat exact mint. Every $THREE payment shows the token amount, network, payingwallet, and recipient, then requires explicit confirmation before signing.-See [x402 for VS Code](#sec-861) for installation, wallet setup, settings,+See [x402 for VS Code](#sec-876) for installation, wallet setup, settings,and the payment flow.## Tutorials-- [Pay for an x402 service](#sec-744) — settle a paid request end to end with `@three-ws/x402-fetch`.-- [Build a paid x402 endpoint](#sec-743) — stand up a seller endpoint with `@three-ws/x402-server`.+- [Pay for an x402 service](#sec-752) — settle a paid request end to end with `@three-ws/x402-fetch`.+- [Build a paid x402 endpoint](#sec-751) — stand up a seller endpoint with `@three-ws/x402-server`.## Related-- [x402 paid endpoints](#sec-854) — the catalog of the platform's own paid endpoints.-- [Financial controls](#sec-306): where settled payments are recorded.-- [x402 buyer client](#sec-851) — how to settle a 402 challenge in code.-- [x402 bazaar over MCP](#sec-416) — discover and pay endpoints through the MCP bazaar.-- [Autonomous x402](#sec-140) — agents paying for services on their own.+- [x402 paid endpoints](#sec-869) — the catalog of the platform's own paid endpoints.+- [Financial controls](#sec-309): where settled payments are recorded.+- [x402 buyer client](#sec-866) — how to settle a 402 challenge in code.+- [x402 bazaar over MCP](#sec-420) — discover and pay endpoints through the MCP bazaar.+- [Autonomous x402](#sec-141) — agents paying for services on their own.----<a id="sec-863"></a>+<a id="sec-878"></a>> **Source:** `docs/zauth/database.md` · [↑ table of contents](#table-of-contents)@@ -202352,7 +203540,7 @@ Use this endpoint to browse all known x402 endpoints before your agents commit t----<a id="sec-864"></a>+<a id="sec-879"></a>> **Source:** `docs/zauth/index.md` · [↑ table of contents](#table-of-contents)@@ -202372,11 +203560,11 @@ zauth is the security and trust layer that allows agents to act with confidence,## Products-### [VectorAI-powered vulnerability scanner. Automated recon, multi-category exploit testing, and detailed security reports for your web applications.Vector](#sec-867)### [RepoScanAI-powered code analysis for crypto communities. Scan GitHub repos for red flags, get trust scores, and compare code similarity across millions of repositories.RepoScan](#sec-866)### [DatabaseLive registry of x402 endpoints. AI agents continuously test and verify endpoints, tracking success rates, pricing, and response data.Database](#sec-863)### [Provider HubManage your x402 endpoints. Monitor health, track agent interactions, configure refunds, and verify your services through our SDK.Provider Hub](#sec-865)+### [VectorAI-powered vulnerability scanner. Automated recon, multi-category exploit testing, and detailed security reports for your web applications.Vector](#sec-882)### [RepoScanAI-powered code analysis for crypto communities. Scan GitHub repos for red flags, get trust scores, and compare code similarity across millions of repositories.RepoScan](#sec-881)### [DatabaseLive registry of x402 endpoints. AI agents continuously test and verify endpoints, tracking success rates, pricing, and response data.Database](#sec-878)### [Provider HubManage your x402 endpoints. Monitor health, track agent interactions, configure refunds, and verify your services through our SDK.Provider Hub](#sec-880)----<a id="sec-865"></a>+<a id="sec-880"></a>> **Source:** `docs/zauth/provider-hub.md` · [↑ table of contents](#table-of-contents)@@ -202478,7 +203666,7 @@ Supply your EVM or Solana private keys to enable automatic refunds when your end----<a id="sec-866"></a>+<a id="sec-881"></a>> **Source:** `docs/zauth/reposcan.md` · [↑ table of contents](#table-of-contents)@@ -202804,7 +203992,7 @@ TypeScript -@x402/fetch----<a id="sec-867"></a>+<a id="sec-882"></a>> **Source:** `docs/zauth/vector.md` · [↑ table of contents](#table-of-contents)diff --git a/docs/contributing.md b/docs/contributing.mdindex 4bdb94450..1a0caee58 100644--- a/docs/contributing.md+++ b/docs/contributing.md@@ -205,48 +205,33 @@ GitHub token for that account (`GITHUB_TOKEN`, or the PAT on the `origin` remoteA token for a different account authenticates fine and is then rejected for thatnamespace.-**3. Standalone GitHub mirrors** - each package also lives in its own repo at-`github.com/<owner>/<name>` (a read-only mirror; the monorepo stays canonical).-Each sync force-pushes one snapshot commit whose message records the source-monorepo SHA, and rewrites the mirror's `package.json` / `server.json`-`repository` fields to point at the standalone repo:+**3. Standalone GitHub mirrors** - about 80 directories in this monorepo also+live in their own public repo at `github.com/<owner>/<name>` (a read-only+mirror; the monorepo stays canonical). [`data/standalone-mirrors.json`](../data/standalone-mirrors.json)+is the single source of truth for "which directory is which public repo, in+which direction": every exporter (`sync-standalone-repos.mjs`,+`export-growth-satellites.mjs`, `build-awesome.mjs --standalone`,+`build-standalone-skill-repos.mjs`) reads repo names from it instead of+hardcoding its own list. A `direction: "in"` entry (the `robinhood/*` copies)+is a reference copy of an external repo; no exporter pushes those.++`scripts/sync-standalone-repos.mjs` only **stages**; it never pushes and never+calls the GitHub API:```bash-npm run sync:repos:dry # plan only, both lanes-npm run sync:repos # create missing repos + push snapshots (needs gh auth as the owner)-# scope it:-node scripts/sync-standalone-repos.mjs --dry-run --kind lib --new-node scripts/sync-standalone-repos.mjs --execute --only agent-sniper,copy-mcp+npm run sync:repos # stage every manifest "sync" entry under dist/standalone-mirrors/+npm run sync:repos:check # compare staged trees against the live repos; exits non-zero on drift+node scripts/sync-standalone-repos.mjs --only tty-avatar,x402-bridge```-`--kind mcp` / `--kind lib` narrows to one lane, `--new` limits the run to repos-that do not exist yet, and the dry run prints how many repos it would CREATE-before you commit to it. Repo names come from the unscoped npm name, except that-a single-token `@three-ws/*` name mirrors as `three-ws-<name>`: the scope carries-the identity on npm, but `github.com/nirholas/render` says nothing about what it-is or who ships it.--Auth: `gh` must be authenticated as the target owner (default `nirholas`; override-with `--owner`) so it can create and push under that account.--**What every mirror ships.** Besides the package, each sync generates the discovery-layer from `scripts/lib/standalone-enrich.mjs`, so no mirror is a bare code dump:--| Generated file | Audience |-|---|---|-| `AGENTS.md`, `llms.txt`, `llms-full.txt`, `glama.json` (MCP) | AI coding agents and MCP directories |-| `CONTRIBUTING.md`, `SECURITY.md`, `CODE_OF_CONDUCT.md`, `CITATION.cff`, issue forms, PR template | Contributors and security reporters |-| `docs/` (README rendered with OG tags, JSON-LD, sitemap, robots, 404) | Search engines and humans, served by GitHub Pages from `main:/docs` |--It also sets the repository topics (from the package keywords), description,-homepage (`https://<owner>.github.io/<repo>/`), Discussions, Pages and-vulnerability alerts over the API. A file the package already ships is kept, so a-package overrides any generated file by committing its own. `--settings-only`-re-applies the repository settings without pushing. `GH_PAT` authenticates both-`git push` and `gh` when set, and never lands in a remote URL or process args.-A package listed in `HOLD_NEW` keeps syncing if its repo exists, but its first-repo is not created until the owner approves (it is built around another crypto-project).+Each staged mirror is a fresh one-commit git repo whose message records the+source monorepo SHA (`Sync from three.ws@<sha>`), with `package.json`'s+`repository` field rewritten to point at the standalone repo and any stale+"All rights reserved" README footer or LICENSE replaced with the Apache-2.0+text this repo ships today. Nothing else in the snapshot changes: the staged+tree is otherwise byte-for-byte the source directory. `sync:repos` finishes by+printing the exact `git push --force` command per mirror; publishing a mirror+is the owner's call, not this script's.---diff --git a/package.json b/package.jsonindex 3d43b28df..784f8ccd9 100644--- a/package.json+++ b/package.json@@ -375,8 +375,8 @@"publish:queue": "node scripts/publish-npm-queue.mjs --publish","publish:mcp": "node scripts/publish-mcp-servers.mjs","publish:mcp:dry": "node scripts/publish-mcp-servers.mjs --dry-run",- "sync:repos": "node scripts/sync-standalone-repos.mjs --execute",- "sync:repos:dry": "node scripts/sync-standalone-repos.mjs --dry-run",+ "sync:repos": "node scripts/sync-standalone-repos.mjs",+ "sync:repos:check": "node scripts/sync-standalone-repos.mjs --check","build:chat": "cd chat && node scripts/ensure-deps.mjs && npm run build && cd .. && mkdir -p dist/chat && cp -rf public/chat/. dist/chat/","deps:chat": "cd chat && node scripts/ensure-deps.mjs","build:avatar-studio": "npm run build --prefix character-studio",diff --git a/packages/README.md b/packages/README.mdindex 019cbf2f2..852eea301 100644--- a/packages/README.md+++ b/packages/README.md@@ -1,6 +1,6 @@# packages/-Publishable npm packages for the three.ws platform: client SDKs, agent tooling, and a large family of MCP servers under the `@three-ws/*` scope. Several are npm workspaces declared in the root [package.json](../package.json). Publishing is decided by the filesystem, not by a hand-kept list: a directory holding a `server.json` publishes through `npm run publish:mcp` (npm plus the official MCP registry), everything else with a non-private `package.json` through `npm run publish:packages` (both have `--dry-run` variants). `npm run sync:repos` mirrors each one to its own standalone GitHub repo. The full runbook, including the publish preflight, is in [docs/contributing.md](../docs/contributing.md#publishing-packages--standalone-mirrors). Each package's README covers its install, API, and examples.+Publishable npm packages for the three.ws platform: client SDKs, agent tooling, and a large family of MCP servers under the `@three-ws/*` scope. Several are npm workspaces declared in the root [package.json](../package.json). Publishing is decided by the filesystem, not by a hand-kept list: a directory holding a `server.json` publishes through `npm run publish:mcp` (npm plus the official MCP registry), everything else with a non-private `package.json` through `npm run publish:packages` (both have `--dry-run` variants). `npm run sync:repos` stages each one as a standalone GitHub mirror under `dist/standalone-mirrors/` and prints the push command; publishing is the owner's call. [data/standalone-mirrors.json](../data/standalone-mirrors.json) is the source of truth for which directory maps to which repo. The full runbook, including the publish preflight, is in [docs/contributing.md](../docs/contributing.md#publishing-packages--standalone-mirrors). Each package's README covers its install, API, and examples.| Package | Description || --- | --- |diff --git a/public/changelog-recent.json b/public/changelog-recent.jsonindex 4d24cbcc3..53ce55992 100644--- a/public/changelog-recent.json+++ b/public/changelog-recent.json@@ -1,14 +1,25 @@{- "generated_at": "2026-10-13T23:51:19.583Z",+ "generated_at": "2026-10-14T01:31:00.180Z","generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json","site": {"name": "three.ws","url": "https://three.ws"},- "total": 4078,+ "total": 4079,"complete": false,"full_feed": "/changelog.json","entries": [+ {+ "date": "2026-10-14",+ "type": "update",+ "title": "Standalone GitHub mirrors now stage instead of force-pushing",+ "summary": "scripts/sync-standalone-repos.mjs force-pushed straight to main on every run, which could silently create duplicate repos for the eleven mirrors already renamed on GitHub and bypassed the owner's push-approval rule. data/standalone-mirrors.json is now the single source of truth for which monorepo directory maps to which public repo, read by every exporter (sync, growth satellites, the awesome list, the skill-repo builder) instead of each keeping its own list. The sync script only stages a snapshot under dist/standalone-mirrors/, fixes any stale pre-Apache-2.0 README or LICENSE footer, and prints the push command for the owner; npm run sync:repos:check compares what is staged against each mirror's live tree and reports drift without writing anything.",+ "link": "/docs/contributing",+ "tags": [+ "infra",+ "docs"+ ]+ },{"date": "2026-10-13","type": "launch",@@ -1543,16 +1554,6 @@"tags": ["feature"]- },- {- "date": "2026-10-10",- "type": "update",- "title": "Event Markets: pick the winner of any event, free",- "summary": "Every event now has a market where you put free points on who you think wins. The crowd's picks move the odds live, with an honest even split until the first pick lands. Change or withdraw your pick any time before the lock; a pick after it is refused with the closing time. Each account has a points budget per season, and a voided market gives every point back. Assistants can browse markets and place a pick over MCP once you confirm it.",- "link": "/event-markets",- "tags": [- "feature"- ]}]}diff --git a/public/changelog.json b/public/changelog.jsonindex 4ffd1f54a..3ff52fa13 100644--- a/public/changelog.json+++ b/public/changelog.json@@ -1,11 +1,22 @@{- "generated_at": "2026-10-13T23:51:19.561Z",+ "generated_at": "2026-10-14T01:31:00.152Z","generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json","site": {"name": "three.ws","url": "https://three.ws"},"entries": [+ {+ "date": "2026-10-14",+ "type": "update",+ "title": "Standalone GitHub mirrors now stage instead of force-pushing",+ "summary": "scripts/sync-standalone-repos.mjs force-pushed straight to main on every run, which could silently create duplicate repos for the eleven mirrors already renamed on GitHub and bypassed the owner's push-approval rule. data/standalone-mirrors.json is now the single source of truth for which monorepo directory maps to which public repo, read by every exporter (sync, growth satellites, the awesome list, the skill-repo builder) instead of each keeping its own list. The sync script only stages a snapshot under dist/standalone-mirrors/, fixes any stale pre-Apache-2.0 README or LICENSE footer, and prints the push command for the owner; npm run sync:repos:check compares what is staged against each mirror's live tree and reports drift without writing anything.",+ "link": "/docs/contributing",+ "tags": [+ "infra",+ "docs"+ ]+ },{"date": "2026-10-13","type": "launch",diff --git a/public/changelog.xml b/public/changelog.xmlindex b61da0845..d2fb4edf5 100644--- a/public/changelog.xml+++ b/public/changelog.xml@@ -6,6 +6,14 @@<atom:link href="https://three.ws/changelog.xml" rel="self" type="application/rss+xml"/><description>What's new on three.ws: features, improvements, and releases, newest first.</description><language>en</language>+ <item>+ <title>Standalone GitHub mirrors now stage instead of force-pushing</title>+ <link>https://three.ws/docs/contributing</link>+ <guid isPermaLink="false">2026-10-14:Standalone GitHub mirrors now stage instead of force-pushing</guid>+ <pubDate>Wed, 14 Oct 2026 12:00:00 GMT</pubDate>+ <category>infra</category>+ <description>scripts/sync-standalone-repos.mjs force-pushed straight to main on every run, which could silently create duplicate repos for the eleven mirrors already renamed on GitHub and bypassed the owner's push-approval rule. data/standalone-mirrors.json is now the single source of truth for which monorepo directory maps to which public repo, read by every exporter (sync, growth satellites, the awesome list, the skill-repo builder) instead of each keeping its own list. The sync script only stages a snapshot under dist/standalone-mirrors/, fixes any stale pre-Apache-2.0 README or LICENSE footer, and prints the push command for the owner; npm run sync:repos:check compares what is staged against each mirror's live tree and reports drift without writing anything.</description>+ </item><item><title>Docs · Staked Event Markets</title><link>https://three.ws/docs/event-markets-staking</link>diff --git a/public/features.json b/public/features.jsonindex 0629d67dc..b9f381e71 100644--- a/public/features.json+++ b/public/features.json@@ -1,5 +1,5 @@{- "generated_at": "2026-10-13T23:51:19.549Z",+ "generated_at": "2026-10-14T01:31:00.131Z","generated_by": "scripts/build-page-index.mjs from data/pages.json","site": {"name": "three.ws",diff --git a/public/sitemap/index.html b/public/sitemap/index.htmlindex a7e4c8b77..8de69d932 100644--- a/public/sitemap/index.html+++ b/public/sitemap/index.html@@ -3,16 +3,16 @@<head><meta charset="utf-8" /><meta name="viewport" content="width=device-width,initial-scale=1" />-<title data-i18n="sitemap_index.meta_title">Sitemap · three.ws</title>-<meta name="description" content="Human-readable index of every page on three.ws." data-i18n-attr="content:sitemap_index.meta_description"/>+<title>Sitemap · three.ws</title>+<meta name="description" content="Human-readable index of every page on three.ws." /><meta name="robots" content="index, follow, max-image-preview:large, max-snippet:-1" /><link rel="canonical" href="https://three.ws/sitemap" /><meta property="og:type" content="website" /><meta property="og:site_name" content="three.ws" /><meta property="og:locale" content="en_US" /><meta property="og:url" content="https://three.ws/sitemap" />-<meta property="og:title" content="Sitemap · three.ws" data-i18n-attr="content:sitemap_index.meta_og_title"/>-<meta property="og:description" content="Human-readable index of every page on three.ws." data-i18n-attr="content:sitemap_index.meta_og_description"/>+<meta property="og:title" content="Sitemap · three.ws" />+<meta property="og:description" content="Human-readable index of every page on three.ws." /><meta property="og:image" content="https://three.ws/api/page-og?s=main&t=Sitemap&d=Human-readable+index+of+every+page+on+three.ws.&p=%2Fsitemap" /><meta property="og:image:width" content="1200" /><meta property="og:image:height" content="630" />@@ -20,8 +20,8 @@<meta property="og:image:alt" content="Sitemap - three.ws" /><meta name="twitter:card" content="summary_large_image" /><meta name="twitter:site" content="@trythreews" />-<meta name="twitter:title" content="Sitemap · three.ws" data-i18n-attr="content:sitemap_index.meta_twitter_title"/>-<meta name="twitter:description" content="Human-readable index of every page on three.ws." data-i18n-attr="content:sitemap_index.meta_twitter_description"/>+<meta name="twitter:title" content="Sitemap · three.ws" />+<meta name="twitter:description" content="Human-readable index of every page on three.ws." /><meta name="twitter:image" content="https://three.ws/api/page-og?s=main&t=Sitemap&d=Human-readable+index+of+every+page+on+three.ws.&p=%2Fsitemap" /><script type="application/ld+json">{"@context":"https://schema.org","@graph":[{"@type":"WebPage","name":"Sitemap","description":"Human-readable index of every page on three.ws.","url":"https://three.ws/sitemap","isPartOf":{"@type":"WebSite","name":"three.ws","url":"https://three.ws"},"primaryImageOfPage":"https://three.ws/api/page-og?s=main&t=Sitemap&d=Human-readable+index+of+every+page+on+three.ws.&p=%2Fsitemap"}]}</script><link rel="alternate" type="application/xml" title="XML sitemap" href="/sitemap.xml" />@@ -95,16 +95,16 @@<header><div id="nav-container"></div></header><main class="sm-wrap"><div class="sm-hero">- <h1 data-i18n="sitemap_index.sitemap">Sitemap</h1>+ <h1>Sitemap</h1><p><span>1078</span> <span data-i18n="sitemap_index.pages_grouped">pages on three.ws, grouped by purpose. Looking for the machine-readable versions?</span></p><div class="sm-formats">- <a href="/everything" data-i18n-html="sitemap_index.browse_by_goal_not_by_section"><code>/everything</code> · browse by goal, not by section</a>- <a href="/sitemap.xml" data-i18n-html="sitemap_index.for_search_engines"><code>sitemap.xml</code> · for search engines</a>- <a href="/llms.txt" data-i18n-html="sitemap_index.for_ai_agents"><code>llms.txt</code> · for AI agents</a>- <a href="/llms-full.txt" data-i18n-html="sitemap_index.long_form"><code>llms-full.txt</code> · long form</a>- <a href="/api/features.json" data-i18n-html="sitemap_index.machine_manifest"><code>features.json</code> · machine manifest</a>- <a href="/changelog" data-i18n-html="sitemap_index.what_s_new"><code>changelog</code> · what's new</a>- <a href="/openapi.json" data-i18n-html="sitemap_index.http_api"><code>openapi.json</code> · HTTP API</a>+ <a href="/everything"><code>/everything</code> · browse by goal, not by section</a>+ <a href="/sitemap.xml"><code>sitemap.xml</code> · for search engines</a>+ <a href="/llms.txt"><code>llms.txt</code> · for AI agents</a>+ <a href="/llms-full.txt"><code>llms-full.txt</code> · long form</a>+ <a href="/api/features.json"><code>features.json</code> · machine manifest</a>+ <a href="/changelog"><code>changelog</code> · what's new</a>+ <a href="/openapi.json"><code>openapi.json</code> · HTTP API</a></div></div><div class="sm-filter">@@ -114,8 +114,8 @@</div><p class="sm-filter-count" role="status" aria-live="polite"><span id="sm-filter-count"></span><span id="sm-filter-hint" aria-hidden="true"></span></p><section class="sm-new" id="sm-new" aria-labelledby="sm-new-title">- <h2 id="sm-new-title" data-i18n-html="sitemap_index.newestfull_changelog">Newest<a class="sm-new-more" href="/changelog">full changelog →</a></h2>- <p class="sm-section-desc" data-i18n="sitemap_index.the_9_most_recently_launched_pages_straight">The 9 most recently launched pages, straight to the live surface.</p>+ <h2 id="sm-new-title">Newest<a class="sm-new-more" href="/changelog">full changelog →</a></h2>+ <p class="sm-section-desc">The 9 most recently launched pages, straight to the live surface.</p><ul class="sm-list"><li><a href="/video-to-motion">@@ -192,22 +192,22 @@</ul></section><nav class="sm-toc" aria-label="Sections">- <a href="#main" data-i18n="sitemap_index.main">Main</a>- <a href="#build" data-i18n="sitemap_index.build">Build</a>- <a href="#labs" data-i18n="sitemap_index.labs">Labs</a>- <a href="#crypto" data-i18n="sitemap_index.crypto">Crypto</a>- <a href="#agent-tools" data-i18n="sitemap_index.agent_tools">Agent Tools</a>- <a href="#account" data-i18n="sitemap_index.account">Account</a>- <a href="#learn" data-i18n="sitemap_index.learn">Learn</a>- <a href="#blog" data-i18n="sitemap_index.blog">Blog</a>- <a href="#legal" data-i18n="sitemap_index.legal">Legal</a>- <a href="#machine" data-i18n="sitemap_index.machine_readable">Machine-readable</a>- <a href="#news" data-i18n="sitemap_index.news">News</a>+ <a href="#main">Main</a>+ <a href="#build">Build</a>+ <a href="#labs">Labs</a>+ <a href="#crypto">Crypto</a>+ <a href="#agent-tools">Agent Tools</a>+ <a href="#account">Account</a>+ <a href="#learn">Learn</a>+ <a href="#blog">Blog</a>+ <a href="#legal">Legal</a>+ <a href="#machine">Machine-readable</a>+ <a href="#news">News</a></nav><section class="sm-section" id="main"><header><h2><span data-i18n="sitemap_index.section_main">Main</span><span class="sm-count" data-count>75</span></h2>- <p class="sm-section-desc" data-i18n="sitemap_index.entry_points_into_the_product">Entry points into the product.</p>+ <p class="sm-section-desc">Entry points into the product.</p></header><ul class="sm-list"><li>@@ -741,7 +741,7 @@<section class="sm-section" id="build"><header><h2><span data-i18n="sitemap_index.section_build">Build</span><span class="sm-count" data-count>94</span></h2>- <p class="sm-section-desc" data-i18n="sitemap_index.create_and_customize_an_agent">Create and customize an agent.</p>+ <p class="sm-section-desc">Create and customize an agent.</p></header><ul class="sm-list"><li>@@ -1408,7 +1408,7 @@<section class="sm-section" id="labs"><header><h2><span data-i18n="sitemap_index.section_labs">Labs</span><span class="sm-count" data-count>26</span></h2>- <p class="sm-section-desc" data-i18n="sitemap_index.experimental_features_actively_shipping_expe">Experimental features actively shipping. Expect fast iteration.</p>+ <p class="sm-section-desc">Experimental features actively shipping. Expect fast iteration.</p></header><ul class="sm-list"><li>@@ -1599,7 +1599,7 @@<section class="sm-section" id="crypto"><header><h2><span data-i18n="sitemap_index.section_crypto">Crypto</span><span class="sm-count" data-count>170</span></h2>- <p class="sm-section-desc" data-i18n="sitemap_index.on_chain_features_pay_per_call_token">On-chain features: pay-per-call, token launches, vanity wallets.</p>+ <p class="sm-section-desc">On-chain features: pay-per-call, token launches, vanity wallets.</p></header><ul class="sm-list"><li>@@ -2798,7 +2798,7 @@<section class="sm-section" id="agent-tools"><header><h2><span data-i18n="sitemap_index.section_agent-tools">Agent Tools</span><span class="sm-count" data-count>11</span></h2>- <p class="sm-section-desc" data-i18n="sitemap_index.manage_talk_to_and_deploy_individual_agents">Manage, talk to, and deploy individual agents.</p>+ <p class="sm-section-desc">Manage, talk to, and deploy individual agents.</p></header><ul class="sm-list"><li>@@ -2884,7 +2884,7 @@<section class="sm-section" id="account"><header><h2><span data-i18n="sitemap_index.section_account">Account</span><span class="sm-count" data-count>15</span></h2>- <p class="sm-section-desc" data-i18n="sitemap_index.sign_in_dashboard_billing">Sign-in, dashboard, billing.</p>+ <p class="sm-section-desc">Sign-in, dashboard, billing.</p></header><ul class="sm-list"><li>@@ -2998,7 +2998,7 @@<section class="sm-section" id="learn"><header><h2><span data-i18n="sitemap_index.section_learn">Learn</span><span class="sm-count" data-count>509</span></h2>- <p class="sm-section-desc" data-i18n="sitemap_index.docs_tutorials_and_reference">Docs, tutorials, and reference.</p>+ <p class="sm-section-desc">Docs, tutorials, and reference.</p></header><ul class="sm-list"><li>@@ -6570,7 +6570,7 @@<section class="sm-section" id="blog"><header><h2><span data-i18n="sitemap_index.section_blog">Blog</span><span class="sm-count" data-count>39</span></h2>- <p class="sm-section-desc" data-i18n="sitemap_index.long_form_announcements_launches_and_writing">Long-form announcements, launches, and writing from three.ws.</p>+ <p class="sm-section-desc">Long-form announcements, launches, and writing from three.ws.</p></header><ul class="sm-list"><li>@@ -6924,7 +6924,7 @@<section class="sm-section" id="machine"><header><h2><span data-i18n="sitemap_index.section_machine">Machine-readable</span><span class="sm-count" data-count>18</span></h2>- <p class="sm-section-desc" data-i18n="sitemap_index.indexes_and_well_known_files_for_crawlers">Indexes and well-known files for crawlers and AI agents.</p>+ <p class="sm-section-desc">Indexes and well-known files for crawlers and AI agents.</p></header><ul class="sm-list"><li>@@ -7059,7 +7059,7 @@<section class="sm-section" id="news"><header><h2><span data-i18n="sitemap_index.section_news">News</span><span class="sm-count" data-count>112</span></h2>- <p class="sm-section-desc" data-i18n="sitemap_index.product_launches_integrations_and_announceme">Product launches, integrations, and announcements from three.ws.</p>+ <p class="sm-section-desc">Product launches, integrations, and announcements from three.ws.</p></header><ul class="sm-list"><li>@@ -7850,10 +7850,10 @@</section><div class="sm-empty" id="sm-empty" hidden><p><span data-i18n="sitemap_index.no_pages_match">No pages match</span> “<span id="sm-empty-q"></span>”.</p>- <p class="sm-empty-hint" data-i18n="sitemap_index.try_a_shorter_word_or_search_everything">Try a shorter word, or search everything: global search covers agents, coins, and skills too.</p>+ <p class="sm-empty-hint">Try a shorter word, or search everything: global search covers agents, coins, and skills too.</p><div class="sm-empty-actions">- <button type="button" id="sm-empty-clear" data-i18n="sitemap_index.clear_filter">Clear filter</button>- <a id="sm-empty-search" href="/search" data-i18n="sitemap_index.search_all_of_three_ws">Search all of three.ws</a>+ <button type="button" id="sm-empty-clear">Clear filter</button>+ <a id="sm-empty-search" href="/search">Search all of three.ws</a></div></div></main>diff --git a/scripts/build-awesome.mjs b/scripts/build-awesome.mjsindex 2de97f1f0..fecaaa3aa 100644--- a/scripts/build-awesome.mjs+++ b/scripts/build-awesome.mjs@@ -37,6 +37,12 @@ const outFlag = (() => {const list = JSON.parse(readFileSync(path.join(root, 'data/awesome.json'), 'utf8'));+// The standalone mirror's repo name is the manifest's job, not awesome.json's,+// so there is one list of "which directory is which public repo".+const mirrors = JSON.parse(readFileSync(path.join(root, 'data/standalone-mirrors.json'), 'utf8')).mirrors;+const awesomeMirror = mirrors.find((m) => m.exporter === 'awesome');+if (awesomeMirror?.repo) list.slug = awesomeMirror.repo;+const problems = [];const slugs = new Set();const urls = new Map();diff --git a/scripts/build-standalone-skill-repos.mjs b/scripts/build-standalone-skill-repos.mjsindex 6aa3480e0..2845e2e4c 100644--- a/scripts/build-standalone-skill-repos.mjs+++ b/scripts/build-standalone-skill-repos.mjs@@ -76,6 +76,21 @@ export const REPO_SPECS = [},];+// data/standalone-mirrors.json is the one list of "which directory is which+// public repo"; REPO_SPECS carries the per-repo skill selection this exporter+// alone needs, so it is checked against the manifest rather than duplicated+// into it (the manifest schema has no room for a select() predicate).+const manifestRepos = new Set(+ JSON.parse(fs.readFileSync(path.join(ROOT, 'data', 'standalone-mirrors.json'), 'utf8'))+ .mirrors.filter((m) => m.exporter === 'skill-repos')+ .map((m) => m.repo),+);+for (const spec of REPO_SPECS) {+ if (!manifestRepos.has(spec.repo)) {+ throw new Error(`${spec.repo}: missing from data/standalone-mirrors.json (exporter: "skill-repos")`);+ }+}+// Importable as a library (the tests read REPO_SPECS): only build when this file// is the entry point.const invokedDirectly =diff --git a/scripts/export-growth-satellites.mjs b/scripts/export-growth-satellites.mjsindex 8f8cb4a26..d35cccffd 100644--- a/scripts/export-growth-satellites.mjs+++ b/scripts/export-growth-satellites.mjs@@ -26,26 +26,18 @@ const OUT = resolve(valueAfter('--out') || DEFAULT_OUT);const OFFLINE = argv.includes('--offline');const ONLY = valueAfter('--target');-const TARGETS = [- {- name: 'agent-starter',- source: 'satellites/agent-starter',- repository: 'https://github.com/nirholas/threews-agent-starter.git',- build: false,- },- {- name: 'glb-quality-gate',- source: 'satellites/glb-quality-gate',- repository: 'https://github.com/nirholas/glb-quality-gate.git',- build: true,- },- {- name: 'oracle-desk',- source: 'satellites/oracle-desk',- repository: 'https://github.com/nirholas/oracle-desk.git',- build: false,- },-];+// Repo names and paths come from the manifest (one source of truth for every+// standalone mirror); only the build toggle is specific to this exporter.+const BUILD = { 'glb-quality-gate': true };+const MANIFEST = JSON.parse(readFileSync(join(REPO, 'data', 'standalone-mirrors.json'), 'utf8'));+const TARGETS = MANIFEST.mirrors+ .filter((m) => m.exporter === 'growth-satellites')+ .map((m) => ({+ name: m.path.split('/').pop(),+ source: m.path,+ repository: `https://github.com/nirholas/${m.repo}.git`,+ build: Boolean(BUILD[m.path.split('/').pop()]),+ }));function assertSafeOutput(path) {const relativePath = relative(REPO, path);diff --git a/scripts/sync-standalone-repos.mjs b/scripts/sync-standalone-repos.mjsindex 9f356036f..ad4d7cf01 100644--- a/scripts/sync-standalone-repos.mjs+++ b/scripts/sync-standalone-repos.mjs@@ -1,63 +1,40 @@#!/usr/bin/env node-// Sync every publishable three.ws package (MCP servers AND library SDKs) to its-// own standalone GitHub repo, idempotently. The monorepo (nirholas/three.ws)-// stays the canonical source of truth; each standalone repo is a generated,-// read-only MIRROR of one package.+// Stage every outbound standalone mirror listed in data/standalone-mirrors.json+// under dist/standalone-mirrors/<repo>/, idempotently. The monorepo+// (nirholas/three.ws) stays the canonical source of truth; each standalone repo+// is a generated, read-only MIRROR of one directory here.//-// Why mirrors and not a live split: this repo's operating rules make threews the-// single source of truth, and `git subtree`/`git filter-repo` aren't available-// here. A deterministic snapshot push is the professional pattern for generated-// mirrors — every sync force-pushes one commit whose message records the exact-// monorepo SHA it came from, so provenance is never lost.+// This script never pushes and never talks to the GitHub API. It used to+// force-push straight to main, which broke the owner's "git push is owner-gated"+// rule every run; now it only writes under dist/ (gitignored) and prints the+// exact push command, so the owner decides when a mirror actually updates.//-// A package is in scope when its dir holds a non-private package.json. Scoping-// on server.json (the old rule) silently excluded every library package, so the-// 18 SDKs under packages/ had no mirror at all; --kind narrows it back down when-// you only want one lane.-//-// For each package it:-// 1. resolves the standalone repo name (unscoped npm name, overridable below);-// 2. creates github.com/<owner>/<repo> via `gh` if it doesn't exist (public);-// 3. snapshots the package dir into a temp working tree, rewrites the mirror's-// package.json + server.json `repository` to point at the standalone repo-// (the monorepo copy is never touched), commits, and force-pushes to main.-//-// Auth: needs `gh` authenticated as the repo OWNER (so it can create/push under-// that account). The default owner is `nirholas`; override with --owner.+// The manifest (data/standalone-mirrors.json) is the one list of "which+// directory is which public repo, in which direction": this script only+// acts on entries where direction is "out" and exporter is "sync" (the+// "in" entries, e.g. robinhood/*, are reference copies this tool never+// touches; order 503 decides their fate).//// Usage:-// node scripts/sync-standalone-repos.mjs --dry-run # plan only (default)-// node scripts/sync-standalone-repos.mjs --execute # create + push all-// node scripts/sync-standalone-repos.mjs --execute --only agent-sniper,copy-mcp-// node scripts/sync-standalone-repos.mjs --execute --owner my-org-// node scripts/sync-standalone-repos.mjs --kind mcp # MCP servers only-// node scripts/sync-standalone-repos.mjs --kind lib # library packages only-// node scripts/sync-standalone-repos.mjs --new # only repos that don't exist yet-// node scripts/sync-standalone-repos.mjs --execute --metadata-only # re-apply description, topics,-// # homepage and Discussions to EXISTING repos, no push+// node scripts/sync-standalone-repos.mjs # stage every sync entry+// node scripts/sync-standalone-repos.mjs --only tty-avatar,x402-bridge+// node scripts/sync-standalone-repos.mjs --check # diff staged vs. live, write nothingimport { execFileSync } from 'node:child_process';-import { readFileSync, writeFileSync, existsSync, mkdtempSync, rmSync, cpSync, readdirSync } from 'node:fs';-import { resolve, dirname, join, basename } from 'node:path';+import { readFileSync, writeFileSync, existsSync, mkdtempSync, rmSync, cpSync, readdirSync, mkdirSync } from 'node:fs';+import { resolve, dirname, join } from 'node:path';import { tmpdir } from 'node:os';import { fileURLToPath } from 'node:url';-import { applyRepoSettings, enrichMirror, enrichPackageJson } from './lib/standalone-enrich.mjs';-import { boostMirror } from './lib/standalone-kit.mjs';+import { fixLicenseFooter } from './lib/standalone-kit.mjs';const root = resolve(dirname(fileURLToPath(import.meta.url)), '..');+const STAGE_ROOT = join(root, 'dist', 'standalone-mirrors');// ── flags ─────────────────────────────────────────────────────────────────────const argv = process.argv.slice(2);-const execute = argv.includes('--execute');-const dryRun = !execute; // dry-run is the default; --execute opts in to writesconst owner = flagValue('--owner') || 'nirholas';const onlyArg = flagValue('--only');-const kind = flagValue('--kind') || 'all'; // all | mcp | lib-const newOnly = argv.includes('--new');-const metadataOnly = argv.includes('--metadata-only');-const settingsOnly = argv.includes('--settings-only');-// A scoped token passed as GH_PAT also authenticates the `gh` calls below.-if (process.env.GH_PAT && !process.env.GH_TOKEN) process.env.GH_TOKEN = process.env.GH_PAT;+const check = argv.includes('--check');const only = onlyArg ? onlyArg.split(',').map((s) => s.trim()).filter(Boolean) : null;function flagValue(name) {@@ -67,101 +44,26 @@ function flagValue(name) {return i !== -1 && argv[i + 1] && !argv[i + 1].startsWith('--') ? argv[i + 1] : null;}-// Standalone repo names that shouldn't just be the unscoped npm name (e.g. where-// the dir name is the clearer public identity). Keyed by package dir basename.-// Packages whose public identity is built around another crypto project. Existing-// mirrors keep syncing; a NEW repo for one waits for explicit owner approval-// (CLAUDE.md commit gate), so --execute skips creating it.-const HOLD_NEW = new Set(['agenc']);--const REPO_NAME_OVERRIDES = {- 'mcp-server': '3d-agent-mcp',- 'mcp-bridge': 'x402-bridge',- 'threews-avatar-mcp': 'threews-avatar-mcp',- 'avatar-agent-mcp': 'avatar-agent-mcp',- // Renamed on GitHub; the old name only redirects, and the settings API- // answers 307 on a redirected slug.- 'agent-sniper': 'solana-sniper-mcp',-};--/**- * The standalone repo name for a package.- *- * On npm the `@three-ws` scope carries the identity, so a package can be called- * `see` or `render`. A repo cannot: github.com/nirholas/render says nothing- * about what it is or who ships it, and single-token names are the ones most- * likely to collide with something else later. Single-token `@three-ws/*` names- * therefore mirror as `three-ws-<name>`; anything already hyphenated (glb-diff,- * x402-preflight, agent-vitals) is distinctive enough to stand alone.- */-function repoNameFor(base, pkg) {- if (REPO_NAME_OVERRIDES[base]) return REPO_NAME_OVERRIDES[base];- const unscoped = pkg.name.replace(/^@[^/]+\//, '');- const scoped = pkg.name.startsWith('@three-ws/');- return scoped && !unscoped.includes('-') ? `three-ws-${unscoped}` : unscoped;-}--// ── helpers ─────────────────────────────────────────────────────────────────────const log = (...a) => console.log(...a);function git(args, opts = {}) {return execFileSync('git', args, { cwd: root, encoding: 'utf8', ...opts }).trim();}-// GitHub's secondary limit throttles bursts of writes even with core quota to-// spare, so mutating `gh api` calls are spaced out and retried with backoff.-const sleepSync = (ms) => Atomics.wait(new Int32Array(new SharedArrayBuffer(4)), 0, 0, ms);-function gh(args, opts = {}) {- const mutating = args[0] === 'api' && /^(PUT|POST|PATCH|DELETE)$/.test(args[args.indexOf('-X') + 1] || '');- for (let attempt = 0; ; attempt++) {- try {- if (mutating) sleepSync(1200);- return execFileSync('gh', args, { encoding: 'utf8', stdio: ['pipe', 'pipe', 'pipe'], ...opts }).trim();- } catch (e) {- const text = `${e.stderr || ''}${e.message}`;- if (attempt >= 5 || !/rate limit|secondary|abuse/i.test(text)) throw e;- sleepSync(30_000 * (attempt + 1));- }- }-}function readJson(path) {return JSON.parse(readFileSync(path, 'utf8'));}-// Discover every mirrorable package: a dir holding a non-private package.json.-// A server.json in the dir marks it as an MCP server (kind 'mcp'); everything-// else is a library package (kind 'lib').-function discoverPackages() {- const dirs = [- 'mcp-server',- 'mcp-bridge',- 'assistant-sdk',- ...readdirSync(join(root, 'packages')).map((d) => `packages/${d}`),- ];- const out = [];- for (const dir of dirs) {- const abs = resolve(root, dir);- if (!existsSync(join(abs, 'package.json'))) continue;- const pkg = readJson(join(abs, 'package.json'));- if (pkg.private) continue; // never mirror a private package- const base = basename(dir);- const packageKind = existsSync(join(abs, 'server.json')) ? 'mcp' : 'lib';- if (kind !== 'all' && kind !== packageKind) continue;- const repo = repoNameFor(base, pkg);- out.push({ key: base, dir, abs, pkg, repo, kind: packageKind });- }- return out.sort((a, b) => a.repo.localeCompare(b.repo));-}+// ── manifest ─────────────────────────────────────────────────────────────────+const manifest = readJson(join(root, 'data', 'standalone-mirrors.json'));+const entries = manifest.mirrors+ .filter((m) => m.exporter === 'sync' && m.direction === 'out' && m.repo)+ .filter((p) => !only || only.includes(p.repo) || only.includes(p.path))+ .map((m) => ({ ...m, abs: resolve(root, m.path), kind: existsSync(join(root, m.path, 'server.json')) ? 'mcp' : 'lib' }))+ .sort((a, b) => a.repo.localeCompare(b.repo));-function repoExists(slug) {- try {- gh(['repo', 'view', slug, '--json', 'name'], { stdio: ['ignore', 'pipe', 'ignore'] });- return true;- } catch {- return false;- }-}--// Rewrite a mirror's metadata so the standalone repo is self-consistent: its-// package.json + server.json point at THEMSELVES, not the monorepo subfolder.+// Rewrite a mirror's own manifests so they point at THEMSELVES, not the+// monorepo subfolder. This, and the license footer fix below, are the only+// content changes staging makes: everything else in the snapshot is a+// byte-for-byte copy of the source directory.function rewriteMirrorMetadata(workDir, slug) {const url = `https://github.com/${slug}.git`;const pkgPath = join(workDir, 'package.json');@@ -173,68 +75,28 @@ function rewriteMirrorMetadata(workDir, slug) {const manifestPath = join(workDir, 'server.json');if (existsSync(manifestPath)) {const m = readJson(manifestPath);- if (m.repository) {- m.repository = { url: `https://github.com/${slug}`, source: 'github' };- }+ if (m.repository) m.repository = { url: `https://github.com/${slug}`, source: 'github' };writeFileSync(manifestPath, JSON.stringify(m, null, '\t') + '\n');}}--// ── discovery metadata ──────────────────────────────────────────────────────────-// Topics are how both people and agents find a repo on GitHub. The package's own-// keywords come first (they are the author's words), then a fixed set that every-// three.ws mirror carries so the whole family is one search away.-const BASE_TOPICS = ['three-ws', 'ai-agents', 'mcp', 'model-context-protocol'];-const KIND_TOPICS = { mcp: ['mcp-server'], lib: ['sdk'] };--function topicsFor(p) {- const clean = (t) => String(t).toLowerCase().replace(/[^a-z0-9-]+/g, '-').replace(/^-+|-+$/g, '').slice(0, 50);- const own = (p.pkg.keywords || []).map(clean).filter(Boolean);- const seen = new Set();- const out = [];- for (const t of [...own, ...(KIND_TOPICS[p.kind] || []), ...BASE_TOPICS]) {- if (t && !seen.has(t)) { seen.add(t); out.push(t); }+// 93 mirrors currently ship a stale "All rights reserved" README footer and/or+// LICENSE from before this package was Apache-2.0'd. Fix both at stage time so+// the next owner push corrects all of them in one pass.+function fixLicense(workDir, monorepoLicense) {+ const readmePath = join(workDir, 'README.md');+ if (existsSync(readmePath)) {+ const readme = readFileSync(readmePath, 'utf8');+ const fixed = fixLicenseFooter(readme);+ if (fixed !== readme) writeFileSync(readmePath, fixed);}- return out.slice(0, 20); // GitHub allows 20-}--function homepageFor(p) {- return /^https?:\/\//.test(p.pkg.homepage || '') && !/github\.com/.test(p.pkg.homepage) ? p.pkg.homepage : 'https://three.ws';-}--function applyRepoMetadata(p, slug) {- const desc = (p.pkg.description || '').slice(0, 350);- gh(['repo', 'edit', slug, '--description', desc, '--homepage', homepageFor(p), '--enable-discussions']);- const topics = topicsFor(p);- gh(['api', '-X', 'PUT', `repos/${slug}/topics`, ...topics.flatMap((t) => ['-f', `names[]=${t}`]), '--silent']);-}--// Files a mirror needs to be a first-class repo on its own. Written only when the-// package does not already ship one, so an author's own file always wins. These are-// generated into the mirror and never touch the monorepo copy.-function communityFiles(p, slug) {- const name = p.pkg.name;- const desc = p.pkg.description || '';- const npm = `https://www.npmjs.com/package/${name}`;- const docs = homepageFor(p);- const bin = p.kind === 'mcp' ? `npx -y ${name}` : `npm install ${name}`;- return {- 'AGENTS.md': `# AGENTS.md\n\n${name}: ${desc}\n\n## Install\n\n\`\`\`bash\n${bin}\n\`\`\`\n\n## Where things are\n\n- \`README.md\`: usage, configuration and the public API.\n- \`src/\`: the implementation.\n- \`test/\`: the test suite. Run it with \`npm test\` after \`npm install\`.\n- npm: ${npm}\n- Docs and the rest of the platform: ${docs}\n- Machine-readable index of the platform: https://three.ws/llms.txt\n\n## Rules for agents working in this repo\n\n- This repository is a generated read-only mirror. The canonical source is https://github.com/nirholas/three.ws (path \`${p.dir}\`), so open pull requests there.\n- Do not commit credentials. Configuration is read from environment variables documented in the README.\n- Keep changes small and covered by a test.\n`,- 'llms.txt': `# ${name}\n\n> ${desc}\n\nPart of three.ws, a platform for embodied AI agents: 3D avatars, wallets, tools and a paid-API economy.\n\n## Docs\n\n- [README](https://github.com/${slug}#readme): install, usage and API\n- [npm package](${npm})\n- [three.ws](${docs}): the platform this package belongs to\n- [Platform index for LLMs](https://three.ws/llms.txt)\n\n## Source\n\n- [Mirror](https://github.com/${slug}): generated read-only mirror\n- [Canonical monorepo](https://github.com/nirholas/three.ws): source of truth and where pull requests go\n`,- 'CONTRIBUTING.md': `# Contributing to ${name}\n\nThanks for helping. This repository is a generated mirror of one package in the three.ws monorepo, so the workflow is:\n\n1. **Issues and questions:** open them here. Use Discussions for questions and ideas.\n2. **Code changes:** open the pull request against https://github.com/nirholas/three.ws, in \`${p.dir}\`. A change merged here would be overwritten by the next sync.\n3. Run \`npm install && npm test\` in the package before you open it, and add a test for new behavior.\n4. Keep commit messages in the form \`type(scope): what changed and why\`.\n`,- 'SECURITY.md': `# Security policy\n\nPlease report vulnerabilities in ${name} privately rather than in a public issue.\n\n- Use GitHub's private vulnerability reporting: https://github.com/${slug}/security/advisories/new\n- Or email [email protected]\n\nInclude the version, what you did, what you expected and what happened. You will get an acknowledgement within three working days. Never include live credentials or private keys in a report.\n`,- };-}--function addCommunityFiles(workDir, p, slug) {- for (const [file, body] of Object.entries(communityFiles(p, slug))) {- const target = join(workDir, file);- if (!existsSync(target)) writeFileSync(target, body);+ const licensePath = join(workDir, 'LICENSE');+ if (!existsSync(licensePath) || /all rights reserved/i.test(readFileSync(licensePath, 'utf8'))) {+ writeFileSync(licensePath, monorepoLicense);}}-// Last line of defense before a public push: refuse to publish a tree that holds+// Last line of defense before a public repo sees this tree: refuse to stage// something shaped like a credential or a private key.const SECRET_SHAPES = [/-----BEGIN (?:RSA |EC |OPENSSH |DSA )?PRIVATE KEY-----/,@@ -243,134 +105,123 @@ const SECRET_SHAPES = [/\bsk-(?:ant-|proj-)?[A-Za-z0-9_-]{32,}/,/\bAKIA[0-9A-Z]{16}\b/,];-function assertNoSecrets(dir) {- const walk = (d) => readdirSync(d, { withFileTypes: true }).flatMap((e) => {- const f = join(d, e.name);+function walk(dir) {+ return readdirSync(dir, { withFileTypes: true }).flatMap((e) => {+ const f = join(dir, e.name);return e.isDirectory() ? (e.name === '.git' ? [] : walk(f)) : [f];});+}+function assertNoSecrets(dir) {for (const f of walk(dir)) {if (/\.(png|jpe?g|gif|webp|ico|glb|gltf|wasm|woff2?|zip|gz)$/i.test(f)) continue;const text = readFileSync(f, 'utf8');for (const re of SECRET_SHAPES) {- if (re.test(text)) throw new Error(`refusing to publish: ${f.slice(dir.length + 1)} matches a credential pattern (${re.source.slice(0, 24)})`);+ if (re.test(text)) throw new Error(`refusing to stage: ${f.slice(dir.length + 1)} matches a credential pattern (${re.source.slice(0, 24)})`);}}}-// Snapshot one package into a fresh git repo and force-push it to the mirror's main.-async function pushSnapshot(p, slug, sourceSha) {- const tmp = mkdtempSync(join(tmpdir(), `mirror-${p.repo}-`));+// Build one mirror's snapshot as a fresh one-commit git repo at `dest`.+function stage(entry, sourceSha, dest, monorepoLicense) {+ rmSync(dest, { recursive: true, force: true });+ mkdirSync(dirname(dest), { recursive: true });+ cpSync(entry.abs, dest, {+ recursive: true,+ filter: (src) => !/(^|\/)node_modules(\/|$)/.test(src),+ });+ const slug = `${owner}/${entry.repo}`;+ rewriteMirrorMetadata(dest, slug);+ fixLicense(dest, monorepoLicense);+ assertNoSecrets(dest);++ const run = (args) => execFileSync('git', args, { cwd: dest, stdio: 'pipe', encoding: 'utf8' });+ run(['init', '-q', '-b', 'main']);+ run(['add', '-A']);+ run([+ '-c', 'user.name=three.ws sync',+ '-c', '[email protected]',+ 'commit', '-q', '-m',+ `Sync from three.ws@${sourceSha.slice(0, 12)}\n\nGenerated mirror of ${entry.path}. Canonical source: https://github.com/nirholas/three.ws`,+ ]);+ return slug;+}++// Fetch a repo's default-branch tree via codeload (not rate limited, never a+// git remote) and extract it to `dest`. Returns false when the mirror has no+// history yet (never pushed) instead of throwing.+function fetchLiveTree(slug, dest) {+ mkdirSync(dest, { recursive: true });try {- // Copy the package's working-tree contents (respecting the npm files set is- // overkill for a source mirror; the full dir is the source repo).- cpSync(p.abs, tmp, {- recursive: true,- filter: (src) => !/(^|\/)node_modules(\/|$)/.test(src),- });- rewriteMirrorMetadata(tmp, slug);- enrichPackageJson(tmp, { slug, kind: p.kind });- const mirrorPkg = JSON.parse(readFileSync(join(tmp, 'package.json'), 'utf8'));- enrichMirror(tmp, { pkg: mirrorPkg, slug, kind: p.kind });- await boostMirror(tmp, { pkg: mirrorPkg, slug, kind: p.kind, sourceDir: p.dir, monorepoLicense: readFileSync(join(root, 'LICENSE'), 'utf8') });+ execFileSync('sh', ['-c', `curl -sfL "https://codeload.github.com/${slug}/tar.gz/HEAD" | tar -xz -C "${dest}" --strip-components=1`], { stdio: 'pipe' });+ return true;+ } catch {+ return false;+ }+}- assertNoSecrets(tmp);+function filesOf(dir) {+ if (!existsSync(dir)) return [];+ return readdirSync(dir, { withFileTypes: true }).flatMap((e) => {+ const f = join(dir, e.name);+ if (e.name === '.git') return [];+ return e.isDirectory() ? filesOf(f) : [f.slice(dir.length + 1)];+ });+}- const run = (args) => execFileSync('git', args, { cwd: tmp, stdio: 'pipe', encoding: 'utf8' });- run(['init', '-q', '-b', 'main']);- run(['add', '-A']);- run([- '-c', 'user.name=three.ws sync',- '-c', '[email protected]',- 'commit', '-q', '-m',- `Sync from three.ws@${sourceSha.slice(0, 12)}\n\nGenerated mirror of packages path ${p.dir}. Canonical source: https://github.com/nirholas/three.ws`,- ]);- run(['remote', 'add', 'origin', `https://github.com/${slug}.git`]);- // Auth without leaking the token: when GH_PAT is set, a credential helper- // reads it from the environment at push time, so the token never lands in a- // remote URL, in process args, or in any error message.- // The empty `credential.helper=` first RESETS any globally-configured helper- // (e.g. gh's, which would otherwise auth as the wrong account); our token- // helper is then the only one git consults.- const authArgs = process.env.GH_PAT- ? ['-c', 'credential.helper=', '-c', 'credential.helper=!f() { echo username=x-access-token; echo "password=$GH_PAT"; }; f']- : [];- run([...authArgs, 'push', '--force', 'origin', 'main']);- } finally {- rmSync(tmp, { recursive: true, force: true });+function treesDiffer(stagedDir, liveDir) {+ const stagedFiles = new Set(filesOf(stagedDir));+ const liveFiles = new Set(filesOf(liveDir));+ if (stagedFiles.size !== liveFiles.size) return true;+ for (const f of stagedFiles) {+ if (!liveFiles.has(f)) return true;+ if (!readFileSync(join(stagedDir, f)).equals(readFileSync(join(liveDir, f)))) return true;}+ return false;}// ── main ─────────────────────────────────────────────────────────────────────-const pkgs = discoverPackages().filter((p) => !only || only.includes(p.key) || only.includes(p.repo));const sourceSha = git(['rev-parse', 'HEAD']);+const monorepoLicense = readFileSync(join(root, 'LICENSE'), 'utf8');-const lanes = `${pkgs.filter((p) => p.kind === 'mcp').length} MCP, ${pkgs.filter((p) => p.kind === 'lib').length} library`;-log(`${dryRun ? 'DRY RUN' : 'EXECUTE'}: mirroring ${pkgs.length} package(s) (${lanes}) to github.com/${owner}/*`);-log(`source: three.ws@${sourceSha.slice(0, 12)}\n`);--if (execute) {- // Fail fast if gh can't act as the owner, before touching anything.+if (check) {+ log(`CHECK: comparing ${entries.length} staged mirror(s) against their live GitHub tree\n`);+ const drifted = [];+ const scratch = mkdtempSync(join(tmpdir(), 'mirror-check-'));try {- const who = gh(['api', 'user', '--jq', '.login']);- if (who.toLowerCase() !== owner.toLowerCase()) {- log(`⚠ gh is authenticated as "${who}", not "${owner}". Creating/pushing under`);- log(` ${owner} requires that account's credentials (or org membership with repo-create rights).`);- log(` Re-auth with: gh auth login (as ${owner}), then re-run.\n`);+ for (const entry of entries) {+ const slug = `${owner}/${entry.repo}`;+ const stagedDir = join(scratch, 'staged', entry.repo);+ const liveDir = join(scratch, 'live', entry.repo);+ stage(entry, sourceSha, stagedDir, monorepoLicense);+ const fetched = fetchLiveTree(slug, liveDir);+ const differs = !fetched || treesDiffer(stagedDir, liveDir);+ log(`${differs ? 'DRIFT' : 'clean'} ${entry.repo}${fetched ? '' : ' (no history on GitHub yet)'}`);+ if (differs) drifted.push(entry.repo);}- } catch {- log('⚠ could not resolve `gh api user` — is gh authenticated? Run `gh auth status`.\n');+ } finally {+ rmSync(scratch, { recursive: true, force: true });}-}--let created = 0, pushed = 0, failed = 0, skipped = 0;-const plannedNew = [];-for (const p of pkgs) {- let slug = `${owner}/${p.repo}`;- const exists = (() => { try { return repoExists(slug); } catch { return false; } })();- // A repo renamed since it was created answers on its old name only through a- // redirect that git follows but `gh api -X PUT/POST` does not, so settings and- // Pages URLs must be built from the canonical name.- if (exists) {- try { slug = gh(['api', `repos/${slug}`, '--jq', '.full_name']) || slug; } catch { /* keep the requested name */ }+ log(`\n${drifted.length} of ${entries.length} mirror(s) drifted from what is staged.`);+ if (drifted.length) {+ log(`drifted: ${drifted.join(', ')}`);+ process.exitCode = 1;}- if (newOnly && exists) { skipped++; continue; }- if (!exists && HOLD_NEW.has(p.key)) { skipped++; log(`── ${p.pkg.name}: new repo held for owner approval (references another crypto project)`); continue; }- if (!exists) plannedNew.push(slug);- log(`── ${p.pkg.name} [${p.kind}] → github.com/${slug} ${exists ? '(exists)' : '(NEW)'}`);+ process.exit();+}- if (dryRun) {- if (!exists) log(` would: gh repo create ${slug} --public`);- if (!metadataOnly) log(` would: snapshot ${p.dir} → force-push to ${slug}#main`);- log(` would: set homepage ${homepageFor(p)}, Discussions on, topics ${topicsFor(p).join(', ')}`);- continue;- }- if (metadataOnly && !exists) { skipped++; continue; }+log(`STAGE: ${entries.length} mirror(s) under dist/standalone-mirrors/*`);+log(`source: three.ws@${sourceSha.slice(0, 12)}\n`);- try {- if (!exists) {- const desc = (p.pkg.description || '').slice(0, 350);- gh(['repo', 'create', slug, '--public', '--description', desc, '--homepage', 'https://three.ws']);- created++;- log(' created repo');- }- if (!settingsOnly) {- await pushSnapshot(p, slug, sourceSha);- pushed++;- log(' pushed snapshot');- }- const enriched = JSON.parse(readFileSync(join(p.abs, 'package.json'), 'utf8'));- log(` settings: ${applyRepoSettings(gh, { pkg: enriched, slug, kind: p.kind }).join(' | ')}`);- } catch (err) {- failed++;- log(` ✗ ${err.message.split('\n')[0]}`);- }+const pushLines = [];+for (const entry of entries) {+ const dest = join(STAGE_ROOT, entry.repo);+ const slug = stage(entry, sourceSha, dest, monorepoLicense);+ log(`-- ${entry.path} [${entry.kind}] -> dist/standalone-mirrors/${entry.repo} (github.com/${slug})`);+ pushLines.push(`git -C dist/standalone-mirrors/${entry.repo} push --force https://github.com/${slug}.git HEAD:main`);}-if (dryRun) {- log(`\nDry run complete. ${pkgs.length - skipped} package(s) planned, ${plannedNew.length} of them NEW repos.`);- if (plannedNew.length) log(` new: ${plannedNew.join(', ')}`);- log(`Re-run with --execute (and gh auth as ${owner}) to apply.`);-} else {- log(`\nDone. ${created} created, ${pushed} pushed, ${skipped} skipped, ${failed} failed.`);+log(`\nStaged ${entries.length} mirror(s). 0 repos created, 0 pushed (this tool never does either).`);+if (pushLines.length) {+ log('\nTo publish, run (owner-gated, one line per mirror):\n');+ for (const line of pushLines) log(` ${line}`);}-if (failed) process.exitCode = 1;diff --git a/tests/standalone-mirrors.test.js b/tests/standalone-mirrors.test.jsnew file mode 100644index 000000000..806daf98e--- /dev/null+++ b/tests/standalone-mirrors.test.js@@ -0,0 +1,50 @@+// data/standalone-mirrors.json is the single source of truth every standalone-mirror+// exporter (sync-standalone-repos.mjs, export-growth-satellites.mjs, build-awesome.mjs+// --standalone, build-standalone-skill-repos.mjs) reads instead of hardcoding repo+// names. These tests lock down the shape so a bad hand-edit cannot silently break an+// exporter: the manifest must validate against its own schema, every path must exist+// on disk, and every non-null repo slug must be unique (two entries claiming the same+// mirror would make one of them silently overwrite the other on the next sync).++import { describe, it, expect } from 'vitest';+import { existsSync, readFileSync } from 'node:fs';+import { resolve } from 'node:path';+import Ajv from 'ajv';++const ROOT = resolve(import.meta.dirname, '..');+const manifest = JSON.parse(readFileSync(resolve(ROOT, 'data/standalone-mirrors.json'), 'utf8'));+const schema = JSON.parse(readFileSync(resolve(ROOT, 'data/standalone-mirrors.schema.json'), 'utf8'));++describe('data/standalone-mirrors.json', () => {+ it('validates against its schema', () => {+ const ajv = new Ajv({ allErrors: true, strict: false });+ const validate = ajv.compile(schema);+ const valid = validate(manifest);+ expect(validate.errors, JSON.stringify(validate.errors)).toBeFalsy();+ expect(valid).toBe(true);+ });++ it('has at least one mirror entry', () => {+ expect(manifest.mirrors.length).toBeGreaterThan(0);+ });++ it('every path exists on disk', () => {+ const missing = manifest.mirrors.filter((m) => !existsSync(resolve(ROOT, m.path)));+ expect(missing.map((m) => m.path)).toEqual([]);+ });++ it('every non-null repo slug is unique', () => {+ const repos = manifest.mirrors.map((m) => m.repo).filter(Boolean);+ const dupes = repos.filter((r, i) => repos.indexOf(r) !== i);+ expect(dupes).toEqual([]);+ });++ it('a repeated path only ever repeats for the skill-repos exporter', () => {+ // skill-repos is the one legitimate 1-path-to-many-repos case: three+ // plugin marketplaces are cut from the same .agents/skills tree.+ const byPath = new Map();+ for (const m of manifest.mirrors) byPath.set(m.path, (byPath.get(m.path) || 0) + 1);+ const unexpectedDupes = manifest.mirrors.filter((m) => byPath.get(m.path) > 1 && m.exporter !== 'skill-repos');+ expect(unexpectedDupes.map((m) => m.path)).toEqual([]);+ });+});