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): log today's fixes for holders and rebuild the public feeds
nirholas97d788521d8c
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex f7ae9a55a..cd10efe59 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -17,7 +17,9 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr- **A database blip during a scheduled job now reads as a database blip, not a healthy run**: Two of the scheduled jobs behind the trading fleet could fail without anything looking wrong. The job that reallocates budget across strategies talks to the database over a socket, and when that socket never opened the failure arrived as an object carrying no message at all. The job caught it, answered with an empty error string, and the scheduler recorded a success, so the health record stayed green while the loop did nothing. Failures of that kind are now recognised as what they are, a database that could not be reached, so the run is marked unhealthy and retried on the next tick instead of being logged as fine. Every page and endpoint that reads from the database inherits the same correction: this class of outage now returns a retryable service-unavailable response rather than an internal error. The fleet watchdog also gained a seventh check, over the calibration pass that measures whether a high-conviction coin actually wins as often as its score claims, so that loop can no longer go quiet unnoticed. `[fix, infra]`- **A paid-call share link now previews on Slack, Telegram and LinkedIn**: Every settled x402 call has a permalink whose social preview image is drawn on demand. Slack, Telegram and LinkedIn ask an image URL for its type and size before they fetch it, and this one answered "method not allowed" to that probe, so the card silently never appeared on those platforms. It answers them now. Three more fixes to the same card: a receipt is captioned with the network it actually settled on rather than always reading mainnet; a link shared in the seconds before its receipt finishes saving, or during a cache outage, is retried a minute later instead of being pinned to the generic card for an hour; and a damaged record shows a plain "unknown" rather than a "NaNd ago" timestamp or an invented amount. (`/pay`) `[fix]`- **Add funds now opens Coinbase on the buy step, not on a transfer you cannot make**: The Add funds window hands you a Coinbase checkout with your three.ws wallet already filled in as the destination. That checkout was not told which step to open on, so Coinbase could land you on "transfer from your Coinbase balance", which is no help at all if you reached Add funds precisely because you hold nothing yet. It now always opens on the buy step for the asset you picked (USDC or SOL, both settling on Solana). The suggested dollar amount is also rounded to real dollars and cents before it reaches Coinbase, so an amount worked out from a shortfall can no longer show up as something like $25.777777 on the checkout screen or in the window itself. `[fix, improvement]`+- **AgenC task lists no longer hang when a Solana provider goes quiet**: Browsing tasks on the AgenC coordination protocol reads directly from Solana, and the platform keeps a chain of providers so a bad one gets skipped. That skipping only worked when a provider answered with an error. A provider that accepted the request and then went silent held the page open for minutes with nothing to react to, which is what happened to the task list, the heaviest read of the set. Each provider now gets a fixed time to answer before the next one is tried, so a silent provider costs seconds instead of stalling the page. (`/agenc`) `[fix]`- **Agent share cards keep their portrait, and a sealed-drop card always paints a real theme**: The image an agent link unfurls with inlines the agent's avatar thumbnail. It resolved that thumbnail with its own URL builder rather than the platform's, so a stored key holding a space, or one of the legacy origin-pointing keys that never had an image behind it, cost the card its portrait and spent a doomed fetch on every crawl. It now uses the same resolver every other surface uses, ignores what a remote server claims the image type is unless it is a real image type, and an unset storage setting costs the portrait instead of the whole card. Separately, a sealed gift card could paint blank colors if a drop record ever carried a theme name outside the curated set, and an unreadable balance now reads as a plain blank rather than a long dash. `[fix]`+- **Agent-runtime and agent-guards docs now match what the code actually returns**: Two developer packages shipped quick-start examples that described results the code does not produce: the runtime's guard example annotated the wrong decision and named a field on the ledger checker that does not exist, and the guards package documented only its hosted half while the local, no-network guard functions went unmentioned. Both are corrected against real executed output, with the local guards now documented end to end including a runnable example and the exact reason codes they return. `[docs, sdk]`- **Agents that discover us the documented way can now reach the wallet tools**: An AI client that finds three.ws on its own follows a trail: it calls a tool, gets told it needs to sign in, and reads a small public document that lists the permissions it is allowed to ask for. That document had fallen behind. It advertised eight permissions while the sign-up endpoint actually grants twelve, and the three it left out were exactly the ones that unlock the agent wallet tools, so a client doing everything correctly could never ask to check a balance, pay for a service, provision a wallet, or put an endpoint up for sale. The published list and the list the server honors are now read from one place, with a test that fails the build if they ever drift apart again. Separately, the paid-call example an agent receives with the payment request pointed at a sample model file on a domain that does not exist, so the very first call a paying agent copied failed on a dead address; it now points at a real model served from three.ws. Every discovery endpoint was re-checked end to end afterwards. (`/docs/mcp-agent`) `[fix, security]`- **An Oracle coin page now tells you what happened after the call, and stops letting a score be read as a percentage**: A conviction of 100 sitting above a chart that had already spiked and collapsed looked like a broken engine. It was not: the score is a rank on a 0 to 100 line, fitted to predict that a launch runs 3x or graduates, and it says nothing about whether the run survives. Nothing on the page said that, and the ground truth was buried below the fold. The verdict card now carries both missing sentences right under the dial. It quotes what calls in that band actually did, measured over resolved coins rather than inferred from the score (26 percent of calls in the 90-100 band went on to graduate or run 2x without ever rugging, 4.8 times what a random launch manages), it says how early the call was made, and it says plainly that the score ranks the odds of a run and not the odds of a safe hold. Under that, once the market has settled a coin, a Since the call line states the outcome in the order a holder reads it: peak multiple, graduated or rugged, and what it is worth now. Both lines are rendered on the server, so a link pasted into a chat shows the outcome in the preview instead of a bare triumphant number, and the feed at /oracle carries the same outcome as a chip on every resolved card. The accuracy pages were reporting three numbers wrong in the same way. The calibration table, its Brier score, and the calibration cron all read a score of 86 as a claim of 86 percent when the model claims 55, which overstated the engine's own confidence by up to four times and made a calibrated ranking look wildly overconfident; all three now use the real score-to-probability map, and the table publishes both the trained event and the stricter rug-aware win side by side so neither is presented as the other. The monotonicity check was also flattering itself: it tolerated any dip under five points, which was exactly the size of the dip in production, and reported the ladder as calibrated anyway. It now counts an inversion whenever two bands' confidence intervals cannot overlap, and the page names the bands that failed instead of asserting that all is well. (`/oracle`) `[fix, improvement]`- **Another site can no longer swap your agent's body or burn your avatar credits behind your back**: The two avatar onboarding endpoints (the one that opens the photo editor, and the one that attaches a finished avatar to an agent) accepted a request that arrived with your login cookie but no proof you meant to send it. A page you had merely visited could therefore repoint your agent to a different body, or spend your hourly avatar-editor allowance, without you doing anything. Both now require the same one-time token every other account-changing action on three.ws already asks for, and both refuse the request outright without it. API-key callers are unaffected. A second change: when the photo editor is not configured in an environment, the request is turned away before it counts against your hourly allowance, so a temporary outage no longer locks you out of the flow for an hour once it is back. `[security, fix]`@@ -91,6 +93,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr- **Withdrawing a reputation stake now stops counting as a vote of confidence**: You can back an agent by staking SOL behind it, and the agent's reputation card shows how much conviction is escrowed and who put it there. Until now that figure only ever went up: withdrawing your stake returned your money but left your endorsement standing forever, so an agent could show several SOL of backing that nobody was actually behind any more. The card now counts what is still staked. The moment a withdrawal settles, that position drops out of the total and its owner drops out of the list of backers. Nothing is hidden by the change: the card also reports everything ever staked and everything settlement gave back, so a long track record of people staking and withdrawing still reads as one. Only the market's own escrow can retire a position, so nobody can make an agent look abandoned by publishing a note about somebody else's stake, and the total can never be pushed below zero. The staking market page also now says why staking is closed when a network has no escrow configured, instead of showing a greyed-out button with no explanation. (`/reputation/market`) `[fix, feature]`- **Withdrawing your agent token's earnings is confirmed against the real payout, and cannot be triggered from another site**: Two fixes to the withdraw flow on your agent's pump.fun token. The confirmation step used to accept any successful Solana transaction that simply mentioned your token and its authority wallet, which an ordinary transfer or memo does, and report it back as a completed payout; it now requires that the payments program actually ran, the same check the launch flow already made. Both withdraw steps also now reject requests that arrive from a site other than three.ws while riding your signed-in session, so a page you happen to have open elsewhere cannot start a withdrawal on your behalf. Alongside that, an unreadable token-program value in a withdraw request is now refused up front with a clear message instead of being quietly ignored and producing a transaction that only failed after you had signed it. `[security, fix]`- **Your agent now leads with the GitHub work you seeded it from**: Seeding an agent from your GitHub profile and repositories stored the facts correctly, but filed all of them in the tier the agent only consults when a message happens to match one. So the seed worked and yet asking your agent an open question like 'what do you know about my work?' could come back with nothing, because nothing in the question named a repository. The five top-ranked facts from a seed now sit in the context the agent always carries, so they ground an answer without being prompted for by name; the rest stay searchable exactly as before and still surface when you ask about that specific project. Facts also keep the order they were distilled in, which matters because each reply carries only the ten strongest memories, and until now that cut was made arbitrarily among facts that all scored the same. Nothing about what is read or stored changes: the seed still reads only the profile, repositories, and READMEs you ticked, and disconnecting GitHub still deletes every fact it wrote across all your agents. (`/docs/github-memory-seeding`) `[fix, improvement]`+- **Your agent's memory graph was never being built, and now it is**: Memory Studio promises a knowledge graph: every fact your agent stores is scanned for the mints, tickers, wallets, people, and strategies it mentions, and those become nodes you can click through to ask what your agent remembers about any one of them. That scan was failing on a type mismatch the moment it tried to save a node, and because the failure was caught quietly, nothing ever looked broken: the graph simply came back empty forever, for every agent, and the memories were never marked as scanned. The save is fixed, so the graph now fills in on your next visit, including for everything your agents have stored up to now. Recall and search were never affected. (`/memory`) `[fix]`- **Your referrals page now shows how many people actually opened your link**: Every three.ws referral link already recorded a visit when someone opened it, but nothing ever showed you those numbers. The referrals dashboard now has a Share funnel: link visits, how many of those visits became signups, and how many of those signups went on to make their first creation, with the conversion rate between each step over the last 30 days. Visits are counted once per person per day, so refreshing a link does not inflate the number, and the page only shows the funnel once you have at least one visit. The same data is available on the referrals API as a funnel block, with an optional lookback window. (`/dashboard/referrals`) `[feature, improvement]`## 2026-08-13@@ -3189,7 +3192,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr- **Docs · SDK** (`/docs/sdk`): JavaScript / Node SDK for three.ws.- **Docs · Skills** (`/docs/skills`): Write, package, and monetize agent skills.- **OpenAPI** (`/openapi.json`): Machine-readable HTTP API spec.-- **Privacy Policy** (`/legal/privacy`): How three.ws handles user data.+- **Privacy Policy** (`/legal/privacy`): What data three.ws collects, why we hold it, who we share it with, how long we keep it, and the controls you have over it.- **Terms of Use** (`/legal/tos`): Terms of service for three.ws.- **Tutorial · Build a custom skill** (`/tutorials/custom-skill`): A complete walkthrough of building a weather skill an agent can invoke: bundle format, LLM tool calling, context API.- **Tutorial · Build a personal AI website** (`/tutorials/personal-ai-site`): A 3D version of you, on your domain, ready to answer any question about your work: with a portfolio, contact form, and resume.diff --git a/data/changelog.json b/data/changelog.jsonindex 88e72a4cc..c21be813f 100644--- a/data/changelog.json+++ b/data/changelog.json@@ -1,6 +1,33 @@{"$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-14",+ "title": "Your agent's memory graph was never being built, and now it is",+ "summary": "Memory Studio promises a knowledge graph: every fact your agent stores is scanned for the mints, tickers, wallets, people, and strategies it mentions, and those become nodes you can click through to ask what your agent remembers about any one of them. That scan was failing on a type mismatch the moment it tried to save a node, and because the failure was caught quietly, nothing ever looked broken: the graph simply came back empty forever, for every agent, and the memories were never marked as scanned. The save is fixed, so the graph now fills in on your next visit, including for everything your agents have stored up to now. Recall and search were never affected.",+ "tags": [+ "fix"+ ],+ "link": "/memory"+ },+ {+ "date": "2026-08-14",+ "title": "AgenC task lists no longer hang when a Solana provider goes quiet",+ "summary": "Browsing tasks on the AgenC coordination protocol reads directly from Solana, and the platform keeps a chain of providers so a bad one gets skipped. That skipping only worked when a provider answered with an error. A provider that accepted the request and then went silent held the page open for minutes with nothing to react to, which is what happened to the task list, the heaviest read of the set. Each provider now gets a fixed time to answer before the next one is tried, so a silent provider costs seconds instead of stalling the page.",+ "tags": [+ "fix"+ ],+ "link": "/agenc"+ },+ {+ "date": "2026-08-14",+ "title": "Agent-runtime and agent-guards docs now match what the code actually returns",+ "summary": "Two developer packages shipped quick-start examples that described results the code does not produce: the runtime's guard example annotated the wrong decision and named a field on the ledger checker that does not exist, and the guards package documented only its hosted half while the local, no-network guard functions went unmentioned. Both are corrected against real executed output, with the local guards now documented end to end including a runnable example and the exact reason codes they return.",+ "tags": [+ "docs",+ "sdk"+ ]+ },{"date": "2026-08-14","title": "Agents that discover us the documented way can now reach the wallet tools",diff --git a/public/changelog.json b/public/changelog.jsonindex 388d5adbb..4d4fc3cf3 100644--- a/public/changelog.json+++ b/public/changelog.json@@ -1,5 +1,5 @@{- "generated_at": "2026-08-14T18:18:09.426Z",+ "generated_at": "2026-08-14T18:22:30.219Z","generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json","site": {"name": "three.ws",@@ -120,6 +120,16 @@"improvement"]},+ {+ "date": "2026-08-14",+ "type": "update",+ "title": "AgenC task lists no longer hang when a Solana provider goes quiet",+ "summary": "Browsing tasks on the AgenC coordination protocol reads directly from Solana, and the platform keeps a chain of providers so a bad one gets skipped. That skipping only worked when a provider answered with an error. A provider that accepted the request and then went silent held the page open for minutes with nothing to react to, which is what happened to the task list, the heaviest read of the set. Each provider now gets a fixed time to answer before the next one is tried, so a silent provider costs seconds instead of stalling the page.",+ "link": "/agenc",+ "tags": [+ "fix"+ ]+ },{"date": "2026-08-14","type": "update",@@ -130,6 +140,17 @@"fix"]},+ {+ "date": "2026-08-14",+ "type": "update",+ "title": "Agent-runtime and agent-guards docs now match what the code actually returns",+ "summary": "Two developer packages shipped quick-start examples that described results the code does not produce: the runtime's guard example annotated the wrong decision and named a field on the ledger checker that does not exist, and the guards package documented only its hosted half while the local, no-network guard functions went unmentioned. Both are corrected against real executed output, with the local guards now documented end to end including a runnable example and the exact reason codes they return.",+ "link": null,+ "tags": [+ "docs",+ "sdk"+ ]+ },{"date": "2026-08-14","type": "update",@@ -928,6 +949,16 @@"improvement"]},+ {+ "date": "2026-08-14",+ "type": "update",+ "title": "Your agent's memory graph was never being built, and now it is",+ "summary": "Memory Studio promises a knowledge graph: every fact your agent stores is scanned for the mints, tickers, wallets, people, and strategies it mentions, and those become nodes you can click through to ask what your agent remembers about any one of them. That scan was failing on a type mismatch the moment it tried to save a node, and because the failure was caught quietly, nothing ever looked broken: the graph simply came back empty forever, for every agent, and the memories were never marked as scanned. The save is fixed, so the graph now fills in on your next visit, including for everything your agents have stored up to now. Recall and search were never affected.",+ "link": "/memory",+ "tags": [+ "fix"+ ]+ },{"date": "2026-08-14","type": "update",@@ -30125,7 +30156,7 @@"date": "2026-04-27","type": "launch","title": "Privacy Policy",- "summary": "How three.ws handles user data.",+ "summary": "What data three.ws collects, why we hold it, who we share it with, how long we keep it, and the controls you have over it.","link": "/legal/privacy","tags": ["launch"diff --git a/public/changelog.xml b/public/changelog.xmlindex 9a2d5e258..0f4420396 100644--- a/public/changelog.xml+++ b/public/changelog.xml@@ -94,6 +94,14 @@<category>fix</category><description>The Add funds window hands you a Coinbase checkout with your three.ws wallet already filled in as the destination. That checkout was not told which step to open on, so Coinbase could land you on "transfer from your Coinbase balance", which is no help at all if you reached Add funds precisely because you hold nothing yet. It now always opens on the buy step for the asset you picked (USDC or SOL, both settling on Solana). The suggested dollar amount is also rounded to real dollars and cents before it reaches Coinbase, so an amount worked out from a shortfall can no longer show up as something like $25.777777 on the checkout screen or in the window itself.</description></item>+ <item>+ <title>AgenC task lists no longer hang when a Solana provider goes quiet</title>+ <link>https://three.ws/agenc</link>+ <guid isPermaLink="false">2026-08-14:AgenC task lists no longer hang when a Solana provider goes quiet</guid>+ <pubDate>Fri, 14 Aug 2026 12:00:00 GMT</pubDate>+ <category>fix</category>+ <description>Browsing tasks on the AgenC coordination protocol reads directly from Solana, and the platform keeps a chain of providers so a bad one gets skipped. That skipping only worked when a provider answered with an error. A provider that accepted the request and then went silent held the page open for minutes with nothing to react to, which is what happened to the task list, the heaviest read of the set. Each provider now gets a fixed time to answer before the next one is tried, so a silent provider costs seconds instead of stalling the page.</description>+ </item><item><title>Agent share cards keep their portrait, and a sealed-drop card always paints a real theme</title><link>https://three.ws/changelog</link>@@ -102,6 +110,14 @@<category>fix</category><description>The image an agent link unfurls with inlines the agent's avatar thumbnail. It resolved that thumbnail with its own URL builder rather than the platform's, so a stored key holding a space, or one of the legacy origin-pointing keys that never had an image behind it, cost the card its portrait and spent a doomed fetch on every crawl. It now uses the same resolver every other surface uses, ignores what a remote server claims the image type is unless it is a real image type, and an unset storage setting costs the portrait instead of the whole card. Separately, a sealed gift card could paint blank colors if a drop record ever carried a theme name outside the curated set, and an unreadable balance now reads as a plain blank rather than a long dash.</description></item>+ <item>+ <title>Agent-runtime and agent-guards docs now match what the code actually returns</title>+ <link>https://three.ws/changelog</link>+ <guid isPermaLink="false">2026-08-14:Agent-runtime and agent-guards docs now match what the code actually returns</guid>+ <pubDate>Fri, 14 Aug 2026 12:00:00 GMT</pubDate>+ <category>docs</category>+ <description>Two developer packages shipped quick-start examples that described results the code does not produce: the runtime's guard example annotated the wrong decision and named a field on the ledger checker that does not exist, and the guards package documented only its hosted half while the local, no-network guard functions went unmentioned. Both are corrected against real executed output, with the local guards now documented end to end including a runnable example and the exact reason codes they return.</description>+ </item><item><title>Agents that discover us the documented way can now reach the wallet tools</title><link>https://three.ws/docs/mcp-agent</link>@@ -686,6 +702,14 @@<category>fix</category><description>Seeding an agent from your GitHub profile and repositories stored the facts correctly, but filed all of them in the tier the agent only consults when a message happens to match one. So the seed worked and yet asking your agent an open question like 'what do you know about my work?' could come back with nothing, because nothing in the question named a repository. The five top-ranked facts from a seed now sit in the context the agent always carries, so they ground an answer without being prompted for by name; the rest stay searchable exactly as before and still surface when you ask about that specific project. Facts also keep the order they were distilled in, which matters because each reply carries only the ten strongest memories, and until now that cut was made arbitrarily among facts that all scored the same. Nothing about what is read or stored changes: the seed still reads only the profile, repositories, and READMEs you ticked, and disconnecting GitHub still deletes every fact it wrote across all your agents.</description></item>+ <item>+ <title>Your agent's memory graph was never being built, and now it is</title>+ <link>https://three.ws/memory</link>+ <guid isPermaLink="false">2026-08-14:Your agent's memory graph was never being built, and now it is</guid>+ <pubDate>Fri, 14 Aug 2026 12:00:00 GMT</pubDate>+ <category>fix</category>+ <description>Memory Studio promises a knowledge graph: every fact your agent stores is scanned for the mints, tickers, wallets, people, and strategies it mentions, and those become nodes you can click through to ask what your agent remembers about any one of them. That scan was failing on a type mismatch the moment it tried to save a node, and because the failure was caught quietly, nothing ever looked broken: the graph simply came back empty forever, for every agent, and the memories were never marked as scanned. The save is fixed, so the graph now fills in on your next visit, including for everything your agents have stored up to now. Recall and search were never affected.</description>+ </item><item><title>Your referrals page now shows how many people actually opened your link</title><link>https://three.ws/dashboard/referrals</link>@@ -23100,7 +23124,7 @@<guid isPermaLink="false">2026-04-27:Privacy Policy</guid><pubDate>Mon, 27 Apr 2026 12:00:00 GMT</pubDate><category>launch</category>- <description>How three.ws handles user data.</description>+ <description>What data three.ws collects, why we hold it, who we share it with, how long we keep it, and the controls you have over it.</description></item><item><title>Terms of Use</title>diff --git a/public/features.json b/public/features.jsonindex 0236b978b..f04e657ff 100644--- a/public/features.json+++ b/public/features.json@@ -1,5 +1,5 @@{- "generated_at": "2026-08-14T18:18:09.396Z",+ "generated_at": "2026-08-14T18:22:30.133Z","generated_by": "scripts/build-page-index.mjs from data/pages.json","site": {"name": "three.ws",@@ -6974,7 +6974,7 @@{"path": "/legal/privacy","title": "Privacy Policy",- "description": "How three.ws handles user data.",+ "description": "What data three.ws collects, why we hold it, who we share it with, how long we keep it, and the controls you have over it.","added": "2026-04-27","auth": null,"indexable": true,diff --git a/public/llms-full.txt b/public/llms-full.txtindex 33faba201..2e5087bfa 100644--- a/public/llms-full.txt+++ b/public/llms-full.txt@@ -320,6 +320,13 @@ URL: https://three.ws/demosIndex of live demos across the platform: viewers, agents, payments, and experiments.+### Agent Interaction Lab++URL: https://three.ws/demos/agents+Indexable: no (excluded from sitemap)++Fourteen prototypes exploring how a 3D agent physically inhabits a web page: real gravity, page elements as the playground, and the agent reacting to scroll, clicks, and the cursor.+## BuildCreate and customize an agent.@@ -2038,6 +2045,12 @@ URL: https://three.ws/docs/mocap-studioDrive a 3D avatar's face live from your webcam in the browser: MediaPipe face landmarks mapped to ARKit blendshapes, smoothing, record and replay, and save.+### Docs · Draft Agent Mint++URL: https://three.ws/docs/draft-agent-mint++Every finished reconstruction is stored durably and minted as a draft on-chain agent identity: the Solana leg, the ERC-8004 leg, the flags that arm each one, and how to prove the whole path on devnet.+### Docs · Selfie to AvatarURL: https://three.ws/docs/selfie-to-avatar@@ -2930,13 +2943,13 @@ Every three.ws agent owns one custodial Solana wallet. Seven owner-only HTTP surURL: https://three.ws/docs/vaults-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, under "Back-an-Agent Vaults". Read that first.+A vault lets strangers put real USDC behind one trading agent, on terms the agent's owner publishes up front. The deep reference: every route and who may call it, the share and fee math, the guards in front of a trade, and the public audit ledger.### Docs: Your master walletURL: https://three.ws/docs/user-wallet-Every three.ws agent owns a wallet (agent-wallets.md). Separately, every user account can own one custodial wallet of its own: the master wallet. It is the financial hub for the person rather than the bot.+Every user account can own one custodial wallet: the master wallet, the financial hub for the person rather than the bot. Provision it, read balances, send SOL or any SPL token, fund an agent, and read its on-chain history, with the spend safeguards on each route.### Docs: Copy Trading@@ -2972,7 +2985,7 @@ URL: https://three.ws/docs/viabilityURL: https://three.ws/docs/press-kit-Everything a journalist, analyst, conference organiser, or partner needs to write about three.ws: the marks, the announcement graphics, approved boilerplate at three lengths, the fast facts, and the rules that govern all of it.+Everything a journalist, analyst, conference organiser, or partner needs to write about three.ws: the marks, the announcement graphics, approved boilerplate at four lengths, the fast facts, and the rules that govern all of it.### Docs: Partner ecosystem@@ -4202,7 +4215,7 @@ Every three.ws policy in one place, plus which address to use to report copyrighURL: https://three.ws/legal/privacy-How three.ws handles user data.+What data three.ws collects, why we hold it, who we share it with, how long we keep it, and the controls you have over it.### End-User License Agreementdiff --git a/public/llms.txt b/public/llms.txtindex 8a8ade756..2b9f6f2dd 100644--- a/public/llms.txt+++ b/public/llms.txt@@ -375,6 +375,7 @@ Docs, tutorials, and reference.- [Docs · Animation Studio](https://three.ws/docs/animation-studio): Pose any avatar or the built-in mannequin with FK/IK, keyframe a timeline, preview live, and export an animated GLB or clip JSON. Save clips to your account and list them for sale in USDC.- [Docs · Avatar Studio](https://three.ws/docs/avatar-studio): Build a rigged 3D avatar from scratch with no selfie: choose a base body, sculpt face and body morphs, add outfits and accessories, and export a GLB.- [Docs · Mocap Studio](https://three.ws/docs/mocap-studio): Drive a 3D avatar's face live from your webcam in the browser: MediaPipe face landmarks mapped to ARKit blendshapes, smoothing, record and replay, and save.+- [Docs · Draft Agent Mint](https://three.ws/docs/draft-agent-mint): Every finished reconstruction is stored durably and minted as a draft on-chain agent identity: the Solana leg, the ERC-8004 leg, the flags that arm each one, and how to prove the whole path on devnet.- [Docs · Selfie to Avatar](https://three.ws/docs/selfie-to-avatar): Point your camera at your face and get a rigged 3D avatar in about a minute, free and in the browser. The capture flow, the reconstruction pipeline, and where the avatar goes next.- [Docs · Voice Lab](https://three.ws/docs/voice-lab): Pick a voice from any provider or clone your own from a short browser recording, play it in the TTS playground, and assign it to an agent.- [Docs · Lipsync](https://three.ws/docs/lipsync): Two in-browser lipsync demos: TTS-driven mouth animation and live-mic viseme detection, both driving an avatar's viseme morph targets in real time.@@ -523,14 +524,14 @@ Docs, tutorials, and reference.- [Docs: Creator portfolio](https://three.ws/docs/creator-portfolio): Everything a creator makes on three.ws (avatars, agents, forged models, worlds, coins, skills, plugins, and more) aggregates onto one public page: https://three.ws/u/<username>.- [Docs: Autonomous agent-to-agent payments](https://three.ws/docs/a2a-payments): How one three.ws agent pays another agent's paid endpoint with no human approving each payment: how the spending mandate is issued, every gate a payment passes, the record each one leaves behind, and how to stop an agent that has gone wrong.- [Docs: Agent wallet control API](https://three.ws/docs/agent-wallet-api): Every three.ws agent owns one custodial Solana wallet. Seven owner-only HTTP surfaces hang off it, and this is their developer reference: exact routes, exact request and response JSON, exact error codes, and a working curl call for each.-- [Docs: USDC agent vaults](https://three.ws/docs/vaults): 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, under "Back-an-Agent Vaults". Read that first.-- [Docs: Your master wallet](https://three.ws/docs/user-wallet): Every three.ws agent owns a wallet (agent-wallets.md). Separately, every user account can own one custodial wallet of its own: the master wallet. It is the financial hub for the person rather than the bot.+- [Docs: USDC agent vaults](https://three.ws/docs/vaults): A vault lets strangers put real USDC behind one trading agent, on terms the agent's owner publishes up front. The deep reference: every route and who may call it, the share and fee math, the guards in front of a trade, and the public audit ledger.+- [Docs: Your master wallet](https://three.ws/docs/user-wallet): Every user account can own one custodial wallet: the master wallet, the financial hub for the person rather than the bot. Provision it, read balances, send SOL or any SPL token, fund an agent, and read its on-chain history, with the spend safeguards on each route.- [Docs: Copy Trading](https://three.ws/docs/copy-trading): Copy trading lets one wallet follow another's real trades. Two engines sit behind it: the custodial agent mirror, where the platform signs a real on-chain trade from your agent's wallet within its spend policy, and non-custodial subscriptions, which record a sized intent for you to sign.- [Docs: On-chain Deployments](https://three.ws/docs/deployments): /deployments is the live, cross-chain feed of agent identities landing on-chain: every ERC-8004 Identity Registry registration on EVM and every Metaplex Core agent mint on Solana, in one chronological stream, as each one lands. It is a read-only public surface.- [Docs: CA to x402](https://three.ws/docs/ca2x402): Paste a token contract address, get back a live, agent-payable x402 market-intel endpoint for that exact token. The generated endpoint costs a small USDC payment per call, is discoverable in the x402 bazaar, and needs no keys, no backend, and no deploy from the person who generated it.- [Docs: Agent Economy Volume](https://three.ws/docs/agent-economy-volume): /agent-economy-volume is the public roll-up of the agent-to-agent economy: the total USDC that three.ws agents have actually paid each other for paid skills over the x402 rails, plus who earns it, who spends it, and how it moves day to day for the last 90 days.- [Docs: Viability](https://three.ws/docs/viability): /viability answers one question about three.ws without decoration: are the two money loops real? The skill marketplace ($THREE skill GMV, take-rate, repeat buyers, trading pairs) and agent trading (guarded coin-trade flow, what it cost, and the realized profit and loss on positions that have.-- [Docs: Press kit](https://three.ws/docs/press-kit): Everything a journalist, analyst, conference organiser, or partner needs to write about three.ws: the marks, the announcement graphics, approved boilerplate at three lengths, the fast facts, and the rules that govern all of it.+- [Docs: Press kit](https://three.ws/docs/press-kit): Everything a journalist, analyst, conference organiser, or partner needs to write about three.ws: the marks, the announcement graphics, approved boilerplate at four lengths, the fast facts, and the rules that govern all of it.- [Docs: Partner ecosystem](https://three.ws/docs/partners): 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.- [Docs: Agent Identity Studio](https://three.ws/docs/agent-identities): Every AI agent deserves a face. The Agent Identity Studio takes an agent's name and a plain-language brand brief and returns a complete visual identity: a rigged, animation-ready GLB avatar, a square profile picture that stays legible at thumbnail size, and a set of posed, studio-lit full-body.- [Docs: OKX.AI marketplace services](https://three.ws/docs/okx-marketplace): The 3D services three.ws sells to other AI agents on OKX.AI: the Agent Identity Studio flagship plus micro-priced text-to-3D, rigging, retargeting, pose and export endpoints, each paid per call over x402 on X Layer.@@ -742,7 +743,7 @@ Long-form announcements, launches, and writing from three.ws.## Legal- [Legal](https://three.ws/legal): Every three.ws policy in one place, plus which address to use to report copyright, abuse, or privacy issues.-- [Privacy Policy](https://three.ws/legal/privacy): How three.ws handles user data.+- [Privacy Policy](https://three.ws/legal/privacy): What data three.ws collects, why we hold it, who we share it with, how long we keep it, and the controls you have over it.- [End-User License Agreement](https://three.ws/legal/eula): License terms for the three.ws Seeker/Saga app.- [Terms of Use](https://three.ws/legal/tos): Terms of service for three.ws.- [Risk Disclosure](https://three.ws/legal/risk): Risk disclosure for real-funds features: experimental software, total-loss risk, autonomous agents, no liability.diff --git a/public/sitemap/index.html b/public/sitemap/index.htmlindex d188be732..e176be5e0 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 818 pages on three.ws, grouped by purpose. Looking for the machine-readable versions?</p>+ <p>All 820 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 818 pages by name, path, or description…" aria-label="Filter pages" autocomplete="off" spellcheck="false" />+ <input id="sm-filter-input" type="search" placeholder="Filter 820 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>@@ -111,6 +111,14 @@<span class="sm-desc">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.</span></a></li>+ <li>+ <a href="/docs/draft-agent-mint">+ <span class="sm-new-date">Aug 14, 2026</span>+ <span class="sm-title">Docs · Draft Agent Mint</span>+ <span class="sm-path">/docs/draft-agent-mint</span>+ <span class="sm-desc">Every finished reconstruction is stored durably and minted as a draft on-chain agent identity: the Solana leg, the ERC-8004 leg, the flags that arm each one, and how to prove the whole path on devnet.</span>+ </a>+ </li><li><a href="/docs/agent-index"><span class="sm-new-date">Aug 14, 2026</span>@@ -167,14 +175,6 @@<span class="sm-desc">Join the open inference network: the node-operator client registers your machine, claims inference jobs, executes them with a real open model, and returns Ed25519-signed results anyone can verify. Covers install, config, the wire contract, GPU Docker, and the local end-to-end proof.</span></a></li>- <li>- <a href="/docs/github-memory-seeding">- <span class="sm-new-date">Aug 12, 2026</span>- <span class="sm-title">Docs · GitHub memory seeding</span>- <span class="sm-path">/docs/github-memory-seeding</span>- <span class="sm-desc">Give an agent your work: your public GitHub profile plus the repositories and READMEs you pick, distilled into long-term memory so the agent speaks concretely about what you build instead of guessing. Consent is explicit and revoking it deletes every memory the grant produced.</span>- </a>- </li></ul></section><nav class="sm-toc" aria-label="Sections">@@ -192,7 +192,7 @@</nav><section class="sm-section" id="main"><header>- <h2>Main<span class="sm-count" data-count>51</span></h2>+ <h2>Main<span class="sm-count" data-count>52</span></h2><p class="sm-section-desc">Entry points into the product.</p></header><ul class="sm-list">@@ -553,6 +553,13 @@<span class="sm-desc">Index of live demos across the platform: viewers, agents, payments, and experiments.</span></a></li>+ <li>+ <a href="/demos/agents">+ <span class="sm-title">Agent Interaction Lab<span class="sm-badge sm-badge-internal">internal</span></span>+ <span class="sm-path">/demos/agents</span>+ <span class="sm-desc">Fourteen prototypes exploring how a 3D agent physically inhabits a web page: real gravity, page elements as the playground, and the agent reacting to scroll, clicks, and the cursor.</span>+ </a>+ </li></ul></section>@@ -2255,7 +2262,7 @@<section class="sm-section" id="learn"><header>- <h2>Learn<span class="sm-count" data-count>361</span></h2>+ <h2>Learn<span class="sm-count" data-count>362</span></h2><p class="sm-section-desc">Docs, tutorials, and reference.</p></header><ul class="sm-list">@@ -2553,6 +2560,13 @@<span class="sm-desc">Drive a 3D avatar's face live from your webcam in the browser: MediaPipe face landmarks mapped to ARKit blendshapes, smoothing, record and replay, and save.</span></a></li>+ <li>+ <a href="/docs/draft-agent-mint">+ <span class="sm-title">Docs · Draft Agent Mint</span>+ <span class="sm-path">/docs/draft-agent-mint</span>+ <span class="sm-desc">Every finished reconstruction is stored durably and minted as a draft on-chain agent identity: the Solana leg, the ERC-8004 leg, the flags that arm each one, and how to prove the whole path on devnet.</span>+ </a>+ </li><li><a href="/docs/selfie-to-avatar"><span class="sm-title">Docs · Selfie to Avatar</span>@@ -3593,14 +3607,14 @@<a href="/docs/vaults"><span class="sm-title">Docs: USDC agent vaults</span><span class="sm-path">/docs/vaults</span>- <span class="sm-desc">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, under "Back-an-Agent Vaults". Read that first.</span>+ <span class="sm-desc">A vault lets strangers put real USDC behind one trading agent, on terms the agent's owner publishes up front. The deep reference: every route and who may call it, the share and fee math, the guards in front of a trade, and the public audit ledger.</span></a></li><li><a href="/docs/user-wallet"><span class="sm-title">Docs: Your master wallet</span><span class="sm-path">/docs/user-wallet</span>- <span class="sm-desc">Every three.ws agent owns a wallet (agent-wallets.md). Separately, every user account can own one custodial wallet of its own: the master wallet. It is the financial hub for the person rather than the bot.</span>+ <span class="sm-desc">Every user account can own one custodial wallet: the master wallet, the financial hub for the person rather than the bot. Provision it, read balances, send SOL or any SPL token, fund an agent, and read its on-chain history, with the spend safeguards on each route.</span></a></li><li>@@ -3642,7 +3656,7 @@<a href="/docs/press-kit"><span class="sm-title">Docs: Press kit</span><span class="sm-path">/docs/press-kit</span>- <span class="sm-desc">Everything a journalist, analyst, conference organiser, or partner needs to write about three.ws: the marks, the announcement graphics, approved boilerplate at three lengths, the fast facts, and the rules that govern all of it.</span>+ <span class="sm-desc">Everything a journalist, analyst, conference organiser, or partner needs to write about three.ws: the marks, the announcement graphics, approved boilerplate at four lengths, the fast facts, and the rules that govern all of it.</span></a></li><li>@@ -5088,7 +5102,7 @@<a href="/legal/privacy"><span class="sm-title">Privacy Policy</span><span class="sm-path">/legal/privacy</span>- <span class="sm-desc">How three.ws handles user data.</span>+ <span class="sm-desc">What data three.ws collects, why we hold it, who we share it with, how long we keep it, and the controls you have over it.</span></a></li><li>