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
docs(changelog): record the ASL drill and agora repairs, and refresh the page index
nirholas220082f5e300
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex 0939e7977..642e83bc1 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -75,6 +75,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr- **The background agent mint says out loud whether it ran**: Every avatar that finishes a scan or a prompt is given a draft on-chain identity in the background. That step is deliberately best-effort, so it can never cost you your avatar, but it was also completely silent: whether it minted, was skipped because the deployment holds no minting key, or was switched off entirely, the logs looked identical, which is how a run of avatars can go by without anyone noticing the identity was never created. Each finished avatar now records the outcome of both chains, including the reason a leg was skipped. The documentation for the feature also gained a way to prove the whole path on a machine that cannot reach the public test-network faucet, which is routinely exhausted on shared build machines: run your own node with the real Metaplex programs, and the proof reports which node served it rather than handing back an explorer link that leads nowhere. (`/docs/draft-agent-mint`) `[improvement, docs]`- **The BNB block race stops showing a dead chain's last number as if it were live**: The live block race compares BNB Chain, Base, Ethereum and Solana by measuring each one off a public RPC every few seconds, and it promises that a chain going quiet says so instead of freezing a fake number. The four lane cards kept that promise; the big headline number did not. When the BNB RPC stopped answering, the headline held its last reading at full brightness, kept claiming it was N times faster than Base, and the Updated stamp sat on "just now" no matter how long the outage ran. The headline now dims the moment the reading stops being live, labels it as last measured and prints its real age in seconds, and drops the speed comparison rather than race a stale number against a live one. The Updated stamp ages off the measurement time the server reports, and a poll that measured nothing no longer refreshes it. If every chain goes down at once the page now raises its outage notice and its Retry button, which previously could only ever appear before the first successful reading and so was unreachable during a real outage. Retry now shows it is working, makes a genuinely new request rather than reporting an older in-flight one's failure, and no longer sits underneath the floating helper widgets where the click was being swallowed. A lane that has never returned a sample says so plainly instead of pointing at a reading that is not on screen, each poll goes to the network instead of replaying a cached body up to fifteen seconds old, and screen readers now hear a lane announce a change of state rather than re-reading all four numbers twelve times a minute. (`/bnb-latency`) `[fix, improvement]`- **The BNB Chain page now says how many demos are actually live**: The BNB Chain page checks each of its three demo tracks against the running deployment and reports the tally in its header. That line was stuck: it read "Checking which tracks are live" forever, even once all three cards beside it had finished and said Live. The page's own result was being written first and then overwritten by the translation pass that swaps the page into your language, so the finished count never survived. The header now holds its result and reads "3 of 3 demo tracks live now". The same checks were also leaving four cancelled requests in the browser's network log on every visit, which made a healthy page look like it was failing to anyone with developer tools open. They now close cleanly. (`/bnb`) `[fix]`+- **The Commons now fills with citizens in seconds instead of standing empty**: Agora said it held 200 citizens while the square in front of you stayed empty. Every citizen was waiting on its own 3D model, and those run from 3 MB to 21 MB each, so the world was downloading close to a gigabyte before anyone could stand up: measured, 19 of 200 citizens had arrived after four and a half minutes. On top of that the page asked the server where each citizen's model lived one citizen at a time, 184 separate requests that also crowded out the economy ticker, which is why the population, tasks and $THREE readouts sat on dashes and the feed said it was reconnecting. The population endpoint now answers that question once for the whole square, and the crowd is drawn in two passes: everybody is standing within seconds, and the most recently active citizens change into their own avatar as it arrives, in place, without losing their spot or interrupting a walk to the job board. The population counter reads "n / 200" honestly while they arrive rather than reporting a number that did not match the square, and the Reload button on the "failed to load" screen now actually reloads. (`/agora`) `[fix, improvement]`- **The creations gallery now counts every creation a creator has made, and pages all the way to the end**: The gallery ranked creators and paged the feed over only the newest 120 creations, however many the feed actually held. A creator's older work was invisible in their profile count, the top-creator board scored people on a fraction of their output, and scrolling the gallery dead-ended early with items still left to show. It now reads the full feed depth it always meant to, and does it in two database round trips instead of two per item, so the deeper read loads faster than the shallow one did. (`/creations`) `[fix, improvement]`- **The FLAME paper link in the Avatar Engines Atlas opens the paper again**: FLAME is the parametric head model underneath most of the photoreal-head engines in the atlas at /avatar-engines, so its Paper button is one a builder actually follows. It pointed at a Max Planck publication page that answers every visitor, browsers included, with a 403 Forbidden, so the button led to an error page instead of the paper. It now opens the paper PDF that the FLAME project site itself links to. All 68 outbound links on the page were re-checked afterwards and every one of them resolves. (`/avatar-engines`) `[fix]`- **The Forge community board remembers what you liked**: The community showcase on /forge, and the same feed on the daily page and the model explorer, kept showing your own likes as un-liked. The board is held at the edge for a minute so it loads instantly for everyone, but the copy being held was the one built for a visitor who is not you, and it was handed to you as well. Your like button then started from the wrong state, and pressing it again fought with what the server already knew. The board now keeps a separate copy for a signed browser, so the hearts you filled in stay filled. Alongside it, a security fix on the Game-Ready export: when the export was paid for with $THREE rather than covered by holding, a badly formed payment reference made the server answer with the raw internals of its own database instead of a plain "that payment could not be verified". It now says only what a caller needs, and a database problem is no longer reported as a bad payment, so nobody is told to pay twice for an outage on our side. (`/forge`) `[fix, security]`diff --git a/STRUCTURE.md b/STRUCTURE.mdindex 7961f675e..8e9a9f1d3 100644--- a/STRUCTURE.md+++ b/STRUCTURE.md@@ -50,6 +50,7 @@ bottom.| Platform activity feed | [pages/feed.html](pages/feed.html) `→ /feed` + [pages/community.html](pages/community.html) `→ /community`, backend [api/users/me/feed.js](api/users/me/feed.js) | Live | Reverse-chronological creation events (avatars, agents, coins, models, worlds) plus follow activity, merged at read time from `forge_creations`, `dioramas`, and `user_follows` (no separate event log to drift out of sync). `?scope=following` (default; session-gated, anonymous gets 401) vs `?scope=all` (public; powers `/community` and first-visit feeds); `limit` 1..50, `before` ISO cursor. Items deep-link to creator portfolios. Distinct from the Money Pulse ticker `GET /api/feed` ([docs/money-feed.md](docs/money-feed.md)). Docs: [docs/social-layer.md](docs/social-layer.md) || Follow graph | [api/users/[username]/follow.js](api/users/%5Busername%5D/follow.js) + [api/users/[username]/follows.js](api/users/%5Busername%5D/follows.js), table `user_follows`, buttons on [pages/profile.html](pages/profile.html) | Live | `GET` returns `{following, followed_by, followers_count, following_count}`; `POST`/`DELETE` are idempotent (session + CSRF, self-follow 400) and return the same envelope so one round-trip updates the button and the counts. A genuinely new edge (`ON CONFLICT DO NOTHING`) publishes a `follow` user event to the notification bell exactly once. Feeds the activity feed's following scope, search ranking, and the `followers` leaderboard metric. Tests: [tests/api/users-follow.test.js](tests/api/users-follow.test.js). Docs: [docs/social-layer.md](docs/social-layer.md) || Notification bell & preferences | Event vocabulary [api/_lib/feed.js](api/_lib/feed.js) (`USER_EVENT_TYPES` → `publishUserEvent()` → `user_notifications`), endpoints [api/notifications/](api/notifications), preference matrix [api/_lib/notify-prefs.js](api/_lib/notify-prefs.js), bell client [src/notifications.js](src/notifications.js), settings panel [src/dashboard-next/pages/settings.js](src/dashboard-next/pages/settings.js) | Live | In-app inbox covering remixes ([api/x402/remix-asset.js](api/x402/remix-asset.js)), DMs ([api/friends/messages.js](api/friends/messages.js)), coin bonding-curve graduations (pump cron in [api/cron/[name].js](api/cron/%5Bname%5D.js)), follows, sales, purchases, IRL, market, and account events. Preferences are a category × channel matrix (`in_app` always on; push/email/telegram are per-category opt-outs) edited from `/dashboard/settings`. Docs: [docs/social-layer.md](docs/social-layer.md) |+| Skill bundles (seller builder + evidence pricing) | [pages/bundles.html](pages/bundles.html) `→ /bundles`, API [api/agents/[id]/bundles.js](api/agents/%5Bid%5D/bundles.js), arithmetic [api/_lib/bundle-pricing.js](api/_lib/bundle-pricing.js), checkout [api/marketplace/purchase-bundle.js](api/marketplace/purchase-bundle.js) | Live (seller side); no buyer-facing browser view yet | Sell several of one agent's skills as one purchase. The price is derived from the agent's own ledger rather than a rule of thumb: the public `?action=pricing` endpoint finds every buyer who already bought 2+ of the selected skills, suggests the median of what they really paid (`basis: median_basket`), and backtests any candidate price against those same baskets; with no such buyer yet it falls back to 20% off the sum of the parts and labels itself `discount_off_list` so a default is never read as a finding. Every amount is an atomic integer carried as a BigInt end to end, because a 9-decimal mint puts real sums past `Number.MAX_SAFE_INTEGER`. Checkout settles on-chain and writes one `skill_purchases` row per skill (`kind = 'bundle'`, amount 0) so one bundle sale is never counted as N skill sales. Docs: [docs/skill-bundles.md](docs/skill-bundles.md). Tests: [tests/bundle-pricing.test.js](tests/bundle-pricing.test.js), [tests/vercel-agents-subpath-routes.test.js](tests/vercel-agents-subpath-routes.test.js) || Marketplace analytics & trial funnel | [pages/marketplace-analytics.html](pages/marketplace-analytics.html) `→ /marketplace/analytics`, renderer [src/marketplace-analytics.js](src/marketplace-analytics.js), backend [api/marketplace/analytics.js](api/marketplace/analytics.js) | Live | Public transparency page for the skill marketplace: paid sales, volume, top skills/agents, and the trial conversion funnel. **Every money aggregate gates on `status = 'confirmed'` alone.** Counting `status IN ('confirmed','trial')` as a sale published 10,454 "sales" and 6.2M $THREE of "volume" on 2026-07-30 against a table holding zero confirmed purchases, because a `trial` row is a free grant whose `amount` is only the list price it would have cost. Free trials now render as their own stat and as a four-stage funnel (granted → used → exhausted → converted), which also names the two shapes that mean a wiring fault rather than weak demand: trials never spent, or trials exhausted with nothing converting. Docs: [docs/marketplace.md](docs/marketplace.md), tutorial [docs/tutorials/sell-a-skill-with-a-trial.md](docs/tutorials/sell-a-skill-with-a-trial.md). Tests: [tests/marketplace-analytics-paid-only.test.js](tests/marketplace-analytics-paid-only.test.js) || OKX.AI marketplace services | [api/okx/3d/[service].js](api/okx/3d/%5Bservice%5D.js) `→ /api/okx/3d/*` | Live | 3D services sold to other agents on OKX.AI (agent #2632): Agent Identity Studio flagship + decomposed studio services. Catalog source of truth: [api/_lib/okx-catalog.js](api/_lib/okx-catalog.js); pipeline: [api/_okx3d/](api/_okx3d); showcase: [pages/agent-identities.html](pages/agent-identities.html) `→ /agent-identities` + [src/agent-identities.js](src/agent-identities.js), fed at runtime by [api/agent-identities.js](api/agent-identities.js) `→ /api/agent-identities` (demo runs from `data/agent-identities.json` merged with the live catalog row, so the price the page quotes is the price the paid endpoint charges); docs: [docs/okx-marketplace.md](docs/okx-marketplace.md), [docs/agent-identities.md](docs/agent-identities.md) || OKX.AI marketplace chat bot host | [workers/okx-chat-bot/](workers/okx-chat-bot) (Cloud Run service `okx-chat-bot`), local revive [scripts/okx-bot-revive.mjs](scripts/okx-bot-revive.mjs) `→ npm run okx:bot` | Built · deploy owner-gated | Always-on host for the XMTP chat behind agent #2632. Supervises the `okx-a2a` daemon plus the `onchainos` wallet session, persists the wallet/XMTP identity to GCS across revisions, and rebuilds the AI subsession's briefing from [api/_lib/okx-chat-briefing.js](api/_lib/okx-chat-briefing.js) on every boot so quoted prices can never drift from the catalog. It exists because the stack used to live on a codespace that sleeps, and its outage mode is silent: an expired wallet session leaves the process healthy while no chat is delivered, which flagged the listing offline once. Health reaches the platform as the `okx_chat_bot` subsystem on `/api/healthz` via a `bot_heartbeat` row; a logged-out session pages with the exact login commands. Deploy: [workers/okx-chat-bot/cloudbuild.yaml](workers/okx-chat-bot/cloudbuild.yaml) (`--max-instances=1` is load-bearing, one GCS state writer). Tests: [tests/okx-chat-bot.test.js](tests/okx-chat-bot.test.js) |diff --git a/data/changelog.json b/data/changelog.jsonindex b36f70bef..eb8521fe7 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. `link` is optional and must be a live three.ws path.","entries": [+ {+ "date": "2026-08-16",+ "title": "The Commons now fills with citizens in seconds instead of standing empty",+ "summary": "Agora said it held 200 citizens while the square in front of you stayed empty. Every citizen was waiting on its own 3D model, and those run from 3 MB to 21 MB each, so the world was downloading close to a gigabyte before anyone could stand up: measured, 19 of 200 citizens had arrived after four and a half minutes. On top of that the page asked the server where each citizen's model lived one citizen at a time, 184 separate requests that also crowded out the economy ticker, which is why the population, tasks and $THREE readouts sat on dashes and the feed said it was reconnecting. The population endpoint now answers that question once for the whole square, and the crowd is drawn in two passes: everybody is standing within seconds, and the most recently active citizens change into their own avatar as it arrives, in place, without losing their spot or interrupting a walk to the job board. The population counter reads \"n / 200\" honestly while they arrive rather than reporting a number that did not match the square, and the Reload button on the \"failed to load\" screen now actually reloads.",+ "tags": [+ "fix",+ "improvement"+ ],+ "link": "/agora"+ },{"date": "2026-08-16","title": "The Avatar SDK playground now changes the avatar you are looking at, not just the code beside it",diff --git a/data/examples.json b/data/examples.jsonindex 5b73303ac..886205f34 100644--- a/data/examples.json+++ b/data/examples.json@@ -231,7 +231,7 @@"kind": "package","group": "Package examples","title": "@three-ws/kol-mcp",- "description": "Track one smart trader from any AI agent - a tracked KOL wallet's portfolio P&L (realized/unrealized, win rate, top holding) and its trades on a given mint. Read-only over the live public three.ws KOL API. No key, no signer, no payment.",+ "description": "Two runnable examples. Both spawn this package's own MCP server over stdio (the same node src/index.js entry point the README documents), speak real MCP JSON-RPC to it, and read the live public KOL API.","path": "packages/kol-mcp/examples","files": ["list-tools.mjs",@@ -239,7 +239,7 @@],"run": "node packages/kol-mcp/examples/list-tools.mjs","runKind": "command",- "readme": null,+ "readme": "packages/kol-mcp/examples/README.md","owner": "packages/kol-mcp"},{@@ -247,14 +247,15 @@"kind": "package","group": "Package examples","title": "@three-ws/loom-mcp",- "description": "Loom - the three.ws community 3D-creation gallery from any AI agent. Browse the public feed of community-forged GLB creations, fetch one with its viewer URL, and submit your own. Public API, no key required.",+ "description": "Two runnable examples. Both spawn this package's own MCP server over stdio (the same node src/index.js entry point the README documents), speak real MCP JSON-RPC to it, and read the live public Loom gallery.","path": "packages/loom-mcp/examples","files": [+ "browse-loom.mjs","list-tools.mjs"],- "run": "node packages/loom-mcp/examples/list-tools.mjs",+ "run": "node packages/loom-mcp/examples/browse-loom.mjs","runKind": "command",- "readme": null,+ "readme": "packages/loom-mcp/examples/README.md","owner": "packages/loom-mcp"},{diff --git a/data/pages.json b/data/pages.jsonindex 3c1a150bf..ce2205e8a 100644--- a/data/pages.json+++ b/data/pages.json@@ -2407,6 +2407,14 @@"changefreq": "weekly","added": "2026-04-27"},+ {+ "path": "/docs/skill-bundles",+ "title": "Docs · Skill bundles",+ "description": "How a bundle of an agent's skills is priced from that agent's own sales rather than a rule of thumb: the median-basket and flat-discount bases, the public pricing and backtest endpoint, the owner endpoints that publish and retire a bundle, and the on-chain checkout that unlocks every skill in one payment.",+ "priority": 0.6,+ "changefreq": "monthly",+ "added": "2026-08-16"+ },{"path": "/docs/avatar-artifact","title": "Docs · Avatar Artifact viewer",diff --git a/docs/examples.md b/docs/examples.mdindex 98792bdb2..fbf185893 100644--- a/docs/examples.md+++ b/docs/examples.md@@ -761,8 +761,8 @@ The repo ships 45 examples: 11 web component demos, 10 end-to-end projects, and| [`avatar-sdk/examples`](../avatar-sdk/examples) | A self-contained page, no build step. It loads the SDK's @three-ws/avatar/agent entry from a CDN, awaits ensureAgent3D() to register the <agent-3d> element, and renders the real three.ws default avatar using the documented src and kiosk attributes. | `npm run dev, then open /avatar-sdk/examples/index.html` || [`packages/avatar-schema/examples`](../packages/avatar-schema/examples) | JSON Schema and validator for three.ws on-chain avatar manifests - the canonical, hash-anchored format any cross-chain client can use to resolve an avatar. | Reference files, nothing to execute || [`concierge-sdk/examples`](../concierge-sdk/examples) | Runnable examples for every way to use the concierge. The HTML files load the SDK from ../dist, build it first (npm run build in the package root), then serve this folder (npx serve .) and open each file. | `npm run dev, then open /concierge-sdk/examples/custom-avatar.html` |-| [`packages/kol-mcp/examples`](../packages/kol-mcp/examples) | Track one smart trader from any AI agent - a tracked KOL wallet's portfolio P&L (realized/unrealized, win rate, top holding) and its trades on a given mint. Read-only over the live public three.ws KOL API. No key, no signer, no payment. | `node packages/kol-mcp/examples/list-tools.mjs` |-| [`packages/loom-mcp/examples`](../packages/loom-mcp/examples) | Loom - the three.ws community 3D-creation gallery from any AI agent. Browse the public feed of community-forged GLB creations, fetch one with its viewer URL, and submit your own. Public API, no key required. | `node packages/loom-mcp/examples/list-tools.mjs` |+| [`packages/kol-mcp/examples`](../packages/kol-mcp/examples) | Two runnable examples. Both spawn this package's own MCP server over stdio (the same node src/index.js entry point the README documents), speak real MCP JSON-RPC to it, and read the live public KOL API. | `node packages/kol-mcp/examples/list-tools.mjs` |+| [`packages/loom-mcp/examples`](../packages/loom-mcp/examples) | Two runnable examples. Both spawn this package's own MCP server over stdio (the same node src/index.js entry point the README documents), speak real MCP JSON-RPC to it, and read the live public Loom gallery. | `node packages/loom-mcp/examples/browse-loom.mjs` || [`packages/marketplace-mcp/examples`](../packages/marketplace-mcp/examples) | Two runnable examples. Both spawn this package's own MCP server over stdio (the same node src/index.js entry point the README documents), speak real MCP JSON-RPC to it, and read the live public marketplace. | `node packages/marketplace-mcp/examples/browse-marketplace.mjs` || [`mcp-server/examples`](../mcp-server/examples) | Two zero-dependency walkthroughs of the MCP Streamable HTTP lifecycle against the live three.ws server at https://three.ws/api/mcp (MCP 2025-06-18, JSON-RPC 2.0). | `node mcp-server/examples/client.mjs` || [`page-agent-sdk/examples`](../page-agent-sdk/examples) | Run these from the package root with any static server so the import map can resolve the unbundled source from ../src: | `npm run dev, then open /page-agent-sdk/examples/custom-avatar.html` |diff --git a/public/changelog.json b/public/changelog.jsonindex c3f0e9a7e..2b9776f01 100644--- a/public/changelog.json+++ b/public/changelog.json@@ -1,5 +1,5 @@{- "generated_at": "2026-08-16T22:10:38.249Z",+ "generated_at": "2026-08-16T22:41:51.246Z","generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json","site": {"name": "three.ws",@@ -745,6 +745,17 @@"fix"]},+ {+ "date": "2026-08-16",+ "type": "update",+ "title": "The Commons now fills with citizens in seconds instead of standing empty",+ "summary": "Agora said it held 200 citizens while the square in front of you stayed empty. Every citizen was waiting on its own 3D model, and those run from 3 MB to 21 MB each, so the world was downloading close to a gigabyte before anyone could stand up: measured, 19 of 200 citizens had arrived after four and a half minutes. On top of that the page asked the server where each citizen's model lived one citizen at a time, 184 separate requests that also crowded out the economy ticker, which is why the population, tasks and $THREE readouts sat on dashes and the feed said it was reconnecting. The population endpoint now answers that question once for the whole square, and the crowd is drawn in two passes: everybody is standing within seconds, and the most recently active citizens change into their own avatar as it arrives, in place, without losing their spot or interrupting a walk to the job board. The population counter reads \"n / 200\" honestly while they arrive rather than reporting a number that did not match the square, and the Reload button on the \"failed to load\" screen now actually reloads.",+ "link": "/agora",+ "tags": [+ "fix",+ "improvement"+ ]+ },{"date": "2026-08-16","type": "update",diff --git a/public/changelog.xml b/public/changelog.xmlindex 866cccf93..e63aebfe2 100644--- a/public/changelog.xml+++ b/public/changelog.xml@@ -558,6 +558,14 @@<category>fix</category><description>The BNB Chain page checks each of its three demo tracks against the running deployment and reports the tally in its header. That line was stuck: it read "Checking which tracks are live" forever, even once all three cards beside it had finished and said Live. The page's own result was being written first and then overwritten by the translation pass that swaps the page into your language, so the finished count never survived. The header now holds its result and reads "3 of 3 demo tracks live now". The same checks were also leaving four cancelled requests in the browser's network log on every visit, which made a healthy page look like it was failing to anyone with developer tools open. They now close cleanly.</description></item>+ <item>+ <title>The Commons now fills with citizens in seconds instead of standing empty</title>+ <link>https://three.ws/agora</link>+ <guid isPermaLink="false">2026-08-16:The Commons now fills with citizens in seconds instead of standing empty</guid>+ <pubDate>Sun, 16 Aug 2026 12:00:00 GMT</pubDate>+ <category>fix</category>+ <description>Agora said it held 200 citizens while the square in front of you stayed empty. Every citizen was waiting on its own 3D model, and those run from 3 MB to 21 MB each, so the world was downloading close to a gigabyte before anyone could stand up: measured, 19 of 200 citizens had arrived after four and a half minutes. On top of that the page asked the server where each citizen's model lived one citizen at a time, 184 separate requests that also crowded out the economy ticker, which is why the population, tasks and $THREE readouts sat on dashes and the feed said it was reconnecting. The population endpoint now answers that question once for the whole square, and the crowd is drawn in two passes: everybody is standing within seconds, and the most recently active citizens change into their own avatar as it arrives, in place, without losing their spot or interrupting a walk to the job board. The population counter reads "n / 200" honestly while they arrive rather than reporting a number that did not match the square, and the Reload button on the "failed to load" screen now actually reloads.</description>+ </item><item><title>The creations gallery now counts every creation a creator has made, and pages all the way to the end</title><link>https://three.ws/creations</link>diff --git a/public/examples.json b/public/examples.jsonindex 7fc7e328e..66f4286d8 100644--- a/public/examples.json+++ b/public/examples.json@@ -231,7 +231,7 @@"kind": "package","group": "Package examples","title": "@three-ws/kol-mcp",- "description": "Track one smart trader from any AI agent - a tracked KOL wallet's portfolio P&L (realized/unrealized, win rate, top holding) and its trades on a given mint. Read-only over the live public three.ws KOL API. No key, no signer, no payment.",+ "description": "Two runnable examples. Both spawn this package's own MCP server over stdio (the same node src/index.js entry point the README documents), speak real MCP JSON-RPC to it, and read the live public KOL API.","path": "packages/kol-mcp/examples","files": ["list-tools.mjs",@@ -239,7 +239,7 @@],"run": "node packages/kol-mcp/examples/list-tools.mjs","runKind": "command",- "readme": null,+ "readme": "packages/kol-mcp/examples/README.md","owner": "packages/kol-mcp"},{@@ -247,14 +247,15 @@"kind": "package","group": "Package examples","title": "@three-ws/loom-mcp",- "description": "Loom - the three.ws community 3D-creation gallery from any AI agent. Browse the public feed of community-forged GLB creations, fetch one with its viewer URL, and submit your own. Public API, no key required.",+ "description": "Two runnable examples. Both spawn this package's own MCP server over stdio (the same node src/index.js entry point the README documents), speak real MCP JSON-RPC to it, and read the live public Loom gallery.","path": "packages/loom-mcp/examples","files": [+ "browse-loom.mjs","list-tools.mjs"],- "run": "node packages/loom-mcp/examples/list-tools.mjs",+ "run": "node packages/loom-mcp/examples/browse-loom.mjs","runKind": "command",- "readme": null,+ "readme": "packages/loom-mcp/examples/README.md","owner": "packages/loom-mcp"},{diff --git a/public/features.json b/public/features.jsonindex 009130f17..2763a3dbb 100644--- a/public/features.json+++ b/public/features.json@@ -1,5 +1,5 @@{- "generated_at": "2026-08-16T22:10:38.040Z",+ "generated_at": "2026-08-16T22:41:51.141Z","generated_by": "scripts/build-page-index.mjs from data/pages.json","site": {"name": "three.ws",diff --git a/public/llms-full.txt b/public/llms-full.txtindex 1ebbb5676..939da0bcb 100644--- a/public/llms-full.txt+++ b/public/llms-full.txt@@ -1799,6 +1799,18 @@ URL: https://three.ws/docsFull documentation: SDKs, API reference, embedding, agent system, smart contracts.+### Docs · Skill bundles++URL: https://three.ws/docs/skill-bundles++How a bundle of an agent's skills is priced from that agent's own sales rather than a rule of thumb: the median-basket and flat-discount bases, the public pricing and backtest endpoint, the owner endpoints that publish and retire a bundle, and the on-chain checkout that unlocks every skill in one payment.++### Docs · Avatar Artifact viewer++URL: https://three.ws/docs/avatar-artifact++The standalone avatar viewer you paste into any site as a one-line iframe: its ?agent= and ?model= parameters, the hosts a model may come from, how a clip-less rig still comes to life, and the sentence the page shows for every way it can fail.+### Docs · Site load performanceURL: https://three.ws/docs/site-performancediff --git a/public/llms.txt b/public/llms.txtindex 2d85560a3..921b37585 100644--- a/public/llms.txt+++ b/public/llms.txt@@ -334,6 +334,8 @@ Sign-in, dashboard, billing.Docs, tutorials, and reference.- [Docs](https://three.ws/docs): Full documentation: SDKs, API reference, embedding, agent system, smart contracts.+- [Docs · Skill bundles](https://three.ws/docs/skill-bundles): How a bundle of an agent's skills is priced from that agent's own sales rather than a rule of thumb: the median-basket and flat-discount bases, the public pricing and backtest endpoint, the owner endpoints that publish and retire a bundle, and the on-chain checkout that unlocks every skill in one payment.+- [Docs · Avatar Artifact viewer](https://three.ws/docs/avatar-artifact): The standalone avatar viewer you paste into any site as a one-line iframe: its ?agent= and ?model= parameters, the hosts a model may come from, how a clip-less rig still comes to life, and the sentence the page shows for every way it can fail.- [Docs · Site load performance](https://three.ws/docs/site-performance): The load-cost rules behind every page that is not /play, each with the Lighthouse measurement that produced it: catalogue grids skip the rows nobody can see, analytics waits for the first idle moment, the CDN bundle ships minified, below-the-fold sections load below the fold, and thumbnails decode off the critical path.- [Docs · Farcaster memory seeding](https://three.ws/docs/farcaster-memory-seeding): Give an agent your Farcaster voice with explicit consent: ownership is proved by signing a challenge with a wallet the fid itself verified on the protocol (Solana first), only your public profile and casts are read, and revoking the grant deletes every memory it produced.- [Docs · Likeness evaluation](https://three.ws/docs/likeness-eval): How three.ws measures whether a generated avatar actually looks like the person in the photos: three head-framed renders, an open-source face-recognition embedding, and a 1-5 score anchored to the model's own same-person threshold rather than to anyone's opinion.diff --git a/public/sitemap/index.html b/public/sitemap/index.htmlindex 4e1caf8f5..bcfaf3f57 100644--- a/public/sitemap/index.html+++ b/public/sitemap/index.html@@ -83,7 +83,7 @@<main class="sm-wrap"><div class="sm-hero"><h1>Sitemap</h1>- <p>All 822 pages on three.ws, grouped by purpose. Looking for the machine-readable versions?</p>+ <p>All 824 pages on three.ws, grouped by purpose. Looking for the machine-readable versions?</p><div class="sm-formats"><a href="/sitemap.xml"><code>sitemap.xml</code> · for search engines</a><a href="/llms.txt"><code>llms.txt</code> · for AI agents</a>@@ -95,7 +95,7 @@</div><div class="sm-filter"><svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" aria-hidden="true"><circle cx="11" cy="11" r="7"/><path d="m21 21-4.3-4.3"/></svg>- <input id="sm-filter-input" type="search" placeholder="Filter 822 pages by name, path, or description…" aria-label="Filter pages" autocomplete="off" spellcheck="false" />+ <input id="sm-filter-input" type="search" placeholder="Filter 824 pages by name, path, or description…" aria-label="Filter pages" autocomplete="off" spellcheck="false" /><kbd aria-hidden="true">/</kbd></div><p class="sm-filter-count" id="sm-filter-count" role="status" aria-live="polite"></p>@@ -103,6 +103,22 @@<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="/docs/skill-bundles">+ <span class="sm-new-date">Aug 16, 2026</span>+ <span class="sm-title">Docs · Skill bundles</span>+ <span class="sm-path">/docs/skill-bundles</span>+ <span class="sm-desc">How a bundle of an agent's skills is priced from that agent's own sales rather than a rule of thumb: the median-basket and flat-discount bases, the public pricing and backtest endpoint, the owner endpoints that publish and retire a bundle, and the on-chain checkout that unlocks every skill in one payment.</span>+ </a>+ </li>+ <li>+ <a href="/docs/avatar-artifact">+ <span class="sm-new-date">Aug 16, 2026</span>+ <span class="sm-title">Docs · Avatar Artifact viewer</span>+ <span class="sm-path">/docs/avatar-artifact</span>+ <span class="sm-desc">The standalone avatar viewer you paste into any site as a one-line iframe: its ?agent= and ?model= parameters, the hosts a model may come from, how a clip-less rig still comes to life, and the sentence the page shows for every way it can fail.</span>+ </a>+ </li><li><a href="/docs/site-performance"><span class="sm-new-date">Aug 14, 2026</span>@@ -159,22 +175,6 @@<span class="sm-desc">Create, pause, resume and cancel recurring on-chain USDC payments and DCA schedules, see every charge each one has settled, and watch what is being paid into your own agents.</span></a></li>- <li>- <a href="/docs/skill-royalties">- <span class="sm-new-date">Aug 13, 2026</span>- <span class="sm-title">Docs · Skill royalties</span>- <span class="sm-path">/docs/skill-royalties</span>- <span class="sm-desc">Publish a skill, price it, and earn on every call. The exact author/platform split, why your share routes to your own wallet at settlement (Solana first), the ledger where you watch payouts land with an explorer link each, and the proof lane that verifies the whole accounting path without moving a cent.</span>- </a>- </li>- <li>- <a href="/reputation/market">- <span class="sm-new-date">Aug 12, 2026</span>- <span class="sm-title">Reputation Staking Market</span>- <span class="sm-path">/reputation/market</span>- <span class="sm-desc">Stake conviction on an agent and earn from its attested action history: escrowed principal, per-epoch yield derived from signed on-chain attestations, withdraw any time.</span>- </a>- </li></ul></section><nav class="sm-toc" aria-label="Sections">@@ -2262,7 +2262,7 @@<section class="sm-section" id="learn"><header>- <h2>Learn<span class="sm-count" data-count>364</span></h2>+ <h2>Learn<span class="sm-count" data-count>366</span></h2><p class="sm-section-desc">Docs, tutorials, and reference.</p></header><ul class="sm-list">@@ -2273,6 +2273,20 @@<span class="sm-desc">Full documentation: SDKs, API reference, embedding, agent system, smart contracts.</span></a></li>+ <li>+ <a href="/docs/skill-bundles">+ <span class="sm-title">Docs · Skill bundles</span>+ <span class="sm-path">/docs/skill-bundles</span>+ <span class="sm-desc">How a bundle of an agent's skills is priced from that agent's own sales rather than a rule of thumb: the median-basket and flat-discount bases, the public pricing and backtest endpoint, the owner endpoints that publish and retire a bundle, and the on-chain checkout that unlocks every skill in one payment.</span>+ </a>+ </li>+ <li>+ <a href="/docs/avatar-artifact">+ <span class="sm-title">Docs · Avatar Artifact viewer</span>+ <span class="sm-path">/docs/avatar-artifact</span>+ <span class="sm-desc">The standalone avatar viewer you paste into any site as a one-line iframe: its ?agent= and ?model= parameters, the hosts a model may come from, how a clip-less rig still comes to life, and the sentence the page shows for every way it can fail.</span>+ </a>+ </li><li><a href="/docs/site-performance"><span class="sm-title">Docs · Site load performance</span>