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): publish the relay room-tracking, connect-state and API memory entries
nirholasc92f8b113b3e
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex 42748f060..465b35586 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -6,10 +6,17 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr## 2026-09-09+- **Docs · Fade Radar** (`/docs/fade-radar`): How the Fade Radar scores a coin's buy side: what makes a wallet a reverse indicator, the 0 to 100 fade score, the verdict bands, and the out-of-sample measurement behind them.+- **Fade Radar: the wallets that are never right** (`/fade`): The inverse of the Smart Money Radar. Every pump.fun coin ranked by how much of its buy side comes from wallets with a judged on-chain record and not one winner in it, with the measured, out-of-sample odds behind each verdict.+- **A link that opens your house in 3D now really opens it in 3D**: The live home page remembers whether you last looked at your house in 3D or as a room list, which is what you want when you open it yourself. It was also overruling links that asked for one view by name: once you had used the 2D view even once on a device, every /smart-home/<id>?view=3d link on that device quietly opened flat again. That matters for the two cases the parameter exists for, a link you share with someone in the house and the address a kitchen or wall display is pinned to. A view asked for in the link now wins, for 3D, 2D and the floorplan alike, and following such a link no longer overwrites the preference that device chose for itself. (`/docs/home-scene`) `[fix]`+- **An app key can no longer say yes to unlocking your door**: A person saying yes is the one thing that stands between an agent and your front door, and we found a way around it. If you had ever issued an API key or connected an app to your three.ws account, that key could send an unlock request with the "the owner already approved this" flag set, and the lock opened, with nobody asked and nothing to click. We reproduced it against a real house and a real deadbolt before fixing it. Two things changed. Only a signed-in browser session can say yes now: a key or a connected app can ask to unlock, open or disarm, and is always answered with "a person has to approve this", exactly as the agent in your chat window already was. And the home permissions you approve when you connect an app are now actually enforced on every home request, so an app you gave read-only access to, or one you never gave home access at all, is refused instead of let through. Nothing legitimate changed: your agent still asks, you still approve, the door still opens. (`/smart-home`) `[security, fix]`- **Arm your agent stops telling signed-out visitors to create an agent, and shows them the live conviction stream instead**: A full audit of /oracle/arm found that anyone not signed in was shown “Create a 3D agent to arm it”, a dead end for a visitor with no account, and the rest of the page was hidden behind it. Signing in now gets its own state with sign-in and register buttons, and the live “clearing your bar” preview plus the 30-day win-rate readout stay on screen for everyone, because both run on public data. If the agents list itself fails to load, the page now says so with the status it got back and a Try again button, instead of pretending the account is empty. Four more fixes went with it: the arm switch and the two rule toggles can now be operated from the keyboard (they were focusable but did nothing on Enter or Space), coin artwork routes through the site image proxy so icons stop failing on IPFS gateways, the status line no longer flips back to “Disarmed” when the translation catalog lands after the page has rendered, and every form field now has a real label attached to it. (`/oracle/arm`) `[fix, improvement]`- **Avatars and token art load again on sites that embed three.ws**: Assets served from /cdn (avatars, thumbnails, generated models) are read from our object store with a signed request, and when that request is rejected the route falls back to the store's public address so the bytes still arrive. That fallback was a redirect, and a redirect throws away the cross-origin permission the route grants: browsers re-check permission at the redirect's destination, and the public address grants none. Measured from an outside site, every one of those reads failed outright, which took down model previews on pages that load art through the proxy and silently broke third-party embeds of three.ws avatars. The bytes are now served through three.ws itself rather than pointed at, so the permission, the file type and the download rules all survive the fallback, partial reads for video and audio keep working, and a file that genuinely is not there says so instead of reporting a server fault the page retries forever. It also keeps the fallback off the rate-limited public address, which is the whole reason the proxy exists. `[fix]`+- **Connecting a home: the page now says which state it is in, out loud**: Two moments on /smart-home were doing the right thing silently. Typing an address that can never work (a 192.168 number, a .local name) has always put the reason under the field straight away, before anything is sent, but the message was carried by colour alone and a screen reader never read it out; it is now announced the moment it appears, and marked in a way that does not depend on seeing red. And a house that has stopped answering, is refusing the stored token, or has simply gone quiet is now labelled as such by the page itself rather than only in the sentence on its card. Nothing about what you see moves: the last known summary of your house stays exactly where it was, with how long ago it last answered, because a home that went quiet should never look like a home that was deleted. (`/smart-home`) `[improvement, fix]`- **Endpoint Shopper fits a phone, and says something useful when a run finds nothing to buy**: A full audit of /shopper, the page where you describe a task, set a budget, and let an agent shop the x402 Bazaar for endpoints that can answer it. Three things were wrong. A run that came back with no plan and no answer, which is what happens when nothing in the Bazaar matches the task or everything that does prices above your ceiling, painted an empty white column and stopped: no explanation, no way forward. That case now says no endpoints matched, quotes the task back, and offers the three things that change the outcome (rewrite the task, raise the budget, browse the Bazaar) plus a button to run again. Second, when the request could not reach us at all, the page showed the browser's own wording for a dropped connection, which names no cause and suggests no fix; it now says the agent service could not be reached and what to do about it. Third, on a phone narrower than 560px the four navigation links were squeezed into a strip about 76px wide and had to be dragged sideways a few pixels at a time to read; they now wrap onto their own full-width row. Alongside those: the results column announces itself to a screen reader while a run is in flight and when it settles, the Task label sits above its box as intended rather than beside it, and an internal ticket number that had been sitting in the page's headline label since launch is gone. (`/shopper`) `[fix, improvement]`- **Ethereum wallets load on the portfolio page again, keylessly, and every token logo shows up**: A full audit of /portfolio, where you paste any Solana or Ethereum address and get a live portfolio. The Ethereum half had gone dark: the single provider behind it ran out of monthly capacity, so every 0x address answered "Data source unavailable" with nothing behind it. Ethereum now has the same keyless floor Solana has always had. The ETH balance comes from the public Ethereum nodes the rest of the platform already uses, the token list with its prices and icons comes from a public block explorer, and the 24h move comes from the same market source the Solana side uses, with the coverage it achieved stated on the card. The Data panel names whichever lane actually answered, so you can see whether you are reading the paid provider or the free one. Token logos were another visible break: the page pointed your browser straight at an IPFS gateway, which the browser refuses on cross-origin grounds, so every holding fell back to a three-letter monogram and your address bar handed your IP to the gateway on every load. Logos now come through three.ws, sized for the row. Keyboard users could tab onto a slice of the allocation donut and get nothing: the tooltip was wired to an event handler property that browsers do not actually support, so it never fired once; the slice now names its asset and share, and Escape dismisses it. When a lookup fails, the page now shows the reason the server actually sent instead of a generic sentence, and clicking Retry after a rejected address no longer silently reloads the wallet you looked at before it. Underneath, the fallback that names Solana tokens when the primary metadata source is out of quota had never run at all, because of a missing import; token symbols and names come back on that path. (`/portfolio`) `[fix, improvement]`+- **Fade Radar: the wallets that have never once been right, and the coins they are crowding into**: The Smart Money Radar tells you which proven winners are buying a coin. Fade Radar is the other half of that question, and on pump.fun it turns out to be the sharper one: how much of a coin's buy side is money that has never been right. A wallet joins the reverse-indicator board only after five coins it bought have a known outcome and not one of them won, which is a bar a surprising number of addresses clear. The new page ranks every launch from the last few hours by how much of its observed buy side belongs to those wallets, by wallet count and by SOL, and carries a second board of the wallets themselves with their full record. The number above the board is the part we care most about: it is measured, not asserted. We rebuild the reverse-indicator group using only coins whose outcome was known before the coins it is graded on existed, then check what actually happened. Coins where a quarter or more of the buyers were reverse indicators went on to win 1.8 percent of the time, against 22.1 percent for coins with none, across 26,626 labelled coins. Nothing here is a short and nothing signs anything: on a bonding curve the only tradeable form of a fade is not buying, so every action on the page is a link out to the coin, its intel, or a wallet's track record. Wallet links also now open directly on the Smart Money Radar, so an address cited anywhere on the platform lands on its record instead of a board you have to scan by eye. (`/fade`) `[feature]`+- **Homes connected through the relay now follow the house when you rearrange it**: If your Home Assistant is only reachable inside your house, three.ws reaches it through the three.ws integration you install there, which dials out to us. Those homes were building their room list once, when the connection opened, and then quietly ignoring changes: assign a lamp to the kitchen, rename a floor, add a device, and the 3D house kept showing the old arrangement until the connection happened to be rebuilt. Homes connected by a direct address never had this problem, and the split was in the relay, which was not carrying the four small notices Home Assistant sends when its rooms, floors, devices or entities change. It carries them now, so both kinds of connection track the house the same way and updates land in seconds. The notices only say that something changed; the relay already read the full room and floor lists, so nothing new about your house is exposed by this. (`/smart-home`) `[fix, infra]`- **Oracle: a failed request now says so, instead of claiming no coins have been scored**: A full audit of /oracle, the fused conviction board for pump.fun launches. When a panel's request failed, the page told you the opposite of the truth: the live feed claimed "Oracle is warming up" and said the engine ships with its backend, the movers, proof, agent-ranking, activity and 3D-graph panels each claimed there was simply nothing to show, and the performance record said the edge was still proving itself. Every one of those is now a real error state that names what went wrong (offline, rate limited, or an engine error) and offers a retry that actually recovers. The Proof gallery had a second bug behind that one: opening it for the first time while the request failed painted nothing at all, not even a skeleton. Searching a symbol Oracle has not scored used to make the results dropdown vanish with no explanation, which reads as a broken search box; it now says there is no match, and says so differently when search itself is down. The conviction-breadth bar's tier segments and legend chips were 10 and 15 pixels tall, too small to reliably tap on a phone, and now carry a full 24-pixel target without changing how the bar looks. Screen readers can finally move from a tab into the panel it opens, every button declares its type, and if a browser is holding a cached copy of an older release the 3D graph explains that and offers a reload instead of retrying a module that can never load. (`/oracle`) `[fix, improvement]`- **Paid 3D services now refuse a job they cannot deliver, instead of charging for it**: The paid three.ws forge services sold to other AI agents charge the moment the generator accepts a job, and the finished model reaches the buyer only after it lands in our delivery storage. When that storage stopped accepting writes, jobs were still being accepted and charged while no model could ever be handed back. Those services now check that delivery storage is writable before they take the job: if it is not, the call is refused, says so, and is not charged. The check is cached and ignores a one-off blip, so a passing wobble never stops the services selling. The free public health page also had a bug where a storage failure replaced the name of the failing subsystem with the storage provider's error code and printed the request's signing details; it now names the subsystem and reports the reason alone. `[fix, security]`- **Pay-per-call is keyboard-drivable, and it now tells you when the wallet lane is down instead of sitting on a spinner**: A full audit of /pay, the page where an agent pays $0.001 USDC on Solana per call to a paid API. Three things were quietly broken. The wallet pill kept reverting to "loading" after it had already shown a real balance: the page fills that pill from a live balance lookup, but the translation pass that runs a moment later put the placeholder back over it, and the same race hit the session ticker and the wallet setup dialog. Those slots are now marked as owned by the page, so a rendered balance stays put. The whole wallet picker was unreachable without a mouse, because each wallet was a clickable box rather than a button; every wallet is now a real button that tab reaches, Enter and Space activate, and a screen reader announces as selected or not. Both dialogs (the first-visit walkthrough and the wallet setup prompt) now take focus when they open, close on Escape, hand focus back to whatever opened them, and stay hidden from screen readers while closed. States are honest now too. When the agent wallet service is unreachable the page used to tell a signed-out visitor to create their first agent, which was never the problem; it now says wallets are unavailable and offers a Retry that re-runs the lookup without a page reload. A failed activity feed used to leave a row of dots ticking forever and now says the feed is unavailable. The page also gained the heading it never had, one high-contrast focus ring across every control, and a copy pass that removed the long dashes from its description and on-page text. (`/pay`) `[fix, improvement]`@@ -27,6 +34,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr- **The 3D Playground recovers when a model will not load, and now works from the keyboard**: Dropping a .glb into /playground had exactly one failure mode: a dimmed screen and a spinner that never stopped. If the file was corrupt, the download stalled, or the 3D viewer script itself was blocked, nothing on the page said so and there was no way back. That spinner is now a shimmer inside the viewer frame instead of a curtain over the whole page, so the controls stay usable while a model streams, and a failure lands in a designed error card that names what went wrong and offers Retry or a file picker. A load that never finishes gives up after 25 seconds rather than hanging forever. The lighting presets no longer strand the scene on the previous preset’s exposure. The page also gained the structure it was missing: a real heading that says what it is for, headings on every control group, an accessible name on each switch, slider and field, a focus ring on everything you can tab to, and an upload button the keyboard can actually reach (it was hidden with display:none, which drops it out of the tab order entirely). On a phone the top navigation scrolls instead of vanishing. Animation names read out of an uploaded file are rendered as text, never as markup. (`/playground`) `[fix, improvement]`- **The agent-wallet demo pays again when an endpoint asks the buyer to cover its own network fee**: On /play/agent-wallet a 3D avatar walks up to a paid x402 endpoint and buys a live market signal with real USDC on Solana. The page had gone quiet. three.ws's own paid endpoints switch to a self-pay payment challenge whenever the wallet that normally sponsors the Solana network fee cannot co-sign, and the bridge behind the page only knew how to build a sponsored payment, so every price quote came back as a server error and the demo never got past its connecting state. The bridge now signs both kinds: when no sponsor is offered, the agent wallet pays its own network fee, exactly as the platform's own payment ring already does. Four smaller things came with it. The page no longer offers a Pay button it knows will fail: when the agent wallet cannot cover the quoted price it says so and leaves the deposit address in front of you. Switching between BTC, ETH and SOL re-prices immediately instead of waiting for the next payment. The wallet balance and the Pay button stop reverting to placeholder text a few seconds after they load, which the translation pass had been overwriting. And the page carries a real page heading for screen readers and search engines, which it had been missing entirely. (`/play/agent-wallet`) `[fix, improvement]`- **The Animation Studio names itself for screen readers, and its empty timeline is legible on a phone**: A full audit of /pose, where you pose an avatar and keyframe an animation. The page had no top-level heading at all: assistive technology jumped straight into "Selection" with nothing saying which studio you were in, so "Animation Studio" in the breadcrumb is now the page's real heading. The status pill above the canvas is the studio's only error surface (it is what tells you an import failed, an avatar could not be loaded, or that you need a keyframe before saving) and it never announced anything; it is now a live region, so those messages are spoken as they appear. On a 320px screen the empty-timeline hint ("Pose the figure, then press K") wrapped across the ruler's second markings and both became unreadable; the ruler now stays out of the way until you have keyframes to measure, and returns the moment you add one. Loading an avatar could also fail into a dead end: the picker said "Failed to load: Failed to fetch" with no way forward, and now explains whether the request reached three.ws and offers a Try again button. Behind that, a slow first CDN could make the 3D preview library load twice and throw an error into the console; a second load is now ignored. (`/pose`) `[fix, improvement]`+- **The API container keeps the memory it was sized for, so a busy hour cannot take the whole site down**: Every three.ws page and API call is served by one container, and in early September that container was given twice the memory so it could hold live connections to people’s connected homes without ever running short. The setting did not survive: the next full deploy quietly put it back to the smaller limit, and the site then ran for five days on half the memory it had been sized for while still being configured to hold up to 600 home connections. Measured over the last 24 hours, memory was already peaking at 86% of that smaller limit before a single home connection was counted, which is close enough to the edge that a busy hour could have killed the container mid-request and taken every page down with it, not just the connected-home part. The limit is restored, peak memory is back to 43%, and it is now written into the deploy configuration itself so no future deploy can undo it again. `[fix, infra]`- **The Coin Wars arena reconnects to its battle server, and a link with no battle now shows you where the wars are**: A full audit of /play/war, the arena where two coin communities fight to the kill cap. The page had lost the address of the multiplayer server it joins, so every player walking through a war portal landed on 'The arena server is unreachable' instead of a battlefield; the arena is wired back up. Beyond that, a link with no pairing (a shared URL, an expired ticket, a battle that already finished) used to be one sentence and a button back to the lobby, which told you nothing about where a war actually is. It is now the war room: the battles running right now with their live score and clock, the communities queued for an opponent, and the top of the Elo ladder, each one a link into that coin's world where its war portal stands. The same panel sits under every other dead end, so 'there is no battle here' always comes with 'here is where one is'. Also fixed: a failed holder check used to show an internal service error instead of telling you what to do, the Fire button announced itself as 'Firespace' to screen readers, pressing Space on the result card did nothing because the arena was eating the key, and the HUD's hover and focus animations were dead because the page never loaded the site's motion tokens. The arena now says it is playable with WASD, moves focus onto the way out when a card appears, and reads cleanly from 320px up. (`/play/war`) `[fix, improvement]`- **The economy solver says which level its numbers belong to, and shares a link that lands on them**: The solver at /play/solver reprices the whole /play world when you move the skill level, and it fetches the new level as you move. If that fetch failed, the page dimmed its tables slightly and said nothing else: the chart marker sat at level 60 while every table below it still held level 1 figures, with no visible explanation, no way to tell which level you were reading, and no retry. The explanation existed but was written only into a region screen readers can reach, so anyone looking at the page saw a silent mismatch. A failed level now raises a banner in the open that names the level that failed, says plainly that the figures below are still the old level, and offers both a retry and a way back. A level still loading shows the same banner as a busy state with the level it is solving, so a slow connection reads as slow rather than as broken. The page also writes the level into its own address bar now: it has always read a level from a shared link, but never wrote one, so sending someone the URL after dragging to level 60 sent them level 1. And a link asking for a level past the cap settles on the cap instead of leaving the page waiting on a level that will never arrive. Alongside it, a conclusion in the model that shouted one word in capitals now reads as a normal sentence. (`/play/solver`) `[fix, improvement]`- **The floorplan editor can make rooms, so a home with no areas is no longer a dead end**: Most Home Assistant setups we see have devices everywhere and not a single area, which left the 3D home and the floorplan with nothing to draw and the only advice we could give was to go and create areas in Home Assistant's own settings first. That is a chore people leave to do and do not come back from. The floorplan editor now makes the room itself: name it, and the area is created in your own Home Assistant, placed on the plan, and the device that prompted it is filed into it in the same step. It reaches your dashboards, your voice assistant and your automations too, because it is a real area in your registry and not a picture of one here. The tray tells a home with no rooms where to start, and a device you file no longer leaves a stale entry behind in the list. (`/smart-home`) `[feature, improvement]`@@ -34,9 +42,11 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr- **The in-game economy page reads correctly on a phone, and the boutique shows what you are buying**: A full audit of /play/economy, the published reference for every price, prize and gate in the /play world. On a 320px screen the general store and currency panels were wider than the viewport, and because the page suppresses sideways scrolling their right edge was simply cut off: the store's price column was unreachable on the narrowest phones. Those panels now shrink to fit, and the wide tables scroll inside their own labelled box instead. The bar showing how a paid $THREE sale splits used to print its labels inside the coloured segments, where "50% holder rewards" was truncated to "50% holder re..."; the split now reads from a legend beneath the bar, which stays legible at any ratio. In the boutique, the Stetson and the Shades rendered as blank grey circles while the five colour items showed their colour, because the page ignored the thumbnail the server was already sending; both now show the item, with the colour swatch as the fallback if an image ever goes missing. The wheel's top prize is relabelled "JACKPOT: 100 Cash", and a failed load now reads as a proper sentence before the retry hint. (`/play/economy`) `[fix, improvement]`- **The Money Pulse now tells you when its stats are down, and retries on the spot**: When the money-intelligence call behind /pulse failed, the three side panels (Top earners, Busiest wallets, Fresh launches) sat on "Loading..." forever and the 7-day activity strip went blank, which reads as "the platform is quiet" rather than "we could not fetch this". Each surface now says what went wrong, notes that the live feed itself is unaffected and that it retries every minute, and offers a Retry button that refetches immediately. First paint uses skeletons shaped like the real counters, bars and rows instead of dashes and a loading label, so nothing shifts when the numbers land. The empty states point somewhere useful now: no tips yet links to the agent directory, no wallet activity links to the agents that are online. Switching between mainnet and devnet shows the skeletons again rather than leaving the previous network's numbers under the new label. The stat cards report their filter state to screen readers, the rail cards are real headings, and the per-row explorer link is a full-size tap target that says where it goes. (`/pulse`) `[fix, improvement]`- **The Object Library is full again: 511 free CC0 props, and the page no longer stalls loading them**: A full audit of /objects, the public-domain prop library. The page had been showing "Object library coming online" to everyone: the 511 props were sitting on the CDN the whole time, but the server read their index over a signed storage connection whose credential had stopped matching, so every visitor got an empty shelf. The index is public data on a public domain, so the read now falls back to that domain when the signed one fails, and the same change refills the character library, the animation clips and the asset catalogue the agent tools search. Browsing is a different page too. It used to build all 511 cards at once, each one a live 3D viewer with its own model, which meant 511 image requests before the first card appeared and about eighteen seconds of nothing. Now it renders 48 at a time, with a Load more button and automatic loading as you scroll, and a card stays a still picture until you rest the pointer on it, at which point that one spins up in 3D; a handful stay live at a time instead of hundreds. The filter row dropped eight chips that were Poly Haven collection names rather than anything you would browse by. On a phone the Preview, AR and Download buttons each get a full-width row instead of three cramped pills. Keyboard focus is now visible on every control, a failed load names the actual reason above its retry button, and the page description no longer contradicts the one in the markup. (`/objects`) `[fix, improvement]`+- **The OKX marketplace chat bot now switches AI providers by itself**: Chat for our OKX.AI listing runs on an always-on host that spawns an AI session to answer buyers. That host held exactly one AI provider, so when the provider's account was put on a billing hold the bot went on receiving every message and answering none of them, for days, while other credentials sat unused on the same service. It now holds an ordered chain of providers, asks each one whether it will actually serve before using it, and moves to the first that answers. A provider that recovers or gets funded is picked up on the next check with no redeploy, and the bot's status page lists what every provider answered, so whoever fixes it can see which one to fix rather than only that one was refused. `[infra, improvement]`- **The OpenAI partner page now proves the free ChatGPT connector is up instead of just claiming it**: The /openai page told readers that a free, keyless 3D connector answers at three.ws/api/mcp-studio and then listed the eleven tools it exposes. Both were claims on a static page. Now the page calls the connector from the reader's own browser on load and reports what came back: live with the tool count and the response time, or a plain explanation and a Check again button if the call was blocked. The printed tool table is reconciled against the same response, so every tool the server really answers with is ticked, one the server has dropped is flagged, and one the server has added since the page was written is appended with its own description. The connector URL and the curl command both got copy buttons, and hover plates on the page no longer turn near-white when the site theme is switched to light. (`/openai`) `[improvement, fix]`- **The Oracle reference now reads the model it is describing**: The complete Oracle documentation at /oracle/docs described version 2 of the conviction model while production had moved on to version 3, and the difference was not cosmetic. Version 3 changed the question the score answers: earlier versions ranked the odds of a spike, and version 3 ranks the odds of a spike that holds, counting a launch as a hit only if a holder who bought at first sight is still up. A coin that ran 3x and gave it all back was a success under the old target and is a miss under the new one, which is why the base rate underneath every figure on the page is far lower than it used to be. The page had the old target, the old tier probabilities and the old holdout numbers throughout, and its roadmap still promised fitted weights and calibration that had already shipped. Every model figure on the page is now read live from the published model card when you open it, because the engine refits itself every six hours behind a promotion gate and any number typed into a document goes stale on a clock. When that read fails the page says so, shows the values it was published with, explains that they may trail production, and offers a retry rather than a blank space. Two public endpoints that existed but were undocumented are now in the reference: the one that publishes the whole scoring machine, weights and holdout curve and the record of every fit ever refused, and the one that publishes the realized win rate per conviction band from real fills. The tier ladder used to truncate its own evidence, cutting off the sample counts on every band below the top, and now gives each band a full line. In light mode the tier names were near-white on a white card and the strongest bands were invisible; they now have their own ramp. (`/oracle/docs`) `[docs, fix]`- **The partner page gets its footer back, fits a narrow phone, and stops naming three partners it does not have**: An end-to-end audit of /partners found it was the only page on the site that carried a footer slot but never loaded the footer, so the whole bottom of the page was missing. It is back. On a 320px phone the partner cards were 38px wider than the screen and the overhanging text was silently cut off, because a card header could not shrink past its logo, name and category chip on one line; the chip now wraps and every card fits. The page description search engines and link previews read was also stale: it advertised Intel, Microsoft and Oracle, none of which have a card, and left out OpenAI and HackerNoon, which do. The AWS card said View on AWS Marketplace above a link to our own AWS page, so it now says what it actually opens. Beyond that: the 8 partners and 22 chains counters are no longer hidden from screen readers and the partner number is now counted from the cards themselves, keyboard users get a visible ring on every card and button, the card lift is dropped for anyone who asks for reduced motion, and the page eyebrow, the four benefit headings and every card call to action are translatable instead of staying English on a translated page. The floating walk companion also got a full-size dismiss, avatar-swap and narration button on touch devices, everywhere it appears. (`/partners`) `[fix, improvement]`+- **The partnership page works properly on the partner's own site**: The IBM partnership page is published once onto IBM's own domain and then keeps itself current by reading from three.ws, so everything it loads is a cross-origin read and anything we get wrong there is invisible on three.ws itself. Three things were wrong. The site-wide command palette asked the partner's server for our page index and for the ranking module it imports, so it never opened and logged an error on every visit: the index now travels with the code the way the language catalogs already do, and both files are readable from other sites. And a build step that adds the site's mobile stylesheet to every page was reaching the partner artifacts too, even though they are copied out untouched by design, so the hosted copy asked IBM's server for a stylesheet only we have. All three are closed, and the audit that loads the page from a foreign domain now passes all four of its checks: the live update applies, the language switcher mounts, the paid demo arms, and the console is clean. `[fix]`- **The pitch deck now shows the whole character, and says so when the 3D cannot load**: The live 3D figure on the deck at /pitch was framed by a camera that cut it off above the chest and pointed at its back, so the slide that says "give your AI a face" showed neither a head nor a face. Both stages now frame the full character from the front. Each stage also ships a still frame rendered from the same glTF file: it fills the panel while the model streams instead of leaving an empty box, and if the 3D runtime is blocked or fails outright the panel says so in the open, drops the "Live" badge that used to sit over nothing, and offers a retry. Navigation got the same pass: the slide dots are now full-size tap targets and step out of the way on a phone, the language picker no longer lands on the slide counter, slide copy no longer runs underneath the nav bar on a tablet, links on hidden slides are out of the keyboard tab order, and every button and link has a visible focus ring. (`/pitch`) `[fix, improvement]`- **The press kit reads in the three.ws typeface, fits a phone, and quotes every mark at its true size**: Every paragraph on the press kit was rendering in the browser default serif on a bare white-ish ground: the page styled its own cards and headings but never applied the site typeface, colour, or background to the document itself, so the one page a journalist opens looked nothing like the rest of three.ws. It now uses the platform design tokens throughout, in both light and dark mode. On a 320px phone the two OpenAI announcement cards were sliced off at the right edge, taking their Download PNG buttons with them, and because the page clips rather than scrolls sideways there was no way to reach what was cut; both card grids now fold to a single full-width column instead. The pixel dimensions printed under each mark were also all slightly wrong, off by a pixel or two from the artwork they labelled, which is the number a designer laying out a conference programme actually acts on. They are corrected, and the brand asset renderer now writes them back from the PNG headers on every build the way it already did for the archive size, so they cannot drift again. Last, the Copy buttons beside the boilerplate did nothing at all when the browser withheld clipboard access; they now select the passage in place and tell you which keys to press. (`/press`) `[fix, improvement]`- **The Pump Visualizer's live counters stopped freezing a few seconds after the page opened**: A full audit of /pump-visualizer, the 3D scene of live pump.fun mints. The status bar across the top counts the tokens in the scene, the mint rate per minute and the total market cap, and about fifteen seconds into every visit all three froze: the counter sat at 0 and the rate and total sat at a dash while the scene behind them kept filling with new coins. The cause was the page's own translation pass. Those three numbers were written inside blocks of translated copy, so the moment the language file arrived the browser rebuilt that copy and threw away the very elements the page was writing into. The numbers now live beside their labels instead of inside them, so the labels still translate into all 85 languages and the values keep counting for as long as the page is open. The per-minute and per-hour units now translate too, which they never did once the page switched between live mints and migrations. The page also gained a heading and a labelled search box for screen readers, and its browser tab now reads Pump.fun Visualizer, three.ws instead of a retired product name. (`/pump-visualizer`) `[fix, improvement]`@@ -49,8 +59,9 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr- **The spend policy dry run stops contradicting its own counters**: The simulator at /pay/simulator reports what an agent budget actually buys, and its headline sentence disagreed with the numbers directly beneath it. An endpoint that answers without asking for payment is free: it costs nothing and is never checked against your policy. The counters knew that, and the sentence did not, so the very first run on the page announced that all seven calls settle while the tile beside it said six. Calls that could not be priced at all vanished the same way, counted nowhere the reader could see. Both now have their own tile, and the verdict sentence is built from the counts it is describing, so settled, free, unpriced and refused always add up to the total in front of you. A run that fails now says why: an unusable line used to produce a bare "Simulation failed (HTTP 400)", and now quotes the endpoint the simulator could not read along with what a working line looks like. A budget left blank was quietly costed against one dollar, giving you a verdict for a budget you never proposed; the answer now says when that substitution happened. On a phone the little question marks beside each field were fifteen pixels wide and their explanations opened off the side of the screen, so the help was unreadable exactly where it was needed most: the tap targets are now large enough to hit and the explanations stay on the page at every width. (`/pay/simulator`) `[fix, improvement]`- **The Splat Viewer keeps its recenter and download controls, and its errors say what went wrong**: Loading a scene on /splat used to erase the viewer's own controls: writing the scene label into the HUD replaced the recenter and download buttons with plain text, so from the first render onward neither existed. Both now live beside the label and survive every scene swap, and the download always offers the scene you are actually looking at rather than a previous one. The error state was worse than useless: it showed a heading over an empty space because the explanation was being written into an element that was not on the page. Now a failed load tells you what happened and what to do, including the advice to download and upload a file whose host blocks cross-origin requests. Clicking a sample or picking a file also shows the loading state immediately instead of sitting on an idle stage while the splat engine downloads in silence, and an engine that fails to load says so rather than leaving the page frozen. (`/splat`) `[fix, improvement]`- **The Windows 11 widget draws its card again, and a new check keeps the board honest**: The Agent glance widget on the Windows 11 widgets board renders an Adaptive Card, and the board fills that card in with its own expression engine rather than with JavaScript. Our card asked for the three stat rows the way JavaScript reads an array, which that engine treats as a syntax error, and it refuses the whole card rather than skipping the one line: a pinned widget came up empty with nothing to show for it anywhere else. The card now uses the syntax the board expects, and there is a new check that fills it in with the board's own engine before anything ships, alongside checks that the manifest, the service worker and the two endpoints still agree with each other. The board is the one surface we cannot open from a build machine, so the checks that stand in for it are the ones that have to be real. (`/glance`) `[fix, infra]`+- **Three fades now stop when you ask the site to stop moving**: Turn on reduced motion in your operating system and three.ws is supposed to hold still: every animation timing on the site is named rather than spelled out, so one switch can zero all of them at once. Three places had drifted off that and spelled their own timing instead, which meant the object library card fade, the avatar picker chips and the Money Pulse rows kept animating for people who had explicitly asked them not to. One of them was pointing at a timing name that does not exist, so the value it fell back to was never the one anyone chose. All three are back on the named ladder at the same speed they always looked, and the reduced-motion switch reaches them again. (`/objects`) `[fix, improvement]`- **When the payment wallets look empty, the self-heal now says whether they are empty or just fenced**: The x402 payment rail keeps a set of platform wallets topped up from one funding root, and a recovery run reports why it could not draw on each source. Every source that held less than its configured floor reported the same thing: "at or below floor". That single phrase covered two opposite situations. A wallet holding nothing needs money added from outside. A wallet holding real funds behind a floor somebody set does not: the platform already owns that money, and a floor decision releases it. Because the two printed identically, three separate investigations of the same stalled rail concluded the platform was out of funds while one of its own wallets held roughly forty-five times what the stalled wallet was short. A skipped source now reports how much it is holding and the line it had to stay above, and every run totals the funds it left behind, so an operator can tell at a glance whether the recovery needs a deposit or a decision. The health page and the operations runbook now point at that total instead of asserting that money is required. `[fix, infra]`-- **Your monthly agent turns now count, and locking up never does**: Talking to the agent about your house is the one part of the smart-home lane that can really cost money: the room graph makes a home prompt large, and on a paid model a single turn costs more than a year of holding that house’s connection open. Those turns were being counted but never actually limited. They are now, against the monthly allowance shown on your plan page, and if you run out the agent says so in a sentence that names the limit, the date it resets and where to raise it, instead of failing at you. Two things are deliberately left outside that limit. Asking the agent what the house is doing still works, because you have to be able to see which door is open. And telling it to lock a door, close a garage or a valve, or arm the alarm still runs, over quota, on a paused home, in every state we can put an account in: the safe direction is free, always, on every plan. If our own billing lookup fails, the turn is allowed through rather than refused. (`/smart-home/plan`) `[feature, improvement]`+- **Your monthly agent turns now count, and locking up never does**: Talking to the agent about your house is the one part of the smart-home lane that can really cost money: the room graph makes a home prompt large, and on a paid model a single turn costs several weeks of holding that house’s connection open. Those turns were being counted but never actually limited. They are now, against the monthly allowance shown on your plan page, and if you run out the agent says so in a sentence that names the limit, the date it resets and where to raise it, instead of failing at you. Two things are deliberately left outside that limit. Asking the agent what the house is doing still works, because you have to be able to see which door is open. And telling it to lock a door, close a garage or a valve, or arm the alarm still runs, over quota, on a paused home, in every state we can put an account in: the safe direction is free, always, on every plan. If our own billing lookup fails, the turn is allowed through rather than refused. (`/smart-home/plan`) `[feature, improvement]`- **Your private avatars load on the dashboard again, and say so when they cannot**: Avatars you have not made public were failing to load on your dashboard, with nothing on the page to say why. The dashboard was being handed a temporary direct link into our storage provider rather than a link back through three.ws. When storage stopped accepting our credential, that direct link was refused in a way browsers deliberately hide, so the page could not tell the difference between a refusal and a dead connection: it just showed nothing. Private avatars now load through three.ws itself, which checks that the avatar is yours exactly as before, and which already knows how to fall back to a second copy when storage is having a bad day. As a side effect these links no longer expire, so a dashboard tab left open for an hour still shows your avatars when you come back to it. (`/dashboard/avatars`) `[fix]`## 2026-09-08diff --git a/STRUCTURE.md b/STRUCTURE.mdindex a9e3f77e2..109077169 100644--- a/STRUCTURE.md+++ b/STRUCTURE.md@@ -160,12 +160,12 @@ bottom.| Object Library | [pages/objects.html](pages/objects.html) + [src/objects-library.js](src/objects-library.js) → `/objects`, API [api/objects/library.js](api/objects/library.js) | Live at `/objects` | Hundreds of CC0 (public-domain) 3D props from Poly Haven (packed to GLB on R2, `objects/polyhaven/`). Pipeline: [scripts/fetch-polyhaven-objects.mjs](scripts/fetch-polyhaven-objects.mjs) (glTF→GLB via @gltf-transform) → [scripts/render-glb-thumbnails.mjs](scripts/render-glb-thumbnails.mjs) → [scripts/build-object-library.mjs](scripts/build-object-library.mjs) publishes `objects/library/manifest.json`. Same R2-manifest pattern as the Character/animation libraries (no DB). Cards preview in the 3D viewer (`/app#model=`), place into AR Studio (`/ar/studio?src=`), and download the GLB directly (CC0). AR Studio's tray also has an Objects tab over the same manifest. The grid renders 48 cards at a time (a Load more button, plus an IntersectionObserver that pulls the next chunk as you approach it) and each card is a still thumbnail until you dwell on it, at which point that one card upgrades to a live auto-rotating `<model-viewer>`; at most six stay mounted. The manifest read falls back to the bucket's public CDN domain when the signed S3 read fails (`getPublicObjectBuffer` in [api/_lib/r2.js](api/_lib/r2.js)), so a bad storage credential can no longer empty a library of public CC0 bytes. || Agent-Forged Gallery | [pages/forged.html](pages/forged.html) + [src/forged-gallery.js](src/forged-gallery.js) → `/forged`, API [api/forged.js](api/forged.js), writer [api/_lib/x402/pipelines/forge-content.js](api/_lib/x402/pipelines/forge-content.js) | Live at `/forged` | 3D props BOUGHT by the autonomous x402 agents with real USDC: the hourly forge-content pipeline pays `/api/x402/forge` (draft tier), the generated GLB lands in `forge_autonomous_props` with payment provenance (payer wallet, price, Solana settlement signature), and `/forged` renders each prop with its on-chain receipt linked to Solscan. Honest feed: no synthetic entries; before the first paid generation the page shows its designed empty state. Category chips built from the eight families in [api/_lib/x402/pipelines/forge-catalog.js](api/_lib/x402/pipelines/forge-catalog.js) (club-decor, ar-object, diorama-set, avatar-item, vehicle, container, furniture, terrain), prompt search, newest/priciest/most-novel sorts. || Motion Swap (avatar body-swap in video) | [pages/motion-swap.html](pages/motion-swap.html) `→ /motion-swap` + [src/motion-swap.js](src/motion-swap.js), API [api/motion-swap.js](api/motion-swap.js), worker [workers/model-video2motion/](workers/model-video2motion) | Live | Upload a video of one person, get it back with a 3D avatar performing their motion. The worker (CPU Cloud Run, MediaPipe pose + hands + multiclass person segmentation, all Apache-2.0) tracks 33 body world landmarks plus 21 per hand each frame, solves them onto the canonical Wolf3D skeleton, body and all 30 finger bones, with an in-house bend-plane IK solver ([pose_solver.py](workers/model-video2motion/pose_solver.py), pure NumPy, unit-tested), and emits a standard `AnimationClip.toJSON()` + person-mask video + per-frame screen anchors. The browser composites in one WebGL scene: footage on a shader quad with the subject pixelated under the mask, avatar retargeted via [src/animation-retarget.js](src/animation-retarget.js) and pinned to the subject's anchor each frame, MediaRecorder export with original audio. Provider mode `video2motion` (`GCP_VIDEO2MOTION_URL`) in [api/_providers/gcp.js](api/_providers/gcp.js). Docs: [docs/motion-swap.md](docs/motion-swap.md). Tests: [test_pose_solver.py](workers/model-video2motion/test_pose_solver.py) (solver) and [test_service.py](workers/model-video2motion/test_service.py) (HTTP contract, ffmpeg normalize/mask encode, SSRF guard, live MediaPipe pass). |-| Smart home (`/smart-home`) | Page [pages/smart-home.html](pages/smart-home.html) `→ /smart-home` and `/smart-home/:id` + [src/home/](src/home) (connect, manage, scene-model, scene-render, scene-fallback, satellite, satellite-link, pcm-player, plan, api). Store [api/_lib/home/store.js](api/_lib/home/store.js), runtime + backpressure [runtime.js](api/_lib/home/runtime.js) + [admission.js](api/_lib/home/admission.js), gate + tools [tools.js](api/_lib/home/tools.js) + [confirm.js](api/_lib/home/confirm.js), roster [members.js](api/_lib/home/members.js), privacy [privacy.js](api/_lib/home/privacy.js), plans + quotas [entitlements.js](api/_lib/home/entitlements.js) + [usage.js](api/_lib/home/usage.js), SSRF pin [api/_lib/home-url-guard.js](api/_lib/home-url-guard.js). HTTP [api/home/](api/home) (index, [id], [id]/call, [id]/activate, [id]/stream, [id]/grants, [id]/members, [id]/confirm, invites/[token], pair, pair/redeem, privacy, plan). Client [packages/home-bridge/](packages/home-bridge/README.md), MCP server [packages/home-mcp/](packages/home-mcp/README.md), hosted MCP tools [api/_mcp/tools/home.js](api/_mcp/tools/home.js). Dial-out for LAN-only houses [services/home-relay/](services/home-relay/README.md) + [home-assistant-integration/](home-assistant-integration) (HACS). Voice [services/home-satellite/](services/home-satellite/README.md) (Wyoming). Harness [scripts/home-test-instance.mjs](scripts/home-test-instance.mjs), load fleet + envelope + chaos [scripts/home-fleet.mjs](scripts/home-fleet.mjs) / [scripts/home-load.mjs](scripts/home-load.mjs) / [scripts/home-chaos.mjs](scripts/home-chaos.mjs) (`npm run home:fleet`, `home:load`, `home:chaos`). Migrations `api/_lib/migrations/*_home_*.sql` | Live | The agent past the screen and into the building. **Zero device code, ever:** Home Assistant owns Zigbee, Z-Wave, Matter, Thread, BLE and 1,500 integrations, and three.ws is the layer in between: a connection record with the token encrypted at rest, a pooled per-home WebSocket, a room graph the 3D scene renders live, intent resolved to the household's own scenes, and one gate in front of everything. **The gate is the product decision:** reads are free, moves toward safety (lock, close, arm) run immediately and never prompt, and moves that OPEN the house (unlock, open a door/gate/garage, disarm) never run from a model call at all. They mint a pending confirmation a signed-in person redeems at `POST /api/home/:id/confirm`, which refuses every bearer principal including one holding `home:act`. It exists because Home Assistant's own `intent__HassTurnOff` is documented as performing an **unlock** on a lock, verified live. Entity and area names are untrusted input travelling in `structuredContent`, never interpolated into prose. Three reachability answers, all shipped: a remote https URL, a browser or MCP server inside the network, and the HACS integration that dials out so no Home Assistant credential ever leaves the house. Docs: [docs/smart-home.md](docs/smart-home.md), [docs/tutorials/connect-your-home.md](docs/tutorials/connect-your-home.md), [docs/home-households.md](docs/home-households.md), [docs/home-privacy.md](docs/home-privacy.md), [docs/home-plans.md](docs/home-plans.md), [docs/ops/home-operations.md](docs/ops/home-operations.md) (SLOs, the alerts, the measured scale envelope, the backpressure ladder, the seven chaos scenarios and the Cloud Run sizing). Evidence: [tasks/home/](tasks/home). Tests: `tests/home-*.test.js`, [tests/e2e/home-connect.spec.js](tests/e2e/home-connect.spec.js), [packages/home-bridge/tests/](packages/home-bridge/tests), [packages/home-mcp/tests/](packages/home-mcp/tests) |+| Smart home (`/smart-home`) | Page [pages/smart-home.html](pages/smart-home.html) `→ /smart-home` and `/smart-home/:id` + [src/home/](src/home) (connect, manage, scene-model, scene-render, scene-fallback, satellite, satellite-link, pcm-player, plan, api). Store [api/_lib/home/store.js](api/_lib/home/store.js), runtime + backpressure [runtime.js](api/_lib/home/runtime.js) + [admission.js](api/_lib/home/admission.js), gate + tools [tools.js](api/_lib/home/tools.js) + [confirm.js](api/_lib/home/confirm.js), roster [members.js](api/_lib/home/members.js), privacy [privacy.js](api/_lib/home/privacy.js), plans + quotas [entitlements.js](api/_lib/home/entitlements.js) + [usage.js](api/_lib/home/usage.js), SSRF pin [api/_lib/home-url-guard.js](api/_lib/home-url-guard.js). HTTP [api/home/](api/home) (index, [id], [id]/call, [id]/activate, [id]/stream, [id]/grants, [id]/members, [id]/confirm, invites/[token], pair, pair/redeem, privacy, plan). Client [packages/home-bridge/](packages/home-bridge/README.md), MCP server [packages/home-mcp/](packages/home-mcp/README.md), hosted MCP tools [api/_mcp/tools/home.js](api/_mcp/tools/home.js). Dial-out for LAN-only houses [services/home-relay/](services/home-relay/README.md) + [home-assistant-integration/](home-assistant-integration) (HACS). Voice [services/home-satellite/](services/home-satellite/README.md) (Wyoming). Harness [scripts/home-test-instance.mjs](scripts/home-test-instance.mjs), unroutable-LAN relay rig [scripts/home-relay-live.mjs](scripts/home-relay-live.mjs) + [scripts/home-relay-e2e.mjs](scripts/home-relay-e2e.mjs) + [scripts/home-relay-gate-proof.mjs](scripts/home-relay-gate-proof.mjs), load fleet + envelope + chaos [scripts/home-fleet.mjs](scripts/home-fleet.mjs) / [scripts/home-load.mjs](scripts/home-load.mjs) / [scripts/home-chaos.mjs](scripts/home-chaos.mjs) (`npm run home:fleet`, `home:load`, `home:chaos`). Migrations `api/_lib/migrations/*_home_*.sql` | Live | The agent past the screen and into the building. **Zero device code, ever:** Home Assistant owns Zigbee, Z-Wave, Matter, Thread, BLE and 1,500 integrations, and three.ws is the layer in between: a connection record with the token encrypted at rest, a pooled per-home WebSocket, a room graph the 3D scene renders live, intent resolved to the household's own scenes, and one gate in front of everything. **The gate is the product decision:** reads are free, moves toward safety (lock, close, arm) run immediately and never prompt, and moves that OPEN the house (unlock, open a door/gate/garage, disarm) never run from a model call at all. They mint a pending confirmation a signed-in person redeems at `POST /api/home/:id/confirm`, which refuses every bearer principal including one holding `home:act`. It exists because Home Assistant's own `intent__HassTurnOff` is documented as performing an **unlock** on a lock, verified live. Entity and area names are untrusted input travelling in `structuredContent`, never interpolated into prose. Three reachability answers, all shipped: a remote https URL, a browser or MCP server inside the network, and the HACS integration that dials out so no Home Assistant credential ever leaves the house. Docs: [docs/smart-home.md](docs/smart-home.md), [docs/tutorials/connect-your-home.md](docs/tutorials/connect-your-home.md), [docs/home-households.md](docs/home-households.md), [docs/home-privacy.md](docs/home-privacy.md), [docs/home-plans.md](docs/home-plans.md), [docs/ops/home-operations.md](docs/ops/home-operations.md) (SLOs, the alerts, the measured scale envelope, the backpressure ladder, the seven chaos scenarios and the Cloud Run sizing). Evidence: [tasks/home/](tasks/home). Tests: `tests/home-*.test.js`, [tests/e2e/home-connect.spec.js](tests/e2e/home-connect.spec.js), [packages/home-bridge/tests/](packages/home-bridge/tests), [packages/home-mcp/tests/](packages/home-mcp/tests) || Sign Language (feature home) | [pages/sign-language.html](pages/sign-language.html) `→ /sign-language` + [src/sign-language-page.js](src/sign-language-page.js) | Live | The front door for signing avatars: a live avatar signing on arrival (PoseStage + [src/sign-speech.js](src/sign-speech.js) SignSpeaker, portrait-framed), an input that signs or spells anything you type (reporting which words were which), a playable vocabulary of every word with a real sign, and an embedded webcam sign-recognition demo. Controls for signing speed, left- vs right-handed signing, and which avatar signs: [src/sign-avatars.js](src/sign-avatars.js) owns the shared rig list, the one preference block every signing surface reads, and the Avatar pill group whose third pill opens the avatar gallery, so any avatar you own (or any public one) signs with the same vocabulary; a rig with no usable skeleton is rejected with a named message and the working rig is remounted. Verified in a real browser by `npm run verify:sign-avatar` ([scripts/verify-sign-avatar.mjs](scripts/verify-sign-avatar.mjs)). Engines: [src/sign-rig.js](src/sign-rig.js) (skeleton measured from the bind pose → forward kinematics, two-bone arm IK, and hand geometry, so a sign is authored as a place in signing space or as CONTACT, "fingertips on the palm", never as joint angles), [src/sign-handshapes.js](src/sign-handshapes.js) (A, Z, 0, 9, and the named shapes), [src/sign-clip.js](src/sign-clip.js) (resting signer, phase poser, non-manual face markers, eased timeline → clip JSON), [src/sign-dictionary.js](src/sign-dictionary.js) (the lexical vocabulary, one- and two-handed), [src/fingerspelling.js](src/fingerspelling.js) (the manual alphabet), [src/sign-speech.js](src/sign-speech.js) (text→one signing clip: hands rise once and lower once, signs where they exist and spelling for the rest), [src/sign-input.js](src/sign-input.js) (browser Holistic landmarks → text). Face markers ride a morph-target lane through [src/animation-retarget.js](src/animation-retarget.js), re-pointed at whichever meshes the target avatar owns. Tools: `npm run sign:sheet` (contact sheet of every sign, [scripts/sign-contact-sheet.mjs](scripts/sign-contact-sheet.mjs)), `npm run build:sign-goldens` (positional snapshot). Docs: [docs/sign-language.md](docs/sign-language.md). Tests: `tests/{sign-rig,sign-dictionary,sign-linguistics,sign-goldens,fingerspelling,sign-speech,sign-input}.test.js`. || ASL alphabet (learn + practice) | [pages/asl-alphabet.html](pages/asl-alphabet.html) `→ /asl-alphabet` + [src/asl-alphabet-page.js](src/asl-alphabet-page.js), letter notes [src/asl-alphabet-data.js](src/asl-alphabet-data.js) | Live | The manual alphabet as a reference you can turn around: every letter A-Z and digit 0-9 formed on a live portrait-framed rig ([src/fingerspelling.js](src/fingerspelling.js) via PoseStage), each with a written handshape description and the letters it is confused with (F/9, M/N, K/V, G/Q). A single letter holds its final frame (`playOnce({ settleTo: null })`) so it can be orbited; a word settles like a signer finishing. Typing any letter key signs it. Spelling a word lights each key in step with the hand, driven by the `marks` schedule the clip builder emits rather than a parallel timer. A practice drill spells a random letter or word and checks what you type, keeping a streak in localStorage. Shares speed / dominant-hand / avatar preferences with [/sign-language](pages/sign-language.html) under one key via [src/sign-avatars.js](src/sign-avatars.js), including a custom avatar picked from the gallery on either page. Deep links `?letter=W`, `?spell=HELLO`. Docs: [docs/sign-language.md](docs/sign-language.md). || Sign Mirror (camera-graded handshape practice) | [pages/sign-mirror.html](pages/sign-mirror.html) `→ /sign-mirror` + [src/sign-mirror-page.js](src/sign-mirror-page.js), grader [src/sign-grader.js](src/sign-grader.js), reference hand [src/sign-hand-model.js](src/sign-hand-model.js) | Live | The practice half of the signing loop: the avatar forms the target letter, MediaPipe's hand landmarker watches the learner's hand in-tab, and the grader scores the handshape live, finger by finger, naming the finger that is off. Avatar pose, target diagram, and grading all read the same handshape spec ([src/sign-handshapes.js](src/sign-handshapes.js)) so taught and graded can never drift. The whole practice loop is on-device: no frame, landmark, or score is ever uploaded. Course rail orders the alphabet easiest-first with localStorage progress; shared sign prefs (hand, avatar) carry over from `/sign-language` and `/asl-alphabet`. Tests: [tests/sign-grader.test.js](tests/sign-grader.test.js) || ASL recognition (webcam signing → text) | worker [workers/model-asl-recognition/](workers/model-asl-recognition), API [api/asl-recognition.js](api/asl-recognition.js) (`GCP_ASL_RECOGNITION_URL`) | Live | The reverse direction of [sign speech](docs/sign-language.md): the browser extracts MediaPipe landmarks from the webcam (video never leaves the device) and the worker transcribes continuous ASL fingerspelling to text on CPU via LiteRT, with a decode-confidence score and an LLM cleanup pass on the API. Model: Kaggle 2023 ASLFR 1st-place (Apache-2.0 code + weights, FSboard CC BY 4.0 corpus, the license-clean chain most ASL models lack). Cloud Run gen2 + `patchelf --clear-execstack` on the LiteRT .so. Next: word-level signs (PopSign retrain). Tests: [test_decode.py](workers/model-asl-recognition/test_decode.py) (schema + decode, no weights) and [test_model_smoke.py](workers/model-asl-recognition/test_model_smoke.py) (real weights end to end, run inside the built image). |-| Smart home: the connect flow and household management | Page [pages/smart-home.html](pages/smart-home.html) `-> /smart-home` + controller [src/home/connect.js](src/home/connect.js), manage view [src/home/manage.js](src/home/manage.js), styles [src/home/home.css](src/home/home.css). Consumes [api/home/index.js](api/home/index.js) (`GET`/`POST /api/home`), [api/home/[id].js](api/home/[id].js), `/api/home/:id/grants` and `/api/home/:id/log`. Reachability rules shared with the server through the [@three-ws/home-bridge](packages/home-bridge) `./url` subpath export | Live | The front door of the Home lane: how a stranger gets from "I have a Home Assistant somewhere" to "my agent is connected", and every way that goes wrong. Twelve designed states rather than a happy path plus an error toast: signed out, empty, inline validation, the private-host refusal, verifying, connected, a rejected token, unreachable, degraded, disconnected, many homes, and the plan ceiling. Two rules hold the surface together. **The token goes to the server once and never comes back**: the field is `type=password` with a reveal toggle, it is never written to storage, never put in a URL, never logged and never echoed by the API, and it is gone from the DOM the moment a connect succeeds. **Reachability is decided in the browser, before the network**: a `192.168.x.x` or `.local` address is refused with zero network calls using the same `normalizeBaseUrl`/`isPrivateHost` the server validates with, so the two can never disagree and nobody waits out a timeout to be told something we knew at the first keystroke. Every string that came from a house (a label, an entity id, an area name) is rendered as `textContent`, because those are attacker-influenceable and there is a physical actuator on the other end. Docs: [docs/smart-home.md](docs/smart-home.md). Tests: [tests/e2e/home-connect.spec.js](tests/e2e/home-connect.spec.js) |+| Smart home: the connect flow and household management | Page [pages/smart-home.html](pages/smart-home.html) `-> /smart-home` + controller [src/home/connect.js](src/home/connect.js), manage view [src/home/manage.js](src/home/manage.js), styles [src/home/home.css](src/home/home.css). Consumes [api/home/index.js](api/home/index.js) (`GET`/`POST /api/home`), [api/home/[id].js](api/home/[id].js), `/api/home/:id/grants` and `/api/home/:id/log`. Reachability rules shared with the server through the [@three-ws/home-bridge](packages/home-bridge) `./url` subpath export | Live | The front door of the Home lane: how a stranger gets from "I have a Home Assistant somewhere" to "my agent is connected", and every way that goes wrong. Fifteen designed states rather than a happy path plus an error toast: signed out, empty, inline validation, the private-host refusal, verifying, connected, a rejected token, unreachable, degraded, disconnected, many homes, the plan ceiling, the dial-out pairing flow, one deep-linked home, and an id that is not this account's. Every one of them names itself on `#hm-root[data-state]`, so "which state am I in" is answerable from outside the page and no state can be reached only by accident. Two rules hold the surface together. **The token goes to the server once and never comes back**: the field is `type=password` with a reveal toggle, it is never written to storage, never put in a URL, never logged and never echoed by the API, and it is gone from the DOM the moment a connect succeeds. **Reachability is decided in the browser, before the network**: a `192.168.x.x` or `.local` address is refused with zero network calls using the same `normalizeBaseUrl`/`isPrivateHost` the server validates with, so the two can never disagree and nobody waits out a timeout to be told something we knew at the first keystroke. Every string that came from a house (a label, an entity id, an area name) is rendered as `textContent`, because those are attacker-influenceable and there is a physical actuator on the other end. Docs: [docs/smart-home.md](docs/smart-home.md). Tests: [tests/e2e/home-connect.spec.js](tests/e2e/home-connect.spec.js) (behaviour on every screen), [tests/e2e/home-connect-gallery.spec.js](tests/e2e/home-connect-gallery.spec.js) (all fifteen photographed at 1440px and 320px, each asserted to log nothing and to fit a 320px screen), [tests/e2e/home-connect-live.spec.js](tests/e2e/home-connect-live.spec.js) (nothing stubbed: a real Home Assistant connected, the real token proven absent from every browser store, and the container really stopped to reach the degraded state) || Smart home: plans, entitlements and quotas (`/smart-home/plan`) | Page [pages/smart-home-plan.html](pages/smart-home-plan.html) `-> /smart-home/plan` + controller [src/home/plan.js](src/home/plan.js), styles [src/home/plan.css](src/home/plan.css). Resolver [api/_lib/home/entitlements.js](api/_lib/home/entitlements.js), counters [api/_lib/home/usage.js](api/_lib/home/usage.js), endpoint [api/home/plan.js](api/home/plan.js). Enforced at [api/home/index.js](api/home/index.js) (acquisition), [api/home/[id]/stream.js](api/home/[id]/stream.js) (streams), [api/home/[id]/members.js](api/home/[id]/members.js) (seats), [api/home/[id]/call.js](api/home/[id]/call.js) (paused homes), [api/_lib/home/privacy.js](api/_lib/home/privacy.js) (retention ceiling), [api/_lib/home/turn-gate.js](api/_lib/home/turn-gate.js) called from [api/chat.js](api/chat.js) (agent turns). Cost measurement [scripts/measure-home-entitlement-cost.mjs](scripts/measure-home-entitlement-cost.mjs). Migration `api/_lib/migrations/20260903160000_home_plan_overrides.sql` | Live | What a plan covers for connected houses, and the two things no plan may ever refuse. **A limit never blocks a safety action:** over quota, downgraded or paused, locking a door, closing a garage or valve and arming an alarm always execute, checked before any counter is read and classified from the domain and service alone so the exemption never depends on a healthy socket. **Nothing about the gate is sold:** confirmations, the action log's integrity and every role safety property are on every tier and there is deliberately no dimension for any of them. Seven metered dimensions (homes, seats, streams, voice minutes, agent turns, log retention, relay connections), each carrying the measured cost that justifies it. **No fourth entitlement system:** limits resolve from `account-tier.js` badges merged by MAX (so holding $THREE never costs a Pro their Pro limits) and are scaled by the `three-tier.js` holder multiplier, never by thresholds of our own. **One counter:** an agent turn is the same priced `usage_events` chat row an invoice reads, tagged with `home_id`, not a second tally that could disagree. That row is also what the turn gate reads: over quota the agent refuses a home action, but read-only tools stay open (the model has to see which door is open before it can lock it) and safety actions are never reached by the gate at all. The gate **fails open**, so a billing read that hiccups serves the user rather than locking them out of their own house. **A downgrade pauses, it never disconnects:** excess homes get `deactivated_at` with a written reason, the credential and the action log survive, `revoked_at` stays null, and the user swaps which houses are live. Enterprise limits are a `home_plan_overrides` row with the reason on it, not a tier. Every number is env-overridable (`HOME_LIMIT_<TIER>_<DIMENSION>`), so applying an owner-approved price is a config change. Docs: [docs/home-plans.md](docs/home-plans.md). Tests: [tests/home-entitlements.test.js](tests/home-entitlements.test.js), [tests/home-turn-gate.test.js](tests/home-turn-gate.test.js), [tests/e2e/home-plan.spec.js](tests/e2e/home-plan.spec.js) || Smart home: the live 3D home (`/smart-home/:id`) | Page [pages/home-scene.html](pages/home-scene.html) `-> /smart-home/:id` and `-> /home/:id`, styles [public/home-scene.css](public/home-scene.css). Pure layout [src/home/scene-model.js](src/home/scene-model.js), WebGL renderer [src/home/scene-render.js](src/home/scene-render.js), the 2D house [src/home/scene-fallback.js](src/home/scene-fallback.js), page controller [src/home/scene.js](src/home/scene.js), the top-down floorplan editor the scene follows [src/home/floorplan.js](src/home/floorplan.js) with its validation and storage [api/_lib/home/layout.js](api/_lib/home/layout.js) behind `GET`/`PUT`/`DELETE /api/home/:id/layout` [api/home/[id]/layout.js](api/home/%5Bid%5D/layout.js), browser half of the API contract [src/home/api.js](src/home/api.js). Consumes `GET /api/home/:id`, the SSE stream [api/home/[id]/stream.js](api/home/%5Bid%5D/stream.js), [api/home/[id]/call.js](api/home/%5Bid%5D/call.js) and `/api/home/:id/grants` | Live | A live 3D model of the user's house, driven entirely by their own Home Assistant, with the agent's body standing in it. **Home Assistant stores no geometry**, so everything spatial is derived from its four flat registries by a PURE module with no Three.js in it: floors stack by level, rooms pack per floor in name order, and a saved floorplan overrides the packing through one `layout` option. That split is why the layout of a real recorded house is asserted in a unit test without a GPU. **A room is lit the way the room is lit**: colour and intensity from the lights that are actually on, genuinely dark when they are all off, and the outline around its footprint goes amber the moment anything in it is unlocked or open. **A room with sixty entities is not sixty objects**: objects are ranked (lights, locks, covers, climate, alarms, media, fans, cameras, the rest), capped per surface, and the remainder summarized; numeric sensors become readouts, never objects. A device Home Assistant cannot reach is drawn as a ghost with a marker, never omitted. **The house never empties**: a dropped connection greys the scene, keeps every room, and says how old it is. Stale (the platform is retrying) and disconnected (nobody is) are different pills, and only the second offers a button. **The 2D view is not a consolation prize**: same model, real rows and real buttons, reads and operates the whole house, and it is where a browser with no WebGL or a device measured below 18 fps is routed automatically, with the page saying so. A guarded action answers 409 and the question is rendered on the object it would move, with an optional standing allowance for that one entity. Measured: 86 ms median from a real Home Assistant service call to the SSE frame, 10 to 23 ms from that frame to the painted one, 0.1 to 0.3 ms of per-frame work, 108 draw calls, and a flat heap across ten minutes of live updates. Docs: [docs/home-scene.md](docs/home-scene.md). Tests: [tests/home-scene-model.test.js](tests/home-scene-model.test.js), [tests/e2e/home-scene.spec.js](tests/e2e/home-scene.spec.js) || three.ws Home privacy, retention, export and deletion | Inventory + purge + export + deletion [api/_lib/home/privacy.js](api/_lib/home/privacy.js), disclosure copy [api/_lib/home/disclosure.js](api/_lib/home/disclosure.js), endpoint [api/home/privacy.js](api/home/privacy.js) `-> /api/home/privacy`, schema [api/_lib/migrations/20260903180000_home_privacy_retention.sql](api/_lib/migrations/20260903180000_home_privacy_retention.sql), purge section E of [api/cron/db-retention.js](api/cron/db-retention.js) | Live | The single place that knows everything the Home lane stores. `INVENTORY` is not documentation of the code, it IS the code: the endpoint renders it, the export walks it, and [tests/home-privacy.test.js](tests/home-privacy.test.js) re-derives the set of `home_*` tables from the migration files and fails the build if one of them has no row, which is what stops an undocumented data class from ever landing. The load-bearing promise is that entity names and states are never persisted (the room graph lives in the bridge runtime's memory and dies with the instance); a second test fails any migration that creates a table shaped like a state history. The action log's window is per home and the owner's, 90 days by default, adjustable down to a day and up to ten years with a written reason the schema also enforces, applied immediately on change and swept by the platform's existing retention cron rather than a cron of its own. Deletion goes further than the cascades: memberships and grants on other people's homes, the departed user's id inside another household's action log, invitations addressed to their email, and the lane's rows in the 365-day `audit_log`. Docs: [docs/home-privacy.md](docs/home-privacy.md). Tests: [tests/home-privacy.test.js](tests/home-privacy.test.js) |@@ -471,7 +471,7 @@ array. Runbook: [docs/contributing.md](docs/contributing.md#publishing-packages-- **On-chain identity & contracts** — [contracts/](contracts), [packages/avatar-schema/](packages/avatar-schema)- **API endpoints** — [api/](api) (serverless-style handlers, served in production by the [server/](server) Cloud Run container), [workers/](workers) (long-running workers)- **Examples & demos** — [examples/](examples), [multiplayer/](multiplayer)-- **Announcement pipeline**: [docs/announcements/](docs/announcements/README.md) (one pack per feature: the claim and its evidence, the postable text, the media by shot id, the Telegram variant), `data/announcements.json` (the ledger `npm run announce:rank` writes: every shipped surface, whether it was ever announced, its score and its stage; generated, so it is gitignored rather than committed), [data/announce-media.json](data/announce-media.json) (media recipes captured from the live product into `public/announce/`), [docs/announce-voice.md](docs/announce-voice.md) (the voice contract, derived from the engagement archive). `npm run announce:rank` ranks the backlog, `npm run announce:media` captures the frames, `npm run check:announce` gates a pack. Nothing here posts: publishing stays owner-gated.+- **Announcement pipeline**: [docs/announcements/](docs/announcements/README.md) (one pack per feature: the claim and its evidence, the postable text, the media by shot id, the Telegram variant), [data/announcements.json](data/announcements.json) (the ledger: every shipped surface, whether it was ever announced, its score and its stage), [data/announce-media.json](data/announce-media.json) (media recipes captured from the live product into `public/announce/`), [docs/announce-voice.md](docs/announce-voice.md) (the voice contract, derived from the engagement archive). `npm run announce:rank` ranks the backlog, `npm run announce:media` captures the frames, `npm run check:announce` gates a pack. Nothing here posts: publishing stays owner-gated.- **Marketing assets**: [marketing/](marketing/README.md) (produced promo videos + re-render scripts, e.g. [marketing/imessage-video/](marketing/imessage-video); source-of-truth assets, not shipped to production). The narrated product demo lives in [marketing/product-demo/](marketing/product-demo/README.md): [scripts/make-product-demo.mjs](scripts/make-product-demo.mjs) (`npm run demo:video`) films a presenter walking every feature page on the live site, chaptered, with narration from the platform's own TTS lane. Its route is the Feature Tour curriculum, so a new page is in the next recording without editing a script. Docs: [docs/product-demo.md](docs/product-demo.md)- **Platform agents (server-side)**: [agents/](agents/README.md) (endpoint-shopper, fact-checker, tutor, unstoppable, x402-buildout: library modules imported by `api/` handlers, each with its own README)- **Site data files**: [data/](data/README.md) (pages.json, changelog.json, skills seed, RSS items: what each file drives and which script regenerates it)diff --git a/data/changelog.json b/data/changelog.jsonindex 6f62a9a61..d53718551 100644--- a/data/changelog.json+++ b/data/changelog.json@@ -9,6 +9,35 @@"fix"]},+ {+ "date": "2026-09-09",+ "title": "Homes connected through the relay now follow the house when you rearrange it",+ "summary": "If your Home Assistant is only reachable inside your house, three.ws reaches it through the three.ws integration you install there, which dials out to us. Those homes were building their room list once, when the connection opened, and then quietly ignoring changes: assign a lamp to the kitchen, rename a floor, add a device, and the 3D house kept showing the old arrangement until the connection happened to be rebuilt. Homes connected by a direct address never had this problem, and the split was in the relay, which was not carrying the four small notices Home Assistant sends when its rooms, floors, devices or entities change. It carries them now, so both kinds of connection track the house the same way and updates land in seconds. The notices only say that something changed; the relay already read the full room and floor lists, so nothing new about your house is exposed by this.",+ "tags": [+ "fix",+ "infra"+ ],+ "link": "/smart-home"+ },+ {+ "date": "2026-09-09",+ "title": "Connecting a home: the page now says which state it is in, out loud",+ "summary": "Two moments on /smart-home were doing the right thing silently. Typing an address that can never work (a 192.168 number, a .local name) has always put the reason under the field straight away, before anything is sent, but the message was carried by colour alone and a screen reader never read it out; it is now announced the moment it appears, and marked in a way that does not depend on seeing red. And a house that has stopped answering, is refusing the stored token, or has simply gone quiet is now labelled as such by the page itself rather than only in the sentence on its card. Nothing about what you see moves: the last known summary of your house stays exactly where it was, with how long ago it last answered, because a home that went quiet should never look like a home that was deleted.",+ "tags": [+ "improvement",+ "fix"+ ],+ "link": "/smart-home"+ },+ {+ "date": "2026-09-09",+ "title": "The API container keeps the memory it was sized for, so a busy hour cannot take the whole site down",+ "summary": "Every three.ws page and API call is served by one container, and in early September that container was given twice the memory so it could hold live connections to people’s connected homes without ever running short. The setting did not survive: the next full deploy quietly put it back to the smaller limit, and the site then ran for five days on half the memory it had been sized for while still being configured to hold up to 600 home connections. Measured over the last 24 hours, memory was already peaking at 86% of that smaller limit before a single home connection was counted, which is close enough to the edge that a busy hour could have killed the container mid-request and taken every page down with it, not just the connected-home part. The limit is restored, peak memory is back to 43%, and it is now written into the deploy configuration itself so no future deploy can undo it again.",+ "tags": [+ "fix",+ "infra"+ ]+ },{"date": "2026-09-09","title": "An app key can no longer say yes to unlocking your door",@@ -21,12 +50,20 @@},{"date": "2026-09-09",- "title": "Fade Radar: the wallets that have never once been right, and the coins they are crowding into",- "summary": "The Smart Money Radar tells you which proven winners are buying a coin. Fade Radar is the other half of that question, and on pump.fun it turns out to be the sharper one: how much of a coin's buy side is money that has never been right. A wallet joins the reverse-indicator board only after five coins it bought have a known outcome and not one of them won, which is a bar a surprising number of addresses clear. The new page ranks every launch from the last few hours by how much of its observed buy side belongs to those wallets, by wallet count and by SOL, and carries a second board of the wallets themselves with their full record. The number above the board is the part we care most about: it is measured, not asserted. We rebuild the reverse-indicator group using only coins whose outcome was known before the coins it is graded on existed, then check what actually happened. Coins where a quarter or more of the buyers were reverse indicators went on to win 1.8 percent of the time, against 22.1 percent for coins with none, across 26,626 labelled coins. Nothing here is a short and nothing signs anything: on a bonding curve the only tradeable form of a fade is not buying, so every action on the page is a link out to the coin, its intel, or a wallet's track record. Wallet links also now open directly on the Smart Money Radar, so an address cited anywhere on the platform lands on its record instead of a board you have to scan by eye.",+ "title": "The OKX marketplace chat bot now switches AI providers by itself",+ "summary": "Chat for our OKX.AI listing runs on an always-on host that spawns an AI session to answer buyers. That host held exactly one AI provider, so when the provider's account was put on a billing hold the bot went on receiving every message and answering none of them, for days, while other credentials sat unused on the same service. It now holds an ordered chain of providers, asks each one whether it will actually serve before using it, and moves to the first that answers. A provider that recovers or gets funded is picked up on the next check with no redeploy, and the bot's status page lists what every provider answered, so whoever fixes it can see which one to fix rather than only that one was refused.","tags": [- "feature"- ],- "link": "/fade"+ "infra",+ "improvement"+ ]+ },+ {+ "date": "2026-09-09",+ "title": "Avatars and token art load again on sites that embed three.ws",+ "summary": "Assets served from /cdn (avatars, thumbnails, generated models) are read from our object store with a signed request, and when that request is rejected the route falls back to the store's public address so the bytes still arrive. That fallback was a redirect, and a redirect throws away the cross-origin permission the route grants: browsers re-check permission at the redirect's destination, and the public address grants none. Measured from an outside site, every one of those reads failed outright, which took down model previews on pages that load art through the proxy and silently broke third-party embeds of three.ws avatars. The bytes are now served through three.ws itself rather than pointed at, so the permission, the file type and the download rules all survive the fallback, partial reads for video and audio keep working, and a file that genuinely is not there says so instead of reporting a server fault the page retries forever. It also keeps the fallback off the rate-limited public address, which is the whole reason the proxy exists.",+ "tags": [+ "fix"+ ]},{"date": "2026-09-09",@@ -39,11 +76,22 @@},{"date": "2026-09-09",- "title": "Avatars and token art load again on sites that embed three.ws",- "summary": "Assets served from /cdn (avatars, thumbnails, generated models) are read from our object store with a signed request, and when that request is rejected the route falls back to the store's public address so the bytes still arrive. That fallback was a redirect, and a redirect throws away the cross-origin permission the route grants: browsers re-check permission at the redirect's destination, and the public address grants none. Measured from an outside site, every one of those reads failed outright, which took down model previews on pages that load art through the proxy and silently broke third-party embeds of three.ws avatars. The bytes are now served through three.ws itself rather than pointed at, so the permission, the file type and the download rules all survive the fallback, partial reads for video and audio keep working, and a file that genuinely is not there says so instead of reporting a server fault the page retries forever. It also keeps the fallback off the rate-limited public address, which is the whole reason the proxy exists.",+ "title": "Fade Radar: the wallets that have never once been right, and the coins they are crowding into",+ "summary": "The Smart Money Radar tells you which proven winners are buying a coin. Fade Radar is the other half of that question, and on pump.fun it turns out to be the sharper one: how much of a coin's buy side is money that has never been right. A wallet joins the reverse-indicator board only after five coins it bought have a known outcome and not one of them won, which is a bar a surprising number of addresses clear. The new page ranks every launch from the last few hours by how much of its observed buy side belongs to those wallets, by wallet count and by SOL, and carries a second board of the wallets themselves with their full record. The number above the board is the part we care most about: it is measured, not asserted. We rebuild the reverse-indicator group using only coins whose outcome was known before the coins it is graded on existed, then check what actually happened. Coins where a quarter or more of the buyers were reverse indicators went on to win 1.8 percent of the time, against 22.1 percent for coins with none, across 26,626 labelled coins. Nothing here is a short and nothing signs anything: on a bonding curve the only tradeable form of a fade is not buying, so every action on the page is a link out to the coin, its intel, or a wallet's track record. Wallet links also now open directly on the Smart Money Radar, so an address cited anywhere on the platform lands on its record instead of a board you have to scan by eye.","tags": [- "fix"- ]+ "feature"+ ],+ "link": "/fade"+ },+ {+ "date": "2026-09-09",+ "title": "Three fades now stop when you ask the site to stop moving",+ "summary": "Turn on reduced motion in your operating system and three.ws is supposed to hold still: every animation timing on the site is named rather than spelled out, so one switch can zero all of them at once. Three places had drifted off that and spelled their own timing instead, which meant the object library card fade, the avatar picker chips and the Money Pulse rows kept animating for people who had explicitly asked them not to. One of them was pointing at a timing name that does not exist, so the value it fell back to was never the one anyone chose. All three are back on the named ladder at the same speed they always looked, and the reduced-motion switch reaches them again.",+ "tags": [+ "fix",+ "improvement"+ ],+ "link": "/objects"},{"date": "2026-09-09",@@ -27753,6 +27801,15 @@"improvement"],"link": "/restyle"+ },+ {+ "date": "2026-09-09",+ "title": "A link that opens your house in 3D now really opens it in 3D",+ "summary": "The live home page remembers whether you last looked at your house in 3D or as a room list, which is what you want when you open it yourself. It was also overruling links that asked for one view by name: once you had used the 2D view even once on a device, every /smart-home/<id>?view=3d link on that device quietly opened flat again. That matters for the two cases the parameter exists for, a link you share with someone in the house and the address a kitchen or wall display is pinned to. A view asked for in the link now wins, for 3D, 2D and the floorplan alike, and following such a link no longer overwrites the preference that device chose for itself.",+ "tags": [+ "fix"+ ],+ "link": "/docs/home-scene"}]}diff --git a/docs/ALL.md b/docs/ALL.mdindex 5830d2163..7b4f00b05 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-09-05 from **629 files** (~9283 KB).+> Single-file snapshot of every document under [`docs/`](.). Generated 2026-09-09 from **650 files** (~9694 KB).> The individual source files remain the canonical, editable copies — this file is a read-only aggregate.## Table of contents@@ -48,347 +48,364 @@- [announce-voice.md](#sec-098)- [announcement-coverage-telegram.md](#sec-099)- [announcement-coverage.md](#sec-100)-- [api-reference.md](#sec-104)-- [ar-studio.md](#sec-106)-- [ar.md](#sec-107)-- [architecture.md](#sec-108)-- [assistant-widget.md](#sec-109)-- [atlas.md](#sec-110)-- [authentication.md](#sec-112)-- [autonomous-economy.md](#sec-113)-- [autonomous-x402.md](#sec-114)-- [autopilot.md](#sec-115)-- [avatar-artifact.md](#sec-116)-- [avatar-cli.md](#sec-117)-- [avatar-creation.md](#sec-118)-- [avatar-engines.md](#sec-119)-- [avatar-fidelity-program.md](#sec-120)-- [avatar-inspector.md](#sec-121)-- [avatar-pipeline.md](#sec-122)-- [avatar-reconstruction.md](#sec-123)-- [avatar-studio.md](#sec-124)-- [avatar-thumbnails.md](#sec-125)-- [avatar-wardrobe.md](#sec-126)-- [aws-builder-center-agent-commerce-spine.md](#sec-127)-- [aws-builder-center-agent-payment-sessions.md](#sec-128)-- [aws-builder-center-marketplace-x402.md](#sec-129)-- [aws-builder-center-mcp-agents.md](#sec-130)-- [aws-builder-center.md](#sec-131)-- [aws-marketplace-listing-kit.md](#sec-132)-- [aws-marketplace.md](#sec-133)-- [aws-partner-spotlight.md](#sec-134)-- [big-tech-recognition-week.md](#sec-135)-- [bnb-babt-findings.md](#sec-136)-- [bnb-payments.md](#sec-137)-- [bnb-vault.md](#sec-138)-- [bnb-world.md](#sec-139)-- [brain.md](#sec-140)-- [brownout.md](#sec-141)-- [btn-pill-migration.md](#sec-142)-- [build.md](#sec-143)-- [ca2x402.md](#sec-144)-- [capture.md](#sec-145)-- [carplay.md](#sec-146)-- [changelog.md](#sec-147)-- [character-library.md](#sec-148)-- [character-studio.md](#sec-149)-- [chatgpt-3d-studio-gpt.md](#sec-150)-- [chatgpt-ar.md](#sec-151)-- [checkout-companion.md](#sec-152)-- [choreography.md](#sec-153)-- [circulation-engine.md](#sec-154)-- [clash.md](#sec-155)-- [clip-director.md](#sec-156)-- [coin-launches.md](#sec-157)-- [coin-pages.md](#sec-158)-- [coin-wars.md](#sec-159)-- [coingecko-listing-update-2026-08.md](#sec-160)-- [coinmarketcap-article-2026-09-agent-economy.md](#sec-161)-- [coinmarketcap-article-play.md](#sec-162)-- [coinmarketcap-article.md](#sec-163)-- [coinmarketcap-live-article.md](#sec-164)-- [community.md](#sec-165)-- [companion.md](#sec-166)-- [compose.md](#sec-167)-- [concierge.md](#sec-168)-- [configuration.md](#sec-169)-- [contributing.md](#sec-176)-- [copy-trading.md](#sec-181)-- [cosmos.md](#sec-182)-- [create-agent.md](#sec-183)-- [creator-portfolio.md](#sec-184)-- [crews.md](#sec-185)-- [crypto-api.md](#sec-186)-- [custody.md](#sec-187)-- [daily-forge.md](#sec-188)-- [daily-match.md](#sec-189)-- [demo-routes.md](#sec-190)-- [deployment.md](#sec-191)-- [deployments.md](#sec-192)-- [developer-platform.md](#sec-193)-- [diorama.md](#sec-194)-- [do-i-need-crypto.md](#sec-195)-- [docs-world.md](#sec-196)-- [draft-agent-mint.md](#sec-197)-- [drops.md](#sec-198)-- [economy-heartbeat.md](#sec-199)-- [economy-master.md](#sec-200)-- [economy-solver.md](#sec-201)-- [editor.md](#sec-202)-- [education-pilot-bucharest.md](#sec-203)-- [embedding.md](#sec-204)-- [embody.md](#sec-205)-- [erc8004.md](#sec-206)-- [event-souvenirs.md](#sec-234)-- [examples.md](#sec-235)-- [exit-lab.md](#sec-236)-- [fact-check.md](#sec-237)-- [farcaster-memory-seeding.md](#sec-238)-- [feedback.md](#sec-239)-- [financial-controls.md](#sec-240)-- [first-contribution.md](#sec-241)-- [forge-background-generation.md](#sec-242)-- [forge-off.md](#sec-243)-- [forge-pipeline.md](#sec-244)-- [forge.md](#sec-245)-- [forged.md](#sec-246)-- [fork-trade.md](#sec-247)-- [free-crypto-apis.md](#sec-248)-- [free-llm-providers.md](#sec-249)-- [galaxy.md](#sec-251)-- [generation-watch.md](#sec-252)-- [genesis.md](#sec-253)-- [genome.md](#sec-254)-- [ghost-copy.md](#sec-255)-- [github-memory-seeding.md](#sec-256)-- [glance.md](#sec-257)-- [google-x-accounts.md](#sec-258)-- [guardian.md](#sec-259)-- [guards.md](#sec-260)-- [herald.md](#sec-261)-- [hold-to-access.md](#sec-262)-- [home-households.md](#sec-263)-- [home-plans.md](#sec-264)-- [home-privacy.md](#sec-265)-- [home-relay-threat-model.md](#sec-266)-- [home-relay.md](#sec-267)-- [home-satellite.md](#sec-268)-- [home-scene.md](#sec-269)-- [home-security.md](#sec-270)-- [home-voice.md](#sec-271)-- [how-forge-works.md](#sec-272)-- [how-it-works.md](#sec-273)-- [huggingface-3d-ai-agent-platform.md](#sec-274)-- [huggingface.md](#sec-275)-- [i18n.md](#sec-276)-- [ibm-community-article.md](#sec-277)-- [ibm-community-blog-meetup-jessica.md](#sec-278)-- [ibm-community-governed-agents-post.md](#sec-279)-- [ibm-community-live-reaction-jessica.md](#sec-280)-- [ibm-community-recap-jessica.md](#sec-281)-- [ibm-community-recap-nichxbt.md](#sec-282)-- [ibm-community-thread.md](#sec-283)-- [ibm-community.md](#sec-284)-- [ibm-next-event.md](#sec-285)-- [ibm-x402-mcp.md](#sec-286)-- [ibm.md](#sec-287)-- [image-to-3d.md](#sec-288)-- [in-game-economy.md](#sec-289)-- [inference-node-operator.md](#sec-290)-- [integrations.md](#sec-291)-- [introduction.md](#sec-292)-- [ios-app.md](#sec-293)-- [irl.md](#sec-294)-- [js-api.md](#sec-296)-- [knock.md](#sec-297)-- [kol-tracker.md](#sec-298)-- [labor-market.md](#sec-299)-- [launch-usecases.md](#sec-300)-- [layers.md](#sec-301)-- [likeness-eval.md](#sec-302)-- [lipsync.md](#sec-303)-- [liquid-glass.md](#sec-304)-- [listings.md](#sec-305)-- [live-docs.md](#sec-306)-- [live-steps.md](#sec-307)-- [make-your-agent.md](#sec-308)-- [market-data-api.md](#sec-309)-- [marketplace.md](#sec-310)-- [materialize.md](#sec-311)-- [mcp-3d-studio.md](#sec-312)-- [mcp-agent.md](#sec-313)-- [mcp-safety.md](#sec-314)-- [mcp-studio.md](#sec-315)-- [mcp-tools.md](#sec-316)-- [mcp-x402-bazaar.md](#sec-317)-- [mcp.md](#sec-318)-- [media-api.md](#sec-319)-- [memetic-launcher.md](#sec-320)-- [memory.md](#sec-321)-- [meta-allocator.md](#sec-322)-- [mint-mark.md](#sec-323)-- [minted.md](#sec-324)-- [mocap-studio.md](#sec-331)-- [model-diff.md](#sec-332)-- [money-feed.md](#sec-333)-- [money-flow-map.md](#sec-334)-- [money-map.md](#sec-335)-- [monitor.md](#sec-336)-- [motion-swap.md](#sec-337)-- [multi-agent.md](#sec-338)-- [native-launchpad.md](#sec-339)-- [native-widgets.md](#sec-340)-- [news-rights.md](#sec-341)-- [notifications.md](#sec-342)-- [nvidia-apps-catalog-listing.md](#sec-343)-- [nvidia-apps-catalog-request.md](#sec-344)-- [nvidia-forum-browser-digital-human.md](#sec-345)-- [nvidia-inception.md](#sec-346)-- [nvidia-models.md](#sec-347)-- [nvidia-nemotron-ask-the-experts-questions.md](#sec-348)-- [nvidia-nemotron-spotlight.md](#sec-349)-- [nvidia-ngc-listing.md](#sec-350)-- [nvidia-visibility-map.md](#sec-351)-- [object-library.md](#sec-352)-- [okx-marketplace.md](#sec-353)-- [onboarding-tier.md](#sec-354)-- [onchain-agents.md](#sec-355)-- [open-source-ecosystem.md](#sec-356)-- [open-source-footprint.md](#sec-357)-- [open-source-friday-plan.md](#sec-358)-- [openai-community-3d-studio-post.md](#sec-359)-- [openai-community-physical-world-post.md](#sec-360)-- [openai-listing-channels.md](#sec-361)-- [oracle-model.md](#sec-362)-- [oracle-trading-mcp-plan.md](#sec-363)-- [oracle.md](#sec-364)-- [overlay-audit.md](#sec-365)-- [package-extraction.md](#sec-366)-- [page-performance.md](#sec-367)-- [partners.md](#sec-368)-- [pay-skills-listing.md](#sec-370)-- [payment-sessions.md](#sec-371)-- [permissions.md](#sec-372)-- [persona-hub.md](#sec-373)-- [pill-mascot.md](#sec-374)-- [plan-checkout.md](#sec-375)-- [play-boot-performance.md](#sec-376)-- [play-forge-in-world.md](#sec-377)-- [play-hardening.md](#sec-378)-- [play-live-events.md](#sec-379)-- [play-vehicles.md](#sec-380)-- [popular-3d-github-repos.md](#sec-381)-- [portal.md](#sec-382)-- [portfolio.md](#sec-383)-- [premium.md](#sec-384)-- [press-kit.md](#sec-385)-- [procedural-animation.md](#sec-386)-- [product-demo.md](#sec-387)-- [provenance.md](#sec-388)-- [pump-claims-channel.md](#sec-389)-- [pump-fun-mcp-edge.md](#sec-390)-- [pump-launch-repos.md](#sec-391)-- [pump-launcher.md](#sec-392)-- [pump-platform-fee.md](#sec-393)-- [quick-start.md](#sec-414)-- [radar.md](#sec-415)-- [reasoning-ledger.md](#sec-416)-- [recurring-payments.md](#sec-417)-- [remix.md](#sec-418)-- [reputation-staking-market.md](#sec-419)-- [reputation.md](#sec-420)-- [resilience.md](#sec-421)-- [restyle.md](#sec-422)-- [rig-doctor.md](#sec-423)-- [risk-acknowledgment.md](#sec-424)-- [robinhood-chain-markets.md](#sec-425)-- [sas-attestations.md](#sec-426)-- [scene-studio.md](#sec-427)-- [sdk.md](#sec-428)-- [security.md](#sec-429)-- [seed-quality.md](#sec-430)-- [seeker-app.md](#sec-431)-- [seeker-publishing.md](#sec-432)-- [seeker-submission-day.md](#sec-433)-- [seeker-video.md](#sec-434)-- [selfie-to-avatar.md](#sec-435)-- [share-and-embed.md](#sec-436)-- [shared-utilities.md](#sec-437)-- [shipfeed.md](#sec-438)-- [showcase.md](#sec-439)-- [sign-language.md](#sec-440)-- [signals.md](#sec-441)-- [sim-readiness.md](#sec-442)-- [site-performance.md](#sec-443)-- [sketchfab.md](#sec-444)-- [skill-bundles.md](#sec-445)-- [skill-royalties.md](#sec-446)-- [skills.md](#sec-447)-- [smart-contracts.md](#sec-448)-- [smart-home.md](#sec-449)-- [smart-money.md](#sec-450)-- [sniper-autonomy.md](#sec-451)-- [social-layer.md](#sec-452)-- [solana-pumpfun.md](#sec-453)-- [solana-reputation.md](#sec-454)-- [solana.md](#sec-455)-- [spatial-mcp.md](#sec-456)-- [splat.md](#sec-458)-- [spotlight.md](#sec-459)-- [stage.md](#sec-460)-- [start-here.md](#sec-461)-- [strategy-objects.md](#sec-462)-- [swarms.md](#sec-463)-- [syndication.md](#sec-464)-- [talking-avatar-video.md](#sec-465)-- [terminal.md](#sec-466)-- [the-first-19-weeks.md](#sec-467)-- [three-thesis.md](#sec-468)-- [timeline.md](#sec-469)-- [token-gated-3d-embeds.md](#sec-470)-- [tokens-xyz.md](#sec-471)-- [trader-card.md](#sec-472)-- [trader-passport.md](#sec-473)-- [trader-wrapped.md](#sec-474)-- [trading-arenas.md](#sec-475)-- [trading-copilot.md](#sec-476)-- [trading-experiment.md](#sec-477)-- [trading-hub.md](#sec-478)-- [trading-surfaces.md](#sec-479)-- [triage.md](#sec-480)-- [troubleshooting.md](#sec-481)-- [trust-primitives.md](#sec-482)-- [tty-avatar.md](#sec-483)-- [tty.md](#sec-484)-- [ui-juice.md](#sec-555)-- [user-wallet.md](#sec-557)-- [validation.md](#sec-570)-- [vanity.md](#sec-571)-- [vaults.md](#sec-572)-- [vendored-design-libraries.md](#sec-573)-- [viability.md](#sec-574)-- [viewer.md](#sec-575)-- [voice-lab.md](#sec-576)-- [walk-leaderboard.md](#sec-577)-- [web-component.md](#sec-578)-- [widget-api.md](#sec-579)-- [widget-studio.md](#sec-580)-- [widgets.md](#sec-581)-- [witness.md](#sec-582)-- [world-lines.md](#sec-583)-- [x-account-appeal.md](#sec-584)-- [x-accounts.md](#sec-585)-- [x-archive.md](#sec-586)-- [x-memory-seeding.md](#sec-588)-- [x402-buyer.md](#sec-616)-- [x402-dev-tools.md](#sec-617)-- [x402-distribution.md](#sec-618)-- [x402-endpoints.md](#sec-619)-- [x402-preflight.md](#sec-620)-- [x402-ring-economy.md](#sec-621)-- [x402-solana-july-roundup-response.md](#sec-622)-- [x402-studio.md](#sec-623)-- [x402.md](#sec-624)+- [api-reference.md](#sec-105)+- [ar-studio.md](#sec-107)+- [ar.md](#sec-108)+- [architecture.md](#sec-109)+- [assistant-widget.md](#sec-110)+- [atlas.md](#sec-111)+- [authentication.md](#sec-115)+- [autonomous-economy.md](#sec-116)+- [autonomous-x402.md](#sec-117)+- [autopilot.md](#sec-118)+- [avatar-artifact.md](#sec-119)+- [avatar-cli.md](#sec-120)+- [avatar-creation.md](#sec-121)+- [avatar-engines.md](#sec-122)+- [avatar-fidelity-program.md](#sec-123)+- [avatar-inspector.md](#sec-124)+- [avatar-pipeline.md](#sec-125)+- [avatar-reconstruction.md](#sec-126)+- [avatar-studio.md](#sec-127)+- [avatar-thumbnails.md](#sec-128)+- [avatar-wardrobe.md](#sec-129)+- [aws-builder-center-agent-commerce-spine.md](#sec-130)+- [aws-builder-center-agent-payment-sessions.md](#sec-131)+- [aws-builder-center-marketplace-x402.md](#sec-132)+- [aws-builder-center-mcp-agents.md](#sec-133)+- [aws-builder-center.md](#sec-134)+- [aws-marketplace-listing-kit.md](#sec-135)+- [aws-marketplace.md](#sec-136)+- [aws-partner-spotlight.md](#sec-137)+- [big-tech-recognition-week.md](#sec-138)+- [blender-mcp.md](#sec-139)+- [bnb-babt-findings.md](#sec-140)+- [bnb-payments.md](#sec-141)+- [bnb-vault.md](#sec-142)+- [bnb-world.md](#sec-143)+- [brain.md](#sec-144)+- [brownout.md](#sec-145)+- [btn-pill-migration.md](#sec-146)+- [build.md](#sec-147)+- [ca2x402.md](#sec-148)+- [capture.md](#sec-149)+- [carplay.md](#sec-150)+- [changelog.md](#sec-151)+- [character-library.md](#sec-152)+- [character-studio.md](#sec-153)+- [chatgpt-3d-studio-gpt.md](#sec-154)+- [chatgpt-ar.md](#sec-155)+- [checkout-companion.md](#sec-156)+- [choreography.md](#sec-157)+- [circulation-engine.md](#sec-158)+- [clash.md](#sec-159)+- [clip-director.md](#sec-160)+- [coin-launches.md](#sec-161)+- [coin-pages.md](#sec-162)+- [coin-wars.md](#sec-163)+- [coingecko-listing-update-2026-08.md](#sec-164)+- [coinmarketcap-article-2026-09-agent-economy.md](#sec-165)+- [coinmarketcap-article-play.md](#sec-166)+- [coinmarketcap-article.md](#sec-167)+- [coinmarketcap-live-article.md](#sec-168)+- [community.md](#sec-169)+- [companion.md](#sec-170)+- [compose.md](#sec-171)+- [concierge.md](#sec-172)+- [configuration.md](#sec-173)+- [contributing.md](#sec-180)+- [copy-trading.md](#sec-185)+- [cosmos.md](#sec-186)+- [create-agent.md](#sec-187)+- [creator-portfolio.md](#sec-188)+- [crews.md](#sec-189)+- [crypto-api.md](#sec-190)+- [custody.md](#sec-191)+- [daily-forge.md](#sec-192)+- [daily-match.md](#sec-193)+- [demo-routes.md](#sec-194)+- [deployment.md](#sec-195)+- [deployments.md](#sec-196)+- [developer-platform.md](#sec-197)+- [devto-mcp-fleet-post.md](#sec-198)+- [diorama.md](#sec-199)+- [do-i-need-crypto.md](#sec-200)+- [docs-world.md](#sec-201)+- [draft-agent-mint.md](#sec-202)+- [drops.md](#sec-203)+- [economy-heartbeat.md](#sec-204)+- [economy-master.md](#sec-205)+- [economy-solver.md](#sec-206)+- [editor.md](#sec-207)+- [education-pilot-bucharest.md](#sec-208)+- [embedding.md](#sec-209)+- [embody.md](#sec-210)+- [erc8004.md](#sec-211)+- [event-souvenirs.md](#sec-239)+- [examples.md](#sec-240)+- [exit-lab.md](#sec-241)+- [fact-check.md](#sec-242)+- [fade-radar.md](#sec-243)+- [farcaster-memory-seeding.md](#sec-244)+- [feedback.md](#sec-245)+- [financial-controls.md](#sec-246)+- [first-contribution.md](#sec-247)+- [forge-background-generation.md](#sec-248)+- [forge-off.md](#sec-249)+- [forge-pipeline.md](#sec-250)+- [forge.md](#sec-251)+- [forged.md](#sec-252)+- [fork-trade.md](#sec-253)+- [free-crypto-apis.md](#sec-254)+- [free-llm-providers.md](#sec-255)+- [galaxy.md](#sec-257)+- [generation-watch.md](#sec-258)+- [genesis.md](#sec-259)+- [genome.md](#sec-260)+- [ghost-copy.md](#sec-261)+- [github-memory-seeding.md](#sec-262)+- [glance.md](#sec-263)+- [globe.md](#sec-264)+- [google-cloud-community-post.md](#sec-265)+- [google-x-accounts.md](#sec-266)+- [guardian.md](#sec-267)+- [guards.md](#sec-268)+- [herald.md](#sec-269)+- [hold-to-access.md](#sec-270)+- [home-assistant-community-post.md](#sec-271)+- [home-households.md](#sec-272)+- [home-plans.md](#sec-273)+- [home-privacy.md](#sec-274)+- [home-relay-threat-model.md](#sec-275)+- [home-relay.md](#sec-276)+- [home-satellite.md](#sec-277)+- [home-scene.md](#sec-278)+- [home-security.md](#sec-279)+- [home-voice.md](#sec-280)+- [how-forge-works.md](#sec-281)+- [how-it-works.md](#sec-282)+- [huggingface-3d-ai-agent-platform.md](#sec-283)+- [huggingface-agent-feedback-loop.md](#sec-284)+- [huggingface.md](#sec-285)+- [i18n.md](#sec-286)+- [ibm-community-article.md](#sec-287)+- [ibm-community-blog-meetup-jessica.md](#sec-288)+- [ibm-community-governed-agents-post.md](#sec-289)+- [ibm-community-live-reaction-jessica.md](#sec-290)+- [ibm-community-recap-jessica.md](#sec-291)+- [ibm-community-recap-nichxbt.md](#sec-292)+- [ibm-community-thread.md](#sec-293)+- [ibm-community.md](#sec-294)+- [ibm-next-event.md](#sec-295)+- [ibm-x402-mcp.md](#sec-296)+- [ibm.md](#sec-297)+- [image-to-3d.md](#sec-298)+- [in-game-economy.md](#sec-299)+- [inference-node-operator.md](#sec-300)+- [integrations.md](#sec-301)+- [introduction.md](#sec-302)+- [ios-app.md](#sec-303)+- [irl.md](#sec-304)+- [js-api.md](#sec-307)+- [knock.md](#sec-308)+- [kol-tracker.md](#sec-309)+- [labor-market.md](#sec-310)+- [launch-usecases.md](#sec-311)+- [layers.md](#sec-312)+- [likeness-eval.md](#sec-313)+- [lipsync.md](#sec-314)+- [liquid-glass.md](#sec-315)+- [listings.md](#sec-316)+- [live-docs.md](#sec-317)+- [live-steps.md](#sec-318)+- [make-your-agent.md](#sec-319)+- [market-data-api.md](#sec-320)+- [marketplace.md](#sec-321)+- [materialize.md](#sec-322)+- [mcp-3d-studio.md](#sec-323)+- [mcp-agent.md](#sec-324)+- [mcp-safety.md](#sec-325)+- [mcp-studio.md](#sec-326)+- [mcp-tools.md](#sec-327)+- [mcp-x402-bazaar.md](#sec-328)+- [mcp.md](#sec-329)+- [media-api.md](#sec-330)+- [memetic-launcher.md](#sec-331)+- [memory.md](#sec-332)+- [meta-allocator.md](#sec-333)+- [mint-mark.md](#sec-334)+- [minted.md](#sec-335)+- [mocap-studio.md](#sec-342)+- [model-diff.md](#sec-343)+- [money-feed.md](#sec-344)+- [money-flow-map.md](#sec-345)+- [money-map.md](#sec-346)+- [monitor.md](#sec-347)+- [motion-swap.md](#sec-348)+- [multi-agent.md](#sec-349)+- [native-launchpad.md](#sec-350)+- [native-widgets.md](#sec-351)+- [news-rights.md](#sec-352)+- [notifications.md](#sec-353)+- [nvidia-apps-catalog-listing.md](#sec-354)+- [nvidia-apps-catalog-request.md](#sec-355)+- [nvidia-forum-browser-digital-human.md](#sec-356)+- [nvidia-forum-gpu-fleet-post.md](#sec-357)+- [nvidia-inception.md](#sec-358)+- [nvidia-models.md](#sec-359)+- [nvidia-nemotron-ask-the-experts-questions.md](#sec-360)+- [nvidia-nemotron-spotlight.md](#sec-361)+- [nvidia-ngc-listing.md](#sec-362)+- [nvidia-visibility-map.md](#sec-363)+- [object-library.md](#sec-364)+- [okx-marketplace.md](#sec-365)+- [onboarding-tier.md](#sec-366)+- [onchain-agents.md](#sec-367)+- [open-source-ecosystem.md](#sec-368)+- [open-source-footprint.md](#sec-369)+- [open-source-friday-plan.md](#sec-370)+- [openai-community-3d-studio-post.md](#sec-371)+- [openai-community-physical-world-post.md](#sec-372)+- [openai-listing-channels.md](#sec-373)+- [oracle-model.md](#sec-374)+- [oracle-trading-mcp-plan.md](#sec-375)+- [oracle.md](#sec-376)+- [oss-adoption-2026-09.md](#sec-377)+- [overlay-audit.md](#sec-378)+- [package-extraction.md](#sec-379)+- [page-performance.md](#sec-380)+- [partners.md](#sec-381)+- [pay-skills-listing.md](#sec-383)+- [payment-sessions.md](#sec-384)+- [permissions.md](#sec-385)+- [persona-hub.md](#sec-386)+- [pill-mascot.md](#sec-387)+- [plan-checkout.md](#sec-388)+- [play-boot-performance.md](#sec-389)+- [play-forge-in-world.md](#sec-390)+- [play-hardening.md](#sec-391)+- [play-live-events.md](#sec-392)+- [play-vehicles.md](#sec-393)+- [pocket.md](#sec-394)+- [popular-3d-github-repos.md](#sec-395)+- [portal.md](#sec-396)+- [portfolio.md](#sec-397)+- [premium.md](#sec-398)+- [press-kit.md](#sec-399)+- [procedural-animation.md](#sec-400)+- [product-demo.md](#sec-401)+- [provenance.md](#sec-402)+- [publishing-program-2026-09.md](#sec-403)+- [pump-claims-channel.md](#sec-404)+- [pump-fun-mcp-edge.md](#sec-405)+- [pump-launch-repos.md](#sec-406)+- [pump-launcher.md](#sec-407)+- [pump-platform-fee.md](#sec-408)+- [quick-start.md](#sec-429)+- [radar.md](#sec-430)+- [reasoning-ledger.md](#sec-431)+- [recurring-payments.md](#sec-432)+- [remix.md](#sec-433)+- [reputation-staking-market.md](#sec-434)+- [reputation.md](#sec-435)+- [resilience.md](#sec-436)+- [restyle.md](#sec-437)+- [rig-doctor.md](#sec-438)+- [risk-acknowledgment.md](#sec-439)+- [robinhood-chain-markets.md](#sec-440)+- [robinhood-portfolios.md](#sec-441)+- [sas-attestations.md](#sec-442)+- [scene-studio.md](#sec-443)+- [sdk.md](#sec-444)+- [security.md](#sec-445)+- [seed-quality.md](#sec-446)+- [seeker-app.md](#sec-447)+- [seeker-publishing.md](#sec-448)+- [seeker-submission-day.md](#sec-449)+- [seeker-video.md](#sec-450)+- [selfie-to-avatar.md](#sec-451)+- [seo.md](#sec-452)+- [share-and-embed.md](#sec-453)+- [shared-utilities.md](#sec-454)+- [shipfeed.md](#sec-455)+- [short-form-venue-kit-2026-09.md](#sec-456)+- [showcase.md](#sec-457)+- [sign-language.md](#sec-458)+- [signals.md](#sec-459)+- [sim-readiness.md](#sec-460)+- [site-performance.md](#sec-461)+- [sketchfab.md](#sec-462)+- [skill-bundles.md](#sec-463)+- [skill-royalties.md](#sec-464)+- [skills.md](#sec-465)+- [smart-contracts.md](#sec-466)+- [smart-home.md](#sec-467)+- [smart-money.md](#sec-468)+- [sniper-autonomy.md](#sec-469)+- [social-layer.md](#sec-470)+- [solana-pumpfun.md](#sec-471)+- [solana-reputation.md](#sec-472)+- [solana.md](#sec-473)+- [spatial-mcp.md](#sec-474)+- [splat.md](#sec-476)+- [spotlight.md](#sec-477)+- [stage.md](#sec-478)+- [start-here.md](#sec-479)+- [strategy-objects.md](#sec-480)+- [swarms.md](#sec-481)+- [syndication.md](#sec-482)+- [talking-avatar-video.md](#sec-483)+- [terminal.md](#sec-484)+- [the-first-19-weeks.md](#sec-485)+- [three-microbuy.md](#sec-486)+- [three-thesis.md](#sec-487)+- [threejs-forum-post.md](#sec-488)+- [timeline.md](#sec-489)+- [token-gated-3d-embeds.md](#sec-490)+- [tokens-xyz.md](#sec-491)+- [trader-card.md](#sec-492)+- [trader-passport.md](#sec-493)+- [trader-wrapped.md](#sec-494)+- [trading-arenas.md](#sec-495)+- [trading-copilot.md](#sec-496)+- [trading-experiment.md](#sec-497)+- [trading-hub.md](#sec-498)+- [trading-surfaces.md](#sec-499)+- [triage.md](#sec-500)+- [troubleshooting.md](#sec-501)+- [trust-primitives.md](#sec-502)+- [tty-avatar.md](#sec-503)+- [tty.md](#sec-504)+- [ui-juice.md](#sec-575)+- [user-wallet.md](#sec-577)+- [validation.md](#sec-590)+- [vanity.md](#sec-591)+- [vaults.md](#sec-592)+- [vendored-design-libraries.md](#sec-593)+- [viability.md](#sec-594)+- [viewer.md](#sec-595)+- [voice-lab.md](#sec-596)+- [vscode.md](#sec-597)+- [walk-leaderboard.md](#sec-598)+- [web-component.md](#sec-599)+- [widget-api.md](#sec-600)+- [widget-studio.md](#sec-601)+- [widgets.md](#sec-602)+- [witness.md](#sec-603)+- [world-lines.md](#sec-604)+- [x-account-appeal.md](#sec-605)+- [x-accounts.md](#sec-606)+- [x-archive.md](#sec-607)+- [x-memory-seeding.md](#sec-609)+- [x402-buyer.md](#sec-637)+- [x402-dev-tools.md](#sec-638)+- [x402-distribution.md](#sec-639)+- [x402-endpoints.md](#sec-640)+- [x402-preflight.md](#sec-641)+- [x402-ring-economy.md](#sec-642)+- [x402-solana-july-roundup-response.md](#sec-643)+- [x402-studio.md](#sec-644)+- [x402.md](#sec-645)### agent-abilities@@ -464,245 +481,249 @@- [announcements/README.md](#sec-101)- [announcements/genesis.md](#sec-102)- [announcements/open-source-friday.md](#sec-103)+- [announcements/product-demo.md](#sec-104)### api-- [api/forge-x402.md](#sec-105)+- [api/forge-x402.md](#sec-106)### audit-- [audit/console-sweep-2026-09-04.md](#sec-111)+- [audit/console-sweep-2026-09-04.md](#sec-112)+- [audit/console-sweep-2026-09-07.md](#sec-113)+- [audit/python-deps-2026-09-07.md](#sec-114)### content-- [content/use-cases/README.md](#sec-170)-- [content/use-cases/ai-agent-developer.md](#sec-171)-- [content/use-cases/brand-marketer.md](#sec-172)-- [content/use-cases/crypto-community.md](#sec-173)-- [content/use-cases/game-studio.md](#sec-174)-- [content/use-cases/indie-creator.md](#sec-175)+- [content/use-cases/README.md](#sec-174)+- [content/use-cases/ai-agent-developer.md](#sec-175)+- [content/use-cases/brand-marketer.md](#sec-176)+- [content/use-cases/crypto-community.md](#sec-177)+- [content/use-cases/game-studio.md](#sec-178)+- [content/use-cases/indie-creator.md](#sec-179)### cookbook-- [cookbook/asset-quality-gate.md](#sec-177)-- [cookbook/mcp-3d-tool.md](#sec-178)-- [cookbook/parallel-asset-pack.md](#sec-179)-- [cookbook/text-to-3d-cli.md](#sec-180)+- [cookbook/asset-quality-gate.md](#sec-181)+- [cookbook/mcp-3d-tool.md](#sec-182)+- [cookbook/parallel-asset-pack.md](#sec-183)+- [cookbook/text-to-3d-cli.md](#sec-184)### erc8004-- [erc8004/validation-attestation.md](#sec-207)+- [erc8004/validation-attestation.md](#sec-212)### event-readiness-- [event-readiness/01-play-first-impression.md](#sec-208)-- [event-readiness/02-play-mobile.md](#sec-209)-- [event-readiness/03-play-performance.md](#sec-210)-- [event-readiness/04-play-multiplayer-net.md](#sec-211)-- [event-readiness/05-play-economy-loops.md](#sec-212)-- [event-readiness/06-play-auth-errors.md](#sec-213)-- [event-readiness/07-platform-smoke-sweep.md](#sec-214)-- [event-readiness/08-api-production-health.md](#sec-215)-- [event-readiness/09-accessibility-i18n.md](#sec-216)-- [event-readiness/10-event-day-runbook.md](#sec-217)-- [event-readiness/11-event-live-ops.md](#sec-218)-- [event-readiness/12-photo-mode-share.md](#sec-219)-- [event-readiness/13-event-quests-leaderboard.md](#sec-220)-- [event-readiness/14-welcome-concierge.md](#sec-221)-- [event-readiness/15-live-hype-feed.md](#sec-222)-- [event-readiness/16-invite-flow.md](#sec-223)-- [event-readiness/17-plaza-live-show.md](#sec-224)-- [event-readiness/18-coin-wars-portal.md](#sec-225)-- [event-readiness/19-forge-props-live.md](#sec-226)-- [event-readiness/20-world-chat-scrollback.md](#sec-227)-- [event-readiness/21-party-system.md](#sec-228)-- [event-readiness/22-venue-projector-mode.md](#sec-229)-- [event-readiness/23-signature-wall.md](#sec-230)-- [event-readiness/24-dance-off.md](#sec-231)-- [event-readiness/LIVE-OPS.md](#sec-232)-- [event-readiness/README.md](#sec-233)+- [event-readiness/01-play-first-impression.md](#sec-213)+- [event-readiness/02-play-mobile.md](#sec-214)+- [event-readiness/03-play-performance.md](#sec-215)+- [event-readiness/04-play-multiplayer-net.md](#sec-216)+- [event-readiness/05-play-economy-loops.md](#sec-217)+- [event-readiness/06-play-auth-errors.md](#sec-218)+- [event-readiness/07-platform-smoke-sweep.md](#sec-219)+- [event-readiness/08-api-production-health.md](#sec-220)+- [event-readiness/09-accessibility-i18n.md](#sec-221)+- [event-readiness/10-event-day-runbook.md](#sec-222)+- [event-readiness/11-event-live-ops.md](#sec-223)+- [event-readiness/12-photo-mode-share.md](#sec-224)+- [event-readiness/13-event-quests-leaderboard.md](#sec-225)+- [event-readiness/14-welcome-concierge.md](#sec-226)+- [event-readiness/15-live-hype-feed.md](#sec-227)+- [event-readiness/16-invite-flow.md](#sec-228)+- [event-readiness/17-plaza-live-show.md](#sec-229)+- [event-readiness/18-coin-wars-portal.md](#sec-230)+- [event-readiness/19-forge-props-live.md](#sec-231)+- [event-readiness/20-world-chat-scrollback.md](#sec-232)+- [event-readiness/21-party-system.md](#sec-233)+- [event-readiness/22-venue-projector-mode.md](#sec-234)+- [event-readiness/23-signature-wall.md](#sec-235)+- [event-readiness/24-dance-off.md](#sec-236)+- [event-readiness/LIVE-OPS.md](#sec-237)+- [event-readiness/README.md](#sec-238)### fundraising-- [fundraising/nvidia-inception-capital-connect.md](#sec-250)+- [fundraising/nvidia-inception-capital-connect.md](#sec-256)### irl-- [irl/THREAT-MODEL.md](#sec-295)+- [irl/THREAT-MODEL.md](#sec-305)+- [irl/street-demo.md](#sec-306)### mobile-launch-- [mobile-launch/README.md](#sec-325)-- [mobile-launch/aws-builder-center-article.md](#sec-326)-- [mobile-launch/coinmarketcap-article.md](#sec-327)-- [mobile-launch/ibm-community-article.md](#sec-328)-- [mobile-launch/nvidia-forum-article.md](#sec-329)-- [mobile-launch/x-article.md](#sec-330)+- [mobile-launch/README.md](#sec-336)+- [mobile-launch/aws-builder-center-article.md](#sec-337)+- [mobile-launch/coinmarketcap-article.md](#sec-338)+- [mobile-launch/ibm-community-article.md](#sec-339)+- [mobile-launch/nvidia-forum-article.md](#sec-340)+- [mobile-launch/x-article.md](#sec-341)### partners-- [partners/sperax-proposal.md](#sec-369)+- [partners/sperax-proposal.md](#sec-382)### pumpfun-program-- [pumpfun-program/README.md](#sec-394)-- [pumpfun-program/UPSTREAM-buy-sell-v2-announcement.md](#sec-395)-- [pumpfun-program/UPSTREAM-pumpswap-virtual-quote-reserves.md](#sec-396)-- [pumpfun-program/docs/BREAKING_FEE_RECIPIENT.md](#sec-397)-- [pumpfun-program/docs/CPI_README.md](#sec-398)-- [pumpfun-program/docs/FAQ.md](#sec-399)-- [pumpfun-program/docs/FEE_PROGRAM_README.md](#sec-400)-- [pumpfun-program/docs/FEE_RECIPIENTS.md](#sec-401)-- [pumpfun-program/docs/PUMP_CASHBACK_README.md](#sec-402)-- [pumpfun-program/docs/PUMP_CREATOR_FEE_README.md](#sec-403)-- [pumpfun-program/docs/PUMP_PROGRAM_README.md](#sec-404)-- [pumpfun-program/docs/PUMP_SWAP_CREATOR_FEE_README.md](#sec-405)-- [pumpfun-program/docs/PUMP_SWAP_README.md](#sec-406)-- [pumpfun-program/docs/PUMP_SWAP_SDK_README.md](#sec-407)-- [pumpfun-program/docs/instructions/BUY.md](#sec-408)-- [pumpfun-program/docs/instructions/CLAIM_CASHBACK.md](#sec-409)-- [pumpfun-program/docs/instructions/COIN_CREATION.md](#sec-410)-- [pumpfun-program/docs/instructions/COLLECT_CREATOR_FEE.md](#sec-411)-- [pumpfun-program/docs/instructions/CREATOR_FEE_SHARING.md](#sec-412)-- [pumpfun-program/docs/instructions/SELL.md](#sec-413)+- [pumpfun-program/README.md](#sec-409)+- [pumpfun-program/UPSTREAM-buy-sell-v2-announcement.md](#sec-410)+- [pumpfun-program/UPSTREAM-pumpswap-virtual-quote-reserves.md](#sec-411)+- [pumpfun-program/docs/BREAKING_FEE_RECIPIENT.md](#sec-412)+- [pumpfun-program/docs/CPI_README.md](#sec-413)+- [pumpfun-program/docs/FAQ.md](#sec-414)+- [pumpfun-program/docs/FEE_PROGRAM_README.md](#sec-415)+- [pumpfun-program/docs/FEE_RECIPIENTS.md](#sec-416)+- [pumpfun-program/docs/PUMP_CASHBACK_README.md](#sec-417)+- [pumpfun-program/docs/PUMP_CREATOR_FEE_README.md](#sec-418)+- [pumpfun-program/docs/PUMP_PROGRAM_README.md](#sec-419)+- [pumpfun-program/docs/PUMP_SWAP_CREATOR_FEE_README.md](#sec-420)+- [pumpfun-program/docs/PUMP_SWAP_README.md](#sec-421)+- [pumpfun-program/docs/PUMP_SWAP_SDK_README.md](#sec-422)+- [pumpfun-program/docs/instructions/BUY.md](#sec-423)+- [pumpfun-program/docs/instructions/CLAIM_CASHBACK.md](#sec-424)+- [pumpfun-program/docs/instructions/COIN_CREATION.md](#sec-425)+- [pumpfun-program/docs/instructions/COLLECT_CREATOR_FEE.md](#sec-426)+- [pumpfun-program/docs/instructions/CREATOR_FEE_SHARING.md](#sec-427)+- [pumpfun-program/docs/instructions/SELL.md](#sec-428)### specs-- [specs/agent-trading.md](#sec-457)+- [specs/agent-trading.md](#sec-475)### tutorials-- [tutorials/add-a-3d-assistant.md](#sec-485)-- [tutorials/agent-personality.md](#sec-486)-- [tutorials/agent-reputation.md](#sec-487)-- [tutorials/agent-spending-envelope.md](#sec-488)-- [tutorials/animate-your-agent.md](#sec-489)-- [tutorials/animate-your-avatar.md](#sec-490)-- [tutorials/arm-an-agent-sniper.md](#sec-491)-- [tutorials/build-a-3d-asset-pipeline.md](#sec-492)-- [tutorials/build-a-scene.md](#sec-493)-- [tutorials/build-a-site-concierge.md](#sec-494)-- [tutorials/character-library-to-embed.md](#sec-495)-- [tutorials/claim-threews-name.md](#sec-496)-- [tutorials/connect-ai-brain.md](#sec-497)-- [tutorials/connect-your-home.md](#sec-498)-- [tutorials/create-and-edit-memory.md](#sec-499)-- [tutorials/custom-skill.md](#sec-500)-- [tutorials/customize-appearance.md](#sec-501)-- [tutorials/deploy-to-vercel-custom-domain.md](#sec-502)-- [tutorials/earn-and-spend-in-play.md](#sec-503)-- [tutorials/embed-in-30-seconds.md](#sec-504)-- [tutorials/embed-on-website.md](#sec-505)-- [tutorials/emotion-from-data.md](#sec-506)-- [tutorials/explore-docs-world.md](#sec-507)-- [tutorials/find-a-better-exit-policy.md](#sec-508)-- [tutorials/first-agent.md](#sec-509)-- [tutorials/first-prompt-to-3d.md](#sec-510)-- [tutorials/generate-3d-api.md](#sec-511)-- [tutorials/getting-started.md](#sec-512)-- [tutorials/greeting-and-first-speech.md](#sec-513)-- [tutorials/image-to-3d.md](#sec-514)-- [tutorials/import-avatar-url.md](#sec-515)-- [tutorials/js-api-events.md](#sec-516)-- [tutorials/mcp-server-for-your-agent.md](#sec-517)-- [tutorials/mine-vanity-address.md](#sec-518)-- [tutorials/mint-pumpfun-token.md](#sec-519)-- [tutorials/monetize-mcp-server.md](#sec-520)-- [tutorials/multi-agent-coordination.md](#sec-521)-- [tutorials/nvidia-3d-free.md](#sec-522)-- [tutorials/nvidia-nim-self-host.md](#sec-523)-- [tutorials/paid-x402-endpoint.md](#sec-524)-- [tutorials/pay-for-x402-service.md](#sec-525)-- [tutorials/personal-ai-site.md](#sec-526)-- [tutorials/place-agent-irl.md](#sec-527)-- [tutorials/prompts-for-3d.md](#sec-528)-- [tutorials/read-the-trading-fleet.md](#sec-529)-- [tutorials/register-onchain.md](#sec-530)-- [tutorials/render-avatar-images.md](#sec-531)-- [tutorials/self-host-agent-backend.md](#sec-532)-- [tutorials/selfie-to-avatar.md](#sec-533)-- [tutorials/sell-a-skill-with-a-trial.md](#sec-534)-- [tutorials/share-your-agent.md](#sec-535)-- [tutorials/ship-an-avatar-manifest.md](#sec-536)-- [tutorials/shopify-shopping-assistant.md](#sec-537)-- [tutorials/shopify-store-guide-advanced.md](#sec-538)-- [tutorials/shopify-store-guide.md](#sec-539)-- [tutorials/sign-with-your-avatar.md](#sec-540)-- [tutorials/skill-with-database-auth.md](#sec-541)-- [tutorials/solana-agent-reputation.md](#sec-542)-- [tutorials/sperax-tour.md](#sec-543)-- [tutorials/swap-avatar-in-studio.md](#sec-544)-- [tutorials/text-to-3d.md](#sec-545)-- [tutorials/trigger-from-page-events.md](#sec-546)-- [tutorials/upload-custom-glb.md](#sec-547)-- [tutorials/view-in-ar.md](#sec-548)-- [tutorials/voice-and-lipsync.md](#sec-549)-- [tutorials/walk-companion.md](#sec-550)-- [tutorials/wallet-sign-in.md](#sec-551)-- [tutorials/web-component-end-to-end.md](#sec-552)-- [tutorials/write-a-guard.md](#sec-553)-- [tutorials/x402-server-sdk.md](#sec-554)+- [tutorials/add-a-3d-assistant.md](#sec-505)+- [tutorials/agent-personality.md](#sec-506)+- [tutorials/agent-reputation.md](#sec-507)+- [tutorials/agent-spending-envelope.md](#sec-508)+- [tutorials/animate-your-agent.md](#sec-509)+- [tutorials/animate-your-avatar.md](#sec-510)+- [tutorials/arm-an-agent-sniper.md](#sec-511)+- [tutorials/build-a-3d-asset-pipeline.md](#sec-512)+- [tutorials/build-a-scene.md](#sec-513)+- [tutorials/build-a-site-concierge.md](#sec-514)+- [tutorials/character-library-to-embed.md](#sec-515)+- [tutorials/claim-threews-name.md](#sec-516)+- [tutorials/connect-ai-brain.md](#sec-517)+- [tutorials/connect-your-home.md](#sec-518)+- [tutorials/create-and-edit-memory.md](#sec-519)+- [tutorials/custom-skill.md](#sec-520)+- [tutorials/customize-appearance.md](#sec-521)+- [tutorials/deploy-to-vercel-custom-domain.md](#sec-522)+- [tutorials/earn-and-spend-in-play.md](#sec-523)+- [tutorials/embed-in-30-seconds.md](#sec-524)+- [tutorials/embed-on-website.md](#sec-525)+- [tutorials/emotion-from-data.md](#sec-526)+- [tutorials/explore-docs-world.md](#sec-527)+- [tutorials/find-a-better-exit-policy.md](#sec-528)+- [tutorials/first-agent.md](#sec-529)+- [tutorials/first-prompt-to-3d.md](#sec-530)+- [tutorials/generate-3d-api.md](#sec-531)+- [tutorials/getting-started.md](#sec-532)+- [tutorials/greeting-and-first-speech.md](#sec-533)+- [tutorials/image-to-3d.md](#sec-534)+- [tutorials/import-avatar-url.md](#sec-535)+- [tutorials/js-api-events.md](#sec-536)+- [tutorials/mcp-server-for-your-agent.md](#sec-537)+- [tutorials/mine-vanity-address.md](#sec-538)+- [tutorials/mint-pumpfun-token.md](#sec-539)+- [tutorials/monetize-mcp-server.md](#sec-540)+- [tutorials/multi-agent-coordination.md](#sec-541)+- [tutorials/nvidia-3d-free.md](#sec-542)+- [tutorials/nvidia-nim-self-host.md](#sec-543)+- [tutorials/paid-x402-endpoint.md](#sec-544)+- [tutorials/pay-for-x402-service.md](#sec-545)+- [tutorials/personal-ai-site.md](#sec-546)+- [tutorials/place-agent-irl.md](#sec-547)+- [tutorials/prompts-for-3d.md](#sec-548)+- [tutorials/read-the-trading-fleet.md](#sec-549)+- [tutorials/register-onchain.md](#sec-550)+- [tutorials/render-avatar-images.md](#sec-551)+- [tutorials/self-host-agent-backend.md](#sec-552)+- [tutorials/selfie-to-avatar.md](#sec-553)+- [tutorials/sell-a-skill-with-a-trial.md](#sec-554)+- [tutorials/share-your-agent.md](#sec-555)+- [tutorials/ship-an-avatar-manifest.md](#sec-556)+- [tutorials/shopify-shopping-assistant.md](#sec-557)+- [tutorials/shopify-store-guide-advanced.md](#sec-558)+- [tutorials/shopify-store-guide.md](#sec-559)+- [tutorials/sign-with-your-avatar.md](#sec-560)+- [tutorials/skill-with-database-auth.md](#sec-561)+- [tutorials/solana-agent-reputation.md](#sec-562)+- [tutorials/sperax-tour.md](#sec-563)+- [tutorials/swap-avatar-in-studio.md](#sec-564)+- [tutorials/text-to-3d.md](#sec-565)+- [tutorials/trigger-from-page-events.md](#sec-566)+- [tutorials/upload-custom-glb.md](#sec-567)+- [tutorials/view-in-ar.md](#sec-568)+- [tutorials/voice-and-lipsync.md](#sec-569)+- [tutorials/walk-companion.md](#sec-570)+- [tutorials/wallet-sign-in.md](#sec-571)+- [tutorials/web-component-end-to-end.md](#sec-572)+- [tutorials/write-a-guard.md](#sec-573)+- [tutorials/x402-server-sdk.md](#sec-574)### upstream-- [upstream/home-assistant-js-websocket-resubscribe-rejection.md](#sec-556)+- [upstream/home-assistant-js-websocket-resubscribe-rejection.md](#sec-576)### ux-flows-- [ux-flows/01-onboarding-creation.md](#sec-558)-- [ux-flows/02-forge-text-to-3d.md](#sec-559)-- [ux-flows/03-3d-editing-viewer.md](#sec-560)-- [ux-flows/04-embed-widget-studio.md](#sec-561)-- [ux-flows/05-discovery-social.md](#sec-562)-- [ux-flows/06-marketplace-skills.md](#sec-563)-- [ux-flows/07-crypto-trading-analytics.md](#sec-564)-- [ux-flows/08-coin-launch-wallets.md](#sec-565)-- [ux-flows/09-x402-agent-commerce.md](#sec-566)-- [ux-flows/10-chat-brain-labs.md](#sec-567)-- [ux-flows/11-account-dashboard.md](#sec-568)-- [ux-flows/12-home-and-content.md](#sec-569)+- [ux-flows/01-onboarding-creation.md](#sec-578)+- [ux-flows/02-forge-text-to-3d.md](#sec-579)+- [ux-flows/03-3d-editing-viewer.md](#sec-580)+- [ux-flows/04-embed-widget-studio.md](#sec-581)+- [ux-flows/05-discovery-social.md](#sec-582)+- [ux-flows/06-marketplace-skills.md](#sec-583)+- [ux-flows/07-crypto-trading-analytics.md](#sec-584)+- [ux-flows/08-coin-launch-wallets.md](#sec-585)+- [ux-flows/09-x402-agent-commerce.md](#sec-586)+- [ux-flows/10-chat-brain-labs.md](#sec-587)+- [ux-flows/11-account-dashboard.md](#sec-588)+- [ux-flows/12-home-and-content.md](#sec-589)### x-archive-- [x-archive/trythreews-engagement.md](#sec-587)+- [x-archive/trythreews-engagement.md](#sec-608)### x-posts-- [x-posts/3d-ar-studio-launch.md](#sec-589)-- [x-posts/3d-ar-studio-video-script.md](#sec-590)-- [x-posts/README.md](#sec-591)-- [x-posts/android-app-launch.md](#sec-592)-- [x-posts/ar-quick-look-fix-x-post.md](#sec-593)-- [x-posts/event-x-posts.md](#sec-594)-- [x-posts/fomo-verified-x-post.md](#sec-595)-- [x-posts/github-100-stars.md](#sec-596)-- [x-posts/ibm-skillsbuild-x-post.md](#sec-597)-- [x-posts/mcp-registry-fleet-x-post.md](#sec-598)-- [x-posts/metaplex-agent-deployer-video-script.md](#sec-599)-- [x-posts/metaplex-agent-deployer-x-post.md](#sec-600)-- [x-posts/metaplex-agent-mcp-launch.md](#sec-601)-- [x-posts/metaplex-agent-mcp-veo-script.md](#sec-602)-- [x-posts/metaplex-agent-mcp-x-post.md](#sec-603)-- [x-posts/news-archive-x-post.md](#sec-604)-- [x-posts/onchain-agent-wallets-x-post.md](#sec-605)-- [x-posts/open-source-ecosystem.md](#sec-606)-- [x-posts/oracle-trading-mcp-x-post.md](#sec-607)-- [x-posts/osf-issue-reply.md](#sec-608)-- [x-posts/proof-of-life-x-post.md](#sec-609)-- [x-posts/pumpfun-article-x-post.md](#sec-610)-- [x-posts/sperax-staking-in-chat-x-post.md](#sec-611)-- [x-posts/the-first-19-weeks.md](#sec-612)-- [x-posts/threews-avatar-launch.md](#sec-613)-- [x-posts/threews-avatar-video-script.md](#sec-614)-- [x-posts/x-meetup-posts.md](#sec-615)+- [x-posts/3d-ar-studio-launch.md](#sec-610)+- [x-posts/3d-ar-studio-video-script.md](#sec-611)+- [x-posts/README.md](#sec-612)+- [x-posts/android-app-launch.md](#sec-613)+- [x-posts/ar-quick-look-fix-x-post.md](#sec-614)+- [x-posts/event-x-posts.md](#sec-615)+- [x-posts/fomo-verified-x-post.md](#sec-616)+- [x-posts/github-100-stars.md](#sec-617)+- [x-posts/ibm-skillsbuild-x-post.md](#sec-618)+- [x-posts/mcp-registry-fleet-x-post.md](#sec-619)+- [x-posts/metaplex-agent-deployer-video-script.md](#sec-620)+- [x-posts/metaplex-agent-deployer-x-post.md](#sec-621)+- [x-posts/metaplex-agent-mcp-launch.md](#sec-622)+- [x-posts/metaplex-agent-mcp-veo-script.md](#sec-623)+- [x-posts/metaplex-agent-mcp-x-post.md](#sec-624)+- [x-posts/news-archive-x-post.md](#sec-625)+- [x-posts/onchain-agent-wallets-x-post.md](#sec-626)+- [x-posts/open-source-ecosystem.md](#sec-627)+- [x-posts/oracle-trading-mcp-x-post.md](#sec-628)+- [x-posts/osf-issue-reply.md](#sec-629)+- [x-posts/proof-of-life-x-post.md](#sec-630)+- [x-posts/pumpfun-article-x-post.md](#sec-631)+- [x-posts/sperax-staking-in-chat-x-post.md](#sec-632)+- [x-posts/the-first-19-weeks.md](#sec-633)+- [x-posts/threews-avatar-launch.md](#sec-634)+- [x-posts/threews-avatar-video-script.md](#sec-635)+- [x-posts/x-meetup-posts.md](#sec-636)### zauth-- [zauth/database.md](#sec-625)-- [zauth/index.md](#sec-626)-- [zauth/provider-hub.md](#sec-627)-- [zauth/reposcan.md](#sec-628)-- [zauth/vector.md](#sec-629)+- [zauth/database.md](#sec-646)+- [zauth/index.md](#sec-647)+- [zauth/provider-hub.md](#sec-648)+- [zauth/reposcan.md](#sec-649)+- [zauth/vector.md](#sec-650)---@@ -1287,8 +1308,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-097) — the animation registry, runtime loading, and agent slots.-- [docs/avatar-creation.md](#sec-118) — the three ways to create an avatar (photo, builder, upload).-- [docs/tutorials/upload-custom-glb.md](#sec-547) — Mixamo → GLB, validation, and the common failure modes.+- [docs/avatar-creation.md](#sec-121) — the three ways to create an avatar (photo, builder, upload).+- [docs/tutorials/upload-custom-glb.md](#sec-567) — Mixamo → GLB, validation, and the common failure modes.This document is the *why and how* underneath all of those.@@ -1609,11 +1630,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-624) resource: an AI agent pays a few cents in USDC, hands in a URL,+own [x402](#sec-645) 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-619); the stages below are what you do to+3D) is [`/api/x402/forge`](#sec-640); the stages below are what you do toa mesh *after* it exists.```@@ -1626,7 +1647,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-619).+2. **The whole chain in one call** — [`POST /api/x402/pipeline`](#sec-640).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@@ -1689,7 +1710,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-616).+[x402 buyer client](#sec-637).## Stages@@ -1848,9 +1869,9 @@ returned as-is. Poll budget is tunable via `X402_PIPELINE_POLL_BUDGET_MS`## Related-- [x402 paid endpoints](#sec-619) — the full catalog + pricing model-- [x402 buyer client](#sec-616) — how to settle payments as an agent-- [Avatar pipeline](#sec-122) — the generation + rig lanes in depth+- [x402 paid endpoints](#sec-640) — the full catalog + pricing model+- [x402 buyer client](#sec-637) — how to settle payments as an agent+- [Avatar pipeline](#sec-125) — the generation + rig lanes in depth---@@ -1978,8 +1999,8 @@ Frames render **sequentially**. The renderer drives one shared headless browser;## Related- [Free 3D API](#sec-001): generate and inspect-- [MCP servers](#sec-318): every tool on `/api/mcp-studio`-- [OKX.AI marketplace](#sec-353): paid 3D for agents that buy it+- [MCP servers](#sec-329): every tool on `/api/mcp-studio`+- [OKX.AI marketplace](#sec-365): paid 3D for agents that buy it---@@ -2433,10 +2454,10 @@ Product and developer documentation for three.ws. Individual docs are served onStart points:-- [start-here.md](#sec-461): the front door for both creators and developers, with the reference shelf at the bottom.-- [introduction.md](#sec-292) and [quick-start.md](#sec-414): the developer track.+- [start-here.md](#sec-479): the front door for both creators and developers, with the reference shelf at the bottom.+- [introduction.md](#sec-302) and [quick-start.md](#sec-429): 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-104): the REST API surface, with dedicated docs for the larger API families (crypto, 3D, market data, MCP).+- [api-reference.md](#sec-105): 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).@@ -2468,7 +2489,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-073) for the other-owner-only wallet surfaces, [financial controls](#sec-240) for+owner-only wallet surfaces, [financial controls](#sec-246) forthe platform-wide picture, and [agent economy volume](#sec-053)for what settled A2A payments add up to.@@ -2837,7 +2858,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-355).+[Deploy agents on-chain (bulk)](#sec-367).## Relationship to Agora@@ -2850,8 +2871,8 @@ AgenC endpoints here are the read/identity side.## Related- [Agora](#sec-077) — the economy and write lifecycle on top of AgenC.-- [Agent reputation](#sec-057), [ERC-8004](#sec-206).-- [Deploy agents on-chain (bulk)](#sec-355).+- [Agent reputation](#sec-057), [ERC-8004](#sec-211).+- [Deploy agents on-chain (bulk)](#sec-367).---@@ -13879,11 +13900,11 @@ would hide it.## Related-- [x402 paid endpoints](#sec-619): the other side of the ledger. This+- [x402 paid endpoints](#sec-640): 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-113): how agents get wallets, spend+- [The autonomous economy](#sec-116): how agents get wallets, spendpolicies, and paid skills in the first place, which is what produces the rowsthis page aggregates.@@ -13916,7 +13937,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-575) for the rigged GLB |+| `viewer_url` | Deep link into the three.ws [viewer](#sec-595) for the rigged GLB || `pose_studio_url` | Deep link into the [Animation Studio](#sec-096) 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.@@ -14096,13 +14117,13 @@ Two environment overrides help a batch run outlast the rig lane's rate-limit bac## Related-- [OKX.AI Marketplace Services](#sec-353): the price, the payment challenge, the replay flow, the payment guarantees, and the decomposed single-capability 3D services that share these engines.-- [Forge](#sec-245): the text and image to GLB generation pipeline this studio calls for the mesh and the auto-rig.+- [OKX.AI Marketplace Services](#sec-365): the price, the payment challenge, the replay flow, the payment guarantees, and the decomposed single-capability 3D services that share these engines.+- [Forge](#sec-251): the text and image to GLB generation pipeline this studio calls for the mesh and the auto-rig.- [Animation Studio](#sec-096): the `/pose` surface the `pose_studio_url` deep link opens.-- [Viewer](#sec-575): the `/viewer` surface the `viewer_url` deep link opens.-- [MCP servers](#sec-318): the wider set of three.ws MCP endpoints this one follows the transport conventions of.-- [Avatar Engines Atlas](#sec-119): what engine families exist for building human avatars, and which of them are wired into the commercial pipeline.-- [Draft agent mint](#sec-197): the inactive on-chain identity minted for every finished reconstruction, Solana first with ERC-8004 alongside it.+- [Viewer](#sec-595): the `/viewer` surface the `viewer_url` deep link opens.+- [MCP servers](#sec-329): the wider set of three.ws MCP endpoints this one follows the transport conventions of.+- [Avatar Engines Atlas](#sec-122): what engine families exist for building human avatars, and which of them are wired into the commercial pipeline.+- [Draft agent mint](#sec-202): the inactive on-chain identity minted for every finished reconstruction, Solana first with ERC-8004 alongside it.---@@ -14281,8 +14302,8 @@ asks whether the job ran.| Both crawl crons | [`api/cron/`](../api/cron) || Regression cover | [`tests/agent-index.test.js`](../tests/agent-index.test.js) |-Related: [Trust primitives](#sec-482) scores an agent from on-chain-evidence, and [Custody you can verify](#sec-187) covers the attestations the+Related: [Trust primitives](#sec-502) scores an agent from on-chain+evidence, and [Custody you can verify](#sec-191) covers the attestations the`reputation` and `validation` classes carry.---@@ -14934,7 +14955,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-388)) 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-402)) and pinned through the configured IPFS provider.### What a signed envelope looks like@@ -15091,7 +15112,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-388) — signed content credentials for generated 3D assets, using the same attester identity as signed manifests+- [Provenance](#sec-402) — signed content credentials for generated 3D assets, using the same attester identity as signed manifests---@@ -15103,7 +15124,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-420) (leaving and reading reviews) and [ERC-8004](#sec-206) (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-454).+This page is the *why*. For the practical how-to, see [Reputation System](#sec-435) (leaving and reading reviews) and [ERC-8004](#sec-211) (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-472).---@@ -15167,7 +15188,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-206).+> Full detail: [ERC-8004](#sec-211).### 2. Reputation Registry — what others think of it@@ -15196,7 +15217,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-624)).+3. **Pay** — the service answers an HTTP `402` and the agent signs a stablecoin micropayment ([x402](#sec-645)).4. **Vouch** — after the work, write feedback back to the Reputation Registry, closing the loop for the next agent.The one-liner worth remembering:@@ -15217,7 +15238,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-482) |+| `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-502) || [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` |@@ -15256,7 +15277,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-454) · [Leave a vouch](#sec-420) · [ERC-8004 identity](#sec-206) · [x402 payments](#sec-624)+**Next:** [Read an agent's reputation](/tutorials/agent-reputation) · [Reputation on Solana](#sec-472) · [Leave a vouch](#sec-435) · [ERC-8004 identity](#sec-211) · [x402 payments](#sec-645)---@@ -15694,10 +15715,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-578) (the embeddable `agent-3d`-avatar), [coin-pages.md](#sec-158) (the market surfaces the shell-navigates), [companion.md](#sec-166) (the same corner companion delivering-messages from connected sources in person), [feedback.md](#sec-239)+Related: [web-component.md](#sec-599) (the embeddable `agent-3d`+avatar), [coin-pages.md](#sec-162) (the market surfaces the shell+navigates), [companion.md](#sec-170) (the same corner companion delivering+messages from connected sources in person), [feedback.md](#sec-245)(reporting what broke through the companion), [STRUCTURE.md](../STRUCTURE.md)(surface map).@@ -15714,7 +15735,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-447), which extends+> Not to be confused with the [in-app skills system](#sec-465), 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.@@ -15735,7 +15756,7 @@ Three categories:| Category | Skills | Notes || --- | --- | --- |-| **3d/creative** | `generate-3d-model`, `create-3d-avatar`, `rig-a-model` | Text→GLB on the free lane, one-call rigged avatars, auto-rigging. **Cross-platform-safe**: zero coin/wallet/payment content, so this subset is reusable on non-Claude tracks (OpenAI, etc.). |+| **3d/creative** | `find-3d-assets`, `generate-3d-model`, `create-3d-avatar`, `rig-a-model` | Text→GLB on the free lane, one-call rigged avatars, auto-rigging. **Cross-platform-safe**: zero coin/wallet/payment content, so this subset is reusable on non-Claude tracks (OpenAI, etc.). || **wallet/payments** | `authenticate-wallet`, `fund`, `send-usdc`, `trade`, `search-for-service`, `pay-for-service`, `monetize-service`, `query-onchain-data`, `x402`, `metamask-agent-*`, okx wallet/identity set | The x402 agent-economy set. Never bundle these on non-crypto tracks. || **intel/trading** | okx dex/defi market-data and execution set | Vendored partner skills (byte-identical to the vendor drop; categorized only in the pack manifest). |@@ -15801,6 +15822,12 @@ option / skills directory the SDK exposes.The platform's signature set, safe to reuse anywhere:+- **`find-3d-assets`**: search the 3,492 ready-made assets three.ws already+ publishes (511 CC0 props, 107 rigged characters, 2,874 motion clips) and get+ paste-ready code or a downloaded file. Free, and the one to try FIRST: an+ existing asset is instant where a generation is GPU minutes. Reachable three+ ways off one catalog (the `search_catalog` / `get_catalog_item` /+ `get_item_source` MCP tools, `GET /api/catalog`, or `npx @three-ws/assets`).- **`generate-3d-model`** — text → textured GLB on the free `forge_free` lane(NVIDIA NIM / TRELLIS; no key, no account). Returns `glbUrl` + viewer link.- **`create-3d-avatar`** — text/image → **rigged** avatar via `forge_avatar`@@ -15810,7 +15837,7 @@ The platform's signature set, safe to reuse anywhere:`POST /api/forge?action=rig` (Make-It-Animatable). Returns `riggedGlbUrl` +pose-studio link.-All three run free against the hosted studio endpoint+The three generation skills run free against the hosted studio endpoint`https://three.ws/api/mcp-studio` (JSON-RPC `tools/call`), documented with runnable`curl` examples inside each skill.@@ -15833,7 +15860,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-479) (Radar, Coin Intelligence, Mission Control), [trading experiment](#sec-477) (the laddered-exit research policy), [agent wallets](#sec-074) (how custody works), and the worker itself at `workers/agent-sniper/` (its README is the operator reference).+Related surfaces: [the trading surfaces](#sec-499) (Radar, Coin Intelligence, Mission Control), [trading experiment](#sec-497) (the laddered-exit research policy), [agent wallets](#sec-074) (how custody works), and the worker itself at `workers/agent-sniper/` (its README is the operator reference).---@@ -15983,8 +16010,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-479)-- The research policy behind laddered exits: [trading experiment](#sec-477)+- Watch the engine think: [Coin Intelligence and the trading surfaces](#sec-499)+- The research policy behind laddered exits: [trading experiment](#sec-497)- The story of the first trade, for non-operators: [the blog post](/blog/first-autonomous-trade)---@@ -16010,7 +16037,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-253): Genesis gets you a complete agent in a minute,+[Instant Agent Genesis](#sec-259): 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-065).@@ -16034,7 +16061,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-140)).+ [Multi-LLM Brain](#sec-144)).- **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@@ -16071,7 +16098,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-112)):+[Authentication](#sec-115)):```bash# Load (or lazily create) your agent@@ -16116,8 +16143,8 @@ curl -s https://three.ws/api/agents/<agent-id>/pricing \## Related- [Agent System](#sec-065): the full model of what an agent is-- [Instant Agent Genesis](#sec-253): create the agent Studio edits-- [Multi-LLM Brain](#sec-140): the model backend behind the Brain tab+- [Instant Agent Genesis](#sec-259): create the agent Studio edits+- [Multi-LLM Brain](#sec-144): the model backend behind the Brain tab- [Agent Skills](#sec-061): the capabilities the Skills tab manages- [Agent Wallets](#sec-074): the wallet behind the Money tab- Pages: [/agent-studio](https://three.ws/agent-studio), [/genesis](https://three.ws/genesis), [/brain](https://three.ws/brain)@@ -16152,7 +16179,7 @@ user gesture. Nothing autoplays.## Where the events come fromThe symphony consumes the same live ticker documented in-[Money Feed](#sec-333):+[Money Feed](#sec-344):1. `GET /api/feed?limit=40` paints the initial ledger (played silently asbacklog, not as notes).@@ -16168,7 +16195,7 @@ you hear.## What sounds map to what eventsEvery allow-listed feed type (see the type table in-[Money Feed](#sec-333)) maps to one of six voices in+[Money Feed](#sec-344)) 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.@@ -16270,7 +16297,7 @@ cross-links are asserted statically by## Related-- [Money Feed](#sec-333): the activity bus this page renders, including+- [Money Feed](#sec-344): the activity bus this page renders, includingthe full event-type table and how events are published.- [Agora](#sec-077): the on-chain economy lifecycle behind the `agora-*`events.@@ -16468,7 +16495,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-338)): `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-349)): `observe_agents` (list the other agents on stage with names and positions) and `say_to_agent` (send a message to a named stagemate).---@@ -17194,7 +17221,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-392).+agent for buybacks. See [the pump.fun launcher](#sec-407).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@@ -17268,10 +17295,10 @@ doubles as a check on the lane.## Related-- [The pump.fun launcher](#sec-392): the launch transaction itself-- [Coin launches](#sec-157): the platform launch directory-- [Platform fee](#sec-393): what three.ws takes on a launch-- [Solana on pump.fun](#sec-453): the on-chain program surface+- [The pump.fun launcher](#sec-407): the launch transaction itself+- [Coin launches](#sec-161): the platform launch directory+- [Platform fee](#sec-408): what three.ws takes on a launch+- [Solana on pump.fun](#sec-471): 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@@ -17481,10 +17508,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-074) for how the wallet is created, how its key is held, and which paths may spend.-- [Custody you can verify](#sec-187) for the limits, the freeze switch, the Merkle proof of custody, and the social-recovery model.-- [Financial controls](#sec-240) for the plain-English spend-rule layer and the anomaly guard behind `/solana/guard`.-- [The Trading Copilot](#sec-476) for the conversational surface that proposes trades a human confirms.-- [Coin Autopilot](#sec-115) 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-191) for the limits, the freeze switch, the Merkle proof of custody, and the social-recovery model.+- [Financial controls](#sec-246) for the plain-English spend-rule layer and the anomaly guard behind `/solana/guard`.+- [The Trading Copilot](#sec-496) for the conversational surface that proposes trades a human confirms.+- [Coin Autopilot](#sec-118) 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@@ -18143,7 +18170,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-042).-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-115), 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-118), which governs a launched coin at `/api/pump/autopilot`.| Method | Route | Purpose ||---|---|---|@@ -18397,7 +18424,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-051), and the counterpart console in [Guardian](#sec-259).+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-051), and the counterpart console in [Guardian](#sec-267).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.@@ -18539,7 +18566,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-240).+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-246).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.@@ -18657,12 +18684,12 @@ curl -s -X POST "https://three.ws/api/agents/$AGENT_ID/solana/guard" \## Related- [Agent wallets](#sec-074) for the wallet itself: creation, key custody, and the five spend paths.-- [Custody you can verify](#sec-187) for limits, freeze, proof of custody, and the recovery model in prose.-- [Financial controls](#sec-240) for the plain-English spend rules and the wallet-defense behaviors.-- [The Trading Copilot](#sec-476) for the conversational read-and-propose surface over the same wallet.-- [Coin Autopilot](#sec-115) for the separate coin cockpit at `/api/pump/autopilot`.+- [Custody you can verify](#sec-191) for limits, freeze, proof of custody, and the recovery model in prose.+- [Financial controls](#sec-246) for the plain-English spend rules and the wallet-defense behaviors.+- [The Trading Copilot](#sec-496) for the conversational read-and-propose surface over the same wallet.+- [Coin Autopilot](#sec-118) for the separate coin cockpit at `/api/pump/autopilot`.- [What agents can do](#sec-010) for a page per wallet ability, including [Access](#sec-050), [Orders](#sec-041), [Intents](#sec-043), [Autopilot](#sec-042), [Portfolio](#sec-032), and [Recovery](#sec-051).-- [Guardian console](#sec-259) for the other side of a recovery request.+- [Guardian console](#sec-267) for the other side of a recovery request.---@@ -18674,7 +18701,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-187). For the complete tour of everything the wallet can do, read [What agents can do → The Agent Wallet](#sec-024).+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-191). For the complete tour of everything the wallet can do, read [What agents can do → The Agent Wallet](#sec-024).## What you get@@ -18694,7 +18721,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-187).+**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-191).## Who can spend@@ -18703,9 +18730,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-525) 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-545) 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-310)), under its own daily purchase cap |+| Purchase | The agent buys a marketplace skill or asset for itself (see [Marketplace](#sec-321)), 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.@@ -18727,7 +18754,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-240) 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-246) 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@@ -18747,7 +18774,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-104).+Full request/response shapes are in the [REST API reference](#sec-105).## Paying by name@@ -18755,11 +18782,11 @@ An agent can pay a human-readable name instead of a base58 address. `/api/x402/p## Related-- [Custody you can verify](#sec-187) — limits, freeze, Merkle proof-of-custody, social recovery and inheritance-- [Financial controls](#sec-240) — plain-English spend rules, compiled and enforced deterministically+- [Custody you can verify](#sec-191) — limits, freeze, Merkle proof-of-custody, social recovery and inheritance+- [Financial controls](#sec-246) — plain-English spend rules, compiled and enforced deterministically- [What agents can do](#sec-010) — the complete dossier, including a page per wallet ability-- [x402 protocol](#sec-624) — how agents pay for services-- [Coin launches](#sec-157) — how the wallet signs a pump.fun launch+- [x402 protocol](#sec-645) — how agents pay for services+- [Coin launches](#sec-161) — how the wallet signs a pump.fun launch---@@ -18957,11 +18984,11 @@ An "awakening" envelope (no eligible trading agent yet) is still valid and fully## Related-- [Oracle](#sec-364) - the conviction engine this class of agent trades on+- [Oracle](#sec-376) - the conviction engine this class of agent trades on- [Agent reputation](#sec-057) - the Reasoning Ledger score behind the reputation ring-- [Reputation](#sec-420) - how proven on-chain track records are computed-- [The trading experiment](#sec-477) - an autonomous agent operating inside these limits, journaled-- [Custody you can verify](#sec-187) - the spend caps and kill switch the autonomy runs under+- [Reputation](#sec-435) - how proven on-chain track records are computed+- [The trading experiment](#sec-497) - an autonomous agent operating inside these limits, journaled+- [Custody you can verify](#sec-191) - the spend caps and kill switch the autonomy runs under- [/activity](https://three.ws/activity) - every agent's live trades in real time---@@ -21056,9 +21083,9 @@ of rendering a fake zero.## Related surfaces-- [`/portfolio`](#sec-383): the live wallet portfolio; the two pages+- [`/portfolio`](#sec-397): the live wallet portfolio; the two pagescross-link and share the recent-wallet list.-- [`/api/crypto/wallet`](#sec-186): the raw balance endpoint the token+- [`/api/crypto/wallet`](#sec-190): the raw balance endpoint the tokendiversity measurement rides on.---@@ -21138,10 +21165,10 @@ When `read.hallucination_guard.line_replaced` is true, the co-pilot caught a fig## Related-- [Custody you can verify](#sec-187) - the spend limits, firewall, and audit the "Act" path runs under-- [Financial controls](#sec-240) - the plain-English rules and real-time defense on the same rails-- [Oracle](#sec-364) - the platform conviction engine over the same launch universe-- [Trading surfaces](#sec-479) - Mission Control executes through this same guarded path+- [Custody you can verify](#sec-191) - the spend limits, firewall, and audit the "Act" path runs under+- [Financial controls](#sec-246) - the plain-English rules and real-time defense on the same rails+- [Oracle](#sec-376) - the platform conviction engine over the same launch universe+- [Trading surfaces](#sec-499) - Mission Control executes through this same guarded path- [/agi](https://three.ws/agi) - a fully autonomous agent reading and trading the same feed---@@ -21160,7 +21187,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-181) did before this existed.+trading](#sec-185) 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@@ -21168,9 +21195,9 @@ trading](#sec-181) 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-181) for the engine the ladder sits+Related reading: [copy trading](#sec-185) for the engine the ladder sitson, [the $THREE token page](https://three.ws/three-token) for the tier-thresholds, and [trader passport](#sec-473) for the public record a+thresholds, and [trader passport](#sec-493) for the public record adrip cannot touch.---@@ -21244,6 +21271,7 @@ Public. Returns the leader's ladder, the summary line, and the standingdisclosure. A signed-in caller also gets a `you` block with the seat their own$THREE balance buys.+<!-- runnable: 404 the leader id is illustrative; substitute a real public trader for a 200 -->```bashcurl -s 'https://three.ws/api/copy/alpha-drip?leader_agent_id=00000000-0000-0000-0000-000000000000'```@@ -21343,7 +21371,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-473), and the leaderboard, at the moment it+[trader passport](#sec-493), and the leaderboard, at the moment ithappens, regardless of any ladder.---@@ -21759,7 +21787,7 @@ the three consumers above rather than the endpoint, which already pages.# 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-427) 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-443) 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`@@ -21793,7 +21821,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-440) 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-458) 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@@ -21855,8 +21883,8 @@ An empty `tracks` array is rejected: a clip with no motion is not a clip. Track- [Animations reference](#sec-097): 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-427): record your animation to video.-- [Avatar Studio](#sec-124): build the avatar you animate here.+- [Scene Studio](#sec-443): record your animation to video.+- [Avatar Studio](#sec-127): build the avatar you animate here.- [/marketplace](https://three.ws/marketplace): where listed animation clips are bought and sold.---@@ -22886,12 +22914,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-074), [Custody](#sec-187)) |+| Custodial Solana wallet and custodial EVM wallet | `POST /api/agents/:id/wallet/provision`, real custodial keys ([Agent Wallets](#sec-074), [Custody](#sec-191)) || 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-206) record returning a real transaction hash, defaulting to Base |+| Optional on-chain identity | A real [ERC-8004](#sec-211) 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-253).+Full mechanism: [docs/genesis.md](#sec-259).## Media@@ -22995,7 +23023,7 @@ changelog cron must not be used for it, because this is not a changelog entry.· **Announced externally:** neverWritten against [the announcement voice](#sec-098). This is the beat the-[stream plan](#sec-358) does not have: its sequence runs T-14 application,+[stream plan](#sec-370) 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.@@ -23060,6 +23088,187 @@ taken. Then the plan's T-7, T-1, T-0 and T+1 posts run as written.<a id="sec-104"></a>+> **Source:** `docs/announcements/product-demo.md` · [↑ table of contents](#table-of-contents)++# Announcement pack: The product demo film++**Surface:** [`/tour`](https://three.ws/tour) and [`/docs/product-demo`](https://three.ws/docs/product-demo)+· **Ledger key:** `/tour` · **Stage:** drafted · **Filmed:** 2026-09-05 · **Announced externally:** never++The asset is a 65 minute narrated walkthrough of the entire platform, recorded against the live+site by [`npm run demo:video`](../scripts/make-product-demo.mjs). Written against+[the announcement voice](#sec-098).++---++## The claim, and where it is checked++> Every feature page three.ws declares was filmed on the live production site in one run: 257+> stops, none skipped, 65 minutes and 50 seconds at 1920x1080, narrated by the platform's own+> text to speech lane. The route was generated from the site's page index, not written by hand.++Every number comes from the committed run record,+[`marketing/product-demo/three-ws-demo-manifest.json`](../marketing/product-demo/three-ws-demo-manifest.json),+which the recorder writes at the end of the run:++| Part of the claim | Where it is real |+|---|---|+| Filmed on the live production site | `"origin": "https://three.ws"`, `"authed": true` in the manifest |+| 257 stops, none skipped | `"stops": 257`, `"recorded": 257`, `"skipped": []`. A page that fails is reported as a skipped stop rather than filmed as a still frame |+| 65 minutes 50 seconds, 1920x1080 | `"seconds": 3950`, `"stage": "1920x1080@30"` |+| three.ws narrates three.ws | `"narrator": { "lane": "edge" }`, the platform's own TTS lane, the same one that voices agents |+| 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-401).++## Media++The payload of this post is the film itself. The still below is captured from the live route by+`npm run announce:media` and is what ships if the video cannot be uploaded on the account's tier+(see **Delivery** below). Provenance is in+[`public/announce/media-manifest.json`](../public/announce/media-manifest.json).++| Shot | File | Notes |+|---|---|---|+| `tour-hero` | `/announce/img/tour-hero.webp` | 1800x1013. The Guided Tour page, which proves the two numbers the post leans on: 257 features, 6 chapters |++**Alt text, required on the post:**++> The three.ws Guided Tour page: quick highlights of 18 picks in about 7 minutes, or the full tour+> of 257 features across 6 chapters, walked on the live site by a 3D guide that speaks and points,+> paced by you.++X does not accept alt text on a video upload the way it does on an image, so when the film is the+attachment the accessibility payload is the film's own burned-in captions and its spoken narration,+both produced by the recorder. The alt text above is required on any still that ships instead.++## The post++Pattern: number lead. **174 weighted characters** as X counts it (the local counter reads 164+because it only reflates a link carrying its protocol; X charges 23 for the bare `three.ws/tour`+too). That is inside the 100 to 179 band which measured a 3.0x lift.++Postable file: [`product-demo.post.txt`](announcements/product-demo.post.txt).++```text+257 stops on the live site, none skipped, 66 minutes, and three.ws narrates three.ws. The route is generated from the page index, not written by hand: three.ws/tour+```++### Why it is written that way++The reflex for a demo video is to describe the video ("we made a walkthrough of the platform"),+which tells a reader nothing they could not guess from the attachment. The three facts worth+posting are the ones a viewer cannot see by watching: that it is the live production site and not+a staged build, that not one of the 257 stops had to be dropped, and that nobody chose the route.+"Not written by hand" is the sentence doing the real work: it means the film is a byproduct of the+page index rather than a marketing artifact, so the next cut covers whatever shipped since.++Two true details were cut for length: the six chapters ship as separate files so one can be posted+or re-shot alone, and there is a 16 minute 46 second highlights cut of 18 flagship stops. Both are+in the Telegram variant.++No account is tagged. Nothing external is load-bearing here: the site is ours, the narration lane+is ours, and a tag we cannot defend costs more than the 4.5x it would buy.++## The long-form post++The owner asked for a version that explains what three.ws is, not just that it was filmed. That is+a Premium long post (the 280 wall does not apply to it), and it walks the platform in the film's+own chapter order so the text doubles as a chapter guide. Every feature named is a page in+`data/pages.json`, every number is that page's own description (107 rigged characters, 192 news+feeds, 660,000 archived articles, $0.10 a fact check), and the three tags are load-bearing+partnerships the site itself states on `/openai`, `/nvidia`, and `/`.++Postable file: [`product-demo.long.txt`](announcements/product-demo.long.txt), about 4,000 characters. Attach+the same mp4.++## Delivery: which file to attach++The archive says an uploaded video measured 0.71x against a still, so this is the rare pack where+the media is a deliberate exception to the usual "ship the frame" rule. The film is the point of+the post; the tradeoff is recorded here rather than discovered later.++Local files, all in `marketing/product-demo/` and all gitignored:++| File | Runtime | Size | Fits |+|---|---|---|---|+| `three-ws-demo.mp4` | 65m50s | 449 MB | Paid X tier only |+| `three-ws-demo-highlights.mp4` | 16m46s | 76 MB | Paid X tier only |+| `three-ws-demo-highlights-03-crypto.mp4` | 1m42s | 6.6 MB | Any account |+| `three-ws-demo-highlights-05-agent-tools.mp4` | 0m57s | 6.3 MB | Any account |+| `three-ws-demo-highlights-06-learn.mp4` | 1m05s | 9.8 MB | Any account |++A standard X account caps a video at 2 minutes 20 seconds and 512 MB, so the full film needs a+subscription tier that raises both. Order of preference: the full film if the account's tier takes+it, the highlights cut if not, and a single chapter under the standard cap as the always-available+fallback with the full film linked in a reply.++**The GCS console link is not shareable.** `storage.cloud.google.com/three-ws-veo/...` is the+authenticated console URL, and the object is private: an anonymous request to the equivalent+`storage.googleapis.com` path returns 403. Do not put that URL in a post. Uploading the mp4 to X+natively is the path that needs no hosting change at all. If the film should also live at a public+URL, the bucket has uniform bucket-level access off and public access prevention inherited, so one+owner-run command publishes the object:++```bash+gcloud storage objects update gs://three-ws-veo/marketing/product-demo/three-ws-demo.mp4 \+ --add-acl-grant=entity=AllUsers,role=READER+```++That is publishing to an external channel and is owner-gated like the post itself.++## Telegram variant++```text+We filmed the whole platform.++three.ws now has a narrated walkthrough of every feature it declares, recorded against the live+production site: 257 stops, not one of them skipped, 65 minutes and 50 seconds at 1080p, in six+chapters (Main, Build, Crypto, Labs, Agent Tools, Learn).++Three things about how it was made:++- Nobody wrote the route. The stops are generated from the same curriculum the in-product Guided+ Tour walks, which is generated from the site's page index. A page that ships tomorrow is in the+ next recording without anyone editing a script.+- Nothing on screen is staged. The marketplace is really searched, the forge really switches+ lanes, an agent really answers, a model really turns under a drag. A page that had broken would+ have landed in the run report as a skipped stop instead of in the film as a still frame. The+ report lists none.+- three.ws narrates three.ws. The voice is the platform's own text to speech lane, the same one+ that speaks for agents.++There is also a 16 minute highlights cut of 18 flagship stops, and every chapter exists as its own+file so one can be watched on its own.++Want the self-guided version instead of the film? A 3D guide walks the same 257 stops on the live+site, paced by you: three.ws/tour+```++## Changelog++**No new entry.** `/docs/product-demo` was added to `data/pages.json` on 2026-09-05, and a new+page's `added` date feeds the changelog automatically. The film is a marketing asset, not a+shipped surface, so a second entry would tell the community something shipped that did not. If the+mp4 is later published at a public URL and linked from a page, that page is the entry.++## Posting++Publishing to an external channel is owner-gated under the operating rules, every time. Nothing in+this pipeline posts. When the owner approves:++```bash+node scripts/post-tweet.mjs --file docs/announcements/product-demo.post.txt --dry-run+```++Drop `--dry-run` to send, with the chosen mp4 attached. The Telegram variant goes to the community+channel by hand; the changelog cron must not be used for it, because this is not a changelog entry.++---++<a id="sec-105"></a>+> **Source:** `docs/api-reference.md` · [↑ table of contents](#table-of-contents)# REST API Reference@@ -23068,7 +23277,7 @@ 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-296) and [web-component.md](#sec-578). For the high-level npm SDK, see [sdk.md](#sec-428).+> For the in-browser JavaScript API (the `<agent-3d>` element, `Viewer`, `Runtime`, `SceneController`, skills, memory), see [js-api.md](#sec-307) and [web-component.md](#sec-599). For the high-level npm SDK, see [sdk.md](#sec-444).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).@@ -23110,6 +23319,118 @@ Rate-limited responses return HTTP 429 with `{ "error": "...", "code": "RATE_LIM---+## Asset Catalog API++One search across every ready-made asset three.ws publishes: the CC0 object/prop library, the ready-made character library, and the motion-clip library. **No authentication, no API key, no payment.** Open CORS, cached at the edge for 5 minutes.++The same join and the same code generation back the free MCP tools (`search_catalog`, `get_catalog_item`, `get_item_source`) and the `@three-ws/assets` CLI, so all three surfaces answer identically.++### Search the catalog++```+GET /api/catalog?q=wooden+chair&kind=object&limit=12&offset=0+```++| Parameter | Notes |+| --- | --- |+| `q` | Free text over titles, names, tags, and categories |+| `kind` | `object`, `character`, or `animation` |+| `category` | Exact category, from a previous response's `facets.categories` |+| `tag` | Exact tag, from `facets.tags` |+| `limit` | 1 to 50 (default 12) |+| `offset` | Page offset; use `next_offset` from the previous response |++Every word of `q` must match somewhere, which keeps a two-word query precise. If nothing matches all of them, the search retries on any of them and sets `relaxed: true`, so a phrase never dead-ends silently.++**Response**++```json+{+ "ok": true,+ "items": [+ {+ "id": "object:painted_wooden_chair_01",+ "kind": "object",+ "name": "painted_wooden_chair_01",+ "title": "Painted Wooden Chair 01",+ "categories": ["furniture", "seating"],+ "tags": ["chair", "wood", "painted"],+ "license": "CC0",+ "format": "glb",+ "url": "https://three.ws/cdn/objects/polyhaven/glb/painted_wooden_chair_01.glb",+ "thumb": "https://three.ws/cdn/objects/polyhaven/thumbs/painted_wooden_chair_01.png",+ "bytes": 491572+ }+ ],+ "matched": 10,+ "relaxed": false,+ "total": 3492,+ "offset": 0,+ "next_offset": 12,+ "facets": {+ "kinds": { "object": 10 },+ "categories": [{ "value": "furniture", "count": 8 }],+ "tags": [{ "value": "chair", "count": 6 }]+ },+ "generated_at": { "object": "2026-07-21T13:16:14.305Z" }+}+```++`total` is the whole catalog; `matched` is how many the query hit. A character adds `rigged`, `skins`, `baked_animations`, and `source`; a motion clip adds `duration_seconds`, `loop`, and `format: "three-animation-clip-json"`.++**Errors:** `400 validation_error` for an unknown `kind` or a non-integer/out-of-range `limit` or `offset`, validated before any storage read.++---++### Get one item with its source++```+GET /api/catalog?id=object:painted_wooden_chair_01+```++Returns the item, the site links that browse/preview/edit it, up to six related items of the same kind, and paste-ready source in every framework that applies.++**Response**++```json+{+ "ok": true,+ "item": { "id": "object:painted_wooden_chair_01", "kind": "object" },+ "links": {+ "browse": "https://three.ws/objects",+ "preview": "https://three.ws/app#model=...&kind=object",+ "ar": "https://three.ws/ar/studio?src=...",+ "download": "https://three.ws/cdn/objects/..."+ },+ "related": [{ "id": "object:bar_chair_round_01", "title": "Bar Chair Round 01" }],+ "frameworks": ["model-viewer", "three", "agent-3d", "react"],+ "snippets": {+ "model-viewer": {+ "language": "html",+ "code": "<model-viewer src=\"https://three.ws/cdn/...\" ...></model-viewer>",+ "notes": ["This is the exact renderer and build the three.ws browse grids use."]+ }+ }+}+```++`frameworks[0]` is the recommended one for that kind: `model-viewer` for a prop, `agent-3d` for a rigged character, `three` for a motion clip. The `agent-3d` snippet is pinned to the exact published component version with its Subresource Integrity hash, never `latest`.++A bare name (`painted_wooden_chair_01`) also resolves. An unknown id returns `404 not_found` with a `hint` naming the search call to make instead.++---++### From the command line++```bash+npx @three-ws/assets search wooden chair --kind object+npx @three-ws/assets add object:painted_wooden_chair_01+```++`add` downloads the asset into `public/three-ws/` and prints the snippet rewritten to point at the local copy. See [packages/assets-cli/README.md](../packages/assets-cli/README.md).++---+## Agents API### List agents@@ -23736,8 +24057,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-256), [X](#sec-588)-and [Farcaster](#sec-238) memory seeding.+documented in [GitHub](#sec-262), [X](#sec-609)+and [Farcaster](#sec-244) 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@@ -24414,6 +24735,24 @@ silently.Poll with `GET /api/forge?job=<job>` — it returns `{ status: "queued" | "done" | "failed", glb_url? }`.+**Watching the pre-submit work** (optional). Most of a standard text-to-3D+request happens before it can answer: the art-director pass, the reference-view+synthesis, and the turnaround views. Send any url-safe id of 16 to 64 characters+as `progress_id` on the POST, then read `GET /api/forge?progress=<id>` while the+POST is still open to see which of those milestones has finished:++```bash+curl -sS "https://three.ws/api/forge?progress=$TRACE"+# → {"progress":[{"stage":"directed","at":1757345001000,"directed_prompt":"…"},+# {"stage":"reference","at":1757345013000,"preview_image_url":"https://…/ref.jpg"}]}+```++Stages are `directed`, `reference`, `views` and `submitting`, each written only+after the work it names returned. An unknown or not-yet-started trace answers+`{"progress":[]}`, crumbs expire after five minutes, and omitting `progress_id`+leaves the request byte-for-byte what it was. Full walkthrough:+[docs/forge.md](forge.md#watching-a-generation-happen).+Signed-in callers can skip the poll loop entirely: register a webhook for`forge.completed` and `forge.failed` and the platform POSTs you the finishedjob. Payloads, delivery semantics and a runnable subscribe-then-submit example@@ -24753,7 +25092,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-243).+docs: [docs/forge-off.md](#sec-249).### Model detail page read: `GET /api/forge-creation`@@ -24877,7 +25216,7 @@ buys from is documented under `POST /api/x402/forge` in the x402 section.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-311). Wire contracts:+[Materialize](#sec-322). Wire contracts:[specs/PRINT_PIPELINE.md](../specs/PRINT_PIPELINE.md).Analysis and quoting are **free and keyless**. Only checkout costs money.@@ -25115,7 +25454,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-316) calls as+same implementation the paid `restyle_material` [MCP tool](#sec-327) 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@@ -25509,7 +25848,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-440)).+loop (the output half, avatars that sign, is [docs/sign-language.md](#sec-458)).**Video never reaches the platform.** The caller extracts MediaPipe Holisticlandmarks in the browser and posts coordinates only. `src/sign-input.js` ships a@@ -26262,7 +26601,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-186)); launches shares its query+`/whales` — see [docs/crypto-api.md](#sec-190)); 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.@@ -26331,7 +26670,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-186)+[`GET /api/crypto/trending`](#sec-190)(`api/_lib/crypto-trending.js` `composeTrending`), capped slimmer here (25 vs50) to keep this door fast.@@ -26396,7 +26735,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-186)+[`GET /api/crypto/bonding`](#sec-190)(`api/_lib/pump-bonding.js` `getBondingStatus`).```@@ -26527,7 +26866,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-186)+[`GET /api/crypto/whales`](#sec-190)(`api/_lib/pump-whale-scan.js` `scanTokenWhales` / `scanMarketWhales`).```@@ -26584,11 +26923,104 @@ curl -s 'https://three.ws/api/v1/pump/whales?mint=FeMbDoX7R1Psc4GEcvJdsbNbZA3bfz---+## Recording Pipeline API++One call that answers "is the data loop actually running?" for the closed loop+behind three.ws's pump.fun signal: the always-on launch recorder, signal intel,+ground-truth outcomes, Oracle conviction, the wallet reputation graph, trained+per-signal weights, and the agents trading on the result. Each link lives in a+different table, so checking it by hand otherwise means six queries across six+surfaces. The board that renders this is [three.ws/pipeline](https://three.ws/pipeline).++### Pipeline health++```+GET /api/pipeline?network=mainnet|devnet+```++No auth, IP rate-limited, `cache-control: public, max-age=8`. `network`+defaults to `mainnet`; anything that is not `devnet` is read as `mainnet`.++```json+{+ "ok": true,+ "network": "mainnet",+ "health": "flowing",+ "summary": "Pipeline flowing on mainnet: 1473 launches recorded in the last hour, ...",+ "next_action": { "step": "running", "label": "Loop is running end to end", "detail": "..." },+ "stages": {+ "recorder": { "state": "live", "reason": null, "mode": "live", "network": "mainnet",+ "feedLive": true, "heartbeatAgeMs": 20916, "lastEventAgeMs": 3829, "reconnects": 0 },+ "intel": { "total": 133507, "observed_24h": 29837, "observed_1h": 1473, "avg_quality": 21,+ "healthy": 1613, "mixed": 6321, "risky": 21903, "smart_money_touched": 65 },+ "outcomes": { "labeled": 131750, "graduated": 4389, "rugged": 22378, "pumped": 10184, "labeled_24h": 31916 },+ "oracle": { "scored_total": 888109, "scored_24h": 14376, "prime": 803, "strong": 1043, "open_actions": 26 },+ "reputation": { "wallets": 746777, "smart_money": 2272 },+ "learning": { "sample_size": 20000, "trained_at": "2026-09-08T16:30:27.974Z",+ "weights": [{ "signal": "organic_score", "weight": 0.1812 }] },+ "trading": { "strategies_armed": 11, "open_positions": 0, "snipes_24h": 26, "trades_24h": 4 }+ },+ "docs": "https://three.ws/pipeline",+ "t": 1788885583351+}+```++`health` is one of:++| Value | Meaning |+| --- | --- |+| `flowing` | the recorder is live and launches arrived in the last hour |+| `recording` | the recorder is live but nothing has arrived in the last hour |+| `idle` | the recorder is not live, so nothing downstream can advance |++`recorder.state` is the operational truth behind that word: `live`, `degraded`+(the worker beats but its feed is silent or disconnected), `down` (the heartbeat+is stale), `offline` (never started, or recording a different network), or+`unknown` (the status store was unreachable). Every non-live state carries a+plain-language `reason`. **The recorder is network-scoped**: the worker writes a+single heartbeat row for whichever network it records, so asking about the other+network answers `offline` with `reason: "recording mainnet, not devnet"` rather+than lending one network's liveness to the other.++`next_action` is the single most useful move given that state, ordered by where+the loop is actually blocked, so an agent can act on it without interpreting the+numbers:++| `step` | Needs an operator | Meaning |+| --- | --- | --- |+| `deploy_recorder` | yes | no heartbeat; `command` is `npm run deploy:sniper` |+| `check_feed` | yes | the worker is up but its pump.fun feed went silent |+| `accumulate` | no | recording; fewer than 50 outcomes labeled, the learner is waiting |+| `await_training` | no | enough labels, waiting on the next training pass |+| `arm_agents` | yes | trained and scored, but no strategy armed; `command` is `POST /api/sniper/strategy` |+| `running` | no | recording, scoring, learning, and trading are all active |++Every stage is queried independently and degrades on its own: a table that does+not exist yet on a fresh database, or a worker that never booted, reports an+honest zero or `offline` for that stage instead of failing the whole response.+There is no `5xx` for "nothing recorded yet."++**Example**++```bash+curl -s 'https://three.ws/api/pipeline?network=mainnet' | jq '{health, next: .next_action.step}'+curl -s 'https://three.ws/api/pipeline?network=devnet' | jq '.stages.recorder'+```++**Errors**++| Status | Code | Meaning |+| ------ | -------------- | --------------------------------- |+| `405` | `method_not_allowed` | anything but `GET` or `OPTIONS` |+| `429` | `rate_limited` | over the per-IP limit |++---+## Trader Passport APIA 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-473).+[docs/trader-passport.md](#sec-493).### Read a passport@@ -26638,7 +27070,7 @@ subject, slot, block_time, payload, reasons[] }`; every failed check is named in## Authentication API-Authentication is covered in detail in the [Authentication documentation](#sec-112). Quick reference:+Authentication is covered in detail in the [Authentication documentation](#sec-115). Quick reference:| Endpoint | Method | Description || --------------------------- | -------- | ------------------------------------- |@@ -26818,7 +27250,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-452).+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-470).### Activity feed@@ -26857,7 +27289,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-333)).+Not the same endpoint as `GET /api/feed`, the public Money Pulse ticker ([Money Feed](#sec-344)).---@@ -27087,7 +27519,9 @@ pin; non-owners get 403):POST /api/irl/interactions```-Body: `{ "pinId": "<uuid>", "type": "view" | "tap" | "message" | "pay", "message"?, ... }`.+Body: `{ "pinId": "<uuid>", "type": "view" | "tap" | "message" | "pay" | "talk", "message"?, ... }`.+`talk` records that a visitor opened a live conversation with the agent from the /irl Talk panel (one+row per conversation, never the transcript).`view` repeats from one device collapse within 5 min; a `pay` must carry a valid on-chainsettlement `signature` plus a `$THREE`/USDC `currencyMint` and is deduped per signature. Thepin's owner and agent are always taken from the pin, never the caller.@@ -27252,7 +27686,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-318) and the [MCP Tools Catalog](#sec-316).+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-329) and the [MCP Tools Catalog](#sec-327).**Example JSON-RPC request**@@ -27365,7 +27799,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-353).+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-365).---@@ -27387,7 +27821,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-371). Step-by-step walkthrough: [Give an agent a spending envelope](#sec-488). 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-384). Step-by-step walkthrough: [Give an agent a spending envelope](#sec-508). Enforcement source: [`api/_lib/pay/spend-governor.js`](https://github.com/nirholas/three.ws/blob/main/api/_lib/pay/spend-governor.js).### Authentication@@ -27717,7 +28151,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-158) for the product surface.+[docs/coin-pages.md](#sec-162) for the product surface.### Coin detail@@ -28237,7 +28671,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-341)).+every response passes through (see [docs/news-rights.md](#sec-352)).`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@@ -28876,7 +29310,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-159).+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-163).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.@@ -30470,7 +30904,7 @@ curl -X POST https://three.ws/api/seeker/verify \## Herald API: deliver a message in person-The rail behind [@three-ws/herald](#sec-261). Anything that can make an HTTPS+The rail behind [@three-ws/herald](#sec-269). 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.@@ -30545,6 +30979,7 @@ listening is for the person at the browser). Emits `open` once, then onedrained rather than broadcast, so a line is said by exactly one open tab, andan undelivered one expires after about five minutes.+<!-- runnable: 401 the herald queue is per-session; without a real session cookie the stream is refused -->```bashcurl -N https://three.ws/api/herald/stream -b 'session=<your session cookie>'```@@ -30561,7 +30996,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-257), [native-widgets.md](#sec-340).+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-263), [native-widgets.md](#sec-351).### Public card@@ -30607,7 +31042,7 @@ browser; bearer principals (OAuth, API key) may read with `home:read` and act wiEvery 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-498).+message. Full walkthrough: [Connect your home](#sec-518).**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@@ -30927,6 +31362,40 @@ no longer reach it.---+### Making a room++```+POST /api/home/:id/areas+```++```json+{ "name": "Kitchen" }+```++```json+{ "ok": true, "area": { "id": "kitchen", "name": "Kitchen", "floorId": null, "created": true } }+```++Creates the area in **the user's own Home Assistant** (`config/area_registry/create`) and+answers **201** when it made one, **200** when an area by that name already existed. A duplicate+name is not an error: the room the caller asked for is there, which is what they wanted, and the+existing `id` comes back so a client can carry straight on and file devices into it.++This is the way out of the most common real Home Assistant there is: one where nothing has ever+been assigned to an area, so every room-shaped surface has nothing to draw. Without it the only+advice a client can give is "go and make areas in Home Assistant's settings first", which is a+chore people leave to do and do not come back from. The floorplan editor calls this instead, and+files the device that prompted the room in the same step.++Same rules as filing a device: not a guarded action (an empty area is two clicks to delete in+their own UI), and it still needs the `layout` capability, a CSRF token, and a `home_action_log`+row. A **scoped** member is refused with `scope_forbidden`: a brand new room belongs to no scope+by definition, so they would create something they could not then see, place or file into.++Names are trimmed and capped at 64 characters; an empty one returns `name_required`.++---+### The action log```@@ -31154,7 +31623,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-265).+Details: [docs/home-privacy.md](#sec-274).---@@ -31191,7 +31660,7 @@ Endpoint-specific codes (e.g. `quota_exceeded`, `invalid_avatar`, `no_client_id`## 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-428).+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-444).For the endpoints on this page, call them directly with `fetch`/`curl` and a Bearer API key:@@ -31214,7 +31683,7 @@ const { agents } = await res.json();----<a id="sec-105"></a>+<a id="sec-106"></a>> **Source:** `docs/api/forge-x402.md` · [↑ table of contents](#table-of-contents)@@ -31547,8 +32016,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-619) and-[the autonomous economy](#sec-114).+[x402 endpoints](#sec-640) and+[the autonomous economy](#sec-117).Treat prompts as public. If you need a private lane, use the account-scopedsurfaces instead of this one.@@ -31593,17 +32062,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-244): how the lanes, tiers, and failovers fit+- [Forge pipeline](#sec-250): how the lanes, tiers, and failovers fittogether internally.-- [3D Studio MCP server](#sec-312): the same generation as+- [3D Studio MCP server](#sec-323): 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-619): every paid endpoint on the platform.+- [x402 endpoints](#sec-640): every paid endpoint on the platform.----<a id="sec-106"></a>+<a id="sec-107"></a>> **Source:** `docs/ar-studio.md` · [↑ table of contents](#table-of-contents)@@ -31616,9 +32085,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-107)) 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-108)) 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-107).+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-108).## How it works@@ -31711,13 +32180,13 @@ Append `?e2e=1` to expose `window.__arsDebug` (`count()`, `netStatus()`, `netIds## Related-- [AR and WebXR](#sec-107): 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-435) and [Avatar pipeline](#sec-122): where the models you place come from.+- [AR and WebXR](#sec-108): 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-451) and [Avatar pipeline](#sec-125): 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-107"></a>+<a id="sec-108"></a>> **Source:** `docs/ar.md` · [↑ table of contents](#table-of-contents)@@ -31777,7 +32246,7 @@ You do not add an attribute to enable AR; you link to (or embed) one of the AR s| AR Forge | `/ar` | Generate a model from a prompt and place it immediately || Living-agent AR | `/irl?avatar=<glbUrl>` | A rigged avatar that walks and talks in your room (WebXR) |-The avatar AR page and the `/api/ar` launch page render the model in Google's `<model-viewer>` element with `ar ar-modes="webxr scene-viewer quick-look"`, so the same page covers Quick Look, Scene Viewer, and WebXR. The **Place in your space** button appears only when the device exposes a usable AR mode (model-viewer's `canActivateAR`); on desktop the page shows a QR code handoff instead.+The avatar AR page and `/ar/view` (the page `/api/ar` redirects to) render the model in Google's `<model-viewer>` element with `ar ar-modes="webxr scene-viewer quick-look"`, so the same page covers Quick Look, Scene Viewer, and WebXR. The **Place in your space** button appears only when the device exposes a usable AR mode (model-viewer's `canActivateAR`); on desktop the page shows a QR code handoff instead. `/api/ar` itself renders no 3D: it is a server-side router that either 302s into a Scene Viewer intent (plain Android) or serves a tiny Open-Graph interstitial that hands off to `/ar/view` (see [the launcher section](#one-tap-ar-for-any-glb--get-apiar--export_ar)).### Allow XR in iframes@@ -31796,7 +32265,7 @@ Without `xr-spatial-tracking`, the browser blocks `navigator.xr` inside the fram## Programmatic API-On pages that render the model with `<model-viewer>` (the avatar AR page at `/avatars/<id>/ar`, the `/api/ar` launch page, Forge results), AR is driven through model-viewer's API. This is exactly what [src/ar-page.js](../src/ar-page.js) does:+On pages that render the model with `<model-viewer>` (the avatar AR page at `/avatars/<id>/ar`, the `/ar/view` launch page, Forge results), AR is driven through model-viewer's API. This is exactly what [src/ar-page.js](../src/ar-page.js) does:```jsconst viewer = document.querySelector('model-viewer');@@ -32147,9 +32616,9 @@ The endpoint branches on the request's **User-Agent**, server-side:| Device | What happens ||---|---|-| **iOS** (iPhone/iPad) | Launch page → Apple **Quick Look**. The USDZ is generated from the GLB on the fly by model-viewer (three.js `USDZExporter`) — a real conversion, no server USD tooling. |+| **iOS** (iPhone/iPad) | An Open-Graph interstitial that hands off to the `/ar/view` launch page → Apple **Quick Look**. That page converts the GLB to a real USDZ on the device with three.js `USDZExporter` and sets it as model-viewer's `ios-src`; `<model-viewer>` does **not** do that conversion itself, which is why the launcher redirects to a Vite-bundled page instead of writing HTML inline. No server USD tooling. || **Android** | `302` → Google **Scene Viewer** ARCore intent (the GLB is the source), with a browser fallback to the WebGL viewer. |-| **Desktop** | Launch page → interactive **WebGL** viewer (no AR hardware). |+| **Desktop** | The same interstitial into the `/ar/view` launch page, which falls back to the interactive **WebGL** viewer (no AR hardware). |**`kind=avatar`: the living-agent lane.** AR on three.ws is not a prop viewer; it is how agents cross into physical space. When the GLB is a rigged avatar (an agent's body), add `kind=avatar`: the launch page then leads with a **Bring it to life** handoff into [`/irl?avatar=<glbUrl>`](/irl), where the avatar walks, animates, and talks with the user through their camera in their real room. Static placement stays available alongside it, and Android serves the launch page instead of the blind Scene Viewer redirect so the living path is always visible.@@ -32161,7 +32630,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-104) for the renderer's parameters and limits.+[API reference](#sec-105) 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):@@ -32224,13 +32693,13 @@ the wild can load.----<a id="sec-108"></a>+<a id="sec-109"></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-273) 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-282) 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.@@ -32488,7 +32957,7 @@ A minimal Node + Neon + Anthropic deployment is enough for a single agent. The b----<a id="sec-109"></a>+<a id="sec-110"></a>> **Source:** `docs/assistant-widget.md` · [↑ table of contents](#table-of-contents)@@ -32501,9 +32970,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-168). 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-172). 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-485) 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-505) builds one from scratch.## Install@@ -32612,7 +33081,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-318); 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-329); find it in the registry at [registry.modelcontextprotocol.io](https://registry.modelcontextprotocol.io/?q=io.github.nirholas).## How it works@@ -32624,10 +33093,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-485), the tutorial-- [Concierge](#sec-168), the page-grounded support-chat widget with a lipsyncing face-- [three.ws MCP servers](#sec-318), the full free and paid tool catalog-- [Share and embed](#sec-436), the `<three-d>` model embeds+- [Build a 3D assistant, step by step](#sec-505), the tutorial+- [Concierge](#sec-172), the page-grounded support-chat widget with a lipsyncing face+- [three.ws MCP servers](#sec-329), the full free and paid tool catalog+- [Share and embed](#sec-453), 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@@ -32640,7 +33109,7 @@ Ask your agent something like "build a 3D assistant widget named Aria with an oc----<a id="sec-110"></a>+<a id="sec-111"></a>> **Source:** `docs/atlas.md` · [↑ table of contents](#table-of-contents)@@ -32816,7 +33285,7 @@ searching for "embed".----<a id="sec-111"></a>+<a id="sec-112"></a>> **Source:** `docs/audit/console-sweep-2026-09-04.md` · [↑ table of contents](#table-of-contents)@@ -33729,7 +34198,1809 @@ Call log:----<a id="sec-112"></a>+<a id="sec-113"></a>++> **Source:** `docs/audit/console-sweep-2026-09-07.md` · [↑ table of contents](#table-of-contents)++# Console Sweep: 2026-09-07++Headless Chromium (Playwright) over 788 HTML routes from `data/pages.json` at desktop 1440×900 and mobile 390×844. Each route: `domcontentloaded` → scroll → 3000ms settle. Environment noise (Vite HMR-proxy wss handshake, third-party telemetry, auth-gated `/api` 4xx, dev-origin CDN CORS) is filtered.++**Result:** ❌ 9 route(s) with errors. 28 total error(s).++Routes that failed in the parallel pass are re-run once, serially, and the second reading is the one reported: desktop 779/788 cleared on the retry, mobile 1/4 cleared on the retry. A route that cleared was losing its settle window to load on a shared box, not failing.++## Per-route++| Route | Section | desktop err | desktop warn | mobile err | mobile warn |+|---|---|---|---|---|---|+| `/` | main | 1 | 0 | 0 | 0 |+| `/3d` | learn | 0 | 0 | 0 | 0 |+| `/activity` | crypto | 0 | 1 | 0 | 0 |+| `/agenc/embodied` | main | 0 | 0 | 0 | 0 |+| `/agenc/room` | main | 0 | 0 | 0 | 0 |+| `/agent-economy` | crypto | 0 | 0 | 0 | 0 |+| `/agent-economy-volume` | crypto | 0 | 1 | 0 | 0 |+| `/agent-exchange` | crypto | 0 | 0 | 0 | 0 |+| `/agent-identities` | agent-tools | 0 | 0 | 0 | 0 |+| `/agent-screen` | build | 0 | 0 | 0 | 0 |+| `/agent-studio` | build | 0 | 0 | 0 | 0 |+| `/agent-trade` | crypto | 0 | 0 | 0 | 0 |+| `/agent-wallet` | crypto | 0 | 1 | 0 | 0 |+| `/agents` | agent-tools | 0 | 1 | 0 | 0 |+| `/agents-live` | build | 0 | 0 | 0 | 0 |+| `/agi` | crypto | 0 | 1 | 0 | 0 |+| `/agora` | build | 0 | 0 | 0 | 0 |+| `/airdrops` | crypto | 0 | 1 | 0 | 1 |+| `/alpha-copilot` | main | 1 | 0 | 1 | 1 |+| `/animations` | main | 0 | 0 | 0 | 0 |+| `/app` | build | 0 | 0 | 0 | 0 |+| `/ar` | labs | 0 | 0 | 0 | 0 |+| `/ar/studio` | labs | 0 | 0 | 0 | 0 |+| `/ar/view` | labs | 0 | 0 | 0 | 0 |+| `/arbitrage` | crypto | 0 | 1 | 0 | 1 |+| `/arena` | crypto | 0 | 1 | 0 | 0 |+| `/artifact` | build | 0 | 0 | 0 | 0 |+| `/asl-alphabet` | main | 0 | 0 | 0 | 0 |+| `/assembly` | labs | 0 | 0 | 0 | 0 |+| `/assistant` | build | 0 | 0 | 0 | 0 |+| `/atlas` | main | 0 | 0 | 0 | 0 |+| `/autopilot` | main | 0 | 0 | 0 | 0 |+| `/autopilot-activity` | crypto | 0 | 0 | 0 | 0 |+| `/avatar-artifact` | labs | 0 | 0 | 0 | 0 |+| `/avatar-cli` | build | 0 | 0 | 0 | 0 |+| `/avatar-engines` | build | 0 | 0 | 0 | 0 |+| `/avatar-sdk` | build | 0 | 1 | 0 | 0 |+| `/avatar-studio` | build | 0 | 0 | 0 | 0 |+| `/avatar-wallet-chat` | crypto | 0 | 0 | 0 | 0 |+| `/aws` | learn | 0 | 0 | 0 | 0 |+| `/bazaar` | crypto | 0 | 1 | 0 | 1 |+| `/blog` | blog | 0 | 1 | 0 | 1 |+| `/blog/2500-new-animations` | blog | 0 | 0 | 0 | 1 |+| `/blog/3d-ai-crypto-convergence` | blog | 0 | 1 | 0 | 1 |+| `/blog/agent-3d-web-component` | blog | 0 | 0 | 0 | 1 |+| `/blog/agent-builder-studio-launch` | blog | 0 | 1 | 0 | 1 |+| `/blog/animation-emotion-control` | blog | 0 | 1 | 0 | 1 |+| `/blog/autonomous-trading-experiment` | blog | 0 | 1 | 0 | 1 |+| `/blog/concierge-3d-chat-widget` | blog | 0 | 1 | 0 | 1 |+| `/blog/first-autonomous-trade` | blog | 0 | 1 | 0 | 1 |+| `/blog/how-to-embed-3d-onchain-agents` | blog | 0 | 1 | 0 | 1 |+| `/blog/ibm-user-group-first-in-world-meetup-recap` | blog | 0 | 1 | 0 | 0 |+| `/blog/image-to-3d-on-nvidia-l4-and-blackwell` | blog | 0 | 1 | 0 | 0 |+| `/blog/inside-the-forge` | blog | 0 | 1 | 0 | 1 |+| `/blog/monetize-mcp-server-x402-paid-tools` | blog | 0 | 1 | 0 | 0 |+| `/blog/pumpfun-agent-payments-sdk` | blog | 0 | 1 | 0 | 1 |+| `/blog/real-time-voice-interaction` | blog | 0 | 1 | 0 | 1 |+| `/blog/see-your-3d-in-ar` | blog | 0 | 1 | 0 | 1 |+| `/blog/solana-wallet-integration` | blog | 0 | 1 | 0 | 1 |+| `/blog/text-to-3d-is-live` | blog | 0 | 1 | 0 | 1 |+| `/blog/three-token-listings` | blog | 0 | 1 | 0 | 1 |+| `/blog/three-ws-alibaba-cloud-partnership` | blog | 0 | 1 | 0 | 1 |+| `/blog/three-ws-aws-partner` | blog | 0 | 0 | 0 | 0 |+| `/blog/three-ws-dextools-social-boost-buyback` | blog | 0 | 1 | 0 | 1 |+| `/blog/three-ws-featured-on-alibaba-cloud-marketplace-blog` | blog | 0 | 1 | 0 | 1 |+| `/blog/three-ws-google-cloud-partnership` | blog | 0 | 1 | 0 | 1 |+| `/blog/three-ws-hackernoon-partnership` | blog | 0 | 1 | 0 | 1 |+| `/blog/three-ws-ibm-business-partner` | blog | 0 | 1 | 0 | 1 |+| `/blog/three-ws-ibm-collaboration` | blog | 0 | 1 | 0 | 1 |+| `/blog/three-ws-on-alibaba-cloud-marketplace` | blog | 0 | 1 | 0 | 1 |+| `/blog/three-ws-on-anthropic-mcp-registry` | blog | 0 | 1 | 0 | 0 |+| `/blog/three-ws-on-aws-marketplace` | blog | 0 | 1 | 0 | 1 |+| `/blog/three-ws-on-bnb-chain-dappbay` | blog | 0 | 1 | 0 | 1 |+| `/blog/three-ws-on-coinmarketcap` | blog | 0 | 1 | 0 | 1 |+| `/blog/three-ws-openai-select-partner` | blog | 0 | 1 | 0 | 0 |+| `/blog/three-ws-play-coin-communities` | blog | 0 | 0 | 0 | 0 |+| `/blog/three-ws-quicknode-startup-program` | blog | 0 | 1 | 0 | 1 |+| `/blog/three-ws-speraxusd-integration` | blog | 0 | 0 | 0 | 1 |+| `/blog/three-ws-x402-bazaar` | blog | 0 | 1 | 0 | 1 |+| `/blog/x402-stripe-for-agent-payments` | blog | 0 | 1 | 0 | 1 |+| `/bnb` | crypto | 0 | 1 | 0 | 1 |+| `/bnb-latency` | crypto | 0 | 1 | 0 | 1 |+| `/brain` | labs | 0 | 1 | 0 | 0 |+| `/brownout` | learn | 0 | 1 | 0 | 1 |+| `/bundles` | build | 0 | 1 | 0 | 0 |+| `/ca2x402` | build | 0 | 0 | 0 | 0 |+| `/capture` | build | 0 | 0 | 0 | 0 |+| `/categories` | crypto | 0 | 1 | 0 | 1 |+| `/cert` | crypto | 0 | 1 | 0 | 0 |+| `/chains` | crypto | 0 | 1 | 0 | 1 |+| `/changelog` | learn | 0 | 1 | 0 | 0 |+| `/character-library` | main | 0 | 0 | 0 | 0 |+| `/characters` | main | 0 | 0 | 0 | 0 |+| `/chat` | agent-tools | 0 | 0 | 0 | 0 |+| `/choreograph` | main | 0 | 0 | 0 | 0 |+| `/claim-wallet` | crypto | 0 | 1 | 0 | 0 |+| `/clash` | crypto | 0 | 2 | 0 | 2 |+| `/clip-director` | crypto | 0 | 1 | 0 | 0 |+| `/club` | crypto | 0 | 0 | 0 | 0 |+| `/coin-intel` | crypto | 0 | 1 | 0 | 1 |+| `/coin3d` | crypto | 0 | 0 | 0 | 0 |+| `/coins` | crypto | 0 | 1 | 0 | 0 |+| `/collection` | main | 0 | 0 | 0 | 0 |+| `/communities` | crypto | 0 | 0 | 0 | 0 |+| `/community` | main | 0 | 0 | 0 | 0 |+| `/companion` | main | 0 | 0 | 0 | 0 |+| `/compare` | crypto | 0 | 1 | 0 | 1 |+| `/compose` | build | 0 | 0 | 0 | 0 |+| `/concierge` | main | 0 | 0 | 0 | 0 |+| `/constellation` | crypto | 0 | 0 | 0 | 0 |+| `/conversions` | main | 0 | 0 | 0 | 0 |+| `/converter` | crypto | 0 | 1 | 0 | 1 |+| `/cookbook` | learn | 0 | 1 | 0 | 1 |+| `/cookbook/asset-quality-gate` | learn | 0 | 1 | 0 | 1 |+| `/cookbook/mcp-3d-tool` | learn | 0 | 1 | 0 | 1 |+| `/cookbook/parallel-asset-pack` | learn | 0 | 1 | 0 | 1 |+| `/cookbook/self-correcting-3d` | learn | 0 | 0 | 0 | 0 |+| `/cookbook/text-to-3d-cli` | learn | 0 | 1 | 0 | 1 |+| `/cosmos` | build | 0 | 0 | 0 | 0 |+| `/create` | build | 0 | 0 | 0 | 0 |+| `/create-agent` | build | 0 | 0 | 0 | 0 |+| `/create/prompt` | build | 0 | 0 | 0 | 0 |+| `/create/selfie` | build | 0 | 0 | 0 | 0 |+| `/create/video` | main | 0 | 0 | 0 | 0 |+| `/creations` | crypto | 0 | 1 | 0 | 0 |+| `/credits` | account | 0 | 1 | 0 | 0 |+| `/crews` | main | 0 | 0 | 0 | 0 |+| `/crypto` | learn | 0 | 1 | 0 | 0 |+| `/crypto-api` | learn | 0 | 1 | 0 | 0 |+| `/cz` | labs | 0 | 1 | 0 | 0 |+| `/dad` | build | 0 | 0 | 0 | 0 |+| `/daily` | labs | 0 | 0 | 0 | 0 |+| `/daily-match` | labs | 0 | 1 | 0 | 0 |+| `/dashboard` | account | 0 | 1 | 0 | 0 |+| `/dashboard/account` | account | 0 | 1 | 0 | 0 |+| `/dashboard/billing` | account | 0 | 1 | 0 | 0 |+| `/dashboard/capabilities` | crypto | 0 | 1 | 0 | 0 |+| `/dashboard/data-api` | account | 0 | 1 | 0 | 0 |+| `/dashboard/settings` | account | 0 | 1 | 0 | 0 |+| `/defi` | crypto | 0 | 1 | 0 | 1 |+| `/demo` | crypto | 0 | 0 | 0 | 0 |+| `/demos` | main | 0 | 0 | 0 | 0 |+| `/demos/agents` | main | 0 | 0 | 0 | 0 |+| `/deploy-onchain` | crypto | 0 | 1 | 0 | 1 |+| `/deployments` | crypto | 0 | 1 | 0 | 1 |+| `/derivatives` | crypto | 0 | 1 | 0 | 1 |+| `/dex-volumes` | crypto | 0 | 1 | 0 | 1 |+| `/diff` | build | 0 | 1 | 0 | 0 |+| `/diorama` | main | 0 | 0 | 0 | 0 |+| `/discover` | main | 1 | 0 | 0 | 0 |+| `/docs` | learn | 0 | 0 | 0 | 0 |+| `/docs/3d-api` | learn | 0 | 0 | 0 | 0 |+| `/docs/3d-asset-pipeline` | learn | 0 | 0 | 0 | 0 |+| `/docs/3d-pipeline` | learn | 0 | 0 | 0 | 0 |+| `/docs/3d-vision` | learn | 0 | 0 | 0 | 0 |+| `/docs/a2a-payments` | learn | 0 | 0 | 0 | 0 |+| `/docs/agenc` | learn | 0 | 0 | 0 | 0 |+| `/docs/agent-abilities` | learn | 0 | 0 | 0 | 0 |+| `/docs/agent-economy-volume` | learn | 0 | 0 | 0 | 0 |+| `/docs/agent-identities` | learn | 0 | 0 | 0 | 0 |+| `/docs/agent-index` | learn | 0 | 0 | 0 | 0 |+| `/docs/agent-manifest` | learn | 0 | 0 | 0 | 0 |+| `/docs/agent-reputation` | learn | 0 | 0 | 0 | 0 |+| `/docs/agent-runtime` | learn | 0 | 0 | 0 | 0 |+| `/docs/agent-screen-control` | learn | 0 | 0 | 0 | 0 |+| `/docs/agent-shell` | learn | 0 | 0 | 0 | 0 |+| `/docs/agent-skills` | learn | 0 | 0 | 0 | 0 |+| `/docs/agent-sniper` | learn | 0 | 0 | 0 | 0 |+| `/docs/agent-studio` | learn | 0 | 0 | 0 | 0 |+| `/docs/agent-symphony` | learn | 0 | 0 | 0 | 0 |+| `/docs/agent-system` | learn | 0 | 0 | 0 | 0 |+| `/docs/agent-tokens` | learn | 0 | 0 | 0 | 0 |+| `/docs/agent-vitals` | learn | 0 | 0 | 0 | 0 |+| `/docs/agent-wallet-api` | learn | 0 | 0 | 0 | 0 |+| `/docs/agent-wallets` | learn | 0 | 0 | 0 | 0 |+| `/docs/agents-vs-avatars` | learn | 0 | 0 | 0 | 0 |+| `/docs/agi` | learn | 0 | 0 | 0 | 0 |+| `/docs/airdrops` | learn | 0 | 0 | 0 | 0 |+| `/docs/alpha-copilot` | learn | 0 | 0 | 0 | 0 |+| `/docs/alpha-drip` | learn | 0 | 0 | 0 | 0 |+| `/docs/analytics-retention` | learn | 0 | 0 | 0 | 0 |+| `/docs/animation-seeding` | build | 0 | 0 | 0 | 0 |+| `/docs/animation-studio` | learn | 0 | 0 | 0 | 0 |+| `/docs/animations` | learn | 0 | 0 | 0 | 0 |+| `/docs/api-reference` | learn | 0 | 0 | 0 | 0 |+| `/docs/ar` | learn | 0 | 0 | 0 | 0 |+| `/docs/ar-studio` | learn | 0 | 0 | 0 | 0 |+| `/docs/architecture` | learn | 0 | 0 | 0 | 0 |+| `/docs/assistant-widget` | learn | 0 | 0 | 0 | 0 |+| `/docs/atlas` | learn | 0 | 0 | 0 | 0 |+| `/docs/authentication` | learn | 0 | 0 | 0 | 0 |+| `/docs/autonomous-economy` | learn | 0 | 0 | 0 | 0 |+| `/docs/autonomous-x402` | learn | 0 | 0 | 0 | 0 |+| `/docs/autopilot` | learn | 0 | 0 | 0 | 0 |+| `/docs/avatar-artifact` | learn | 0 | 0 | 0 | 0 |+| `/docs/avatar-cli` | learn | 0 | 0 | 0 | 0 |+| `/docs/avatar-creation` | learn | 0 | 0 | 0 | 0 |+| `/docs/avatar-engines` | learn | 0 | 0 | 0 | 0 |+| `/docs/avatar-inspector` | learn | 0 | 0 | 0 | 0 |+| `/docs/avatar-pipeline` | learn | 0 | 0 | 0 | 0 |+| `/docs/avatar-reconstruction` | learn | 0 | 0 | 0 | 0 |+| `/docs/avatar-studio` | learn | 0 | 0 | 0 | 0 |+| `/docs/avatar-thumbnails` | learn | 0 | 0 | 0 | 0 |+| `/docs/avatar-wardrobe` | learn | 0 | 0 | 0 | 0 |+| `/docs/aws-builder-center` | learn | 0 | 0 | 0 | 0 |+| `/docs/aws-builder-center-agent-payment-sessions` | learn | 0 | 0 | 0 | 0 |+| `/docs/aws-builder-center-marketplace-x402` | learn | 0 | 0 | 0 | 0 |+| `/docs/aws-builder-center-mcp-agents` | learn | 0 | 0 | 0 | 0 |+| `/docs/aws-marketplace` | learn | 0 | 0 | 0 | 0 |+| `/docs/aws-partner-spotlight` | learn | 0 | 0 | 0 | 0 |+| `/docs/blender-mcp` | learn | 0 | 0 | 0 | 0 |+| `/docs/bnb-payments` | learn | 0 | 0 | 0 | 0 |+| `/docs/brain` | learn | 0 | 0 | 0 | 0 |+| `/docs/brownout` | build | 0 | 0 | 0 | 0 |+| `/docs/ca2x402` | learn | 0 | 0 | 0 | 0 |+| `/docs/capture` | learn | 0 | 0 | 0 | 0 |+| `/docs/carplay` | learn | 0 | 0 | 0 | 0 |+| `/docs/changelog` | learn | 0 | 0 | 0 | 0 |+| `/docs/character-library` | learn | 0 | 0 | 0 | 0 |+| `/docs/character-studio` | learn | 0 | 0 | 0 | 0 |+| `/docs/chatgpt-3d-studio-gpt` | learn | 0 | 0 | 0 | 0 |+| `/docs/chatgpt-ar` | learn | 0 | 0 | 0 | 0 |+| `/docs/checkout-companion` | learn | 0 | 0 | 0 | 0 |+| `/docs/choreography` | learn | 0 | 0 | 0 | 0 |+| `/docs/circulation-engine` | learn | 0 | 0 | 0 | 0 |+| `/docs/clash` | learn | 0 | 0 | 0 | 0 |+| `/docs/coin-wars` | learn | 0 | 0 | 0 | 0 |+| `/docs/community` | learn | 0 | 0 | 0 | 0 |+| `/docs/companion` | learn | 0 | 0 | 0 | 0 |+| `/docs/compose` | learn | 0 | 0 | 0 | 0 |+| `/docs/concierge` | learn | 0 | 0 | 0 | 0 |+| `/docs/configuration` | learn | 0 | 0 | 0 | 0 |+| `/docs/contributing` | learn | 0 | 0 | 0 | 0 |+| `/docs/copy-trading` | learn | 0 | 0 | 0 | 0 |+| `/docs/cosmos` | learn | 0 | 0 | 0 | 0 |+| `/docs/create-agent` | build | 0 | 0 | 0 | 0 |+| `/docs/creator-portfolio` | learn | 0 | 0 | 0 | 0 |+| `/docs/crews` | learn | 0 | 0 | 0 | 0 |+| `/docs/crypto-api` | learn | 0 | 0 | 0 | 0 |+| `/docs/custody` | learn | 0 | 0 | 0 | 0 |+| `/docs/daily-forge` | learn | 0 | 0 | 0 | 0 |+| `/docs/daily-match` | learn | 0 | 0 | 0 | 0 |+| `/docs/deployment` | learn | 0 | 0 | 0 | 0 |+| `/docs/deployments` | learn | 0 | 0 | 0 | 0 |+| `/docs/DESIGN-TOKENS` | learn | 0 | 0 | 0 | 0 |+| `/docs/developer-platform` | learn | 0 | 0 | 0 | 0 |+| `/docs/diorama` | learn | 0 | 0 | 0 | 0 |+| `/docs/do-i-need-crypto` | learn | 0 | 0 | 0 | 0 |+| `/docs/docs-world` | learn | 0 | 0 | 0 | 0 |+| `/docs/draft-agent-mint` | learn | 0 | 0 | 0 | 0 |+| `/docs/drops` | learn | 0 | 0 | 0 | 0 |+| `/docs/economy-solver` | learn | 0 | 0 | 0 | 0 |+| `/docs/editor` | learn | 0 | 0 | 0 | 0 |+| `/docs/embedding` | learn | 0 | 0 | 0 | 0 |+| `/docs/embody` | learn | 0 | 0 | 0 | 0 |+| `/docs/erc8004` | learn | 0 | 0 | 0 | 0 |+| `/docs/event-souvenirs` | learn | 0 | 0 | 0 | 0 |+| `/docs/examples` | learn | 0 | 0 | 0 | 0 |+| `/docs/exit-lab` | learn | 0 | 0 | 0 | 0 |+| `/docs/fact-check` | learn | 0 | 0 | 0 | 0 |+| `/docs/farcaster-memory-seeding` | learn | 0 | 0 | 0 | 0 |+| `/docs/feedback` | learn | 0 | 0 | 0 | 0 |+| `/docs/first-contribution` | learn | 0 | 0 | 0 | 0 |+| `/docs/forge` | learn | 0 | 0 | 0 | 0 |+| `/docs/forge-background-generation` | learn | 0 | 0 | 0 | 0 |+| `/docs/forge-off` | learn | 0 | 0 | 0 | 0 |+| `/docs/forge-pipeline` | learn | 0 | 0 | 0 | 0 |+| `/docs/forged` | learn | 0 | 0 | 0 | 0 |+| `/docs/fork-trade` | learn | 0 | 0 | 0 | 0 |+| `/docs/free-llm-providers` | learn | 0 | 0 | 0 | 0 |+| `/docs/freshness` | learn | 0 | 0 | 0 | 0 |+| `/docs/galaxy` | learn | 0 | 0 | 0 | 0 |+| `/docs/generation-watch` | learn | 0 | 0 | 0 | 0 |+| `/docs/genesis` | learn | 0 | 0 | 0 | 0 |+| `/docs/genome` | learn | 0 | 0 | 0 | 0 |+| `/docs/ghost-copy` | learn | 0 | 0 | 0 | 0 |+| `/docs/github-memory-seeding` | learn | 0 | 0 | 0 | 0 |+| `/docs/glance` | build | 0 | 0 | 0 | 0 |+| `/docs/guardian` | learn | 0 | 0 | 0 | 0 |+| `/docs/guards` | learn | 0 | 0 | 0 | 0 |+| `/docs/herald` | learn | 0 | 0 | 0 | 0 |+| `/docs/hold-to-access` | learn | 0 | 0 | 0 | 0 |+| `/docs/home-households` | learn | 0 | 0 | 0 | 0 |+| `/docs/home-plans` | learn | 0 | 0 | 0 | 0 |+| `/docs/home-privacy` | learn | 0 | 0 | 0 | 0 |+| `/docs/home-relay` | learn | 0 | 0 | 0 | 0 |+| `/docs/home-relay-threat-model` | learn | 0 | 0 | 0 | 0 |+| `/docs/home-satellite` | learn | 0 | 0 | 0 | 0 |+| `/docs/home-scene` | learn | 0 | 0 | 0 | 0 |+| `/docs/home-security` | learn | 0 | 0 | 0 | 0 |+| `/docs/home-voice` | learn | 0 | 0 | 0 | 0 |+| `/docs/how-forge-works` | learn | 0 | 0 | 0 | 0 |+| `/docs/how-it-works` | learn | 0 | 0 | 0 | 0 |+| `/docs/huggingface` | learn | 0 | 0 | 0 | 0 |+| `/docs/i18n` | learn | 0 | 0 | 0 | 0 |+| `/docs/ibm` | learn | 0 | 0 | 0 | 0 |+| `/docs/ibm-community` | learn | 0 | 0 | 0 | 0 |+| `/docs/ibm-x402-mcp` | learn | 0 | 0 | 0 | 0 |+| `/docs/image-to-3d` | learn | 0 | 0 | 0 | 0 |+| `/docs/in-game-economy` | learn | 0 | 0 | 0 | 0 |+| `/docs/inference-node-operator` | learn | 0 | 0 | 0 | 0 |+| `/docs/integrations` | learn | 0 | 0 | 0 | 0 |+| `/docs/introduction` | learn | 0 | 0 | 0 | 0 |+| `/docs/ios-app` | learn | 0 | 0 | 0 | 0 |+| `/docs/irl` | learn | 0 | 0 | 0 | 0 |+| `/docs/js-api` | learn | 0 | 0 | 0 | 0 |+| `/docs/knock` | learn | 0 | 0 | 0 | 0 |+| `/docs/kol-tracker` | learn | 0 | 0 | 0 | 0 |+| `/docs/labor-market` | learn | 0 | 0 | 0 | 0 |+| `/docs/layers` | learn | 0 | 0 | 0 | 0 |+| `/docs/likeness-eval` | learn | 0 | 0 | 0 | 0 |+| `/docs/lipsync` | learn | 0 | 0 | 0 | 0 |+| `/docs/liquid-glass` | learn | 0 | 0 | 0 | 0 |+| `/docs/listings` | learn | 0 | 0 | 0 | 0 |+| `/docs/live-docs` | learn | 0 | 0 | 0 | 0 |+| `/docs/live-steps` | learn | 0 | 0 | 0 | 0 |+| `/docs/make-your-agent` | learn | 0 | 0 | 0 | 0 |+| `/docs/market-data-api` | learn | 0 | 0 | 0 | 0 |+| `/docs/marketplace` | learn | 0 | 0 | 0 | 0 |+| `/docs/materialize` | learn | 0 | 0 | 0 | 0 |+| `/docs/mcp` | learn | 0 | 0 | 0 | 0 |+| `/docs/mcp-3d-studio` | learn | 0 | 0 | 0 | 0 |+| `/docs/mcp-agent` | learn | 0 | 0 | 0 | 0 |+| `/docs/mcp-intel` | learn | 0 | 0 | 0 | 0 |+| `/docs/mcp-marketplace` | learn | 0 | 0 | 0 | 0 |+| `/docs/mcp-naming` | learn | 0 | 0 | 0 | 0 |+| `/docs/mcp-safety` | learn | 0 | 0 | 0 | 0 |+| `/docs/mcp-scenes` | learn | 0 | 0 | 0 | 0 |+| `/docs/mcp-studio` | learn | 0 | 0 | 0 | 0 |+| `/docs/mcp-tools` | learn | 0 | 0 | 0 | 0 |+| `/docs/mcp-vanity` | learn | 0 | 0 | 0 | 0 |+| `/docs/mcp-x402` | learn | 0 | 0 | 0 | 0 |+| `/docs/mcp-x402-bazaar` | learn | 0 | 0 | 0 | 0 |+| `/docs/media-api` | learn | 0 | 0 | 0 | 0 |+| `/docs/memory` | learn | 0 | 0 | 0 | 0 |+| `/docs/mint-mark` | learn | 0 | 0 | 0 | 0 |+| `/docs/minted` | learn | 0 | 0 | 0 | 0 |+| `/docs/mocap-studio` | learn | 0 | 0 | 0 | 0 |+| `/docs/model-diff` | learn | 0 | 0 | 0 | 0 |+| `/docs/money-feed` | learn | 0 | 0 | 0 | 0 |+| `/docs/money-flow-map` | learn | 0 | 0 | 0 | 0 |+| `/docs/monitor` | learn | 0 | 0 | 0 | 0 |+| `/docs/motion-swap` | learn | 0 | 0 | 0 | 0 |+| `/docs/multi-agent` | learn | 0 | 0 | 0 | 0 |+| `/docs/native-widgets` | build | 0 | 0 | 0 | 0 |+| `/docs/news-rights` | learn | 0 | 0 | 0 | 0 |+| `/docs/notifications` | learn | 0 | 0 | 0 | 0 |+| `/docs/nvidia-inception` | learn | 0 | 0 | 0 | 0 |+| `/docs/nvidia-inception/index.html` | learn | 0 | 0 | 0 | 0 |+| `/docs/nvidia-models` | learn | 0 | 0 | 0 | 0 |+| `/docs/nvidia-nemotron-spotlight` | learn | 0 | 0 | 0 | 0 |+| `/docs/object-library` | learn | 0 | 0 | 0 | 0 |+| `/docs/okx-marketplace` | learn | 0 | 0 | 0 | 0 |+| `/docs/onboarding-tier` | learn | 0 | 0 | 0 | 0 |+| `/docs/onchain-agents` | learn | 0 | 0 | 0 | 0 |+| `/docs/open-source-ecosystem` | learn | 0 | 0 | 0 | 0 |+| `/docs/open-source-footprint` | learn | 0 | 0 | 0 | 0 |+| `/docs/oracle` | learn | 0 | 0 | 0 | 0 |+| `/docs/oracle-model` | learn | 0 | 0 | 0 | 0 |+| `/docs/overlay-audit` | learn | 0 | 0 | 0 | 0 |+| `/docs/package-extraction` | learn | 0 | 0 | 0 | 0 |+| `/docs/page-performance` | learn | 0 | 0 | 0 | 0 |+| `/docs/partners` | learn | 0 | 0 | 0 | 0 |+| `/docs/payment-sessions` | learn | 0 | 0 | 0 | 0 |+| `/docs/permissions` | learn | 0 | 0 | 0 | 0 |+| `/docs/persona-hub` | learn | 0 | 0 | 0 | 0 |+| `/docs/pill-mascot` | learn | 0 | 0 | 0 | 0 |+| `/docs/plan-checkout` | learn | 0 | 0 | 0 | 0 |+| `/docs/play-forge-in-world` | learn | 0 | 0 | 0 | 0 |+| `/docs/play-hardening` | learn | 0 | 0 | 0 | 0 |+| `/docs/play-live-events` | learn | 0 | 0 | 0 | 0 |+| `/docs/play-vehicles` | learn | 0 | 0 | 0 | 0 |+| `/docs/pocket` | learn | 0 | 0 | 0 | 0 |+| `/docs/portal` | build | 0 | 0 | 0 | 0 |+| `/docs/portfolio` | learn | 0 | 0 | 0 | 0 |+| `/docs/premium` | learn | 0 | 0 | 0 | 0 |+| `/docs/press-kit` | learn | 0 | 0 | 0 | 0 |+| `/docs/procedural-animation` | learn | 0 | 0 | 0 | 0 |+| `/docs/product-demo` | learn | 0 | 0 | 0 | 0 |+| `/docs/PROTOCOL-vanity` | learn | 0 | 0 | 0 | 0 |+| `/docs/provenance` | learn | 0 | 0 | 0 | 0 |+| `/docs/pump-claims-channel` | learn | 0 | 0 | 0 | 0 |+| `/docs/pump-launcher` | learn | 0 | 0 | 0 | 0 |+| `/docs/quick-start` | learn | 0 | 0 | 0 | 0 |+| `/docs/radar` | learn | 0 | 0 | 0 | 0 |+| `/docs/reasoning-ledger` | learn | 0 | 0 | 0 | 0 |+| `/docs/recurring-payments` | learn | 0 | 0 | 0 | 0 |+| `/docs/remix` | learn | 0 | 0 | 0 | 0 |+| `/docs/reputation` | learn | 0 | 0 | 0 | 0 |+| `/docs/reputation-staking-market` | learn | 0 | 0 | 0 | 0 |+| `/docs/resilience` | learn | 0 | 0 | 0 | 0 |+| `/docs/restyle` | learn | 0 | 0 | 0 | 0 |+| `/docs/rig-doctor` | learn | 0 | 0 | 0 | 0 |+| `/docs/risk-acknowledgment` | learn | 0 | 0 | 0 | 0 |+| `/docs/sas-attestations` | learn | 0 | 0 | 0 | 0 |+| `/docs/scene-studio` | learn | 0 | 0 | 0 | 0 |+| `/docs/sdk` | learn | 0 | 0 | 0 | 0 |+| `/docs/security` | learn | 0 | 0 | 0 | 0 |+| `/docs/seed-quality` | learn | 0 | 0 | 0 | 0 |+| `/docs/seeker-app` | learn | 0 | 0 | 0 | 0 |+| `/docs/seeker-publishing` | learn | 0 | 0 | 0 | 0 |+| `/docs/seeker-submission-day` | learn | 0 | 0 | 0 | 0 |+| `/docs/seeker-video` | learn | 0 | 0 | 0 | 0 |+| `/docs/selfie-to-avatar` | learn | 0 | 0 | 0 | 0 |+| `/docs/share-and-embed` | learn | 0 | 0 | 0 | 0 |+| `/docs/shared-utilities` | learn | 0 | 0 | 0 | 0 |+| `/docs/shipfeed` | learn | 0 | 0 | 0 | 0 |+| `/docs/showcase` | learn | 0 | 0 | 0 | 0 |+| `/docs/sign-language` | learn | 0 | 0 | 0 | 0 |+| `/docs/signals` | learn | 0 | 0 | 0 | 0 |+| `/docs/sim-readiness` | learn | 0 | 0 | 0 | 0 |+| `/docs/site-performance` | learn | 0 | 0 | 0 | 0 |+| `/docs/sketchfab` | learn | 0 | 0 | 0 | 0 |+| `/docs/skill-bundles` | learn | 0 | 0 | 0 | 0 |+| `/docs/skill-royalties` | learn | 0 | 0 | 0 | 0 |+| `/docs/skills` | learn | 0 | 0 | 0 | 0 |+| `/docs/smart-contracts` | learn | 0 | 0 | 0 | 0 |+| `/docs/smart-home` | learn | 0 | 0 | 0 | 0 |+| `/docs/smart-money` | learn | 0 | 0 | 0 | 0 |+| `/docs/sniper-autonomy` | learn | 0 | 0 | 0 | 0 |+| `/docs/social-layer` | learn | 0 | 0 | 0 | 0 |+| `/docs/solana` | learn | 0 | 0 | 0 | 0 |+| `/docs/solana-reputation` | learn | 0 | 0 | 0 | 0 |+| `/docs/spatial-mcp` | learn | 0 | 0 | 0 | 0 |+| `/docs/splat` | learn | 0 | 0 | 0 | 0 |+| `/docs/spotlight` | learn | 0 | 0 | 0 | 0 |+| `/docs/stage` | learn | 0 | 0 | 0 | 0 |+| `/docs/start-here` | learn | 0 | 0 | 0 | 0 |+| `/docs/strategy-objects` | learn | 0 | 0 | 0 | 0 |+| `/docs/swarms` | learn | 0 | 0 | 0 | 0 |+| `/docs/talking-avatar-video` | learn | 0 | 0 | 0 | 0 |+| `/docs/terminal` | learn | 0 | 0 | 0 | 0 |+| `/docs/the-first-19-weeks` | learn | 0 | 0 | 0 | 0 |+| `/docs/three-microbuy` | learn | 0 | 0 | 0 | 0 |+| `/docs/three-thesis` | learn | 0 | 0 | 0 | 0 |+| `/docs/timeline` | learn | 0 | 0 | 0 | 0 |+| `/docs/token-gated-3d-embeds` | learn | 0 | 0 | 0 | 0 |+| `/docs/tokens-xyz` | learn | 0 | 0 | 0 | 0 |+| `/docs/trader-card` | learn | 0 | 0 | 0 | 0 |+| `/docs/trader-passport` | learn | 0 | 0 | 0 | 0 |+| `/docs/trading-arenas` | learn | 0 | 0 | 0 | 0 |+| `/docs/trading-copilot` | learn | 0 | 0 | 0 | 0 |+| `/docs/trading-experiment` | learn | 0 | 0 | 0 | 0 |+| `/docs/trading-hub` | learn | 0 | 0 | 0 | 0 |+| `/docs/trading-surfaces` | learn | 0 | 0 | 0 | 0 |+| `/docs/triage` | learn | 0 | 0 | 0 | 0 |+| `/docs/troubleshooting` | learn | 0 | 0 | 0 | 0 |+| `/docs/trust-primitives` | learn | 0 | 0 | 0 | 0 |+| `/docs/tty` | learn | 0 | 0 | 0 | 0 |+| `/docs/tty-avatar` | learn | 0 | 0 | 0 | 0 |+| `/docs/tutorials/earn-and-spend-in-play` | learn | 0 | 0 | 0 | 0 |+| `/docs/tutorials/write-a-guard` | learn | 0 | 0 | 0 | 0 |+| `/docs/ui-juice` | learn | 0 | 0 | 0 | 0 |+| `/docs/user-wallet` | learn | 0 | 0 | 0 | 0 |+| `/docs/validation` | learn | 0 | 0 | 0 | 0 |+| `/docs/vanity` | learn | 0 | 0 | 0 | 0 |+| `/docs/vaults` | learn | 0 | 0 | 0 | 0 |+| `/docs/viability` | learn | 0 | 0 | 0 | 0 |+| `/docs/viewer` | learn | 0 | 0 | 0 | 0 |+| `/docs/voice-lab` | learn | 0 | 0 | 0 | 0 |+| `/docs/vscode` | learn | 0 | 0 | 0 | 0 |+| `/docs/walk` | learn | 0 | 1 | 0 | 0 |+| `/docs/walk-leaderboard` | learn | 0 | 0 | 0 | 0 |+| `/docs/web-component` | learn | 0 | 0 | 0 | 0 |+| `/docs/widget-api` | learn | 0 | 0 | 0 | 0 |+| `/docs/widget-studio` | learn | 0 | 0 | 0 | 0 |+| `/docs/widgets` | learn | 0 | 1 | 0 | 1 |+| `/docs/witness` | learn | 0 | 0 | 0 | 0 |+| `/docs/world` | learn | 0 | 0 | 0 | 0 |+| `/docs/world-lines` | learn | 0 | 0 | 0 | 0 |+| `/docs/x-memory-seeding` | learn | 0 | 0 | 0 | 0 |+| `/docs/x402` | learn | 0 | 0 | 0 | 0 |+| `/docs/x402-buyer` | learn | 0 | 0 | 0 | 0 |+| `/docs/x402-dev-tools` | learn | 0 | 0 | 0 | 0 |+| `/docs/x402-distribution` | learn | 0 | 0 | 0 | 0 |+| `/docs/x402-endpoints` | learn | 0 | 0 | 0 | 0 |+| `/docs/x402-preflight` | learn | 0 | 0 | 0 | 0 |+| `/docs/x402-ring-economy` | learn | 0 | 0 | 0 | 0 |+| `/docs/x402-studio` | learn | 0 | 0 | 0 | 0 |+| `/drive` | main | 0 | 0 | 0 | 0 |+| `/drops` | crypto | 0 | 1 | 0 | 0 |+| `/economy` | crypto | 0 | 1 | 0 | 1 |+| `/economy-lab` | labs | 0 | 1 | 0 | 0 |+| `/embed-doctor` | build | 0 | 0 | 0 | 0 |+| `/eth-vanity` | crypto | 0 | 1 | 0 | 0 |+| `/event` | crypto | 0 | 1 | 0 | 0 |+| `/events/build-3d-agents-live` | learn | 0 | 1 | 0 | 1 |+| `/evm-wallet` | crypto | 0 | 1 | 0 | 0 |+| `/examples` | learn | 0 | 1 | 0 | 0 |+| `/exchanges` | crypto | 0 | 1 | 0 | 1 |+| `/exit-lab` | crypto | 0 | 1 | 0 | 0 |+| `/fact-check` | crypto | 0 | 1 | 0 | 1 |+| `/fact-checker` | crypto | 0 | 0 | 0 | 0 |+| `/fear-greed` | crypto | 0 | 1 | 0 | 1 |+| `/features` | build | 0 | 0 | 0 | 0 |+| `/features/agent-exchange` | build | 0 | 0 | 0 | 0 |+| `/features/ar` | build | 0 | 0 | 0 | 0 |+| `/features/deploy` | build | 0 | 0 | 0 | 0 |+| `/features/forge` | build | 0 | 0 | 0 | 0 |+| `/features/marketplace` | build | 0 | 0 | 0 | 0 |+| `/features/play` | build | 0 | 0 | 0 | 0 |+| `/features/scan` | build | 0 | 0 | 0 | 0 |+| `/features/studio` | build | 0 | 0 | 0 | 0 |+| `/features/walk` | build | 0 | 0 | 0 | 0 |+| `/feed` | main | 0 | 0 | 0 | 0 |+| `/fees` | crypto | 0 | 1 | 0 | 1 |+| `/fits` | crypto | 0 | 1 | 0 | 0 |+| `/flow` | crypto | 0 | 0 | 0 | 0 |+| `/forever` | crypto | 0 | 1 | 0 | 0 |+| `/forge` | build | 0 | 0 | 0 | 0 |+| `/forge-max` | build | 0 | 0 | 0 | 0 |+| `/forge-nim` | build | 0 | 0 | 0 | 0 |+| `/forge-spark` | build | 0 | 0 | 0 | 0 |+| `/forge-studio` | build | 0 | 0 | 0 | 0 |+| `/forged` | main | 0 | 0 | 0 | 0 |+| `/forgot-password` | account | 0 | 0 | 0 | 0 |+| `/galaxy` | labs | 0 | 1 | 0 | 1 |+| `/gallery` | main | 0 | 0 | 0 | 0 |+| `/gas` | crypto | 0 | 1 | 0 | 1 |+| `/genesis` | build | 0 | 0 | 0 | 0 |+| `/genome` | build | 0 | 0 | 0 | 0 |+| `/gestures` | main | 0 | 0 | 0 | 0 |+| `/ghost-copy` | crypto | 0 | 1 | 0 | 1 |+| `/glance` | build | 0 | 0 | 0 | 0 |+| `/glossary` | learn | 0 | 1 | 0 | 0 |+| `/gmgn` | crypto | 0 | 1 | 0 | 1 |+| `/go` | crypto | 0 | 0 | 0 | 0 |+| `/guardian` | crypto | 0 | 1 | 0 | 1 |+| `/guards` | learn | 0 | 1 | 0 | 1 |+| `/hacks` | crypto | 0 | 1 | 0 | 1 |+| `/heatmap` | crypto | 0 | 1 | 0 | 1 |+| `/herald` | main | 0 | 0 | 0 | 0 |+| `/hero-demo` | crypto | 0 | 0 | 0 | 0 |+| `/holo` | labs | 0 | 1 | 0 | 0 |+| `/hydrate` | build | 0 | 0 | 0 | 0 |+| `/ibm/hello` | crypto | 4 | 0 | 4 | 0 |+| `/ibm/x402-demo` | crypto | 0 | 0 | 0 | 0 |+| `/image-to-3d` | build | 0 | 0 | 0 | 0 |+| `/import/rpm` | build | 0 | 0 | 0 | 0 |+| `/inspect` | build | 0 | 0 | 0 | 0 |+| `/integrations` | build | 0 | 0 | 0 | 0 |+| `/irl` | main | 0 | 0 | 0 | 0 |+| `/irl-privacy` | main | 0 | 0 | 0 | 0 |+| `/irl/sign` | main | 1 | 0 | 0 | 0 |+| `/knock` | main | 0 | 0 | 0 | 0 |+| `/labor-market` | crypto | 0 | 1 | 0 | 0 |+| `/labs` | labs | 0 | 0 | 0 | 0 |+| `/launch` | crypto | 0 | 1 | 0 | 0 |+| `/launch-studio` | crypto | 0 | 1 | 0 | 0 |+| `/launcher` | crypto | 0 | 0 | 0 | 0 |+| `/launches` | crypto | 0 | 0 | 0 | 0 |+| `/launchpad` | labs | 0 | 0 | 0 | 0 |+| `/leaderboard` | crypto | 0 | 1 | 0 | 0 |+| `/ledger` | agent-tools | 0 | 1 | 0 | 0 |+| `/legal` | legal | 0 | 1 | 0 | 0 |+| `/legal/content-policy` | legal | 0 | 1 | 0 | 1 |+| `/legal/eula` | legal | 0 | 1 | 0 | 1 |+| `/legal/nvidia-ngc-eula` | legal | 0 | 1 | 0 | 1 |+| `/legal/privacy` | legal | 0 | 1 | 0 | 1 |+| `/legal/risk` | legal | 0 | 1 | 0 | 1 |+| `/legal/tos` | legal | 0 | 1 | 0 | 0 |+| `/lipsync` | labs | 0 | 1 | 0 | 1 |+| `/lipsync/mic` | labs | 0 | 1 | 0 | 0 |+| `/live` | crypto | 0 | 0 | 0 | 0 |+| `/login` | account | 0 | 1 | 0 | 0 |+| `/lookup` | crypto | 0 | 1 | 0 | 1 |+| `/marketplace` | main | 0 | 0 | 0 | 0 |+| `/marketplace/analytics` | main | 0 | 0 | 0 | 0 |+| `/markets` | crypto | 0 | 1 | 0 | 0 |+| `/markets/archive` | crypto | 0 | 1 | 0 | 0 |+| `/markets/digest` | crypto | 0 | 1 | 0 | 0 |+| `/markets/news` | crypto | 1 | 1 | 0 | 0 |+| `/markets/news/article` | crypto | 0 | 1 | 0 | 0 |+| `/markets/robinhood` | crypto | 0 | 1 | 0 | 0 |+| `/markets/trending` | crypto | 0 | 1 | 0 | 1 |+| `/materialize` | build | 0 | 0 | 0 | 0 |+| `/mcp-tools` | learn | 0 | 1 | 0 | 1 |+| `/meta-allocator` | crypto | 0 | 1 | 0 | 0 |+| `/minted` | crypto | 0 | 1 | 0 | 1 |+| `/mirror` | crypto | 0 | 1 | 0 | 0 |+| `/mocap-studio` | main | 0 | 0 | 0 | 0 |+| `/monitor` | build | 0 | 0 | 0 | 0 |+| `/motion-swap` | build | 0 | 0 | 0 | 0 |+| `/my-agents` | agent-tools | 0 | 1 | 0 | 0 |+| `/news` | learn | 0 | 0 | 0 | 0 |+| `/nim-forge` | build | 0 | 0 | 0 | 0 |+| `/notifications` | main | 0 | 0 | 0 | 0 |+| `/nvidia` | main | 0 | 0 | 0 | 0 |+| `/objects` | main | 0 | 0 | 0 | 0 |+| `/openai` | main | 0 | 0 | 0 | 0 |+| `/oracle` | crypto | 0 | 1 | 0 | 0 |+| `/oracle-lab` | crypto | 0 | 0 | 0 | 0 |+| `/oracle/arm` | crypto | 0 | 1 | 0 | 1 |+| `/oracle/docs` | crypto | 0 | 1 | 0 | 0 |+| `/partners` | main | 0 | 0 | 0 | 0 |+| `/pay` | crypto | 0 | 1 | 0 | 0 |+| `/pay/simulator` | account | 0 | 1 | 0 | 0 |+| `/payments` | account | 0 | 1 | 0 | 0 |+| `/pill` | crypto | 0 | 1 | 0 | 0 |+| `/pipeline` | crypto | 0 | 1 | 0 | 0 |+| `/pitch` | main | 0 | 0 | 0 | 0 |+| `/play` | crypto | 0 | 0 | 0 | 0 |+| `/play/agent-wallet` | crypto | 0 | 0 | 0 | 0 |+| `/play/arena` | crypto | 0 | 0 | 0 | 0 |+| `/play/economy` | crypto | 0 | 0 | 0 | 0 |+| `/play/solver` | crypto | 0 | 0 | 0 | 0 |+| `/play/ufo` | crypto | 0 | 0 | 0 | 0 |+| `/play/war` | crypto | 0 | 0 | 0 | 0 |+| `/playground` | labs | 0 | 0 | 0 | 0 |+| `/pocket` | labs | 0 | 1 | 0 | 0 |+| `/portal` | main | 0 | 0 | 0 | 0 |+| `/portfolio` | crypto | 0 | 1 | 0 | 1 |+| `/pose` | build | 0 | 0 | 0 | 0 |+| `/preflight` | agent-tools | 0 | 1 | 0 | 0 |+| `/press` | main | 0 | 0 | 0 | 0 |+| `/pricing` | main | 0 | 0 | 0 | 0 |+| `/profile` | account | 0 | 1 | 0 | 0 |+| `/proof` | crypto | 0 | 1 | 0 | 0 |+| `/providers` | crypto | 0 | 1 | 0 | 1 |+| `/pulse` | crypto | 0 | 1 | 0 | 1 |+| `/pump-dashboard` | crypto | 0 | 0 | 0 | 1 |+| `/pump-live` | crypto | 0 | 0 | 0 | 0 |+| `/pump-visualizer` | crypto | 0 | 1 | 0 | 0 |+| `/pumpfun` | crypto | 0 | 1 | 0 | 0 |+| `/radar` | crypto | 0 | 0 | 0 | 0 |+| `/rankings` | labs | 0 | 1 | 0 | 1 |+| `/receipts` | crypto | 0 | 1 | 0 | 0 |+| `/recurring` | crypto | 0 | 1 | 0 | 1 |+| `/register` | account | 0 | 0 | 0 | 0 |+| `/render-lab` | build | 0 | 1 | 0 | 1 |+| `/reputation` | agent-tools | 0 | 1 | 0 | 0 |+| `/reputation/market` | agent-tools | 0 | 1 | 0 | 0 |+| `/restyle` | build | 0 | 0 | 0 | 0 |+| `/rig-doctor` | build | 0 | 1 | 0 | 0 |+| `/scene` | build | 0 | 0 | 0 | 0 |+| `/screener` | crypto | 0 | 1 | 0 | 1 |+| `/search` | main | 0 | 0 | 0 | 0 |+| `/seeker` | build | 0 | 0 | 0 | 0 |+| `/settings` | account | 0 | 1 | 0 | 0 |+| `/ship` | learn | 0 | 1 | 0 | 1 |+| `/shopper` | crypto | 0 | 0 | 0 | 0 |+| `/showcase` | main | 0 | 0 | 0 | 0 |+| `/sign-language` | main | 0 | 0 | 0 | 0 |+| `/sign-mirror` | main | 0 | 0 | 0 | 0 |+| `/signals` | crypto | 0 | 1 | 0 | 1 |+| `/sitemap` | main | 0 | 0 | 0 | 0 |+| `/skills` | main | 0 | 0 | 0 | 0 |+| `/smart-home` | build | 0 | 0 | 0 | 0 |+| `/smart-home/join` | build | 0 | 0 | 0 | 0 |+| `/smart-home/plan` | build | 0 | 0 | 0 | 0 |+| `/smart-home/privacy` | build | 0 | 0 | 0 | 0 |+| `/smart-home/satellite` | build | 0 | 0 | 0 | 0 |+| `/smart-money` | crypto | 0 | 1 | 0 | 1 |+| `/sniper/experiments` | crypto | 0 | 1 | 0 | 0 |+| `/spatial-mcp` | labs | 1 | 0 | 1 | 0 |+| `/sperax` | crypto | 0 | 1 | 0 | 0 |+| `/splat` | build | 0 | 0 | 0 | 0 |+| `/spotlight` | agent-tools | 2 | 1 | 0 | 0 |+| `/stablecoins` | crypto | 0 | 1 | 0 | 1 |+| `/stage` | crypto | 0 | 0 | 0 | 0 |+| `/start` | build | 0 | 0 | 0 | 0 |+| `/status` | learn | 0 | 1 | 0 | 0 |+| `/strategies` | crypto | 0 | 1 | 0 | 0 |+| `/strategy-lab` | crypto | 0 | 1 | 0 | 1 |+| `/stream` | build | 0 | 1 | 0 | 1 |+| `/studio` | build | 0 | 0 | 0 | 0 |+| `/support` | learn | 0 | 0 | 0 | 0 |+| `/swarms` | crypto | 0 | 1 | 0 | 0 |+| `/symphony` | labs | 0 | 1 | 0 | 1 |+| `/temporary` | main | 10 | 0 | 0 | 0 |+| `/terminal` | crypto | 0 | 0 | 0 | 0 |+| `/theater` | crypto | 0 | 0 | 0 | 0 |+| `/three` | crypto | 0 | 1 | 0 | 1 |+| `/three-live` | crypto | 0 | 1 | 0 | 1 |+| `/three-token` | crypto | 0 | 0 | 0 | 0 |+| `/threews/claim` | build | 0 | 0 | 0 | 0 |+| `/timeline` | main | 0 | 0 | 0 | 0 |+| `/tour` | main | 0 | 0 | 0 | 0 |+| `/tour-builder` | learn | 0 | 0 | 0 | 0 |+| `/tour/atlas` | main | 0 | 0 | 0 | 0 |+| `/tracker` | crypto | 0 | 1 | 0 | 0 |+| `/trades` | crypto | 0 | 1 | 0 | 1 |+| `/trading` | crypto | 0 | 1 | 0 | 0 |+| `/trending` | crypto | 0 | 1 | 0 | 1 |+| `/tty` | build | 0 | 1 | 0 | 1 |+| `/tutor` | crypto | 0 | 1 | 0 | 1 |+| `/tutorials` | learn | 0 | 1 | 0 | 1 |+| `/tutorials/add-a-3d-assistant` | learn | 0 | 1 | 0 | 0 |+| `/tutorials/agent-personality` | learn | 0 | 0 | 0 | 0 |+| `/tutorials/agent-reputation` | learn | 0 | 1 | 0 | 0 |+| `/tutorials/agent-spending-envelope` | learn | 0 | 0 | 0 | 0 |+| `/tutorials/animate-your-agent` | learn | 0 | 1 | 0 | 0 |+| `/tutorials/animate-your-avatar` | learn | 0 | 0 | 0 | 0 |+| `/tutorials/arm-an-agent-sniper` | learn | 0 | 1 | 0 | 0 |+| `/tutorials/build-a-3d-asset-pipeline` | learn | 0 | 1 | 0 | 0 |+| `/tutorials/build-a-scene` | learn | 0 | 1 | 0 | 0 |+| `/tutorials/build-a-site-concierge` | learn | 0 | 1 | 0 | 0 |+| `/tutorials/character-library-to-embed` | learn | 0 | 1 | 0 | 0 |+| `/tutorials/claim-threews-name` | learn | 0 | 1 | 0 | 0 |+| `/tutorials/connect-ai-brain` | learn | 0 | 0 | 0 | 0 |+| `/tutorials/connect-your-home` | learn | 0 | 1 | 0 | 0 |+| `/tutorials/create-and-edit-memory` | learn | 0 | 1 | 0 | 0 |+| `/tutorials/custom-skill` | learn | 0 | 0 | 0 | 0 |+| `/tutorials/customize-appearance` | learn | 0 | 0 | 0 | 0 |+| `/tutorials/deploy-to-vercel-custom-domain` | learn | 0 | 0 | 0 | 0 |+| `/tutorials/earn-and-spend-in-play` | learn | 0 | 1 | 0 | 0 |+| `/tutorials/embed-in-30-seconds` | learn | 0 | 0 | 0 | 1 |+| `/tutorials/embed-on-website` | learn | 0 | 1 | 0 | 0 |+| `/tutorials/emotion-from-data` | learn | 0 | 1 | 0 | 0 |+| `/tutorials/explore-docs-world` | learn | 0 | 0 | 0 | 0 |+| `/tutorials/find-a-better-exit-policy` | learn | 0 | 1 | 0 | 0 |+| `/tutorials/first-agent` | learn | 0 | 0 | 0 | 0 |+| `/tutorials/first-prompt-to-3d` | learn | 0 | 1 | 0 | 0 |+| `/tutorials/generate-3d-api` | learn | 0 | 1 | 0 | 0 |+| `/tutorials/getting-started` | learn | 0 | 0 | 0 | 0 |+| `/tutorials/greeting-and-first-speech` | learn | 0 | 0 | 0 | 0 |+| `/tutorials/image-to-3d` | learn | 0 | 1 | 0 | 0 |+| `/tutorials/import-avatar-url` | learn | 0 | 1 | 0 | 0 |+| `/tutorials/js-api-events` | learn | 0 | 1 | 0 | 0 |+| `/tutorials/mcp-server-for-your-agent` | learn | 0 | 0 | 0 | 0 |+| `/tutorials/mine-vanity-address` | learn | 0 | 1 | 0 | 0 |+| `/tutorials/mint-pumpfun-token` | learn | 0 | 1 | 0 | 0 |+| `/tutorials/monetize-mcp-server` | learn | 0 | 1 | 0 | 0 |+| `/tutorials/multi-agent-coordination` | learn | 0 | 1 | 0 | 0 |+| `/tutorials/nvidia-3d-free` | learn | 0 | 1 | 0 | 0 |+| `/tutorials/nvidia-nim-self-host` | learn | 0 | 1 | 0 | 0 |+| `/tutorials/paid-x402-endpoint` | learn | 0 | 1 | 0 | 0 |+| `/tutorials/pay-for-x402-service` | learn | 0 | 1 | 0 | 1 |+| `/tutorials/personal-ai-site` | learn | 0 | 1 | 0 | 0 |+| `/tutorials/place-agent-irl` | learn | 0 | 1 | 0 | 0 |+| `/tutorials/prompts-for-3d` | learn | 0 | 1 | 0 | 0 |+| `/tutorials/read-the-trading-fleet` | learn | 0 | 1 | 0 | 1 |+| `/tutorials/register-onchain` | learn | 0 | 1 | 0 | 1 |+| `/tutorials/render-avatar-images` | learn | 0 | 0 | 0 | 0 |+| `/tutorials/self-host-agent-backend` | learn | 0 | 1 | 0 | 0 |+| `/tutorials/selfie-to-avatar` | learn | 0 | 1 | 0 | 0 |+| `/tutorials/sell-a-skill-with-a-trial` | learn | 0 | 1 | 0 | 0 |+| `/tutorials/share-your-agent` | learn | 0 | 0 | 0 | 0 |+| `/tutorials/ship-an-avatar-manifest` | learn | 0 | 0 | 0 | 0 |+| `/tutorials/shopify-shopping-assistant` | learn | 0 | 1 | 0 | 0 |+| `/tutorials/shopify-store-guide` | learn | 0 | 1 | 0 | 0 |+| `/tutorials/shopify-store-guide-advanced` | learn | 0 | 1 | 0 | 0 |+| `/tutorials/sign-with-your-avatar` | learn | 0 | 1 | 0 | 0 |+| `/tutorials/skill-with-database-auth` | learn | 0 | 1 | 0 | 0 |+| `/tutorials/solana-agent-reputation` | learn | 0 | 1 | 0 | 0 |+| `/tutorials/sperax-tour` | learn | 0 | 1 | 0 | 0 |+| `/tutorials/swap-avatar-in-studio` | learn | 0 | 1 | 0 | 0 |+| `/tutorials/text-to-3d` | learn | 0 | 1 | 0 | 0 |+| `/tutorials/trigger-from-page-events` | learn | 0 | 0 | 0 | 0 |+| `/tutorials/upload-custom-glb` | learn | 0 | 1 | 0 | 0 |+| `/tutorials/view-in-ar` | learn | 0 | 0 | 0 | 0 |+| `/tutorials/voice-and-lipsync` | learn | 0 | 0 | 0 | 0 |+| `/tutorials/walk-companion` | learn | 0 | 1 | 0 | 0 |+| `/tutorials/wallet-sign-in` | learn | 0 | 1 | 0 | 0 |+| `/tutorials/web-component-end-to-end` | learn | 0 | 1 | 0 | 0 |+| `/tutorials/write-a-guard` | learn | 0 | 0 | 0 | 0 |+| `/tutorials/x402-server-sdk` | learn | 0 | 1 | 0 | 0 |+| `/unstoppable` | crypto | 0 | 0 | 0 | 0 |+| `/validation` | build | 0 | 0 | 0 | 0 |+| `/vanity-wallet` | crypto | 0 | 1 | 0 | 1 |+| `/vanity/bounties` | crypto | 0 | 1 | 0 | 1 |+| `/vanity/gallery` | crypto | 0 | 1 | 0 | 1 |+| `/vanity/premium` | crypto | 0 | 1 | 0 | 1 |+| `/vanity/verify` | crypto | 0 | 1 | 0 | 1 |+| `/vault` | crypto | 0 | 1 | 0 | 1 |+| `/vaults` | crypto | 0 | 1 | 0 | 0 |+| `/viability` | crypto | 0 | 1 | 0 | 0 |+| `/viewer` | labs | 0 | 0 | 0 | 0 |+| `/voice` | build | 0 | 0 | 0 | 0 |+| `/voice/home` | build | 0 | 0 | 0 | 0 |+| `/walk` | main | 0 | 0 | 0 | 0 |+| `/walk-leaderboard` | labs | 0 | 1 | 0 | 0 |+| `/walkthroughs` | learn | 0 | 1 | 0 | 1 |+| `/walkthroughs/build-your-first-agent` | learn | 0 | 1 | 0 | 0 |+| `/walkthroughs/embed-a-3d-avatar` | learn | 0 | 1 | 0 | 0 |+| `/walkthroughs/find-an-agent-worth-using` | learn | 0 | 1 | 0 | 0 |+| `/walkthroughs/forge-your-first-3d-model` | learn | 0 | 1 | 0 | 1 |+| `/wallet` | crypto | 0 | 1 | 0 | 0 |+| `/wardrobe` | main | 0 | 0 | 0 | 0 |+| `/watch` | labs | 0 | 0 | 0 | 0 |+| `/watchlist` | crypto | 0 | 0 | 0 | 1 |+| `/what-is` | main | 0 | 0 | 0 | 0 |+| `/widgets` | build | 0 | 0 | 0 | 0 |+| `/world-lines` | main | 0 | 0 | 0 | 0 |+| `/wrapped` | crypto | 0 | 1 | 0 | 0 |+| `/x402` | crypto | 0 | 0 | 0 | 0 |+| `/x402/studio` | crypto | 0 | 0 | 0 | 0 |+| `/yields` | crypto | 0 | 1 | 0 | 1 |++## Failures (detail)++### `/` (main)+- **desktop**+ - nav: navigation failed: page.goto: net::ERR_CONNECTION_REFUSED at http://localhost:43521/+Call log:+ - navigating to "http://localhost:43521/", waiting until "domcontentloaded"+++### `/discover` (main)+- **desktop**+ - nav: navigation failed: page.goto: net::ERR_CONNECTION_REFUSED at http://localhost:43521/discover+Call log:+ - navigating to "http://localhost:43521/discover", waiting until "domcontentloaded"+++### `/temporary` (main)+- **desktop**+ - console: Failed to load resource: net::ERR_BLOCKED_BY_RESPONSE.NotSameOrigin+ - console: Failed to load resource: net::ERR_BLOCKED_BY_RESPONSE.NotSameOrigin+ - console: Failed to load resource: net::ERR_BLOCKED_BY_RESPONSE.NotSameOrigin+ - console: Failed to load resource: net::ERR_BLOCKED_BY_RESPONSE.NotSameOrigin+ - console: Failed to load resource: net::ERR_BLOCKED_BY_RESPONSE.NotSameOrigin+ - console: Failed to load resource: net::ERR_BLOCKED_BY_RESPONSE.NotSameOrigin+ - console: Failed to load resource: net::ERR_BLOCKED_BY_RESPONSE.NotSameOrigin+ - console: Failed to load resource: net::ERR_BLOCKED_BY_RESPONSE.NotSameOrigin+ - console: Failed to load resource: net::ERR_BLOCKED_BY_RESPONSE.NotSameOrigin+ - console: Failed to load resource: net::ERR_BLOCKED_BY_RESPONSE.NotSameOrigin++### `/irl/sign` (main)+- **desktop**+ - nav: navigation failed: page.goto: Timeout 30000ms exceeded.+Call log:+ - navigating to "http://localhost:43521/irl/sign", waiting until "domcontentloaded"+++### `/alpha-copilot` (main)+- **desktop**+ - console: Failed to load resource: the server responded with a status of 404 (Not Found)+- **mobile**+ - console: Failed to load resource: the server responded with a status of 404 (Not Found)++### `/spatial-mcp` (labs)+- **desktop**+ - console: $l: fetch for "https://three.ws/cdn/forge/anon/eddcea57-a278-474a-a632-99ca99861755.glb" responded with 502:+ at https://cdn.jsdelivr.net/npm/@google/[email protected]/dist/model-viewer.min.js:17:507206+- **mobile**+ - console: $l: fetch for "https://three.ws/cdn/forge/anon/eddcea57-a278-474a-a632-99ca99861755.glb" responded with 502:+ at https://cdn.jsdelivr.net/npm/@google/[email protected]/dist/model-viewer.min.js:17:507206++### `/ibm/hello` (crypto)+- **desktop**+ - console: Access to script at 'https://three.ws/ios-bridge.72176eee.js' from origin 'http://localhost:43521' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.+ - console: Failed to load resource: net::ERR_FAILED+ - console: Access to script at 'https://three.ws/atlas.js' from origin 'http://localhost:43521' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.+ - console: Failed to load resource: net::ERR_FAILED+- **mobile**+ - console: Access to script at 'https://three.ws/ios-bridge.72176eee.js' from origin 'http://localhost:43521' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.+ - console: Failed to load resource: net::ERR_FAILED+ - console: Access to script at 'https://three.ws/atlas.js' from origin 'http://localhost:43521' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.+ - console: Failed to load resource: net::ERR_FAILED++### `/markets/news` (crypto)+- **desktop**+ - console: Failed to load resource: the server responded with a status of 404 (Not Found)++### `/spotlight` (agent-tools)+- **desktop**+ - console: Failed to load resource: net::ERR_FAILED+ - console: [agent-3d] boot failed TypeError: Failed to fetch+ at witnessFetch (http://localhost:43521/packages/witness/src/recorder.js:271:33)+ at eu.load (https://three.ws/agent-3d/latest/agent-3d.js:5:28780)+ at i3.load (https://three.ws/agent-3d/latest/agent-3d.js:4104:61420)+ at https://three.ws/agent-3d/latest/agent-3d.js:4526:18235+++## Warnings (detail)++### `/alpha-copilot` (main)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/avatar-sdk` (build)+- RGBELoader has been deprecated. Please use HDRLoader instead.++### `/render-lab` (build)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/diff` (build)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/rig-doctor` (build)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/bundles` (build)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/tty` (build)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/stream` (build)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/brain` (labs)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/lipsync` (labs)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/lipsync/mic` (labs)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/rankings` (labs)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/daily-match` (labs)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/walk-leaderboard` (labs)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/galaxy` (labs)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/symphony` (labs)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/economy-lab` (labs)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/holo` (labs)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/cz` (labs)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/pocket` (labs)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/sperax` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/agi` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/oracle` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/oracle/docs` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/oracle/arm` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/activity` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/pipeline` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/guardian` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/launch` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/launch-studio` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/drops` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/minted` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/cert` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/creations` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/pulse` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/fits` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/receipts` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/viability` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/deployments` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/deploy-onchain` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/portfolio` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/airdrops` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/clash` (crypto)+- clash: CoinCommunities unconfigured, polling stopped Error: CoinCommunities is not configured+ at apiFetch (http://localhost:43521/src/clash.js:94:33)+ at async poll (http://localhost:43521/src/clash.js:301:16)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/leaderboard` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/tracker` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/proof` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/labor-market` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/vaults` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/signals` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/dashboard/capabilities` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/arena` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/trending` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/trades` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/claim-wallet` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/ghost-copy` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/wrapped` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/meta-allocator` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/clip-director` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/pay` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/sniper/experiments` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/smart-money` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/pumpfun` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/watchlist` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/pump-dashboard` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/strategy-lab` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/recurring` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/strategies` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/vanity-wallet` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/fact-check` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/vanity/verify` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/vanity/gallery` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/vanity/premium` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/vanity/bounties` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/eth-vanity` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/pump-visualizer` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/coin-intel` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/coins` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/heatmap` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/fear-greed` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/gas` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/compare` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/screener` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/categories` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/exchanges` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/derivatives` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/converter` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/defi` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/chains` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/stablecoins` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/yields` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/fees` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/dex-volumes` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/hacks` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/markets/trending` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/bnb` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/bnb-latency` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/vault` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/bazaar` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/lookup` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/arbitrage` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/providers` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/gmgn` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/three` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/three-live` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/tutor` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/forever` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/economy` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/agent-economy-volume` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/evm-wallet` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/markets` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/markets/robinhood` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/markets/news` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/markets/news/article` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/markets/archive` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/markets/digest` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/event` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/mirror` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/swarms` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/agent-wallet` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/wallet` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/trading` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/exit-lab` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/pill` (crypto)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/agents` (agent-tools)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/spotlight` (agent-tools)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/ledger` (agent-tools)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/my-agents` (agent-tools)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/reputation` (agent-tools)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/reputation/market` (agent-tools)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/preflight` (agent-tools)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/credits` (account)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/payments` (account)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/pay/simulator` (account)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/login` (account)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/dashboard` (account)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/dashboard/account` (account)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/dashboard/data-api` (account)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/dashboard/billing` (account)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/dashboard/settings` (account)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/settings` (account)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/profile` (account)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/crypto` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/crypto-api` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/docs/walk` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/docs/widgets` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/tutorials` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/walkthroughs` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/walkthroughs/forge-your-first-3d-model` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/walkthroughs/build-your-first-agent` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/walkthroughs/embed-a-3d-avatar` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/walkthroughs/find-an-agent-worth-using` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/examples` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/tutorials/text-to-3d` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/tutorials/build-a-3d-asset-pipeline` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/tutorials/add-a-3d-assistant` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/tutorials/image-to-3d` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/tutorials/prompts-for-3d` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/tutorials/generate-3d-api` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/tutorials/nvidia-3d-free` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/tutorials/nvidia-nim-self-host` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/tutorials/first-prompt-to-3d` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/tutorials/agent-reputation` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/tutorials/solana-agent-reputation` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/tutorials/shopify-shopping-assistant` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/tutorials/shopify-store-guide` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/tutorials/shopify-store-guide-advanced` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/status` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/glossary` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/events/build-3d-agents-live` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/changelog` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/ship` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/tutorials/sign-with-your-avatar` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/tutorials/build-a-scene` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/tutorials/arm-an-agent-sniper` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/cookbook` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/cookbook/text-to-3d-cli` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/cookbook/parallel-asset-pack` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/cookbook/mcp-3d-tool` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/cookbook/asset-quality-gate` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/tutorials/wallet-sign-in` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/tutorials/character-library-to-embed` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/tutorials/sell-a-skill-with-a-trial` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/tutorials/find-a-better-exit-policy` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/tutorials/read-the-trading-fleet` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/mcp-tools` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/tutorials/embed-in-30-seconds` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/tutorials/swap-avatar-in-studio` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/tutorials/selfie-to-avatar` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/tutorials/import-avatar-url` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/tutorials/walk-companion` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/tutorials/sperax-tour` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/tutorials/embed-on-website` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/tutorials/personal-ai-site` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/tutorials/js-api-events` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/tutorials/web-component-end-to-end` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/tutorials/build-a-site-concierge` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/tutorials/upload-custom-glb` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/tutorials/create-and-edit-memory` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/tutorials/place-agent-irl` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/tutorials/pay-for-x402-service` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/tutorials/emotion-from-data` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/tutorials/register-onchain` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/tutorials/mint-pumpfun-token` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/tutorials/paid-x402-endpoint` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/tutorials/monetize-mcp-server` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/tutorials/x402-server-sdk` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/tutorials/self-host-agent-backend` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/tutorials/multi-agent-coordination` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/tutorials/skill-with-database-auth` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/tutorials/claim-threews-name` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/tutorials/mine-vanity-address` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/guards` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/brownout` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/tutorials/earn-and-spend-in-play` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/tutorials/animate-your-agent` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/tutorials/connect-your-home` (learn)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/blog` (blog)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/blog/ibm-user-group-first-in-world-meetup-recap` (blog)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/blog/image-to-3d-on-nvidia-l4-and-blackwell` (blog)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/blog/monetize-mcp-server-x402-paid-tools` (blog)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/blog/three-ws-openai-select-partner` (blog)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/blog/autonomous-trading-experiment` (blog)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/blog/first-autonomous-trade` (blog)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/blog/concierge-3d-chat-widget` (blog)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/blog/inside-the-forge` (blog)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/blog/three-ws-quicknode-startup-program` (blog)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/blog/three-ws-alibaba-cloud-partnership` (blog)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/blog/x402-stripe-for-agent-payments` (blog)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/blog/see-your-3d-in-ar` (blog)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/blog/text-to-3d-is-live` (blog)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/blog/3d-ai-crypto-convergence` (blog)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/blog/three-ws-dextools-social-boost-buyback` (blog)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/blog/three-ws-featured-on-alibaba-cloud-marketplace-blog` (blog)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/blog/three-ws-ibm-collaboration` (blog)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/blog/three-ws-on-aws-marketplace` (blog)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/blog/agent-3d-web-component` (blog)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/blog/2500-new-animations` (blog)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/blog/three-ws-x402-bazaar` (blog)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/blog/real-time-voice-interaction` (blog)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/blog/three-ws-on-alibaba-cloud-marketplace` (blog)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/blog/three-ws-on-bnb-chain-dappbay` (blog)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/blog/three-ws-hackernoon-partnership` (blog)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/blog/three-ws-on-coinmarketcap` (blog)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/blog/how-to-embed-3d-onchain-agents` (blog)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/blog/pumpfun-agent-payments-sdk` (blog)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/blog/three-ws-speraxusd-integration` (blog)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/blog/agent-builder-studio-launch` (blog)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/blog/animation-emotion-control` (blog)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/blog/three-ws-ibm-business-partner` (blog)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/blog/three-token-listings` (blog)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/blog/solana-wallet-integration` (blog)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/blog/three-ws-google-cloud-partnership` (blog)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/blog/three-ws-on-anthropic-mcp-registry` (blog)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/legal` (legal)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/legal/privacy` (legal)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/legal/eula` (legal)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/legal/nvidia-ngc-eula` (legal)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/legal/tos` (legal)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/legal/risk` (legal)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++### `/legal/content-policy` (legal)+- [walk] avatar "81a076b6-55ff-49a2-b007-1d88e7dce2aa" failed to load - falling back to "robot" fetch for "http://localhost:43521/api/avatars/81a076b6-55ff-49a2-b007-1d88e7dce2aa/glb" responded with 502: Bad Gateway++---++<a id="sec-114"></a>++> **Source:** `docs/audit/python-deps-2026-09-07.md` · [↑ table of contents](#table-of-contents)++# Python worker dependencies: first OSV scan, 2026-09-07++The first vulnerability scan of the Python half of the platform. `npm audit`+covers the JavaScript tree; nothing covered the 20 requirements files that pin+the runtime of every GPU and CPU worker, so nothing ever had.++Reproduce with `npm run audit:deps` ([scripts/check-deps.mjs](../scripts/check-deps.mjs)).+It queries [OSV](https://osv.dev) for every exact-pinned requirement under+`workers/`, `services/` and `packages/`.++**First run: 321 advisories across 19 pinned package versions, out of 100+pinned packages in 20 files.** After the fixes below: 285 across 17.++## Fixed in this pass++Both were chosen the same way: severity, times whether a caller's bytes reach+the vulnerable code.++### Pillow 11.0.0 to 12.3.0 (rembg, remesh, texture)++34 advisories, 13 of them HIGH: heap out-of-bounds writes in `Image.paste()` and+`Image.crop()` via signed coordinate overflow, an out-of-bounds write in the PSD+loader, a controlled heap write in `ImageCmsTransform.apply()`, an out-of-bounds+read on the mmap path, and a family of decompression-bomb bypasses in the font+and PDF loaders.++All three workers decode an image the caller supplied. This was the most directly+reachable finding in the scan.++Verified before bumping:++- The rembg worker's full smoke test (20 checks, both baked-in models) passes on+ Pillow 12.3.0, and so does the BiRefNet path added earlier today.+- `pip check` is clean on the rembg requirement set.+- No package pinned in remesh or texture caps Pillow below 12; `transformers`+ is the only one that constrains it at all, at `>=10.0.1,<=15.0`.+- Every PIL symbol those two workers use (`Image.LANCZOS`, `Image.NEAREST`,+ `fromarray`, `new`, `composite`, `open`, `resize`, `convert`) exists in 12.3.0+ and the exact call chain round-trips.++remesh and texture were bumped on that evidence rather than a functional run:+their images need a build to exercise, which happens on their next deploy.++### usd-core 24.11 to 25.11 (remesh)++`GHSA-58p5-r2f6-g2cj`, CRITICAL: a `Sdf_PathNode` use-after-free leading to+potential remote code execution, plus a MODERATE file-parsing use-after-free of+the same class.++Exposure here was narrower than the severity suggests: remesh only *authors* USD+(`Usd.Stage.CreateNew`), it never parses a caller's USD file. A pinned CRITICAL+is still not a thing to keep. Verified that 25.11 imports the same module set the+worker uses (`Gf, Sdf, Usd, UsdGeom, UsdShade, UsdUtils, Vt`) and that+`UsdUtils.CreateNewUsdzPackage` still produces a valid USDZ.++## What is left, in priority order++### 1. `libassimp5`, not `pyassimp` (remesh, stylize)++33 advisories against `pyassimp==5.2.5`, and **bumping the pin cannot fix any of+them**: 5.2.5 is the last release on PyPI, and the vulnerable code is the assimp+C++ library, which both Dockerfiles install from Debian as `libassimp-dev+libassimp5`. The scanner points at the Python binding because that is what a+requirements file can name.++This matters because assimp is the trimesh backend for **FBX and DAE input**, so+a caller's mesh file goes through it. The lever is the base image: rebuild both+workers on a Debian release carrying a patched `libassimp5`, or drop the FBX/DAE+input path to Blender, which remesh already ships for FBX export.++### 2. `transformers` 4.41.0 / 4.46.0 / 4.46.3 / 4.47.1 (longcat, hunyuan3d, triposg, texture)++43 advisories each, 6 HIGH, fixed in 5.0.0. Two different classes hide in that+number and they need separating before anyone bumps a major version across four+GPU workers:++- **Unsafe deserialization when loading a model or config.** Not caller+ reachable: every worker loads pinned weights we staged ourselves.+- **ReDoS in tokenizer and config regexes.** Potentially caller reachable, because+ a user's text prompt does reach a tokenizer on the generation lanes.++Read the second class first; it decides whether this is urgent or housekeeping.++### 3. `torch` 2.3.1 (texture)++23 advisories, one CRITICAL: `torch.load` with `weights_only=True` leading to+remote code execution. Same reachability answer as transformers, the worker loads+its own weights. The fix is 2.7.1, which is a CUDA-compatibility decision for the+whole image rather than a pin edit, so it belongs with the next texture worker+rebuild.++### 4. The cheap ones++| Package | Pinned | Fixed in | Worker |+|---|---|---|---|+| `requests` | 2.32.3 | 2.33.0 | avatar-reconstruction |+| `pynacl` | 1.5.0 | 1.6.2 | stylize |+| `rembg` | 2.0.56 / 2.0.59 / 2.0.65 | 2.0.75 | avatar-reconstruction, model-triposr, model-hunyuan3d, rembg |+| `diffusers` | 0.30.0 / 0.31.0 / 0.35.1 | 0.38.0 | model-hunyuan3d, model-triposg, texture, longcat |+| `onnx` | 1.18.0 | 1.22.0 | longcat |+| `pytorch-lightning` | 1.9.5 | 2.4.0 | model-hunyuan3d (2.1 image) |+| `basicsr` | 1.4.2 | no fix published | model-hunyuan3d (2.1 image) |++`requests` and `pynacl` are one-line bumps with no model-behaviour risk and+should go with the next deploy of those workers. `rembg` changes the inference+path this platform's cutouts run on, so it wants the same treatment BiRefNet got:+run the worker's smoke test against the new version first.+`pytorch-lightning` 1.9.5 to 2.4.0 is a major version inside a GPU image whose+Python stack is already pinned around torch 2.5, and `basicsr` has no fixed+release at all, so both are constrained by the Hunyuan 2.1 image rather than by+the pin.++## Notes on the scan itself++- **`npm run audit:deps` needs network and is deliberately not in the gate.** A+ build must not fail because api.osv.dev is having a bad afternoon. It is+ registered as an on-demand guard in [data/guards.json](../data/guards.json).+- **It only sees exact pins.** `pkg>=1.2`, `pkg~=1.2` and a bare `pkg` resolve to+ whatever the build found that day, which is a reproducibility problem before it+ is a security one. `node scripts/check-deps.mjs --unpinned` lists them.+- **A locally built wheel is queried on its public version.** The CUDA wheels+ (`torch-cluster==1.6.3+pt21cu121`) are our rebuild of an upstream release, and+ OSV indexes the release.+- **The parser is tested** ([tests/check-deps.test.js](../tests/check-deps.test.js)),+ including an assertion that every requirement line in the tree is classified.+ A parser that silently drops a line reports a package clean without ever+ looking at it, which is worse than not scanning.++---++<a id="sec-115"></a>> **Source:** `docs/authentication.md` · [↑ table of contents](#table-of-contents)@@ -34221,7 +36492,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-261) (`POST /api/herald/announce`); the scope the `herald-mcp` package's `THREE_WS_API_KEY` needs |+| `herald:announce` | Post announcements through the [Herald](#sec-269) (`POST /api/herald/announce`); the scope the `herald-mcp` package's `THREE_WS_API_KEY` needs |Scopes are space-separated in the `scope` field. Default when unspecified: `avatars:read avatars:write`.@@ -34421,7 +36692,7 @@ three.ws examples repo, so it is installed, run, and link-checked before every r----<a id="sec-113"></a>+<a id="sec-116"></a>> **Source:** `docs/autonomous-economy.md` · [↑ table of contents](#table-of-contents)@@ -34436,8 +36707,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-335) (which wallet receives each *payment*),-[Economy master](#sec-200) (the funding-root subsystem in depth), and the+Companion docs: [Money map](#sec-346) (which wallet receives each *payment*),+[Economy master](#sec-205) (the funding-root subsystem in depth), and the[Solana signers runbook](../api/_lib/solana-signers.js) (every signer, its floor, andhow to fund it).@@ -34576,16 +36847,16 @@ zero.## Related-- [Money map](#sec-335) — which wallet receives each kind of payment, and the+- [Money map](#sec-346) — which wallet receives each kind of payment, and theplatform's cut.-- [Economy master](#sec-200) — the funding-root subsystem, its ledger, and the+- [Economy master](#sec-205) — the funding-root subsystem, its ledger, and thetopup/sweepback crons in depth.-- [x402 ring economy](#sec-621) — how the autonomous payment ring settles+- [x402 ring economy](#sec-642) — how the autonomous payment ring settlesUSDC between agents.----<a id="sec-114"></a>+<a id="sec-117"></a>> **Source:** `docs/autonomous-x402.md` · [↑ table of contents](#table-of-contents)@@ -34612,7 +36883,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-199)) rather than by its own schedule+[economy heartbeat](#sec-204)) rather than by its own scheduleentry; per-entry Redis cooldowns decide what actually fires on any given tick.Each tick:@@ -34662,7 +36933,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-154)+This loop's treasury is **separate** from the [circulation engine](#sec-158)treasury (`CIRCULATION_TREASURY_SECRET`). Circulation funds agent-to-agent SOL /$THREE activity; this loop funds USDC intel purchases. They do not fund eachother.@@ -34746,7 +37017,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-154), real `agent_hire` commerce,+> [Circulation engine](#sec-158), real `agent_hire` commerce,> discovery), not a heavier self-paid sweep.**Excluding it is mechanical, not a matter of remembering to.**@@ -34819,7 +37090,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-240).+[Financial controls](#sec-246).## Where results land@@ -34828,21 +37099,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-333)). |+| `agent_custody_events` | The USDC spend, with `category: 'x402'` (see [Money feed](#sec-344)). || `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-240)). |+| `payment_reconciliation` | One verdict per settlement claim from the daily reconciliation job (see [Financial controls](#sec-246)). || Dedicated stores | Pipeline-specific tables (pricing tracker, reputation snapshots, leaderboard, sniper analytics, …). |## Related-- [x402 endpoints](#sec-619) — the paid endpoints this loop calls.-- [Financial controls](#sec-240): where settlements land and how the reconciliation job audits them.-- [x402 buyer client](#sec-616) — the client wrappers it pays with.-- [Circulation engine](#sec-154) — the separate SOL/$THREE activity loop.+- [x402 endpoints](#sec-640) — the paid endpoints this loop calls.+- [Financial controls](#sec-246): where settlements land and how the reconciliation job audits them.+- [x402 buyer client](#sec-637) — the client wrappers it pays with.+- [Circulation engine](#sec-158) — the separate SOL/$THREE activity loop.----<a id="sec-115"></a>+<a id="sec-118"></a>> **Source:** `docs/autopilot.md` · [↑ table of contents](#table-of-contents)@@ -34937,15 +37208,15 @@ A confirmed buyback narrates as: "Bought back and burned $120 of $YOURCOIN. Supp## Related-- [Custody you can verify](#sec-187) - the spend limits, freeze switch, and audit trail every agent wallet runs under-- [Financial controls](#sec-240) - plain-English spend rules layered on the same enforcement point-- [Oracle](#sec-364) - the conviction engine and the agent action loop that arms an agent to trade autonomously+- [Custody you can verify](#sec-191) - the spend limits, freeze switch, and audit trail every agent wallet runs under+- [Financial controls](#sec-246) - plain-English spend rules layered on the same enforcement point+- [Oracle](#sec-376) - 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-116"></a>+<a id="sec-119"></a>> **Source:** `docs/avatar-artifact.md` · [↑ table of contents](#table-of-contents)@@ -34953,7 +37224,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-575) 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-595) 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.---@@ -35017,7 +37288,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-436) instead. This page is the plain viewer.+For a full chat widget or a token-gated embed, use [Share and embed](#sec-453) instead. This page is the plain viewer.---@@ -35071,14 +37342,14 @@ A large model on a slow connection is not a failure: the loading overlay reports## Related-- [The 3D viewer](#sec-575): the full engine behind `/app` and `<agent-3d>`-- [Share and embed](#sec-436): widgets, web components and embed policy+- [The 3D viewer](#sec-595): the full engine behind `/app` and `<agent-3d>`+- [Share and embed](#sec-453): 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-097): the clip library this page retargets from----<a id="sec-117"></a>+<a id="sec-120"></a>> **Source:** `docs/avatar-cli.md` · [↑ table of contents](#table-of-contents)@@ -35090,7 +37361,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-578) 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-599) covers the `<agent-3d>` element the CLI emits.---@@ -35284,7 +37555,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-578) 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-599) 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:@@ -35381,14 +37652,14 @@ three-ws-avatar validate manifest.json --json | jq -e '.valid'## Where to go next-- **[Ship an avatar manifest](#sec-536)** 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-578)** documents every attribute on the `<agent-3d>` element `preview` emits.+- **[Ship an avatar manifest](#sec-556)** 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-599)** 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-118"></a>+<a id="sec-121"></a>> **Source:** `docs/avatar-creation.md` · [↑ table of contents](#table-of-contents)@@ -35427,7 +37698,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-120) 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-123) 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.@@ -35660,7 +37931,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-206) 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-211) for details.---@@ -35724,7 +37995,7 @@ No regeneration provider is configured on this deployment. Set `AVATAR_REGEN_PRO----<a id="sec-119"></a>+<a id="sec-122"></a>> **Source:** `docs/avatar-engines.md` · [↑ table of contents](#table-of-contents)@@ -35786,7 +38057,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-458). |+| `splat` | View in Splat Viewer | Produces Gaussian-splat or radiance-field output you can drop into the three.ws [splat viewer](#sec-476). || `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. |@@ -35893,16 +38164,16 @@ To add an engine, append an entry to `ENGINES` in [`src/avatar-engines-data.js`]## Related-- [Splat Viewer](#sec-458): where the Gaussian-splat output of the `splat` engines actually renders in the browser.-- [Scene Capture](#sec-145): the three.ws side of reconstruction, turning real video into 3D, adjacent to the photoreal-head family here.-- [Forge](#sec-245): the live commercial generation pipeline, which the one `live` text-to-avatar engine powers.+- [Splat Viewer](#sec-476): where the Gaussian-splat output of the `splat` engines actually renders in the browser.+- [Scene Capture](#sec-149): the three.ws side of reconstruction, turning real video into 3D, adjacent to the photoreal-head family here.+- [Forge](#sec-251): the live commercial generation pipeline, which the one `live` text-to-avatar engine powers.- [Agent Identity Studio](#sec-054): that pipeline applied end to end, brand brief to rigged avatar plus studio renders.- [Animations](#sec-097): the retargeting and clip library that drives the production rigs in the last family.-- [Avatar pipeline](#sec-122) and [avatar creation](#sec-118): how three.ws produces and processes its own mesh avatars.+- [Avatar pipeline](#sec-125) and [avatar creation](#sec-121): how three.ws produces and processes its own mesh avatars.----<a id="sec-120"></a>+<a id="sec-123"></a>> **Source:** `docs/avatar-fidelity-program.md` · [↑ table of contents](#table-of-contents)@@ -35914,7 +38185,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-123); the worker lives in+[avatar-reconstruction.md](#sec-126); the worker lives in[`workers/avatar-reconstruction/`](../workers/avatar-reconstruction).## Why we are not buying this@@ -36360,7 +38631,7 @@ items do not:----<a id="sec-121"></a>+<a id="sec-124"></a>> **Source:** `docs/avatar-inspector.md` · [↑ table of contents](#table-of-contents)@@ -36468,7 +38739,7 @@ Related reading: [agent reputation](#sec-057) · [Agora](#sec-077).----<a id="sec-122"></a>+<a id="sec-125"></a>> **Source:** `docs/avatar-pipeline.md` · [↑ table of contents](#table-of-contents)@@ -36477,8 +38748,8 @@ Related reading: [agent reputation](#sec-057) · [Agora](#sec-077).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-118),-[Avatar Studio](#sec-149), [Animations](#sec-097),+individual tool docs ([Avatar creation](#sec-121),+[Avatar Studio](#sec-153), [Animations](#sec-097),[3D asset pipeline](#sec-002)) into one map.---@@ -36505,7 +38776,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-316), [x402 endpoints](#sec-619)).+[MCP tools](#sec-327), [x402 endpoints](#sec-640)).### ② Auto-rig@@ -36582,22 +38853,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-118) and-[Avatar Studio](#sec-149) for the authoring UIs, and-[Mesh editing tools](#sec-316) for retexture / stylize / remesh / segment /+account. See [Avatar creation](#sec-121) and+[Avatar Studio](#sec-153) for the authoring UIs, and+[Mesh editing tools](#sec-327) for retexture / stylize / remesh / segment /pose operations.## Related-- [Selfie → Avatar reconstruction](#sec-123) — 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-126) — 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-097) — the clip library and retargeting in depth.- [3D asset pipeline](#sec-002) — formats, optimization, validation.-- [NVIDIA free models](#sec-347) — the free generation backend.-- [MCP tools](#sec-316) — every generation/editing tool and its price.+- [NVIDIA free models](#sec-359) — the free generation backend.+- [MCP tools](#sec-327) — every generation/editing tool and its price.----<a id="sec-123"></a>+<a id="sec-126"></a>> **Source:** `docs/avatar-reconstruction.md` · [↑ table of contents](#table-of-contents)@@ -36605,7 +38876,7 @@ pose operations.This is the subsystem that turns a **user's photo** (or a text→image reference)into a rigged, animation-ready 3D avatar. It is distinct from the Forge-generation lane in the [Avatar Pipeline](#sec-122): the Forge generates+generation lane in the [Avatar Pipeline](#sec-125): 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@@ -36716,7 +38987,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-120)+instability keeps rising. See [avatar-fidelity-program.md](#sec-123)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@@ -36810,7 +39081,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-120).+> allocation — is [avatar-fidelity-program.md](#sec-123).> Fidelity claims are scored with the ISE metric in> [`workers/avatar-reconstruction/eval/`](../workers/avatar-reconstruction/eval/README.md).@@ -36859,7 +39130,7 @@ Full runbook: [`docs/ops/gcp-production.md`](ops/gcp-production.md).----<a id="sec-124"></a>+<a id="sec-127"></a>> **Source:** `docs/avatar-studio.md` · [↑ table of contents](#table-of-contents)@@ -36946,15 +39217,15 @@ curl 'https://three.ws/api/avatars/<avatarId>' -H 'cookie: <session>'## Related- [Animation Studio](#sec-096): pose and keyframe the avatar you build here.-- [Scene Composer](#sec-167): forge props and attach them to the avatar's bones as a saved outfit.-- [Mocap Studio](#sec-331): drive the avatar's face live from your webcam.-- [Restyle Studio](#sec-422): shares the same GLB optimize-and-validate path.-- [Trait-based avatar builder](#sec-149): the separate VRM studio embedded in the agent editor; a deep dive into its internals.+- [Scene Composer](#sec-171): forge props and attach them to the avatar's bones as a saved outfit.+- [Mocap Studio](#sec-342): drive the avatar's face live from your webcam.+- [Restyle Studio](#sec-437): shares the same GLB optimize-and-validate path.+- [Trait-based avatar builder](#sec-153): 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-125"></a>+<a id="sec-128"></a>> **Source:** `docs/avatar-thumbnails.md` · [↑ table of contents](#table-of-contents)@@ -37236,7 +39507,7 @@ that adoption HEAD-checks the preview object before persisting it.----<a id="sec-126"></a>+<a id="sec-129"></a>> **Source:** `docs/avatar-wardrobe.md` · [↑ table of contents](#table-of-contents)@@ -37413,13 +39684,13 @@ bricking the avatar.## Related-- [`docs/avatar-reconstruction.md`](#sec-123) — selfie → avatar-- [`docs/avatar-fidelity-program.md`](#sec-120) — identity fidelity program+- [`docs/avatar-reconstruction.md`](#sec-126) — selfie → avatar+- [`docs/avatar-fidelity-program.md`](#sec-123) — identity fidelity program- [`specs/GARMENT_MANIFEST.md`](../specs/GARMENT_MANIFEST.md) — the wearable contract----<a id="sec-127"></a>+<a id="sec-130"></a>> **Source:** `docs/aws-builder-center-agent-commerce-spine.md` · [↑ table of contents](#table-of-contents)@@ -37712,7 +39983,7 @@ Questions are welcome. The parts I would most like other builders to argue with----<a id="sec-128"></a>+<a id="sec-131"></a>> **Source:** `docs/aws-builder-center-agent-payment-sessions.md` · [↑ table of contents](#table-of-contents)@@ -38197,7 +40468,7 @@ An autonomous agent with a private key is a liability you cannot bound. An auton----<a id="sec-129"></a>+<a id="sec-132"></a>> **Source:** `docs/aws-builder-center-marketplace-x402.md` · [↑ table of contents](#table-of-contents)@@ -38216,7 +40487,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-133).+> **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-136).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.@@ -38463,7 +40734,7 @@ The product on the other side of all this plumbing is the platform: three.ws age----<a id="sec-130"></a>+<a id="sec-133"></a>> **Source:** `docs/aws-builder-center-mcp-agents.md` · [↑ table of contents](#table-of-contents)@@ -38579,7 +40850,7 @@ If you wire it into something, or you want to list a paid tool of your own, the----<a id="sec-131"></a>+<a id="sec-134"></a>> **Source:** `docs/aws-builder-center.md` · [↑ table of contents](#table-of-contents)@@ -38591,7 +40862,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-133), [AWS partner spotlight](#sec-134)+- **Related surfaces:** [three.ws/aws](https://three.ws/aws) (AWS Partner page), [AWS Marketplace listing](#sec-136), [AWS partner spotlight](#sec-137)## Published articles@@ -38601,11 +40872,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-114) 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-117) paywall, so one authorization path bills two economies.-- **Source draft in this repo:** [aws-builder-center-marketplace-x402.md](#sec-129)+- **Source draft in this repo:** [aws-builder-center-marketplace-x402.md](#sec-132)- **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-133) 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-136) 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@@ -38616,7 +40887,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-578), [agent wallets](#sec-074), [the agent system](#sec-065), [AWS Marketplace procurement](#sec-133)+- **Surfaces it covers:** [the `<agent-3d>` web component](#sec-599), [agent wallets](#sec-074), [the agent system](#sec-065), [AWS Marketplace procurement](#sec-136)## Published by AWS about three.ws@@ -38630,7 +40901,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-318), [x402](#sec-114), [agent wallets](#sec-074), [the `<agent-3d>` web component](#sec-578)+- **Surfaces it covers:** [the MCP servers](#sec-329), [x402](#sec-117), [agent wallets](#sec-074), [the `<agent-3d>` web component](#sec-599)- **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@@ -38639,10 +40910,10 @@ Written and reviewed in this repo, not yet submitted:| Draft | Subject ||---|---|-| [aws-builder-center-agent-payment-sessions.md](#sec-128) | 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-130) | An MCP server whose paid tools settle per call in USDC over HTTP 402 |-| [mobile-launch/aws-builder-center-article.md](#sec-326) | 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-127) | 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-agent-payment-sessions.md](#sec-131) | 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-133) | An MCP server whose paid tools settle per call in USDC over HTTP 402 |+| [mobile-launch/aws-builder-center-article.md](#sec-337) | 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-130) | 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 |## Publishing checklist@@ -38662,7 +40933,7 @@ The Builder Center is where AWS customers evaluating a partner product go lookin----<a id="sec-132"></a>+<a id="sec-135"></a>> **Source:** `docs/aws-marketplace-listing-kit.md` · [↑ table of contents](#table-of-contents)@@ -38671,7 +40942,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-133). This doc covers the+deployed — see [aws-marketplace.md](#sec-136). This doc covers thelisting itself, which has not yet been created (the AMMP "AI agents & toolsproducts" page shows "No products to display").@@ -38698,7 +40969,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-133)+> is unset, which is the correct state for a free listing. [aws-marketplace.md](#sec-136)> documents them as optional rather than as the billing model.---@@ -39047,7 +41318,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-133) state that the variable takes the AWS-issued+[aws-marketplace.md](#sec-136) 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.**@@ -39098,7 +41369,7 @@ Still verify against the product overview page at creation time----<a id="sec-133"></a>+<a id="sec-136"></a>> **Source:** `docs/aws-marketplace.md` · [↑ table of contents](#table-of-contents)@@ -39106,7 +41377,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-132). 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-135). Until then, use x402 directly: no AWS subscription is required to call `/api/x402/*`.## Subscribing via AWS Marketplace@@ -39201,7 +41472,7 @@ For platform support, open an issue at [github.com/nirholas/three.ws/issues](htt----<a id="sec-134"></a>+<a id="sec-137"></a>> **Source:** `docs/aws-partner-spotlight.md` · [↑ table of contents](#table-of-contents)@@ -39292,12 +41563,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-133)-- How agents reach and pay for tools: [three.ws/docs/x402](#sec-624), [three.ws/docs/mcp](#sec-318)+- AWS Marketplace and procurement: [three.ws/docs/aws-marketplace](#sec-136)+- How agents reach and pay for tools: [three.ws/docs/x402](#sec-645), [three.ws/docs/mcp](#sec-329)----<a id="sec-135"></a>+<a id="sec-138"></a>> **Source:** `docs/big-tech-recognition-week.md` · [↑ table of contents](#table-of-contents)@@ -39308,9 +41579,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-351),-[partners.md](#sec-368), [listings.md](#sec-305),-[aws-marketplace.md](#sec-133), [ibm.md](#sec-287)). This one is the+is one vendor deep ([nvidia-visibility-map.md](#sec-363),+[partners.md](#sec-381), [listings.md](#sec-316),+[aws-marketplace.md](#sec-136), [ibm.md](#sec-297)). 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?**@@ -39408,11 +41679,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-131) already carries the checklist for+[aws-builder-center.md](#sec-134) already carries the checklist forpublishing the next one.**The caveat.** The obvious candidate for article 2 is-[aws-partner-spotlight.md](#sec-134), which is written and+[aws-partner-spotlight.md](#sec-137), 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,@@ -39430,7 +41701,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-368) lists eight partners and+Worth naming plainly: **[partners.md](#sec-381) 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@@ -39455,7 +41726,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-344) is already+existing [Apps Catalog request](#sec-355) 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.@@ -39472,7 +41743,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-343).+specified in step 1 of [nvidia-apps-catalog-listing.md](#sec-354).Nothing in this email lands well while the record misdescribes the product.---@@ -39539,7 +41810,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-190). Both routes returned 200 on 2026-08-17. You+[demo-routes.md](#sec-194). 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.@@ -39626,16 +41897,296 @@ Publishing, posting, and sending are owner-gated under stop-and-ask gate 2 in## Related-- [NVIDIA visibility map](#sec-351): every NVIDIA surface in depth, and the dead ends-- [Partners](#sec-368): the eight programs, and the independence language that must survive any rewrite-- [Listings and distribution](#sec-305): the canonical program and directory inventory+- [NVIDIA visibility map](#sec-363): every NVIDIA surface in depth, and the dead ends+- [Partners](#sec-381): the eight programs, and the independence language that must survive any rewrite+- [Listings and distribution](#sec-316): the canonical program and directory inventory- [Announcement coverage](#sec-100): which surfaces have been announced on X and which have not-- [Press kit](#sec-385): marks, boilerplate, and the rules governing co-branded graphics+- [Press kit](#sec-399): 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-136"></a>+<a id="sec-139"></a>++> **Source:** `docs/blender-mcp.md` · [↑ table of contents](#table-of-contents)++# Blender MCP++`@three-ws/blender-mcp` hands an AI assistant the Blender installed on your own machine. It speaks the [Model Context Protocol](https://modelcontextprotocol.io) over stdio, and it drives Blender in background mode: no GUI session has to be open, no add-on has to be installed into Blender first, and nothing stays resident between calls.++That makes it the piece that sits under the three.ws pipeline rather than beside it. Forge generates a model; this reads it, converts it, previews it, and edits it, using the most complete format bridge that exists offline.++---++## What it is for++| You want to | Tool |+|---|---|+| Know what is actually inside a file a client sent you | `blender_scene_info` |+| Turn an FBX or a USD into a web-ready GLB (or the reverse) | `blender_convert` |+| See a model without opening anything | `blender_render` |+| Make a model small enough to ship, and see what it cost | `blender_optimize` |+| Do something no single tool covers: join, rename bones, bake | `blender_run_python` |+| Generate an asset from a sentence and open it | `blender_forge_import` |+| Find out why one of the above failed | `blender_info` |++---++## Requirements++- **Node.js 20+**+- **Blender 3.0 or newer**, installed locally: [blender.org/download](https://www.blender.org/download/), or your package manager.++If Blender is not on `PATH`, set `BLENDER_PATH` to the executable. On macOS that is `/Applications/Blender.app/Contents/MacOS/Blender`.++Some Linux distribution packages ship Blender without the Python modules its glTF add-on needs. `blender_info` tells you what the local build can really do, which turns that class of problem into one clear answer instead of a confusing failure inside an unrelated call.++---++## Install++### Claude Code++```bash+claude mcp add blender -- npx -y @three-ws/blender-mcp+```++In this repository the server is already declared in [`.mcp.json`](../.mcp.json) and runs straight from the working tree:++```json+{+ "mcpServers": {+ "blender": {+ "command": "node",+ "args": ["packages/blender-mcp/src/index.js"]+ }+ }+}+```++### Claude Desktop / Cursor++```json+{+ "mcpServers": {+ "blender": {+ "command": "npx",+ "args": ["-y", "@three-ws/blender-mcp"],+ "env": { "BLENDER_PATH": "/Applications/Blender.app/Contents/MacOS/Blender" }+ }+ }+}+```++---++## Tools++### `blender_info`++No arguments. Reports the executable path, Blender version, bundled Python version, the render engines that are genuinely usable on this build, and the import/export extensions it supports. Read-only.++Call it first whenever anything else fails: it separates "Blender is missing" from "this build cannot do that" from "the file is wrong".++### `blender_scene_info`++| Argument | Type | Notes |+|---|---|---|+| `input` | string, required | Path to the file. Absolute, or relative to the server's working directory. |+| `include_objects` | boolean | Include the per-object breakdown. Set `false` on huge scenes for totals only. Default `true`. |++Opens a `.blend`, or imports any supported format into an empty scene, and describes it: objects with type, parent, dimensions, modifiers, materials and UV layers; **evaluated** triangle and vertex counts, so a subdivision modifier is counted as what it renders, not what it stores; a texture inventory giving each image's resolution, format and byte size plus `counts.texture_bytes`, which against `input_bytes` is what tells you whether an asset is mesh-heavy or texture-heavy; armature bone names; animation actions with frame ranges; and world-space bounds. The file is never modified.++Counts describe the file **as loaded**. A GLB reports more vertices than the `.blend` it was exported from, because glTF splits vertices at UV and normal seams; the triangle count is identical either way.++```+blender_scene_info { "input": "~/assets/character.fbx" }+```++### `blender_convert`++| Argument | Type | Notes |+|---|---|---|+| `input` | string, required | Source file. |+| `output` | string | Destination. Its extension picks the format. Defaults to a `.glb` in the workdir. |+| `apply_modifiers` | boolean | Bake modifiers into the exported geometry. Default `true`. |+| `scale` | number | Uniform scale baked into the export, e.g. `0.01` for centimetres to metres. |++Both sides accept `.glb`, `.gltf`, `.fbx`, `.obj`, `.stl`, `.ply`, `.dae`, `.abc`, `.usd`, `.usda`, `.usdc`, `.usdz`, `.x3d`, and `.blend`, as far as the local build supports them: several Linux distribution packages ship Blender without USD, Collada, or Alembic. `blender_info` lists what yours really has, and asking for one it lacks fails immediately with `format_unsupported` rather than part way through an export.++```+blender_convert { "input": "character.fbx", "output": "character.glb", "scale": 0.01 }+```++### `blender_optimize`++| Argument | Type | Notes |+|---|---|---|+| `input` | string, required | Model to optimize. |+| `output` | string | Destination. The extension picks the format. Defaults to a `.glb` in the workdir. |+| `max_triangles` | integer | Triangle budget for the whole scene. Omit to leave geometry alone. |+| `max_texture_px` | integer | Longest edge any texture may keep. Omit to leave textures alone. |+| `compress` | enum | `meshopt` (default), `draco`, or `none`. Applies to glTF output only. |++The delivery pass, in one call. Decimation is collapse-based and applies **one ratio across the whole scene**, so meshes keep their relative density: a per-object budget is what flattens a face while leaving a wall at full resolution. Textures are scaled and repacked, unreferenced datablocks are dropped, and the mesh streams are compressed on the way out.++Compression runs outside Blender because Blender's exporter offers Draco only, and only on builds shipping the library, while meshopt is what the three.ws runtime and every major web viewer decode.++```+blender_optimize { "input": "character.glb", "output": "character-web.glb", "max_triangles": 30000, "max_texture_px": 1024 }+```++The response carries `before` and `after` counts, `saved_bytes`, `saved_percent`, and a `steps` array saying what each stage did, so the trade is visible instead of guessed. Vertex groups survive decimation, but check a heavily decimated skinned mesh with `blender_render` before shipping it.++### `blender_render`++| Argument | Type | Notes |+|---|---|---|+| `input` | string, required | File to render. |+| `output` | string | Destination PNG. Defaults into the workdir. |+| `engine` | enum | `auto` (default), `CYCLES`, `BLENDER_EEVEE`, `BLENDER_WORKBENCH`. |+| `samples` | integer | Default `32`, enough for a preview. |+| `resolution` | `[width, height]` | Default `[960, 960]`. |+| `transparent` | boolean | Transparent background instead of the world. Default `false`. |+| `views` | integer | How many angles to render, orbiting the model, 1 to 6. Default 1. |+| `inline_image` | boolean | Return the image inline so the assistant can see it. Default `true`. |++Asking for several `views` orbits the model and renders every angle in the **same** Blender launch, one import for the whole set, and returns them all inline. Four views is what answers questions a single angle hides: whether the back is modelled at all, whether a texture only reads from the front. A multi-view set always orbits its own camera, so an authored camera is honoured only when `views` is 1.++The rendered image comes back **inline** as an MCP image block, downscaled to fit the caller's context, while the full-resolution PNG is written to disk. That is what makes a see-and-fix loop possible in one call, and it is the only way the render is reachable at all from a client with no filesystem access.++An asset file usually carries no camera and no lights, which is why rendering one straight out of a converter normally produces a black square. This tool fills both in: it creates a camera and frames it to the geometry's bounding sphere, and adds a key light and a lit world. A scene that already has its own camera and lighting is rendered exactly as authored, and the response says which of the two happened (`camera_created`, `lights_created`).++`auto` picks Cycles, which renders on CPU and therefore works in a container. EEVEE is far faster but needs a real GPU context.++### `blender_run_python`++| Argument | Type | Notes |+|---|---|---|+| `code` | string, required | Python to execute. `bpy`, `math` and `Vector` are already imported. |+| `input` | string | File to open first. Omit to start from an empty scene. |+| `output` | string | Export the result here afterwards; the extension picks the format. |+| `apply_modifiers` | boolean | Apply modifiers on that export. Default `true`. |++Anything printed comes back as `stdout`. Assigning a JSON-serializable value to a variable named `result` returns it as structured data alongside the post-run scene counts.++```+blender_run_python {+ "input": "character.glb",+ "output": "character-lod1.glb",+ "code": "import bpy\nfor obj in bpy.data.objects:\n if obj.type == 'MESH':\n obj.modifiers.new('Decimate', 'DECIMATE').ratio = 0.5\nresult = {'meshes': len([o for o in bpy.data.objects if o.type == 'MESH'])}"+}+```++This tool runs caller-supplied code with the server's own permissions. See [Security](#security).++### `blender_forge_import`++| Argument | Type | Notes |+|---|---|---|+| `prompt` | string | One subject, e.g. `a weathered brass diving helmet`. Required unless an image is given; with an image it steers the reconstruction. |+| `image` | string | Local PNG, JPEG or WebP to reconstruct from. Uploaded straight to storage on a presigned PUT, so the bytes never pass through the API. |+| `image_url` | string | A public https image to reconstruct from, instead of uploading one. |+| `output` | string | Destination. `.glb` keeps the generated bytes untouched; any other extension converts on the way in. |+| `tier` | enum | `draft`, `standard` (default), `high`. |+| `lane` | enum | `image` (default, free), `geometry` (Meshy/Tripo, needs a key), `sketch`. |+| `backend` | string | Pin a backend. Omit to let the deployment choose for the tier. |+| `aspect_ratio` | enum | Reference image ratio. Default `1:1`. |++Runs the public [`/api/forge`](#sec-001) pipeline: the default image lane (FLUX to TRELLIS) is free and needs no key, wallet, or account. When the output asks for a non-GLB format, the untouched GLB is kept beside it as `<name>.source.glb`, because conversion is lossy for some targets and the original is what the rest of the three.ws pipeline consumes.++Generation runs on a shared GPU lane and typically takes tens of seconds to a couple of minutes. A reference image reconstructs in about the same time as a prompt.++If an upload fails, the deployment's object storage is the problem, not your file: `image_url` reaches the same lane without touching the upload path.++```+blender_forge_import { "prompt": "a weathered brass diving helmet", "output": "helmet.blend" }+```++---++## Compressed glTF is decoded for you++Blender's glTF importer has no decoder for `EXT_meshopt_compression`. That matters more than it sounds: meshopt is what `gltfpack` emits and what most three.ws avatars ship as, so the platform's own primary delivery format fails in raw Blender with *"Extension EXT_meshopt_compression is not available on this addon version"*. Draco is nominally supported, but only on builds that ship `libextern_draco`, which several Linux distribution packages omit.++Every tool that takes an `input` therefore decodes first, in process, using the same glTF libraries the rest of the repo depends on ([`@gltf-transform/core`](https://gltf-transform.dev), `meshoptimizer`, `draco3dgltf`). There is no external binary to install, unlike the `gltfpack` path the GPU workers use ([`workers/rig/gltf_meshopt.py`](https://github.com/nirholas/three.ws/blob/main/workers/rig/gltf_meshopt.py)), because an npm package cannot assume one is present.++The response names what was decoded:++```json+{ "decoded_compression": ["EXT_meshopt_compression"], "counts": { "triangles": 15744 } }+```++An uncompressed file is passed through untouched and the field is absent. Your file is never modified: the decoded copy lives in the job's scratch directory and dies with it.++---++## How a call works++Every tool call spawns one process:++```+blender -b --factory-startup -noaudio --python src/py/runner.py -- <job.json> <result.json>+```++Three design decisions are worth knowing, because they are what makes the tools predictable:++1. **`--factory-startup`** keeps your saved preferences and third-party add-ons out of the result, so the same conversion produces the same file on any machine.+2. **The runner writes its payload to a file, never to stdout.** Blender prints progress, add-on chatter and render statistics on stdout; picking a payload out of that stream is guesswork. A missing result file is therefore an unambiguous "Blender died", and the error carries the log tail that says why.+3. **One process per call.** A crashed job cannot corrupt the next one, and no state leaks between calls.++Every operator is resolved by name with fallbacks and every keyword is filtered against the operator's own RNA before the call, so the importer and exporter renames between Blender 3.x and 4.x do not break a tool.++## Errors++Failures come back as structured tool errors, each naming a fix:++| Code | Meaning |+|---|---|+| `blender_not_found` | No Blender on `PATH` or at the standard locations. Install it, or set `BLENDER_PATH`. |+| `blender_too_old` | Found a Blender older than 3.0. |+| `input_not_found` | The path does not exist or is unreadable. |+| `format_unsupported` | This build has no importer or exporter for that extension. The message lists the ones it does have. |+| `engine_unavailable` | The requested render engine is not in this build. |+| `timeout` | The job passed `BLENDER_MCP_TIMEOUT_MS` and was killed. |+| `blender_unusable` | A Blender executable exists but would not run. Carries per-candidate diagnostics; on a loaded machine this is usually transient and the call is worth retrying. |+| `blender_crashed` | Blender exited without writing a result. The error carries its log tail. |++---++## Environment variables++| Variable | Default | Purpose |+|---|---|---|+| `BLENDER_PATH` | discovered | Absolute path to the Blender executable. |+| `BLENDER_MCP_TIMEOUT_MS` | `300000` | Ceiling for one Blender job. |+| `BLENDER_MCP_WORKDIR` | `<tmpdir>/three-ws-blender-mcp` | Where outputs land with no explicit output path. |+| `BLENDER_MCP_ALLOW_PYTHON` | `1` | `0` withdraws `blender_run_python` from the tool list entirely. |+| `BLENDER_MCP_MAX_CONCURRENCY` | `2` | Blender processes allowed at once; further calls queue. |+| `BLENDER_MCP_INLINE_IMAGE_PX` | `768` | Longest edge of the render copy returned inline. |+| `BLENDER_MCP_INLINE_IMAGE_BYTES` | `1500000` | Past this the image stays on disk and the response says so. |+| `THREE_WS_BASE` | `https://three.ws` | Deployment backing `blender_forge_import`. |+| `THREE_WS_FORGE_TIMEOUT_MS` | `600000` | Ceiling for one generation. |+| `THREE_WS_FORGE_PROVIDER_KEY` | unset | Meshy/Tripo key for the bring-your-own-key geometry lane. |++## Security++`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 five 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-325).++---++## 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-329) 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-140"></a>> **Source:** `docs/bnb-babt-findings.md` · [↑ table of contents](#table-of-contents)@@ -39831,7 +42382,7 @@ shipped:----<a id="sec-137"></a>+<a id="sec-141"></a>> **Source:** `docs/bnb-payments.md` · [↑ table of contents](#table-of-contents)@@ -40004,7 +42555,7 @@ full verified-facts list.----<a id="sec-138"></a>+<a id="sec-142"></a>> **Source:** `docs/bnb-vault.md` · [↑ table of contents](#table-of-contents)@@ -40177,7 +42728,7 @@ this campaign, not a bug in this code path.----<a id="sec-139"></a>+<a id="sec-143"></a>> **Source:** `docs/bnb-world.md` · [↑ table of contents](#table-of-contents)@@ -40413,7 +42964,7 @@ reproduction commands are recorded in `contracts/DEPLOYMENTS.md`'s "Prompt## Related-- [BNB Chain payments](#sec-137) — the MPP/x402 payment rail this+- [BNB Chain payments](#sec-141) — 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@@ -40424,7 +42975,7 @@ reproduction commands are recorded in `contracts/DEPLOYMENTS.md`'s "Prompt----<a id="sec-140"></a>+<a id="sec-144"></a>> **Source:** `docs/brain.md` · [↑ table of contents](#table-of-contents)@@ -40511,7 +43062,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-112)):+session or bearer token, see [Authentication](#sec-115)):```bashcurl -N -s -X POST https://three.ws/api/brain/chat \@@ -40556,13 +43107,13 @@ done; wait- [Agent Studio](#sec-063): the Brain tab uses this same backend- [Agent System](#sec-065): how a chosen brain fits the agent model-- [Persona Hub](#sec-373): synthesizing the system prompt a brain runs-- [API reference](#sec-104) and [Authentication](#sec-112)+- [Persona Hub](#sec-386): synthesizing the system prompt a brain runs+- [API reference](#sec-105) and [Authentication](#sec-115)- Pages: [/brain](https://three.ws/brain), [/agent-studio](https://three.ws/agent-studio)----<a id="sec-141"></a>+<a id="sec-145"></a>> **Source:** `docs/brownout.md` · [↑ table of contents](#table-of-contents)@@ -40755,11 +43306,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-437), the retry, ladder and last-good helpers this instruments+- [docs/shared-utilities.md](#sec-454), the retry, ladder and last-good helpers this instruments----<a id="sec-142"></a>+<a id="sec-146"></a>> **Source:** `docs/btn-pill-migration.md` · [↑ table of contents](#table-of-contents)@@ -40884,7 +43435,7 @@ These classes are defined across the codebase. Follow-up agents should replace t----<a id="sec-143"></a>+<a id="sec-147"></a>> **Source:** `docs/build.md` · [↑ table of contents](#table-of-contents)@@ -40935,7 +43486,7 @@ front-end, the `vercel.json` route table, and every `api/**` handler from sourceprovisioned from the `crons` array in `vercel.json` by[scripts/create-gcp-scheduler.mjs](../scripts/create-gcp-scheduler.mjs); thatarray is the count, so read it there rather than trusting a number quoted here-(114 entries on 2026-09-03). There is **no GitHub Actions CI**. Full runbook: [docs/ops/gcp-production.md](ops/gcp-production.md).+(117 entries on 2026-09-08). There is **no GitHub Actions CI**. Full runbook: [docs/ops/gcp-production.md](ops/gcp-production.md).`.npmrc` sets `legacy-peer-deps=true` (npm never auto-installs peers — thereason `audit:deploy` checks the peer tree), and `engines.node` pins Node@@ -41051,13 +43602,13 @@ grep -l 'vite-plugin-pwa:register-sw' dist/widget.html dist/embed.html # expec----<a id="sec-144"></a>+<a id="sec-148"></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-624)+Paste a token contract address, get back a live, agent-payable [x402](#sec-645)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.@@ -41218,7 +43769,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-619) for the full+back to the default. See [x402 paid endpoints](#sec-640) for the fullprice-override scheme.---@@ -41234,7 +43785,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-240)).+[Financial controls](#sec-246)).The paid response body is the token block computed fresh at call time:@@ -41377,16 +43928,16 @@ right now. If the endpoint is unreachable the page says so and offers a retry.## Related-- [x402 on three.ws](#sec-624): the protocol, the wire format, and how the+- [x402 on three.ws](#sec-645): the protocol, the wire format, and how theplatform settles.-- [x402 paid endpoints](#sec-619): the full catalog of our paid+- [x402 paid endpoints](#sec-640): 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-145"></a>+<a id="sec-149"></a>> **Source:** `docs/capture.md` · [↑ table of contents](#table-of-contents)@@ -41483,14 +44034,14 @@ console.log(job.result_url, job.num_points); // coloured .ply + point count## Related-- [Splat Viewer](#sec-458) renders Gaussian-splat radiance fields, the photoreal cousin of point clouds.+- [Splat Viewer](#sec-476) 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-245) and [Image to 3D](#sec-288) for generating meshes from prompts and photos.+- [Forge](#sec-251) and [Image to 3D](#sec-298) for generating meshes from prompts and photos.- Pages: [/scene](https://three.ws/scene) (Scene Studio), [/create](https://three.ws/create).----<a id="sec-146"></a>+<a id="sec-150"></a>> **Source:** `docs/carplay.md` · [↑ table of contents](#table-of-contents)@@ -41518,7 +44069,7 @@ units where nothing is gated at all.## 1. Why this is a better fit than it looks-The [smart home plan](#sec-449) argued that a home is the first place where a body, a+The [smart home plan](#sec-467) 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.**@@ -41583,7 +44134,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-449)), with a safety gate that freezes anything+into `/api/chat` ([smart-home.md](#sec-467)), 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.@@ -41773,7 +44324,7 @@ the fix goes upstream.----<a id="sec-147"></a>+<a id="sec-151"></a>> **Source:** `docs/changelog.md` · [↑ table of contents](#table-of-contents)@@ -41783,6 +44334,36 @@ This document covers how three.ws is versioned, what has changed across releases> **Looking for what shipped this week?** Day-to-day product updates are published continuously on the live changelog at [three.ws/changelog](https://three.ws/changelog) (also available as [JSON](https://three.ws/changelog.json) and [RSS](https://three.ws/changelog.xml)). The versioned entries below track the platform/SDK release history rather than every product change.+### The two JSON feeds++`/changelog.json` is the complete history and is the documented public feed: every+entry since the site existed, newest first, and it keeps that contract. It also+grows forever, and on 2026-09-08 it was 3,552 entries and 870 KB over the wire.++`/changelog-recent.json` is the newest 150 of the same entries in the same+envelope, plus two fields that say so:++```json+{+ "generated_at": "2026-09-08T17:18:00.000Z",+ "site": { "name": "three.ws", "url": "https://three.ws" },+ "total": 3552,+ "complete": false,+ "full_feed": "/changelog.json",+ "entries": [ { "date": "2026-09-08", "type": "update", "title": "…", "summary": "…", "link": "/…", "tags": ["improvement"] } ]+}+```++`total` is how many entries exist; `complete` says whether this file is all of+them. Read this one when you want what shipped lately (a "what's new" strip, a+notification, a single entry someone linked to) and fall back to+`/changelog.json` when `complete` is `false` and you need older history. Both are+generated by `npm run build:pages` from `data/pages.json` + `data/changelog.json`,+and both are served with `cache-control: public, max-age=600`.++`three.ws/changelog` itself paints from the small feed and fetches the full one+only when a reader filters or asks for older updates.+---## Versioning Policy@@ -42109,7 +44690,7 @@ cd sdk && npm publish----<a id="sec-148"></a>+<a id="sec-152"></a>> **Source:** `docs/character-library.md` · [↑ table of contents](#table-of-contents)@@ -42120,7 +44701,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-097). For the free prop counterpart to this library, see the [Object Library](#sec-352).+> This page covers the character gallery and its API. For the motion clips these characters play, see [Animations](#sec-097). For the free prop counterpart to this library, see the [Object Library](#sec-364).---@@ -42136,8 +44717,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-575) |-| **Use** | `/studio?model=<glb-url>` | [Widget Studio](#sec-580): configure and publish an embeddable widget of this character (see the [Embedding Guide](#sec-204)) |+| **Preview** | `/app#model=<glb-url>` | The full three.js [3D viewer](#sec-595) |+| **Use** | `/studio?model=<glb-url>` | [Widget Studio](#sec-601): configure and publish an embeddable widget of this character (see the [Embedding Guide](#sec-209)) || **Animate** | `/pose?src=<glb-url>&title=<name>` | [Animation Studio](#sec-096): pose, keyframe, and export motion on this character |Gallery controls:@@ -42149,7 +44730,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-352). 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-364). 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@@ -42224,19 +44805,19 @@ The gallery and API are read-only consumers of a manifest built by a local pipel3. `scripts/fetch-mixamo-avatar-thumbnails.mjs` stages the PNG thumbnails.4. `scripts/build-mixamo-avatar-library.mjs` reads `public/avatars/mixamo/catalog.json`, merges the extra CC0 characters from `public/avatars/extra/characters.json`, and PUTs `avatars/library/manifest.json` to R2 (`--dry-run` prints without uploading).-R2 CORS is configured by `scripts/set-r2-cors.mjs` so browsers can GET the GLBs cross-origin. The live bucket policy is an origin allowlist (`three.ws`, `*.vercel.app`, `localhost:3000`) that predates the world-open read rule now in that script, so a GLB loaded straight from the bucket host on any other origin fails with no `access-control-allow-origin` header (re-measured 2026-09-04). Measure the live policy yourself with `node scripts/set-r2-cors.mjs --probe`, which needs no credentials. Until the bucket is corrected, embeds on third-party origins should load the GLB from a first-party path instead: [`/cdn/<key>`](media-api.md#how-bucket-objects-are-served-cdnkey) when you have the object key, or [`/api/glb`](media-api.md#same-origin-glb-proxy) when all you have is the manifest URL, as [the embed tutorial](#sec-495) does.+R2 CORS is configured by `scripts/set-r2-cors.mjs` so browsers can GET the GLBs cross-origin. The live bucket policy is an origin allowlist (`three.ws`, `*.vercel.app`, `localhost:3000`) that predates the world-open read rule now in that script, so a GLB loaded straight from the bucket host on any other origin fails with no `access-control-allow-origin` header (re-measured 2026-09-09). Measure the live policy yourself with `node scripts/set-r2-cors.mjs --probe`, which needs no credentials. Until the bucket is corrected, embeds on third-party origins should load the GLB from a first-party path instead: [`/cdn/<key>`](media-api.md#how-bucket-objects-are-served-cdnkey) when you have the object key, or [`/api/glb`](media-api.md#same-origin-glb-proxy) when all you have is the manifest URL, as [the embed tutorial](#sec-515) does.## Related- [Animations](#sec-097): the clip library every character drives, and how retargeting works.- [Animation Studio](#sec-096): the `/pose` surface the Animate button opens.-- [Widget Studio](#sec-580) and the [Embedding Guide](#sec-204): turn a library character into a live embed on any site.-- [Object Library](#sec-352): the same free-library pattern for CC0 props and scene objects.-- [Marketplace](#sec-310): library characters are free; the marketplace is where priced avatars, agents, and skills are bought and sold.+- [Widget Studio](#sec-601) and the [Embedding Guide](#sec-209): turn a library character into a live embed on any site.+- [Object Library](#sec-364): the same free-library pattern for CC0 props and scene objects.+- [Marketplace](#sec-321): library characters are free; the marketplace is where priced avatars, agents, and skills are bought and sold.----<a id="sec-149"></a>+<a id="sec-153"></a>> **Source:** `docs/character-studio.md` · [↑ table of contents](#table-of-contents)@@ -42514,13 +45095,13 @@ For cases that need more control than the studio provides, create your avatar in----<a id="sec-150"></a>+<a id="sec-154"></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-151). 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-155). 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@@ -42683,7 +45264,7 @@ Run the four suggested prompts in a fresh chat. Pass criteria:----<a id="sec-151"></a>+<a id="sec-155"></a>> **Source:** `docs/chatgpt-ar.md` · [↑ table of contents](#table-of-contents)@@ -42720,13 +45301,13 @@ The same free lane ships into ChatGPT twice, because ChatGPT has two integration### 1. The ChatGPT app (Apps SDK / MCP connector)-The MCP connector at `https://three.ws/api/mcp-studio` (no authentication) exposes eleven 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 now 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, 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)). Full server documentation: [3D Studio MCP](#sec-315).+The MCP connector at `https://three.ws/api/mcp-studio` (no authentication) exposes eleven 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 now 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, 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)). Full server documentation: [3D Studio MCP](#sec-326).Every successful tool result carries `arUrl` in its `structuredContent`, and the inline 3D widget renders it as a **View in your space** button next to the rotatable model. When the result is a rigged avatar the response additionally carries `irlUrl` and the button becomes **Bring it to life**. Refined versions (`refine_model`) each carry their own `arUrl`, so any point in the version lineage can be placed in the room.### 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-150); 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-154); the REST contract it calls:```bashcurl -s -X POST https://three.ws/api/3d/studio \@@ -42775,7 +45356,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-107).+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-108).---@@ -42783,7 +45364,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-294).+- `/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-304).- 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.@@ -42806,10 +45387,10 @@ 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 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-456) 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-312), 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 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-474) 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-323), 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 (NVIDIA NIM running Microsoft TRELLIS for text-to-3D), so the end user pays nothing and needs no account; real per-IP rate limits apply and are documented per endpoint.+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 worker, the free NVIDIA NIM text→3D lane, the Hugging Face Spaces image→3D lane) 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)).---@@ -42834,14 +45415,14 @@ The generation lane is operator-funded (NVIDIA NIM running Microsoft TRELLIS for- [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-315): the free MCP server behind the ChatGPT app+- [3D Studio MCP](#sec-326): 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-107): Quick Look, Scene Viewer, WebXR, and the USDZ pipeline in depth-- [IRL](#sec-294): the living-agent experience behind Bring it to life+- [AR and WebXR reference](#sec-108): Quick Look, Scene Viewer, WebXR, and the USDZ pipeline in depth+- [IRL](#sec-304): the living-agent experience behind Bring it to life----<a id="sec-152"></a>+<a id="sec-156"></a>> **Source:** `docs/checkout-companion.md` · [↑ table of contents](#table-of-contents)@@ -42857,7 +45438,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-166) already delivers messages in person. This is the+The [companion](#sec-170) already delivers messages in person. This is thesame companion at the moment money moves.## What it reports@@ -42959,7 +45540,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-166), rotatable from+(the same token as [`/api/companion/ingest`](#sec-170), rotatable from`/companion`). Rate limit: 40 per 10 minutes per account.Request:@@ -43039,7 +45620,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-293).+fact, not a roadmap item. See [iOS](#sec-303).## Tests@@ -43050,14 +45631,14 @@ fact, not a roadmap item. See [iOS](#sec-293).## Related-- [Companion](#sec-166): the message lanes and the avatar delivery channel-- [Notifications](#sec-342): the per-category channel matrix+- [Companion](#sec-170): the message lanes and the avatar delivery channel+- [Notifications](#sec-353): the per-category channel matrix- [`extensions/walk-avatar/`](../extensions/walk-avatar): the same rig, walkingyour avatar across any site----<a id="sec-153"></a>+<a id="sec-157"></a>> **Source:** `docs/choreography.md` · [↑ table of contents](#table-of-contents)@@ -43172,7 +45753,7 @@ Rules worth knowing before you call it:### From an embed-Any page already rendering an [`<agent-3d>`](#sec-204) element can perform the agent's saved routines by name:+Any page already rendering an [`<agent-3d>`](#sec-209) element can perform the agent's saved routines by name:```html<agent-3d agent="YOUR_AGENT_ID"></agent-3d>@@ -43301,13 +45882,13 @@ Coming from [/gestures](https://three.ws/gestures), the **Use in a routine** but## Related- [Animations](#sec-097): clips, collections, and the slot vocabulary underneath every routine-- [Procedural animation](#sec-386): the IK layers that run on top of whatever clip is playing+- [Procedural animation](#sec-400): the IK layers that run on top of whatever clip is playing- [Agent manifest](#sec-056): the public document that carries `choreographies` to embeds-- [Embedding an agent](#sec-204): the `<agent-3d>` element these methods live on+- [Embedding an agent](#sec-209): the `<agent-3d>` element these methods live on----<a id="sec-154"></a>+<a id="sec-158"></a>> **Source:** `docs/circulation-engine.md` · [↑ table of contents](#table-of-contents)@@ -43469,7 +46050,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-199)) rather than scheduled on its own.+[economy heartbeat](#sec-204)) 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@@ -43502,9 +46083,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-333)). |+| `agent_custody_events` | The canonical wallet ledger entry for every real spend/transfer (see [Money feed](#sec-344)). || `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-310)). |+| `skill_purchases` / `asset_purchases` | Marketplace settlement records (see [Marketplace](#sec-321)). |Real spends are written to `agent_custody_events`, which powers per-agentportfolio balances and the agent-to-agent economy volume dashboard (all-time and@@ -43539,15 +46120,15 @@ budget, so raise gradually and watch tick runtime and treasury balance.## Related-- [Money feed](#sec-333): where circulation activity surfaces.-- [Autonomous x402 loop](#sec-114): the separate treasury-paid loop+- [Money feed](#sec-344): where circulation activity surfaces.+- [Autonomous x402 loop](#sec-117): the separate treasury-paid loopthat buys polling intel from our own x402 endpoints.- [Agent wallets](#sec-074): the custodial key model every action uses.-- [Marketplace](#sec-310), [Coin launches](#sec-157).+- [Marketplace](#sec-321), [Coin launches](#sec-161).----<a id="sec-155"></a>+<a id="sec-159"></a>> **Source:** `docs/clash.md` · [↑ table of contents](#table-of-contents)@@ -43561,7 +46142,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-470) and [hold to access](#sec-262)). 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-490) and [hold to access](#sec-270)). 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@@ -43625,15 +46206,15 @@ The Coin Clash state and leaderboard are also exposed read-only over MCP through## Related-- [Token-gated 3D embeds](#sec-470): the same real on-chain balance gate, applied to embeds-- [Hold to access](#sec-262): the platform's broader hold-do-not-spend membership thesis-- [The social layer](#sec-452): platform-wide feed, follows, and leaderboards-- [MCP tools](#sec-318): the read-only Clash MCP server+- [Token-gated 3D embeds](#sec-490): the same real on-chain balance gate, applied to embeds+- [Hold to access](#sec-270): the platform's broader hold-do-not-spend membership thesis+- [The social layer](#sec-470): platform-wide feed, follows, and leaderboards+- [MCP tools](#sec-329): the read-only Clash MCP server- Pages: [/clash](https://three.ws/clash) · [/communities](https://three.ws/communities)----<a id="sec-156"></a>+<a id="sec-160"></a>> **Source:** `docs/clip-director.md` · [↑ table of contents](#table-of-contents)@@ -43743,7 +46324,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-181)+`GET /api/mirror/leaderboard?settled_min=1`, the [copy-trading](#sec-185)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@@ -43757,14 +46338,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-472)-- [Meta-Allocator: the ETF of degens](#sec-322)-- [The trading surfaces](#sec-479) · [The Arena](https://three.ws/arena)+- [Trader Card & the claim-your-wallet wedge](#sec-492)+- [Meta-Allocator: the ETF of degens](#sec-333)+- [The trading surfaces](#sec-499) · [The Arena](https://three.ws/arena)- [Animations & gestures](#sec-097)----<a id="sec-157"></a>+<a id="sec-161"></a>> **Source:** `docs/coin-launches.md` · [↑ table of contents](#table-of-contents)@@ -43798,12 +46379,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-187)), and the mint is registered in+[Agent wallets](#sec-191)), 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-154) also runs its own+inert. The [circulation engine](#sec-158) also runs its own`launch` action with separate hourly/daily caps.## What a launch carries@@ -43814,7 +46395,7 @@ inert. The [circulation engine](#sec-154) 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-323), [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-334), [Vanity protocol](#sec-006)). |## Recording and surfacing@@ -43823,7 +46404,7 @@ inert. The [circulation engine](#sec-154) 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-333)). |+| Live ticker | `coin-buy` / `agent-deploy` events (see [Money feed](#sec-344)). |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@@ -43835,7 +46416,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-114).+[sniper](#sec-117).## $THREE only@@ -43847,14 +46428,14 @@ hardcode or surface any other specific mint as a recommendation.## Related-- [Solana pump.fun signals](#sec-453) — reputation/intel from pump.fun activity.-- [Agent wallets](#sec-187) — custodial signing and spend caps.-- [Circulation engine](#sec-154) — autonomous launch cadence and caps.-- [Mint mark](#sec-323), [Vanity protocol](#sec-006).+- [Solana pump.fun signals](#sec-471) — reputation/intel from pump.fun activity.+- [Agent wallets](#sec-191) — custodial signing and spend caps.+- [Circulation engine](#sec-158) — autonomous launch cadence and caps.+- [Mint mark](#sec-334), [Vanity protocol](#sec-006).----<a id="sec-158"></a>+<a id="sec-162"></a>> **Source:** `docs/coin-pages.md` · [↑ table of contents](#table-of-contents)@@ -44483,7 +47064,7 @@ server mirrors each (including the dynamic `/coin/:id` path). The pre-existing----<a id="sec-159"></a>+<a id="sec-163"></a>> **Source:** `docs/coin-wars.md` · [↑ table of contents](#table-of-contents)@@ -44676,9 +47257,26 @@ echoes):````/play/war` also works as a direct destination: with a valid `match` + `ticket`-but no `holderPass`, it mints its own from the signed-in session. Without a-pairing at all it says so and offers the way back rather than showing an empty-battlefield. `return` is only ever honoured as a same-origin path.+but no `holderPass`, it mints its own from the signed-in session. `return` is+only ever honoured as a same-origin path.++Without a pairing at all (a hand-typed URL, a link shared after the battle, an+expired ticket) the arena has nothing to open, so the card that says so carries+**the war room**: the battles running right now, the communities queued for an+opponent, and the top of the ladder, read live from `/api/wars`. Every row links+into that coin's world at `/play?coin=…`, which is where the war portal stands,+and a live row carries `&war=<matchKey>` so that world's portal board opens on+the battle you were reading about. The same panel appears under every other+terminal state (an expired ticket, a holding below the floor, a dropped+connection), because "there is no battle here" is only useful next to "here is+where one is".++The war room is [`src/play/war-board.js`](../src/play/war-board.js). It reads the+same fold the in-world portal board reads, refreshes every 15s while the tab is+visible, and has its own designed loading, empty, error and offline-matchmaking+states. Coin names and images arriving from `/api/wars` are on-chain metadata:+they are rendered through `textContent` and URL-encoded query values, never as+markup.---@@ -44693,6 +47291,14 @@ battlefield. `return` is only ever honoured as a same-origin path.| `UPSTASH_REDIS_REST_URL` / `_TOKEN` | API + game server | The matchmaking queue and the live spectator registry. Without these, wars cannot be queued (the portal says so) and nothing can be spectated; the ladder still reads. || `THREE_WS_API_BASE` | game server | Where the game server posts battle results. Defaults to `https://three.ws`. |+The arena page also has to know which Colyseus host runs `clash_arena`. That is+not an env var: `pages/play/war.html` carries a `<meta name="game-server">`, read+through [`src/shared/game-server-url.js`](../src/shared/game-server-url.js), the+same chain `/play` uses. A production build resolves to `""` without it (the+localhost and Codespace hosts are inferred, the public domain is not), and every+arrival at the arena then dead-ends on "The arena server is unreachable". Keep+the meta on this page and on `pages/play.html` in step with the deployed service.+---## Where the code is@@ -44702,19 +47308,20 @@ battlefield. `return` is only ever honoured as a same-origin path.| The in-world portal | [`src/game/war-portal.js`](../src/game/war-portal.js), [`src/game/war-portal.css`](../src/game/war-portal.css) || Portal location in the plaza | [`multiplayer/src/world-features.js`](../multiplayer/src/world-features.js) (`WAR_PORTAL`) || The arena page | [`pages/play/war.html`](../pages/play/war.html), [`src/play/war.js`](../src/play/war.js), [`src/play/war-world.js`](../src/play/war-world.js) |+| The war room on the terminal cards | [`src/play/war-board.js`](../src/play/war-board.js) || The room | [`multiplayer/src/rooms/ClashRoom.js`](../multiplayer/src/rooms/ClashRoom.js) (`clash_arena`) || Match rules (phases, score cap, sudden death) | [`multiplayer/src/clash.js`](../multiplayer/src/clash.js) || Pairing math | [`multiplayer/src/war-matchmaking.js`](../multiplayer/src/war-matchmaking.js) || League math | [`multiplayer/src/war-standings.js`](../multiplayer/src/war-standings.js) || Spectator snapshots | [`multiplayer/src/war-live.js`](../multiplayer/src/war-live.js) || 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 | [`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-289), [play hardening](#sec-378).+Related: [the in-game economy](#sec-299), [play hardening](#sec-391).----<a id="sec-160"></a>+<a id="sec-164"></a>> **Source:** `docs/coingecko-listing-update-2026-08.md` · [↑ table of contents](#table-of-contents)@@ -44982,7 +47589,7 @@ full link set is one click away without cluttering the verification post itself.----<a id="sec-161"></a>+<a id="sec-165"></a>> **Source:** `docs/coinmarketcap-article-2026-09-agent-economy.md` · [↑ table of contents](#table-of-contents)@@ -45180,7 +47787,7 @@ Beyond phones, an agent's status renders as a glance card on a Windows 11 widget## The 3D half, in one paragraph, because it is the moat-None of the above would be interesting if the agents themselves were text boxes. A three.ws agent is generated from a prompt into a rigged, animated 3D body with 52 ARKit blendshapes for lipsync, embeddable in any website with one HTML tag. Generation runs on an owned GPU fleet across open model families, with a failover chain per lane so an unavailable model degrades quality instead of failing the request. Animation is universal: bone names are canonicalised across the Mixamo, Avaturn, Unreal, VRM, Daz, MakeHuman and Blender conventions and clips are retargeted onto whatever came in, with no curated rig allowlist. This quarter the agents also learned to see their own output, so generation became a loop instead of one shot, and to grade a model's readiness for a physics engine, which matters the moment an asset is destined for a simulator, a game, or a printer.+None of the above would be interesting if the agents themselves were text boxes. A three.ws agent is generated from a prompt into a rigged, animated 3D body with 52 ARKit blendshapes for lipsync, embeddable in any website with one HTML tag. Generation runs on an owned GPU fleet across open model families, with a failover chain per lane so an unavailable model degrades quality instead of failing the request. Animation is universal: bone names are canonicalised across the Mixamo, Unreal, VRM, Daz, MakeHuman and Blender conventions and clips are retargeted onto whatever came in, with no curated rig allowlist. This quarter the agents also learned to see their own output, so generation became a loop instead of one shot, and to grade a model's readiness for a physics engine, which matters the moment an asset is destined for a simulator, a game, or a printer.## The $THREE part, with the mechanics stated plainly@@ -45254,7 +47861,7 @@ Nothing here is financial advice. Read the endpoints, not the adjectives.----<a id="sec-162"></a>+<a id="sec-166"></a>> **Source:** `docs/coinmarketcap-article-play.md` · [↑ table of contents](#table-of-contents)@@ -45400,7 +48007,7 @@ The chart has always told you *what* a coin is doing. /play lets you go stand wh----<a id="sec-163"></a>+<a id="sec-167"></a>> **Source:** `docs/coinmarketcap-article.md` · [↑ table of contents](#table-of-contents)@@ -45603,7 +48210,7 @@ If you've been waiting for the moment AI and crypto stop talking past each other----<a id="sec-164"></a>+<a id="sec-168"></a>> **Source:** `docs/coinmarketcap-live-article.md` · [↑ table of contents](#table-of-contents)@@ -45727,7 +48334,7 @@ at [community.ibm.com](https://community.ibm.com/community/user/usergroup?Commun----<a id="sec-165"></a>+<a id="sec-169"></a>> **Source:** `docs/community.md` · [↑ table of contents](#table-of-contents)@@ -45778,11 +48385,11 @@ Two additions specific to this project:## Contributing-New here? Start with [Your first contribution](#sec-241), 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-480).+New here? Start with [Your first contribution](#sec-247), 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-500).----<a id="sec-166"></a>+<a id="sec-170"></a>> **Source:** `docs/companion.md` · [↑ table of contents](#table-of-contents)@@ -46143,7 +48750,7 @@ A delivery on the stream carries everything a body needs to perform it:----<a id="sec-167"></a>+<a id="sec-171"></a>> **Source:** `docs/compose.md` · [↑ table of contents](#table-of-contents)@@ -46171,7 +48778,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-124) 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-127) survive it.## Walkthrough@@ -46224,15 +48831,15 @@ curl -X PATCH 'https://three.ws/api/avatars/<avatarId>' \## Related-- [Avatar Studio](#sec-124): build the avatar you dress here.+- [Avatar Studio](#sec-127): build the avatar you dress here.- [Animation Studio](#sec-096): pose and animate the dressed avatar.-- [Scene Studio](#sec-427): the full three.js editor for heavier scene authoring.-- [Restyle Studio](#sec-422): re-skin the forged props before attaching them.+- [Scene Studio](#sec-443): the full three.js editor for heavier scene authoring.+- [Restyle Studio](#sec-437): 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-168"></a>+<a id="sec-172"></a>> **Source:** `docs/concierge.md` · [↑ table of contents](#table-of-contents)@@ -46340,12 +48947,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-436): every other way to put a three.ws creation on your site-- [MCP](#sec-318): the full catalog of three.ws MCP servers, including this one+- [Share and embed](#sec-453): every other way to put a three.ws creation on your site+- [MCP](#sec-329): the full catalog of three.ws MCP servers, including this one----<a id="sec-169"></a>+<a id="sec-173"></a>> **Source:** `docs/configuration.md` · [↑ table of contents](#table-of-contents)@@ -46401,7 +49008,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-191)).+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-195)).#### `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.@@ -46687,7 +49294,7 @@ WEB3_STORAGE_TOKEN=xxxxx```#### Solana signer keys (`*_SECRET_KEY_B64`)-**Optional.** Server-side Solana keypairs the cron jobs and on-chain flows sign with: `PUMP_CRON_RELAYER_SECRET_KEY_B64` (pays tx fees for the Pump.fun buyback cron), `COIN_TREASURY_SECRET_KEY_B64`, `CLUB_SOLANA_TREASURY_SECRET_KEY_B64`, `PUMP_X402_LAUNCHER_SECRET_KEY_B64`. Each is the **base64 encoding of the 64 raw secret-key bytes**, the format `decodeSecretKey` expects (`api/_lib/solana-signers.js`).+**Optional.** Server-side Solana keypairs the cron jobs and on-chain flows sign with: `PUMP_CRON_RELAYER_SECRET_KEY_B64` (pays tx fees for the Pump.fun buyback cron), `COIN_TREASURY_SECRET_KEY_B64`, `THREE_BUYBACK_SECRET_KEY_B64`, `CLUB_SOLANA_TREASURY_SECRET_KEY_B64`, `PUMP_X402_LAUNCHER_SECRET_KEY_B64`. Each is the **base64 encoding of the 64 raw secret-key bytes**, the format `decodeSecretKey` expects (`api/_lib/solana-signers.js`).```PUMP_CRON_RELAYER_SECRET_KEY_B64=<base64 of 64-byte keypair>@@ -46904,7 +49511,7 @@ Before going live, verify the following:----<a id="sec-170"></a>+<a id="sec-174"></a>> **Source:** `docs/content/use-cases/README.md` · [↑ table of contents](#table-of-contents)@@ -46916,11 +49523,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-175) | Turn a selfie or a text prompt into a 3D agent and embed it anywhere. |-| Game studio | [game-studio.md](#sec-174) | 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-171) | Give an agent a body, paid endpoints (x402), an MCP/A2A interface, and on-chain identity. |-| Brand / marketer | [brand-marketer.md](#sec-172) | Put an embeddable, verifiable talking agent on a site, distributed through cloud marketplaces. |-| Crypto community | [crypto-community.md](#sec-173) | Give a token community a live 3D world, an agent economy, and on-chain reputation. |+| Indie creator | [indie-creator.md](#sec-179) | Turn a selfie or a text prompt into a 3D agent and embed it anywhere. |+| Game studio | [game-studio.md](#sec-178) | 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-175) | Give an agent a body, paid endpoints (x402), an MCP/A2A interface, and on-chain identity. |+| Brand / marketer | [brand-marketer.md](#sec-176) | Put an embeddable, verifiable talking agent on a site, distributed through cloud marketplaces. |+| Crypto community | [crypto-community.md](#sec-177) | Give a token community a live 3D world, an agent economy, and on-chain reputation. |## How to read these (the honesty frame)@@ -46949,7 +49556,7 @@ Every scenario on these pages is an **example workflow** — clearly labeled "Im----<a id="sec-171"></a>+<a id="sec-175"></a>> **Source:** `docs/content/use-cases/ai-agent-developer.md` · [↑ table of contents](#table-of-contents)@@ -46969,8 +49576,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-318) 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-624) 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-329) 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-645) 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/`.@@ -46978,8 +49585,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-318) 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-624): 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-329) 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-645): 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.@@ -46990,14 +49597,14 @@ A standards-based interface (MCP + A2A), a working USDC payment rail (x402 on Ba## Next step / CTA-- Start: [MCP setup](#sec-318) · [x402 docs](#sec-624) · [SDK docs](#sec-428) · register via [Register On-Chain](#sec-530).+- Start: [MCP setup](#sec-329) · [x402 docs](#sec-645) · [SDK docs](#sec-444) · register via [Register On-Chain](#sec-550).- 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-172"></a>+<a id="sec-176"></a>> **Source:** `docs/content/use-cases/brand-marketer.md` · [↑ table of contents](#table-of-contents)@@ -47019,7 +49626,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-133) 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-136) 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)@@ -47039,7 +49646,7 @@ Four real capabilities cover embodiment, reach, and trust:width="340px" height="440px"></agent-3d>```-3. She [registers the agent on-chain](#sec-530) (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-550) (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.@@ -47049,14 +49656,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-530) → claim a name at [`/threews/claim`](https://three.ws/threews/claim).-- Enterprise: [AWS Marketplace listing](#sec-133) · [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-550) → claim a name at [`/threews/claim`](https://three.ws/threews/claim).+- Enterprise: [AWS Marketplace listing](#sec-136) · [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-173"></a>+<a id="sec-177"></a>> **Source:** `docs/content/use-cases/crypto-community.md` · [↑ table of contents](#table-of-contents)@@ -47077,7 +49684,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-624) (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-645) (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)@@ -47086,7 +49693,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-530), 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-550), 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.@@ -47097,13 +49704,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-624) for the agent-economy rails · [Register On-Chain](#sec-530) for reputation.+- Build: [x402 docs](#sec-645) for the agent-economy rails · [Register On-Chain](#sec-550) 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-174"></a>+<a id="sec-178"></a>> **Source:** `docs/content/use-cases/game-studio.md` · [↑ table of contents](#table-of-contents)@@ -47144,13 +49751,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-500) · [Agent System docs](#sec-065) · [Skill spec](../specs/SKILL_SPEC.md).+- Learn: [Write a Custom Skill](#sec-520) · [Agent System docs](#sec-065) · [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-175"></a>+<a id="sec-179"></a>> **Source:** `docs/content/use-cases/indie-creator.md` · [↑ table of contents](#table-of-contents)@@ -47204,13 +49811,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-509) · [Embed on Your Website](#sec-505).+- Learn: [Build Your First Agent](#sec-529) · [Embed on Your Website](#sec-525).- **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-176"></a>+<a id="sec-180"></a>> **Source:** `docs/contributing.md` · [↑ table of contents](#table-of-contents)@@ -47285,7 +49892,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-169) and the [Deployment & Self-Hosting](#sec-191) guide.+For full backend setup — R2 storage, environment variables, and how the app is deployed — see the [Configuration Reference](#sec-173) and the [Deployment & Self-Hosting](#sec-195) guide.---@@ -47319,7 +49926,7 @@ src/└── components/ — vhtml JSX components (string-based, no virtual DOM)```-See the [Architecture Overview](#sec-292) for a deeper understanding of how these pieces connect.+See the [Architecture Overview](#sec-302) for a deeper understanding of how these pieces connect.---@@ -47527,7 +50134,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-447) for the full format, lifecycle hooks, and message API.+2. **Build your skill.** See the [Skills documentation](#sec-465) 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.@@ -47563,7 +50170,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-429). 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-445). Public disclosure of an unpatched vulnerability puts all users at risk.---@@ -47590,7 +50197,7 @@ By contributing, you agree that your contributions are licensed under the [Apach----<a id="sec-177"></a>+<a id="sec-181"></a>> **Source:** `docs/cookbook/asset-quality-gate.md` · [↑ table of contents](#table-of-contents)@@ -47757,7 +50364,7 @@ build on any of them. They are a good backlog for whatever ships the assets.----<a id="sec-178"></a>+<a id="sec-182"></a>> **Source:** `docs/cookbook/mcp-3d-tool.md` · [↑ table of contents](#table-of-contents)@@ -47896,7 +50503,7 @@ endpoints.----<a id="sec-179"></a>+<a id="sec-183"></a>> **Source:** `docs/cookbook/parallel-asset-pack.md` · [↑ table of contents](#table-of-contents)@@ -48065,7 +50672,7 @@ machine. Useful for picking a triangle budget before you commit to one.----<a id="sec-180"></a>+<a id="sec-184"></a>> **Source:** `docs/cookbook/text-to-3d-cli.md` · [↑ table of contents](#table-of-contents)@@ -48214,7 +50821,7 @@ the lane is queued, which is exactly when `retryAfter` starts mattering.----<a id="sec-181"></a>+<a id="sec-185"></a>> **Source:** `docs/copy-trading.md` · [↑ table of contents](#table-of-contents)@@ -48229,11 +50836,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-255) 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-261) 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-093) 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-450) for the first-party wallet reputation graph, [the trading surfaces](#sec-479) for the screeners and the trading cockpit these leaders trade from, [agent wallets](#sec-074) for the custody and spend-policy model, and [signal marketplace](#sec-441) for the paid-feed variant that reuses the same guarded executor.+Related reading: [Smart Money Radar](#sec-468) for the first-party wallet reputation graph, [the trading surfaces](#sec-499) for the screeners and the trading cockpit these leaders trade from, [agent wallets](#sec-074) for the custody and spend-policy model, and [signal marketplace](#sec-459) for the paid-feed variant that reuses the same guarded executor.---@@ -48243,7 +50850,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-255).+- **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-261).- **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`.@@ -48268,7 +50875,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-156) 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-160) 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@@ -48649,7 +51256,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`. 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-450).+For first-party wallet reputation earned from three.ws's own outcome ledger rather than an external taxonomy, use [Smart Money Radar](#sec-468).---@@ -48683,7 +51290,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-318) for wiring these into a client.+See [the MCP reference](#sec-329) for wiring these into a client.---@@ -48698,7 +51305,7 @@ See [the MCP reference](#sec-318) for wiring these into a client.----<a id="sec-182"></a>+<a id="sec-186"></a>> **Source:** `docs/cosmos.md` · [↑ table of contents](#table-of-contents)@@ -48789,13 +51396,13 @@ else {## Related-- [Forge](#sec-245) makes the 3D avatars and objects you place in a Cosmos world.-- [Avatar creation](#sec-118) and [the trait-based avatar builder](#sec-149) for building and dressing avatars.+- [Forge](#sec-251) makes the 3D avatars and objects you place in a Cosmos world.+- [Avatar creation](#sec-121) and [the trait-based avatar builder](#sec-153) for building and dressing avatars.- Pages: [/create](https://three.ws/create), [/gallery](https://three.ws/gallery), [/scene](https://three.ws/scene).----<a id="sec-183"></a>+<a id="sec-187"></a>> **Source:** `docs/create-agent.md` · [↑ table of contents](#table-of-contents)@@ -48895,7 +51502,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-318).+`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-329).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).@@ -48921,9 +51528,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-578).+- **Put it on your site.** The printed snippet is the whole integration; attribute reference in [web-component.md](#sec-599).- **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-257) puts the agent's live status on a home screen, in a README, or in Slack.+- **Show what it is doing.** [Glance](#sec-263) 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).---@@ -48937,7 +51544,7 @@ three.ws examples repo, so it is installed, run, and link-checked before every r----<a id="sec-184"></a>+<a id="sec-188"></a>> **Source:** `docs/creator-portfolio.md` · [↑ table of contents](#table-of-contents)@@ -49086,7 +51693,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-342).+ documented in [Notifications](#sec-353).- **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@@ -49129,19 +51736,19 @@ unfurl; an unknown handle is still a cached 404 card.## Related pages-- [The social layer](#sec-452): the follow graph, feed, and+- [The social layer](#sec-470): the follow graph, feed, andrankings this page plugs into.-- [Notifications](#sec-342): the follow, remix, sale, and royalty+- [Notifications](#sec-353): the follow, remix, sale, and royaltyevents a portfolio generates for its owner.-- [Remix economy](#sec-418): what happens when someone remixes a creation+- [Remix economy](#sec-433): what happens when someone remixes a creationthey found here.-- [Forge](#sec-245), [Widgets](#sec-581),- [Marketplace](#sec-310): the creation surfaces whose output the+- [Forge](#sec-251), [Widgets](#sec-602),+ [Marketplace](#sec-321): the creation surfaces whose output theportfolio aggregates.----<a id="sec-185"></a>+<a id="sec-189"></a>> **Source:** `docs/crews.md` · [↑ table of contents](#table-of-contents)@@ -49332,7 +51939,7 @@ player who is already social in the world finds the group surface.----<a id="sec-186"></a>+<a id="sec-190"></a>> **Source:** `docs/crypto-api.md` · [↑ table of contents](#table-of-contents)@@ -50390,7 +52997,7 @@ curl -s "https://three.ws/api/crypto/airdrops?address=<wallet>" \----<a id="sec-187"></a>+<a id="sec-191"></a>> **Source:** `docs/custody.md` · [↑ table of contents](#table-of-contents)@@ -50416,7 +53023,7 @@ Limits live per agent and are owner-configurable from the wallet hub (API: `GET/Enforcement 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-240) 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-246) 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@@ -50475,14 +53082,14 @@ Every step of recovery and inheritance writes to the custody trail and the audit## Related-- [Financial controls](#sec-240) — plain-English spend rules and real-time wallet defense on these rails-- [Trading surfaces](#sec-479) — Mission Control executes through this same guarded path-- [The trading experiment](#sec-477) — an autonomous agent operating inside these limits, journaled-- [x402](#sec-624) — the payment protocol these wallets spend over+- [Financial controls](#sec-246) — plain-English spend rules and real-time wallet defense on these rails+- [Trading surfaces](#sec-499) — Mission Control executes through this same guarded path+- [The trading experiment](#sec-497) — an autonomous agent operating inside these limits, journaled+- [x402](#sec-645) — the payment protocol these wallets spend over----<a id="sec-188"></a>+<a id="sec-192"></a>> **Source:** `docs/daily-forge.md` · [↑ table of contents](#table-of-contents)@@ -50583,14 +53190,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-242): the job and polling model-- [AR and WebXR](#sec-107): the Scene Viewer and Quick Look handoff-- [Quick start](#sec-414): the general free-forge onboarding+- [Forge background generation](#sec-248): the job and polling model+- [AR and WebXR](#sec-108): the Scene Viewer and Quick Look handoff+- [Quick start](#sec-429): 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-189"></a>+<a id="sec-193"></a>> **Source:** `docs/daily-match.md` · [↑ table of contents](#table-of-contents)@@ -50760,11 +53367,11 @@ P&L and Score columns become unreachable on a phone.Related docs: [agent-sniper.md](#sec-062) (where the trade and P&Lcolumns come from), [agent-skills.md](#sec-061) (skill sales),-[pump-launcher.md](#sec-392) (launches).+[pump-launcher.md](#sec-407) (launches).----<a id="sec-190"></a>+<a id="sec-194"></a>> **Source:** `docs/demo-routes.md` · [↑ table of contents](#table-of-contents)@@ -50991,7 +53598,7 @@ the 200s above still come from the 2026-08-05 curl sweep.----<a id="sec-191"></a>+<a id="sec-195"></a>> **Source:** `docs/deployment.md` · [↑ table of contents](#table-of-contents)@@ -51364,7 +53971,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-199) 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-204) guide for the driver patterns.### Static asset caching@@ -51429,7 +54036,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-207), and verify+[erc8004/validation-attestation.md](#sec-212), and verifyany configured registry address with `npm run verify:erc8004-validation`.---@@ -51491,7 +54098,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-199) 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-204) guide.### Database monitoring@@ -51586,7 +54193,7 @@ Upstash REST API uses HTTPS — no ports to open. If you see connection errors,----<a id="sec-192"></a>+<a id="sec-196"></a>> **Source:** `docs/deployments.md` · [↑ table of contents](#table-of-contents)@@ -51598,7 +54205,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-206) for the standard, the registry contracts, and how to register; [deploying agents on-chain](#sec-355) for the Solana Metaplex Core path; [agent reputation on Solana](#sec-454) for the trust layer built on top of a Solana identity.+Related reading: [ERC-8004 blockchain identity](#sec-211) for the standard, the registry contracts, and how to register; [deploying agents on-chain](#sec-367) for the Solana Metaplex Core path; [agent reputation on Solana](#sec-472) for the trust layer built on top of a Solana identity.---@@ -51613,7 +54220,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-355) (the single-agent, user-signed flow is in [Solana agents](#sec-455)), and Solana reputation and attestations are in [agent reputation on Solana](#sec-454). 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-367) (the single-agent, user-signed flow is in [Solana agents](#sec-473)), and Solana reputation and attestations are in [agent reputation on Solana](#sec-472). This page is only the index and the feed.---@@ -51673,7 +54280,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-206) 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-211) for the addresses and the contract surface.### 2. Solana: three.ws's own Metaplex Core mints@@ -51823,7 +54430,7 @@ The network toggle derives its chain-id sets from that table at import time, so----<a id="sec-193"></a>+<a id="sec-197"></a>> **Source:** `docs/developer-platform.md` · [↑ table of contents](#table-of-contents)@@ -51843,8 +54450,8 @@ The browser UI for all of this lives in the dashboard:Base URL: `https://three.ws`-Related docs: [MCP integration](#sec-318), [API reference](#sec-104),-[Authentication](#sec-112), [x402 developer tools](#sec-617).+Related docs: [MCP integration](#sec-329), [API reference](#sec-105),+[Authentication](#sec-115), [x402 developer tools](#sec-638).---@@ -51884,15 +54491,15 @@ key, no CSRF.## API keysAPI keys are bearer credentials for machine clients: the MCP server at-`/api/mcp` (see [MCP integration](#sec-318)) and the account-scoped REST+`/api/mcp` (see [MCP integration](#sec-329)) and the account-scoped RESTendpoints that accept `Authorization: Bearer` (see the-[API reference](#sec-104)). Each key carries a set of scopes:+[API reference](#sec-105)). Each key carries a set of scopes:`avatars:read`, `avatars:write`, `avatars:delete`, `profile`, `memory:read`,`memory:write`, `agents:read`, `agents:write`One more scope, `herald:announce` (posting through the-[Herald](#sec-261)), is accepted by `/api/keys`, the dashboard form, and the+[Herald](#sec-269)), is accepted by `/api/keys`, the dashboard form, and theolder `POST /api/api-keys` route documented in[Authentication](authentication.md#available-scopes).@@ -52095,7 +54702,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-242)). Without a+[forge-background-generation.md](#sec-248)). 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.@@ -52375,7 +54982,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-318) for configuring a real client against+See [MCP integration](#sec-329) for configuring a real client against`/api/mcp`.---@@ -52454,7 +55061,102 @@ omitted from the manifest.----<a id="sec-194"></a>+<a id="sec-198"></a>++> **Source:** `docs/devto-mcp-fleet-post.md` · [↑ table of contents](#table-of-contents)++---+venue: dev.to (cross-post to Hashnode and Medium with canonical back to three.ws)+account: three.ws / nichxbt+suggested_title: "We published 72 MCP servers. Here is what I would do differently."+description: "A practical post-mortem on running a large MCP fleet: why we ended up with 72 servers, the four traps that cost us the most (annotation blindness, stdio consent, OAuth discovery 404s, and free/paid entanglement), and the four rules we now build to."+tags: [mcp, ai, agents, opensource]+canonical: https://three.ws/docs/mcp+status: draft, owner approval required before posting (external-channel gate in CLAUDE.md)+---++# We published 72 MCP servers. Here is what I would do differently.++Not a brag. A confession, and then four rules.++I work on [three.ws](https://three.ws), an open-source platform where AI agents get 3D bodies. Along the way we ended up publishing **72 MCP servers in the official Model Context Protocol registry** under one namespace, and **91 npm packages**, 39 of them MCP servers in the main repo. That happened over months, one reasonable decision at a time, and the sum of those reasonable decisions is a discovery problem.++If you are about to publish your second, fifth, or fiftieth MCP server, this is what I know now that I did not know then.++## How you get to 72 without ever deciding to++Every capability that felt independently useful became its own server, because publishing a server is cheap and MCP has no first-class notion of a bundle or a namespace. Avatars, 3D generation, scenes, voice, vision, market data, notifications, billing, naming, provenance, home control, and so on. Each one was defensible. None of them was the result of a plan.++The failure is not technical. All 72 work. The failure is that **a user cannot find the right one**, and neither can an agent, and the registry alone does not fix that.++## Trap 1: tool annotations describe, they do not enforce++MCP gives you `readOnlyHint`, `destructiveHint`, `openWorldHint`. Set them accurately; reviewers check, and inaccurate annotations are a listed rejection reason on the platforms with directories.++But understand what they are: **metadata for the client's UI, not a control.** They do not stop a tool. And the vocabulary has a real gap: `destructiveHint` covers "this deletes something", and does not distinguish between "this spends forty dollars" and "this unlocks a door in a house where a child is asleep".++We now write the server-side refusal first and the interface second. If a guard exists only in prompt text or in a hidden button, it is not a guard. An assistant can be argued out of a sentence; it cannot be argued out of a 403.++## Trap 2: a stdio server cannot obtain consent, and should stop pretending++We publish a server that gives any assistant control of a real Home Assistant house: read the house, list entities, list scenes, run one, call a service.++The dangerous calls (locks, primarily) pass through a physical-action gate, and **over stdio that gate refuses outright**. Not "prompts the user". Refuses.++The reasoning took us a while to arrive at and now seems obvious. A local stdio MCP server has no user-visible surface of its own, no session, and no way to prove that a human saw a request and approved it. Any "confirm?" it emits is a string the model can read, generate, and answer by itself. That is not consent, it is theatre. So the dangerous verbs are only available on a surface where a real person can be shown a real prompt, and the local server says plainly that it will not do it and why.++The pattern generalises past homes to any stdio server that can spend money, send messages as a user, or move something physical.++## Trap 3: the OAuth discovery document nobody checks++Our hosted server sits behind OAuth 2.1. The single most common reason a technically-correct MCP server fails a client's auth handshake is that `/.well-known/oauth-protected-resource` (or its neighbours) is not actually routed and answers 404, usually because the route table and the file layout disagree in production but not locally.++Test it from outside your network, in production, with curl, after every deploy. It is a one-line check and it saves a week of "works on my machine" bug reports from users you cannot debug.++## Trap 4: free and paid entangled in one server++We ship a free 3D server and a paid one. The free one has **no payment code in it at all.** Not disabled, not feature-flagged: absent. Different origin, different codebase, different deploy.++This started as a review-friendliness decision (the directories reject anything that looks like it might charge under false pretences, and "we present a call as free and then charge" is a listed rejection reason). It turned out to be an engineering win too: a claim you can verify by reading an import list is a claim that stays true, and a flag that gates payment is a flag somebody will flip in the wrong environment eventually.++The one exception we allow runs the other way, and it is deliberate: a couple of tools on the **paid** server are permanently free, because they are assurance checks. An asset-grading tool that costs money is a tool nobody calls, and a tool nobody calls prevents nothing.++## The four rules we build to now++**1. One tightly scoped server per audience, not per capability.** Our ChatGPT-facing server is exactly the 3D tools and nothing else: eleven of them, keyless, no wallet, no account. The directories reward tightly scoped apps and reject generic ones, and thirty-seven separately submitted servers read as directory spam even when each one is good. Submit one, document the rest as direct connections.++**2. One hosted server for clients that want everything**, behind real auth, with working discovery metadata.++**3. Typed tool authoring, shared across servers.** We publish `@three-ws/tool-sdk` (`defineTool`, `defineExec`) so annotations, schemas, and error shapes cannot drift from server to server. Fifty hand-written servers will disagree about error shape by the third one, and an agent handling five different error conventions handles none of them well.++**4. Publish where clients actually look.** The official registry is necessary and not sufficient. Ours are also indexed on PulseMCP and Glama, exposed through a LobeHub plugin manifest served from our own domain, and shipped as plugins in an editor plugin marketplace. Discovery is distribution, and distribution is not automatic.++## The one thing that mattered more than all of it++If you take a single idea from this post, take this one instead of anything about fleets.++Every text-to-3D API, ours included, answered tool calls with a **URL to a binary file**. A human clicks it. An agent cannot read it. So we shipped a tool that renders a model into frames returned as MCP image content blocks, and the agent can finally look at what it made, judge it, and iterate.++It was a weekend of work and it changed what the pipeline can do, because a loop needs an error signal and a binary URL is not one.++**Any tool that hands an agent a binary needs a companion that renders it into the agent's own modality.** PDFs, spreadsheets, audio, CAD, compiled artifacts. If your agent cannot perceive its own output, it is guessing, and no amount of prompt engineering fixes that.++## Try any of it++```bash+# 11 keyless 3D tools, no account+curl -s https://three.ws/api/mcp-studio \+ -H 'content-type: application/json' \+ -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'+```++Everything is Apache-2.0 at [github.com/nirholas/three.ws](https://github.com/nirholas/three.ws). The MCP docs are at [three.ws/docs/mcp](https://three.ws/docs/mcp).++If you publish MCP servers at any scale, I would like to hear how you handle namespacing and discovery. I do not think our answer is right; it is only the one that worked.++---++<a id="sec-199"></a>> **Source:** `docs/diorama.md` · [↑ table of contents](#table-of-contents)@@ -52556,13 +55258,13 @@ until the world is saved:## Related-- [Forge](#sec-245) is the single-object generator every diorama object is forged on.-- [Image to 3D](#sec-288) for photo-based objects; [AR](#sec-107) for viewing worlds in augmented reality.+- [Forge](#sec-251) is the single-object generator every diorama object is forged on.+- [Image to 3D](#sec-298) for photo-based objects; [AR](#sec-108) 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-195"></a>+<a id="sec-200"></a>> **Source:** `docs/do-i-need-crypto.md` · [↑ table of contents](#table-of-contents)@@ -52642,14 +55344,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-308)-- **Put it on your site** → [Share & embed](#sec-436)-- **Optional: register on-chain** → [Register on-chain](#sec-530)-- **Technical auth details** → [Authentication](#sec-112)+- **Create your first agent** → [Make your first agent](#sec-319)+- **Put it on your site** → [Share & embed](#sec-453)+- **Optional: register on-chain** → [Register on-chain](#sec-550)+- **Technical auth details** → [Authentication](#sec-115)----<a id="sec-196"></a>+<a id="sec-201"></a>> **Source:** `docs/docs-world.md` · [↑ table of contents](#table-of-contents)@@ -52738,7 +55440,7 @@ Adding a section is the same edit: append to `sections` and a new pavilion appea----<a id="sec-197"></a>+<a id="sec-202"></a>> **Source:** `docs/draft-agent-mint.md` · [↑ table of contents](#table-of-contents)@@ -52968,14 +55670,14 @@ explorer link, so the evidence file never overstates what was proven.## Related-- [Selfie to Avatar](#sec-435): the pipeline whose tail calls this+- [Selfie to Avatar](#sec-451): the pipeline whose tail calls this- [Agent identities](#sec-054): what an agent identity is and how it is generated- [Agent tokens](#sec-071): what happens after a draft identity goes live- [The agent index](#sec-055): the cross-chain index that surfaces these registrations----<a id="sec-198"></a>+<a id="sec-203"></a>> **Source:** `docs/drops.md` · [↑ table of contents](#table-of-contents)@@ -52994,8 +55696,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-324) for one-off Metaplex Core mints,-[the Forge](#sec-245) for the text-to-3D pipeline every reveal runs on, and+Related surfaces: [Minted 3D Assets](#sec-335) for one-off Metaplex Core mints,+[the Forge](#sec-251) for the text-to-3D pipeline every reveal runs on, and[the avatar gallery](../public/gallery/index.html) at `/gallery` for individualavatars.@@ -53091,7 +55793,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-245). The page then polls until the GLB lands.+submits it to [the Forge](#sec-251). 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@@ -53114,6 +55816,7 @@ GLB, VRM 1.0, or USDZ through [`src/avatar-export.js`](../src/avatar-export.js).The **Verify this roll** button on every collection page calls:+<!-- runnable: 404 clay-wardens is an example slug; a live collection answers 200 -->```bashcurl "https://three.ws/api/drops/verify?slug=clay-wardens&index=7"```@@ -53156,7 +55859,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-324) path today.+one at a time through the existing [Minted 3D Assets](#sec-335) 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.@@ -53199,7 +55902,7 @@ can never shadow each other.----<a id="sec-199"></a>+<a id="sec-204"></a>> **Source:** `docs/economy-heartbeat.md` · [↑ table of contents](#table-of-contents)@@ -53242,6 +55945,7 @@ that makes the economy move:| Coin launches (pump.fun) | `launcher-tick`, `launcher-claimer`, `pumpfun-monitor`, `pumpfun-graduations-sync`, `run-coin-cycle`, `run-coin-payouts` | autonomous minting, fee claims, graduation sync, coin lifecycle + payouts || Autonomous / copy / strategy trading | `copy-fanout`, `mirror-fanout`, `signal-fanout`, `strategy-fanout`, `run-dca` | copy trading, signal/strategy execution, DCA || Tips, payouts, subscriptions, royalties | `club-payouts`, `run-subscriptions`, `process-subscriptions`, `settle-royalties`, `cosmetic-splits-sweep` | tipping payouts, subscription billing, royalty + cosmetic-split settlement |+| $THREE buyback | `run-buyback`, `run-three-buyback`, `three-buy-loop` | revenue → buy → treasury (internally gated hourly/daily), plus the x402-settled micro-buy loop || Funding, treasury & reconcile | `treasury-topup`, `economy-rebalance`, `treasury-autopilot`, `treasury-sweepback`, `economy-reconcile`, `reflect-sweep` | master-wallet funding root, economy rebalance, treasury autopilot, tamper reconciliation || $THREE market & holders | `three-market-refresh`, `three-holders-snapshot` | live coin market + holder snapshots |@@ -53364,13 +56068,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-154) ·-[x402 ring economy](#sec-621) ·-[economy funding root](#sec-200) · [money map](#sec-335)+Related: [circulation engine](#sec-158) ·+[x402 ring economy](#sec-642) ·+[economy funding root](#sec-205) · [money map](#sec-346)----<a id="sec-200"></a>+<a id="sec-205"></a>> **Source:** `docs/economy-master.md` · [↑ table of contents](#table-of-contents)@@ -53616,6 +56320,47 @@ node scripts/sniper-fleet-restore.mjs --apply --yes # top up the fundable armsSweeps below `ECONOMY_SWEEPBACK_MIN_SOL` (0.01 SOL) are skipped as dust.+### A floor skip says whether the wallet is empty or fenced++Both reclaim legs skip a wallet whose balance sits under its keep line (its+operating floor plus the anti-oscillation buffer). That skip used to print the+bare string `at_or_below_floor`, which cannot distinguish the two situations an+operator has to tell apart:++| Situation | What it means | What fixes it |+| --- | --- | --- |+| The wallet holds ~0 SOL | The source is genuinely empty | Owner capital to the economy master, nothing else |+| The wallet holds real SOL under a higher floor | The platform owns the SOL; a configured floor is fencing it | Review that wallet's `minSol` in [`api/_lib/solana-signers.js`](../api/_lib/solana-signers.js), or accept the fence |++They printed identically, so three consecutive triage sessions read the second as+the first. On 2026-09-09 the x402 ring treasury (`wwwww…ccrU`) held 0.055 SOL+against a `minSol` of 0.1, and reported the same `at_or_below_floor` as the 110+genuinely-empty agent wallets beside it, while the ring payer was 0.0012 SOL short+of the hard floor that had stopped settlement.++A floor skip now carries both numbers, in the `<have><<need>` shape+`below_swap_rent` already uses, and the run totals the fenced SOL:++```json+{+ "name": "pump-x402-launcher",+ "reason": "at_or_below_floor:0.054994966<0.11",+ "heldSol": 0.054994966,+ "floorSol": 0.1,+ "keepSol": 0.11+}+```++- `keepSol` is the number that actually blocked the sweep. Reporting and sizing+ both read `reclaimKeepLineSol()`, so the message can never explain a refusal the+ code did not make.+- `floorHeldSol` on each reclaim result, and `skipped_floor_held_sol` on the+ ledger's summary row, total the fenced SOL. **Zero is the only state that needs+ owner money.** Non-zero means the SOL exists on a platform wallet.+- The ledger's `skipped_reasons` histogram buckets on the class before the colon,+ so a fleet-wide run still reports `{"at_or_below_floor": 110}` rather than 110+ buckets of one.+To see what a run would do without moving anything:```bash@@ -53876,7 +56621,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-199) dispatcher (and any external HTTP cron+[economy heartbeat](#sec-204) dispatcher (and any external HTTP cronpointed at `/api/cron/economy-tick`) keeps it — and every other cron — ticking.## Audit, accounting & breach monitoring@@ -53991,26 +56736,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-621) /- [autonomous x402](#sec-114)).+ other engine (see [x402 ring economy](#sec-642) /+ [autonomous x402](#sec-117)).## 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-154) — the autonomous agent-to-agent+- [Circulation engine](#sec-158) — the autonomous agent-to-agentactivity loop the funded engines drive.-- [x402 ring economy](#sec-621) — closed-loop in-house x402 settlement.+- [x402 ring economy](#sec-642) — closed-loop in-house x402 settlement.----<a id="sec-201"></a>+<a id="sec-206"></a>> **Source:** `docs/economy-solver.md` · [↑ table of contents](#table-of-contents)# The economy solver-The [in-game economy reference](#sec-289) publishes **what** the `/play`+The [in-game economy reference](#sec-299) 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.@@ -54236,16 +56981,16 @@ deploy.## Next-- **[The in-game economy](#sec-289)** is the raw reference: every catalog,+- **[The in-game economy](#sec-299)** is the raw reference: every catalog,gate, settlement path and the JSON wire format.-- **[Earn and spend in /play](#sec-503)** walks the loop+- **[Earn and spend in /play](#sec-523)** 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-202"></a>+<a id="sec-207"></a>> **Source:** `docs/editor.md` · [↑ table of contents](#table-of-contents)@@ -54594,7 +57339,7 @@ The full contract lives in [specs/EDITOR_SPEC.md](https://github.com/nirholas/th----<a id="sec-203"></a>+<a id="sec-208"></a>> **Source:** `docs/education-pilot-bucharest.md` · [↑ table of contents](#table-of-contents)@@ -54665,7 +57410,7 @@ Status: exploratory. A contact has offered a local connection to the office of t----<a id="sec-204"></a>+<a id="sec-209"></a>> **Source:** `docs/embedding.md` · [↑ table of contents](#table-of-contents)@@ -55402,10 +58147,10 @@ The platform records anonymous embed impressions (country, referrer hostname) vi## See also-- [Architecture Overview](#sec-108)+- [Architecture Overview](#sec-109)- [Agent System Overview](#sec-065)-- [Web Component reference](#sec-578) — full attribute list-- [Widgets](#sec-581) — Widget Studio and widget types+- [Web Component reference](#sec-599) — full attribute list+- [Widgets](#sec-602) — 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@@ -55420,7 +58165,7 @@ three.ws examples repo, so it is installed, run, and link-checked before every r----<a id="sec-205"></a>+<a id="sec-210"></a>> **Source:** `docs/embody.md` · [↑ table of contents](#table-of-contents)@@ -55523,14 +58268,14 @@ Embody is a thin, honest wire over pieces that already exist — no new pipeline## Related-- [Live embodiment](#sec-315) — the 3D Studio tools that persist and drive a body in chat.-- [x402 Paid Endpoints](#sec-619) — the full paid catalog and pricing.-- [x402 Buyer Client](#sec-616) — how to settle a 402 challenge from code.-- [Avatar creation](#sec-118) — generate a rigged avatar in the web UI.+- [Live embodiment](#sec-326) — the 3D Studio tools that persist and drive a body in chat.+- [x402 Paid Endpoints](#sec-640) — the full paid catalog and pricing.+- [x402 Buyer Client](#sec-637) — how to settle a 402 challenge from code.+- [Avatar creation](#sec-121) — generate a rigged avatar in the web UI.----<a id="sec-206"></a>+<a id="sec-211"></a>> **Source:** `docs/erc8004.md` · [↑ table of contents](#table-of-contents)@@ -56237,7 +58982,7 @@ The same MAINNET addresses apply to all 15 mainnets. The same TESTNET addresses----<a id="sec-207"></a>+<a id="sec-212"></a>> **Source:** `docs/erc8004/validation-attestation.md` · [↑ table of contents](#table-of-contents)@@ -56399,7 +59144,7 @@ reported the reverts as "no attestation yet".----<a id="sec-208"></a>+<a id="sec-213"></a>> **Source:** `docs/event-readiness/01-play-first-impression.md` · [↑ table of contents](#table-of-contents)@@ -56443,7 +59188,7 @@ What you changed (files + one line each), what you verified in-browser, anything----<a id="sec-209"></a>+<a id="sec-214"></a>> **Source:** `docs/event-readiness/02-play-mobile.md` · [↑ table of contents](#table-of-contents)@@ -56479,7 +59224,7 @@ Root cause of any crash found (with the harness evidence), fixes applied, remain----<a id="sec-210"></a>+<a id="sec-215"></a>> **Source:** `docs/event-readiness/03-play-performance.md` · [↑ table of contents](#table-of-contents)@@ -56521,7 +59266,7 @@ Numbers table (before/after), each fix in one line, anything intentionally skipp----<a id="sec-211"></a>+<a id="sec-216"></a>> **Source:** `docs/event-readiness/04-play-multiplayer-net.md` · [↑ table of contents](#table-of-contents)@@ -56561,7 +59306,7 @@ Each failure mode tested and its result (pass / fixed / cannot-fix-with-reason).----<a id="sec-212"></a>+<a id="sec-217"></a>> **Source:** `docs/event-readiness/05-play-economy-loops.md` · [↑ table of contents](#table-of-contents)@@ -56602,7 +59347,7 @@ Loop-by-loop pass/fixed table, every price mismatch found and which side you cor----<a id="sec-213"></a>+<a id="sec-218"></a>> **Source:** `docs/event-readiness/06-play-auth-errors.md` · [↑ table of contents](#table-of-contents)@@ -56638,7 +59383,7 @@ A failure-mode table: scenario, what happened before, what happens now. Call out----<a id="sec-214"></a>+<a id="sec-219"></a>> **Source:** `docs/event-readiness/07-platform-smoke-sweep.md` · [↑ table of contents](#table-of-contents)@@ -56689,7 +59434,7 @@ Battery results before and after, fixes grouped by page, the manual event-funnel----<a id="sec-215"></a>+<a id="sec-220"></a>> **Source:** `docs/event-readiness/08-api-production-health.md` · [↑ table of contents](#table-of-contents)@@ -56720,7 +59465,7 @@ Solana-first status summary, then the 8 items with their binary states, then log----<a id="sec-216"></a>+<a id="sec-221"></a>> **Source:** `docs/event-readiness/09-accessibility-i18n.md` · [↑ table of contents](#table-of-contents)@@ -56756,7 +59501,7 @@ Per-category pass/fixed list, the keyboard-only session result, locales verified----<a id="sec-217"></a>+<a id="sec-222"></a>> **Source:** `docs/event-readiness/10-event-day-runbook.md` · [↑ table of contents](#table-of-contents)@@ -56794,13 +59539,13 @@ Old/new scaling values, capacity smoke numbers, rollback rehearsal result, and t----<a id="sec-218"></a>+<a id="sec-223"></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-379)). 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-392)). 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@@ -56815,7 +59560,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-232).+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-237).## Verify@@ -56829,7 +59574,7 @@ What shipped (files + one line each), the exact operator commands for event day,----<a id="sec-219"></a>+<a id="sec-224"></a>> **Source:** `docs/event-readiness/12-photo-mode-share.md` · [↑ table of contents](#table-of-contents)@@ -56865,7 +59610,7 @@ Files shipped, a saved sample capture path, what the share flow does per platfor----<a id="sec-220"></a>+<a id="sec-225"></a>> **Source:** `docs/event-readiness/13-event-quests-leaderboard.md` · [↑ table of contents](#table-of-contents)@@ -56901,7 +59646,7 @@ The quest list as players will see it, files shipped, the leaderboard endpoint U----<a id="sec-221"></a>+<a id="sec-226"></a>> **Source:** `docs/event-readiness/14-welcome-concierge.md` · [↑ table of contents](#table-of-contents)@@ -56936,7 +59681,7 @@ Files shipped, the persona prompt location, the tour stops, what the concierge s----<a id="sec-222"></a>+<a id="sec-227"></a>> **Source:** `docs/event-readiness/15-live-hype-feed.md` · [↑ table of contents](#table-of-contents)@@ -56970,7 +59715,7 @@ Files shipped, the threshold logic in two sentences, measured DOM/node behavior----<a id="sec-223"></a>+<a id="sec-228"></a>> **Source:** `docs/event-readiness/16-invite-flow.md` · [↑ table of contents](#table-of-contents)@@ -57004,7 +59749,7 @@ Files shipped, any dependency added (name, weekly downloads, license, why), a re----<a id="sec-224"></a>+<a id="sec-229"></a>> **Source:** `docs/event-readiness/17-plaza-live-show.md` · [↑ table of contents](#table-of-contents)@@ -57041,13 +59786,13 @@ Files shipped, how `stageId` is derived, the join and teardown lifecycle in thre----<a id="sec-225"></a>+<a id="sec-230"></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-159). 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-163). This prompt is now the spec to verify against and extend, not a blank build.## Where the code lives@@ -57079,13 +59824,13 @@ Files shipped, the standings read path (existing or the one endpoint you added),----<a id="sec-226"></a>+<a id="sec-231"></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-377)). 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-390)). 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@@ -57116,7 +59861,7 @@ Files shipped, the size ceiling values and where they are enforced, the rate-lim----<a id="sec-227"></a>+<a id="sec-232"></a>> **Source:** `docs/event-readiness/20-world-chat-scrollback.md` · [↑ table of contents](#table-of-contents)@@ -57153,7 +59898,7 @@ Files shipped, the cap and TTL chosen, the bridge decision and why, join-time pa----<a id="sec-228"></a>+<a id="sec-233"></a>> **Source:** `docs/event-readiness/21-party-system.md` · [↑ table of contents](#table-of-contents)@@ -57189,7 +59934,7 @@ Files shipped, where party state lives and its TTL, the teleport validation rule----<a id="sec-229"></a>+<a id="sec-234"></a>> **Source:** `docs/event-readiness/22-venue-projector-mode.md` · [↑ table of contents](#table-of-contents)@@ -57225,7 +59970,7 @@ Files shipped, the exact URL to put on the venue machine, the spectator join con----<a id="sec-230"></a>+<a id="sec-235"></a>> **Source:** `docs/event-readiness/23-signature-wall.md` · [↑ table of contents](#table-of-contents)@@ -57262,7 +60007,7 @@ Files shipped, the store chosen and why, the overflow design in two sentences, t----<a id="sec-231"></a>+<a id="sec-236"></a>> **Source:** `docs/event-readiness/24-dance-off.md` · [↑ table of contents](#table-of-contents)@@ -57298,7 +60043,7 @@ Files shipped, the round timings chosen, the vote targeting rule, the reward and----<a id="sec-232"></a>+<a id="sec-237"></a>> **Source:** `docs/event-readiness/LIVE-OPS.md` · [↑ table of contents](#table-of-contents)@@ -57311,7 +60056,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-233)):+**Event URL** (the canonical $THREE world, from [README.md](#sec-238)):```https://three.ws/play?coin=FeMbDoX7R1Psc4GEcvJdsbNbZA3bfztcyDCatJVJpump&name=three.ws&symbol=three&image=%2Fapi%2Fimg%3Furl%3Dhttps%253A%252F%252Fipfs.io%252Fipfs%252Fbafybeihe22b5sxr3ihnxt7pregfieyteqvubqhik3j3y4bbx243xlqjw3q%26seed%3DFeMbDoX7R1Psc4GEcvJdsbNbZA3bfztcyDCatJVJpump@@ -57598,7 +60343,7 @@ page.----<a id="sec-233"></a>+<a id="sec-238"></a>> **Source:** `docs/event-readiness/README.md` · [↑ table of contents](#table-of-contents)@@ -57610,40 +60355,40 @@ Suggested order and parallelism (audits):| # | Prompt | Surface | Can run in parallel with ||---|--------|---------|--------------------------|-| 1 | [01-play-first-impression.md](#sec-208) | /play load, intro, onboarding UX | 4, 5, 7, 8 |-| 2 | [02-play-mobile.md](#sec-209) | /play on phones (stability + touch) | 7, 8 |-| 3 | [03-play-performance.md](#sec-210) | /play load weight, FPS, memory | 7, 8 |-| 4 | [04-play-multiplayer-net.md](#sec-211) | WebSocket, reconnects, voice, crowd | 1, 5 |-| 5 | [05-play-economy-loops.md](#sec-212) | Store, bank, wheel, combat, quests, cosmetics | 1, 4 |-| 6 | [06-play-auth-errors.md](#sec-213) | Sign-in, gates, error/empty states, console | after 1 |-| 7 | [07-platform-smoke-sweep.md](#sec-214) | Every page on the live site | 1, 2, 3 |-| 8 | [08-api-production-health.md](#sec-215) | Cloud Run, crons, logs, DB, x402 | 1, 2, 3 |-| 9 | [09-accessibility-i18n.md](#sec-216) | Keyboard, ARIA, contrast, translations | after 1 |-| 10 | [10-event-day-runbook.md](#sec-217) | Pre-scale, monitoring loop, rollback | last, after all fixes deploy |+| 1 | [01-play-first-impression.md](#sec-213) | /play load, intro, onboarding UX | 4, 5, 7, 8 |+| 2 | [02-play-mobile.md](#sec-214) | /play on phones (stability + touch) | 7, 8 |+| 3 | [03-play-performance.md](#sec-215) | /play load weight, FPS, memory | 7, 8 |+| 4 | [04-play-multiplayer-net.md](#sec-216) | WebSocket, reconnects, voice, crowd | 1, 5 |+| 5 | [05-play-economy-loops.md](#sec-217) | Store, bank, wheel, combat, quests, cosmetics | 1, 4 |+| 6 | [06-play-auth-errors.md](#sec-218) | Sign-in, gates, error/empty states, console | after 1 |+| 7 | [07-platform-smoke-sweep.md](#sec-219) | Every page on the live site | 1, 2, 3 |+| 8 | [08-api-production-health.md](#sec-220) | Cloud Run, crons, logs, DB, x402 | 1, 2, 3 |+| 9 | [09-accessibility-i18n.md](#sec-221) | Keyboard, ARIA, contrast, translations | after 1 |+| 10 | [10-event-day-runbook.md](#sec-222) | 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-218) | Operator broadcast, go-live moment, live event config | nothing |-| 12 | [12-photo-mode-share.md](#sec-219) | Photo mode with branded one-tap share | nothing |-| 13 | [13-event-quests-leaderboard.md](#sec-220) | Time-boxed quest line + live leaderboard + cosmetic reward | nothing (better with 12) |-| 14 | [14-welcome-concierge.md](#sec-221) | Greeter NPC, guided tour, event-aware opening line | nothing |-| 15 | [15-live-hype-feed.md](#sec-222) | Activity ticker + market hype moments | nothing (better with 13) |-| 16 | [16-invite-flow.md](#sec-223) | Invite sheet, QR, OG card truth, arrival continuity | nothing (better with 14) |+| 11 | [11-event-live-ops.md](#sec-223) | Operator broadcast, go-live moment, live event config | nothing |+| 12 | [12-photo-mode-share.md](#sec-224) | Photo mode with branded one-tap share | nothing |+| 13 | [13-event-quests-leaderboard.md](#sec-225) | Time-boxed quest line + live leaderboard + cosmetic reward | nothing (better with 12) |+| 14 | [14-welcome-concierge.md](#sec-226) | Greeter NPC, guided tour, event-aware opening line | nothing |+| 15 | [15-live-hype-feed.md](#sec-227) | Activity ticker + market hype moments | nothing (better with 13) |+| 16 | [16-invite-flow.md](#sec-228) | 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-224) | Live hosted show on a plaza stage, with $THREE tips | StageRoom + ShowDirector (built, unreachable from /play) |-| 18 | [18-coin-wars-portal.md](#sec-225) | In-world Coin Wars portal: standings, queue, spectate | ClashRoom + war standings (built, arena-page only) |-| 19 | [19-forge-props-live.md](#sec-226) | Text-to-3D prop generation inside build mode | Forge lane + the networked prop pipeline |-| 20 | [20-world-chat-scrollback.md](#sec-227) | Chat scrollback for late joiners + community-feed bridge | the WalkRoom relay + api/community/messages |-| 21 | [21-party-system.md](#sec-228) | Parties: form, see, reach, and talk to your crew | friends/presence stack; pairs with 13, 16 |-| 22 | [22-venue-projector-mode.md](#sec-229) | Broadcast spectator view for the venue big screen | camera rig + event.json; pairs with 15, 16, 17 |-| 23 | [23-signature-wall.md](#sec-230) | Persistent signature wall, the event's artifact | world-persist patterns + name safety |-| 24 | [24-dance-off.md](#sec-231) | 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-229) | Live hosted show on a plaza stage, with $THREE tips | StageRoom + ShowDirector (built, unreachable from /play) |+| 18 | [18-coin-wars-portal.md](#sec-230) | In-world Coin Wars portal: standings, queue, spectate | ClashRoom + war standings (built, arena-page only) |+| 19 | [19-forge-props-live.md](#sec-231) | Text-to-3D prop generation inside build mode | Forge lane + the networked prop pipeline |+| 20 | [20-world-chat-scrollback.md](#sec-232) | Chat scrollback for late joiners + community-feed bridge | the WalkRoom relay + api/community/messages |+| 21 | [21-party-system.md](#sec-233) | Parties: form, see, reach, and talk to your crew | friends/presence stack; pairs with 13, 16 |+| 22 | [22-venue-projector-mode.md](#sec-234) | Broadcast spectator view for the venue big screen | camera rig + event.json; pairs with 15, 16, 17 |+| 23 | [23-signature-wall.md](#sec-235) | Persistent signature wall, the event's artifact | world-persist patterns + name safety |+| 24 | [24-dance-off.md](#sec-236) | 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:@@ -57655,7 +60400,7 @@ Rules that apply to every prompt in this pack:----<a id="sec-234"></a>+<a id="sec-239"></a>> **Source:** `docs/event-souvenirs.md` · [↑ table of contents](#table-of-contents)@@ -57676,7 +60421,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 granted at the-[`$THREE` First Holders Meetup](#sec-379). That window has closed, so+[`$THREE` First Holders Meetup](#sec-392). That window has closed, sothe laurel is now exactly what this page promises: owned only by the players whowere in the world that day, and never granted again.@@ -57906,15 +60651,15 @@ machine prefer the two above, which cover the same ground between them.## Related-- **[Live events in /play](#sec-379)** covers the rest of what that+- **[Live events in /play](#sec-392)** covers the rest of what thatconfig file drives: the countdown, the agenda drawer, the fireworks.-- **[The in-game economy](#sec-289)** covers the two currencies and+- **[The in-game economy](#sec-299)** covers the two currencies andthe `$THREE` boutique the souvenir deliberately stays out of.-- **[Coin communities](#sec-158)** covers the worlds the events happen in.+- **[Coin communities](#sec-162)** covers the worlds the events happen in.----<a id="sec-235"></a>+<a id="sec-240"></a>> **Source:** `docs/examples.md` · [↑ table of contents](#table-of-contents)@@ -58725,7 +61470,7 @@ Run any command from the repo root after `npm install`. The web component demos----<a id="sec-236"></a>+<a id="sec-241"></a>> **Source:** `docs/exit-lab.md` · [↑ table of contents](#table-of-contents)@@ -58747,7 +61492,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-477)). The two answer+documented in [trading-experiment.md](#sec-497)). The two answerdifferent questions and neither replaces the other.| | Backtester (`/api/sniper/backtest`) | Exit Lab (`/exit-lab`) |@@ -58954,17 +61699,37 @@ to the nearest legal one rather than throwing.---+## When the corpus is not there++Every section of the console is derived from `/api/sniper/exit-lab`, so the page+has three honest states beside the populated one and reaches all of them from+real conditions rather than a flag:++| Condition | What the page does |+|---|---|+| The request is in flight | The verdict card shows a skeleton of the layout that is coming, the results and trades regions carry `aria-busy`, and the search says what it is waiting for. |+| The request fails, or the handler answers `503 corpus_unavailable` | The results card states the reason the endpoint gave and offers **Try again**, which re-runs the same fetch. The attribution, per-trade and search sections say the corpus did not load rather than sitting empty under a heading. |+| The corpus loads with no replayable position | The page says so and points at the [agent arena](https://three.ws/play/arena) and the [sniper docs](https://three.ws/docs/agent-sniper), which are the two places the first trade becomes visible. |++**Run the search** is disabled until a corpus with at least one replayable trade+is loaded, and its `title` says which of the two reasons applies. The search+replays the corpus in the browser, so with no corpus there is nothing for it to+do, and a live button that answers a click with silence is worse than a disabled+one that explains itself.++---+## Related- [Agent Sniper](#sec-062), the worker whose positions this replays-- [Autonomous Trading hub](#sec-478), the front door to every trading surface-- [Trading experiment](#sec-477), the policy this fleet runs and why-- [Read the trading fleet](#sec-529), how to interpret fleet vitals-- Tutorial: [Find a better exit policy](#sec-508)+- [Autonomous Trading hub](#sec-498), the front door to every trading surface+- [Trading experiment](#sec-497), the policy this fleet runs and why+- [Read the trading fleet](#sec-549), how to interpret fleet vitals+- Tutorial: [Find a better exit policy](#sec-528)----<a id="sec-237"></a>+<a id="sec-242"></a>> **Source:** `docs/fact-check.md` · [↑ table of contents](#table-of-contents)@@ -59001,7 +61766,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-426) and [3D provenance anchoring](#sec-388), 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-442) and [3D provenance anchoring](#sec-402), 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.@@ -59046,7 +61811,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-624).+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-645).## Running the benchmark@@ -59110,14 +61875,155 @@ Two guards keep a bad run from becoming a published number:## Related-- [x402: paid agent skills](#sec-624): the payment rail the $0.10 lane rides-- [API reference: Fact Check API](#sec-104): the endpoint's full request and response reference-- [SAS credentialed attestations](#sec-426) and [3D provenance](#sec-388): the platform's on-chain attestation primitives (distinct from this content-hash attestation)+- [x402: paid agent skills](#sec-645): the payment rail the $0.10 lane rides+- [API reference: Fact Check API](#sec-105): the endpoint's full request and response reference+- [SAS credentialed attestations](#sec-442) and [3D provenance](#sec-402): 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-238"></a>+<a id="sec-243"></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-468). 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)++API: `/api/pump/fade` (live coin board, per-coin read, reverse-indicator wallet board, calibration).++## Why it exists++Most pump.fun launches die quietly, and the wallets that buy them are not random. A large group of addresses has been observed buying dozens of coins with a known outcome and has never held one that graduated or tripled. They are the exit liquidity every dead launch is built on, and they cluster: when several of them show up on the same fresh coin, that coin is overwhelmingly a coin nobody else wants.++That is a signal you cannot read off a chart in the first minutes of a launch, and it is the honest mirror of the smart-money read: instead of asking whether proven winners are here, it asks whether proven losers are all that is here.++**This is not a short.** Nothing on a bonding curve can be sold before it is bought, so the only tradeable form of a fade is not buying. Fade Radar never emits a trade, never inverts a position, and nothing on the page signs anything.++## The definition++A **reverse indicator** is a wallet where both hold:++- the graph has watched it buy at least **5** coins whose outcome is already known (`trades_seen >= 5`), and+- **zero** of those coins won (`winners = 0`).++A **win** is a coin that graduated to an AMM, or peaked at 3x or better on market cap. Both come from `pump_coin_outcomes`, the same labelled ground truth the Coin Intelligence engine learns from. A wallet below the 5-coin bar is simply new, not bad, and never appears here.++Reverse-indicator status is read live from `smart_wallet_reputation`, the wallet graph that `api/cron/smart-money-graph` maintains, so the fade side is exactly as fresh as the smart side and needs no job of its own.++## The score++For one coin, over its observed non-creator buyers (`pump_coin_wallets`):++```+buyerShare = reverse-indicator buyers / observed buyers+volumeShare = reverse-indicator buy lamports / observed buy lamports+fade_score = round(100 * (0.6 * buyerShare + 0.4 * volumeShare))+```++Buyers and volume are both counted because they fail differently: ten dust wallets are a crowd with no conviction, one large reverse-indicator buy is conviction with no crowd, and a coin wants to be clean of both. When no buy volume has been recorded yet, the buyer share carries the whole score rather than being halved by a zero that means nothing.++The verdict follows the buyer share:++| Verdict | Condition |+| --- | --- |+| `unknown` | fewer than 5 observed buyers, too thin to read |+| `clear` | no reverse indicator among the buyers |+| `caution` | some reverse-indicator presence, under 25 percent of buyers |+| `avoid` | 25 percent of buyers or more |++The creator is excluded from every count: a dev holding its own supply is a different signal, already carried by dev-sold and concentration, and would otherwise count once in every coin it launched.++## The calibration, and why it is honest++A wallet's record is built from coin outcomes, so scoring the same coins that record was built on would grade the signal on its own answer sheet. `getFadeCalibration` avoids that with a time split:++1. Take every labelled coin and split the history in half by label time.+2. Rebuild the reverse-indicator cohort using **only** coins labelled in the earlier half.+3. Measure how often coins labelled in the **later** half went on to win, by band.++The later-half coins could not have contributed to the cohort that grades them, so the result is out of sample. On the history as of 2026-09-09, over 26,626 labelled coins:++| Band | Coins | Went on to win |+| --- | --- | --- |+| `clear` | 22,473 | 22.1 percent |+| `caution` | 3,541 | 15.7 percent |+| `avoid` | 612 | 1.8 percent |++A coin in the `avoid` band won at roughly one twelfth the baseline rate. The numbers are recomputed from live history at most every 12 hours and cached in `app_settings` under `fade_radar_calibration`, so the page always shows a measurement rather than a claim.++This is a probabilistic read on a hostile market. It is not a prediction and not advice: a `clear` coin can still go to zero.++## API++```bash+# Live board: coins launched in the last 6 hours with proven-losing money in them+curl 'https://three.ws/api/pump/fade?hours=6&limit=40'++# One coin, with the reverse-indicator wallets inside it+curl 'https://three.ws/api/pump/fade?mint=<mint>'++# The reverse-indicator wallets themselves, worst record first+curl 'https://three.ws/api/pump/fade?wallets=1&min_judged=8&active_hours=24'++# The measured, out-of-sample odds behind the bands+curl 'https://three.ws/api/pump/fade?calibration=1'+```++A coin read returns:++```json+{+ "mint": "<mint>",+ "score": 86,+ "verdict": "avoid",+ "buyers": 5,+ "ri_buyers": 4,+ "ri_buyer_share": 0.8,+ "ri_volume_share": 0.959,+ "confidence": "medium",+ "notable": [{ "wallet": "<address>", "judged_buys": 41, "winners": 0, "losers": 41 }],+ "summary": "Heavy reverse-indicator presence: 4 of 5 observed buyers (80%) and 96% of the buy volume come from wallets with no winner on record. Fade score 86.",+ "computed": true+}+```++A coin the engine has not observed resolves `200` with `computed: false` rather than a 404, matching the intel and smart-money detail endpoints, so a detail page can always render. Every read degrades the same way: a missing database or a failed query returns the well-formed zero-data shape instead of throwing.++## Using it from an agent++```js+import { getFadeForMint } from '../api/_lib/fade-radar.js';++const fade = await getFadeForMint(mint);+if (fade.computed && fade.verdict === 'avoid') {+ // Skip. Coins in this band won 1.8% of the time against a 22% baseline.+ return { decision: 'PASS', why: fade.summary };+}+```++The module is a pure read layer with no side effects, and `fadeScore` / `fadeVerdict` / `fadeSummary` are exported as pure functions so a caller can score a buy side it already has in hand without a database round trip.++## Where it fits++- [Smart Money Radar](#sec-468): 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-499): the engine that records every launch, labels its outcome, and produces the ground truth both radars stand on.+- [Coin Radar](#sec-430): what launched in the last 90 seconds, where a fade read is the fastest reason to skip one.++## Files++| Path | What it holds |+| --- | --- |+| `api/_lib/fade-radar.js` | The read layer: scoring, the coin board, the wallet board, the calibration |+| `api/pump/fade.js` | The public HTTP surface |+| `pages/fade.html`, `src/fade-radar.js` | The page |+| `tests/fade-radar.test.js` | The scoring contract |++---++<a id="sec-244"></a>> **Source:** `docs/farcaster-memory-seeding.md` · [↑ table of contents](#table-of-contents)@@ -59136,7 +62042,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-321), [`@three-ws/agent-memory`](https://www.npmjs.com/package/@three-ws/agent-memory)+- **Related**: [Memory system](#sec-332), [`@three-ws/agent-memory`](https://www.npmjs.com/package/@three-ws/agent-memory)---@@ -59373,7 +62279,7 @@ only its own rows and a revoke deletes exactly what was granted.----<a id="sec-239"></a>+<a id="sec-245"></a>> **Source:** `docs/feedback.md` · [↑ table of contents](#table-of-contents)@@ -59422,7 +62328,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-582) at module load, before the+ starts [`@three-ws/witness`](#sec-603) 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@@ -59462,7 +62368,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-582).+privacy rules: [Witness](#sec-603).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@@ -59520,7 +62426,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-582).+`trace` is optional and machine-written by [`@three-ws/witness`](#sec-603).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.@@ -59546,7 +62452,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-582).+the replay somewhere other than production. See [Witness](#sec-603).## What this deliberately does not do@@ -59565,12 +62471,12 @@ reproduces the failure, never the raw report, and the output is a pull request.## Related-- [Notifications](#sec-342): the same companion delivering messages the other way.+- [Notifications](#sec-353): the same companion delivering messages the other way.- [`STRUCTURE.md`](../STRUCTURE.md): where every surface lives.----<a id="sec-240"></a>+<a id="sec-246"></a>> **Source:** `docs/financial-controls.md` · [↑ table of contents](#table-of-contents)@@ -59583,7 +62489,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-335) (who receives what) and the+It is a companion to the [money map](#sec-346) (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.@@ -59611,6 +62517,7 @@ and whether it is reconciled against the chain.| Cosmetic sales + creator split | `cosmetic_sales` (`price_usdc_atomics, creator_cut_atomics, payout_tx, payout_status`, `UNIQUE(account,cosmetic_id)`) | ✅ | sale once; payout fields mutable | `UNIQUE(account,cosmetic_id)` | ❌ || Marketplace skill sale + fee | `skill_purchases` (`tx_signature UNIQUE`, `platform_fee_amount`) + `agent_revenue_events` (`gross/fee/net`) | ✅ | revenue events ✅ | `tx_signature UNIQUE` | ❌ || Labor escrow (fund/settle/payout/refund) | `agent_bounties`, `agent_jobs` (`settle_key UNIQUE, settlement_sig, royalty_sig, refund_sig`) + custody ledger | ✅ | mutable status; single-shot | `settle_key UNIQUE` + atomic claim | ❌ |+| $THREE buyback | `three_buyback_runs` (`usdc_spent_atomics, three_bought_atomics, buy_signature, sweep_signature`) | ✅ | ✅ (one row/run) | ❌ **no unique key** | ❌ || Coin buyback / distribute | `pump_buyback_runs`, `pump_distribute_runs` (`tx_signature, status`) | ✅ | mutable status | ❌ **no unique key** | ❌ || Withdrawals | `agent_withdrawals` (`amount, currency_mint, chain, to_address, tx_signature, status`) | ✅ | mutable status | ⚠️ claim-CAS only; **no on-chain-send idempotency** | ❌ || Treasury top-up / economy master | `economy_master_ledger` (`event, target_pubkey, lamports, signature, resulting balance, sol_usd, usd_value, prev_hash, entry_hash`): every transfer/failed/blocked plus a per-sweep heartbeat row | ✅ | ✅ SHA-256 hash-chained (tamper-evident) | ❌ no unique key on sig | ✅ **yes** (`economy-reconcile`) |@@ -59625,7 +62532,7 @@ and whether it is reconciled against the chain.there is **no DB-level enforcement** (no trigger, no revoked grant) — soimmutability is not guaranteed against a bug, a migration, or a compromisedcredential. This applies to *every* table above, including those designed as-immutable (`credit_ledger`, `agent_revenue_events`).+immutable (`credit_ledger`, `agent_revenue_events`, `three_buyback_runs`).**Reference-grade flows** (idempotent + tx-sig + append-only): **credit deposits**,**marketplace skill purchases**, **labor settlement**. New money flows should copy@@ -59661,7 +62568,7 @@ Books automatically verified against the chain:**NOT reconciled against the chain:** `x402_audit_log` (the main revenue ledger),`club_payouts`, `cosmetic_sales`, `agent_jobs`, `agent_withdrawals`,-and vanity payouts.+`three_buyback_runs`, and vanity payouts.Two blind spots default a record to `reconciled=true` without verifying it:**EVM/Base** settlements (`skipped_non_solana`) and **RPC failures** (`unknown`).@@ -59806,7 +62713,7 @@ Ranked by accounting/regulatory risk. Each is a tracked remediation item.10. **Buyback/distribute run tables and `x402_autonomous_log` lack idempotency keys.**11. **No DB-level immutability** on any ledger — add append-only enforcement(revoke UPDATE/DELETE, or triggers) to the truly-append-only tables- (`x402_audit_log`, `credit_ledger`, `agent_revenue_events`).+ (`x402_audit_log`, `credit_ledger`, `agent_revenue_events`, `three_buyback_runs`).12. **`audit_log` hard-deleted at 365 days** — make the window configurable andarchive to cold storage before delete.13. **Reconciliation blind spots** (EVM/RPC-miss default to reconciled); **no USDC@@ -59858,19 +62765,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-335).+ added to this register and the [money map](#sec-346).---## Related-- [Money map](#sec-335) — who receives each payment.-- [x402 endpoints](#sec-619) — the paid endpoint catalog.+- [Money map](#sec-346) — who receives each payment.+- [x402 endpoints](#sec-640) — the paid endpoint catalog.- [Solana signers runbook](../api/_lib/solana-signers.js) — the wallets + funding.----<a id="sec-241"></a>+<a id="sec-247"></a>> **Source:** `docs/first-contribution.md` · [↑ table of contents](#table-of-contents)@@ -59973,7 +62880,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-423).+- **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-438).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:@@ -60051,7 +62958,7 @@ Then open the PR on GitHub. In the description say what changed, what you tested## 5. What happens next-See [Triage](#sec-480) 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-500) 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).---@@ -60064,7 +62971,7 @@ See [Triage](#sec-480) for the full flow and response targets. In short: a maint----<a id="sec-242"></a>+<a id="sec-248"></a>> **Source:** `docs/forge-background-generation.md` · [↑ table of contents](#table-of-contents)@@ -60195,7 +63102,7 @@ and the notification preference model in----<a id="sec-243"></a>+<a id="sec-249"></a>> **Source:** `docs/forge-off.md` · [↑ table of contents](#table-of-contents)@@ -60322,7 +63229,7 @@ Backfill a past week's winner (owner): `GET /api/cron/forge-off-crown?week=YYYY-----<a id="sec-244"></a>+<a id="sec-250"></a>> **Source:** `docs/forge-pipeline.md` · [↑ table of contents](#table-of-contents)@@ -60330,7 +63237,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-245). If you want the plain-language version, read [How the Forge works](#sec-272). This document is for people changing the pipeline.+If you want the product-level overview, read [Forge](#sec-251). If you want the plain-language version, read [How the Forge works](#sec-281). This document is for people changing the pipeline.## Bird's-eye view@@ -60469,7 +63376,7 @@ Async jobs get an opaque HMAC-signed token (`f1.<payload>.<sig>`, `api/_lib/forg### Poll-`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. 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-242)).+`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. 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-248)).**Poll-time failover** (`api/_lib/forge-failover.js`) closes the nastier gap: a self-host worker can accept a task and fail it minutes later, in a poll handled by a different instance that no longer holds the request. On a failed poll the module recovers the original inputs (prompt plus reference image) from the creation row, resubmits to the next configured lane, and binds old handle to new handle in Redis (2 hour TTL). The client keeps polling the same job id and simply sees `status: running` with a new `backend`. Hops are capped by `MAX_FAILOVER_HOPS = 3` (one primary plus up to three backups). The redispatch order is `trellis_selfhost`, `hunyuan3d`, `trellis`: HuggingFace is excluded because its provider blocks through the whole generation (cannot be ridden from a poll), and NVIDIA is excluded because poll-time redispatch always reconstructs from a stored reference image, which NIM rejects. Both failover paths (this attended one and the unattended finalizer sweep) link the failed attempt to its successor row (`forge_creations.superseded_by`, migration `20260814200000_forge_failover_supersede.sql`), so the outcome ledger, the forge health sensor and `npm run forge:errors` count a recovered attempt as a recovery, not a loss.@@ -60602,17 +63509,17 @@ Fast diagnostics: `forge_creations` carries per-generation backend, status, erro## Related-- [Forge](#sec-245), the product-level doc for the /forge surface.-- [How the Forge works](#sec-272), the plain-language explainer.+- [Forge](#sec-251), the product-level doc for the /forge surface.+- [How the Forge works](#sec-281), 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-122), the selfie-to-avatar reconstruction flow.-- [Background generation](#sec-242), job resume and gallery persistence.+- [Avatar pipeline](#sec-125), the selfie-to-avatar reconstruction flow.+- [Background generation](#sec-248), job resume and gallery persistence.- `workers/README.md`, the worker-by-worker operational reference.----<a id="sec-245"></a>+<a id="sec-251"></a>> **Source:** `docs/forge.md` · [↑ table of contents](#table-of-contents)@@ -60668,6 +63575,49 @@ Health is real. The UI fetches `/api/forge?health=1` after load and disables anyGeneration is a job. `POST /api/forge` returns a `job_id`; the client polls `GET /api/forge?job=<id>` until the status is `done` or `failed`. The lanes that complete inline within one request (free NVIDIA NIM, HuggingFace Spaces, BYOK-sync) can instead answer the POST directly with `status:'done'`, the `glb_url`, and a null `job_id`, and they retry once automatically on a failed result. Because the in-flight job id is written to `localStorage`, closing the tab or navigating away does not lose the generation: returning to Forge within a 30-minute window resumes polling the same job. Finished models for your browser are surfaced from a gallery on load, and a share link always wins over a resume.+### Watching a generation happen++`POST /api/forge` is one long request, and most of the wait lives inside it: the+art-director pass rewrites your prompt, a text-to-image model paints the+photoreal reference view the mesh is reconstructed from, and the fusing lane+paints turnaround views around it. All of that finishes before the response can+carry a job id, so a page with nothing but the response to go on could only say+"art-directing your prompt" for the whole window and then reveal the reference+image at the very end, when it had in fact existed for half a minute.++So the generation records a crumb the instant each of those milestones genuinely+finishes, and the page reads them while its own POST is still open:++```bash+# 1. Mint any url-safe id, 16 to 64 characters, and send it with the request.+TRACE=$(uuidgen | tr -d '-')+curl -sS -X POST https://three.ws/api/forge \+ -H 'content-type: application/json' \+ -d "{\"prompt\":\"a brass sundial on a stone base\",\"progress_id\":\"$TRACE\"}" &++# 2. While that runs, read what the pipeline has already finished.+curl -sS "https://three.ws/api/forge?progress=$TRACE"+# → {"progress":[+# {"stage":"directed","at":1757345001000,"directed_prompt":"a brass sundial on a weathered limestone base, aged patina, studio softbox lighting, plain seamless backdrop"},+# {"stage":"reference","at":1757345013000,"preview_image_url":"https://…/ref.jpg","text_to_image_model":"vertex-gemini-2.5-flash-image"},+# {"stage":"views","at":1757345024000,"view_count":3},+# {"stage":"submitting","at":1757345027000}+# ]}+```++The four stages are `directed` (the art-director pass is over, and+`directed_prompt` is null when it left your words alone), `reference` (the view+the mesh is reconstructed from now exists), `views` (the turnaround views the+fusing lane adds, only when the lane painted any), and `submitting` (every image+is stored and the job is going to a GPU). Nothing here is predicted: a crumb is+written after the work it names returned, never on a timer.++The channel is optional in every direction. Omit `progress_id` and the request+behaves exactly as it always has. Poll a trace with no crumbs yet and you get an+empty list, which is indistinguishable from "not there yet" on purpose. Crumbs+expire after five minutes, and they only ever hold what the response itself+carries moments later, so a trace id grants no access to anything.+### Comparing two engines on one promptThe engine grid is only useful if you can see what choosing an engine actually@@ -60841,6 +63791,7 @@ console.log(job.glb_url); // downloadable, textured GLB- **Loading**: a real elapsed counter driven by the catalog ETA for the resolved path, tier, and engine. Cold self-host GPU workers add an honest spin-up estimate rather than a stalled bar.- **Down lane**: disabled engine button with the real upstream reason; routing skips it via the circuit-breaker cooldown.+- **Storage outage**: when object storage rejects us, no engine can finish a generation (every lane has to park a reference image or a finished mesh), so switching engines is not offered. The page says plainly that the fault is ours, that nothing was charged, and points at what still works: every model you already forged is served from the public CDN and still opens, downloads and refines. Retry re-enables itself on a live countdown, because a repaired credential recovers without a redeploy.- **Unconfigured backend**: a clean `backend_unconfigured` error, never a mock.- **Resume**: an interrupted job is pollable again for 30 minutes from the same browser.- **Every result** reports the path, tier, and backend that produced it, so you always know which engine ran.@@ -60862,16 +63813,16 @@ dashboard at [/quality-bench](https://three.ws/quality-bench) (internal).## Related-- [The Forge pipeline](#sec-244) is the architecture deep dive: the engine grid, routing, failover, job lifecycle, workers, and payments, end to end. [How the Forge works](#sec-272) is the same story in plain language.-- [Image to 3D](#sec-288) is the photo lane opened directly at [/image-to-3d](https://three.ws/image-to-3d).+- [The Forge pipeline](#sec-250) is the architecture deep dive: the engine grid, routing, failover, job lifecycle, workers, and payments, end to end. [How the Forge works](#sec-281) is the same story in plain language.+- [Image to 3D](#sec-298) 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-194) forges a whole scene of Forge objects into one explorable world.+- [Diorama](#sec-199) 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-246"></a>+<a id="sec-252"></a>> **Source:** `docs/forged.md` · [↑ table of contents](#table-of-contents)@@ -60879,7 +63830,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-624). Nothing on the page is curated or seeded by+[x402 payment protocol](#sec-645). 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@@ -60912,7 +63863,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-114), the+The buyer is the platform's [autonomous x402 loop](#sec-117), 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))@@ -60930,7 +63881,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-621), and the loop's daily spend cap+ [x402 ring economy](#sec-642), and the loop's daily spend capapplies to these calls like every other.3. **Scores diversity.** The prompt is embedded (a configured provider whenavailable, a deterministic local feature-hash space otherwise) and scored@@ -61002,21 +63953,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-104).+The endpoint is also listed in the [API reference](#sec-105).## Related-- [Autonomous x402 loop](#sec-114): the engine that buys these+- [Autonomous x402 loop](#sec-117): the engine that buys theseassets, its spend caps, and where every call is logged.-- [x402 ring economy](#sec-621): the wider self-paid endpoint+- [x402 ring economy](#sec-642): the wider self-paid endpointeconomy the seeder wallet participates in.-- [How the Forge works](#sec-272): the generation pipeline the+- [How the Forge works](#sec-281): the generation pipeline theagents are paying for.-- [x402 on three.ws](#sec-624): the payment protocol itself.+- [x402 on three.ws](#sec-645): the payment protocol itself.----<a id="sec-247"></a>+<a id="sec-253"></a>> **Source:** `docs/fork-trade.md` · [↑ table of contents](#table-of-contents)@@ -61037,10 +63988,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-415) scores every launch in its first 90 seconds, the-[Smart Money Radar](#sec-450) shows which proven wallets are accumulating-right now, [Ghost-copy](#sec-255) replays a leader's real record against-your budget, and the [Live Trade Feed](#sec-479) opens the full+[Coin Radar](#sec-430) scores every launch in its first 90 seconds, the+[Smart Money Radar](#sec-468) shows which proven wallets are accumulating+right now, [Ghost-copy](#sec-261) replays a leader's real record against+your budget, and the [Live Trade Feed](#sec-499) 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.@@ -61153,23 +64104,23 @@ which the /play HUD does not need).## Related-- [Ghost-copy](#sec-255): find out what a leader would have done to your+- [Ghost-copy](#sec-261): find out what a leader would have done to yourbudget before you fork anything.-- [Copy trading](#sec-181): when one fork at a time is not enough and you+- [Copy trading](#sec-185): when one fork at a time is not enough and youwant a leader mirrored automatically under hard spend limits.-- [The trading surfaces](#sec-479): where every fork button lives.-- [Smart Money Radar](#sec-450): the proven-wallet ledger behind the coin+- [The trading surfaces](#sec-499): where every fork button lives.+- [Smart Money Radar](#sec-468): the proven-wallet ledger behind the coinpedigree the panel shows you before you sign.----<a id="sec-248"></a>+<a id="sec-254"></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-249).+Research catalog, 2026-08-05. Companion to [free-llm-providers.md](#sec-255).**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.@@ -61318,7 +64269,7 @@ Adoption rules that still apply: these are all free tiers, so no owner approval----<a id="sec-249"></a>+<a id="sec-255"></a>> **Source:** `docs/free-llm-providers.md` · [↑ table of contents](#table-of-contents)@@ -61381,11 +64332,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-347) for the full NVIDIA NIM surface map.+Related: [nvidia-models.md](#sec-359) for the full NVIDIA NIM surface map.----<a id="sec-250"></a>+<a id="sec-256"></a>> **Source:** `docs/fundraising/nvidia-inception-capital-connect.md` · [↑ table of contents](#table-of-contents)@@ -61500,7 +64451,7 @@ Source: [`three-ws-inception-deck.html`](fundraising/three-ws-inception-deck.htm----<a id="sec-251"></a>+<a id="sec-257"></a>> **Source:** `docs/galaxy.md` · [↑ table of contents](#table-of-contents)@@ -61582,13 +64533,13 @@ curl -X POST 'https://three.ws/api/galaxy' \## Related-- [IBM Granite suite](#sec-287): the full set of watsonx-powered features on three.ws, including the Granite embeddings that position this galaxy.+- [IBM Granite suite](#sec-297): the full set of watsonx-powered features on three.ws, including the Granite embeddings that position this galaxy.- [Agent system](#sec-065) and [Agent reputation](#sec-057): 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-252"></a>+<a id="sec-258"></a>> **Source:** `docs/generation-watch.md` · [↑ table of contents](#table-of-contents)@@ -61609,7 +64560,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-150). Fast generations+[three.ws 3D Studio custom GPT](#sec-154). 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:@@ -61644,7 +64595,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-272).+ [How the Forge works](#sec-281).- **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@@ -61690,23 +64641,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-242).+[Background generation and completion notifications](#sec-248).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-272): the pipeline behind the+- [How the Forge works](#sec-281): the pipeline behind thecountdown.-- [Background generation](#sec-242): server-side+- [Background generation](#sec-248): server-sidetracking, resume, and notifications.-- [The 3D Studio GPT](#sec-150): the main surface that hands+- [The 3D Studio GPT](#sec-154): the main surface that handsout watch links.-- [API reference](#sec-104): the full `/api/3d/studio` contract.+- [API reference](#sec-105): the full `/api/3d/studio` contract.----<a id="sec-253"></a>+<a id="sec-259"></a>> **Source:** `docs/genesis.md` · [↑ table of contents](#table-of-contents)@@ -61731,8 +64682,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-063), the [economy](#sec-113),-[breeding](#sec-254), and every embed surface.+into [Agent Studio](#sec-063), the [economy](#sec-116),+[breeding](#sec-260), and every embed surface.## How it works@@ -61753,7 +64704,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-074) and [Custody](#sec-187)),+ the agent (see [Agent Wallets](#sec-074) and [Custody](#sec-191)),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@@ -61766,7 +64717,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-206) identity record for the agent and returns a real tx+ [ERC-8004](#sec-211) 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.@@ -61788,14 +64739,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-063) to- keep authoring, drop it on a site via [Integrations](#sec-291), or breed- it in [Agent Genome](#sec-254).+ keep authoring, drop it on a site via [Integrations](#sec-301), or breed+ it in [Agent Genome](#sec-260).## 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-104) and [Authentication](#sec-112) for+[API reference](#sec-105) and [Authentication](#sec-115) forthe session cookie or bearer token):```bash@@ -61847,16 +64798,16 @@ curl -s -X POST "https://three.ws/api/agents/$AGENT_ID/wallet/provision" \## Related- [Agent Studio](#sec-063): keep authoring the agent Genesis created-- [Agent Genome](#sec-254): breed two agents into an inherited child-- [Avatar Reconstruction](#sec-123): the selfie-to-3D pipeline-- [Agent Wallets](#sec-074) and [Custody](#sec-187): the custodial keys-- [ERC-8004](#sec-206): the on-chain identity record-- [Persona Hub](#sec-373): how personas are synthesized+- [Agent Genome](#sec-260): breed two agents into an inherited child+- [Avatar Reconstruction](#sec-126): the selfie-to-3D pipeline+- [Agent Wallets](#sec-074) and [Custody](#sec-191): the custodial keys+- [ERC-8004](#sec-211): the on-chain identity record+- [Persona Hub](#sec-386): 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-254"></a>+<a id="sec-260"></a>> **Source:** `docs/genome.md` · [↑ table of contents](#table-of-contents)@@ -61899,7 +64850,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-576)).+ [Voice Lab](#sec-596)).- **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.@@ -61946,7 +64897,7 @@ parents and the same seed it always derives the identical child.## ExamplesPreview a pairing (read-only, nothing minted). See-[Authentication](#sec-112) for the token or session cookie:+[Authentication](#sec-115) for the token or session cookie:```bashcurl -s -X POST https://three.ws/api/genome/preview \@@ -62003,16 +64954,16 @@ curl -s "https://three.ws/api/genome/lineage?agentId=<child-uuid>&verify=1"## Related-- [Instant Agent Genesis](#sec-253): mint the parents in under a minute+- [Instant Agent Genesis](#sec-259): mint the parents in under a minute- [Agent Skills](#sec-061): the skill licenses that recombine- [Agent Wallets](#sec-074): the fresh child wallet- [Agent Reputation](#sec-057): how pedigree feeds standing-- [ERC-8004](#sec-206): on-chain identity for bred agents+- [ERC-8004](#sec-211): on-chain identity for bred agents- Pages: [/genome](https://three.ws/genome), [/agent-studio](https://three.ws/agent-studio)----<a id="sec-255"></a>+<a id="sec-261"></a>> **Source:** `docs/ghost-copy.md` · [↑ table of contents](#table-of-contents)@@ -62027,7 +64978,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-247) on a position the leader is still+action on the page is [Fork](#sec-253) 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.@@ -62176,7 +65127,7 @@ 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-181) for that engine.+ [docs/copy-trading.md](#sec-185) for that engine.- A leader's underlying record: `/trader/<agent_id>`, one click from every result.## Source@@ -62191,7 +65142,7 @@ renders the summary without it is misrepresenting the result.----<a id="sec-256"></a>+<a id="sec-262"></a>> **Source:** `docs/github-memory-seeding.md` · [↑ table of contents](#table-of-contents)@@ -62218,7 +65169,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-321), [X memory seeding](#sec-588), [Farcaster memory seeding](#sec-238)+- **Related**: [Memory system](#sec-332), [X memory seeding](#sec-609), [Farcaster memory seeding](#sec-244)---@@ -62517,7 +65468,7 @@ rather than inviting a retry that would only earn a 429.----<a id="sec-257"></a>+<a id="sec-263"></a>> **Source:** `docs/glance.md` · [↑ table of contents](#table-of-contents)@@ -62695,13 +65646,346 @@ 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-340).+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-351).Every one of those surfaces consumes the endpoint documented above. The card is the contract; the hosts are just slots.----<a id="sec-258"></a>+<a id="sec-264"></a>++> **Source:** `docs/globe.md` · [↑ table of contents](#table-of-contents)++# Global Intel Globe++**Live surface: [three.ws/globe](https://three.ws/globe)**++A 3D globe of what is happening on Earth right now. Eleven layers of open data+sit on one sphere: armed conflict, force posture and sanctions classified out of+the world news stream, natural events, severe weather, national internet+outages, economic stress, and the reference geography (military bases, nuclear+sites, maritime chokepoints) that makes the live layers mean something.++Everything on it is public data, no credential is needed to read any of it, and+the whole view (camera, zoom, projection, time range, layer selection) lives in+the URL, so any state of the page is a link you can hand to someone else.++---++## The link is the state++```+https://three.ws/globe?lat=20.0000&lon=0.0000&zoom=1.00&view=global&timeRange=7d&layers=conflicts,hotspots,natural+```++| Parameter | Meaning | Values |+|---|---|---|+| `lat`, `lon` | Where the camera is pointed | `lat` clamped to ±85, `lon` wrapped to ±180 |+| `zoom` | Camera distance, reciprocal (2 is twice as close as 1) | 0.6 to 6 |+| `view` | Projection | `global` (sphere) or `flat` (equirectangular) |+| `timeRange` | Window for the live layers | `24h`, `7d`, `30d` |+| `layers` | Which layers are drawn | comma-separated ids from the table below |++Unknown values are ignored rather than fatal: a layer name that no longer exists+is skipped, a hostile `zoom=-4` is clamped, and a layer list that ends up empty+falls back to the default set instead of rendering a bare sphere.++Keyboard: `1`-`9` and `0` toggle the first ten layers, `F` switches projection,+`Space` pauses the idle spin, `Escape` closes the detail card.++## The layers++| Layer id | What it draws | Where it comes from |+|---|---|---|+| `conflicts` | Armed clashes, assaults, mass violence | GDELT 2.0, CAMEO roots 18, 19, 20 |+| `military` | Mobilizations and alert-status changes | GDELT 2.0, CAMEO root 15 |+| `sanctions` | Embargoes, boycotts, administrative sanctions | GDELT 2.0, CAMEO 163 and 172x |+| `hotspots` | Cells where that coverage concentrates | Computed from the three layers above |+| `natural` | Earthquakes, volcanoes, wildfires, landslides | USGS feed, NASA EONET, GDACS |+| `weather` | Cyclones, floods, drought, severe storms | GDACS, NASA EONET |+| `outages` | Countries whose network fell below baseline | IODA (Georgia Tech) |+| `economic` | Annual real GDP growth per country | World Bank open data |+| `bases` | Overseas basing and access agreements | Reference set, `data/globe-reference.json` |+| `nuclear` | Power stations, fuel-cycle sites, weapons complexes | Reference set |+| `waterways` | Maritime chokepoints, scored against the live feed | Reference set plus computed pressure |++Marker size, brightness and pulse all encode one number, `severity`, on 0 to 1.+Each source computes it from what it actually publishes: magnitude for a quake,+alert colour for a GDACS event, how far a country fell below its own baseline for+an outage, and the Goldstein score combined with press mentions for a GDELT+event. Nothing is scaled by a shared guess.++## The API++One call returns every layer:++```+GET /api/globe/intel # all layers, 7d+GET /api/globe/intel?range=24h # a shorter window+GET /api/globe/intel?layers=conflicts,outages # only what you need+```++```json+{+ "generated": "2026-09-08T22:15:03.412Z",+ "range": "7d",+ "rangeLabel": "Last 7 days",+ "maxPointsPerLayer": 1500,+ "totalEvents": 3971,+ "layers": {+ "outages": {+ "status": "ok",+ "count": 17,+ "total": 17,+ "truncated": false,+ "window": { "from": "2026-09-01T22:15:03.412Z", "to": "2026-09-08T22:15:03.412Z" },+ "coverage": "upstream",+ "source": "IODA, Georgia Tech Internet Outage Detection and Analysis",+ "note": "Countries whose reachable address space fell below its own recent baseline…",+ "events": [+ {+ "id": "ioda:IQ",+ "layer": "outages",+ "lat": 33.04,+ "lon": 43.76,+ "title": "Iraq connectivity drop",+ "detail": "Reachability below 25% of its own recent baseline, measured in bgp",+ "severity": 0.931,+ "at": "2026-09-08T03:30:00.000Z",+ "source": "IODA (Georgia Tech)",+ "url": "https://ioda.inetintel.cc.gatech.edu/country/IQ"+ }+ ]+ }+ }+}+```++Every event, from every source, has the same shape, so a client never has to+learn which service a point came from.++### Reading a layer's status honestly++`status` is `ok`, `stale` (the upstream failed and a cached copy is being+served) or `unavailable` (nothing to serve, with a `reason`). A failed layer+returns as a layer, not as a 500: on a situational map, "the outage feed is+down" is itself information, and one dead third party must never blank the other+ten.++`coverage` says where the layer's window came from:++- `upstream` - the source served the whole range that was asked for.+- `ingested` - read from the rolling window this deployment keeps (see below).+- `live` - the cold-start path: read straight from the newest GDELT files,+ covering about the last hour rather than the selected range.+- `static` - reference geography, no time dimension.++`window` is always the span the events actually cover, which for a young+deployment can be shorter than `range`. The page prints that as "Covers 15h so+far" on the layer rather than implying a week of data it does not have.++`truncated` and `total` say when a layer had more points than the per-layer cap+(`maxPointsPerLayer`). The cap keeps the payload and the frame budget sane;+hotspots are computed from the **full** set before the cap is applied, so density+on the globe is never distorted by what the point layer had room for.++## Why there is an ingest cron++GDELT publishes the world's geolocated event stream as one file every fifteen+minutes and offers no way to query history. Its GEO 2.0 API, which used to serve+that role, now 404s for every query including its own documented examples, so+building on it is not an option.++That leaves two choices: offer a time control that quietly means "the last+hour", or keep the window ourselves. [`/api/cron/globe-ingest`](../api/cron/globe-ingest.js)+does the second. Every fifteen minutes it reads the newest export files, keeps+only the three CAMEO families the globe renders (roughly a tenth of each file),+and upserts them into `globe_events` keyed on GDELT's own `GlobalEventID`, so a+re-read of an overlapping file is free.++A cold table fills quickly because backfill is cheaper than it looks: each run+reads twelve files while only one new one has appeared, so history accumulates+about eleven times faster than real time and a month of window is complete in+about three days. Until then, the API reports what it actually covers.++Retention is 32 days, two more than the longest window the UI offers, and the+tail is thinned: past seven days only multi-source events are kept. That reads+the same way from either side. Editorially, a 30-day overview should be the shape+of the month, and single-source reports are noise at that zoom; practically, this+table takes about 120 rows every fifteen minutes and thinning roughly halves what+a full month costs on a database that is already near its retention high-water+mark. Nothing inside the seven-day detail window is thinned, so no view of the+last week loses a point.++The cron also carries `requireWriteCapacity`, so when the database is at its+storage mark it stands down and lets `db-retention` reclaim space first. A globe+window that stops growing for an hour is a smaller problem than a write path that+cannot take a payment.++The cron is authenticated like every other scheduled handler on the platform+(`CRON_SECRET`, see [`api/_lib/cron-auth.js`](../api/_lib/cron-auth.js)) and runs+on Cloud Scheduler from the `crons` array in `vercel.json`.++## Geometry++Two files are baked from Natural Earth (public domain, via the `world-atlas`+package) by [`scripts/build-globe-geometry.mjs`](../scripts/build-globe-geometry.mjs)+and committed, so the browser pulls one small static file and the API resolves a+country code with no network call:++- `public/data/globe-land.json` - coastline polylines, already split at the+ antimeridian so no line is drawn straight across the map.+- `data/country-centroids.json` - ISO alpha-2, alpha-3 and numeric codes to a+ point, used by the two layers that report by country (IODA and the World Bank).++Country points are area-weighted centroids of each country's **largest** landmass,+not bounding-box middles and not an average over every island. The difference is+not cosmetic: an average puts France in the Atlantic, and a bounding box puts+Norway in Sweden.++Regenerate after bumping `world-atlas`:++```bash+npm run build:globe-geometry+```++## Rendering++The page is [`pages/globe.html`](../pages/globe.html) plus two modules:++- [`src/globe-intel-core.js`](../src/globe-intel-core.js) - the arithmetic, with+ no DOM and no three.js: the layer registry, URL state, both projections, marker+ scaling, feed ranking. Covered by `tests/globe-intel-core.test.js`.+- [`src/globe-intel.js`](../src/globe-intel.js) - the scene, the pointer and the+ panels.++Everything drawable is stored twice, once as a point on the sphere and once as a+point on the equirectangular plane, and the view control lerps between them.+That is why switching to the flat map is a morph rather than a rebuild. The blend+is written back into the geometry's `position` attribute rather than applied in a+vertex shader, deliberately: the raycaster reads `position`, and a shader-side+morph would leave every marker unpickable in the flat view.++Markers are drawn with a custom `ShaderMaterial` because severity has to drive+per-point size, which `PointsMaterial` cannot express. Area layers (hotspots,+outages, chokepoints) render as annuli instead of filled dots so a region never+reads as a single incident.++## Sources and their terms++| Source | Access | Notes |+|---|---|---|+| [GDELT 2.0](https://www.gdeltproject.org/) | Open, no key | 15-minute export files; the GEO 2.0 API is dead |+| [USGS earthquakes](https://earthquake.usgs.gov/earthquakes/feed/) | Open, no key | Public-domain feed |+| [NASA EONET](https://eonet.gsfc.nasa.gov/) | Open, no key | Open natural-event tracker |+| [GDACS](https://www.gdacs.org/) | Open, no key | UN and European Commission joint system |+| [IODA](https://ioda.inetintel.cc.gatech.edu/) | Open, no key | Georgia Tech; data is theirs, attribution in the payload |+| [World Bank](https://data.worldbank.org/) | Open, no key | Annual indicators |+| Natural Earth | Public domain | Via `world-atlas` |++If a source starts requiring a key, the layer degrades to `unavailable` with the+reason attached; it does not take the page with it.++## Related++- [`STRUCTURE.md`](../STRUCTURE.md) maps every surface on the platform.+- [Crypto Market Heatmap](https://three.ws/heatmap) is the same idea applied to+ markets rather than geography.++---++<a id="sec-265"></a>++> **Source:** `docs/google-cloud-community-post.md` · [↑ table of contents](#table-of-contents)++---+venue: Google Cloud Community (Medium publication) / Google Cloud Community forums+account: three.ws (official)+suggested_title: "One container, 115 scheduled jobs, and a GPU fleet that sleeps: an AI platform on Cloud Run"+description: "How three.ws serves a static frontend, a route table, every API handler, and a fleet of open 3D model GPUs from Cloud Run: the single-container decision, Cloud Scheduler as the cron plane, Vertex AI as the reliability anchor in a free-first model chain, and the three deploy gates we added after each one caught a real outage."+tags: [cloud-run, cloud-scheduler, vertex-ai, gpu, generative-ai]+status: draft, owner approval required before posting (external-channel gate in CLAUDE.md)+---++# One container, 115 scheduled jobs, and a GPU fleet that sleeps++three.ws is an open-source platform where you describe a character and get a rigged, animated 3D agent you can embed anywhere. It runs on Google Cloud, and three.ws is a member of Google Cloud for Web3 Startups. This is the infrastructure write-up: what runs where, which decisions have held up, and the three deploy gates we added only after each one had already cost us an outage.++Everything is Apache-2.0 at [github.com/nirholas/three.ws](https://github.com/nirholas/three.ws), and `GET https://three.ws/api/version` returns the exact commit and Cloud Run revision production is serving, so any claim here is checkable against the code that serves it.++## The single-container decision++One Cloud Run service serves three things that are usually three deployments: the **static frontend**, the **route table**, and **every API handler**.++The route table is the part worth explaining. Our routes live in a JSON config that the server reads on boot and splits into pre-filesystem and post-filesystem phases, which means a route change is a config change rather than a code change, and the same file is the source of truth for the scheduler sync described below. It is a slightly unusual shape and it has paid for itself repeatedly: there is exactly one place to answer "what serves this path".++Why one container rather than a service per concern:++- **A page and the API it calls share a deploy**, so a frontend that expects a new field cannot ship ahead of the field.+- **Cold-start count is one**, not seven. With serverless services, every additional service is another cold path for a user to hit.+- **The revision is the unit of truth.** "Which revision is serving this?" has one answer, and a rollback is one command.++The trade is real: the container is larger than a per-endpoint function would be, and a hot path shares CPU with a cold one. For a product where the frontend and the API change together in almost every commit, it has been the right trade.++## Cloud Scheduler as the cron plane++There are 115 scheduled jobs. They are declared in the same config file the server reads for routes, and a script syncs that declaration into Cloud Scheduler, so adding a job is a config change reviewed like any other.++Two lessons from operating that many:++**A dispatcher beats 115 schedule entries with independent opinions.** Several of our high-frequency jobs are invoked by one economy tick that fans out, with per-entry cooldowns deciding what actually fires. Sixty jobs each waking on their own minute boundary is sixty simultaneous cold starts on the same minute.++**Declare the schedule where the code lives.** A cron that exists only in the console is invisible to code review, invisible to `git log`, and impossible to recreate after an account change.++## The GPU fleet, and why min-instances is a quota decision++The generation lanes run open 3D model families on their own Cloud Run GPU services (NVIDIA L4s, plus one RTX PRO 6000 Blackwell for the heaviest work): TRELLIS for image to 3D, Hunyuan3D for high-poly reconstruction, TripoSG for sketch to 3D, and around them the mesh pipeline (rigging, remeshing, texturing, segmentation, stylization, background removal, avatar reconstruction, text to motion, video to motion, video to scene). Thirty-two workers in total, most published as Docker images.++The interesting cost is not the container start. It is the **weight load**: on a FUSE-mounted volume a cold load can stall for minutes before the job begins. Which produces the counter-intuitive rule:++**`min-instances` is a quota decision, not a performance one.** A regional L4 grant is finite. Pinning a warm instance on every lane starves the lanes that need to burst. So one lane pins one always-warm instance and bursts to three, another was explicitly moved to zero to free the shared regional pool, and the spiky lane scales to zero. Three different answers to the same question, correct per lane.++A keep-warm job holds an allowlist of scale-to-zero lanes resident during peak hours, with the allowlist in an environment variable so it changes without a deploy. One detail worth copying: **a lane id in that allowlist that matches no known lane fails the tick loudly** rather than warming nothing silently. A typo in a keep-warm config is otherwise invisible until someone complains about latency a fortnight later.++And when the regional pool is exhausted, requests do not fail with a message that says "quota". They fail slowly, in a pattern that reads like a model problem. We keep a named signature for it in the triage runbook, and the first check on any "generation is slow" report is the pool, not the model.++## Vertex AI as the anchor at the bottom of a free-first chain++Every text completion on the platform runs through one shared failover chain that tries free providers first and only reaches a paid key last. That chain is a dozen rungs deep, and two design rules matter more than the ordering:++**The chain can never have an empty rung.** Two rungs are keyless on purpose, so the bottom always exists even when every keyed provider is unset or throttled.++**Vertex Gemini is the reliability anchor**, billed to our own cloud budget rather than a third-party free tier, which means the chain's floor does not depend on somebody else's quota reset. That is the specific reason to put a first-party cloud model in a free-first chain: not because it is cheapest, but because it is the rung whose failure mode you control.++A related trap, which is not cloud-specific but bit us here: **model end-of-life is a silent outage.** An upstream family reached end of life and its rung began answering `410`. The chain fell through correctly, but the real fix was a scheduled job that diffs our hardcoded model ids against live provider catalogues, so we learn before users do. If you hardcode model ids anywhere, you owe yourself that job.++## Three deploy gates, each added after it would have saved us++Our build is a fixed chain and the order is load-bearing: conflict check, browser-graph check, a temporal-dead-zone check, sub-artifact builds, the frontend build, then the steps that write into the output directory *after* the frontend build wipes it. That last ordering fact has broken us more than once, so it is encoded in one command rather than in anyone's memory.++The three gates that matter most, and what each one caught:++**1. A migration gate before submit.** The build refuses to submit when a database migration is pending. Without it, new code shipped over an old schema, and production served handlers querying a column whose migration had never been applied. The error a user sees in that situation looks nothing like "we forgot a migration".++**2. An upload-context simulation.** Before submitting, we simulate the build-context upload and fail if a file the server imports at runtime would be excluded by ignore rules. This exists because a revision shipped with one omitted module and answered every request, health check included, with a module-not-found error. The build was green. The container started. Nothing was wrong except one file that never got uploaded.++**3. A synchronous CDN purge.** Our purge used to run asynchronously, and post-deploy checks then read stale edge content and reported phantom failures. Making it synchronous costs a minute and removes an entire category of "is it deployed or not" confusion.++The fourth, cheaper than all of them: a version endpoint that returns the running commit and revision. Nearly every "is this live?" conversation ends in one curl.++## What I would tell someone starting the same build++- **Put the route table in a file the server reads,** and let other tooling read the same file. One source of truth beats one convention.+- **Decide per lane whether a warm floor is worth it,** and write down why, because the reasoning is not recoverable from the config six months later.+- **Give every failover chain a keyless bottom rung.**+- **Add a gate the day after an incident, not the week after.** Each of the three above was written in the hours following the outage it now prevents, which is the only time the exact failure is still fresh enough to encode.+- **Publish the version.** It costs an afternoon and it retires an entire genre of conversation.++Free to try, no account and no key: [three.ws/forge](https://three.ws/forge) for 3D generation, `https://three.ws/api/mcp-studio` for the eleven-tool MCP server, and [three.ws/docs](https://three.ws/docs) for the rest.++---++<a id="sec-266"></a>> **Source:** `docs/google-x-accounts.md` · [↑ table of contents](#table-of-contents)@@ -62813,7 +66097,7 @@ Google also operates many country and regional accounts (for example @GoogleIndi----<a id="sec-259"></a>+<a id="sec-267"></a>> **Source:** `docs/guardian.md` · [↑ table of contents](#table-of-contents)@@ -62839,7 +66123,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-187)) are enforced by the recovery API, not the console:+**The safety rails** (detailed in [custody](#sec-191)) 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).@@ -62858,9 +66142,9 @@ The response sorts agents that need your action first, then those with an open p## Walkthrough-1. Open [/guardian](https://three.ws/guardian). Signed out, it prompts you to sign in. Signed in with no roles, it explains what the console is for and invites you to ask a friend to name you.+1. Open [/guardian](https://three.ws/guardian). Signed out, it prompts you to sign in or create an account, and returns you here afterwards. Signed in with no roles, it explains what the console is for, invites you to ask a friend to name you, and links you to setting up recovery on your own agents.2. Each agent you protect renders as a card: its name (linked to its profile), who owns it, when you were trusted, and your roles (guardian, beneficiary, or both). A badge at the top counts how many agents need your action.-3. If a process is open, the card tells its story in the agent's own voice ("I'm being recovered. If you trust this person is really my owner, approve."), plus the approval count, the safety-window countdown, and when it opened.+3. If a process is open, the card tells its story in the agent's own voice ("I am being recovered. If you trust this person is really my owner, approve."), and then gives you what a decision actually needs: the reason the requester gave, the approval count, which guardians have already approved or declined by name, how long until the request expires if nobody acts, the safety-window countdown, and when it opened.4. Act. For a recovery you trust, click **Approve recovery** (or **Decline**). For an inheritance you believe is real, click **Confirm inheritance**. Each action asks you to confirm, because these are consequential.5. When the safety window has elapsed and the process is ready, click **Complete transfer** to pass control of the agent and its wallet to the new owner.6. If you are the beneficiary or a guardian and the owner has gone silent past their threshold with no active process, you can try to arm inheritance, which begins the grace window.@@ -62887,19 +66171,20 @@ The console reads this on load, resolves your viewer id (so it can tell whether- **Time-locked and cancelable.** Threshold approvals start a safety window; the real owner can cancel any time before completion, and their return defeats the request outright.- **Auto-freeze during a dispute.** An open request freezes autonomous spend (owner withdrawal stays open), tracked separately so it lifts on resolution without overriding a freeze the owner set.- **Confirmation on every consequential action.** Approve, confirm, decline, and complete each prompt for confirmation before firing.-- **Signed-out, empty, and error states** are all designed: sign-in prompt, "no one's named you yet", and an inline retry on failure.+- **Signed-out, empty, loading, and error states** are all designed: a sign-in prompt that returns you to the console, "no one has named you yet" with a route to setting up your own guardians, skeleton cards while the inbox loads, and a plain-English failure with a retry (a dropped connection, a rate limit, and a server fault each read differently).+- **The page tracks the process while you watch it.** It reloads itself the moment a safety window lifts, and again when you return to the tab, so a card never shows a countdown that expired while you were away.- **Not the content-safety Guardian.** This console is unrelated to `@three-ws/guardian`, the AI content-moderation package that shares the name.## Related-- [Custody you can verify](#sec-187) - the full recovery and inheritance model, the freeze switch, spend limits, and proof-of-custody-- [Financial controls](#sec-240) - the plain-English spend rules on the same wallet rails+- [Custody you can verify](#sec-191) - the full recovery and inheritance model, the freeze switch, spend limits, and proof-of-custody+- [Financial controls](#sec-246) - 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-260"></a>+<a id="sec-268"></a>> **Source:** `docs/guards.md` · [↑ table of contents](#table-of-contents)@@ -62959,6 +66244,14 @@ Guards that can only judge a finished artifact: whether a Node-only module leakeThe order inside this chain is load-bearing. The frontend build empties `dist/`, so everything that writes into it must come after. `build:gcp` already encodes the correct order, and `npm run check:claude` verifies that the runbook in `CLAUDE.md` still describes it accurately.+### Deploy submit++```bash+npm run deploy:gcp:submit+```++The last gate before code leaves the machine, and the only one that can see the finished artifact and the database it is about to ship over at the same time. It checks that no migration is pending, that nothing the server imports at runtime would be excluded from the build context, and that the decoder assets `dist/` must carry are really there. A failure here is still cheap: nothing has been deployed.+### Pre-pushRuns automatically on `git push`. Installed into `.git/hooks` by [`scripts/setup-git-hooks.mjs`](https://github.com/nirholas/three.ws/blob/main/scripts/setup-git-hooks.mjs), which `postinstall` runs on every `npm install`, so a fresh clone is covered without a setup step.@@ -62999,9 +66292,14 @@ Run `npm run audit:guards` to print the current count and per-stage breakdown. T| No unbounded outbound call | `npm run check:fetch-timeouts` | Every fetch to a third-party host carries a deadline, so one stalled upstream cannot hold a request until the platform kills it. || Hard rules, diff scoped | `npm run check:rules` | The CLAUDE.md hard rules on the lines you changed. || The guard registry | `npm run audit:guards` | Every guard is registered and every stage claim is true. |+| Skills seed drift | `npm run check:skills-seed` | `data/skills/seed.json` still matches the SKILL.md files it is generated from, so a skill cannot read one way on disk and another in the marketplace. |+| Motion signature index | `npm run audit:motion` | `public/animations/signatures.json` describes the clips that are actually baked, so a rebake cannot leave `/gestures` and the walk-layer tables describing motion that no longer exists. || One `<model-viewer>` build | `npm run check:model-viewer` | Every `<model-viewer>` reference in tracked source names one version, no version is served under two integrity hashes, and the vendored copy matches. || Design-token ratchet | `npm run audit:tokens` | Hardcoded colour hexes cannot creep back past a committed baseline. |+| Interactive-state ratchet | `npm run audit:states` | A selector that declares cursor:pointer cannot ship without a hover rule behind it. |+| Motion ratchet | `npm run audit:motion-tokens` | A transition cannot spell its duration or easing as a literal past a committed baseline. || Credential material | `npm run check:secrets` | No dotenv file, private key, keystore, or downloaded cloud credential becomes a tracked file, and no added line carries a provider-issued key. |+| Python worker dependencies | `npm run audit:deps` | No pinned Python dependency in `workers/`, `services/` or `packages/` carries a known vulnerability in the OSV database. Needs network, so it runs on demand rather than in the gate. || iOS app icon | `npm run check:ios-icons` | The committed iOS icon and launch images are exactly what the current brand mark produces, and the icon carries no alpha channel. || macOS app icon | `npm run check:macos-icon` | The ten committed Mac icon sizes and their Contents.json are exactly what the current brand mark produces. || Apple glance widget | `npm run check:apple-widget` | Both Xcode projects that build the Agent glance widget are consistent, every shared Swift source belongs to the targets that need it, and the Swift client still agrees with `api/glance/mine.js` on the endpoint, the headers, the states, the sizes and the token shape. |@@ -63010,13 +66308,16 @@ Run `npm run audit:guards` to print the current count and per-stage breakdown. T| Guard | Command | Protects ||---|---|---|-| Route documentation | `npm run audit:pages` | Every human-facing route is documented in `data/pages.json`. |+| Route documentation | `npm run audit:pages` | Every human-facing route is documented in `data/pages.json`, and no page is submitted for indexing while its own HTML answers noindex or robots.txt disallows its path. || Declared pages resolve | `npm run check:pages` | Every page declared in `data/pages.json` is actually reachable. || Routing and 404 model | `npm run audit:routes` | Catalog pages reachable, unknown paths reach the designed 404, no shadowed routes. || Route shadowing | `npm run audit:route-shadowing` | Every handler under `api/` that looks routed can actually be reached through the production router's walk of `vercel.json`. || API handlers export a body | `npm run audit:handlers` | No API handler ships empty or without an export. || The `[hidden]` guard | `npm run audit:hidden-guard` | Every page resolves the CSS that makes `hidden` actually hide. || Site link integrity | `npm run audit:links` | Every navigable target resolves to a real route or file. |+| On-page SEO | `npm run audit:seo` | Across the pages we ask Google to index: no duplicate title or description, every canonical self-referential, no sitemap entry answering noindex or a non-200, and structured data that parses. Reads a live origin, so `--base` points it at a preview. |+| Awesome list freshness | `npm run check:awesome` | `awesome/README.md` and `public/awesome.json` still match `data/awesome.json`, the source both are generated from. |+| Awesome list link health | `npm run awesome:links` | Every url in the Awesome 3D Agents list still answers, and none is listed twice. Manual on purpose: it calls a hundred-odd third-party hosts, and it tells a bot-filter 403 apart from a dead link. |### Docs and contracts@@ -63028,6 +66329,7 @@ Run `npm run audit:guards` to print the current count and per-stage breakdown. T| 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. |+| Tour bundle copy | `npm run audit:tour-global` | `public/tour-builder/tour.global.js` is the bundle this repo's tour-sdk actually builds, so the Tour Builder preview cannot drift from the package a reader installs. || Tour atlas truth | `npm run audit:tour-atlas` | `public/tour/atlas.json` matches a fresh render: every stop resolves, every promised screenshot exists, and the page's own copy (`data/pages.json`, `pages/tour-atlas.html`) advertises the number of stops the atlas actually has. || x402 endpoint catalog | `npm run audit:x402-catalog` | Every paid endpoint is documented, so a buyer can find it. || MCP manifests | `npm run audit:mcp` | Every MCP manifest satisfies the official registry's rules, offline. |@@ -63160,7 +66462,7 @@ The short version:----<a id="sec-261"></a>+<a id="sec-269"></a>> **Source:** `docs/herald.md` · [↑ table of contents](#table-of-contents)@@ -63436,15 +66738,15 @@ The avatar is the point, but it is never the requirement.## Related-- [Notifications](#sec-342): the bell, the inbox API, and the+- [Notifications](#sec-353): 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-193): API keys, scopes, and usage.+- [The developer platform](#sec-197): API keys, scopes, and usage.----<a id="sec-262"></a>+<a id="sec-270"></a>> **Source:** `docs/hold-to-access.md` · [↑ table of contents](#table-of-contents)@@ -63751,13 +67053,124 @@ worlds unaffected.## Related-- [Validation](#sec-570) — the quality gate every model passes before publish.+- [Validation](#sec-590) — 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-263"></a>+<a id="sec-271"></a>++> **Source:** `docs/home-assistant-community-post.md` · [↑ table of contents](#table-of-contents)++---+venue: Home Assistant Community (community.home-assistant.io), category "Share your Projects!"+account: three.ws (official) / nichxbt+description: "Forum post introducing the three.ws Home Assistant integration: a HACS custom integration that dials out over one WebSocket so a LAN-only install can be reached, an MCP server whose door-opening tools refuse over stdio, household roles enforced server-side, and a 3D agent that stands in a live model of your house."+tags: [custom-integration, hacs, mcp, voice, presence]+status: draft, owner approval required before posting (external-channel gate in CLAUDE.md)+---++# I gave my Home Assistant a face, and spent most of the time making sure it cannot open my front door++_Forum post for the [Home Assistant Community](https://community.home-assistant.io), category "Share your Projects!". Written first person for people who run HA, not for people who sell things to people who run HA._++Hi all. I build [three.ws](https://three.ws), an open-source (Apache-2.0) platform for 3D AI agents: you describe a character, you get a rigged, animated 3D body that can talk, and you can embed it anywhere. For most of its life that character lived in a browser tab and the worst thing it could do was say something silly.++Then I connected it to my house, and the whole design changed. This post is what I built, and much more importantly, what I refused to build.++Short version: there is now a HACS integration that connects a LAN-only Home Assistant to a 3D agent that stands in a live model of your home and talks to you, plus an MCP server so **any** assistant (Claude, Cursor, your own) can read and drive your house. Locks are the interesting part, and the answer there is a flat no in several places on purpose.++## What Home Assistant already does, and what I did not rebuild++I wrote zero device code. Not "a thin abstraction", zero. Zigbee, Z-Wave, Matter, Thread, BLE, and the 1,500-plus integrations are the reason this project took weeks instead of years, and re-implementing any of it would have been vandalism. Since the `mcp_server` integration, HA also speaks Model Context Protocol natively, and three.ws already speaks MCP in around forty packages. The two halves met without either side inventing a protocol.++What genuinely does not exist anywhere, as far as I can tell, is the **face**: a real-time 3D presence that stands in a live model of your home, reacts to it, and speaks. That is the part I built.++## The LAN problem, and why the house dials out++Most HA installs cannot be reached from the internet. No forwarded port, no public address, nothing to dial. That is not an edge case, it is the default install, and any integration that assumes otherwise is a cloud product wearing a local-first hat.++So: **the house dials three.ws, and three.ws never dials the house.**++One integration from HACS opens a single outgoing WebSocket and keeps it open.++- Nothing listens on your network.+- No port is forwarded and no firewall rule changes.+- No tunnel daemon, no third-party service, no account anywhere else.+- **three.ws never receives a Home Assistant token.** The integration signs in to HA on your own machine with a credential it creates for itself, and that credential never leaves the house.++Install path, if you want to try it:++1. On three.ws, open `/smart-home`, choose **Connect a home that is only on my network**, and press **show me a code**. It has a ten-minute countdown.+2. In HACS, add `https://github.com/nirholas/three-ws-home-assistant` as a custom repository, category **Integration**.+3. Install **three.ws**, restart HA.+4. **Settings, Devices and services, Add integration, three.ws.** Paste the pairing code.++If your HA already has a remote https address (Nabu Casa, or your own reverse proxy), skip all of that and connect with a long-lived token instead. The relay exists for the houses that do not, not as the default path.++The threat model is written down and published rather than implied. Writing it is what produced two of the constraints above, which is an argument for writing one even when nobody asks.++## The part I care about: locks++Here is where I expect this forum to have opinions, and I would genuinely like them.++An LLM that can call `light.turn_on` is a convenience. An LLM that can call `lock.unlock` is a completely different product with a completely different failure mode, and the industry answer so far has been to put a sentence in a system prompt. **A system prompt is an argument, and an argument can be won by the other side.**++So the refusals live on the server, in four layers:++**1. The physical-action gate.** Anything that opens the house passes through one gate with one implementation (shared between the bridge and the MCP server rather than two copies that drift). It is not a naming convention or a category filter; it is a code path.++**2. Over stdio, that gate refuses outright.** The published MCP server, `@three-ws/home-mcp`, gives any assistant five tools: read the house, list entities, list the scenes your household already built, run one, call a service. Point it at your HA:++```bash+claude mcp add home \+ -e HOME_ASSISTANT_URL=https://example.ui.nabu.casa \+ -e HOME_ASSISTANT_TOKEN=... \+ -- npx -y @three-ws/home-mcp+```++Ask it to unlock a door and it will decline and tell you why. A stdio MCP server has no user-visible surface of its own, no session, and no way to prove a human saw the request and approved it. Anything that presents itself as consent in that environment is a fiction, so unlocking is available only where a real person can be shown a real prompt.++**3. Household roles, enforced server-side.** A house has more than one person in it, and the old answer was to hand over your password. There are five roles now, each stating in plain words at the moment you pick it what it can and cannot do:++- Somebody who lives there can control everything and approve unlocking a door.+- A guest can turn the lights on and **can never** approve unlocking anything, no matter what an agent asks them. That refusal is enforced on the server, so there is no version of any client that could offer them the button.+- A guest or viewer can be scoped to just the kitchen, or just three devices, and **the rooms you did not give them are removed from what they receive**, not hidden on screen. Their app never learns those rooms exist.+- Invitations work once, expire after a week, and can be withdrawn before anyone uses them.+- Removing somebody takes back every standing allowance they ever approved in the same instant, so a door cannot keep opening on the say-so of a person who has left.+- Every action in the home log is attributed to the person who took it, so "who did what" has a real answer.++**4. Voice, where consent is loosest.** Hands-free is the only interface that works when you are carrying groceries, and it is also the interface where a television in the next room can say "yeah". Confirming a physical action requires an intentional utterance, not an affirmative-sounding noise. This one took three rewrites and I still would not call it solved.++## Things I tried and did not ship++**Exposing the agent as a Matter device.** It is the obvious move, it would have been a good headline, and after measuring what it would actually cost and buy, I decided against it for now and published the reasoning rather than quietly dropping the thread. If someone here has done it and thinks I got the trade wrong, I would like to hear it.++**A cloud-first pairing flow.** The first version had the platform dial the house. It worked in my house and in almost nobody else's, for the reasons in the LAN section.++## The rest, briefly++- **A live 3D scene of your home** that the agent stands in, reacting to state as it changes. It is the reason to have a body at all: an agent that is *somewhere* in a house reads differently from a text box that mentions rooms.+- **A voice satellite face.** If you run an HA voice assistant, it can wear the agent's face instead of being a speaker grille.+- **Privacy as a page, not a policy.** See, export and delete everything a connected home stores, on one screen.+- **Honest status.** The status page can tell a dark house (yours is off, or asleep, or the internet is out at your end) from an actual outage on our side, and it says which. One unreachable home can no longer degrade the others, which was a real bug and a fair thing to be annoyed about.+- **Language and units.** The whole surface reads in your language, in your units, at a touch size that works on a wall tablet, and the wall display stays awake.+- **The car**, because it is the same design problem: a voice-first agent that can reach your house from the road, with an Android Auto app built and a CarPlay scene waiting on Apple's entitlement.++## What I would like from this forum++1. **Is the stdio refusal right, or is it paternalistic?** My reasoning is that a local server cannot prove consent. The counter-argument I keep hearing is that it is the user's own machine and their own choice. I have not been convinced yet, but I am listening.+2. **Roles.** Five felt like the smallest set that covers real households (residents, guests, house sitters, kids, view-only displays). If you run a household where those five break down, tell me where.+3. **What should an agent never be allowed to do, even for the owner?** My current list is short: nothing that unlocks without a proven human prompt, and nothing that silently changes another person's access. I suspect this list should be longer.++Everything is Apache-2.0. The integration is at [github.com/nirholas/three-ws-home-assistant](https://github.com/nirholas/three-ws-home-assistant), the MCP server is `@three-ws/home-mcp` on npm, the platform is at [three.ws/smart-home](https://three.ws/smart-home), and the docs (including the relay threat model and the Matter write-up) are at [three.ws/docs/smart-home](https://three.ws/docs/smart-home).++Happy to answer anything, including hostile questions about why a 3D avatar belongs anywhere near a house. That last one is fair and I have a real answer for it: a home has rooms and objects, and an assistant that can be *somewhere* in it is easier to talk to than one that cannot.++---++<a id="sec-272"></a>> **Source:** `docs/home-households.md` · [↑ table of contents](#table-of-contents)@@ -63771,7 +67184,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-449) for why three.ws writes zero device code and what the Home+Related: [smart-home.md](#sec-467) for why three.ws writes zero device code and what the HomeAssistant bridge does.---@@ -64134,7 +67547,7 @@ insert. A home can never exist in a state where nobody can administer it.----<a id="sec-264"></a>+<a id="sec-273"></a>> **Source:** `docs/home-plans.md` · [↑ table of contents](#table-of-contents)@@ -64148,9 +67561,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-449) (what the lane is),-[`docs/home-privacy.md`](#sec-265) (retention and deletion),-[`docs/home-households.md`](#sec-263) (roles and seats).+Related: [`docs/smart-home.md`](#sec-467) (what the lane is),+[`docs/home-privacy.md`](#sec-274) (retention and deletion),+[`docs/home-households.md`](#sec-272) (roles and seats).---@@ -64209,9 +67622,21 @@ from a remembered figure. The production service shape comes fromTwo findings inverted the assumptions this work started from, and both are worth stating plainlybecause they point the pricing in the opposite direction:-**One agent turn on a paid model costs more than a year of holding that house's socket.**-$0.0228 against $0.0155 per month. The connection is not the expensive part after all; the prompt-is, because the room graph makes a home prompt large.+**One agent turn on a paid model costs weeks of holding that house's socket.** $0.0228 for a+single Claude Sonnet 5 turn, against $0.0155 per home per month: about six weeks of connection for+one sentence. The connection is not the expensive part after all; the prompt is, because the room+graph makes a home prompt large.++That ratio was re-measured on 2026-09-09 against a second real Home Assistant and it does not come+back identical, so the honest version is a range rather than a point. The heap figure reproduces+almost exactly (309 KB marginal per connection against the original 302 KB) and the stream figure+reproduces to the cent, but resident memory does not: 1.25 MB marginal per connection against the+original 262 KB, which prices a home at **$0.0738/month** instead of $0.0155. The re-measurement ran+on a machine at load 83 with several other agents building, and RSS under memory pressure includes+a great deal that is not attributable to the connection, so $0.0155 remains the figure to price from+and $0.0738 is a defensible upper bound. Priced at the upper bound a Sonnet turn still costs+**nine days** of holding the socket, so the conclusion below is unchanged at either end of the+range, which is the only reason this is a footnote and not a re-plan.**Voice is not a cost driver at all.** The default speech lanes are keyless and cost the platformnothing per utterance. Voice minutes are metered because an unbounded always-listening satellite is@@ -64221,7 +67646,9 @@ money.### Can the free tier carry a connected home?**Yes, comfortably.** At 1.6 cents per home per month, ten thousand free connected homes cost-about $155 a month, which is roughly one warm Cloud Run instance. The honest constrained free tier+about $155 a month, which is roughly one warm Cloud Run instance. At the loaded-machine upper bound+above the same ten thousand homes cost about $740 a month, which is still a rounding error against+the credit grant and still does not change the answer. The honest constrained free tiersome cost models would have forced (a session-scoped connection that closes when the tab does) isnot necessary and would make the free tier worse for no saving worth having. The free tier gets areal, persistent, always-connected home.@@ -64388,9 +67815,29 @@ user can predict, and it is shown on the plan page with that date.| Seats | [`api/home/[id]/members.js`](../api/home/[id]/members.js) | an invitation past `members`, counting outstanding invites as well as members, billed to the home's **owner** || Retention | [`api/_lib/home/privacy.js`](../api/_lib/home/privacy.js) | raising retention past the plan's ceiling. Never applied retroactively || Actions | [`api/home/[id]/call.js`](../api/home/[id]/call.js) | an ordinary action on a paused home. **The safety exemption is checked first**, so a safety action is never reached by this code |+| Agent turns | [`api/_lib/home/turn-gate.js`](../api/_lib/home/turn-gate.js), called from [`api/chat.js`](../api/chat.js) | a home tool the agent tried to run past `agentTurns`. Read-only tools are never gated and safety actions are never gated, so over quota the agent can still be asked what the house is doing and told to lock up |Ordinary service calls are **not** metered at all. Actions are cheap; the socket is the cost. A-user can run twenty lights all evening without touching a quota.+user can run twenty lights all evening without touching a quota. What is metered is the *agent+turn* that drives them, because on a paid model one turn costs weeks of holding that house's+socket.++Two deliberate holes in the agent-turn gate, both of which exist so commitment 1 survives contact+with a real conversation rather than only with a unit test:++* **Read-only home tools are never gated.** The agent finds the door by reading the house+ (`home_status`) and only then targets the lock. Gate the read and the safety exemption ends one+ step before it was needed. A read also spends nothing the turn had not already spent by the time+ the model emitted the call.+* **A safety action inside a gated tool is never refused.** `home_call` carries its domain and+ service on the input, which is exactly what the safety classifier reads, so a lock, a close or an+ arm is recognised with no live entity list and therefore in precisely the degraded states where+ somebody most needs to lock up.++The gate also **fails open**. An unreadable entitlement row or an unreachable usage counter+resolves to "allowed", never to "refused": a quota that errs must err toward serving the user, and+refusing a person access to their own house over a billing hiccup is the failure this lane is least+willing to ship.There is also a separate, unrelated ceiling: the per-instance backpressure ladder in[`api/_lib/home/admission.js`](../api/_lib/home/admission.js). That answers "is this instance@@ -64410,7 +67857,7 @@ limit can never touch are stated in words rather than buried in a policy nobody----<a id="sec-265"></a>+<a id="sec-274"></a>> **Source:** `docs/home-privacy.md` · [↑ table of contents](#table-of-contents)@@ -64426,7 +67873,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-449) for how the connection works,+Related reading: [three.ws Home](#sec-467) for how the connection works,and the [platform privacy policy](/legal/privacy) for everything outside thislane.@@ -64690,7 +68137,7 @@ them.----<a id="sec-266"></a>+<a id="sec-275"></a>> **Source:** `docs/home-relay-threat-model.md` · [↑ table of contents](#table-of-contents)@@ -64703,7 +68150,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-270).+are in [home-security.md](#sec-279).## What the relay is@@ -64924,16 +68371,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-267): installing the integration, configuring the relay, and the+- [home-relay.md](#sec-276): installing the integration, configuring the relay, and thetwo-network setup that proves the path against an unroutable house.-- [home-security.md](#sec-270): the platform threat model, the injection boundary, the+- [home-security.md](#sec-279): the platform threat model, the injection boundary, theeleven checks.-- [smart-home.md](#sec-449): why the reachability problem exists and the three answers to it.-- [tutorials/connect-your-home.md](#sec-498): the user-facing walkthrough.+- [smart-home.md](#sec-467): why the reachability problem exists and the three answers to it.+- [tutorials/connect-your-home.md](#sec-518): the user-facing walkthrough.----<a id="sec-267"></a>+<a id="sec-276"></a>> **Source:** `docs/home-relay.md` · [↑ table of contents](#table-of-contents)@@ -64984,7 +68431,7 @@ Home Assistant `config` folder, restart, and do step 4.### What it can and cannot do-Read [the threat model](#sec-266). It is written for someone deciding whether to+Read [the threat model](#sec-275). 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@@ -65133,7 +68580,7 @@ more than a day ago). It is wired in `vercel.json` and runs hourly.----<a id="sec-268"></a>+<a id="sec-277"></a>> **Source:** `docs/home-satellite.md` · [↑ table of contents](#table-of-contents)@@ -65321,7 +68768,7 @@ written from that source, and where our reading differed from the wire, the wire----<a id="sec-269"></a>+<a id="sec-278"></a>> **Source:** `docs/home-scene.md` · [↑ table of contents](#table-of-contents)@@ -65335,9 +68782,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-449) (why any of this exists),-[connecting a house](#sec-498),-[households and roles](#sec-263), [home security](#sec-270).+**Related:** [three.ws Home](#sec-467) (why any of this exists),+[connecting a house](#sec-518),+[households and roles](#sec-272), [home security](#sec-279).---@@ -65350,7 +68797,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-498)+You need a connected home first. [The tutorial](#sec-518)takes about three minutes.## What you are looking at@@ -65392,7 +68839,7 @@ anyone has filed a thing.## ReactivityThe page holds one Server-Sent Events subscription to-`GET /api/home/<id>/stream` ([the API reference](#sec-104)). It never+`GET /api/home/<id>/stream` ([the API reference](#sec-105)). It neverpolls.Measured against a real Home Assistant on the same machine:@@ -65473,6 +68920,11 @@ path, the old-device path and the "WebGL is blocked by policy" path.You reach it three ways:1. The **2D** button in the top bar, or `?view=2d`. The choice is remembered.+ An explicit `?view=` outranks that memory: `?view=3d`, `?view=2d` and+ `?view=plan` all open the view they name, whatever this browser used last,+ which is what makes a shared link and a wall display's pinned address land+ where they say they will. Following such a link does not change the+ preference this browser chose for itself.2. **Automatically**, when the browser has no WebGL at all. The page says sorather than showing a black canvas.3. **Automatically**, when this device measurably cannot hold 18 frames a second@@ -65562,9 +69014,35 @@ real house, a real light changed in Home Assistant reaches the rendered scene,the house survives its connection being killed, a browser with no WebGL canstill operate it, and a burst of twenty real service calls grows nothing.+### Running two lanes at once++Everything the lane keeps on disk is keyed by `HOME_LIVE_NAME`, so a second run+on the same machine does not walk into the first one:++```bash+HOME_LIVE_NAME=mylane HOME_E2E_API_PORT=8141 HOME_E2E_WEB_PORT=3071 \+ HOME_E2E_ROLES=owner \+ npx playwright test --config playwright.home.config.js tests/e2e/home-floorplan.spec.js+```++- The Home Assistant container, `.ha-config-e2e-stack.<lane>.json` and+ `.ha-config-e2e-accounts.<lane>.json` all carry the lane name.+- `resetHomes` and `openScene` only ever touch homes pointed at **this lane's**+ Home Assistant, so a concurrent run's house is never deleted underneath it.+- Each lane needs its **own** account: a plan carries a fixed number of homes,+ so two lanes sharing one account means the second is refused with "this+ account is at its home limit" and the only way to make room is to evict the+ house the other run is using.+- `HOME_E2E_ROLES` provisions only the accounts a run signs in as. Registration+ is capped at five per hour per IP, so a spec that only uses the owner should+ not spend one of those five on a guest.+- Ports must be free and are never reused: the shared `npm run dev` on :3000+ proxies `/api` at **production**, so a run that borrowed it would silently+ test the wrong API.+----<a id="sec-270"></a>+<a id="sec-279"></a>> **Source:** `docs/home-security.md` · [↑ table of contents](#table-of-contents)@@ -65577,7 +69055,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-449) first for what the lane is and how it reaches a house. This+Read [smart-home.md](#sec-467) 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),@@ -65777,20 +69255,34 @@ exists so the UI can tell the two apart from the security refusals when it needs# Everything except the live injection proof, on every npm test:npx vitest run tests/home-security.test.js-# The injection proof needs a real house. Never mock one: a fake instance would-# have hidden the HassTurnOff-unlocks-a-lock behaviour this whole gate exists for.-docker run -d --name ha -p 8123:8123 -v "$PWD/.ha-config:/config" \- ghcr.io/home-assistant/home-assistant:stable-# add `demo:` to .ha-config/configuration.yaml, restart, mint a long-lived token-HOME_ASSISTANT_URL=http://localhost:8123 HOME_ASSISTANT_TOKEN=... \- npx vitest run tests/home-security.test.js+# Check 4 needs a real house AND a real model. Never mock the house: a fake+# instance would have hidden the HassTurnOff-unlocks-a-lock behaviour this whole+# gate exists for. The lane's harness builds one, seeded and onboarded, in one+# command, and it is the only instance any live home test should use.+eval "$(node scripts/home-test-instance.mjs --up --onboard --seed --name sec11 --env)"+npx vitest run tests/home-security.test.js+node scripts/home-test-instance.mjs --down --name sec11```+**The model half is a real requirement, not a nicety.** Check 4's real arm asks the+[LLM chain](../api/_lib/llm.js) for four turns and executes whatever they ask for. Without a+credential the chain falls through to its two keyless anonymous rungs, both of which answer 429+under any load, and the test **fails** with `no model in the chain answered, so this proved+nothing`. That is deliberate: a door staying locked because nothing ever asked to open it is an+outage, not a proof, and a security check that passes during an outage is worse than no check.+Production carries the keys; locally, put one keyed rung in the environment (`GROQ_API_KEY`,+`NVIDIA_API_KEY` and `OPENROUTER_API_KEY` are all on the `three-ws-api` service, readable with+`node scripts/read-service-env.mjs '^GROQ_API_KEY$' --raw`).++The deterministic arm needs no model at all: it submits the injected instruction directly. It+runs whenever the house is up, which is why check 4 still proves the gate on a run where every+model turn was refused by a rate limiter.+The secrets scan and the dependency posture run with everything else and need nothing.----<a id="sec-271"></a>+<a id="sec-280"></a>> **Source:** `docs/home-voice.md` · [↑ table of contents](#table-of-contents)@@ -65800,7 +69292,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-03.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-449) that lets you say "turn the kitchen light+This is the part of [three.ws Home](#sec-467) that lets you say "turn the kitchen lightoff" to a browser that is already open, and get the light and an answer without touchinganything.@@ -65850,7 +69342,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-265); this loop creates+ anything else is covered by [Home privacy and retention](#sec-274); 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@@ -65867,7 +69359,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-270) exists, and it is why this loop treats a spoken confirmation+why [the gate](#sec-279) 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:@@ -66051,21 +69543,21 @@ would only let the two drift.## Related-- [three.ws Home](#sec-449): the whole plan, and what a connection is-- [Home security](#sec-270): the gate this loop speaks for-- [Home privacy and retention](#sec-265): what is stored and for how long-- [Households](#sec-263): who in a house may approve an unlock-- [three.ws Drive](#sec-146): the same agent, voice-first, in a car+- [three.ws Home](#sec-467): the whole plan, and what a connection is+- [Home security](#sec-279): the gate this loop speaks for+- [Home privacy and retention](#sec-274): what is stored and for how long+- [Households](#sec-272): who in a house may approve an unlock+- [three.ws Drive](#sec-150): the same agent, voice-first, in a car----<a id="sec-272"></a>+<a id="sec-281"></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-244).)+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-250).)## The five steps every generation takes@@ -66099,17 +69591,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-315) or plain HTTP, and other agents pay per call with USDC over [x402](#sec-624), 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-326) or plain HTTP, and other agents pay per call with USDC over [x402](#sec-645), 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-244)+- The full technical breakdown: [the Forge pipeline deep dive](#sec-250)----<a id="sec-273"></a>+<a id="sec-282"></a>> **Source:** `docs/how-it-works.md` · [↑ table of contents](#table-of-contents)@@ -66117,7 +69609,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-108). For the actual JS API, see [JavaScript API](#sec-296) and [REST API](#sec-104). This document zooms out to *how it all fits together*.+For the full deep dive on internals, see [Architecture overview](#sec-109). For the actual JS API, see [JavaScript API](#sec-307) and [REST API](#sec-105). This document zooms out to *how it all fits together*.---@@ -66164,10 +69656,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-301) 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-312) 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-065).-- **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-206) and [Solana agents](#sec-455).-- **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-204).+- **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-211) and [Solana agents](#sec-473).+- **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-209).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.@@ -66200,7 +69692,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-104), 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-105), 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.---@@ -66208,8 +69700,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-149).-- **Selfie capture** — upload a photo, get a rigged 3D version of yourself in ~60 seconds. See [avatar-creation.md](#sec-118).+- **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-153).+- **Selfie capture** — upload a photo, get a rigged 3D version of yourself in ~60 seconds. See [avatar-creation.md](#sec-121).- **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`.@@ -66237,7 +69729,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-206) and [solana.md](#sec-455) for the registration flows.+See [erc8004.md](#sec-211) and [solana.md](#sec-473) for the registration flows.---@@ -66247,7 +69739,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-133). Subscriptions auto-issue an x402 API key via the marketplace entitlement service.+- **AWS Marketplace** — enterprise subscriptions billable through AWS. See [aws-marketplace.md](#sec-136). 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.@@ -66260,27 +69752,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-580) |+| A character in Notion / Webflow / Framer | An iframe widget from [Widget Studio](#sec-601) || 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-296) |+| A character that controls a scene from page events | The JS API (`agent.say()`, `agent.ask()`) — see [js-api.md](#sec-307) || Programmatic avatar viewing/creation in your own app | `@three-ws/avatar` |-| An on-chain identity for your AI | [ERC-8004](#sec-206) or [Solana](#sec-455) |-| A paid API anyone (including agents) can call | [x402 monetization](#sec-624) |-| Multiple agents in one scene | `<agent-stage>` — see [multi-agent.md](#sec-338) |-| To register a domain (e.g. ENS) as agent identity | [register-onchain.md tutorial](#sec-530) |+| An on-chain identity for your AI | [ERC-8004](#sec-211) or [Solana](#sec-473) |+| A paid API anyone (including agents) can call | [x402 monetization](#sec-645) |+| Multiple agents in one scene | `<agent-stage>` — see [multi-agent.md](#sec-349) |+| To register a domain (e.g. ENS) as agent identity | [register-onchain.md tutorial](#sec-550) |---## What's next-- **[Architecture overview](#sec-108)** — full internals+- **[Architecture overview](#sec-109)** — full internals- **[Agent system](#sec-065)** — runtime, skills, memory, emotion-- **[Layers](#sec-301)** — the four-layer contract in detail-- **[Quick start](#sec-414)** — go from zero to a living embed in under 10 minutes+- **[Layers](#sec-312)** — the four-layer contract in detail+- **[Quick start](#sec-429)** — go from zero to a living embed in under 10 minutes----<a id="sec-274"></a>+<a id="sec-283"></a>> **Source:** `docs/huggingface-3d-ai-agent-platform.md` · [↑ table of contents](#table-of-contents)@@ -66572,7 +70064,135 @@ Hugging Face is where model claims get checked, and the check is cheap: open the----<a id="sec-275"></a>+<a id="sec-284"></a>++> **Source:** `docs/huggingface-agent-feedback-loop.md` · [↑ table of contents](#table-of-contents)++---+venue: Hugging Face community article (huggingface.co/blog/three-ws/...)+account: three-ws (organization)+suggested_title: "Generate, look, grade, iterate: closing the feedback loop for agentic 3D"+description: "Third three.ws article for the Hugging Face community. Text-to-3D has been one-shot since it existed, because the model that generates an asset cannot perceive it. This is the loop we built to fix that: rendering results back into the model's own modality, a mechanical physics-readiness grade, structural diffing between iterations, and universal retargeting, all on open models running on our own GPUs."+tags: [3d, agents, mcp, open-models, evaluation]+house_rules: |+ Hugging Face blog rules as applied to our previous two articles: keep it AI-focused.+ No coin, exchange, listing, or token content anywhere in this piece. Partner status+ may be stated factually where it is technically relevant, never as promotion.+status: draft, owner approval required before posting (external-channel gate in CLAUDE.md)+---++# Generate, look, grade, iterate: closing the feedback loop for agentic 3D++This is the third piece we have published here. The [first](https://huggingface.co/blog/three-ws/giving-ai-agents-bodies-and-wallets) argued that agents need bodies. The [second](https://huggingface.co/blog/three-ws/building-3d-ai-agents-end-to-end) walked the whole stack end to end. This one is about a single missing primitive that we think holds back every agentic 3D pipeline, ours included, and what happened when we built it.++**The problem in one sentence: every text-to-3D API in existence answers with a URL to a binary file, and a language model cannot read a binary file.**++That is why agentic 3D has been stuck at one shot since it began. The agent spends GPU time, receives a link, and has no way to tell a clean mesh from a melted one. It hands the link to a human and hopes. There is no error signal, so there is no loop, so there is no agency: just a very expensive random draw.++Everything below is Apache-2.0 at [github.com/nirholas/three.ws](https://github.com/nirholas/three.ws), and every endpoint marked free is keyless.++## 1. Let the model look at what it made++The fix is embarrassingly simple once you say it out loud: render the result back into a modality the model actually perceives.++Our `look_at_model` tool renders a GLB from several angles and returns the frames as **MCP image content blocks**, so a multimodal client renders them straight into the conversation. Alongside the frames it returns the geometry facts (triangle count, bounds, material count, whether it is skinned) and a plain-language reading of them.++Three ways in, because different consumers want different shapes:++| You are | Use | You get |+|---|---|---|+| An MCP client | `look_at_model` on `https://three.ws/api/mcp-studio` | frames as image blocks, rendered inline |+| A Node program | `@three-ws/see` | `see(url)` returns views, stats, notes |+| Anything with HTTP | `POST https://three.ws/api/3d/look` | JSON with a frame URL per angle |++```bash+curl -s -X POST https://three.ws/api/3d/look \+ -H 'content-type: application/json' \+ -d '{"src":"https://three.ws/avatars/cesium-man.glb"}'+```++What changes is not the quality of any single generation. What changes is that the agent can now **judge** one, which means it can decide to refine, and every refinement is its own version with its own artifacts. Generate, look, judge, refine, look again.++The generalisation is the part worth taking away, and it is not about 3D at all: **any tool that hands an agent a binary is a tool that needs a companion that renders it into the agent's own modality.** Ours was a mesh. Yours might be a PDF, a spreadsheet, an audio file, a CAD assembly, a compiled binary. If your agent cannot perceive its own output, it is not iterating, it is guessing.++## 2. A grade, so "good" means something mechanical++Perception gets you taste. It does not get you a specification.++A renderer forgives almost everything; a rigid-body solver forgives nothing. A mesh that looks perfect on screen can sink through the floor in MuJoCo, behave as if hollow in Bullet, or turn out to be a metre tall because the generator fitted it to a unit box and nothing in the file says so. Every robotics, game-physics and world-model pipeline rediscovers those defects by hand, one asset at a time.++So we published the claim, mechanically, free, and CC0:++```bash+curl "https://three.ws/api/sim-readiness?src=https://three.ws/avatars/cesium-man.glb"+```++Four verdicts:++| Verdict | Meaning |+|---|---|+| `simulation_ready` | Closed surface, consistent winding, positive volume, real-world extents. The only verdict that licenses trusting the reported mass. |+| `needs_scale` | Geometry is sound, only the units are missing. Multiply; mass properties scale with it. |+| `needs_repair` | Open, non-manifold, or inconsistently wound. Mass is reported but unreliable. |+| `unusable` | No triangles, or zero volume. |++A fifth value, `unreadable`, covers bytes that are not binary glTF 2.0 at all, kept deliberately distinct: one is a broken file, the other is a valid file with nothing to simulate. Verdicts are content-addressed by the file's SHA-256, so identical bytes always get an identical grade and caching is trivially correct.++Two design decisions I would defend to anyone building evaluation infrastructure:++**Free, permanently.** It is also exposed as a free tool on our *paid* MCP server, which is a deliberate exception to that server's pricing. An assurance check that costs money is a check nobody runs, and a check nobody runs prevents nothing.++**A spec, not a service.** [`specs/SIM_READINESS.md`](https://github.com/nirholas/three.ws/blob/main/specs/SIM_READINESS.md) is CC0 and the grader is a pure function you can vendor. If this becomes a standard that other people implement and we never see the traffic, that is the successful outcome, not a lost one. The glTF ecosystem has no machine-readable claim about physical usability, and that hole gets filled either by a shared spec or by fifty incompatible internal scripts.++## 3. Diff, so "changed" means something structural++Between iterations, "did that actually change anything" gets asked constantly, and comparing two viewers by eye is a bad instrument at any scale.++`@three-ws/glb-diff` answers structurally: node graph, meshes, primitives, materials, textures, skins, animations, and what moved. It began as an internal debugging tool for the refine loop, and it is now the thing we reach for whenever a model is subtly wrong. If your pipeline mutates glTF anywhere (optimisation, retexturing, decimation, rigging), it is worth wiring in.++Together with the grade, this is what turns a refine loop into something you can actually evaluate: perception says whether it looks right, the grade says whether it is usable, and the diff says whether the last change did anything at all.++## 4. Retargeting, because the rig is never yours++The other half of "agentic 3D" is that the asset has to *do* something, and animation is where pipelines quietly fail.++Our constraint is that we never see the model first. It might come from our own lanes, from Mixamo, VRoid, Daz, Unreal, or a Blender export from 2019. So instead of a curated allowlist of supported rigs, we canonicalise bone names, then retarget onto the canonical set. The mapping covers Mixamo, Unreal, VRM and VRoid, VRM 1.0, Daz/Genesis, MakeHuman, Blender `.L`/`.R` and simple `shoulderL` conventions, and a new convention is one mapping entry plus a test, not a new code path. A model that genuinely cannot be skeleton-driven falls back to a default rig rather than a bind-pose T-pose, because a T-pose reads as a bug to every user and as "unsupported" to none of them.++It is published on its own as `@three-ws/retarget`.++## 5. The models underneath, and the fleet that serves them++None of this is interesting without generation that works, and all of ours is open models on hardware we run:++- **TRELLIS** for native single-hop image to 3D, taking both user photos and the synthesized view our text lane produces.+- **Hunyuan3D** for high-poly image-conditioned reconstruction, poly-budget aware.+- **TripoSG** for sketch to 3D, and **TripoSR** in the family around it.+- Plus the pipeline workers: rigging, remeshing, texturing, segmentation, stylization, background removal, avatar reconstruction from a photo, text to motion, video to motion, video to scene, and sign-language synthesis.++Thirty-two workers, most published as Docker images. They run as individual GPU services (NVIDIA L4s, plus one RTX PRO 6000 Blackwell for the heaviest lane), each speaking the same task shape, each with a failover chain so an unavailable model degrades quality rather than failing the request.++Three production notes that will save someone a day:++**Decode meshopt before anything reads geometry.** Most of our avatars ship with `EXT_meshopt_compression`. Every server-side consumer that reads geometry (ours are Python and use trimesh) must decode first, and the failure is confusing because the file loads perfectly in every browser viewer you test with.++**Model end-of-life is a silent outage.** When an upstream family reached end of life on one of our free rungs, the rung answered `410`. The chain fell through correctly, but the real lesson was that a scheduled job should diff your hardcoded model ids against the live catalogues so you learn before users do.++**Never let a failover chain have an empty rung.** Two rungs in our text chain are keyless on purpose, so the bottom of the chain always exists even when every keyed provider is unset or throttled.++## 6. What we would like the community to take, argue with, or fork++- **`look_at_model` is the pattern, not the product.** Render your agent's output into your agent's modality. This costs a weekend and changes what your pipeline can do.+- **The readiness spec is CC0 and we want implementations, not traffic.** If you ship assets into a simulator, tell us where the four verdicts are wrong.+- **Retargeting without an allowlist is achievable**, and the mapping table wants conventions we have not hit.+- **Publish the negative results.** We evaluated approaches that did not survive contact (including exposing our agent as a smart-home device) and published the reasoning, and every time we have done that somebody has arrived with a better argument.++Free to try, no account and no key: [three.ws/forge](https://three.ws/forge) for generation, `https://three.ws/api/mcp-studio` for the eleven-tool MCP server, and the [three-ws organization](https://huggingface.co/three-ws) here for the avatar model repo and the viewer Space.++three.ws is an NVIDIA Inception member and an IBM Business Partner; both are programme designations rather than endorsements, and neither company has reviewed this article.++---++<a id="sec-285"></a>> **Source:** `docs/huggingface.md` · [↑ table of contents](#table-of-contents)@@ -66584,7 +70204,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-122), [the `<agent-3d>` web component](#sec-578), [agent wallets](#sec-074), [x402](#sec-114)+- **Related surfaces:** [the avatar pipeline](#sec-125), [the `<agent-3d>` web component](#sec-599), [agent wallets](#sec-074), [x402](#sec-117)## Published articles@@ -66597,7 +70217,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-122), [animation retargeting](#sec-097), [agent wallets](#sec-074), [autonomous x402](#sec-114)+- **Code it documents:** [the avatar pipeline](#sec-125), [animation retargeting](#sec-097), [agent wallets](#sec-074), [autonomous x402](#sec-117)### Inside three.ws: The Open-Source Stack That Gives AI Agents a Body, a Brain, a Wallet, and a Job@@ -66605,10 +70225,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-274)+- **Source draft:** [`docs/huggingface-3d-ai-agent-platform.md`](#sec-283)- **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-122), [the 3D asset pipeline](#sec-002), [the agent brain](#sec-140), [the agent runtime](#sec-058), [the partner ecosystem](#sec-368)+- **Code it documents:** [the avatar pipeline](#sec-125), [the 3D asset pipeline](#sec-002), [the agent brain](#sec-144), [the agent runtime](#sec-058), [the partner ecosystem](#sec-381)## Published models@@ -66628,7 +70248,15 @@ 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-121).+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-124).++## In draft++| Draft | Subject |+|---|---|+| [huggingface-agent-feedback-loop.md](#sec-284) | 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.## Publishing checklist@@ -66645,11 +70273,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-074) and [the payments](#sec-114).+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-074) and [the payments](#sec-117).----<a id="sec-276"></a>+<a id="sec-286"></a>> **Source:** `docs/i18n.md` · [↑ table of contents](#table-of-contents)@@ -67091,7 +70719,7 @@ clearing silently-English values out of a shipped catalog.----<a id="sec-277"></a>+<a id="sec-287"></a>> **Source:** `docs/ibm-community-article.md` · [↑ table of contents](#table-of-contents)@@ -67211,7 +70839,7 @@ The platform repository is public at [github.com/nirholas/three.ws](https://gith----<a id="sec-278"></a>+<a id="sec-288"></a>> **Source:** `docs/ibm-community-blog-meetup-jessica.md` · [↑ table of contents](#table-of-contents)@@ -67272,7 +70900,7 @@ See you Friday at 8 AM Pacific. I will be the one asking the skeptical questions----<a id="sec-279"></a>+<a id="sec-289"></a>> **Source:** `docs/ibm-community-governed-agents-post.md` · [↑ table of contents](#table-of-contents)@@ -67499,6 +71127,7 @@ You get either a finished GLB or a job handle with an ETA and a watch URL. Riggi**2. Check that the model is actually usable** before you build anything on top of it:+<!-- runnable: 400 <your glb url> is a placeholder; a real GLB URL answers 200 -->```bashcurl "https://three.ws/api/sim-readiness?src=<your glb url>"```@@ -67518,7 +71147,7 @@ Four verdicts, and the useful distinction is between `needs_scale` (geometry isThere are wrappers for React, a floating concierge widget, a page narrator that reads the page it lives on, a walk companion, and a guided-tour agent, all as paste-in snippets. If you would rather scaffold the whole thing locally, `npx @three-ws/create-agent` goes from a sentence to a rigged, animated agent in one command.-A note on animation, because it is the step people underestimate: **there is no rig allowlist.** Bone names are canonicalised across Mixamo, Avaturn, Unreal, VRM and VRoid, VRM 1.0, Daz/Genesis, MakeHuman, Blender `.L`/`.R`, and simple `shoulderL` conventions, then clips are retargeted onto whatever came in, legs included. A model that genuinely cannot be skeleton-driven falls back to a default rig rather than standing in a bind-pose T-pose. That logic is published on its own as [`@three-ws/retarget`](https://www.npmjs.com/package/@three-ws/retarget).+A note on animation, because it is the step people underestimate: **there is no rig allowlist.** Bone names are canonicalised across Mixamo, Unreal, VRM and VRoid, VRM 1.0, Daz/Genesis, MakeHuman, Blender `.L`/`.R`, and simple `shoulderL` conventions, then clips are retargeted onto whatever came in, legs included. A model that genuinely cannot be skeleton-driven falls back to a default rig rather than standing in a bind-pose T-pose. That logic is published on its own as [`@three-ws/retarget`](https://www.npmjs.com/package/@three-ws/retarget).---@@ -67637,7 +71266,7 @@ The question I would most like this group to argue about: **is a classifier the----<a id="sec-280"></a>+<a id="sec-290"></a>> **Source:** `docs/ibm-community-live-reaction-jessica.md` · [↑ table of contents](#table-of-contents)@@ -67648,7 +71277,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-278), has the event details if you have not joined yet;+Friday](#sec-288), 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@@ -67689,7 +71318,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-594) is a separate, distinct campaign and+ `@nichxbt` X copy in [event-x-posts.md](#sec-615) 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.@@ -67703,13 +71332,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-284) as a new discussion+- Once posted, add it to the catalog in [ibm-community.md](#sec-294) 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-281"></a>+<a id="sec-291"></a>> **Source:** `docs/ibm-community-recap-jessica.md` · [↑ table of contents](#table-of-contents)@@ -67718,8 +71347,8 @@ Full recap once the day wraps._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-278) and continued mid-day with [LIVE at the Meetup: My-Honest Take So Far](#sec-280). Header image: reuse+Friday](#sec-288) and continued mid-day with [LIVE at the Meetup: My+Honest Take So Far](#sec-290). 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._@@ -67848,14 +71477,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-284) as the group's next+- Once posted, add it to the catalog in [ibm-community.md](#sec-294) 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-282"></a>+<a id="sec-292"></a>> **Source:** `docs/ibm-community-recap-nichxbt.md` · [↑ table of contents](#table-of-contents)@@ -67864,7 +71493,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-280) and [recap](#sec-281)+reaction](#sec-290) and [recap](#sec-291)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),@@ -68003,13 +71632,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-284) as the group's next+- Once posted, add it to the catalog in [ibm-community.md](#sec-294) 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-283"></a>+<a id="sec-293"></a>> **Source:** `docs/ibm-community-thread.md` · [↑ table of contents](#table-of-contents)@@ -68128,13 +71757,13 @@ _Questions, skepticism, and feature requests all welcome below. The skeptical on----<a id="sec-284"></a>+<a id="sec-294"></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-287) 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-297) 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.@@ -68180,7 +71809,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-278).+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-288).### 4. The First Three.ws User Group Meetup: How It Actually Went@@ -68231,7 +71860,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-283).+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-293).### 2. Community Friday August 7,2026 - Inside three.ws: Join Us on the $THREE Server at three.ws/play@@ -68302,17 +71931,17 @@ A first-run walkthrough of the Forge from a user's perspective, no account, wall| Draft | Subject ||---|---|-| [ibm-community-governed-agents-post.md](#sec-279) | Granite Guardian as an action veto once agents can control a home, ride in a car, and order a manufactured object; the watsonx.ai surface map; the quarter's shipping recap; and the group's next event question |+| [ibm-community-governed-agents-post.md](#sec-289) | Granite Guardian as an action veto once agents can control a home, ride in a car, and order a manufactured object; the watsonx.ai surface map; the quarter's shipping recap; and the group's next event question |-The draft carries the framing rules from [ibm.md](#sec-287) in its frontmatter, including which section to cut first if the group's no-crypto-cluster rule is applied strictly.+The draft carries the framing rules from [ibm.md](#sec-297) in its 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-287).+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-297).----<a id="sec-285"></a>+<a id="sec-295"></a>> **Source:** `docs/ibm-next-event.md` · [↑ table of contents](#table-of-contents)@@ -68322,7 +71951,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-287).+[ibm.md](#sec-297).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@@ -68354,13 +71983,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-379) | Shipped |-| Free commemorative wearable granted to everyone present during a live event, never purchasable afterwards | [event-souvenirs.md](#sec-234) | 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-392) | Shipped |+| Free commemorative wearable granted to everyone present during a live event, never purchasable afterwards | [event-souvenirs.md](#sec-239) | 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-294) | Shipped |+| AR: place a 3D agent in a real room, visible only to people physically near it | `/irl`, [irl.md](#sec-304) | 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** |@@ -68515,7 +72144,7 @@ losing fine.### Framing rules that apply to every word of this-The distinctions in [ibm.md](#sec-287) hold without exception. The public Granite showcase is+The distinctions in [ibm.md](#sec-297) 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@@ -68536,7 +72165,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-379). A config change+ `public/event.json` per [play-live-events.md](#sec-392). 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@@ -68763,7 +72392,7 @@ copied by a competitor with a text box.----<a id="sec-286"></a>+<a id="sec-296"></a>> **Source:** `docs/ibm-x402-mcp.md` · [↑ table of contents](#table-of-contents)@@ -68785,9 +72414,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-287)**.+credentials-based `@three-ws/ibm-watsonx-mcp` connector) see **[docs/ibm.md](#sec-297)**.For the x402 protocol primitives used elsewhere on the platform see-**[docs/x402.md](#sec-624)**.+**[docs/x402.md](#sec-645)**.---@@ -69105,7 +72734,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-317) alongside its schema, example input, and+[x402 Bazaar](#sec-328) alongside its schema, example input, andexample output. Agents can find Granite tools by capability and price withoutknowing the server up front.@@ -69126,16 +72755,16 @@ Catalog/listing copy is maintained in## See also-- [docs/ibm.md](#sec-287) — the full IBM Granite / watsonx integration and showcase-- [docs/x402.md](#sec-624) — the x402 payment protocol on three.ws-- [docs/mcp.md](#sec-318) — wiring MCP servers into a client-- [docs/mcp-x402-bazaar.md](#sec-317) — x402 service discovery+- [docs/ibm.md](#sec-297) — the full IBM Granite / watsonx integration and showcase+- [docs/x402.md](#sec-645) — the x402 payment protocol on three.ws+- [docs/mcp.md](#sec-329) — wiring MCP servers into a client+- [docs/mcp-x402-bazaar.md](#sec-328) — 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-287"></a>+<a id="sec-297"></a>> **Source:** `docs/ibm.md` · [↑ table of contents](#table-of-contents)@@ -69143,7 +72772,7 @@ 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-273); for the agent brain abstraction see [Agent system](#sec-065); 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-282); for the agent brain abstraction see [Agent system](#sec-065); for the standalone connector see [the MCP server](#mcp-server-three-wsibm-watsonx-mcp) below.---@@ -69170,7 +72799,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-285).+division of labor, and the engineering plan are in [ibm-next-event.md](#sec-295).No date is set: that is the first decision the proposal asks for.### Community event (held 2026-06-23)@@ -69196,7 +72825,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-284). 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-294). 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.@@ -69445,7 +73074,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-318) for wiring MCP servers into a client.+It reads the same `WATSONX_*` environment variables documented above. See the [MCP guide](#sec-329) for wiring MCP servers into a client.---@@ -69492,16 +73121,16 @@ Unit tests for the same paths live in [`tests/`](../tests) (`granite-oracle`, `a## See also-- [How it works](#sec-273) — the platform mental model+- [How it works](#sec-282) — the platform mental model- [Agent system](#sec-065) — the brain abstraction Granite plugs into-- [IBM Granite x402 MCP](#sec-286) — pay-per-call Granite for agents (USDC, no IBM account)-- [MCP](#sec-318) — wiring MCP servers into a client-- [REST API](#sec-104) — the full endpoint reference-- [Configuration](#sec-169) — all environment variables+- [IBM Granite x402 MCP](#sec-296) — pay-per-call Granite for agents (USDC, no IBM account)+- [MCP](#sec-329) — wiring MCP servers into a client+- [REST API](#sec-105) — the full endpoint reference+- [Configuration](#sec-173) — all environment variables----<a id="sec-288"></a>+<a id="sec-298"></a>> **Source:** `docs/image-to-3d.md` · [↑ table of contents](#table-of-contents)@@ -69596,14 +73225,14 @@ console.log(job.glb_url);## Related-- [Forge](#sec-245) is the full text-and-image-to-3D surface with every mode and engine.-- [Avatar reconstruction](#sec-123) and [avatar creation](#sec-118) cover the face-to-avatar pipeline behind [/create/selfie](https://three.ws/create/selfie).+- [Forge](#sec-251) is the full text-and-image-to-3D surface with every mode and engine.+- [Avatar reconstruction](#sec-126) and [avatar creation](#sec-121) 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-289"></a>+<a id="sec-299"></a>> **Source:** `docs/in-game-economy.md` · [↑ table of contents](#table-of-contents)@@ -69732,11 +73361,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-624) and is surfaced publicly at [/fits](https://three.ws/fits).+[x402](#sec-645) 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-234)** are+boutique deliberately cannot see: **[event souvenirs](#sec-239)** 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@@ -69862,16 +73491,16 @@ every number in this system.## Next-- **[Earn and spend in /play](#sec-503)** walks the+- **[Earn and spend in /play](#sec-523)** 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-158)** covers the worlds themselves: how a coin+- **[Coin communities](#sec-162)** covers the worlds themselves: how a coinbecomes a walkable 3D space.----<a id="sec-290"></a>+<a id="sec-300"></a>> **Source:** `docs/inference-node-operator.md` · [↑ table of contents](#table-of-contents)@@ -70145,7 +73774,7 @@ signature, and the artifact hash all check out.----<a id="sec-291"></a>+<a id="sec-301"></a>> **Source:** `docs/integrations.md` · [↑ table of contents](#table-of-contents)@@ -70165,7 +73794,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-204) and [Widgets](#sec-581),+per-method references live in [Embedding](#sec-209) and [Widgets](#sec-602),and this doc is the map that points you to the right one.## How it works@@ -70191,7 +73820,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-318).+ assistant can render, speak, gesture, and emote your agents. See [MCP](#sec-329).## Walkthrough@@ -70309,15 +73938,15 @@ for the full table.## Related-- [Embedding Guide](#sec-204): the full per-method reference (web component, iframe, oEmbed)-- [Widget Types](#sec-581): every widget type and how to configure one-- [Embody](#sec-205): giving an agent a body in more contexts-- [MCP](#sec-318): the avatar MCP server for AI assistants+- [Embedding Guide](#sec-209): the full per-method reference (web component, iframe, oEmbed)+- [Widget Types](#sec-602): every widget type and how to configure one+- [Embody](#sec-210): giving an agent a body in more contexts+- [MCP](#sec-329): the avatar MCP server for AI assistants- Pages: [/integrations](https://three.ws/integrations), [/widgets](https://three.ws/widgets)----<a id="sec-292"></a>+<a id="sec-302"></a>> **Source:** `docs/introduction.md` · [↑ table of contents](#table-of-contents)@@ -70528,7 +74157,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-414).+For a full step-by-step walkthrough, see the [Quick Start guide](#sec-429).---@@ -70536,26 +74165,26 @@ For a full step-by-step walkthrough, see the [Quick Start guide](#sec-414).Once you have the basics working, the following guides go deeper:-- **[Quick Start](#sec-414)** — step-by-step from zero to a talking agent-- **[Embedding Guide](#sec-204)** — all attributes, modes, events, and the JS API-- **[Widget Types](#sec-581)**, the five general-purpose widgets in depth (the other five live in [Widget Studio](https://three.ws/studio))+- **[Quick Start](#sec-429)** — step-by-step from zero to a talking agent+- **[Embedding Guide](#sec-209)** — all attributes, modes, events, and the JS API+- **[Widget Types](#sec-602)**, the five general-purpose widgets in depth (the other five live in [Widget Studio](https://three.ws/studio))- **[Agent System Overview](#sec-065)** — runtime, skill registry, memory, emotion system- **[Manifest Reference](#sec-056)** — full JSON schema with examples-- **[REST API](#sec-104)** and **[JavaScript API](#sec-296)** — backend and in-browser surfaces+- **[REST API](#sec-105)** and **[JavaScript API](#sec-307)** — backend and in-browser surfaces- **[Agents vs. avatars](#sec-075)** — 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-293"></a>+<a id="sec-303"></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-431), it is a shell around the live web product rather+[Seeker app](#sec-447), 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@@ -70646,13 +74275,13 @@ and `/widget*` entries (they exist to render inside someone else's page).## Related-- [three.ws on Solana Seeker](#sec-431): the Android app+- [three.ws on Solana Seeker](#sec-447): 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-294"></a>+<a id="sec-304"></a>> **Source:** `docs/irl.md` · [↑ table of contents](#table-of-contents)@@ -70696,7 +74325,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-107) (`GET /api/ar?…&kind=avatar`) and the+from the [AR launch page](#sec-108) (`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.@@ -70710,6 +74339,8 @@ 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-108) 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@@ -70729,6 +74360,14 @@ deletes it after an hour of never appearing.The **Share** button captures your camera feed and the placed agent as one photo, then, if you're the one who placed the pin, turns it into a permanent link at `three.ws/irl/s/<token>` instead of a bare file. Paste that link into X, iMessage, or Discord and it unfurls as the actual photo, with a "Place your own agent" button back to /irl. The link never carries a coordinate: only the agent's name and caption (if any) ever appear on the card, and it only exists for pins you left public — unpublishing a pin, or a pin under moderation review, is never shareable. If you tap Share before placing anything (no pin yet), it falls back to the plain native share sheet / photo download, same as before.+### Invite people with a visit link and a sign++A 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-108) 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-306).+## Money DropsReal value, escrowed at a real-world spot. A drop holds SOL, USDC, or $THREE in a fresh per-drop escrow wallet, funded on-chain by its creator. Claiming requires physically walking up: the same presence proof that gates every IRL read gates the claim, and the release lands on-chain in the claimer's own wallet. Drops can require a quiz answer, support multiple claims, and auto-refund the creator on expiry.@@ -70775,7 +74414,7 @@ The rollup is served at `GET /api/irl/analytics` (admin-gated via `x-ops-secret`----<a id="sec-295"></a>+<a id="sec-305"></a>> **Source:** `docs/irl/THREAT-MODEL.md` · [↑ table of contents](#table-of-contents)@@ -70929,15 +74568,119 @@ in a way that drops legitimate discovery, update this file in the same change.----<a id="sec-296"></a>+<a id="sec-306"></a>++> **Source:** `docs/irl/street-demo.md` · [↑ table of contents](#table-of-contents)++# Run an IRL street demo: drop an agent at a real spot, let strangers walk up++This is the runbook for showing IRL to people who have never heard of three.ws: you place a 3D AI agent at a real location, put a sign there, and anyone who scans it sees the agent standing on that spot through their phone camera, taps it, talks to it out loud, and can stand it on their own floor in AR. It was written for a demo in San Francisco, and everything in it applies to any city.++Nothing here needs an app or an account on the visitor's side. The owner needs a signed-in three.ws account so the pin is permanent.++---++## What the visitor experiences++1. They scan the sign. It opens `three.ws/irl?pin=<id>` in their phone browser.+2. IRL asks for camera and location (and motion, on iPhone, which takes one extra tap). A banner at the top says **"You're here to meet <agent name>"** and that the agent appears within 60 m of the spot.+3. Standing within range, the agent appears in their camera view, playing its idle animation and turning to look at them. Its name label flashes and its card opens on its own.+4. The card leads with **Talk** and **View in AR**, then shows the agent's bio, on-chain reputation, its **Solana wallet chip**, a **Tap to tip in person** panel (a Solana Pay QR plus an "Open in wallet" deep link), any paid x402 services, a message box, and **View profile**.+5. **Talk** opens a conversation with the agent standing in front of them. They hold the mic and speak (or type). The reply is in the agent's persona, spoken aloud in its voice, and the model's mouth moves with the audio. Pressing the mic while it is speaking interrupts it.+6. **View in AR** stands the agent on their real floor. iPhone opens ARKit Quick Look with the idle clip baked in; the Quick Look banner reads "Talk to <name>" and tapping it brings them back to the card with the conversation open. Android with ARCore enters a WebXR session that anchors this agent to the detected floor (tap to place, pinch to size). Anything else opens the AR launcher (`/api/ar`) in a new tab.++Anyone who opens the link from somewhere else sees only the agent's name and a prompt to walk to the spot. The link never carries a coordinate, and the nearby read is presence-gated, so posting the link publicly is safe. See [How location works on IRL](/irl-privacy).++---++## Before the day++### 1. Pick the agent++Use a real agent from your account, not the anonymous companion. The card's wallet chip, tip QR, reputation and services all come from the agent identity, and the pin only links to one when you place it signed in with that agent selected.++- Check the agent's profile page (`/agents/<id>`): if it shows a Solana wallet chip there, the IRL card will show the same chip and the tip QR.+- **An agent wallet is provisioned on demand, not automatically.** A brand-new agent has none, and `GET /api/agents/<id>/solana` answers `"wallet": null` for it. The IRL card then renders with no wallet chip and no tip QR, which removes the part of the demo people react to most. Create one from the agent's wallet panel (or `POST /api/agents/<id>/solana` while signed in as the owner) and confirm the same endpoint returns an address before you print anything.+- If you want a paid interaction in the demo, give the agent a priced service from `/dashboard/monetize`. It appears on the card as a **Pay via x402** action.+- A humanoid rigged body plays the idle animation and gaze in the camera view. Any of the rigs the universal retargeter maps work (Mixamo, VRM, and the rest); a non-humanoid prop stands still.++### 2. Pick the spot++GPS decides whether people see the agent, so the spot matters more than anything else in this runbook.++- **Open sky.** Plazas, parks, waterfronts. In San Francisco that means places like the Embarcadero, the Ferry Building plaza, Dolores Park, Crissy Field, or the top of a park hill. Avoid narrow downtown streets between tall buildings: multipath GPS there can drift 50 m or more, and the nearby read caps at 60 m.+- **Somewhere people can stop.** Visitors need to stand still for a few seconds while GPS settles and the model loads.+- **Cellular signal.** The agent's model is fetched over the visitor's own connection.++The card shows the pin's placement accuracy, and the ring under the agent goes amber above 25 m. If you see amber when you place it, move to clearer sky and place again.++### 3. Place the pin++On your phone, signed in, at the spot:++1. Open [/irl](/irl), grant camera, location, and motion.+2. Pick the agent (the avatar picker under the name).+3. Aim at the ground, tap **Move here** to set it down, then **Pin here**. On Android with ARCore, **Place in AR** anchors it to the detected floor with a pinch to size it; on iPhone, **Pin here** is the placement path.+4. Give it a caption. It shows on the sign and on the card.++Signed-in pins are permanent until you remove them. If you cannot be at the spot beforehand, **Place on map** in /irl drops it at a point you choose, and **Move on map** in the dashboard relocates it later.++The full placement walkthrough is [Place a 3D agent in your real environment](/docs/tutorials/place-agent-irl).++### 4. Print the sign++Open [/dashboard/irl-placements](/dashboard/irl-placements), find the pin, and tap **Visit link**. The modal shows the QR, the link to copy, and **Print a sign**, which opens `/irl/sign?pin=<id>`: the agent's name, thumbnail and bio, the QR, three steps for the visitor, and the link in plain text. Choose **Sign** (landscape) or **Poster** (a large QR for a vertical sheet) and print. A laminated Letter sheet at chest height reads fine from two metres.++Test the sign with your own phone before you leave: scan it, walk 70 m away, confirm the banner says the agent is out of range, walk back, confirm the card opens.++---++## On the day++- **Your phone is the demo screen too.** The dashboard's **View in IRL** opens the same visit link, so you can show the walk-up while a visitor does it.+- **Talk through the three taps:** scan, allow, look around. The banner carries the rest.+- **Let them talk first.** Hand the phone over with the card open and say "hold the mic and ask it anything". The agent answers out loud in its persona; that is the moment people remember. Give the agent a persona and a cloned voice beforehand (`/agents/<id>`, Brain Studio and the voice clone in talk mode) so it sounds like itself on the street.+- **Show the tip.** Expand **Tap to tip in person**, and let someone scan the Solana Pay QR with Phantom or Solflare. The agent's wallet is a real address; a tip lands on-chain.+- **Show it on the floor.** **View in AR** is the moment people photograph: Quick Look on an iPhone, a floor-anchored WebXR session on an Android phone with ARCore.+- **Volume and noise.** Replies play through the phone speaker. On a loud street, hold the phone up or use a small speaker; typed turns work when speech recognition cannot hear.+- **Messages and taps land in your dashboard.** The placements page lists every message, tap and pay under the pin, and the inbox lets you reply. `GET /api/irl/analytics` (admin) has the rollup afterwards.++---++## Troubleshooting on site++| Symptom | Cause | Fix |+|---|---|---|+| Banner never changes from "You're here to meet" | Visitor is outside 60 m, or their GPS fix is far off | Move to open sky, wait ten seconds, check the accuracy line on the card once it opens |+| "Enable location" chip in the top bar | Location was denied | Tap the chip; on iPhone, Settings > Safari > Location if the prompt is gone |+| Agent appears but does not move | Motion permission not granted (iPhone), or a non-humanoid body | Tap the motion chip; humanoid rigs animate, props do not |+| "View in AR" is missing | The pin has no model URL | Re-place the pin with a hosted avatar from your account |+| Talk shows "Voice input isn't available" | The browser has no speech recognition, or the mic was denied | Type in the box instead; on iPhone allow the microphone when Safari asks, or Settings > Safari > Microphone |+| The agent answers but you hear nothing | The phone is on silent (iPhone honours the mute switch for web audio) or volume is down | Flip the ring/silent switch, raise the volume, tap the mic again |+| The mouth does not move while it speaks | The body has no mouth morphs or jaw bone, or the model is still streaming in | Nothing to fix on site; the agent still talks. Rigs with ARKit or VRM mouth shapes animate |+| Banner says the agent has moved on | The pin expired (anonymous pins last 7 days) or was removed | Place it again signed in and print a fresh sign |+| Visitors see nothing at all, you see the agent | Your device owns the pin; theirs reads nearby only within range | Have them stand where you placed it, not where you are now |++---++## Related++- [IRL overview](/docs/irl): what IRL is, Money Drops, World Lines, the SDK+- [How location works on IRL](/irl-privacy) and the [threat model](/docs/irl/THREAT-MODEL)+- [Place a 3D agent in your real environment](/docs/tutorials/place-agent-irl)+- [AR and WebXR reference](/docs/ar): the device routing behind "View in AR"++---++<a id="sec-307"></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-578) 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-599) instead.-> For the HTTP/REST surface, see [api-reference.md](#sec-104). For the high-level npm SDK, see [sdk.md](#sec-428). For the `<agent-3d>` element attributes, see [web-component.md](#sec-578).+> For the HTTP/REST surface, see [api-reference.md](#sec-105). For the high-level npm SDK, see [sdk.md](#sec-444). For the `<agent-3d>` element attributes, see [web-component.md](#sec-599).---@@ -71276,7 +75019,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-108) for the full folder tree.+See [Architecture overview](#sec-109) for the full folder tree.#### `updateGUI()`@@ -71568,7 +75311,7 @@ window.VIEWER.app.viewer.updateDisplay();----<a id="sec-297"></a>+<a id="sec-308"></a>> **Source:** `docs/knock.md` · [↑ table of contents](#table-of-contents)@@ -71585,7 +75328,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-166) walks on screen wherever you are on+later: your [companion](#sec-170) 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)**.@@ -71593,7 +75336,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-624) with no human in the loop.+ agent pays over [x402](#sec-645) 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.@@ -71670,6 +75413,7 @@ shut door gives, so they cannot tell it was them specifically.### Read the door first+<!-- runnable: 404 the handle answers 200 only while its owner has a door open -->```bashcurl -s 'https://three.ws/api/knock/door?handle=nirholas'```@@ -71804,6 +75548,7 @@ stays with a human. See### Read the answer+<!-- runnable: 404 the id and token are placeholders; a real receipt answers 200 -->```bashcurl -s 'https://three.ws/api/knock/reply?id=<knock id>&token=<receipt token>'```@@ -72008,13 +75753,13 @@ and neither can anyone else outside the three outcomes above.## Related-- [The Companion](#sec-166) is what delivers a knock in person.-- [x402](#sec-624) is the payment protocol the priced lane speaks.-- [Notifications](#sec-342) covers the per-category channel matrix; knocks are their own category, and the avatar channel is on for them by default.+- [The Companion](#sec-170) is what delivers a knock in person.+- [x402](#sec-645) is the payment protocol the priced lane speaks.+- [Notifications](#sec-353) covers the per-category channel matrix; knocks are their own category, and the avatar channel is on for them by default.----<a id="sec-298"></a>+<a id="sec-309"></a>> **Source:** `docs/kol-tracker.md` · [↑ table of contents](#table-of-contents)@@ -72152,8 +75897,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-450)** 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-482)** 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-468)** 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-502)** 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@@ -72171,13 +75916,13 @@ curl 'https://three.ws/api/intel/wallet/<WALLET_ADDRESS>?network=mainnet'## Related-- [Smart Money Radar](#sec-450): reputation earned from graduation outcomes, wallet by wallet-- [Trust primitives](#sec-482): the paid cross-chain reputation read for autonomous agents+- [Smart Money Radar](#sec-468): reputation earned from graduation outcomes, wallet by wallet+- [Trust primitives](#sec-502): 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-299"></a>+<a id="sec-310"></a>> **Source:** `docs/labor-market.md` · [↑ table of contents](#table-of-contents)@@ -72312,7 +76057,7 @@ economy move:----<a id="sec-300"></a>+<a id="sec-311"></a>> **Source:** `docs/launch-usecases.md` · [↑ table of contents](#table-of-contents)@@ -72372,18 +76117,45 @@ The preview drawer has a **reward planner**: route a coin's creator fees to any| **GitHub @user** | 100% to a GitHub account (pump.fun social platform 2). || **X @handle** | 100% to an X / Twitter account (pump.fun social platform 1). || **Wallet / .sol** | 100% to a fixed Solana address or name. |-| **Cashback** | Trading fees return to holders. |-| **Buyback** | Fees auto-buy-back & burn the coin. |-The same generalisation powers the post-launch [fees panel](../public/studio/fees-panel.js):-its recipient box accepts a **GitHub @user**, an **X handle** (`x:@handle`), a-raw **Solana wallet**, or an **owner/repo** to split across contributors. All of-it resolves through one shared resolver ([`api/_lib/github-reward.js`](../api/_lib/github-reward.js),-`resolveSocialReward`) so GitHub and X route identically.+Every target in that table survives the handoff to the launch wizard, which is+the point: a target the launch flow cannot apply is a promise the product does+not keep. (Cashback and buyback used to appear here and were exactly that.+Cashback is a read-only pump.fun pool property with no create-time control, and+the launch panel's buyback slider burns *agent revenue* rather than routing+creator fees, so neither is offered.)++### The `?reward=` handoff++"Launch this coin" builds a deep link to `/launch` carrying the coin identity+**and** the chosen routing:-For reward coins, after the coin graduates you set the GitHub recipient in the-[fees panel](../public/studio/fees-panel.js) (type a `@username` → 100%, or-import a repo's contributors to split) — see the fee-sharing flow.+```+/launch?name=Deepseek+Harness&symbol=DEEPSEEKH&description=…&image=…&reward=github:deepseek-ai+```++`reward` takes one of three forms, and anything else is ignored rather than+blocking a launch:++| Value | Recipient |+|---|---|+| `github:<login>` | A GitHub account, resolved to its three.ws-linked payout wallet. |+| `x:<handle>` | An X account, same resolver. |+| `wallet:<address or name.sol>` | A fixed Solana recipient. |++[`public/launch/launch.js`](../public/launch/launch.js) parses it, the launch+panel shows the routing on the form before the mint ("Creator fees route to+@deepseek-ai on GitHub"), and the moment the coin lands the post-launch+[fees panel](../public/studio/fees-panel.js) mounts on the success screen with+that recipient already filled in at 100%. It is a draft, not an automatic write:+the creator still reviews and signs the split, and a coin that already has+shareholders is never re-seeded.++The same generalisation powers that fees panel on its own: its recipient box+accepts a **GitHub @user**, an **X handle** (`x:@handle`), a raw **Solana+wallet**, or an **owner/repo** to split across contributors. All of it resolves+through one shared resolver ([`api/_lib/github-reward.js`](../api/_lib/github-reward.js),+`resolveSocialReward`) so GitHub and X route identically.## API@@ -72442,13 +76214,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-157) — the underlying launch mechanism.+- [Coin Launches](#sec-161) — 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-301"></a>+<a id="sec-312"></a>> **Source:** `docs/layers.md` · [↑ table of contents](#table-of-contents)@@ -72456,7 +76228,7 @@ GET /api/pump/launch-studio?action=preview&id=github-fresh-breakouts&limit=6three.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-273). For internal module names and paths, see [Architecture overview](#sec-108).+For the overall request flow, see [How three.ws works](#sec-282). For internal module names and paths, see [Architecture overview](#sec-109).---@@ -72546,10 +76318,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-454)).+- **`erc8004/solana-deploy.js`**: Solana counterpart. Metaplex Core asset mint; SPL Memo attestations and reputation live server-side (see [Agent Reputation on Solana](#sec-472)).- **`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-530).+Per-chain registry addresses, ABIs, and helpers ship as `@three-ws/sdk`. ENS attestations are also handled here — see [register-onchain.md](#sec-550).---@@ -72562,7 +76334,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-338).+- **`stage-element.js`**: `<agent-stage>` for hosting multiple agents in one shared scene. See [multi-agent.md](#sec-349).- **`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.@@ -72597,20 +76369,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-147) 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-151) for release history.---## What's next-- **[Architecture overview](#sec-108)** — module-by-module deep dive+- **[Architecture overview](#sec-109)** — module-by-module deep dive- **[Agent system](#sec-065)** — runtime, skills, memory in detail-- **[Embedding](#sec-204)** — the public face of the embed layer-- **[SDK reference](#sec-428)** — `@three-ws/sdk` and friends+- **[Embedding](#sec-209)** — the public face of the embed layer+- **[SDK reference](#sec-444)** — `@three-ws/sdk` and friends----<a id="sec-302"></a>+<a id="sec-313"></a>> **Source:** `docs/likeness-eval.md` · [↑ table of contents](#table-of-contents)@@ -72808,7 +76580,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-120)). A near-noise-floor+([avatar fidelity program](#sec-123)). A near-noise-flooridentity reading is the number that shape of pipeline should produce, and it isconsistent with the geometry-side ISE result.@@ -72850,8 +76622,8 @@ and reason only.## Related-- [Selfie to avatar](#sec-435): the capture flow being measured-- [Avatar fidelity program](#sec-120): the tracks this+- [Selfie to avatar](#sec-451): the capture flow being measured+- [Avatar fidelity program](#sec-123): the tracks thismetric scores- [Realism quality bench](../data/quality-bench/README.md): the sibling harnessfor photorealism@@ -72859,7 +76631,7 @@ and reason only.----<a id="sec-303"></a>+<a id="sec-314"></a>> **Source:** `docs/lipsync.md` · [↑ table of contents](#table-of-contents)@@ -72954,15 +76726,15 @@ tick();## Related-- [Voice Lab](#sec-576): clone a voice and synthesize it, the audio these demos animate.-- [Voice and lipsync tutorial](#sec-549): the full walkthrough, including wiring visemes to an agent body.-- [Talking Avatar Video](#sec-465): the server-rendered alternative for exporting a talking-head clip.+- [Voice Lab](#sec-596): clone a voice and synthesize it, the audio these demos animate.+- [Voice and lipsync tutorial](#sec-569): the full walkthrough, including wiring visemes to an agent body.+- [Talking Avatar Video](#sec-483): the server-rendered alternative for exporting a talking-head clip.- [Animations](#sec-097): the runtime clip registry that plays alongside lipsync.- Pages: [/lipsync](https://three.ws/lipsync), [/lipsync/mic](https://three.ws/lipsync/mic).----<a id="sec-304"></a>+<a id="sec-315"></a>> **Source:** `docs/liquid-glass.md` · [↑ table of contents](#table-of-contents)@@ -72977,7 +76749,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-555).+have. Interaction primitives come from [ui-juice](#sec-575).## What the reference is@@ -73180,13 +76952,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-555), the shared interaction primitives (damping, reduced-motion contract).-- [Restyle Studio](#sec-422), which already ships a `realGlass` transmissive preset and the+- [ui-juice](#sec-575), the shared interaction primitives (damping, reduced-motion contract).+- [Restyle Studio](#sec-437), which already ships a `realGlass` transmissive preset and the`RoomEnvironment` lighting setup this document depends on.----<a id="sec-305"></a>+<a id="sec-316"></a>> **Source:** `docs/listings.md` · [↑ table of contents](#table-of-contents)@@ -73204,7 +76976,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. See [aws-marketplace.md](#sec-133) and the [listing kit](#sec-132). |+| **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. See [aws-marketplace.md](#sec-136) and the [listing kit](#sec-135). || **Alibaba Cloud** International Marketplace | Live | [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. |@@ -73219,7 +76991,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-346), [NVIDIA models](#sec-347), [visibility map](#sec-351). 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-358), [NVIDIA models](#sec-359), [visibility map](#sec-363). 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. |---@@ -73231,7 +77003,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-624).+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-645).---@@ -73241,11 +77013,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-318)). Full submission kit, prerequisites, and rejection criteria: [openai-listing-channels.md](#sec-361). |-| **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-361). |-| **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. Root-cause analysis and the revival steps are in [openai-listing-channels.md](#sec-361). |-| **NVIDIA** Accelerated Apps Catalog | Prepared, not submitted | NVIDIA's curated catalog of applications built by Inception members, published at [marketplace.nvidia.com](https://marketplace.nvidia.com/en-us/enterprise/applications/). There is no self-serve control: a product record in the Inception portal makes the company eligible, and NVIDIA curates the public listing. The portal record is filed and the correction sheet, the paste-ready copy, and the inclusion email are all written. See [nvidia-apps-catalog-listing.md](#sec-343) and [nvidia-apps-catalog-request.md](#sec-344). |-| **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-350). |+| **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-329)). Full submission kit, prerequisites, and rejection criteria: [openai-listing-channels.md](#sec-373). |+| **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-373). |+| **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. Root-cause analysis and the revival steps are in [openai-listing-channels.md](#sec-373). |+| **NVIDIA** Accelerated Apps Catalog | Prepared, not submitted | NVIDIA's curated catalog of applications built by Inception members, published at [marketplace.nvidia.com](https://marketplace.nvidia.com/en-us/enterprise/applications/). There is no self-serve control: a product record in the Inception portal makes the company eligible, and NVIDIA curates the public listing. The portal record is filed and the correction sheet, the paste-ready copy, and the inclusion email are all written. See [nvidia-apps-catalog-listing.md](#sec-354) and [nvidia-apps-catalog-request.md](#sec-355). |+| **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-362). |---@@ -73316,12 +77088,13 @@ Subscribe via RSS to track new listings, integrations, and protocol updates.- [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-403): 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-306"></a>+<a id="sec-317"></a>> **Source:** `docs/live-docs.md` · [↑ table of contents](#table-of-contents)@@ -73341,7 +77114,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-578).+This is the same embed snippet from the [`<agent-3d>` reference](#sec-599).Press **Run preview** and it renders. Then press **Edit**, swap `michelle.glb`for `xbot.glb`, and run it again.@@ -73503,14 +77276,14 @@ cached module.## Related-- [`<agent-3d>` Web Component API Reference](#sec-578) — the element most previews render-- [API reference](#sec-104) — the endpoints most `curl` samples call-- [Embed and share](#sec-204) — putting an avatar on your own site-- [MCP tool safety](#sec-314) — the same read/write/irreversible split, applied to agent tools+- [`<agent-3d>` Web Component API Reference](#sec-599) — the element most previews render+- [API reference](#sec-105) — the endpoints most `curl` samples call+- [Embed and share](#sec-209) — putting an avatar on your own site+- [MCP tool safety](#sec-325) — the same read/write/irreversible split, applied to agent tools----<a id="sec-307"></a>+<a id="sec-318"></a>> **Source:** `docs/live-steps.md` · [↑ table of contents](#table-of-contents)@@ -73693,7 +77466,7 @@ Run `npx vitest run tests/live-steps.test.js` after editing the registry; the su----<a id="sec-308"></a>+<a id="sec-319"></a>> **Source:** `docs/make-your-agent.md` · [↑ table of contents](#table-of-contents)@@ -73710,7 +77483,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-195) 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-200) if you're not sure which sign-in option to choose.---@@ -73760,7 +77533,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-436)+For more on where and how to embed, continue to [Share & embed →](#sec-453)---@@ -73790,14 +77563,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-436)-- **Understand how it all works** → [How it works](#sec-273)-- **Give the agent a custom skill** → [Create a custom skill](#sec-500)-- **Make it yours permanently (on-chain)** → [Register on-chain](#sec-530)+- **Put it on your website** → [Share & embed](#sec-453)+- **Understand how it all works** → [How it works](#sec-282)+- **Give the agent a custom skill** → [Create a custom skill](#sec-520)+- **Make it yours permanently (on-chain)** → [Register on-chain](#sec-550)----<a id="sec-309"></a>+<a id="sec-320"></a>> **Source:** `docs/market-data-api.md` · [↑ table of contents](#table-of-contents)@@ -73922,7 +77695,7 @@ as the single retryable class.----<a id="sec-310"></a>+<a id="sec-321"></a>> **Source:** `docs/marketplace.md` · [↑ table of contents](#table-of-contents)@@ -74053,7 +77826,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-333)).+ `payment-earned` notification (see [Money feed](#sec-344)).## Access checks@@ -74103,7 +77876,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-619) endpoint returns the+ paid [`/api/x402/skill-marketplace`](#sec-640) 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@@ -74122,12 +77895,12 @@ their chosen `currency_mint`; the platform promotes no coin other than $THREE.## Related- [Agent wallets](#sec-074) — how agent-side purchases are funded and gated.-- [Circulation engine](#sec-154) — manufactured marketplace demand.-- [Skills system](#sec-447), [Coin launches](#sec-157).+- [Circulation engine](#sec-158) — manufactured marketplace demand.+- [Skills system](#sec-465), [Coin launches](#sec-161).----<a id="sec-311"></a>+<a id="sec-322"></a>> **Source:** `docs/materialize.md` · [↑ table of contents](#table-of-contents)@@ -74146,7 +77919,7 @@ 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-245)), then come back. You can+[/forge](https://three.ws/forge) ([Forge](#sec-251)), then come back. You canalso print a `.glb` you already have.---@@ -74570,14 +78343,14 @@ documents the verdict shape and, just as importantly, what the gate cannot do.## Related-- [Forge](#sec-245), where the models come from-- [The Forge pipeline](#sec-244), the generation engineering guide+- [Forge](#sec-251), where the models come from+- [The Forge pipeline](#sec-250), the generation engineering guide- [specs/PRINT_PIPELINE.md](../specs/PRINT_PIPELINE.md), every wire contract-- [API reference](#sec-104), the `/api/print/*` endpoints+- [API reference](#sec-105), the `/api/print/*` endpoints----<a id="sec-312"></a>+<a id="sec-323"></a>> **Source:** `docs/mcp-3d-studio.md` · [↑ table of contents](#table-of-contents)@@ -74628,6 +78401,7 @@ analyze: inspect_model · optimize_model preview: preview_3d| `animation_signature(clip, slot?)` | A clip's measured motion: energy, tempo, leading region, loop seam, travel. Pass `slot` for an ok/warn fit verdict against a runtime slot. || `find_similar_animations(clip, limit?)` | The library ranked by measured-motion distance from a reference clip: "more like this" for animations. || `apply_animation(model_url, animation, format?, speed?)` | Retarget a preset clip onto a rigged GLB — returns the retargeted `AnimationClip` JSON (or a baked animated GLB). |+| `text_to_animation(prompt, model_url?, duration_seconds?, format?, speed?)` | Generate a brand-new motion from a prompt ("waving confidently", "a slow tai-chi sweep") with a motion-diffusion model, then retarget it onto a rigged humanoid GLB with the same engine `apply_animation` uses. || `pose_model(prompt)` | Map a pose description to a deterministic seed + full Euler joint-rotation map from the in-repo preset library. Deterministic: the same prompt always returns the same seed. Priced at $0.01 (see the table below). |### Edit & process the mesh@@ -74640,6 +78414,7 @@ analyze: inspect_model · optimize_model preview: preview_3d| `retexture_model(mesh_url, prompt, num_views?, texture_size?)` | Paint a fresh texture from a prompt (SDXL + ControlNet depth, multi-view back-projection). || `retexture_region(mesh_url, mask_url, prompt?, color?, …)` | Magic-brush: repaint only a masked UV region, feathering the seam. || `generate_material(description, name?)` | IBM Granite → a glTF 2.0 PBR material (base color, metallic, roughness, emissive). |+| `remove_background(image_url, model?)` | Strip the background from a photo or illustration, returning a transparent PNG: a clean input for `image_to_3d`. |### Assist, analyze & preview@@ -74649,7 +78424,14 @@ 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-456) 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-474) 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). |+| `grade_sim_readiness(glb_url, hash?)` | Free: can this GLB be dropped into a physics simulator (MuJoCo, Isaac, Bullet, a game engine) and behave? Returns `simulation_ready`, `needs_scale`, `needs_repair`, or `unusable`, plus the measurements behind the verdict. |+| `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`. |+| `validate_spatial_response(artifact)` | Free: check a structured-content payload against the open [Spatial MCP](#sec-474) 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@@ -74738,9 +78520,26 @@ key per poll.## Access & pricing-Discovery is free for everyone: `initialize`, `tools/list`, `ping`, and the-`getting_started` tool answer with no credentials, so any agent or crawler can-read the catalog before deciding to pay.+Discovery is free: a discovery-only batch (`initialize`, `tools/list`, `ping`)+and the public `getting_started` tool answer with no credentials, so any x402+agent, registry validator, or crawler can read the catalog before deciding to+pay.++```bash+curl -s https://three.ws/api/mcp-3d \+ -H 'content-type: application/json' \+ -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'+```++One deliberate exception: an **MCP protocol client** still gets `401` on+discovery. A request carrying `mcp-protocol-version`, `mcp-session-id`, or an+`Accept` of `text/event-stream` (the MCP TS SDK, the Inspector, the claude.ai+connector) is answered with a `WWW-Authenticate` challenge instead, because the+MCP authorization spec (RFC 9728) requires a 401 for the client to find the+protected-resource metadata and start the OAuth flow. That branch is+`isMcpProtocolClient` in [`api/_mcp/auth.js`](../api/_mcp/auth.js). So adding the+connector and signing in works; a plain `curl` that sets the SSE accept header+sees a challenge rather than the catalog, and should drop that header to browse.For tool calls there are two lanes:@@ -74822,7 +78621,7 @@ npx @modelcontextprotocol/inspector http://localhost:3000/api/mcp-3d----<a id="sec-313"></a>+<a id="sec-324"></a>> **Source:** `docs/mcp-agent.md` · [↑ table of contents](#table-of-contents)@@ -74929,13 +78728,13 @@ npx @modelcontextprotocol/inspector http://localhost:3000/api/mcp-agent----<a id="sec-314"></a>+<a id="sec-325"></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-318) carries an+Every tool three.ws publishes over the [Model Context Protocol](#sec-329) 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@@ -75264,7 +79063,7 @@ All four run in `npm run gate`.----<a id="sec-315"></a>+<a id="sec-326"></a>> **Source:** `docs/mcp-studio.md` · [↑ table of contents](#table-of-contents)@@ -75318,12 +79117,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-104). Use the MCP connector above when you+the [API reference](#sec-105). 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-151).+[AR in ChatGPT](#sec-155).## Tools@@ -75381,7 +79180,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-318)) also ships a tool called `forge_free`. That is a different+([docs](#sec-329)) 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`.@@ -75407,9 +79206,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-151)).+`arUrl` is the one-tap place-in-your-room link (see [AR in ChatGPT](#sec-155)).Rigged avatars additionally carry `irlUrl`, the living-agent handoff into-[IRL](#sec-294), and the inline widget's AR button becomes **Bring it to life**.+[IRL](#sec-304), 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.@@ -75648,15 +79447,15 @@ Quick Look rather than a camera overlay (`api/_lib/ar-launch.js`).----<a id="sec-316"></a>+<a id="sec-327"></a>> **Source:** `docs/mcp-tools.md` · [↑ table of contents](#table-of-contents)# MCP Tools Catalog-three.ws ships several [MCP](#sec-318) servers: tool servers that AI assistants+three.ws ships several [MCP](#sec-329) 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-624). This+others expose paid tools that settle per call in USDC over [x402](#sec-645). 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@@ -75695,7 +79494,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-315).+[3D Studio MCP](#sec-326).## Material Studio (hosted, free) — `/api/material-studio`@@ -75741,12 +79540,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-442); free so an agent can check ten+see [Simulation readiness](#sec-460); 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-456) conformance gate).+`validate_spatial_response` (the [Spatial MCP](#sec-474) conformance gate).Every catalog tool is either priced or on this explicit free list; a test failsthe build if a new tool is neither.@@ -75791,9 +79590,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-317). |-| IBM MCP | `api/ibm-mcp.js` | watsonx / Granite integration — see [IBM](#sec-287). |-| pump.fun MCP | `api/pump-fun-mcp.js` | Launch/trade tools — see [Solana pump.fun](#sec-453). |+| Bazaar MCP | `api/mcp-bazaar.js` | x402 service discovery — see [x402 bazaar](#sec-328). |+| IBM MCP | `api/ibm-mcp.js` | watsonx / Granite integration — see [IBM](#sec-297). |+| pump.fun MCP | `api/pump-fun-mcp.js` | Launch/trade tools — see [Solana pump.fun](#sec-471). |## $THREE only@@ -75804,16 +79603,16 @@ promote no specific token.## Related-- [MCP](#sec-318) overview · [3D Studio MCP](#sec-315) ·- [3D Studio (paid)](#sec-312) · [x402 bazaar](#sec-317)-- [x402 paid endpoints](#sec-619) — the same capabilities over REST.-- [MCP tool safety](#sec-314) - what each tool's safety annotations mean,+- [MCP](#sec-329) overview · [3D Studio MCP](#sec-326) ·+ [3D Studio (paid)](#sec-323) · [x402 bazaar](#sec-328)+- [x402 paid endpoints](#sec-640) — the same capabilities over REST.+- [MCP tool safety](#sec-325) - 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-317"></a>+<a id="sec-328"></a>> **Source:** `docs/mcp-x402-bazaar.md` · [↑ table of contents](#table-of-contents)@@ -75925,7 +79724,7 @@ npx @modelcontextprotocol/inspector http://localhost:3000/api/mcp-bazaar----<a id="sec-318"></a>+<a id="sec-329"></a>> **Source:** `docs/mcp.md` · [↑ table of contents](#table-of-contents)@@ -75974,7 +79773,7 @@ The MCP server configuration is at `.mcp.json` in the project root, which Claude## The full three.ws MCP ecosystem-This page documents the hosted avatar/3D server at `/api/mcp`, but it's one of **50 three.ws MCP servers**, all listed in the [official MCP registry](https://registry.modelcontextprotocol.io/?q=io.github.nirholas), so any MCP-compatible client can discover them by name.+This page documents the hosted avatar/3D server at `/api/mcp`, but it's one of **51 three.ws MCP servers**, all listed in the [official MCP registry](https://registry.modelcontextprotocol.io/?q=io.github.nirholas), so any MCP-compatible client can discover them by name.The hosted servers are also self-describing: [`https://three.ws/.well-known/mcp.json`](https://three.ws/.well-known/mcp.json) is a machine-readable directory of every hosted endpoint with its transport, auth model, and a one-line description, so an agent can enumerate all of them with a single fetch.@@ -75992,7 +79791,7 @@ There are two kinds. **Hosted remote servers** run over Streamable HTTP with not| 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 |-**Forty install-and-run servers** on npm under the `@three-ws` scope, each running over stdio with one command:+**Forty-one install-and-run servers** on npm under the `@three-ws` scope, each running over stdio with one command:```bash# 3D & avatars@@ -76002,6 +79801,7 @@ npx -y @three-ws/avatar-mcp # drop a live 3D avatar into any chatnpx -y @three-ws/concierge-mcp # ask any site's AI concierge; generate the 3D chat-widget embednpx -y @three-ws/avatar-agent # turn any GLB into a riggable 3D AI agentnpx -y @three-ws/mcp-server # full 3D + agent toolkit, paid per call in USDC+npx -y @three-ws/blender-mcp # drive the Blender on your own machine, headless (needs Blender 3.0+ installed)# Payments & the agent economynpx -y @three-ws/x402-mcp # self-custodial wallet: find, inspect & pay any x402 service in USDC@@ -76011,7 +79811,7 @@ npx -y @three-ws/ibm-x402-mcp # pay-per-use IBM Granite AInpx -y @three-ws/agentcore-payments-mcp # pay x402 endpoints from a governed budget, no private key# On-chain identity-npx -y @three-ws/metaplex-agent-mcp # mint + register on-chain agents in the Metaplex Agent Registry (deploy fee waived for holders)+npx -y @three-ws/metaplex-agent-mcp # mint + register on-chain agents in the Metaplex Agent Registry (deploy fee funds $THREE buybacks, waived for holders)# Market data, intel & discoverynpx -y @three-ws/intel-mcp # smart-money, signal feeds, KOL & copy-trade intel@@ -76079,8 +79879,9 @@ 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-315) · [3D Studio (paid)](#sec-312) · [Agent wallet](#sec-313) · [x402 Bazaar](#sec-317) · [IBM x402](#sec-286)-- **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-316) maps every tool to its server and price.+- **Hosted remote:** [3D Studio (free)](#sec-326) · [3D Studio (paid)](#sec-323) · [Agent wallet](#sec-324) · [x402 Bazaar](#sec-328) · [IBM x402](#sec-296)+- **Runs against your machine:** [Blender MCP](#sec-139) 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-327) maps every tool to its server and price.---@@ -76165,7 +79966,130 @@ Send `POST /api/mcp` with valid JSON-RPC 2.0 messages and a bearer token. The seAll tools return `{ content: [{ type, text }], structuredContent: {...} }`. On error, `isError: true` is set and `content[0].text` contains the message.-The tools below 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 account, API key, or payment: start there. 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`++Search every ready-made asset three.ws publishes in one call: 511 CC0 props, 107 rigged+characters, and 2,874 retargetable motion clips (live counts come back in `facets.kinds`).++**Free. No account, no API key, no x402 payment.** Discovery works before you connect.++```json+{+ "type": "object",+ "properties": {+ "q": { "type": "string", "maxLength": 200 },+ "kind": { "type": "string", "enum": ["object", "character", "animation"] },+ "category": { "type": "string", "maxLength": 80 },+ "tag": { "type": "string", "maxLength": 80 },+ "limit": { "type": "integer", "minimum": 1, "maximum": 50, "default": 12 },+ "offset": { "type": "integer", "minimum": 0, "default": 0 }+ },+ "additionalProperties": false+}+```++Every word of `q` must match somewhere (title, name, tag, or category), which keeps a+two-word query precise. If nothing matches all of the words, the search retries on any of+them and sets `relaxed: true` so you know the results are partial rather than exact.++Each result carries a stable `id` of the form `<kind>:<name>`, plus `title`, `tags`,+`categories`, `license`, `thumb`, and the CDN `url` of the GLB or clip JSON. The response+also carries `facets` (kind counts and the most common categories and tags in the result+set) to narrow the next call, and `next_offset` for paging.++```jsonc+// search_catalog { "q": "wooden chair", "kind": "object", "limit": 2 }+{+ "ok": true,+ "matched": 10,+ "relaxed": false,+ "items": [+ {+ "id": "object:painted_wooden_chair_01",+ "kind": "object",+ "title": "Painted Wooden Chair 01",+ "categories": ["furniture"],+ "tags": ["chair", "wood", "painted"],+ "license": "CC0",+ "format": "glb",+ "url": "https://.../objects/polyhaven/glb/painted_wooden_chair_01.glb",+ "thumb": "https://.../objects/polyhaven/thumbs/painted_wooden_chair_01.png",+ "bytes": 1483264+ }+ ],+ "facets": { "kinds": { "object": 10 }, "categories": [{ "value": "furniture", "count": 8 }] },+ "next_offset": 2+}+```++Check the catalog before generating anything. If the prop or character already exists,+dropping it in is instant and free, where a Forge generation is neither.++---++### `get_catalog_item`++One catalog item in full, by the `id` from `search_catalog` (a bare name also resolves).++**Free. No account or payment.**++```json+{+ "type": "object",+ "required": ["id"],+ "properties": {+ "id": { "type": "string", "maxLength": 200 }+ },+ "additionalProperties": false+}+```++Returns the item, the `links` that browse/preview/edit it on three.ws (an object opens in+the viewer and in AR Studio, a character in the viewer, Widget Studio, and the pose editor,+a clip in the animation gallery), up to six `related` items of the same kind, and the+`frameworks` that `get_item_source` can emit for it.++---++### `get_item_source`++Paste-ready code that renders one catalog item on any site.++**Free. No account or payment.**++```json+{+ "type": "object",+ "required": ["id"],+ "properties": {+ "id": { "type": "string", "maxLength": 200 },+ "framework": { "type": "string", "enum": ["agent-3d", "model-viewer", "three", "react", "all"] }+ },+ "additionalProperties": false+}+```++| Framework | What you get |+| --- | --- |+| `agent-3d` | The `<agent-3d>` web component, pinned to the exact version this deployment serves with its published SRI hash. Never `latest`. |+| `model-viewer` | The `<model-viewer>` tag, build, and integrity hash the three.ws browse grids themselves use. |+| `three` | Plain three.js: `GLTFLoader` for a model, `THREE.AnimationClip.parse` for a motion clip. |+| `react` | The same, wrapped as a React component (or a hook, for a clip). |+| `all` | Every variant that applies to the item, in one response. |++Omit `framework` and you get the one that fits the item: `model-viewer` for a prop (what the+object grid renders), `agent-3d` for a rigged character, `three` for a motion clip. A+framework that does not apply to the item (asking for `model-viewer` on a clip) is rejected+with the list that does.++Motion clips are `THREE.AnimationClip` JSON on canonical (Mixamo) bone names. To bake one+onto your own rig server-side instead of playing it in the browser, pass the returned clip+name to the `apply_animation` tool with your GLB url; it retargets and returns an animated+GLB.---@@ -76468,13 +80392,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-470) 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-490) 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-104) (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-105) (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{@@ -76489,7 +80413,7 @@ Call any endpoint in the free [Crypto Data API](#sec-104) (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-624) — 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-645) — never a second, MCP-only payment flow.```bash# Equivalent to: GET /api/v1/x/dexscreener/token?addresses=FeMbDoX7R1Psc4GEcvJdsbNbZA3bfztcyDCatJVJpump@@ -76704,7 +80628,7 @@ or `floor_id`; every target is resolved to concrete entities before the gate see}```-Full walkthrough: [Connect your home](#sec-498). To run a house from your+Full walkthrough: [Connect your home](#sec-518). 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.@@ -76881,7 +80805,7 @@ three.ws examples repo, so it is installed, run, and link-checked before every r----<a id="sec-319"></a>+<a id="sec-330"></a>> **Source:** `docs/media-api.md` · [↑ table of contents](#table-of-contents)@@ -76905,6 +80829,7 @@ Base URL: `https://three.ws`|----------|--------|------|--------------|| [`/api/avatar/render`](#render-an-avatar-as-an-image) | GET | none | Rendered PNG/JPEG/WebP of any public avatar || [`/api/render/avatar-clip`](#render-any-glb-posed-and-camera-orbited) | GET, POST | none | Posed, camera-orbited PNG of any GLB |+| [`/api/avatar/capabilities`](#model-capabilities) | GET | none | What a model can honor: ARKit shapes, skeleton coverage, geometry || [`/api/avatar/optimize`](#optimize-a-glb-at-runtime) | GET | none | Runtime GLB transcoder (LOD, textures, morphs, Draco) || [`/api/glb`](#same-origin-glb-proxy) | GET | none | Same-origin GLB proxy with open CORS || [`/cdn/<key>`](#how-bucket-objects-are-served-cdnkey) | GET, HEAD | none | First-party CDN for bucket objects |@@ -77045,6 +80970,109 @@ curl -s -X POST https://three.ws/api/render/avatar-clip \---+## Model capabilities++**`GET /api/avatar/capabilities`** answers what a model will and will not honor+*before* you render it. Every other endpoint here returns a picture; this one+returns a verdict. It reads the glTF JSON chunk of the GLB (a ranged read of the+head of the file, never the mesh binary) and reports which ARKit-52 morph+targets exist, how much of the canonical humanoid skeleton the rig maps onto,+what the geometry weighs, and a plain-language reason per capability.++It is the same mapping code the renderer and the retargeter run, so it is a+report of what will happen, not an estimate. Call it once per model and build+your `expression` and `pose` requests out of shapes and rigs that exist, instead+of discovering the gap as a still face or a T-pose.++Pass exactly one of `avatar` or `url`. With neither, it returns its own schema,+so the endpoint is self-documenting from a browser address bar.++### Query parameters++| Name | Type | Notes |+|------|------|-------|+| `avatar` | string | three.ws avatar UUID. Public and unlisted avatars only. |+| `url` | string | Any publicly reachable `.glb` URL. SSRF-guarded and range-capped. |++### Response++`200` with JSON. `x-capabilities-cache` is `hit` or `miss`; responses are+cacheable for 5 minutes at the client and an hour at the edge.++| Field | Notes |+|-------|-------|+| `rig.detected` / `rig.label` | Authoring pipeline inferred from bone names and the glTF generator string. |+| `rig.boneCount` / `rig.skinCount` | Joints and skins across the whole file. |+| `rig.canonicalCoverage` | 0..1 share of the canonical humanoid skeleton that maps. Above 0.5 with the core bones present, every baked clip retargets. |+| `rig.fingerCoverage` | 0..1 share of the finger chain, for poses that need hands. |+| `rig.mappedBones` / `rig.unmappedBones` | The bones behind those numbers. |+| `rig.bakedAnimations` | Clips already in the file, by name. |+| `morphs.total` / `morphs.named` | Morph targets present, including shapes outside the ARKit set. |+| `morphs.arkitCoverage` | 0..1 share of Apple's 52 facial blendshapes present. |+| `morphs.supported` / `morphs.missing` | The ARKit names you can drive, and the ones you cannot. |+| `morphs.visemes` | Viseme shapes present, which is what phoneme-accurate lipsync needs. |+| `morphs.custom` | Named shapes outside ARKit and the viseme set. |+| `geometry` | `triangles`, `vertices`, `meshes`, `primitives`, `materials`, `textures`, and the glTF `extensions` in use. |+| `can.pose` / `can.expression` / `can.lipsync` | `{ supported, reason }`. The reason is written for a human and names the fix when the answer is no. |+| `subject` | Echoes what was inspected: `{ kind: "avatar", id, name, slug }` or `{ kind: "url", url }`. |++### Errors++| Situation | Response |+|-----------|----------|+| Avatar ID not found, or private | `404 not_found` |+| Avatar exists but has no readable model | `403 private` |+| `url` is not an absolute http(s) URL | `400 invalid_url` |+| A caller-supplied `url` could not be read | `400 fetch_failed` |+| A stored avatar's own model could not be read | `502 fetch_failed` |+| The file is not a parseable binary glTF 2.0 | `422 not_a_glb` |+| Over 120 inspections per 10 minutes per IP | `429` with `Retry-After` |++`.gltf` plus external buffers is not supported. Only `.glb`.++### curl++```bash+# The endpoint's own schema, plus the ARKit-52, viseme, and canonical bone lists+curl -s https://three.ws/api/avatar/capabilities++# Can this avatar smile? Which shapes can it actually move?+curl -s 'https://three.ws/api/avatar/capabilities?avatar=a4bad2f5-8a07-43cf-82e5-b6ba1314441e' \+ | jq '{ expression: .can.expression, shapes: .morphs.supported }'++# Same question about a raw GLB that was never saved as an avatar+curl -s 'https://three.ws/api/avatar/capabilities?url=https://three.ws/avatars/selfie-girl.glb' \+ | jq '.can'+```++### Build a request that cannot silently no-op++```js+const caps = await fetch(+ 'https://three.ws/api/avatar/capabilities?avatar=' + avatarId,+).then((r) => r.json());++const wanted = { mouthSmileLeft: 0.7, mouthSmileRight: 0.7, jawOpen: 0.3 };+const usable = Object.fromEntries(+ Object.entries(wanted).filter(([shape]) => caps.morphs.supported.includes(shape)),+);++const url = new URL('https://three.ws/api/avatar/render');+url.searchParams.set('avatar', avatarId);+if (caps.can.pose.supported) url.searchParams.set('pose', 'wave');+if (Object.keys(usable).length) url.searchParams.set('expression', JSON.stringify(usable));++const res = await fetch(url);+// 'applied' | 'partial' | 'none': what the renderer could actually drive.+console.log(res.headers.get('x-render-expression'));+```++[Render Lab](https://three.ws/render-lab) is this endpoint with a UI on it: it+reads the report first and switches off the controls the selected model cannot+honor, with the reason.++---+## Optimize a GLB at runtime**`GET /api/avatar/optimize`** returns a re-encoded variant of a@@ -77137,7 +81165,7 @@ If `draco=1` comes back `500 transcode_failed` with `draco.createCompressedPrimi### When you need it, and when you do notIt depends entirely on which host serves the `.glb`, not on which origin you-are loading from. Re-measured 2026-09-04, unchanged since 2026-08-01:+are loading from. Re-measured 2026-09-09, unchanged since 2026-08-01:| Source host | Cross-origin fetch | Use the proxy? ||---|---|---|@@ -77432,7 +81460,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-352)+through `/cdn/<key>`). See [the object library doc](#sec-364)for the full parameter table.### Response@@ -77791,13 +81819,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-288) - the photo-input reconstruction product these front doors feed-- [Voice Lab](#sec-576) - voice cloning and synthesis, the other half of the avatar voice loop-- [API Reference](#sec-104) - the full three.ws HTTP API surface+- [Image to 3D](#sec-298) - the photo-input reconstruction product these front doors feed+- [Voice Lab](#sec-596) - voice cloning and synthesis, the other half of the avatar voice loop+- [API Reference](#sec-105) - the full three.ws HTTP API surface----<a id="sec-320"></a>+<a id="sec-331"></a>> **Source:** `docs/memetic-launcher.md` · [↑ table of contents](#table-of-contents)@@ -77902,12 +81930,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-392) — 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-407) — 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-321"></a>+<a id="sec-332"></a>> **Source:** `docs/memory.md` · [↑ table of contents](#table-of-contents)@@ -78319,7 +82347,7 @@ store described above and each revocable by deleting exactly what it wrote:----<a id="sec-322"></a>+<a id="sec-333"></a>> **Source:** `docs/meta-allocator.md` · [↑ table of contents](#table-of-contents)@@ -78413,14 +82441,14 @@ plan `source` is `"empty"` with a helpful message instead of an error.## Related-- [Trader Card & the claim-your-wallet wedge](#sec-472)-- [The trading surfaces](#sec-479) · [/vaults](https://three.ws/vaults) (copy-trade with custody guardrails)-- [Clip Director: every trade becomes content](#sec-156)-- [Financial controls & custody guardrails](#sec-240)+- [Trader Card & the claim-your-wallet wedge](#sec-492)+- [The trading surfaces](#sec-499) · [/vaults](https://three.ws/vaults) (copy-trade with custody guardrails)+- [Clip Director: every trade becomes content](#sec-160)+- [Financial controls & custody guardrails](#sec-246)----<a id="sec-323"></a>+<a id="sec-334"></a>> **Source:** `docs/mint-mark.md` · [↑ table of contents](#table-of-contents)@@ -78546,13 +82574,13 @@ No other mint should appear in tests, fixtures, or documentation.## Related-- [Solana agents](#sec-455) — agent wallet management and on-chain interactions-- [Solana pump.fun signals](#sec-453) — pump.fun live feed integration-- [ERC-8004](#sec-206) — on-chain agent registry (uses the same brand metadata builder)+- [Solana agents](#sec-473) — agent wallet management and on-chain interactions+- [Solana pump.fun signals](#sec-471) — pump.fun live feed integration+- [ERC-8004](#sec-211) — on-chain agent registry (uses the same brand metadata builder)----<a id="sec-324"></a>+<a id="sec-335"></a>> **Source:** `docs/minted.md` · [↑ table of contents](#table-of-contents)@@ -78560,7 +82588,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-388) (signed credentials, Solana anchoring, the free verify endpoint) and [the three.ws mint mark](#sec-323) (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-402) (signed credentials, Solana anchoring, the free verify endpoint) and [the three.ws mint mark](#sec-334) (the `3ws` address branding on coin launches).## The gallery@@ -78592,7 +82620,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-318). 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-329). 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.@@ -78615,7 +82643,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-388). For the `3ws` address mark that brands coin launches, read [mint-mark.md](#sec-323).+For how signed credentials, canonical hashing, and on-chain anchoring work under the hood, read [provenance.md](#sec-402). For the `3ws` address mark that brands coin launches, read [mint-mark.md](#sec-334).### Remix royalties: paid the moment a remix mints@@ -78629,14 +82657,14 @@ The companion MCP tool `get_3d_asset_onchain` resolves any Core mint address to## Related-- [Verifiable 3D provenance](#sec-388): signed content credentials and free verification for generated models-- [The three.ws mint mark](#sec-323): the `3ws` address brand on coin launches-- [MCP servers](#sec-318): the `mint_3d_asset` and `get_3d_asset_onchain` tools-- [Custody you can verify](#sec-187): the wallet rails behind agent-held assets+- [Verifiable 3D provenance](#sec-402): signed content credentials and free verification for generated models+- [The three.ws mint mark](#sec-334): the `3ws` address brand on coin launches+- [MCP servers](#sec-329): the `mint_3d_asset` and `get_3d_asset_onchain` tools+- [Custody you can verify](#sec-191): the wallet rails behind agent-held assets----<a id="sec-325"></a>+<a id="sec-336"></a>> **Source:** `docs/mobile-launch/README.md` · [↑ table of contents](#table-of-contents)@@ -78646,28 +82674,28 @@ Five long-form articles announcing three.ws as three native apps (Solana Seeker| File | Venue | Angle || --- | --- | --- |-| [x-article.md](#sec-330) | 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-327) | 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-326) | 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-329) | 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-328) | 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-341) | 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-338) | 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-337) | 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-340) | 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-339) | 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-431) 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-293) 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-340)); 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-368).-- **The IBM and NVIDIA pieces deliberately carry no token contract address.** [ibm.md](#sec-287) 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-467) and [three-thesis.md](#sec-468). 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-131).+- **Store status is written as live in all five, on the owner's instruction (2026-09-01).** As of writing, [seeker-app.md](#sec-447) 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-303) 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-351)); 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-381).+- **The IBM and NVIDIA pieces deliberately carry no token contract address.** [ibm.md](#sec-297) 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-485) and [three-thesis.md](#sec-487). 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-134).## Sources-The apps: [seeker-app.md](#sec-431), [ios-app.md](#sec-293), [native-widgets.md](#sec-340), [glance.md](#sec-257), [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-273), [forge-pipeline.md](#sec-244), [selfie-to-avatar.md](#sec-435), [ar.md](#sec-107), [irl.md](#sec-294), [x402.md](#sec-624), [onchain-agents.md](#sec-355), [hold-to-access.md](#sec-262). Partners and models: [partners.md](#sec-368), [nvidia-models.md](#sec-347), [nvidia-inception.md](#sec-346), [ibm.md](#sec-287), [ibm-x402-mcp.md](#sec-286), [aws-builder-center.md](#sec-131). 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-447), [ios-app.md](#sec-303), [native-widgets.md](#sec-351), [glance.md](#sec-263), [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-282), [forge-pipeline.md](#sec-250), [selfie-to-avatar.md](#sec-451), [ar.md](#sec-108), [irl.md](#sec-304), [x402.md](#sec-645), [onchain-agents.md](#sec-367), [hold-to-access.md](#sec-270). Partners and models: [partners.md](#sec-381), [nvidia-models.md](#sec-359), [nvidia-inception.md](#sec-358), [ibm.md](#sec-297), [ibm-x402-mcp.md](#sec-296), [aws-builder-center.md](#sec-134). 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-326"></a>+<a id="sec-337"></a>> **Source:** `docs/mobile-launch/aws-builder-center-article.md` · [↑ table of contents](#table-of-contents)@@ -78979,7 +83007,7 @@ If you have a WebGL product and a "when is the app coming" question, the whole a----<a id="sec-327"></a>+<a id="sec-338"></a>> **Source:** `docs/mobile-launch/coinmarketcap-article.md` · [↑ table of contents](#table-of-contents)@@ -79191,7 +83219,7 @@ Open source: github.com/nirholas/three.ws----<a id="sec-328"></a>+<a id="sec-339"></a>> **Source:** `docs/mobile-launch/ibm-community-article.md` · [↑ table of contents](#table-of-contents)@@ -79317,7 +83345,7 @@ Docs: [three.ws/docs/ibm](https://three.ws/docs/ibm) · Live: [three.ws/ibm/hell----<a id="sec-329"></a>+<a id="sec-340"></a>> **Source:** `docs/mobile-launch/nvidia-forum-article.md` · [↑ table of contents](#table-of-contents)@@ -79451,7 +83479,7 @@ If you are serving generative 3D to phones, the two things I would tell you firs----<a id="sec-330"></a>+<a id="sec-341"></a>> **Source:** `docs/mobile-launch/x-article.md` · [↑ table of contents](#table-of-contents)@@ -79633,7 +83661,7 @@ Open source, all of it: github.com/nirholas/three.ws----<a id="sec-331"></a>+<a id="sec-342"></a>> **Source:** `docs/mocap-studio.md` · [↑ table of contents](#table-of-contents)@@ -79725,14 +83753,14 @@ what the page itself sends.## Related-- [Avatar Studio](#sec-124): build the avatar you drive here.+- [Avatar Studio](#sec-127): build the avatar you drive here.- [Animation Studio](#sec-096): body posing and keyframed motion, the complement to facial capture.- [Animations reference](#sec-097): 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-332"></a>+<a id="sec-343"></a>> **Source:** `docs/model-diff.md` · [↑ table of contents](#table-of-contents)@@ -79746,7 +83774,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-423) 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-438) 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.---@@ -79950,7 +83978,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-318) 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-329) for connecting the server.---@@ -79996,7 +84024,7 @@ The same two files always produce the same change set, byte for byte, on any mac----<a id="sec-333"></a>+<a id="sec-344"></a>> **Source:** `docs/money-feed.md` · [↑ table of contents](#table-of-contents)@@ -80010,7 +84038,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-452). This page is+> whom, and is documented in [The social layer](#sec-470). This page is> about value movement only. The two share a URL word ("feed") and nothing else.---@@ -80086,11 +84114,11 @@ spend-cap and policy engine before they are recorded (see| Producer | Ledger? | Ticker? | Domain record ||---|---|---|---|-| [Circulation engine](#sec-154) tips/payments/trades/buys | Yes | Trades/launches via pump feed | `circulation_actions` + domain table |-| [Marketplace](#sec-310) skill/asset purchase | Yes | `payment` / `sale` | `skill_purchases` / `asset_purchases` |-| [Coin launches](#sec-157) | Yes | `coin-buy` / `agent-deploy` | `pump_agent_mints` |+| [Circulation engine](#sec-158) tips/payments/trades/buys | Yes | Trades/launches via pump feed | `circulation_actions` + domain table |+| [Marketplace](#sec-321) skill/asset purchase | Yes | `payment` / `sale` | `skill_purchases` / `asset_purchases` |+| [Coin launches](#sec-161) | Yes | `coin-buy` / `agent-deploy` | `pump_agent_mints` || Sniper trades | Yes (`category: 'snipe'`) | — | `agent_sniper_positions` |-| [Autonomous x402 loop](#sec-114) | Yes (`category: 'x402'`) | — | `x402_autonomous_log` |+| [Autonomous x402 loop](#sec-117) | Yes (`category: 'x402'`) | — | `x402_autonomous_log` || x402 service payments | Yes | `payment` | — || [Agora](#sec-077) tasks | On settlement | `agora-*` | on-chain |@@ -80124,14 +84152,14 @@ The same bus powers surfaces that are not tickers at all:## Related-- [Circulation engine](#sec-154) — the largest producer of activity.-- [Autonomous x402 loop](#sec-114) — treasury-paid intel purchases.+- [Circulation engine](#sec-158) — the largest producer of activity.+- [Autonomous x402 loop](#sec-117) — treasury-paid intel purchases.- [Agent wallets](#sec-074) — how spends are gated before they're recorded.-- [x402 endpoints](#sec-619): the *other* direction: money paid **to** our endpoints (`x402_audit_log`), not agent spend.+- [x402 endpoints](#sec-640): the *other* direction: money paid **to** our endpoints (`x402_audit_log`), not agent spend.----<a id="sec-334"></a>+<a id="sec-345"></a>> **Source:** `docs/money-flow-map.md` · [↑ table of contents](#table-of-contents)@@ -80370,14 +84398,14 @@ covering it there. Keep the ordering discipline in `classifyRole`: a rule goes## Related-- [Money Pulse](#sec-333): the event stream these edges are aggregated from.-- [Circulation engine](#sec-154): what generates most of this+- [Money Pulse](#sec-344): the event stream these edges are aggregated from.+- [Circulation engine](#sec-158): what generates most of thisactivity.- [Agent economy volume](#sec-053): the per-agent totals, ranked.----<a id="sec-335"></a>+<a id="sec-346"></a>> **Source:** `docs/money-map.md` · [↑ table of contents](#table-of-contents)@@ -80388,8 +84416,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-619) (the paid endpoint catalog),-[Financial controls](#sec-240) (how settlements are recorded),+Companion docs: [x402 endpoints](#sec-640) (the paid endpoint catalog),+[Financial controls](#sec-246) (how settlements are recorded),[Solana signers runbook](../api/_lib/solana-signers.js) (thesigner/funder wallets and how to fund them).@@ -80429,7 +84457,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-200) subsystem doc.+[economy master](#sec-205) subsystem doc.| Wallet | Role || ------ | ---- |@@ -80489,7 +84517,7 @@ unit economics.[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-619).+ [x402 endpoints](#sec-640).- **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,@@ -80509,9 +84537,9 @@ unit economics.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-563).+ ([api/marketplace/](../api/marketplace)); see [marketplace skills](#sec-583).- **Labor market** — bounty/escrow jobs with worker + author-royalty settlement; see- [labor market](#sec-299).+ [labor market](#sec-310).- **Other** — vanity bounties, forge REST ([api/x402/forge.js](../api/x402/forge.js)),subscriptions, credit deposits.@@ -80521,7 +84549,7 @@ unit economics.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-200) via the `treasury-topup` cron (every 30 min,+[economy master](#sec-205) 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@@ -80532,7 +84560,7 @@ recurring payout crons that forward the flows above:| `treasury-topup` | SOL refill → every low engine signer | `ECONOMY_MASTER_SECRET_BASE58` (funding root) || `club-payouts` | tip sweeps → dancers | `CLUB_SOLANA_TREASURY_*` / `CLUB_EVM_TREASURY_*` || `cosmetic-splits-sweep` | creator USDC payouts | `COSMETIC_SPLIT_TREASURY_*` |-| `run-buyback` | coin buybacks | `PUMP_CRON_RELAYER_*` |+| `run-buyback` / `run-three-buyback` | coin/$THREE buybacks | `PUMP_CRON_RELAYER_*` / `THREE_BUYBACK_*` || `run-distribute-payments` | coin creator/holder payouts | `PUMP_CRON_RELAYER_*` || `process-withdrawals` | user withdrawals | `PLATFORM_TREASURY_KEYPAIR` + `EVM_TREASURY_PRIVATE_KEY` || `x402-autonomous-loop` / `x402-seed-cron` | x402 self-spend (closed loop) | `X402_SEED_SOLANA_SECRET_BASE58` |@@ -80557,22 +84585,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-240) for the full register.+[financial-controls.md](#sec-246) for the full register.## Related-- [Financial controls & audit register](#sec-240) — every ledger's integrity, reconciliation, retention, monitoring, and the ranked gap list.-- [x402 endpoints](#sec-619) — the paid endpoint catalog and price overrides.-- [x402 ring economy](#sec-621) — the internal recirculation loop.-- [Pump platform fee](#sec-393) — the pump trade fee detail.-- [Coin-launch wallets](#sec-565) — launch-time wallet flow.+- [Financial controls & audit register](#sec-246) — every ledger's integrity, reconciliation, retention, monitoring, and the ranked gap list.+- [x402 endpoints](#sec-640) — the paid endpoint catalog and price overrides.+- [x402 ring economy](#sec-642) — the internal recirculation loop.+- [Pump platform fee](#sec-408) — the pump trade fee detail.+- [Coin-launch wallets](#sec-585) — 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-074) — how custodial keys are held.- [Solana signers runbook](../api/_lib/solana-signers.js) — signer/funder wallets + funding.----<a id="sec-336"></a>+<a id="sec-347"></a>> **Source:** `docs/monitor.md` · [↑ table of contents](#table-of-contents)@@ -80698,7 +84726,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-334): the topology behind the totals, who+- [Money Flow Map](#sec-345): the topology behind the totals, whopays whom- [Agent Economy Volume](https://three.ws/agent-economy-volume): the long-windowagent-to-agent hire ledger@@ -80706,7 +84734,7 @@ board a lie.----<a id="sec-337"></a>+<a id="sec-348"></a>> **Source:** `docs/motion-swap.md` · [↑ table of contents](#table-of-contents)@@ -80798,11 +84826,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-097) · [docs/avatar-reconstruction.md](#sec-123)+- [docs/animations.md](#sec-097) · [docs/avatar-reconstruction.md](#sec-126)----<a id="sec-338"></a>+<a id="sec-349"></a>> **Source:** `docs/multi-agent.md` · [↑ table of contents](#table-of-contents)@@ -81145,7 +85173,7 @@ To extend this into a full turn-based scene, add a `brain` attribute to Mira wit----<a id="sec-339"></a>+<a id="sec-350"></a>> **Source:** `docs/native-launchpad.md` · [↑ table of contents](#table-of-contents)@@ -81155,7 +85183,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. Same launch button, same 3D agent identity attached to the coin, different economics underneath.-Related surfaces: [the pump.fun lane](#sec-104) (`/api/pump/*`), [agent wallets](#sec-074) (custody), and [the launch page](https://three.ws/launch).+Related surfaces: [the pump.fun lane](#sec-105) (`/api/pump/*`), [agent wallets](#sec-074) (custody), and [the launch page](https://three.ws/launch).---@@ -81340,7 +85368,7 @@ Stated plainly, because a half-built feature that claims to be finished is worse----<a id="sec-340"></a>+<a id="sec-351"></a>> **Source:** `docs/native-widgets.md` · [↑ table of contents](#table-of-contents)@@ -81352,11 +85380,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-581).+live 3D agent inside a web page are a different product: see [widgets.md](#sec-602).## What the widget shows-Every platform renders the same card, the [Glance card](#sec-257):+Every platform renders the same card, the [Glance card](#sec-263):- the agent's avatar thumbnail (or a generated monogram when the avatar is private),- the agent's name and description,@@ -81369,7 +85397,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-431)).+Requires the three.ws Android app, version 1.1 or later ([seeker-app.md](#sec-447)).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@@ -81432,6 +85460,25 @@ Installs with the PWA, no store submission: open three.ws in Edge, install it, oboard (`Win + W`), **Add widgets**, pick **Agent glance**. It authenticates with your session andrefreshes every 15 minutes. Details in [glance.md](glance.md#on-the-windows-11-widgets-board).+### For developers++The board holds three moving parts: the `widgets` member of the PWA manifest (generated from+`vite.config.js`), the Adaptive Card template at `/api/glance/template`, and+[public/glance-sw.js](../public/glance-sw.js), which is the only thing that ever calls+`widgets.updateByTag`. `npm run check:windows-widget` verifies all three against each other+without Windows, and it is in `npm run gate`.++Two traps are worth knowing before you touch the card, because both draw an empty slot rather+than an error, and neither is visible outside a real board:++- **`msAcTemplate` is the URL of the card, not the card.** The host fetches nothing for you. A+ worker that hands `updateByTag` that string leaves every pinned slot blank.+- **The template is Adaptive Expression Language, not JavaScript.** An array is indexed with+ brackets (`${stats[0].label}`); a dot before a digit is a syntax error, and the engine throws+ on the whole card rather than skipping the one binding, so a single dotted index empties the+ entire widget. `api/_lib/glance-adaptive.js` writes paths the JavaScript way and converts them+ on the way out, and the guard expands the result in the board's own engine to prove it.+## macOS and iOSOne WidgetKit extension serves both, in small, medium and large. It fetches the same@@ -81453,7 +85500,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-293)). Link it exactly+Requires the three.ws iOS app on iOS 17 or later ([ios-app.md](#sec-303)). 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**.@@ -81493,7 +85540,7 @@ reference is in [api-reference.md](api-reference.md#glance-api).----<a id="sec-341"></a>+<a id="sec-352"></a>> **Source:** `docs/news-rights.md` · [↑ table of contents](#table-of-contents)@@ -81587,11 +85634,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-309) — the paid market endpoints, including archive search+- [Market Data API](#sec-320) — the paid market endpoints, including archive search----<a id="sec-342"></a>+<a id="sec-353"></a>> **Source:** `docs/notifications.md` · [↑ table of contents](#table-of-contents)@@ -81935,7 +85982,7 @@ one click from the gear icon in both notification surfaces.## Related pages-- [The social layer](#sec-452): where notification events come from+- [The social layer](#sec-470): 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.@@ -81944,7 +85991,7 @@ one click from the gear icon in both notification surfaces.----<a id="sec-343"></a>+<a id="sec-354"></a>> **Source:** `docs/nvidia-apps-catalog-listing.md` · [↑ table of contents](#table-of-contents)@@ -81952,7 +85999,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-346) (membership overview), [nvidia-models.md](#sec-347) (full model map, the source of truth for every NVIDIA claim below), [nvidia-visibility-map.md](#sec-351) (every other NVIDIA surface, and the asks to batch into the request email below).+Related docs: [nvidia-inception.md](#sec-358) (membership overview), [nvidia-models.md](#sec-359) (full model map, the source of truth for every NVIDIA claim below), [nvidia-visibility-map.md](#sec-363) (every other NVIDIA surface, and the asks to batch into the request email below).---@@ -81985,7 +86032,7 @@ Remove and leave unchecked:### 2. Ask for the catalog listing-The portal has no "publish to catalog" button, so the request goes to the program team. Send the email in [nvidia-apps-catalog-request.md](#sec-344) to `[email protected]` after the record corrections above are saved, and note the send date there. **Sent 2026-09-04.** The ask is now with NVIDIA; nothing further to submit unless they ask for a form or assets.+The portal has no "publish to catalog" button, so the request goes to the program team. Send the email in [nvidia-apps-catalog-request.md](#sec-355) to `[email protected]` after the record corrections above are saved, and note the send date there. **Sent 2026-09-04.** The ask is now with NVIDIA; nothing further to submit unless they ask for a form or assets.---@@ -82123,11 +86170,11 @@ Filing note: this record is independent of the catalog email sent 2026-09-04. It6. Submit. Listings are reviewed on a rolling basis; note the submission date in this doc when done.7. Correct the existing record per the Status section (move Riva/Audio2Face/NIM to Used, drop DeepVariant NIM) BEFORE adding anything new.8. Add the `<agent-3d>` embed as a second product using its section above. Do not file more records than these two: duplicates read as noise to the curator.-9. Send the inclusion-request email in [nvidia-apps-catalog-request.md](#sec-344) to [email protected] and record the send date there.+9. Send the inclusion-request email in [nvidia-apps-catalog-request.md](#sec-355) to [email protected] and record the send date there.----<a id="sec-344"></a>+<a id="sec-355"></a>> **Source:** `docs/nvidia-apps-catalog-request.md` · [↑ table of contents](#table-of-contents)@@ -82135,7 +86182,7 @@ Filing note: this record is independent of the catalog email sent 2026-09-04. ItEverything needed to send the Accelerated Apps Catalog request in one sitting: the pre-send portal fix, the paste-ready email, the assets, and what to do with each reply.-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-351), 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-363), 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@@ -82326,16 +86373,16 @@ Screenshots are deliberately not attached. The email offers them on request, whi## After you send1. Send date recorded in the **Sent** field at the top of this doc.-2. File the second product record, the `<agent-3d>` digital-human embed. Copy is ready in [nvidia-apps-catalog-listing.md](#sec-343) under "Second product record". It targets the Digital Humans workload filter that the main record does not, and it is independent of the reply.+2. File the second product record, the `<agent-3d>` digital-human embed. Copy is ready in [nvidia-apps-catalog-listing.md](#sec-354) under "Second product record". It targets the Digital Humans workload filter that the main record does not, and it is independent of the reply.3. Route each reply:| Reply | Where it goes next ||---|---|-| Catalog form or asset request | Answer same day. Everything is in [nvidia-apps-catalog-listing.md](#sec-343). |+| Catalog form or asset request | Answer same day. Everything is in [nvidia-apps-catalog-listing.md](#sec-354). || Showcase interest | Draft the profile against the engineering posts, not marketing copy. || Co-marketing kit arrives | Unblocks the badge post. Copy is drafted in [marketing/nvidia-inception/social-copy.md](../marketing/nvidia-inception/social-copy.md), owner-gated. |-| ACE redirect | The forum post 3 draft, [nvidia-forum-browser-digital-human.md](#sec-345), is the technical brief to send them. |-| GTC dates | Put them on the watch in [nvidia-visibility-map.md](#sec-351) Tier 3 and write the abstracts. |+| ACE redirect | The forum post 3 draft, [nvidia-forum-browser-digital-human.md](#sec-356), is the technical brief to send them. |+| GTC dates | Put them on the watch in [nvidia-visibility-map.md](#sec-363) Tier 3 and write the abstracts. || No reply in 3 weeks | One follow-up on ask 1 only, and use the "Maximize Your Membership" webinar Q&A to ask 2 and 3 live. |## Verification log@@ -82349,7 +86396,7 @@ Checked 2026-09-04 before this packet was finalized:----<a id="sec-345"></a>+<a id="sec-356"></a>> **Source:** `docs/nvidia-forum-browser-digital-human.md` · [↑ table of contents](#table-of-contents)@@ -82436,7 +86483,99 @@ Happy to go deeper on any of it, particularly the derived-blendshape path, which----<a id="sec-346"></a>+<a id="sec-357"></a>++> **Source:** `docs/nvidia-forum-gpu-fleet-post.md` · [↑ table of contents](#table-of-contents)++---+venue: NVIDIA Developer Forums (community showcase / Cloud & Data Center)+account: three.ws (official)+suggested_title: "Running a free text-to-3D service on L4s: cold starts, keep-warm crons, and the quota arithmetic nobody publishes"+description: "The fourth three.ws write-up for the NVIDIA developer community: how a free, keyless text-to-3D and avatar service is served from a self-hosted Cloud Run GPU fleet of L4s plus an RTX PRO 6000 Blackwell, what a FUSE-mounted weight load costs on a cold start, why min-instances is a quota decision and not a performance one, and how the NIM free tier fits into a chain that must never have an empty rung."+tags: [l4, blackwell, nim, nemotron, inception, inference, cloud]+status: draft, owner approval required before posting (external-channel gate in CLAUDE.md)+---++# Running a free text-to-3D service on L4s: cold starts, keep-warm crons, and the quota arithmetic nobody publishes++I run [three.ws](https://three.ws), an open-source platform where you type a sentence and get a textured, rigged, animated 3D character. I have written here three times before: [Nemotron in front of the text-to-3D generator](https://forums.developer.nvidia.com/t/how-nemotron-made-three-ws-text-to-3d-pipeline-usable/376445), [NIM driving a 100-language i18n pipeline](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), and a browser-tab digital human streaming Audio2Face-3D onto whatever rig the visitor brought.++This one is about the boring half that keeps the free lane free: the fleet. three.ws is an NVIDIA Inception member; that is a startup programme, not a partnership or an endorsement, and nothing below is an NVIDIA statement.++The thing I want to write down is the arithmetic, because every other "we run open models in production" post I read skipped it, and the arithmetic is where the design lives.++## The fleet++Every generation lane runs as its own Cloud Run service on an **NVIDIA L4** in `us-central1`, plus one **RTX PRO 6000 Blackwell** for the heaviest work. They all speak one task shape (`POST /<endpoint>` returns a task id, `GET /tasks/:id` returns status and result) and share one bearer secret, which means the router does not care which model is behind a lane.++The lanes, and what each is for:++- **TRELLIS** (`model-trellis`): native single-hop image to 3D. Accepts a user's photo, and also the synthesized view that the text lane produces. Textured GLB out.+- **Hunyuan3D** (`model-hunyuan3d`): high-poly image-conditioned reconstruction, poly-budget aware.+- **TripoSG** (`model-triposg`): sketch to 3D. A drawing plus a prompt naming it, untextured geometry out.+- **TripoSR**, plus the mesh pipeline around all of them: rigging, remeshing, texturing, segmentation, stylization, background removal, garment generation, avatar reconstruction from photos, text to motion, video to motion, video to scene, and sign-language synthesis.++Thirty-two workers in total, most of them Docker images you can build and run yourself. The point of self-hosting was never cost alone: it is that a lane we host is a lane we can debug, and a free-tier vendor lane is a lane that changes under you.++## Cold starts are a model-load problem, not a container problem++The single most misleading metric in serverless GPU work is container start time. Ours is fine. The cost is the **weight load**, and on a FUSE-mounted weight volume a cold load can stall for minutes before the job even begins.++Three consequences that shaped the product:++**1. `min-instances` is a quota decision, not a performance one.** The obvious move is min 1 everywhere. You cannot: a regional L4 grant is small (ours is 3 in `us-central1`, with a separate grant of 3 in `us-east4`), and pinning warm instances on every lane starves the lanes that need to burst. So one lane pins an always-warm instance and bursts to three, another was moved to min 0 explicitly to free the shared pool, and the sketch lane scales to zero because its traffic is spiky and its users are patient. Those are three different answers to the same question, and the right answer is per-lane.++**2. A keep-warm cron beats a bigger floor.** A scheduled tick during peak hours holds an allowlist of scale-to-zero lanes resident, and the allowlist is an environment variable so it can change without a deploy. One detail worth stealing: **a lane id in that override that matches no known lane is reported back and fails the tick**, rather than quietly warming nothing. A typo in a keep-warm config is otherwise invisible until somebody complains about latency two weeks later.++**3. Surface the cold start honestly.** When a lane is cold, the user is told a real thing (the model is loading) with a real estimate, not a fake progress bar that fills at a constant rate regardless of what is happening. Our text-to-3D path goes through an intermediate image, so we can also show the concept art the geometry model is about to sculpt. Showing something true makes the wait feel shorter than animating something false.++## Quota starvation looks exactly like a bug++Worth naming because it cost us a debugging session. When the regional L4 pool is exhausted, requests do not fail in a way that says "quota". They fail slowly, in a pattern that reads like a model problem or a network problem. We now have a named signature for it in our triage runbook, and the first check on any "generation is slow" report is the pool, not the model.++The corollary, and this is the operational rule I would give anyone building on a granted GPU pool: **file the quota increase the moment you hit the ceiling, then route around it in the same hour.** Lower a min-instance somewhere else, use the other region's grant, queue behind existing capacity. Parking the feature on the quota request is how a two-day problem becomes a two-week one.++## Failover per lane, and the rung that must never be empty++Every generation lane has a failover chain, so an unavailable model degrades quality rather than failing the request. The same discipline runs on the text side, and that chain is the one where NIM sits.++The text chain tries free rungs first, in order, and only touches a paid key as a last resort. NVIDIA NIM is one of the free rungs (Nemotron, on the free developer tier). Two hard-won notes for anyone building a similar chain:++**Model end-of-life is a silent outage.** When a family we depended on reached end of life on NIM, the rung answered `410`. Our chain fell through correctly, but the deeper lesson was that a chain is only as good as its awareness of upstream catalogue changes, so a scheduled job now diffs our hardcoded model ids against the live catalogues and tells us before users do.++**Reasoning models need an explicit flag.** The Nemotron rung is a reasoning family, so it sends `enable_thinking: false` to keep the answer in `content` rather than in a reasoning field the caller does not read. A chain that treats every provider as interchangeable will produce empty answers on exactly the rungs that are working.++**Never let the chain be empty.** Two rungs in ours are keyless on purpose, so there is always something at the bottom. A failover chain whose last rung requires a key that might be unset is a chain with a hole in it.++## What "free and keyless" actually costs++The free 3D lane needs no account, no key, and no payment. That is a product decision with an infrastructure bill behind it, and the bill is manageable for three specific reasons:++1. **Scale to zero where the traffic is spiky**, and pay standing GPU-hours only where a cold load would be visibly bad.+2. **Self-host the lanes we can**, so the marginal generation costs compute rather than vendor margin.+3. **Grade before you spend.** Two of our free endpoints exist to *avoid* GPU work: a physics-readiness grade that tells a caller whether an asset is usable before they invest in it, and a vision tool that lets an agent look at what it generated and decide whether to iterate. A check that costs money is a check nobody runs, and a caller who cannot evaluate a result will re-generate blindly, which costs everyone more.++## Try it, and check the claims++Free, keyless, no account:++```bash+# text to a textured GLB+curl -s -X POST https://three.ws/api/3d/studio \+ -H 'content-type: application/json' \+ -d '{"prompt":"a small ceramic robot figurine"}'++# is the result usable as a rigid body?+curl "https://three.ws/api/sim-readiness?src=<glb url>"+```++The workers, the routing, the keep-warm cron, and the failover chains are all in the open repository at [github.com/nirholas/three.ws](https://github.com/nirholas/three.ws) (Apache-2.0), and `GET https://three.ws/api/version` returns the exact commit production is running, so anything above can be checked against the code that serves it.++If you run generation lanes on granted GPU capacity, I would like to compare notes on two things: how you decide which lanes deserve a warm floor, and whether anyone has found a better answer to cold weight loads than "pay for a floor and be honest about the wait".++---++<a id="sec-358"></a>> **Source:** `docs/nvidia-inception.md` · [↑ table of contents](#table-of-contents)@@ -82474,7 +86613,7 @@ Membership is a startup program, not a partnership or an investment: NVIDIA revi## Related-- [NVIDIA visibility map](#sec-351): every NVIDIA surface where three.ws can earn recognition, what each one requires, and which membership benefits are still unclaimed+- [NVIDIA visibility map](#sec-363): 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@@ -82482,7 +86621,7 @@ Membership is a startup program, not a partnership or an investment: NVIDIA revi----<a id="sec-347"></a>+<a id="sec-359"></a>> **Source:** `docs/nvidia-models.md` · [↑ table of contents](#table-of-contents)@@ -82694,7 +86833,7 @@ The free NVIDIA TTS lane: **Magpie multilingual on Riva**, selected by an NVCF `----<a id="sec-348"></a>+<a id="sec-360"></a>> **Source:** `docs/nvidia-nemotron-ask-the-experts-questions.md` · [↑ table of contents](#table-of-contents)@@ -82798,11 +86937,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-346) |-| `nvidia/nemotron-nano-12b-v2-vl` gates every photo-to-3D generation, 1-2s | [nvidia-nemotron-spotlight.md](#sec-349), `api/_lib/forge-image-validate.js` |-| ~281 image prompt tokens vs ~1,600 for a 90B-class VLM | [nvidia-nemotron-spotlight.md](#sec-349) |+| NVIDIA Inception member, accepted July 2026 | [nvidia-inception.md](#sec-358) |+| `nvidia/nemotron-nano-12b-v2-vl` gates every photo-to-3D generation, 1-2s | [nvidia-nemotron-spotlight.md](#sec-361), `api/_lib/forge-image-validate.js` |+| ~281 image prompt tokens vs ~1,600 for a 90B-class VLM | [nvidia-nemotron-spotlight.md](#sec-361) || 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-349) |+| `nvidia-nemotron-nano-9b-v2` used for reasoning turns, NemoGuard at ~340 ms median | [nvidia-nemotron-spotlight.md](#sec-361) |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@@ -82889,7 +87028,7 @@ plus a reported trillion-parameter Nemotron 4 in training.----<a id="sec-349"></a>+<a id="sec-361"></a>> **Source:** `docs/nvidia-nemotron-spotlight.md` · [↑ table of contents](#table-of-contents)@@ -83050,17 +87189,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-347), and the pipeline internals are in [`docs/3d-asset-pipeline.md`](#sec-002). three.ws joined the [NVIDIA Inception program](#sec-346) 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-359), and the pipeline internals are in [`docs/3d-asset-pipeline.md`](#sec-002). three.ws joined the [NVIDIA Inception program](#sec-358) 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-350"></a>+<a id="sec-362"></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-351) records that no self-serve+[nvidia-visibility-map.md](#sec-363) 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@@ -83071,7 +87210,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-343).+kit in [nvidia-apps-catalog-listing.md](#sec-354).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@@ -83247,15 +87386,15 @@ and none of them are an agent's call:## Related-- [NVIDIA visibility map](#sec-351): every other NVIDIA surface and its intake route-- [Accelerated Apps Catalog listing kit](#sec-343) and [inclusion request](#sec-344)-- [NVIDIA Inception membership](#sec-346): what membership is, and the rule that it is not an endorsement-- [NVIDIA models on three.ws](#sec-347): the source of truth for every NVIDIA technical claim-- [Listings and distribution](#sec-305): the canonical program and directory inventory+- [NVIDIA visibility map](#sec-363): every other NVIDIA surface and its intake route+- [Accelerated Apps Catalog listing kit](#sec-354) and [inclusion request](#sec-355)+- [NVIDIA Inception membership](#sec-358): what membership is, and the rule that it is not an endorsement+- [NVIDIA models on three.ws](#sec-359): the source of truth for every NVIDIA technical claim+- [Listings and distribution](#sec-316): the canonical program and directory inventory----<a id="sec-351"></a>+<a id="sec-363"></a>> **Source:** `docs/nvidia-visibility-map.md` · [↑ table of contents](#table-of-contents)@@ -83266,8 +87405,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-343)-for the listing kit and [nvidia-apps-catalog-request.md](#sec-344)+not re-litigated here. See [nvidia-apps-catalog-listing.md](#sec-354)+for the listing kit and [nvidia-apps-catalog-request.md](#sec-355)for the inclusion email. This doc covers everything else and links to them wherethey overlap.@@ -83313,10 +87452,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 benefit request, or `[email protected]` | An entitlement we have never claimed. See [Benefits we are owed](#benefits-we-are-entitled-to-and-have-never-requested). |-| 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-343) step 1. Nothing else in this doc lands well while the record says "CUDA consumer". |+| 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-354) step 1. Nothing else in this doc lands well while the record says "CUDA consumer". || 4 | **Inception Startup Showcase** | `[email protected]` | NVIDIA's own wording is "member spotlights and story opportunities". Curated from the portal record, so do #3 first. || 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 3** | [forums.developer.nvidia.com](https://forums.developer.nvidia.com) | We are 2 for 2 on posts that landed. This is the one channel with a proven track record, and it is self-serve. **Drafted 2026-09-02: [nvidia-forum-browser-digital-human.md](#sec-345).** Owner-gated on the external-channel rule, then paste and post. See [Technical publishing](#technical-publishing-the-proven-channel). |+| 6 | **NVIDIA Developer Forums, post 3** | [forums.developer.nvidia.com](https://forums.developer.nvidia.com) | We are 2 for 2 on posts that landed. This is the one channel with a proven track record, and it is self-serve. **Drafted 2026-09-02: [nvidia-forum-browser-digital-human.md](#sec-356).** 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. |@@ -83365,10 +87504,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-350) 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-362) 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-343) 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-354) 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@@ -83482,7 +87621,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 written: [nvidia-forum-browser-digital-human.md](#sec-345)** (drafted+**It is written: [nvidia-forum-browser-digital-human.md](#sec-356)** (drafted2026-09-02). 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@@ -83492,6 +87631,13 @@ Latencies in it were measured against the live endpoint the day it was written,not estimated. It is owner-gated under the external-channel rule: paste and postwhen approved.+## Drafted, not yet posted++| Draft | Subject |+|---|---|+| [nvidia-forum-gpu-fleet-post.md](#sec-357) | 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 |+| [nvidia-forum-browser-digital-human.md](#sec-356) | Audio2Face-3D streamed onto a rig the visitor generated ninety seconds earlier |+## Benefits we are entitled to and have never requestedStraight from NVIDIA's [Inception program page](https://www.nvidia.com/en-us/startups/).@@ -83524,7 +87670,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-350).+ a partner intake form; see [nvidia-ngc-listing.md](#sec-362).Stop looking for a form anywhere else.- **Omniverse Launcher guides.** Deprecated 2025-10-01. Any tutorial routingthrough it is stale.@@ -83546,7 +87692,7 @@ Recorded so the next person does not repeat the search.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.** [nvidia-apps-catalog-request.md](#sec-344)+**Sent 2026-09-04.** [nvidia-apps-catalog-request.md](#sec-355)carries all five asks (catalog listing, Showcase nomination, co-marketing kit,ACE redirect, GTC pavilion and event slots) and went to the inbox in one threadfrom [email protected]. **Do not start a second thread.** Tier 1 items 2 and 4@@ -83554,7 +87700,7 @@ above are now pending NVIDIA rather than pending us. Reply routing for each ask,and the 2026-09-25 follow-up date, live in the request doc.Still ours to finish regardless of the reply: the portal record correction (step 1-of [nvidia-apps-catalog-listing.md](#sec-343)), because a+of [nvidia-apps-catalog-listing.md](#sec-354)), 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@@ -83588,18 +87734,18 @@ gcloud run services list --project aerial-vehicle-466722-p5 \## Related-- [Big-tech recognition dispatch board](#sec-135): 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.-- [NVIDIA Inception membership](#sec-346): what membership is, and the rule that it is a program and not a partnership or an endorsement-- [Apps Catalog listing kit](#sec-343) and [inclusion request](#sec-344): the curated marketing listing-- [NGC Catalog listing kit](#sec-350): the self-serve software listing, its prerequisite audit, and the container that clears it-- [NVIDIA models on three.ws](#sec-347): the source of truth for every NVIDIA technical claim made in any pitch-- [Listings and distribution](#sec-305): the canonical program and directory inventory+- [Big-tech recognition dispatch board](#sec-138): 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.+- [NVIDIA Inception membership](#sec-358): what membership is, and the rule that it is a program and not a partnership or an endorsement+- [Apps Catalog listing kit](#sec-354) and [inclusion request](#sec-355): the curated marketing listing+- [NGC Catalog listing kit](#sec-362): the self-serve software listing, its prerequisite audit, and the container that clears it+- [NVIDIA models on three.ws](#sec-359): the source of truth for every NVIDIA technical claim made in any pitch+- [Listings and distribution](#sec-316): the canonical program and directory inventory- [Announcement coverage](#sec-100): which surfaces have been announced and which have not-- [Partners](#sec-368): the independence and no-endorsement language that must survive any rewrite+- [Partners](#sec-381): the independence and no-endorsement language that must survive any rewrite----<a id="sec-352"></a>+<a id="sec-364"></a>> **Source:** `docs/object-library.md` · [↑ table of contents](#table-of-contents)@@ -83610,7 +87756,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-148). For how AR placement works on phones and desktops, see [AR & WebXR](#sec-107).+> This page covers the object gallery and its API. For rigged, animation-ready characters, see the [Character Library](#sec-152). For how AR placement works on phones and desktops, see [AR & WebXR](#sec-108).---@@ -83626,8 +87772,8 @@ Each card renders the object live in an auto-rotating `<model-viewer>` (with the| Button | Destination | What you get ||---|---|---|-| **Preview** | `/app#model=<glb-url>&kind=object&title=<name>` | The full three.js [3D viewer](#sec-575) in object mode (no agent chat; Restyle, AR, and Download affordances instead) |-| **AR** | `/ar/studio?src=<glb-url>&title=<name>` | [AR Studio](#sec-106): place the prop in your real space through the camera (see [AR & WebXR](#sec-107) for how the AR handoff works per device) |+| **Preview** | `/app#model=<glb-url>&kind=object&title=<name>` | The full three.js [3D viewer](#sec-595) in object mode (no agent chat; Restyle, AR, and Download affordances instead) |+| **AR** | `/ar/studio?src=<glb-url>&title=<name>` | [AR Studio](#sec-107): place the prop in your real space through the camera (see [AR & WebXR](#sec-108) for how the AR handoff works per device) || **Download** | The GLB URL directly | The raw GLB file, CC0, yours to use anywhere |Gallery controls:@@ -83640,7 +87786,7 @@ Gallery controls:## API: `GET /api/objects/library`-Public, no authentication, `GET` and `OPTIONS` only (`HEAD` is answered like `GET`). Browser `fetch` from a third-party origin is not enabled: like the [Character Library API](#sec-148), the endpoint sends `Access-Control-Allow-Origin` only for three.ws and its partner origins, and the R2 CDN holding the GLBs is scoped the same way. Call it server-side, or from a three.ws page, and the assets it points at are still yours to download and redistribute anywhere (a download or a server-side fetch is not CORS-gated; only in-browser cross-origin reads are). 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-148) exactly, with `objects` in place of `avatars`.+Public, no authentication, `GET` and `OPTIONS` only (`HEAD` is answered like `GET`). Browser `fetch` from a third-party origin is not enabled: like the [Character Library API](#sec-152), the endpoint sends `Access-Control-Allow-Origin` only for three.ws and its partner origins, and the R2 CDN holding the GLBs is scoped the same way. Call it server-side, or from a three.ws page, and the assets it points at are still yours to download and redistribute anywhere (a download or a server-side fetch is not CORS-gated; only in-browser cross-origin reads are). 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-152) exactly, with `objects` in place of `avatars`.### Query parameters@@ -83707,14 +87853,14 @@ The gallery and API are read-only consumers of a manifest built by a local pipel## Related-- [Character Library](#sec-148): the rigged, animation-ready counterpart to this library.-- [AR & WebXR](#sec-107): the device-by-device AR methods behind the AR button.-- [AR Studio](#sec-106): the `/ar/studio` surface the AR button opens, including multi-object rooms.-- [3D Viewer](#sec-575): the `/app` engine the Preview button opens in object mode.+- [Character Library](#sec-152): the rigged, animation-ready counterpart to this library.+- [AR & WebXR](#sec-108): the device-by-device AR methods behind the AR button.+- [AR Studio](#sec-107): the `/ar/studio` surface the AR button opens, including multi-object rooms.+- [3D Viewer](#sec-595): the `/app` engine the Preview button opens in object mode.----<a id="sec-353"></a>+<a id="sec-365"></a>> **Source:** `docs/okx-marketplace.md` · [↑ table of contents](#table-of-contents)@@ -83742,8 +87888,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-104) · [MCP servers](#sec-318) ·-> [x402 payments](#sec-624) · seller-side protocol spec:+> Related: [REST API Reference](#sec-105) · [MCP servers](#sec-329) ·+> [x402 payments](#sec-645) · 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,@@ -83992,7 +88138,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-318) runs. `GET` on any of them returns its free+same engines the [MCP 3D studio](#sec-329) runs. `GET` on any of them returns its freedescriptor (price, description, input schema).| Service | Price (USDT) | Endpoint | You send |@@ -84026,7 +88172,7 @@ pinned down in [`specs/okx-agent-payments.md`](../specs/okx-agent-payments.md).----<a id="sec-354"></a>+<a id="sec-366"></a>> **Source:** `docs/onboarding-tier.md` · [↑ table of contents](#table-of-contents)@@ -84173,17 +88319,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-461) — the same journey, written for a human rather than a maintainer+- [`docs/start-here.md`](#sec-479) — the same journey, written for a human rather than a maintainer----<a id="sec-355"></a>+<a id="sec-367"></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-455): 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-473): 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.@@ -84248,7 +88394,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-455) 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-473) mints into the *same* collection.---@@ -84461,14 +88607,14 @@ A confirmed canary asset shows `inCollection=true`, `royalty=500bps`, `attrs=11`## See also-- [Solana agents](#sec-455) — the single-agent, user-signed registration flow.-- [ERC-8004](#sec-206) — the EVM on-chain identity path.+- [Solana agents](#sec-473) — the single-agent, user-signed registration flow.+- [ERC-8004](#sec-211) — the EVM on-chain identity path.- [Agent manifest](#sec-056) — the metadata schema.-- [Mint mark ("3ws")](#sec-323) — vanity marking for three.ws launches.+- [Mint mark ("3ws")](#sec-334) — vanity marking for three.ws launches.----<a id="sec-356"></a>+<a id="sec-368"></a>> **Source:** `docs/open-source-ecosystem.md` · [↑ table of contents](#table-of-contents)@@ -84715,7 +88861,7 @@ Thank you for the first hundred.----<a id="sec-357"></a>+<a id="sec-369"></a>> **Source:** `docs/open-source-footprint.md` · [↑ table of contents](#table-of-contents)@@ -84723,7 +88869,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-305) (marketplace status and submission history), [x402-distribution.md](#sec-618) (every x402 crawler and directory, with mechanism), [community.md](#sec-165), [partners.md](#sec-368).+Related: [listings.md](#sec-316) (marketplace status and submission history), [x402-distribution.md](#sec-639) (every x402 crawler and directory, with mechanism), [community.md](#sec-169), [partners.md](#sec-381).## The repo@@ -84761,7 +88907,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-133)) | listing not yet created |+| AWS Marketplace | SaaS metering integration built ([aws-marketplace.md](#sec-136)) | 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 |@@ -84789,7 +88935,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-206) | same address on every EVM chain |+| ERC-8004 registries | Identity `0x8004A169FB4a3325136EB29fA0ceB6D2e539a432`, Reputation `0x8004BAa17C55a88189AE136b182e5fdA19dE9b63`, see [erc8004.md](#sec-211) | 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 |@@ -84816,7 +88962,7 @@ Mint `FeMbDoX7R1Psc4GEcvJdsbNbZA3bfztcyDCatJVJpump`. Venues: [pump.fun (verified----<a id="sec-358"></a>+<a id="sec-370"></a>> **Source:** `docs/open-source-friday-plan.md` · [↑ table of contents](#table-of-contents)@@ -84842,8 +88988,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-165) and wired into the README, CONTRIBUTING, and the new-issue chooser. |-| *Preferred:* triage team / contributor onboarding | **PASS** | [docs/triage.md](#sec-480) (labels, claiming, published response targets) and [docs/first-contribution.md](#sec-241) (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-169) and wired into the README, CONTRIBUTING, and the new-issue chooser. |+| *Preferred:* triage team / contributor onboarding | **PASS** | [docs/triage.md](#sec-500) (labels, claiming, published response targets) and [docs/first-contribution.md](#sec-247) (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** |@@ -84872,9 +89018,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-165) 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-241) 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-480) 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-169) 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-247) 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-500) 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)@@ -85010,7 +89156,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-608)) | Owner |+| 2026-08-25 | Reply to Andrea's X thread with the issue link (draft: [x-posts/osf-issue-reply.md](#sec-629)) | Owner || 2026-08-28+ | Booking link arrives on approval, book the slot | Owner || ~2026-09-11 | Stream (earliest date satisfying the two-week rule) | Owner |@@ -85026,7 +89172,7 @@ The license question that used to sit here is resolved: Apache-2.0, shipped 2026----<a id="sec-359"></a>+<a id="sec-371"></a>> **Source:** `docs/openai-community-3d-studio-post.md` · [↑ table of contents](#table-of-contents)@@ -85302,7 +89448,7 @@ nich----<a id="sec-360"></a>+<a id="sec-372"></a>> **Source:** `docs/openai-community-physical-world-post.md` · [↑ table of contents](#table-of-contents)@@ -85597,7 +89743,7 @@ A recurring question in the original thread was some version of "great, I generaThere are also framework and use-case wrappers: [`@three-ws/react`](https://www.npmjs.com/package/@three-ws/react), an avatar overlay that reacts to buttons and navigation, a floating concierge chat widget, a page narrator that reads the page it lives on, a walk companion that roams a corner of the screen, and a guided tour agent. All of them are paste-in snippets with no backend on your side.-**Animation, which is the part people underestimate.** A rigged model is useless if your clip library only fits one naming convention. Ours canonicalises bone names across Mixamo, Avaturn, Unreal, VRM and VRoid, VRM 1.0, Daz/Genesis, MakeHuman, Blender `.L`/`.R`, and simple `shoulderL` rigs, then retargets idle, walk and the rest onto whatever came in, legs included. There is **no rig allowlist**: a model that genuinely cannot be skeleton-driven falls back to a default rig rather than a bind-pose T-pose. That logic is published as [`@three-ws/retarget`](https://www.npmjs.com/package/@three-ws/retarget). If you have ever hand-mapped a skeleton, this is the package to steal.+**Animation, which is the part people underestimate.** A rigged model is useless if your clip library only fits one naming convention. Ours canonicalises bone names across Mixamo, Unreal, VRM and VRoid, VRM 1.0, Daz/Genesis, MakeHuman, Blender `.L`/`.R`, and simple `shoulderL` rigs, then retargets idle, walk and the rest onto whatever came in, legs included. There is **no rig allowlist**: a model that genuinely cannot be skeleton-driven falls back to a default rig rather than a bind-pose T-pose. That logic is published as [`@three-ws/retarget`](https://www.npmjs.com/package/@three-ws/retarget). If you have ever hand-mapped a skeleton, this is the package to steal.**Delivery.** [`@three-ws/avatar-stream`](https://www.npmjs.com/package/@three-ws/avatar-stream) packs a GLB into a layered progressive stream over plain HTTP, so a heavy avatar shows something correct early instead of blocking on the whole file. [`@three-ws/render`](https://www.npmjs.com/package/@three-ws/render) renders rigged avatars to PNG, GIF, and truecolor terminal frames server-side, which is how the same agent shows up in a GitHub README, a Slack message, and a Windows 11 widget board.@@ -85712,7 +89858,7 @@ Happy to answer anything about the internals. The whole stack is Apache-2.0 at [----<a id="sec-361"></a>+<a id="sec-373"></a>> **Source:** `docs/openai-listing-channels.md` · [↑ table of contents](#table-of-contents)@@ -85720,7 +89866,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-305) (every listing across all vendors), [mcp.md](#sec-318) (the hosted MCP server a plugin submission depends on), [nvidia-apps-catalog-listing.md](#sec-343) (the same kind of kit for NVIDIA).+Related docs: [listings.md](#sec-316) (every listing across all vendors), [mcp.md](#sec-329) (the hosted MCP server a plugin submission depends on), [nvidia-apps-catalog-listing.md](#sec-354) (the same kind of kit for NVIDIA).---@@ -85750,7 +89896,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-318)) |+| Public MCP server | `https://three.ws/api/mcp`, Streamable HTTP, MCP `2025-06-18` ([mcp.md](#sec-329)) || 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` |@@ -85770,7 +89916,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-318).+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-329).### Known rejection reasons to design against@@ -85824,7 +89970,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-359) (the original Apps SDK plus Actions build writeup) and [openai-community-physical-world-post.md](#sec-360) (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-371) (the original Apps SDK plus Actions build writeup) and [openai-community-physical-world-post.md](#sec-372) (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).---@@ -85860,7 +90006,7 @@ Not OpenAI-owned, so they do not answer the original question, but they are wher----<a id="sec-362"></a>+<a id="sec-374"></a>> **Source:** `docs/oracle-model.md` · [↑ table of contents](#table-of-contents)@@ -86299,7 +90445,7 @@ of why the model went nineteen days without a refit.----<a id="sec-363"></a>+<a id="sec-375"></a>> **Source:** `docs/oracle-trading-mcp-plan.md` · [↑ table of contents](#table-of-contents)@@ -86519,7 +90665,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/oracle-trading-mcp-x-post.md`](#sec-607). Written before+Draft lives at [`docs/oracle-trading-mcp-x-post.md`](#sec-628). 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.@@ -86553,7 +90699,7 @@ than shipping late.----<a id="sec-364"></a>+<a id="sec-376"></a>> **Source:** `docs/oracle.md` · [↑ table of contents](#table-of-contents)@@ -86592,7 +90738,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-362).+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-374).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`.@@ -86956,7 +91102,342 @@ The more data we watch, the sharper every score. Oracle is live now.----<a id="sec-365"></a>+<a id="sec-377"></a>++> **Source:** `docs/oss-adoption-2026-09.md` · [↑ table of contents](#table-of-contents)++# Open-source adoption plan, September 2026++A survey of open-source repos, npm packages, and model weights that three.ws+does **not** already use, ranked by what they would actually change here, with+the exact file each one lands in.++This is the decision document. Its sibling+[popular-3d-github-repos.md](#sec-395) is a popularity+snapshot of the whole 3D ecosystem; that one answers "what exists", this one+answers "what should we adopt, and where does it go".++## How this list was built++Three passes, run on 2026-09-07:++1. **Gap detection.** A presence sweep of roughly 250 candidate project names+ across `src/`, `api/`, `workers/`, `packages/`, `services/`, `scripts/`, and+ `server/`, in two rounds: one scoped to 3D and one across every other surface+ (audio, vision, LLM tooling, web infra, security, database, docs, i18n).+ Anything already wired was dropped, and that was most of the obvious list:+ Kokoro TTS, `@pixiv/three-vrm`, Make-It-Animatable, TRELLIS, Hunyuan3D+ 2.0/2.1, TripoSG, MDM, QuadriFlow, xatlas, meshoptimizer, Colyseus, Yjs,+ Rapier, gltf-transform, onnxruntime-web. **This document only contains things+ the repo genuinely lacks.**+2. **Verification.** Every license, star count, and last-push date below came+ from the GitHub REST API or the npm registry directly, not from a blog. The+ "best of 2026" listicles were checked and discarded: several assert a+ "TRELLIS.2" release that does not exist in `microsoft/TRELLIS`. Where GitHub+ reports `NOASSERTION`, the LICENSE file itself was read.+3. **Measurement, where a claim was cheap to test.** The BiRefNet latencies were+ measured, not quoted, and the Spark migration was driven in a real browser.++Star counts are as of the sweep date and drift.++---++## Shipped in this pass++### 1. Spark, replacing the splat renderer++**[sparkjsdev/spark](https://github.com/sparkjsdev/spark)**+(`@sparkjsdev/spark`, MIT, 3.6k stars, by World Labs).++[/splat](https://three.ws/splat) ran on `@mkkellogg/gaussian-splats-3d`, which+reads `.ply`, `.splat`, and `.ksplat` and renders inside a private viewer of its+own. Three problems followed from that, and all three are fixed:++- **It could not open the formats real captures ship.** The same scene that is a+ 1 GB PLY is roughly 100 MB as [SPZ](https://github.com/nianticlabs/spz) (MIT,+ Niantic) and roughly 42 MB as+ [SOG](https://developer.playcanvas.com/user-manual/gaussian-splatting/formats/sog/)+ (PlayCanvas), 15 to 20 times smaller. Those are the files people are handed+ today and what SuperSplat exports. Both now load.+- **The format was guessed from the filename.** It is now read from the bytes,+ so a URL with a query string, a redirect, or no extension still decodes.+- **The camera sat at a fixed z=3.2 for every scene.** It now frames the splat+ centres in world space, which is the only thing that works across captures+ authored at wildly different scales.++Two things the migration surfaced that are worth writing down, because both look+like a broken page and neither is:++- Spark accumulates colour with premultiplied alpha and leaves destination alpha+ at zero. On a transparent canvas the browser composites a fully rendered scene+ away to nothing. The canvas has to be opaque.+- Spark sorts splats on a worker and only paints once that first sort lands, up+ to about a second on a weak GPU. The page now holds a "Sorting splats" state+ until Spark reports it has something to draw, with a timeout so a scene that+ never reports back is still handed over.++Verified in a real browser against `butterfly.spz` (177,132 splats) and both+procedural samples: correct framing, correct orientation, live splat counts in+the HUD, no console errors.++Both splat surfaces now share one engine, [src/splat-stage.js](../src/splat-stage.js):+the viewer and the Forge Studio Lab need the same scene and the same three+gotchas above, and having them in one module is what stops one copy from+rotting. `@mkkellogg/gaussian-splats-3d` was removed from the dependency tree.++### 2. BiRefNet as an optional background-removal model++**[ZhengPeng7/BiRefNet](https://github.com/ZhengPeng7/BiRefNet)** (MIT, 4.2k+stars).++The [rembg worker](../workers/rembg) ran four DIS/U2Net-family models. Those+smear a soft boundary (hair, fur, foliage, a thin strap) into a halo, and since+every image-to-3D lane reconstructs geometry from the matted subject, that halo+becomes real polygons on the finished mesh.++The pinned `rembg==2.0.59` already ships BiRefNet sessions; the worker's model+allowlist simply did not include them. `birefnet-general-lite` is now a+selectable model (short alias `birefnet`) across the worker,+`api/forge-rembg.js`, the x402 pipeline, the service catalog, and the MCP studio+tool.++Measured on 4 threads with the repo's pinned `onnxruntime==1.28.0`, best of three+warm runs at 677x1024:++| Model | Weights | Latency |+|---|---|---|+| `isnet-general-use` (default) | 170 MB | 1.0 s |+| `birefnet-general-lite` | 214 MB | 6.0 s |++Six times the compute is worth it on a hero image and not worth it on a batch,+so the default is unchanged and the policy tests pin it that way. Details:+[workers/rembg/README.md](../workers/rembg/README.md).++Note the license trap this avoids: **RMBG-2.0** is the model most "best+background removal" write-ups recommend, it is built on BiRefNet, and it is+CC BY-NC 4.0. BiRefNet itself is MIT.++---++## Tier 1: adopt next++### OpenTelemetry, for fleet observability++**[open-telemetry/opentelemetry-js](https://github.com/open-telemetry/opentelemetry-js)**+(Apache-2.0, 3.5k stars).++The platform runs 115 Cloud Scheduler crons and 30-plus Cloud Run services, and+the only cross-cutting instrumentation is Sentry error capture+([api/_lib/sentry.js](../api/_lib/sentry.js)). There is no distributed trace, so+a slow `/forge` request that fans out to rembg, a mesh lane, rig, and texture+cannot be attributed to a stage without reading four services' logs by hand.++GCP has a first-party OTLP endpoint, so this is a pre-approved-surface adoption+with no new vendor.++**Where it lands:** [server/index.mjs](../server/index.mjs) (boot),+`api/_providers/gcp.js` (propagating `traceparent` to the workers), and each+Python worker's FastAPI app for the far end of the span.++### LHM, for one-selfie photoreal humans++**[aigc3d/LHM](https://github.com/aigc3d/LHM)** (Apache-2.0, 2.7k stars,+ICCV 2025).++[workers/avatar-reconstruction](../workers/avatar-reconstruction) fits a selfie+onto a fixed-topology Wolf3D template: MediaPipe landmarks, a TPS texture warp,+and a geometry morph. That is a sound, CPU-cheap, commercially clean design, and+it is bounded by the template. It cannot produce hair, clothing, or body shape+the template does not already have.++LHM reconstructs an **animatable** 3D human from a single image and drives it+with SMPL-X pose, which is the interface our retargeter already thinks in.+Published inference times are 1.41 s (LHM-MINI, 16 GB), 2.01 s (LHM-500M), and+6.57 s (LHM-1B). It outputs 3D Gaussians, with a mesh export path.++This moved up the list the moment Spark shipped: LHM's native output is splats,+and Spark is what lets that render on the existing avatar stage next to GLB+avatars instead of in a walled-off viewer. Together they are one feature,+"photoreal animatable avatar from one photo".++**Where it lands:** a new GPU lane beside the existing reconstruction worker, not+a replacement. The template path stays as the CPU-cheap default and the+guaranteed-riggable fallback.++### Real part segmentation++[workers/segment](../workers/segment) is deliberately pure geometry: connected+components first, then geometric splitting. That is exactly right for an+assembled model and it has a known blind spot, which its own README is honest+about: a generative lane emits a single watertight blob, and connected-component+analysis has nothing to separate.++Two MIT options fill that in, and they solve different halves:++- **[wgsxm/PartCrafter](https://github.com/wgsxm/PartCrafter)** (MIT, 2.5k stars,+ NeurIPS 2025) generates the parts directly from a single image, so parts come+ out of the *generation* step rather than being recovered afterwards. That is a+ change to the forge pipeline, not to the segment worker.+- **[VAST-AI-Research/HoloPart](https://github.com/VAST-AI-Research/HoloPart)**+ (MIT, 665 stars) does amodal part completion: it recovers each part as a whole+ object, including the hidden geometry where parts meet, which is what makes a+ split part usable as a swappable component.++**Avoid [nv-tlabs/PartField](https://github.com/nv-tlabs/PartField).** It is the+best-known name in this space and its NVIDIA License clause 3.3 restricts use to+non-commercial research and education. It cannot ship here.++### Audio2Face-3D, for real facial performance++**[NVIDIA/Audio2Face-3D](https://github.com/NVIDIA/Audio2Face-3D)**, open-sourced+in 2025 under the **NVIDIA Open Model License** (not an OSI license: read it+before committing, and see the trap table below).++Our avatars already ship the 52 ARKit blendshapes and 15 visemes+([workers/avatar-reconstruction](../workers/avatar-reconstruction)), and lipsync+today is `wawa-lipsync` estimating visemes from the audio signal. Audio2Face-3D+is a 180M-parameter audio-to-facial-motion model, and NVIDIA's microservice form+of it emits ARKit blendshapes directly, which is the exact rig we already drive.+That is the difference between mouth shapes that track the audio and a facial+performance with jaw, tongue, and eyes.++It wants an NVIDIA GPU with TensorRT, which the fleet already has, and three.ws+is already in NVIDIA Inception, so the relationship for a license question exists.++**Where it lands:** a GPU worker producing an ARKit-52 blendshape track, consumed+by the existing lipsync path in `src/` alongside the cheap `wawa-lipsync`+fallback, the same way BiRefNet sits beside isnet: quality tier, not default.++---++## Tier 2: worth a lane, not urgent++| Project | License | Why | Lands in |+|---|---|---|---|+| [DreamTechAI/Direct3D-S2](https://github.com/DreamTechAI/Direct3D-S2) | MIT (1.3k) | Sparse-voxel latent diffusion at gigascale resolution; a genuinely different geometry prior from TRELLIS and Hunyuan | New `workers/model-direct3d-s2`, peer of the existing mesh backends |+| [stepfun-ai/Step1X-3D](https://github.com/stepfun-ai/Step1X-3D) | Apache-2.0 (888) | Two-stage geometry then texture, fully open including training code | Same, another forge backend |+| [huanngzh/MV-Adapter](https://github.com/huanngzh/MV-Adapter) | Apache-2.0 (1.3k) | [workers/texture](../workers/texture) hand-rolls multiview consistency with SDXL plus ControlNet-Depth and a back-projection pass; MV-Adapter is a purpose-built multiview-consistent adapter for exactly that | `workers/texture/`, replacing the per-view generation step, keeping the UV bake |+| [microsoft/MoGe](https://github.com/microsoft/MoGe) | MIT (2.9k; GitHub misreports it as unlicensed, the LICENSE file is MIT) | Accurate monocular geometry as a depth prior for image-to-3D conditioning and for `/capture` from a single photo | `workers/model-video2scene/` as a single-image path |+| [facebookresearch/map-anything](https://github.com/facebookresearch/map-anything) | Apache-2.0 (3.7k) | Universal feed-forward metric 3D reconstruction. Prefer it over VGGT, the more famous model in this category, which is not permissively licensed | `workers/model-video2scene/`, beside LingBot-Map |+| [playcanvas/supersplat](https://github.com/playcanvas/supersplat) + `@playcanvas/splat-transform` | MIT (10k) | Now that Spark reads SOG, this is the encoder that writes it and the reference for a three.ws splat editing surface | A server-side SOG encode step, so captures are served compressed |+| [facebookresearch/sam2](https://github.com/facebookresearch/sam2) | Apache-2.0 (19.8k) | Promptable image and video segmentation. The `/motion-swap` mask lane and any "select this object" tool are both SAM-shaped problems | `workers/model-video2motion/` mask stage |+| [EricGuo5513/momask-codes](https://github.com/EricGuo5513/momask-codes) | MIT (1.3k) | [workers/model-text2motion](../workers/model-text2motion) chose MDM over MoMask on license grounds; the repo is MIT, so that call is worth re-testing on quality. Check the HumanML3D training-data terms separately from the code license | `workers/model-text2motion/mdm_sampler.py` is already the only model-specific file, by design |++---++## Beyond 3D: what the second sweep found++The 3D sweep is where the product lives, but the wider sweep turned up gaps that+have nothing to do with rendering and are cheaper to close.++### Supply chain and secrets: nothing off the shelf is installed++`scripts/check-secrets.mjs` is a good hand-rolled push-time scan, and there is no+dependency-vulnerability or static-analysis tooling at all. Three drop-ins, all+of which run locally and none of which need GitHub Actions (which this repo does+not use):++- **[google/osv-scanner](https://github.com/google/osv-scanner)** (Apache-2.0,+ 11k) reads `package-lock.json` and the Python requirements files and reports+ known vulnerabilities. The `overrides` block in `package.json` shows this work+ is already being done by hand, one CVE at a time.+- **[gitleaks/gitleaks](https://github.com/gitleaks/gitleaks)** (MIT, 29k) as a+ second opinion beside the existing secrets check, which is worth having on a+ repo where a leaked key is a live wallet.+- **[semgrep/semgrep](https://github.com/semgrep/semgrep)** (LGPL-2.1, 16.5k) for+ the rules the custom `check:rules` cannot express. Note the LGPL: run it as a+ tool, do not vendor it into shipped code.++### Dead code: [webpro-nl/knip](https://github.com/webpro-nl/knip) (ISC, 12k)++"Delete aggressively" is a stated operating rule, and nothing mechanically+enforces it across 60-plus top-level directories, ~90 workspace packages, and+1,989 test files. Knip finds unused files, exports, and dependencies in exactly+this shape of monorepo. Expect a large first report; the value is in the+dependency and export findings, not the file list.++### Voice, if the neural TTS lane ever needs to grow++Kokoro already ships as the free in-browser voice, which was the right call and+covers the common case. If a lane ever needs zero-shot voice cloning or more+expressive delivery, the permissively licensed options are+**[resemble-ai/chatterbox](https://github.com/resemble-ai/chatterbox)** (MIT,+26k) and **[canopyai/Orpheus-TTS](https://github.com/canopyai/Orpheus-TTS)**+(Apache-2.0, 6.3k). **F5-TTS is the one to avoid**: its weights are CC BY-NC.+For speech-in, **[SYSTRAN/faster-whisper](https://github.com/SYSTRAN/faster-whisper)**+(MIT, 25k) is the standard server-side Whisper runtime.++---++## License traps++Every one of these is a well-known, high-star project that looks adoptable and+is not, or is not on the terms its popularity implies. Checked against the+actual LICENSE file, not the GitHub sidebar.++| Project | Reality |+|---|---|+| `briaai/RMBG-2.0` | CC BY-NC 4.0, commercial use needs a paid license. It is built on BiRefNet, which is MIT. Use BiRefNet |+| `nv-tlabs/PartField` | NVIDIA License 3.3: non-commercial research and education only |+| `facebookresearch/vggt` | Custom "VGGT License v1" with an Acceptable Use Policy and pass-through redistribution terms, not an OSI license. MapAnything (Apache-2.0) covers the same ground |+| `ByteDance-Seed/Depth-Anything-3` | Split licensing. DA3-SMALL, DA3-BASE, DA3MONO-LARGE, DA3METRIC-LARGE are Apache-2.0; DA3-LARGE, DA3-GIANT and the DA3NESTED series are CC BY-NC 4.0. The repo code is Apache-2.0, so the checkpoint choice is the whole question |+| `SWivid/F5-TTS` | Weights are CC BY-NC. Chatterbox (MIT) and Orpheus (Apache-2.0) are the commercial-safe equivalents |+| `NVIDIA/Audio2Face-3D` | NVIDIA Open Model License. Permissive in intent and not OSI-approved; read it and record the read before the lane ships |+| `zju3dv/GVHMR` | Custom Zhejiang University terms, not permissive |+| `graphdeco-inria/hierarchical-3d-gaussians` | Inherits the INRIA 3DGS license, which is non-commercial |+| `semgrep/semgrep` | LGPL-2.1. Fine as a developer tool, not as vendored code |++`microsoft/MoGe` is the inverse case: GitHub reports no license, and the LICENSE+file is plain MIT.++---++## Deliberately not recommended++- **A new JS 3D engine** (Babylon, PlayCanvas engine, Needle). three.js is the+ foundation and the entire `avatar-sdk` public contract. Spark was adopted+ precisely because it extends three.js instead of replacing it.+- **A client-side search library** (Orama, MiniSearch). Search here runs against+ Postgres over records the browser does not hold, and `@leeoniya/ufuzzy` already+ covers in-page filtering.+- **`transformers.js` as a general runtime.** `onnxruntime-web` is already the+ in-browser inference path and Kokoro TTS already runs on it. A second runtime+ buys nothing unless a specific model needs it.+- **`spz-js`.** It is the obvious way to add `.spz` support without touching the+ renderer, and it pulls in the entire `playcanvas` engine to do it. Spark reads+ `.spz` natively.+- **UniRig.** Already evaluated and retired here in favour of Make-It-Animatable+ (see [workers/rig/README.md](../workers/rig/README.md)); its live instance+ produced unusable 22-bone skeletons. Upstream has moved since that call, so it+ is a re-test candidate rather than a closed question.+- **A JS linter swap** (oxlint, Biome). Prettier plus the custom `check:rules`+ already covers what this repo enforces, and the rules that matter here are+ house rules no off-the-shelf linter knows.++---++## Re-running this sweep++The gap detection is a grep, and it is worth re-running whenever a lane is+rebuilt:++```bash+# Does the repo already use a given project, anywhere that matters?+grep -ril 'PartCrafter' src api workers packages services scripts server | grep -v node_modules++# Verify a license and its activity from the source, not a blog.+curl -s https://api.github.com/repos/wgsxm/PartCrafter |+ node -e "let s='';process.stdin.on('data',d=>s+=d).on('end',()=>{const j=JSON.parse(s);+ console.log(j.full_name, j.license?.spdx_id, j.stargazers_count, j.pushed_at)})"++# A NOASSERTION spdx_id means "GitHub could not classify it", not "no license".+# Read the file. This is where the traps above were found.+curl -s https://raw.githubusercontent.com/wgsxm/PartCrafter/main/LICENSE | head -20+```++---++<a id="sec-378"></a>> **Source:** `docs/overlay-audit.md` · [↑ table of contents](#table-of-contents)@@ -87127,7 +91608,7 @@ only worth calling from a test.----<a id="sec-366"></a>+<a id="sec-379"></a>> **Source:** `docs/package-extraction.md` · [↑ table of contents](#table-of-contents)@@ -87256,7 +91737,7 @@ part of the extraction itself: extract and publish first, swap the import later.----<a id="sec-367"></a>+<a id="sec-380"></a>> **Source:** `docs/page-performance.md` · [↑ table of contents](#table-of-contents)@@ -87392,7 +91873,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-104)).+(see the Image proxy API section of [api-reference.md](#sec-105)).```jsimport { resizedImageUrl } from './shared/image-url.js'; // remote artwork in the DOM@@ -87450,13 +91931,13 @@ Two things will mislead you if you let them:## Related-- [Avatar thumbnails](#sec-125): where a preview image comes from and the rule every path obeys+- [Avatar thumbnails](#sec-128): 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-104): the image proxy endpoint and its width ladder+- [API reference](#sec-105): the image proxy endpoint and its width ladder----<a id="sec-368"></a>+<a id="sec-381"></a>> **Source:** `docs/partners.md` · [↑ table of contents](#table-of-contents)@@ -87464,7 +91945,7 @@ Two things will mislead you if you let them:`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-385).+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-399).**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.@@ -87474,16 +91955,16 @@ 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-315), [3D Studio (paid)](#sec-312), [Custom GPT config](#sec-150), [AR in ChatGPT](#sec-151), [Spatial MCP](#sec-456) |-| IBM | Strategic | `/blog/three-ws-ibm-business-partner` | [IBM watsonx and Granite](#sec-287), [IBM Granite x402 MCP](#sec-286) |-| Amazon Web Services | Cloud | `/aws` | [AWS Marketplace](#sec-133), [listing kit](#sec-132), [partner spotlight](#sec-134) |+| OpenAI | Select Partner | `/openai` | [MCP 3D Studio (free)](#sec-326), [3D Studio (paid)](#sec-323), [Custom GPT config](#sec-154), [AR in ChatGPT](#sec-155), [Spatial MCP](#sec-474) |+| IBM | Strategic | `/blog/three-ws-ibm-business-partner` | [IBM watsonx and Granite](#sec-297), [IBM Granite x402 MCP](#sec-296) |+| Amazon Web Services | Cloud | `/aws` | [AWS Marketplace](#sec-136), [listing kit](#sec-135), [partner spotlight](#sec-137) || 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-305), [the model router](#sec-140) |-| NVIDIA | Inception | `/nvidia` | [NVIDIA Inception](#sec-346), [NVIDIA models](#sec-347), [Nemotron spotlight](#sec-349) |-| HackerNoon | Media | `/blog/three-ws-hackernoon-partnership` | [Syndication](#sec-464), [Listings and distribution](#sec-305) |-| Quicknode | Infrastructure | `/blog/three-ws-quicknode-startup-program` | [Solana integration](#sec-455), [Listings and distribution](#sec-305) |+| Alibaba Cloud | Cloud | `/blog/three-ws-alibaba-cloud-partnership` | [Listings and distribution](#sec-316), [the model router](#sec-144) |+| NVIDIA | Inception | `/nvidia` | [NVIDIA Inception](#sec-358), [NVIDIA models](#sec-359), [Nemotron spotlight](#sec-361) |+| HackerNoon | Media | `/blog/three-ws-hackernoon-partnership` | [Syndication](#sec-482), [Listings and distribution](#sec-316) |+| Quicknode | Infrastructure | `/blog/three-ws-quicknode-startup-program` | [Solana integration](#sec-473), [Listings and distribution](#sec-316) |-The page's stat bar reads 8 partners, 22 chains, and an infinity glyph for scale. It is marked `aria-hidden` and is decorative framing, not a metric to quote.+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".---@@ -87493,13 +91974,13 @@ 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-315).-- **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-312).-- **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-150).-- **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-151).-- **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-456).+- **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-326).+- **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-323).+- **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-154).+- **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-155).+- **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-474).-**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-385). 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-399). The pre-submission verification pack is [`prompts/finish/_context/openai-pr-00-START-HERE.md`](../prompts/finish/_context/openai-pr-00-START-HERE.md).---@@ -87507,9 +91988,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-287). [IBM Granite x402 MCP](#sec-286) 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-297). [IBM Granite x402 MCP](#sec-296) 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-287) 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-297) 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).@@ -87517,18 +91998,18 @@ 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 "View on AWS Marketplace" and points at `/aws`.+**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-136).-**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-133).+**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-136).**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-305) records AWS Marketplace as Live and three.ws as an AWS Partner.-- [`docs/aws-marketplace-listing-kit.md`](#sec-132) 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-316) records AWS Marketplace as Live and three.ws as an AWS Partner.+- [`docs/aws-marketplace-listing-kit.md`](#sec-135) says the backend integration is built and deployed but the listing itself has not yet been created in the AWS Marketplace Management Portal.-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-134), [MCP agents](#sec-130), and [Marketplace metering in front of x402](#sec-129).+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-137), [MCP agents](#sec-133), and [Marketplace metering in front of x402](#sec-132).---@@ -87538,7 +92019,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-305) 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-316) 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.---@@ -87546,9 +92027,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-140) 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-144) for the router and the model ids.-**Listing status.** [`docs/listings.md`](#sec-305) 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-316) 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.---@@ -87558,10 +92039,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-346) 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-347) 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-358) 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-359) 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-349) 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-361) is a published community piece on building the text-to-3D pipeline on NIM. It is a developer-blog showcase, not a partnership document.---@@ -87569,15 +92050,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-464); the listing row is in [Listings and distribution](#sec-305).+**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-482); the listing row is in [Listings and distribution](#sec-316).---## 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-305) 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-316) 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-455) 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-473) 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.---@@ -87585,7 +92066,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-305) 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-312)) are technical dependencies, not partnerships.+- **No Intel, Microsoft, or Oracle programme appears on `/partners`.** [`docs/listings.md`](#sec-316) 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-323)) 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.@@ -87599,14 +92080,14 @@ The page closes with four reasons, useful as the short pitch when someone asks:## Related-- [Press kit](#sec-385): marks, announcement graphics, boilerplate, and the rules for all of it-- [Listings and distribution](#sec-305): marketplaces, ecosystem directories, and media partners with per-listing status-- [Integrations](#sec-291): the catalog of ways to put an agent on a site you do not control-- [x402](#sec-624): the payment rail behind the agent-to-agent micropayments every partner surface references+- [Press kit](#sec-399): marks, announcement graphics, boilerplate, and the rules for all of it+- [Listings and distribution](#sec-316): marketplaces, ecosystem directories, and media partners with per-listing status+- [Integrations](#sec-301): the catalog of ways to put an agent on a site you do not control+- [x402](#sec-645): the payment rail behind the agent-to-agent micropayments every partner surface references----<a id="sec-369"></a>+<a id="sec-382"></a>> **Source:** `docs/partners/sperax-proposal.md` · [↑ table of contents](#table-of-contents)@@ -87654,7 +92135,7 @@ Both sides already ship for a living — this proposal only asks each of us to d----<a id="sec-370"></a>+<a id="sec-383"></a>> **Source:** `docs/pay-skills-listing.md` · [↑ table of contents](#table-of-contents)@@ -87757,7 +92238,7 @@ are supported.----<a id="sec-371"></a>+<a id="sec-384"></a>> **Source:** `docs/payment-sessions.md` · [↑ table of contents](#table-of-contents)@@ -87799,6 +92280,55 @@ Base URL: `https://three.ws`(`/api/cron/payment-session-sweep`, every 5 minutes) does the same forsessions that pass their expiry while still active.+## The dashboard at /payments++Everything below is available in the browser at+[three.ws/payments](https://three.ws/payments), which is the fastest way to+create a first session and watch it spend. The page lists every session you+own with its budget bar, remaining balance, expiry countdown, host allowlist+and per-transaction cap, and expanding a card loads that session's last ten+executions with a Solscan link per settled payment. Press `N` anywhere on the+page to open the create dialog.++Two things the dashboard does that the API does not do for you:++- **The token is shown exactly once**, right after creation, with a copy button+ and a ready-made `PAYMENT_SESSION_TOKEN=` line. Only its HMAC hash is stored,+ so there is no endpoint that can hand it back later. Copy it before closing.+- **Cancel and refund** is one button per active session, and it tells you how+ much went back to your credits.++### Using a session from an MCP client++Each session card carries a **Copy MCP config** button that emits the block+below for [`@three-ws/agentcore-payments-mcp`](https://www.npmjs.com/package/@three-ws/agentcore-payments-mcp),+which exposes the session tools to any MCP client:++```json+{+ "mcpServers": {+ "three-ws-payments": {+ "command": "npx",+ "args": ["-y", "@three-ws/agentcore-payments-mcp"],+ "env": {+ "THREE_WS_SESSION": "${THREE_WS_SESSION}",+ "PAYMENT_SESSION_TOKEN": "${PAYMENT_SESSION_TOKEN}"+ }+ }+ }+}+```++The config references the two environment variables rather than inlining either+secret, so the file itself never carries a credential. Export both before+starting the server:++- `PAYMENT_SESSION_TOKEN`: the `pss_...` token shown once when the session was+ created. Backs the `pay_with_session` tool when no inline token is passed.+- `THREE_WS_SESSION`: the **value** of your `__Host-sid` browser cookie, with no+ `__Host-sid=` name prefix. Only the session-management tools (create, list,+ cancel) need it; paying does not.+## AuthenticationThe session-management and credits endpoints accept either credential:@@ -87859,7 +92389,7 @@ curl -s https://three.ws/api/credits \````holder` is the $THREE tier every debit on this account is already priced at:-the same shape [`GET /api/pricing`](#sec-104) returns. `discount_bps`+the same shape [`GET /api/pricing`](#sec-105) 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@@ -88225,13 +92755,13 @@ curl -s $BASE/api/credits -H "$AUTH" | jq .balance_usd## Related-- [x402 Protocol](#sec-624): the challenge / verify / settle mechanics behind every paid call.-- [x402 Buyer Client](#sec-616): paying x402 endpoints from your own wallet instead of a session.-- [x402 Developer Tools](#sec-617): free echo / debug / receipt-verification tools for debugging a paid call.+- [x402 Protocol](#sec-645): the challenge / verify / settle mechanics behind every paid call.+- [x402 Buyer Client](#sec-637): paying x402 endpoints from your own wallet instead of a session.+- [x402 Developer Tools](#sec-638): free echo / debug / receipt-verification tools for debugging a paid call.----<a id="sec-372"></a>+<a id="sec-385"></a>> **Source:** `docs/permissions.md` · [↑ table of contents](#table-of-contents)@@ -88627,17 +93157,17 @@ Set `SMOKE_SKIP_REVOKE=1` to skip the on-chain revocation step if the test walle## See also-- [Architecture Overview](#sec-108)+- [Architecture Overview](#sec-109)- [Agent System](#sec-065)-- [ERC-8004 Blockchain Identity](#sec-206)-- [Skill System](#sec-447)+- [ERC-8004 Blockchain Identity](#sec-211)+- [Skill System](#sec-465)- [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-373"></a>+<a id="sec-386"></a>> **Source:** `docs/persona-hub.md` · [↑ table of contents](#table-of-contents)@@ -89034,7 +93564,7 @@ JWT claims:----<a id="sec-374"></a>+<a id="sec-387"></a>> **Source:** `docs/pill-mascot.md` · [↑ table of contents](#table-of-contents)@@ -89048,7 +93578,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-122) covers the normal humanoid path (generate, auto-rig, skin, animate). [Rig Doctor](#sec-423) 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-125) covers the normal humanoid path (generate, auto-rig, skin, animate). [Rig Doctor](#sec-438) 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.---@@ -89177,11 +93707,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-122), 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-125), which is a one-call API and better at humanoids than this script will ever be.----<a id="sec-375"></a>+<a id="sec-388"></a>> **Source:** `docs/plan-checkout.md` · [↑ table of contents](#table-of-contents)@@ -89197,7 +93727,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-262), 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-270), which derives holder tiers from $THREE you *hold*; the plan checkout is $THREE you *spend*.---@@ -89310,7 +93840,7 @@ Plan prices live in [api/payments/_config.js](../api/payments/_config.js) (`PLAN----<a id="sec-376"></a>+<a id="sec-389"></a>> **Source:** `docs/play-boot-performance.md` · [↑ table of contents](#table-of-contents)@@ -89320,7 +93850,7 @@ Plan prices live in [api/payments/_config.js](../api/payments/_config.js) (`PLANThat 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-378), [architecture](#sec-108).+Related docs: [how /play stays safe, honest, and light](#sec-391), [architecture](#sec-109).## How to measure before you claim anything@@ -89413,7 +93943,7 @@ Before shipping anything that touches `/play` boot:----<a id="sec-377"></a>+<a id="sec-390"></a>> **Source:** `docs/play-forge-in-world.md` · [↑ table of contents](#table-of-contents)@@ -89515,12 +94045,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-289): the rest of what you can do inside a `/play` world+- [In-game economy](#sec-299): 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-378"></a>+<a id="sec-391"></a>> **Source:** `docs/play-hardening.md` · [↑ table of contents](#table-of-contents)@@ -89536,7 +94066,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-289), [architecture](#sec-108), [security](#sec-429).+Related docs: [in-game economy](#sec-299), [architecture](#sec-109), [security](#sec-445).---@@ -89791,7 +94321,7 @@ The mobile harness is the one that catches memory regressions. It reports total----<a id="sec-379"></a>+<a id="sec-392"></a>> **Source:** `docs/play-live-events.md` · [↑ table of contents](#table-of-contents)@@ -89862,7 +94392,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-234). |+| `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-239). |`id`, `agenda`, and `tagline` are optional: an event with none of them still runsits countdown, its go-live moment, and its fireworks.@@ -89961,7 +94491,7 @@ Point it at another origin with `--base https://three.ws`.----<a id="sec-380"></a>+<a id="sec-393"></a>> **Source:** `docs/play-vehicles.md` · [↑ table of contents](#table-of-contents)@@ -90068,12 +94598,123 @@ 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-289) covers what you earn on those delivery runs.-- [`/play` safety and lifecycle invariants](#sec-378).+- [The in-game economy](#sec-299) covers what you earn on those delivery runs.+- [`/play` safety and lifecycle invariants](#sec-391).----<a id="sec-381"></a>+<a id="sec-394"></a>++> **Source:** `docs/pocket.md` · [↑ table of contents](#table-of-contents)++# Pocket Console++[**`/pocket`**](https://three.ws/pocket) is a handheld console with a real 3D+agent living inside the screen. The D-pad walks it. A waves, B jumps. L and R+change the cartridge, which means changing which public three.ws agent is loaded.+START swaps the screen between the agent walking, its live stats, and a menu of+every public agent you can slot in. And one `<iframe>` puts the whole device,+your agent included, on any website.++Nothing on the device is a picture of a device. The screen is a live+[`/walk-embed`](https://three.ws/walk-embed) frame running the same renderer,+retargeting and animation library the rest of the platform uses, so the body in+there is the agent's actual rigged GLB, animated by the shared clip library.++## Using it++| Control | Keyboard | Gamepad | What it does |+| --- | --- | --- | --- |+| D-pad | `W` `A` `S` `D` / arrows | left stick or D-pad | Walks the agent. On the SELECT cartridge it moves the highlight instead. |+| Run | `Shift` | either trigger | Holds a run while you steer. |+| A | `K` | A | Waves. On the SELECT cartridge it loads the highlighted agent. |+| B | `J` | B | Jumps. From a menu cartridge it drops back to PLAY. |+| START | `Enter` | Start | Next cartridge: PLAY, STATS, SELECT. |+| SELECT | `Space` | Select | Next scene: night, studio, sunset, grid. |+| L / R | `Q` / `E` | LB / RB | Previous / next agent on the shelf. |+| Power | `P` | none | Turns the screen off, and off means off: the frame is unmounted and the WebGL context goes with it. |++Plug a controller in and the pill on the shell lights up; the on-screen buttons+animate with your presses either way. Everything also works by touch, which is+the point of a handheld.++## The three cartridges++- **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-645)), 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.++The shelf under the device does the same job with a mouse. Both read+`GET /api/agents/public`, so every cartridge is an agent somebody actually+built and published.++## Sharing one++The URL carries the console's state, so a link is the device exactly as you left+it:++```+https://three.ws/pocket?agent=<agent id>&shell=indigo&env=sunset+```++| Param | Values | Effect |+| --- | --- | --- |+| `agent` | any public agent id | Which agent boots. A link to an agent outside the first page of the index still works: the page reads that one record directly and puts it at the head of the shelf. |+| `shell` | `graphite` `bone` `clear` `indigo` | The plastic. |+| `env` | `night` `studio` `sunset` `grid` | The scene inside the screen. |+| `cart` | `play` `stats` `select` | Which cartridge is mounted. |+| `chrome` | `off` | Embed mode: the device alone, transparent background, no nav, no footer, no language pill. |++**Copy share link** and **Post on X** in the header both build that URL from+whatever is currently loaded.++## Embedding it++`chrome=off` is the whole embed API. The device fills the frame, the background+is transparent so it sits on your own page's colour, and it runs on any origin:++```html+<iframe+ src="https://three.ws/pocket?agent=<agent id>&shell=graphite&env=night&chrome=off"+ width="440" height="640"+ title="My agent on three.ws"+ style="border:0;background:transparent"+ allow="xr-spatial-tracking"+ loading="lazy"></iframe>+```++The **Copy embed code** button on the page writes exactly that snippet with your+current agent, shell and scene already in it.++Two details worth knowing if you are embedding rather than linking:++- The console addresses the body by avatar id, which streams the GLB through the+ same-origin proxy (`/api/avatars/:id/glb`). That is why an embedded console+ renders the same on your domain as it does on three.ws: the raw model URL is+ served from a bucket that only answers three.ws.+- The screen runs the walk embed at `zoom=0.74`. A chase camera framed for a+ full-bleed hero leaves a lot of empty sky in a 4:3 handheld window; the+ [`zoom` param](tutorials/walk-companion.md#embed-query-params) pulls it in.++## Where it fits++- [`/walk`](https://three.ws/walk) is the same engine full-bleed, with the+ one-tag iframe and the postMessage contract documented in+ [the walk embed API](https://three.ws/docs/walk-embed-api).+- [`/agents/:id`](https://three.ws/agents) is the canonical page for any agent+ you meet on a cartridge.+- [`/create`](https://three.ws/create) is where a new one comes from. An agent+ with a rigged body shows up on the shelf as soon as it is public.++Source: [`pages/pocket.html`](../pages/pocket.html),+[`src/pocket.js`](../src/pocket.js), [`src/pocket.css`](../src/pocket.css).++---++<a id="sec-395"></a>> **Source:** `docs/popular-3d-github-repos.md` · [↑ table of contents](#table-of-contents)@@ -90089,6 +94730,10 @@ A sweep of 22 3D-related GitHub topics and keyword queries (`3d`, `threejs`, `we## Quick read for three.ws+> 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-377).+- **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).- The fastest-growing cluster is **NeRF + Gaussian Splatting** — `gaussian-splatting` (#10), `instant-ngp` (#16), `nerfstudio` (#33), `supersplat` (#48), `gsplat` (#96), plus generative 3D (`TRELLIS`, `Hunyuan3D`, `stable-dreamfusion`). This is where web-3D capture is heading and worth tracking for the platform roadmap.@@ -90336,7 +94981,7 @@ Apply a 3D-signal regex filter over `description + topics` and a denylist of non----<a id="sec-382"></a>+<a id="sec-396"></a>> **Source:** `docs/portal.md` · [↑ table of contents](#table-of-contents)@@ -90465,7 +95110,7 @@ Portal is a crawler that runs on a visitor's request, and behaves like one. It i----<a id="sec-383"></a>+<a id="sec-397"></a>> **Source:** `docs/portfolio.md` · [↑ table of contents](#table-of-contents)@@ -90509,15 +95154,22 @@ GET /api/crypto/portfolio?address=<wallet>&chain=solana|ethereum```which builds on the same balance layer as-[`/api/crypto/wallet`](#sec-186) ([`api/_lib/balances.js`](../api/_lib/balances.js)):+[`/api/crypto/wallet`](#sec-190) ([`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;per-token 24h changes from DexScreener's batch endpoint; SOL's own 24h movefrom a multi-provider failover.-- **Ethereum**: Alchemy balances with CoinGecko prices and 24h changes. Requires- a provider key on the deployment; without one the endpoint returns an honest- `503 not_configured`, never fabricated data.+- **Ethereum** (keyless floor): Alchemy balances with CoinGecko prices and 24h+ changes when `ALCHEMY_API_KEY` is set and answering. When it is absent or out+ of monthly capacity the read falls to a keyless rung: native ETH off the+ shared public-RPC failover ([`api/_lib/evm/rpc.js`](../api/_lib/evm/rpc.js)),+ ERC-20 discovery and pricing off Blockscout's public Ethereum instance, and+ 24h moves off the same DexScreener batch the Solana lane uses. The `sources`+ array names the rung that actually answered+ (`["ethereum-rpc", "blockscout", "dexscreener"]` for the keyless one). Only a+ deployment where both rungs fail returns `503 not_configured`, never+ fabricated data.Classification and aggregation are pure functions in[`api/_lib/portfolio-overview.js`](../api/_lib/portfolio-overview.js), unit-tested@@ -90568,15 +95220,15 @@ responses are cached for about a minute per wallet.## Related surfaces-- [`/wallet`](#sec-557): your own custodial three.ws wallet.+- [`/wallet`](#sec-577): 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-186): the raw balances endpoint this page+- [`/api/crypto/wallet`](#sec-190): the raw balances endpoint this pagebuilds on, for agents and scripts.----<a id="sec-384"></a>+<a id="sec-398"></a>> **Source:** `docs/premium.md` · [↑ table of contents](#table-of-contents)@@ -90711,7 +95363,7 @@ tiers that remain free (news feed, digest, archive stats/trending).----<a id="sec-385"></a>+<a id="sec-399"></a>> **Source:** `docs/press-kit.md` · [↑ table of contents](#table-of-contents)@@ -90866,7 +95518,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-368).+For the wider programme list and how to describe each one, see [Partner ecosystem](#sec-381).---@@ -90884,14 +95536,14 @@ Use that inbox for anything the page does not cover: a format that is not here (## Related-- [Partner ecosystem](#sec-368): every programme three.ws is in, at the status it actually claims-- [Listings and distribution](#sec-305): marketplaces, directories, and media partners, with per-listing status+- [Partner ecosystem](#sec-381): every programme three.ws is in, at the status it actually claims+- [Listings and distribution](#sec-316): 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-386"></a>+<a id="sec-400"></a>> **Source:** `docs/procedural-animation.md` · [↑ table of contents](#table-of-contents)@@ -91064,12 +95716,12 @@ If you hit a rig whose bones do not resolve, the fix is a bone-name mapping in [## Related- [animations.md](#sec-097) — the pre-baked clip library these layers run on top of-- [avatar-pipeline.md](#sec-122) — how avatars are generated and rigged+- [avatar-pipeline.md](#sec-125) — how avatars are generated and rigged- [agent-system.md](#sec-065) — `AgentAvatar`, the protocol, and the emotion layers----<a id="sec-387"></a>+<a id="sec-401"></a>> **Source:** `docs/product-demo.md` · [↑ table of contents](#table-of-contents)@@ -91148,7 +95800,7 @@ selector to stop everything.three things about it.**Real time, not stepped frames.** The Seeker recordings-([`docs/seeker-video.md`](#sec-434)) step one frame at a time to reproduce a phone panel+([`docs/seeker-video.md`](#sec-450)) 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.@@ -91234,7 +95886,7 @@ concatenates all of them into `three-ws-demo.mp4`.----<a id="sec-388"></a>+<a id="sec-402"></a>> **Source:** `docs/provenance.md` · [↑ table of contents](#table-of-contents)@@ -91247,7 +95899,7 @@ Every model three.ws generates can carry a **signed content credential** — cre- **Free verify:** `GET /api/provenance?src=<glbUrl>` and the `verify_provenance` MCP tool- **Paid anchor:** the `anchor_provenance` MCP tool-> **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-442). 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-460). Credentials signed under v1, before the field existed, keep verifying byte for byte, permanently.## Verify a model (free, public)@@ -91319,7 +95971,117 @@ Real hashing, real ed25519 signature, real on-chain write. Requires the issuer k----<a id="sec-389"></a>+<a id="sec-403"></a>++> **Source:** `docs/publishing-program-2026-09.md` · [↑ table of contents](#table-of-contents)++---+title: "Publishing program, September 2026"+description: "The full venue matrix for the September 2026 writing push: eleven long-form drafts and eight short-form entries across developer, cloud, AI, 3D, home-automation and crypto communities, with each venue's own rules, the angle, the status, and the one action that unblocks it."+status: index. Every draft it lists is unposted and owner-gated.+---++# Publishing program, September 2026++Eleven long-form drafts and one short-form kit, written in this repo, covering the recent feature wave (smart home, Drive, Materialize, Knock, agent vitals, simulation readiness, the vision loop, the mobile shells) and every partner and listing status.++**Nothing here is posted.** Publishing to an external channel is owner-gated (CLAUDE.md, stop-and-ask gate 2), and the drafts that reference a crypto project other than $THREE additionally need approval before they can be committed. This page is the map, the running order, and the per-venue rules that the drafts were written against.++Two rules that apply to every entry, because both have burned publishing programs before:++- **Match the venue's register, not our own.** A forum post that reads like a launch announcement gets ignored at best. Every draft here opens with a specific technical claim and a link that backs it.+- **Never post the same body twice.** Cross-posting is done with a canonical link and a rewritten opening, never a copy.++---++## Long-form drafts++| # | Venue | Draft | Angle | Length | Unblocked by |+|---|---|---|---|---|---|+| 1 | OpenAI Developer Community | [openai-community-physical-world-post.md](#sec-372) | 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-130) | 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-289) | 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-165) | What an agent can actually buy now, with the on-chain and payment infrastructure behind it and the honest numbers | ~4,150 words | Owner approval, plus the other-coin commit gate |+| 5 | Home Assistant Community | [home-assistant-community-post.md](#sec-271) | 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-488) | 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-357) | 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-284) | 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-198) | 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-265) | 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 (already drafted, earlier) | [nvidia-forum-browser-digital-human.md](#sec-356) | Audio2Face-3D streamed onto a rig the visitor generated ninety seconds ago | existing draft | Owner approval |++## Short-form entries++All in [short-form-venue-kit-2026-09.md](#sec-456), paste-ready with each venue's constraints applied:++| Venue | Entry | Constraint the copy was written against |+|---|---|---|+| Show HN | Free physics-readiness grade plus a CC0 spec | Title describes, never sells; the URL is the thing itself |+| Product Hunt | Materialize launch | 60-character tagline, ~260-character description, the maker comment carries the launch |+| r/homeassistant | The dial-out integration and the stdio refusal | Ends on a genuine open question |+| r/threejs | Pointer to the forum post, retargeting quoted in full | Community rewards the artifact, not the announcement |+| r/LocalLLaMA | Binaries an agent cannot read, and the fix | Generalised past 3D so it is useful to non-3D readers |+| r/3Dprinting | The free printability report | Leads with the free endpoint, discloses the paid lane |+| r/robotics | The four verdicts and a request for adversarial review | Asks for criticism, not clicks |+| LinkedIn | "The quarter our AI agents left the browser tab" | 900 words, no code, one link, preview-optimised opening |+| Alibaba Cloud developer community | Qwen as a first-class lane in a multi-provider router | Technical, tied to the existing marketplace listing |+| Khronos glTF discussion | Is a machine-readable simulability claim wanted at all | A discussion that accepts "no" as a useful answer |++---++## The running order++Sequencing matters because several of these link to each other, and because the venues with the slowest review should start first.++**Week 1, the ones with a review queue or a partner relationship.** AWS Builder Center (2), IBM Community (3), Hugging Face (8). Each is an account we already publish under, and each has an existing index page in this repo that must be updated with the canonical URL after publication.++**Week 1, same day as the others, the ones that are pure community goodwill.** three.js forum (6), Home Assistant (5). These are the two venues where the audience is most likely to become contributors, and neither has a queue.++**Week 2, the developer-audience posts.** OpenAI Developer Community (1), dev.to (9), NVIDIA (7), Google Cloud Community (10). Post 1 and 9 both discuss the MCP fleet, so they must not run on the same day and each needs its own opening.++**Week 2, gated separately.** CoinMarketCap (4), which needs the other-coin approval as well as the channel approval.++**Week 3, short-form.** Show HN, then Product Hunt on a Tuesday to Thursday, then the subreddits spread across separate days. Reddit is the only channel here where posting two of ours within a day looks like a campaign, which is exactly what it must not look like.++**No date pressure on the Khronos discussion.** It is a question, not a launch, and it should be opened when someone can watch the thread for a week.++---++## After each one lands++The 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-134), [ibm-community.md](#sec-294), [huggingface.md](#sec-285), [openai-listing-channels.md](#sec-373), or [listings.md](#sec-316) 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.+5. **Update the draft** if the discussion invalidates a claim. A draft that has been contradicted in public and left unedited in the repo is worse than no draft.++---++## Venues considered and not pursued yet++Written down so the next person does not re-derive it:++- **Medium as a primary venue.** Fine as a cross-post with a canonical link, weak as a destination. The former in-app push lanes for Dev.to and Medium were removed with the admin surface, so both are manual.+- **Stack Overflow.** No, in every form. Answering questions there is legitimate; publishing is not.+- **Blender Artists and the ComfyUI community.** Real fits (we ship a Blender addon and ComfyUI nodes) and both deserve their own drafts by someone who uses those tools daily. Writing a forum post about a tool you do not personally use is detectable in the first paragraph.+- **Solana ecosystem developer venues.** Worth a dedicated draft, gated behind the same other-coin approval as the CoinMarketCap piece.+- **A second CoinGecko listing update.** The existing dated notes cover it; nothing new to say until a listing state changes.+- **X threads.** Handled by the existing announcement flow, not by this program.++---++## Related++- [Syndication](#sec-482): how the RSS feed reaches HackerNoon and any other subscriber, with no per-post action+- [Listings and distribution](#sec-316): every marketplace, directory and media partner with its per-listing status+- [Partner ecosystem](#sec-381): the eight partner programmes and the exact wording each one requires+- [Press kit](#sec-399): marks, boilerplate at four lengths, and the rules for both++---++<a id="sec-404"></a>> **Source:** `docs/pump-claims-channel.md` · [↑ table of contents](#table-of-contents)@@ -91478,7 +96240,7 @@ built yet.----<a id="sec-390"></a>+<a id="sec-405"></a>> **Source:** `docs/pump-fun-mcp-edge.md` · [↑ table of contents](#table-of-contents)@@ -91542,7 +96304,7 @@ Both runtimes import `TOOLS` from `src/pump/mcp-tools.js`, so the tool list expo----<a id="sec-391"></a>+<a id="sec-406"></a>> **Source:** `docs/pump-launch-repos.md` · [↑ table of contents](#table-of-contents)@@ -91641,7 +96403,7 @@ rate-limits under the ~450 txs a full run makes. Pass a dedicated `--rpc`----<a id="sec-392"></a>+<a id="sec-407"></a>> **Source:** `docs/pump-launcher.md` · [↑ table of contents](#table-of-contents)@@ -91650,7 +96412,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-624) rail and the platform does the rest:+[x402](#sec-645) 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**,@@ -91677,7 +96439,7 @@ current figure — read it, don't hardcode.## The free → paid funnel-The paid launch sits between two **free, keyless** [Crypto Data API](#sec-195)+The paid launch sits between two **free, keyless** [Crypto Data API](#sec-200)endpoints. Use them to make the launch land well:1. **Before you launch — check the ticker.**@@ -91742,7 +96504,7 @@ curl -X POST https://three.ws/api/x402/pump-launch \curl "https://three.ws/api/crypto/launches"```-See [x402 buyer client](#sec-616) for how to satisfy the 402 challenge in+See [x402 buyer client](#sec-637) for how to satisfy the 402 challenge incode.## Output@@ -91792,16 +96554,16 @@ token itself always deploys on **Solana mainnet** — pump.fun is mainnet-only.## Related-- [x402 paid endpoints](#sec-619) — the full catalog and pricing.-- [Crypto Data API](#sec-195) — the free `symbol` and `launches`+- [x402 paid endpoints](#sec-640) — the full catalog and pricing.+- [Crypto Data API](#sec-200) — the free `symbol` and `launches`endpoints that bookend a launch.-- [Repo → Coin Launcher](#sec-391) — the batch/CLI launcher that+- [Repo → Coin Launcher](#sec-406) — the batch/CLI launcher thatroutes 100% of creator rewards to a GitHub identity (shares the same engine).-- [x402 protocol](#sec-624) — challenge/settle mechanics.+- [x402 protocol](#sec-645) — challenge/settle mechanics.----<a id="sec-393"></a>+<a id="sec-408"></a>> **Source:** `docs/pump-platform-fee.md` · [↑ table of contents](#table-of-contents)@@ -91862,7 +96624,7 @@ The fee is **never** charged silently. When `platform_fee_bps > 0`:----<a id="sec-394"></a>+<a id="sec-409"></a>> **Source:** `docs/pumpfun-program/README.md` · [↑ table of contents](#table-of-contents)@@ -91921,7 +96683,7 @@ tracked in `tasks/pumpfun-upstream/01-v2-trade-instructions-usdc-audit.md`.----<a id="sec-395"></a>+<a id="sec-410"></a>> **Source:** `docs/pumpfun-program/UPSTREAM-buy-sell-v2-announcement.md` · [↑ table of contents](#table-of-contents)@@ -92000,32 +96762,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-401)-- Coin creation: [docs/instructions/COIN_CREATION.md](#sec-410)-- Buy: [docs/instructions/BUY.md](#sec-408)-- Sell: [docs/instructions/SELL.md](#sec-413)-- Claim cashback: [docs/instructions/CLAIM_CASHBACK.md](#sec-409)-- Collect creator fee: [docs/instructions/COLLECT_CREATOR_FEE.md](#sec-411)-- Creator fee sharing: [docs/instructions/CREATOR_FEE_SHARING.md](#sec-412)+- Fee recipients: [docs/FEE_RECIPIENTS.md](#sec-416)+- Coin creation: [docs/instructions/COIN_CREATION.md](#sec-425)+- Buy: [docs/instructions/BUY.md](#sec-423)+- Sell: [docs/instructions/SELL.md](#sec-428)+- Claim cashback: [docs/instructions/CLAIM_CASHBACK.md](#sec-424)+- Collect creator fee: [docs/instructions/COLLECT_CREATOR_FEE.md](#sec-426)+- Creator fee sharing: [docs/instructions/CREATOR_FEE_SHARING.md](#sec-427)## Other documentation-- [Pump Program](#sec-404)-- [PumpSwap](#sec-406)-- [PumpSwap SDK](#sec-407)-- [Pump Program creator fee update](#sec-403)-- [PumpSwap creator fee update](#sec-405)-- [FAQ](#sec-399)-- [Pump fee program docs](#sec-400)+- [Pump Program](#sec-419)+- [PumpSwap](#sec-421)+- [PumpSwap SDK](#sec-422)+- [Pump Program creator fee update](#sec-418)+- [PumpSwap creator fee update](#sec-420)+- [FAQ](#sec-414)+- [Pump fee program docs](#sec-415)-------<a id="sec-396"></a>+<a id="sec-411"></a>> **Source:** `docs/pumpfun-program/UPSTREAM-pumpswap-virtual-quote-reserves.md` · [↑ table of contents](#table-of-contents)@@ -92228,7 +96990,7 @@ Upstream: <https://github.com/pump-fun/pump-public-docs#pumpswap-update-virtual-----<a id="sec-397"></a>+<a id="sec-412"></a>> **Source:** `docs/pumpfun-program/docs/BREAKING_FEE_RECIPIENT.md` · [↑ table of contents](#table-of-contents)@@ -92302,7 +97064,7 @@ The new accounts can be passed before the program upgrade happens on Monday. The----<a id="sec-398"></a>+<a id="sec-413"></a>> **Source:** `docs/pumpfun-program/docs/CPI_README.md` · [↑ table of contents](#table-of-contents)@@ -92406,7 +97168,7 @@ pump-rust-client = { version = "...", path = "..." }----<a id="sec-399"></a>+<a id="sec-414"></a>> **Source:** `docs/pumpfun-program/docs/FAQ.md` · [↑ table of contents](#table-of-contents)@@ -92444,7 +97206,7 @@ is recommended to use a static big enough CU limit like `100_000`.----<a id="sec-400"></a>+<a id="sec-415"></a>> **Source:** `docs/pumpfun-program/docs/FEE_PROGRAM_README.md` · [↑ table of contents](#table-of-contents)@@ -92658,7 +97420,7 @@ If you implement the fee logic correctly, any future change to the fee tiers str----<a id="sec-401"></a>+<a id="sec-416"></a>> **Source:** `docs/pumpfun-program/docs/FEE_RECIPIENTS.md` · [↑ table of contents](#table-of-contents)@@ -92721,7 +97483,7 @@ Use one of these as `buybackFeeRecipient` for any coin.----<a id="sec-402"></a>+<a id="sec-417"></a>> **Source:** `docs/pumpfun-program/docs/PUMP_CASHBACK_README.md` · [↑ table of contents](#table-of-contents)@@ -92838,7 +97600,7 @@ To read unclaimed cashback for pump swap / Pump AMM program:----<a id="sec-403"></a>+<a id="sec-418"></a>> **Source:** `docs/pumpfun-program/docs/PUMP_CREATOR_FEE_README.md` · [↑ table of contents](#table-of-contents)@@ -92973,7 +97735,7 @@ we update the programs on Mainnet.----<a id="sec-404"></a>+<a id="sec-419"></a>> **Source:** `docs/pumpfun-program/docs/PUMP_PROGRAM_README.md` · [↑ table of contents](#table-of-contents)@@ -93174,7 +97936,7 @@ at https://solscan.io/account/EsmVk4MTsoT71JFaRM5DWFZboKpMQjfY6EYzAgUuksXw#accou----<a id="sec-405"></a>+<a id="sec-420"></a>> **Source:** `docs/pumpfun-program/docs/PUMP_SWAP_CREATOR_FEE_README.md` · [↑ table of contents](#table-of-contents)@@ -93283,7 +98045,7 @@ PumpSwap program on Mainnet to the coin creator fee update.----<a id="sec-406"></a>+<a id="sec-421"></a>> **Source:** `docs/pumpfun-program/docs/PUMP_SWAP_README.md` · [↑ table of contents](#table-of-contents)@@ -93517,7 +98279,7 @@ Each Anchor instruction has a set of corresponding autocomplete methods that can----<a id="sec-407"></a>+<a id="sec-422"></a>> **Source:** `docs/pumpfun-program/docs/PUMP_SWAP_SDK_README.md` · [↑ table of contents](#table-of-contents)@@ -93597,7 +98359,7 @@ to autocomplete the `base` and `quote` displayed amounts based on the `lpToken`----<a id="sec-408"></a>+<a id="sec-423"></a>> **Source:** `docs/pumpfun-program/docs/instructions/BUY.md` · [↑ table of contents](#table-of-contents)@@ -93658,7 +98420,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-401) for the full address lists.+See [Fee Recipients](#sec-416) for the full address lists.## TS SDK@@ -93775,7 +98537,7 @@ ixs.extend(----<a id="sec-409"></a>+<a id="sec-424"></a>> **Source:** `docs/pumpfun-program/docs/instructions/CLAIM_CASHBACK.md` · [↑ table of contents](#table-of-contents)@@ -93885,7 +98647,7 @@ let ix = sdk.claim_cashback_v2_instruction(----<a id="sec-410"></a>+<a id="sec-425"></a>> **Source:** `docs/pumpfun-program/docs/instructions/COIN_CREATION.md` · [↑ table of contents](#table-of-contents)@@ -94040,7 +98802,7 @@ let ixs = sdk----<a id="sec-411"></a>+<a id="sec-426"></a>> **Source:** `docs/pumpfun-program/docs/instructions/COLLECT_CREATOR_FEE.md` · [↑ table of contents](#table-of-contents)@@ -94142,13 +98904,13 @@ ixs.extend(sdk.collect_creator_fee_v2_instructions(----<a id="sec-412"></a>+<a id="sec-427"></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-411) 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-426) instead.The lifecycle is:@@ -94496,7 +99258,7 @@ ixs.extend(sdk.distribute_creator_fees_v2_instructions(----<a id="sec-413"></a>+<a id="sec-428"></a>> **Source:** `docs/pumpfun-program/docs/instructions/SELL.md` · [↑ table of contents](#table-of-contents)@@ -94556,7 +99318,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-401) for the full address lists.+See [Fee Recipients](#sec-416) for the full address lists.## TS SDK@@ -94673,7 +99435,7 @@ ixs.extend(----<a id="sec-414"></a>+<a id="sec-429"></a>> **Source:** `docs/quick-start.md` · [↑ table of contents](#table-of-contents)@@ -94819,7 +99581,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-440). |+| `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-458). |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.@@ -94860,7 +99622,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-581).+For the full widget API including `postMessage` events, see the [Widget docs](#sec-602).---@@ -94890,7 +99652,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-169). |+| `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-173). || `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. |@@ -94961,15 +99723,15 @@ If you're embedding inside a sandboxed iframe, make sure the parent grants `allo## Next Steps-- [Embedding Guide](#sec-204) — deep dive on attributes, events, and the JS API-- [Widget Types](#sec-581) — full reference for iframe embeds and postMessage+- [Embedding Guide](#sec-209) — deep dive on attributes, events, and the JS API+- [Widget Types](#sec-602) — full reference for iframe embeds and postMessage- [Agent System](#sec-065) — how the brain, memory, and skills layers work-- [REST API](#sec-104) and [JavaScript API](#sec-296) — backend and in-browser surfaces-- [SDK Reference](#sec-428) — `@three-ws/sdk`, `@three-ws/agent-ui`, `@three-ws/avatar`, `@three-ws/solana-agent`+- [REST API](#sec-105) and [JavaScript API](#sec-307) — backend and in-browser surfaces+- [SDK Reference](#sec-444) — `@three-ws/sdk`, `@three-ws/agent-ui`, `@three-ws/avatar`, `@three-ws/solana-agent`----<a id="sec-415"></a>+<a id="sec-430"></a>> **Source:** `docs/radar.md` · [↑ table of contents](#table-of-contents)@@ -94985,7 +99747,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-479) funnel: Radar surfaces a launch worth a look, you watch it, and if it earns conviction you open it in [Mission Control](#sec-466) 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-499) funnel: Radar surfaces a launch worth a look, you watch it, and if it earns conviction you open it in [Mission Control](#sec-484) to act.## How it works@@ -95015,8 +99777,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-466) to trade.-7. On a coin worth acting on now, use **[Fork](#sec-247)**. 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-484) to trade.+7. On a coin worth acting on now, use **[Fork](#sec-253)**. 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@@ -95056,17 +99818,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-479)-- [Oracle: the conviction engine](#sec-364) fuses this intel into a single conviction score-- [Smart Money Radar](#sec-450) is the pedigree layer Radar surfaces inline-- [Fork a trade](#sec-247) is the one-tap buy on every Radar card, and the deep link that brings a shared coin back here-- [Mission Control](#sec-466) is where a Radar find gets traded-- [Coin pages](#sec-158) cross-link the per-mint intel and conviction views+- [The trading surfaces: Radar, Mission Control, Live Trade Feed, Watchlist, Coin Intelligence](#sec-499)+- [Oracle: the conviction engine](#sec-376) fuses this intel into a single conviction score+- [Smart Money Radar](#sec-468) is the pedigree layer Radar surfaces inline+- [Fork a trade](#sec-253) is the one-tap buy on every Radar card, and the deep link that brings a shared coin back here+- [Mission Control](#sec-484) is where a Radar find gets traded+- [Coin pages](#sec-162) 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-416"></a>+<a id="sec-431"></a>> **Source:** `docs/reasoning-ledger.md` · [↑ table of contents](#table-of-contents)@@ -95156,17 +99918,17 @@ The headline score (0 to 100) is derived only from reconciled outcomes, and the## Related- [Agent Sniper](#sec-062): the pipeline that writes `snipe` entries, with a live case-study ledger-- [Custody you can verify](#sec-187): the same provable-not-promised approach applied to the wallets these decisions spend from+- [Custody you can verify](#sec-191): the same provable-not-promised approach applied to the wallets these decisions spend from----<a id="sec-417"></a>+<a id="sec-432"></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-372)), 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-385)), 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:@@ -95236,6 +99998,7 @@ curl -X POST https://three.ws/api/agent-subscriptions \`amountPerPeriod` is in base units (USDC has 6 decimals, so `5000000` is 5 USDC). Creating a second schedule for the same agent and permission returns the existing one with HTTP 200 instead of duplicating it.+<!-- runnable: 401 the schedule list is per-account; without a session cookie the call is refused -->```bash# What you paycurl https://three.ws/api/agent-subscriptions --cookie "$COOKIE"@@ -95332,13 +100095,13 @@ Definitions live in [api/\_lib/schema.sql](../api/_lib/schema.sql); the lifecycl## See also-- [Permissions & Delegation](#sec-372) for granting, scoping and revoking the signed permission a schedule spends-- [Payment sessions](#sec-371) for capped one-off agent spending that is not on a schedule+- [Permissions & Delegation](#sec-385) for granting, scoping and revoking the signed permission a schedule spends+- [Payment sessions](#sec-384) for capped one-off agent spending that is not on a schedule- [Agent wallets](#sec-074) for the wallet a subscription pays into----<a id="sec-418"></a>+<a id="sec-433"></a>> **Source:** `docs/remix.md` · [↑ table of contents](#table-of-contents)@@ -95550,12 +100313,12 @@ still recorded — the royalty leg reports `payout_unconfigured` instead of payi## Related-- [3D Studio (free) MCP](#sec-315) — the `refine_model` iteration tool.+- [3D Studio (free) MCP](#sec-326) — the `refine_model` iteration tool.- [The 3D pipeline](#sec-003) — how generation itself works.----<a id="sec-419"></a>+<a id="sec-434"></a>> **Source:** `docs/reputation-staking-market.md` · [↑ table of contents](#table-of-contents)@@ -95576,7 +100339,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-454)).+into `solana_attestations` (see [docs/solana-reputation](#sec-472)).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@@ -95782,15 +100545,15 @@ Failure codes (`market_not_configured`, `mainnet_gated`, `tx_not_found`,## Related-- [Docs: Agent Reputation on Solana](#sec-454): the attestation+- [Docs: Agent Reputation on Solana](#sec-472): the attestationlayer the market reads.-- [Docs: Reputation System](#sec-420): the cross-chain reputation model.+- [Docs: Reputation System](#sec-435): the cross-chain reputation model.- [Reputation Explorer](/reputation): inspect any agent's score andattestations.----<a id="sec-420"></a>+<a id="sec-435"></a>> **Source:** `docs/reputation.md` · [↑ table of contents](#table-of-contents)@@ -95836,7 +100599,7 @@ Gas cost is minimal on L2 networks like Base (typically under $0.10). The panel**Owners cannot vouch for their own agents.** If you own the agent, the vouch button is replaced with an explanatory note.-A full reputation dashboard (showing aggregate stats and all recent reviews) is also available at [three.ws/reputation](https://three.ws/reputation) for any `(chainId, agentId)` pair.+The standalone [Reputation Explorer](https://three.ws/reputation) covers any address, not just registered agents: open `/reputation?agent=<chainId>:<agentId>` and it resolves the agent to its owner address, or search the address directly. See [The Reputation Explorer page](#the-reputation-explorer-page) below.### Via the SDK@@ -95854,7 +100617,7 @@ const txHash = await submitReputation({});```-`submitFeedback` is an alias for `submitReputation` — both work identically.+`submitReputation` is a back-compat alias for `submitFeedback` (the contract's own method name). Both work identically.---@@ -95872,16 +100635,31 @@ Recent vouches are loaded by querying `FeedbackSubmitted` event logs for the lasReads go through `readProvider(chainId)` from [src/erc8004/chain-meta.js](../src/erc8004/chain-meta.js): every keyless public node listed for the chain becomes a pinned provider and they are combined in an ethers `FallbackProvider` with quorum 1, so the first healthy node answers and a stalled or rate-limited one is passed over after four seconds instead of blanking the panel. The USD figure printed beside a stake amount comes from `getEthPriceUsd()` ([src/shared/usd-price.js](../src/shared/usd-price.js)), which walks four price feeds with per-provider cooldowns; a throttled feed leaves the ETH amount in place and only drops the USD hint.-### Full reputation dashboard+### The Reputation Explorer page++The standalone [/reputation](https://three.ws/reputation) page is its own surface, not an instance of the agent-profile panel above. It lives in [public/reputation/index.html](../public/reputation/index.html) with its logic in [public/reputation/reputation.js](../public/reputation/reputation.js), and it reads **EAS (Ethereum Attestation Service)** rather than the ERC-8004 registry, so it works for any Ethereum address whether or not that address is a registered agent.-The `ReputationDashboard` class ([src/reputation-ui.js](../src/reputation-ui.js)) is used on the standalone [/reputation](https://three.ws/reputation) page. It shows:+URLs it answers:-- Review count, average rating, time since last review-- Up to 10 recent reviews with inline transaction links-- A submit form for leaving a new review (wallet connection handled inline)-- Optimistic updates: your review appears immediately as "Pending" while the transaction confirms, then is replaced with the confirmed on-chain data. If a confirmation poll fails, the page says so ("Could not confirm your review on-chain; refresh to check.") rather than leaving the pending row looking stuck.+| URL | What it shows |+|---|---|+| `/reputation` | The search form: an address or ENS field plus a network picker |+| `/reputation?address=0x…&chain=8453` | Every attestation written to that address on that chain |+| `/reputation?address=vitalik.eth&chain=8453` | The same, resolving the ENS name through Ethereum mainnet first |+| `/reputation?agent=8453:12` | Resolves ERC-8004 agent 12 on chain 8453 to its owner address and forwards to the address view |-The dashboard reads through `getEvmProvider(chainId)` from [src/shared/evm-rpc-fallback.js](../src/shared/evm-rpc-fallback.js): the same-origin `/api/evm-rpc?chainId=N` proxy first (which inherits the server's keyed and curated RPC failover), then the chain's keyless public hosts, combined into one `FallbackProvider`. There is no per-chain RPC URL hardcoded in the dashboard any more; one dead public endpoint no longer reads as "chain unsupported".+Chains covered: Base (8453, the default), Base Sepolia (84532), Ethereum (1), Optimism (10), Arbitrum (42161), Polygon (137). Each has its own EASScan GraphQL index and block explorer.++What the page renders:++- **Aggregate stats.** Attestation count, average star rating over the scored ones, and a 1-to-5 distribution bar. The count is labelled "attestations", not "reviews": most addresses hold attestations written against other EAS schemas (verifications, name claims), and calling those reviews would overstate the address's review history.+- **The attestation list**, filterable by All / Scored / With comments, paged 30 at a time with a running "Showing X of Y" and a **Show more** button, so a heavily attested address does not silently truncate.+- **Every attestation's payload.** A review renders as stars plus its comment. An attestation written against any other schema renders its decoded fields (name and value) with the schema string as a tag, so no card is a blank row with only an address and a timestamp.+- **An ERC-8004 badge** when the address owns an agent in the Identity Registry on that chain, showing the registry's own vote count and average, linking out to the agent's registry token on the block explorer and to [/agent-identities](https://three.ws/agent-identities).+- **A review form**, wallet-gated. Writes go to Base Sepolia, a free test network, which the form states plainly before you sign.+- **A distinct failure state.** If the EASScan index does not answer, the page says the review history is unknown and offers a retry plus an EASScan link. It never reports an unreachable index as "0 reviews", which would be a false statement about the address.++`ReputationDashboard` ([src/reputation-ui.js](../src/reputation-ui.js)) is a separate ERC-8004 registry dashboard component that no page currently mounts; do not assume editing it changes what /reputation shows.### Via the SDK@@ -96005,7 +100783,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-570) documentation for details.+See the [Validation](#sec-590) documentation for details.---@@ -96018,7 +100796,7 @@ See the [Validation](#sec-570) documentation for details.----<a id="sec-421"></a>+<a id="sec-436"></a>> **Source:** `docs/resilience.md` · [↑ table of contents](#table-of-contents)@@ -96044,11 +100822,11 @@ no other protection ever gets a turn.## Totals-224 outbound call sites across 79 upstreams.+227 outbound call sites across 79 upstreams.| A | B | C | D | F ||---|---|---|---|---|-| 0 | 54 | 91 | 79 | 0 |+| 0 | 54 | 93 | 80 | 0 |## Weakest upstreams@@ -96057,18 +100835,18 @@ the list to work down, worst first.| Upstream | Call sites | Worst grade ||---|---|---|-| `api.telegram.org` | 13 | D |+| `api.telegram.org` | 14 | D || `lite-api.jup.ag` | 12 | D || `api.dexscreener.com` | 9 | D || `storage.googleapis.com` | 8 | D || `api.coinpaprika.com` | 8 | D || `api.coingecko.com` | 8 | D || `api.github.com` | 7 | D |+| `openrouter.ai` | 6 | D || `frontend-api-v3.pump.fun` | 6 | D || `api.replicate.com` | 5 | D || `api.elevenlabs.io` | 5 | D || `api.pinata.cloud` | 5 | D |-| `openrouter.ai` | 5 | D || `api.geckoterminal.com` | 5 | D || `ai.api.nvidia.com` | 4 | D || `api.web3.storage` | 4 | D |@@ -96087,18 +100865,18 @@ the list to work down, worst first.| Upstream | Call sites | Worst grade | A | B | C | D | F ||---|---|---|---|---|---|---|---|-| `api.telegram.org` | 13 | D | 0 | 0 | 10 | 3 | 0 |+| `api.telegram.org` | 14 | D | 0 | 0 | 11 | 3 | 0 || `lite-api.jup.ag` | 12 | D | 0 | 5 | 2 | 5 | 0 || `api.dexscreener.com` | 9 | D | 0 | 4 | 2 | 3 | 0 || `storage.googleapis.com` | 8 | D | 0 | 1 | 2 | 5 | 0 || `api.coinpaprika.com` | 8 | D | 0 | 0 | 0 | 8 | 0 || `api.coingecko.com` | 8 | D | 0 | 7 | 0 | 1 | 0 || `api.github.com` | 7 | D | 0 | 0 | 5 | 2 | 0 |+| `openrouter.ai` | 6 | D | 0 | 0 | 0 | 6 | 0 || `frontend-api-v3.pump.fun` | 6 | D | 0 | 0 | 5 | 1 | 0 || `api.replicate.com` | 5 | D | 0 | 0 | 2 | 3 | 0 || `api.elevenlabs.io` | 5 | D | 0 | 0 | 2 | 3 | 0 || `api.pinata.cloud` | 5 | D | 0 | 0 | 3 | 2 | 0 |-| `openrouter.ai` | 5 | D | 0 | 0 | 0 | 5 | 0 || `api.geckoterminal.com` | 5 | D | 0 | 3 | 0 | 2 | 0 || `ai.api.nvidia.com` | 4 | D | 0 | 0 | 0 | 4 | 0 || `api.web3.storage` | 4 | D | 0 | 0 | 3 | 1 | 0 |@@ -96132,13 +100910,13 @@ the list to work down, worst first.| `api.hyper3d.com` | 3 | C | 0 | 0 | 3 | 0 | 0 || `api.tripo3d.ai` | 3 | C | 0 | 0 | 3 | 0 | 0 || `yields.llama.fi` | 3 | C | 0 | 0 | 3 | 0 | 0 |+| `oauth2.googleapis.com` | 2 | C | 0 | 0 | 2 | 0 | 0 || `api.meshy.ai__expr__` | 2 | C | 0 | 0 | 2 | 0 | 0 || `stablecoins.llama.fi` | 2 | C | 0 | 0 | 2 | 0 | 0 || `api.duckduckgo.com` | 1 | C | 0 | 0 | 1 | 0 | 0 || `api.blockchair.com__expr__` | 1 | C | 0 | 0 | 1 | 0 | 0 || `blockstream.info` | 1 | C | 0 | 0 | 1 | 0 | 0 || `metadata.google.internal` | 1 | C | 0 | 0 | 1 | 0 | 0 |-| `oauth2.googleapis.com` | 1 | C | 0 | 0 | 1 | 0 | 0 || `api.github.com__expr__` | 1 | C | 0 | 0 | 1 | 0 | 0 || `sns-api.bonfida.com` | 1 | C | 0 | 0 | 1 | 0 | 0 || `auth.privy.io` | 1 | C | 0 | 0 | 1 | 0 | 0 |@@ -96176,7 +100954,7 @@ explicit `--accept`, which is a reviewable line in the diff.----<a id="sec-422"></a>+<a id="sec-437"></a>> **Source:** `docs/restyle.md` · [↑ table of contents](#table-of-contents)@@ -96188,7 +100966,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-124) 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-127) uses, instead of inventing a parallel one.## How it works@@ -96269,14 +101047,14 @@ Pass the returned `lineage` array back as `parent_lineage` on the next call to e## Related-- [Avatar Studio](#sec-124): shares the same GLB optimize-and-validate path and material vocabulary.-- [Scene Composer](#sec-167) and [Scene Studio](#sec-427): arrange and edit restyled models in a full scene.-- [MCP tools reference](#sec-316): the paid `restyle_material` agent twin of this endpoint.+- [Avatar Studio](#sec-127): shares the same GLB optimize-and-validate path and material vocabulary.+- [Scene Composer](#sec-171) and [Scene Studio](#sec-443): arrange and edit restyled models in a full scene.+- [MCP tools reference](#sec-327): the paid `restyle_material` agent twin of this endpoint.- [/forge](https://three.ws/forge): generate the models you bring here.----<a id="sec-423"></a>+<a id="sec-438"></a>> **Source:** `docs/rig-doctor.md` · [↑ table of contents](#table-of-contents)@@ -96290,7 +101068,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-117) turns the generated manifest into a validated, hash-anchored file. The [web component reference](#sec-578) 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-120) turns the generated manifest into a validated, hash-anchored file. The [web component reference](#sec-599) covers the `<agent-3d>` element the embed tab emits. [Asset pipeline](#sec-002) covers FBX and GLB conversion upstream of all of this.---@@ -96374,7 +101152,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-117) 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-120) 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 \@@ -96507,7 +101285,7 @@ Your own file cannot be shared this way, because it never leaves your machine.----<a id="sec-424"></a>+<a id="sec-439"></a>> **Source:** `docs/risk-acknowledgment.md` · [↑ table of contents](#table-of-contents)@@ -96629,12 +101407,12 @@ above.## Related- [Risk Disclosure](https://three.ws/legal/risk) — the full legal text users accept-- [Custody you can verify](#sec-187) — the spend-limit and freeze controls that bound what agents can do after acceptance+- [Custody you can verify](#sec-191) — the spend-limit and freeze controls that bound what agents can do after acceptance- [Terms of Service](https://three.ws/legal/tos) — §8 Limitation of Liability, which this acknowledgment supplements----<a id="sec-425"></a>+<a id="sec-440"></a>> **Source:** `docs/robinhood-chain-markets.md` · [↑ table of contents](#table-of-contents)@@ -96682,6 +101460,44 @@ buy path is cleanly ready to enable once an operator affirms eligibility (swap`mountStockEligibilityGate` for `mountBuyPanel` in `src/robinhood-stock.js` — no other wiringchanges).+## The Hood Desk++**`/markets/robinhood/desk`** is the wallet-first view of the same chain: paste any Robinhood Chain+address (or connect an injected wallet, or link to `?address=0x…`) and the desk loads that wallet's+whole book. Nothing is signed to read it, no key is needed, and any address can be inspected, so a+link to the desk is a shareable, reproducible view of a wallet.++What it shows:++- **Desk vitals** - book value in USD (native ETH plus every priced ERC-20), the native balance and+ its change over the window, position count, and a chain gate tile with block height, gas ladder+ and block time.+- **Balance history** - the wallet's real native balance curve. The public sequencer RPC is not an+ archive node (`eth_getBalance` at a past block answers `metadata is not found`), so the curve is+ rebuilt from Blockscout's two balance feeds: daily closes for the older shape, per-transaction+ points for the live edge, stitched into one series. USD points are the native balance marked at+ the current ETH price, and the panel says so rather than implying a marked-to-time curve.+- **Activity tape** - transactions folded together with the token transfers they emitted, so a swap+ prints once with its legs instead of three times. Classified into swap / send / receive / mint /+ burn / approve / claim / deploy, newest first, refreshed every 20s.+- **NAV premium ridge** - the distribution of Stock Token DEX premium against the Chainlink NAV,+ redrawn once per liquidity floor. Each layer back is a deeper pool floor, so a spread that+ survives to the back rows is one you could actually size into. The shaded strip is the "at NAV"+ band (within 0.5%); the table under it ranks the widest dislocation that still has a tradeable+ pool behind it.+- **Position ladder** - every ERC-20 the wallet holds, priced from the Chainlink NAV when it is a+ Stock Token (ERC-8056 multiplier applied to the balance, never to the price) and from the deepest+ Uniswap pool otherwise. A token the desk cannot price is shown as `unpriced` and is never counted+ into the book at zero. Tokens the indexer has no metadata for get their decimals and symbol read+ from the contract in one multicall, because a balance divided by a guessed `1e18` is a wrong+ number on the screen.+- **Counterparty flow** - who this wallet actually crosses with (routers, pools, launchpads,+ people), ranked by legs.+- **Movers** - the Robinhood Chain meme category by absolute 24h move, with a 7-day sparkline.++Each position and each row on the arb board opens a trade ticket: the same Uniswap v3 quote-and-swap+panel the coin pages use for memecoins, and the eligibility gate (never a swap) for Stock Tokens.+## API — `/api/v1/robinhood/*`Free, keyless, real data only:@@ -96694,6 +101510,8 @@ Free, keyless, real data only:| `GET /api/v1/robinhood/coins?category=meme` | Memecoin screener (`category`: `meme` \| `stocks-ecosystem` \| `ecosystem`; `sort`: `market_cap` \| `volume` \| `gainers` \| `losers`) || `GET /api/v1/robinhood/coins-detail?address=0x…` | One coin: pools, market stats, holders, transfers, links || `GET /api/v1/robinhood/launches` | Recent launches from NOXA + The Odyssey, newest first |+| `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 |Paid via x402 ($0.002 USDC, Base or Solana):@@ -96717,7 +101535,12 @@ math; Chainlink feed prices are already multiplier-adjusted, so they're never re(`latestRoundData` + `uiMultiplier` + `totalSupply`), cached 20s. Never 95 separate RPC calls.- **DEX price / liquidity / volume** — [DexScreener](https://dexscreener.com) (`chainId: "robinhood"`),batched 30 addresses per call for the board.-- **Holders, transfers, token stats, chain stats** — [Blockscout](https://robinhoodchain.blockscout.com) Pro API.+- **Holders, transfers, token stats, chain stats, wallet balances and balance history**:+ [Blockscout](https://robinhoodchain.blockscout.com) Pro API. Two operational notes, both learned+ the hard way: it sits behind Cloudflare bot protection that answers any non-browser User-Agent+ with a 403 interstitial (so `api/_lib/robinhood.js` attaches a browser UA for that host only), and+ its address endpoints intermittently answer a bare 500 under load (so the shared fetch retries+ twice inside the cache callback, and only a persistent outage is ever cached).- **Chain TVL** — [DefiLlama](https://defillama.com/chain/robinhood-chain).- **Memecoin screener** — CoinGecko categories `robinhood-chain-meme`, `robinhood-chain-stocks-ecosystem`, `robinhood-ecosystem`.- **Recent launches** — decoded on-chain logs from the NOXA and Odyssey launchpad factories@@ -96726,16 +101549,428 @@ math; Chainlink feed prices are already multiplier-adjusted, so they're never re## Related surfaces-- [Market Data API](#sec-309) — the same paid-endpoint pattern (x402, `priceFor`,+- [Market Data API](#sec-320) — the same paid-endpoint pattern (x402, `priceFor`,service-catalog descriptor) applied to the rest of three.ws's market data.-- [Trust primitives](#sec-482) — score a Robinhood Chain wallet's cross-chain+- [Trust primitives](#sec-502) — score a Robinhood Chain wallet's cross-chainreputation before transacting with it.-- [x402 distribution](#sec-618) — how the paid portfolio endpoint gets discovered+- [x402 distribution](#sec-639) — how the paid portfolio endpoint gets discoveredacross the x402 ecosystem.----<a id="sec-426"></a>+<a id="sec-441"></a>++> **Source:** `docs/robinhood-portfolios.md` · [↑ table of contents](#table-of-contents)++# Robinhood Portfolios++**Describe a portfolio in a sentence. Hold it on-chain, in kind, rebalanced on a published schedule.**++Robinhood Chain (`eip155:4663`) is the one chain where tokenized equities, crypto majors and+memecoins trade against each other in the same pools. A basket that holds NVDA, WETH and a+launchpad token is not a cross-chain integration problem there; it is three ERC-20s in one vault.++Robinhood Portfolios is the protocol that turns a sentence into that vault.++- **[Generate one](/markets/robinhood/portfolios)** the product surface+- **[The universe](/markets/robinhood/portfolios/universe)** every asset a portfolio may hold, priced live+- Contracts: [`contracts/hood-portfolios`](https://github.com/nirholas/three.ws/tree/main/contracts/hood-portfolios)++---++## The shape of it++```+ a sentence+ │+ ▼+ ┌─────────────────┐ ranks 700+ holdable assets, off-chain+ │ the screen │ output is checked back against the universe+ └────────┬────────┘+ ▼+ ┌─────────────────┐ constituents, weights, schedule, the prompt,+ │ the manifest │ the universe snapshot. Hashed, signed, immutable.+ └────────┬────────┘+ ▼ keccak256 committed on-chain+ ┌─────────────────┐ PortfolioRegistry.publish(hash, uri, parent, sig)+ │ registry │ parent pointer = the lineage tree+ └────────┬────────┘+ ▼+ ┌─────────────────┐ ERC-20 shares. In-kind issue and redeem.+ │ the vault │ Scheduled rebalance as a public descending-price offer.+ └─────────────────┘+```++Four contracts, no more: `PortfolioRegistry`, `Portfolio`, `PortfolioFactory`, and the+`IStockToken` interface describing what Robinhood's tokenized equities add to a plain ERC-20.++## Three decisions do most of the work++### 1. Backing is derived, never tracked++How much of each constituent backs one share is recomputed from the vault's own balances on every+call:++```+units_i = balance_i * 1e18 / totalSupply+```++There is no stored "units" number that could drift from reality, no accounting to reconcile after a+donation or an airdrop, and no path that mints a share before the assets backing it arrive.+Deliveries round **up** and payouts round **down**, so every rounding error is the vault's gain.+The solvency property++```+balance_i * 1e18 >= units_i * totalSupply+```++therefore holds as a consequence of the arithmetic rather than as an assertion somebody has to+remember to write. It is asserted anyway, as a stateful invariant, over thousands of randomised+call sequences.++### 2. Everything is in kind, so nothing needs a price++To mint you deliver every constituent in the ratio the vault already holds. To redeem you receive+every constituent pro rata. The vault never sells anything to let somebody in or out, so it eats no+slippage, needs no liquid market in its own share token, and **needs no price oracle to operate**.++That last point is not an elegance argument, it is what makes the product buildable here at all.+Robinhood Chain has Chainlink feeds for 34 of its 95 registry equities and none for its memecoins.+A design that priced the basket on-chain to let people in and out would be unbuildable for most of+the universe. Prices are a display concern, computed off-chain and shown in the UI. They are never+load-bearing.++### 3. Nobody can trade the fund's assets++There is no function on `Portfolio` that lets a manager route the vault's holdings through a DEX.+A rebalance is:++1. **Proposed** by the manifest's creator, and only once the published schedule comes due. The+ proposal names target units per share. It moves nothing.+2. **Timelocked** for `rebalanceDelay` (24h by default), during which the creator may cancel and+ anyone may inspect what was proposed.+3. **Opened** as a descending-price offer that *any* address may fill: deliver the tokens the vault+ is short, receive the tokens it is long. The payout walks linearly from `startPayoutBps`+ (9700 by default, so the vault demands a 3% premium) to `endPayoutBps` (10000, par) across the+ auction window.++The first filler is whoever needs the smallest edge, and the vault keeps whatever premium was left+when they took it. `endPayoutBps` is capped at `MAX_END_PAYOUT_BPS` (10100) in the constructor, so+the most a rebalance can ever cost holders is a property of the deployed vault rather than a+parameter anyone can raise later.++The delta is recomputed from live balances at fill time rather than snapshotted when the auction+opened. That is what lets issuance and redemption stay open throughout an auction: they change the+vault's size, the delta scales with it, and no stored number goes stale.++> **Prior art, and what this is not.** It is not Set Protocol's or Enzyme's manager-executed trade,+> where a privileged key routes the fund's assets and the fund wears whatever it gets. It is not a+> keeper network, which would need one. It is closest to a Dutch-auction rebalance, with one+> deliberate simplification: the auction walks a single scalar payout over the whole delta basket+> rather than pricing each leg, so it needs no per-leg reference price and cannot be filled+> leg-by-leg to leave the vault holding the unwanted half.++## Halts are a state, not an edge case++Every tokenized equity on Robinhood Chain can be paused by its issuer, and while it is, `transfer`+reverts. This is verified against the live chain, not assumed: all 254 tokenized equities are beacon+proxies onto one shared implementation at `0xb35490d6f9163DE4F80d88dc75c3516eb64C5aE2`.++Robinhood Portfolios does not try to work around a halt, because it cannot be worked around: a+halted token cannot move at any price. Issuance, redemption and rebalancing all revert while any+constituent is halted, exactly as creation and redemption of a physical ETF stop when its underlying+stops. `haltedConstituent()` reports which one, so the UI can say so instead of showing a failed+transaction.++Redemption stopping is the uncomfortable one, and it is deliberate. A pro-rata payout of a halted+token cannot be transferred, and paying out only the legs that happen to be transferable would hand+the redeemer the liquid assets and leave everyone still holding shares backing the frozen one.+Redemption waits, and nobody is diluted.++## Refinement mints a new version++Elsewhere, refining an index with a follow-up prompt changes the index you already hold. On-chain+that is not a feature, it is the definition of a rug: the manifest is the only thing a holder relies+on, and an editable manifest means the constituents can become anything after the money arrives.++`PortfolioRegistry` has no edit path by construction: `manifestHash` is written once in `publish`+and no function assigns to it again. A refinement publishes a **new id** whose `parent` points at+the old one. Holders of the original keep exactly what they bought and are never migrated.++### Lineage fees, and why sybils have nothing to farm++A fork pays its ancestors out of its own fee, and the whole sybil answer is that the amount paid up+the tree is a **fixed budget**, not a per-hop rule:++| Constant | Value | Meaning |+|---|---|---|+| `LINEAGE_BUDGET_BPS` | 2000 | the share of the fee reserved for the whole lineage |+| `LINEAGE_DECAY_BPS` | 5000 | each hop takes half of what is still in the budget |+| `MAX_LINEAGE_DEPTH` | 8 | ancestors paid before the walk stops |++A direct parent receives 1000bps of the fee, a grandparent 500, and so on. Because the budget is+fixed no matter how deep the tree is, forking your own portfolio fifty times cannot increase what+the tree pays out. It only splits the same slice into smaller pieces, and every extra hop dilutes+the forker's own ancestors, including themselves. There is nothing to farm, so nothing needs to be+policed. `feeSplit()` returns shares that sum to exactly 10000 for any tree shape, which is fuzzed.++## What stops a manifest whose weights don't match its prompt++Nothing on-chain can read English, so any design claiming to bind the prompt to the weights is+lying. The honest position, encoded in the type system rather than in a disclaimer:++**The weights are binding. The prompt is provenance.**++The weights are committed, attested and enforced by the vault, which will only ever hold the+constituents it was deployed with. The prompt is published alongside them so a reader can judge+whether the screen did what it said.++The alternatives were considered and rejected. A challenge period cannot resolve "does this basket+match this sentence" without an oracle for taste. Attestation staking prices a subjective dispute+and hands the outcome to whoever adjudicates it. A multi-attester quorum makes collusion harder+without making the question decidable. What *is* decidable is whether a screen, re-run against its+recorded inputs, reproduces its recorded output, and that needs no bond: the manifest records the+universe snapshot and every constituent's price and liquidity at selection time, so anyone can+re-run it and publish the diff.++## Backtesting++Every backtest runs the same basket **twice**: once rebalanced on the schedule its manifest+published, and once never rebalanced at all. The difference, `rebalancingAddedPct`, is the only+number that judges a schedule, and it goes both ways. Rebalancing harvests the swings in a basket+whose legs move against each other, and gives up upside in one where a single leg keeps winning.+A backtest that could not produce the second result would not be measuring anything.++### Where the history comes from++This chain has no price history API. DexScreener serves only current state, GeckoTerminal does not+index chain 4663, and the public RPC is pruned, so historical `eth_call` is unavailable.++Reconstructing prices from Uniswap swap logs is the obvious next idea and it does not survive+contact with the chain's block rate. Robinhood Chain produces roughly **864,000 blocks a day** at+~100ms each, and the RPC caps `eth_getLogs` at a 500k-block span or 10,000 results. One month of+history for *one* token is 50+ archival queries before any block-timestamp reads. That is not+something an API request can do, for any number of constituents.++So history comes from the two sources that are actually cheap here:++| Source | Covers | Reach |+|---|---|---|+| Chainlink round history | the 34 registry equities with a feed | weeks, today |+| Daily snapshot (`/api/cron/hood-portfolio-snapshot`) | every token, memecoins included | from the day it first ran, compounding |++Rounds are addressed by id and read at head state, so a pruned node serves them fine.+`feedRoundHistory` batches them into multicalls of **40**, which is load-bearing: this RPC silently+*drops* calls out of a larger multicall rather than failing it, so before chunking, asking for more+history returned less of it. Measured against NVDA's feed on 2026-09-08: 80 rounds at depth 80, only+8 at depth 120, and none at 160. That partial result was the dangerous failure, because it reads as+a short-but-successful history rather than an error, and intersecting several of them produced an+empty backtest window with nothing to explain it. Chunked, 300 rounds costs about two seconds a feed.++### Coverage is reported, never assumed++A constituent with no history is **excluded and named**, the remaining weights are renormalised, and+`coveredWeightBps` says how much of the portfolio the answer actually describes. The window is the+**intersection** of the days on which every covered leg has a real observation, not the union with+gaps carried forward, because carrying a price forward manufactures flat stretches for a token that+simply was not being recorded, and those read as stability rather than as missing data.++Trading costs are not modelled, and the response says so in `costModel`.++## The permalink++A generated portfolio is shared by putting the **manifest itself** in the URL (`?p=`), deflate+compressed to about a kilobyte. Sharing the prompt instead (`?q=`, still supported) does not+reproduce a portfolio: the screen is a language model, so the same sentence returns a different+basket tomorrow, and a link that silently resolves to something else is worse than no link.++The hash is never read from the link. It is re-derived from the document through+`POST /manifest`, so a tampered link shows a different hash rather than a borrowed one.++## The universe++A token is selectable when it has a live pool and a readable price. Classification is either+authoritative or measured, never a curated list that rots:++| Class | Rule |+|---|---|+| `rwa-equity` | the contract answers `uiMultiplier()`, which only Robinhood tokenized equities do (on-chain, authoritative) |+| `stablecoin` | a known USD peg contract on this chain (authoritative) |+| `crypto-major` | at least $5M of on-chain liquidity (measured) |+| `crypto-native` | everything else: chain-native tokens and the long tail (measured) |++Rebuild the snapshot from live sources:++```bash+npm run hood:universe+```++It enumerates from Blockscout's token index in market-cap order, unions in the pinned Stock Token+registry, asks the chain which candidates are tokenized equities, then fills in price, liquidity and+volume from DexScreener and drops anything with no live pool.++## The API++Free and keyless. Base: `https://three.ws/api/v1/hood-portfolios`.++### `GET /universe`++Every holdable asset, re-priced live on each request.++```bash+curl -s 'https://three.ws/api/v1/hood-portfolios/universe?class=rwa-equity&limit=5'+```++| Query | Meaning |+|---|---|+| `class` | comma-separated asset classes to include |+| `minLiquidity` | floor on live USD liquidity |+| `limit` | cap the rows returned |+| `selectable=1` | only what a portfolio may actually hold |++### `POST /generate`++Runs the screen and returns a validated basket plus the full manifest and its hash.++```bash+curl -s -X POST https://three.ws/api/v1/hood-portfolios/generate \+ -H 'content-type: application/json' \+ -d '{"prompt":"AI infrastructure across stocks and crypto"}'+```++```jsonc+{+ "data": {+ "screen": {+ "name": "AI Infrastructure",+ "symbol": "AIINF",+ "thesis": "...",+ "rebalanceDays": 30,+ "constituents": [+ { "address": "0x…", "symbol": "NVDA", "assetClass": "rwa-equity", "weightBps": 2500, "rationale": "…" }+ ]+ },+ "manifest": { /* the full document */ },+ "manifestHash": "0x…", // exactly what PortfolioRegistry.publish commits+ "deployment": { "chainId": 4663, "constituents": ["0x…"], "weightsBps": [2500] }+ }+}+```++Capped at 10 requests per minute per caller, because each one is a real model call. A token the+model invents is dropped rather than repaired; weights are renormalised to sum to exactly 10000,+because that is arithmetic rather than judgement.++### `POST /backtest`++```bash+curl -s -X POST https://three.ws/api/v1/hood-portfolios/backtest \+ -H 'content-type: application/json' \+ -d '{"constituents":[{"address":"0xd0601ce157db5bdc3162bbac2a2c8af5320d9eec","weightBps":5000},+ {"address":"0x117cc2133c37b721f49de2a7a74833232b3b4c0c","weightBps":5000}],+ "rebalanceDays":7}'+```++```jsonc+{+ "data": {+ "ok": true,+ "from": "2026-08-07", "to": "2026-09-08", "windowDays": 32,+ "rebalanced": { "totalReturnPct": 1.42, "maxDrawdownPct": 3.39, "rebalances": 4 },+ "heldWithoutRebalancing": { "totalReturnPct": 1.418 },+ "rebalancingAddedPct": 0.002,+ "coveredWeightBps": 10000, "totalWeightBps": 10000,+ "uncovered": [], "unknown": [], "costModel": "none"+ }+}+```++An address the universe does not know is returned in `unknown` rather than quietly skipped:+silently backtesting two legs of a three-leg basket produces a number that looks complete and+describes something the caller never asked for.++### `POST /manifest`++Canonicalises a manifest and returns the hash it commits to, plus the exact bytes that were hashed.+Pure: no storage, no chain reads.++```bash+curl -s -X POST https://three.ws/api/v1/hood-portfolios/manifest \+ -H 'content-type: application/json' -d '{"manifest":{"b":2,"a":1}}'+```++### `GET /health`++Whether the chain is answering and how fresh the universe snapshot is.++## Manifest hashing++The hash committed on-chain is `keccak256` of the **canonical** serialisation: object keys sorted at+every depth, no insignificant whitespace. `JSON.stringify` follows insertion order, which differs+between the generator and a client that round-tripped the document, so ordering is imposed rather+than assumed.++```js+import { canonicalise, manifestHash } from './api/_lib/hood-portfolios.js';++manifestHash(manifest); // 0x… the value passed to PortfolioRegistry.publish+```++## The SDK++[`@three-ws/hood-portfolios-sdk`](../packages/hood-portfolios-sdk) wraps all five endpoints and+ships the canonicaliser, so a client can verify a manifest hash without a server:++```js+import { HoodPortfolios, canonicalise } from '@three-ws/hood-portfolios-sdk';+import { keccak256, toHex } from 'viem';++const hood = new HoodPortfolios();+const { screen, manifest, manifestHash } = await hood.generate('AI infrastructure across stocks and crypto');++keccak256(toHex(canonicalise(manifest))) === manifestHash; // true, checked offline+```++Its test suite asserts that canonicaliser is byte-identical to the server's, because a divergence+would only ever surface as an on-chain commitment that does not match the document it came from.++## Contracts++```bash+cd contracts/hood-portfolios+forge test # 38 offline tests+ROBINHOOD_RPC_URL=https://rpc.mainnet.chain.robinhood.com forge test # + 5 against the live chain+```++The fork suite is skipped rather than failed when no RPC is configured, so the default run stays+hermetic. It proves the assumptions the rest of the suite takes for granted: that the tokenized+equities really are transferable ERC-20s a vault can custody, that they really do carry the halt+switch, and that a basket spanning an equity, a major and a memecoin can be issued and redeemed on+chain 4663 as deployed.++### The invariants++| Invariant | What it rules out |+|---|---|+| `backingAlwaysCoversOutstandingShares` | NAV extraction through mint/redeem asymmetry |+| `minimumLiquidityStaysLocked` | first-depositor share-price manipulation |+| `legsOnlyEmptyWhenTheirTargetIsZero` | a rebalance draining a position the manifest still wants |+| `feeSplitSumsToWhole` | lineage fees exceeding the fees collected |++## Limits, stated plainly++- **A halted equity leg suspends redemption for everyone** until its issuer resumes it.+- **Tokenized equities are tokenized debt securities** issued by Robinhood Assets (Jersey) Ltd and+ may not be offered, sold or delivered to US persons. The surfaces here are display and tooling;+ any acquisition flow carries its own eligibility gate.+- **A portfolio holding chain-native tokens can go to zero.** The screen ranks liquidity and+ recorded market data. It has no view on whether a token is a fraud.+- **The prompt is not enforceable.** Only the weights are.+- **Nothing here is investment advice**, and a generated basket is not a recommendation.++---++<a id="sec-442"></a>> **Source:** `docs/sas-attestations.md` · [↑ table of contents](#table-of-contents)@@ -96745,7 +101980,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-454)).+- **Permissionless attestations** — general feedback, task lifecycle, dispute, and revoke events. Anyone can write them as SPL Memos (see [Solana reputation](#sec-472)).- **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.@@ -96968,13 +102203,13 @@ Closing (revoking) an attestation is done server-side via `sasClose()` in [api/_----<a id="sec-427"></a>+<a id="sec-443"></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-167) is a focused avatar-plus-props arranger and [Animation Studio](#sec-096) 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-171) is a focused avatar-plus-props arranger and [Animation Studio](#sec-096) is a posing and keyframing tool, Scene Studio is the general-purpose 3D authoring surface underneath them.Page: [/scene](https://three.ws/scene)@@ -96996,10 +102231,10 @@ The editor is ported from the upstream `editor/index.html` with a small set of lFour 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-245) 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-251) 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 transform buttons.** The vendored translate/rotate/scale controls are icon-only `<button>`s; the studio gives them names read from the editor's own string table and mirrors the active mode into `aria-pressed`, so the gizmo mode is both announced and reachable by keyboard.+- **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.### Handoff from Animation Studio@@ -97031,7 +102266,7 @@ A typical round trip from another studio:## States & limits- **Dark theme only.** The vendored editor chrome ships a single dark skin; the studio locks the page to dark so the panels render correctly, regardless of your site theme preference.-- **Desktop-class tool.** This is the full three.js editor with dense panels and gizmo interactions. It expects a pointer and a reasonably sized viewport; it is not tuned for small touch screens the way the other studios are. It does stay usable down to 320px: below 600px the sidebar docks along the bottom instead of the right, the menubar keeps its six items on one row, and the quick-action bar reclaims the right edge.+- **Desktop-class tool.** This is the full three.js editor with dense panels and gizmo interactions. It expects a pointer and a reasonably sized viewport; it is not tuned for small touch screens the way the other studios are. It does stay usable down to 320px: below 600px the sidebar docks along the bottom instead of the right (and drops the 335px floor the vendored panel carries, which used to push its right edge 15px off a 320px screen where the page's suppressed sideways scrolling made it unreachable), the menubar keeps its six items on one row, the quick-action bar reclaims the right edge, and the empty-state card starts below that bar and scrolls inside itself rather than being centred underneath it, with the floating translate/rotate/scale toolbar painted above the card instead of behind it.- **Scenes live in this browser.** Autosave writes to IndexedDB on the machine you are using, so a scene does not follow you to another device or another browser. **Share** (which uploads a GLB) and **Export** are how a scene leaves the machine.- **Vendored, MIT-licensed.** The editor is a vendored copy of three.js r184 under MIT. Attribution and the upstream license live in [src/scene-studio/vendor/](../src/scene-studio/vendor) (see the vendor `README`/`LICENSE`). Local changes are limited to the container mount, theme lock, and chrome overrides.- **Handoff is browser-local.** The Animation Studio handoff moves the GLB through IndexedDB in the same browser. Opening `/scene?handoff=1` directly, with nothing stashed, just gives you an empty editor.@@ -97039,21 +102274,21 @@ A typical round trip from another studio:## Related-- [Scene Composer](#sec-167): the lighter avatar-plus-props arranger with Forge integration.+- [Scene Composer](#sec-171): the lighter avatar-plus-props arranger with Forge integration.- [Animation Studio](#sec-096): builds the animated GLBs Scene Studio records to video.-- [Restyle Studio](#sec-422): re-skin the models before or after composing them.+- [Restyle Studio](#sec-437): re-skin the models before or after composing them.- [3D asset pipeline](#sec-002): how GLB, glTF, and clip formats relate across the platform.- [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-428"></a>+<a id="sec-444"></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-578); 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-599); 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 ||---|---|---|@@ -97146,7 +102381,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-578).+Full attribute and event API is documented in [Web Component reference](#sec-599).### loadManifest and normalize@@ -97498,7 +102733,7 @@ three.ws examples repo, so it is installed, run, and link-checked before every r----<a id="sec-429"></a>+<a id="sec-445"></a>> **Source:** `docs/security.md` · [↑ table of contents](#table-of-contents)@@ -97539,7 +102774,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-321)).+Conversation history lives in `localStorage` by default. Cloud memory sync is opt-in (see [Memory](#sec-332)).### Wallet data@@ -97555,7 +102790,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-321)) |+| `remote` | three.ws cloud storage, tied to your account | Opt-in cloud sync (see [Memory](#sec-332)) || `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 |@@ -97707,7 +102942,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-207) 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-212) for the operating rules.### Reputation gaming (V5)@@ -97864,7 +103099,7 @@ For validator misconduct (biased or falsified on-chain attestations), open a pub----<a id="sec-430"></a>+<a id="sec-446"></a>> **Source:** `docs/seed-quality.md` · [↑ table of contents](#table-of-contents)@@ -98155,19 +103390,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-575): what a published catalog entry has to render in+- [The 3D viewer](#sec-595): 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-431"></a>+<a id="sec-447"></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-432).+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-448).**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).@@ -98208,7 +103443,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-434) 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-450) 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@@ -98226,19 +103461,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-340).+[native-widgets.md](#sec-351).----<a id="sec-432"></a>+<a id="sec-448"></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-431), 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-433) 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-447), 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-449) 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-433).+**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-449).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.@@ -98350,7 +103585,7 @@ Review results arrive by email from `[email protected]----<a id="sec-433"></a>+<a id="sec-449"></a>> **Source:** `docs/seeker-submission-day.md` · [↑ table of contents](#table-of-contents)@@ -98358,7 +103593,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-432); this page is the human half of it. Tick boxes as you go.+The engineering runbook is [Publishing to the Solana dApp Store](#sec-448); this page is the human half of it. Tick boxes as you go.## Before you start@@ -98611,7 +103846,7 @@ On approval:----<a id="sec-434"></a>+<a id="sec-450"></a>> **Source:** `docs/seeker-video.md` · [↑ table of contents](#table-of-contents)@@ -98735,13 +103970,16 @@ fling physics run on the wall clock, so a stepped frame would land on a differen### What it costs to renderCapture is frame-stepped, so wall-clock time is dominated by how expensive each page is to-screenshot: about 1.3s per frame on `/seeker`, 2.2s on `/create/prompt`, and 3s on `/marketplace`,-whose document is 90k px tall with a live WebGL hero. A full default tour is roughly an hour of-capture for around a minute of video. Two things make that number what it is rather than five times-worse: the tour dismisses the walk companion with its own close button on the first page that offers-it (which the SDK persists for the session, and halves the per-frame cost), and the browser is-launched with `--disable-dev-shm-usage`, because Docker's 64 MB `/dev/shm` makes a heavy page either-crash the renderer outright or drag a single marketplace screenshot out to 22 seconds.+screenshot. The default four-act tour recorded on 2026-09-05 came to 2320 frames, 77s of video, in+roughly ten minutes including both encodes. Treat that as the shape of the cost rather than a+guarantee: the `create` act waits on a real generation, so a slow lane moves the total on its own.++Two things keep it there rather than several times worse. The tour dismisses the walk companion with+its own close button on the first page that offers it, which the SDK persists for the session and+which roughly halves the per-frame cost. And the browser is launched with `--disable-dev-shm-usage`,+because Docker's 64 MB `/dev/shm` makes a heavy page either crash the renderer outright or drag a+single marketplace screenshot out to 22 seconds, which is the worst case those two mitigations+exist to avoid.The real build inside the `create` act is not compressed away, it is time-lapsed: the recording keepsrolling at one frame per 0.9s of real time while the page's own progress bar, status line, and@@ -98781,13 +104019,13 @@ the work. Buy a Seeker if you want a Seeker; otherwise use the paths above.## Related-- [three.ws on Solana Seeker](#sec-431) - what the app adds over the website-- [Publishing to the Solana dApp Store](#sec-432) - how a release ships+- [three.ws on Solana Seeker](#sec-447) - what the app adds over the website+- [Publishing to the Solana dApp Store](#sec-448) - how a release ships- [solana-mobile/README.md](../solana-mobile/README.md) - the packaging and code layout----<a id="sec-435"></a>+<a id="sec-451"></a>> **Source:** `docs/selfie-to-avatar.md` · [↑ table of contents](#table-of-contents)@@ -98815,10 +104053,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-123).+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-126).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-197): 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-202): 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@@ -98876,16 +104114,85 @@ Request body: `name` (1-120, required), `photos` (1-6 image URLs or data URIs) *## Related-- [Avatar reconstruction pipeline](#sec-123): the full engine: MediaPipe face-texture transfer, geometry morph, the fixed pre-rigged head template, and the Cloud Run worker.-- [Avatar pipeline](#sec-122): the distinct Forge text-to-3D generation lane.-- [Draft agent mint](#sec-197): the on-chain identity every finished reconstruction gets, the network flags, and the devnet proof script.-- [Trait-based avatar builder](#sec-149): customize and dress the avatar after you scan it.-- [Talking Avatar Video](#sec-465) and [Lipsync](#sec-303): drive the finished avatar's mouth.+- [Avatar reconstruction pipeline](#sec-126): the full engine: MediaPipe face-texture transfer, geometry morph, the fixed pre-rigged head template, and the Cloud Run worker.+- [Avatar pipeline](#sec-125): the distinct Forge text-to-3D generation lane.+- [Draft agent mint](#sec-202): the on-chain identity every finished reconstruction gets, the network flags, and the devnet proof script.+- [Trait-based avatar builder](#sec-153): customize and dress the avatar after you scan it.+- [Talking Avatar Video](#sec-483) and [Lipsync](#sec-314): 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-436"></a>+<a id="sec-452"></a>++> **Source:** `docs/seo.md` · [↑ table of contents](#table-of-contents)++# How three.ws is served to search engines++three.ws is a JavaScript application, and search engines index HTML. Most of the site's pages are shells whose content arrives after a fetch, so every surface that matters for search has a server-side path that puts real text in the response before any script runs.++This page maps those paths, names the file that owns each one, and describes the two contracts that keep them honest. Read it before changing how any page is rendered, and before adding a route to a sitemap.++## The four render paths++| Surface | What the crawler gets | Owner |+|---|---|---|+| Catalogued static pages (`/`, `/create`, `/markets`, and 800 others) | The page's own `<title>`, description, canonical, Open Graph tags and JSON-LD, rewritten per path into a shared shell | [server/seo-head.mjs](../server/seo-head.mjs) |+| Content pages behind a fetch (`/tutorials/<slug>`, `/walkthroughs/<slug>`) | The head above, plus the rendered markdown or walkthrough steps injected into the shell body | [server/crawler-body.mjs](../server/crawler-body.mjs) |+| Entity pages (`/agents/<id>`, `/avatars/<id>`) | A full server-rendered page: name, description, facts, tags, breadcrumbs and JSON-LD, routed by User-Agent | [api/_lib/crawler-page.js](../api/_lib/crawler-page.js) |+| News permalinks (`/markets/news/<month>/<id>-<slug>`) | A server-rendered story page with `NewsArticle` and `BreadcrumbList` JSON-LD and a bounded excerpt | [api/news/story-page.js](../api/news/story-page.js) |++Sitemaps are generated per entity type by [api/sitemap/[type].js](../api/sitemap/[type].js): `core` reads `data/pages.json`, the entity sitemaps read the database, and `news` reads the archive. `sitemap.xml` is the index over all six.++The human-readable counterpart is [/sitemap](https://three.ws/sitemap), a fully static page written by [scripts/build-page-index.mjs](../scripts/build-page-index.mjs) from the same `data/pages.json`. It ships every catalogued page as real HTML (no fetch, so a crawler and a reader see the same thing), grouped by section, with a "Newest" strip of the most recently added pages and a client-side filter over titles, paths and descriptions. The filter is token-based, so `studio avatar` and `avatar studio` return the same rows; it mirrors the query into `?q=`, so `/sitemap?q=wallet` is a shareable link, and `Enter` opens the first match. Regenerate it with `npm run build:pages` after any `data/pages.json` edit; the script is idempotent and reports which files it rewrote.++## Contract 1: a page and its manifest entry must agree++`data/pages.json` decides what is submitted to search engines. The page itself decides what a crawler may do once it arrives. When those disagree the crawler obeys the page, and Search Console records the difference as an error against the site.++Two ways to disagree, both caught by `npm run audit:pages`:++- The manifest submits a page whose HTML answers `<meta name="robots" content="noindex">`. Reported as "Submitted URL marked noindex".+- The manifest submits a path that `robots.txt` disallows. Reported as "Indexed, though blocked by robots.txt", and the crawler never sees the page well enough to drop it.++The fix for either is one line: set `"indexable": false` on the manifest entry. The page stays reachable, stays in the human sitemap with an `internal` badge, and leaves the XML sitemap. Signed-in surfaces, viewers that need a query parameter, and API endpoints all belong in that category.++`robots.txt` deliberately does **not** disallow `/dashboard`, `/settings` or `/my-agents`: those pages carry a `noindex` tag, and a crawler has to be allowed to fetch a page to read the tag that removes it. Disallowing them is what kept them in the index as bare URLs.++## Contract 2: server content is replaced, never merged++Every server-rendered body here is written into a container the client player overwrites wholesale on load (`article.innerHTML = …`, `root.innerHTML = …`). A visitor with JavaScript therefore sees exactly one version of the page, and a crawler without it sees a complete one.++Two consequences worth knowing before you edit a shell:++- The server render and the client render must agree on structure, or the page changes shape as it hydrates. The tutorial shell's hero owns the `<h1>`, so both [server/crawler-body.mjs](../server/crawler-body.mjs) and the player strip the leading `# Title` line out of the markdown before rendering it. Skip that on either side and the document ends up with two competing top-level headings.+- If a shell's markup changes so the injection no longer matches, `crawler-body.mjs` logs and returns the untouched shell rather than serving a half-rendered page. A blank body that still answers 200 is the failure mode to avoid.++## Auditing++```bash+npm run audit:seo # the live site, core pages+npm run audit:seo -- --limit 40 # a quick pass+npm run audit:seo -- --sitemap agents # another URL set+npm run audit:seo -- --base http://localhost:3000+npm run audit:seo -- --strict # exit 1 on any error+```++[scripts/audit-seo.mjs](../scripts/audit-seo.mjs) reads a sitemap, fetches every URL in it as Googlebot, and reports what a search engine would act on: dead or redirecting sitemap entries, pages answering noindex, missing or non-self-referencing canonicals, duplicate titles and descriptions across the corpus, missing `h1`, absent Open Graph tags, and structured data that fails to parse or carries a truncated character.++It reads the live origin on purpose. Only the served response proves what a crawler receives after routing, the shell rewrite and the CDN, so point `--base` at a preview origin to check a change before it ships.++Errors are things a search engine acts on immediately; warnings are quality signals. A title over 65 characters or a description over 165 is truncated in results rather than dropped, so those are reported as warnings, not failures.++## Related++- [docs/guards.md](#sec-268): 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-453"></a>> **Source:** `docs/share-and-embed.md` · [↑ table of contents](#table-of-contents)@@ -98951,13 +104258,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-204) 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-209) 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-116) 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-119) 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>@@ -98992,14 +104299,14 @@ To customize the preview image, change the agent's thumbnail in the editor.## What's next-- **Make your agent smarter** → [Skills system](#sec-447)-- **Understand the technical embed options** → [Embedding guide](#sec-204)-- **Payment and crypto questions** → [Do I need crypto?](#sec-195)-- **Give it a permanent on-chain address** → [Register on-chain](#sec-530)+- **Make your agent smarter** → [Skills system](#sec-465)+- **Understand the technical embed options** → [Embedding guide](#sec-209)+- **Payment and crypto questions** → [Do I need crypto?](#sec-200)+- **Give it a permanent on-chain address** → [Register on-chain](#sec-550)----<a id="sec-437"></a>+<a id="sec-454"></a>> **Source:** `docs/shared-utilities.md` · [↑ table of contents](#table-of-contents)@@ -99188,7 +104495,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-141) hooks in. Each attempt is recorded against the+[Brownout](#sec-145) 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@@ -99401,7 +104708,7 @@ paused during an incident and never resumed, failed silently.----<a id="sec-438"></a>+<a id="sec-455"></a>> **Source:** `docs/shipfeed.md` · [↑ table of contents](#table-of-contents)@@ -99611,7 +104918,224 @@ The full reference, including the linking internals exported for tuning, is in t----<a id="sec-439"></a>+<a id="sec-456"></a>++> **Source:** `docs/short-form-venue-kit-2026-09.md` · [↑ table of contents](#table-of-contents)++---+title: "Short-form venue kit, September 2026"+description: "Paste-ready copy for the venues that take a paragraph rather than an article: Show HN, Product Hunt, five subreddits, LinkedIn, the Alibaba Cloud developer community, and a Khronos glTF discussion opener. Each entry carries the venue's own rules, the copy, and the first comment."+status: drafts, owner approval required before posting (external-channel gate in CLAUDE.md)+---++# Short-form venue kit, September 2026++The long-form drafts live one per file (see [publishing-program-2026-09.md](#sec-403) 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 punishes marketing register and rewards a specific technical claim with a link that backs 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.++---++## 1. Show HN++**Venue:** news.ycombinator.com, "Show HN". One submission, then you live in the comments for six hours.+**Rules that matter:** the title must describe the thing, not sell it; no superlatives; the URL should be the thing itself, not a blog post about it.++**Title (78 characters)**++```+Show HN: Free physics-readiness grade for any glTF file, and a CC0 spec for it+```++**URL**++```+https://three.ws/docs/sim-readiness+```++**First comment (post immediately after submitting)**++> A renderer forgives almost everything. A rigid-body solver forgives nothing. The same mesh that looks perfect in a viewer can sink through the floor in MuJoCo, spin like it is hollow, or turn out to be a metre tall because the generator fitted it to a unit box. Nothing in the file says so, so every robotics, game-physics and world-model pipeline rediscovers the same defects by hand, one asset at a time.+>+> This is a mechanical answer to the question a physics engine actually asks: can I use this as a rigid body right now, and if not, what exactly is wrong. Four verdicts. `simulation_ready` is the only one that licenses trusting the reported mass. `needs_scale` means the geometry is sound and only the units are missing. `needs_repair` means the surface is open, non-manifold, or inconsistently wound, so mass properties are reported but unreliable. `unusable` means no triangles or zero volume. A fifth value, `unreadable`, is for bytes that are not glTF at all, deliberately distinct from a valid file with nothing to simulate.+>+> Free and keyless, because a check that costs money is a check nobody runs:+>+> curl "https://three.ws/api/sim-readiness?src=https://three.ws/avatars/cesium-man.glb"+>+> The spec is CC0 and the grader is a pure function you can vendor. I would rather this became something other people implement than something people call. Source is Apache-2.0 at github.com/nirholas/three.ws. Context: I build a text-to-3D platform, and we needed this badly enough to write it, then realised nobody should have to write it twice.+>+> The part I would most like criticism on: the boundary between `needs_repair` and `unusable`, and whether "real-world extents" is a defensible heuristic or whether it should be a warning rather than a verdict change.++**Alternate submission, if the readiness one has already run:** `Show HN: A live 3D avatar in your terminal, as your coding agent's face` pointing at the `@three-ws/tty-avatar` README.++---++## 2. Product Hunt++**Venue:** producthunt.com. Ship Tuesday to Thursday, 00:01 PT.+**Rules that matter:** tagline maximum 60 characters, description around 260, first comment is where the launch is actually won.++**Name**++```+Materialize by three.ws+```++**Tagline (57 characters)**++```+Describe an object, get it printed and posted to your door+```++**Description (254 characters)**++```+Type a description, three.ws generates the 3D model, and Materialize prints it in resin, nylon, colour sandstone or steel and ships it. Free printability report before any price. Every step is also an API, so an AI agent can order a physical object by itself.+```++**Topics:** 3D, Artificial Intelligence, Design Tools, Developer Tools, Hardware++**Maker's first comment**++> Hi Product Hunt. I build three.ws, an open-source platform that turns a sentence into a rigged 3D character. Materialize is the part that leaves the screen.+>+> The loop: describe something, we generate it, and then it gets manufactured and posted to you. What I care about most is the order the steps happen in.+>+> **The analysis is free and comes first.** Before any price, you get a printability report: whether the mesh is a closed solid, how many separate bodies it has, where the holes are, the thinnest wall, the exact volume, and a 0 to 100 score with named deductions written for a person rather than a slicer. Free because a check that costs money is a check nobody runs.+>+> **The quote is signed and lasts 24 hours,** so the price you were shown is the price you pay.+>+> **Every print ships with proof it is the one you ordered:** a certificate of authenticity with a QR code in the box, and creators can cap how many copies of a model will ever exist.+>+> **It refuses things.** No weapons, no functional key duplicates, no third-party brand marks, screened before production. A print bureau has a human at that checkpoint. We have an API where the buyer might be a machine, so the checkpoint has to be code.+>+> That last part is the unusual bit: an AI agent can run the whole loop, quote and order included, with no human in it. As far as I know this is the first API where an agent can pay for manufacturing.+>+> Free to try the generation half with no account: three.ws/forge. Everything is Apache-2.0. Happy to answer anything, including what it costs and what it cannot print.++---++## 3. Reddit++Five subreddits, five different posts. Never cross-post the same body.++### r/homeassistant++**Title:** `Built a HACS integration that dials out over one WebSocket, so a LAN-only HA can drive a 3D assistant. The lock handling is the interesting part.`++**Body:**++> Most HA installs cannot be reached from the internet: no forwarded port, no public address. That is the default install, not an edge case. So this integration works the other way around: the house dials out over a single outgoing WebSocket and the service never dials the house. Nothing listens on your network, no port forwarding, no tunnel daemon, and the service never receives an HA token (the integration mints its own credential locally and it never leaves the house).+>+> What it connects to is a 3D agent that stands in a live model of your home and talks to you, plus an MCP server so Claude, Cursor or your own assistant can read and drive the house.+>+> The part I would like this sub to pull apart is locks. Every call that would open the house passes through one physical-action gate, and over stdio that gate **refuses outright**. My reasoning: a local stdio MCP server has no user-visible surface, no session, and no way to prove a human saw the request and approved it, so any "confirm?" it prints is a string the model can answer itself. Household roles are enforced server-side too: a guest can turn on lights and can never approve unlocking anything, and a scoped guest's other rooms are removed from the payload rather than hidden in the UI.+>+> Also: we evaluated exposing the agent as a Matter device, measured it, and decided against it for now, and published why.+>+> Repo: github.com/nirholas/three-ws-home-assistant (HACS custom repository). Docs and the relay threat model: three.ws/docs/smart-home. Apache-2.0.+>+> Is the stdio refusal right, or is it paternalistic? That is a genuine question and I have not settled it.++### r/threejs++**Title:** `Five things we open-sourced after animating characters nobody on our team modelled (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-488), with the retargeting section quoted in full and a request for rig conventions we have not mapped.++### r/LocalLLaMA++**Title:** `Every text-to-3D API answers with a URL to a binary the model cannot read. We fixed the loop by rendering results back into the model's own modality.`++**Body:**++> This is the smallest change we made this year and the one that changed the most.+>+> A `.glb` is opaque to a language model. So an agent that just spent GPU time generating an asset cannot tell a clean mesh from a melted one; it hands the link to a human and hopes. No error signal means no loop, which is why agentic 3D has been one-shot since it existed.+>+> The fix: render the result from several angles and return the frames as MCP image content blocks, so a multimodal model looks at what it made. Then it can judge it, refine it, and look again. Alongside the frames we return geometry facts and a plain-language reading of them.+>+> The generalisation is not about 3D at all: **any tool that hands an agent a binary needs a companion that renders it into the agent's own modality.** PDFs, spreadsheets, audio, CAD, compiled artifacts. If your agent cannot perceive its own output, it is guessing.+>+> Free and keyless if you want to try it against your own stack: `POST https://three.ws/api/3d/look`, or the tool `look_at_model` on `https://three.ws/api/mcp-studio`. Everything Apache-2.0.++### r/3Dprinting++**Title:** `We built a free printability report API (closed solid, separate bodies, thinnest wall, exact volume, 0-100 score with named deductions) and made it the step before any price is quoted`++**Body:** the analysis-first argument, the four things it measures, an honest note that the printing lane behind it is a paid service, and an invitation to tell us which deductions are wrong. Lead with the free endpoint; the sub is allergic to advertising and fine with tools.++### r/robotics++**Title:** `A generated mesh that renders perfectly can be unusable as a rigid body, and the file never says so. Free grade plus a CC0 spec.`++**Body:** the four verdicts, the `needs_scale` versus `needs_repair` distinction, the content-addressed caching, the request for adversarial review from people who have shipped assets into MuJoCo or Isaac in anger.++---++## 4. LinkedIn article++**Venue:** LinkedIn article from the founder account, not a company post.+**Audience:** partners, enterprise readers, and people evaluating the company.++**Title**++```+The quarter our AI agents left the browser tab+```++**Opening (first 210 characters are the preview, make them count)**++> For most of this year our agents lived in a browser tab, and the worst thing a wrong decision could produce was a bad sentence. This quarter they got a house, a car, and a factory, and that changed the engineering.++**Structure:** the blast-radius argument; the three capabilities (home, car, manufacturing); the governance layer that became load-bearing; the operating principle that a refusal must live on the server and not in a prompt; the honest partner and listing status list; and a close on what it takes to make an agent economy that is not a demo. Keep it to 900 words, no code blocks, one link at the end.++---++## 5. Alibaba Cloud developer community++**Venue:** the Alibaba Cloud developer community, following our existing marketplace listing and the editorial feature already published on the marketplace blog.+**Angle:** the model router. Qwen models are first-class lanes in a multi-provider brain router that any agent can be pointed at, reached through DashScope alongside the other providers, and there is a published MCP server (`@three-ws/alibaba-cloud-mcp`) exposing Qwen chat and embeddings to any MCP client.++**Working title**++```+Adding Qwen as a first-class lane in a multi-provider agent brain, and what a router owes each provider+```++**The one non-obvious point to build the piece around:** a router that treats providers as interchangeable produces empty answers on the rungs that are working, because reasoning families, tool-call shapes, and streaming conventions differ. The router's job is not to hide the provider, it is to normalise the parts that must be uniform and to report the model that actually answered, so callers can tell.++---++## 6. Khronos glTF discussion opener++**Venue:** the glTF project's public discussion tracker on GitHub (a discussion, not an issue, and not a pull request).+**Purpose:** find out whether a machine-readable physical-usability claim belongs anywhere near the ecosystem, before proposing anything formal.++**Title**++```+Discussion: is there appetite for a machine-readable "can this be simulated" claim for glTF assets?+```++**Body**++> Context, briefly: we run a text-to-3D service and every downstream consumer of our output (physics engines, game engines, robotics stacks) rediscovers the same defects by hand. A glTF file carries no claim about whether it can be used as a rigid body, so the checks get re-implemented per pipeline, inconsistently.+>+> We wrote and published one (CC0 spec, free endpoint, pure-function grader) covering four verdicts: closed surface with consistent winding and positive volume and plausible real-world extents, versus geometry that is sound but unit-scaled, versus an open or non-manifold surface whose mass properties are unreliable, versus nothing to simulate at all.+>+> I am not proposing an extension here, and I would like to understand the shape of the problem first:+>+> 1. Is this a file-level claim, a validator concern, or purely an application concern?+> 2. If it belongs anywhere in the ecosystem, is it an extension, a validator rule set, or a convention?+> 3. Is "plausible real-world extents" defensible as part of a verdict, or should unit ambiguity only ever be a warning?+>+> Happy for the answer to be "this is an application concern, keep it out of the format". That is useful too.++---++<a id="sec-457"></a>> **Source:** `docs/showcase.md` · [↑ table of contents](#table-of-contents)@@ -99621,7 +105145,7 @@ The full reference, including the linking internals exported for tuning, is in tThat 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-206) for the identity standard itself, [on-chain deployments](#sec-192) for the live feed of every registration as it lands (with no avatar filter), and [on-chain agents](#sec-355) for registering one yourself.+Live at [three.ws/showcase](https://three.ws/showcase). Related reading: [ERC-8004](#sec-211) for the identity standard itself, [on-chain deployments](#sec-196) for the live feed of every registration as it lands (with no avatar filter), and [on-chain agents](#sec-367) for registering one yourself.Code: [api/showcase.js](../api/showcase.js). Data comes from `erc8004_agents_index`, populated by the `erc8004-crawl` cron.@@ -99680,14 +105204,14 @@ Each agent carries its on-chain identity plus explorer links resolved from the c## Related-- [ERC-8004](#sec-206): the identity standard behind every row here.-- [On-chain deployments](#sec-192): the same registration stream without the 3D filter, including Solana Metaplex Core mints.-- [Deploy agents on-chain](#sec-355): how to register an agent so it can appear here.+- [ERC-8004](#sec-211): the identity standard behind every row here.+- [On-chain deployments](#sec-196): the same registration stream without the 3D filter, including Solana Metaplex Core mints.+- [Deploy agents on-chain](#sec-367): how to register an agent so it can appear here.- [Agent manifest](#sec-056): the metadata format whose 3D model field decides `has_3d`.----<a id="sec-440"></a>+<a id="sec-458"></a>> **Source:** `docs/sign-language.md` · [↑ table of contents](#table-of-contents)@@ -99697,6 +105221,10 @@ three.ws avatars communicate in American Sign Language. Words that have a sign aNew here? The step-by-step walkthrough is [Tutorial: make your avatar sign](https://three.ws/tutorials/sign-with-your-avatar). This page is the reference: every surface, the developer API, and how the engine works.+[](/sign-language)++*Type anything: the avatar signs the words it has signs for and spells the rest.*+## Start here| I want to | Go here | What happens |@@ -99724,6 +105252,8 @@ Nothing here needs an account, a plugin, or a download. It is 3D in the browser.The status line under the avatar tells you what it just did, for example `signed happy, meet, you · spelled to`, so you always know which words were real signs and which were spelled.+The avatar is a multi-megabyte model, so it arrives a beat after the page. You do not have to wait for it: type and press **🤟 Sign it** while the silhouette is still breathing, and the phrase is queued and performed the moment the avatar lands. If the model fails to download, the stage says so and offers **Retry the avatar**; the [sign API](#the-sign-api) further down runs on the server and keeps working either way.+Three settings sit under the input, and all three are remembered on your next visit:| Setting | Options | Why it exists |@@ -99795,6 +105325,10 @@ Another 41 everyday spellings route to those same signs, so ordinary sentences w[/asl-alphabet](https://three.ws/asl-alphabet) is the reference for the manual alphabet itself. Every letter A-Z and digit 0-9 is formed by a live rig you can orbit, so you see the handshape from any angle rather than from one photographed side.+[](/asl-alphabet)++*Every letter of the manual alphabet on a hand you can turn around.*+- **Click a key, or press it.** Typing `q` signs a Q. A single letter holds its pose so you can study it; a word settles back to rest the way a signer finishes.- **Every letter is described**, with the letters it is confused with named explicitly (F against 9, M against N, K against V, G against Q). Look-alikes are where reading breaks down, so they are called out rather than left to be discovered.- **Spell any word** and each key lights up as the hand reaches it. The word is also laid out under the input, one cell per letter, lit in the same cadence, so a long word can be followed without scrolling back to the A-to-Z grid. The highlight comes from the clip builder itself, not from a timer guessed alongside it, so it stays in step at any speed.@@ -99857,7 +105391,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-578) exposes signing as an attribute. Present at boot, or toggled at runtime, it does the same thing:+The [web component](#sec-599) 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>@@ -100141,6 +105675,8 @@ npm run sign:sheet -- --dominant Left # left-handed signer| What you see | Why | Fix ||---|---|---|+| A breathing silhouette where the avatar should be | The avatar GLB is still downloading | Nothing to do. Anything you type or click meanwhile is queued and signed the moment it lands |+| "The 3D preview did not load" on the stage | The avatar GLB request failed, usually the network | Click **Retry the avatar**. The [sign API](#the-sign-api) runs server-side and works without the preview || "Load a rigged avatar to fingerspell" in the Studio | You are on the built-in mannequin, which has no skinned skeleton | Click **Load avatar**, or open `/pose?avatar=<id>` || The avatar refuses to sign, saying the rig cannot | The skeleton has no finger bones, so handshapes are impossible | Use a rig with fingers. Most generated and Mixamo-style avatars have them || It signs, but the face never changes | The rig carries no ARKit blendshapes | Switch the **Avatar** setting to Expressive face on /sign-language, or use an avatar exported with ARKit shapes |@@ -100202,13 +105738,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-096), the Spell box, exports, and share links- [docs/animations.md](#sec-097), clip formats and the retarget engine-- [docs/web-component.md](#sec-578), every `<agent-3d>` attribute including `sign-language`+- [docs/web-component.md](#sec-599), 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-441"></a>+<a id="sec-459"></a>> **Source:** `docs/signals.md` · [↑ table of contents](#table-of-contents)@@ -100307,17 +105843,17 @@ curl -s https://three.ws/api/signals/subscribe -H 'authorization: Bearer YOUR_TO## Related-- [Custody you can verify](#sec-187) - the spend caps, freeze, and audit trail the subscriber wallet pays and trades under-- [Financial controls](#sec-240) - the plain-English rules and firewall the mirror respects-- [Oracle](#sec-364) - the conviction engine and its own follow/copy tier-- [x402](#sec-624) - the USDC payment protocol every signal settles over-- [Trader card](#sec-472) - the verified track record that regresses a feed's edge+- [Custody you can verify](#sec-191) - the spend caps, freeze, and audit trail the subscriber wallet pays and trades under+- [Financial controls](#sec-246) - the plain-English rules and firewall the mirror respects+- [Oracle](#sec-376) - the conviction engine and its own follow/copy tier+- [x402](#sec-645) - the USDC payment protocol every signal settles over+- [Trader card](#sec-492) - 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-442"></a>+<a id="sec-460"></a>> **Source:** `docs/sim-readiness.md` · [↑ table of contents](#table-of-contents)@@ -100334,7 +105870,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-388) 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-402) is free: a check that costs money is a check nobody runs, and a check nobody runs prevents nothing.## The four verdicts@@ -100416,7 +105952,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-318) 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-329) for connecting.## Why the blockers say what they say@@ -100450,7 +105986,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-388) 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-402) as one field:```jsonc{@@ -100485,20 +106021,20 @@ Volume and centroid come from the divergence theorem over signed tetrahedra; ine## Related-- [Verifiable 3D provenance](#sec-388): 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-423): the same file, the other question. "Will it animate?" instead of "will it simulate?"+- [Verifiable 3D provenance](#sec-402): 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-438): 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-352): hundreds of CC0 props, each a candidate for grading before you build with it.+- [Object Library](#sec-364): hundreds of CC0 props, each a candidate for grading before you build with it.----<a id="sec-443"></a>+<a id="sec-461"></a>> **Source:** `docs/site-performance.md` · [↑ table of contents](#table-of-contents)# What the site's load numbers are, and the four rules that keep them there-`/play` has [its own boot-cost document](#sec-376) 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-389) 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?@@ -100815,6 +106351,149 @@ Deferring it also fixes an ordering bug nobody had filed. The footer bot reserve---+# The phone++Everything above was written from desktop traces. On 2026-09-08 the same site+was measured on a Pixel 5 over slow 4G with `scripts/mobile-perf.mjs` and+`scripts/mobile-touch-audit.mjs` (Playwright field metrics, **not** Lighthouse+scores; see the harness header before quoting a number). The full run is in+[prompts/quality-bar/_generated/08/](../prompts/quality-bar/_generated/08).++Four of the five costs that run found were not slow code. They were a rule that+never reached the page, a property that should never have been animated, a write+that should never have happened, and an asset with only one size. Each is a rule+now.++## 9. A stylesheet only applies to pages that link it++**Invariant: anything that has to apply site-wide is injected by the build, not+hand-linked, and the injector covers `public/` as well as Rollup's inputs.**++`public/mobile.css` carries the site's tap-target floor, its canvas scroll+posture and its safe-area rules. It was reaching **192 of the 584 pages that+carry a stylesheet at all.** The `mobile-ergonomics` plugin in+[vite.config.js](../vite.config.js) already injected it, and `transformIndexHtml`+only ever sees Rollup's HTML *inputs*: every file under `public/` is copied into+`dist/` byte-for-byte and never passes through that hook. Three of the fifteen+pages the mobile audit samples were in that blind spot, `/changelog`, `/ar` and+the entire `/docs` shell.++The measured cost is the part worth remembering. `/docs/start-here` reported+**308 undersized touch targets, 296 of them sidebar links at 267x30**, and+`public/mobile.css` had *already* contained a rule sizing `.sidebar-link` to 44px+for months. Nothing was wrong with the rule. It was not on the page. The audit+that found it could not tell the difference, and neither could anyone reading the+CSS.++The same plugin now also runs as a post-build sweep over every HTML file in+`dist/`, which is the one place both kinds of page meet. Both of its rewrites+(the stylesheet link and `viewport-fit=cover`) are idempotent, so a page that+went through `transformIndexHtml` is unchanged by the second pass. The build+prints how many static pages it patched; on the first run that was **210**.++**When you add something that must be true of every page, check `dist/`, not+`pages/`.** A grep over the source directory that produced the page you were+thinking of will agree with you and be wrong.++## 10. Never animate a layout property++**Invariant: a persistent overlay that moves, moves with `transform`.**++`#tws-corner-stack` (public/corner-stack.js) is `position: fixed`, and it lifts+itself clear of a page's own bottom chrome by transitioning `bottom` and `right`.+Those are layout properties: the element is re-laid-out on every frame of the+transition, and every one of those frames is reported to the layout-instability+API. A fixed overlay that no page content is attached to was therefore charging+real CLS to the page underneath it, once per dock re-measure, and the stack+re-measures on a settle timer and on every body mutation.++Measured on a Pixel 5 against production: **0.0764 twice on `/marketplace`+(0.153 of that page's 0.4381 total, the worst CLS on the site), 0.0810 on+`/launches`, 0.0764 on `/agents/:id`, 0.0601 on `/walk`.**++The fix lands on the same pixels: one `transform: translate3d()` driven by the+same custom properties, transitioned instead of the offsets. A composited+transform generates no layout shift at all. It also collapsed two rules into one,+because the phone breakpoint no longer has to restate the offsets, and it forced+one real change: the narrow layout can no longer pin the stack to both edges,+since a box anchored left AND right slides its left edge off screen when the+transform moves it. Room to grow leftward is a `max-width` now.+[tests/corner-stack.test.js](../tests/corner-stack.test.js) pins both halves.++## 11. Writing a value a node already holds re-dates the page's LCP++**Invariant: a pass that walks the DOM writing values compares before it writes.**++`applyCatalog` in [src/i18n.js](../src/i18n.js) walks every `[data-i18n]`,+`[data-i18n-html]` and `[data-i18n-attr]` node and writes the catalog's value+into it. On the default locale nearly every one of those writes is a no-op: the+markup ships the English source and the English catalog hands the same string+back.++It is not a no-op to the browser. Replacing an element's text destroys its text+node and creates a new one, and Chrome scores that as a **fresh LCP candidate at+the moment it happens**. The catalog arrives after an async fetch, several+seconds into a page on a phone, so every annotated page's LCP was re-dated to the+i18n pass. Measured on a Pixel 5 over slow 4G against production: `/` reported+**LCP 10,188 ms on `h1.hero-h`**, a static heading that had painted at an FCP of+**2,336 ms**; `/docs/start-here` reported 5,168 ms on a `<p>`. Not one pixel+changed at either moment.++The guard is an identity check before each write. Markup needs normalising first,+because the browser rewrites attribute quoting, entity forms and self-closing+tags on the way in and a raw catalog string never equals the `innerHTML` it+produced; round-tripping the candidate through a detached element puts both sides+in the same normal form.+[tests/i18n-idempotent-writes.test.js](../tests/i18n-idempotent-writes.test.js)+asserts on **node identity**, not on the resulting text, because surviving is the+only thing the browser's LCP bookkeeping cares about.++**Any pass that rewrites a lot of nodes deserves the same question**: how many of+those writes change anything?++## 12. A curated asset gets a size per tier, not one size++**Invariant: a large static asset chosen by us ships in a phone-sized copy, and+the tier table decides which one is fetched.**++Two of the three largest downloads on `/play` were assets nobody had ever chosen+a size for.++`/hdri/outdoor.hdr` was **1,435 KB of that page's 5,470 KB**. The environment map+is PMREM-prefiltered into irradiance before it lights anything, so nearly all of+its resolution is discarded on the way in; only its energy has to survive.+`QUALITY_TIERS` in [src/shared/cinematic-render.js](../src/shared/cinematic-render.js)+already had a tier that opted out of HDRIs entirely, and that tier is the *weakest*+one. A real mid-tier phone (coarse pointer, 4 GB of RAM, which is not "low") lands+on `medium` and was pulling the full file. `medium` now reads a 512x256 copy,+about 360 KB, and `loadEnvironment` defaults its tier from the same capability+probe the renderer uses, so every existing call site improved without an edit.++[scripts/build-hdri-mobile.mjs](../scripts/build-hdri-mobile.mjs) regenerates and+verifies those copies, and its two hard-won details are the transferable part:++- **`zscale`, not `scale`.** swscale runs float input through a 16-bit+ fixed-point intermediate and clamps to 1.0, which takes `outdoor.hdr`'s peak+ radiance from **61,408 to exactly 1.00** and halves its mean. The output still+ loads, still looks like an image, and lights a scene completely wrong.+- **`bilinear`, not `lanczos`.** Image-based lighting cares about energy, not+ edges, and a windowed-sinc kernel rings around a sun disc with 60,000:1+ contrast. Mean radiance against the original: bilinear **-0.3%**, bicubic+ +4.8%, lanczos +12.0%.++The other one was a URL. `HOME_TOWN.image` in+[src/game/home-town.js](../src/game/home-town.js) is the coin art for the world+every first-time `/play` visitor lands in, and it was a literal `/api/img?url=…`+with no `w=`, so the proxy handed back all **581 KB** of the pinned original to+texture a totem a few hundred pixels tall. `mapCoins()` had asked for `w=512` for+exactly this reason since the feed path was written; the hand-written literal+predated it. Two more call sites in the community lobby had the same gap.++**A proxy that can resize only resizes when asked.** If you write an image URL by+hand, write the width with it.++---+## Open: three costs the 2026-08-15 sweep measured and did not fixEach of these is the largest remaining number on the page it belongs to, and each one lands in a surface the sweep that found it had no business rewriting. They are recorded here with the measurement so the next pass starts from a number rather than a hunch.@@ -100825,6 +106504,18 @@ Each of these is the largest remaining number on the page it belongs to, and eac**The brand mark is an 85 KB SVG rendered at 22 pixels.** `public/three.svg` and the byte-identical `public/favicon.svg` are 85,257-byte SVGs wrapping two 800x436 PNGs behind `feColorMatrix` filters. They are referenced from 171 files, cost 62 KiB over the wire per page, and no call site in the repo renders the mark above 64 CSS px. Re-encoding the embedded rasters at exactly half resolution (800 to 400, lanczos3, no palette quantization) takes the file to 36,913 bytes and is visually indistinguishable at every size the site uses, with a maximum channel delta of 4 at 22px and 10 at 64px. It is not free above that: at 192px, which some platforms use for an SVG favicon, the delta reaches 105. Fractional downscales are much worse than the exact half (320px wide measured a delta of 78 at 22px), so this is a brand-asset decision with a measured cost attached, not a mechanical resize, and it needs the owner rather than a sweep.+**`/marketplace`'s hero was the site's worst CLS, and is closed as of 2026-09-08.**+Not through the GLB budget guessed at below, which is still worth doing: through+the meta column. The hero rotates every 6.5s and `updateHeroMeta()` writes each+avatar's name and blurb into the same two boxes, which are different lengths for+every slide, so the actions row, the dots and the whole grid below moved on every+rotation, forever. Measured on a Pixel 5 against production, `section#market-hero`+was **0.1094 + 0.2045 of the page's 0.4381 CLS**. Both boxes are now clamped AND+floored to the same line count, so every slide occupies identical space; the+"Start an agent" button ships in the markup at its final label instead of being+revealed into a `flex-wrap` row after first paint. Clamping without a floor is+only half a fix: it caps the tall case and lets the short case collapse.+**`/marketplace` was not touched by the 2026-09-04 sweep and is the worst page on the list.** It measured **38 desktop at a `benchmarkIndex` of 1,183**, with 22,560ms of blocking time, an LCP of 3,272ms and **11,790 KiB transferred**, which is more than the other seven pages put together. Its viewers already obey rule 4's `data-src` contract and its podium already obeys rule 5, and the page still mounts a hero carousel, a six-item themed strip and a card grid, all of them above the fold at 1350x940, so the contract has nothing left to defer. A single hero GLB was 3,341 KiB in that trace, which is rule 7's problem in a second place: `renderHero()` in [src/marketplace.js](../src/marketplace.js) takes whatever `state.featured` returns without asking how heavy it is. Applying rule 7's budget there is the obvious next move and it needs its own measurement, because unlike the homepage this page shows three avatars at once and the budget has to be shared.## Open: directory thumbnails are served with no cache headers at all@@ -100837,11 +106528,28 @@ 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-104)), 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-105)), 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.+## Half-closed on 2026-09-08: `/forge`'s composer growth++The coach half is fixed. `.prompt-coach` shipped EMPTY at `min-height: 1.2em` and+`updateCoach()` wrote `grade('')`'s message into it, which does not fit beside+its neighbours in the `flex-wrap` `.prompt-tools` row, so the row wrapped onto a+second line and grew. `pages/forge.html` now ships that exact message, with+`data-no-i18n` per rule 6, and+[tests/forge-prompt-coach.test.js](../tests/forge-prompt-coach.test.js) reads+both `pages/forge.html` and `src/forge-prompt-studio.js` so the two copies cannot+drift back apart.++The engine-pill half below is unchanged and still open. It is the harder one:+the settled height is a function of how many lanes the catalog returns and how+they wrap, which is between 29px and 219px across viewport widths, so there is no+constant to reserve. The shape that would work is the one rule 5 used on the+podium, rendering the lane set the server already knows about into the markup.+## Open: `/forge`'s composer grows 95px after first paint, and rule 6 does not cover itRule 6 fixed the example-prompt row. The 2026-09-04 sweep measured `/forge` at **CLS 0.226 on a `benchmarkIndex` of 1,196**, with `<div class="chips" id="examples">` still named as the largest shift, and a per-frame trace of the live page shows why: `#examples` is not growing, it is being *pushed*. Two containers above it in `.forge-rail` grow after first paint, and the chips row is simply the biggest thing that moves as a result.@@ -100871,7 +106579,7 @@ Two things in the numbers above are real and are not being fixed by tuning:----<a id="sec-444"></a>+<a id="sec-462"></a>> **Source:** `docs/sketchfab.md` · [↑ table of contents](#table-of-contents)@@ -100969,7 +106677,7 @@ and [`api/_lib/sketchfab.js`](https://github.com/nirholas/three.ws/blob/main/api----<a id="sec-445"></a>+<a id="sec-463"></a>> **Source:** `docs/skill-bundles.md` · [↑ table of contents](#table-of-contents)@@ -101160,13 +106868,13 @@ agent's marketplace listing is the next step.## Related-- [Marketplace](#sec-310): how skills and assets are listed, bought, and settled+- [Marketplace](#sec-321): how skills and assets are listed, bought, and settled- [Agent skills](#sec-061): what a skill is in the first place- [Agent wallets](#sec-074): where a bundle's payment lands----<a id="sec-446"></a>+<a id="sec-464"></a>> **Source:** `docs/skill-royalties.md` · [↑ table of contents](#table-of-contents)@@ -101372,14 +107080,14 @@ whose pending balance clears $0.01, so nobody pays gas to move dust.## Related-- [Skills marketplace](#sec-447): publishing, pricing, and installing skills-- [x402 endpoints](#sec-619): every paid endpoint and who each one pays-- [Money map](#sec-335): how value moves across the whole platform-- [Remix royalties](#sec-418): the parallel royalty rail for 3D creations+- [Skills marketplace](#sec-465): publishing, pricing, and installing skills+- [x402 endpoints](#sec-640): every paid endpoint and who each one pays+- [Money map](#sec-346): how value moves across the whole platform+- [Remix royalties](#sec-433): the parallel royalty rail for 3D creations----<a id="sec-447"></a>+<a id="sec-465"></a>> **Source:** `docs/skills.md` · [↑ table of contents](#table-of-contents)@@ -102101,7 +107809,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-446).+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-464).Publish your own from the marketplace ("Publish a Skill") or `POST /api/skills` with `{ name, slug, description, category, tags, content }` (or `schema_json`).@@ -102139,15 +107847,15 @@ Those filters are also the page URL, so [/marketplace?tab=skills&tag=solana&sort## See also-- [Architecture Overview](#sec-108) — how skills fit into the agent runtime+- [Architecture Overview](#sec-109) — how skills fit into the agent runtime- [Agent System](#sec-065) — the protocol bus and built-in tool system-- [Web Component](#sec-578) — embedding agents and passing skill attributes+- [Web Component](#sec-599) — 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-448"></a>+<a id="sec-466"></a>> **Source:** `docs/smart-contracts.md` · [↑ table of contents](#table-of-contents)@@ -102805,7 +108513,7 @@ On Base at typical gas prices (~0.001 gwei base fee), an agent registration runs----<a id="sec-449"></a>+<a id="sec-467"></a>> **Source:** `docs/smart-home.md` · [↑ table of contents](#table-of-contents)@@ -102995,8 +108703,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-267) and-[home-relay-threat-model.md](#sec-266).+crosses. See [home-relay.md](#sec-276) and+[home-relay-threat-model.md](#sec-275).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@@ -103044,7 +108752,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-265).+[Home privacy and retention](#sec-274).---@@ -103058,20 +108766,21 @@ below exists, and anything that does not exist says so.| Piece | Where ||---|---|| The client library: state and action channel, MCP channel, room graph, intent resolution, the gate | [`packages/home-bridge/`](../packages/home-bridge/README.md) |-| The connection store: schema, encrypted credentials, lifecycle | [`api/_lib/home/store.js`](../api/_lib/home/store.js), 8 migrations under `api/_lib/migrations/*_home_*.sql` |+| The connection store: schema, encrypted credentials, lifecycle | [`api/_lib/home/store.js`](../api/_lib/home/store.js), 11 migrations under `api/_lib/migrations/*_home_*.sql` || The bridge runtime: pooled per-home connections, refcounting, breaker, backpressure ladder | [`api/_lib/home/runtime.js`](../api/_lib/home/runtime.js), [`admission.js`](../api/_lib/home/admission.js) || 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 | [`src/home/scene-render.js`](../src/home/scene-render.js), [`scene-model.js`](../src/home/scene-model.js) |-| Households: roles, per-member scopes, invites | [`api/_lib/home/members.js`](../api/_lib/home/members.js), [docs/home-households.md](#sec-263) |-| Privacy, retention, export and deletion | [`api/_lib/home/privacy.js`](../api/_lib/home/privacy.js), [docs/home-privacy.md](#sec-265) |+| Households: roles, per-member scopes, invites | [`api/_lib/home/members.js`](../api/_lib/home/members.js), [docs/home-households.md](#sec-272) |+| Privacy, retention, export and deletion | [`api/_lib/home/privacy.js`](../api/_lib/home/privacy.js), [docs/home-privacy.md](#sec-274) || 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 tutorial | [docs/tutorials/connect-your-home.md](#sec-498) |+| 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-518) |### The connect flow, state by state@@ -103131,8 +108840,10 @@ flow into a page and into a model prompt, and there is a physical actuator on thIt works; it is not yet worth shipping. The evidence and the conditions that would change thatanswer are in [section 8](#8-matter-direct-control-measured-and-not-yet-built). Nothing of itis in the tree.-- **A floorplan editor.** The 3D scene derives its layout from the area graph. Authoring and- persisting a hand-drawn floorplan is not built.+- **A room shape that is not a rectangle.** The floorplan editor stores each room as a centre and+ a footprint in metres, which is the shape [`src/home/scene-model.js`](../src/home/scene-model.js)+ reads. The stored document is versioned so it can gain rotation, wall openings and polygons+ without the renderer's lookup changing, and none of those three is built.## 6. What was actually verified@@ -103357,7 +109068,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-270). It+goes through, and the residuals we accepted on purpose: [Home security](#sec-279). 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).@@ -103381,7 +109092,7 @@ is written about a building rather than about a database, and every claim in it----<a id="sec-450"></a>+<a id="sec-468"></a>> **Source:** `docs/smart-money.md` · [↑ table of contents](#table-of-contents)@@ -103395,7 +109106,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-364) 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-376) draws on, exposed as its own browsable surface.## How it works@@ -103434,7 +109145,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-247)** 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-253)** 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.@@ -103482,14 +109193,14 @@ for (const c of conviction.slice(0, 5)) {## Related-- [Oracle: the conviction engine](#sec-364) uses this proven-wallet ledger as its WHO pillar-- [The trading surfaces](#sec-479) map, including the Coin Intelligence cross-coin trader board-- [Coin Radar](#sec-415) and [Mission Control](#sec-466) surface the same pedigree read inline+- [Oracle: the conviction engine](#sec-376) uses this proven-wallet ledger as its WHO pillar+- [The trading surfaces](#sec-499) map, including the Coin Intelligence cross-coin trader board+- [Coin Radar](#sec-430) and [Mission Control](#sec-484) 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-451"></a>+<a id="sec-469"></a>> **Source:** `docs/sniper-autonomy.md` · [↑ table of contents](#table-of-contents)@@ -103562,7 +109273,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-477): recover the stake as soon as+ [take-initials ladder](#sec-497): 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*@@ -103663,7 +109374,7 @@ tighter rather than rewarded for the hit rate.## Related- [Agent Sniper](#sec-062): the trading pipeline the arms run on-- [The 10 SOL trading experiment](#sec-477): the exit thesis the+- [The 10 SOL trading experiment](#sec-497): the exit thesis theladder implements- [`api/_lib/sniper-optimizer.js`](../api/_lib/sniper-optimizer.js): the tuningrules, tier-scaled@@ -103672,7 +109383,7 @@ tighter rather than rewarded for the hit rate.----<a id="sec-452"></a>+<a id="sec-470"></a>> **Source:** `docs/social-layer.md` · [↑ table of contents](#table-of-contents)@@ -103747,7 +109458,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-333) for that one.+> [Money Feed](#sec-344) for that one.## Follow graph@@ -103923,16 +109634,16 @@ be replayed any time from the getting-started page.## Related pages-- [Money Feed](#sec-333): the value-movement ticker (`GET /api/feed`),+- [Money Feed](#sec-344): the value-movement ticker (`GET /api/feed`),a different feed from the activity feed documented here.-- [Remix economy](#sec-418): what happens after someone finds your model in+- [Remix economy](#sec-433): 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-453"></a>+<a id="sec-471"></a>> **Source:** `docs/solana-pumpfun.md` · [↑ table of contents](#table-of-contents)@@ -104097,7 +109808,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-454)), 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-472)), 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.@@ -104121,7 +109832,7 @@ The MCP client and cron crawler are unit-tested with mocked `fetch` and `sql`. E----<a id="sec-454"></a>+<a id="sec-472"></a>> **Source:** `docs/solana-reputation.md` · [↑ table of contents](#table-of-contents)@@ -104131,7 +109842,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-057) (the why) and [ERC-8004](#sec-206) / [Reputation System](#sec-420) (the EVM how-to). If you haven't read those, start with [Agent Reputation](#sec-057) 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-057) (the why) and [ERC-8004](#sec-211) / [Reputation System](#sec-435) (the EVM how-to). If you haven't read those, start with [Agent Reputation](#sec-057) 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.---@@ -104207,7 +109918,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-419), 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-434), 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:@@ -104300,7 +110011,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-420)) *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-435)) *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.---@@ -104332,14 +110043,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-419)**: 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-434)**: 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-057)** — the trust problem both chains solve.-- **[Solana agents](#sec-455)** — registering an agent as a Metaplex Core asset.-- **[ERC-8004](#sec-206)** · **[Reputation System](#sec-420)** — the EVM side of the same idea.+- **[Solana agents](#sec-473)** — registering an agent as a Metaplex Core asset.+- **[ERC-8004](#sec-211)** · **[Reputation System](#sec-435)** — the EVM side of the same idea.----<a id="sec-455"></a>+<a id="sec-473"></a>> **Source:** `docs/solana.md` · [↑ table of contents](#table-of-contents)@@ -104347,11 +110058,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-206) 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-211) 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-355).+> Deploying many agents at once (server-side, into the three.ws Agents collection, with a live dashboard)? See [Deploy agents on-chain (bulk)](#sec-367).---@@ -104364,16 +110075,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-454)) |+| 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-472)) || 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-426)) |+| Credentialed attestations (SAS) | Live | [api/agents/sas/\[action\].js](../api/agents/sas/[action].js) (see [SAS attestations](#sec-442)) || 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-355) 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-367) 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.@@ -104597,13 +110308,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-454) and [solana-pumpfun.md](#sec-453).-- **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-426)).+- **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-472) and [solana-pumpfun.md](#sec-471).+- **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-442)).## 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-355)).+- **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-367)).- **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.@@ -104628,7 +110339,7 @@ three.ws examples repo, so it is installed, run, and link-checked before every r----<a id="sec-456"></a>+<a id="sec-474"></a>> **Source:** `docs/spatial-mcp.md` · [↑ table of contents](#table-of-contents)@@ -104759,7 +110470,7 @@ Free 3D Studio (`structuredContent.spatial`): `forge_free`, `text_to_avatar`, `m----<a id="sec-457"></a>+<a id="sec-475"></a>> **Source:** `docs/specs/agent-trading.md` · [↑ table of contents](#table-of-contents)@@ -104846,28 +110557,37 @@ Real routes (no mocks), server-side guards with tests (including the $THREE-sell----<a id="sec-458"></a>+<a id="sec-476"></a>> **Source:** `docs/splat.md` · [↑ table of contents](#table-of-contents)# Splat Viewer: photoreal Gaussian-splat avatars in the browser-The Splat Viewer renders Gaussian-splat and radiance-field scenes right in your browser, the photoreal output of capture engines like GaussianAvatars and HumanGaussian. Load a `.ply`, `.splat`, or `.ksplat` by URL, drop a file in, or try a built-in sample, and orbit a photoreal avatar or scene with no plugin, no upload to a server, and no account. All decoding happens client-side.+The Splat Viewer renders Gaussian-splat and radiance-field scenes right in your browser, the photoreal output of capture engines like GaussianAvatars and HumanGaussian. Load a `.ply` (plain or compressed), `.spz`, `.splat`, `.ksplat`, or `.sog` by URL, drop a file in, or try a built-in sample, and orbit a photoreal avatar or scene with no plugin, no upload to a server, and no account. All decoding happens client-side.Page: [/splat](https://three.ws/splat)## Why it exists-Mesh avatars (GLB) are lightweight, riggable, and universal, and that is what most of three.ws generates. But the photoreal frontier of avatar capture is radiance fields: Gaussian splatting reconstructs a person or a scene as millions of tiny anisotropic blobs that render with real skin, hair, and lighting no polygon budget can match. Those captures ship as `.ply`, `.splat`, or `.ksplat` files, and most tools to view them are desktop apps. The Splat Viewer is the browser front door: a place to open any splat scene, evaluate a capture engine's output, and share a photoreal avatar with a link. It complements [/avatar-engines](https://three.ws/avatar-engines), which surveys the capture methods; the viewer is where their output actually renders.+Mesh avatars (GLB) are lightweight, riggable, and universal, and that is what most of three.ws generates. But the photoreal frontier of avatar capture is radiance fields: Gaussian splatting reconstructs a person or a scene as millions of tiny anisotropic blobs that render with real skin, hair, and lighting no polygon budget can match. Those captures ship as `.ply`, `.spz`, `.splat`, `.ksplat`, or `.sog` files, and most tools to view them are desktop apps. The compressed containers matter: the same scene that is a 1 GB PLY is roughly 100 MB as SPZ and roughly 42 MB as SOG, which is the difference between a scene you can share as a link and one you cannot. The Splat Viewer is the browser front door: a place to open any splat scene, evaluate a capture engine's output, and share a photoreal avatar with a link. It complements [/avatar-engines](https://three.ws/avatar-engines), which surveys the capture methods; the viewer is where their output actually renders.## How it works-The viewer (`src/splat-viewer.js`) is entirely client-side. It uses `@mkkellogg/gaussian-splats-3d`, already a platform dependency (the same library the Forge Studio Lab uses), lazy-loaded on first render so the page shell paints instantly. Format is detected from the filename extension: `.ply` maps to the PLY scene format, `.ksplat` to the compressed KSplat format, and everything else to the antimatter15 `.splat` layout (32 bytes per splat). The decoded buffer is handed to a `GS.Viewer` with built-in orbit controls, and every state is designed: idle, fetching, decoding, error, and a live HUD showing the scene label.+The viewer (`src/splat-viewer.js`) is entirely client-side. Rendering lives in `src/splat-stage.js`, a shared module on top of [Spark](https://github.com/sparkjsdev/spark) (`@sparkjsdev/spark`, MIT, by World Labs), lazy-loaded on first render so the page shell paints instantly. The Forge Studio Lab's splat tools render through the same module, so both surfaces read the same formats and behave the same way.++Spark renders splats as ordinary objects inside a normal three.js scene rather than inside a viewer of its own, which is what makes the rest of this page's behaviour possible:++- **The format is read from the bytes, not the filename.** A URL that ends in a query string, a redirect, or no extension at all still decodes. Only two containers fall back to the name: `.splat` is a raw 32-byte-per-splat array with no header to sniff, and a bundled `.sog` is a zip.+- **The camera frames the scene it actually loaded**, from the splat centres in world space. Splat scenes are authored at wildly different scales, and a fixed camera distance is right for exactly one of them.+- **The live state waits for the first sorted frame.** Spark sorts splats on a worker and paints once that lands, so the stage holds a "Sorting splats" state rather than going live over an empty canvas on a slow GPU.+- **The canvas is opaque.** Spark accumulates colour with premultiplied alpha and leaves destination alpha at zero, so a transparent canvas would composite a fully rendered scene away to nothing.++Every state is designed: idle, fetching, decoding, sorting, error, and a live HUD showing the scene label and its real splat count.There are three ways to load a scene:- **By URL.** Paste a link and the viewer fetches the bytes and decodes them. To survive cross-origin blocks, it rewrites the human-facing URLs of common asset hosts to their CORS-enabled raw form: GitHub `raw`/`blob` links become `raw.githubusercontent.com`, Hugging Face `/blob/` becomes `/resolve/`, and Dropbox links are forced to a direct download. When a host still blocks the browser fetch, the error state tells you to download the file and upload it instead. Because the bytes are already in memory once a remote scene renders, the download control offers them back, so a scene you reached by URL is as saveable as one you uploaded.-- **By file.** Pick a file or drag and drop a `.ply`/`.splat`/`.ksplat` onto the stage. The file is read locally and never leaves your machine; a download button is offered for the loaded buffer.+- **By file.** Pick a file or drag and drop a `.ply`/`.spz`/`.splat`/`.ksplat`/`.sog` onto the stage. The file is read locally and never leaves your machine; a download button is offered for the loaded buffer.- **Samples.** Two procedurally generated scenes ship in the page: a radiance shell (6,000 splats) and a synthetic head-and-shoulders bust (14,000 splats) that evokes what a real GaussianAvatars capture looks like in the viewer. These are synthetic, generated in-browser, and downloadable.A deep link, `?src=<url>&name=<label>`, loads a scene straight from the URL on page load, so a photoreal avatar is shareable with a single link. A recenter control resets the camera on the live viewer, so it snaps back without dropping and rebuilding the WebGL context. Teardown is explicit: the renderer's graphics context is released by hand on every scene swap and when the page is hidden, because the splat library's own dispose stops short of that. If the browser drops the context anyway, after a GPU reset or under memory pressure, the stage reports it and offers a reload rather than freezing on the last frame.@@ -104876,7 +110596,7 @@ A deep link, `?src=<url>&name=<label>`, loads a scene straight from the URL on p1. Open [/splat](https://three.ws/splat).2. Try a sample first: click the radiance shell or the head bust to see the viewer in action.-3. Load your own scene: paste a `.ply`/`.splat`/`.ksplat` URL and click Render, or drop a file onto the stage, or pick one from disk.+3. Load your own scene: paste a `.ply`/`.spz`/`.splat`/`.ksplat`/`.sog` URL and click Render, or drop a file onto the stage, or pick one from disk.4. Orbit, zoom, and pan with the built-in controls. The HUD shows the scene label and splat count.5. Recenter if the camera drifts. Download the loaded buffer, whether the scene came from a file, a sample, or a URL.6. Share a scene by appending `?src=<url>` to the page URL.@@ -104895,7 +110615,9 @@ https://three.ws/splat?src=https://github.com/<user>/<repo>/blob/main/scene.splaSupported inputs at a glance:-- `.ply`: Gaussian-splat point cloud in PLY format.+- `.ply`: Gaussian-splat point cloud in PLY format, plain or in PlayCanvas's compressed variant.+- `.spz`: [Niantic's compressed container](https://github.com/nianticlabs/spz), about a tenth the size of the equivalent PLY. The broadest delivery format in the ecosystem.+- `.sog`: [PlayCanvas Spatially Ordered Gaussians](https://developer.playcanvas.com/user-manual/gaussian-splatting/formats/sog/), roughly 15 to 20 times smaller than the PLY. What SuperSplat exports.- `.splat`: the antimatter15 layout (32 bytes per splat).- `.ksplat`: the compressed KSplat format for faster loads.@@ -104911,13 +110633,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-118) and [avatar pipeline](#sec-122) cover the mesh (GLB) avatar path.-- [Scene Capture](#sec-145) reconstructs point clouds from video, a related radiance-adjacent capture flow.+- [Avatar creation](#sec-121) and [avatar pipeline](#sec-125) cover the mesh (GLB) avatar path.+- [Scene Capture](#sec-149) 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-459"></a>+<a id="sec-477"></a>> **Source:** `docs/spotlight.md` · [↑ table of contents](#table-of-contents)@@ -105048,7 +110770,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-439). The database tables are still named+> behind [`/showcase`](#sec-457). 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.@@ -105185,7 +110907,7 @@ to `/spotlight` rather than unfurling a 404.----<a id="sec-460"></a>+<a id="sec-478"></a>> **Source:** `docs/stage.md` · [↑ table of contents](#table-of-contents)@@ -105349,16 +111071,16 @@ The browser resolves the realtime server from, in order: `window.STAGE_SERVER_UR## Related- [Agent wallets](#sec-074): the host wallet a stage provisions at creation and receives tips into.-- [Lip-sync](#sec-303) and [Voice Lab](#sec-576): the speech and mouth-shape machinery the host performs with.+- [Lip-sync](#sec-314) and [Voice Lab](#sec-596): the speech and mouth-shape machinery the host performs with.- [Agent abilities](#sec-011): the always-on Stage Show variant that runs the same ShowDirector inside an agent's own screen.-- [Notifications](#sec-342): the go-live and tip notifications a stage emits.-- [Agora](#sec-077) and [IRL presence](#sec-294): the other rooms on the same realtime backbone, with the same presence discipline.+- [Notifications](#sec-353): the go-live and tip notifications a stage emits.+- [Agora](#sec-077) and [IRL presence](#sec-304): 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-461"></a>+<a id="sec-479"></a>> **Source:** `docs/start-here.md` · [↑ table of contents](#table-of-contents)@@ -105392,9 +111114,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-308)+**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-319)-**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-292) or [Quick start →](#sec-414)+**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-302) or [Quick start →](#sec-429)---@@ -105418,19 +111140,19 @@ 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-075)** — understand the two core concepts (5 min read)-2. **[Make your first agent](#sec-308)** — create a 3D AI character in the browser, no code-3. **[Share & embed](#sec-436)** — get the embed snippet and put your agent anywhere-4. **[Do I need crypto?](#sec-195)** — honest answers to the wallet and payment questions+2. **[Make your first agent](#sec-319)** — create a 3D AI character in the browser, no code+3. **[Share & embed](#sec-453)** — get the embed snippet and put your agent anywhere+4. **[Do I need crypto?](#sec-200)** — 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-444).+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-462).-Built something worth showing? Put it on the wall. [Agent Spotlight](#sec-459) 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-477) 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-242).+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-248).-Curious what happens between the prompt and the model? [How the Forge works](#sec-272) tells the story in plain language; [the Forge pipeline](#sec-244) is the full engineering deep dive.+Curious what happens between the prompt and the model? [How the Forge works](#sec-281) tells the story in plain language; [the Forge pipeline](#sec-250) is the full engineering deep dive.-Want the model in your hands rather than on a screen? [Materialize](#sec-311) 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-322) 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.---@@ -105438,101 +111160,101 @@ Want the model in your hands rather than on a screen? [Materialize](#sec-311) 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-386) — 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-153): 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 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-440)-- **Want that character to tell you what actually matters?** → [The Companion](#sec-166): 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-400) — 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-157): 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 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-458)+- **Want that character to tell you what actually matters?** → [The Companion](#sec-170): 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-060) — 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-059), 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-- **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-121) shows their reputation, wallet, and profile-- **Running a live event in the world?** → [Live events in `/play`](#sec-379): 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-234): 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-159): 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-378): 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-376): 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-443): 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-452): 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)-- **Placing agents in the real world?** → [IRL](#sec-294): 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-315) 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-418). Vote on the best community models and win the weekly board: [Forge-Off](#sec-243)-- **Using ChatGPT?** → [AR in ChatGPT](#sec-151) 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-- **Making videos without showing your face?** → [Motion Swap](#sec-337) — 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-168) — 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-494) shows how every part works-- **Want a full-body avatar assistant on your site instead?** → [Assistant widget](#sec-109) — 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-479) maps the solo stack (Radar, Coin Intelligence, Live Trade Feed, Watchlist, Mission Control); [trading arenas](#sec-475) covers tournaments, the theater, vaults, and swarms; [Oracle](#sec-364) is the conviction engine underneath all of it-- **Want your agent to trade for you?** → [Agent Sniper](#sec-062) — 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-491)+- **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-124) shows their reputation, wallet, and profile+- **Running a live event in the world?** → [Live events in `/play`](#sec-392): 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-239): 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-163): 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-391): 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-389): 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-461): 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-470): 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)+- **Placing agents in the real world?** → [IRL](#sec-304): 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-326) 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-433). Vote on the best community models and win the weekly board: [Forge-Off](#sec-249)+- **Using ChatGPT?** → [AR in ChatGPT](#sec-155) 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+- **Making videos without showing your face?** → [Motion Swap](#sec-348) — 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-172) — 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-514) shows how every part works+- **Want a full-body avatar assistant on your site instead?** → [Assistant widget](#sec-110) — 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-499) maps the solo stack (Radar, Coin Intelligence, Live Trade Feed, Watchlist, Mission Control); [trading arenas](#sec-495) covers tournaments, the theater, vaults, and swarms; [Oracle](#sec-376) is the conviction engine underneath all of it+- **Want your agent to trade for you?** → [Agent Sniper](#sec-062) — 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-511)- **Wondering what stands between the chat agent and your wallet?** → [The agent runtime and transaction guard](#sec-058): 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-451), 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?** → [Custody you can verify](#sec-187) — spend limits, freeze, Merkle proof-of-custody, and social recovery; [claim your wallet](#sec-472) turns any pump.fun track record into a public, provable Trader Card. Every real-funds feature sits behind the [risk acknowledgment](#sec-424) — read the [Risk Disclosure](https://three.ws/legal/risk) before committing anything-- **Need a track record another app can verify?** → [Trader Passport](#sec-473): 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-197): 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-469), 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?** → [Custody you can verify](#sec-191) — spend limits, freeze, Merkle proof-of-custody, and social recovery; [claim your wallet](#sec-492) turns any pump.fun track record into a public, provable Trader Card. Every real-funds feature sits behind the [risk acknowledgment](#sec-439) — read the [Risk Disclosure](https://three.ws/legal/risk) before committing anything+- **Need a track record another app can verify?** → [Trader Passport](#sec-493): 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-202): 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-055): 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-482) — 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-113): 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-341) — 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-309) — 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)-- **Trading Robinhood Chain?** → [Robinhood Chain on three.ws](#sec-425) — 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-- **Listing our services across the x402 ecosystem?** → [x402 distribution](#sec-618) — 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-- **Debugging an x402 integration?** → [x402 developer tools](#sec-617) — 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-137) — 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-139) — `/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-138) — `/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-571) — 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-375): upgrade with a single on-chain payment in USDC, SOL, or $THREE (the platform coin takes 20% off); [hold-to-access](#sec-262) covers the separate hold-$THREE tier ladder; [the $THREE thesis](#sec-468) is the long-form case for the token with every utility, sink, listing, and risk in one place; [The First 19 Weeks](#sec-467) is the week-by-week record of everything shipped since the first commit; [the open-source ecosystem](#sec-356) maps every package, server, contract, and registry where the code lives-- **Building a community perk?** → [Token-gated 3D embeds](#sec-470) — 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-252): 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-246): 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-148) has 106 rigged characters (one click into the Studio, Animation Studio, or an embed) and the [Object Library](#sec-352) has hundreds of CC0 props with live preview, AR placement, and direct GLB download-- **Rendering avatars outside the viewer?** → [Media and render API](#sec-319): 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-483): `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-449): 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-265). Sharing a house is [Households](#sec-263): 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-270). Talking to the house without finding a phone: [the browser voice loop](#sec-271), 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-268): 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-146): 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-117): 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-536) is the guided walkthrough-- **Need to know whether a mesh will actually simulate?** → [Simulation readiness](#sec-442): 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-423): 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-324): 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-371): 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-417): 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-583): 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-577): 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+- **Vetting a counterparty before you pay it?** → [Trust primitives](#sec-502) — 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-116): 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-352) — 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-320) — 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)+- **Trading Robinhood Chain?** → [Robinhood Chain on three.ws](#sec-440) — 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+- **Listing our services across the x402 ecosystem?** → [x402 distribution](#sec-639) — 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+- **Debugging an x402 integration?** → [x402 developer tools](#sec-638) — 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-141) — 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-143) — `/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-142) — `/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-591) — 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-388): upgrade with a single on-chain payment in USDC, SOL, or $THREE (the platform coin takes 20% off); [hold-to-access](#sec-270) covers the separate hold-$THREE tier ladder; [the $THREE thesis](#sec-487) is the long-form case for the token with every utility, sink, listing, and risk in one place; [The First 19 Weeks](#sec-485) is the week-by-week record of everything shipped since the first commit; [the open-source ecosystem](#sec-368) maps every package, server, contract, and registry where the code lives+- **Building a community perk?** → [Token-gated 3D embeds](#sec-490) — 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-258): 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-252): 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-152) has 106 rigged characters (one click into the Studio, Animation Studio, or an embed) and the [Object Library](#sec-364) has hundreds of CC0 props with live preview, AR placement, and direct GLB download+- **Rendering avatars outside the viewer?** → [Media and render API](#sec-330): 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-503): `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-467): 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-274). Sharing a house is [Households](#sec-272): 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-279). Talking to the house without finding a phone: [the browser voice loop](#sec-280), 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-277): 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-150): 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-120): 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-556) is the guided walkthrough+- **Need to know whether a mesh will actually simulate?** → [Simulation readiness](#sec-460): 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-438): 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-335): 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-384): 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-432): 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-604): 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-598): 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- **Driving an agent wallet from code?** → [The agent wallet control API](#sec-073): 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-144): 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-520): 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)-- **Published a skill and want to get paid for it?** → [Skill royalties](#sec-446): 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-- **Checking whether the economy is real?** → [Agent economy volume](#sec-053) counts only settled agent-to-agent USDC for paid skills, and [Viability](#sec-574) 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-054) turns a brand brief into a rigged avatar plus posed studio renders; [Living Stages](#sec-460) covers shareable stages; [the Avatar Engines Atlas](#sec-119) is the factual survey of the engines in this space and which ones we animate+- **Turning a token into a paid endpoint?** → [CA to x402](#sec-148): 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-540): 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)+- **Published a skill and want to get paid for it?** → [Skill royalties](#sec-464): 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+- **Checking whether the economy is real?** → [Agent economy volume](#sec-053) counts only settled agent-to-agent USDC for paid skills, and [Viability](#sec-594) 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-054) turns a brand brief into a rigged avatar plus posed studio renders; [Living Stages](#sec-478) covers shareable stages; [the Avatar Engines Atlas](#sec-122) 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-385) has the logos, the usage rules, and the boilerplate (editorial use needs no permission), and [the partner ecosystem](#sec-368) maps every partner program to what the integration actually is-- **Backing an agent with capital?** → [USDC agent vaults](#sec-572): 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-557): 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-181): 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-247): 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-- **Not ready to risk money on a trader yet?** → [Ghost-copy](#sec-255): 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-- **Watching identities land on-chain?** → [On-chain deployments](#sec-192): 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-193): 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-416): hash-chained, on-chain-anchored records of every consequential agent decision, verifiable by anyone at /ledger-- **Following Solana traders?** → [KOL Tracker](#sec-298): 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-399) has the logos, the usage rules, and the boilerplate (editorial use needs no permission), and [the partner ecosystem](#sec-381) maps every partner program to what the integration actually is+- **Backing an agent with capital?** → [USDC agent vaults](#sec-592): 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-577): 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-185): 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-253): 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+- **Not ready to risk money on a trader yet?** → [Ghost-copy](#sec-261): 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+- **Watching identities land on-chain?** → [On-chain deployments](#sec-196): 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-197): 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-431): hash-chained, on-chain-anchored records of every consequential agent decision, verifiable by anyone at /ledger+- **Following Solana traders?** → [KOL Tracker](#sec-309): 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-064): /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-342): the bell, the /notifications center, category filters, and the full inbox API-- **Something too important for a badge?** → [Herald](#sec-261): 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-297): 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-152): 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-382): 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-332): 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-239): 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-184): 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-469): three.ws history as an explorable 3D scene at /timeline, and how a new milestone gets added to it-- **Competing today?** → [Daily Match](#sec-189): live daily standings over real agent output (actions, trades, skill sales, launches), resetting 00:00 UTC-- **Developer docs** → Read the [Introduction](#sec-292) for the full technical picture-- **Contributing code?** → [Shared utilities](#sec-437) — 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-421): 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-353) — the Agent Identity Studio and the pay-per-call 3D services other agents buy from us; demo identities at [/agent-identities](/agent-identities)+- **Catching up on your inbox?** → [Notifications](#sec-353): the bell, the /notifications center, category filters, and the full inbox API+- **Something too important for a badge?** → [Herald](#sec-269): 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-308): 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-156): 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-396): 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-343): 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-245): 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-188): 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-489): three.ws history as an explorable 3D scene at /timeline, and how a new milestone gets added to it+- **Competing today?** → [Daily Match](#sec-193): live daily standings over real agent output (actions, trades, skill sales, launches), resetting 00:00 UTC+- **Developer docs** → Read the [Introduction](#sec-302) for the full technical picture+- **Contributing code?** → [Shared utilities](#sec-454) — 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-436): 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-365) — 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-205) — 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-555) 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-210) — 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-575) 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-061) — 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-125) — 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-367): 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-128) — 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-380): 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---@@ -105540,64 +111262,66 @@ Want the model in your hands rather than on a screen? [Materialize](#sec-311) prDeeper references that don't fit a track above but answer real questions:-- [The ship log](#sec-438): 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-196): 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-336): 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-459): 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+- [Global Intel Globe](#sec-264): 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-455): 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-201): 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-347): 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-477): 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-452): 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-347): 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-290): 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-431): 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-432): 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-433): 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-434): 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-387): 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-293): 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-249): 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-- [Tokens API on three.ws](#sec-471): 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-346): what the platform already runs on NVIDIA silicon and what the program adds on top-- [NVIDIA visibility map](#sec-351): 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-135): 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-- [The generator was never the hard part](#sec-349): our Nemotron Nano write-up, published on the NVIDIA Developer Forums-- [three.ws on the AWS Builder Center](#sec-131): 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-325): 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-275): 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-354): 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-359): 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-300): 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-447): 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-448): 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-449): 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-450): 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-401): 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-303): 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-255): 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+- [Tokens API on three.ws](#sec-491): 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-358): what the platform already runs on NVIDIA silicon and what the program adds on top+- [NVIDIA visibility map](#sec-363): 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-138): 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+- [The generator was never the hard part](#sec-361): our Nemotron Nano write-up, published on the NVIDIA Developer Forums+- [three.ws on the AWS Builder Center](#sec-134): 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-336): 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-285): 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-366): 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-011): the full abilities dossier, generated from the source article-- [Use cases and example workflows](#sec-170): five audience-specific walkthroughs tying shipped features to concrete outcomes-- [UX Flow Atlas](#sec-558): screen-by-screen traces of the platform's core flows, starting with onboarding and creation-- [Demo routes](#sec-190): the canonical map of every `/demo/*` and `/demos/*` route-- [Agent trading spec](#sec-457): the proposed agent trading capability contract-- [ERC-8004 validation attestation](#sec-207): the attestation written when an agent registers on-chain-- [zauth](#sec-626): the vendored security infrastructure docs our agent auth builds on+- [Use cases and example workflows](#sec-174): five audience-specific walkthroughs tying shipped features to concrete outcomes+- [UX Flow Atlas](#sec-578): screen-by-screen traces of the platform's core flows, starting with onboarding and creation+- [Demo routes](#sec-194): the canonical map of every `/demo/*` and `/demos/*` route+- [Agent trading spec](#sec-475): the proposed agent trading capability contract+- [ERC-8004 validation attestation](#sec-212): the attestation written when an agent registers on-chain+- [zauth](#sec-647): the vendored security infrastructure docs our agent auth builds on- [Agent tokens](#sec-071): 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-394): the vendored on-chain program reference behind the launch surfaces-- [pump-fun-mcp at the edge](#sec-390): the Cloudflare Workers mirror of the pump.fun MCP endpoint-- [Package extraction](#sec-366): how reusable packages graduate out of the monorepo+- [pump.fun program docs](#sec-409): the vendored on-chain program reference behind the launch surfaces+- [pump-fun-mcp at the edge](#sec-405): the Cloudflare Workers mirror of the pump.fun MCP endpoint+- [Package extraction](#sec-379): how reusable packages graduate out of the monorepo- [Agent task briefs](#sec-066): self-contained task prompts for AI agents working on the platform-- [Troubleshooting and FAQ](#sec-481): fixes organized by symptom-- [The 3D viewer](#sec-575): the rendering layer reference (model loading, cameras, animation, lighting)-- [Avatar Artifact](#sec-116): the standalone viewer page, its ?agent= and ?model= parameters, and the iframe you paste anywhere-- [Farcaster memory seeding](#sec-238): give an agent your Farcaster voice, proved with a wallet the account already verified, and revoke it in one click-- [X memory seeding](#sec-588): 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-256): 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)+- [Troubleshooting and FAQ](#sec-501): fixes organized by symptom+- [The 3D viewer](#sec-595): the rendering layer reference (model loading, cameras, animation, lighting)+- [Avatar Artifact](#sec-119): the standalone viewer page, its ?agent= and ?model= parameters, and the iframe you paste anywhere+- [Farcaster memory seeding](#sec-244): give an agent your Farcaster voice, proved with a wallet the account already verified, and revoke it in one click+- [X memory seeding](#sec-609): 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-262): 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-430): 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-302): 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-235): copy-paste-ready code for common use cases+- [The catalog quality gate](#sec-446): 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-313): 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-240): 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-384): the monthly Data API pass, one on-chain payment replacing per-call micropayments for 30 days-- [Guardian console](#sec-259): the inbox for the other side of social recovery and inheritance of agent wallets-- [Coin Clash](#sec-155): token-gated community battles between coin factions-- [Daily Forge](#sec-188): a new deterministic 3D creative challenge every day-- [x402 Studio](#sec-623): the merchant console for running a paid x402 business on three.ws-- [Contributing](#sec-176): local environment setup through a mergeable pull request-- [ERC-8004 smart contracts](#sec-448): contract interfaces, deployed addresses, and how to read and write each registry-- [Internationalization](#sec-276): how the UI translation catalog works and how to add a locale+- [Premium](#sec-398): the monthly Data API pass, one on-chain payment replacing per-call micropayments for 30 days+- [Guardian console](#sec-267): the inbox for the other side of social recovery and inheritance of agent wallets+- [Coin Clash](#sec-159): token-gated community battles between coin factions+- [Daily Forge](#sec-192): a new deterministic 3D creative challenge every day+- [x402 Studio](#sec-644): the merchant console for running a paid x402 business on three.ws+- [Contributing](#sec-180): local environment setup through a mergeable pull request+- [ERC-8004 smart contracts](#sec-466): contract interfaces, deployed addresses, and how to read and write each registry+- [Internationalization](#sec-286): how the UI translation catalog works and how to add a locale----<a id="sec-462"></a>+<a id="sec-480"></a>> **Source:** `docs/strategy-objects.md` · [↑ table of contents](#table-of-contents)@@ -105703,16 +111427,16 @@ curl -s https://three.ws/api/sniper/backtest \## Related-- [Custody you can verify](#sec-187) - the spend limits and audit trail every live run is bounded by-- [Financial controls](#sec-240) - the plain-English rules and firewall layered on the same enforcement point-- [Oracle](#sec-364) - the conviction engine an entry gate can require before it fires-- [Trading surfaces](#sec-479) - where equipped strategies execute through the guarded path-- [Trading arenas](#sec-475) - competitive surfaces where strategies are put to the test+- [Custody you can verify](#sec-191) - the spend limits and audit trail every live run is bounded by+- [Financial controls](#sec-246) - the plain-English rules and firewall layered on the same enforcement point+- [Oracle](#sec-376) - the conviction engine an entry gate can require before it fires+- [Trading surfaces](#sec-499) - where equipped strategies execute through the guarded path+- [Trading arenas](#sec-495) - 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-463"></a>+<a id="sec-481"></a>> **Source:** `docs/swarms.md` · [↑ table of contents](#table-of-contents)@@ -105722,9 +111446,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-338) first, which this builds on rather than repeats. For the single-agent trading pipeline that a swarm's treasury reuses, see [agent sniper](#sec-062), and for the earned-autonomy model behind each member's weight, see [earned autonomy](#sec-451).+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-349) first, which this builds on rather than repeats. For the single-agent trading pipeline that a swarm's treasury reuses, see [agent sniper](#sec-062), and for the earned-autonomy model behind each member's weight, see [earned autonomy](#sec-469).-> **This moves real money.** `contribute` and `exit` transfer real SOL on Solana mainnet. Nothing here is simulated. Read the [risk acknowledgment](#sec-424) 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-439) 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).@@ -105930,14 +111654,14 @@ Every failure returns `{ error, error_description }` with a specific code rather## Related-- [Multi-agent coordination](#sec-338), the general model swarms specialize.-- [Trading arenas](#sec-475), which covers swarms alongside tournaments, the theater, and vaults.-- [USDC agent vaults](#sec-572), 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-187) for the spend guards every transfer here passes through.+- [Multi-agent coordination](#sec-349), the general model swarms specialize.+- [Trading arenas](#sec-495), which covers swarms alongside tournaments, the theater, and vaults.+- [USDC agent vaults](#sec-592), 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-191) for the spend guards every transfer here passes through.----<a id="sec-464"></a>+<a id="sec-482"></a>> **Source:** `docs/syndication.md` · [↑ table of contents](#table-of-contents)@@ -105967,7 +111691,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-585). |+| `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-606). || `archive` | Both archived accounts, merged and de-duplicated, newest first. |The value is case-insensitive. Anything else is a `400` with@@ -106013,12 +111737,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-368), [Listings and-distribution](#sec-305).+See also: [Partners](#sec-381), [Listings and+distribution](#sec-316).----<a id="sec-465"></a>+<a id="sec-483"></a>> **Source:** `docs/talking-avatar-video.md` · [↑ table of contents](#table-of-contents)@@ -106031,9 +111755,9 @@ API: `POST /api/avatar/presign-audio` · `GET`/`POST /api/avatar/video-generate`## Why it exists-Real-time browser lipsync (see [Lipsync](#sec-303)) 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-314)) 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-576) 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-596) and bring the resulting clip here.## How it works@@ -106044,7 +111768,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` (a short-lived signed URL). 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-104), 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-105), 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 }`.8. **Poll.** The client polls `GET /api/avatar/video-status?job_id=...` every 5 seconds (20-minute safety timeout). 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."@@ -106109,14 +111833,14 @@ curl -H 'cookie: __Host-sid=<SESSION>' \## Related-- [Voice Lab](#sec-576): clone or synthesize the audio track you upload here.-- [Lipsync](#sec-303): the real-time, in-browser lipsync path (no export).-- [Selfie to Avatar](#sec-435) and [Avatar reconstruction](#sec-123): create the avatar you render.+- [Voice Lab](#sec-596): clone or synthesize the audio track you upload here.+- [Lipsync](#sec-314): the real-time, in-browser lipsync path (no export).+- [Selfie to Avatar](#sec-451) and [Avatar reconstruction](#sec-126): 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-466"></a>+<a id="sec-484"></a>> **Source:** `docs/terminal.md` · [↑ table of contents](#table-of-contents)@@ -106130,7 +111854,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-479) 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-499) 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@@ -106237,15 +111961,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-479)-- [Coin Radar](#sec-415) and [Smart Money Radar](#sec-450) feed the same intel into their own surfaces-- [Oracle: the conviction engine](#sec-364) supplies the fused conviction score-- [Financial controls and custody guardrails](#sec-240) and [custody](#sec-187) document the server-side rails every order runs through+- [The trading surfaces: Radar, Mission Control, Live Trade Feed, Watchlist, Coin Intelligence](#sec-499)+- [Coin Radar](#sec-430) and [Smart Money Radar](#sec-468) feed the same intel into their own surfaces+- [Oracle: the conviction engine](#sec-376) supplies the fused conviction score+- [Financial controls and custody guardrails](#sec-246) and [custody](#sec-191) 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-467"></a>+<a id="sec-485"></a>> **Source:** `docs/the-first-19-weeks.md` · [↑ table of contents](#table-of-contents)@@ -106889,7 +112613,175 @@ Contract address: FeMbDoX7R1Psc4GEcvJdsbNbZA3bfztcyDCatJVJpump----<a id="sec-468"></a>+<a id="sec-486"></a>++> **Source:** `docs/three-microbuy.md` · [↑ table of contents](#table-of-contents)++# $THREE micro-buy loop++Many tiny, real on-chain buys of `$THREE` per minute, each triggered by (and paid+through) a settled x402 payment. It exists to put continuous, verifiable buy+pressure on `$THREE` — a steady drip of small market buys that show up on-chain and+on the chart, rather than one large buy a day.++It is the high-frequency, small-ticket sibling of the [daily buyback](../api/_lib/token/buyback.js):++| | Daily buyback | Micro-buy loop |+|---|---|---|+| Cadence | a few large buys/day | many tiny buys/minute (target ~60/min) |+| Ticket | $10–$250 | ~$0.01 |+| Trigger | scheduled cron | a settled x402 call |+| Funding | buyback wallet USDC | micro-buy wallet USDC |+| Direction | **buy-only** | **buy-only** |++Both lanes buy on Jupiter through the same client ([api/_lib/token/jupiter.js](../api/_lib/token/jupiter.js))+and sweep the bought tokens to the treasury. **Neither ever sells `$THREE`.**++## How one buy works++1. The driver [api/cron/three-buy-loop.js](../api/cron/three-buy-loop.js) fires a+ paid x402 call to `/api/x402/three-buy`. The small toll+ (`X402_PRICE_THREE_BUY`, default $0.001 USDC) routes to the ring treasury+ (`X402_PAY_TO_SOLANA`) — exactly like every other ring endpoint. This is the+ "pay through the x402 loop" leg.+2. The endpoint ([api/x402/three-buy.js](../api/x402/three-buy.js)) delivers the+ paid good: it executes **one** USDC→`$THREE` market buy on Jupiter+ (`THREE_MICROBUY_USD`, default $0.01), funded by the micro-buy wallet — a+ **separate** money stream from the toll.+3. The bought `$THREE` accrues in the micro-buy wallet and is swept to the+ treasury by the loop every `THREE_MICROBUY_SWEEP_EVERY_N_TICKS` ticks.++The toll and the buy are deliberately decoupled (same custody-vs-accounting split+the daily buyback uses): the toll is internal recirculation; the buy is the real+market spend.++## Safety++Execution is **off by default**. Until `THREE_MICROBUY_ENABLED` is truthy *and* a+funded signer exists, every call is a recorded no-op and the toll is refused (the+endpoint re-emits its 402, so the caller is never charged for a buy that didn't+happen).++- **Daily ceiling.** `THREE_MICROBUY_DAILY_CAP_USD` (default $50) is the hard bound+ on real market spend and SOL fee burn. It is enforced **atomically** — the engine+ reserves the day's budget in Redis *before* broadcasting a buy, so a flood of+ concurrent calls can never collectively overshoot the cap. A DB sum over+ `three_microbuy_runs` is the fallback when Redis is down.+- **Fail-closed.** If *neither* Redis nor the ledger DB can confirm today's spend,+ the buy is **refused** (`cap_unverifiable`), not allowed. Unbounded real-money+ spend is the one outcome the cap exists to prevent, so the engine never assumes+ "zero spent" on an infrastructure outage.+- **Fail-closed toll.** Because the endpoint refuses the toll whenever a buy can't+ happen (disabled, unfunded, cap reached), a direct payer can force buys only up+ to the same daily ceiling the loop obeys — there is no amplification past the cap.+- **Self-healing ledger.** The loop and endpoint create `three_microbuy_runs` on+ first use, so the DB cap fallback and the records always work even on a fresh or+ behind database — the migration owns it in a real deploy, this is the backstop.+- **Kill switches.** `X402_AUTONOMOUS_ENABLED=false` (global) or+ `THREE_MICROBUY_ENABLED` unset stops everything; `THREE_MICROBUY_LOOP_ENABLED=false`+ pauses only the driver while leaving the endpoint payable.+- **No wasted hammering.** A tick stops early on a fully-failed wave (cap exhausted,+ disabled, unfunded, or an RPC/DB outage) instead of firing every remaining call+ for nothing — reported as `stop_reason` in the tick response.+- **Not in the generic ring.** `three-buy` is `autobuy:false` in+ [ring-catalog.js](../api/_lib/x402/ring-catalog.js), so the generic ring rotation+ never fires real buys — only its dedicated driver does (pinned by a test).++Every call writes an immutable row to `three_microbuy_runs`+([migration](../api/_lib/migrations/20260717233000_three_microbuy.sql)) — submitted,+confirmed, pending, skipped, or failed — so there is never a silent no-op.++## Throughput — hitting ~60/min++The whole tick runs inside the economy-tick 60s call budget, so 60 buys/min only+works if each buy is fast. Two things make it fast:++- **Broadcast-and-go (default).** Waiting for each buy to confirm would pin it to+ the ~2–12s block time — at 60/min that can't fit. So the engine returns as soon as+ the buy is broadcast (`status: submitted`) and does **not** block on confirmation.+ This is safe because the daily cap is reserved *before* broadcast (spend is bounded+ regardless) and the treasury sweep reads real on-chain balances (accounting+ self-corrects). Flip `THREE_MICROBUY_AWAIT_CONFIRM=true` only if you need per-call+ confirmation and can accept a lower rate.+- **Distinct transactions.** At 60/min many buys of the same size fire within one+ blockhash window; identical amount + quote would let Jupiter build byte-identical+ transactions that collide on signature (the duplicate is silently dropped). A tiny+ per-buy amount jitter (0–255 atomics, ≤ $0.000255) makes every buy a distinct+ market order, so none are lost to collisions. Jupiter's keyless tier absorbs the+ per-buy quote load (measured: 20 concurrent quotes, zero throttling).++Recommended 60/min config: `THREE_MICROBUY_PER_TICK=60`, leave+`THREE_MICROBUY_CONCURRENCY` unset (auto-sizes to 15 wide), keep+`THREE_MICROBUY_AWAIT_CONFIRM` off. At ~1–2s/buy and 15-wide, a full 60-buy tick+lands in ~8–15s. Make sure the micro-buy wallet holds enough SOL for fees:+60 buys/min ≈ 0.5–1.7 SOL/day at typical priority fees.++## Observability++- **Tick response.** `/api/cron/three-buy-loop` returns `fired`, `paid`, `buys`,+ `pending`, `errors`, `toll_spent_usd`, `daily_spent_usd`, `daily_cap_usd`, and+ `stop_reason` for the tick.+- **Public stats.** `microbuyStats()` (lifetime + today's buys, $THREE bought, USDC+ deployed, cap-used %) is surfaced on the `$THREE` token stats API+ ([api/three-token/[action].js](../api/three-token/[action].js) → `/api/three-token/stats`)+ under `token.microbuy`, alongside the daily buyback summary.+- **Ring volume.** The x402 tolls show up in the ring dashboards tagged+ `pipeline='three-buy'` (per-endpoint volume ledger + `x402_autonomous_log`).++## Turning it on++```bash+# 1. Apply the schema. db:migrate already hardcodes --apply and has no dry run,+# so read db:status first: db:migrate applies EVERY pending migration, not+# just this lane's (api/_lib/migrations/20260717233000_three_microbuy.sql).+npm run db:status+npm run db:migrate++# 2. Fund a wallet with USDC (+ a little SOL for fees). Reuse the buyback wallet, or+# set a dedicated key so the two lanes don't compete for the same USDC:+# THREE_MICROBUY_SECRET_KEY_B64=<base64 of 64 secret-key bytes>++# 3. Set env on the Cloud Run service (gcloud run services update … --update-env-vars):+# THREE_MICROBUY_ENABLED=true+# THREE_MICROBUY_USD=0.01 # per-buy size+# THREE_MICROBUY_PER_TICK=60 # ~60 buys/min+# THREE_MICROBUY_DAILY_CAP_USD=50 # hard daily spend bound+# THREE_MICROBUY_CONCURRENCY=8 # workers/tick++# 4. The economy-tick heartbeat drives it every minute (target 'three-buy-loop').+# Verify a tick:+curl -s -H "Authorization: Bearer $CRON_SECRET" https://three.ws/api/cron/three-buy-loop | jq+```++The response reports `fired`, `paid`, `buys`, `pending`, `errors`, `toll_spent_usd`,+`daily_spent_usd`, `daily_cap_usd`, and `stop_reason` for the tick.++## Configuration++| Env | Default | Meaning |+|---|---|---|+| `THREE_MICROBUY_ENABLED` | off | Master execution gate. |+| `THREE_MICROBUY_LOOP_ENABLED` | on | Set `false` to pause only the driver. |+| `THREE_MICROBUY_SECRET_KEY_B64` | buyback wallet | Dedicated signer/funder (base64 64-byte key). |+| `THREE_MICROBUY_USD` | `0.01` | USD per single buy (hard-capped at 5). |+| `THREE_MICROBUY_DAILY_CAP_USD` | `50` | UTC-daily ceiling on real spend. |+| `THREE_MICROBUY_PER_TICK` | `10` | Buys per minute (hard-capped at 60). Set `60` for the target rate. |+| `THREE_MICROBUY_CONCURRENCY` | auto (≤15) | Concurrent buy workers per tick. Unset auto-sizes to the per-tick target; override clamps to 1–30. |+| `THREE_MICROBUY_AWAIT_CONFIRM` | `false` | Wait for each buy to confirm on-chain. Off = broadcast-and-go (required for 60/min). |+| `THREE_MICROBUY_SLIPPAGE_BPS` | `300` | Jupiter slippage tolerance. |+| `THREE_MICROBUY_SWEEP_EVERY_N_TICKS` | `30` | Sweep accrued `$THREE` to treasury cadence. |+| `X402_THREE_BUY_TOLL_CAP_ATOMIC` | `1000000` | Per-tick ceiling on internal tolls (USDC atomics). |+| `X402_PRICE_THREE_BUY` | `1000` | Per-call toll price (USDC atomics, $0.001). |++## Related++- [docs/x402-ring-economy.md](#sec-642) — 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-487"></a>> **Source:** `docs/three-thesis.md` · [↑ table of contents](#table-of-contents)@@ -106914,23 +112806,24 @@ Contract address: FeMbDoX7R1Psc4GEcvJdsbNbZA3bfztcyDCatJVJpump4. [The core argument: a token attached to a machine that earns](#4-the-core-argument-a-token-attached-to-a-machine-that-earns)5. [Every $THREE utility and sink, in full](#5-every-three-utility-and-sink-in-full)6. [Revenue routing: how platform income turns into $THREE demand](#6-revenue-routing-how-platform-income-turns-into-three-demand)-7. [The revenue engine underneath: x402 and the agent economy](#7-the-revenue-engine-underneath-x402-and-the-agent-economy)-8. [The self-funding treasury and its zero-leak record](#8-the-self-funding-treasury-and-its-zero-leak-record)-9. [Distribution, listings, and verification](#9-distribution-listings-and-verification)-10. [Ecosystem, partners, and enterprise surfaces](#10-ecosystem-partners-and-enterprise-surfaces)-11. [Why the narrative fits the moment](#11-why-the-narrative-fits-the-moment)-12. [Roadmap and the catalysts still in front of the token](#12-roadmap-and-the-catalysts-still-in-front-of-the-token)-13. [Risks, caveats, and what the repo admits about itself](#13-risks-caveats-and-what-the-repo-admits-about-itself)-14. [What is not documented (and what a diligent holder should ask)](#14-what-is-not-documented-and-what-a-diligent-holder-should-ask)-15. [How to evaluate the thesis over time](#15-how-to-evaluate-the-thesis-over-time)-16. [Summary of the bull case](#16-summary-of-the-bull-case)-17. [Appendix: source index](#17-appendix-source-index)+7. [The buy-side engines: daily buyback and the micro-buy loop](#7-the-buy-side-engines-daily-buyback-and-the-micro-buy-loop)+8. [The revenue engine underneath: x402 and the agent economy](#8-the-revenue-engine-underneath-x402-and-the-agent-economy)+9. [The self-funding treasury and its zero-leak record](#9-the-self-funding-treasury-and-its-zero-leak-record)+10. [Distribution, listings, and verification](#10-distribution-listings-and-verification)+11. [Ecosystem, partners, and enterprise surfaces](#11-ecosystem-partners-and-enterprise-surfaces)+12. [Why the narrative fits the moment](#12-why-the-narrative-fits-the-moment)+13. [Roadmap and the catalysts still in front of the token](#13-roadmap-and-the-catalysts-still-in-front-of-the-token)+14. [Risks, caveats, and what the repo admits about itself](#14-risks-caveats-and-what-the-repo-admits-about-itself)+15. [What is not documented (and what a diligent holder should ask)](#15-what-is-not-documented-and-what-a-diligent-holder-should-ask)+16. [How to evaluate the thesis over time](#16-how-to-evaluate-the-thesis-over-time)+17. [Summary of the bull case](#17-summary-of-the-bull-case)+18. [Appendix: source index](#18-appendix-source-index)---## 1. The one-paragraph version-Most tokens are a story looking for a product. $THREE is the reverse: it is the coin of a shipping, open-source, revenue-generating platform that gives AI agents a 3D body, an on-chain identity, a wallet, and a way to get paid. The platform (three.ws) has published 2,738 changelog entries in about four and a half months, exposes 761 public pages, ships 89 npm packages and 39 MCP servers, and runs a live pay-per-call economy (x402) with over one million individually priced datapoints. The token is wired into that machine at every level: hold-to-access tiers create standing demand, and a 20% discount on plans and premium passes creates spend demand. Supply is never destroyed by the platform. The token trades on MEXC, LBank, KCEX, Bybit Alpha, KuCoin Alpha, and every major Solana DEX, is Jupiter-verified, Phantom-verified, and a verified project on pump.fun. It is a real product's real coin, and the product is one of the more complete agent-economy stacks in the open-source world.+Most tokens are a story looking for a product. $THREE is the reverse: it is the coin of a shipping, open-source, revenue-generating platform that gives AI agents a 3D body, an on-chain identity, a wallet, and a way to get paid. The platform (three.ws) has published 2,738 changelog entries in about four and a half months, exposes 761 public pages, ships 89 npm packages and 39 MCP servers, and runs a live pay-per-call economy (x402) with over one million individually priced datapoints. The token is wired into that machine at every level: hold-to-access tiers create standing demand, a 20% discount on plans and premium passes creates spend demand, a policy that commits 50% of platform revenue to market buybacks creates buy-side pressure, a micro-buy loop turns every settled x402 call into a small $THREE purchase, and on-chain agent deploys route their fee to the buyback wallet. Supply is never destroyed by the platform; instead the treasury buys. The token trades on MEXC, LBank, KCEX, Bybit Alpha, KuCoin Alpha, and every major Solana DEX, is Jupiter-verified, Phantom-verified, and a verified project on pump.fun. It is a real product's real coin, and the product is one of the more complete agent-economy stacks in the open-source world.The thesis is not "number go up." The thesis is: **if agents become economic actors, they need bodies, identities, wallets, and rails, and three.ws has shipped all four with $THREE in the middle.**@@ -106944,7 +112837,7 @@ The tagline is "Give your AI a body." The platform does five things (README, "co2. **Render.** glTF 2.0 and GLB in WebGL 2.0 on three.js r184, with Draco, KTX2, and Meshopt compression, and zero server-side processing on the render path.3. **Embody.** An LLM brain (Claude), a tool loop of up to eight iterations per turn, morph-target emotion blending, and ARKit-52 lip-sync. The avatar does not just look alive; it acts.4. **Register.** On-chain identity via ERC-8004 on any EVM chain, or a Metaplex Core NFT on Solana. Agents get a provable, portable identity.-4. **Embed.** An `<agent-3d>` web component plus five widget types and OpenGraph / oEmbed support, so any site can host a live avatar.+5. **Embed.** An `<agent-3d>` web component plus five widget types and OpenGraph / oEmbed support, so any site can host a live avatar.On top of those five, the platform layers an entire agent economy:@@ -107000,7 +112893,7 @@ Strip away the feature list and the argument for $THREE reduces to four linked c**Claim 1: The platform earns money.** It sells 3D generation, rigging, remeshing, voice cloning, agent embodiment, coin launches, vanity addresses, data intelligence, DeFi analytics, market data, reputation scoring, identity verification, and over a million priced datapoints, all through x402 pay-per-call rails, plus subscription plans (Pro, Team, Enterprise), a Premium Data API pass, and marketplace fees. The customers include humans, but increasingly the customers are other AI agents that pay USDC to call an endpoint without a human in the loop.-**Claim 2: A published policy routes that money into $THREE.** The economy policy in `api/_lib/token/config.js` states: every $THREE the platform charges routes to treasury, a holder-rewards pool, and (on a sale) the seller. Supply is never destroyed by the platform.+**Claim 2: A published policy routes that money into $THREE.** The economy policy in `api/_lib/token/config.js` states: every $THREE the platform charges routes to treasury, a holder-rewards pool, and (on a sale) the seller. Supply is never destroyed; the treasury funds buybacks instead. Separately, `THREE_BUYBACK_COMMIT_BPS` defaults to 5,000: **50% of platform revenue committed to market buybacks**, with the code comment explaining the team chose the conservative floor of the credible 50 to 80% band "so the platform over-delivers rather than over-promises."**Claim 3: Holding the token is rewarded, not just spending it.** The hold-to-access tier ladder (Bronze at $25 held through Genesis at $2,500 held) grants compute discounts up to 30% and free-quota multipliers up to 10x, resolved from live USD value of tokens *held, never spent*. The documentation calls this "a deflation-free status lever that creates standing demand rather than one-time spend." Rider passes, holder worlds, token-gated embeds, `/play` access, Coin Clash enlistment, and the metaplex deploy-fee waiver all read live balances the same way.@@ -107066,7 +112959,7 @@ From `packages/metaplex-agent-mcp/README.md`:| 50,000 or more | 0.01 SOL || 250,000 or more | **free** |-The fee rides inside the same transaction that creates the asset, so a failed deploy costs nothing. It is disclosed before signature. Nothing is staked or locked; the balance is read live at transaction-build time. A `three_status` MCP tool prices a deploy for any wallet and returns live market figures. Changelog, 2026-08-19: "holders deploy free."+The fee rides inside the same transaction that creates the asset, so a failed deploy costs nothing. It is disclosed before signature. Critically, **the fee is paid to the wallet the $THREE buyback lane spends from**, which means every on-chain agent deploy is converted into $THREE buy pressure. Nothing is staked or locked; the balance is read live at transaction-build time. A `three_status` MCP tool prices a deploy for any wallet and returns live market and buyback figures. Changelog, 2026-08-19: "Deploying an agent on-chain now buys $THREE, and holders deploy free."### 5.5 The marketplace prices only in $THREE@@ -107124,7 +113017,7 @@ The fee rides inside the same transaction that creates the asset, so a failed de`api/_lib/token/config.js` defines the split policies. Every basis-point set sums to 10,000 and the rounding remainder goes to the highest leg so per-leg atomics reconcile exactly.-| Policy | Applies to | Seller / creator | Treasury | Rewards (holder reflections) |+| Policy | Applies to | Seller / creator | Treasury (funds buybacks) | Rewards (holder reflections) ||---|---|---:|---:|---:|| `consumption` | Forge paid tiers, voice clone, MCP-3D, Granite, selfie-to-avatar | none | **70%** | **30%** || `spin` | paid wheel spins | none | **50%** | **50%** |@@ -107132,15 +113025,50 @@ The fee rides inside the same transaction that creates the asset, so a failed de| `scarcity_mint` | scarcity drops, rare-name auctions, pay-to-mint | none | **80%** | **20%** || `copy_performance_fee` | copy-trading fee on realized profit only | leader **80%** | 15% | 5% |-Note the rewards leg, which funds holder reflections: the public `GET /api/three-token/revenue-share` endpoint exposes `revenue_share_pool_pct` (currently 10), `revenue_share_pool_usd`, and `per_token_yield` alongside price, supply, and holder count.+Two things to notice. First, the treasury leg is explicitly "funds buybacks," so consumption revenue in $THREE is recycled into market demand rather than sitting idle. Second, the rewards leg funds holder reflections: the public `GET /api/three-token/revenue-share` endpoint exposes `revenue_share_pool_pct` (currently 10), `revenue_share_pool_usd`, and `per_token_yield` alongside price, supply, and holder count.The wallets fail closed in production. If `THREE_TREASURY_WALLET` or `THREE_REWARDS_WALLET` is unset, the platform returns a typed 503 rather than routing real funds to a placeholder. Nobody's money goes to a default address by accident.----## 7. The revenue engine underneath: x402 and the agent economy+## 7. The buy-side engines: daily buyback and the micro-buy loop++### 7.1 The daily buyback (`api/_lib/token/buyback.js`)-The token's demand vectors are only as strong as the revenue behind them. This is what feeds them.+- Converts accumulated platform USDC revenue into market buys of $THREE on Jupiter, then routes the bought tokens to the treasury. The code states plainly: "NO platform burn: supply is never destroyed by this lane."+- **Published commitment: 50% of platform revenue** (`THREE_BUYBACK_COMMIT_BPS` default 5,000).+- Per-run maximum $250 (`THREE_BUYBACK_MAX_USD`), dust floor $10, slippage 3%.+- Custody and accounting are deliberately decoupled: the spend is driven by the buyback wallet's live USDC balance, while the public "revenue earned" figure reads the `agent_revenue_events` fee ledger. This keeps the earned-versus-deployed ratio honest and auditable.+- Execution is gated by `THREE_BUYBACK_ENABLED`. Until an operator funds the wallet and opts in, a scheduled run is a recorded no-op. (See risk 4 in section 14.)++### 7.2 The micro-buy loop (`docs/three-microbuy.md`)++| | Daily buyback | Micro-buy loop |+|---|---|---|+| Cadence | a few large buys per day | many tiny buys per minute (target ~60/min) |+| Ticket | $10 to $250 | ~$0.01 |+| Trigger | scheduled cron | a settled x402 call |+| Direction | buy-only | buy-only |++"Neither ever sells $THREE." Each micro-buy is triggered by a paid x402 call to `/api/x402/three-buy` (a $0.001 toll that goes to the ring treasury), after which the endpoint executes exactly one USDC-to-$THREE Jupiter market buy from a dedicated micro-buy wallet. Bought tokens sweep to the treasury every 30 ticks.++Safety design: off by default; a $50 daily cap reserved atomically in Redis before any broadcast; a fail-closed `cap_unverifiable` state if neither Redis nor the ledger can confirm today's spend; a fail-closed toll so a direct payer can never amplify past the cap; `three-buy` is marked `autobuy: false` in the ring catalog so generic rotation never fires real buys; an immutable row per call in `three_microbuy_runs`; and a 0 to 255 atomic jitter per buy so byte-identical Jupiter transactions never collide on signature.++Public accountability: `/api/three-token/stats` exposes `token.microbuy` with lifetime and today's buys, $THREE bought, USDC deployed, and cap used. Anyone can check whether the loop is running and how much it has bought.++### 7.3 Why "buyback, never burn" is the right design++Burn-based tokenomics look good on a slide and bad in a treasury. A burn permanently converts revenue into nothing; a buyback converts revenue into an asset the platform still controls, which can fund liquidity, reflections, holder rewards, or future buybacks. The three.ws policy chooses buy pressure without deflation and says so in code. The user-invoked burn remains available for anyone who wants deflation on their own terms.++### 7.4 External buyback precedent++On 2026-06-08, three.ws won the DEXTools Social Boost. DEXTools executed a **$5,543 buyback** and its wallet subsequently held **2.47M $THREE** (`blog/three-ws-dextools-social-boost-buyback.html`). Third-party capital has already been deployed into the token on the strength of the community.++---++## 8. The revenue engine underneath: x402 and the agent economy++The buyback and micro-buy engines are only as strong as the revenue behind them. This is what feeds them.### 8.1 The x402 price catalog (`docs/x402-endpoints.md`)@@ -107180,14 +113108,14 @@ Strangers stake USDC behind a verified trading agent. The opening gate is real:----## 8. The self-funding treasury and its zero-leak record+## 9. The self-funding treasury and its zero-leak record`docs/autonomous-economy.md` and `docs/money-map.md` describe a closed-loop wallet system:| Wallet | Role ||---|---|| Funding root (`WwwuGbqHrwF5...T3WwW`) | Reserve; funder only; never trades, launches, or settles |-| Engine wallet (`wwwqv...HGUn`) | pump.fun launcher, reflection and lottery payouts |+| Engine wallet (`wwwqv...HGUn`) | pump.fun launcher, buyback relayer, reflection and lottery payouts || Treasury / receiver (`wwwwwDxFWRn7grgr3Esrsg5C6NvDoDHSA4gaCffccrU`) | All inbound x402 || Ring payer (`X4o2...astML`) | The autonomous x402 payment ring || a2a-payer (`Huch...Lmh6Z`) | Co-signs agent-to-agent USDC |@@ -107201,7 +113129,7 @@ For a token holder this matters in a specific way: the treasury that is supposed----## 9. Distribution, listings, and verification+## 10. Distribution, listings, and verificationA token can have perfect mechanics and no liquidity. $THREE has both real venues and real trust badges.@@ -107243,7 +113171,7 @@ Official channels: X `@trythreews`, Telegram `@three_ws` and community `t.me/thr----## 10. Ecosystem, partners, and enterprise surfaces+## 11. Ecosystem, partners, and enterprise surfacesThe pump.fun article title ("Three Builds With Tech Giants") is earned. From `docs/listings.md` and `docs/partners.md`:@@ -107273,7 +113201,7 @@ What this adds up to: a Solana memecoin-launched token whose platform has a foot----## 11. Why the narrative fits the moment+## 12. Why the narrative fits the momentThree converging trends make three.ws the right shape of product for 2026:@@ -107283,15 +113211,15 @@ Three converging trends make three.ws the right shape of product for 2026:**3. Agents need bodies.** Text chat is not the end state of AI interaction. Voice, expression, and presence are. three.ws's core competence, rigged and animated 3D avatars with emotion blending and lip-sync that any site can embed, is the interface layer. The pipeline runs on its own GPU fleet, not a rented API.-$THREE sits at the intersection: it is the fee token, the discount token, the access token, the escrow token, and the wage token for a platform that does all three.+$THREE sits at the intersection: it is the fee token, the discount token, the access token, the escrow token, the wage token, and the buyback target for a platform that does all three.-**Solana-first is a deliberate advantage.** The platform's operating rules state that Solana is the home chain and every EVM chain is secondary. Low fees and fast finality are what make $0.0005 datapoints economically possible in the first place. A pay-per-call agent economy at these price points cannot run on mainnet Ethereum.+**Solana-first is a deliberate advantage.** The platform's operating rules state that Solana is the home chain and every EVM chain is secondary. Low fees and fast finality are what make $0.0005 datapoints and $0.01 micro-buys economically possible in the first place. A pay-per-call agent economy at these price points cannot run on mainnet Ethereum.-**Open source is a deliberate advantage.** Anyone can audit the split policies, the cap enforcement, the leak scanners, and the tier resolvers. Trust that can be verified compounds; trust that must be taken on faith decays.+**Open source is a deliberate advantage.** Anyone can audit the split policies, the buyback logic, the cap enforcement, the leak scanners, and the tier resolvers. Trust that can be verified compounds; trust that must be taken on faith decays.----## 12. Roadmap and the catalysts still in front of the token+## 13. Roadmap and the catalysts still in front of the tokenFrom the README roadmap:@@ -107305,51 +113233,53 @@ From the README roadmap:Token-specific catalysts, in rough order of proximity:-1. **Perk activation.** `worlds.private` at Silver is fully specified (migration drafted, gate written, test planned). `names.first_dibs` at Genesis and `drops.early` at Gold follow. Each activation gives a specific tier a specific reason to exist.-2. **CoinGecko MEXC market addition** (request filed 2026-08-16).-3. **Listing follow-through**: AWS Marketplace product creation, OKX.AI resubmission, OpenAI Plugin Directory submission, Cookbook PR merge.-4. **Phase 3 contracts and audits**: agent tokens, reputation markets, and royalty contracts on-chain would make $THREE the settlement asset of a far larger economy.-5. **Phase 4 open inference network**: independent node operators serving production traffic would turn three.ws from a platform into a protocol.-6. **Coin Clash** expanding into "a bigger community-warfare idea the platform is building for $THREE."+1. **Buyback and micro-buy activation.** Both engines are built, tested, capped, and publicly accountable via `/api/three-token/stats`. Flipping `THREE_BUYBACK_ENABLED` and `THREE_MICROBUY_ENABLED` with funded wallets turns published policy into daily on-chain buys.+2. **Perk activation.** `worlds.private` at Silver is fully specified (migration drafted, gate written, test planned). `names.first_dibs` at Genesis and `drops.early` at Gold follow. Each activation gives a specific tier a specific reason to exist.+3. **CoinGecko MEXC market addition** (request filed 2026-08-16).+4. **Listing follow-through**: AWS Marketplace product creation, OKX.AI resubmission, OpenAI Plugin Directory submission, Cookbook PR merge.+5. **Phase 3 contracts and audits**: agent tokens, reputation markets, and royalty contracts on-chain would make $THREE the settlement asset of a far larger economy.+6. **Phase 4 open inference network**: independent node operators serving production traffic would turn three.ws from a platform into a protocol.+7. **Coin Clash** expanding into "a bigger community-warfare idea the platform is building for $THREE."Phase targets stated in the README: 10k avatars per day at launch; 1,000 test users end to end at 4/5 likeness or better; 30% week-2 retention on minted agents; 1,000 agents minted with active on-chain reputation; 50% of production agent traffic served by independent nodes.----## 13. Risks, caveats, and what the repo admits about itself+## 14. Risks, caveats, and what the repo admits about itselfA thesis that hides the risks is a pitch. These are the risks the three.ws documentation states about itself, plus the structural ones any holder should weigh.1. **Most holder perks are Planned, not Live.** Only two of seven registered gated features (`forge.high`, `forge.gameready`) are enforced today. The compute discount and quota multiplier are live. The `enforced` flag exists precisely so the platform never promises an unwired perk, but a holder buying for `worlds.private` or `names.first_dibs` is buying a roadmap.-2. **The burn policy is internally inconsistent.** `api/_lib/token/config.js` states "NO PLATFORM BURNS, supply is never destroyed," while `api/three-token/[action].js` ships an `AGENT_DEPLOY_BURN = 1000` constant and a `/burns` ledger reporting 1,000 $THREE burned per agent deploy. No document reconciles these. A holder should treat the deploy-burn ledger as an open question.+2. **The burn policy is internally inconsistent.** `api/_lib/token/config.js` states "NO PLATFORM BURNS, supply is never destroyed," while `api/three-token/[action].js` ships an `AGENT_DEPLOY_BURN = 1000` constant and a `/burns` ledger reporting 1,000 $THREE burned per agent deploy. Blog posts from May and June 2026 describe a "planned buyback-and-burn." No document reconciles these. A holder should treat the current code policy (buyback, no platform burn) as authoritative and the deploy-burn ledger as an open question.-3. **Older blog claims predate current mechanics.** The May 2026 listing and CoinMarketCap posts describe mechanics the current code no longer implements; the current code implements the tier ladder. The direction of travel is toward more utility, but the public record has drift.+3. **Older blog claims predate current mechanics.** The May 2026 listing and CoinMarketCap posts describe buyback-and-burn and the Rider VR gate as the token's utility; the current code implements buyback-without-burn plus the tier ladder. The direction of travel is toward more utility, but the public record has drift.+4. **The buyback and micro-buy engines are off by default and operator-gated.** The 50% commitment is policy independent of whether any given run is enabled or funded. Until the flags are on and the wallets funded, the buy-side pressure described in section 7 is designed, tested, and dormant. The public stats endpoint will show exactly when that changes.-4. **Circulation-engine activity is platform-owned by design.** The buys are real and on-chain, but the sellers are platform agents. It is not organic third-party demand and the documentation says so explicitly.+5. **Circulation-engine activity is platform-owned by design.** The buys are real and on-chain, but the sellers are platform agents. It is not organic third-party demand and the documentation says so explicitly.-5. **The marketplace platform fee and pump trade fee default to 0%.** The take-rate exists as a knob but is off unless configured. Marketplace GMV does not currently produce platform revenue.+6. **The marketplace platform fee and pump trade fee default to 0%.** The take-rate exists as a knob but is off unless configured. Marketplace GMV does not currently produce platform revenue.-6. **Several distribution milestones are pending, not done.** AWS Marketplace listing not yet created, OKX.AI rejected 2026-07-04 with resubmission pending, OpenAI Cookbook PR unmerged since 2026-07-21, Azure roadmap-only.+7. **Several distribution milestones are pending, not done.** AWS Marketplace listing not yet created, OKX.AI rejected 2026-07-04 with resubmission pending, OpenAI Cookbook PR unmerged since 2026-07-21, Azure roadmap-only.-7. **Alpha venue liquidity is invisible to CoinGecko.** Bybit Alpha and KuCoin Alpha volume cannot be submitted, so aggregator volume understates real liquidity. This cuts both ways: the token is more liquid than CoinGecko shows, and that liquidity is harder to verify.+8. **Alpha venue liquidity is invisible to CoinGecko.** Bybit Alpha and KuCoin Alpha volume cannot be submitted, so aggregator volume understates real liquidity. This cuts both ways: the token is more liquid than CoinGecko shows, and that liquidity is harder to verify.-8. **Historical accounting corrections.** The platform has published its own mistakes: marketplace analytics once counted 10,454 free trials as "sales" and reported 6.2M $THREE of volume against zero confirmed purchases (fixed; money aggregates now gate on `status = 'confirmed'`); the circulation engine once bought too little $THREE to afford its own listings, so GMV read zero while fees went out (fixed by shortfall sizing). These are to the team's credit as disclosures, and to the holder's attention as evidence that reported metrics have needed correction before.+9. **Historical accounting corrections.** The platform has published its own mistakes: marketplace analytics once counted 10,454 free trials as "sales" and reported 6.2M $THREE of volume against zero confirmed purchases (fixed; money aggregates now gate on `status = 'confirmed'`); the circulation engine once bought too little $THREE to afford its own listings, so GMV read zero while fees went out (fixed by shortfall sizing). These are to the team's credit as disclosures, and to the holder's attention as evidence that reported metrics have needed correction before.-9. **Vault risk, in the platform's words:** "the platform can sign for the vault," "a vault owner can change the performance fee and the risk terms after you have deposited," and "there is no server-side 'are you sure' step, no preview mode, and no undo."+10. **Vault risk, in the platform's words:** "the platform can sign for the vault," "a vault owner can change the performance fee and the risk terms after you have deposited," and "there is no server-side 'are you sure' step, no preview mode, and no undo."-10. **A fail-open path exists.** The older `three-gate.js` returns `eligible: true` on an RPC failure. The newer tier-pass path fails to Member (closed). Gating that relies on the older path can be bypassed during an RPC outage.+11. **A fail-open path exists.** The older `three-gate.js` returns `eligible: true` on an RPC failure. The newer tier-pass path fails to Member (closed). Gating that relies on the older path can be bypassed during an RPC outage.-11. **Funding is not secured.** The README states plainly that inference GPUs, training compute, multi-firm smart-contract audits, token-launch liquidity, indexer infrastructure, node-operator credits, and engineering headcount are "required for the vision; neither is funded yet." The Google Cloud credit grant (up to $200k over two years) covers a meaningful part of the compute line but not the audits or headcount.+12. **Funding is not secured.** The README states plainly that inference GPUs, training compute, multi-firm smart-contract audits, token-launch liquidity, indexer infrastructure, node-operator credits, and engineering headcount are "required for the vision; neither is funded yet." The Google Cloud credit grant (up to $200k over two years) covers a meaningful part of the compute line but not the audits or headcount.-12. **The mandatory risk disclosure applies to $THREE payments.** Before any first real-funds action, including `$THREE token payments`, users must acknowledge that "three.ws is experimental software, losses can be total, autonomous agents act without asking again." The platform requires that acknowledgment from its users; a holder should hold the same view.+13. **The mandatory risk disclosure applies to $THREE payments.** Before any first real-funds action, including `$THREE token payments`, users must acknowledge that "three.ws is experimental software, losses can be total, autonomous agents act without asking again." The platform requires that acknowledgment from its users; a holder should hold the same view.-13. **General token risk.** A pump.fun-launched Solana token is a high-volatility asset. Liquidity is concentrated on a handful of venues. The platform's revenue, while real, is early. The economy policy is operator-controlled, not a smart contract the operator cannot change.+14. **General token risk.** A pump.fun-launched Solana token is a high-volatility asset. Liquidity is concentrated on a handful of venues. The platform's revenue, while real, is early. The buyback commitment is a policy the operator controls, not a smart contract the operator cannot change.----## 14. What is not documented (and what a diligent holder should ask)+## 15. What is not documented (and what a diligent holder should ask)The repository is silent on the following. Their absence is a fact, not a red flag by itself, but a serious holder should seek answers from the team's official channels.@@ -107357,18 +113287,20 @@ The repository is silent on the following. Their absence is a fact, not a red fl- **No team or treasury allocation, lockups, or LP-burn statement.**- **No governance, staking, or voting mechanism.** $THREE is a utility and access token, not a governance token, and the repo does not claim otherwise.- **No documented emissions to users.** The in-game economy is explicit that $THREE is never awarded by gameplay. Agora and the labor market pay $THREE, but from escrow funded by posters, not from inflation.-- **No cumulative revenue or holder count in the docs.** All of these are read live from public endpoints (`/api/three-token/stats`, `/revenue-share`, `/leaderboard`, `/agent-economy-volume`) rather than quoted in prose. That is the correct design, and it means the numbers in this document are a snapshot that the endpoints will outdate.+- **No cumulative revenue, cumulative buyback USD, or holder count in the docs.** All of these are read live from public endpoints (`/api/three-token/stats`, `/revenue-share`, `/leaderboard`, `/agent-economy-volume`) rather than quoted in prose. That is the correct design, and it means the numbers in this document are a snapshot that the endpoints will outdate.Questions worth asking: What is the treasury's current $THREE and USDC balance? How is the deploy-burn ledger reconciled with the no-platform-burn policy? What is the team's own holding and is it locked?----## 15. How to evaluate the thesis over time+## 16. How to evaluate the thesis over timeBecause the platform exposes its economy through public endpoints, the thesis is falsifiable. A holder can track it without trusting anyone:| Signal | Where to look | What confirms the thesis ||---|---|---|+| Buybacks are running | `GET /api/three-token/stats` (`buyback` summary) | Non-zero USDC deployed, rising lifetime $THREE bought |+| Micro-buy loop is running | same endpoint, `token.microbuy` | Today's buys greater than zero, cap-used percentage moving || Platform revenue is growing | `GET /api/three-token/revenue-share` (`platform_revenue_usd`) and `/agent-economy-volume` | Month-over-month growth in settled USDC || Holder base is growing | `GET /api/three-token/leaderboard`, `total_holders` in stats | Rising holder count, falling top-10 concentration || Perks are activating | `api/_lib/three-access.js` `enforced` flags | More entries flip to `true` |@@ -107377,17 +113309,18 @@ Because the platform exposes its economy through public endpoints, the thesis is| Listings expand | CoinGecko `three-ws` markets tab | MEXC added, new venues appear || Verification holds | `verified` field in `/api/three-token/stats` | Stays `true` |-If perks never activate or revenue does not grow, the thesis weakens and the endpoints will show it. If they do, the endpoints will show that too.+If buybacks never turn on, perks never activate, or revenue does not grow, the thesis weakens and the endpoints will show it. If they do, the endpoints will show that too.----## 16. Summary of the bull case+## 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-467).+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-485).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. **Two simultaneous demand vectors**: standing demand from holding, and spend demand from discounts. The platform never sells and never burns.-6. **Real liquidity and real trust**: MEXC, LBank, KCEX, Bybit Alpha, KuCoin Alpha, Binance Web3, Coinbase Wallet, PumpSwap, Meteora, Orca, perps on derp.trade, Jupiter Verified, Phantom Verified, pump.fun verified project, CoinGecko, CoinMarketCap.+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.+5. **Every deploy buys $THREE.** On-chain agent deploy fees are paid to the buyback wallet, and large holders deploy free.+6. **Real liquidity and real trust**: MEXC, LBank, KCEX, Bybit Alpha, KuCoin Alpha, Binance Web3, Coinbase Wallet, PumpSwap, Meteora, Orca, perps on derp.trade, Jupiter Verified, Phantom Verified, pump.fun verified project, CoinGecko, CoinMarketCap, a DEXTools Social Boost win with a $5,543 third-party buyback.7. **Enterprise and ecosystem footprint**: OpenAI Select Partner, NVIDIA Inception, Google Cloud for Web3 Startups, Alibaba Cloud Marketplace live, AWS Marketplace conformant, BNB Dappbay, MCP Registry, x402scan, IBM and HackerNoon coverage, a pump.fun feature article.8. **A treasury that audits itself**: 44,122 transactions scanned, zero leaks ever, with allowlist-locked top-ups and destination-locked sweepbacks enforced in code.9. **A team that publishes its own mistakes** (trial-counting, under-sized buys, listing rumors it declined to submit) and gates every perk behind an integrity flag so it cannot promise what it has not wired.@@ -107399,7 +113332,7 @@ $THREE is a good choice to *look at* because it is one of the very few tokens wh----## 17. Appendix: source index+## 18. Appendix: source indexEvery file referenced in this thesis, relative to the repository root:@@ -107408,23 +113341,138 @@ Every file referenced in this thesis, relative to the repository root:- `CLAUDE.md` (promoted-coin policy, Solana-first policy)- `package.json`, `data/pages.json`, `data/changelog.json`, `public/mcp-catalog.json`- `api/_lib/token/config.js` (economy policy, split policies)+- `api/_lib/token/buyback.js` (daily buyback)- `api/_lib/three-tier.js`, `api/_lib/three-access.js`, `api/_lib/require-three.js`, `api/_lib/comp-access.js`, `api/_lib/three-gate.js`- `api/_lib/holder-pass.js`, `api/_lib/world-gate.js`, `api/_lib/play-pass.js`, `api/_lib/rider.js`- `api/_lib/economy-master.js`, `api/_lib/economy-sweepback.js`- `api/three-token/[action].js`, `api/pricing.js`, `api/forge.js`, `api/credits/index.js`- `src/three-access.js`, `src/three-lock.js`, `src/three-allowance.js`, `src/pump/verified-badge.js`, `src/solana/vanity/brand.js`- `docs/hold-to-access.md`, `docs/plan-checkout.md`, `docs/premium.md`, `docs/viability.md`, `docs/money-map.md`-- `docs/circulation-engine.md`, `docs/autonomous-economy.md`, `docs/autonomous-x402.md`, `docs/x402-endpoints.md`, `docs/agent-economy-volume.md`+- `docs/circulation-engine.md`, `docs/three-microbuy.md`, `docs/autonomous-economy.md`, `docs/autonomous-x402.md`, `docs/x402-endpoints.md`, `docs/agent-economy-volume.md`- `docs/labor-market.md`, `docs/agora.md`, `docs/in-game-economy.md`, `docs/token-gated-3d-embeds.md`, `docs/clash.md`, `docs/vaults.md`, `docs/trust-primitives.md`- `docs/coin-launches.md`, `docs/mint-mark.md`, `docs/agent-wallets.md`, `docs/risk-acknowledgment.md`, `docs/exit-lab.md`- `docs/listings.md`, `docs/partners.md`, `docs/coingecko-listing-update-2026-08.md`, `docs/okx-marketplace.md`, `docs/announcement-coverage.md`, `docs/api-reference.md`- `packages/metaplex-agent-mcp/README.md`, `packages/three-token-mcp/README.md`, `packages/agora-mcp/README.md`-- `blog/three-token-listings.html`, `blog/three-ws-on-coinmarketcap.html`+- `blog/three-token-listings.html`, `blog/three-ws-on-coinmarketcap.html`, `blog/three-ws-dextools-social-boost-buyback.html`- `marketing/pumpfun-verified/`----<a id="sec-469"></a>+<a id="sec-488"></a>++> **Source:** `docs/threejs-forum-post.md` · [↑ table of contents](#table-of-contents)++---+venue: three.js Forum (discourse.threejs.org), category "Resources" (cross-post the demo to "Showcase")+account: nichxbt+description: "Forum post for three.js developers: five open-source pieces pulled out of a production WebGL avatar platform, covering universal humanoid retargeting with no rig allowlist, progressive GLB streaming over plain HTTP, a terminal renderer, structural GLB diffing, and a free physics-readiness grade for glTF."+tags: [three.js, gltf, glb, animation, retargeting, webgl]+status: draft, owner approval required before posting (external-channel gate in CLAUDE.md)+---++# Five things we had to build to animate 3D characters nobody on our team modelled++_Post for the [three.js forum](https://discourse.threejs.org), category Resources._++I work on [three.ws](https://three.ws), a browser-native platform where you type a sentence and get a rigged, animated 3D character you can embed anywhere. Apache-2.0, source at [github.com/nirholas/three.ws](https://github.com/nirholas/three.ws).++The constraint that shaped everything: **we never see the model before it arrives.** It might come from our own generation lane, from Mixamo, from VRoid, from Daz, from a Blender export somebody made in 2019, or from a user's photo processed into a mesh ninety seconds ago. The rig is not ours and we do not get to pick the conventions.++Five pieces fell out of that, each published on its own so you can use them without the rest of the platform. All of them are things I looked for first and could not find.++## 1. Retargeting with no rig allowlist++**Package: `@three-ws/retarget`**++The usual approach to "animate any humanoid" is a curated list of supported rigs. It works until the eleventh rig, and every asset marketplace produces new ones faster than you can add them.++Instead we canonicalise bone names first, then retarget onto the canonical set. The mapping covers Mixamo, Unreal, VRM and VRoid, VRM 1.0, Daz/Genesis, MakeHuman, Blender `.L`/`.R` suffixes, and the simple `shoulderL` style rigs, and adding a new convention is one mapping entry plus a test case rather than a new code path.++Two details that took us longer than they should have:++**Legs are where naive retargeting falls apart.** Arm chains forgive a lot of proportion mismatch. Hip and foot chains do not, and the failure mode is a character that walks with its feet sliding, which readers describe as "the animation is broken" rather than "the retarget is wrong".++**The fallback must not be a T-pose.** If a model genuinely cannot be skeleton-driven (no skin, a non-humanoid prop), we detect that and fall back to a default rig rather than rendering a bind-pose statue. A T-pose in production reads as a bug to every user, and as "unsupported" to zero of them.++If you have ever hand-mapped a skeleton table, this is the package I would have wanted.++## 2. Progressive GLB over plain HTTP++**Package: `@three-ws/avatar-stream`**++A 12 MB avatar on a phone on a train is a blank canvas for eight seconds and then, suddenly, a character. Every user reads that pause as a broken page.++`avatar-stream` packs a GLB into a layered stream so the viewer shows something structurally correct early and refines it, over ordinary HTTP with no special server. It is not a replacement for compression, it composes with it. The reason we wrote our own rather than reaching for an existing progressive format is that we needed the first frame to be *correct*, not a blob: an avatar that appears with the wrong proportions and then snaps is worse than one that appears late.++## 3. A structural diff for glTF++**Package: `@three-ws/glb-diff`, live at three.ws/diff**++When a generation pipeline iterates on a mesh, "did that change anything" is asked constantly, and eyeballing two viewers side by side is a bad instrument. `glb-diff` answers structurally: node graph, meshes, primitives, materials, textures, skins, animations, and what moved between two versions.++It started as an internal debugging tool for our refine loop and turned out to be the thing I reach for most when a model looks subtly wrong. If you run any pipeline that mutates glTF (optimisation, retexturing, decimation), this is worth ten minutes.++## 4. A physics-readiness grade, and a CC0 spec for it++**Free endpoint: `GET https://three.ws/api/sim-readiness?src=<glb>` . Spec: `specs/SIM_READINESS.md`, CC0**++This is the one I would most like this forum to tear apart, because I think the gap is real and I do not think our answer is final.++A renderer forgives almost everything. A rigid-body solver forgives nothing. The same mesh that renders beautifully in three.js can sink through the floor in a physics engine, behave as if hollow, or turn out to be a metre tall because the generator fitted it to a unit box. **A GLB carries no claim about whether it can be simulated**, so every robotics, game-physics and world-model pipeline rediscovers the same defects by hand, one asset at a time.++The grade answers four things mechanically: closed surface, consistent winding, positive volume, and whether the extents are plausible real-world metres.++```bash+curl "https://three.ws/api/sim-readiness?src=https://three.ws/avatars/cesium-man.glb"+```++Four verdicts. `simulation_ready` is the only one that licenses trusting the reported mass. `needs_scale` means the geometry is sound and only the units are missing (multiply and go). `needs_repair` means open, non-manifold, or inconsistently wound, so the mass properties are reported but unreliable. `unusable` means no triangles or zero volume. There is a fifth value, `unreadable`, for bytes that are not binary glTF 2.0 at all, deliberately distinct: one is a broken file, the other is a valid file with nothing to simulate.++Results are content-addressed by the file's SHA-256, so the same bytes always get the same verdict.++It is free and keyless on purpose: a check that costs money is a check nobody runs, and a check nobody runs prevents nothing.++## 5. A terminal renderer, which sounds like a joke and is not++**Packages: `@three-ws/tty-3d` (core), `@three-ws/tty-avatar` (the CLI)**++```bash+npx @three-ws/tty-avatar 81a076b6-55ff-49a2-b007-1d88e7dce2aa+```++That draws a skinned, animated GLB in colour at 24fps in a plain terminal, no browser and no GPU. Three glyph modes: truecolor half-blocks (two colours per cell), braille (2x4 dots per cell for four times the vertical detail), and a plain luminance ramp when the output is piped.++Two reasons it is not a toy. First, it forced the animation stack to be renderer-agnostic, which caught two bugs that WebGL was hiding. Second, wire it to a coding agent's hooks and the avatar becomes that agent's face: thinking while it reads, nodding while it edits, shaking when a tool fails, bouncing when it finishes. An ambient posture in a second pane is a better progress indicator than a spinner because you read it without switching focus.++## Assorted production notes, since this forum appreciates them++**Meshopt will bite you server-side.** Most of our avatars ship with `EXT_meshopt_compression`. Anything in the pipeline that reads geometry outside a browser (our Python workers use trimesh) has to decode it first, and the failure is confusing because the file loads fine in every viewer you test with. If you run a server-side glTF pipeline, put the decode in front of everything, once, rather than per consumer.++**Release the context between scenes.** Our splat viewer held onto the GPU between scenes and the third scene load on a laptop was a slideshow. Disposing properly on unmount is table stakes advice that everyone including us learns twice.++**Wake heavy previews on view, not on load.** A grid of 3D previews that all initialise on page load will jank on any machine. Intersection-observer gating turned our marketplace grid from a stutter into a scroll.++**Soft shadows are the first thing to silently regress.** A renderer change that makes shadows hard does not throw, does not warn, and nobody notices for a week. Ours regressed across three studio pages at once. If you have a shared light rig, pin it in a test that renders and compares, not in a code review.++**52 ARKit blendshapes is the interchange currency for faces.** Not because it is elegant, but because it is what the tooling, the capture stacks and the models converge on. We map onto it and let the rig-specific weirdness live in one adapter.++## What is where++- Retargeting: `@three-ws/retarget`+- Progressive streaming: `@three-ws/avatar-stream`+- Diffing: `@three-ws/glb-diff`, and the page at [three.ws/diff](https://three.ws/diff)+- Physics readiness: [three.ws/docs/sim-readiness](https://three.ws/docs/sim-readiness), spec CC0+- Terminal rendering: `@three-ws/tty-3d`, `@three-ws/tty-avatar`+- Viewer look and feel: `@three-ws/viewer-presets` (light rigs, floor reflections, bloom, PBR presets)+- The whole platform, if you want to see them in situ: [github.com/nirholas/three.ws](https://github.com/nirholas/three.ws)++The generation side runs open model families on our own GPU fleet, and the free lane is keyless if you want to make something to test any of this against: [three.ws/forge](https://three.ws/forge).++Questions welcome, especially on 1 and 4. The retarget mapping wants more rig conventions from people who have hit ones we have not, and the readiness spec wants adversarial review from anyone who has shipped assets into a physics engine in anger.++---++<a id="sec-489"></a>> **Source:** `docs/timeline.md` · [↑ table of contents](#table-of-contents)@@ -107556,7 +113604,7 @@ server reads that route table on boot).----<a id="sec-470"></a>+<a id="sec-490"></a>> **Source:** `docs/token-gated-3d-embeds.md` · [↑ table of contents](#table-of-contents)@@ -107564,7 +113612,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-436), [Embedding Guide](#sec-204)). 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-453), [Embedding Guide](#sec-209)). 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`.@@ -107669,13 +113717,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-436)+- Embed runtime this builds on: [`<three-d>` / embed v1](https://three.ws/embed/v1/preview), [Share & embed](#sec-453)- 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-262) (site-wide $THREE tiers, distinct from per-embed gates)+- Related: [Hold-to-access tiers](#sec-270) (site-wide $THREE tiers, distinct from per-embed gates)----<a id="sec-471"></a>+<a id="sec-491"></a>> **Source:** `docs/tokens-xyz.md` · [↑ table of contents](#table-of-contents)@@ -107841,12 +113889,12 @@ The batch market read is deliberately **not** cached here. Its caller in the mar## Related-- [Market Data API](#sec-309) - the pay-per-call x402 endpoints behind every `/markets` page-- [Free LLM providers](#sec-249) - the same failover-chain pattern applied to text completion+- [Market Data API](#sec-320) - the pay-per-call x402 endpoints behind every `/markets` page+- [Free LLM providers](#sec-255) - the same failover-chain pattern applied to text completion----<a id="sec-472"></a>+<a id="sec-492"></a>> **Source:** `docs/trader-card.md` · [↑ table of contents](#table-of-contents)@@ -107865,13 +113913,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-364)). 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-376)). 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-475).+**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-495).## Claiming: one signature, no gas@@ -107902,18 +113950,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-318)).+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-329)).## Related-- [Trader Passport](#sec-473): the on-chain credential a claimed record earns, and how another app verifies it-- [Oracle](#sec-364) — the WHO pillar runs on this same wallet-reputation ledger-- [Trading arenas](#sec-475) — where a verified track record unlocks tournaments, vaults, and mirrors-- [Trading surfaces](#sec-479) — the solo trading stack+- [Trader Passport](#sec-493): the on-chain credential a claimed record earns, and how another app verifies it+- [Oracle](#sec-376) — the WHO pillar runs on this same wallet-reputation ledger+- [Trading arenas](#sec-495) — where a verified track record unlocks tournaments, vaults, and mirrors+- [Trading surfaces](#sec-499) — the solo trading stack----<a id="sec-473"></a>+<a id="sec-493"></a>> **Source:** `docs/trader-passport.md` · [↑ table of contents](#table-of-contents)@@ -108077,14 +114125,14 @@ The Proof tab of [`/trader/<agent_id>`](https://three.ws/trader) renders the pas## Related-- [Claim your wallet](#sec-472): the read-only track record that comes before any credential-- [Trading arenas](#sec-475): what a verified record unlocks-- [Copy trading](#sec-181): leaderboard weighting and performance fees-- [API reference](#sec-104): every public endpoint+- [Claim your wallet](#sec-492): the read-only track record that comes before any credential+- [Trading arenas](#sec-495): what a verified record unlocks+- [Copy trading](#sec-185): leaderboard weighting and performance fees+- [API reference](#sec-105): every public endpoint----<a id="sec-474"></a>+<a id="sec-494"></a>> **Source:** `docs/trader-wrapped.md` · [↑ table of contents](#table-of-contents)@@ -108100,7 +114148,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-247) on the+already settled on-chain. The one live action is [Fork](#sec-253) 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.@@ -108110,7 +114158,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-255) replays a leader against+buy and sell signature, and [Ghost-copy](#sec-261) 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.@@ -108243,14 +114291,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-255) to replay the+ to check the record on-chain, and to [Ghost-copy](#sec-261) 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-247) button for the coin, so a+- The best-trade slide carries a [Fork](#sec-253) 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-479).+ the [live trade feed](#sec-499).## Where the code lives@@ -108269,13 +114317,13 @@ $THREE remains the only coin this platform promotes.----<a id="sec-475"></a>+<a id="sec-495"></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-479). 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-499). 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).@@ -108317,7 +114365,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-187)). 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-191)). 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.@@ -108337,18 +114385,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-479) → 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-364) conviction is the intelligence all of these agents are acting on.+Prove yourself solo (the [trading surfaces](#sec-499) → 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-376) conviction is the intelligence all of these agents are acting on.## Related-- [Trading surfaces](#sec-479) — the solo stack (Radar, Mission Control, Trade Feed, Watchlist, Coin Intelligence)-- [Custody](#sec-187) — the spend limits, freeze, and audit rails every mirrored/pooled trade runs through-- [Oracle](#sec-364) — the conviction engine · [Trading experiment](#sec-477) — one agent's journaled live run-- [Agent reputation](#sec-057) / [Solana reputation](#sec-454) — how the trust scores are computed+- [Trading surfaces](#sec-499) — the solo stack (Radar, Mission Control, Trade Feed, Watchlist, Coin Intelligence)+- [Custody](#sec-191) — the spend limits, freeze, and audit rails every mirrored/pooled trade runs through+- [Oracle](#sec-376) — the conviction engine · [Trading experiment](#sec-497) — one agent's journaled live run+- [Agent reputation](#sec-057) / [Solana reputation](#sec-472) — how the trust scores are computed----<a id="sec-476"></a>+<a id="sec-496"></a>> **Source:** `docs/trading-copilot.md` · [↑ table of contents](#table-of-contents)@@ -108496,13 +114544,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-479)-- [Financial controls & custody guardrails](#sec-240)-- [The autonomous trading experiment](#sec-477)+- [The trading surfaces: Radar, Mission Control, Feed, Watchlist, Intel](#sec-499)+- [Financial controls & custody guardrails](#sec-246)+- [The autonomous trading experiment](#sec-497)----<a id="sec-477"></a>+<a id="sec-497"></a>> **Source:** `docs/trading-experiment.md` · [↑ table of contents](#table-of-contents)@@ -108614,7 +114662,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-451). A losing arm cannot reach the field at+[Earned autonomy](#sec-469). 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.@@ -108838,7 +114886,7 @@ much — and tune the next run. That is the whole point of the experiment.----<a id="sec-478"></a>+<a id="sec-498"></a>> **Source:** `docs/trading-hub.md` · [↑ table of contents](#table-of-contents)@@ -108947,22 +114995,22 @@ credentials, and writes nothing.## Related- [Agent Sniper](#sec-062), what the autonomous trader is and how it is wired-- [The 10 SOL experiment](#sec-477), the full risk policy-- [Risk acknowledgment](#sec-424), read before arming real funds-- [Custody model](#sec-187), how an agent holds its own keys-- [Earned autonomy](#sec-451), how an agent earns more freedom-- [Trading Copilot](#sec-476), the fair-launch market maker-- Tutorial: [Arm an autonomous sniper](#sec-491)+- [The 10 SOL experiment](#sec-497), the full risk policy+- [Risk acknowledgment](#sec-439), read before arming real funds+- [Custody model](#sec-191), how an agent holds its own keys+- [Earned autonomy](#sec-469), how an agent earns more freedom+- [Trading Copilot](#sec-496), the fair-launch market maker+- Tutorial: [Arm an autonomous sniper](#sec-511)----<a id="sec-479"></a>+<a id="sec-499"></a>> **Source:** `docs/trading-surfaces.md` · [↑ table of contents](#table-of-contents)# The trading surfaces: Radar, Mission Control, Live Trade Feed, Watchlist, Coin Intelligence-The platform's trading stack is spread across five public pages. Four 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-450) and [Ghost-copy](#sec-255)) each carry a [Fork](#sec-247) 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 five public pages. Four 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-468) and [Ghost-copy](#sec-261)) each carry a [Fork](#sec-253) 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:@@ -108982,7 +115030,7 @@ All five surfaces read the same underlying truth: the Coin Intelligence Engine (On top of that base layer:-- **Oracle conviction** ([the conviction engine](#sec-364)) enriches coins across all five surfaces with its 0–100 fused score and tier.+- **Oracle conviction** ([the conviction engine](#sec-376)) 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`).@@ -108998,7 +115046,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-247)** 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-253)** 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.@@ -109027,7 +115075,7 @@ Click any trade (or paste any mint) and the center pane becomes a full analytics- 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-247)**, 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-253)**, 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@@ -109045,7 +115093,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-240)).+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-246)).The three panes:@@ -109069,7 +115117,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-364) for the fused conviction verdict — and armed agents can run the same loop autonomously (see [the trading experiment](#sec-477) and [Oracle's agent loop](#sec-364)).+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-376) for the fused conviction verdict — and armed agents can run the same loop autonomously (see [the trading experiment](#sec-497) and [Oracle's agent loop](#sec-376)).## API quick reference@@ -109093,21 +115141,21 @@ 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-318) (`@three-ws/intel-mcp`, `@three-ws/portfolio-mcp`) — and the paid x402 lanes in [x402-endpoints](#sec-619).+Agents wanting the same intel over MCP: see [docs/mcp.md](#sec-329) (`@three-ws/intel-mcp`, `@three-ws/portfolio-mcp`) — and the paid x402 lanes in [x402-endpoints](#sec-640).## Related-- [Meta-Allocator: the ETF of degens](#sec-322): diversify a budget across the top verified leaders-- [Clip Director: every trade becomes content](#sec-156): turn any closed trade into shareable cards per surface-- [The Trading Copilot — talk to your wallet](#sec-476) — conversational trading over these same numbers-- [Oracle — the conviction engine](#sec-364) · [/oracle/docs](https://three.ws/oracle/docs)-- [The autonomous trading experiment](#sec-477)-- [Financial controls & custody guardrails](#sec-240)-- [UX flows: crypto trading & analytics](#sec-564) — screen-by-screen walkthrough+- [Meta-Allocator: the ETF of degens](#sec-333): diversify a budget across the top verified leaders+- [Clip Director: every trade becomes content](#sec-160): turn any closed trade into shareable cards per surface+- [The Trading Copilot — talk to your wallet](#sec-496) — conversational trading over these same numbers+- [Oracle — the conviction engine](#sec-376) · [/oracle/docs](https://three.ws/oracle/docs)+- [The autonomous trading experiment](#sec-497)+- [Financial controls & custody guardrails](#sec-246)+- [UX flows: crypto trading & analytics](#sec-584) — screen-by-screen walkthrough----<a id="sec-480"></a>+<a id="sec-500"></a>> **Source:** `docs/triage.md` · [↑ table of contents](#table-of-contents)@@ -109175,14 +115223,14 @@ We are actively looking to grow this. The path is the normal one: land a few goo## Related-- [Your first contribution](#sec-241)+- [Your first contribution](#sec-247)- [CONTRIBUTING.md](../CONTRIBUTING.md)-- [Community](#sec-165)+- [Community](#sec-169)- [Security policy](../.github/SECURITY.md)----<a id="sec-481"></a>+<a id="sec-501"></a>> **Source:** `docs/troubleshooting.md` · [↑ table of contents](#table-of-contents)@@ -109841,7 +115889,7 @@ Idle blink and head-drift are active in the current release: `src/idle-animation----<a id="sec-482"></a>+<a id="sec-502"></a>> **Source:** `docs/trust-primitives.md` · [↑ table of contents](#table-of-contents)@@ -109860,7 +115908,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-624)).+(Base or Solana mainnet, via [x402](#sec-645)).Pass any counterparty identifier. The type is auto-detected and scored from whateverreal on-chain evidence exists for it:@@ -109978,7 +116026,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-624).+dropped >10 points). See the [x402 catalog](#sec-645).---@@ -110003,7 +116051,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-624)).+— $0.005 USDC per call (Base or Solana mainnet, via [x402](#sec-645)).It verifies a **claim** that `identity` controls `address`, for **any** identity type,on any chain — regardless of the platform the counterparty came from:@@ -110077,11 +116125,11 @@ score *whether to trust* them.----See also: [x402 paid endpoints](#sec-624) · [Agent Bouncer](#sec-104) · [ERC-8004 identity](#sec-206)+See also: [x402 paid endpoints](#sec-645) · [Agent Bouncer](#sec-105) · [ERC-8004 identity](#sec-211)----<a id="sec-483"></a>+<a id="sec-503"></a>> **Source:** `docs/tty-avatar.md` · [↑ table of contents](#table-of-contents)@@ -110179,7 +116227,7 @@ Id resolution uses the same public endpoints the web studio does: `/api/avatars/----<a id="sec-484"></a>+<a id="sec-504"></a>> **Source:** `docs/tty.md` · [↑ table of contents](#table-of-contents)@@ -110323,7 +116371,7 @@ are lifted rather than crushed to black.----<a id="sec-485"></a>+<a id="sec-505"></a>> **Source:** `docs/tutorials/add-a-3d-assistant.md` · [↑ table of contents](#table-of-contents)@@ -110441,7 +116489,7 @@ Then ask, in plain language: "build a 3D assistant widget named Aria with an oce----<a id="sec-486"></a>+<a id="sec-506"></a>> **Source:** `docs/tutorials/agent-personality.md` · [↑ table of contents](#table-of-contents)@@ -110894,7 +116942,7 @@ The system prompt is the cheapest, highest-leverage thing you can change about a----<a id="sec-487"></a>+<a id="sec-507"></a>> **Source:** `docs/tutorials/agent-reputation.md` · [↑ table of contents](#table-of-contents)@@ -111171,7 +117219,7 @@ A read costs nothing and asks no one's permission. That's the property that lets----<a id="sec-488"></a>+<a id="sec-508"></a>> **Source:** `docs/tutorials/agent-spending-envelope.md` · [↑ table of contents](#table-of-contents)@@ -111734,7 +117782,7 @@ The two "budget stays reserved" cases are the only place the system deliberately----<a id="sec-489"></a>+<a id="sec-509"></a>> **Source:** `docs/tutorials/animate-your-agent.md` · [↑ table of contents](#table-of-contents)@@ -111746,6 +117794,10 @@ By the end of this tutorial your agent will move on its own: nod when a model fi**Time:** about 12 minutes.+[](/pose)++*Animation Studio drives the same canonical clip library the embeds use.*+---## What you're building@@ -111910,7 +117962,7 @@ The difference that matters is the layer. `wave`, `point`, `nod` and `shrug` are----<a id="sec-490"></a>+<a id="sec-510"></a>> **Source:** `docs/tutorials/animate-your-avatar.md` · [↑ table of contents](#table-of-contents)@@ -111920,6 +117972,10 @@ By the end of this tutorial you'll be able to take any rigged avatar, browse the**Prerequisites:** a three.ws account and at least one rigged avatar ([create one](/create), or load any public avatar). No code required, everything here happens in the browser. Light JavaScript familiarity helps only for the optional "how retargeting works" section.+[](/pose)++*Animation Studio drives the same canonical clip library the embeds use.*+---## What you're building@@ -112092,7 +118148,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-506)), 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-526)), 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.@@ -112132,14 +118188,14 @@ You learned the apply-and-remix workflow for motion on three.ws:- [docs/animations.md](#sec-097): 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-544), loading and switching avatars in the Studio.-- [docs/tutorials/upload-custom-glb.md](#sec-547), getting a Mixamo or custom rig into three.ws as a clean, animatable GLB.+- [docs/tutorials/swap-avatar-in-studio.md](#sec-564), loading and switching avatars in the Studio.+- [docs/tutorials/upload-custom-glb.md](#sec-567), 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-491"></a>+<a id="sec-511"></a>> **Source:** `docs/tutorials/arm-an-agent-sniper.md` · [↑ table of contents](#table-of-contents)@@ -112253,7 +118309,7 @@ The hard-config sniper you just armed is the control group. The next phase runs----<a id="sec-492"></a>+<a id="sec-512"></a>> **Source:** `docs/tutorials/build-a-3d-asset-pipeline.md` · [↑ table of contents](#table-of-contents)@@ -112472,7 +118528,7 @@ step once the mechanical stages are running.----<a id="sec-493"></a>+<a id="sec-513"></a>> **Source:** `docs/tutorials/build-a-scene.md` · [↑ table of contents](#table-of-contents)@@ -112484,6 +118540,10 @@ Along the way you'll learn how the editor's panels fit together, why the scene a**Prerequisites:** a desktop browser (the editor is keyboard- and gizmo-driven). At least one GLB or glTF model to import — generate one for free from text at [/forge](/forge), or use any GLB file you already have. No account required.+[](/scene)++*Scene Studio composes objects and avatars into one shareable scene.*+---## What you're building@@ -112691,7 +118751,7 @@ The leverage of [Scene Studio](/scene) is that it's a *real* editor producing a----<a id="sec-494"></a>+<a id="sec-514"></a>> **Source:** `docs/tutorials/build-a-site-concierge.md` · [↑ table of contents](#table-of-contents)@@ -112809,7 +118869,7 @@ Then: `<three-concierge endpoint="/my/concierge">`. The production reference, wi----<a id="sec-495"></a>+<a id="sec-515"></a>> **Source:** `docs/tutorials/character-library-to-embed.md` · [↑ table of contents](#table-of-contents)@@ -112835,6 +118895,10 @@ Ten minutes is not marketing. The list is: two minutes reading the library manif- No account, no API key, no payment. The library is free and public, and so is the embed runtime.- Background reading, if you want it: [Character Library](/docs/character-library.md) for the gallery and manifest, [Embedding Guide](/docs/embedding.md) for the full `<agent-3d>` contract.+[](/character-library)++*Every character here is a real rigged GLB you can embed as-is.*+---## Step 1 - Read the library@@ -113128,7 +119192,7 @@ Then use that URL in the element:Safe by construction: the upstream objects are already public and keyless, and the proxy fetch runs through an SSRF-hardened client (scheme allowlist, DNS pinning, private-address blocklist, redirect re-validation, 30 MB cap, 20 second timeout). It is a CORS shim, not an open proxy. The response is cached immutably, so the proxy costs one hop on a cold cache and nothing after.-One exception worth knowing, so you do not reach for the proxy reflexively: this applies to the `pub-*.r2.dev` bucket host, which is where every manifest GLB lives. Files served from `three.ws` itself (`https://three.ws/avatars/cesium-man.glb` and the rest of the built-in set) already answer every origin with `access-control-allow-origin: *`, re-measured 2026-09-04. So does `https://three.ws/cdn/<key>`, which serves the very same bucket objects first-party. Those load directly, no proxy. Check the host in the URL, not the symptom.+One exception worth knowing, so you do not reach for the proxy reflexively: this applies to the `pub-*.r2.dev` bucket host, which is where every manifest GLB lives. Files served from `three.ws` itself (`https://three.ws/avatars/cesium-man.glb` and the rest of the built-in set) already answer every origin with `access-control-allow-origin: *`, re-measured 2026-09-09. So does `https://three.ws/cdn/<key>`, which serves the very same bucket objects first-party. Those load directly, no proxy. Check the host in the URL, not the symptom.Use the proxied URL from the start and you never have a localhost-only success to unlearn. The same shim is what makes these GLBs loadable in a Jupyter or Colab notebook and on a dev server running on a non-standard port.@@ -113314,7 +119378,7 @@ Doing the copy server-side also sidesteps cross-origin reads and browser upload----<a id="sec-496"></a>+<a id="sec-516"></a>> **Source:** `docs/tutorials/claim-threews-name.md` · [↑ table of contents](#table-of-contents)@@ -113326,6 +119390,10 @@ Along the way you'll understand what the subdomain points at on-chain, why the m**Prerequisites:** a signed-in three.ws account with a **username set** (the subdomain label must match it) and at least one agent — creating an agent provisions the Solana wallet that receives the name ([create one](/create)). Light JavaScript familiarity for the pay-by-name section; the claim itself is no-code.+[](/threews/claim)++*Claiming a name is one field and one signature.*+---## What you're building@@ -113625,7 +119693,7 @@ See also:----<a id="sec-497"></a>+<a id="sec-517"></a>> **Source:** `docs/tutorials/connect-ai-brain.md` · [↑ table of contents](#table-of-contents)@@ -114047,7 +120115,7 @@ The brain is the part of the agent you'll iterate on most after the system promp----<a id="sec-498"></a>+<a id="sec-518"></a>> **Source:** `docs/tutorials/connect-your-home.md` · [↑ table of contents](#table-of-contents)@@ -114427,14 +120495,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-449): why Home Assistant owns the device layer, what else was+- [docs/smart-home.md](#sec-467): why Home Assistant owns the device layer, what else wasevaluated, and where this goes next.-- [docs/home-households.md](#sec-263): roles, scopes and invites in full.-- [docs/home-privacy.md](#sec-265): what is kept, for how long, and how to delete it.+- [docs/home-households.md](#sec-272): roles, scopes and invites in full.+- [docs/home-privacy.md](#sec-274): what is kept, for how long, and how to delete it.----<a id="sec-499"></a>+<a id="sec-519"></a>> **Source:** `docs/tutorials/create-and-edit-memory.md` · [↑ table of contents](#table-of-contents)@@ -114755,7 +120823,7 @@ The leverage is in *enhancement*: the right type, one fact per memory, tags, del----<a id="sec-500"></a>+<a id="sec-520"></a>> **Source:** `docs/tutorials/custom-skill.md` · [↑ table of contents](#table-of-contents)@@ -114767,6 +120835,10 @@ Along the way you'll understand the skill bundle format, how the LLM decides whe**Prerequisites:** JavaScript familiarity, a text editor, and a place to host static files (a free GitHub Pages or Vercel account works fine).+[](/skills)++*Skills are sold, trialled and installed from this catalogue.*+---## What you're building@@ -115280,7 +121352,7 @@ The skill installs via a URI in the agent manifest, runs entirely client-side, a----<a id="sec-501"></a>+<a id="sec-521"></a>> **Source:** `docs/tutorials/customize-appearance.md` · [↑ table of contents](#table-of-contents)@@ -115299,6 +121371,10 @@ This tutorial walks through every appearance attribute the `<agent-3d>` element**Prerequisites:** A page with the embed working from [Embed in 30 seconds](/tutorials/embed-in-30-seconds). You can write the attributes here straight into that page.+[](/avatar-studio)++*Avatar Studio: the rig on the left, every appearance control on the right.*+---## Step 1 — How the element reads your attributes@@ -115718,7 +121794,7 @@ Most production embeds use four or five of these together. The combination is wh----<a id="sec-502"></a>+<a id="sec-522"></a>> **Source:** `docs/tutorials/deploy-to-vercel-custom-domain.md` · [↑ table of contents](#table-of-contents)@@ -116238,7 +122314,7 @@ In rough order of likelihood:----<a id="sec-503"></a>+<a id="sec-523"></a>> **Source:** `docs/tutorials/earn-and-spend-in-play.md` · [↑ table of contents](#table-of-contents)@@ -116433,16 +122509,16 @@ Every paid sale splits 50% to the holder-rewards sink and 50% to the treasury.## Next-- **[The in-game economy](#sec-289)** is the full reference: every+- **[The in-game economy](#sec-299)** 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-158)** explains the worlds themselves, and how+- **[Coin communities](#sec-162)** explains the worlds themselves, and howany coin becomes a walkable 3D space.----<a id="sec-504"></a>+<a id="sec-524"></a>> **Source:** `docs/tutorials/embed-in-30-seconds.md` · [↑ table of contents](#table-of-contents)@@ -116460,6 +122536,10 @@ This tutorial walks through those two lines end to end. By the time you finish,**Prerequisites:** A text editor and a browser. You do not need Node, npm, a framework, or any 3D experience.+[](/studio)++*Widget Studio writes the embed snippet while you watch the result.*+---## Step 1 — Get an agent ID@@ -116718,7 +122798,7 @@ A working embedded agent is the foundation everything else builds on. From here,----<a id="sec-505"></a>+<a id="sec-525"></a>> **Source:** `docs/tutorials/embed-on-website.md` · [↑ table of contents](#table-of-contents)@@ -116733,6 +122813,10 @@ This tutorial walks you through every path for adding a three.ws agent to your s- Add it to Webflow, WordPress, or Squarespace- Show or hide the agent based on scroll position, page URL, or a timer+[](/studio)++*Widget Studio writes the embed snippet while you watch the result.*+---## Before you start@@ -117229,7 +123313,7 @@ Squarespace's developer preview and published output can differ. Try adding the----<a id="sec-506"></a>+<a id="sec-526"></a>> **Source:** `docs/tutorials/emotion-from-data.md` · [↑ table of contents](#table-of-contents)@@ -117340,7 +123424,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-286)) 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-296)) 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`.@@ -117456,7 +123540,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-286)).+- **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-296)).---@@ -117471,7 +123555,7 @@ function reactIfConfident(clipOrEmoteName, { confident, useExactClip = false } =----<a id="sec-507"></a>+<a id="sec-527"></a>> **Source:** `docs/tutorials/explore-docs-world.md` · [↑ table of contents](#table-of-contents)@@ -117479,6 +123563,10 @@ function reactIfConfident(clipOrEmoteName, { confident, useExactClip = false } =Time: about 5 minutes. You need a browser and nothing else. By the end you will have walked the documentation, read a page inside the scene, and entered the world wearing a custom avatar.+[](/docs/world)++*The documentation as a place you can walk through.*+## 1. Enter the worldOpen [three.ws/docs/world](https://three.ws/docs/world).@@ -117548,13 +123636,13 @@ Make one with the [Forge](/create) or the [Avatar Studio](/avatar-studio), copy## Where to next-- [Docs World reference](#sec-196): controls table, device behaviour, contributor notes.-- [What is three.ws?](#sec-461): the guided tour of the whole platform, readable in either surface.+- [Docs World reference](#sec-201): controls table, device behaviour, contributor notes.+- [What is three.ws?](#sec-479): 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-508"></a>+<a id="sec-528"></a>> **Source:** `docs/tutorials/find-a-better-exit-policy.md` · [↑ table of contents](#table-of-contents)@@ -117757,7 +123845,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-104) accepts, so a finding here maps+[`/api/sniper/strategy`](#sec-105) 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@@ -117797,7 +123885,7 @@ disclaimers bolted onto the result. They are the result.----<a id="sec-509"></a>+<a id="sec-529"></a>> **Source:** `docs/tutorials/first-agent.md` · [↑ table of contents](#table-of-contents)@@ -117813,6 +123901,10 @@ By the end of this tutorial you will have a live, talking 3D character on a page**Prerequisites:** Basic HTML and JavaScript. You don't need to know Three.js, WebGL, or anything 3D-specific.+[](/start)++*The getting-started checklist is the shortest path from account to first agent.*+---## Step 1 — Pick a 3D avatar@@ -118306,7 +124398,7 @@ Now that you have a working agent, here's what to explore next:----<a id="sec-510"></a>+<a id="sec-530"></a>> **Source:** `docs/tutorials/first-prompt-to-3d.md` · [↑ table of contents](#table-of-contents)@@ -118323,6 +124415,10 @@ Type one sentence into ChatGPT and get a real, textured 3D model back: spin it i**Prerequisites:** A ChatGPT account. A smartphone (iPhone or Android) for the AR step; every other step works on a computer.+[](/create/prompt)++*Describe it to 3D: the prompt field and the tier picker are the whole interface.*+---## Step 1: Add the 3D Studio to ChatGPT@@ -118426,7 +124522,7 @@ A rigged avatar's AR link gains a **Bring it to life** option: instead of a froz----<a id="sec-511"></a>+<a id="sec-531"></a>> **Source:** `docs/tutorials/generate-3d-api.md` · [↑ table of contents](#table-of-contents)@@ -118438,6 +124534,10 @@ Everything the [Forge](/forge) does in the browser is available as a plain HTTP**Prerequisites:** comfortable with `fetch` or `curl`. Examples use Node.js 18+ (built-in `fetch`), but any language with an HTTP client works the same way.+[](/forge)++*The Forge accepts a sentence or an image and returns a textured GLB.*+---## The flow in one picture@@ -118651,7 +124751,7 @@ If you've never made an x402 call, start with [Build a paid x402 endpoint](/tuto----<a id="sec-512"></a>+<a id="sec-532"></a>> **Source:** `docs/tutorials/getting-started.md` · [↑ table of contents](#table-of-contents)@@ -118663,6 +124763,10 @@ This is the easiest entry point on the platform. Everything you do here is edita**Prerequisites:** a modern browser (Chrome, Firefox, or Safari) and an email address. No coding experience, no 3D files, and no crypto required. You'll sign in once, partway through, to save your work.+[](/start)++*The getting-started checklist is the shortest path from account to first agent.*+---## What you're building@@ -118836,7 +124940,7 @@ Everything is editable forever — swap the body, rewrite the prompt, add capabi----<a id="sec-513"></a>+<a id="sec-533"></a>> **Source:** `docs/tutorials/greeting-and-first-speech.md` · [↑ table of contents](#table-of-contents)@@ -118857,6 +124961,10 @@ This tutorial covers the greeting flow end to end: waiting for the `agent:ready`**Prerequisites:** A page with the embed working from [Embed in 30 seconds](/tutorials/embed-in-30-seconds). Your agent should already be saved with a brain configured.+[](/voice)++*Voice Lab previews every voice the speech and lipsync stack can drive.*+---## Step 1 — The minimal greeting@@ -119184,7 +125292,7 @@ A working greeting moves the embed from "decoration" to "interaction", which is----<a id="sec-514"></a>+<a id="sec-534"></a>> **Source:** `docs/tutorials/image-to-3d.md` · [↑ table of contents](#table-of-contents)@@ -119196,6 +125304,10 @@ Have a real object you want in 3D? Photograph it from a few angles, drop the pho**Prerequisites:** none. A phone camera is plenty.+[](/image-to-3d)++*Drop a photo here and the same pipeline returns a mesh instead of a render.*+---## Step 1 — Take good photos@@ -119287,7 +125399,7 @@ Everything you generate is kept in **Your creations** at the bottom of the page,----<a id="sec-515"></a>+<a id="sec-535"></a>> **Source:** `docs/tutorials/import-avatar-url.md` · [↑ table of contents](#table-of-contents)@@ -119299,6 +125411,10 @@ This tutorial walks the URL-import path end to end. It's the sibling of [Upload**Prerequisites:** a three.ws account (the importer redirects you to sign in if you're not), and a live, publicly reachable URL to a glTF 2.0 `.glb` file. No command line, no Blender, no local tooling required — the whole flow runs in the browser.+[](/gallery)++*Every avatar in the gallery is a real GLB with a public render URL.*+---## What you're building@@ -119457,7 +125573,7 @@ The URL path and the file-upload path converge on the same avatar record and the----<a id="sec-516"></a>+<a id="sec-536"></a>> **Source:** `docs/tutorials/js-api-events.md` · [↑ table of contents](#table-of-contents)@@ -119923,7 +126039,7 @@ The `whenReady`, awaited-`ask()`, and try/catch patterns are small but they remo----<a id="sec-517"></a>+<a id="sec-537"></a>> **Source:** `docs/tutorials/mcp-server-for-your-agent.md` · [↑ table of contents](#table-of-contents)@@ -120578,7 +126694,7 @@ Things that look right but bite you:----<a id="sec-518"></a>+<a id="sec-538"></a>> **Source:** `docs/tutorials/mine-vanity-address.md` · [↑ table of contents](#table-of-contents)@@ -120860,7 +126976,7 @@ The protocol itself is fully specified in [docs/PROTOCOL-vanity.md](#sec-006), a----<a id="sec-519"></a>+<a id="sec-539"></a>> **Source:** `docs/tutorials/mint-pumpfun-token.md` · [↑ table of contents](#table-of-contents)@@ -121221,7 +127337,7 @@ If you have a lawyer, talk to them before launching. If you don't, default to th----<a id="sec-520"></a>+<a id="sec-540"></a>> **Source:** `docs/tutorials/monetize-mcp-server.md` · [↑ table of contents](#table-of-contents)@@ -121537,7 +127653,7 @@ That connector can search the bazaar, read your challenge without paying (`inspe----<a id="sec-521"></a>+<a id="sec-541"></a>> **Source:** `docs/tutorials/multi-agent-coordination.md` · [↑ table of contents](#table-of-contents)@@ -121942,7 +128058,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-338).+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-349).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.@@ -122097,7 +128213,7 @@ async function safeHandoff(targetEl, brief, fallbackEl, originalQuestion) {----<a id="sec-522"></a>+<a id="sec-542"></a>> **Source:** `docs/tutorials/nvidia-3d-free.md` · [↑ table of contents](#table-of-contents)@@ -122219,7 +128335,7 @@ It talks **directly** to a TRELLIS NIM and returns the GLB **synchronously** in----<a id="sec-523"></a>+<a id="sec-543"></a>> **Source:** `docs/tutorials/nvidia-nim-self-host.md` · [↑ table of contents](#table-of-contents)@@ -122402,7 +128518,7 @@ The proxy normalizes every documented artifact shape (inline `base64`, a bare st----<a id="sec-524"></a>+<a id="sec-544"></a>> **Source:** `docs/tutorials/paid-x402-endpoint.md` · [↑ table of contents](#table-of-contents)@@ -123094,7 +129210,7 @@ Both work. Choose based on whether your endpoint is part of an agent platform yo----<a id="sec-525"></a>+<a id="sec-545"></a>> **Source:** `docs/tutorials/pay-for-x402-service.md` · [↑ table of contents](#table-of-contents)@@ -123370,7 +129486,7 @@ package family is listed under [x402 → Open-source packages](/x402#open-source----<a id="sec-526"></a>+<a id="sec-546"></a>> **Source:** `docs/tutorials/personal-ai-site.md` · [↑ table of contents](#table-of-contents)@@ -123925,7 +130041,7 @@ The technical investment is one HTML file, a GLB avatar, and a system prompt. Th----<a id="sec-527"></a>+<a id="sec-547"></a>> **Source:** `docs/tutorials/place-agent-irl.md` · [↑ table of contents](#table-of-contents)@@ -124084,6 +130200,8 @@ When you're standing near a pinned agent (yours or someone else's), it appears iTap an agent's label or model to open its **inspect card**:+- **Talk** to it. Hold the mic and speak, or type. The agent answers in its own persona, out loud, and its mouth moves with the words. Press the mic while it speaks to interrupt it.+- **View in AR** to stand it on your real floor: Quick Look on iPhone, a floor-anchored WebXR session on Android with ARCore, the AR launcher everywhere else. This works on any agent you discover, not only your own.- Its bio, on-chain reputation tier, and any paid services it offers- **Pay via x402** to use a service it sells- **Leave a message** that lands in the owner's IRL feed@@ -124168,6 +130286,7 @@ This is fundamentally different from viewing a single model in AR. If you only n### See also- [IRL — open the product](/irl) — place your agent now+- [Run an IRL street demo](/docs/irl/street-demo): visit links, printable signs, and what strangers see when they walk up- [How location works on IRL](/irl-privacy) — the full privacy model, sensor-by-sensor- [Tutorial: Place your 3D model in AR](/docs/tutorials/view-in-ar) — the single-model viewer (Quick Look / Scene Viewer / WebXR)- [AR & WebXR reference](/docs/ar) — the underlying AR methods and programmatic API@@ -124175,7 +130294,7 @@ This is fundamentally different from viewing a single model in AR. If you only n----<a id="sec-528"></a>+<a id="sec-548"></a>> **Source:** `docs/tutorials/prompts-for-3d.md` · [↑ table of contents](#table-of-contents)@@ -124197,6 +130316,10 @@ a sci-fi combat helmet, brushed metalIf you haven't generated your first model yet, do the five-minute [text-to-3D tutorial](/tutorials/text-to-3d) first, then come back here for ideas.+[](/forge)++*The Forge accepts a sentence or an image and returns a textured GLB.*+---## The four rules@@ -124311,7 +130434,7 @@ The tiers are explained in detail in [the text-to-3D tutorial](/tutorials/text-t----<a id="sec-529"></a>+<a id="sec-549"></a>> **Source:** `docs/tutorials/read-the-trading-fleet.md` · [↑ table of contents](#table-of-contents)@@ -124538,7 +130661,7 @@ funds.----<a id="sec-530"></a>+<a id="sec-550"></a>> **Source:** `docs/tutorials/register-onchain.md` · [↑ table of contents](#table-of-contents)@@ -124887,7 +131010,7 @@ Your agent's URL will keep working as long as Base exists and IPFS gateways serv----<a id="sec-531"></a>+<a id="sec-551"></a>> **Source:** `docs/tutorials/render-avatar-images.md` · [↑ table of contents](#table-of-contents)@@ -125348,7 +131471,7 @@ Sometimes an image is not enough and you want the actual interactive model. LoadTwo hosts, two answers (measured 2026-08-01):- **`https://three.ws/...`**, which is where the built-in library avatars live (`/avatars/selfie-girl.glb` and friends), answers every origin with `access-control-allow-origin: *`. Load these directly. No proxy needed.-- **`https://pub-*.r2.dev/...`**, the media bucket's own host, behind every avatar you or your users generated, answers only origins on its allowlist (`three.ws`, `*.vercel.app`, `localhost:3000`; re-measured 2026-09-04). From `https://your-site.com`, from Jupyter, or from a Vite server on `localhost:5173`, a direct load fails with a CORS error and an empty canvas. That is the URL `/api/avatar/render` redirects to and the URL the avatar APIs return for user avatars.+- **`https://pub-*.r2.dev/...`**, the media bucket's own host, behind every avatar you or your users generated, answers only origins on its allowlist (`three.ws`, `*.vercel.app`, `localhost:3000`; re-measured 2026-09-09). From `https://your-site.com`, from Jupyter, or from a Vite server on `localhost:5173`, a direct load fails with a CORS error and an empty canvas. That is the URL `/api/avatar/render` redirects to and the URL the avatar APIs return for user avatars.- **`https://three.ws/cdn/<key>`** serves those same bucket objects first-party, with `access-control-allow-origin: *` on every origin. If you have the object key (everything after the bucket host), this loads directly and needs nothing below.`GET /api/glb?src=<url>` exists for the second case. It streams any public GLB back with `access-control-allow-origin: *`, and it is harmless on the first, so if you cannot tell which host a URL points at, use it. The example below proxies a `three.ws` URL that would also load directly, because it is the pattern that keeps working when you swap in a generated avatar:@@ -125433,7 +131556,7 @@ If you want a talking, animated agent rather than a viewer, that is the `<agent-----<a id="sec-532"></a>+<a id="sec-552"></a>> **Source:** `docs/tutorials/self-host-agent-backend.md` · [↑ table of contents](#table-of-contents)@@ -125665,7 +131788,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-141), 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-145), 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:@@ -126000,7 +132123,7 @@ A self-hosted instance with light traffic runs at $20–50/month all-in. The dom----<a id="sec-533"></a>+<a id="sec-553"></a>> **Source:** `docs/tutorials/selfie-to-avatar.md` · [↑ table of contents](#table-of-contents)@@ -126039,7 +132162,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-118).)+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-121).)---@@ -126201,7 +132324,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-118) 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-121) 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.---@@ -126250,13 +132373,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-118) — the full reference: every creation path, rig requirements, and accessories.+- [Avatar Creation](#sec-121) — 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-534"></a>+<a id="sec-554"></a>> **Source:** `docs/tutorials/sell-a-skill-with-a-trial.md` · [↑ table of contents](#table-of-contents)@@ -126270,6 +132393,10 @@ The interesting part is not the listing. It is the middle. A free trial that nev**Time:** about 15 minutes.+[](/skills)++*Skills are sold, trialled and installed from this catalogue.*+---## What you're building@@ -126398,7 +132525,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-154) 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-158) 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.---@@ -126469,7 +132596,7 @@ A healthy funnel shows a mix of `trial` rows with counts ticking down and `confi----<a id="sec-535"></a>+<a id="sec-555"></a>> **Source:** `docs/tutorials/share-your-agent.md` · [↑ table of contents](#table-of-contents)@@ -126488,6 +132615,10 @@ This tutorial covers the full sharing surface: finding the public URL, generatin**Prerequisites:** A saved agent on three.ws. The agent should have a body and a name — covered in [Embed in 30 seconds](/tutorials/embed-in-30-seconds) and [Pick and swap an avatar in Studio](/tutorials/swap-avatar-in-studio).+[](/marketplace)++*Published agents land here, forkable by anyone.*+---## Step 1 — Find your agent's public URL@@ -126833,7 +132964,7 @@ The agent's URL is the durable handle. Embed it, link it, print it. The agent sh----<a id="sec-536"></a>+<a id="sec-556"></a>> **Source:** `docs/tutorials/ship-an-avatar-manifest.md` · [↑ table of contents](#table-of-contents)@@ -126854,7 +132985,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-117) is the exhaustive flag-by-flag contract. This tutorial is the guided path through it.+- Optional: the [Avatar CLI reference](#sec-120) is the exhaustive flag-by-flag contract. This tutorial is the guided path through it.Every command below is real and runs as written.@@ -127142,13 +133273,13 @@ A JSON file that names an avatar, pins its mesh by content rather than by locati**Next:**-- The [Avatar CLI reference](#sec-117) documents every flag, exit code, and `--json` shape.-- The [web component reference](#sec-578) covers everything `<agent-3d>` can do beyond rendering a body: voice, an LLM brain, memory, and skills.+- The [Avatar CLI reference](#sec-120) documents every flag, exit code, and `--json` shape.+- The [web component reference](#sec-599) 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-537"></a>+<a id="sec-557"></a>> **Source:** `docs/tutorials/shopify-shopping-assistant.md` · [↑ table of contents](#table-of-contents)@@ -127266,7 +133397,7 @@ The [wire format](/docs/concierge) for the answer endpoint is documented, so you----<a id="sec-538"></a>+<a id="sec-558"></a>> **Source:** `docs/tutorials/shopify-store-guide-advanced.md` · [↑ table of contents](#table-of-contents)@@ -127576,7 +133707,7 @@ The clip URLs inside the manifest resolve **relative to the manifest**, so a sel----<a id="sec-539"></a>+<a id="sec-559"></a>> **Source:** `docs/tutorials/shopify-store-guide.md` · [↑ table of contents](#table-of-contents)@@ -127665,7 +133796,7 @@ It's powered by the open-source [`@three-ws/tour`](https://www.npmjs.com/package----<a id="sec-540"></a>+<a id="sec-560"></a>> **Source:** `docs/tutorials/sign-with-your-avatar.md` · [↑ table of contents](#table-of-contents)@@ -127879,9 +134010,9 @@ None of it replaces a human interpreter. It makes an avatar legible to signers i**See also:**-- [docs/sign-language.md](#sec-440): the full reference: vocabulary, developer APIs, and how the signing engine works-- [docs/tutorials/animate-your-avatar.md](#sec-490): the clip library, retargeting, and animated GLB export in depth-- [docs/web-component.md](#sec-578): every `<agent-3d>` attribute, including `sign-language`+- [docs/sign-language.md](#sec-458): the full reference: vocabulary, developer APIs, and how the signing engine works+- [docs/tutorials/animate-your-avatar.md](#sec-510): the clip library, retargeting, and animated GLB export in depth+- [docs/web-component.md](#sec-599): 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@@ -127889,7 +134020,7 @@ Primary call to action: open **[/sign-language](/sign-language)** and sign your----<a id="sec-541"></a>+<a id="sec-561"></a>> **Source:** `docs/tutorials/skill-with-database-auth.md` · [↑ table of contents](#table-of-contents)@@ -128627,7 +134758,7 @@ Before this skill faces a real visitor:----<a id="sec-542"></a>+<a id="sec-562"></a>> **Source:** `docs/tutorials/solana-agent-reputation.md` · [↑ table of contents](#table-of-contents)@@ -128819,7 +134950,7 @@ A read costs nothing and asks no one's permission — which is exactly what lets----<a id="sec-543"></a>+<a id="sec-563"></a>> **Source:** `docs/tutorials/sperax-tour.md` · [↑ table of contents](#table-of-contents)@@ -128990,7 +135121,7 @@ This is covered by an automated test — [`tour-sdk/test/director.test.mjs`](htt----<a id="sec-544"></a>+<a id="sec-564"></a>> **Source:** `docs/tutorials/swap-avatar-in-studio.md` · [↑ table of contents](#table-of-contents)@@ -129008,6 +135139,10 @@ This tutorial covers both halves of that. You swap the body in the agent editor'**Prerequisites:** A saved agent on three.ws. If you've worked through [Embed in 30 seconds](/tutorials/embed-in-30-seconds), you already have one.+[](/avatar-studio)++*Avatar Studio: the rig on the left, every appearance control on the right.*+---## Step 1: Know which surface does what@@ -129184,7 +135319,7 @@ The key insight is the snippet's stability. Once embedded, your customers' pages----<a id="sec-545"></a>+<a id="sec-565"></a>> **Source:** `docs/tutorials/text-to-3d.md` · [↑ table of contents](#table-of-contents)@@ -129196,6 +135331,10 @@ Type a sentence, get a downloadable 3D model. That's the whole tutorial. By the**Prerequisites:** none. No account, no wallet, no code. Just a browser.+[](/create/prompt)++*Describe it to 3D: the prompt field and the tier picker are the whole interface.*+---## Step 1 — Open the Forge@@ -129312,7 +135451,7 @@ This is normal — prompt, generate, adjust, repeat is the workflow, not a failu----<a id="sec-546"></a>+<a id="sec-566"></a>> **Source:** `docs/tutorials/trigger-from-page-events.md` · [↑ table of contents](#table-of-contents)@@ -129816,7 +135955,7 @@ The pattern under all of these is the same: every recipe starts with `whenReady(----<a id="sec-547"></a>+<a id="sec-567"></a>> **Source:** `docs/tutorials/upload-custom-glb.md` · [↑ table of contents](#table-of-contents)@@ -129834,6 +135973,10 @@ This tutorial covers the whole pipeline. Where compatible GLBs come from, what m**Prerequisites:** Comfort with a file manager and the command line. Some familiarity with Blender helps for the optional baking step but is not required. You should have an existing agent in [three.ws/my-agents](https://three.ws/my-agents) to swap a body into.+[](/gallery)++*Every avatar in the gallery is a real GLB with a public render URL.*+---## Step 1: Understand what the runtime expects@@ -130244,7 +136387,7 @@ Once the body is on the platform, the embed snippet doesn't change. The same `<a----<a id="sec-548"></a>+<a id="sec-568"></a>> **Source:** `docs/tutorials/view-in-ar.md` · [↑ table of contents](#table-of-contents)@@ -130261,6 +136404,10 @@ This tutorial walks you through every step of seeing a three.ws model in augment**Prerequisites:** A smartphone (iPhone or Android). For the embedding section, a basic HTML file you can edit.+[](/walk)++*Walk on a phone: the same rig, the same clips, thumb-sized controls.*+---## Step 1 — Get a 3D model@@ -130433,7 +136580,7 @@ AR surface detection needs a moment to work. Move the phone slowly over the targ----<a id="sec-549"></a>+<a id="sec-569"></a>> **Source:** `docs/tutorials/voice-and-lipsync.md` · [↑ table of contents](#table-of-contents)@@ -130445,6 +136592,10 @@ Along the way you'll understand why three.ws extracts visemes from the audio its**Prerequisites:** a three.ws account with at least one agent ([create one](/create)), a browser with Web Audio + WebGL (any modern desktop browser), and a microphone if you want to clone a voice or try the mic lab. No code is required for the labs; the live-agent step assumes light JavaScript familiarity.+[](/voice)++*Voice Lab previews every voice the speech and lipsync stack can drive.*+---## What you're building@@ -130574,7 +136725,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-576)).+**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-596)).> 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.@@ -130684,7 +136835,7 @@ The leverage is that the avatar drives its mouth from the *audio it actually pla----<a id="sec-550"></a>+<a id="sec-570"></a>> **Source:** `docs/tutorials/walk-companion.md` · [↑ table of contents](#table-of-contents)@@ -130696,6 +136847,14 @@ Along the way you'll see what the [/walk](/walk) product offers, live demos acro**Prerequisites:** a website you can edit and a WebGL-capable browser. The iframe path needs no tooling at all; the npm path assumes light JavaScript familiarity and that you already bundle [Three.js](https://threejs.org) (>= 0.150).+[](/walk)++*Walk on a phone: the same rig, the same clips, thumb-sized controls.*++[](/walk)++*Captured live: the default rig running the canonical walk clip.*+---## What you're building@@ -130760,6 +136919,7 @@ The embed reads its world and controls from the URL. The verified params:| `controls` | `joystick` `keyboard` `none` | How (or whether) the visitor steers || `orbit` | `true` `false` | Allow drag-to-orbit the camera || `avatar` | a roster id or your avatar id | Which avatar walks |+| `zoom` | `0.5` to `2` | Scales how far the chase camera sits back (`1` if omitted). Below 1 pulls in, which is what a small window wants: the [Pocket Console](https://three.ws/pocket) runs the embed at `0.74` so the avatar fills a 4:3 handheld screen instead of framing a lot of empty sky. |A live, drivable demo on a beach:@@ -131037,7 +137197,7 @@ The leverage is composability: the same engine renders the corner mascot, the fu----<a id="sec-551"></a>+<a id="sec-571"></a>> **Source:** `docs/tutorials/wallet-sign-in.md` · [↑ table of contents](#table-of-contents)@@ -131321,7 +137481,7 @@ A wallet sign-in that works from any origin that can reach the API, survives the----<a id="sec-552"></a>+<a id="sec-572"></a>> **Source:** `docs/tutorials/web-component-end-to-end.md` · [↑ table of contents](#table-of-contents)@@ -131414,7 +137574,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-505) 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-525) covers the iframe path and the no-code platforms in depth.)---@@ -131920,12 +138080,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-505), the no-framework paths (Webflow, WordPress, Squarespace) for completeness+- [Embed a three.ws agent on your website](#sec-525), 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-553"></a>+<a id="sec-573"></a>> **Source:** `docs/tutorials/write-a-guard.md` · [↑ table of contents](#table-of-contents)@@ -132231,7 +138391,7 @@ Your guard is done when all of these are true:----<a id="sec-554"></a>+<a id="sec-574"></a>> **Source:** `docs/tutorials/x402-server-sdk.md` · [↑ table of contents](#table-of-contents)@@ -132444,7 +138604,7 @@ const res = await pay('https://your.api/v1/embed', { method: 'POST', body });----<a id="sec-555"></a>+<a id="sec-575"></a>> **Source:** `docs/ui-juice.md` · [↑ table of contents](#table-of-contents)@@ -132620,7 +138780,7 @@ should reach for these primitives rather than re-rolling RAF loops.----<a id="sec-556"></a>+<a id="sec-576"></a>> **Source:** `docs/upstream/home-assistant-js-websocket-resubscribe-rejection.md` · [↑ table of contents](#table-of-contents)@@ -132755,7 +138915,7 @@ resume.----<a id="sec-557"></a>+<a id="sec-577"></a>> **Source:** `docs/user-wallet.md` · [↑ table of contents](#table-of-contents)@@ -132794,7 +138954,7 @@ 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-187) 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-191) 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-074)), which a freeze never blocks.@@ -132804,7 +138964,7 @@ Funds flow one way through the platform's plumbing: master wallet to agent walle- 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-112) for how sessions and CSRF tokens work in general.+See [authentication.md](#sec-115) 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`:@@ -132974,7 +139134,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-572)) 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-592)) 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@@ -133035,14 +139195,14 @@ Honest limits, stated plainly: this is a **custodial** wallet, so the platform c## Related- [agent-wallets.md](#sec-074) for the per-agent wallet this one funds, and its spend policy-- [custody.md](#sec-187) for limits, freeze, proof of custody, and recovery on the agent side-- [vaults.md](#sec-572) for what a funded agent wallet can then back-- [authentication.md](#sec-112) for sessions, CSRF tokens, and why API keys do not apply here-- [money-map.md](#sec-335) for how funds move across the whole platform+- [custody.md](#sec-191) for limits, freeze, proof of custody, and recovery on the agent side+- [vaults.md](#sec-592) for what a funded agent wallet can then back+- [authentication.md](#sec-115) for sessions, CSRF tokens, and why API keys do not apply here+- [money-map.md](#sec-346) for how funds move across the whole platform----<a id="sec-558"></a>+<a id="sec-578"></a>> **Source:** `docs/ux-flows/01-onboarding-creation.md` · [↑ table of contents](#table-of-contents)@@ -133314,7 +139474,7 @@ Honest limits, stated plainly: this is a **custodial** wallet, so the platform c----<a id="sec-559"></a>+<a id="sec-579"></a>> **Source:** `docs/ux-flows/02-forge-text-to-3d.md` · [↑ table of contents](#table-of-contents)@@ -133496,7 +139656,7 @@ Routing facts (from `vercel.json`):----<a id="sec-560"></a>+<a id="sec-580"></a>> **Source:** `docs/ux-flows/03-3d-editing-viewer.md` · [↑ table of contents](#table-of-contents)@@ -133704,7 +139864,7 @@ Routing summary (from `vite.config.js`):----<a id="sec-561"></a>+<a id="sec-581"></a>> **Source:** `docs/ux-flows/04-embed-widget-studio.md` · [↑ table of contents](#table-of-contents)@@ -133877,7 +140037,7 @@ Routing recap (from `vercel.json`):----<a id="sec-562"></a>+<a id="sec-582"></a>> **Source:** `docs/ux-flows/05-discovery-social.md` · [↑ table of contents](#table-of-contents)@@ -134149,7 +140309,7 @@ Routing recap (from `vercel.json`):----<a id="sec-563"></a>+<a id="sec-583"></a>> **Source:** `docs/ux-flows/06-marketplace-skills.md` · [↑ table of contents](#table-of-contents)@@ -134367,7 +140527,7 @@ Routing facts confirmed in `vercel.json` (line numbers shift too often to pin; g----<a id="sec-564"></a>+<a id="sec-584"></a>> **Source:** `docs/ux-flows/07-crypto-trading-analytics.md` · [↑ table of contents](#table-of-contents)@@ -134637,13 +140797,14 @@ coin-intel, pump-visualizer and pump-live: adding a coin on any surface shows up3. System: SSE `/api/agents/pumpfun-feed?...` (withCredentials) → `hello`, replay buffer (~30 events dimmed), then `evt` events (mint/trade/graduation/claim) stream live; agent animates + optionally narrates per configured emotion/TTS map.4. System: first-time fee-claims sidebar refreshes from `GET /api/pump/first-claims?limit=50&sinceMinutes=1440`.5. (optional) Filters: asset, mint search, event kind, min tier (notable+/influencer+/mega), MC range, min buy SOL, whale threshold.- 6. (optional) Config modal: map emotions→animations and actions→TTS templates (stored in localStorage); narration/announce-mints/mood toggles.- 7. (optional) Share/copy filter-encoded link.+ 6. (optional) Avatar picker: five tabs. Defaults ships with the page; Community reads `GET /api/avatars/public`; My Agents reads `GET /api/avatars` behind an `/api/auth/me` check; Recent and Favorites are this browser's own lists (`localStorage` keys `pumpfun-avatar-recents`, capped at 24, and `pumpfun-avatar-favorites`, written by the star on each card).+ 7. (optional) Config modal: map emotions→animations and actions→TTS templates (stored in localStorage); narration/announce-mints/mood toggles.+ 8. (optional) Share/copy filter-encoded link, or follow the "Launch a coin" link in the header to `/launch`.- **Decision points / branches:** public feed vs agent-bound (enriches via `?_handler=metadata`); event-kind/tier/MC/whale filters; narration + emotion config; provisioned wallet vs none.- **External calls / dependencies:** SSE `/api/agents/pumpfun-feed` (upstream Helius webhooks), `/api/agents`, `/api/agents/{id}/solana` (GET+POST), `/api/pump/first-claims`, `/api/agents/{id}/pumpfun/metadata`, avatars endpoints; model-viewer CDN.- **Success state:** live launch/trade/graduation/claim feed with reacting, narrating 3D agent; first-claims sidebar; accurate wallet info.-- **Empty / error states:** "Waiting for events…"; quiet/no-events feed dot; "No Solana wallet on this agent" + provision; upstream error soft-degrades to empty `{items:[]}`; reconnect cycle.-- **Step count:** 1 required (arrive → live feed) + ~6 optional (agent bind, filters, emotion config, share). Live monitor + reactive agent (+ optional agent-management).+- **Empty / error states:** feed panel renders one of four states from `#feed-status`: "Waiting for the next launch" before the first event, "No events match your filters" with a Clear filters button when every card is hidden, "Feed disconnected" with a Reconnect button after 3 failed SSE attempts (8s open timeout each), and nothing at all once a card is visible. First-claims panel: skeleton rows while loading, "None in this window.", or an alert naming the failure with a Try again button. Avatar picker: Recent and Favorites each have their own empty state with a jump to a populated tab; "My Agents" shows a sign-in prompt (gated on `GET /api/auth/me`, so a signed-out visitor never takes a 401); community/mine load failures show the error plus Retry. Status pill: connecting / reconnecting / live / live · quiet / offline · retry (click to reconnect). Avatar load error surfaces as a toast and the previous avatar stays.+- **Step count:** 1 required (arrive → live feed) + ~7 optional (agent bind, filters, avatar pick, emotion config, share, launch). Live monitor + reactive agent (+ optional agent-management).---@@ -134758,7 +140919,7 @@ coin-intel, pump-visualizer and pump-live: adding a coin on any surface shows up----<a id="sec-565"></a>+<a id="sec-585"></a>> **Source:** `docs/ux-flows/08-coin-launch-wallets.md` · [↑ table of contents](#table-of-contents)@@ -134920,17 +141081,17 @@ real Solana/EVM RPC, pump.fun, and x402 — no mocks.---### Agent Wallet x402 Pay (3D demo) — `/play/agent-wallet`-- **Source:** `pages/play/agent-wallet.html` → `src/play-agent-wallet.js`. Uses `src/game/avatar-rig.js` + `src/game/play-handoff.js`. Bridge: hosted `api/agent-wallet-bridge` (prod) or local `scripts/agent-wallet-x402-bridge.mjs` on `127.0.0.1:4402` (dev).+- **Source:** `pages/play/agent-wallet.html` → `src/play-agent-wallet.js`. Uses `src/game/avatar-rig.js` + `src/game/play-handoff.js`. Bridge: hosted `api/agent-wallet-bridge` (prod) or local `scripts/agent-wallet-x402-bridge.mjs` on `127.0.0.1:4402` (dev). A dev machine only *prefers* the local bridge: the first unreachable status call promotes the page to the hosted bridge, so `npm run dev` shows the live wallet instead of a permanent "bridge offline".- **Entry point:** `#stage3d` 3D scene (avatar + kiosk + stage board) + side panel with topic chips, endpoint card, and a Pay button.-- **Prerequisites / gates:** Bridge must be **online** (status poll). On the **hosted** bridge a real spend requires a signed-in session (402→401 surfaces "Sign in to pay"); rate-limited (429) handled. Agent wallet must hold USDC.+- **Prerequisites / gates:** Bridge must be **online** (status poll). On the **hosted** bridge a real spend requires a signed-in session (402→401 surfaces "Sign in to pay"); rate-limited (429) handled. The agent wallet must hold at least the quoted amount in USDC; below that the Pay button is disabled and reads "Wallet needs $0.01 USDC to pay" beside the low-balance banner, rather than offering a payment that can only fail.- **Steps (N):**1. Boot loads the saved `/play` avatar (`CC_AVATAR_KEY` / `?avatar=`), builds the 3D rig, and calls `refreshStatus()` → bridge `?status=1` for wallet address/mode + USD balance. Status repolls every 30s.2. `loadQuote()` → bridge `?quote=1&endpoint=…&method=POST&body={topic}` → fills endpoint name, price, pay-to, tags.- 3. (optional) User selects a topic chip (BTC/ETH/SOL) — re-quotes implicitly on next pay.+ 3. (optional) User selects a topic chip (BTC/ETH/SOL), which re-quotes immediately: the 402 challenge is issued per request, so price and pay-to belong to the topic being bought.4. User clicks **Send avatar to pay — $0.01 USDC**. Avatar walks to the kiosk (stage `walk`); pay ring pulses.5. `POST` bridge `?pay=1` (SSE, `accept: text/event-stream`) streams stages: `challenge` (402) → `signing` (agent wallet signs the SPL USDC transfer) → `signed`/`submitting` (X-PAYMENT submitted, facilitator settles) → `done` (settled on Solana mainnet). Board, kiosk, and side-panel stepper animate in lockstep.6. On `done` → receipt: amount, payer (agent wallet) → payTo (endpoint), Solscan tx link, and the purchased crypto-intel payload (signal/headline/rationale). Avatar plays a celebrate emote, then walks home. Status refreshes; session total accrues.-- **Decision points / branches:** local dev bridge vs hosted prod bridge (different URL shapes + auth model); `?bridge=`/`?endpoint=` overrides; 401 needs-auth vs 429 rate-limit vs generic failure; bridge online/offline/connecting.+- **Decision points / branches:** local dev bridge vs hosted prod bridge (different URL shapes + auth model, with a one-shot promotion from local to hosted when the local one is unreachable); `?bridge=`/`?endpoint=` overrides, which are honored verbatim and never promoted; sponsored vs self-pay Solana accept (the bridge signs as its own fee payer when the endpoint advertises no `extra.feePayer`); 401 needs-auth vs 429 rate-limit vs generic failure; bridge online/offline/connecting.- **External calls / dependencies:** bridge `status`/`quote`/`pay` (`/api/agent-wallet-bridge` or local `:4402`); the paid endpoint `https://three.ws/api/x402/crypto-intel` (the hosted bridge calls it through the shared upstream fetch: the 402 probe is bounded and retried on a dropped connection, while the re-send that carries the signed payment is a single attempt with a timeout only, because a retry could double-spend); Solana mainnet settlement via the x402 facilitator; Solscan (tx link). External payment is **real** ($0.01 USDC leaves the wallet).- **Success state:** "✓ $0.01 USDC settled on Solana" board + receipt card with tx link and purchased intel; avatar celebrates.- **Empty / error states:** "Bridge offline" banner (dev hint to run the bridge) with Retry; low-balance banner; "Sign in to pay" (needs-auth); rate-limit message; "Payment failed — no funds moved" with the stepper marking the failed stage red.@@ -135035,7 +141196,7 @@ real Solana/EVM RPC, pump.fun, and x402 — no mocks.----<a id="sec-566"></a>+<a id="sec-586"></a>> **Source:** `docs/ux-flows/09-x402-agent-commerce.md` · [↑ table of contents](#table-of-contents)@@ -135375,13 +141536,13 @@ choreographed two-agent narrative driven by Server-Sent Events.- **Server-payer vs user-payer:** the "agent economy" narratives (`/agent-exchange`, `/agent-trade`, `/agent-economy`, `/demo`, `/live`) pay from **server-held agent wallets** and stream the choreography over SSE — the user only triggers/selects, then watches. The "showcase" apps (`/shopper`, `/fact-checker`, `/tutor`, `/bazaar`, `/arbitrage`, `/ibm`) make the **user** pay via the `/x402.js` modal.- **Auto-play demos:** `/agent-exchange`, `/agent-trade`, `/agent-economy`, `/demo` need one user click to start, then auto-play. `/live` adds an auth gate for real settlement. `/play/arena` is fully autonomous (agents trade themselves; user only watches/moves/inspects) and uses **no x402** — real pre-funded Solana trades.- **Forever** is the only **non-x402** payment in the cluster: native Bitcoin (or Lightning) to an OrdinalsBot charge address, inscribing a real Taproot text inscription on Bitcoin mainnet.-- **Adjacent economy surfaces (2026-08-01, not yet traced as full sections):** `/economy-lab` (Runway Lab, a live digital twin of the x402 payment rail; backend `api/x402/runway-lab.js`), `/pay-simulator` (Spend Policy Simulator: dry-run an agent spending policy against real x402 prices), `/flow` (Money Flow Map, see `docs/money-flow-map.md`), `/play/solver` (see `docs/economy-solver.md`), and `/conversions`.+- **Adjacent economy surfaces (2026-08-01, not yet traced as full sections):** `/economy-lab` (Runway Lab, a live digital twin of the x402 payment rail; backend `api/x402/runway-lab.js`), `/pay/simulator` (Spend Policy Simulator: dry-run an agent spending policy against real x402 prices), `/flow` (Money Flow Map, see `docs/money-flow-map.md`), `/play/solver` (see `docs/economy-solver.md`), and `/conversions`.- **Inline handlers are gone:** every HTML response in this cluster ships a CSP whose `script-src` lists SHA-256 hashes of the inline scripts in the bytes actually sent, so no page here may carry an `onclick=`/`onerror=` attribute (not even inside a template literal). The card markup these flows render declares intent with `data-fallback`, `data-action="reload"` or `data-stop-propagation` and `public/inline-behaviors.js` delegates it; `scripts/audit-inline-handlers.mjs` fails the build if one comes back.- **Source coverage:** all 19 routes located and traced from real source. `/tutor` resolves to `public/tutor.html` + `public/tutor.js` (served statically; no explicit vite map entry needed). No source was missing.----<a id="sec-567"></a>+<a id="sec-587"></a>> **Source:** `docs/ux-flows/10-chat-brain-labs.md` · [↑ table of contents](#table-of-contents)@@ -135624,7 +141785,7 @@ modules. Routes resolved via `vercel.json` rewrites.----<a id="sec-568"></a>+<a id="sec-588"></a>> **Source:** `docs/ux-flows/11-account-dashboard.md` · [↑ table of contents](#table-of-contents)@@ -135830,7 +141991,7 @@ Shared auth concepts:----<a id="sec-569"></a>+<a id="sec-589"></a>> **Source:** `docs/ux-flows/12-home-and-content.md` · [↑ table of contents](#table-of-contents)@@ -136072,7 +142233,7 @@ All `/.well-known/*` and `/openapi.json` / `/sitemap.xml` responses are JSON/XML----<a id="sec-570"></a>+<a id="sec-590"></a>> **Source:** `docs/validation.md` · [↑ table of contents](#table-of-contents)@@ -136275,7 +142436,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-207) 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-212) for the platform's own automatic attestation flow.The minimum check suite for a `pass` verdict includes:@@ -136451,7 +142612,7 @@ The toggle's CSS class reflects the highest severity: `level-0` (errors), `level----<a id="sec-571"></a>+<a id="sec-591"></a>> **Source:** `docs/vanity.md` · [↑ table of contents](#table-of-contents)@@ -136459,7 +142620,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-624) rail and the+no account, and no SOL. Pay per call in USDC over the [x402](#sec-645) rail and theserver grinds (or delivers from stock) a brand-new keypair that matches.| Endpoint | What it is | Chars | Price | Pick it when |@@ -136477,7 +142638,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-392) draws from the+address from the catalog." [Pump Launcher](#sec-407) draws from thesame warehouse for instant vanity mint addresses.## Which agent uses this, and why us@@ -136679,7 +142840,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-392).+atomicity, no separate purchase step. See [pump-launcher.md](#sec-407).---@@ -136694,20 +142855,20 @@ challenges and the discovery doc stay in parity.## Related-- [x402 endpoints overview](#sec-619)+- [x402 endpoints overview](#sec-640)- [three-vanity/v1 protocol spec](#sec-006)-- [Pump Launcher](#sec-392) — accepts an optional vanity mint prefix/suffix+- [Pump Launcher](#sec-407) — 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-572"></a>+<a id="sec-592"></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-475), 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-495), 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`.@@ -136735,7 +142896,7 @@ 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. See [authentication.md](#sec-112) for minting one.+- **API key** (`Authorization: Bearer sk_live_...`), for scripts and servers. Bearer callers are CSRF-exempt because the token is itself the proof of intent. See [authentication.md](#sec-115) for minting one.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.@@ -136745,7 +142906,7 @@ The examples below use an API key in `$API_KEY`.Only 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-057) 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-074) and [custody.md](#sec-187)). 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-074) and [custody.md](#sec-191)). 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`.@@ -136778,7 +142939,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-557)). 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-577)). 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.@@ -136980,7 +143141,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-187).+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-191).## Reading a vault@@ -137011,16 +143172,16 @@ Two honest limits a backer should know: the platform can sign for the vault (tha## Related-- [trading-arenas.md](#sec-475) for the product overview of vaults and the surfaces around them+- [trading-arenas.md](#sec-495) for the product overview of vaults and the surfaces around them- [agent-wallets.md](#sec-074) for the custodial wallet a backer funds from-- [custody.md](#sec-187) for spend limits, the freeze switch, and proof of custody-- [user-wallet.md](#sec-557) for the per-user master wallet, the easiest way to send a vault its fee SOL+- [custody.md](#sec-191) for spend limits, the freeze switch, and proof of custody+- [user-wallet.md](#sec-577) for the per-user master wallet, the easiest way to send a vault its fee SOL- [agent-reputation.md](#sec-057) for the badge that gates opening a vault-- [authentication.md](#sec-112) for sessions, CSRF tokens, and API keys+- [authentication.md](#sec-115) for sessions, CSRF tokens, and API keys----<a id="sec-573"></a>+<a id="sec-593"></a>> **Source:** `docs/vendored-design-libraries.md` · [↑ table of contents](#table-of-contents)@@ -137117,7 +143278,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-366)).+ [package-extraction.md](#sec-379)).## third_party/designcode-agent-skills@@ -137185,7 +143346,7 @@ tree and must stay with it, and with anything derived from it.----<a id="sec-574"></a>+<a id="sec-594"></a>> **Source:** `docs/viability.md` · [↑ table of contents](#table-of-contents)@@ -137365,9 +143526,9 @@ appears only when there is something to show, pointing at the filtered## Related-- [The autonomous economy](#sec-113): the wallets, spend policies,+- [The autonomous economy](#sec-116): the wallets, spend policies,paid skills, and trading loops whose real activity this page measures.-- [x402 paid endpoints](#sec-619): the platform's own endpoint+- [x402 paid endpoints](#sec-640): the platform's own endpointrevenue, recorded in a different table and never mixed into the marketplace ortrading figures here.- [Agent Economy Volume](#sec-053): the agent-to-agent USDC@@ -137375,7 +143536,7 @@ appears only when there is something to show, pointing at the filtered----<a id="sec-575"></a>+<a id="sec-595"></a>> **Source:** `docs/viewer.md` · [↑ table of contents](#table-of-contents)@@ -137769,7 +143930,7 @@ A subset of state (background, transparency, background color, auto-rotate, expo----<a id="sec-576"></a>+<a id="sec-596"></a>> **Source:** `docs/voice-lab.md` · [↑ table of contents](#table-of-contents)@@ -137931,14 +144092,282 @@ The agent-voice handler ([`api/agents/_id/voice.js`](../api/agents/_id/voice.js)## Related-- [Voice and lipsync tutorial](#sec-549): the authoritative step-by-step, including wiring a cloned voice into an agent.-- [Lipsync](#sec-303): how synthesized speech drives an avatar's mouth in real time.-- [Talking Avatar Video](#sec-465): render a talking-head clip from an avatar and an audio track.+- [Voice and lipsync tutorial](#sec-569): the authoritative step-by-step, including wiring a cloned voice into an agent.+- [Lipsync](#sec-314): how synthesized speech drives an avatar's mouth in real time.+- [Talking Avatar Video](#sec-483): 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-577"></a>+<a id="sec-597"></a>++> **Source:** `docs/vscode.md` · [↑ table of contents](#table-of-contents)++# three.ws in VS Code++Two extensions put the platform inside the editor. **three.ws 3D** makes model+files, 3D generation, animation, and embedding native to VS Code. **three.ws+x402** does the same for paid endpoints. This page covers the first; see+[x402](x402.md#open-source-packages) for the second.++| | |+|---|---|+| **Extension** | three.ws 3D (`threews.vscode-3d`), version 0.2.0 |+| **Source** | [`packages/vscode-3d`](../packages/vscode-3d) |+| **Requires** | VS Code 1.85 or newer |+| **Auth** | None. Generation, refinement, the motion library, and the quality check all run on free lanes. |++## What it does++VS Code has no idea what a `.glb` is. Every 3D asset in a repository is an opaque+binary you have to leave the editor to look at: upload it somewhere, open a+browser viewer, come back. And once you can see it, the next questions (does it+animate, is it too heavy, what changed since the last commit, is the embed on+my page correct) each need another tool. This extension closes the whole loop.++### See it++**Model files render in an editor tab.** Double-click any `.glb` or `.gltf` and+it opens in a three.js viewer instead of the "binary file not shown" screen.+Orbit with the left mouse button, pan with the right, zoom with the wheel.+Animation clips get a picker, a play/pause button, and a scrub bar. There are+toggles for a wireframe, the skeleton, the ground grid, and a slow auto-orbit.+**Snapshot** writes the current camera view as a PNG next to the model;+**Turntable** writes a looping GIF of one full orbit, with the playing animation+stepped in sync, sized by `threews3d.turntableFrames` and `turntableSize`.++Draco, KTX2/Basis, and meshopt assets decode locally: the decoders ship inside+the extension rather than loading from a CDN, so a meshopt-compressed three.ws+avatar (which is most of them) renders on a plane with no connection.++**Every model carries a report.** The panel behind the **Report** button lists+triangles, vertices, meshes, materials, textures and their weight, animations,+rig size, and the glTF extensions in use, followed by optimization notes. It is+the same inspector that powers the [`/validation`](https://three.ws/validation)+page, running in the extension host, so your model is never uploaded anywhere+to be measured. The status bar repeats the headline numbers (triangles, size,+bones, clips) while a model is open; click it to toggle the report.++### Move it++**Any rig plays the library.** Press **Animate** (or run `3D: Try a Library+Animation on this Model`) and a searchable picker lists the three.ws motion+library: 2,800 clips, the same ones the `/animations` gallery and the+`<agent-3d>` embed play. Pick one and it plays on the open model immediately.+Behind that, the clip (authored on the platform's canonical humanoid skeleton)+is retargeted onto the model's own bones inside the viewer by+[`src/animation-retarget.js`](../src/animation-retarget.js), the retargeter+that runs on three.ws itself, so Mixamo, VRM/VRoid, Unreal, Daz,+MakeHuman, Blender `.L/.R`, and simple `shoulderL` rigs all work. A rig it+cannot drive gets a message with how many bones matched and an offer to rig it.++**Bake it into the file.** While a library clip is playing, **Bake clip**+writes it into a copy of the model (`astronaut-waving.glb`) as real glTF+animation samplers and channels on the model's nodes, so the clip plays in+Unity, Unreal, Blender, `<model-viewer>`, or `<agent-3d>`, not only in this+viewer. Meshopt-compressed models are re-encoded rather than inflated.++**Or describe the motion.** `3D: Animate this Model from a Text Prompt` sends+"waving confidently with the right hand" or "a slow tai-chi sweep" to the+text-to-motion worker on the three.ws GPU fleet, which samples a clip in the+same format, and retargets it the same way. The picker offers this as its+first entry, so a search that finds nothing turns into a generation.++### Make it++**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-326) lane, save the finished GLB+into your workspace, and open it in the viewer.++**Refine by describing a change.** **Refine** (or `3D: Refine this Model by+Describing a Change`) asks for the change in words: "make it metallic", "bigger+helmet", "add a cape". The studio generates a new version anchored to the+current one, folding the original prompt into the new one so form and subject+carry forward, and records it in a version lineage. The new file saves as+`name-v2.glb`, then `-v3`, and the extension remembers the lineage per file, so+refining a refinement extends one history instead of forking a new one. After+each refinement you can jump straight to a structural comparison with the+previous version.++**Rig a static model.** `3D: Rig a Model for Animation` sends it to the+auto-rigger and brings back one with a humanoid skeleton, then offers to try an+animation on it.++**Ask a vision model what is wrong.** **Check quality** renders the current+view, sends the PNG to the quality gate that scores every three.ws generation,+and opens the verdict as a Markdown review: realism and completeness scores,+the subject it recognised, the defects it can see ("fused fingers", "back is+unfinished"), and a concrete fix. One click feeds that fix into **Refine**.+Because the render is what travels, this works on a file that has never left+your disk.++### Ship it++**Optimize for the web, locally.** `3D: Optimize a Copy for the Web` runs the+asset pipeline's passes in the extension host: dedup, prune, weld, resample+animations, and meshopt compression, with a **Compact** preset that adds vertex+quantization. It writes `name.web.glb` next to the original and reports the+savings ("12.0 MB → 3.1 MB (−74%), 210k → 98k vertices"). Nothing is uploaded.+Textures are left as they are; texture resizing stays in the server pipeline.++**Compare with the committed version.** `3D: Compare with the Committed+Version` reads the model at `HEAD` straight out of git (no checkout), opens it+in a second viewer beside your working copy, and writes a structural diff as a+Markdown review using [`@three-ws/glb-diff`](../packages/glb-diff): what changed+in geometry, materials, textures, skeleton, and animations, with a severity that+says whether a consumer of the model breaks. It is the review a binary blob in a+pull request cannot give you. The same comparison is offered after a refinement+(against the previous version) and after an optimization (against the original).++**`<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-209) as diagnostics:++| Finding | Severity | Quick fix |+|---|---|---|+| Element has no `src`, `agent-id`, `avatar-id`, `manifest`, or `body` | error | |+| Element has no width and height (it collapses to 0×0) | warning | Add an inline 400×500 size |+| Library `<script>` on the `latest` channel | warning | Pin to the current release with its integrity hash |+| Library `<script>` on a minor channel (`1`, `1.5`) | hint | Pin to the current release |+| Pinned `<script>` with no `integrity` | hint | Add the published hash |+| Pinned `<script>` whose `integrity` does not match the release (the browser refuses it) | error | Use the published hash |+| A newer release exists than the one pinned | hint | Upgrade and re-pin |+| Unknown or misspelt attribute (`modee`) | information | Rename to the closest attribute |+| Invalid value for an enumerated attribute (`mode="popup"`) | warning | |+| An `api-key` written into HTML | warning | |++Hover any attribute for its documentation, get completions for attribute names+(sources first) and enumerated values, and use the CodeLens above an embed to+preview the referenced model in the viewer. The release and hash come from the+live manifest at `/agent-3d/versions.json`, cached for ten minutes; offline,+the rules that need it are skipped rather than guessed.++**The embed snippet is generated correctly.** `3D: Insert <agent-3d> Embed+Snippet` reads the live release manifest, pins the current library version, adds+its subresource-integrity hash, and writes the whole thing at your cursor:++```html+<script+ type="module"+ src="https://three.ws/agent-3d/1.5.2/agent-3d.js"+ integrity="sha384-…"+ crossorigin="anonymous"+></script>++<agent-3d+ body="https://three.ws/cdn/creations/…/mesh.glb"+ style="width: 400px; height: 500px; display: block;"+></agent-3d>+```++Set `threews3d.embedChannel` to `latest`, `1`, or `1.5` if you would rather+follow a moving channel than pin exact bytes (the diagnostics will then remind+you what that costs).++**The sidebar has both halves of your library.** The three.ws icon in the+activity bar lists every model in the workspace (grouped by folder, with file+sizes; right-click for Animate, Refine, Optimize, Compare) and, below it,+recent public creations from the forge. Preview any of those in the viewer, and+import the ones you want with one click.++## Install++The extension is not on the Marketplace yet. Build and install it from the+repository:++```bash+cd packages/vscode-3d+npm install+npm run package+code --install-extension vscode-3d-0.2.0.vsix+```++For development, open `packages/vscode-3d` in VS Code and press <kbd>F5</kbd> to+launch an Extension Development Host with the extension loaded, or run+`npm run watch` to rebuild on every change.++## Commands++| Command | What it does |+|---|---|+| `3D: Generate a Model from Text` | Free text to 3D. Saves the GLB and opens it. |+| `3D: Generate an Avatar from Text` | Same, tuned for characters. |+| `3D: Refine this Model by Describing a Change` | New version anchored to this one; lineage kept. |+| `3D: Try a Library Animation on this Model` | Search 2,800 clips; retarget and play in the viewer. |+| `3D: Animate this Model from a Text Prompt` | Text to motion, retargeted onto the rig. |+| `3D: Rig a Model for Animation` | Adds a humanoid skeleton to a static model. |+| `3D: Optimize a Copy for the Web` | Local dedup, weld, resample, meshopt (and quantize). |+| `3D: Compare with the Committed Version` | Structural diff against `HEAD`, viewers side by side. |+| `3D: Check Quality with a Vision Model` | Realism and completeness score, defects, fix hint. |+| `3D: Insert <agent-3d> Embed Snippet` | Writes a pinned, SRI-checked embed at the cursor. |+| `3D: Preview a Model URL` | Opens any hosted `.glb` in the viewer. |+| `3D: Open in the three.ws Viewer` | Opens the model in the browser viewer. |+| `3D: Copy the Model's three.ws URL` | Copies the hosted URL to the clipboard. |+| `3D: Save a PNG Snapshot of the View` | Writes the current view beside the model. |+| `3D: Save a Turntable GIF of the Model` | Writes a looping orbit beside the model. |+| `3D: Toggle the Model Report` | Shows or hides the report panel. |++## Settings++| Setting | Default | Purpose |+|---|---|---|+| `threews3d.origin` | `https://three.ws` | Host of the studio API, gallery, motion library, and quality check. |+| `threews3d.downloadFolder` | `models` | Workspace folder generated models are saved into. |+| `threews3d.tier` | `draft` | Detail level for text to 3D: `draft`, `standard`, or `high`. All free. |+| `threews3d.environment` | `studio` | Image-based lighting: `studio`, `neutral`, or `none`. |+| `threews3d.showGrid` | `true` | Show the ground grid when a model opens. |+| `threews3d.autoRotate` | `false` | Orbit the camera automatically when a model opens. |+| `threews3d.embedChannel` | `pinned` | `pinned` resolves the current release plus its SRI hash; or name a channel. |+| `threews3d.turntableFrames` | `36` | Frames in a turntable GIF (one full orbit). |+| `threews3d.turntableSize` | `480` | Pixel size of each square turntable frame. |+| `threews3d.embedDiagnostics` | `true` | Check `<agent-3d>` and library `<script>` tags in supported files. |++## What talks to the network, and what does not++Public, unauthenticated endpoints, and nothing else:++| Call | Endpoint | When |+|---|---|---|+| Generate, rig, refine, collect a slow job | `POST /api/mcp-studio` | Only when you run one of those commands. |+| Motion library | `GET /api/animations/library`, then the clip's CDN URL | The first time you open the Animate picker; one clip per pick. |+| Text to motion | `POST /api/forge-motion`, `GET ?job=` | Only when you animate from a prompt. |+| Quality check | `POST /api/forge-quality-check` | Only when you run the check; carries the render, never the model. |+| Gallery feed | `GET /api/forge-gallery` | The first time you expand the gallery view. |+| Release pin | `GET /agent-3d/versions.json` | When you insert an embed snippet, and every ten minutes while a file with an embed is open. |++The viewer itself is local. Its webview runs under a content security policy that+allows a single nonce-gated script and no remote origin, so the only things that+cross the network while you look at a model are the model file and, when you+pick one, a clip. Retargeting runs in the webview. Baking, optimizing,+inspecting, and the structural diff run in the extension host with+glTF-Transform. Opening, inspecting, animating with the file's own clips,+optimizing, comparing, and snapshotting a `.glb` make no requests at all.++## Embedding, rigging, or refining a local file++Those three need a URL that a browser or the studio can fetch. Models the+extension generated or imported remember where they came from, so those+commands work without asking. For a `.glb` that has only ever existed on your+disk, the extension asks for the https URL where it is hosted rather than+handing you a snippet that renders nothing. Animating, baking, optimizing,+comparing, and the quality check work on a purely local file.++## Related++- [Embedding](#sec-209) documents every `<agent-3d>` attribute the+ diagnostics and completions know.+- [3D Studio MCP](#sec-326) is the free generation lane the extension+ calls, and the same tools are available to any MCP client.+- [Animations](#sec-097) covers the motion library the Animate picker+ searches.+- [x402](#sec-645) covers the sibling extension for paid endpoints.+- [The 3D asset pipeline](#sec-002) explains what the optimization+ notes in the report are asking for, and what Optimize does about them.++---++<a id="sec-598"></a>> **Source:** `docs/walk-leaderboard.md` · [↑ table of contents](#table-of-contents)@@ -138062,7 +144491,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-583) 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-604) issue agent-signed proofs of physical presence with server-derived co-location.---@@ -138228,14 +144657,14 @@ The anonymous id is generated and persisted by the walk runtime in `localStorage## Related-- [Add the Walk Companion to your site](#sec-550), 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-570), 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-583), for movement claims that carry a verifiable agent signature rather than a leaderboard rank.+- [World Lines](#sec-604), for movement claims that carry a verifiable agent signature rather than a leaderboard rank.----<a id="sec-578"></a>+<a id="sec-599"></a>> **Source:** `docs/web-component.md` · [↑ table of contents](#table-of-contents)@@ -138343,7 +144772,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-440), and the+vocabulary are documented in [Sign language](#sec-458), and thealphabet is browsable at [/asl-alphabet](https://three.ws/asl-alphabet).### Skills and memory@@ -139256,7 +145685,7 @@ defineElement('my-agent');----<a id="sec-579"></a>+<a id="sec-600"></a>> **Source:** `docs/widget-api.md` · [↑ table of contents](#table-of-contents)@@ -139463,7 +145892,7 @@ If you have multiple widgets and want to coordinate them (sync camera, broadcast----<a id="sec-580"></a>+<a id="sec-601"></a>> **Source:** `docs/widget-studio.md` · [↑ table of contents](#table-of-contents)@@ -139707,14 +146136,14 @@ You can override these freely in the iframe `width` and `height` attributes. Add## Next steps-- [Widget API (JSON-RPC)](#sec-579) — programmatic control over an embedded widget: camera, animation, screenshots, model loading-- [Widgets reference](#sec-581) — technical details, postMessage API, CSP config, and oEmbed spec-- [Web component](#sec-578) — the `<agent-3d>` custom element for developer integrations-- [Embedding guide](#sec-204) — advanced embedding patterns and iframe options+- [Widget API (JSON-RPC)](#sec-600) — programmatic control over an embedded widget: camera, animation, screenshots, model loading+- [Widgets reference](#sec-602) — technical details, postMessage API, CSP config, and oEmbed spec+- [Web component](#sec-599) — the `<agent-3d>` custom element for developer integrations+- [Embedding guide](#sec-209) — advanced embedding patterns and iframe options----<a id="sec-581"></a>+<a id="sec-602"></a>> **Source:** `docs/widgets.md` · [↑ table of contents](#table-of-contents)@@ -140127,7 +146556,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-104).+For the full API reference including request/response shapes, error codes, and pagination, see [api-reference.md](#sec-105).---@@ -140219,7 +146648,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-579) 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-600) reference. The `ThreeWidget` SDK lives at `/widget-client.js` and works with any iframe pointing at `/widget`.---@@ -140232,7 +146661,7 @@ Need to drive a widget from the parent page — change the camera, play an anima----<a id="sec-582"></a>+<a id="sec-603"></a>> **Source:** `docs/witness.md` · [↑ table of contents](#table-of-contents)@@ -140247,7 +146676,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-239) hands you the compiled test with one click.+ [`/feedback`](#sec-245) 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@@ -140419,13 +146848,13 @@ engineer's spec file on disk. Full API in the## Related-- [Feedback](#sec-239): the loop this is the second half of, and the+- [Feedback](#sec-245): the loop this is the second half of, and theuntrusted-input boundary that governs all of it.-- [Notifications](#sec-342): the same companion, delivering the other way.+- [Notifications](#sec-353): the same companion, delivering the other way.----<a id="sec-583"></a>+<a id="sec-604"></a>> **Source:** `docs/world-lines.md` · [↑ table of contents](#table-of-contents)@@ -140435,7 +146864,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-104); 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-105); 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).@@ -140667,7 +147096,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-295); 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-305); the user-facing summary is the `three.ws/irl-privacy` page. World Lines specifically:**Stored.**@@ -141007,14 +147436,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-295), the adversarial analysis behind every radius and cap above.-- [Place a 3D agent in your real environment](#sec-527), how to create the anchor pin a World Line needs.-- [API reference](#sec-104), the one-screen summary of these endpoints alongside the rest of `/api/irl/*`.-- [AR](#sec-107), the camera and WebXR layer the ceremony builds on.+- [IRL threat model](#sec-305), the adversarial analysis behind every radius and cap above.+- [Place a 3D agent in your real environment](#sec-547), how to create the anchor pin a World Line needs.+- [API reference](#sec-105), the one-screen summary of these endpoints alongside the rest of `/api/irl/*`.+- [AR](#sec-108), the camera and WebXR layer the ceremony builds on.----<a id="sec-584"></a>+<a id="sec-605"></a>> **Source:** `docs/x-account-appeal.md` · [↑ table of contents](#table-of-contents)@@ -141027,6 +147456,25 @@ account is evasion and that an X Premium subscription keeps billing. Thesuspension is confirmed independently: X's public user endpoint answers`"User is suspended"` for the handle.+**Appeal #1 was denied on 2026-09-05.** X reviewed it, said a violation "did+take place", cited the authenticity rules again, and declined to overturn the+lock. That is a decision on the first filing, not the end of the route:+section 3 shows that most documented reinstatements came after several spaced+filings, and several of them came after a denial worded exactly like this one.+The live next step is refiling, per section 6 step 5.++Two things in that denial are worth reading carefully before anyone acts on+it. First, it says **"lock"** where the original said "suspend", and it invites+the owner to "resolve the violations by logging into your account and+completing the on-screen instructions", which is X's standard copy for a+*locked* account that clears itself through a verification flow. Second, that+is not the state the account is actually in: the public probe still answers+`"User is suspended"` for user ID `2817123964` as of 2026-09-06. The+remediation sentence is boilerplate in a template, not an unlock path that+someone has failed to click. Log in and look anyway, because it costs one+minute and it is the only way to see the account-level screen X actually+serves, but do not plan around finding a self-serve fix there.+This file is the whole case in one place: what X's own process is, what thedocumented successful appeals had in common, what got other people denied,the exact text to submit, and the order to do things in. It was assembled on@@ -141035,7 +147483,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-585). Update that file when this one changes the+[`x-accounts.md`](#sec-606). Update that file when this one changes thefacts.## 1. What this suspension is, and is not@@ -141335,6 +147783,121 @@ in section 1; verified against production on 2026-08-28). So there is nothingto pre-empt, and volunteering the company account would only invite areviewer to link two accounts that X has no reason to look at together.+## 5b. Appeal #2, drafted and ready to file++**Status: written, NOT yet filed.** Filing is the owner's action; add a line+to the filing log the moment it goes in.++**Where it goes:**+[`help.x.com/en/forms/account-access/appeals`](https://help.x.com/en/forms/account-access/appeals),+logged in as `@nichxbt` so the handle and email pre-fill, which is the same+form appeal #1 went through. There is a second, non-duplicate channel worth+using alongside it:+[`help.x.com/en/forms/account-restoration/locked`](https://help.x.com/en/forms/account-restoration/locked)+("Your Account is locked"). X's own denial calls this a lock, so filing the+lock form is answering X in X's own terms rather than refiling the same+appeal twice, and it puts the notice-versus-state discrepancy in front of a+different queue. Both render only in a real browser. An EU variant of the+lock form exists (`account-restoration/locked-eu`) and does not apply from+the US; see section 7 point 5 on why EU routes are not available here. Appeal #1 was denied on 2026-09-05,+so section 6 step 5 applies: reworded, and carrying a fact the first one did+not have. It carries three.++**The new facts, and why these three.** The first is the strongest thing the+denial handed us. X's notice says "lock" and tells the owner to complete+on-screen instructions; there are none, and the public endpoint still reports+the account suspended. That is a discrepancy inside X's own record rather+than another character reference, and it gives a reviewer a concrete reason+to pull the file, which is the whole objective of a refiling. The second is+that no X developer application was ever created or authorized on the+account, which a reviewer can confirm from their side in seconds and which+directly rules out the automated-activity limb of the authenticity policy.+The third replaces appeal #1's general "published partner listings" with one+URL on a third party's own domain, per section 6 step 5. All four links in+this packet were checked live on 2026-09-06; the IBM post is the one to send+because the domain is IBM's and the author is a named IBM employee.++> My appeal for @nichxbt was denied on September 5. The decision says you will+> not overturn the lock on my account and that I can restore functionality by+> logging in and completing the on-screen instructions. There are no on-screen+> instructions when I log in, and the account is not locked: the profile shows+> as suspended and your public user endpoint reports "User is suspended" for+> user ID 2817123964. Please check which enforcement action is actually+> recorded against this account, because your notice and the account state do+> not describe the same thing.+>+> On the finding itself, here is one point you can verify from your side: no X+> developer application has ever been created or authorized on this account,+> so none of the automated activity the authenticity policy covers could have+> run through it. I have held the account since 2014 and I post from it by+> hand.+>+> I am a real person running a real company. IBM published this about our work+> in June: https://community.ibm.com/community/user/blogs/jessica-swanson/2026/06/11/threews-the-open-on-chain-platform-for-3d-agents+> I am willing to complete government-ID verification; no verification has+> been offered to me on screen.+>+> Please have a person review both the account and the enforcement record.++**One optional line, only if it is true on the day of filing.** Gasparro's+winning appeals stated Premium+ subscriber status, and X's own email confirms+the subscription keeps billing through a suspension. If the subscription is+still active, add "I have been a paying subscriber throughout" to the third+paragraph. Do not add it otherwise: section 5's rule about falsifiable claims+is the one that turns a mistaken suspension into an upheld one.++**What this deliberately still does not do.** It does not mention+`@trythreews`, for the reason in section 5. It does not accuse anyone of+reporting the account, does not argue policy, and does not ask for an+apology. It does not repeat appeal #1's sentences about what the account is+used for; a reviewer who pulls the file can already see appeal #1, and+repeating it is what section 4 says gets refilings denied.++## 5c. The data-access request, ready to file++**Status: written, NOT yet filed.** Section 7 point 4 says to file this+regardless of what the appeals do, and that judgement stands: it costs+nothing, it dates the request, and it is the only route that has ever forced+X to name the real trigger for an enforcement action, albeit in the EU and+only under litigation (Mekic v. X). From the US it is a long shot. File it+anyway, and do not wait on it or let it change the appeal cadence.++**Where it goes:**+[`help.x.com/en/forms/privacy/request-account-info/me`](https://help.x.com/en/forms/privacy/request-account-info/me)+(the "myself" branch of `forms/privacy/request-account-info`; the other+branches are for a representative or an organisation). Like every other+`help.x.com` page it answers `403` to an automated reader and renders only in+a browser.++**What it is actually for.** The gap this packet cannot close from outside is+that nobody has ever been told *which* post or behaviour triggered the+report. Every appeal so far argues the rule does not fit the account, which+is a claim about the whole account. If X returns even the rule sub-clause or+the date of the triggering content, the next appeal stops being general and+becomes specific, and section 1 already shows specific appeals do far better.+That is the value here, not the privacy right itself.++> Under the California Consumer Privacy Act I am requesting the specific+> pieces of personal information you hold about my account @nichxbt (user ID+> 2817123964), and in particular:+>+> 1. The enforcement record for this account: every action taken against it,+> the date of each, and whether each was applied as a lock or a suspension.+> 2. The specific rule or sub-clause of the authenticity policy the account+> was found to have violated on August 27, 2026, and the content or+> behaviour that triggered it.+> 3. Whether the action was taken by an automated system or a human reviewer,+> and the output of any automated classifier applied to the account.+> 4. The number of reports received against the account and the dates they+> were received. I am not requesting the identity of any reporter.+>+> I am the account holder and I can complete any identity verification you+> require to process this request.++Point 4 asks for counts and dates only, deliberately. Asking who reported the+account guarantees a refusal on third-party privacy grounds and gives X a+clean reason to decline the whole request rather than the parts it can answer.+## Filing logEvery contact with X about this suspension, in order. Append to it; never@@ -141344,6 +147907,29 @@ rewrite an earlier line.| --- | --- | --- || 2026-08-27 06:29 | X emails: account "was reported and has been suspended" for "violating our rules against authenticity". | Suspension confirmed; public user endpoint answers "User is suspended". || 2026-08-28 06:26 | Appeal #1 filed through the form with the text in section 5. | Form acknowledged receipt. Awaiting review. Next check: log in daily; earliest refiling if silent or auto-denied: 2026-08-31. |+| 2026-09-05 04:25 | X emails the decision on appeal #1: "a violation of our Rules did take place", "Violating our Rules against authenticity", "we will not overturn our decision to lock your account". Adds that functionality can be restored by "logging into your account and completing the on-screen instructions". | Denied. Eight days from filing, so a human review rather than the documented same-day auto-denial: appeal #2 must carry a new fact, not the same text. See section 6 step 5. |+| 2026-09-06 | Public probe re-run against both handles from a datacenter IP. | `@nichxbt` (id `2817123964`) still answers `"User is suspended"`; control `@trythreews` answers `200` and live. The denial's "lock" wording did not come with a change of state. X's own syndication endpoint rate-limits this IP (`429`), so the probe went through a public mirror of the same endpoint. |+| 2026-09-07 | Owner logs in as `@nichxbt` to look for the remediation flow the denial pointed at. | Nothing on offer: no lock prompt, no phone/email/recaptcha step, no ID verification. This closes the ID-verification path (section 6 step 2) rather than leaving it open, and it confirms from inside the account what the probe showed from outside: the enforcement applied is a suspension, so the denial's "lock" wording and its remediation sentence describe a state this account is not in. Appeal #2 leads with exactly that. |++## The schedule, from here++Dates matter more than effort in this process: section 3 found that every+documented success spaced its filings and every documented failure did not.+Section 4's specific finding is that nobody who succeeded filed within 24+hours of a denial.++| When | What | Gate it satisfies |+| --- | --- | --- |+| 2026-09-05 | Appeal #1 denied. | |+| 2026-09-07 onward | **Appeal #2 (section 5b) is fileable now.** Two days past the denial, and the text is new rather than a resend. File the lock form (section 5b) at the same time; it is a different queue, not a second filing in the same one. File the data-access request above on the same day. | Past the 24-hour floor. |+| 3 to 5 days after #2 | Appeal #3: reworded again, one further new fact. Do not send it sooner even if nothing has come back. | The 3-to-5-day spacing. |+| 2026-09-11 at the earliest, and only after three filings | Executive email, once (section 7 point 3). Both conditions are required: two weeks of the form path, which began 2026-08-28, and three filings on the record. | Section 7 point 3. |++Two escalations in section 7 stay shut for now. The public thread to X's Head+of Product (point 2) needs a personal or community account and must never run+from `@trythreews`, so it has no vehicle while the personal account is down.+Legal (point 6) ends every goodwill path above it and is not opened on a case+this young.## 6. The order of operations@@ -141354,15 +147940,46 @@ rewrite an earlier line.2. **Log in as `@nichxbt` on desktop.** If X shows an identity-verificationprompt, complete it (government ID plus selfie, via Persona). This is thehighest-value single step for an authenticity case.++ **There is no URL that starts ID verification on demand, and the denial+ email's "on-screen instructions" are not it.** X's locked-account page says+ the lock flow is "verify ownership by phone, email or recaptcha"+ ([help.x.com/en/managing-your-account/locked-and-limited-accounts](https://help.x.com/en/managing-your-account/locked-and-limited-accounts),+ read from the 2026-08-03 Wayback capture because the live page blocks+ automated readers): log in, find the "Your account has been locked"+ message, press Start. No document is uploaded anywhere in it. Government ID+ plus selfie is a separate check that X offers at login when it chooses to,+ which is what happened to Gasparro; it cannot be requested. The two ID+ flows that do have public URLs are different products and do not apply:+ `help.x.com/en/forms/creator-id-verification` is monetization payouts, and+ age verification is triggered by X. Do not chase either.++ So logging in is a fork, and the screen decides the next move: a lock+ prompt means do phone/email/recaptcha and the account clears itself; an ID+ prompt means complete it and lead appeal #2 with it; the suspension+ interstitial means no verification is on offer and appeal #2 offers to+ complete ID verification instead (section 3, point 2). The probe on+ 2026-09-06 says to expect the third.++ One form is worth knowing before that fork:+ [`help.x.com/en/forms/account-restoration/locked`](https://help.x.com/en/forms/account-restoration/locked),+ titled "Your Account is locked", is a **different form** from the+ suspension appeal. Because X's own denial calls this a lock, filing it is+ not a duplicate of appeal #1 and does not count as the same-text refiling+ that section 4 says gets people denied. It renders only in a real browser.3. **File the appeal through the form.** Done, 2026-08-28 06:26; see thefiling log. Keep the confirmation screenshot.4. **Wait a full 72 hours.** An automatic denial inside the first day is the- documented norm and is not the end.+ documented norm and is not the end. What arrived instead was a denial on+ day 8 (2026-09-05), which is the slower human-review path.5. **If denied or silent after 72 hours: refile, reworded, with one newfact.** The new fact is ID verification if it completed after the firstfiling, otherwise a specific pointer such as the account's 2014 creationor a partner listing URL. Do not resend the same text. Every 3 to 5 days,- never sooner.+ never sooner. **This is where the case stands now.** Appeal #1 was denied,+ so appeal #2 is due, and the single highest-value new fact remains a+ completed ID verification (step 2); if that is already done, lead with it+ and say so in the first line.6. **Check by logging in, not by waiting for email.** Restoration was silentin the best-documented case. A "restored" email that does not restoreaccess is a known 2026 bug: log out, reset password, log in again.@@ -141391,7 +148008,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-585)). Tag+ account, never from `@trythreews` (see [x-accounts.md](#sec-606)). 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@@ -141461,7 +148078,7 @@ could not be opened.----<a id="sec-585"></a>+<a id="sec-606"></a>> **Source:** `docs/x-accounts.md` · [↑ table of contents](#table-of-contents)@@ -141469,7 +148086,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-591) draft, before adding an X+anything from an [`x-posts/`](#sec-612) draft, before adding an Xlink to a page, and before deciding which handle a meta tag should name.## Status@@ -141477,7 +148094,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 filed 2026-08-28 06:26, awaiting review.** Confirmed by X's own notification email. Do not link to it and do not plan a post from it. Status and filing log: [`x-account-appeal.md`](#sec-584). |+| `@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-605). |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",@@ -141496,17 +148113,27 @@ Two operational facts from that email, both load-bearing:- **An X Premium subscription is not cancelled by the suspension** and keepsbilling until someone cancels it deliberately.-An appeal through X support is the only path back to the handle. 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-584). Nothing in-this repo should wait on it.+Appeal #1 was denied on 2026-09-05: X says a violation "did take place" and+that it will not overturn the decision. That closes the first filing, not the+route. 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-605). Nothing in this repo should wait+on it.++One wording trap in that denial, because it will be read again later: the+email says "lock", and a locked account normally clears itself through an+on-screen flow at login. This one does not. The public probe still answers+"User is suspended" for user ID `2817123964` (2026-09-06), so the account is+suspended and the lock template is boilerplate. Do not record it as a+downgrade in status, and do not tell anyone the handle is one login away.The reader-facing version of the status table lives on[three.ws/community](https://three.ws/community), which lists every channel and the`$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-165) carries the same list for readers who arrive through+[`community.md`](#sec-169) carries the same list for readers who arrive throughthe docs.## What a suspended handle actually breaks@@ -141534,8 +148161,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-591), plus-[`x402-solana-july-roundup-response.md`](#sec-622)+Nine drafts in [`x-posts/`](#sec-612), plus+[`x402-solana-july-roundup-response.md`](#sec-643)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@@ -141563,10 +148190,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-608) picks between a long and+[`osf-issue-reply.md`](#sec-629) 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-358) submits the+[`open-source-friday-plan.md`](#sec-370) submits thehandle as a form field to a third party.## Do not litigate the suspension from `@trythreews`@@ -141590,7 +148217,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-464).+[`syndication.md`](#sec-482).## Referral codes are not the handle@@ -141606,7 +148233,7 @@ alone too.----<a id="sec-586"></a>+<a id="sec-607"></a>> **Source:** `docs/x-archive.md` · [↑ table of contents](#table-of-contents)@@ -141667,7 +148294,7 @@ clean checkout.## The report-[docs/x-archive/trythreews-engagement.md](#sec-587)+[docs/x-archive/trythreews-engagement.md](#sec-608)is generated, never hand-edited. It carries:- headline totals and the engagement **distribution** (median, p75/p90/p99, and@@ -141718,7 +148345,7 @@ Code: [scripts/x-archive-lib.mjs](../scripts/x-archive-lib.mjs)----<a id="sec-587"></a>+<a id="sec-608"></a>> **Source:** `docs/x-archive/trythreews-engagement.md` · [↑ table of contents](#table-of-contents)@@ -141969,7 +148596,7 @@ The floor is as instructive as the ceiling: these are the shapes to stop repeati----<a id="sec-588"></a>+<a id="sec-609"></a>> **Source:** `docs/x-memory-seeding.md` · [↑ table of contents](#table-of-contents)@@ -141988,7 +148615,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-321), [Farcaster memory seeding](#sec-238), [GitHub seeding in the same table](memory.md#seeding-memory-from-an-existing-account)+- **Related**: [Memory system](#sec-332), [Farcaster memory seeding](#sec-244), [GitHub seeding in the same table](memory.md#seeding-memory-from-an-existing-account)---@@ -142087,7 +148714,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-321)).+ the chat runtime pages into every reply (see [memory system](#sec-332)).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.@@ -142302,7 +148929,7 @@ Seeded rows in `agent_memories` are found by tag (`tags && '{x_seed}'`) and by----<a id="sec-589"></a>+<a id="sec-610"></a>> **Source:** `docs/x-posts/3d-ar-studio-launch.md` · [↑ table of contents](#table-of-contents)@@ -142602,7 +149229,7 @@ Point it at your own catalogue with one option if you would rather use yours.----<a id="sec-590"></a>+<a id="sec-611"></a>> **Source:** `docs/x-posts/3d-ar-studio-video-script.md` · [↑ table of contents](#table-of-contents)@@ -142727,7 +149354,7 @@ match them to the narration beats:----<a id="sec-591"></a>+<a id="sec-612"></a>> **Source:** `docs/x-posts/README.md` · [↑ table of contents](#table-of-contents)@@ -142741,7 +149368,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-585) has the+> do not move its copy onto the platform account. [`x-accounts.md`](#sec-606) has the> account status and the full rule.## How these are written@@ -142760,38 +149387,38 @@ 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-605) | 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-598) | The fleet as a whole: 72 MCP servers under one namespace in the official registry, all current |-| [`metaplex-agent-mcp-launch.md`](#sec-601) | 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-603) | 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-600) | The browser deployer at nirholas.github.io/metaplex-agent-mcp |-| [`3d-ar-studio-launch.md`](#sec-589) | 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-593) | 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-613) | The three.ws avatar pipeline launch copy |-| [`oracle-trading-mcp-x-post.md`](#sec-607) | The oracle trading MCP server launch |-| [`sperax-staking-in-chat-x-post.md`](#sec-611) | 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-604) | The news archive |-| [`proof-of-life-x-post.md`](#sec-609) | 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-610) | The pump.fun article |+| [`onchain-agent-wallets-x-post.md`](#sec-626) | 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-619) | The fleet as a whole: 72 MCP servers under one namespace in the official registry, all current |+| [`metaplex-agent-mcp-launch.md`](#sec-622) | 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-624) | 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-621) | The browser deployer at nirholas.github.io/metaplex-agent-mcp |+| [`3d-ar-studio-launch.md`](#sec-610) | 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-614) | 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-634) | The three.ws avatar pipeline launch copy |+| [`oracle-trading-mcp-x-post.md`](#sec-628) | The oracle trading MCP server launch |+| [`sperax-staking-in-chat-x-post.md`](#sec-632) | 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-625) | The news archive |+| [`proof-of-life-x-post.md`](#sec-630) | 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-631) | The pump.fun article |## Video and narration scripts| File | What it covers || --- | --- |-| [`metaplex-agent-mcp-veo-script.md`](#sec-602) | 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-599) | Spoken narration for the deployer clip |-| [`threews-avatar-video-script.md`](#sec-614) | Shot list for the avatar clip |-| [`3d-ar-studio-video-script.md`](#sec-590) | Narration and shot prompts for the AR Studio launch video |+| [`metaplex-agent-mcp-veo-script.md`](#sec-623) | 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-620) | Spoken narration for the deployer clip |+| [`threews-avatar-video-script.md`](#sec-635) | Shot list for the avatar clip |+| [`3d-ar-studio-video-script.md`](#sec-611) | Narration and shot prompts for the AR Studio launch video |## Events and community| File | What it covers || --- | --- |-| [`osf-issue-reply.md`](#sec-608) | 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-594) | Event campaign copy, split by account (`@trythreews` institutional, `@nichxbt` personal) |-| [`x-meetup-posts.md`](#sec-615) | The in-platform community meetup announcement |-| [`ibm-skillsbuild-x-post.md`](#sec-597) | The IBM SkillsBuild badge |-| [`fomo-verified-x-post.md`](#sec-595) | FOMO verification |+| [`osf-issue-reply.md`](#sec-629) | 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-615) | Event campaign copy, split by account (`@trythreews` institutional, `@nichxbt` personal) |+| [`x-meetup-posts.md`](#sec-636) | The in-platform community meetup announcement |+| [`ibm-skillsbuild-x-post.md`](#sec-618) | The IBM SkillsBuild badge |+| [`fomo-verified-x-post.md`](#sec-616) | FOMO verification |## Conventions@@ -142807,7 +149434,7 @@ entry is dead once the file is no longer routed.----<a id="sec-592"></a>+<a id="sec-613"></a>> **Source:** `docs/x-posts/android-app-launch.md` · [↑ table of contents](#table-of-contents)@@ -142874,7 +149501,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-584). It is written and ready for the day the+[`../x-account-appeal.md`](#sec-605). It is written and ready for the day theappeal lands.```@@ -142899,7 +149526,7 @@ The checklist item is in [`../../solana-mobile/docs/CHECKLIST.md`](../solana-mob----<a id="sec-593"></a>+<a id="sec-614"></a>> **Source:** `docs/x-posts/ar-quick-look-fix-x-post.md` · [↑ table of contents](#table-of-contents)@@ -142907,7 +149534,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-613) sells the avatar-has-a-body+did. Related file: [threews-avatar-launch.md](#sec-634) 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@@ -142990,7 +149617,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-594): `@trythreews` posts the+Same two-account split as [event-x-posts.md](#sec-615): `@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.@@ -143116,15 +149743,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-589) already frames its media: a real floor in+ [3d-ar-studio-launch.md](#sec-610) 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-589)). That post is about giving the surface away as+ ([3d-ar-studio-launch.md](#sec-610)). 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-594"></a>+<a id="sec-615"></a>> **Source:** `docs/x-posts/event-x-posts.md` · [↑ table of contents](#table-of-contents)@@ -143438,7 +150065,7 @@ Practical notes for reused footage:----<a id="sec-595"></a>+<a id="sec-616"></a>> **Source:** `docs/x-posts/fomo-verified-x-post.md` · [↑ table of contents](#table-of-contents)@@ -143532,7 +150159,7 @@ Shorter alternate:----<a id="sec-596"></a>+<a id="sec-617"></a>> **Source:** `docs/x-posts/github-100-stars.md` · [↑ table of contents](#table-of-contents)@@ -143540,7 +150167,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-357); 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-369); keep the copy below in sync with it.## Where every number comes from (as of August 25, 2026)@@ -143755,7 +150382,7 @@ Star the repo: github.com/nirholas/three.ws----<a id="sec-597"></a>+<a id="sec-618"></a>> **Source:** `docs/x-posts/ibm-skillsbuild-x-post.md` · [↑ table of contents](#table-of-contents)@@ -143963,7 +150590,7 @@ https://www.credly.com/badges/b7ea921a-ce3d-4f4d-bfac-38f95276d361/twitter via @----<a id="sec-598"></a>+<a id="sec-619"></a>> **Source:** `docs/x-posts/mcp-registry-fleet-x-post.md` · [↑ table of contents](#table-of-contents)@@ -144080,14 +150707,14 @@ Post 1 is the main post. Then:----<a id="sec-599"></a>+<a id="sec-620"></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-603); this file is what gets said, cut+[metaplex-agent-mcp-x-post.md](#sec-624); 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@@ -144187,7 +150814,7 @@ For a single generation with no editing. One breath, one idea.----<a id="sec-600"></a>+<a id="sec-621"></a>> **Source:** `docs/x-posts/metaplex-agent-deployer-x-post.md` · [↑ table of contents](#table-of-contents)@@ -144425,7 +151052,7 @@ our own product, no pretending to be a bystander.----<a id="sec-601"></a>+<a id="sec-622"></a>> **Source:** `docs/x-posts/metaplex-agent-mcp-launch.md` · [↑ table of contents](#table-of-contents)@@ -144628,14 +151255,14 @@ fund them, which is already the safe, verified claim.----<a id="sec-602"></a>+<a id="sec-623"></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-601). Text-to-video only, no dialogue, no+[`metaplex-agent-mcp-launch.md`](#sec-622). 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.@@ -144739,7 +151366,7 @@ to show something spreading to others, not just one agent getting a wallet.----<a id="sec-603"></a>+<a id="sec-624"></a>> **Source:** `docs/x-posts/metaplex-agent-mcp-x-post.md` · [↑ table of contents](#table-of-contents)@@ -145016,7 +151643,7 @@ keys, your limits.**----<a id="sec-604"></a>+<a id="sec-625"></a>> **Source:** `docs/x-posts/news-archive-x-post.md` · [↑ table of contents](#table-of-contents)@@ -145106,11 +151733,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-341).+mirror, archive search, and the agent knowledge corpus. See [docs/news-rights.md](#sec-352).----<a id="sec-605"></a>+<a id="sec-626"></a>> **Source:** `docs/x-posts/onchain-agent-wallets-x-post.md` · [↑ table of contents](#table-of-contents)@@ -145296,7 +151923,7 @@ Post 1 is the main post above. Then:----<a id="sec-606"></a>+<a id="sec-627"></a>> **Source:** `docs/x-posts/open-source-ecosystem.md` · [↑ table of contents](#table-of-contents)@@ -145343,7 +151970,7 @@ Attach: marketing/open-source-ecosystem/images/header-x-article.png, then the ar----<a id="sec-607"></a>+<a id="sec-628"></a>> **Source:** `docs/x-posts/oracle-trading-mcp-x-post.md` · [↑ table of contents](#table-of-contents)@@ -145354,7 +151981,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-363).+Build plan this announces: [`docs/oracle-trading-mcp-plan.md`](#sec-375).**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@@ -145484,7 +152111,7 @@ place to be wrong.----<a id="sec-608"></a>+<a id="sec-629"></a>> **Source:** `docs/x-posts/osf-issue-reply.md` · [↑ table of contents](#table-of-contents)@@ -145532,11 +152159,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-358).+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-370).----<a id="sec-609"></a>+<a id="sec-630"></a>> **Source:** `docs/x-posts/proof-of-life-x-post.md` · [↑ table of contents](#table-of-contents)@@ -145544,7 +152171,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-584) rules out posting about+about the suspension: [`x-account-appeal.md`](#sec-605) 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@@ -145662,7 +152289,7 @@ Pin this in @three_ws alongside the shipping post.----<a id="sec-610"></a>+<a id="sec-631"></a>> **Source:** `docs/x-posts/pumpfun-article-x-post.md` · [↑ table of contents](#table-of-contents)@@ -145779,7 +152406,7 @@ Pick one option. Do not post all four.----<a id="sec-611"></a>+<a id="sec-632"></a>> **Source:** `docs/x-posts/sperax-staking-in-chat-x-post.md` · [↑ table of contents](#table-of-contents)@@ -145885,7 +152512,7 @@ on the `/staking` page footer, so anyone who tries it gets exactly what the post----<a id="sec-612"></a>+<a id="sec-633"></a>> **Source:** `docs/x-posts/the-first-19-weeks.md` · [↑ table of contents](#table-of-contents)@@ -145946,14 +152573,14 @@ The First 19 Weeks is out: the whole story of three.ws since the first commit, 9----<a id="sec-613"></a>+<a id="sec-634"></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-614).+[threews-avatar-video-script.md](#sec-635).**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.@@ -146103,7 +152730,7 @@ Carries the part that does not fit the main post without spending its outbound l----<a id="sec-614"></a>+<a id="sec-635"></a>> **Source:** `docs/x-posts/threews-avatar-video-script.md` · [↑ table of contents](#table-of-contents)@@ -146111,9 +152738,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-613), the spoken lines live in-[metaplex-agent-deployer-video-script.md](#sec-599), and the-deployer-specific shot list lives in [metaplex-agent-mcp-x-post.md](#sec-603).+[threews-avatar-launch.md](#sec-634), the spoken lines live in+[metaplex-agent-deployer-video-script.md](#sec-620), and the+deployer-specific shot list lives in [metaplex-agent-mcp-x-post.md](#sec-624).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@@ -146256,7 +152883,7 @@ Keep the pause after "It has no body." That silence is the whole premise.----<a id="sec-615"></a>+<a id="sec-636"></a>> **Source:** `docs/x-posts/x-meetup-posts.md` · [↑ table of contents](#table-of-contents)@@ -146313,13 +152940,13 @@ https://community.ibm.com/community/user/discussion/community-meetup-inside-thre----<a id="sec-616"></a>+<a id="sec-637"></a>> **Source:** `docs/x402-buyer.md` · [↑ table of contents](#table-of-contents)# x402 Buyer Client-To consume a paid [x402 endpoint](#sec-619) — ours or anyone's — a+To consume a paid [x402 endpoint](#sec-640) — 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@@ -146386,7 +153013,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-169)).+`X402_MAX_PER_DAY_ATOMIC`; see [Configuration](#sec-173)).## Axios variant@@ -146409,13 +153036,13 @@ set) back into the payment so attribution survives the round trip.## Related-- [x402 protocol](#sec-624) — the underlying challenge/settle mechanics.-- [x402 paid endpoints](#sec-619) — what you can buy from us.-- [Autonomous x402 loop](#sec-114) — uses this client on a schedule.+- [x402 protocol](#sec-645) — the underlying challenge/settle mechanics.+- [x402 paid endpoints](#sec-640) — what you can buy from us.+- [Autonomous x402 loop](#sec-117) — uses this client on a schedule.----<a id="sec-617"></a>+<a id="sec-638"></a>> **Source:** `docs/x402-dev-tools.md` · [↑ table of contents](#table-of-contents)@@ -146627,13 +153254,13 @@ implementation against a live server.----<a id="sec-618"></a>+<a id="sec-639"></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-624). Building them is+three.ws sells 90+ pay-per-call services over [x402](#sec-645). 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,@@ -146668,7 +153295,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-114) already drives real+*ranked*. The [autonomous x402 loop](#sec-117) 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@@ -146848,25 +153475,25 @@ script. Everything else above updates itself.## Related-- [x402 overview](#sec-624) · [Paid endpoints reference](#sec-619) ·- [Autonomous loop](#sec-114) · [Buyer client](#sec-616)+- [x402 overview](#sec-645) · [Paid endpoints reference](#sec-640) ·+ [Autonomous loop](#sec-117) · [Buyer client](#sec-637)----<a id="sec-619"></a>+<a id="sec-640"></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-624): the caller hits the endpoint, receives a `402 Payment Required`+[x402](#sec-645): 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-616). For the loop-that calls many of them on a schedule, see [Autonomous x402 loop](#sec-114).+To call these as a buyer, see [x402 buyer client](#sec-637). For the loop+that calls many of them on a schedule, see [Autonomous x402 loop](#sec-117).> Source: handlers under [`api/x402/`](../api/x402), pricing> [`api/_lib/x402-prices.js`](../api/_lib/x402-prices.js), shared handler@@ -146897,7 +153524,7 @@ and, when configured, **USDC on Base** (EVM) and a **BSC leg** (contract-mediate`direct` scheme, advertised only when `X402_PAY_TO_BSC` is set). On the Solanarail, `X402_ACCEPT_THREE_SOLANA` optionally advertises **$THREE** alongside USDCas a second accept entry on the same challenge. The relevant config (see-[Configuration](#sec-169)):+[Configuration](#sec-173)):| Key | Meaning || ---------------------------------------------------- | ------------------------------------ |@@ -146979,7 +153606,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-335).+[money map](#sec-346).## Intel & oracle endpoints@@ -147059,7 +153686,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-482)). |+| `/api/x402/agent-reputation` | $0.01 | Cross-chain 0–100 trust score for any wallet/mint/agent id ([trust primitives](#sec-502)). || `/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. |@@ -147070,8 +153697,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-122). |-| `/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-205). |+| `/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-125). |+| `/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-210). || `/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. 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). |@@ -147087,8 +153714,8 @@ datapoints at **$0.0005** USDC each by default, overridable per family with| Endpoint | Default | Returns || ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------- | --------------------------------------------------------------------------------------------------------------------------- |-| [`/api/x402/pump-launch`](#sec-392) | $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-392). |-| [`/api/x402/vanity`](#sec-571) | $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-571). |+| [`/api/x402/pump-launch`](#sec-407) | $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-407). |+| [`/api/x402/vanity`](#sec-591) | $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-591). || [`/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-074)); 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. |@@ -147139,10 +153766,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-617). |-| `/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-617). |-| `/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-617). |-| `/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-290). |+| `/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-638). |+| `/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-638). |+| `/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-638). |+| `/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-300). |## $THREE only@@ -147153,16 +153780,16 @@ input and do not promote any specific token.## Related-- [Pump Launcher](#sec-392) — the full launch flow, inputs/outputs, and the free `symbol` → launch → `launches` funnel.-- [x402 protocol](#sec-624) — the challenge/settle mechanics.-- [x402 buyer client](#sec-616) — how to pay these endpoints in code.-- [Financial controls](#sec-240): where settled payments are recorded.-- [Autonomous x402 loop](#sec-114) — the scheduled buyer that drives volume through these endpoints.-- [MCP tools](#sec-316) — the same capabilities exposed as paid MCP tools.+- [Pump Launcher](#sec-407) — the full launch flow, inputs/outputs, and the free `symbol` → launch → `launches` funnel.+- [x402 protocol](#sec-645) — the challenge/settle mechanics.+- [x402 buyer client](#sec-637) — how to pay these endpoints in code.+- [Financial controls](#sec-246): where settled payments are recorded.+- [Autonomous x402 loop](#sec-117) — the scheduled buyer that drives volume through these endpoints.+- [MCP tools](#sec-327) — the same capabilities exposed as paid MCP tools.----<a id="sec-620"></a>+<a id="sec-641"></a>> **Source:** `docs/x402-preflight.md` · [↑ table of contents](#table-of-contents)@@ -147361,13 +153988,13 @@ lines.## Related-- [docs/x402.md](#sec-624) walks the payment flow itself.-- [docs/mcp.md](#sec-318) covers connecting an agent to the three.ws MCP server.+- [docs/x402.md](#sec-645) walks the payment flow itself.+- [docs/mcp.md](#sec-329) 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-621"></a>+<a id="sec-642"></a>> **Source:** `docs/x402-ring-economy.md` · [↑ table of contents](#table-of-contents)@@ -148484,7 +155111,7 @@ activation runbook above is the fix.----<a id="sec-622"></a>+<a id="sec-643"></a>> **Source:** `docs/x402-solana-july-roundup-response.md` · [↑ table of contents](#table-of-contents)@@ -148502,7 +155129,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-594): `@trythreews` posts the institutional version, `@nichxbt`+[event-x-posts.md](#sec-615): `@trythreews` posts the institutional version, `@nichxbt`posts the human one. Do not post both within a few minutes of each other.---@@ -148543,7 +155170,7 @@ the specific claim the roundup credited us for. Second choice: the AR drop-in on----<a id="sec-623"></a>+<a id="sec-644"></a>> **Source:** `docs/x402-studio.md` · [↑ table of contents](#table-of-contents)@@ -148553,11 +155180,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-624) 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-645) 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-616) and the [paid endpoint catalog](#sec-619).+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-637) and the [paid endpoint catalog](#sec-640).## How it works@@ -148643,16 +155270,16 @@ const { tx_base64, blockhash } = await res.json();## Related-- [x402: paid agent skills](#sec-624): the payment protocol Studio sits on top of-- [Financial controls](#sec-240): where settled payments are recorded-- [x402 paid endpoints](#sec-619): the platform's own catalog of paid endpoints-- [x402 buyer client](#sec-616): the caller side of a 402 challenge-- [x402 developer tools](#sec-617) and [x402 distribution](#sec-618)+- [x402: paid agent skills](#sec-645): the payment protocol Studio sits on top of+- [Financial controls](#sec-246): where settled payments are recorded+- [x402 paid endpoints](#sec-640): the platform's own catalog of paid endpoints+- [x402 buyer client](#sec-637): the caller side of a 402 challenge+- [x402 developer tools](#sec-638) and [x402 distribution](#sec-639)- Pages: [/x402/studio](https://three.ws/x402/studio) · [/x402](https://three.ws/x402)----<a id="sec-624"></a>+<a id="sec-645"></a>> **Source:** `docs/x402.md` · [↑ table of contents](#table-of-contents)@@ -148666,7 +155293,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-619).+[x402 paid endpoints](#sec-640).**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.@@ -148822,20 +155449,20 @@ Each package has its own repository with a full README, API reference, and examp## Tutorials-- [Pay for an x402 service](#sec-525) — settle a paid request end to end with `@three-ws/x402-fetch`.-- [Build a paid x402 endpoint](#sec-524) — stand up a seller endpoint with `@three-ws/x402-server`.+- [Pay for an x402 service](#sec-545) — settle a paid request end to end with `@three-ws/x402-fetch`.+- [Build a paid x402 endpoint](#sec-544) — stand up a seller endpoint with `@three-ws/x402-server`.## Related-- [x402 paid endpoints](#sec-619) — the catalog of the platform's own paid endpoints.-- [Financial controls](#sec-240): where settled payments are recorded.-- [x402 buyer client](#sec-616) — how to settle a 402 challenge in code.-- [x402 bazaar over MCP](#sec-317) — discover and pay endpoints through the MCP bazaar.-- [Autonomous x402](#sec-114) — agents paying for services on their own.+- [x402 paid endpoints](#sec-640) — the catalog of the platform's own paid endpoints.+- [Financial controls](#sec-246): where settled payments are recorded.+- [x402 buyer client](#sec-637) — how to settle a 402 challenge in code.+- [x402 bazaar over MCP](#sec-328) — discover and pay endpoints through the MCP bazaar.+- [Autonomous x402](#sec-117) — agents paying for services on their own.----<a id="sec-625"></a>+<a id="sec-646"></a>> **Source:** `docs/zauth/database.md` · [↑ table of contents](#table-of-contents)@@ -148981,7 +155608,7 @@ Use this endpoint to browse all known x402 endpoints before your agents commit t----<a id="sec-626"></a>+<a id="sec-647"></a>> **Source:** `docs/zauth/index.md` · [↑ table of contents](#table-of-contents)@@ -149001,11 +155628,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-629)### [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-628)### [DatabaseLive registry of x402 endpoints. AI agents continuously test and verify endpoints, tracking success rates, pricing, and response data.Database](#sec-625)### [Provider HubManage your x402 endpoints. Monitor health, track agent interactions, configure refunds, and verify your services through our SDK.Provider Hub](#sec-627)+### [VectorAI-powered vulnerability scanner. Automated recon, multi-category exploit testing, and detailed security reports for your web applications.Vector](#sec-650)### [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-649)### [DatabaseLive registry of x402 endpoints. AI agents continuously test and verify endpoints, tracking success rates, pricing, and response data.Database](#sec-646)### [Provider HubManage your x402 endpoints. Monitor health, track agent interactions, configure refunds, and verify your services through our SDK.Provider Hub](#sec-648)----<a id="sec-627"></a>+<a id="sec-648"></a>> **Source:** `docs/zauth/provider-hub.md` · [↑ table of contents](#table-of-contents)@@ -149107,7 +155734,7 @@ Supply your EVM or Solana private keys to enable automatic refunds when your end----<a id="sec-628"></a>+<a id="sec-649"></a>> **Source:** `docs/zauth/reposcan.md` · [↑ table of contents](#table-of-contents)@@ -149433,7 +156060,7 @@ TypeScript -@x402/fetch----<a id="sec-629"></a>+<a id="sec-650"></a>> **Source:** `docs/zauth/vector.md` · [↑ table of contents](#table-of-contents)diff --git a/docs/announce-voice.md b/docs/announce-voice.mdindex 7126ed886..d58c3c5f0 100644--- a/docs/announce-voice.md+++ b/docs/announce-voice.md@@ -142,7 +142,7 @@ pack carries:- **The Telegram variant.** The community channel takes plain text and a different register: moredetail, no character ceiling worth worrying about, no tagging.- **The changelog entry**, ready to paste into `data/changelog.json`.-- **Its state**, mirrored in `data/announcements.json` (generated by `npm run announce:rank`, so it is gitignored; run that first if you do not have it).+- **Its state**, mirrored in [`data/announcements.json`](../data/announcements.json).## What this file does not decidediff --git a/docs/announcements/README.md b/docs/announcements/README.mdindex 443f7ee76..6d55eda4d 100644--- a/docs/announcements/README.md+++ b/docs/announcements/README.md@@ -18,8 +18,7 @@ npm run check:announce # gate the pack before anyone reads it1. **Rank.** [`scripts/announce-rank.mjs`](../../scripts/announce-rank.mjs) re-derives theinventory from `data/pages.json`, `packages/`, `workers/` and `services/`, reads the announcedstatus out of the coverage audit, probes each route, scores what is left, and writes- `data/announcements.json`. That ledger is generated, not committed, so this is the- command that creates it. The score's weights come from the+ [`data/announcements.json`](../../data/announcements.json). The score's weights come from theengagement archive, not from taste; the sources are named in[announce-voice.md](../announce-voice.md).2. **Capture.** Add a shot to [`data/announce-media.json`](../../data/announce-media.json) and rundiff --git a/public/atlas-index.json b/public/atlas-index.jsonindex 08e133083..78df8d3d9 100644--- a/public/atlas-index.json+++ b/public/atlas-index.json@@ -1 +1 @@-{"version":1,"pageCount":812,"intentCount":15,"sections":[{"id":"main","title":"Main","hint":"Entry points into the product."},{"id":"build","title":"Build","hint":"Create and customize an agent."},{"id":"labs","title":"Labs","hint":"Experimental features actively shipping. Expect fast iteration."},{"id":"crypto","title":"Crypto","hint":"On-chain features: pay-per-call, token launches, vanity wallets."},{"id":"agent-tools","title":"Agent Tools","hint":"Manage, talk to, and deploy individual agents."},{"id":"account","title":"Account","hint":"Sign-in, dashboard, billing."},{"id":"learn","title":"Learn","hint":"Docs, tutorials, and reference."},{"id":"blog","title":"Blog","hint":"Long-form announcements, launches, and writing from three.ws."},{"id":"legal","title":"Legal","hint":""},{"id":"machine","title":"Machine-readable","hint":"Indexes and well-known files for crawlers and AI agents."}],"pages":[["/","Home","Landing page. 3D AI agents that think on IBM watsonx.ai (Granite): the pitch, live agent demos, and the front door to every flow.","main",1,0],["/discover","Discover","On-chain agent directory (ERC-8004 + Solana). Browse, search, and inspect every registered agent.","main",0.9,0],["/gallery","Avatar Gallery","Every public 3D avatar in the system, browsable as a grid.","main",0.8,0],["/animations","Animation Gallery","Browse and preview public animations authored by the three.ws community. Apply any clip to your avatar in the Animation Studio.","main",0.8,0],["/gestures","Agent Gestures","The three.ws agent gesture vocabulary: every animation slot, the clip it plays, the skills that trigger it, and a builder for overriding any slot on your own...","main",0.7,0],["/choreograph","Choreographer","Compose agent gestures into a timed routine on a real timeline, preview the whole performance on a live 3D avatar, then save it to your agent and play it by...","main",0.7,0],["/character-library","Character Library","Professionally rigged 3D characters, free to use. Every one drives the full animation library and drops into the Studio, Animation Studio, and embed viewer.","main",0.8,0],["/sign-language","Sign Language Avatars","three.ws avatars sign in American Sign Language: fingerspell any word or number, get signed chat replies, and sign back with your webcam. The whole loop, live...","main",0.9,0],["/asl-alphabet","ASL Alphabet","The American manual alphabet on a live 3D avatar: every letter and number, what to look for, the look-alikes it is confused with, spell any word, and a drill...","main",0.8,0],["/sign-mirror","Sign Mirror","Learn the ASL alphabet by making it: the avatar forms the letter, your camera watches your hand, and the page grades the handshape live, naming the finger that...","main",0.8,0],["/objects","Object Library","Hundreds of free CC0 3D objects and props: furniture, lighting, electronics, decor. Public domain, no attribution required. Preview live, place it in your room...","main",0.8,0],["/forged","Agent-Forged Gallery","3D props bought by autonomous AI agents with real USDC over x402. Every asset carries its on-chain receipt: the paying agent wallet, the price, and the Solana...","main",0.7,0],["/wardrobe","Wardrobe","The open garment catalog for 3D avatars: browse every wearable, inspect it in 3D, and generate new pieces from a text prompt. Every piece binds to any humanoid...","main",0.7,0],["/diorama","Diorama","Speak a little world into being: describe a scene and watch it assemble into an explorable 3D diorama you can walk through, then take it into AR.","main",0.7,0],["/mocap-studio","Mocap Studio","Drive a 3D avatar with your webcam: real-time facial motion capture in the browser, no rig and no download.","main",0.7,0],["/autopilot","Coin Autopilot","A hands-off token cockpit. Set the rules (buys, sells, and guardrails) and let your agent run the coin autonomously.","main",0.7,0],["/drive","three.ws Drive","Your 3D agent in the car: voice-first, glanceable, and built to the rules CarPlay and Android Auto enforce. Runs on a head unit, a phone in the cradle, or...","main",0.7,0],["/agenc/embodied","AgenC · Embodied","Watch two AI agents negotiate and coordinate a task, embodied as 3D characters: the AgenC coordination protocol made visible.","main",0.6,0],["/agenc/room","AgenC · Task Room","A live room where autonomous agents discover open work, bid for it, and settle on-chain: the labor market up close.","main",0.6,0],["/create/video","Talking Avatar Video","Turn a three.ws avatar into a talking-head video: upload your audio and export a lip-synced clip.","main",0.6,0],["/temporary","Drive Your Avatar","Drive a 3D avatar around with a joystick or WASD, then toggle the back camera for AR-style passthrough on your phone.","main",0.7,0],["/irl","IRL","Pin a 3D AI agent at a real place and meet the ones around you. Walk up, see it through your camera, talk to it out loud, view it in AR on your own floor, and...","main",0.75,0],["/irl/sign","Printable IRL sign","Print a sign for a placed IRL agent: its name, thumbnail and a QR of the visit link. Scan it at the spot to open IRL, walk up, and meet the 3D AI agent in AR....","main",0.4,0],["/irl-privacy","How location works on IRL","Placed agents are private by location: they appear only to people physically standing near them, never on a map or a list. What's shared, what isn't, and how...","main",0.4,0],["/alpha-copilot","Alpha Co-pilot: your agent narrates its own alpha","Your 3D agent reads a real pump.fun launch in character, grounded in live liquidity, holder, and smart-money data, and speaks its verdict aloud. Fabricated...","main",0.8,0],["/world-lines","World Lines: agent proof-of-presence quests","Walk to an AI agent's real-world spot, complete its AR challenge, and earn a cryptographically real, agent-signed proof of presence. Privacy-preserving (only a...","main",0.7,0],["/marketplace","Marketplace","Buy access to agents, skills, and avatars from other creators.","main",0.8,0],["/marketplace/analytics","Marketplace Analytics","Real-time stats on the three.ws skill marketplace: top skills, top agents, and sales volume.","main",0.6,0],["/conversions","Trial Conversions","Both sides of the moment a metered free trial runs out: the trials you are holding with the runs you have left and the price to keep them, and the trials...","main",0.5,1],["/collection","My Collection","View all the skills and subscriptions you've unlocked on three.ws.","main",0.5,2],["/portal","Portal","Paste any web address and walk through it in 3D. Portal reads the page's real structure and builds a place from it: sections become buildings sized by what...","main",0.8,0],["/companion","Companion","A 3D companion that delivers your important messages in person. Connect your own Telegram bot, calendar, inbox, or phone, give each contact their own avatar...","main",0.7,0],["/knock","Knock","Put a price on reaching you. Anyone, a person or an agent, can pay it to get exactly one message through, and your 3D companion walks on screen and delivers it...","main",0.7,0],["/herald","Herald","Deliver a message in person: a 3D character walks onto your page and tells the user what happened. Open SDK, one line of code, an accessible fallback, and a...","main",0.7,0],["/notifications","Notifications","Every payment, sale, remix, follow, quest, and royalty notification on three.ws: all in one place, filterable by category.","main",0.5,2],["/skills","Skills Marketplace","Browse, search, and install agent skills: tool packs, knowledge bases, and capabilities that make AI agents smarter. Now lives inside the Marketplace; this...","main",0.8,2],["/community","Community","Live platform activity plus where to follow, contribute, and connect with three.ws creators.","main",0.6,0],["/crews","Crew HQ","Found a crew, invite your people, and watch the whole roster stand in one 3D headquarters. Every member appears as their own agent, lit when they are live in...","main",0.7,0],["/search","Search","One search across every creation type on three.ws: avatars, agents, 3D models, worlds, and coins. Remix a model straight from the results.","main",0.8,0],["/atlas","Atlas","The whole platform as one searchable map: every page grouped by what it is for, plus the task shortcuts the Cmd+K palette answers with. Press Cmd+K anywhere on...","main",0.7,0],["/sitemap","Sitemap","Human-readable index of every page on three.ws.","main",0.4,0],["/characters","Characters","Discover AI characters on three.ws. Chat, trade, and create.","main",0.8,0],["/what-is","What is three.ws?","Plain-English introduction to three.ws: what a 3D AI agent is, real use-cases, and where to begin.","main",0.8,0],["/pitch","Pitch Deck","The three.ws story as a presentable slide deck: one platform that gives any AI a real-time 3D body you can embed anywhere in one line. Arrow-key navigation, a...","main",0.6,0],["/timeline","The Story So Far","three.ws's history as an explorable 3D scene: every launch, partnership, listing, and milestone laid out along a path you can orbit in 360° or walk end to end...","main",0.6,0],["/tour","Guided Tour","A 3D guide walks across the live site, points at every feature, and narrates what each one does and how to use it: voice plus an on-screen chat bubble, paced...","main",0.7,0],["/tour/atlas","Tour Atlas","Every stop on the guided tour as a real screenshot of the live site, with the feature circled by the tour's own spotlight. Search 263 stops, filter by chapter...","main",0.6,0],["/walk","Walk Anywhere on the Web","Your 3D avatar walks anywhere on the web. Live demos across six environments, a Chrome extension, one-tag embeds, and a global distance leaderboard.","main",0.8,0],["/concierge","Concierge: AI Chat Widget","Give any website an AI concierge with a talking 3D avatar: one-tag embed, streaming answers grounded in the live page, voice in and out, themes, and an avatar...","main",0.8,0],["/feed","Feed","Live avatars, agents, 3D models, worlds, and launches across three.ws: filter to everyone or just the people you follow.","main",0.6,2],["/partners","Partner Ecosystem","three.ws partner ecosystem: OpenAI, IBM, AWS, Google Cloud, Alibaba Cloud, NVIDIA, Quicknode, HackerNoon. The AI, cloud, and infrastructure programs powering...","main",0.8,0],["/openai","three.ws is an OpenAI Select Partner","three.ws is an OpenAI Select Partner in the OpenAI Partner Network. Connect the free three.ws 3D Studio MCP server to ChatGPT and turn a prompt into an...","main",0.8,0],["/nvidia","three.ws on NVIDIA","three.ws is a member of the NVIDIA Inception program. Every 3D model, avatar, and voice on the platform runs on NVIDIA: a free hosted lane behind one API key...","main",0.8,0],["/press","Press kit","Logos, announcement graphics, boilerplate, and usage rules for three.ws. Every asset is downloadable and current, and editorial use needs no permission.","main",0.6,0],["/pricing","Pricing","Plans and pricing for three.ws: free forge quota, premium passes, and pay-per-use API surfaces.","main",0.8,0],["/showcase","Showcase","Browse every ERC-8004 agent that carries a 3D glTF body, indexed from canonical registries across 22 chains, and open any of them in the live viewer.","main",0.6,0],["/demos","Lab Demos","Index of live demos across the platform: viewers, agents, payments, and experiments.","main",0.6,2],["/demos/agents","Agent Interaction Lab","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...","main",0.5,2],["/assistant","Assistant widget","Put a 3D avatar assistant on any website with one script tag. A floating launcher opens a real animated avatar, against your page, a color, or a gradient, with...","build",0.8,0],["/embed-doctor","Embed Doctor","Find out why your 3D agent embed is not showing up. Paste your page URL and we load it in a real browser, watch the embed try to boot, and name the exact line...","build",0.8,0],["/agora","Agora: the Commons","A watchable 3D world where AI agent and human citizens live, work, and earn $THREE. Walk the square, inspect any citizen's passport, and watch the economy come...","build",0.8,0],["/start","Get Started","5-step onboarding wizard: create a 3D avatar, name your agent, enable skills, deploy an embed widget, and set up monetization: all in under 5 minutes.","build",1,2],["/create","Create","The front door for everything you can create on three.ws: build an AI agent, make a 3D avatar (from a photo, from scratch, from a text prompt, or a file)...","build",0.9,0],["/genome","Agent Genome: breed two agents","Breed two AI agents into a provably-inherited offspring. The child inherits a recombination of both parents' brain, voice, body, and on-chain skill licenses...","build",0.8,0],["/genesis","Instant Agent Genesis","A prompt or a selfie becomes a rigged 3D AI agent with its own custodial Solana + EVM wallet and a verifiable on-chain identity: in under a minute, owned by...","build",0.9,0],["/create-agent","Create an Agent","Step-by-step wizard to create a 3D AI agent: name, 3D body, skills, personality, voice, and on-chain identity.","build",0.9,0],["/agent-screen","Agent Screen","Watch your agent work in real time: split view with the agent's live screen on the left and their 3D avatar rendered as a webcam on the right.","build",0.5,3],["/agents-live","Live Agents","Mission control: real-time grid of all AI agents with active screen streams. Watch their screens and avatar feeds live.","build",0.5,0],["/monitor","Agent Monitor","Ops-room dashboard for the 3D AI agent fleet: live agent activity with a 3D spotlight, on-chain money pulse, agent-to-agent hires, coin launches, the community...","build",0.5,0],["/agent-studio","Agent Studio","Author your agent's brain, memory, body, money, and skills in one place, with a live 3D avatar that updates everywhere as you edit.","build",0.5,3],["/app","Viewer","Drag-and-drop glTF/GLB viewer for inspecting 3D models in the browser.","build",0.7,0],["/create/prompt","Describe it to 3D","Type a description. About a minute later: a rigged 3D avatar you can animate and download.","build",0.9,0],["/forge","Forge: Text & Image to 3D","Type a prompt, or drop in photos or a sketch, and get a downloadable textured 3D model (GLB). Pick from multiple generation engines with live health status.","build",0.9,0],["/image-to-3d","Image to 3D: Turn a Photo into a 3D Model","Upload a photo (or up to 6 angles) and get a downloadable textured 3D model (GLB). The Forge's photo lane, opened directly: for objects and props; for faces...","build",0.9,0],["/forge-max","Forge Max: Highest-Quality Text & Image to 3D","The Forge's maximum-quality lane, opened directly: High tier pinned (200k-poly geometry, 4K PBR and HD textures, subject-aware engine routing). A $THREE holder...","build",0.9,0],["/restyle","Restyle Studio: material presets, AI restyle & variants","Re-skin any 3D model in the browser: apply PBR material presets (chrome, gold, glass, wood…), restyle from a plain-language AI instruction, fan out seeded...","build",0.8,0],["/avatar-engines","Avatar Engines Atlas","A curated, factual atlas of the open-source and commercial engines that build high-quality and photoreal 3D human avatars: Gaussian-splat heads, single-photo...","build",0.7,0],["/splat","Splat Viewer: Photoreal Gaussian Avatars","Render Gaussian-splat and radiance-field avatars in the browser: the photoreal output of engines like GaussianAvatars and HumanGaussian. Load a .ply / .splat /...","build",0.7,0],["/capture","Scene Capture: Video to 3D Point Cloud","Turn a phone video of any space into an explorable 3D point cloud. Streaming feed-forward reconstruction (LingBot-Map Geometric Context Transformer) fuses the...","build",0.7,0],["/motion-swap","Motion Swap: Replace Yourself in Video with Your Avatar","Upload a video of yourself and get it back with your 3D avatar performing your motion instead of you. Server-side pose tracking and person masking...","build",0.7,0],["/forge-nim","Forge · NIM: Self-Hosted Image to 3D","Drive a self-hosted TRELLIS NIM (nvcr.io/nim/microsoft/trellis) directly: drop a photo, hit /v1/infer, and get the textured GLB back synchronously as base64...","build",0.7,0],["/forge-spark","Text → 3D: Nemotron → FLUX → TRELLIS","Describe an object and watch it become a textured 3D mesh: Nemotron sharpens the prompt, FLUX paints a clean reference, and TRELLIS reconstructs the model...","build",0.7,0],["/forge-studio","Studio: Object + Avatar from text","One canvas for both text-to-3D pipelines: forge a textured object (GLB) in the Object tab, or describe a character and get a rigged avatar in the Avatar tab.","build",0.8,0],["/cosmos","Cosmos: Living Worlds","Bring your avatar to life: type a world and NVIDIA Cosmos renders a living, photoreal scene that plays behind your 3D avatar. Generate, preview, and download a...","build",0.8,0],["/scene","Scene Studio","Full 3D scene editor in the browser: import GLB models, arrange them with transform gizmos, edit materials and lights, and export complete scenes.","build",0.8,0],["/compose","Scene Composer","Real-time 3D scene composer: forge items from text, attach them to your avatar's skeleton bones, arrange and scale freely, then export your creation or save it...","build",0.9,0],["/pose","Animation Studio","Pose any three.ws avatar or the built-in mannequin with FK/IK, keyframe a timeline, and preview the motion live. Export an animated GLB or clip JSON, save...","build",0.9,0],["/validation","glTF Validator","Khronos-spec validator for glTF/GLB files. Paste a URL or upload a model.","build",0.6,0],["/studio","Widget Studio","Build an embeddable 3D widget: pick an avatar (or your own model URL), pick a widget type, tune it live, and copy the snippet. No account needed for the...","build",0.8,2],["/artifact","Artifact Viewer","Renders Claude artifact bundles as standalone embeddable apps.","build",0.5,0],["/docs/create-agent","create-agent: one command, one 3D character","npm create @three-ws/agent turns a sentence into a rigged, downloadable 3D character with a working demo page. No account, no API key.","build",0.6,0],["/docs/brownout","Brownout: proven fallbacks, not promised ones","Every response says where its data came from and how fresh it is, and every fallback the API claims has been executed for real against a genuinely refusing...","build",0.6,0],["/docs/portal","How Portal builds a 3D world from a URL","Paste a web address and Portal builds a place out of it: sections become buildings sized by what they say, links become doors you step through, images become...","build",0.6,0],["/docs/glance","Glance: agent cards for home screens","Put a three.ws agent on the Windows 11 widgets board, in a README, in Slack, on a page, or in your terminal. Endpoint, element, widget worker and npm client.","build",0.6,0],["/docs/native-widgets","Native widgets: your agent on the home screen","Put your three.ws agent on an Android home screen (and the Windows 11 widgets board): what the widget shows, how to link and revoke it, every state it can be...","build",0.6,0],["/glance","Glance","Your three.ws agent on every home screen: a live card for the Windows 11 widgets board, a README, Slack, or any page.","build",0.7,0],["/widgets","Widgets Gallery","Pre-built chat, voice, and 3D-avatar widgets you can drop into any page.","build",0.7,0],["/hydrate","Hydrate","Take an existing on-chain agent (ERC-8004 / Solana) and attach a 3D body, voice, and skills.","build",0.7,0],["/integrations","Integrations","Drop-in 3D agents, chat widgets, walk companions, and live token embeds for any site. One script tag. Powered by three.ws.","build",0.8,0],["/features","Features","Full feature overview of the three.ws platform: avatars, agents, on-chain identity, x402 payments, and embedding.","build",0.8,0],["/features/ar","AR & WebXR: Place Any 3D Agent in Your Real World","Every three.ws avatar and Forge model has a View in AR button. On mobile it anchors the model to real surfaces through your camera. WebXR on Android, Quick...","build",0.8,0],["/features/forge","Forge: Text & Image to 3D Models","Type a description or upload photos, and get a downloadable textured 3D model (GLB). Multiple self-hosted engines, from fast drafts to PBR realism.","build",0.8,0],["/features/scan","Scan: Selfie to 3D Avatar","Point your camera at your face, hold still, and walk away with a rigged 3D avatar in 60 seconds. Free, in your browser.","build",0.8,0],["/features/play","Play: Live 3D Coin Worlds","Every pump.fun coin gets a deterministic 3D world. Walk in as your avatar, chat with holders, and trade: all in the browser.","build",0.8,0],["/features/walk","Walk: 3D Avatar AR","Drive your AI agent's 3D avatar with WASD or joystick. Toggle AR mode and it walks on your real floor through your phone camera.","build",0.8,0],["/features/studio","Studio: Embeddable AI Widget Builder","Configure avatar, voice, and knowledge base in the Widget Studio, then copy one script tag to embed a 3D AI agent anywhere.","build",0.8,0],["/features/marketplace","Marketplace: Discover and Fork AI Agents","Browse hundreds of community-built AI agents with 3D avatars and on-chain identities. Fork any agent, buy paid skills, and ship in minutes.","build",0.8,0],["/features/agent-exchange","Agent Exchange: AI Agents Paying Each Other","Watch two AI agents with 3D avatars autonomously negotiate and pay each other for crypto intelligence via x402 micropayments on Solana.","build",0.7,0],["/features/deploy","Deploy: On-Chain Agent Identity","Register your AI agent on Solana via ERC-8004 and Metaplex Core. Permanent, verifiable identity: discoverable by any wallet or other agent.","build",0.8,0],["/create/selfie","Selfie to Avatar","One selfie. About a minute. A rigged 3D avatar that works everywhere.","build",0.7,0],["/seeker","three.ws for Seeker","The home screen of the three.ws app on Solana Seeker: one-tap Seed Vault sign-in, selfie to avatar, your agents, the marketplace, and Seeker Genesis Token...","build",0.6,0],["/import/rpm","Import an avatar URL","Import any GLB or glTF avatar into three.ws and give it an agent brain.","build",0.6,2],["/threews/claim","Claim threews.sol Subdomain","Claim your own <name>.threews.sol subdomain and get a Brave-resolvable personal showcase page.","build",0.6,0],["/voice/home","Hands-free voice for your home","Talk to your house without finding a phone: a wake word matched on your own device, real barge-in mid-sentence, and a spoken confirmation that a background yes...","build",0.7,0],["/voice","Voice Lab","Browse hundreds of voices across Microsoft Edge, Gemini, NVIDIA, OpenAI and ElevenLabs, preview any of them, or clone your own from a short recording, then...","build",0.7,0],["/dad","Make Dad a 3D Avatar","Turn one photo of your dad into a recognizable, rigged, animated 3D avatar. It idles, walks, and waves, and you can share a permalink.","build",0.7,0],["/ca2x402","CA → x402","Paste any token contract address and get a live, agent-payable x402 endpoint for its market intel (price, momentum, and a bullish/bearish signal) for $0.01...","build",0.7,0],["/avatar-studio","Avatar Studio","Build a custom 3D avatar from scratch. Sculpt the face and body, dress it from the closet, add accessories, and walk it around the stage. No selfie required.","build",0.7,0],["/nim-forge","TRELLIS NIM Forge","Drop in a photo, get a textured 3D model, reconstructed on a self-hosted Microsoft TRELLIS NIM. Single-hop image to GLB.","build",0.6,2],["/avatar-sdk","Avatar SDK","The @three-ws/avatar package: embed the platform 3D avatars in any site with a few lines of JavaScript.","build",0.6,0],["/materialize","Materialize","Turn any 3D model into a real printed object. Live printability analysis and automatic repair, a true-scale AR preview on your own desk, an itemized price from...","build",0.8,0],["/smart-home/join","Join a home","Accept an invitation to somebody's connected home. The link says which home it is, exactly what your role would let you do there and what it would never let...","build",0.4,2],["/smart-home/privacy","Your home data","Everything three.ws stores about the homes you connected, with why it exists and how long it stays. Set how long your action log lives and watch the old...","build",0.5,0],["/smart-home/plan","Home plan","What your plan covers for connected homes: homes, household seats, live screens, voice minutes and agent turns, each with what you have used and when it...","build",0.6,0],["/smart-home","Smart home","Connect a Home Assistant house to your three.ws agent. Your agent reads every room and device, runs the scenes you already built, and stops to ask before it...","build",0.8,0],["/smart-home/satellite","Voice satellite","Give your existing Home Assistant voice assistant a face. Pair a three.ws satellite and the same pipeline you already use gains a 3D agent that lip-syncs its...","build",0.7,0],["/inspect","Model Inspector","Run the exact quality gate three.ws applies to its own catalog against any .glb, in your browser. Nothing is uploaded. Per-rule verdict, what was measured...","build",0.7,0],["/avatar-cli","Avatar CLI","The @three-ws/avatar-cli package: scaffold a hash-anchored avatar manifest from a wallet and a GLB, validate it against the schema, and print an embed snippet....","build",0.6,0],["/render-lab","Render Lab","Compose a real avatar render in the browser and copy the exact API call. Reads each model first (ARKit morph targets, canonical-skeleton coverage, geometry)...","build",0.8,0],["/diff","Model Diff","Drop two .glb files and see exactly what changed: geometry, materials, textures, skeletons and animation clips, with git-style rename and move detection and a...","build",0.7,0],["/rig-doctor","Rig Doctor","Drop a .glb and find out in one second whether it will animate on three.ws. Names your skeleton convention, scores every limb group against the 52-joint...","build",0.6,0],["/bundles","Skill Bundles","Sell several of an agent's skills as one purchase, priced from your own sales instead of a rule of thumb. three.ws finds the buyers who already bought two or...","build",0.6,0],["/tty","Terminal renderer","curl three.ws/tty and a rigged 3D agent walks in your terminal. A software rasterizer streams ANSI frames over HTTP: no GPU, no WebGL, nothing to install. Also...","build",0.6,0],["/stream","Progressive Avatars","A3S packs a GLB into nested layers whose first 50 KB is already a complete, skinned, spec-valid avatar, then refines it in place over plain HTTP range...","build",0.6,0],["/docs/animation-seeding","Generated animation seeding","How three.ws generates its own animation clips: the text-to-motion GPU lane, the world-space quality gate that judges joint positions instead of raw rotations...","build",0.6,0],["/docs/robinhood-portfolios","Docs · Robinhood Portfolios","How Robinhood Portfolios works: the manifest that makes a generated basket binding, in-kind issuance that needs no price oracle, the descending-price rebalance...","build",0.6,0],["/globe","Global Intel Globe","A live 3D globe of what is happening on Earth right now: armed conflict, force posture, sanctions, natural events, severe weather, internet outages and...","labs",0.7,0],["/assembly","Machine Atlas","A radial aero engine and a steam locomotive generated in the browser from code, with no 3D model files: solved linkages, live dimensions, explode views and a...","labs",0.7,0],["/launchpad","Launchpad Studio","Build a hosted 3D launchpad, token page, concierge, or showroom on a three.ws subdomain.","labs",0.7,0],["/brain","Multi-LLM Brain","Send one prompt to Claude, GPT, Qwen, ModelScope, and Groq simultaneously. Side-by-side streaming with latency and token stats.","labs",0.7,0],["/lipsync","Lipsync (TTS)","Type text, stream it through the avatar's voice, and the mouth animates in real time via wawa-lipsync viseme detection.","labs",0.6,0],["/lipsync/mic","Lipsync (Mic)","Feed live mic audio through the viseme analyser and watch the avatar's mouth track your voice in real time.","labs",0.6,0],["/avatar-artifact","Avatar Artifact","Standalone Three.js viewer for avatar artifacts: embeddable and shareable without any wrapper page.","labs",0.5,0],["/viewer","glTF / GLB Viewer","Preview any public glTF/GLB inline, then take it further: pose and animate it, restyle the material, build a scene, place it in AR, embed it on your site, or...","labs",0.5,2],["/watch","Generation Watch","Live progress page for a running text-to-3D generation: real countdown, the painted concept art, and an automatic hand-off into the interactive viewer the...","labs",0.4,2],["/ar","AR Forge","Type a prompt, get a real 3D model, and place it in your room: free text-to-3D with one-tap AR on any phone (WebXR, Scene Viewer, Quick Look) and a QR handoff...","labs",0.7,0],["/ar/studio","AR Studio","A live multi-model AR scene through your camera: place any number of 3D models and avatars in your real space, pull in your forge creations, community models...","labs",0.7,0],["/ar/view","View in AR","Place any three.ws GLB in your real space from a plain link: real ARKit Quick Look on iPhone (a genuine on-device USDZ conversion, not a camera overlay), Scene...","labs",0.3,2],["/daily","Daily Forge","A new 3D creative challenge every day. Forge today's theme into a real 3D model, free and no sign-up, build a daily streak, and place your creation in AR on...","labs",0.8,0],["/spatial-mcp","Spatial MCP: reference renderer","The open standard for returning a live, interactive 3D scene as a first-class MCP tool result, with a framework-free reference renderer that displays any...","labs",0.5,0],["/playground","Playground","Sandbox for experimenting with agents, prompts, and 3D scenes.","labs",0.5,0],["/labs","Labs Showcase","A curated gallery of three.ws's most powerful (and most hidden) features. Find and try things you didn't know existed.","labs",0.8,0],["/rankings","Rankings","The cross-surface three.ws leaderboard: creators ranked by real creations, remixes received, coin launches, followers, and distance walked. Track your streak...","labs",0.7,0],["/daily-match","Daily Match","Which agent ships the most real output today? Live daily standings over real agent activity: actions, trades, skill sales, and coin launches. Resets at 00:00...","labs",0.7,0],["/walk-leaderboard","Walk Leaderboard","Global leaderboard for the walking avatar: distance walked, sites visited, and time, ranked daily, weekly, and all-time.","labs",0.6,0],["/galaxy","Agent Galaxy","Every public agent embedded by IBM Granite on watsonx.ai into a navigable 3D constellation with natural-language semantic search.","labs",0.6,0],["/symphony","Agent Symphony","The agent economy, played live as generative music. Every real payment, trade, launch and level-up on three.ws becomes a synthesized note in real time; record...","labs",0.6,0],["/economy-lab","Runway Lab","A live digital twin of the three.ws x402 payment rail. Runs the exact admission-control code the production settle path runs, seeded with live production...","labs",0.7,0],["/holo","Holo Sticker","A live holographic foil sticker rendered in your browser: tilt it with your pointer, peel the corner, switch foils, die-cut your own text, and download the...","labs",0.6,0],["/cz","Claim the CZ agent","Connect a wallet, sign one line, and take ownership of the pre-registered CZ agent, then copy its embed snippet.","labs",0.5,0],["/pocket","Pocket Console","A handheld console with a live 3D agent inside the screen. Steer it with the D-pad, swap cartridges for any public agent, and embed the whole console anywhere...","labs",0.7,0],["/go","GO Bounty Board","Post a bounty with a SOL reward, submit proof of doing it, and let the poster (or the AI judge) pick a winner. Live earner and spender leaderboards.","crypto",0.7,0],["/sperax","Sperax on three.ws","Free AI credits for three.ws users on chat.sperax.io: what the integration is and how to claim it.","crypto",0.5,0],["/agi","The AGI: narrow by design","The first AGI, narrow by design: a single autonomous agent that is genuinely superhuman at one thing, trading memecoins on pump.fun (Solana), and deliberately...","crypto",0.95,0],["/oracle","Oracle: AI Conviction Engine","A fused AI conviction engine for every pump.fun launch: pedigree (who's buying), structure (bundle vs organic), narrative (what story is it riding), and...","crypto",0.9,0],["/oracle-lab","Oracle Lab: the model, published","The Oracle's conviction model in full: every bucket weight with the number of labeled launches behind it and what happened to them, the held-out reliability...","crypto",0.8,0],["/oracle/docs","Oracle Docs: the conviction engine, end to end","The complete Oracle reference: the thesis behind fused pump.fun conviction, the four-pillar scoring model and its exact math, the data pipeline and worker...","crypto",0.75,0],["/oracle/arm","Arm your agent: automate Oracle conviction","Configure your 3D agent to trade Oracle conviction automatically: set the minimum score, position size, daily and open-position caps, narrative filters and...","crypto",0.8,0],["/activity","Agent Activity: Oracle conviction in real time","The trading floor: every Oracle conviction action from every autonomous 3D agent on pump.fun, live. Filter by tier and mode, track outcomes, and copy the...","crypto",0.8,0],["/pipeline","Recording Pipeline: the data loop, live","One-glance health of the closed loop that turns every pump.fun launch into a trade signal: the launch recorder, signal intel, ground-truth outcomes, Oracle...","crypto",0.7,0],["/guardian","Guardian console: recover & inherit agent wallets","The agents you’re trusted to protect. Approve a recovery or confirm an inheritance to help a fellow human back into their funded agent wallet: through a...","crypto",0.6,0],["/launch","Launch a Coin","Mint a coin for your 3D AI agent in one flow: pick an agent, set the name, symbol, and image, then launch on pump.fun straight from your wallet with an...","crypto",0.8,0],["/launch-studio","Launch Studio: 50 ways to mint a coin","A catalog of 50 coin-launch use cases: reward coins for trending GitHub repos and creators, and coins riding live cultural, news, and onchain narratives....","crypto",0.8,0],["/launches","Agent Launches","Live public feed of every coin launched by a three.ws agent: market caps, graduation status, and the agent behind each launch.","crypto",0.8,0],["/drops","3D Drops","Launch a supply-capped collection of AI-forged 3D characters. Pick a style, define weighted trait layers, and three.ws rolls the whole supply from a published...","crypto",0.8,0],["/minted","Minted 3D Assets","Live public gallery of every generated 3D avatar minted as a Metaplex Core NFT through three.ws: interactive viewer, baked provenance, and enforced creator...","crypto",0.7,0],["/cert","Print Certificates","Check the certificate of authenticity that ships with every three.ws physical print. Scan the code on the box or type the certificate number to see the...","crypto",0.6,0],["/creations","Creator Gallery","Search, filter, and live-preview the remix bazaar: remix any published 3D creation for a real on-chain USDC royalty, view parent → child lineage, and see the...","crypto",0.7,0],["/theater","Live Trading Theater","Watch agents trade in 3D, in real time. Every trader is a 3D character with a wallet and a verifiable on-chain reputation: when a real on-chain buy fills, its...","crypto",0.8,0],["/pulse","Money Pulse","The Money Pulse: a real-time, platform-wide feed of three.ws agent wallet activity: tips landing, coins launching, agents trading and paying each other. Every...","crypto",0.8,0],["/flow","Money Flow Map","The shape of the agent economy: a live force-directed map of who pays whom, for which skill, and how much. Every edge is a real settled on-chain transfer...","crypto",0.8,0],["/fits","Fits: the cosmetics economy","The live cosmetics economy: the scarcest premium fits ranked by how few wallets own them, the top collectors wearing them, the creators actually getting paid...","crypto",0.6,0],["/receipts","Receipt Vault","Every x402 payment you ever made to three.ws, retrievable forever. Connect a Solana or EVM wallet, sign one read-only message, and get back every signed...","crypto",0.6,0],["/viability","Viability","The honest signal behind three.ws: real marketplace and trading viability. Live $THREE skill GMV, take-rate, repeat buyers and trading pairs, plus real guarded...","crypto",0.8,0],["/deployments","On-chain Deployments","A live, cross-chain feed of every agent registered on the ERC-8004 Identity Registry: the moment each registration lands on-chain. Real on-chain registrations...","crypto",0.8,0],["/deploy-onchain","Deploy On-chain","Mint your agent into the Metaplex Agent Registry on Solana, in the exact shape the Genesis 333 shipped: a Metaplex Core asset with its own wallet, EIP-8004...","crypto",0.8,0],["/portfolio","Wallet Portfolio","A live portfolio view for any Solana or Ethereum wallet: total value, 24h move with honest coverage, stablecoin/major/token breakdown, top-asset allocation...","crypto",0.8,0],["/airdrops","Airdrop Checker","Check any Solana or Ethereum wallet against tracked airdrop criteria: a real on-chain activity scan, a 0-100 eligibility score per program, exactly what is...","crypto",0.8,0],["/launcher","Memetic Launcher","Your personal autonomous coin launcher: set your mode (trend, meme, hybrid, random), pick trend sources, tune your cadence, preview what your agents would...","crypto",0.8,2],["/clash","Coin Clash","Token-gated community warfare. Every coin community is an army: hold the coin, enlist, and rally for your faction in timed battles against other communities.","crypto",0.7,0],["/leaderboard","Trader Leaderboard","Pump.fun traders ranked by a provable, on-chain track record: realized P&L, win rate, and drawdown, with every number traceable to its transaction.","crypto",0.8,0],["/tracker","KOL Tracker","Solana crypto KOLs ranked by realized P&L computed from their own wallet's on-chain trade history, with win rate, volume, trade count, and X follower counts...","crypto",0.8,0],["/proof","Verify Custody","Verify your own three.ws agent wallet's custody: recompute your Merkle leaf, walk the path, and confirm it against the root anchored on Solana, entirely in...","crypto",0.5,3],["/labor-market","Agent Labor Market","A live machine economy: agents post bounties, bid on each other's work, and settle in $THREE on-chain: escrowed, verified, and royalty-routed, with no human in...","crypto",0.8,0],["/vaults","Back-an-Agent Vaults","Copy-trade a 3D agent with a verifiable on-chain reputation: stake into a verified trader, share its real P&L pro-rata, and watch it trade your capital live...","crypto",0.8,0],["/signals","Signal Marketplace: paid alpha feeds, ranked by proven edge","Verified traders publish their live entry/exit signals as x402-metered feeds. Your agent pays per signal or per epoch in USDC and auto-mirrors the trade...","crypto",0.8,0],["/dashboard/capabilities","Capabilities: Alpha Hunt, Launcher, Auto-Claim & Market Maker","Live command center for all 4 autonomous agent capabilities: Alpha Hunt smart-money scoring, autonomous Coin Launcher on schedule, Creator Auto-Claim for fee...","crypto",0.7,2],["/arena","The Arena: live PvP trading tournaments","Time-boxed PvP tournaments where AI agents compete on real, verified pump.fun P&L. Live rankings, on-chain attested standings, and $THREE prizes for the...","crypto",0.8,0],["/trending","Trending: Top Agents & Coins on three.ws","What’s hot on three.ws right now. Top 3D AI agents ranked by real chat activity and top Oracle conviction coins by score, with 24h/7d/all-time windows.","crypto",0.8,0],["/trades","Live Trade Feed: Notable pump.fun Exits","Real-time feed of every notable pump.fun exit from three.ws AI agents: realized PnL, hold time, exit multiple, conviction tier, and a one-click path to copy...","crypto",0.8,0],["/claim-wallet","Claim Your Wallet: Verified pump.fun Track Record","Paste your Solana wallet to see your provable pump.fun track record: win rate, smart-money score, reputation label, and coin history. Sign in to claim it as...","crypto",0.8,0],["/ghost-copy","Ghost-copy: what if you'd copied them?","Paper-copy any verified pump.fun trader agent with fake money over their real closed on-chain trades. Pick a leader, a budget and a window, and see the equity...","crypto",0.7,0],["/wrapped","Trader Wrapped: your season on pump.fun","The season recap for any verified pump.fun trading agent on three.ws: realized profit and loss, the trade that carried the season, the trade that hurt, the...","crypto",0.7,0],["/meta-allocator","Meta-Allocator: the ETF of degens","Do not pick a coin, pick a basket of proven traders. The Meta-Allocator spreads a budget across the top verified pump.fun trader agents, ranked by...","crypto",0.7,0],["/clip-director","Clip Director: every trade becomes content","Turn any trader agent's real closed pump.fun trade into the optimal shareable card per surface (X, Telegram, or the in-app Feed): an honest hook, the real...","crypto",0.7,0],["/pay","Pay (x402)","Pay-per-call gateway: invoke any x402-protocol paid API with a USDC micro-transaction.","crypto",0.9,0],["/x402/studio","x402 Studio: the Stripe of x402","Merchant console to run a paid x402 business: products and pricing, payout and agent wallets, a real USDC send/receive with SNS .sol resolution, a...","crypto",0.7,0],["/play/agent-wallet","Agent Wallet (x402 on Solana)","Watch your 3D avatar walk up to a paid endpoint and pay for it with its agent wallet: a real USDC micropayment signed by the agent and settled on Solana.","crypto",0.7,0],["/play/arena","Sniper Arena: autonomous AI agents trading live","Watch three.ws AI agents trade pump.fun autonomously in real time. Live P&L leaderboard, each trade signed by the agent's own wallet and verifiable on-chain.","crypto",0.8,0],["/play/war","Coin Wars arena: two communities, one battlefield","The live Coin Wars arena. Enlist at your coin world's war portal, fight the rival community to the kill cap, and the result lands on the Elo ladder. You fight...","crypto",0.7,0],["/sniper/experiments","Sniper Experiments: rules vs LLM judgment, scored live","The sniper fleet runs different rule sets side by side, including LLM-judged agents with no rules at all. The live scoreboard of which entry conditions...","crypto",0.7,0],["/play/ufo","Flappin UFO: retired demo","The Flappin UFO arcade demo ran on an external deployment that is no longer online, so the game has been retired. The page now points visitors to the live...","crypto",0.3,0],["/smart-money","Smart Money Radar: follow the wallets that win on pump.fun","A live first-party reputation graph of every pump.fun wallet. We cross each coin's buyers with the coins that actually graduated, so you can see which wallets...","crypto",0.8,0],["/pumpfun","Pump.fun Stream","Mint and trade pump.fun agent tokens on Solana. Live feed of every launch.","crypto",0.8,0],["/pump-live","Pump Live","Real-time feed of every pump.fun launch as it happens, with a 3D agent that reacts live.","crypto",0.7,0],["/terminal","Mission Control","The real-time pump.fun trading terminal: the live launch firehose fused with intel scores, firewall verdicts, and smart-money flow, your streaming positions...","crypto",0.85,0],["/radar","Coin Radar","Live pump.fun launch intelligence: every new coin scored in its first ~90 seconds: bundle vs organic, wallet concentration, dev behaviour, and risk flags from...","crypto",0.8,0],["/watchlist","Watchlist","Your privately-stored watchlist of pump.fun coins: live market caps, graduation status, and quick links to full coin profiles. No account required; stored in...","crypto",0.7,0],["/pump-dashboard","Pump Dashboard","Pump.fun trading desk: watchlists, scanner, quotes, portfolio, and live charts.","crypto",0.8,0],["/strategy-lab","Strategy Lab","Write a pump.fun trading strategy as data, backtest it against real on-chain history, then run it live through your agent's wallet.","crypto",0.7,0],["/recurring","Recurring Payments","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...","crypto",0.7,0],["/strategies","Strategy Objects","A marketplace of how agents trade: ownable, forkable, leaderboard-ranked trade strategies your agent can equip and run on-chain within your spend policy.","crypto",0.8,0],["/vanity-wallet","Solana Vanity Wallet","Grind a Solana address with a custom prefix: entirely in your browser, across your CPU cores. Also send sealed wallet gifts: fund a fresh (optionally...","crypto",0.6,0],["/fact-check","Fact Check","Sourced fact-checking with cryptographic attestations: a published, checkable accuracy benchmark plus a live free-check box. 3 free checks/day per IP, then...","crypto",0.7,0],["/vanity/verify","Verify a Vanity Receipt","Independently verify a three.ws provably-fair vanity wallet receipt: entirely in your browser. Prove the key was generated fresh under a committed seed and the...","crypto",0.6,0],["/vanity/gallery","Proof-of-Grind Gallery","A public gallery and leaderboard of the rarest Solana vanity addresses ground on three.ws: each provably-fair, verified, and shareable. Appraise any address to...","crypto",0.6,0],["/vanity/premium","Premium Vanity Inventory","Buy a long, brandable Solana vanity address delivered instantly from stock: 4-5+ character prefixes the live grinder can't reach, ground ahead of time on batch...","crypto",0.6,0],["/vanity/bounties","Grind-Bounty Market","A decentralized x402 bounty market for hard Solana vanity addresses: escrow a USDC bounty and a fleet of independent workers grinds it in parallel. The first...","crypto",0.6,0],["/eth-vanity","ETH Vanity (CREATE2)","Grind a vanity smart-contract address using the ThreeWSFactory CREATE2 deployer on BSC.","crypto",0.6,0],["/pump-visualizer","Pump Visualizer","3D visualizer of trending pump.fun tokens: live market data rendered as an interactive scene.","crypto",0.7,0],["/coin-intel","Coin Intelligence","Every pump.fun launch watched and classified in real time: organic vs bundle, the wallets behind it, a transparent quality score, and a model that learns which...","crypto",0.8,0],["/coins","Coins: Live Prices & Market Caps","Live global cryptocurrency market data: total market cap, dominance, Fear & Greed, and the top coins with prices, 24h/7d moves, and 7d sparklines. Every coin...","crypto",0.8,0],["/heatmap","Crypto Market Heatmap","A live market heatmap of the top cryptocurrencies: every tile is a coin, sized by market cap and colored by its 24h or 7d price move. See where money is...","crypto",0.7,0],["/fear-greed","Crypto Fear & Greed Index","The Crypto Fear & Greed Index: live market sentiment from 0 (Extreme Fear) to 100 (Extreme Greed), shown on a gauge with a week-over-week delta, a full...","crypto",0.7,0],["/gas","Ethereum Gas Tracker","Live Ethereum gas fees straight from the chain: slow, standard, and fast tiers in gwei with USD cost estimates for transfers, token sends, DEX swaps, and NFT...","crypto",0.7,0],["/compare","Compare Crypto Side by Side","Compare cryptocurrencies head to head: overlay normalized price performance and line up market cap, volume, FDV, supply, and all-time-high stats for up to four...","crypto",0.7,0],["/screener","Crypto Token Screener","Screen the top 250 cryptocurrencies with live filters: search by name or symbol, isolate gainers or losers, and set minimum market cap and 24h volume...","crypto",0.7,0],["/categories","Crypto Categories by Market Cap","Every crypto sector ranked by market cap: smart contract platforms, AI agents, memecoins, DeFi, gaming, and more, with 24h change, volume, and the top coins in...","crypto",0.7,0],["/exchanges","Top Crypto Exchanges","The leading cryptocurrency exchanges ranked by trust score and 24-hour trading volume, with country, launch year, and a direct link to each. Real CoinGecko...","crypto",0.7,0],["/derivatives","Crypto Derivatives & Perpetual Futures","Live perpetual-futures markets across exchanges: price, 24h change, funding rate, open interest, and volume for every major contract. Filter by underlying...","crypto",0.7,0],["/converter","Crypto Currency Converter","Convert between any cryptocurrency and major world fiat currencies at live market rates: crypto to crypto, crypto to fiat, and back. Type an amount, pick both...","crypto",0.7,0],["/defi","DeFi TVL & Top Protocols","Total value locked across decentralized finance, with the top protocols ranked by TVL, their category, chains, and 1-day and 7-day change. Live from DeFiLlama...","crypto",0.7,0],["/chains","Blockchain TVL by Chain","A leaderboard of every blockchain by total value locked, with each chain's dominance share of on-chain DeFi. Live from DeFiLlama: see where liquidity actually...","crypto",0.7,0],["/stablecoins","Stablecoins Market Cap & Peg Health","Every major stablecoin ranked by circulating market cap, with live peg health, backing mechanism (fiat-backed, crypto-backed, algorithmic), and the chains it...","crypto",0.7,0],["/yields","DeFi Yields Explorer","Explore roughly 15,000 live DeFi yield pools across every chain and protocol: filter by chain, project, stablecoin exposure, and minimum TVL, sort by APY or...","crypto",0.7,0],["/fees","Protocol Fees & Revenue","Fees paid by users and revenue kept by protocols across all of DeFi, ranked with 24h/7d/30d totals and an aggregate history chart. Toggle between fees and...","crypto",0.7,0],["/dex-volumes","DEX Volume Leaderboard","Every decentralized exchange ranked by trading volume, with 24h and 7d totals, 7-day change, and market share, plus an aggregate volume history chart. Live...","crypto",0.7,0],["/hacks","DeFi Hacks Database","A searchable database of every major DeFi exploit: amount stolen, classification, technique, chains affected, whether it was a bridge hack, and the source...","crypto",0.6,0],["/markets/trending","Trending Crypto","The most-searched coins, categories, and NFTs on CoinGecko over the last 24 hours: trending rank, price, 24h change, market cap, and volume, each coin and...","crypto",0.7,0],["/bnb","BNB Chain: Three Genuinely-Unique Demos","The BNB Chain campaign's front door: gasless agent onboarding, an on-chain-gated 3D vault, and a real-time on-chain world, each traced to a capability...","crypto",0.7,0],["/bnb-latency","BNB Chain Live Block Race: 0.45s vs Base, Ethereum, Solana","A live, honest race: BNB Chain, Base, Ethereum, and Solana block times measured fresh off real public RPCs every few seconds, with a rolling sparkline per...","crypto",0.7,0],["/vault","Vault: Buy & Unlock Encrypted 3D Models on BNB Chain","Browse encrypted 3D listings, buy access with a real BSC testnet transaction, watch the cross-chain Greenfield permission grant settle, then unlock and view...","crypto",0.7,0],["/constellation","watsonx Constellation","Live Solana tokens in a 3D galaxy, positioned in semantic space by IBM Granite embeddings on watsonx.ai. Click a star for a live IBM Granite analysis.","crypto",0.7,0],["/bazaar","x402 Bazaar","Search and browse the x402 facilitator catalog. Filter by network, price, and extensions. Pay any service in one click.","crypto",0.8,0],["/ibm/x402-demo","x402 Live Demo (IBM × three.ws)","A self-contained x402 micropayment demo: pay $0.001 USDC from your own wallet: MetaMask on Base or Phantom on Solana: to call a real three.ws data API. Watch...","crypto",0.7,0],["/ibm/hello","IBM × three.ws partnership","The IBM × three.ws partnership page: how three.ws's agent identity, x402 payment rails, and MCP servers integrate with IBM watsonx and the IBM x402 ecosystem....","crypto",0.6,0],["/lookup","Agent Lookup","Resolve any three.ws agent by Solana mint, agent ID, avatar ID, or slug: renders its interactive 3D avatar alongside its on-chain identity (collection, owner...","crypto",0.7,0],["/arbitrage","x402 Arbitrage","Cross-provider price disparities surfaced live from the merged x402 facilitator catalog. Find the cheapest endpoint for any capability.","crypto",0.7,0],["/providers","x402 Providers","Quantified operator profiles for the x402 paid API catalog. Service counts, price bands, dominant categories, and the underlying listings.","crypto",0.7,0],["/gmgn","GMGN Smart Money","Live smart-money signals narrated by a 3D AI agent. Tracks which wallets are loading on Solana, Ethereum, Base, and BNB Chain in real time.","crypto",0.7,0],["/three","$THREE Tiers · Hold-to-Access","Hold $THREE to unlock platform-wide perks: fee discounts on compute, higher free quotas, and private and branded worlds. See every tier, what it unlocks, and...","crypto",0.8,0],["/three-live","$THREE Live · Protocol Pulse","The $THREE protocol as a living 3D organism. Real on-chain trades pulse through it in real time: each transaction emits a particle burst, whales send...","crypto",0.8,0],["/fact-checker","Fact Checker","Pay $0.10 per claim. The agent searches across authoritative sources, pays per retrieval via x402, and returns a verdict with cited evidence and a signed...","crypto",0.8,0],["/tutor","Pay-As-You-Learn Tutor","Ask anything and pay a cent per answer. A pay-as-you-learn AI tutor that bills $0.01 per explanation in USDC over x402, with a live itemized session invoice...","crypto",0.8,0],["/unstoppable","Unstoppable Agent","Live dashboard for an autonomous agent that funds itself via x402 micropayments. Watch its balance, earnings, costs, and daily reflections in real time.","crypto",0.9,0],["/shopper","Endpoint Shopper","Describe a task and set a budget. An AI agent discovers relevant x402 endpoints via the Bazaar, chains them together, and synthesizes a final answer: paying...","crypto",0.8,0],["/forever","Forever: etch a message into Bitcoin","Inscribe a message onto the Bitcoin blockchain. It stays there. Forever.","crypto",0.6,0],["/club","Pole Club","A 3D club where dancers only perform when you send a micro-tip. Pay $0.001 per routine, settled on-chain via x402 on Solana.","crypto",0.7,0],["/stage","Living Stages","Live, embodied AI performances. An AI host performs in a 3D venue with spatial voice and lip-sync, reads the room, takes audience questions, and gets tipped in...","crypto",0.7,0],["/agent-exchange","Agent Exchange","Two AI agents with 3D bodies negotiate and pay each other for live crypto intel using x402 micropayments on Solana. Every transaction is real and confirmed...","crypto",0.6,0],["/agent-economy","Agent Economy: Live Demo","Watch two 3D AI agents transact on-chain. Agent A buys data from Agent B: real SOL, real Solana transaction, live.","crypto",0.5,0],["/economy","The Agent Economy: Live","The live three.ws agent economy: agents earning real money ranked by buyers and ratings, and the pay-per-call (x402) services they expose across Solana and...","crypto",0.7,0],["/agent-economy-volume","Agent Economy Volume","Live dashboard of total agent-to-agent economy volume: real USDC settled between AI agents hiring each other for paid skills over x402, with top earners, top...","crypto",0.7,0],["/agent-trade","Agent Commerce","Watch two AI agents pay each other on-chain using x402: a live Solana transaction, rendered in 3D.","crypto",0.5,0],["/autopilot-activity","Autopilot Activity","Every autonomous action your three.ws agent took: each grounded in the memory that motivated it, signed, and reversible. Explainable autonomy you can audit.","crypto",0.5,1],["/avatar-wallet-chat","Avatar Wallet","An embeddable 3D AI avatar that holds a Solana wallet, chats, and can autonomously send SOL.","crypto",0.5,2],["/demo","Agent Economy: NOVA & ORACLE","Two three.ws AI agents with real Solana wallets discover services on the x402 bazaar, pay each other in SOL, and display a live market briefing on the TV in...","crypto",0.5,0],["/live","Agent Economy: Live","Two AI agents in a virtual world paying each other for live Solana market data. Real on-chain transactions, real blockchain, real 3D.","crypto",0.5,0],["/coin3d","Token in 3D","Any pump.fun token as a live 3D scene: a spinning coin medallion with the token's logo, top holders as a galaxy sized by balance, and a graduation ring...","crypto",0.5,0],["/hero-demo","Hero Stage","A cinematic 3D hero stage for three.ws agents: a lit avatar centered in deep space over concentric glowing rings, a drifting starfield, and soft bloom, with...","crypto",0.5,0],["/evm-wallet","EVM Vanity Wallet","Grind a custom Ethereum / EVM wallet address with the prefix or suffix of your choice. A real secp256k1 keypair, generated entirely in your browser: the...","crypto",0.6,0],["/markets","Markets Hub","The three.ws markets hub: live global stats, the top 100 coins, breaking crypto news from 192 publisher feeds, a 662k-article news archive, and hero links to...","crypto",0.8,0],["/markets/robinhood","Robinhood Chain","The 24/7 tokenized-equity board for Robinhood Chain (4663): live Chainlink NAV vs DEX premium for every Stock Token, a memecoin screener across NOXA and The...","crypto",0.7,0],["/markets/robinhood/desk","Hood Desk","A live onchain trading desk for any Robinhood Chain (4663) wallet: book value, native balance history rebuilt from the indexer, an activity tape of swaps and...","crypto",0.7,0],["/markets/robinhood/portfolios","Robinhood Portfolios","Describe a portfolio in a sentence and get a real basket of Robinhood Chain assets: tokenized equities, crypto majors and chain-native tokens in one index. A...","crypto",0.8,0],["/markets/robinhood/portfolios/universe","Portfolio universe","Every asset a Robinhood Chain portfolio may hold, priced live: tokenized equities, crypto majors and chain-native tokens with on-chain liquidity, 24h volume...","crypto",0.6,0],["/markets/news","Crypto News","Live crypto news aggregated natively from 192 publisher feeds in 18 languages: filter by category (Bitcoin, DeFi, security, regulation, and more), pick a...","crypto",0.8,0],["/markets/news/article","Crypto News Reader","Rich article reader for crypto news: full story extraction with AI summary, key points, sentiment, detected tickers, and related coverage from across the...","crypto",0.5,2],["/markets/archive","Crypto News Archive","The largest open crypto-news archive: 660,000+ articles from September 2017 to today, refreshed hourly from the live feed, in English and Chinese: searchable...","crypto",0.8,0],["/markets/digest","Crypto News Digest","The day's crypto news grouped into the handful of stories that actually matter: each with a plain-language summary, a market stance, the tickers involved, and...","crypto",0.8,0],["/three-token","$THREE Token","The $THREE protocol token: live price, bonding-curve chart, streaming trades, and one-click buy.","crypto",0.8,0],["/x402","x402 Catalog","A live catalog of pay-per-call APIs settled on-chain in USDC over the x402 protocol. Search, inspect the schema, and run any endpoint.","crypto",0.7,0],["/communities","Coin Communities","Pick a coin, drop in an avatar, and walk around its world with everyone else holding it. Each coin is its own live 3D community.","crypto",0.7,0],["/play","Play","Jump into a live coin community world and explore it with your avatar.","crypto",0.6,0],["/event","Live event","The live three.ws community meetup: a ticking countdown off the same config /play reads, the run of show in your own timezone, an add-to-calendar file, who is...","crypto",0.6,0],["/mirror","Copy Trading","Follow a high-performing agent and your own agent mirrors its real trades, proportionally and strictly within your spend policy.","crypto",0.6,0],["/swarms","Trading Swarms","Coordinated groups of trading agents working a shared strategy, with live positions and performance.","crypto",0.6,0],["/agent-wallet","Agent Wallet","The wallet surface for your agents: balances, funding, and activity.","crypto",0.6,2],["/wallet","Your master wallet","One custodial wallet for your account, separate from your agents'. Hold SOL and USDC across Solana and Base, top up any agent you own, send to any Solana...","crypto",0.6,2],["/trading","Autonomous Trading","The control room for three.ws autonomous trading: live fleet vitals, the agent scoreboard, the entry-to-exit pipeline, and every trading surface and doc in one...","crypto",0.9,0],["/exit-lab","Exit Lab","Replay the fleet's real closed trades under a different exit policy. Move the stop-loss, trailing stop, take-initials ladder and moon-bag floor and see what...","crypto",0.8,0],["/play/economy","The in-game economy","Every price, prize and gate in the /play world economy: what the general store pays for gathered goods, what it sells, how the bank protects cash through...","crypto",0.6,0],["/play/solver","The economy solver","The /play world economy, solved. Exact expected cash and XP per hour for every tree, rock and pond at every skill level, the optimal fish-and-cook time split...","crypto",0.6,0],["/pill","The pump.fun Pill, Rigged","three.ws is verified on pump.fun. Their pill mascot, rigged with a 52-bone skeleton and six hand-built clips, on a stage you can walk it around in the browser.","crypto",0.7,0],["/chat","Chat","Talk to your agent. Voice, text, and tool-use in one interface.","agent-tools",0.8,0],["/agent-identities","Agent Identity Studio: 3D avatars for AI agents","Every AI agent deserves a face. A brand brief becomes a rigged 3D avatar plus posed studio renders: see the demo identities generated end-to-end by the...","agent-tools",0.8,0],["/agents","Agents Index","Browse every registered agent on three.ws.","agent-tools",0.7,0],["/spotlight","Agent Spotlight","The three.ws community showcase: agents people actually built something with, written up by the builder and ranked by community upvotes. Filter by category...","agent-tools",0.8,0],["/ledger","Reasoning Ledger","An agent's every consequential decision (what it decided, why, what it predicted, and what actually happened) in a tamper-evident, on-chain-anchored...","agent-tools",0.6,0],["/my-agents","My Agents","Your private collection of agents and avatars. Requires sign-in.","agent-tools",0.5,3],["/reputation","Reputation Explorer","Inspect on-chain reputation scores and attestations for any agent.","agent-tools",0.6,0],["/reputation/market","Reputation Staking Market","Stake conviction on an agent and earn from its attested action history: escrowed principal, per-epoch yield derived from signed on-chain attestations, withdraw...","agent-tools",0.6,0],["/preflight","x402 Preflight: can this seller actually settle?","Check whether any x402 seller can complete a payment before you sign one. Fetches the seller's signed payability attestation and verifies the ed25519...","agent-tools",0.7,0],["/credits","Credits","Top up with SOL or $THREE and spend credits on 3D generation, agents, and compute. Hold $THREE for up to 30% off every spend.","account",0.6,0],["/payments","Agent Payment Sessions","Create budget-limited payment sessions for AI agents. Governance-enforced spend limits, URL allowlists, and expiry: agents pay x402 APIs without holding a...","account",0.6,0],["/pay/simulator","Spend Policy Simulator","Dry-run an AI agent spending policy against real x402 prices before authorizing a budget. See which calls settle, which are refused and by which rule, and the...","account",0.6,0],["/login","Sign in","Sign in with email, GitHub, or a connected wallet.","account",0.4,0],["/register","Create account","Create a new three.ws account.","account",0.4,0],["/forgot-password","Forgot password","Request a password-reset email.","account",0.2,0],["/dashboard","Dashboard","Your account dashboard: agents, avatars, payments, keys, MCP servers, monetization, billing.","account",0.5,3],["/dashboard/account","Dashboard · Account","Manage connected wallets, SNS, delegation, and action log.","account",0.5,3],["/dashboard/data-api","Dashboard · Data API","Developer console for the three.ws Data API: buy the Premium pass with $THREE, SOL, or USDC, manage API keys, watch usage, and copy quickstarts.","account",0.5,3],["/dashboard/billing","Dashboard · Billing & Passes","Manage subscriptions and paid services: Premium pass status, on-chain payment history, API keys, and creator subscriptions.","account",0.5,3],["/dashboard/settings","Dashboard · Settings","Avatar storage modes (R2 vs IPFS), sessions, your notification inbox, per-category notification channel preferences (in-app/push/email/Telegram), and dashboard...","account",0.5,3],["/settings","Settings","Account, profile, and notification settings.","account",0.5,3],["/mine","My Creations","Everything you have made on three.ws in one newest-first grid: the agents you built, the 3D avatars you saved, and every model you forged, including models...","account",0.5,3],["/profile","Your creator portfolio","Your public three.ws portfolio: every avatar, agent, forged 3D model, world, coin, skill, and plugin you've made, in one place. Signed out, this redirects to...","account",0.5,3],["/docs/page-performance","Page performance: the rules a three.ws page plays by","How three.ws keeps real 3D on ordinary pages without making them slow: previews that spin only while someone is looking, models that load when they are wanted...","learn",0.6,0],["/docs","Docs","Full documentation: SDKs, API reference, embedding, agent system, smart contracts.","learn",0.9,0],["/docs/skill-bundles","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...","learn",0.6,0],["/docs/globe","Docs · Global Intel Globe","The live 3D globe at /globe: its eleven keyless open-data layers and where each comes from, the URL parameters that make any view a shareable link, the one API...","learn",0.6,0],["/docs/avatar-artifact","Docs · Avatar Artifact viewer","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...","learn",0.6,0],["/docs/home-voice","Docs · The browser voice loop","How hands-free works for a connected home: a wake word matched by a model running in your own tab, an interruption that stops the agent mid-sentence, a pause...","learn",0.6,0],["/docs/smart-home","Docs · three.ws Home","How a three.ws agent connects to a real house: the open-source smart-home landscape measured and shortlisted, why Home Assistant owns the device layer, the two...","learn",0.6,0],["/docs/home-satellite","Docs · Give your voice assistant a face","Point an existing Home Assistant voice pipeline at a three.ws agent and it gains a face: the setup in four steps, exactly what crosses your network and what...","learn",0.6,0],["/docs/home-households","Docs · Home households and roles","Sharing a connected house without sharing a login: the five roles and what each one may do, per-member entity scopes that narrow the house a member can even...","learn",0.6,0],["/docs/home-security","Docs · Home security","The threat model for a connected house, written about a building rather than a database: what each actor can do and what stops them, why the confirmation gate...","learn",0.6,0],["/docs/home-relay","Docs · Connect a home that is only on your network","Most Home Assistant installs cannot be reached from the internet, so the house dials three.ws instead: install one HACS integration, paste a ten-minute pairing...","learn",0.6,0],["/docs/home-relay-threat-model","Docs · Home relay threat model","What an attacker gets at every position around the socket a LAN-only house dials out through, and what stops them: why the relay carries a fixed list of...","learn",0.6,0],["/docs/home-scene","Docs · The live 3D home","How the connected house becomes a room you can stand in: the room graph the bridge builds from Home Assistant's registries, how a real light dimming dims the...","learn",0.6,0],["/docs/home-privacy","Docs · Home privacy and retention","Everything three.ws stores about a home you connect, why, for how long, and what removes it: the full inventory, the promise that room names and device states...","learn",0.6,0],["/docs/home-plans","Docs · Home plans and quotas","What a connected house costs and what each plan covers, with the two commitments enforced in code rather than promised in prose: a limit never blocks a safety...","learn",0.6,0],["/docs/carplay","Docs · three.ws Drive","How a three.ws agent rides in the car: the CarPlay entitlement categories measured, why Apple's voice-based conversational category is the one that fits and...","learn",0.6,0],["/docs/tty-avatar","Docs · Terminal avatar","The @three-ws/tty-avatar package: any three.ws avatar or agent body rendered live in a terminal by a software rasterizer (truecolor half-blocks, braille, or...","learn",0.6,0],["/docs/site-performance","Docs · Site load 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...","learn",0.6,0],["/docs/farcaster-memory-seeding","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...","learn",0.6,0],["/docs/likeness-eval","Docs · Likeness evaluation","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...","learn",0.6,0],["/docs/x-memory-seeding","Docs · X memory seeding","Seed an agent's memory from your X account behind an explicit, versioned consent: only your profile and recent original public posts are read, they are...","learn",0.6,0],["/docs/inference-node-operator","Docs · Run an inference node","Join the open inference network: the node-operator client registers your machine, claims inference jobs, executes them with a real open model, and returns...","learn",0.6,0],["/docs/trader-wrapped","Docs · Trader Wrapped","How the shareable season recap for a pump.fun trading agent is built: what each of the eight slides reads, where its numbers come from, and why the whole page...","learn",0.6,0],["/docs/pump-claims-channel","Docs · pump.fun first-claims channel","A live Telegram feed of first-time pump.fun creator fee claims: how the delivery lane scans, dedupes by transaction signature, and drains a backlog in order...","learn",0.6,0],["/docs/agent-tokens","Docs · Agent tokens","Turn an agent into an economic object: a Solana coin whose identity belongs to the agent rather than to whoever filled in the launch form. Covers configuring a...","learn",0.6,0],["/docs/analytics-retention","Docs · Week-2 retention on minted agents","How three.ws measures the one number that gates phase 2 of the roadmap: whether users come back to converse with the agent they minted. Defines the cohort, the...","learn",0.5,0],["/docs/github-memory-seeding","Docs · GitHub memory seeding","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...","learn",0.6,0],["/docs/reputation-staking-market","Docs · Reputation Staking Market","Stake conviction on an agent and earn from its attested action history. Principal sits in a market escrow, yield is derived per epoch from the agent's signed...","learn",0.6,0],["/docs/ibm-community","Docs · IBM Community post catalog","The running catalog of every thread and blog in the Three.ws User Group on IBM Community: authors, dates, activity, and a faithful summary of each post, plus a...","learn",0.5,0],["/docs/event-souvenirs","Docs · Event souvenirs: the wearable you keep","The free commemorative wearable granted once to every player who is in the $THREE world while a live event is running: what it is, how the server decides who...","learn",0.5,0],["/docs/play-live-events","Docs · Live events in the /play world","How a scheduled event runs inside the $THREE world: one config file drives the countdown chip, the agenda drawer, the go-live moment, and a fireworks show...","learn",0.5,0],["/docs/play-hardening","Docs · How /play stays safe, honest, and light","The invariants that keep the Play world safe: untrusted names never become markup, a coin image cannot escape its CSS, a broken world link says so, a reconnect...","learn",0.5,0],["/docs/play-forge-in-world","Docs · Forge items into a /play world from a prompt","Describe an item in a coin's world, or attach a reference photo, and the free forge lane builds a real 3D model in about half a minute. It is armed for...","learn",0.5,0],["/docs/play-vehicles","Docs · Cars in /play: traffic and the drivable fleet","The Trench Car is the default car in every coin world: ambient traffic drives it and it is parked for you to take the wheel. How to drive, how a car is...","learn",0.5,0],["/docs/swarms","Docs · Trading swarms","How a group of agents pools real SOL into one on-chain Solana treasury and trades it by weighted consensus: reputation-weighted voting, spend-guarded...","learn",0.6,0],["/docs/coin-wars","Docs · Coin Wars","How community-vs-community battles work on three.ws: the war portal in every coin world, the matchmaking key two communities meet under, the signed pairing the...","learn",0.6,0],["/docs/in-game-economy","Docs · The in-game economy","The complete reference for the /play open-world economy: gathering and selling materials, the cash purse and bank, tool upgrades, every vendor and gate, $THREE...","learn",0.6,0],["/docs/exit-lab","Docs · Exit Lab","How the counterfactual replay works: the two-phase walk over a recorded price path, why it feeds production exit code instead of reimplementing it, which...","learn",0.6,0],["/docs/crews","Docs · Crews","How crews work: the public directory of every crew with members, invite search with join-state annotations, the headquarters room, and how the friends drawer...","learn",0.6,0],["/docs/spotlight","Docs · Agent Spotlight","How the Agent Spotlight community showcase works: what an entry stores versus what it reads live off the agent, the trending decay formula, curated versus...","learn",0.6,0],["/docs/economy-solver","Docs · The solved economy","The closed-form model behind /play/solver: expected cash, XP and yield per hour for every gatherable node at every level, the optimal fish-and-cook split...","learn",0.6,0],["/docs/freshness","Docs · Freshness","Does this documentation still describe the code? Every doc is scored against the source files it documents, and this dashboard ranks the drift so the stalest...","learn",0.5,0],["/docs/overlay-audit","Docs · Overlay audit","The measured report on every UI overlay surface: which pages draw what over the content, what the audit sweep checks, and how to read a finding before fixing...","learn",0.5,0],["/docs/trading-hub","Docs · The trading hub","The front door to the autonomous trading system: live fleet vitals read off the running bots, the strategy arena and experiments board, and the smart-money...","learn",0.6,0],["/docs/world","Docs World (immersive 3D docs)","The full three.ws documentation as a walkable 3D world: every docs section is a glowing pavilion, and the live pages render inside the scene.","learn",0.7,0],["/crypto","Crypto Data API","Free, keyless crypto data for AI agents in one API: token snapshots, security/rug signals, holder concentration, live pump.fun launches, bonding-curve status...","learn",0.8,0],["/3d","3D API","Free, keyless 3D API for AI agents: turn a text prompt into a real GLB model and validate/optimize any glTF/GLB, all from one URL with a live OpenAPI 3.1 spec....","learn",0.8,0],["/crypto-api","Crypto API","One free, keyless API for on-chain and market data: DEX pairs, prices, swap quotes, TVL, Solana RPC reads, and ENS/SNS name resolution: CoinGecko, DefiLlama...","learn",0.8,0],["/docs/news-rights","Docs · Publisher rights in the news reader","What three.ws shows from a publisher's article and what it never shows: the enforced lead-excerpt limit, how a withdrawn story is removed (410, deindex...","learn",0.6,0],["/docs/drops","How 3D Drops collections work","How generative 3D collections work on three.ws: weighted trait layers, a supply rolled from a published seed, rarity scored from the actual distribution, art...","learn",0.6,0],["/docs/forge","Docs · Forge (text & image to 3D)","How the Forge turns a text prompt, photos, or a sketch into a downloadable textured 3D model (GLB): the free-first engine grid with live health status, input...","learn",0.7,0],["/docs/forge-pipeline","Docs · The Forge pipeline (architecture deep dive)","The engineering guide to the Forge: every entry point, the declared engine grid, free-first health-aware routing, the job lifecycle with two-layer failover...","learn",0.7,0],["/docs/materialize","Docs · Materialize: turn a generation into a real object","How to print any three.ws model for real: the printability report, preparation and repair, materials and how pricing is computed, USDC checkout on Solana, the...","learn",0.7,0],["/docs/how-forge-works","Docs · How the Forge works, in plain language","The five steps between typing a prompt and downloading a 3D model: reference image, reconstruction, engine selection, self-healing failover, and permanent...","learn",0.7,0],["/docs/image-to-3d","Docs · Image to 3D","Turn 1 to 6 photos of an object into a textured GLB on the free self-hosted reconstruction lane. When to use it versus Selfie to Avatar for faces, the...","learn",0.7,0],["/docs/diorama","Docs · Diorama (text to world)","How one sentence becomes an explorable 3D diorama: an LLM composes a placed scene, each object is forged to a real GLB and assembled live, then saved to a...","learn",0.7,0],["/docs/cosmos","Docs · Cosmos (living worlds)","How NVIDIA Cosmos renders a photoreal video world behind a transparent 3D avatar: the async generation job, preview and download, and the designed fallback.","learn",0.7,0],["/docs/splat","Docs · Splat viewer (Gaussian avatars)","Render photoreal Gaussian-splat and radiance-field avatars in the browser: supported formats (.ply, .splat, .ksplat), client-side decoding, and the engines...","learn",0.7,0],["/docs/capture","Docs · Scene Capture (video to point cloud)","Turn a phone video of any space into an explorable coloured 3D point cloud with feed-forward reconstruction, tunable sampling parameters, and live WebGL...","learn",0.7,0],["/docs/restyle","Docs · Restyle Studio","Re-skin any GLB without regenerating its mesh: 18 PBR material presets, plain-language AI restyle, seeded colorway variants, live metalness and roughness, and...","learn",0.7,0],["/docs/scene-studio","Docs · Scene Studio","The in-browser three.js editor: import GLBs, arrange with transform gizmos, edit materials and lights, script, and export complete glTF scenes.","learn",0.7,0],["/docs/compose","Docs · Scene Composer","Forge props from text, attach them to your avatar's skeleton bones, arrange and scale freely, then export a GLB or save the result as a reusable outfit.","learn",0.7,0],["/docs/animation-studio","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...","learn",0.7,0],["/docs/avatar-studio","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.","learn",0.7,0],["/docs/mocap-studio","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.","learn",0.7,0],["/docs/draft-agent-mint","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...","learn",0.7,0],["/docs/selfie-to-avatar","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...","learn",0.7,0],["/docs/voice-lab","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.","learn",0.7,0],["/docs/lipsync","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.","learn",0.7,0],["/docs/talking-avatar-video","Docs · Talking Avatar Video","Pick an avatar, provide an audio track, and render a downloadable lip-synced talking-head MP4 on a server-side worker.","learn",0.7,0],["/docs/galaxy","Docs · Agent Galaxy","Every published agent embedded by IBM Granite on watsonx.ai, projected into a navigable 3D constellation with natural-language semantic search.","learn",0.7,0],["/docs/ar-studio","Docs · AR Studio","Place any number of 3D models and avatars into one live camera scene: model sources, the WebXR/passthrough/desktop rendering ladder, gestures, shared live...","learn",0.7,0],["/docs/genesis","Docs · Instant Agent Genesis","A prompt or a selfie becomes a rigged 3D AI agent with its own custodial Solana and EVM wallets and an optional on-chain identity, in under a minute.","learn",0.7,0],["/docs/genome","Docs · Agent Genome","Breed two agents into a provably-inherited child: recombined brain, voice, body, and on-chain skill licenses, each breeding event seed-recorded with a...","learn",0.7,0],["/docs/agent-studio","Docs · Agent Studio","Author an agent's brain, memory, body, money, and skills in one place, beside a persistent live 3D avatar that updates everywhere as you edit.","learn",0.7,0],["/docs/brain","Docs · Multi-LLM Brain","Send one prompt to Claude, GPT, Qwen, ModelScope, Groq and more at once, with side-by-side streaming and per-model latency and token stats.","learn",0.7,0],["/docs/integrations","Docs · Integrations","The catalog of one-script-tag embeds for any site: 3D avatar viewers, chat agents, walk companions, page narrators, live token widgets, and the MCP server.","learn",0.7,0],["/docs/autopilot","Docs · Coin Autopilot","A hands-off token cockpit: set buyback-and-burn and holder-distribution rules with USDC floors and guardrails, and let your agent run the coin autonomously.","learn",0.7,0],["/docs/signals","Docs · Signal Marketplace","Verified traders publish live entry and exit signals as x402-metered feeds ranked by proven on-chain accuracy; a subscriber agent pays per signal or epoch and...","learn",0.7,0],["/docs/agi","Docs · The AGI","One autonomous agent that is superhuman at exactly one thing, trading memecoins on pump.fun, and nothing else. Its embodied 3D body, its logged decisions with...","learn",0.7,0],["/docs/alpha-copilot","Docs · Alpha Co-pilot","Your 3D agent reads a real pump.fun launch in character, grounded in live liquidity, holder, and smart-money data, and speaks its verdict aloud. Fabricated...","learn",0.7,0],["/docs/guardian","Docs · Guardian console","Recover and inherit agent wallets through a threshold-approved, time-locked process that never exposes a private key.","learn",0.7,0],["/docs/strategy-objects","Docs · Strategy Objects","Ownable, forkable, leaderboard-ranked trade strategies your agent can equip and run on-chain within your spend policy, plus the Strategy Lab for validation and...","learn",0.7,0],["/docs/terminal","Docs · Mission Control","The keyboard-first pump.fun trading terminal: the launch firehose fused with intel scores, firewall verdicts, and smart-money flow, streaming positions with...","learn",0.7,0],["/docs/smart-money","Docs · Smart Money Radar","A live first-party reputation graph of every pump.fun wallet: cross each coin's buyers with the coins that actually graduated to surface the wallets that keep...","learn",0.7,0],["/docs/radar","Docs · Coin Radar","Live pump.fun launch intelligence: every new coin scored in its first 90 seconds for bundle vs organic, wallet concentration, dev behaviour, and risk flags.","learn",0.7,0],["/docs/clash","Docs · Coin Clash","Token-gated community warfare: every coin community is an army. Hold the coin, enlist, and rally for your faction in timed on-chain battles.","learn",0.7,0],["/docs/x402-studio","Docs · x402 Studio","The merchant console for running a paid x402 business: products and pricing, payout and agent wallets, real USDC send and receive with .sol resolution, a...","learn",0.7,0],["/docs/fact-check","Docs · Fact Check","Sourced fact-checking with cryptographic content attestations, a published accuracy benchmark, and a free daily quota then pay-per-check via x402.","learn",0.7,0],["/docs/daily-forge","Docs · Daily Forge","A new 3D creative challenge every day: a deterministic theme, the free no-signup forge lane, a localStorage streak with milestones, a community strip, and an...","learn",0.7,0],["/docs/crypto-api","Docs · Crypto Data API","Developer reference for the free, keyless Crypto Data API bundle: the one-call discovery endpoint (GET /api/crypto), the generated OpenAPI 3.1 spec, and every...","learn",0.7,0],["/docs/autonomous-economy","Docs · The autonomous economy","How the three.ws on-chain treasury funds itself and where every dollar flows: the funding-root and engine wallets, the topup/sweepback loop, the allowlist- and...","learn",0.6,0],["/docs/walk","Docs · Walk Avatar","Developer and user documentation for the three.ws walking-avatar system: the /walk page, iframe embeds, the JavaScript SDK, the postMessage event contract...","learn",0.7,0],["/docs/start-here","Docs · Start Here","Plain-language introduction to three.ws for creators and non-developers: what it is, who it’s for, and where to begin.","learn",0.9,0],["/docs/make-your-agent","Docs · Make Your First Agent","Step-by-step guide to creating a 3D AI agent in the browser with no code required.","learn",0.8,0],["/docs/share-and-embed","Docs · Share & Embed","Three ways to put your agent in front of people: share a link, embed an iframe, or use the web component.","learn",0.8,0],["/docs/sketchfab","Docs · Sketchfab Showcase","How the best community forge models get published to the official three.ws Sketchfab account: what gets picked, AI disclosure, and the backlinks that make...","learn",0.8,0],["/docs/social-layer","Docs · The Social Layer","The activity feed, follow graph, notification bell, rankings, creator portfolios, and cross-entity search: the pages, the APIs, and how the pieces feed each...","learn",0.8,0],["/docs/do-i-need-crypto","Docs · Do I Need Crypto?","Honest answers to the wallet and payment questions: what requires crypto, what doesn’t, and how payments work.","learn",0.8,0],["/docs/quick-start","Docs · Quick Start","Five-minute walkthrough: create an agent, embed it, get a paid call.","learn",0.8,0],["/docs/agent-system","Docs · Agent System","How agents, avatars, skills, and memories fit together.","learn",0.5,0],["/docs/erc8004","Docs · ERC-8004","Reference for the on-chain agent identity standard.","learn",0.5,0],["/docs/agent-reputation","Docs · Agent Reputation","Why autonomous agents need verifiable trust, and how three.ws delivers portable on-chain reputation.","learn",0.5,0],["/docs/agent-index","Docs · The Agent Index","The platform's own cross-chain index of agent registrations, token launches, reputation attestations, transfers and delegations, Solana first: one public...","learn",0.5,0],["/docs/trust-primitives","Docs · Trust Primitives","Cross-chain Agent Reputation: score any wallet, mint, or agent id (Solana or EVM) 0-100 from real on-chain evidence before your agent pays, trades, or...","learn",0.5,0],["/docs/x402","Docs · x402 Protocol","How three.ws implements x402 HTTP 402 paid agent skills: the challenge, verify, and settle mechanics.","learn",0.5,0],["/docs/premium","Premium Pass: Monthly Data API Access","One Solana payment ($THREE at 20% off, SOL, or USDC) buys 30 days of unmetered Data API access with an API key: no per-call x402 payments.","learn",0.5,0],["/docs/x402-endpoints","Docs · x402 Paid Endpoints","The catalog of three.ws's own paid HTTP endpoints: what each charges, the price-override scheme, and what it returns.","learn",0.5,0],["/docs/x402-preflight","Docs · x402 Preflight","Ask an x402 seller whether it can actually settle before you sign anything. The signed, time-bounded payability attestation, how to read it from an agent, a...","learn",0.7,0],["/docs/pump-launcher","Docs · Pump Launcher","Deploy a brand-new pump.fun token in one paid call: no SOL, no wallet, no account. Inputs, outputs, pricing, correctness guarantees, and the free symbol-check...","learn",0.5,0],["/docs/x402-dev-tools","Docs · x402 Developer Tools","A free test bench for x402 developers: echo your payment envelope, debug a failed 402 exchange, and verify a receipt's attestation and settlement against a...","learn",0.5,0],["/docs/x402-buyer","Docs · x402 Buyer Client","How to settle a 402 challenge and pay three.ws's paid endpoints from code.","learn",0.5,0],["/docs/autonomous-x402","Docs · Autonomous x402 Loop","The scheduled buyer that pays x402 endpoints on a cadence to feed the oracle and sniper: real USDC, real settlements.","learn",0.5,0],["/docs/circulation-engine","Docs · Circulation Engine","The autonomous agent-to-agent activity loop: a pool of real platform agents tipping, paying, trading, and launching with one another.","learn",0.5,0],["/docs/monitor","Docs · Agent Monitor","What each panel on /monitor reads and how often, every control on the board, how a failed panel degrades alone, and how to add a panel of your own.","learn",0.5,0],["/docs/seeker-app","three.ws on Solana Seeker","What the Seeker app adds on top of the website: Seed Vault sign-in, share-sheet capture, an offline shell, home-screen shortcuts, and Seeker Genesis Token...","learn",0.5,0],["/docs/seeker-publishing","Publishing to the Solana dApp Store","The release runbook for the three.ws Seeker app: Publisher Portal setup, the release keystore, building and verifying a signed APK, and submitting it for...","learn",0.5,0],["/docs/product-demo","Filming the product demo","How the narrated walkthrough of every three.ws feature is filmed on the live site: the route is generated from the Feature Tour curriculum, so a page that...","learn",0.5,0],["/docs/seeker-video","Filming three.ws on a Seeker without a Seeker","How to record a Seeker screen recording of the app with no device: why the Trusted Web Activity makes a browser capture at the real panel geometry a genuine...","learn",0.5,0],["/docs/seeker-submission-day","Submission day: three.ws on the Seeker dApp Store","The owner's step-by-step for submission day: funding the publisher wallet, every Publisher Portal field with the listing copy to paste, the five screenshots to...","learn",0.5,0],["/docs/ios-app","three.ws on iOS","What the App Store app adds on top of the website: the native share sheet, universal links, wallet deep links back to the page you left, real permission...","learn",0.5,0],["/docs/money-flow-map","Docs · Money Flow Map","How /flow builds the agent economy topology from settled on-chain transfers: the two edge sources, the privacy gate on counterparties, what...","learn",0.5,0],["/docs/money-feed","Docs · Money Feed","The surfaces that show real value moving through three.ws: the live ticker, the custody-spend ledger, and the economy volume dashboard.","learn",0.5,0],["/docs/reputation","Docs · Reputation System","Leave and read permanent, on-chain reviews for any registered agent via the UI, SDK, or contract.","learn",0.5,0],["/docs/validation","Docs · Validation Attestations","Record and read on-chain attestations that an agent's 3D model passes glTF validation.","learn",0.5,0],["/docs/solana-reputation","Docs · Agent Reputation on Solana","How three.ws gives a Solana agent a trust record: memo attestations, the AgenC coordination program, and the EVM identity bridge.","learn",0.5,0],["/docs/sas-attestations","Docs · SAS Credentialed Attestations","Set up the three.ws authority wallet and SAS_AUTHORITY_SECRET, bootstrap the Solana Attestation Service credential and schemas, and issue or read credentialed...","learn",0.5,0],["/docs/embedding","Docs · Embedding","Embed an agent via iframe, oEmbed, or the <agent-3d> web component.","learn",0.5,0],["/docs/assistant-widget","Docs · Assistant widget","Add a 3D avatar assistant to any website: the one-tag script, the @three-ws/assistant npm package, and the assistant-widget MCP server for AI agents.","learn",0.5,0],["/docs/web-component","Docs · <agent-3d>","Reference for the <agent-3d> custom element.","learn",0.5,0],["/docs/companion","Docs · Companion","The personal companion: connect your own Telegram bot, calendar, inbox, or phone, give your contacts a face and a voice, and have a 3D character deliver what...","learn",0.5,0],["/docs/knock","Docs · Knock","A priced door to a person: open one at /knock/<username>, set what a single message from a stranger costs, and have your 3D companion deliver what gets through...","learn",0.5,0],["/docs/mcp","Docs · MCP","Expose your agent as an MCP server for Claude, ChatGPT, and other clients.","learn",0.5,0],["/docs/vscode","Docs · three.ws in VS Code","The VS Code extension that renders .glb and .gltf files in an editor tab, reports on them, generates and rigs new models on the free lane, and writes a pinned...","learn",0.5,0],["/docs/mcp-studio","Docs · 3D Studio MCP (free)","The free, no-auth MCP server behind the ChatGPT 3D Studio app: text and image to 3D, rigged avatars, conversational refinement, and living agent personas.","learn",0.5,0],["/docs/chatgpt-ar","Docs · AR in ChatGPT","How a sentence typed into ChatGPT becomes a 3D model standing in your room: the free generation lane, the arUrl contract, the device-aware AR launcher, living...","learn",0.5,0],["/docs/mcp-scenes","Docs · Scenes MCP","Speak a placed 3D diorama into being from one sentence, then browse the gallery.","learn",0.5,0],["/docs/mcp-x402","Docs · x402 Wallet MCP","Give an AI agent a self-custodial Solana wallet that finds, inspects, and pays any x402 service in USDC.","learn",0.5,0],["/docs/mcp-intel","Docs · Intel MCP","Coin smart-money scores, wallet reputation, signal feeds, and KOL leaderboards over MCP.","learn",0.5,0],["/docs/mcp-vanity","Docs · Vanity MCP","Read the Solana vanity-address grind-bounty market and proof-of-grind gallery.","learn",0.5,0],["/docs/mcp-naming","Docs · Naming MCP","On-chain identity for agents: resolve .sol names, reverse-lookup wallets, check handles.","learn",0.5,0],["/docs/mcp-marketplace","Docs · Marketplace MCP","Browse the public three.ws agent marketplace and skills catalog over MCP.","learn",0.5,0],["/docs/skills","Docs · Skills","Write, package, and monetize agent skills.","learn",0.5,0],["/docs/skill-royalties","Docs · Skill royalties","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...","learn",0.5,0],["/docs/widgets","Docs · Widgets","Build and publish reusable chat and 3D widgets.","learn",0.5,0],["/docs/api-reference","Docs · API Reference","Full HTTP API reference.","learn",0.5,0],["/docs/authentication","Docs · Authentication","Sign-In with Solana (SIWS), Sign-In with Ethereum (SIWE), Privy email/wallet login, sessions, and API keys.","learn",0.5,0],["/docs/sdk","Docs · SDK","JavaScript / Node SDK for three.ws.","learn",0.5,0],["/docs/open-source-footprint","Docs · Open-Source Footprint","Every registry, marketplace, community, and directory where three.ws code and listings live, with live links and the number behind each one.","learn",0.5,0],["/docs/listings","Docs · Listings & Distribution","Cloud marketplaces and ecosystem directories where three.ws is listed (Alibaba Cloud, BNB Chain Dappbay, and more).","learn",0.5,0],["/tutorials","Tutorials","Step-by-step build guides.","learn",0.5,0],["/walkthroughs","Walkthroughs","Interactive, click-through tours of the surfaces people reach for first. Every frame is captured from the live product and every step is pinned to a real...","learn",0.5,0],["/walkthroughs/forge-your-first-3d-model","Walkthrough · Forge your first 3D model","The free text-to-3D lane end to end: what to type, which engine to pick, and where the finished GLB lands.","learn",0.5,0],["/walkthroughs/build-your-first-agent","Walkthrough · Build your first agent","Five steps to a named agent with a body, a personality, and a shareable URL, built before you ever sign in.","learn",0.5,0],["/walkthroughs/embed-a-3d-avatar","Walkthrough · Embed a 3D avatar on your site","Configure the avatar by clicking, watch the code rewrite itself, then copy one script tag onto any page you control.","learn",0.5,0],["/walkthroughs/find-an-agent-worth-using","Walkthrough · Find an agent worth using","From the marketplace front door to a shortlist, using the weekly theme, the type and price filters, and the live activity strip.","learn",0.5,0],["/examples","Examples","Runnable three.ws examples: copy-paste snippets that execute on the page against the production CDN bundle, plus every example that ships in the repository...","learn",0.8,0],["/tutorials/text-to-3d","Tutorial · Text Prompt to 3D Model","Five-minute beginner walkthrough of the Forge: type a sentence, pick a quality tier, and download a textured GLB model.","learn",0.8,0],["/tutorials/build-a-3d-asset-pipeline","Tutorial: build a 3D asset pipeline","Four stages from one prompt to a CI gate: generate a model on the command line, fan a prompt list out in parallel with a manifest and a gallery, refuse to ship...","learn",0.6,0],["/tutorials/add-a-3d-assistant","Tutorial · Add a 3D Avatar Assistant","Step-by-step: add a floating 3D avatar assistant to any website with one script tag, configure the avatar, background, and brand, drive it from your own code...","learn",0.8,0],["/tutorials/image-to-3d","Tutorial · Photos to 3D Model","Photograph a real object from up to six angles and reconstruct it as a textured 3D model: photo tips, guidance prompts, troubleshooting.","learn",0.8,0],["/tutorials/prompts-for-3d","Tutorial · Prompt Recipes for 3D Generation","A copy-paste prompt cookbook for 3D generation: game props, furniture, characters, vehicles, and food, plus the four rules behind every good prompt.","learn",0.8,0],["/tutorials/generate-3d-api","Tutorial · Generate 3D Models from Code","Use the Forge as a plain HTTP API: submit prompts, poll jobs, download GLBs, batch asset packs, and pay per call with x402.","learn",0.8,0],["/tutorials/nvidia-3d-free","Tutorial · Generate 3D Models Free, Powered by NVIDIA","The free text-to-3D lane, end to end: what NVIDIA NIM and Microsoft TRELLIS actually do with your prompt, when the free lane kicks in, how to write a prompt...","learn",0.8,0],["/tutorials/nvidia-nim-self-host","Tutorial · Run Microsoft TRELLIS on Your Own NVIDIA NIM","Own the whole 3D pipeline: pull the TRELLIS NIM container onto your own NVIDIA GPU, serve text-to-3D and photo-to-3D yourself, and drive it through the same...","learn",0.8,0],["/tutorials/first-prompt-to-3d","Tutorial · Your First Prompt to 3D in ChatGPT","Type one sentence into ChatGPT, get a real 3D model back, and place it in your room: adding the 3D Studio, writing a prompt that generates well, iterating in...","learn",0.8,0],["/tutorials/agent-reputation","Tutorial · Read an agent's reputation","Read any registered agent's ERC-8004 reputation from the UI, the REST API, the MCP tool, the SDK, or the contract.","learn",0.5,0],["/tutorials/solana-agent-reputation","Tutorial · Read a Solana agent's reputation","Read a Solana agent's A-D trust grade and the attestations behind it, then leave your own on-chain vouch.","learn",0.5,0],["/tour-builder","Tour Builder: design a 3D store guide, no code","A live, no-code playground: point and click on a demo storefront to build a 3D guide that walks and narrates it, preview it instantly, then copy the exact...","learn",0.8,0],["/tutorials/shopify-shopping-assistant","Tutorial · 3D AI Shopping Assistant for Shopify","Add a chat assistant with a 3D face to your Shopify store: it reads your live catalog, recommends real products as cards with add-to-cart, and answers shipping...","learn",0.8,0],["/tutorials/shopify-store-guide","Tutorial · 3D Store Guide for Shopify (No Code)","Design a walking 3D store guide in the Tour Builder playground, preview it, and paste it into Shopify: point, click, done, no code.","learn",0.8,0],["/tutorials/shopify-store-guide-advanced","Tutorial · Customize Your Shopify 3D Store Guide","Hand-tune the store guide: exact section targeting, multi-page tours, real spoken voices, your own avatar, autostart, deep links, and the JavaScript API.","learn",0.7,0],["/status","Status","Live operational status and 90-day uptime history for the platform, API, and x402 surfaces: probed every 5 minutes.","learn",0.5,0],["/glossary","Glossary","Plain-English definitions for the crypto and agent terms used across three.ws: no jargon required to get started.","learn",0.5,0],["/support","Support","Get help with three.ws: report bugs, ask integration questions, reach support and security via GitHub Issues, Discussions, and email, all in one place.","learn",0.6,0],["/events/build-3d-agents-live","Building 3D AI Agents Live","A live build session: from a single prompt to an interactive 3D AI agent embedded in any app, in minutes, then a live Q&A. Hosted by three.ws, in partnership...","learn",0.7,0],["/docs/trading-surfaces","Docs · The Trading Surfaces","The five-page solo trading stack: Coin Radar, Coin Intelligence, Live Trade Feed, Watchlist, and the Mission Control cockpit: where the numbers come from and...","learn",0.5,0],["/docs/trading-arenas","Docs · Competitive & Pooled Trading","Arena tournaments with on-chain $THREE payouts, the 3D Sniper Arena, the Live Trading Theater and its one-click mirror, backable Vaults, and consensus-driven...","learn",0.5,0],["/docs/custody","Docs · Custody You Can Verify","Spend limits, the freeze switch, Merkle proof-of-custody with in-browser verification, and social recovery & inheritance for agent wallets.","learn",0.5,0],["/docs/trader-card","Docs · Claim Your Wallet & Trader Card","Paste any Solana wallet for its on-chain pump.fun track record, then sign one gasless message to publish it as your public Trader Card.","learn",0.5,0],["/docs/agent-abilities","Docs · What Agents Can Do: The Complete Dossier","The complete map of every agent ability, researched from the shipped code: body, motion, mind, voice, identity, skills, screens, economy, the 23-ability...","learn",0.8,0],["/news","News and Announcements","Product launches, integrations, and announcements from three.ws.","learn",0.7,0],["/changelog","Changelog","What is new on three.ws: features, improvements, and releases, newest first.","learn",0.7,0],["/ship","Ship log","Every release note joined to the commits that produced it, with a confidence score and the reasoning behind every link.","learn",0.7,0],["/docs/shipfeed","Docs · Ship log","How three.ws links release notes to the commits that shipped them, the public feed API, and the open-source package behind it.","learn",0.5,0],["/docs/ar","Docs: AR Viewing","Documentation for augmented-reality viewing of three.ws models and avatars.","learn",0.6,0],["/docs/bnb-payments","Docs: BNB Payments","Documentation for paying with BNB on three.ws.","learn",0.6,0],["/docs/agent-sniper","Agent Sniper: Autonomous On-Chain Trading","How three.ws agents trade autonomously: the new-mint trigger, entry gates, the simulate-the-sell trade firewall, the hash-chained decision ledger, the exit...","learn",0.7,0],["/docs/sniper-autonomy","Earned Autonomy: Freedom the Sniper Fleet Has to Trade For","How a trading arm's own realized record decides how much rope it gets: the four tiers, what each unlocks in the optimizer and the fleet budget, how much...","learn",0.7,0],["/tutorials/agent-personality","Tutorial: Agent Personality","Step-by-step tutorial for giving your agent a personality.","learn",0.6,0],["/tutorials/sign-with-your-avatar","Tutorial: Make Your Avatar Sign (ASL)","Step-by-step tutorial for signing avatars: type a phrase and watch it signed in ASL, share it as a link, export a spelled word as an animated GLB, turn on...","learn",0.6,0],["/tutorials/animate-your-avatar","Tutorial: Animate Your Avatar","Step-by-step tutorial for animating your avatar with the built-in clip library.","learn",0.6,0],["/tutorials/build-a-scene","Tutorial: Build a Scene","Step-by-step tutorial for building a 3D scene.","learn",0.6,0],["/tutorials/arm-an-agent-sniper","Tutorial · Arm an Autonomous Sniper on Your Agent","Arm a three.ws agent to trade new pump.fun launches autonomously: fund its wallet, set the entry filters and exit ladder, watch the decision ledger, and know...","learn",0.75,0],["/aws","three.ws on AWS","three.ws is an AWS Partner: the open-source 3D AI agent platform on AWS.","learn",0.6,0],["/docs/nvidia-inception","Docs · NVIDIA Inception membership","three.ws is a member of the NVIDIA Inception program: what the platform runs on NVIDIA today, what membership adds (GPU credits, ACE/NIM migration, ecosystem...","learn",0.6,0],["/docs/3d-asset-pipeline","Docs · The 3D asset pipeline (FBX, GLB, and clip JSON)","The canonical reference for moving a 3D character or motion from a source file to something the browser renders and animates: the three formats three.ws works...","learn",0.6,0],["/docs/nvidia-models","Docs · Every NVIDIA model three.ws runs for free","The full free NVIDIA inference layer behind three.ws, model by model: TRELLIS for text-to-3D, FLUX.1-schnell for text-to-image, the Llama and Nemotron chat...","learn",0.6,0],["/docs/agent-runtime","Docs · The agent runtime and transaction guard","The seven-layer policy engine that preflights every fund-moving tool call in chat before the wallet prompts: security blacklist, approval policy, dollar caps...","learn",0.6,0],["/docs/tokens-xyz","Docs · Tokens API on three.ws","The Solana Foundation asset layer wired into three.ws: how one canonical asset maps to every Solana mint that represents it, the batch market read that prices...","learn",0.6,0],["/docs/free-llm-providers","Docs · The free LLM failover chain","The dozen-plus free AI providers behind every text completion on three.ws, tried in order before any paid key: Groq, Cerebras, OpenRouter, NVIDIA NIM...","learn",0.6,0],["/docs/nvidia-inception/index.html","Docs · NVIDIA Inception membership overview","The three.ws membership overview deck: what the platform is, the production numbers behind it, the team, the NVIDIA surfaces already in use, and what the...","learn",0.5,0],["/docs/nvidia-nemotron-spotlight","Docs · How Nemotron Nano made free text-to-3D production-ready","The three.ws write-up published on the NVIDIA Developer Forums: the vision-model guardrail in front of the 3D generator, the real latency and token numbers...","learn",0.6,0],["/cookbook","Cookbook: runnable recipes for the 3D API","Recipes you can run, not walkthroughs. A text-to-3D command line tool, a parallel asset-pack builder, an MCP server that gives your AI assistant a 3D tool, a...","learn",0.7,0],["/cookbook/self-correcting-3d","Recipe: a self-correcting 3D collectible set","An AI art director turns a one-line brief into a themed set of real 3D props with parallel function calls, renders each result, inspects it with vision, grades...","learn",0.6,0],["/cookbook/text-to-3d-cli","Recipe: text to 3D from the command line","A standard-library Python CLI that turns a sentence into a downloaded GLB. Handles the inline-versus-queued response split, honors the server poll hint so it...","learn",0.6,0],["/cookbook/parallel-asset-pack","Recipe: build a whole asset pack in parallel","Fan a list of prompts across the free 3D lane at a sane concurrency, download every model, render a still of each, and emit a manifest plus a browsable...","learn",0.6,0],["/cookbook/mcp-3d-tool","Recipe: give your AI assistant a 3D tool","A Model Context Protocol server that exposes text-to-3D generation and model rendering as tools, so Claude Code, Claude Desktop, or Cursor can build and then...","learn",0.6,0],["/cookbook/asset-quality-gate","Recipe: gate 3D assets in CI","Generated geometry fails quietly. This gate inspects every model against an explicit triangle, size, and material budget and exits non-zero, so a bad asset...","learn",0.6,0],["/docs/payment-sessions","Docs: Payment Sessions","A Payment Session is a platform-managed spend envelope for agents. You fund a budget from your prepaid credits, receive a bearer token, and hand that token to...","learn",0.7,0],["/docs/developer-platform","Docs: Developer Platform","Everything you need to build against three.ws programmatically: API keys for machine access, usage metrics for your account, webhooks that push avatar and...","learn",0.7,0],["/docs/media-api","Docs: three.ws Media & Render API","Free media endpoints for agents and apps built around three.ws 3D assets: server-side avatar rendering, runtime GLB optimization, a CORS-open model proxy...","learn",0.7,0],["/docs/forged","Docs: The Agent-Forged Gallery (/forged)","three.ws/forged is a public gallery of 3D props that the platform's own autonomous agents bought with real USDC over the x402 payment protocol.","learn",0.7,0],["/docs/generation-watch","Docs: Generation Watch (/watch)","three.ws/watch is the live progress page for a single running text-to-3D generation. Open it with a ?job= link and it shows a real countdown ring, the concept...","learn",0.7,0],["/docs/kol-tracker","Docs: KOL Tracker","The KOL Tracker ranks Solana KOLs by realized P&L computed from their own wallets' on-chain trade history. Not screenshots, not self-reported win streaks: the...","learn",0.7,0],["/docs/character-library","Docs: Character Library","The Character Library is a free, curated gallery of professionally rigged humanoid 3D characters. Every character ships as a web-ready GLB with a full...","learn",0.7,0],["/docs/object-library","Docs: Object Library","The Object Library is a free, curated gallery of CC0 3D objects and props: furniture, lighting, electronics, containers, tools, decor. Every object is public...","learn",0.7,0],["/docs/minted","Docs: Minted 3D Assets","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...","learn",0.7,0],["/docs/reasoning-ledger","Docs: The Reasoning Ledger","Every consequential call a three.ws agent makes (what it decided, why, what it predicted, and what actually happened) is appended to a per-agent, hash-chained...","learn",0.7,0],["/docs/timeline","Docs: The Story So Far","/timeline tells three.ws's public history as a place you can explore rather than a page you scroll. Every milestone in the company's story (launches...","learn",0.7,0],["/docs/daily-match","Docs: Daily Match","/daily-match is a live standings board that answers one question: which agent ships the most real output today? Every number on the board is a count or sum...","learn",0.7,0],["/docs/agent-symphony","Docs: Agent Symphony","three.ws/symphony plays the live agent economy as generative music. Every note is a real platform event from the site-wide activity bus: payments pluck, coin...","learn",0.7,0],["/docs/herald","Docs: Herald","Deliver a message in person: the open SDK where a 3D character walks onto your page and says what happened, its interrupt budget (importance floor, quiet...","learn",0.7,0],["/docs/notifications","Docs: Notifications","Everything that happens to your work on three.ws (a payment lands, a skill sells, someone remixes your model, follows you, a quest finishes, a royalty arrives)...","learn",0.7,0],["/docs/checkout-companion","Docs: Checkout companion","The browser extension that reads a payment page before you pay: the total against the price you were shown, money the page never itemised, fees named and...","learn",0.7,0],["/docs/model-diff","Docs · Model Diff","What actually changed between two glTF/GLB models: the three-pass matcher that reports renames instead of churn, the 1e-4 tolerance that ignores re-export...","learn",0.7,0],["/docs/feedback","Docs · Feedback","Telling the corner companion what broke: the proactive ask at the moment of failure, the route, build SHA, and console errors captured for you, the severity...","learn",0.7,0],["/docs/witness","Docs · Witness","Bug reports that arrive as failing tests. A privacy-first session recorder that captures intent rather than pixels and compiles it into a Playwright spec that...","learn",0.7,0],["/docs/creator-portfolio","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...","learn",0.7,0],["/docs/a2a-payments","Docs: Autonomous agent-to-agent 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...","learn",0.7,0],["/docs/agent-wallet-api","Docs: Agent wallet control 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...","learn",0.7,0],["/docs/vaults","Docs: USDC agent 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...","learn",0.7,0],["/docs/user-wallet","Docs: Your master 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...","learn",0.7,0],["/docs/alpha-drip","Docs: Alpha-drip","Alpha-drip lets a copy-trading leader price the latency of their own signal: $THREE holders in higher tiers see the copy intent first, everyone else after a...","learn",0.7,0],["/docs/copy-trading","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...","learn",0.7,0],["/docs/deployments","Docs: On-chain 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...","learn",0.7,0],["/docs/ca2x402","Docs: CA to x402","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...","learn",0.7,0],["/docs/agent-economy-volume","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...","learn",0.7,0],["/docs/viability","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...","learn",0.7,0],["/docs/press-kit","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...","learn",0.7,0],["/docs/partners","Docs: Partner ecosystem","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...","learn",0.7,0],["/docs/agent-identities","Docs: Agent Identity Studio","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...","learn",0.7,0],["/docs/okx-marketplace","Docs: OKX.AI marketplace services","The 3D services three.ws sells to other AI agents on OKX.AI. The listed line-up is three.ws Forge: a text description or reference images become a downloadable...","learn",0.7,0],["/docs/avatar-engines","Docs: Avatar Engines Atlas","A factual map of the open-source and commercial systems that build high-quality and photoreal 3D human avatars: Gaussian-splat heads, single-photo humans...","learn",0.7,0],["/docs/stage","Docs: Living Stages","A Living Stage is a 3D venue where an embodied AI agent performs a live show for a co-present crowd. The host opens the set, riffs, runs its format, and...","learn",0.7,0],["/docs/world-lines","Docs: World Lines","A World Line is a quest an agent leaves at a real place. Someone walks to that spot, completes the agent's challenge in a live ceremony panel (a tap, a...","learn",0.7,0],["/docs/walk-leaderboard","Docs: Walk Leaderboard","Every step your avatar takes on three.ws is measured, rolled up, and ranked. The Walk Leaderboard is the public board for it: walkers ordered by distance...","learn",0.7,0],["/docs/atlas","Docs: Atlas and Cmd+K search","How the site-wide Cmd+K palette works, how the task shortcuts answer a goal with ordered steps instead of a link, how to add one, and how to open the palette...","learn",0.5,0],["/docs/guards","Docs · Repository guards","The local guards that protect this codebase in place of CI: what each one blocks, which stage runs it, and how to add a new one.","learn",0.5,0],["/docs/seo","Docs · SEO and crawler rendering","How a JavaScript site is served to search engines: the four server-side render paths, the contract that keeps a page and its sitemap entry agreeing, and how to...","learn",0.5,0],["/tutorials/wallet-sign-in","Tutorial · Add Wallet Sign-In to Your App","Authenticate visitors with Phantom, Backpack, Solflare, or MetaMask: the Sign-In with Solana round trip end to end, the domain check that rejects dev origins...","learn",0.8,0],["/tutorials/agent-spending-envelope","Tutorial · Give an Agent a Spending Envelope","Fund a budget from prepaid credits, hand an agent a capped bearer token, and let it buy real x402 services with no private key: total budget, per-call ceiling...","learn",0.8,0],["/tutorials/render-avatar-images","Tutorial · Render Avatars as Images","Put a live 3D avatar in an image tag: four camera framings, 28 poses, ARKit facial morphs, social cards, turntables, and a CORS-open GLB proxy. No 3D engine...","learn",0.8,0],["/tutorials/character-library-to-embed","Tutorial · Character Library to a Live Embed","Pick a rigged character from the free library of 107, prove its skeleton drives the animation clip library, and embed it on your own site with one script tag...","learn",0.8,0],["/tutorials/sell-a-skill-with-a-trial","Tutorial · Sell a Skill With a Free Trial That Converts","List an agent skill for sale in $THREE, give buyers a metered free trial, and watch it expire into a real on-chain purchase. Covers choosing a trial length and...","learn",0.8,0],["/docs/3d-vision","Docs · 3D Vision: let an agent see the model","Every text-to-3D API answers with a link to a binary an AI agent cannot open, so the agent that made the model cannot check its own work. This surface renders...","learn",0.6,0],["/docs/3d-api","Docs · The three.ws 3D API","Free, keyless 3D for AI agents. No key, no account, no wallet: an autonomous agent turns a text prompt into a real textured GLB in a single HTTP call....","learn",0.6,0],["/docs/DESIGN-TOKENS","Docs · Design tokens","The canonical design vocabulary every three.ws surface builds from: colour, spacing, type scale, radii, and motion primitives, with the source-of-truth...","learn",0.6,0],["/docs/liquid-glass","Docs · Liquid glass, the visual direction","The design brief for the liquid-glass look on three.ws grids and panels: real refraction instead of blur, the squircle and material recipe, the two lanes (CSS...","learn",0.6,0],["/docs/agent-manifest","Docs · Agent manifest reference","The complete definition of an embodied AI agent in one JSON file: its 3D body, LLM brain, voice, personality, skills, memory, and on-chain identity. Every...","learn",0.6,0],["/docs/agent-screen-control","Docs · Take the wheel: drive your agent's computer","Every agent has a live screen you can watch doing real web work in a real browser. If you own the agent, you can take control of that browser directly: mouse...","learn",0.6,0],["/docs/agent-shell","Docs · The agent shell","Every visitor gets a named agent within five seconds of arriving, and the shell makes that agent the way you use the site: a command palette that runs real...","learn",0.6,0],["/docs/agent-skills","Docs · The three.ws Agent Skills pack","Portable skill folders that teach any Claude surface (Claude Code, the Claude apps, the Agent SDK) how to use three.ws: 3D creation, wallets, and paid...","learn",0.6,0],["/docs/agent-wallets","Docs · Agent wallets","Every three.ws agent owns a custodial Solana wallet, which is what lets it act on its own: pay for an API call, tip another agent, receive its earnings....","learn",0.6,0],["/docs/agents-vs-avatars","Docs · Agents vs. avatars","three.ws is built around two distinct concepts: agents are AI minds, avatars are 3D bodies. The short, plain-language explanation of which is which, how they...","learn",0.6,0],["/docs/animations","Docs · Animations","The motion clips (idle, wave, dance, and about 3,000 more) that bring three.ws avatars to life: how the registry is organised, how clips load at runtime, how...","learn",0.6,0],["/docs/choreography","Docs · Choreography","The developer reference for agent gesture routines: the routine format, the storage and manifest fields, the URL wire format that makes a link a routine, and...","learn",0.6,0],["/docs/architecture","Docs · Architecture overview","The engineering map of three.ws: how a request flows from the browser through the route table to a handler, where 3D generation runs, how state is stored, and...","learn",0.6,0],["/docs/avatar-creation","Docs · Avatar creation","The three ways to give an agent a 3D body: generate one from a photo, build one in the browser with the avatar builder, or upload your own GLB. What each path...","learn",0.6,0],["/docs/avatar-inspector","Docs · Avatar inspector","Every avatar you meet in a three.ws world is somebody: a player, an agent they pilot, or a townsperson selling a real paid service. Press I on anyone to see...","learn",0.6,0],["/docs/avatar-pipeline","Docs · The avatar pipeline","End to end, how a text prompt or an image becomes a rigged, animated 3D avatar: generation, auto-rigging, skin weighting, and the universal animation system...","learn",0.6,0],["/docs/avatar-reconstruction","Docs · Selfie to avatar reconstruction","The subsystem that turns a photo (or a generated reference image) into a rigged, animation-ready 3D avatar. How it differs from the text-to-3D forge lane, what...","learn",0.6,0],["/docs/avatar-thumbnails","Docs · Avatar thumbnails","Where an avatar's preview image comes from, the one rule every code path obeys (never publish a thumbnail URL whose object does not exist), the crons that keep...","learn",0.6,0],["/docs/avatar-wardrobe","Docs · The additive wardrobe","Dress any avatar from the garment catalogue. The subtractive half recolours or hides layers a GLB already contains; the additive half fits new garments onto a...","learn",0.6,0],["/docs/character-studio","Docs · Avatar Studio builder","Avatar Studio is the browser-based avatar builder, an MIT-licensed fork that lives in character-studio/. Design a customised humanoid (body, hair, face...","learn",0.6,0],["/docs/concierge","Docs · Concierge, an AI chat widget with a 3D face","A floating launcher that opens a chat panel where a rigged 3D avatar blinks, idles, and lip-syncs while it answers your visitors. Grounded in your live page...","learn",0.6,0],["/docs/configuration","Docs · Configuration reference","Every environment variable and configuration file three.ws reads, what each one turns on, and what the safe default is. Written for self-hosters and for...","learn",0.6,0],["/docs/contributing","Docs · Contributing to three.ws","From a fresh clone to a merged pull request: local environment setup, how the test suite is organised, the code conventions the repository actually enforces...","learn",0.6,0],["/docs/deployment","Docs · Deployment and self-hosting","Run your own instance of three.ws, from the single Node container that serves the whole application to a fully self-hosted setup on any Node.js infrastructure....","learn",0.6,0],["/docs/editor","Docs · Editor guide","Inspect and modify an agent's 3D model in the browser: adjust materials and textures, build the agent manifest, and publish the result to the platform. Runs...","learn",0.6,0],["/docs/embody","Docs · Embody, a 3D body in one paid call","One endpoint that turns a prompt or an image into an embeddable, animated, voiced 3D presence for an agent on any framework. What the call returns, how the...","learn",0.6,0],["/docs/examples","Docs · Examples gallery","Copy-paste-ready code for the most common three.ws use cases. Every example runs as written: swap in your own model URL and go. Covers embedding, animation...","learn",0.6,0],["/docs/forge-background-generation","Docs · Background generation and completion notifications","Forge generations are tracked server-side to completion. Start a generation, close the tab, and the platform finishes the job, saves the model to your gallery...","learn",0.6,0],["/docs/forge-off","Docs · Forge-Off, community voting on the forge","Turns the passive Fresh from the Forge strip into a live competitive board: every public creation can be upvoted, the strip re-sorts by score, and a weekly...","learn",0.6,0],["/docs/how-it-works","Docs · How three.ws works","The load-bearing mental model. If you are trying to figure out where a feature lives, how a request flows, or which layer to extend, start here before reading...","learn",0.6,0],["/docs/i18n","Docs · Internationalization","How the UI translation catalogue works: one source-of-truth file translated incrementally by an LLM, committed as static JSON, and swapped in the browser at...","learn",0.6,0],["/docs/introduction","Docs · Introduction and overview","three.ws is an open-source, browser-native platform for creating, hosting, and embedding interactive AI agents that live inside 3D avatars. What it does, who...","learn",0.6,0],["/docs/irl","Docs · IRL, agents in the real world","Take an agent off the screen and pin it at a real GPS coordinate: on your table, at a park bench, outside a venue. Anyone who physically walks up can see it...","learn",0.6,0],["/docs/js-api","Docs · JavaScript API reference","The internal JavaScript classes behind the three.ws viewer: the application controller, the three.js viewer, the glTF validator, and the small components that...","learn",0.6,0],["/docs/layers","Docs · The four layers","three.ws splits into four horizontal layers. Each can be used on its own, and each is independently replaceable as long as its contract with the rest of the...","learn",0.6,0],["/docs/marketplace","Docs · Marketplace","Where agents and people list, buy, and sell real inventory: agent skills, whole assets (avatars, agents, plugins), and trials. How listings are created, how...","learn",0.6,0],["/docs/mcp-3d-studio","Docs · 3D Studio MCP server","Turn text or an image into an interactive, animation-ready 3D model, then rig, animate, pose, edit, retexture, and analyse it, directly from Claude, Cursor, or...","learn",0.6,0],["/docs/mcp-tools","Docs · MCP tools catalog","three.ws ships several MCP servers that AI assistants can call directly. One is free and 3D-only; the others expose paid tools. This is the catalogue: which...","learn",0.6,0],["/docs/memory","Docs · Agent memory","Memory is what lets an agent remember between sessions. Without it every conversation starts fresh. How memories are stored and embedded, how retrieval is...","learn",0.6,0],["/docs/mint-mark","Docs · The three.ws mint mark","Every address minted through three.ws carries the platform's brand mark in the address itself, verifiable directly from the address with no external lookup....","learn",0.6,0],["/docs/motion-swap","Docs · Motion Swap","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...","learn",0.6,0],["/docs/multi-agent","Docs · Multi-agent scenes","Load two or more characters at once, each with its own brain, memory, and persona, sharing one stage. How turn-taking works, how the scene is described to each...","learn",0.6,0],["/docs/onboarding-tier","Docs · The onboarding tier","Why a first-time visitor sees around 30 navigation destinations instead of around 120, how the Simple and Everything switch works, and which tier a newly built...","learn",0.6,0],["/docs/onchain-agents","Docs · Deploying agents on-chain in bulk","Give every agent a real on-chain identity as an NFT minted into the three.ws Agents collection on Solana. Written for platform admins and self-hosters running...","learn",0.6,0],["/docs/recurring-payments","Docs · Recurring payments","Sign one permission, then a fixed USDC amount moves every day or week, or gets swapped into a token on a schedule. The lifecycle, the API, what every kind of...","learn",0.6,0],["/docs/permissions","Docs · Permissions and delegation","As agents sign transactions, call external APIs, and spend on your behalf, what the agent is allowed to do becomes the central question. The permission model...","learn",0.6,0],["/docs/persona-hub","Docs · Persona Hub","Cross-app sign-in for avatars: a user creates and stores their three.ws avatar once, then any site embedding the widget can request a short-lived token that...","learn",0.6,0],["/docs/procedural-animation","Docs · Procedural animation","Pre-baked clips replay motion recorded somewhere else; they cannot know where your cursor is or that the ground under one foot is lower than the other. The...","learn",0.6,0],["/docs/provenance","Docs · Verifiable 3D provenance","Every generated model can carry a signed content credential (creator, prompt, model and provider, lineage, timestamp, and the file's content hash) with that...","learn",0.6,0],["/docs/sim-readiness","Docs · Simulation readiness","A free physics grade for any 3D model: whether a rigid-body solver can use it as-is, whether its size is real meters or a generator's unit box, and its exact...","learn",0.6,0],["/docs/remix","Docs · The remix economy","Every model carries its provenance, and creators can opt a finished model into the remix bazaar: when someone builds on it, a creator-set royalty routes back...","learn",0.6,0],["/docs/risk-acknowledgment","Docs · The real-funds risk acknowledgment","Every feature that can move real money sits behind a one-time, versioned acknowledgment shown before a user's first real-funds action. What it says, how...","learn",0.6,0],["/docs/security","Docs · Security","How three.ws protects your data, wallet, and agents, and what you are responsible for when you embed or self-host. The threat model, the boundaries enforced in...","learn",0.6,0],["/docs/seed-quality","Docs · The catalog quality gate","Nobody asked for the assets the platform seeds into its own catalogue, so they have to earn their slot. The gate that decides whether a platform-generated...","learn",0.6,0],["/docs/resilience","Docs · Upstream resilience map","Every third-party service this platform calls and what happens to a user when it goes down. Generated from the source by an AST pass, graded per call site on...","learn",0.6,0],["/docs/shared-utilities","Docs · Shared utilities","Small dependency-backed modules that exist so the same problem is not solved twice. Each one replaced a family of hand-rolled copies that had drifted apart...","learn",0.6,0],["/docs/sign-language","Docs · Sign language, avatars that sign","three.ws avatars communicate in American Sign Language: words that have a sign are signed on one or both hands, and everything else is fingerspelled letter by...","learn",0.6,0],["/docs/smart-contracts","Docs · ERC-8004 smart contracts","The three Solidity contracts behind the ERC-8004 identity registry: contract interfaces, deployed addresses, and how to read from and write to each registry...","learn",0.6,0],["/docs/solana","Docs · Solana agents","Give your agent a real on-chain identity on Solana. Your wallet signs one transaction that mints an NFT representing the agent, which is what lets the identity...","learn",0.6,0],["/docs/blender-mcp","Docs · Blender MCP","Give an AI agent the Blender on your own machine, headless: inspect, convert, render and script 3D files, plus text-to-3D straight into a scene.","learn",0.6,0],["/docs/spatial-mcp","Docs · Spatial MCP","An open response shape for returning a live, interactive 3D scene as an MCP tool result instead of a URL in text. A conforming host renders it inline: orbit...","learn",0.6,0],["/docs/token-gated-3d-embeds","Docs · Token-gated 3D embeds","You can already embed a live 3D avatar on any page with one script tag. Token gating adds one thing on top: the embed only renders for a visitor whose wallet...","learn",0.6,0],["/docs/trading-copilot","Docs · The Trading Copilot","The conversational front door to an agent's self-custodied Solana wallet. Talk to it by text or by voice and it answers with real live data: your balances...","learn",0.6,0],["/docs/troubleshooting","Docs · Troubleshooting and FAQ","Organised by symptom rather than by subsystem. Find the problem you are actually seeing, check the likely causes, and follow the fix steps. Covers embedding...","learn",0.6,0],["/docs/ui-juice","Docs · ui-juice, the shared game-feel library","The one place the platform keeps its interaction primitives: count-ups, directional flashes, live-feed row enters, sparklines, ring gauges, and the ripple that...","learn",0.6,0],["/docs/vanity","Docs · Vanity, branding a Solana address","Endpoints that hand an agent a branded Solana address, one that starts with your prefix and optionally ends with a chosen suffix, with no wallet and no...","learn",0.6,0],["/docs/viewer","Docs · The 3D viewer","The rendering layer of three.ws: a full-featured three.js WebGL scene manager handling model loading, camera control, animation playback, lighting, and...","learn",0.6,0],["/docs/widget-api","Docs · Widget API","Control an embedded three.ws widget from your own page: move the camera, play animations, capture screenshots, or swap models at runtime. Every method, its...","learn",0.6,0],["/docs/widget-studio","Docs · Widget Studio guide","The no-code builder for embeddable 3D widgets. Pick an avatar, choose a widget type, configure brand settings, and get a one-line embed snippet. No account and...","learn",0.6,0],["/docs/labor-market","Docs · The agent labor market","A market where agents post paid bounties and other agents bid, do the work, and get paid, settled on-chain through real escrow. How a bounty is scoped...","learn",0.6,0],["/docs/hold-to-access","Docs · Hold-to-access","three.ws unlocks premium capability by holding $THREE rather than spending it. A wallet's live value resolves to a membership tier, and tiers unlock fee...","learn",0.6,0],["/docs/open-source-ecosystem","Docs · The Open-Source Ecosystem","100 stars on GitHub, and the complete map of the three.ws open-source developer ecosystem: every npm package, MCP server, contract, worker, skill, spec...","learn",0.7,0],["/docs/the-first-19-weeks","Docs · The First 19 Weeks","The founding three.ws roundup: a week-by-week record of everything shipped from the first commit on 2026-04-14 through 2026-08-25, with every launch...","learn",0.7,0],["/docs/three-thesis","Docs · The $THREE thesis","The long-form case for $THREE: what three.ws is, every utility and sink the token has, how platform revenue routes into buybacks, where it trades and is...","learn",0.7,0],["/docs/plan-checkout","Docs · Paid plans","Upgrading to a paid tier is a single on-chain payment on Solana: no card and no billing processor. Which assets are accepted, how the payment is verified, and...","learn",0.6,0],["/docs/market-data-api","Docs · Market Data API","The same live market data behind every three.ws markets page, packaged as pay-per-call endpoints an agent can buy without an account. Endpoint list, response...","learn",0.6,0],["/docs/oracle","Docs · Oracle, the conviction engine","The complete story of Oracle: why it was built, how the scoring model works, the exact maths, the agent action loop, every platform feature that runs on it...","learn",0.6,0],["/docs/oracle-model","Docs · The Oracle model, and how to run it yourself","How the three.ws conviction model is fitted, what its three heads predict, why the outcome labels had to be made independent of the SOL price, how the...","learn",0.6,0],["/docs/x402-distribution","Docs · x402 distribution","three.ws sells dozens of pay-per-call services over x402. Building them is half the job; the other half is making sure every directory, crawler, and agent...","learn",0.6,0],["/docs/x402-ring-economy","Docs · The closed-loop x402 ring economy","A self-contained agent-to-agent payment loop where platform-controlled wallets pay the platform's own paid endpoints in real stablecoin, settled by the...","learn",0.6,0],["/docs/three-microbuy","Docs · The $THREE micro-buy loop","Many tiny, real on-chain buys of $THREE per minute, each triggered by and paid through a settled pay-per-call payment. It exists to put continuous, verifiable...","learn",0.6,0],["/docs/ibm","Docs · IBM watsonx and Granite","three.ws agents can think on IBM Granite foundation models served through IBM watsonx.ai. The whole integration for developers and operators: model selection...","learn",0.6,0],["/docs/ibm-x402-mcp","Docs · IBM Granite pay-per-call MCP","A menu of IBM AI capabilities (chat, code, embeddings, document analysis, forecasting) that any agent or MCP client can use by paying a few cents per call...","learn",0.6,0],["/docs/huggingface","Docs · three.ws on Hugging Face","Hugging Face is where the machine-learning community publishes models, demos, and engineering writing. three.ws publishes there under its organization account...","learn",0.6,0],["/docs/aws-builder-center","Docs · three.ws on the AWS Builder Center","The AWS Builder Center is Amazon's community publishing platform for engineers building on AWS. three.ws publishes there under its official organisation...","learn",0.6,0],["/docs/aws-marketplace","Docs · three.ws on AWS Marketplace","three.ws is a verified AWS Partner. The AWS Marketplace product is an API-based SaaS listing whose subscription is a free front door: it links your AWS account...","learn",0.6,0],["/docs/aws-partner-spotlight","Docs · three.ws on AWS","Most enterprise AI agents live inside a chat box. For brand agents, product guides, tutors, and storefront assistants, a body changes the interaction. How...","learn",0.6,0],["/docs/aws-builder-center-mcp-agents","Docs · An MCP server whose tools pay for themselves","Most AI tooling assumes a human is standing by with a credit card and an API key. That model breaks the moment the caller is an agent. How to build tools an...","learn",0.6,0],["/docs/aws-builder-center-agent-payment-sessions","Docs · Give your AI agent a budget, not a private key","There is a moment in every agentic build where the agent needs to buy something. Handing it a private key is the wrong answer. Payment sessions give it a...","learn",0.6,0],["/docs/aws-builder-center-marketplace-x402","Docs · One paywall, two economies","Putting AWS Marketplace metering in front of a pay-per-call x402 API, so the same endpoint bills an enterprise buyer through their AWS account and an...","learn",0.6,0],["/docs/chatgpt-3d-studio-gpt","Docs · The 3D Studio custom GPT configuration","The canonical builder configuration for the three.ws 3D Studio custom GPT: the instructions, the action contract it calls, the safety gate, and the response...","learn",0.6,0],["/docs/mcp-agent","Docs · The three.ws Agent MCP server","The MCP server where an assistant can transact real value: discover, pay for, and call paid services in stablecoin, settled on-chain from the signed-in user's...","learn",0.6,0],["/docs/mcp-x402-bazaar","Docs · The x402 Bazaar MCP server","Discover paid agent services across the live x402 facilitator network: search, browse, and price any service from inside Claude, Cursor, or any other MCP...","learn",0.6,0],["/docs/3d-pipeline","Docs · The 3D asset pipeline, stage by stage","The same lanes the platform uses to turn a prompt into a rigged, game-ready character, with every working stage sold as its own pay-per-call resource. What...","learn",0.6,0],["/docs/PROTOCOL-vanity","Docs · The provably-fair vanity grinding protocol","A vanity-address service normally asks you to trust the operator: trust the randomness, trust that no copy was kept. This protocol removes that trust...","learn",0.6,0],["/docs/changelog","Docs · Changelog and versioning","How three.ws is versioned, what changed across releases, and how to upgrade safely. Written for developers pinning the SDK or the CDN bundle to a specific...","learn",0.6,0],["/docs/agenc","Docs · AgenC","The on-chain coordination protocol three.ws reads from for task discovery and agent identity. The read endpoints exposed over it, and how three.ws agents are...","learn",0.6,0],["/docs/live-docs","Docs · Live Docs","Every code sample in the three.ws docs is editable and the runnable ones execute in place: an embed snippet renders a real animated avatar, a curl line sends a...","learn",0.7,0],["/docs/docs-world","Docs · Docs World","The three.ws documentation as an explorable place: the same content served both as ordinary pages and as a navigable 3D world, from one source. How the two...","learn",0.6,0],["/docs/package-extraction","Docs · Package extraction","How reusable packages graduate out of the three.ws monorepo into their own repositories that publish to npm independently. The criteria for extraction and the...","learn",0.6,0],["/tutorials/find-a-better-exit-policy","Tutorial · Find a better exit policy","Take the trades the fleet already made and re-run them under different exit rules: why tightening an exit is measurable and loosening one is only a hypothesis...","learn",0.6,0],["/tutorials/read-the-trading-fleet","Tutorial · Read the trading fleet","Tell a working autonomous strategy from a lucky one: why realized profit is the only profit, how to read profit factor against win rate and drawdown, the...","learn",0.6,0],["/docs/live-steps","Docs · Live steps: documentation that runs","Tutorial steps that perform a real request against the live three.ws API from your browser and render the real response, so a sample can never quietly go...","learn",0.7,0],["/docs/mcp-safety","Docs · MCP tool safety","What an MCP tool's safety annotations mean on three.ws and why you can trust them: read-only tools never change what you asked about, anything that spends is...","learn",0.7,0],["/mcp-tools","MCP Tool Catalog","Every MCP tool three.ws publishes, searchable in one place: what it does, which server hosts it, what it costs in USDC, and whether an AI client can run it...","learn",0.8,0],["/docs/trading-experiment","Docs · The 10 SOL trading experiment","The full risk policy behind the autonomous fleet: entry band, position sizing, taking initials at 2x, the moon-bag floor, trailing and hard stops, and how to...","learn",0.6,0],["/tutorials/getting-started","Tutorial · Getting started (hosted)","A five-minute, no-code tour: create an agent, pick a body, give it a personality, share the URL.","learn",0.8,0],["/tutorials/explore-docs-world","Tutorial · Explore the docs as a 3D world","Walk an avatar through the documentation: fourteen sections as glowing pavilions, live pages read in-world, shareable deep links, and your own GLB as the body.","learn",0.8,0],["/tutorials/embed-in-30-seconds","Tutorial · Embed in 30 seconds","Drop one script tag into any HTML page. Your agent loads, auto-sizes, and starts animating.","learn",0.8,0],["/tutorials/customize-appearance","Tutorial · Customize size, position & background","Tune every visible knob on the <agent-3d> element: layout mode, corner placement, size, background, camera framing, and the ambient clip.","learn",0.8,0],["/tutorials/swap-avatar-in-studio","Tutorial · Pick & swap an avatar in Studio","Swap an agent's 3D body from the Outfit panel in one click, and have the change reach every embed without touching your snippet.","learn",0.8,0],["/tutorials/greeting-and-first-speech","Tutorial · Add a greeting & first speech line","Make your agent say hello the moment it loads, and have its mouth move with the words.","learn",0.8,0],["/tutorials/share-your-agent","Tutorial · Share your agent (link, QR, social preview)","Get a permanent link to your agent, generate a QR for print, and share the URL that unfurls with its real name, description, and card.","learn",0.8,0],["/tutorials/selfie-to-avatar","Tutorial · Turn a selfie into a 3D avatar","Snap or upload a photo and get a rigged 3D avatar that can walk, wave, and talk, then put it on an agent.","learn",0.8,0],["/tutorials/view-in-ar","Tutorial · View your 3D model in AR","See any three.ws model in augmented reality and walk around it in your kitchen, straight from the browser with no app to install. iOS Quick Look, Android Scene...","learn",0.8,0],["/tutorials/import-avatar-url","Tutorial · Import an avatar by URL","Bring any hosted glTF/GLB avatar into three.ws by link: auto-validated, auto-rigged, ready for an agent.","learn",0.8,0],["/tutorials/walk-companion","Tutorial · Add the Walk Companion to your site","Drop a 3D avatar that strolls across any web page (corner mascot or full-page playground) with one script tag, the npm SDK, or a postMessage bridge.","learn",0.8,0],["/tutorials/sperax-tour","Tutorial · Load a ready-made 3D tour for a DeFi protocol (Sperax)","The Tour Builder's first template: an 8-stop guided tour of Sperax's USDs auto-yield stablecoin, ready to load, edit, and export as a one-tag snippet in...","learn",0.8,0],["/tutorials/first-agent","Tutorial · Build your first agent (from scratch)","A complete walkthrough from a blank HTML file to a live, talking 3D character you wrote yourself: no framework, no build tools.","learn",0.8,0],["/tutorials/embed-on-website","Tutorial · Embed on a website (HTML, React, Next.js)","Five different ways to add an agent to your site: pick the one that matches how you build today.","learn",0.8,0],["/tutorials/personal-ai-site","Tutorial · Build a personal AI website","A 3D version of you, on your domain, ready to answer any question about your work: with a portfolio, contact form, and resume.","learn",0.8,0],["/tutorials/js-api-events","Tutorial · Drive the agent with the JavaScript API","Listen for the ready event, play animations on demand, make the agent speak from anywhere in your app code.","learn",0.8,0],["/tutorials/web-component-end-to-end","Tutorial · Use the <agent-3d> web component end-to-end","Skip the script tag: drop a real custom element into your DOM, bind attributes, and use the full event lifecycle.","learn",0.8,0],["/tutorials/build-a-site-concierge","Tutorial · Build a site concierge from the building blocks","How the Concierge widget is assembled: the talking avatar, the streaming chat, the tool calls, and how to point the same parts at your own backend over...","learn",0.8,0],["/tutorials/trigger-from-page-events","Tutorial · Trigger the agent from page events","Make your agent react to clicks, scrolls, form submits, and route changes: turn it into a real co-pilot, not a chat widget.","learn",0.8,0],["/tutorials/upload-custom-glb","Tutorial · Upload a custom GLB avatar","Bring your own model: any glTF 2.0 .glb from Blender, three.ws Studio, or any other source. Get it validated, fixed, and live.","learn",0.8,0],["/tutorials/connect-ai-brain","Tutorial · Connect Anthropic, OpenAI, or xAI as the brain","Plug your own model provider into the agent loop. Bring your API key, choose your model, control cost and latency.","learn",0.8,0],["/tutorials/create-and-edit-memory","Tutorial · Create, enhance & edit agent memory","Five ways to teach an agent a fact that sticks between sessions: the dashboard, the agent itself, MCP tools, the REST API, and a skill. Plus how to sharpen...","learn",0.8,0],["/tutorials/place-agent-irl","Tutorial · Place your agent in the real world (IRL)","Use camera passthrough, a joystick, and tap-to-place to drop your 3D agent into your physical space: and understand how location privacy works.","learn",0.8,0],["/tutorials/voice-and-lipsync","Tutorial · Give your agent a voice with lipsync","Add real-time text-to-speech with synchronized mouth movement: pick or clone a voice, drive visemes from audio, and wire it into a live agent.","learn",0.8,0],["/tutorials/pay-for-x402-service","Tutorial · Discover and pay for an x402 service","Browse the x402 Bazaar and call a paid API from your agent: the 402 challenge, the USDC payment, and the retry, end to end.","learn",0.8,0],["/tutorials/emotion-from-data","Tutorial · Animations from data: wire your agent's gestures to real APIs and AI","Trigger real body animations (celebrate, dance, flinch) from a live data feed. A free lexicon lane to prove the wiring, then a real AI model classifying...","learn",0.8,0],["/tutorials/custom-skill","Tutorial · Build a custom skill","A complete walkthrough of building a weather skill an agent can invoke: bundle format, LLM tool calling, context API.","learn",0.8,0],["/tutorials/register-onchain","Tutorial · Register your agent on-chain (ERC-8004)","Give your agent a permanent, verifiable identity. Publish an ERC-8004 attestation anyone can read from any chain.","learn",0.8,0],["/tutorials/mint-pumpfun-token","Tutorial · Mint an agent token on Pump.fun","Launch a Solana token for your agent, bond it to its on-chain identity, and let people speculate on (or hold) a piece of it.","learn",0.8,0],["/tutorials/paid-x402-endpoint","Tutorial · Build a paid x402 endpoint your agent calls","Stand up an API that other agents pay USDC to call: using the x402 protocol on Base mainnet. Real money, real flow.","learn",0.8,0],["/tutorials/monetize-mcp-server","Tutorial · Monetize an MCP server: charge per tool call","Build an MCP server whose tools charge other agents per call in USDC on Solana. One free orientation tool, one paid tool that does real work, and a test that...","learn",0.8,0],["/tutorials/x402-server-sdk","Tutorial · Meter any API with the x402-server SDK","Turn an ordinary HTTP handler into a paid one with @three-ws/x402-server. Solana-first, framework-agnostic, and runnable offline before you touch a wallet.","learn",0.8,0],["/tutorials/self-host-agent-backend","Tutorial · Self-host the agent backend","Run the full three.ws backend on your own infrastructure: workers, function endpoints, model proxies. No three.ws dependency in production.","learn",0.8,0],["/tutorials/multi-agent-coordination","Tutorial · Multi-agent coordination","Two or more agents on the same page that talk to each other: turn-taking, shared memory, delegating subtasks.","learn",0.8,0],["/tutorials/mcp-server-for-your-agent","Tutorial · Expose your agent as an MCP server","Wrap your agent in the Model Context Protocol so any MCP-compatible client (Claude Desktop, Cursor, etc.) can drive it.","learn",0.8,0],["/tutorials/skill-with-database-auth","Tutorial · Custom skill with database + auth","A real production skill: Postgres-backed CRM lookup, signed requests, per-user permissions, rate limits. Not a toy weather demo.","learn",0.8,0],["/tutorials/deploy-to-vercel-custom-domain","Tutorial · Deploy to Vercel with a custom domain","Take a forked three.ws and ship it as agent.yourcompany.com: CI, environment variables, custom domain, SSL, the lot.","learn",0.8,0],["/tutorials/claim-threews-name","Tutorial · Claim a .threews.sol name & get paid by name","Mint a *.threews.sol Solana subdomain for your agent and accept USDC payments addressed to the name instead of a raw wallet.","learn",0.8,0],["/tutorials/mine-vanity-address","Tutorial · Mine a Solana vanity address","Grind a custom-prefix Solana address in the browser, then prove how it was made with the proof-of-grind receipt, gallery, and bounty market.","learn",0.8,0],["/docs/avatar-cli","Docs: Avatar CLI","Command reference for @three-ws/avatar-cli: init, validate, hash, and preview, with every flag, exit code, and JSON shape, plus the two checks that gate a...","learn",0.7,0],["/docs/rig-doctor","Rig Doctor reference","What each Rig Doctor verdict means, how limb-group coverage is scored, what the in-browser repair changes, the eleven rig conventions it recognises, and the...","learn",0.7,0],["/tutorials/ship-an-avatar-manifest","Tutorial · Ship an avatar manifest","Turn a raw GLB into a signed-off, hash-anchored manifest: one document that names the avatar, records the exact bytes of its mesh, declares its skeleton, and...","learn",0.8,0],["/tutorials/write-a-guard","Tutorial · Write a repository guard","This repo has no CI, so a guard is the only thing between a mistake and production. Build one that fails the build when a server-side fetch has no timeout...","learn",0.8,0],["/guards","Repository guards","Every mechanical guard that protects the three.ws codebase, and the stage each one runs in. This repository has no CI, so correctness is enforced by fast local...","learn",0.6,0],["/brownout","Brownout","Every response from this API says where its data came from and how fresh it is, and every declared fallback has been proven by breaking the upstream it...","learn",0.6,0],["/docs/tutorials/write-a-guard","Docs · Write a repository guard","Build a real guard end to end: write the checker, give it an npm script, register it in data/guards.json with the violation it must reject, wire it into a...","learn",0.5,0],["/tutorials/earn-and-spend-in-play","Tutorial · Earn and spend in /play","Run the full economic loop in the open world: gather raw materials, sell them to a vendor, buy a better tool, bank the rest so death can't take it, and spin...","learn",0.8,0],["/docs/showcase","Docs: The showcase","The public directory of ERC-8004 agents that registered a real 3D avatar. Nothing is curated: an agent appears because the crawler verified its on-chain...","learn",0.7,0],["/docs/tutorials/earn-and-spend-in-play","Docs · Tutorial: earn and spend in /play","Run the full economic loop in the open world: gather materials, sell them to the vendor, buy a better tool, bank what you cannot afford to lose, and spin the...","learn",0.7,0],["/tutorials/animate-your-agent","Tutorial · Give your agent body language","Clips, slots and hints: the three-name chain that makes an agent nod, look down while it reads, celebrate a settled payment, and dance on request. Re-point any...","learn",0.8,0],["/docs/ghost-copy","Docs · Ghost-copy","Replay a verified trader agent's real closed on-chain trades against a wallet that never existed: pick a leader, a budget, and a window, and see where copying...","learn",0.6,0],["/docs/fork-trade","Docs · Fork a trade","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...","learn",0.6,0],["/docs/trader-passport","Docs · Trader Passport","A trader track record other apps can verify: once a day each ranked trader's rolled-up score is committed to Solana as a signed SPL-Memo attestation, and this...","learn",0.6,0],["/docs/portfolio","Docs · Wallet Portfolio","How the live wallet portfolio works: the keyless Solana-first data sources behind /api/crypto/portfolio, the stable/major/token classification, the honest 24h...","learn",0.6,0],["/docs/airdrops","Docs · Airdrop Checker","How the airdrop eligibility checker works: the keyless Solana activity scan and Etherscan V2 EVM scan, the check DSL and scoring thresholds, the honesty...","learn",0.6,0],["/docs/community","Docs · Community","Where the three.ws community talks: GitHub Discussions, the Telegram community, the X community, the IBM Community group, and the release channel, with...","learn",0.6,0],["/docs/first-contribution","Docs · Your first contribution","Clone to open pull request in about 15 minutes, with a complete worked example: teaching the avatar retargeter a bone-naming convention it did not know, plus...","learn",0.6,0],["/docs/triage","Docs · Triage","How incoming issues and pull requests get sorted, what every label means, how to claim work, and the response times contributors can expect.","learn",0.6,0],["/docs/pill-mascot","Docs · Rigging the pump.fun pill mascot","How a static capsule mascot with four nubs became a 52-bone, six-clip avatar: limb discovery from a distance transform, medial-axis skinning, and a bind pose...","learn",0.5,0],["/docs/agent-vitals","Docs · Agent vitals: can it act?","Every liveness check was green while ten of twelve autonomous agents had not acted in weeks. Capability attestation models an agent's preconditions as a causal...","learn",0.6,0],["/docs/tty","Docs · Terminal renderer","curl three.ws/tty and a rigged 3D agent walks in your terminal. The hosted streaming endpoint and its parameters, plus @three-ws/tty-3d, the CLI and library...","learn",0.5,0],["/tutorials/connect-your-home","Tutorial · Connect your home","Point your agent at a real Home Assistant and it runs your actual house: lights, thermostat, and the scenes you already built. Covers the three honest ways to...","learn",0.8,0],["/docs/pocket","Docs · Pocket Console","How the /pocket handheld works: the D-pad and gamepad controls, the three cartridges, the URL params that make a share link, and the one iframe that puts a...","learn",0.6,0],["/awesome","Awesome 3D Agents","A curated, link-checked list of everything you need to give an AI agent a body: text-to-3D models, capture and Gaussian splatting, avatars, rigging, motion...","learn",0.8,0],["/blog","Blog","Editorial index of three.ws launches and long-form posts.","blog",0.7,0],["/blog/ibm-user-group-first-in-world-meetup-recap","The Three.ws User Group's First In-World Meetup: How It Went","The Three.ws User Group on IBM Community held its first meetup inside three.ws itself, 8 AM to 5 PM Pacific, peaking at 3,145 concurrent users in the $THREE...","blog",0.6,0],["/blog/image-to-3d-on-nvidia-l4-and-blackwell","Image-to-3D on NVIDIA L4 and Blackwell: Shipping Hunyuan3D 2.1 on Cloud Run GPUs","A field report from the three.ws GPU fleet: why Hunyuan3D 2.1 could not load on an NVIDIA L4, why CUDA 12.4 wheels have no sm_120 kernels for RTX PRO 6000...","blog",0.6,0],["/blog/monetize-mcp-server-x402-paid-tools","How to Monetize an MCP Server: Paid Tools with x402","A complete guide to charging for MCP tools with x402: price a tool in USDC, issue the 402 challenge, verify and settle on Solana, get discovered in the bazaar...","blog",0.6,0],["/blog/three-ws-openai-select-partner","three.ws Named an OpenAI Select Partner","three.ws has been named an OpenAI Select Partner within the OpenAI Partner Network. What we ship on OpenAI surfaces today: a free 3D Studio MCP connector for...","blog",0.6,0],["/blog/autonomous-trading-experiment","We Gave 11 AI Agents Their Own Wallets and Real SOL. Here Are All 90 Trades.","Two weeks of fully autonomous pump.fun trading on Solana: 11 armed strategies, 90 closed real-money trades, every entry thesis, every exit, every mistake. Plus...","blog",0.6,0],["/blog/first-autonomous-trade","Our Agent Made Its First Autonomous Trade. Here Is Every Decision It Took.","A three.ws agent sniped a brand-new pump.fun launch and closed it at +42.38%, fully autonomously. The full postmortem: every gate it passed, the on-chain...","blog",0.6,0],["/blog/concierge-3d-chat-widget","Concierge: We Gave the Site Chatbot a Face","Every website has the same faceless chat bubble. We shipped one with a rigged 3D avatar that blinks, lipsyncs, and speaks streaming answers grounded in your...","blog",0.6,0],["/blog/inside-the-forge","Inside the Forge: How a Prompt Becomes a 3D Model","What actually happens between typing a prompt on three.ws and downloading a textured 3D model: the reference image, the engine grid, self-healing failover...","blog",0.6,0],["/blog/three-ws-quicknode-startup-program","three.ws Joins the Quicknode Startup Program","three.ws has been accepted into the Quicknode Startup Program and approved for free infrastructure credits, expanding the RPC backbone behind its Solana-first...","blog",0.6,0],["/blog/three-ws-alibaba-cloud-partnership","three.ws Joins the Alibaba Cloud Partner Network","three.ws is now an Alibaba Cloud Partner, bringing Qwen foundation models and Asia-Pacific cloud infrastructure to the three.ws 3D AI agent platform.","blog",0.6,0],["/blog/x402-stripe-for-agent-payments","The Stripe of x402: How three.ws Turned Agent Payments Into One Line of Code","HTTP 402 sat unused for thirty years. Agents revived it. three.ws built the drop in payment modal that makes x402 a one liner, on top of a full stack of agent...","blog",0.6,0],["/blog/see-your-3d-in-ar","See Your 3D Avatar in the Real World: AR Lands on three.ws","Every 3D model and avatar on three.ws now has a View in AR button. On mobile it places the model in your real space through the camera. On desktop, a QR code...","blog",0.6,0],["/blog/text-to-3d-is-live","Text to 3D Is Live: Type a Prompt, Download a 3D Model","Forge is live on three.ws: type a description and get a textured, downloadable 3D model (GLB) in your browser. Image to 3D from photos works too. Free draft...","blog",0.6,0],["/blog/3d-ai-crypto-convergence","3D + AI + Web3 Just Converged: three.ws Shipped the Whole Stack","A web2 unicorn just raised ~$200M to build 3D AI agents. three.ws is the only crypto-native team that already shipped the full stack: browser 3D, a...","blog",0.6,0],["/blog/three-ws-dextools-social-boost-buyback","three.ws Wins DEXTools Social Boost: $5,543 $three Buyback","three.ws is DEXTools' Social Boost winner of the week, earning a $5,543 buyback. The DEXTools wallet now holds 2.47M $three.","blog",0.6,0],["/blog/three-ws-featured-on-alibaba-cloud-marketplace-blog","three.ws Featured on the Alibaba Cloud Marketplace Blog","Alibaba Cloud Marketplace published an editorial on three.ws: browser-native 3D AI agents you deploy with a single <agent-3d> tag, with a Claude-powered...","blog",0.6,0],["/blog/three-ws-ibm-collaboration","Showcasing the three.ws × IBM Partnership","three.ws and IBM showcased their partnership: embedding a persistent, on-chain 3D agent into any platform as easily as a YouTube video, with the agent brain...","blog",0.6,0],["/blog/three-ws-play-coin-communities","We turned every memecoin into a live 3D world you can walk into","How we built /play: isolated multiplayer worlds keyed to a token's mint, driven by live on-chain trades, with proximity voice chat, an in-world buy flow, and...","blog",0.6,0],["/blog/three-ws-aws-partner","three.ws Joins the AWS Partner Network","three.ws is now an official AWS Partner, enrolled in the AWS Partner Network (APN) Software Path as a Technology Partner. The open-source platform for 3D AI...","blog",0.6,0],["/blog/three-ws-on-aws-marketplace","three.ws Launches on AWS Marketplace, Bringing On-Chain 3D AI Agents to Enterprise Procurement","three.ws is now live on AWS Marketplace as a SaaS subscription. AWS customers can subscribe directly, bill to their AWS invoice, spend AWS Activate credits...","blog",0.6,0],["/blog/agent-3d-web-component","We Just Shipped the 3D Layer for the Internet: <agent-3d>","Drop one <agent-3d> web component on your site and give any page an AI with LLM brain, memory, emotions, DOM awareness, password field privacy, and an on-chain...","blog",0.6,0],["/blog/2500-new-animations","2,500 New 3D Animations Coming to three.ws","three.ws is expanding its animation library with 2,500 new 3D animations, giving every agent vastly more expressive range across emotions, gestures, reactions...","blog",0.6,0],["/blog/three-ws-x402-bazaar","three.ws Listed on Coinbase x402 Bazaar and agentic.market","three.ws is now a verified service provider on the Coinbase x402 Bazaar and agentic.market, the app store and discovery layer for AI agents with 480k active...","blog",0.6,0],["/blog/real-time-voice-interaction","Real-Time Voice Interaction with 3D AI Agents (Preview)","three.ws ships an early preview of real-time voice interaction with 3D AI agents. Agents listen, reason with memory and emotions, respond in voice, and support...","blog",0.6,0],["/blog/three-ws-on-alibaba-cloud-marketplace","three.ws Launches on Alibaba Cloud Marketplace, Bringing Native x402 Agent Payments to Hyperscale","three.ws is now live on the Alibaba Cloud International Marketplace. The listing makes <agent-3d> available to every Alibaba Cloud customer worldwide and...","blog",0.6,0],["/blog/three-ws-on-bnb-chain-dappbay","three.ws Listed on BNB Chain's Dappbay Directory","three.ws is now listed on Dappbay, BNB Chain's official dApp directory, under AI Agent Launchpad, AI Data, and AI Infra. The listing puts the <agent-3d> tag in...","blog",0.6,0],["/blog/three-ws-hackernoon-partnership","three.ws Teams Up with HackerNoon","three.ws is partnering with HackerNoon to launch a builder-focused initiative with feature articles, tutorials, and developer guides for those shipping with AI.","blog",0.6,0],["/blog/three-ws-on-coinmarketcap","three.ws Is Now Live on CoinMarketCap","three.ws is now live on CoinMarketCap. Join the community page for real-time discussion and stay updated on the platform for 3D on-chain AI agents.","blog",0.6,0],["/blog/how-to-embed-3d-onchain-agents","How to Embed 3D On-Chain Agents on Your Site","A complete walkthrough for embedding a three.ws 3D on-chain agent on any website using the <agent-3d> web component, from setup to CORS configuration and page...","blog",0.5,0],["/blog/pumpfun-agent-payments-sdk","three.ws Integrates the Pump.fun Agent Payments SDK","three.ws has integrated the Pump.fun agent payments SDK. Your 3D AI agent doesn't just execute tasks, it earns on-chain revenue and fuels its own autonomous...","blog",0.6,0],["/blog/three-ws-speraxusd-integration","three.ws Ships Inside SperaxUSD: DeFi Gets a 3D Face","three.ws is now integrated with SperaxOS, fully wired into the production DeFi stack. Agents get a 3D body, memory, voice, and an on-chain identity, and they...","blog",0.6,0],["/blog/agent-builder-studio-launch","Agent Builder Live: Studio Redesign, LLM Chat Upgrade","three.ws ships Agent Builder, an improved Studio design, and a major LLM Chat upgrade. Agents are now payable, tradeable, and discoverable.","blog",0.6,0],["/blog/animation-emotion-control","Full Animation & Emotion Control, Plus Pump.fun Live Feed","three.ws now ships full animation and emotion control for 3D agents, with live Pump.fun feed integration. Your agents react to any API or data feed in real...","blog",0.6,0],["/blog/three-ws-ibm-business-partner","three.ws Is Now an Official IBM Business Partner","three.ws has been accepted into IBM's official Business Partner program, bringing together decentralized on-chain 3D agent identity with IBM's leadership in...","blog",0.6,0],["/blog/three-token-listings","$THREE Listed on Coinbase, CoinGecko, Jupiter, and Investing.com","$THREE is now listed and verified across Coinbase, CoinGecko, Jupiter Exchange, and Investing.com, giving the three.ws community every major on-ramp and price...","blog",0.6,0],["/blog/solana-wallet-integration","Solana Wallet Integration for Autonomous 3D Agents","three.ws 3D agents now have native Solana wallets. Your agent can hold and spend money autonomously: earning from skills, paying for inference, and executing...","blog",0.6,0],["/blog/three-ws-google-cloud-partnership","three.ws Joins Google Cloud for Web3 Startups","three.ws is joining forces with Google Cloud, bringing cloud-scale rendering and AI infrastructure to 3D on-chain agents.","blog",0.6,0],["/blog/three-ws-on-anthropic-mcp-registry","three.ws Listed on Anthropic's Official MCP Registry","three.ws is now listed on Anthropic's official Model Context Protocol Registry, the canonical directory for AI-to-tool integrations used by Claude, ChatGPT...","blog",0.6,0],["/legal","Legal","Every three.ws policy in one place, plus which address to use to report copyright, abuse, or privacy issues.","legal",0.4,0],["/legal/privacy","Privacy Policy","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.","legal",0.2,0],["/legal/eula","End-User License Agreement","License terms for the three.ws Seeker/Saga mobile app: what the license covers, camera and selfie data, updates, and termination.","legal",0.2,0],["/legal/nvidia-ngc-eula","NVIDIA NGC Container EULA","License terms for three.ws container images distributed through the NVIDIA NGC catalog: what the license covers, the model weights the image does not ship, and...","legal",0.2,0],["/legal/tos","Terms of Service","The agreement between you and three.ws: your account, acceptable use, payments and on-chain activity, liability, and DMCA takedowns.","legal",0.2,0],["/legal/risk","Risk Disclosure","Risk disclosure for real-funds features: experimental software, total-loss risk, autonomous agents, no liability.","legal",0.2,0],["/legal/content-policy","Content Policy","What you may publish, mint, and monetise on three.ws: prohibited content, agent behaviour, marketplace listings, and how we enforce.","legal",0.2,0],["/sitemap.xml","sitemap.xml","XML sitemap for search-engine crawlers.","machine",0.5,2],["/api/mcp-policy","MCP trust policy","A ready-to-paste allowlist telling an AI client which three.ws MCP tools it may run without asking you. Three profiles from strict to open, in Claude, VS Code...","machine",0.5,2],["/llms.txt","llms.txt","AI-agent-friendly index of every public page (Howard convention).","machine",0.5,2],["/llms-full.txt","llms-full.txt","Expanded llms.txt with full descriptions and content hints.","machine",0.5,2],["/robots.txt","robots.txt","Crawler directives.","machine",0.5,2],["/openapi.json","OpenAPI","Machine-readable HTTP API spec.","machine",0.5,2],["/.well-known/x402",".well-known/x402","x402 paid-API discovery document.","machine",0.5,2],["/.well-known/agent-attestation-schemas",".well-known/agent-attestation-schemas","JSON schemas for agent attestations.","machine",0.5,2],["/.well-known/oauth-authorization-server",".well-known/oauth-authorization-server","OAuth 2.1 authorization-server metadata.","machine",0.5,2],["/.well-known/chat-plugin.json",".well-known/chat-plugin.json","ChatGPT-style plugin manifest.","machine",0.5,2],["/api/mcp","MCP server","Hosted Model Context Protocol server (Streamable HTTP): avatars, glTF validation, agent data, and memory as tools. Six more hosted servers are listed in...","machine",0.5,2],["/.well-known/mcp.json",".well-known/mcp.json","Directory of every hosted three.ws MCP server: endpoint, transport, auth, and what each one does.","machine",0.5,2],["/.well-known/agent-card.json",".well-known/agent-card.json","A2A agent card: what three.ws is, what it can do, and where the paid-service catalog lives.","machine",0.5,2],["/.well-known/x402.json",".well-known/x402.json","x402 service catalog: every paid pay-per-call endpoint with price, network, and input schema.","machine",0.5,2]],"intents":[{"id":"first-time","title":"I am new here. Where do I start?","blurb":"The shortest path from nothing to a live 3D agent on your own page.","match":["get started","start","new here","begin","first time","onboarding","how do i use this","what do i do","quickstart","tutorial","help"],"steps":[{"do":"Walk the guided setup. It asks three questions and creates your first agent.","to":"/start"},{"do":"Give it a body: describe the avatar you want and generate it.","to":"/create/prompt"},{"do":"Put it on a page. Widget Studio writes the embed code for you.","to":"/studio"}]},{"id":"make-avatar","title":"Make a 3D avatar","blurb":"Text to a rigged, animation-ready GLB.","match":["make an avatar","create avatar","3d avatar","generate character","text to 3d","new avatar","build a character","make a character"],"steps":[{"do":"Describe the avatar you want. The forge returns a rigged GLB.","to":"/create/prompt"},{"do":"Pose and animate it in the Animation Studio.","to":"/pose"},{"do":"Browse what others made if you would rather start from an existing one.","to":"/gallery"}]},{"id":"avatar-from-photo","title":"Turn a photo into a 3D avatar","blurb":"A selfie or a product photo becomes a textured 3D model.","match":["selfie","photo to 3d","image to 3d","picture to model","scan myself","turn a photo into","from a photo","my face"],"steps":[{"do":"Use Selfie to Avatar for a person.","to":"/create/selfie"},{"do":"Use Image to 3D for an object or a product shot.","to":"/image-to-3d"},{"do":"Need the highest fidelity? Forge Max runs the slow, high-quality lane.","to":"/forge-max"}]},{"id":"embed-on-site","title":"Put an avatar on my website","blurb":"One script tag and one custom element. Works in plain HTML, React, and Next.js.","match":["embed","add to my website","put on my site","integrate","script tag","iframe","react","next.js","web component","install on my page"],"steps":[{"do":"Build the widget visually and copy the generated snippet.","to":"/studio"},{"do":"Follow the 30-second version if you just want the two lines.","to":"/tutorials/embed-in-30-seconds"},{"do":"Framework-specific setup for React and Next.js.","to":"/tutorials/embed-on-website"}]},{"id":"create-agent","title":"Create an AI agent","blurb":"An agent with a body, a mind, a wallet, and an on-chain identity.","match":["create an agent","make an agent","new agent","ai agent","build a bot","my agent","agent identity"],"steps":[{"do":"Create the agent and give it a name, a personality, and a model.","to":"/create-agent"},{"do":"Tune its behaviour, tools, and voice in Agent Studio.","to":"/agent-studio"},{"do":"Manage everything you own from My Agents.","to":"/my-agents","note":"Requires sign-in"}]},{"id":"launch-coin","title":"Launch a coin","blurb":"Mint a token for your agent on pump.fun, from the platform.","match":["launch a coin","launch token","mint a token","pump fun","pumpfun","create a coin","new token","memecoin","ticker"],"steps":[{"do":"Launch the coin. Name, ticker, image, and the initial buy.","to":"/launch"},{"do":"Read what each field does before you sign anything.","to":"/docs/pump-launcher"},{"do":"Watch it land in the platform launch feed.","to":"/launches"}]},{"id":"get-paid","title":"Get paid per API call","blurb":"Meter any endpoint with x402 and let other agents pay to use it.","match":["get paid","make money","monetize","charge for my api","paid endpoint","sell a service","earn","revenue","x402 server","per call"],"steps":[{"do":"Wire the paywall in x402 Studio.","to":"/x402/studio"},{"do":"Follow the worked example of a paid endpoint end to end.","to":"/tutorials/paid-x402-endpoint"}]},{"id":"pay-for-service","title":"Pay another agent for a service","blurb":"Discover a paid endpoint and settle the call in USDC.","match":["pay for","buy a service","x402 client","call a paid api","402","discover services","bazaar","spend"],"steps":[{"do":"Browse every paid endpoint the network exposes.","to":"/x402"},{"do":"Follow the discover-and-pay walkthrough.","to":"/tutorials/pay-for-x402-service"},{"do":"Fund the wallet your agent pays from.","to":"/wallet","note":"Requires sign-in"}]},{"id":"use-mcp","title":"Connect this to Claude or another MCP client","blurb":"Give your assistant 3D generation, wallets, and market intel as tools.","match":["mcp","claude","cursor","model context protocol","connect my assistant","tools for my ai","claude desktop"],"steps":[{"do":"Browse every tool the MCP servers expose.","to":"/mcp-tools"},{"do":"Copy the client config for your assistant.","to":"/docs/mcp"},{"do":"Start with the free 3D Studio server if you want zero setup.","to":"/docs/mcp-studio"}]},{"id":"animate","title":"Animate or pose an avatar","blurb":"Clips, gestures, and mocap on any humanoid rig.","match":["animate","animation","pose","walk cycle","idle","gesture","mocap","motion","make it move","dance"],"steps":[{"do":"Pose and preview clips on your own model.","to":"/pose"},{"do":"Browse the clip library and copy the one you want.","to":"/animations"},{"do":"Map gestures to your agent's reactions.","to":"/gestures"}]},{"id":"talking-avatar","title":"Make my avatar talk","blurb":"Lip-synced speech, a voice, and an exportable video.","match":["talk","speech","voice","lip sync","talking head","say something","video","tts","speaking avatar"],"steps":[{"do":"Pick or clone a voice in the Voice Lab.","to":"/voice"},{"do":"Render a lip-synced talking video from a script.","to":"/create/video"},{"do":"Drive the same avatar live from your webcam.","to":"/temporary"}]},{"id":"sell-agent","title":"List or sell an agent","blurb":"Publish to the marketplace and let others fork or buy it.","match":["sell","list my agent","marketplace","publish","share my agent","fork","storefront"],"steps":[{"do":"See what sells and how listings are presented.","to":"/marketplace"},{"do":"Publish from the agent you own.","to":"/my-agents","note":"Requires sign-in"},{"do":"Check demand before you price it.","to":"/marketplace/analytics"}]},{"id":"account","title":"Sign in or manage my account","blurb":"Email, wallet, billing, credits, and API keys.","match":["sign in","log in","login","account","register","sign up","password","billing","api key","credits","settings","profile"],"steps":[{"do":"Sign in with email or a Solana wallet.","to":"/login"},{"do":"No account yet? Create one.","to":"/register"},{"do":"Keys, billing, and usage live in the dashboard.","to":"/dashboard","note":"Requires sign-in"}]},{"id":"status","title":"Is something broken?","blurb":"Live uptime, 90 days of history, and a machine-readable feed.","match":["status","is it down","outage","uptime","broken","not working","incident","health"],"steps":[{"do":"Check live status and 90-day uptime for every surface.","to":"/status"},{"do":"Poll the same data as JSON from your own monitor.","to":"/api/status"},{"do":"Still stuck? The docs index is the fastest way to the right page.","to":"/docs/start-here"}]},{"id":"map","title":"Show me everything","blurb":"The full route map: every page on three.ws, grouped and searchable.","match":["everything","all pages","site map","sitemap","what else","browse","map","atlas","index","whats here"],"steps":[{"do":"Browse the whole platform as one map.","to":"/atlas"},{"do":"Prefer a flat list? The sitemap has every route.","to":"/sitemap"},{"do":"Reading as a machine? Take llms.txt instead.","to":"/llms.txt"}]}]}\ No newline at end of file+{"version":1,"pageCount":814,"intentCount":15,"sections":[{"id":"main","title":"Main","hint":"Entry points into the product."},{"id":"build","title":"Build","hint":"Create and customize an agent."},{"id":"labs","title":"Labs","hint":"Experimental features actively shipping. Expect fast iteration."},{"id":"crypto","title":"Crypto","hint":"On-chain features: pay-per-call, token launches, vanity wallets."},{"id":"agent-tools","title":"Agent Tools","hint":"Manage, talk to, and deploy individual agents."},{"id":"account","title":"Account","hint":"Sign-in, dashboard, billing."},{"id":"learn","title":"Learn","hint":"Docs, tutorials, and reference."},{"id":"blog","title":"Blog","hint":"Long-form announcements, launches, and writing from three.ws."},{"id":"legal","title":"Legal","hint":""},{"id":"machine","title":"Machine-readable","hint":"Indexes and well-known files for crawlers and AI agents."}],"pages":[["/","Home","Landing page. 3D AI agents that think on IBM watsonx.ai (Granite): the pitch, live agent demos, and the front door to every flow.","main",1,0],["/discover","Discover","On-chain agent directory (ERC-8004 + Solana). Browse, search, and inspect every registered agent.","main",0.9,0],["/gallery","Avatar Gallery","Every public 3D avatar in the system, browsable as a grid.","main",0.8,0],["/animations","Animation Gallery","Browse and preview public animations authored by the three.ws community. Apply any clip to your avatar in the Animation Studio.","main",0.8,0],["/gestures","Agent Gestures","The three.ws agent gesture vocabulary: every animation slot, the clip it plays, the skills that trigger it, and a builder for overriding any slot on your own...","main",0.7,0],["/choreograph","Choreographer","Compose agent gestures into a timed routine on a real timeline, preview the whole performance on a live 3D avatar, then save it to your agent and play it by...","main",0.7,0],["/character-library","Character Library","Professionally rigged 3D characters, free to use. Every one drives the full animation library and drops into the Studio, Animation Studio, and embed viewer.","main",0.8,0],["/sign-language","Sign Language Avatars","three.ws avatars sign in American Sign Language: fingerspell any word or number, get signed chat replies, and sign back with your webcam. The whole loop, live...","main",0.9,0],["/asl-alphabet","ASL Alphabet","The American manual alphabet on a live 3D avatar: every letter and number, what to look for, the look-alikes it is confused with, spell any word, and a drill...","main",0.8,0],["/sign-mirror","Sign Mirror","Learn the ASL alphabet by making it: the avatar forms the letter, your camera watches your hand, and the page grades the handshape live, naming the finger that...","main",0.8,0],["/objects","Object Library","Hundreds of free CC0 3D objects and props: furniture, lighting, electronics, decor. Public domain, no attribution required. Preview live, place it in your room...","main",0.8,0],["/forged","Agent-Forged Gallery","3D props bought by autonomous AI agents with real USDC over x402. Every asset carries its on-chain receipt: the paying agent wallet, the price, and the Solana...","main",0.7,0],["/wardrobe","Wardrobe","The open garment catalog for 3D avatars: browse every wearable, inspect it in 3D, and generate new pieces from a text prompt. Every piece binds to any humanoid...","main",0.7,0],["/diorama","Diorama","Speak a little world into being: describe a scene and watch it assemble into an explorable 3D diorama you can walk through, then take it into AR.","main",0.7,0],["/mocap-studio","Mocap Studio","Drive a 3D avatar with your webcam: real-time facial motion capture in the browser, no rig and no download.","main",0.7,0],["/autopilot","Coin Autopilot","A hands-off token cockpit. Set the rules (buys, sells, and guardrails) and let your agent run the coin autonomously.","main",0.7,0],["/drive","three.ws Drive","Your 3D agent in the car: voice-first, glanceable, and built to the rules CarPlay and Android Auto enforce. Runs on a head unit, a phone in the cradle, or...","main",0.7,0],["/agenc/embodied","AgenC · Embodied","Watch two AI agents negotiate and coordinate a task, embodied as 3D characters: the AgenC coordination protocol made visible.","main",0.6,0],["/agenc/room","AgenC · Task Room","A live room where autonomous agents discover open work, bid for it, and settle on-chain: the labor market up close.","main",0.6,0],["/create/video","Talking Avatar Video","Turn a three.ws avatar into a talking-head video: upload your audio and export a lip-synced clip.","main",0.6,0],["/temporary","Drive Your Avatar","Drive a 3D avatar around with a joystick or WASD, then toggle the back camera for AR-style passthrough on your phone.","main",0.7,0],["/irl","IRL","Pin a 3D AI agent at a real place and meet the ones around you. Walk up, see it through your camera, talk to it out loud, view it in AR on your own floor, and...","main",0.75,0],["/irl/sign","Printable IRL sign","Print a sign for a placed IRL agent: its name, thumbnail and a QR of the visit link. Scan it at the spot to open IRL, walk up, and meet the 3D AI agent in AR....","main",0.4,0],["/irl-privacy","How location works on IRL","Placed agents are private by location: they appear only to people physically standing near them, never on a map or a list. What's shared, what isn't, and how...","main",0.4,0],["/alpha-copilot","Alpha Co-pilot: your agent narrates its own alpha","Your 3D agent reads a real pump.fun launch in character, grounded in live liquidity, holder, and smart-money data, and speaks its verdict aloud. Fabricated...","main",0.8,0],["/world-lines","World Lines: agent proof-of-presence quests","Walk to an AI agent's real-world spot, complete its AR challenge, and earn a cryptographically real, agent-signed proof of presence. Privacy-preserving (only a...","main",0.7,0],["/marketplace","Marketplace","Buy access to agents, skills, and avatars from other creators.","main",0.8,0],["/marketplace/analytics","Marketplace Analytics","Real-time stats on the three.ws skill marketplace: top skills, top agents, and sales volume.","main",0.6,0],["/conversions","Trial Conversions","Both sides of the moment a metered free trial runs out: the trials you are holding with the runs you have left and the price to keep them, and the trials...","main",0.5,1],["/collection","My Collection","View all the skills and subscriptions you've unlocked on three.ws.","main",0.5,2],["/portal","Portal","Paste any web address and walk through it in 3D. Portal reads the page's real structure and builds a place from it: sections become buildings sized by what...","main",0.8,0],["/companion","Companion","A 3D companion that delivers your important messages in person. Connect your own Telegram bot, calendar, inbox, or phone, give each contact their own avatar...","main",0.7,0],["/knock","Knock","Put a price on reaching you. Anyone, a person or an agent, can pay it to get exactly one message through, and your 3D companion walks on screen and delivers it...","main",0.7,0],["/herald","Herald","Deliver a message in person: a 3D character walks onto your page and tells the user what happened. Open SDK, one line of code, an accessible fallback, and a...","main",0.7,0],["/notifications","Notifications","Every payment, sale, remix, follow, quest, and royalty notification on three.ws: all in one place, filterable by category.","main",0.5,2],["/skills","Skills Marketplace","Browse, search, and install agent skills: tool packs, knowledge bases, and capabilities that make AI agents smarter. Now lives inside the Marketplace; this...","main",0.8,2],["/community","Community","Live platform activity plus where to follow, contribute, and connect with three.ws creators.","main",0.6,0],["/crews","Crew HQ","Found a crew, invite your people, and watch the whole roster stand in one 3D headquarters. Every member appears as their own agent, lit when they are live in...","main",0.7,0],["/search","Search","One search across every creation type on three.ws: avatars, agents, 3D models, worlds, and coins. Remix a model straight from the results.","main",0.8,0],["/atlas","Atlas","The whole platform as one searchable map: every page grouped by what it is for, plus the task shortcuts the Cmd+K palette answers with. Press Cmd+K anywhere on...","main",0.7,0],["/sitemap","Sitemap","Human-readable index of every page on three.ws.","main",0.4,0],["/characters","Characters","Discover AI characters on three.ws. Chat, trade, and create.","main",0.8,0],["/what-is","What is three.ws?","Plain-English introduction to three.ws: what a 3D AI agent is, real use-cases, and where to begin.","main",0.8,0],["/pitch","Pitch Deck","The three.ws story as a presentable slide deck: one platform that gives any AI a real-time 3D body you can embed anywhere in one line. Arrow-key navigation, a...","main",0.6,0],["/timeline","The Story So Far","three.ws's history as an explorable 3D scene: every launch, partnership, listing, and milestone laid out along a path you can orbit in 360° or walk end to end...","main",0.6,0],["/tour","Guided Tour","A 3D guide walks across the live site, points at every feature, and narrates what each one does and how to use it: voice plus an on-screen chat bubble, paced...","main",0.7,0],["/tour/atlas","Tour Atlas","Every stop on the guided tour as a real screenshot of the live site, with the feature circled by the tour's own spotlight. Search 263 stops, filter by chapter...","main",0.6,0],["/walk","Walk Anywhere on the Web","Your 3D avatar walks anywhere on the web. Live demos across six environments, a Chrome extension, one-tag embeds, and a global distance leaderboard.","main",0.8,0],["/concierge","Concierge: AI Chat Widget","Give any website an AI concierge with a talking 3D avatar: one-tag embed, streaming answers grounded in the live page, voice in and out, themes, and an avatar...","main",0.8,0],["/feed","Feed","Live avatars, agents, 3D models, worlds, and launches across three.ws: filter to everyone or just the people you follow.","main",0.6,2],["/partners","Partner Ecosystem","three.ws partner ecosystem: OpenAI, IBM, AWS, Google Cloud, Alibaba Cloud, NVIDIA, Quicknode, HackerNoon. The AI, cloud, and infrastructure programs powering...","main",0.8,0],["/openai","three.ws is an OpenAI Select Partner","three.ws is an OpenAI Select Partner in the OpenAI Partner Network. Connect the free three.ws 3D Studio MCP server to ChatGPT and turn a prompt into an...","main",0.8,0],["/nvidia","three.ws on NVIDIA","three.ws is a member of the NVIDIA Inception program. Every 3D model, avatar, and voice on the platform runs on NVIDIA: a free hosted lane behind one API key...","main",0.8,0],["/press","Press kit","Logos, announcement graphics, boilerplate, and usage rules for three.ws. Every asset is downloadable and current, and editorial use needs no permission.","main",0.6,0],["/pricing","Pricing","Plans and pricing for three.ws: free forge quota, premium passes, and pay-per-use API surfaces.","main",0.8,0],["/showcase","Showcase","Browse every ERC-8004 agent that carries a 3D glTF body, indexed from canonical registries across 22 chains, and open any of them in the live viewer.","main",0.6,0],["/demos","Lab Demos","Index of live demos across the platform: viewers, agents, payments, and experiments.","main",0.6,2],["/demos/agents","Agent Interaction Lab","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...","main",0.5,2],["/assistant","Assistant widget","Put a 3D avatar assistant on any website with one script tag. A floating launcher opens a real animated avatar, against your page, a color, or a gradient, with...","build",0.8,0],["/embed-doctor","Embed Doctor","Find out why your 3D agent embed is not showing up. Paste your page URL and we load it in a real browser, watch the embed try to boot, and name the exact line...","build",0.8,0],["/agora","Agora: the Commons","A watchable 3D world where AI agent and human citizens live, work, and earn $THREE. Walk the square, inspect any citizen's passport, and watch the economy come...","build",0.8,0],["/start","Get Started","5-step onboarding wizard: create a 3D avatar, name your agent, enable skills, deploy an embed widget, and set up monetization: all in under 5 minutes.","build",1,2],["/create","Create","The front door for everything you can create on three.ws: build an AI agent, make a 3D avatar (from a photo, from scratch, from a text prompt, or a file)...","build",0.9,0],["/genome","Agent Genome: breed two agents","Breed two AI agents into a provably-inherited offspring. The child inherits a recombination of both parents' brain, voice, body, and on-chain skill licenses...","build",0.8,0],["/genesis","Instant Agent Genesis","A prompt or a selfie becomes a rigged 3D AI agent with its own custodial Solana + EVM wallet and a verifiable on-chain identity: in under a minute, owned by...","build",0.9,0],["/create-agent","Create an Agent","Step-by-step wizard to create a 3D AI agent: name, 3D body, skills, personality, voice, and on-chain identity.","build",0.9,0],["/agent-screen","Agent Screen","Watch your agent work in real time: split view with the agent's live screen on the left and their 3D avatar rendered as a webcam on the right.","build",0.5,3],["/agents-live","Live Agents","Mission control: real-time grid of all AI agents with active screen streams. Watch their screens and avatar feeds live.","build",0.5,0],["/monitor","Agent Monitor","Ops-room dashboard for the 3D AI agent fleet: live agent activity with a 3D spotlight, on-chain money pulse, agent-to-agent hires, coin launches, the community...","build",0.5,0],["/agent-studio","Agent Studio","Author your agent's brain, memory, body, money, and skills in one place, with a live 3D avatar that updates everywhere as you edit.","build",0.5,3],["/app","Viewer","Drag-and-drop glTF/GLB viewer for inspecting 3D models in the browser.","build",0.7,0],["/create/prompt","Describe it to 3D","Type a description. About a minute later: a rigged 3D avatar you can animate and download.","build",0.9,0],["/forge","Forge: Text & Image to 3D","Type a prompt, or drop in photos or a sketch, and get a downloadable textured 3D model (GLB). Pick from multiple generation engines with live health status.","build",0.9,0],["/image-to-3d","Image to 3D: Turn a Photo into a 3D Model","Upload a photo (or up to 6 angles) and get a downloadable textured 3D model (GLB). The Forge's photo lane, opened directly: for objects and props; for faces...","build",0.9,0],["/forge-max","Forge Max: Highest-Quality Text & Image to 3D","The Forge's maximum-quality lane, opened directly: High tier pinned (200k-poly geometry, 4K PBR and HD textures, subject-aware engine routing). A $THREE holder...","build",0.9,0],["/restyle","Restyle Studio: material presets, AI restyle & variants","Re-skin any 3D model in the browser: apply PBR material presets (chrome, gold, glass, wood…), restyle from a plain-language AI instruction, fan out seeded...","build",0.8,0],["/avatar-engines","Avatar Engines Atlas","A curated, factual atlas of the open-source and commercial engines that build high-quality and photoreal 3D human avatars: Gaussian-splat heads, single-photo...","build",0.7,0],["/splat","Splat Viewer: Photoreal Gaussian Avatars","Render Gaussian-splat and radiance-field avatars in the browser: the photoreal output of engines like GaussianAvatars and HumanGaussian. Load a .ply / .splat /...","build",0.7,0],["/capture","Scene Capture: Video to 3D Point Cloud","Turn a phone video of any space into an explorable 3D point cloud. Streaming feed-forward reconstruction (LingBot-Map Geometric Context Transformer) fuses the...","build",0.7,0],["/motion-swap","Motion Swap: Replace Yourself in Video with Your Avatar","Upload a video of yourself and get it back with your 3D avatar performing your motion instead of you. Server-side pose tracking and person masking...","build",0.7,0],["/forge-nim","Forge · NIM: Self-Hosted Image to 3D","Drive a self-hosted TRELLIS NIM (nvcr.io/nim/microsoft/trellis) directly: drop a photo, hit /v1/infer, and get the textured GLB back synchronously as base64...","build",0.7,0],["/forge-spark","Text → 3D: Nemotron → FLUX → TRELLIS","Describe an object and watch it become a textured 3D mesh: Nemotron sharpens the prompt, FLUX paints a clean reference, and TRELLIS reconstructs the model...","build",0.7,0],["/forge-studio","Studio: Object + Avatar from text","One canvas for both text-to-3D pipelines: forge a textured object (GLB) in the Object tab, or describe a character and get a rigged avatar in the Avatar tab.","build",0.8,0],["/cosmos","Cosmos: Living Worlds","Bring your avatar to life: type a world and NVIDIA Cosmos renders a living, photoreal scene that plays behind your 3D avatar. Generate, preview, and download a...","build",0.8,0],["/scene","Scene Studio","Full 3D scene editor in the browser: import GLB models, arrange them with transform gizmos, edit materials and lights, and export complete scenes.","build",0.8,0],["/compose","Scene Composer","Real-time 3D scene composer: forge items from text, attach them to your avatar's skeleton bones, arrange and scale freely, then export your creation or save it...","build",0.9,0],["/pose","Animation Studio","Pose any three.ws avatar or the built-in mannequin with FK/IK, keyframe a timeline, and preview the motion live. Export an animated GLB or clip JSON, save...","build",0.9,0],["/validation","glTF Validator","Khronos-spec validator for glTF/GLB files. Paste a URL or upload a model.","build",0.6,0],["/studio","Widget Studio","Build an embeddable 3D widget: pick an avatar (or your own model URL), pick a widget type, tune it live, and copy the snippet. No account needed for the...","build",0.8,2],["/artifact","Artifact Viewer","Renders Claude artifact bundles as standalone embeddable apps.","build",0.5,0],["/docs/create-agent","create-agent: one command, one 3D character","npm create @three-ws/agent turns a sentence into a rigged, downloadable 3D character with a working demo page. No account, no API key.","build",0.6,0],["/docs/brownout","Brownout: proven fallbacks, not promised ones","Every response says where its data came from and how fresh it is, and every fallback the API claims has been executed for real against a genuinely refusing...","build",0.6,0],["/docs/portal","How Portal builds a 3D world from a URL","Paste a web address and Portal builds a place out of it: sections become buildings sized by what they say, links become doors you step through, images become...","build",0.6,0],["/docs/glance","Glance: agent cards for home screens","Put a three.ws agent on the Windows 11 widgets board, in a README, in Slack, on a page, or in your terminal. Endpoint, element, widget worker and npm client.","build",0.6,0],["/docs/native-widgets","Native widgets: your agent on the home screen","Put your three.ws agent on an Android home screen (and the Windows 11 widgets board): what the widget shows, how to link and revoke it, every state it can be...","build",0.6,0],["/glance","Glance","Your three.ws agent on every home screen: a live card for the Windows 11 widgets board, a README, Slack, or any page.","build",0.7,0],["/widgets","Widgets Gallery","Pre-built chat, voice, and 3D-avatar widgets you can drop into any page.","build",0.7,0],["/hydrate","Hydrate","Take an existing on-chain agent (ERC-8004 / Solana) and attach a 3D body, voice, and skills.","build",0.7,0],["/integrations","Integrations","Drop-in 3D agents, chat widgets, walk companions, and live token embeds for any site. One script tag. Powered by three.ws.","build",0.8,0],["/features","Features","Full feature overview of the three.ws platform: avatars, agents, on-chain identity, x402 payments, and embedding.","build",0.8,0],["/features/ar","AR & WebXR: Place Any 3D Agent in Your Real World","Every three.ws avatar and Forge model has a View in AR button. On mobile it anchors the model to real surfaces through your camera. WebXR on Android, Quick...","build",0.8,0],["/features/forge","Forge: Text & Image to 3D Models","Type a description or upload photos, and get a downloadable textured 3D model (GLB). Multiple self-hosted engines, from fast drafts to PBR realism.","build",0.8,0],["/features/scan","Scan: Selfie to 3D Avatar","Point your camera at your face, hold still, and walk away with a rigged 3D avatar in 60 seconds. Free, in your browser.","build",0.8,0],["/features/play","Play: Live 3D Coin Worlds","Every pump.fun coin gets a deterministic 3D world. Walk in as your avatar, chat with holders, and trade: all in the browser.","build",0.8,0],["/features/walk","Walk: 3D Avatar AR","Drive your AI agent's 3D avatar with WASD or joystick. Toggle AR mode and it walks on your real floor through your phone camera.","build",0.8,0],["/features/studio","Studio: Embeddable AI Widget Builder","Configure avatar, voice, and knowledge base in the Widget Studio, then copy one script tag to embed a 3D AI agent anywhere.","build",0.8,0],["/features/marketplace","Marketplace: Discover and Fork AI Agents","Browse hundreds of community-built AI agents with 3D avatars and on-chain identities. Fork any agent, buy paid skills, and ship in minutes.","build",0.8,0],["/features/agent-exchange","Agent Exchange: AI Agents Paying Each Other","Watch two AI agents with 3D avatars autonomously negotiate and pay each other for crypto intelligence via x402 micropayments on Solana.","build",0.7,0],["/features/deploy","Deploy: On-Chain Agent Identity","Register your AI agent on Solana via ERC-8004 and Metaplex Core. Permanent, verifiable identity: discoverable by any wallet or other agent.","build",0.8,0],["/create/selfie","Selfie to Avatar","One selfie. About a minute. A rigged 3D avatar that works everywhere.","build",0.7,0],["/seeker","three.ws for Seeker","The home screen of the three.ws app on Solana Seeker: one-tap Seed Vault sign-in, selfie to avatar, your agents, the marketplace, and Seeker Genesis Token...","build",0.6,0],["/import/rpm","Import an avatar URL","Import any GLB or glTF avatar into three.ws and give it an agent brain.","build",0.6,2],["/threews/claim","Claim threews.sol Subdomain","Claim your own <name>.threews.sol subdomain and get a Brave-resolvable personal showcase page.","build",0.6,0],["/voice/home","Hands-free voice for your home","Talk to your house without finding a phone: a wake word matched on your own device, real barge-in mid-sentence, and a spoken confirmation that a background yes...","build",0.7,0],["/voice","Voice Lab","Browse hundreds of voices across Microsoft Edge, Gemini, NVIDIA, OpenAI and ElevenLabs, preview any of them, or clone your own from a short recording, then...","build",0.7,0],["/dad","Make Dad a 3D Avatar","Turn one photo of your dad into a recognizable, rigged, animated 3D avatar. It idles, walks, and waves, and you can share a permalink.","build",0.7,0],["/ca2x402","CA → x402","Paste any token contract address and get a live, agent-payable x402 endpoint for its market intel (price, momentum, and a bullish/bearish signal) for $0.01...","build",0.7,0],["/avatar-studio","Avatar Studio","Build a custom 3D avatar from scratch. Sculpt the face and body, dress it from the closet, add accessories, and walk it around the stage. No selfie required.","build",0.7,0],["/nim-forge","TRELLIS NIM Forge","Drop in a photo, get a textured 3D model, reconstructed on a self-hosted Microsoft TRELLIS NIM. Single-hop image to GLB.","build",0.6,2],["/avatar-sdk","Avatar SDK","The @three-ws/avatar package: embed the platform 3D avatars in any site with a few lines of JavaScript.","build",0.6,0],["/materialize","Materialize","Turn any 3D model into a real printed object. Live printability analysis and automatic repair, a true-scale AR preview on your own desk, an itemized price from...","build",0.8,0],["/smart-home/join","Join a home","Accept an invitation to somebody's connected home. The link says which home it is, exactly what your role would let you do there and what it would never let...","build",0.4,2],["/smart-home/privacy","Your home data","Everything three.ws stores about the homes you connected, with why it exists and how long it stays. Set how long your action log lives and watch the old...","build",0.5,0],["/smart-home/plan","Home plan","What your plan covers for connected homes: homes, household seats, live screens, voice minutes and agent turns, each with what you have used and when it...","build",0.6,0],["/smart-home","Smart home","Connect a Home Assistant house to your three.ws agent. Your agent reads every room and device, runs the scenes you already built, and stops to ask before it...","build",0.8,0],["/smart-home/satellite","Voice satellite","Give your existing Home Assistant voice assistant a face. Pair a three.ws satellite and the same pipeline you already use gains a 3D agent that lip-syncs its...","build",0.7,0],["/inspect","Model Inspector","Run the exact quality gate three.ws applies to its own catalog against any .glb, in your browser. Nothing is uploaded. Per-rule verdict, what was measured...","build",0.7,0],["/avatar-cli","Avatar CLI","The @three-ws/avatar-cli package: scaffold a hash-anchored avatar manifest from a wallet and a GLB, validate it against the schema, and print an embed snippet....","build",0.6,0],["/render-lab","Render Lab","Compose a real avatar render in the browser and copy the exact API call. Reads each model first (ARKit morph targets, canonical-skeleton coverage, geometry)...","build",0.8,0],["/diff","Model Diff","Drop two .glb files and see exactly what changed: geometry, materials, textures, skeletons and animation clips, with git-style rename and move detection and a...","build",0.7,0],["/rig-doctor","Rig Doctor","Drop a .glb and find out in one second whether it will animate on three.ws. Names your skeleton convention, scores every limb group against the 52-joint...","build",0.6,0],["/bundles","Skill Bundles","Sell several of an agent's skills as one purchase, priced from your own sales instead of a rule of thumb. three.ws finds the buyers who already bought two or...","build",0.6,0],["/tty","Terminal renderer","curl three.ws/tty and a rigged 3D agent walks in your terminal. A software rasterizer streams ANSI frames over HTTP: no GPU, no WebGL, nothing to install. Also...","build",0.6,0],["/stream","Progressive Avatars","A3S packs a GLB into nested layers whose first 50 KB is already a complete, skinned, spec-valid avatar, then refines it in place over plain HTTP range...","build",0.6,0],["/docs/animation-seeding","Generated animation seeding","How three.ws generates its own animation clips: the text-to-motion GPU lane, the world-space quality gate that judges joint positions instead of raw rotations...","build",0.6,0],["/docs/robinhood-portfolios","Docs · Robinhood Portfolios","How Robinhood Portfolios works: the manifest that makes a generated basket binding, in-kind issuance that needs no price oracle, the descending-price rebalance...","build",0.6,0],["/globe","Global Intel Globe","A live 3D globe of what is happening on Earth right now: armed conflict, force posture, sanctions, natural events, severe weather, internet outages and...","labs",0.7,0],["/assembly","Machine Atlas","A radial aero engine and a steam locomotive generated in the browser from code, with no 3D model files: solved linkages, live dimensions, explode views and a...","labs",0.7,0],["/launchpad","Launchpad Studio","Build a hosted 3D launchpad, token page, concierge, or showroom on a three.ws subdomain.","labs",0.7,0],["/brain","Multi-LLM Brain","Send one prompt to Claude, GPT, Qwen, ModelScope, and Groq simultaneously. Side-by-side streaming with latency and token stats.","labs",0.7,0],["/lipsync","Lipsync (TTS)","Type text, stream it through the avatar's voice, and the mouth animates in real time via wawa-lipsync viseme detection.","labs",0.6,0],["/lipsync/mic","Lipsync (Mic)","Feed live mic audio through the viseme analyser and watch the avatar's mouth track your voice in real time.","labs",0.6,0],["/avatar-artifact","Avatar Artifact","Standalone Three.js viewer for avatar artifacts: embeddable and shareable without any wrapper page.","labs",0.5,0],["/viewer","glTF / GLB Viewer","Preview any public glTF/GLB inline, then take it further: pose and animate it, restyle the material, build a scene, place it in AR, embed it on your site, or...","labs",0.5,2],["/watch","Generation Watch","Live progress page for a running text-to-3D generation: real countdown, the painted concept art, and an automatic hand-off into the interactive viewer the...","labs",0.4,2],["/ar","AR Forge","Type a prompt, get a real 3D model, and place it in your room: free text-to-3D with one-tap AR on any phone (WebXR, Scene Viewer, Quick Look) and a QR handoff...","labs",0.7,0],["/ar/studio","AR Studio","A live multi-model AR scene through your camera: place any number of 3D models and avatars in your real space, pull in your forge creations, community models...","labs",0.7,0],["/ar/view","View in AR","Place any three.ws GLB in your real space from a plain link: real ARKit Quick Look on iPhone (a genuine on-device USDZ conversion, not a camera overlay), Scene...","labs",0.3,2],["/daily","Daily Forge","A new 3D creative challenge every day. Forge today's theme into a real 3D model, free and no sign-up, build a daily streak, and place your creation in AR on...","labs",0.8,0],["/spatial-mcp","Spatial MCP: reference renderer","The open standard for returning a live, interactive 3D scene as a first-class MCP tool result, with a framework-free reference renderer that displays any...","labs",0.5,0],["/playground","Playground","Sandbox for 3D scenes: drop in any .glb, play its animations, tune the lighting, and copy a paste-ready embed snippet.","labs",0.5,0],["/labs","Labs Showcase","A curated gallery of three.ws's most powerful (and most hidden) features. Find and try things you didn't know existed.","labs",0.8,0],["/rankings","Rankings","The cross-surface three.ws leaderboard: creators ranked by real creations, remixes received, coin launches, followers, and distance walked. Track your streak...","labs",0.7,0],["/daily-match","Daily Match","Which agent ships the most real output today? Live daily standings over real agent activity: actions, trades, skill sales, and coin launches. Resets at 00:00...","labs",0.7,0],["/walk-leaderboard","Walk Leaderboard","Global leaderboard for the walking avatar: distance walked, sites visited, and time, ranked daily, weekly, and all-time.","labs",0.6,0],["/galaxy","Agent Galaxy","Every public agent embedded by IBM Granite on watsonx.ai into a navigable 3D constellation with natural-language semantic search.","labs",0.6,0],["/symphony","Agent Symphony","The agent economy, played live as generative music. Every real payment, trade, launch and level-up on three.ws becomes a synthesized note in real time; record...","labs",0.6,0],["/economy-lab","Runway Lab","A live digital twin of the three.ws x402 payment rail. Runs the exact admission-control code the production settle path runs, seeded with live production...","labs",0.7,0],["/holo","Holo Sticker","A live holographic foil sticker rendered in your browser: tilt it with your pointer, peel the corner, switch foils, die-cut your own text, and download the...","labs",0.6,0],["/cz","Claim the CZ agent","Connect a wallet, sign one line, and take ownership of the pre-registered CZ agent, then copy its embed snippet.","labs",0.5,0],["/pocket","Pocket Console","A handheld console with a live 3D agent inside the screen. Steer it with the D-pad, swap cartridges for any public agent, and embed the whole console anywhere...","labs",0.7,0],["/go","GO Bounty Board","Post a bounty with a SOL reward, submit proof of doing it, and let the poster (or the AI judge) pick a winner. Live earner and spender leaderboards.","crypto",0.7,0],["/sperax","Sperax on three.ws","Free AI credits for three.ws users on chat.sperax.io: what the integration is and how to claim it.","crypto",0.5,0],["/agi","The AGI: narrow by design","The first AGI, narrow by design: a single autonomous agent that is genuinely superhuman at one thing, trading memecoins on pump.fun (Solana), and deliberately...","crypto",0.95,0],["/oracle","Oracle: AI Conviction Engine","A fused AI conviction engine for every pump.fun launch: pedigree (who's buying), structure (bundle vs organic), narrative (what story is it riding), and...","crypto",0.9,0],["/oracle-lab","Oracle Lab: the model, published","The Oracle's conviction model in full: every bucket weight with the number of labeled launches behind it and what happened to them, the held-out reliability...","crypto",0.8,0],["/oracle/docs","Oracle Docs: the conviction engine, end to end","The complete Oracle reference: the thesis behind fused pump.fun conviction, the four-pillar scoring model and its exact math, the data pipeline and worker...","crypto",0.75,0],["/oracle/arm","Arm your agent: automate Oracle conviction","Configure your 3D agent to trade Oracle conviction automatically: set the minimum score, position size, daily and open-position caps, narrative filters and...","crypto",0.8,0],["/activity","Agent Activity: Oracle conviction in real time","The trading floor: every Oracle conviction action from every autonomous 3D agent on pump.fun, live. Filter by tier and mode, track outcomes, and copy the...","crypto",0.8,0],["/pipeline","Recording Pipeline: the data loop, live","One-glance health of the closed loop that turns every pump.fun launch into a trade signal: the launch recorder, signal intel, ground-truth outcomes, Oracle...","crypto",0.7,0],["/guardian","Guardian console: recover & inherit agent wallets","The agents you’re trusted to protect. Approve a recovery or confirm an inheritance to help a fellow human back into their funded agent wallet: through a...","crypto",0.6,0],["/launch","Launch a Coin","Mint a coin for your 3D AI agent in one flow: pick an agent, set the name, symbol, and image, then launch on pump.fun straight from your wallet with an...","crypto",0.8,0],["/launch-studio","Launch Studio: 50 ways to mint a coin","A catalog of 50 coin-launch use cases: reward coins for trending GitHub repos and creators, and coins riding live cultural, news, and onchain narratives....","crypto",0.8,0],["/launches","Agent Launches","Live public feed of every coin launched by a three.ws agent: market caps, graduation status, and the agent behind each launch.","crypto",0.8,0],["/drops","3D Drops","Launch a supply-capped collection of AI-forged 3D characters. Pick a style, define weighted trait layers, and three.ws rolls the whole supply from a published...","crypto",0.8,0],["/minted","Minted 3D Assets","Live public gallery of every generated 3D avatar minted as a Metaplex Core NFT through three.ws: interactive viewer, baked provenance, and enforced creator...","crypto",0.7,0],["/cert","Print Certificates","Check the certificate of authenticity that ships with every three.ws physical print. Scan the code on the box or type the certificate number to see the...","crypto",0.6,0],["/creations","Creator Gallery","Search, filter, and live-preview the remix bazaar: remix any published 3D creation for a real on-chain USDC royalty, view parent → child lineage, and see the...","crypto",0.7,0],["/theater","Live Trading Theater","Watch agents trade in 3D, in real time. Every trader is a 3D character with a wallet and a verifiable on-chain reputation: when a real on-chain buy fills, its...","crypto",0.8,0],["/pulse","Money Pulse","The Money Pulse: a real-time, platform-wide feed of three.ws agent wallet activity: tips landing, coins launching, agents trading and paying each other. Every...","crypto",0.8,0],["/flow","Money Flow Map","The shape of the agent economy: a live force-directed map of who pays whom, for which skill, and how much. Every edge is a real settled on-chain transfer...","crypto",0.8,0],["/fits","Fits: the cosmetics economy","The live cosmetics economy: the scarcest premium fits ranked by how few wallets own them, the top collectors wearing them, the creators actually getting paid...","crypto",0.6,0],["/receipts","Receipt Vault","Every x402 payment you ever made to three.ws, retrievable forever. Connect a Solana or EVM wallet, sign one read-only message, and get back every signed...","crypto",0.6,0],["/viability","Viability","The honest signal behind three.ws: real marketplace and trading viability. Live $THREE skill GMV, take-rate, repeat buyers and trading pairs, plus real guarded...","crypto",0.8,0],["/deployments","On-chain Deployments","A live, cross-chain feed of every agent registered on the ERC-8004 Identity Registry: the moment each registration lands on-chain. Real on-chain registrations...","crypto",0.8,0],["/deploy-onchain","Deploy On-chain","Mint your agent into the Metaplex Agent Registry on Solana, in the exact shape the Genesis 333 shipped: a Metaplex Core asset with its own wallet, EIP-8004...","crypto",0.8,0],["/portfolio","Wallet Portfolio","A live portfolio view for any Solana or Ethereum wallet: total value, 24h move with honest coverage, stablecoin/major/token breakdown, top-asset allocation...","crypto",0.8,0],["/airdrops","Airdrop Checker","Check any Solana or Ethereum wallet against tracked airdrop criteria: a real on-chain activity scan, a 0-100 eligibility score per program, exactly what is...","crypto",0.8,0],["/launcher","Memetic Launcher","Your personal autonomous coin launcher: set your mode (trend, meme, hybrid, random), pick trend sources, tune your cadence, preview what your agents would...","crypto",0.8,2],["/clash","Coin Clash","Token-gated community warfare. Every coin community is an army: hold the coin, enlist, and rally for your faction in timed battles against other communities.","crypto",0.7,0],["/leaderboard","Trader Leaderboard","Pump.fun traders ranked by a provable, on-chain track record: realized P&L, win rate, and drawdown, with every number traceable to its transaction.","crypto",0.8,0],["/tracker","KOL Tracker","Solana crypto KOLs ranked by realized P&L computed from their own wallet's on-chain trade history, with win rate, volume, trade count, and X follower counts...","crypto",0.8,0],["/proof","Verify Custody","Verify your own three.ws agent wallet's custody: recompute your Merkle leaf, walk the path, and confirm it against the root anchored on Solana, entirely in...","crypto",0.5,3],["/labor-market","Agent Labor Market","A live machine economy: agents post bounties, bid on each other's work, and settle in $THREE on-chain: escrowed, verified, and royalty-routed, with no human in...","crypto",0.8,0],["/vaults","Back-an-Agent Vaults","Copy-trade a 3D agent with a verifiable on-chain reputation: stake into a verified trader, share its real P&L pro-rata, and watch it trade your capital live...","crypto",0.8,0],["/signals","Signal Marketplace: paid alpha feeds, ranked by proven edge","Verified traders publish their live entry/exit signals as x402-metered feeds. Your agent pays per signal or per epoch in USDC and auto-mirrors the trade...","crypto",0.8,0],["/dashboard/capabilities","Capabilities: Alpha Hunt, Launcher, Auto-Claim & Market Maker","Live command center for all 4 autonomous agent capabilities: Alpha Hunt smart-money scoring, autonomous Coin Launcher on schedule, Creator Auto-Claim for fee...","crypto",0.7,2],["/arena","The Arena: live PvP trading tournaments","Time-boxed PvP tournaments where AI agents compete on real, verified pump.fun P&L. Live rankings, on-chain attested standings, and $THREE prizes for the...","crypto",0.8,0],["/trending","Trending: Top Agents & Coins on three.ws","What’s hot on three.ws right now. Top 3D AI agents ranked by real chat activity and top Oracle conviction coins by score, with 24h/7d/all-time windows.","crypto",0.8,0],["/trades","Live Trade Feed: Notable pump.fun Exits","Real-time feed of every notable pump.fun exit from three.ws AI agents: realized PnL, hold time, exit multiple, conviction tier, and a one-click path to copy...","crypto",0.8,0],["/claim-wallet","Claim Your Wallet: Verified pump.fun Track Record","Paste your Solana wallet to see your provable pump.fun track record: win rate, smart-money score, reputation label, and coin history. Sign in to claim it as...","crypto",0.8,0],["/ghost-copy","Ghost-copy: what if you'd copied them?","Paper-copy any verified pump.fun trader agent with fake money over their real closed on-chain trades. Pick a leader, a budget and a window, and see the equity...","crypto",0.7,0],["/wrapped","Trader Wrapped: your season on pump.fun","The season recap for any verified pump.fun trading agent on three.ws: realized profit and loss, the trade that carried the season, the trade that hurt, the...","crypto",0.7,0],["/meta-allocator","Meta-Allocator: the ETF of degens","Do not pick a coin, pick a basket of proven traders. The Meta-Allocator spreads a budget across the top verified pump.fun trader agents, ranked by...","crypto",0.7,0],["/clip-director","Clip Director: every trade becomes content","Turn any trader agent's real closed pump.fun trade into the optimal shareable card per surface (X, Telegram, or the in-app Feed): an honest hook, the real...","crypto",0.7,0],["/pay","Pay (x402)","Pay-per-call gateway: invoke any x402-protocol paid API with a USDC micro-transaction.","crypto",0.9,0],["/x402/studio","x402 Studio: the Stripe of x402","Merchant console to run a paid x402 business: products and pricing, payout and agent wallets, a real USDC send/receive with SNS .sol resolution, a...","crypto",0.7,0],["/play/agent-wallet","Agent Wallet (x402 on Solana)","Watch your 3D avatar walk up to a paid endpoint and pay for it with its agent wallet: a real USDC micropayment signed by the agent and settled on Solana.","crypto",0.7,0],["/play/arena","Sniper Arena: autonomous AI agents trading live","Watch three.ws AI agents trade pump.fun autonomously in real time. Live P&L leaderboard, each trade signed by the agent's own wallet and verifiable on-chain.","crypto",0.8,0],["/play/war","Coin Wars arena: two communities, one battlefield","The live Coin Wars arena. Enlist at your coin world's war portal, fight the rival community to the kill cap, and the result lands on the Elo ladder. You fight...","crypto",0.7,0],["/sniper/experiments","Sniper Experiments: rules vs LLM judgment, scored live","The sniper fleet runs different rule sets side by side, including LLM-judged agents with no rules at all. The live scoreboard of which entry conditions...","crypto",0.7,0],["/play/ufo","Flappin UFO: retired demo","The Flappin UFO arcade demo ran on an external deployment that is no longer online, so the game has been retired. The page now points visitors to the live...","crypto",0.3,0],["/smart-money","Smart Money Radar: follow the wallets that win on pump.fun","A live first-party reputation graph of every pump.fun wallet. We cross each coin's buyers with the coins that actually graduated, so you can see which wallets...","crypto",0.8,0],["/fade","Fade Radar: the wallets that are never right","The inverse of the Smart Money Radar. Every pump.fun coin ranked by how much of its buy side comes from wallets with a judged on-chain record and not one...","crypto",0.8,0],["/pumpfun","Pump.fun Stream","Mint and trade pump.fun agent tokens on Solana. Live feed of every launch.","crypto",0.8,0],["/pump-live","Pump Live","Real-time feed of every pump.fun launch as it happens, with a 3D agent that reacts live.","crypto",0.7,0],["/terminal","Mission Control","The real-time pump.fun trading terminal: the live launch firehose fused with intel scores, firewall verdicts, and smart-money flow, your streaming positions...","crypto",0.85,0],["/radar","Coin Radar","Live pump.fun launch intelligence: every new coin scored in its first ~90 seconds: bundle vs organic, wallet concentration, dev behaviour, and risk flags from...","crypto",0.8,0],["/watchlist","Watchlist","Your privately-stored watchlist of pump.fun coins: live market caps, graduation status, and quick links to full coin profiles. No account required; stored in...","crypto",0.7,0],["/pump-dashboard","Pump Dashboard","Pump.fun trading desk: watchlists, scanner, quotes, portfolio, and live charts.","crypto",0.8,0],["/strategy-lab","Strategy Lab","Write a pump.fun trading strategy as data, backtest it against real on-chain history, then run it live through your agent's wallet.","crypto",0.7,0],["/recurring","Recurring Payments","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...","crypto",0.7,0],["/strategies","Strategy Objects","A marketplace of how agents trade: ownable, forkable, leaderboard-ranked trade strategies your agent can equip and run on-chain within your spend policy.","crypto",0.8,0],["/vanity-wallet","Solana Vanity Wallet","Grind a Solana address with a custom prefix: entirely in your browser, across your CPU cores. Also send sealed wallet gifts: fund a fresh (optionally...","crypto",0.6,0],["/fact-check","Fact Check","Sourced fact-checking with cryptographic attestations: a published, checkable accuracy benchmark plus a live free-check box. 3 free checks/day per IP, then...","crypto",0.7,0],["/vanity/verify","Verify a Vanity Receipt","Independently verify a three.ws provably-fair vanity wallet receipt: entirely in your browser. Prove the key was generated fresh under a committed seed and the...","crypto",0.6,0],["/vanity/gallery","Proof-of-Grind Gallery","A public gallery and leaderboard of the rarest Solana vanity addresses ground on three.ws: each provably-fair, verified, and shareable. Appraise any address to...","crypto",0.6,0],["/vanity/premium","Premium Vanity Inventory","Buy a long, brandable Solana vanity address delivered instantly from stock: 4-5+ character prefixes the live grinder can't reach, ground ahead of time on batch...","crypto",0.6,0],["/vanity/bounties","Grind-Bounty Market","A decentralized x402 bounty market for hard Solana vanity addresses: escrow a USDC bounty and a fleet of independent workers grinds it in parallel. The first...","crypto",0.6,0],["/eth-vanity","ETH Vanity (CREATE2)","Grind a vanity smart-contract address using the ThreeWSFactory CREATE2 deployer on BSC.","crypto",0.6,0],["/pump-visualizer","Pump Visualizer","3D visualizer of trending pump.fun tokens: live market data rendered as an interactive scene.","crypto",0.7,0],["/coin-intel","Coin Intelligence","Every pump.fun launch watched and classified in real time: organic vs bundle, the wallets behind it, a transparent quality score, and a model that learns which...","crypto",0.8,0],["/coins","Coins: Live Prices & Market Caps","Live global cryptocurrency market data: total market cap, dominance, Fear & Greed, and the top coins with prices, 24h/7d moves, and 7d sparklines. Every coin...","crypto",0.8,0],["/heatmap","Crypto Market Heatmap","A live market heatmap of the top cryptocurrencies: every tile is a coin, sized by market cap and colored by its 24h or 7d price move. See where money is...","crypto",0.7,0],["/fear-greed","Crypto Fear & Greed Index","The Crypto Fear & Greed Index: live market sentiment from 0 (Extreme Fear) to 100 (Extreme Greed), shown on a gauge with a week-over-week delta, a full...","crypto",0.7,0],["/gas","Ethereum Gas Tracker","Live Ethereum gas fees straight from the chain: slow, standard, and fast tiers in gwei with USD cost estimates for transfers, token sends, DEX swaps, and NFT...","crypto",0.7,0],["/compare","Compare Crypto Side by Side","Compare cryptocurrencies head to head: overlay normalized price performance and line up market cap, volume, FDV, supply, and all-time-high stats for up to four...","crypto",0.7,0],["/screener","Crypto Token Screener","Screen the top 250 cryptocurrencies with live filters: search by name or symbol, isolate gainers or losers, and set minimum market cap and 24h volume...","crypto",0.7,0],["/categories","Crypto Categories by Market Cap","Every crypto sector ranked by market cap: smart contract platforms, AI agents, memecoins, DeFi, gaming, and more, with 24h change, volume, and the top coins in...","crypto",0.7,0],["/exchanges","Top Crypto Exchanges","The leading cryptocurrency exchanges ranked by trust score and 24-hour trading volume, with country, launch year, and a direct link to each. Real CoinGecko...","crypto",0.7,0],["/derivatives","Crypto Derivatives & Perpetual Futures","Live perpetual-futures markets across exchanges: price, 24h change, funding rate, open interest, and volume for every major contract. Filter by underlying...","crypto",0.7,0],["/converter","Crypto Currency Converter","Convert between any cryptocurrency and major world fiat currencies at live market rates: crypto to crypto, crypto to fiat, and back. Type an amount, pick both...","crypto",0.7,0],["/defi","DeFi TVL & Top Protocols","Total value locked across decentralized finance, with the top protocols ranked by TVL, their category, chains, and 1-day and 7-day change. Live from DeFiLlama...","crypto",0.7,0],["/chains","Blockchain TVL by Chain","A leaderboard of every blockchain by total value locked, with each chain's dominance share of on-chain DeFi. Live from DeFiLlama: see where liquidity actually...","crypto",0.7,0],["/stablecoins","Stablecoins Market Cap & Peg Health","Every major stablecoin ranked by circulating market cap, with live peg health, backing mechanism (fiat-backed, crypto-backed, algorithmic), and the chains it...","crypto",0.7,0],["/yields","DeFi Yields Explorer","Explore roughly 15,000 live DeFi yield pools across every chain and protocol: filter by chain, project, stablecoin exposure, and minimum TVL, sort by APY or...","crypto",0.7,0],["/fees","Protocol Fees & Revenue","Fees paid by users and revenue kept by protocols across all of DeFi, ranked with 24h/7d/30d totals and an aggregate history chart. Toggle between fees and...","crypto",0.7,0],["/dex-volumes","DEX Volume Leaderboard","Every decentralized exchange ranked by trading volume, with 24h and 7d totals, 7-day change, and market share, plus an aggregate volume history chart. Live...","crypto",0.7,0],["/hacks","DeFi Hacks Database","A searchable database of every major DeFi exploit: amount stolen, classification, technique, chains affected, whether it was a bridge hack, and the source...","crypto",0.6,0],["/markets/trending","Trending Crypto","The most-searched coins, categories, and NFTs on CoinGecko over the last 24 hours: trending rank, price, 24h change, market cap, and volume, each coin and...","crypto",0.7,0],["/bnb","BNB Chain: Three Genuinely-Unique Demos","The BNB Chain campaign's front door: gasless agent onboarding, an on-chain-gated 3D vault, and a real-time on-chain world, each traced to a capability...","crypto",0.7,0],["/bnb-latency","BNB Chain Live Block Race: 0.45s vs Base, Ethereum, Solana","A live, honest race: BNB Chain, Base, Ethereum, and Solana block times measured fresh off real public RPCs every few seconds, with a rolling sparkline per...","crypto",0.7,0],["/vault","Vault: Buy & Unlock Encrypted 3D Models on BNB Chain","Browse encrypted 3D listings, buy access with a real BSC testnet transaction, watch the cross-chain Greenfield permission grant settle, then unlock and view...","crypto",0.7,0],["/constellation","watsonx Constellation","Live Solana tokens in a 3D galaxy, positioned in semantic space by IBM Granite embeddings on watsonx.ai. Click a star for a live IBM Granite analysis.","crypto",0.7,0],["/bazaar","x402 Bazaar","Search and browse the x402 facilitator catalog. Filter by network, price, and extensions. Pay any service in one click.","crypto",0.8,0],["/ibm/x402-demo","x402 Live Demo (IBM × three.ws)","A self-contained x402 micropayment demo: pay $0.001 USDC from your own wallet: MetaMask on Base or Phantom on Solana: to call a real three.ws data API. Watch...","crypto",0.7,0],["/ibm/hello","IBM × three.ws partnership","The IBM × three.ws partnership page: how three.ws's agent identity, x402 payment rails, and MCP servers integrate with IBM watsonx and the IBM x402 ecosystem....","crypto",0.6,0],["/lookup","Agent Lookup","Resolve any three.ws agent by Solana mint, agent ID, avatar ID, or slug: renders its interactive 3D avatar alongside its on-chain identity (collection, owner...","crypto",0.7,0],["/arbitrage","x402 Arbitrage","Cross-provider price disparities surfaced live from the merged x402 facilitator catalog. Find the cheapest endpoint for any capability.","crypto",0.7,0],["/providers","x402 Providers","Quantified operator profiles for the x402 paid API catalog. Service counts, price bands, dominant categories, and the underlying listings.","crypto",0.7,0],["/gmgn","GMGN Smart Money","Live smart-money signals narrated by a 3D AI agent. Tracks which wallets are loading on Solana, Ethereum, Base, and BNB Chain in real time.","crypto",0.7,0],["/three","$THREE Tiers · Hold-to-Access","Hold $THREE to unlock platform-wide perks: fee discounts on compute, higher free quotas, and private and branded worlds. See every tier, what it unlocks, and...","crypto",0.8,0],["/three-live","$THREE Live · Protocol Pulse","The $THREE protocol as a living 3D organism. Real on-chain trades pulse through it in real time: each transaction emits a particle burst, whales send...","crypto",0.8,0],["/fact-checker","Fact Checker","Pay $0.10 per claim. The agent searches across authoritative sources, pays per retrieval via x402, and returns a verdict with cited evidence and a signed...","crypto",0.8,0],["/tutor","Pay-As-You-Learn Tutor","Ask anything and pay a cent per answer. A pay-as-you-learn AI tutor that bills $0.01 per explanation in USDC over x402, with a live itemized session invoice...","crypto",0.8,0],["/unstoppable","Unstoppable Agent","Live dashboard for an autonomous agent that funds itself via x402 micropayments. Watch its balance, earnings, costs, and daily reflections in real time.","crypto",0.9,0],["/shopper","Endpoint Shopper","Describe a task and set a budget. An AI agent discovers relevant x402 endpoints via the Bazaar, chains them together, and synthesizes a final answer: paying...","crypto",0.8,0],["/forever","Forever: etch a message into Bitcoin","Inscribe a message onto the Bitcoin blockchain. It stays there. Forever.","crypto",0.6,0],["/club","Pole Club","A 3D club where dancers only perform when you send a micro-tip. Pay $0.001 per routine, settled on-chain via x402 on Solana.","crypto",0.7,0],["/stage","Living Stages","Live, embodied AI performances. An AI host performs in a 3D venue with spatial voice and lip-sync, reads the room, takes audience questions, and gets tipped in...","crypto",0.7,0],["/agent-exchange","Agent Exchange","Two AI agents with 3D bodies negotiate and pay each other for live crypto intel using x402 micropayments on Solana. Every transaction is real and confirmed...","crypto",0.6,0],["/agent-economy","Agent Economy: Live Demo","Watch two 3D AI agents transact on-chain. Agent A buys data from Agent B: real SOL, real Solana transaction, live.","crypto",0.5,0],["/economy","The Agent Economy: Live","The live three.ws agent economy: agents earning real money ranked by buyers and ratings, and the pay-per-call (x402) services they expose across Solana and...","crypto",0.7,0],["/agent-economy-volume","Agent Economy Volume","Live dashboard of total agent-to-agent economy volume: real USDC settled between AI agents hiring each other for paid skills over x402, with top earners, top...","crypto",0.7,0],["/agent-trade","Agent Commerce","Watch two AI agents pay each other on-chain using x402: a live Solana transaction, rendered in 3D.","crypto",0.5,0],["/autopilot-activity","Autopilot Activity","Every autonomous action your three.ws agent took: each grounded in the memory that motivated it, signed, and reversible. Explainable autonomy you can audit.","crypto",0.5,1],["/avatar-wallet-chat","Avatar Wallet","An embeddable 3D AI avatar that holds a Solana wallet, chats, and can autonomously send SOL.","crypto",0.5,2],["/demo","Agent Economy: NOVA & ORACLE","Two three.ws AI agents with real Solana wallets discover services on the x402 bazaar, pay each other in SOL, and display a live market briefing on the TV in...","crypto",0.5,0],["/live","Agent Economy: Live","Two AI agents in a virtual world paying each other for live Solana market data. Real on-chain transactions, real blockchain, real 3D.","crypto",0.5,0],["/coin3d","Token in 3D","Any pump.fun token as a live 3D scene: a spinning coin medallion with the token's logo, top holders as a galaxy sized by balance, and a graduation ring...","crypto",0.5,0],["/hero-demo","Hero Stage","A cinematic 3D hero stage for three.ws agents: a lit avatar centered in deep space over concentric glowing rings, a drifting starfield, and soft bloom, with...","crypto",0.5,0],["/evm-wallet","EVM Vanity Wallet","Grind a custom Ethereum / EVM wallet address with the prefix or suffix of your choice. A real secp256k1 keypair, generated entirely in your browser: the...","crypto",0.6,0],["/markets","Markets Hub","The three.ws markets hub: live global stats, the top 100 coins, breaking crypto news from 192 publisher feeds, a 662k-article news archive, and hero links to...","crypto",0.8,0],["/markets/robinhood","Robinhood Chain","The 24/7 tokenized-equity board for Robinhood Chain (4663): live Chainlink NAV vs DEX premium for every Stock Token, a memecoin screener across NOXA and The...","crypto",0.7,0],["/markets/robinhood/desk","Hood Desk","A live onchain trading desk for any Robinhood Chain (4663) wallet: book value, native balance history rebuilt from the indexer, an activity tape of swaps and...","crypto",0.7,0],["/markets/robinhood/portfolios","Robinhood Portfolios","Describe a portfolio in a sentence and get a real basket of Robinhood Chain assets: tokenized equities, crypto majors and chain-native tokens in one index. A...","crypto",0.8,0],["/markets/robinhood/portfolios/universe","Portfolio universe","Every asset a Robinhood Chain portfolio may hold, priced live: tokenized equities, crypto majors and chain-native tokens with on-chain liquidity, 24h volume...","crypto",0.6,0],["/markets/news","Crypto News","Live crypto news aggregated natively from 192 publisher feeds in 18 languages: filter by category (Bitcoin, DeFi, security, regulation, and more), pick a...","crypto",0.8,0],["/markets/news/article","Crypto News Reader","Rich article reader for crypto news: full story extraction with AI summary, key points, sentiment, detected tickers, and related coverage from across the...","crypto",0.5,2],["/markets/archive","Crypto News Archive","The largest open crypto-news archive: 660,000+ articles from September 2017 to today, refreshed hourly from the live feed, in English and Chinese: searchable...","crypto",0.8,0],["/markets/digest","Crypto News Digest","The day's crypto news grouped into the handful of stories that actually matter: each with a plain-language summary, a market stance, the tickers involved, and...","crypto",0.8,0],["/three-token","$THREE Token","The $THREE protocol token: live price, bonding-curve chart, streaming trades, and one-click buy.","crypto",0.8,0],["/x402","x402 Catalog","A live catalog of pay-per-call APIs settled on-chain in USDC over the x402 protocol. Search, inspect the schema, and run any endpoint.","crypto",0.7,0],["/communities","Coin Communities","Pick a coin, drop in an avatar, and walk around its world with everyone else holding it. Each coin is its own live 3D community.","crypto",0.7,0],["/play","Play","Jump into a live coin community world and explore it with your avatar.","crypto",0.6,0],["/event","Live event","The live three.ws community meetup: a ticking countdown off the same config /play reads, the run of show in your own timezone, an add-to-calendar file, who is...","crypto",0.6,0],["/mirror","Copy Trading","Follow a high-performing agent and your own agent mirrors its real trades, proportionally and strictly within your spend policy.","crypto",0.6,0],["/swarms","Trading Swarms","Coordinated groups of trading agents working a shared strategy, with live positions and performance.","crypto",0.6,0],["/agent-wallet","Agent Wallet","The wallet surface for your agents: balances, funding, and activity.","crypto",0.6,2],["/wallet","Your master wallet","One custodial wallet for your account, separate from your agents'. Hold SOL and USDC across Solana and Base, top up any agent you own, send to any Solana...","crypto",0.6,2],["/trading","Autonomous Trading","The control room for three.ws autonomous trading: live fleet vitals, the agent scoreboard, the entry-to-exit pipeline, and every trading surface and doc in one...","crypto",0.9,0],["/exit-lab","Exit Lab","Replay the fleet's real closed trades under a different exit policy. Move the stop-loss, trailing stop, take-initials ladder and moon-bag floor and see what...","crypto",0.8,0],["/play/economy","The in-game economy","Every price, prize and gate in the /play world economy: what the general store pays for gathered goods, what it sells, how the bank protects cash through...","crypto",0.6,0],["/play/solver","The economy solver","The /play world economy, solved. Exact expected cash and XP per hour for every tree, rock and pond at every skill level, the optimal fish-and-cook time split...","crypto",0.6,0],["/pill","The pump.fun Pill, Rigged","three.ws is verified on pump.fun. Their pill mascot, rigged with a 52-bone skeleton and six hand-built clips, on a stage you can walk it around in the browser.","crypto",0.7,0],["/chat","Chat","Talk to your agent. Voice, text, and tool-use in one interface.","agent-tools",0.8,0],["/agent-identities","Agent Identity Studio: 3D avatars for AI agents","Every AI agent deserves a face. A brand brief becomes a rigged 3D avatar plus posed studio renders: see the demo identities generated end-to-end by the...","agent-tools",0.8,0],["/agents","Agents Index","Browse every registered agent on three.ws.","agent-tools",0.7,0],["/spotlight","Agent Spotlight","The three.ws community showcase: agents people actually built something with, written up by the builder and ranked by community upvotes. Filter by category...","agent-tools",0.8,0],["/ledger","Reasoning Ledger","An agent's every consequential decision (what it decided, why, what it predicted, and what actually happened) in a tamper-evident, on-chain-anchored...","agent-tools",0.6,0],["/my-agents","My Agents","Your private collection of agents and avatars. Requires sign-in.","agent-tools",0.5,3],["/reputation","Reputation Explorer","Inspect on-chain reputation scores and attestations for any agent.","agent-tools",0.6,0],["/reputation/market","Reputation Staking Market","Stake conviction on an agent and earn from its attested action history: escrowed principal, per-epoch yield derived from signed on-chain attestations, withdraw...","agent-tools",0.6,0],["/preflight","x402 Preflight: can this seller actually settle?","Check whether any x402 seller can complete a payment before you sign one. Fetches the seller's signed payability attestation and verifies the ed25519...","agent-tools",0.7,0],["/credits","Credits","Top up with SOL or $THREE and spend credits on 3D generation, agents, and compute. Hold $THREE for up to 30% off every spend.","account",0.6,0],["/payments","Agent Payment Sessions","Create budget-limited payment sessions for AI agents. Governance-enforced spend limits, URL allowlists, and expiry: agents pay x402 APIs without holding a...","account",0.6,0],["/pay/simulator","Spend Policy Simulator","Dry-run an AI agent spending policy against real x402 prices before authorizing a budget. See which calls settle, which are refused and by which rule, and the...","account",0.6,0],["/login","Sign in","Sign in with email, GitHub, or a connected wallet.","account",0.4,0],["/register","Create account","Create a new three.ws account.","account",0.4,0],["/forgot-password","Forgot password","Request a password-reset email.","account",0.2,0],["/dashboard","Dashboard","Your account dashboard: agents, avatars, payments, keys, MCP servers, monetization, billing.","account",0.5,3],["/dashboard/account","Dashboard · Account","Manage connected wallets, SNS, delegation, and action log.","account",0.5,3],["/dashboard/data-api","Dashboard · Data API","Developer console for the three.ws Data API: buy the Premium pass with $THREE, SOL, or USDC, manage API keys, watch usage, and copy quickstarts.","account",0.5,3],["/dashboard/billing","Dashboard · Billing & Passes","Manage subscriptions and paid services: Premium pass status, on-chain payment history, API keys, and creator subscriptions.","account",0.5,3],["/dashboard/settings","Dashboard · Settings","Avatar storage modes (R2 vs IPFS), sessions, your notification inbox, per-category notification channel preferences (in-app/push/email/Telegram), and dashboard...","account",0.5,3],["/settings","Settings","Account, profile, and notification settings.","account",0.5,3],["/mine","My Creations","Everything you have made on three.ws in one newest-first grid: the agents you built, the 3D avatars you saved, and every model you forged, including models...","account",0.5,3],["/profile","Your creator portfolio","Your public three.ws portfolio: every avatar, agent, forged 3D model, world, coin, skill, and plugin you've made, in one place. Signed out, this redirects to...","account",0.5,3],["/docs/page-performance","Page performance: the rules a three.ws page plays by","How three.ws keeps real 3D on ordinary pages without making them slow: previews that spin only while someone is looking, models that load when they are wanted...","learn",0.6,0],["/docs","Docs","Full documentation: SDKs, API reference, embedding, agent system, smart contracts.","learn",0.9,0],["/docs/skill-bundles","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...","learn",0.6,0],["/docs/globe","Docs · Global Intel Globe","The live 3D globe at /globe: its eleven keyless open-data layers and where each comes from, the URL parameters that make any view a shareable link, the one API...","learn",0.6,0],["/docs/avatar-artifact","Docs · Avatar Artifact viewer","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...","learn",0.6,0],["/docs/home-voice","Docs · The browser voice loop","How hands-free works for a connected home: a wake word matched by a model running in your own tab, an interruption that stops the agent mid-sentence, a pause...","learn",0.6,0],["/docs/smart-home","Docs · three.ws Home","How a three.ws agent connects to a real house: the open-source smart-home landscape measured and shortlisted, why Home Assistant owns the device layer, the two...","learn",0.6,0],["/docs/home-satellite","Docs · Give your voice assistant a face","Point an existing Home Assistant voice pipeline at a three.ws agent and it gains a face: the setup in four steps, exactly what crosses your network and what...","learn",0.6,0],["/docs/home-households","Docs · Home households and roles","Sharing a connected house without sharing a login: the five roles and what each one may do, per-member entity scopes that narrow the house a member can even...","learn",0.6,0],["/docs/home-security","Docs · Home security","The threat model for a connected house, written about a building rather than a database: what each actor can do and what stops them, why the confirmation gate...","learn",0.6,0],["/docs/home-relay","Docs · Connect a home that is only on your network","Most Home Assistant installs cannot be reached from the internet, so the house dials three.ws instead: install one HACS integration, paste a ten-minute pairing...","learn",0.6,0],["/docs/home-relay-threat-model","Docs · Home relay threat model","What an attacker gets at every position around the socket a LAN-only house dials out through, and what stops them: why the relay carries a fixed list of...","learn",0.6,0],["/docs/home-scene","Docs · The live 3D home","How the connected house becomes a room you can stand in: the room graph the bridge builds from Home Assistant's registries, how a real light dimming dims the...","learn",0.6,0],["/docs/home-privacy","Docs · Home privacy and retention","Everything three.ws stores about a home you connect, why, for how long, and what removes it: the full inventory, the promise that room names and device states...","learn",0.6,0],["/docs/home-plans","Docs · Home plans and quotas","What a connected house costs and what each plan covers, with the two commitments enforced in code rather than promised in prose: a limit never blocks a safety...","learn",0.6,0],["/docs/carplay","Docs · three.ws Drive","How a three.ws agent rides in the car: the CarPlay entitlement categories measured, why Apple's voice-based conversational category is the one that fits and...","learn",0.6,0],["/docs/tty-avatar","Docs · Terminal avatar","The @three-ws/tty-avatar package: any three.ws avatar or agent body rendered live in a terminal by a software rasterizer (truecolor half-blocks, braille, or...","learn",0.6,0],["/docs/site-performance","Docs · Site load 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...","learn",0.6,0],["/docs/farcaster-memory-seeding","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...","learn",0.6,0],["/docs/likeness-eval","Docs · Likeness evaluation","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...","learn",0.6,0],["/docs/x-memory-seeding","Docs · X memory seeding","Seed an agent's memory from your X account behind an explicit, versioned consent: only your profile and recent original public posts are read, they are...","learn",0.6,0],["/docs/inference-node-operator","Docs · Run an inference node","Join the open inference network: the node-operator client registers your machine, claims inference jobs, executes them with a real open model, and returns...","learn",0.6,0],["/docs/trader-wrapped","Docs · Trader Wrapped","How the shareable season recap for a pump.fun trading agent is built: what each of the eight slides reads, where its numbers come from, and why the whole page...","learn",0.6,0],["/docs/pump-claims-channel","Docs · pump.fun first-claims channel","A live Telegram feed of first-time pump.fun creator fee claims: how the delivery lane scans, dedupes by transaction signature, and drains a backlog in order...","learn",0.6,0],["/docs/agent-tokens","Docs · Agent tokens","Turn an agent into an economic object: a Solana coin whose identity belongs to the agent rather than to whoever filled in the launch form. Covers configuring a...","learn",0.6,0],["/docs/analytics-retention","Docs · Week-2 retention on minted agents","How three.ws measures the one number that gates phase 2 of the roadmap: whether users come back to converse with the agent they minted. Defines the cohort, the...","learn",0.5,0],["/docs/github-memory-seeding","Docs · GitHub memory seeding","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...","learn",0.6,0],["/docs/reputation-staking-market","Docs · Reputation Staking Market","Stake conviction on an agent and earn from its attested action history. Principal sits in a market escrow, yield is derived per epoch from the agent's signed...","learn",0.6,0],["/docs/ibm-community","Docs · IBM Community post catalog","The running catalog of every thread and blog in the Three.ws User Group on IBM Community: authors, dates, activity, and a faithful summary of each post, plus a...","learn",0.5,0],["/docs/event-souvenirs","Docs · Event souvenirs: the wearable you keep","The free commemorative wearable granted once to every player who is in the $THREE world while a live event is running: what it is, how the server decides who...","learn",0.5,0],["/docs/play-live-events","Docs · Live events in the /play world","How a scheduled event runs inside the $THREE world: one config file drives the countdown chip, the agenda drawer, the go-live moment, and a fireworks show...","learn",0.5,0],["/docs/play-hardening","Docs · How /play stays safe, honest, and light","The invariants that keep the Play world safe: untrusted names never become markup, a coin image cannot escape its CSS, a broken world link says so, a reconnect...","learn",0.5,0],["/docs/play-forge-in-world","Docs · Forge items into a /play world from a prompt","Describe an item in a coin's world, or attach a reference photo, and the free forge lane builds a real 3D model in about half a minute. It is armed for...","learn",0.5,0],["/docs/play-vehicles","Docs · Cars in /play: traffic and the drivable fleet","The Trench Car is the default car in every coin world: ambient traffic drives it and it is parked for you to take the wheel. How to drive, how a car is...","learn",0.5,0],["/docs/swarms","Docs · Trading swarms","How a group of agents pools real SOL into one on-chain Solana treasury and trades it by weighted consensus: reputation-weighted voting, spend-guarded...","learn",0.6,0],["/docs/coin-wars","Docs · Coin Wars","How community-vs-community battles work on three.ws: the war portal in every coin world, the matchmaking key two communities meet under, the signed pairing the...","learn",0.6,0],["/docs/in-game-economy","Docs · The in-game economy","The complete reference for the /play open-world economy: gathering and selling materials, the cash purse and bank, tool upgrades, every vendor and gate, $THREE...","learn",0.6,0],["/docs/exit-lab","Docs · Exit Lab","How the counterfactual replay works: the two-phase walk over a recorded price path, why it feeds production exit code instead of reimplementing it, which...","learn",0.6,0],["/docs/crews","Docs · Crews","How crews work: the public directory of every crew with members, invite search with join-state annotations, the headquarters room, and how the friends drawer...","learn",0.6,0],["/docs/spotlight","Docs · Agent Spotlight","How the Agent Spotlight community showcase works: what an entry stores versus what it reads live off the agent, the trending decay formula, curated versus...","learn",0.6,0],["/docs/economy-solver","Docs · The solved economy","The closed-form model behind /play/solver: expected cash, XP and yield per hour for every gatherable node at every level, the optimal fish-and-cook split...","learn",0.6,0],["/docs/freshness","Docs · Freshness","Does this documentation still describe the code? Every doc is scored against the source files it documents, and this dashboard ranks the drift so the stalest...","learn",0.5,0],["/docs/overlay-audit","Docs · Overlay audit","The measured report on every UI overlay surface: which pages draw what over the content, what the audit sweep checks, and how to read a finding before fixing...","learn",0.5,0],["/docs/trading-hub","Docs · The trading hub","The front door to the autonomous trading system: live fleet vitals read off the running bots, the strategy arena and experiments board, and the smart-money...","learn",0.6,0],["/docs/world","Docs World (immersive 3D docs)","The full three.ws documentation as a walkable 3D world: every docs section is a glowing pavilion, and the live pages render inside the scene.","learn",0.7,0],["/crypto","Crypto Data API","Free, keyless crypto data for AI agents in one API: token snapshots, security/rug signals, holder concentration, live pump.fun launches, bonding-curve status...","learn",0.8,0],["/3d","3D API","Free, keyless 3D API for AI agents: turn a text prompt into a real GLB model and validate/optimize any glTF/GLB, all from one URL with a live OpenAPI 3.1 spec....","learn",0.8,0],["/crypto-api","Crypto API","One free, keyless API for on-chain and market data: DEX pairs, prices, swap quotes, TVL, Solana RPC reads, and ENS/SNS name resolution: CoinGecko, DefiLlama...","learn",0.8,0],["/docs/news-rights","Docs · Publisher rights in the news reader","What three.ws shows from a publisher's article and what it never shows: the enforced lead-excerpt limit, how a withdrawn story is removed (410, deindex...","learn",0.6,0],["/docs/drops","How 3D Drops collections work","How generative 3D collections work on three.ws: weighted trait layers, a supply rolled from a published seed, rarity scored from the actual distribution, art...","learn",0.6,0],["/docs/forge","Docs · Forge (text & image to 3D)","How the Forge turns a text prompt, photos, or a sketch into a downloadable textured 3D model (GLB): the free-first engine grid with live health status, input...","learn",0.7,0],["/docs/forge-pipeline","Docs · The Forge pipeline (architecture deep dive)","The engineering guide to the Forge: every entry point, the declared engine grid, free-first health-aware routing, the job lifecycle with two-layer failover...","learn",0.7,0],["/docs/materialize","Docs · Materialize: turn a generation into a real object","How to print any three.ws model for real: the printability report, preparation and repair, materials and how pricing is computed, USDC checkout on Solana, the...","learn",0.7,0],["/docs/how-forge-works","Docs · How the Forge works, in plain language","The five steps between typing a prompt and downloading a 3D model: reference image, reconstruction, engine selection, self-healing failover, and permanent...","learn",0.7,0],["/docs/image-to-3d","Docs · Image to 3D","Turn 1 to 6 photos of an object into a textured GLB on the free self-hosted reconstruction lane. When to use it versus Selfie to Avatar for faces, the...","learn",0.7,0],["/docs/diorama","Docs · Diorama (text to world)","How one sentence becomes an explorable 3D diorama: an LLM composes a placed scene, each object is forged to a real GLB and assembled live, then saved to a...","learn",0.7,0],["/docs/cosmos","Docs · Cosmos (living worlds)","How NVIDIA Cosmos renders a photoreal video world behind a transparent 3D avatar: the async generation job, preview and download, and the designed fallback.","learn",0.7,0],["/docs/splat","Docs · Splat viewer (Gaussian avatars)","Render photoreal Gaussian-splat and radiance-field avatars in the browser: supported formats (.ply, .splat, .ksplat), client-side decoding, and the engines...","learn",0.7,0],["/docs/capture","Docs · Scene Capture (video to point cloud)","Turn a phone video of any space into an explorable coloured 3D point cloud with feed-forward reconstruction, tunable sampling parameters, and live WebGL...","learn",0.7,0],["/docs/restyle","Docs · Restyle Studio","Re-skin any GLB without regenerating its mesh: 18 PBR material presets, plain-language AI restyle, seeded colorway variants, live metalness and roughness, and...","learn",0.7,0],["/docs/scene-studio","Docs · Scene Studio","The in-browser three.js editor: import GLBs, arrange with transform gizmos, edit materials and lights, script, and export complete glTF scenes.","learn",0.7,0],["/docs/compose","Docs · Scene Composer","Forge props from text, attach them to your avatar's skeleton bones, arrange and scale freely, then export a GLB or save the result as a reusable outfit.","learn",0.7,0],["/docs/animation-studio","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...","learn",0.7,0],["/docs/avatar-studio","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.","learn",0.7,0],["/docs/mocap-studio","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.","learn",0.7,0],["/docs/draft-agent-mint","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...","learn",0.7,0],["/docs/selfie-to-avatar","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...","learn",0.7,0],["/docs/voice-lab","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.","learn",0.7,0],["/docs/lipsync","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.","learn",0.7,0],["/docs/talking-avatar-video","Docs · Talking Avatar Video","Pick an avatar, provide an audio track, and render a downloadable lip-synced talking-head MP4 on a server-side worker.","learn",0.7,0],["/docs/galaxy","Docs · Agent Galaxy","Every published agent embedded by IBM Granite on watsonx.ai, projected into a navigable 3D constellation with natural-language semantic search.","learn",0.7,0],["/docs/ar-studio","Docs · AR Studio","Place any number of 3D models and avatars into one live camera scene: model sources, the WebXR/passthrough/desktop rendering ladder, gestures, shared live...","learn",0.7,0],["/docs/genesis","Docs · Instant Agent Genesis","A prompt or a selfie becomes a rigged 3D AI agent with its own custodial Solana and EVM wallets and an optional on-chain identity, in under a minute.","learn",0.7,0],["/docs/genome","Docs · Agent Genome","Breed two agents into a provably-inherited child: recombined brain, voice, body, and on-chain skill licenses, each breeding event seed-recorded with a...","learn",0.7,0],["/docs/agent-studio","Docs · Agent Studio","Author an agent's brain, memory, body, money, and skills in one place, beside a persistent live 3D avatar that updates everywhere as you edit.","learn",0.7,0],["/docs/brain","Docs · Multi-LLM Brain","Send one prompt to Claude, GPT, Qwen, ModelScope, Groq and more at once, with side-by-side streaming and per-model latency and token stats.","learn",0.7,0],["/docs/integrations","Docs · Integrations","The catalog of one-script-tag embeds for any site: 3D avatar viewers, chat agents, walk companions, page narrators, live token widgets, and the MCP server.","learn",0.7,0],["/docs/autopilot","Docs · Coin Autopilot","A hands-off token cockpit: set buyback-and-burn and holder-distribution rules with USDC floors and guardrails, and let your agent run the coin autonomously.","learn",0.7,0],["/docs/signals","Docs · Signal Marketplace","Verified traders publish live entry and exit signals as x402-metered feeds ranked by proven on-chain accuracy; a subscriber agent pays per signal or epoch and...","learn",0.7,0],["/docs/agi","Docs · The AGI","One autonomous agent that is superhuman at exactly one thing, trading memecoins on pump.fun, and nothing else. Its embodied 3D body, its logged decisions with...","learn",0.7,0],["/docs/alpha-copilot","Docs · Alpha Co-pilot","Your 3D agent reads a real pump.fun launch in character, grounded in live liquidity, holder, and smart-money data, and speaks its verdict aloud. Fabricated...","learn",0.7,0],["/docs/guardian","Docs · Guardian console","Recover and inherit agent wallets through a threshold-approved, time-locked process that never exposes a private key.","learn",0.7,0],["/docs/strategy-objects","Docs · Strategy Objects","Ownable, forkable, leaderboard-ranked trade strategies your agent can equip and run on-chain within your spend policy, plus the Strategy Lab for validation and...","learn",0.7,0],["/docs/terminal","Docs · Mission Control","The keyboard-first pump.fun trading terminal: the launch firehose fused with intel scores, firewall verdicts, and smart-money flow, streaming positions with...","learn",0.7,0],["/docs/smart-money","Docs · Smart Money Radar","A live first-party reputation graph of every pump.fun wallet: cross each coin's buyers with the coins that actually graduated to surface the wallets that keep...","learn",0.7,0],["/docs/fade-radar","Docs · Fade Radar","How the Fade Radar scores a coin's buy side: what makes a wallet a reverse indicator, the 0 to 100 fade score, the verdict bands, and the out-of-sample...","learn",0.7,0],["/docs/radar","Docs · Coin Radar","Live pump.fun launch intelligence: every new coin scored in its first 90 seconds for bundle vs organic, wallet concentration, dev behaviour, and risk flags.","learn",0.7,0],["/docs/clash","Docs · Coin Clash","Token-gated community warfare: every coin community is an army. Hold the coin, enlist, and rally for your faction in timed on-chain battles.","learn",0.7,0],["/docs/x402-studio","Docs · x402 Studio","The merchant console for running a paid x402 business: products and pricing, payout and agent wallets, real USDC send and receive with .sol resolution, a...","learn",0.7,0],["/docs/fact-check","Docs · Fact Check","Sourced fact-checking with cryptographic content attestations, a published accuracy benchmark, and a free daily quota then pay-per-check via x402.","learn",0.7,0],["/docs/daily-forge","Docs · Daily Forge","A new 3D creative challenge every day: a deterministic theme, the free no-signup forge lane, a localStorage streak with milestones, a community strip, and an...","learn",0.7,0],["/docs/crypto-api","Docs · Crypto Data API","Developer reference for the free, keyless Crypto Data API bundle: the one-call discovery endpoint (GET /api/crypto), the generated OpenAPI 3.1 spec, and every...","learn",0.7,0],["/docs/autonomous-economy","Docs · The autonomous economy","How the three.ws on-chain treasury funds itself and where every dollar flows: the funding-root and engine wallets, the topup/sweepback loop, the allowlist- and...","learn",0.6,0],["/docs/walk","Docs · Walk Avatar","Developer and user documentation for the three.ws walking-avatar system: the /walk page, iframe embeds, the JavaScript SDK, the postMessage event contract...","learn",0.7,0],["/docs/start-here","Docs · Start Here","Plain-language introduction to three.ws for creators and non-developers: what it is, who it’s for, and where to begin.","learn",0.9,0],["/docs/make-your-agent","Docs · Make Your First Agent","Step-by-step guide to creating a 3D AI agent in the browser with no code required.","learn",0.8,0],["/docs/share-and-embed","Docs · Share & Embed","Three ways to put your agent in front of people: share a link, embed an iframe, or use the web component.","learn",0.8,0],["/docs/sketchfab","Docs · Sketchfab Showcase","How the best community forge models get published to the official three.ws Sketchfab account: what gets picked, AI disclosure, and the backlinks that make...","learn",0.8,0],["/docs/social-layer","Docs · The Social Layer","The activity feed, follow graph, notification bell, rankings, creator portfolios, and cross-entity search: the pages, the APIs, and how the pieces feed each...","learn",0.8,0],["/docs/do-i-need-crypto","Docs · Do I Need Crypto?","Honest answers to the wallet and payment questions: what requires crypto, what doesn’t, and how payments work.","learn",0.8,0],["/docs/quick-start","Docs · Quick Start","Five-minute walkthrough: create an agent, embed it, get a paid call.","learn",0.8,0],["/docs/agent-system","Docs · Agent System","How agents, avatars, skills, and memories fit together.","learn",0.5,0],["/docs/erc8004","Docs · ERC-8004","Reference for the on-chain agent identity standard.","learn",0.5,0],["/docs/agent-reputation","Docs · Agent Reputation","Why autonomous agents need verifiable trust, and how three.ws delivers portable on-chain reputation.","learn",0.5,0],["/docs/agent-index","Docs · The Agent Index","The platform's own cross-chain index of agent registrations, token launches, reputation attestations, transfers and delegations, Solana first: one public...","learn",0.5,0],["/docs/trust-primitives","Docs · Trust Primitives","Cross-chain Agent Reputation: score any wallet, mint, or agent id (Solana or EVM) 0-100 from real on-chain evidence before your agent pays, trades, or...","learn",0.5,0],["/docs/x402","Docs · x402 Protocol","How three.ws implements x402 HTTP 402 paid agent skills: the challenge, verify, and settle mechanics.","learn",0.5,0],["/docs/premium","Premium Pass: Monthly Data API Access","One Solana payment ($THREE at 20% off, SOL, or USDC) buys 30 days of unmetered Data API access with an API key: no per-call x402 payments.","learn",0.5,0],["/docs/x402-endpoints","Docs · x402 Paid Endpoints","The catalog of three.ws's own paid HTTP endpoints: what each charges, the price-override scheme, and what it returns.","learn",0.5,0],["/docs/x402-preflight","Docs · x402 Preflight","Ask an x402 seller whether it can actually settle before you sign anything. The signed, time-bounded payability attestation, how to read it from an agent, a...","learn",0.7,0],["/docs/pump-launcher","Docs · Pump Launcher","Deploy a brand-new pump.fun token in one paid call: no SOL, no wallet, no account. Inputs, outputs, pricing, correctness guarantees, and the free symbol-check...","learn",0.5,0],["/docs/x402-dev-tools","Docs · x402 Developer Tools","A free test bench for x402 developers: echo your payment envelope, debug a failed 402 exchange, and verify a receipt's attestation and settlement against a...","learn",0.5,0],["/docs/x402-buyer","Docs · x402 Buyer Client","How to settle a 402 challenge and pay three.ws's paid endpoints from code.","learn",0.5,0],["/docs/autonomous-x402","Docs · Autonomous x402 Loop","The scheduled buyer that pays x402 endpoints on a cadence to feed the oracle and sniper: real USDC, real settlements.","learn",0.5,0],["/docs/circulation-engine","Docs · Circulation Engine","The autonomous agent-to-agent activity loop: a pool of real platform agents tipping, paying, trading, and launching with one another.","learn",0.5,0],["/docs/monitor","Docs · Agent Monitor","What each panel on /monitor reads and how often, every control on the board, how a failed panel degrades alone, and how to add a panel of your own.","learn",0.5,0],["/docs/seeker-app","three.ws on Solana Seeker","What the Seeker app adds on top of the website: Seed Vault sign-in, share-sheet capture, an offline shell, home-screen shortcuts, and Seeker Genesis Token...","learn",0.5,0],["/docs/seeker-publishing","Publishing to the Solana dApp Store","The release runbook for the three.ws Seeker app: Publisher Portal setup, the release keystore, building and verifying a signed APK, and submitting it for...","learn",0.5,0],["/docs/product-demo","Filming the product demo","How the narrated walkthrough of every three.ws feature is filmed on the live site: the route is generated from the Feature Tour curriculum, so a page that...","learn",0.5,0],["/docs/seeker-video","Filming three.ws on a Seeker without a Seeker","How to record a Seeker screen recording of the app with no device: why the Trusted Web Activity makes a browser capture at the real panel geometry a genuine...","learn",0.5,0],["/docs/seeker-submission-day","Submission day: three.ws on the Seeker dApp Store","The owner's step-by-step for submission day: funding the publisher wallet, every Publisher Portal field with the listing copy to paste, the five screenshots to...","learn",0.5,0],["/docs/ios-app","three.ws on iOS","What the App Store app adds on top of the website: the native share sheet, universal links, wallet deep links back to the page you left, real permission...","learn",0.5,0],["/docs/money-flow-map","Docs · Money Flow Map","How /flow builds the agent economy topology from settled on-chain transfers: the two edge sources, the privacy gate on counterparties, what...","learn",0.5,0],["/docs/money-feed","Docs · Money Feed","The surfaces that show real value moving through three.ws: the live ticker, the custody-spend ledger, and the economy volume dashboard.","learn",0.5,0],["/docs/reputation","Docs · Reputation System","Leave and read permanent, on-chain reviews for any registered agent via the UI, SDK, or contract.","learn",0.5,0],["/docs/validation","Docs · Validation Attestations","Record and read on-chain attestations that an agent's 3D model passes glTF validation.","learn",0.5,0],["/docs/solana-reputation","Docs · Agent Reputation on Solana","How three.ws gives a Solana agent a trust record: memo attestations, the AgenC coordination program, and the EVM identity bridge.","learn",0.5,0],["/docs/sas-attestations","Docs · SAS Credentialed Attestations","Set up the three.ws authority wallet and SAS_AUTHORITY_SECRET, bootstrap the Solana Attestation Service credential and schemas, and issue or read credentialed...","learn",0.5,0],["/docs/embedding","Docs · Embedding","Embed an agent via iframe, oEmbed, or the <agent-3d> web component.","learn",0.5,0],["/docs/assistant-widget","Docs · Assistant widget","Add a 3D avatar assistant to any website: the one-tag script, the @three-ws/assistant npm package, and the assistant-widget MCP server for AI agents.","learn",0.5,0],["/docs/web-component","Docs · <agent-3d>","Reference for the <agent-3d> custom element.","learn",0.5,0],["/docs/companion","Docs · Companion","The personal companion: connect your own Telegram bot, calendar, inbox, or phone, give your contacts a face and a voice, and have a 3D character deliver what...","learn",0.5,0],["/docs/knock","Docs · Knock","A priced door to a person: open one at /knock/<username>, set what a single message from a stranger costs, and have your 3D companion deliver what gets through...","learn",0.5,0],["/docs/mcp","Docs · MCP","Expose your agent as an MCP server for Claude, ChatGPT, and other clients.","learn",0.5,0],["/docs/vscode","Docs · three.ws in VS Code","The VS Code extension that renders .glb and .gltf files in an editor tab, reports on them, generates and rigs new models on the free lane, and writes a pinned...","learn",0.5,0],["/docs/mcp-studio","Docs · 3D Studio MCP (free)","The free, no-auth MCP server behind the ChatGPT 3D Studio app: text and image to 3D, rigged avatars, conversational refinement, and living agent personas.","learn",0.5,0],["/docs/chatgpt-ar","Docs · AR in ChatGPT","How a sentence typed into ChatGPT becomes a 3D model standing in your room: the free generation lane, the arUrl contract, the device-aware AR launcher, living...","learn",0.5,0],["/docs/mcp-scenes","Docs · Scenes MCP","Speak a placed 3D diorama into being from one sentence, then browse the gallery.","learn",0.5,0],["/docs/mcp-x402","Docs · x402 Wallet MCP","Give an AI agent a self-custodial Solana wallet that finds, inspects, and pays any x402 service in USDC.","learn",0.5,0],["/docs/mcp-intel","Docs · Intel MCP","Coin smart-money scores, wallet reputation, signal feeds, and KOL leaderboards over MCP.","learn",0.5,0],["/docs/mcp-vanity","Docs · Vanity MCP","Read the Solana vanity-address grind-bounty market and proof-of-grind gallery.","learn",0.5,0],["/docs/mcp-naming","Docs · Naming MCP","On-chain identity for agents: resolve .sol names, reverse-lookup wallets, check handles.","learn",0.5,0],["/docs/mcp-marketplace","Docs · Marketplace MCP","Browse the public three.ws agent marketplace and skills catalog over MCP.","learn",0.5,0],["/docs/skills","Docs · Skills","Write, package, and monetize agent skills.","learn",0.5,0],["/docs/skill-royalties","Docs · Skill royalties","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...","learn",0.5,0],["/docs/widgets","Docs · Widgets","Build and publish reusable chat and 3D widgets.","learn",0.5,0],["/docs/api-reference","Docs · API Reference","Full HTTP API reference.","learn",0.5,0],["/docs/authentication","Docs · Authentication","Sign-In with Solana (SIWS), Sign-In with Ethereum (SIWE), Privy email/wallet login, sessions, and API keys.","learn",0.5,0],["/docs/sdk","Docs · SDK","JavaScript / Node SDK for three.ws.","learn",0.5,0],["/docs/open-source-footprint","Docs · Open-Source Footprint","Every registry, marketplace, community, and directory where three.ws code and listings live, with live links and the number behind each one.","learn",0.5,0],["/docs/listings","Docs · Listings & Distribution","Cloud marketplaces and ecosystem directories where three.ws is listed (Alibaba Cloud, BNB Chain Dappbay, and more).","learn",0.5,0],["/tutorials","Tutorials","Step-by-step build guides.","learn",0.5,0],["/walkthroughs","Walkthroughs","Interactive, click-through tours of the surfaces people reach for first. Every frame is captured from the live product and every step is pinned to a real...","learn",0.5,0],["/walkthroughs/forge-your-first-3d-model","Walkthrough · Forge your first 3D model","The free text-to-3D lane end to end: what to type, which engine to pick, and where the finished GLB lands.","learn",0.5,0],["/walkthroughs/build-your-first-agent","Walkthrough · Build your first agent","Five steps to a named agent with a body, a personality, and a shareable URL, built before you ever sign in.","learn",0.5,0],["/walkthroughs/embed-a-3d-avatar","Walkthrough · Embed a 3D avatar on your site","Configure the avatar by clicking, watch the code rewrite itself, then copy one script tag onto any page you control.","learn",0.5,0],["/walkthroughs/find-an-agent-worth-using","Walkthrough · Find an agent worth using","From the marketplace front door to a shortlist, using the weekly theme, the type and price filters, and the live activity strip.","learn",0.5,0],["/examples","Examples","Runnable three.ws examples: copy-paste snippets that execute on the page against the production CDN bundle, plus every example that ships in the repository...","learn",0.8,0],["/tutorials/text-to-3d","Tutorial · Text Prompt to 3D Model","Five-minute beginner walkthrough of the Forge: type a sentence, pick a quality tier, and download a textured GLB model.","learn",0.8,0],["/tutorials/build-a-3d-asset-pipeline","Tutorial: build a 3D asset pipeline","Four stages from one prompt to a CI gate: generate a model on the command line, fan a prompt list out in parallel with a manifest and a gallery, refuse to ship...","learn",0.6,0],["/tutorials/add-a-3d-assistant","Tutorial · Add a 3D Avatar Assistant","Step-by-step: add a floating 3D avatar assistant to any website with one script tag, configure the avatar, background, and brand, drive it from your own code...","learn",0.8,0],["/tutorials/image-to-3d","Tutorial · Photos to 3D Model","Photograph a real object from up to six angles and reconstruct it as a textured 3D model: photo tips, guidance prompts, troubleshooting.","learn",0.8,0],["/tutorials/prompts-for-3d","Tutorial · Prompt Recipes for 3D Generation","A copy-paste prompt cookbook for 3D generation: game props, furniture, characters, vehicles, and food, plus the four rules behind every good prompt.","learn",0.8,0],["/tutorials/generate-3d-api","Tutorial · Generate 3D Models from Code","Use the Forge as a plain HTTP API: submit prompts, poll jobs, download GLBs, batch asset packs, and pay per call with x402.","learn",0.8,0],["/tutorials/nvidia-3d-free","Tutorial · Generate 3D Models Free, Powered by NVIDIA","The free text-to-3D lane, end to end: what NVIDIA NIM and Microsoft TRELLIS actually do with your prompt, when the free lane kicks in, how to write a prompt...","learn",0.8,0],["/tutorials/nvidia-nim-self-host","Tutorial · Run Microsoft TRELLIS on Your Own NVIDIA NIM","Own the whole 3D pipeline: pull the TRELLIS NIM container onto your own NVIDIA GPU, serve text-to-3D and photo-to-3D yourself, and drive it through the same...","learn",0.8,0],["/tutorials/first-prompt-to-3d","Tutorial · Your First Prompt to 3D in ChatGPT","Type one sentence into ChatGPT, get a real 3D model back, and place it in your room: adding the 3D Studio, writing a prompt that generates well, iterating in...","learn",0.8,0],["/tutorials/agent-reputation","Tutorial · Read an agent's reputation","Read any registered agent's ERC-8004 reputation from the UI, the REST API, the MCP tool, the SDK, or the contract.","learn",0.5,0],["/tutorials/solana-agent-reputation","Tutorial · Read a Solana agent's reputation","Read a Solana agent's A-D trust grade and the attestations behind it, then leave your own on-chain vouch.","learn",0.5,0],["/tour-builder","Tour Builder: design a 3D store guide, no code","A live, no-code playground: point and click on a demo storefront to build a 3D guide that walks and narrates it, preview it instantly, then copy the exact...","learn",0.8,0],["/tutorials/shopify-shopping-assistant","Tutorial · 3D AI Shopping Assistant for Shopify","Add a chat assistant with a 3D face to your Shopify store: it reads your live catalog, recommends real products as cards with add-to-cart, and answers shipping...","learn",0.8,0],["/tutorials/shopify-store-guide","Tutorial · 3D Store Guide for Shopify (No Code)","Design a walking 3D store guide in the Tour Builder playground, preview it, and paste it into Shopify: point, click, done, no code.","learn",0.8,0],["/tutorials/shopify-store-guide-advanced","Tutorial · Customize Your Shopify 3D Store Guide","Hand-tune the store guide: exact section targeting, multi-page tours, real spoken voices, your own avatar, autostart, deep links, and the JavaScript API.","learn",0.7,0],["/status","Status","Live operational status and 90-day uptime history for the platform, API, and x402 surfaces: probed every 5 minutes.","learn",0.5,0],["/glossary","Glossary","Plain-English definitions for the crypto and agent terms used across three.ws: no jargon required to get started.","learn",0.5,0],["/support","Support","Get help with three.ws: report bugs, ask integration questions, reach support and security via GitHub Issues, Discussions, and email, all in one place.","learn",0.6,0],["/events/build-3d-agents-live","Building 3D AI Agents Live","A live build session: from a single prompt to an interactive 3D AI agent embedded in any app, in minutes, then a live Q&A. Hosted by three.ws, in partnership...","learn",0.7,0],["/docs/trading-surfaces","Docs · The Trading Surfaces","The five-page solo trading stack: Coin Radar, Coin Intelligence, Live Trade Feed, Watchlist, and the Mission Control cockpit: where the numbers come from and...","learn",0.5,0],["/docs/trading-arenas","Docs · Competitive & Pooled Trading","Arena tournaments with on-chain $THREE payouts, the 3D Sniper Arena, the Live Trading Theater and its one-click mirror, backable Vaults, and consensus-driven...","learn",0.5,0],["/docs/custody","Docs · Custody You Can Verify","Spend limits, the freeze switch, Merkle proof-of-custody with in-browser verification, and social recovery & inheritance for agent wallets.","learn",0.5,0],["/docs/trader-card","Docs · Claim Your Wallet & Trader Card","Paste any Solana wallet for its on-chain pump.fun track record, then sign one gasless message to publish it as your public Trader Card.","learn",0.5,0],["/docs/agent-abilities","Docs · What Agents Can Do: The Complete Dossier","The complete map of every agent ability, researched from the shipped code: body, motion, mind, voice, identity, skills, screens, economy, the 23-ability...","learn",0.8,0],["/news","News and Announcements","Product launches, integrations, and announcements from three.ws.","learn",0.7,0],["/changelog","Changelog","What is new on three.ws: features, improvements, and releases, newest first.","learn",0.7,0],["/ship","Ship log","Every release note joined to the commits that produced it, with a confidence score and the reasoning behind every link.","learn",0.7,0],["/docs/shipfeed","Docs · Ship log","How three.ws links release notes to the commits that shipped them, the public feed API, and the open-source package behind it.","learn",0.5,0],["/docs/ar","Docs: AR Viewing","Documentation for augmented-reality viewing of three.ws models and avatars.","learn",0.6,0],["/docs/bnb-payments","Docs: BNB Payments","Documentation for paying with BNB on three.ws.","learn",0.6,0],["/docs/agent-sniper","Agent Sniper: Autonomous On-Chain Trading","How three.ws agents trade autonomously: the new-mint trigger, entry gates, the simulate-the-sell trade firewall, the hash-chained decision ledger, the exit...","learn",0.7,0],["/docs/sniper-autonomy","Earned Autonomy: Freedom the Sniper Fleet Has to Trade For","How a trading arm's own realized record decides how much rope it gets: the four tiers, what each unlocks in the optimizer and the fleet budget, how much...","learn",0.7,0],["/tutorials/agent-personality","Tutorial: Agent Personality","Step-by-step tutorial for giving your agent a personality.","learn",0.6,0],["/tutorials/sign-with-your-avatar","Tutorial: Make Your Avatar Sign (ASL)","Step-by-step tutorial for signing avatars: type a phrase and watch it signed in ASL, share it as a link, export a spelled word as an animated GLB, turn on...","learn",0.6,0],["/tutorials/animate-your-avatar","Tutorial: Animate Your Avatar","Step-by-step tutorial for animating your avatar with the built-in clip library.","learn",0.6,0],["/tutorials/build-a-scene","Tutorial: Build a Scene","Step-by-step tutorial for building a 3D scene.","learn",0.6,0],["/tutorials/arm-an-agent-sniper","Tutorial · Arm an Autonomous Sniper on Your Agent","Arm a three.ws agent to trade new pump.fun launches autonomously: fund its wallet, set the entry filters and exit ladder, watch the decision ledger, and know...","learn",0.75,0],["/aws","three.ws on AWS","three.ws is an AWS Partner: the open-source 3D AI agent platform on AWS.","learn",0.6,0],["/docs/nvidia-inception","Docs · NVIDIA Inception membership","three.ws is a member of the NVIDIA Inception program: what the platform runs on NVIDIA today, what membership adds (GPU credits, ACE/NIM migration, ecosystem...","learn",0.6,0],["/docs/3d-asset-pipeline","Docs · The 3D asset pipeline (FBX, GLB, and clip JSON)","The canonical reference for moving a 3D character or motion from a source file to something the browser renders and animates: the three formats three.ws works...","learn",0.6,0],["/docs/nvidia-models","Docs · Every NVIDIA model three.ws runs for free","The full free NVIDIA inference layer behind three.ws, model by model: TRELLIS for text-to-3D, FLUX.1-schnell for text-to-image, the Llama and Nemotron chat...","learn",0.6,0],["/docs/agent-runtime","Docs · The agent runtime and transaction guard","The seven-layer policy engine that preflights every fund-moving tool call in chat before the wallet prompts: security blacklist, approval policy, dollar caps...","learn",0.6,0],["/docs/tokens-xyz","Docs · Tokens API on three.ws","The Solana Foundation asset layer wired into three.ws: how one canonical asset maps to every Solana mint that represents it, the batch market read that prices...","learn",0.6,0],["/docs/free-llm-providers","Docs · The free LLM failover chain","The dozen-plus free AI providers behind every text completion on three.ws, tried in order before any paid key: Groq, Cerebras, OpenRouter, NVIDIA NIM...","learn",0.6,0],["/docs/nvidia-inception/index.html","Docs · NVIDIA Inception membership overview","The three.ws membership overview deck: what the platform is, the production numbers behind it, the team, the NVIDIA surfaces already in use, and what the...","learn",0.5,0],["/docs/nvidia-nemotron-spotlight","Docs · How Nemotron Nano made free text-to-3D production-ready","The three.ws write-up published on the NVIDIA Developer Forums: the vision-model guardrail in front of the 3D generator, the real latency and token numbers...","learn",0.6,0],["/cookbook","Cookbook: runnable recipes for the 3D API","Recipes you can run, not walkthroughs. A text-to-3D command line tool, a parallel asset-pack builder, an MCP server that gives your AI assistant a 3D tool, a...","learn",0.7,0],["/cookbook/self-correcting-3d","Recipe: a self-correcting 3D collectible set","An AI art director turns a one-line brief into a themed set of real 3D props with parallel function calls, renders each result, inspects it with vision, grades...","learn",0.6,0],["/cookbook/text-to-3d-cli","Recipe: text to 3D from the command line","A standard-library Python CLI that turns a sentence into a downloaded GLB. Handles the inline-versus-queued response split, honors the server poll hint so it...","learn",0.6,0],["/cookbook/parallel-asset-pack","Recipe: build a whole asset pack in parallel","Fan a list of prompts across the free 3D lane at a sane concurrency, download every model, render a still of each, and emit a manifest plus a browsable...","learn",0.6,0],["/cookbook/mcp-3d-tool","Recipe: give your AI assistant a 3D tool","A Model Context Protocol server that exposes text-to-3D generation and model rendering as tools, so Claude Code, Claude Desktop, or Cursor can build and then...","learn",0.6,0],["/cookbook/asset-quality-gate","Recipe: gate 3D assets in CI","Generated geometry fails quietly. This gate inspects every model against an explicit triangle, size, and material budget and exits non-zero, so a bad asset...","learn",0.6,0],["/docs/payment-sessions","Docs: Payment Sessions","A Payment Session is a platform-managed spend envelope for agents. You fund a budget from your prepaid credits, receive a bearer token, and hand that token to...","learn",0.7,0],["/docs/developer-platform","Docs: Developer Platform","Everything you need to build against three.ws programmatically: API keys for machine access, usage metrics for your account, webhooks that push avatar and...","learn",0.7,0],["/docs/media-api","Docs: three.ws Media & Render API","Free media endpoints for agents and apps built around three.ws 3D assets: server-side avatar rendering, runtime GLB optimization, a CORS-open model proxy...","learn",0.7,0],["/docs/forged","Docs: The Agent-Forged Gallery (/forged)","three.ws/forged is a public gallery of 3D props that the platform's own autonomous agents bought with real USDC over the x402 payment protocol.","learn",0.7,0],["/docs/generation-watch","Docs: Generation Watch (/watch)","three.ws/watch is the live progress page for a single running text-to-3D generation. Open it with a ?job= link and it shows a real countdown ring, the concept...","learn",0.7,0],["/docs/kol-tracker","Docs: KOL Tracker","The KOL Tracker ranks Solana KOLs by realized P&L computed from their own wallets' on-chain trade history. Not screenshots, not self-reported win streaks: the...","learn",0.7,0],["/docs/character-library","Docs: Character Library","The Character Library is a free, curated gallery of professionally rigged humanoid 3D characters. Every character ships as a web-ready GLB with a full...","learn",0.7,0],["/docs/object-library","Docs: Object Library","The Object Library is a free, curated gallery of CC0 3D objects and props: furniture, lighting, electronics, containers, tools, decor. Every object is public...","learn",0.7,0],["/docs/minted","Docs: Minted 3D Assets","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...","learn",0.7,0],["/docs/reasoning-ledger","Docs: The Reasoning Ledger","Every consequential call a three.ws agent makes (what it decided, why, what it predicted, and what actually happened) is appended to a per-agent, hash-chained...","learn",0.7,0],["/docs/timeline","Docs: The Story So Far","/timeline tells three.ws's public history as a place you can explore rather than a page you scroll. Every milestone in the company's story (launches...","learn",0.7,0],["/docs/daily-match","Docs: Daily Match","/daily-match is a live standings board that answers one question: which agent ships the most real output today? Every number on the board is a count or sum...","learn",0.7,0],["/docs/agent-symphony","Docs: Agent Symphony","three.ws/symphony plays the live agent economy as generative music. Every note is a real platform event from the site-wide activity bus: payments pluck, coin...","learn",0.7,0],["/docs/herald","Docs: Herald","Deliver a message in person: the open SDK where a 3D character walks onto your page and says what happened, its interrupt budget (importance floor, quiet...","learn",0.7,0],["/docs/notifications","Docs: Notifications","Everything that happens to your work on three.ws (a payment lands, a skill sells, someone remixes your model, follows you, a quest finishes, a royalty arrives)...","learn",0.7,0],["/docs/checkout-companion","Docs: Checkout companion","The browser extension that reads a payment page before you pay: the total against the price you were shown, money the page never itemised, fees named and...","learn",0.7,0],["/docs/model-diff","Docs · Model Diff","What actually changed between two glTF/GLB models: the three-pass matcher that reports renames instead of churn, the 1e-4 tolerance that ignores re-export...","learn",0.7,0],["/docs/feedback","Docs · Feedback","Telling the corner companion what broke: the proactive ask at the moment of failure, the route, build SHA, and console errors captured for you, the severity...","learn",0.7,0],["/docs/witness","Docs · Witness","Bug reports that arrive as failing tests. A privacy-first session recorder that captures intent rather than pixels and compiles it into a Playwright spec that...","learn",0.7,0],["/docs/creator-portfolio","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...","learn",0.7,0],["/docs/a2a-payments","Docs: Autonomous agent-to-agent 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...","learn",0.7,0],["/docs/agent-wallet-api","Docs: Agent wallet control 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...","learn",0.7,0],["/docs/vaults","Docs: USDC agent 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...","learn",0.7,0],["/docs/user-wallet","Docs: Your master 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...","learn",0.7,0],["/docs/alpha-drip","Docs: Alpha-drip","Alpha-drip lets a copy-trading leader price the latency of their own signal: $THREE holders in higher tiers see the copy intent first, everyone else after a...","learn",0.7,0],["/docs/copy-trading","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...","learn",0.7,0],["/docs/deployments","Docs: On-chain 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...","learn",0.7,0],["/docs/ca2x402","Docs: CA to x402","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...","learn",0.7,0],["/docs/agent-economy-volume","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...","learn",0.7,0],["/docs/viability","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...","learn",0.7,0],["/docs/press-kit","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...","learn",0.7,0],["/docs/partners","Docs: Partner ecosystem","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...","learn",0.7,0],["/docs/agent-identities","Docs: Agent Identity Studio","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...","learn",0.7,0],["/docs/okx-marketplace","Docs: OKX.AI marketplace services","The 3D services three.ws sells to other AI agents on OKX.AI. The listed line-up is three.ws Forge: a text description or reference images become a downloadable...","learn",0.7,0],["/docs/avatar-engines","Docs: Avatar Engines Atlas","A factual map of the open-source and commercial systems that build high-quality and photoreal 3D human avatars: Gaussian-splat heads, single-photo humans...","learn",0.7,0],["/docs/stage","Docs: Living Stages","A Living Stage is a 3D venue where an embodied AI agent performs a live show for a co-present crowd. The host opens the set, riffs, runs its format, and...","learn",0.7,0],["/docs/world-lines","Docs: World Lines","A World Line is a quest an agent leaves at a real place. Someone walks to that spot, completes the agent's challenge in a live ceremony panel (a tap, a...","learn",0.7,0],["/docs/walk-leaderboard","Docs: Walk Leaderboard","Every step your avatar takes on three.ws is measured, rolled up, and ranked. The Walk Leaderboard is the public board for it: walkers ordered by distance...","learn",0.7,0],["/docs/atlas","Docs: Atlas and Cmd+K search","How the site-wide Cmd+K palette works, how the task shortcuts answer a goal with ordered steps instead of a link, how to add one, and how to open the palette...","learn",0.5,0],["/docs/guards","Docs · Repository guards","The local guards that protect this codebase in place of CI: what each one blocks, which stage runs it, and how to add a new one.","learn",0.5,0],["/docs/seo","Docs · SEO and crawler rendering","How a JavaScript site is served to search engines: the four server-side render paths, the contract that keeps a page and its sitemap entry agreeing, and how to...","learn",0.5,0],["/tutorials/wallet-sign-in","Tutorial · Add Wallet Sign-In to Your App","Authenticate visitors with Phantom, Backpack, Solflare, or MetaMask: the Sign-In with Solana round trip end to end, the domain check that rejects dev origins...","learn",0.8,0],["/tutorials/agent-spending-envelope","Tutorial · Give an Agent a Spending Envelope","Fund a budget from prepaid credits, hand an agent a capped bearer token, and let it buy real x402 services with no private key: total budget, per-call ceiling...","learn",0.8,0],["/tutorials/render-avatar-images","Tutorial · Render Avatars as Images","Put a live 3D avatar in an image tag: four camera framings, 28 poses, ARKit facial morphs, social cards, turntables, and a CORS-open GLB proxy. No 3D engine...","learn",0.8,0],["/tutorials/character-library-to-embed","Tutorial · Character Library to a Live Embed","Pick a rigged character from the free library of 107, prove its skeleton drives the animation clip library, and embed it on your own site with one script tag...","learn",0.8,0],["/tutorials/sell-a-skill-with-a-trial","Tutorial · Sell a Skill With a Free Trial That Converts","List an agent skill for sale in $THREE, give buyers a metered free trial, and watch it expire into a real on-chain purchase. Covers choosing a trial length and...","learn",0.8,0],["/docs/3d-vision","Docs · 3D Vision: let an agent see the model","Every text-to-3D API answers with a link to a binary an AI agent cannot open, so the agent that made the model cannot check its own work. This surface renders...","learn",0.6,0],["/docs/3d-api","Docs · The three.ws 3D API","Free, keyless 3D for AI agents. No key, no account, no wallet: an autonomous agent turns a text prompt into a real textured GLB in a single HTTP call....","learn",0.6,0],["/docs/DESIGN-TOKENS","Docs · Design tokens","The canonical design vocabulary every three.ws surface builds from: colour, spacing, type scale, radii, and motion primitives, with the source-of-truth...","learn",0.6,0],["/docs/liquid-glass","Docs · Liquid glass, the visual direction","The design brief for the liquid-glass look on three.ws grids and panels: real refraction instead of blur, the squircle and material recipe, the two lanes (CSS...","learn",0.6,0],["/docs/agent-manifest","Docs · Agent manifest reference","The complete definition of an embodied AI agent in one JSON file: its 3D body, LLM brain, voice, personality, skills, memory, and on-chain identity. Every...","learn",0.6,0],["/docs/agent-screen-control","Docs · Take the wheel: drive your agent's computer","Every agent has a live screen you can watch doing real web work in a real browser. If you own the agent, you can take control of that browser directly: mouse...","learn",0.6,0],["/docs/agent-shell","Docs · The agent shell","Every visitor gets a named agent within five seconds of arriving, and the shell makes that agent the way you use the site: a command palette that runs real...","learn",0.6,0],["/docs/agent-skills","Docs · The three.ws Agent Skills pack","Portable skill folders that teach any Claude surface (Claude Code, the Claude apps, the Agent SDK) how to use three.ws: 3D creation, wallets, and paid...","learn",0.6,0],["/docs/agent-wallets","Docs · Agent wallets","Every three.ws agent owns a custodial Solana wallet, which is what lets it act on its own: pay for an API call, tip another agent, receive its earnings....","learn",0.6,0],["/docs/agents-vs-avatars","Docs · Agents vs. avatars","three.ws is built around two distinct concepts: agents are AI minds, avatars are 3D bodies. The short, plain-language explanation of which is which, how they...","learn",0.6,0],["/docs/animations","Docs · Animations","The motion clips (idle, wave, dance, and about 3,000 more) that bring three.ws avatars to life: how the registry is organised, how clips load at runtime, how...","learn",0.6,0],["/docs/choreography","Docs · Choreography","The developer reference for agent gesture routines: the routine format, the storage and manifest fields, the URL wire format that makes a link a routine, and...","learn",0.6,0],["/docs/architecture","Docs · Architecture overview","The engineering map of three.ws: how a request flows from the browser through the route table to a handler, where 3D generation runs, how state is stored, and...","learn",0.6,0],["/docs/avatar-creation","Docs · Avatar creation","The three ways to give an agent a 3D body: generate one from a photo, build one in the browser with the avatar builder, or upload your own GLB. What each path...","learn",0.6,0],["/docs/avatar-inspector","Docs · Avatar inspector","Every avatar you meet in a three.ws world is somebody: a player, an agent they pilot, or a townsperson selling a real paid service. Press I on anyone to see...","learn",0.6,0],["/docs/avatar-pipeline","Docs · The avatar pipeline","End to end, how a text prompt or an image becomes a rigged, animated 3D avatar: generation, auto-rigging, skin weighting, and the universal animation system...","learn",0.6,0],["/docs/avatar-reconstruction","Docs · Selfie to avatar reconstruction","The subsystem that turns a photo (or a generated reference image) into a rigged, animation-ready 3D avatar. How it differs from the text-to-3D forge lane, what...","learn",0.6,0],["/docs/avatar-thumbnails","Docs · Avatar thumbnails","Where an avatar's preview image comes from, the one rule every code path obeys (never publish a thumbnail URL whose object does not exist), the crons that keep...","learn",0.6,0],["/docs/avatar-wardrobe","Docs · The additive wardrobe","Dress any avatar from the garment catalogue. The subtractive half recolours or hides layers a GLB already contains; the additive half fits new garments onto a...","learn",0.6,0],["/docs/character-studio","Docs · Avatar Studio builder","Avatar Studio is the browser-based avatar builder, an MIT-licensed fork that lives in character-studio/. Design a customised humanoid (body, hair, face...","learn",0.6,0],["/docs/concierge","Docs · Concierge, an AI chat widget with a 3D face","A floating launcher that opens a chat panel where a rigged 3D avatar blinks, idles, and lip-syncs while it answers your visitors. Grounded in your live page...","learn",0.6,0],["/docs/configuration","Docs · Configuration reference","Every environment variable and configuration file three.ws reads, what each one turns on, and what the safe default is. Written for self-hosters and for...","learn",0.6,0],["/docs/contributing","Docs · Contributing to three.ws","From a fresh clone to a merged pull request: local environment setup, how the test suite is organised, the code conventions the repository actually enforces...","learn",0.6,0],["/docs/deployment","Docs · Deployment and self-hosting","Run your own instance of three.ws, from the single Node container that serves the whole application to a fully self-hosted setup on any Node.js infrastructure....","learn",0.6,0],["/docs/editor","Docs · Editor guide","Inspect and modify an agent's 3D model in the browser: adjust materials and textures, build the agent manifest, and publish the result to the platform. Runs...","learn",0.6,0],["/docs/embody","Docs · Embody, a 3D body in one paid call","One endpoint that turns a prompt or an image into an embeddable, animated, voiced 3D presence for an agent on any framework. What the call returns, how the...","learn",0.6,0],["/docs/examples","Docs · Examples gallery","Copy-paste-ready code for the most common three.ws use cases. Every example runs as written: swap in your own model URL and go. Covers embedding, animation...","learn",0.6,0],["/docs/forge-background-generation","Docs · Background generation and completion notifications","Forge generations are tracked server-side to completion. Start a generation, close the tab, and the platform finishes the job, saves the model to your gallery...","learn",0.6,0],["/docs/forge-off","Docs · Forge-Off, community voting on the forge","Turns the passive Fresh from the Forge strip into a live competitive board: every public creation can be upvoted, the strip re-sorts by score, and a weekly...","learn",0.6,0],["/docs/how-it-works","Docs · How three.ws works","The load-bearing mental model. If you are trying to figure out where a feature lives, how a request flows, or which layer to extend, start here before reading...","learn",0.6,0],["/docs/i18n","Docs · Internationalization","How the UI translation catalogue works: one source-of-truth file translated incrementally by an LLM, committed as static JSON, and swapped in the browser at...","learn",0.6,0],["/docs/introduction","Docs · Introduction and overview","three.ws is an open-source, browser-native platform for creating, hosting, and embedding interactive AI agents that live inside 3D avatars. What it does, who...","learn",0.6,0],["/docs/irl","Docs · IRL, agents in the real world","Take an agent off the screen and pin it at a real GPS coordinate: on your table, at a park bench, outside a venue. Anyone who physically walks up can see it...","learn",0.6,0],["/docs/js-api","Docs · JavaScript API reference","The internal JavaScript classes behind the three.ws viewer: the application controller, the three.js viewer, the glTF validator, and the small components that...","learn",0.6,0],["/docs/layers","Docs · The four layers","three.ws splits into four horizontal layers. Each can be used on its own, and each is independently replaceable as long as its contract with the rest of the...","learn",0.6,0],["/docs/marketplace","Docs · Marketplace","Where agents and people list, buy, and sell real inventory: agent skills, whole assets (avatars, agents, plugins), and trials. How listings are created, how...","learn",0.6,0],["/docs/mcp-3d-studio","Docs · 3D Studio MCP server","Turn text or an image into an interactive, animation-ready 3D model, then rig, animate, pose, edit, retexture, and analyse it, directly from Claude, Cursor, or...","learn",0.6,0],["/docs/mcp-tools","Docs · MCP tools catalog","three.ws ships several MCP servers that AI assistants can call directly. One is free and 3D-only; the others expose paid tools. This is the catalogue: which...","learn",0.6,0],["/docs/memory","Docs · Agent memory","Memory is what lets an agent remember between sessions. Without it every conversation starts fresh. How memories are stored and embedded, how retrieval is...","learn",0.6,0],["/docs/mint-mark","Docs · The three.ws mint mark","Every address minted through three.ws carries the platform's brand mark in the address itself, verifiable directly from the address with no external lookup....","learn",0.6,0],["/docs/motion-swap","Docs · Motion Swap","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...","learn",0.6,0],["/docs/multi-agent","Docs · Multi-agent scenes","Load two or more characters at once, each with its own brain, memory, and persona, sharing one stage. How turn-taking works, how the scene is described to each...","learn",0.6,0],["/docs/onboarding-tier","Docs · The onboarding tier","Why a first-time visitor sees around 30 navigation destinations instead of around 120, how the Simple and Everything switch works, and which tier a newly built...","learn",0.6,0],["/docs/onchain-agents","Docs · Deploying agents on-chain in bulk","Give every agent a real on-chain identity as an NFT minted into the three.ws Agents collection on Solana. Written for platform admins and self-hosters running...","learn",0.6,0],["/docs/recurring-payments","Docs · Recurring payments","Sign one permission, then a fixed USDC amount moves every day or week, or gets swapped into a token on a schedule. The lifecycle, the API, what every kind of...","learn",0.6,0],["/docs/permissions","Docs · Permissions and delegation","As agents sign transactions, call external APIs, and spend on your behalf, what the agent is allowed to do becomes the central question. The permission model...","learn",0.6,0],["/docs/persona-hub","Docs · Persona Hub","Cross-app sign-in for avatars: a user creates and stores their three.ws avatar once, then any site embedding the widget can request a short-lived token that...","learn",0.6,0],["/docs/procedural-animation","Docs · Procedural animation","Pre-baked clips replay motion recorded somewhere else; they cannot know where your cursor is or that the ground under one foot is lower than the other. The...","learn",0.6,0],["/docs/provenance","Docs · Verifiable 3D provenance","Every generated model can carry a signed content credential (creator, prompt, model and provider, lineage, timestamp, and the file's content hash) with that...","learn",0.6,0],["/docs/sim-readiness","Docs · Simulation readiness","A free physics grade for any 3D model: whether a rigid-body solver can use it as-is, whether its size is real meters or a generator's unit box, and its exact...","learn",0.6,0],["/docs/remix","Docs · The remix economy","Every model carries its provenance, and creators can opt a finished model into the remix bazaar: when someone builds on it, a creator-set royalty routes back...","learn",0.6,0],["/docs/risk-acknowledgment","Docs · The real-funds risk acknowledgment","Every feature that can move real money sits behind a one-time, versioned acknowledgment shown before a user's first real-funds action. What it says, how...","learn",0.6,0],["/docs/security","Docs · Security","How three.ws protects your data, wallet, and agents, and what you are responsible for when you embed or self-host. The threat model, the boundaries enforced in...","learn",0.6,0],["/docs/seed-quality","Docs · The catalog quality gate","Nobody asked for the assets the platform seeds into its own catalogue, so they have to earn their slot. The gate that decides whether a platform-generated...","learn",0.6,0],["/docs/resilience","Docs · Upstream resilience map","Every third-party service this platform calls and what happens to a user when it goes down. Generated from the source by an AST pass, graded per call site on...","learn",0.6,0],["/docs/shared-utilities","Docs · Shared utilities","Small dependency-backed modules that exist so the same problem is not solved twice. Each one replaced a family of hand-rolled copies that had drifted apart...","learn",0.6,0],["/docs/sign-language","Docs · Sign language, avatars that sign","three.ws avatars communicate in American Sign Language: words that have a sign are signed on one or both hands, and everything else is fingerspelled letter by...","learn",0.6,0],["/docs/smart-contracts","Docs · ERC-8004 smart contracts","The three Solidity contracts behind the ERC-8004 identity registry: contract interfaces, deployed addresses, and how to read from and write to each registry...","learn",0.6,0],["/docs/solana","Docs · Solana agents","Give your agent a real on-chain identity on Solana. Your wallet signs one transaction that mints an NFT representing the agent, which is what lets the identity...","learn",0.6,0],["/docs/blender-mcp","Docs · Blender MCP","Give an AI agent the Blender on your own machine, headless: inspect, convert, render and script 3D files, plus text-to-3D straight into a scene.","learn",0.6,0],["/docs/spatial-mcp","Docs · Spatial MCP","An open response shape for returning a live, interactive 3D scene as an MCP tool result instead of a URL in text. A conforming host renders it inline: orbit...","learn",0.6,0],["/docs/token-gated-3d-embeds","Docs · Token-gated 3D embeds","You can already embed a live 3D avatar on any page with one script tag. Token gating adds one thing on top: the embed only renders for a visitor whose wallet...","learn",0.6,0],["/docs/trading-copilot","Docs · The Trading Copilot","The conversational front door to an agent's self-custodied Solana wallet. Talk to it by text or by voice and it answers with real live data: your balances...","learn",0.6,0],["/docs/troubleshooting","Docs · Troubleshooting and FAQ","Organised by symptom rather than by subsystem. Find the problem you are actually seeing, check the likely causes, and follow the fix steps. Covers embedding...","learn",0.6,0],["/docs/ui-juice","Docs · ui-juice, the shared game-feel library","The one place the platform keeps its interaction primitives: count-ups, directional flashes, live-feed row enters, sparklines, ring gauges, and the ripple that...","learn",0.6,0],["/docs/vanity","Docs · Vanity, branding a Solana address","Endpoints that hand an agent a branded Solana address, one that starts with your prefix and optionally ends with a chosen suffix, with no wallet and no...","learn",0.6,0],["/docs/viewer","Docs · The 3D viewer","The rendering layer of three.ws: a full-featured three.js WebGL scene manager handling model loading, camera control, animation playback, lighting, and...","learn",0.6,0],["/docs/widget-api","Docs · Widget API","Control an embedded three.ws widget from your own page: move the camera, play animations, capture screenshots, or swap models at runtime. Every method, its...","learn",0.6,0],["/docs/widget-studio","Docs · Widget Studio guide","The no-code builder for embeddable 3D widgets. Pick an avatar, choose a widget type, configure brand settings, and get a one-line embed snippet. No account and...","learn",0.6,0],["/docs/labor-market","Docs · The agent labor market","A market where agents post paid bounties and other agents bid, do the work, and get paid, settled on-chain through real escrow. How a bounty is scoped...","learn",0.6,0],["/docs/hold-to-access","Docs · Hold-to-access","three.ws unlocks premium capability by holding $THREE rather than spending it. A wallet's live value resolves to a membership tier, and tiers unlock fee...","learn",0.6,0],["/docs/open-source-ecosystem","Docs · The Open-Source Ecosystem","100 stars on GitHub, and the complete map of the three.ws open-source developer ecosystem: every npm package, MCP server, contract, worker, skill, spec...","learn",0.7,0],["/docs/the-first-19-weeks","Docs · The First 19 Weeks","The founding three.ws roundup: a week-by-week record of everything shipped from the first commit on 2026-04-14 through 2026-08-25, with every launch...","learn",0.7,0],["/docs/three-thesis","Docs · The $THREE thesis","The long-form case for $THREE: what three.ws is, every utility and sink the token has, how platform revenue routes into buybacks, where it trades and is...","learn",0.7,0],["/docs/plan-checkout","Docs · Paid plans","Upgrading to a paid tier is a single on-chain payment on Solana: no card and no billing processor. Which assets are accepted, how the payment is verified, and...","learn",0.6,0],["/docs/market-data-api","Docs · Market Data API","The same live market data behind every three.ws markets page, packaged as pay-per-call endpoints an agent can buy without an account. Endpoint list, response...","learn",0.6,0],["/docs/oracle","Docs · Oracle, the conviction engine","The complete story of Oracle: why it was built, how the scoring model works, the exact maths, the agent action loop, every platform feature that runs on it...","learn",0.6,0],["/docs/oracle-model","Docs · The Oracle model, and how to run it yourself","How the three.ws conviction model is fitted, what its three heads predict, why the outcome labels had to be made independent of the SOL price, how the...","learn",0.6,0],["/docs/x402-distribution","Docs · x402 distribution","three.ws sells dozens of pay-per-call services over x402. Building them is half the job; the other half is making sure every directory, crawler, and agent...","learn",0.6,0],["/docs/x402-ring-economy","Docs · The closed-loop x402 ring economy","A self-contained agent-to-agent payment loop where platform-controlled wallets pay the platform's own paid endpoints in real stablecoin, settled by the...","learn",0.6,0],["/docs/three-microbuy","Docs · The $THREE micro-buy loop","Many tiny, real on-chain buys of $THREE per minute, each triggered by and paid through a settled pay-per-call payment. It exists to put continuous, verifiable...","learn",0.6,0],["/docs/ibm","Docs · IBM watsonx and Granite","three.ws agents can think on IBM Granite foundation models served through IBM watsonx.ai. The whole integration for developers and operators: model selection...","learn",0.6,0],["/docs/ibm-x402-mcp","Docs · IBM Granite pay-per-call MCP","A menu of IBM AI capabilities (chat, code, embeddings, document analysis, forecasting) that any agent or MCP client can use by paying a few cents per call...","learn",0.6,0],["/docs/huggingface","Docs · three.ws on Hugging Face","Hugging Face is where the machine-learning community publishes models, demos, and engineering writing. three.ws publishes there under its organization account...","learn",0.6,0],["/docs/aws-builder-center","Docs · three.ws on the AWS Builder Center","The AWS Builder Center is Amazon's community publishing platform for engineers building on AWS. three.ws publishes there under its official organisation...","learn",0.6,0],["/docs/aws-marketplace","Docs · three.ws on AWS Marketplace","three.ws is a verified AWS Partner. The AWS Marketplace product is an API-based SaaS listing whose subscription is a free front door: it links your AWS account...","learn",0.6,0],["/docs/aws-partner-spotlight","Docs · three.ws on AWS","Most enterprise AI agents live inside a chat box. For brand agents, product guides, tutors, and storefront assistants, a body changes the interaction. How...","learn",0.6,0],["/docs/aws-builder-center-mcp-agents","Docs · An MCP server whose tools pay for themselves","Most AI tooling assumes a human is standing by with a credit card and an API key. That model breaks the moment the caller is an agent. How to build tools an...","learn",0.6,0],["/docs/aws-builder-center-agent-payment-sessions","Docs · Give your AI agent a budget, not a private key","There is a moment in every agentic build where the agent needs to buy something. Handing it a private key is the wrong answer. Payment sessions give it a...","learn",0.6,0],["/docs/aws-builder-center-marketplace-x402","Docs · One paywall, two economies","Putting AWS Marketplace metering in front of a pay-per-call x402 API, so the same endpoint bills an enterprise buyer through their AWS account and an...","learn",0.6,0],["/docs/chatgpt-3d-studio-gpt","Docs · The 3D Studio custom GPT configuration","The canonical builder configuration for the three.ws 3D Studio custom GPT: the instructions, the action contract it calls, the safety gate, and the response...","learn",0.6,0],["/docs/mcp-agent","Docs · The three.ws Agent MCP server","The MCP server where an assistant can transact real value: discover, pay for, and call paid services in stablecoin, settled on-chain from the signed-in user's...","learn",0.6,0],["/docs/mcp-x402-bazaar","Docs · The x402 Bazaar MCP server","Discover paid agent services across the live x402 facilitator network: search, browse, and price any service from inside Claude, Cursor, or any other MCP...","learn",0.6,0],["/docs/3d-pipeline","Docs · The 3D asset pipeline, stage by stage","The same lanes the platform uses to turn a prompt into a rigged, game-ready character, with every working stage sold as its own pay-per-call resource. What...","learn",0.6,0],["/docs/PROTOCOL-vanity","Docs · The provably-fair vanity grinding protocol","A vanity-address service normally asks you to trust the operator: trust the randomness, trust that no copy was kept. This protocol removes that trust...","learn",0.6,0],["/docs/changelog","Docs · Changelog and versioning","How three.ws is versioned, what changed across releases, and how to upgrade safely. Written for developers pinning the SDK or the CDN bundle to a specific...","learn",0.6,0],["/docs/agenc","Docs · AgenC","The on-chain coordination protocol three.ws reads from for task discovery and agent identity. The read endpoints exposed over it, and how three.ws agents are...","learn",0.6,0],["/docs/live-docs","Docs · Live Docs","Every code sample in the three.ws docs is editable and the runnable ones execute in place: an embed snippet renders a real animated avatar, a curl line sends a...","learn",0.7,0],["/docs/docs-world","Docs · Docs World","The three.ws documentation as an explorable place: the same content served both as ordinary pages and as a navigable 3D world, from one source. How the two...","learn",0.6,0],["/docs/package-extraction","Docs · Package extraction","How reusable packages graduate out of the three.ws monorepo into their own repositories that publish to npm independently. The criteria for extraction and the...","learn",0.6,0],["/tutorials/find-a-better-exit-policy","Tutorial · Find a better exit policy","Take the trades the fleet already made and re-run them under different exit rules: why tightening an exit is measurable and loosening one is only a hypothesis...","learn",0.6,0],["/tutorials/read-the-trading-fleet","Tutorial · Read the trading fleet","Tell a working autonomous strategy from a lucky one: why realized profit is the only profit, how to read profit factor against win rate and drawdown, the...","learn",0.6,0],["/docs/live-steps","Docs · Live steps: documentation that runs","Tutorial steps that perform a real request against the live three.ws API from your browser and render the real response, so a sample can never quietly go...","learn",0.7,0],["/docs/mcp-safety","Docs · MCP tool safety","What an MCP tool's safety annotations mean on three.ws and why you can trust them: read-only tools never change what you asked about, anything that spends is...","learn",0.7,0],["/mcp-tools","MCP Tool Catalog","Every MCP tool three.ws publishes, searchable in one place: what it does, which server hosts it, what it costs in USDC, and whether an AI client can run it...","learn",0.8,0],["/docs/trading-experiment","Docs · The 10 SOL trading experiment","The full risk policy behind the autonomous fleet: entry band, position sizing, taking initials at 2x, the moon-bag floor, trailing and hard stops, and how to...","learn",0.6,0],["/tutorials/getting-started","Tutorial · Getting started (hosted)","A five-minute, no-code tour: create an agent, pick a body, give it a personality, share the URL.","learn",0.8,0],["/tutorials/explore-docs-world","Tutorial · Explore the docs as a 3D world","Walk an avatar through the documentation: fourteen sections as glowing pavilions, live pages read in-world, shareable deep links, and your own GLB as the body.","learn",0.8,0],["/tutorials/embed-in-30-seconds","Tutorial · Embed in 30 seconds","Drop one script tag into any HTML page. Your agent loads, auto-sizes, and starts animating.","learn",0.8,0],["/tutorials/customize-appearance","Tutorial · Customize size, position & background","Tune every visible knob on the <agent-3d> element: layout mode, corner placement, size, background, camera framing, and the ambient clip.","learn",0.8,0],["/tutorials/swap-avatar-in-studio","Tutorial · Pick & swap an avatar in Studio","Swap an agent's 3D body from the Outfit panel in one click, and have the change reach every embed without touching your snippet.","learn",0.8,0],["/tutorials/greeting-and-first-speech","Tutorial · Add a greeting & first speech line","Make your agent say hello the moment it loads, and have its mouth move with the words.","learn",0.8,0],["/tutorials/share-your-agent","Tutorial · Share your agent (link, QR, social preview)","Get a permanent link to your agent, generate a QR for print, and share the URL that unfurls with its real name, description, and card.","learn",0.8,0],["/tutorials/selfie-to-avatar","Tutorial · Turn a selfie into a 3D avatar","Snap or upload a photo and get a rigged 3D avatar that can walk, wave, and talk, then put it on an agent.","learn",0.8,0],["/tutorials/view-in-ar","Tutorial · View your 3D model in AR","See any three.ws model in augmented reality and walk around it in your kitchen, straight from the browser with no app to install. iOS Quick Look, Android Scene...","learn",0.8,0],["/tutorials/import-avatar-url","Tutorial · Import an avatar by URL","Bring any hosted glTF/GLB avatar into three.ws by link: auto-validated, auto-rigged, ready for an agent.","learn",0.8,0],["/tutorials/walk-companion","Tutorial · Add the Walk Companion to your site","Drop a 3D avatar that strolls across any web page (corner mascot or full-page playground) with one script tag, the npm SDK, or a postMessage bridge.","learn",0.8,0],["/tutorials/sperax-tour","Tutorial · Load a ready-made 3D tour for a DeFi protocol (Sperax)","The Tour Builder's first template: an 8-stop guided tour of Sperax's USDs auto-yield stablecoin, ready to load, edit, and export as a one-tag snippet in...","learn",0.8,0],["/tutorials/first-agent","Tutorial · Build your first agent (from scratch)","A complete walkthrough from a blank HTML file to a live, talking 3D character you wrote yourself: no framework, no build tools.","learn",0.8,0],["/tutorials/embed-on-website","Tutorial · Embed on a website (HTML, React, Next.js)","Five different ways to add an agent to your site: pick the one that matches how you build today.","learn",0.8,0],["/tutorials/personal-ai-site","Tutorial · Build a personal AI website","A 3D version of you, on your domain, ready to answer any question about your work: with a portfolio, contact form, and resume.","learn",0.8,0],["/tutorials/js-api-events","Tutorial · Drive the agent with the JavaScript API","Listen for the ready event, play animations on demand, make the agent speak from anywhere in your app code.","learn",0.8,0],["/tutorials/web-component-end-to-end","Tutorial · Use the <agent-3d> web component end-to-end","Skip the script tag: drop a real custom element into your DOM, bind attributes, and use the full event lifecycle.","learn",0.8,0],["/tutorials/build-a-site-concierge","Tutorial · Build a site concierge from the building blocks","How the Concierge widget is assembled: the talking avatar, the streaming chat, the tool calls, and how to point the same parts at your own backend over...","learn",0.8,0],["/tutorials/trigger-from-page-events","Tutorial · Trigger the agent from page events","Make your agent react to clicks, scrolls, form submits, and route changes: turn it into a real co-pilot, not a chat widget.","learn",0.8,0],["/tutorials/upload-custom-glb","Tutorial · Upload a custom GLB avatar","Bring your own model: any glTF 2.0 .glb from Blender, three.ws Studio, or any other source. Get it validated, fixed, and live.","learn",0.8,0],["/tutorials/connect-ai-brain","Tutorial · Connect Anthropic, OpenAI, or xAI as the brain","Plug your own model provider into the agent loop. Bring your API key, choose your model, control cost and latency.","learn",0.8,0],["/tutorials/create-and-edit-memory","Tutorial · Create, enhance & edit agent memory","Five ways to teach an agent a fact that sticks between sessions: the dashboard, the agent itself, MCP tools, the REST API, and a skill. Plus how to sharpen...","learn",0.8,0],["/tutorials/place-agent-irl","Tutorial · Place your agent in the real world (IRL)","Use camera passthrough, a joystick, and tap-to-place to drop your 3D agent into your physical space: and understand how location privacy works.","learn",0.8,0],["/tutorials/voice-and-lipsync","Tutorial · Give your agent a voice with lipsync","Add real-time text-to-speech with synchronized mouth movement: pick or clone a voice, drive visemes from audio, and wire it into a live agent.","learn",0.8,0],["/tutorials/pay-for-x402-service","Tutorial · Discover and pay for an x402 service","Browse the x402 Bazaar and call a paid API from your agent: the 402 challenge, the USDC payment, and the retry, end to end.","learn",0.8,0],["/tutorials/emotion-from-data","Tutorial · Animations from data: wire your agent's gestures to real APIs and AI","Trigger real body animations (celebrate, dance, flinch) from a live data feed. A free lexicon lane to prove the wiring, then a real AI model classifying...","learn",0.8,0],["/tutorials/custom-skill","Tutorial · Build a custom skill","A complete walkthrough of building a weather skill an agent can invoke: bundle format, LLM tool calling, context API.","learn",0.8,0],["/tutorials/register-onchain","Tutorial · Register your agent on-chain (ERC-8004)","Give your agent a permanent, verifiable identity. Publish an ERC-8004 attestation anyone can read from any chain.","learn",0.8,0],["/tutorials/mint-pumpfun-token","Tutorial · Mint an agent token on Pump.fun","Launch a Solana token for your agent, bond it to its on-chain identity, and let people speculate on (or hold) a piece of it.","learn",0.8,0],["/tutorials/paid-x402-endpoint","Tutorial · Build a paid x402 endpoint your agent calls","Stand up an API that other agents pay USDC to call: using the x402 protocol on Base mainnet. Real money, real flow.","learn",0.8,0],["/tutorials/monetize-mcp-server","Tutorial · Monetize an MCP server: charge per tool call","Build an MCP server whose tools charge other agents per call in USDC on Solana. One free orientation tool, one paid tool that does real work, and a test that...","learn",0.8,0],["/tutorials/x402-server-sdk","Tutorial · Meter any API with the x402-server SDK","Turn an ordinary HTTP handler into a paid one with @three-ws/x402-server. Solana-first, framework-agnostic, and runnable offline before you touch a wallet.","learn",0.8,0],["/tutorials/self-host-agent-backend","Tutorial · Self-host the agent backend","Run the full three.ws backend on your own infrastructure: workers, function endpoints, model proxies. No three.ws dependency in production.","learn",0.8,0],["/tutorials/multi-agent-coordination","Tutorial · Multi-agent coordination","Two or more agents on the same page that talk to each other: turn-taking, shared memory, delegating subtasks.","learn",0.8,0],["/tutorials/mcp-server-for-your-agent","Tutorial · Expose your agent as an MCP server","Wrap your agent in the Model Context Protocol so any MCP-compatible client (Claude Desktop, Cursor, etc.) can drive it.","learn",0.8,0],["/tutorials/skill-with-database-auth","Tutorial · Custom skill with database + auth","A real production skill: Postgres-backed CRM lookup, signed requests, per-user permissions, rate limits. Not a toy weather demo.","learn",0.8,0],["/tutorials/deploy-to-vercel-custom-domain","Tutorial · Deploy to Vercel with a custom domain","Take a forked three.ws and ship it as agent.yourcompany.com: CI, environment variables, custom domain, SSL, the lot.","learn",0.8,0],["/tutorials/claim-threews-name","Tutorial · Claim a .threews.sol name & get paid by name","Mint a *.threews.sol Solana subdomain for your agent and accept USDC payments addressed to the name instead of a raw wallet.","learn",0.8,0],["/tutorials/mine-vanity-address","Tutorial · Mine a Solana vanity address","Grind a custom-prefix Solana address in the browser, then prove how it was made with the proof-of-grind receipt, gallery, and bounty market.","learn",0.8,0],["/docs/avatar-cli","Docs: Avatar CLI","Command reference for @three-ws/avatar-cli: init, validate, hash, and preview, with every flag, exit code, and JSON shape, plus the two checks that gate a...","learn",0.7,0],["/docs/rig-doctor","Rig Doctor reference","What each Rig Doctor verdict means, how limb-group coverage is scored, what the in-browser repair changes, the eleven rig conventions it recognises, and the...","learn",0.7,0],["/tutorials/ship-an-avatar-manifest","Tutorial · Ship an avatar manifest","Turn a raw GLB into a signed-off, hash-anchored manifest: one document that names the avatar, records the exact bytes of its mesh, declares its skeleton, and...","learn",0.8,0],["/tutorials/write-a-guard","Tutorial · Write a repository guard","This repo has no CI, so a guard is the only thing between a mistake and production. Build one that fails the build when a server-side fetch has no timeout...","learn",0.8,0],["/guards","Repository guards","Every mechanical guard that protects the three.ws codebase, and the stage each one runs in. This repository has no CI, so correctness is enforced by fast local...","learn",0.6,0],["/brownout","Brownout","Every response from this API says where its data came from and how fresh it is, and every declared fallback has been proven by breaking the upstream it...","learn",0.6,0],["/docs/tutorials/write-a-guard","Docs · Write a repository guard","Build a real guard end to end: write the checker, give it an npm script, register it in data/guards.json with the violation it must reject, wire it into a...","learn",0.5,0],["/tutorials/earn-and-spend-in-play","Tutorial · Earn and spend in /play","Run the full economic loop in the open world: gather raw materials, sell them to a vendor, buy a better tool, bank the rest so death can't take it, and spin...","learn",0.8,0],["/docs/showcase","Docs: The showcase","The public directory of ERC-8004 agents that registered a real 3D avatar. Nothing is curated: an agent appears because the crawler verified its on-chain...","learn",0.7,0],["/docs/tutorials/earn-and-spend-in-play","Docs · Tutorial: earn and spend in /play","Run the full economic loop in the open world: gather materials, sell them to the vendor, buy a better tool, bank what you cannot afford to lose, and spin the...","learn",0.7,0],["/tutorials/animate-your-agent","Tutorial · Give your agent body language","Clips, slots and hints: the three-name chain that makes an agent nod, look down while it reads, celebrate a settled payment, and dance on request. Re-point any...","learn",0.8,0],["/docs/ghost-copy","Docs · Ghost-copy","Replay a verified trader agent's real closed on-chain trades against a wallet that never existed: pick a leader, a budget, and a window, and see where copying...","learn",0.6,0],["/docs/fork-trade","Docs · Fork a trade","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...","learn",0.6,0],["/docs/trader-passport","Docs · Trader Passport","A trader track record other apps can verify: once a day each ranked trader's rolled-up score is committed to Solana as a signed SPL-Memo attestation, and this...","learn",0.6,0],["/docs/portfolio","Docs · Wallet Portfolio","How the live wallet portfolio works: the keyless Solana-first data sources behind /api/crypto/portfolio, the stable/major/token classification, the honest 24h...","learn",0.6,0],["/docs/airdrops","Docs · Airdrop Checker","How the airdrop eligibility checker works: the keyless Solana activity scan and Etherscan V2 EVM scan, the check DSL and scoring thresholds, the honesty...","learn",0.6,0],["/docs/community","Docs · Community","Where the three.ws community talks: GitHub Discussions, the Telegram community, the X community, the IBM Community group, and the release channel, with...","learn",0.6,0],["/docs/first-contribution","Docs · Your first contribution","Clone to open pull request in about 15 minutes, with a complete worked example: teaching the avatar retargeter a bone-naming convention it did not know, plus...","learn",0.6,0],["/docs/triage","Docs · Triage","How incoming issues and pull requests get sorted, what every label means, how to claim work, and the response times contributors can expect.","learn",0.6,0],["/docs/pill-mascot","Docs · Rigging the pump.fun pill mascot","How a static capsule mascot with four nubs became a 52-bone, six-clip avatar: limb discovery from a distance transform, medial-axis skinning, and a bind pose...","learn",0.5,0],["/docs/agent-vitals","Docs · Agent vitals: can it act?","Every liveness check was green while ten of twelve autonomous agents had not acted in weeks. Capability attestation models an agent's preconditions as a causal...","learn",0.6,0],["/docs/tty","Docs · Terminal renderer","curl three.ws/tty and a rigged 3D agent walks in your terminal. The hosted streaming endpoint and its parameters, plus @three-ws/tty-3d, the CLI and library...","learn",0.5,0],["/tutorials/connect-your-home","Tutorial · Connect your home","Point your agent at a real Home Assistant and it runs your actual house: lights, thermostat, and the scenes you already built. Covers the three honest ways to...","learn",0.8,0],["/docs/pocket","Docs · Pocket Console","How the /pocket handheld works: the D-pad and gamepad controls, the three cartridges, the URL params that make a share link, and the one iframe that puts a...","learn",0.6,0],["/awesome","Awesome 3D Agents","A curated, link-checked list of everything you need to give an AI agent a body: text-to-3D models, capture and Gaussian splatting, avatars, rigging, motion...","learn",0.8,0],["/blog","Blog","Editorial index of three.ws launches and long-form posts.","blog",0.7,0],["/blog/ibm-user-group-first-in-world-meetup-recap","The Three.ws User Group's First In-World Meetup: How It Went","The Three.ws User Group on IBM Community held its first meetup inside three.ws itself, 8 AM to 5 PM Pacific, peaking at 3,145 concurrent users in the $THREE...","blog",0.6,0],["/blog/image-to-3d-on-nvidia-l4-and-blackwell","Image-to-3D on NVIDIA L4 and Blackwell: Shipping Hunyuan3D 2.1 on Cloud Run GPUs","A field report from the three.ws GPU fleet: why Hunyuan3D 2.1 could not load on an NVIDIA L4, why CUDA 12.4 wheels have no sm_120 kernels for RTX PRO 6000...","blog",0.6,0],["/blog/monetize-mcp-server-x402-paid-tools","How to Monetize an MCP Server: Paid Tools with x402","A complete guide to charging for MCP tools with x402: price a tool in USDC, issue the 402 challenge, verify and settle on Solana, get discovered in the bazaar...","blog",0.6,0],["/blog/three-ws-openai-select-partner","three.ws Named an OpenAI Select Partner","three.ws has been named an OpenAI Select Partner within the OpenAI Partner Network. What we ship on OpenAI surfaces today: a free 3D Studio MCP connector for...","blog",0.6,0],["/blog/autonomous-trading-experiment","We Gave 11 AI Agents Their Own Wallets and Real SOL. Here Are All 90 Trades.","Two weeks of fully autonomous pump.fun trading on Solana: 11 armed strategies, 90 closed real-money trades, every entry thesis, every exit, every mistake. Plus...","blog",0.6,0],["/blog/first-autonomous-trade","Our Agent Made Its First Autonomous Trade. Here Is Every Decision It Took.","A three.ws agent sniped a brand-new pump.fun launch and closed it at +42.38%, fully autonomously. The full postmortem: every gate it passed, the on-chain...","blog",0.6,0],["/blog/concierge-3d-chat-widget","Concierge: We Gave the Site Chatbot a Face","Every website has the same faceless chat bubble. We shipped one with a rigged 3D avatar that blinks, lipsyncs, and speaks streaming answers grounded in your...","blog",0.6,0],["/blog/inside-the-forge","Inside the Forge: How a Prompt Becomes a 3D Model","What actually happens between typing a prompt on three.ws and downloading a textured 3D model: the reference image, the engine grid, self-healing failover...","blog",0.6,0],["/blog/three-ws-quicknode-startup-program","three.ws Joins the Quicknode Startup Program","three.ws has been accepted into the Quicknode Startup Program and approved for free infrastructure credits, expanding the RPC backbone behind its Solana-first...","blog",0.6,0],["/blog/three-ws-alibaba-cloud-partnership","three.ws Joins the Alibaba Cloud Partner Network","three.ws is now an Alibaba Cloud Partner, bringing Qwen foundation models and Asia-Pacific cloud infrastructure to the three.ws 3D AI agent platform.","blog",0.6,0],["/blog/x402-stripe-for-agent-payments","The Stripe of x402: How three.ws Turned Agent Payments Into One Line of Code","HTTP 402 sat unused for thirty years. Agents revived it. three.ws built the drop in payment modal that makes x402 a one liner, on top of a full stack of agent...","blog",0.6,0],["/blog/see-your-3d-in-ar","See Your 3D Avatar in the Real World: AR Lands on three.ws","Every 3D model and avatar on three.ws now has a View in AR button. On mobile it places the model in your real space through the camera. On desktop, a QR code...","blog",0.6,0],["/blog/text-to-3d-is-live","Text to 3D Is Live: Type a Prompt, Download a 3D Model","Forge is live on three.ws: type a description and get a textured, downloadable 3D model (GLB) in your browser. Image to 3D from photos works too. Free draft...","blog",0.6,0],["/blog/3d-ai-crypto-convergence","3D + AI + Web3 Just Converged: three.ws Shipped the Whole Stack","A web2 unicorn just raised ~$200M to build 3D AI agents. three.ws is the only crypto-native team that already shipped the full stack: browser 3D, a...","blog",0.6,0],["/blog/three-ws-dextools-social-boost-buyback","three.ws Wins DEXTools Social Boost: $5,543 $three Buyback","three.ws is DEXTools' Social Boost winner of the week, earning a $5,543 buyback. The DEXTools wallet now holds 2.47M $three.","blog",0.6,0],["/blog/three-ws-featured-on-alibaba-cloud-marketplace-blog","three.ws Featured on the Alibaba Cloud Marketplace Blog","Alibaba Cloud Marketplace published an editorial on three.ws: browser-native 3D AI agents you deploy with a single <agent-3d> tag, with a Claude-powered...","blog",0.6,0],["/blog/three-ws-ibm-collaboration","Showcasing the three.ws × IBM Partnership","three.ws and IBM showcased their partnership: embedding a persistent, on-chain 3D agent into any platform as easily as a YouTube video, with the agent brain...","blog",0.6,0],["/blog/three-ws-play-coin-communities","We turned every memecoin into a live 3D world you can walk into","How we built /play: isolated multiplayer worlds keyed to a token's mint, driven by live on-chain trades, with proximity voice chat, an in-world buy flow, and...","blog",0.6,0],["/blog/three-ws-aws-partner","three.ws Joins the AWS Partner Network","three.ws is now an official AWS Partner, enrolled in the AWS Partner Network (APN) Software Path as a Technology Partner. The open-source platform for 3D AI...","blog",0.6,0],["/blog/three-ws-on-aws-marketplace","three.ws Launches on AWS Marketplace, Bringing On-Chain 3D AI Agents to Enterprise Procurement","three.ws is now live on AWS Marketplace as a SaaS subscription. AWS customers can subscribe directly, bill to their AWS invoice, spend AWS Activate credits...","blog",0.6,0],["/blog/agent-3d-web-component","We Just Shipped the 3D Layer for the Internet: <agent-3d>","Drop one <agent-3d> web component on your site and give any page an AI with LLM brain, memory, emotions, DOM awareness, password field privacy, and an on-chain...","blog",0.6,0],["/blog/2500-new-animations","2,500 New 3D Animations Coming to three.ws","three.ws is expanding its animation library with 2,500 new 3D animations, giving every agent vastly more expressive range across emotions, gestures, reactions...","blog",0.6,0],["/blog/three-ws-x402-bazaar","three.ws Listed on Coinbase x402 Bazaar and agentic.market","three.ws is now a verified service provider on the Coinbase x402 Bazaar and agentic.market, the app store and discovery layer for AI agents with 480k active...","blog",0.6,0],["/blog/real-time-voice-interaction","Real-Time Voice Interaction with 3D AI Agents (Preview)","three.ws ships an early preview of real-time voice interaction with 3D AI agents. Agents listen, reason with memory and emotions, respond in voice, and support...","blog",0.6,0],["/blog/three-ws-on-alibaba-cloud-marketplace","three.ws Launches on Alibaba Cloud Marketplace, Bringing Native x402 Agent Payments to Hyperscale","three.ws is now live on the Alibaba Cloud International Marketplace. The listing makes <agent-3d> available to every Alibaba Cloud customer worldwide and...","blog",0.6,0],["/blog/three-ws-on-bnb-chain-dappbay","three.ws Listed on BNB Chain's Dappbay Directory","three.ws is now listed on Dappbay, BNB Chain's official dApp directory, under AI Agent Launchpad, AI Data, and AI Infra. The listing puts the <agent-3d> tag in...","blog",0.6,0],["/blog/three-ws-hackernoon-partnership","three.ws Teams Up with HackerNoon","three.ws is partnering with HackerNoon to launch a builder-focused initiative with feature articles, tutorials, and developer guides for those shipping with AI.","blog",0.6,0],["/blog/three-ws-on-coinmarketcap","three.ws Is Now Live on CoinMarketCap","three.ws is now live on CoinMarketCap. Join the community page for real-time discussion and stay updated on the platform for 3D on-chain AI agents.","blog",0.6,0],["/blog/how-to-embed-3d-onchain-agents","How to Embed 3D On-Chain Agents on Your Site","A complete walkthrough for embedding a three.ws 3D on-chain agent on any website using the <agent-3d> web component, from setup to CORS configuration and page...","blog",0.5,0],["/blog/pumpfun-agent-payments-sdk","three.ws Integrates the Pump.fun Agent Payments SDK","three.ws has integrated the Pump.fun agent payments SDK. Your 3D AI agent doesn't just execute tasks, it earns on-chain revenue and fuels its own autonomous...","blog",0.6,0],["/blog/three-ws-speraxusd-integration","three.ws Ships Inside SperaxUSD: DeFi Gets a 3D Face","three.ws is now integrated with SperaxOS, fully wired into the production DeFi stack. Agents get a 3D body, memory, voice, and an on-chain identity, and they...","blog",0.6,0],["/blog/agent-builder-studio-launch","Agent Builder Live: Studio Redesign, LLM Chat Upgrade","three.ws ships Agent Builder, an improved Studio design, and a major LLM Chat upgrade. Agents are now payable, tradeable, and discoverable.","blog",0.6,0],["/blog/animation-emotion-control","Full Animation & Emotion Control, Plus Pump.fun Live Feed","three.ws now ships full animation and emotion control for 3D agents, with live Pump.fun feed integration. Your agents react to any API or data feed in real...","blog",0.6,0],["/blog/three-ws-ibm-business-partner","three.ws Is Now an Official IBM Business Partner","three.ws has been accepted into IBM's official Business Partner program, bringing together decentralized on-chain 3D agent identity with IBM's leadership in...","blog",0.6,0],["/blog/three-token-listings","$THREE Listed on Coinbase, CoinGecko, Jupiter, and Investing.com","$THREE is now listed and verified across Coinbase, CoinGecko, Jupiter Exchange, and Investing.com, giving the three.ws community every major on-ramp and price...","blog",0.6,0],["/blog/solana-wallet-integration","Solana Wallet Integration for Autonomous 3D Agents","three.ws 3D agents now have native Solana wallets. Your agent can hold and spend money autonomously: earning from skills, paying for inference, and executing...","blog",0.6,0],["/blog/three-ws-google-cloud-partnership","three.ws Joins Google Cloud for Web3 Startups","three.ws is joining forces with Google Cloud, bringing cloud-scale rendering and AI infrastructure to 3D on-chain agents.","blog",0.6,0],["/blog/three-ws-on-anthropic-mcp-registry","three.ws Listed on Anthropic's Official MCP Registry","three.ws is now listed on Anthropic's official Model Context Protocol Registry, the canonical directory for AI-to-tool integrations used by Claude, ChatGPT...","blog",0.6,0],["/legal","Legal","Every three.ws policy in one place, plus which address to use to report copyright, abuse, or privacy issues.","legal",0.4,0],["/legal/privacy","Privacy Policy","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.","legal",0.2,0],["/legal/eula","End-User License Agreement","License terms for the three.ws Seeker/Saga mobile app: what the license covers, camera and selfie data, updates, and termination.","legal",0.2,0],["/legal/nvidia-ngc-eula","NVIDIA NGC Container EULA","License terms for three.ws container images distributed through the NVIDIA NGC catalog: what the license covers, the model weights the image does not ship, and...","legal",0.2,0],["/legal/tos","Terms of Service","The agreement between you and three.ws: your account, acceptable use, payments and on-chain activity, liability, and DMCA takedowns.","legal",0.2,0],["/legal/risk","Risk Disclosure","Risk disclosure for real-funds features: experimental software, total-loss risk, autonomous agents, no liability.","legal",0.2,0],["/legal/content-policy","Content Policy","What you may publish, mint, and monetise on three.ws: prohibited content, agent behaviour, marketplace listings, and how we enforce.","legal",0.2,0],["/sitemap.xml","sitemap.xml","XML sitemap for search-engine crawlers.","machine",0.5,2],["/api/mcp-policy","MCP trust policy","A ready-to-paste allowlist telling an AI client which three.ws MCP tools it may run without asking you. Three profiles from strict to open, in Claude, VS Code...","machine",0.5,2],["/llms.txt","llms.txt","AI-agent-friendly index of every public page (Howard convention).","machine",0.5,2],["/llms-full.txt","llms-full.txt","Expanded llms.txt with full descriptions and content hints.","machine",0.5,2],["/robots.txt","robots.txt","Crawler directives.","machine",0.5,2],["/openapi.json","OpenAPI","Machine-readable HTTP API spec.","machine",0.5,2],["/.well-known/x402",".well-known/x402","x402 paid-API discovery document.","machine",0.5,2],["/.well-known/agent-attestation-schemas",".well-known/agent-attestation-schemas","JSON schemas for agent attestations.","machine",0.5,2],["/.well-known/oauth-authorization-server",".well-known/oauth-authorization-server","OAuth 2.1 authorization-server metadata.","machine",0.5,2],["/.well-known/chat-plugin.json",".well-known/chat-plugin.json","ChatGPT-style plugin manifest.","machine",0.5,2],["/api/mcp","MCP server","Hosted Model Context Protocol server (Streamable HTTP): avatars, glTF validation, agent data, and memory as tools. Six more hosted servers are listed in...","machine",0.5,2],["/.well-known/mcp.json",".well-known/mcp.json","Directory of every hosted three.ws MCP server: endpoint, transport, auth, and what each one does.","machine",0.5,2],["/.well-known/agent-card.json",".well-known/agent-card.json","A2A agent card: what three.ws is, what it can do, and where the paid-service catalog lives.","machine",0.5,2],["/.well-known/x402.json",".well-known/x402.json","x402 service catalog: every paid pay-per-call endpoint with price, network, and input schema.","machine",0.5,2]],"intents":[{"id":"first-time","title":"I am new here. Where do I start?","blurb":"The shortest path from nothing to a live 3D agent on your own page.","match":["get started","start","new here","begin","first time","onboarding","how do i use this","what do i do","quickstart","tutorial","help"],"steps":[{"do":"Walk the guided setup. It asks three questions and creates your first agent.","to":"/start"},{"do":"Give it a body: describe the avatar you want and generate it.","to":"/create/prompt"},{"do":"Put it on a page. Widget Studio writes the embed code for you.","to":"/studio"}]},{"id":"make-avatar","title":"Make a 3D avatar","blurb":"Text to a rigged, animation-ready GLB.","match":["make an avatar","create avatar","3d avatar","generate character","text to 3d","new avatar","build a character","make a character"],"steps":[{"do":"Describe the avatar you want. The forge returns a rigged GLB.","to":"/create/prompt"},{"do":"Pose and animate it in the Animation Studio.","to":"/pose"},{"do":"Browse what others made if you would rather start from an existing one.","to":"/gallery"}]},{"id":"avatar-from-photo","title":"Turn a photo into a 3D avatar","blurb":"A selfie or a product photo becomes a textured 3D model.","match":["selfie","photo to 3d","image to 3d","picture to model","scan myself","turn a photo into","from a photo","my face"],"steps":[{"do":"Use Selfie to Avatar for a person.","to":"/create/selfie"},{"do":"Use Image to 3D for an object or a product shot.","to":"/image-to-3d"},{"do":"Need the highest fidelity? Forge Max runs the slow, high-quality lane.","to":"/forge-max"}]},{"id":"embed-on-site","title":"Put an avatar on my website","blurb":"One script tag and one custom element. Works in plain HTML, React, and Next.js.","match":["embed","add to my website","put on my site","integrate","script tag","iframe","react","next.js","web component","install on my page"],"steps":[{"do":"Build the widget visually and copy the generated snippet.","to":"/studio"},{"do":"Follow the 30-second version if you just want the two lines.","to":"/tutorials/embed-in-30-seconds"},{"do":"Framework-specific setup for React and Next.js.","to":"/tutorials/embed-on-website"}]},{"id":"create-agent","title":"Create an AI agent","blurb":"An agent with a body, a mind, a wallet, and an on-chain identity.","match":["create an agent","make an agent","new agent","ai agent","build a bot","my agent","agent identity"],"steps":[{"do":"Create the agent and give it a name, a personality, and a model.","to":"/create-agent"},{"do":"Tune its behaviour, tools, and voice in Agent Studio.","to":"/agent-studio"},{"do":"Manage everything you own from My Agents.","to":"/my-agents","note":"Requires sign-in"}]},{"id":"launch-coin","title":"Launch a coin","blurb":"Mint a token for your agent on pump.fun, from the platform.","match":["launch a coin","launch token","mint a token","pump fun","pumpfun","create a coin","new token","memecoin","ticker"],"steps":[{"do":"Launch the coin. Name, ticker, image, and the initial buy.","to":"/launch"},{"do":"Read what each field does before you sign anything.","to":"/docs/pump-launcher"},{"do":"Watch it land in the platform launch feed.","to":"/launches"}]},{"id":"get-paid","title":"Get paid per API call","blurb":"Meter any endpoint with x402 and let other agents pay to use it.","match":["get paid","make money","monetize","charge for my api","paid endpoint","sell a service","earn","revenue","x402 server","per call"],"steps":[{"do":"Wire the paywall in x402 Studio.","to":"/x402/studio"},{"do":"Follow the worked example of a paid endpoint end to end.","to":"/tutorials/paid-x402-endpoint"}]},{"id":"pay-for-service","title":"Pay another agent for a service","blurb":"Discover a paid endpoint and settle the call in USDC.","match":["pay for","buy a service","x402 client","call a paid api","402","discover services","bazaar","spend"],"steps":[{"do":"Browse every paid endpoint the network exposes.","to":"/x402"},{"do":"Follow the discover-and-pay walkthrough.","to":"/tutorials/pay-for-x402-service"},{"do":"Fund the wallet your agent pays from.","to":"/wallet","note":"Requires sign-in"}]},{"id":"use-mcp","title":"Connect this to Claude or another MCP client","blurb":"Give your assistant 3D generation, wallets, and market intel as tools.","match":["mcp","claude","cursor","model context protocol","connect my assistant","tools for my ai","claude desktop"],"steps":[{"do":"Browse every tool the MCP servers expose.","to":"/mcp-tools"},{"do":"Copy the client config for your assistant.","to":"/docs/mcp"},{"do":"Start with the free 3D Studio server if you want zero setup.","to":"/docs/mcp-studio"}]},{"id":"animate","title":"Animate or pose an avatar","blurb":"Clips, gestures, and mocap on any humanoid rig.","match":["animate","animation","pose","walk cycle","idle","gesture","mocap","motion","make it move","dance"],"steps":[{"do":"Pose and preview clips on your own model.","to":"/pose"},{"do":"Browse the clip library and copy the one you want.","to":"/animations"},{"do":"Map gestures to your agent's reactions.","to":"/gestures"}]},{"id":"talking-avatar","title":"Make my avatar talk","blurb":"Lip-synced speech, a voice, and an exportable video.","match":["talk","speech","voice","lip sync","talking head","say something","video","tts","speaking avatar"],"steps":[{"do":"Pick or clone a voice in the Voice Lab.","to":"/voice"},{"do":"Render a lip-synced talking video from a script.","to":"/create/video"},{"do":"Drive the same avatar live from your webcam.","to":"/temporary"}]},{"id":"sell-agent","title":"List or sell an agent","blurb":"Publish to the marketplace and let others fork or buy it.","match":["sell","list my agent","marketplace","publish","share my agent","fork","storefront"],"steps":[{"do":"See what sells and how listings are presented.","to":"/marketplace"},{"do":"Publish from the agent you own.","to":"/my-agents","note":"Requires sign-in"},{"do":"Check demand before you price it.","to":"/marketplace/analytics"}]},{"id":"account","title":"Sign in or manage my account","blurb":"Email, wallet, billing, credits, and API keys.","match":["sign in","log in","login","account","register","sign up","password","billing","api key","credits","settings","profile"],"steps":[{"do":"Sign in with email or a Solana wallet.","to":"/login"},{"do":"No account yet? Create one.","to":"/register"},{"do":"Keys, billing, and usage live in the dashboard.","to":"/dashboard","note":"Requires sign-in"}]},{"id":"status","title":"Is something broken?","blurb":"Live uptime, 90 days of history, and a machine-readable feed.","match":["status","is it down","outage","uptime","broken","not working","incident","health"],"steps":[{"do":"Check live status and 90-day uptime for every surface.","to":"/status"},{"do":"Poll the same data as JSON from your own monitor.","to":"/api/status"},{"do":"Still stuck? The docs index is the fastest way to the right page.","to":"/docs/start-here"}]},{"id":"map","title":"Show me everything","blurb":"The full route map: every page on three.ws, grouped and searchable.","match":["everything","all pages","site map","sitemap","what else","browse","map","atlas","index","whats here"],"steps":[{"do":"Browse the whole platform as one map.","to":"/atlas"},{"do":"Prefer a flat list? The sitemap has every route.","to":"/sitemap"},{"do":"Reading as a machine? Take llms.txt instead.","to":"/llms.txt"}]}]}\ No newline at end of filediff --git a/public/changelog-recent.json b/public/changelog-recent.jsonindex 3e372ddfa..57cd1647b 100644--- a/public/changelog-recent.json+++ b/public/changelog-recent.json@@ -1,14 +1,55 @@{- "generated_at": "2026-09-09T05:54:28.300Z",+ "generated_at": "2026-09-09T07:20:21.694Z","generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json","site": {"name": "three.ws","url": "https://three.ws"},- "total": 3623,+ "total": 3634,"complete": false,"full_feed": "/changelog.json","entries": [+ {+ "date": "2026-09-09",+ "type": "launch",+ "title": "Docs · Fade Radar",+ "summary": "How the Fade Radar scores a coin's buy side: what makes a wallet a reverse indicator, the 0 to 100 fade score, the verdict bands, and the out-of-sample measurement behind them.",+ "link": "/docs/fade-radar",+ "tags": [+ "launch"+ ]+ },+ {+ "date": "2026-09-09",+ "type": "launch",+ "title": "Fade Radar: the wallets that are never right",+ "summary": "The inverse of the Smart Money Radar. Every pump.fun coin ranked by how much of its buy side comes from wallets with a judged on-chain record and not one winner in it, with the measured, out-of-sample odds behind each verdict.",+ "link": "/fade",+ "tags": [+ "launch"+ ]+ },+ {+ "date": "2026-09-09",+ "type": "update",+ "title": "A link that opens your house in 3D now really opens it in 3D",+ "summary": "The live home page remembers whether you last looked at your house in 3D or as a room list, which is what you want when you open it yourself. It was also overruling links that asked for one view by name: once you had used the 2D view even once on a device, every /smart-home/<id>?view=3d link on that device quietly opened flat again. That matters for the two cases the parameter exists for, a link you share with someone in the house and the address a kitchen or wall display is pinned to. A view asked for in the link now wins, for 3D, 2D and the floorplan alike, and following such a link no longer overwrites the preference that device chose for itself.",+ "link": "/docs/home-scene",+ "tags": [+ "fix"+ ]+ },+ {+ "date": "2026-09-09",+ "type": "update",+ "title": "An app key can no longer say yes to unlocking your door",+ "summary": "A person saying yes is the one thing that stands between an agent and your front door, and we found a way around it. If you had ever issued an API key or connected an app to your three.ws account, that key could send an unlock request with the \"the owner already approved this\" flag set, and the lock opened, with nobody asked and nothing to click. We reproduced it against a real house and a real deadbolt before fixing it. Two things changed. Only a signed-in browser session can say yes now: a key or a connected app can ask to unlock, open or disarm, and is always answered with \"a person has to approve this\", exactly as the agent in your chat window already was. And the home permissions you approve when you connect an app are now actually enforced on every home request, so an app you gave read-only access to, or one you never gave home access at all, is refused instead of let through. Nothing legitimate changed: your agent still asks, you still approve, the door still opens.",+ "link": "/smart-home",+ "tags": [+ "security",+ "fix"+ ]+ },{"date": "2026-09-09","type": "update",@@ -30,6 +71,17 @@"fix"]},+ {+ "date": "2026-09-09",+ "type": "update",+ "title": "Connecting a home: the page now says which state it is in, out loud",+ "summary": "Two moments on /smart-home were doing the right thing silently. Typing an address that can never work (a 192.168 number, a .local name) has always put the reason under the field straight away, before anything is sent, but the message was carried by colour alone and a screen reader never read it out; it is now announced the moment it appears, and marked in a way that does not depend on seeing red. And a house that has stopped answering, is refusing the stored token, or has simply gone quiet is now labelled as such by the page itself rather than only in the sentence on its card. Nothing about what you see moves: the last known summary of your house stays exactly where it was, with how long ago it last answered, because a home that went quiet should never look like a home that was deleted.",+ "link": "/smart-home",+ "tags": [+ "improvement",+ "fix"+ ]+ },{"date": "2026-09-09","type": "update",@@ -52,6 +104,27 @@"improvement"]},+ {+ "date": "2026-09-09",+ "type": "update",+ "title": "Fade Radar: the wallets that have never once been right, and the coins they are crowding into",+ "summary": "The Smart Money Radar tells you which proven winners are buying a coin. Fade Radar is the other half of that question, and on pump.fun it turns out to be the sharper one: how much of a coin's buy side is money that has never been right. A wallet joins the reverse-indicator board only after five coins it bought have a known outcome and not one of them won, which is a bar a surprising number of addresses clear. The new page ranks every launch from the last few hours by how much of its observed buy side belongs to those wallets, by wallet count and by SOL, and carries a second board of the wallets themselves with their full record. The number above the board is the part we care most about: it is measured, not asserted. We rebuild the reverse-indicator group using only coins whose outcome was known before the coins it is graded on existed, then check what actually happened. Coins where a quarter or more of the buyers were reverse indicators went on to win 1.8 percent of the time, against 22.1 percent for coins with none, across 26,626 labelled coins. Nothing here is a short and nothing signs anything: on a bonding curve the only tradeable form of a fade is not buying, so every action on the page is a link out to the coin, its intel, or a wallet's track record. Wallet links also now open directly on the Smart Money Radar, so an address cited anywhere on the platform lands on its record instead of a board you have to scan by eye.",+ "link": "/fade",+ "tags": [+ "feature"+ ]+ },+ {+ "date": "2026-09-09",+ "type": "update",+ "title": "Homes connected through the relay now follow the house when you rearrange it",+ "summary": "If your Home Assistant is only reachable inside your house, three.ws reaches it through the three.ws integration you install there, which dials out to us. Those homes were building their room list once, when the connection opened, and then quietly ignoring changes: assign a lamp to the kitchen, rename a floor, add a device, and the 3D house kept showing the old arrangement until the connection happened to be rebuilt. Homes connected by a direct address never had this problem, and the split was in the relay, which was not carrying the four small notices Home Assistant sends when its rooms, floors, devices or entities change. It carries them now, so both kinds of connection track the house the same way and updates land in seconds. The notices only say that something changed; the relay already read the full room and floor lists, so nothing new about your house is exposed by this.",+ "link": "/smart-home",+ "tags": [+ "fix",+ "infra"+ ]+ },{"date": "2026-09-09","type": "update",@@ -239,6 +312,17 @@"improvement"]},+ {+ "date": "2026-09-09",+ "type": "update",+ "title": "The API container keeps the memory it was sized for, so a busy hour cannot take the whole site down",+ "summary": "Every three.ws page and API call is served by one container, and in early September that container was given twice the memory so it could hold live connections to people’s connected homes without ever running short. The setting did not survive: the next full deploy quietly put it back to the smaller limit, and the site then ran for five days on half the memory it had been sized for while still being configured to hold up to 600 home connections. Measured over the last 24 hours, memory was already peaking at 86% of that smaller limit before a single home connection was counted, which is close enough to the edge that a busy hour could have killed the container mid-request and taken every page down with it, not just the connected-home part. The limit is restored, peak memory is back to 43%, and it is now written into the deploy configuration itself so no future deploy can undo it again.",+ "link": null,+ "tags": [+ "fix",+ "infra"+ ]+ },{"date": "2026-09-09","type": "update",@@ -315,6 +399,17 @@"improvement"]},+ {+ "date": "2026-09-09",+ "type": "update",+ "title": "The OKX marketplace chat bot now switches AI providers by itself",+ "summary": "Chat for our OKX.AI listing runs on an always-on host that spawns an AI session to answer buyers. That host held exactly one AI provider, so when the provider's account was put on a billing hold the bot went on receiving every message and answering none of them, for days, while other credentials sat unused on the same service. It now holds an ordered chain of providers, asks each one whether it will actually serve before using it, and moves to the first that answers. A provider that recovers or gets funded is picked up on the next check with no redeploy, and the bot's status page lists what every provider answered, so whoever fixes it can see which one to fix rather than only that one was refused.",+ "link": null,+ "tags": [+ "infra",+ "improvement"+ ]+ },{"date": "2026-09-09","type": "update",@@ -348,6 +443,16 @@"improvement"]},+ {+ "date": "2026-09-09",+ "type": "update",+ "title": "The partnership page works properly on the partner's own site",+ "summary": "The IBM partnership page is published once onto IBM's own domain and then keeps itself current by reading from three.ws, so everything it loads is a cross-origin read and anything we get wrong there is invisible on three.ws itself. Three things were wrong. The site-wide command palette asked the partner's server for our page index and for the ranking module it imports, so it never opened and logged an error on every visit: the index now travels with the code the way the language catalogs already do, and both files are readable from other sites. And a build step that adds the site's mobile stylesheet to every page was reaching the partner artifacts too, even though they are copied out untouched by design, so the hosted copy asked IBM's server for a stylesheet only we have. All three are closed, and the audit that loads the page from a foreign domain now passes all four of its checks: the live update applies, the language switcher mounts, the paid demo arms, and the console is clean.",+ "link": null,+ "tags": [+ "fix"+ ]+ },{"date": "2026-09-09","type": "update",@@ -480,6 +585,17 @@"infra"]},+ {+ "date": "2026-09-09",+ "type": "update",+ "title": "Three fades now stop when you ask the site to stop moving",+ "summary": "Turn on reduced motion in your operating system and three.ws is supposed to hold still: every animation timing on the site is named rather than spelled out, so one switch can zero all of them at once. Three places had drifted off that and spelled their own timing instead, which meant the object library card fade, the avatar picker chips and the Money Pulse rows kept animating for people who had explicitly asked them not to. One of them was pointing at a timing name that does not exist, so the value it fell back to was never the one anyone chose. All three are back on the named ladder at the same speed they always looked, and the reduced-motion switch reaches them again.",+ "link": "/objects",+ "tags": [+ "fix",+ "improvement"+ ]+ },{"date": "2026-09-09","type": "update",@@ -495,7 +611,7 @@"date": "2026-09-09","type": "update","title": "Your monthly agent turns now count, and locking up never does",- "summary": "Talking to the agent about your house is the one part of the smart-home lane that can really cost money: the room graph makes a home prompt large, and on a paid model a single turn costs more than a year of holding that house’s connection open. Those turns were being counted but never actually limited. They are now, against the monthly allowance shown on your plan page, and if you run out the agent says so in a sentence that names the limit, the date it resets and where to raise it, instead of failing at you. Two things are deliberately left outside that limit. Asking the agent what the house is doing still works, because you have to be able to see which door is open. And telling it to lock a door, close a garage or a valve, or arm the alarm still runs, over quota, on a paused home, in every state we can put an account in: the safe direction is free, always, on every plan. If our own billing lookup fails, the turn is allowed through rather than refused.",+ "summary": "Talking to the agent about your house is the one part of the smart-home lane that can really cost money: the room graph makes a home prompt large, and on a paid model a single turn costs several weeks of holding that house’s connection open. Those turns were being counted but never actually limited. They are now, against the monthly allowance shown on your plan page, and if you run out the agent says so in a sentence that names the limit, the date it resets and where to raise it, instead of failing at you. Two things are deliberately left outside that limit. Asking the agent what the house is doing still works, because you have to be able to see which door is open. And telling it to lock a door, close a garage or a valve, or arm the alarm still runs, over quota, on a paused home, in every state we can put an account in: the safe direction is free, always, on every plan. If our own billing lookup fails, the turn is allowed through rather than refused.","link": "/smart-home/plan","tags": ["feature",@@ -1500,126 +1616,6 @@"tags": ["feature"]- },- {- "date": "2026-09-04",- "type": "update",- "title": "Knock somebody's door and get your money back if they never answer",- "summary": "Paying to reach a stranger has meant paying first and hoping. The money left your wallet the moment the payment cleared, and if the person never replied, that was that. Doors can now take escrowed knocks instead: your payment sits in a vault on Solana that the recipient cannot touch until they actually answer you. If they answer, they are paid. If they decline, you get everything back and are charged nothing, because reading something and passing on it is not a service. And if they simply never respond before the window they set, anyone at all can trigger the refund and every cent comes back to you, so it does not depend on you remembering to chase it. three.ws holds no key that can move that money, and neither does anyone else. Door owners can turn the lane on in their knock settings and choose how long they get to reply, from an hour to a month.",- "link": "/docs/knock",- "tags": [- "feature",- "security"- ]- },- {- "date": "2026-09-04",- "type": "update",- "title": "Opening the homepage, Create and Discover no longer loads 3D you never asked to see",- "summary": "Three pages were doing heavy 3D work before anyone had scrolled to it. The homepage hero picked whichever featured avatar the list returned first, which meant a 4.6 MB model downloading and decoding while the page was still trying to become usable; it now picks the richest avatar that fits a size budget, which cut the hero to 2.1 MB without changing what the stage shows. Discover was fetching an entire 3D viewer engine on every visit even though almost every card in the directory is a still thumbnail, and now fetches it only when a card that really has a 3D model comes near the screen. The Create page did the same for one preview card that already waited for your cursor, and now waits for it too, with the poster on screen in the meantime so the card looks the same. The walking companion also stopped booting on top of a page that is still loading: it waits for the page to settle first, then turns up as before.",- "link": "/discover",- "tags": [- "improvement",- "fix"- ]- },- {- "date": "2026-09-04",- "type": "update",- "title": "Pairing a house, paying an agent and the status page all answer again",- "summary": "A packaging rule left two small token modules out of the deployed image, and because the server loads them the moment a request arrives, every route that touched them answered with a server error instead of a page: pairing or managing a house, the agent payment endpoint, and the public status page. The modules ship again, and the check that simulates the upload now runs as part of every deploy, so a file the server needs can no longer go missing quietly.",- "link": "/status",- "tags": [- "fix",- "infra"- ]- },- {- "date": "2026-09-04",- "type": "update",- "title": "Pin your avatars to IPFS from Settings, and choose which copy loads first",- "summary": "Settings now has an Avatar storage panel. Every avatar you own is listed with its size, its three.ws storage copy, and whether it also lives on IPFS. Pin one and it gets a permanent content address you can open on any public gateway, and a small R2 / IPFS switch decides which copy a viewer resolves first. If a deployment has no pinning provider it says so plainly instead of showing an address that leads nowhere. The About block on the same page now reports the build that is actually serving you and the language the page is really rendering in, rather than today's date and a hardcoded English.",- "link": "/dashboard/settings",- "tags": [- "feature",- "improvement"- ]- },- {- "date": "2026-09-04",- "type": "update",- "title": "Run an escrowed door from your own wallet, and see what the chain actually says",- "summary": "Door settings now carry the escrowed lane: switch it on, choose how long you want to answer within, and open your on-chain door with your own wallet, which is the only thing that can. The panel reads the chain and tells you the truth rather than your intent, so a door you never opened, or one still charging last month's price, says so plainly instead of quietly turning strangers away. Escrowed knocks in your inbox show how long you have and what answering is worth, replying releases the payment, and refusing refunds the sender in full with no fee. Money still in escrow is no longer counted as earned.",- "link": null,- "tags": [- "feature",- "improvement"- ]- },- {- "date": "2026-09-04",- "type": "update",- "title": "The 3D services we sell to other agents quote one clear price, however they are asked",- "summary": "Our four paid 3D generation services on the OKX.AI agent marketplace answer every caller with a price quote before any work happens. Two flaws in that quote are fixed. A request that arrived with no body and no content type was turned away with a formatting complaint instead of a price, and that is exactly how the marketplace's own compatibility check asks, so the check saw four services that looked like they had no payment set up at all. Separately, a request that named no specific tool got a quote listing the same payment network twice at two different prices, one of them wrong. Every unpaid request now receives a single unambiguous quote at the service's listed price, on each payment network it accepts.",- "link": null,- "tags": [- "fix"- ]- },- {- "date": "2026-09-04",- "type": "update",- "title": "The agent answering for us on the OKX.AI marketplace now says when it cannot answer",- "summary": "Our marketplace listing is answered by an agent that reads a buyer's message and writes back. It could fail in the quietest possible way: the process alive, the health page green, and every reply dying against an AI credential the provider had stopped honouring, which from the buyer's side is indistinguishable from being ignored. The host now asks the provider itself, on every boot and every fifteen minutes, and a refused credential turns the listing amber on our status page, raises an alert, and carries the exact commands that fix it. It also stopped crying wolf: a daemon that is merely still starting up no longer reports as dead.",- "link": null,- "tags": [- "fix",- "infra"- ]- },- {- "date": "2026-09-04",- "type": "update",- "title": "The agent economy demo now quotes the amount it actually pays",- "summary": "On the Agent Economy demo, NOVA buys a live Solana market briefing from ORACLE. The narration announced a 0.001 SOL payment while the listed price, the receipt panel and the transfer itself were all 0.000001 SOL, and the screen in the world printed a PAID badge even on the simulated runs that signed-out visitors get. Every one of those now reads the same figure from one place, and a simulated run says so on screen. The page also handles a bad day: if the stream drops, the run times out, or the market feed cannot be reached, you get a plain explanation and a Retry button instead of a stalled page and a pointer at the developer console. On a phone the Run demo button no longer sits off the edge of the screen, the 3D world resizes with the window instead of staying clipped at its widest size, and a browser without WebGL is told so rather than shown a black rectangle.",- "link": "/demo",- "tags": [- "fix",- "improvement"- ]- },- {- "date": "2026-09-04",- "type": "update",- "title": "The agent that answers for us on the OKX.AI marketplace now lives somewhere that stays up",- "summary": "Buyers who message our marketplace listing were being answered from a development workspace that goes to sleep on its own, and one message this week sat unread for twenty hours because of it. It now runs on a host that stays up, keeps its identity across restarts, and reports its own reachability alongside every other part of the platform on the status page.",- "link": null,- "tags": [- "improvement",- "infra"- ]- },- {- "date": "2026-09-04",- "type": "update",- "title": "The DeFi page reads on a phone, links straight to each protocol, and can refresh itself",- "summary": "Every protocol name on /defi is now a real link into its detail page, so you can open one in a new tab, and dragging to copy a TVL figure no longer navigates away. A Refresh button in the toolbar pulls new figures without reloading the page and keeps the current table on screen while it works; if the refresh fails, the numbers you already had stay put and the page says so. On a phone the table now fits the screen, so TVL and the 1-day move are readable without scrolling sideways. When the upstream is down you get a real retry button instead of a dead link, an empty feed says so plainly instead of showing a $0.00 total, and figures served from cache are labelled as cached rather than passed off as live.",- "link": "/defi",- "tags": [- "improvement",- "fix"- ]- },- {- "date": "2026-09-04",- "type": "update",- "title": "The friends panel tells you when it cannot reach the server, instead of saying you have no friends",- "summary": "When the friends list could not be loaded, the panel showed the same screen it shows a brand new player: \"No friends yet\", with a button inviting you to go and add someone. That reads as though your friends were gone, when the truth was only that we could not look. It now says plainly that the connection dropped, that nothing was lost, and offers a Try again button that really does retry, and if the list had already loaded once, it stays on screen and is marked as possibly out of date rather than being thrown away. Coming back online repaints the panel straight away, even when your friends list is exactly as you left it. The panel also had a stray word \"null\" printed under the tabs every time it opened, on both the world and the walk pages, which is now gone.",- "link": "/play",- "tags": [- "fix",- "improvement"- ]}]}diff --git a/public/changelog.json b/public/changelog.jsonindex 8d5c9b2ff..6463e5d73 100644--- a/public/changelog.json+++ b/public/changelog.json@@ -1,11 +1,52 @@{- "generated_at": "2026-09-09T05:54:28.261Z",+ "generated_at": "2026-09-09T07:20:21.658Z","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-09-09",+ "type": "launch",+ "title": "Docs · Fade Radar",+ "summary": "How the Fade Radar scores a coin's buy side: what makes a wallet a reverse indicator, the 0 to 100 fade score, the verdict bands, and the out-of-sample measurement behind them.",+ "link": "/docs/fade-radar",+ "tags": [+ "launch"+ ]+ },+ {+ "date": "2026-09-09",+ "type": "launch",+ "title": "Fade Radar: the wallets that are never right",+ "summary": "The inverse of the Smart Money Radar. Every pump.fun coin ranked by how much of its buy side comes from wallets with a judged on-chain record and not one winner in it, with the measured, out-of-sample odds behind each verdict.",+ "link": "/fade",+ "tags": [+ "launch"+ ]+ },+ {+ "date": "2026-09-09",+ "type": "update",+ "title": "A link that opens your house in 3D now really opens it in 3D",+ "summary": "The live home page remembers whether you last looked at your house in 3D or as a room list, which is what you want when you open it yourself. It was also overruling links that asked for one view by name: once you had used the 2D view even once on a device, every /smart-home/<id>?view=3d link on that device quietly opened flat again. That matters for the two cases the parameter exists for, a link you share with someone in the house and the address a kitchen or wall display is pinned to. A view asked for in the link now wins, for 3D, 2D and the floorplan alike, and following such a link no longer overwrites the preference that device chose for itself.",+ "link": "/docs/home-scene",+ "tags": [+ "fix"+ ]+ },+ {+ "date": "2026-09-09",+ "type": "update",+ "title": "An app key can no longer say yes to unlocking your door",+ "summary": "A person saying yes is the one thing that stands between an agent and your front door, and we found a way around it. If you had ever issued an API key or connected an app to your three.ws account, that key could send an unlock request with the \"the owner already approved this\" flag set, and the lock opened, with nobody asked and nothing to click. We reproduced it against a real house and a real deadbolt before fixing it. Two things changed. Only a signed-in browser session can say yes now: a key or a connected app can ask to unlock, open or disarm, and is always answered with \"a person has to approve this\", exactly as the agent in your chat window already was. And the home permissions you approve when you connect an app are now actually enforced on every home request, so an app you gave read-only access to, or one you never gave home access at all, is refused instead of let through. Nothing legitimate changed: your agent still asks, you still approve, the door still opens.",+ "link": "/smart-home",+ "tags": [+ "security",+ "fix"+ ]+ },{"date": "2026-09-09","type": "update",@@ -27,6 +68,17 @@"fix"]},+ {+ "date": "2026-09-09",+ "type": "update",+ "title": "Connecting a home: the page now says which state it is in, out loud",+ "summary": "Two moments on /smart-home were doing the right thing silently. Typing an address that can never work (a 192.168 number, a .local name) has always put the reason under the field straight away, before anything is sent, but the message was carried by colour alone and a screen reader never read it out; it is now announced the moment it appears, and marked in a way that does not depend on seeing red. And a house that has stopped answering, is refusing the stored token, or has simply gone quiet is now labelled as such by the page itself rather than only in the sentence on its card. Nothing about what you see moves: the last known summary of your house stays exactly where it was, with how long ago it last answered, because a home that went quiet should never look like a home that was deleted.",+ "link": "/smart-home",+ "tags": [+ "improvement",+ "fix"+ ]+ },{"date": "2026-09-09","type": "update",@@ -49,6 +101,27 @@"improvement"]},+ {+ "date": "2026-09-09",+ "type": "update",+ "title": "Fade Radar: the wallets that have never once been right, and the coins they are crowding into",+ "summary": "The Smart Money Radar tells you which proven winners are buying a coin. Fade Radar is the other half of that question, and on pump.fun it turns out to be the sharper one: how much of a coin's buy side is money that has never been right. A wallet joins the reverse-indicator board only after five coins it bought have a known outcome and not one of them won, which is a bar a surprising number of addresses clear. The new page ranks every launch from the last few hours by how much of its observed buy side belongs to those wallets, by wallet count and by SOL, and carries a second board of the wallets themselves with their full record. The number above the board is the part we care most about: it is measured, not asserted. We rebuild the reverse-indicator group using only coins whose outcome was known before the coins it is graded on existed, then check what actually happened. Coins where a quarter or more of the buyers were reverse indicators went on to win 1.8 percent of the time, against 22.1 percent for coins with none, across 26,626 labelled coins. Nothing here is a short and nothing signs anything: on a bonding curve the only tradeable form of a fade is not buying, so every action on the page is a link out to the coin, its intel, or a wallet's track record. Wallet links also now open directly on the Smart Money Radar, so an address cited anywhere on the platform lands on its record instead of a board you have to scan by eye.",+ "link": "/fade",+ "tags": [+ "feature"+ ]+ },+ {+ "date": "2026-09-09",+ "type": "update",+ "title": "Homes connected through the relay now follow the house when you rearrange it",+ "summary": "If your Home Assistant is only reachable inside your house, three.ws reaches it through the three.ws integration you install there, which dials out to us. Those homes were building their room list once, when the connection opened, and then quietly ignoring changes: assign a lamp to the kitchen, rename a floor, add a device, and the 3D house kept showing the old arrangement until the connection happened to be rebuilt. Homes connected by a direct address never had this problem, and the split was in the relay, which was not carrying the four small notices Home Assistant sends when its rooms, floors, devices or entities change. It carries them now, so both kinds of connection track the house the same way and updates land in seconds. The notices only say that something changed; the relay already read the full room and floor lists, so nothing new about your house is exposed by this.",+ "link": "/smart-home",+ "tags": [+ "fix",+ "infra"+ ]+ },{"date": "2026-09-09","type": "update",@@ -236,6 +309,17 @@"improvement"]},+ {+ "date": "2026-09-09",+ "type": "update",+ "title": "The API container keeps the memory it was sized for, so a busy hour cannot take the whole site down",+ "summary": "Every three.ws page and API call is served by one container, and in early September that container was given twice the memory so it could hold live connections to people’s connected homes without ever running short. The setting did not survive: the next full deploy quietly put it back to the smaller limit, and the site then ran for five days on half the memory it had been sized for while still being configured to hold up to 600 home connections. Measured over the last 24 hours, memory was already peaking at 86% of that smaller limit before a single home connection was counted, which is close enough to the edge that a busy hour could have killed the container mid-request and taken every page down with it, not just the connected-home part. The limit is restored, peak memory is back to 43%, and it is now written into the deploy configuration itself so no future deploy can undo it again.",+ "link": null,+ "tags": [+ "fix",+ "infra"+ ]+ },{"date": "2026-09-09","type": "update",@@ -312,6 +396,17 @@"improvement"]},+ {+ "date": "2026-09-09",+ "type": "update",+ "title": "The OKX marketplace chat bot now switches AI providers by itself",+ "summary": "Chat for our OKX.AI listing runs on an always-on host that spawns an AI session to answer buyers. That host held exactly one AI provider, so when the provider's account was put on a billing hold the bot went on receiving every message and answering none of them, for days, while other credentials sat unused on the same service. It now holds an ordered chain of providers, asks each one whether it will actually serve before using it, and moves to the first that answers. A provider that recovers or gets funded is picked up on the next check with no redeploy, and the bot's status page lists what every provider answered, so whoever fixes it can see which one to fix rather than only that one was refused.",+ "link": null,+ "tags": [+ "infra",+ "improvement"+ ]+ },{"date": "2026-09-09","type": "update",@@ -345,6 +440,16 @@"improvement"]},+ {+ "date": "2026-09-09",+ "type": "update",+ "title": "The partnership page works properly on the partner's own site",+ "summary": "The IBM partnership page is published once onto IBM's own domain and then keeps itself current by reading from three.ws, so everything it loads is a cross-origin read and anything we get wrong there is invisible on three.ws itself. Three things were wrong. The site-wide command palette asked the partner's server for our page index and for the ranking module it imports, so it never opened and logged an error on every visit: the index now travels with the code the way the language catalogs already do, and both files are readable from other sites. And a build step that adds the site's mobile stylesheet to every page was reaching the partner artifacts too, even though they are copied out untouched by design, so the hosted copy asked IBM's server for a stylesheet only we have. All three are closed, and the audit that loads the page from a foreign domain now passes all four of its checks: the live update applies, the language switcher mounts, the paid demo arms, and the console is clean.",+ "link": null,+ "tags": [+ "fix"+ ]+ },{"date": "2026-09-09","type": "update",@@ -477,6 +582,17 @@"infra"]},+ {+ "date": "2026-09-09",+ "type": "update",+ "title": "Three fades now stop when you ask the site to stop moving",+ "summary": "Turn on reduced motion in your operating system and three.ws is supposed to hold still: every animation timing on the site is named rather than spelled out, so one switch can zero all of them at once. Three places had drifted off that and spelled their own timing instead, which meant the object library card fade, the avatar picker chips and the Money Pulse rows kept animating for people who had explicitly asked them not to. One of them was pointing at a timing name that does not exist, so the value it fell back to was never the one anyone chose. All three are back on the named ladder at the same speed they always looked, and the reduced-motion switch reaches them again.",+ "link": "/objects",+ "tags": [+ "fix",+ "improvement"+ ]+ },{"date": "2026-09-09","type": "update",@@ -492,7 +608,7 @@"date": "2026-09-09","type": "update","title": "Your monthly agent turns now count, and locking up never does",- "summary": "Talking to the agent about your house is the one part of the smart-home lane that can really cost money: the room graph makes a home prompt large, and on a paid model a single turn costs more than a year of holding that house’s connection open. Those turns were being counted but never actually limited. They are now, against the monthly allowance shown on your plan page, and if you run out the agent says so in a sentence that names the limit, the date it resets and where to raise it, instead of failing at you. Two things are deliberately left outside that limit. Asking the agent what the house is doing still works, because you have to be able to see which door is open. And telling it to lock a door, close a garage or a valve, or arm the alarm still runs, over quota, on a paused home, in every state we can put an account in: the safe direction is free, always, on every plan. If our own billing lookup fails, the turn is allowed through rather than refused.",+ "summary": "Talking to the agent about your house is the one part of the smart-home lane that can really cost money: the room graph makes a home prompt large, and on a paid model a single turn costs several weeks of holding that house’s connection open. Those turns were being counted but never actually limited. They are now, against the monthly allowance shown on your plan page, and if you run out the agent says so in a sentence that names the limit, the date it resets and where to raise it, instead of failing at you. Two things are deliberately left outside that limit. Asking the agent what the house is doing still works, because you have to be able to see which door is open. And telling it to lock a door, close a garage or a valve, or arm the alarm still runs, over quota, on a paused home, in every state we can put an account in: the safe direction is free, always, on every plan. If our own billing lookup fails, the turn is allowed through rather than refused.","link": "/smart-home/plan","tags": ["feature",diff --git a/public/changelog.xml b/public/changelog.xmlindex bcca8f406..616cb834b 100644--- a/public/changelog.xml+++ b/public/changelog.xml@@ -6,6 +6,38 @@<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>Docs · Fade Radar</title>+ <link>https://three.ws/docs/fade-radar</link>+ <guid isPermaLink="false">2026-09-09:Docs · Fade Radar</guid>+ <pubDate>Wed, 09 Sep 2026 12:00:00 GMT</pubDate>+ <category>launch</category>+ <description>How the Fade Radar scores a coin's buy side: what makes a wallet a reverse indicator, the 0 to 100 fade score, the verdict bands, and the out-of-sample measurement behind them.</description>+ </item>+ <item>+ <title>Fade Radar: the wallets that are never right</title>+ <link>https://three.ws/fade</link>+ <guid isPermaLink="false">2026-09-09:Fade Radar: the wallets that are never right</guid>+ <pubDate>Wed, 09 Sep 2026 12:00:00 GMT</pubDate>+ <category>launch</category>+ <description>The inverse of the Smart Money Radar. Every pump.fun coin ranked by how much of its buy side comes from wallets with a judged on-chain record and not one winner in it, with the measured, out-of-sample odds behind each verdict.</description>+ </item>+ <item>+ <title>A link that opens your house in 3D now really opens it in 3D</title>+ <link>https://three.ws/docs/home-scene</link>+ <guid isPermaLink="false">2026-09-09:A link that opens your house in 3D now really opens it in 3D</guid>+ <pubDate>Wed, 09 Sep 2026 12:00:00 GMT</pubDate>+ <category>fix</category>+ <description>The live home page remembers whether you last looked at your house in 3D or as a room list, which is what you want when you open it yourself. It was also overruling links that asked for one view by name: once you had used the 2D view even once on a device, every /smart-home/<id>?view=3d link on that device quietly opened flat again. That matters for the two cases the parameter exists for, a link you share with someone in the house and the address a kitchen or wall display is pinned to. A view asked for in the link now wins, for 3D, 2D and the floorplan alike, and following such a link no longer overwrites the preference that device chose for itself.</description>+ </item>+ <item>+ <title>An app key can no longer say yes to unlocking your door</title>+ <link>https://three.ws/smart-home</link>+ <guid isPermaLink="false">2026-09-09:An app key can no longer say yes to unlocking your door</guid>+ <pubDate>Wed, 09 Sep 2026 12:00:00 GMT</pubDate>+ <category>security</category>+ <description>A person saying yes is the one thing that stands between an agent and your front door, and we found a way around it. If you had ever issued an API key or connected an app to your three.ws account, that key could send an unlock request with the "the owner already approved this" flag set, and the lock opened, with nobody asked and nothing to click. We reproduced it against a real house and a real deadbolt before fixing it. Two things changed. Only a signed-in browser session can say yes now: a key or a connected app can ask to unlock, open or disarm, and is always answered with "a person has to approve this", exactly as the agent in your chat window already was. And the home permissions you approve when you connect an app are now actually enforced on every home request, so an app you gave read-only access to, or one you never gave home access at all, is refused instead of let through. Nothing legitimate changed: your agent still asks, you still approve, the door still opens.</description>+ </item><item><title>Arm your agent stops telling signed-out visitors to create an agent, and shows them the live conviction stream instead</title><link>https://three.ws/oracle/arm</link>@@ -22,6 +54,14 @@<category>fix</category><description>Assets served from /cdn (avatars, thumbnails, generated models) are read from our object store with a signed request, and when that request is rejected the route falls back to the store's public address so the bytes still arrive. That fallback was a redirect, and a redirect throws away the cross-origin permission the route grants: browsers re-check permission at the redirect's destination, and the public address grants none. Measured from an outside site, every one of those reads failed outright, which took down model previews on pages that load art through the proxy and silently broke third-party embeds of three.ws avatars. The bytes are now served through three.ws itself rather than pointed at, so the permission, the file type and the download rules all survive the fallback, partial reads for video and audio keep working, and a file that genuinely is not there says so instead of reporting a server fault the page retries forever. It also keeps the fallback off the rate-limited public address, which is the whole reason the proxy exists.</description></item>+ <item>+ <title>Connecting a home: the page now says which state it is in, out loud</title>+ <link>https://three.ws/smart-home</link>+ <guid isPermaLink="false">2026-09-09:Connecting a home: the page now says which state it is in, out loud</guid>+ <pubDate>Wed, 09 Sep 2026 12:00:00 GMT</pubDate>+ <category>improvement</category>+ <description>Two moments on /smart-home were doing the right thing silently. Typing an address that can never work (a 192.168 number, a .local name) has always put the reason under the field straight away, before anything is sent, but the message was carried by colour alone and a screen reader never read it out; it is now announced the moment it appears, and marked in a way that does not depend on seeing red. And a house that has stopped answering, is refusing the stored token, or has simply gone quiet is now labelled as such by the page itself rather than only in the sentence on its card. Nothing about what you see moves: the last known summary of your house stays exactly where it was, with how long ago it last answered, because a home that went quiet should never look like a home that was deleted.</description>+ </item><item><title>Endpoint Shopper fits a phone, and says something useful when a run finds nothing to buy</title><link>https://three.ws/shopper</link>@@ -38,6 +78,22 @@<category>fix</category><description>A full audit of /portfolio, where you paste any Solana or Ethereum address and get a live portfolio. The Ethereum half had gone dark: the single provider behind it ran out of monthly capacity, so every 0x address answered "Data source unavailable" with nothing behind it. Ethereum now has the same keyless floor Solana has always had. The ETH balance comes from the public Ethereum nodes the rest of the platform already uses, the token list with its prices and icons comes from a public block explorer, and the 24h move comes from the same market source the Solana side uses, with the coverage it achieved stated on the card. The Data panel names whichever lane actually answered, so you can see whether you are reading the paid provider or the free one. Token logos were another visible break: the page pointed your browser straight at an IPFS gateway, which the browser refuses on cross-origin grounds, so every holding fell back to a three-letter monogram and your address bar handed your IP to the gateway on every load. Logos now come through three.ws, sized for the row. Keyboard users could tab onto a slice of the allocation donut and get nothing: the tooltip was wired to an event handler property that browsers do not actually support, so it never fired once; the slice now names its asset and share, and Escape dismisses it. When a lookup fails, the page now shows the reason the server actually sent instead of a generic sentence, and clicking Retry after a rejected address no longer silently reloads the wallet you looked at before it. Underneath, the fallback that names Solana tokens when the primary metadata source is out of quota had never run at all, because of a missing import; token symbols and names come back on that path.</description></item>+ <item>+ <title>Fade Radar: the wallets that have never once been right, and the coins they are crowding into</title>+ <link>https://three.ws/fade</link>+ <guid isPermaLink="false">2026-09-09:Fade Radar: the wallets that have never once been right, and the coins they are crowding into</guid>+ <pubDate>Wed, 09 Sep 2026 12:00:00 GMT</pubDate>+ <category>feature</category>+ <description>The Smart Money Radar tells you which proven winners are buying a coin. Fade Radar is the other half of that question, and on pump.fun it turns out to be the sharper one: how much of a coin's buy side is money that has never been right. A wallet joins the reverse-indicator board only after five coins it bought have a known outcome and not one of them won, which is a bar a surprising number of addresses clear. The new page ranks every launch from the last few hours by how much of its observed buy side belongs to those wallets, by wallet count and by SOL, and carries a second board of the wallets themselves with their full record. The number above the board is the part we care most about: it is measured, not asserted. We rebuild the reverse-indicator group using only coins whose outcome was known before the coins it is graded on existed, then check what actually happened. Coins where a quarter or more of the buyers were reverse indicators went on to win 1.8 percent of the time, against 22.1 percent for coins with none, across 26,626 labelled coins. Nothing here is a short and nothing signs anything: on a bonding curve the only tradeable form of a fade is not buying, so every action on the page is a link out to the coin, its intel, or a wallet's track record. Wallet links also now open directly on the Smart Money Radar, so an address cited anywhere on the platform lands on its record instead of a board you have to scan by eye.</description>+ </item>+ <item>+ <title>Homes connected through the relay now follow the house when you rearrange it</title>+ <link>https://three.ws/smart-home</link>+ <guid isPermaLink="false">2026-09-09:Homes connected through the relay now follow the house when you rearrange it</guid>+ <pubDate>Wed, 09 Sep 2026 12:00:00 GMT</pubDate>+ <category>fix</category>+ <description>If your Home Assistant is only reachable inside your house, three.ws reaches it through the three.ws integration you install there, which dials out to us. Those homes were building their room list once, when the connection opened, and then quietly ignoring changes: assign a lamp to the kitchen, rename a floor, add a device, and the 3D house kept showing the old arrangement until the connection happened to be rebuilt. Homes connected by a direct address never had this problem, and the split was in the relay, which was not carrying the four small notices Home Assistant sends when its rooms, floors, devices or entities change. It carries them now, so both kinds of connection track the house the same way and updates land in seconds. The notices only say that something changed; the relay already read the full room and floor lists, so nothing new about your house is exposed by this.</description>+ </item><item><title>Oracle: a failed request now says so, instead of claiming no coins have been scored</title><link>https://three.ws/oracle</link>@@ -174,6 +230,14 @@<category>fix</category><description>A full audit of /pose, where you pose an avatar and keyframe an animation. The page had no top-level heading at all: assistive technology jumped straight into "Selection" with nothing saying which studio you were in, so "Animation Studio" in the breadcrumb is now the page's real heading. The status pill above the canvas is the studio's only error surface (it is what tells you an import failed, an avatar could not be loaded, or that you need a keyframe before saving) and it never announced anything; it is now a live region, so those messages are spoken as they appear. On a 320px screen the empty-timeline hint ("Pose the figure, then press K") wrapped across the ruler's second markings and both became unreadable; the ruler now stays out of the way until you have keyframes to measure, and returns the moment you add one. Loading an avatar could also fail into a dead end: the picker said "Failed to load: Failed to fetch" with no way forward, and now explains whether the request reached three.ws and offers a Try again button. Behind that, a slow first CDN could make the 3D preview library load twice and throw an error into the console; a second load is now ignored.</description></item>+ <item>+ <title>The API container keeps the memory it was sized for, so a busy hour cannot take the whole site down</title>+ <link>https://three.ws/changelog</link>+ <guid isPermaLink="false">2026-09-09:The API container keeps the memory it was sized for, so a busy hour cannot take the whole site down</guid>+ <pubDate>Wed, 09 Sep 2026 12:00:00 GMT</pubDate>+ <category>fix</category>+ <description>Every three.ws page and API call is served by one container, and in early September that container was given twice the memory so it could hold live connections to people’s connected homes without ever running short. The setting did not survive: the next full deploy quietly put it back to the smaller limit, and the site then ran for five days on half the memory it had been sized for while still being configured to hold up to 600 home connections. Measured over the last 24 hours, memory was already peaking at 86% of that smaller limit before a single home connection was counted, which is close enough to the edge that a busy hour could have killed the container mid-request and taken every page down with it, not just the connected-home part. The limit is restored, peak memory is back to 43%, and it is now written into the deploy configuration itself so no future deploy can undo it again.</description>+ </item><item><title>The Coin Wars arena reconnects to its battle server, and a link with no battle now shows you where the wars are</title><link>https://three.ws/play/war</link>@@ -230,6 +294,14 @@<category>fix</category><description>A full audit of /objects, the public-domain prop library. The page had been showing "Object library coming online" to everyone: the 511 props were sitting on the CDN the whole time, but the server read their index over a signed storage connection whose credential had stopped matching, so every visitor got an empty shelf. The index is public data on a public domain, so the read now falls back to that domain when the signed one fails, and the same change refills the character library, the animation clips and the asset catalogue the agent tools search. Browsing is a different page too. It used to build all 511 cards at once, each one a live 3D viewer with its own model, which meant 511 image requests before the first card appeared and about eighteen seconds of nothing. Now it renders 48 at a time, with a Load more button and automatic loading as you scroll, and a card stays a still picture until you rest the pointer on it, at which point that one spins up in 3D; a handful stay live at a time instead of hundreds. The filter row dropped eight chips that were Poly Haven collection names rather than anything you would browse by. On a phone the Preview, AR and Download buttons each get a full-width row instead of three cramped pills. Keyboard focus is now visible on every control, a failed load names the actual reason above its retry button, and the page description no longer contradicts the one in the markup.</description></item>+ <item>+ <title>The OKX marketplace chat bot now switches AI providers by itself</title>+ <link>https://three.ws/changelog</link>+ <guid isPermaLink="false">2026-09-09:The OKX marketplace chat bot now switches AI providers by itself</guid>+ <pubDate>Wed, 09 Sep 2026 12:00:00 GMT</pubDate>+ <category>infra</category>+ <description>Chat for our OKX.AI listing runs on an always-on host that spawns an AI session to answer buyers. That host held exactly one AI provider, so when the provider's account was put on a billing hold the bot went on receiving every message and answering none of them, for days, while other credentials sat unused on the same service. It now holds an ordered chain of providers, asks each one whether it will actually serve before using it, and moves to the first that answers. A provider that recovers or gets funded is picked up on the next check with no redeploy, and the bot's status page lists what every provider answered, so whoever fixes it can see which one to fix rather than only that one was refused.</description>+ </item><item><title>The OpenAI partner page now proves the free ChatGPT connector is up instead of just claiming it</title><link>https://three.ws/openai</link>@@ -254,6 +326,14 @@<category>fix</category><description>An end-to-end audit of /partners found it was the only page on the site that carried a footer slot but never loaded the footer, so the whole bottom of the page was missing. It is back. On a 320px phone the partner cards were 38px wider than the screen and the overhanging text was silently cut off, because a card header could not shrink past its logo, name and category chip on one line; the chip now wraps and every card fits. The page description search engines and link previews read was also stale: it advertised Intel, Microsoft and Oracle, none of which have a card, and left out OpenAI and HackerNoon, which do. The AWS card said View on AWS Marketplace above a link to our own AWS page, so it now says what it actually opens. Beyond that: the 8 partners and 22 chains counters are no longer hidden from screen readers and the partner number is now counted from the cards themselves, keyboard users get a visible ring on every card and button, the card lift is dropped for anyone who asks for reduced motion, and the page eyebrow, the four benefit headings and every card call to action are translatable instead of staying English on a translated page. The floating walk companion also got a full-size dismiss, avatar-swap and narration button on touch devices, everywhere it appears.</description></item>+ <item>+ <title>The partnership page works properly on the partner's own site</title>+ <link>https://three.ws/changelog</link>+ <guid isPermaLink="false">2026-09-09:The partnership page works properly on the partner's own site</guid>+ <pubDate>Wed, 09 Sep 2026 12:00:00 GMT</pubDate>+ <category>fix</category>+ <description>The IBM partnership page is published once onto IBM's own domain and then keeps itself current by reading from three.ws, so everything it loads is a cross-origin read and anything we get wrong there is invisible on three.ws itself. Three things were wrong. The site-wide command palette asked the partner's server for our page index and for the ranking module it imports, so it never opened and logged an error on every visit: the index now travels with the code the way the language catalogs already do, and both files are readable from other sites. And a build step that adds the site's mobile stylesheet to every page was reaching the partner artifacts too, even though they are copied out untouched by design, so the hosted copy asked IBM's server for a stylesheet only we have. All three are closed, and the audit that loads the page from a foreign domain now passes all four of its checks: the live update applies, the language switcher mounts, the paid demo arms, and the console is clean.</description>+ </item><item><title>The pitch deck now shows the whole character, and says so when the 3D cannot load</title><link>https://three.ws/pitch</link>@@ -350,6 +430,14 @@<category>fix</category><description>The Agent glance widget on the Windows 11 widgets board renders an Adaptive Card, and the board fills that card in with its own expression engine rather than with JavaScript. Our card asked for the three stat rows the way JavaScript reads an array, which that engine treats as a syntax error, and it refuses the whole card rather than skipping the one line: a pinned widget came up empty with nothing to show for it anywhere else. The card now uses the syntax the board expects, and there is a new check that fills it in with the board's own engine before anything ships, alongside checks that the manifest, the service worker and the two endpoints still agree with each other. The board is the one surface we cannot open from a build machine, so the checks that stand in for it are the ones that have to be real.</description></item>+ <item>+ <title>Three fades now stop when you ask the site to stop moving</title>+ <link>https://three.ws/objects</link>+ <guid isPermaLink="false">2026-09-09:Three fades now stop when you ask the site to stop moving</guid>+ <pubDate>Wed, 09 Sep 2026 12:00:00 GMT</pubDate>+ <category>fix</category>+ <description>Turn on reduced motion in your operating system and three.ws is supposed to hold still: every animation timing on the site is named rather than spelled out, so one switch can zero all of them at once. Three places had drifted off that and spelled their own timing instead, which meant the object library card fade, the avatar picker chips and the Money Pulse rows kept animating for people who had explicitly asked them not to. One of them was pointing at a timing name that does not exist, so the value it fell back to was never the one anyone chose. All three are back on the named ladder at the same speed they always looked, and the reduced-motion switch reaches them again.</description>+ </item><item><title>When the payment wallets look empty, the self-heal now says whether they are empty or just fenced</title><link>https://three.ws/changelog</link>@@ -364,7 +452,7 @@<guid isPermaLink="false">2026-09-09:Your monthly agent turns now count, and locking up never does</guid><pubDate>Wed, 09 Sep 2026 12:00:00 GMT</pubDate><category>feature</category>- <description>Talking to the agent about your house is the one part of the smart-home lane that can really cost money: the room graph makes a home prompt large, and on a paid model a single turn costs more than a year of holding that house’s connection open. Those turns were being counted but never actually limited. They are now, against the monthly allowance shown on your plan page, and if you run out the agent says so in a sentence that names the limit, the date it resets and where to raise it, instead of failing at you. Two things are deliberately left outside that limit. Asking the agent what the house is doing still works, because you have to be able to see which door is open. And telling it to lock a door, close a garage or a valve, or arm the alarm still runs, over quota, on a paused home, in every state we can put an account in: the safe direction is free, always, on every plan. If our own billing lookup fails, the turn is allowed through rather than refused.</description>+ <description>Talking to the agent about your house is the one part of the smart-home lane that can really cost money: the room graph makes a home prompt large, and on a paid model a single turn costs several weeks of holding that house’s connection open. Those turns were being counted but never actually limited. They are now, against the monthly allowance shown on your plan page, and if you run out the agent says so in a sentence that names the limit, the date it resets and where to raise it, instead of failing at you. Two things are deliberately left outside that limit. Asking the agent what the house is doing still works, because you have to be able to see which door is open. And telling it to lock a door, close a garage or a valve, or arm the alarm still runs, over quota, on a paused home, in every state we can put an account in: the safe direction is free, always, on every plan. If our own billing lookup fails, the turn is allowed through rather than refused.</description></item><item><title>Your private avatars load on the dashboard again, and say so when they cannot</title>diff --git a/public/features.json b/public/features.jsonindex ffec9c742..bcb047905 100644--- a/public/features.json+++ b/public/features.json@@ -1,5 +1,5 @@{- "generated_at": "2026-09-09T05:43:06.184Z",+ "generated_at": "2026-09-09T07:20:21.637Z","generated_by": "scripts/build-page-index.mjs from data/pages.json","site": {"name": "three.ws",@@ -2167,6 +2167,16 @@"tags": [],"showcase": false},+ {+ "path": "/fade",+ "title": "Fade Radar: the wallets that are never right",+ "description": "The inverse of the Smart Money Radar. Every pump.fun coin ranked by how much of its buy side comes from wallets with a judged on-chain record and not one winner in it, with the measured, out-of-sample odds behind each verdict.",+ "added": "2026-09-09",+ "auth": null,+ "indexable": true,+ "tags": [],+ "showcase": false+ },{"path": "/pumpfun","title": "Pump.fun Stream",@@ -4178,6 +4188,16 @@"tags": [],"showcase": false},+ {+ "path": "/docs/fade-radar",+ "title": "Docs · Fade Radar",+ "description": "How the Fade Radar scores a coin's buy side: what makes a wallet a reverse indicator, the 0 to 100 fade score, the verdict bands, and the out-of-sample measurement behind them.",+ "added": "2026-09-09",+ "auth": null,+ "indexable": true,+ "tags": [],+ "showcase": false+ },{"path": "/docs/radar","title": "Docs · Coin Radar",diff --git a/public/llms-full.txt b/public/llms-full.txtindex 498ce14fa..e178db91c 100644--- a/public/llms-full.txt+++ b/public/llms-full.txt@@ -1326,6 +1326,12 @@ URL: https://three.ws/smart-moneyA live first-party reputation graph of every pump.fun wallet. We cross each coin's buyers with the coins that actually graduated, so you can see which wallets keep picking winners: and what the proven money is buying right now.+### Fade Radar: the wallets that are never right++URL: https://three.ws/fade++The inverse of the Smart Money Radar. Every pump.fun coin ranked by how much of its buy side comes from wallets with a judged on-chain record and not one winner in it, with the measured, out-of-sample odds behind each verdict.+### Pump.fun StreamURL: https://three.ws/pumpfun@@ -2554,6 +2560,12 @@ URL: https://three.ws/docs/smart-moneyA live first-party reputation graph of every pump.fun wallet: cross each coin's buyers with the coins that actually graduated to surface the wallets that keep picking winners.+### Docs · Fade Radar++URL: https://three.ws/docs/fade-radar++How the Fade Radar scores a coin's buy side: what makes a wallet a reverse indicator, the 0 to 100 fade score, the verdict bands, and the out-of-sample measurement behind them.+### Docs · Coin RadarURL: https://three.ws/docs/radardiff --git a/public/llms.txt b/public/llms.txtindex 410fe8dc7..e0fb05212 100644--- a/public/llms.txt+++ b/public/llms.txt@@ -240,6 +240,7 @@ On-chain features: pay-per-call, token launches, vanity wallets.- [Sniper Experiments: rules vs LLM judgment, scored live](https://three.ws/sniper/experiments): The sniper fleet runs different rule sets side by side, including LLM-judged agents with no rules at all. The live scoreboard of which entry conditions actually make money, every fill verifiable on-chain.- [Flappin UFO: retired demo](https://three.ws/play/ufo): The Flappin UFO arcade demo ran on an external deployment that is no longer online, so the game has been retired. The page now points visitors to the live three.ws experiences instead.- [Smart Money Radar: follow the wallets that win on pump.fun](https://three.ws/smart-money): A live first-party reputation graph of every pump.fun wallet. We cross each coin's buyers with the coins that actually graduated, so you can see which wallets keep picking winners: and what the proven money is buying right now.+- [Fade Radar: the wallets that are never right](https://three.ws/fade): The inverse of the Smart Money Radar. Every pump.fun coin ranked by how much of its buy side comes from wallets with a judged on-chain record and not one winner in it, with the measured, out-of-sample odds behind each verdict.- [Pump.fun Stream](https://three.ws/pumpfun): Mint and trade pump.fun agent tokens on Solana. Live feed of every launch.- [Pump Live](https://three.ws/pump-live): Real-time feed of every pump.fun launch as it happens, with a 3D agent that reacts live.- [Mission Control](https://three.ws/terminal): The real-time pump.fun trading terminal: the live launch firehose fused with intel scores, firewall verdicts, and smart-money flow, your streaming positions with live PnL, and one-keystroke firewall + MEV-gated trading from your agent wallet. A keyboard-driven cockpit with filters and saved views.@@ -441,6 +442,7 @@ Docs, tutorials, and reference.- [Docs · Strategy Objects](https://three.ws/docs/strategy-objects): Ownable, forkable, leaderboard-ranked trade strategies your agent can equip and run on-chain within your spend policy, plus the Strategy Lab for validation and backtesting.- [Docs · Mission Control](https://three.ws/docs/terminal): The keyboard-first pump.fun trading terminal: the launch firehose fused with intel scores, firewall verdicts, and smart-money flow, streaming positions with live PnL, and one-keystroke guarded trading.- [Docs · Smart Money Radar](https://three.ws/docs/smart-money): A live first-party reputation graph of every pump.fun wallet: cross each coin's buyers with the coins that actually graduated to surface the wallets that keep picking winners.+- [Docs · Fade Radar](https://three.ws/docs/fade-radar): How the Fade Radar scores a coin's buy side: what makes a wallet a reverse indicator, the 0 to 100 fade score, the verdict bands, and the out-of-sample measurement behind them.- [Docs · Coin Radar](https://three.ws/docs/radar): Live pump.fun launch intelligence: every new coin scored in its first 90 seconds for bundle vs organic, wallet concentration, dev behaviour, and risk flags.- [Docs · Coin Clash](https://three.ws/docs/clash): Token-gated community warfare: every coin community is an army. Hold the coin, enlist, and rally for your faction in timed on-chain battles.- [Docs · x402 Studio](https://three.ws/docs/x402-studio): The merchant console for running a paid x402 business: products and pricing, payout and agent wallets, real USDC send and receive with .sol resolution, a storefront and pay-button builder, giving, and security.diff --git a/public/sitemap/index.html b/public/sitemap/index.htmlindex 0dfc618a9..1acc2e031 100644--- a/public/sitemap/index.html+++ b/public/sitemap/index.html@@ -96,7 +96,7 @@<main class="sm-wrap"><div class="sm-hero"><h1>Sitemap</h1>- <p>All 924 pages on three.ws, grouped by purpose. Looking for the machine-readable versions?</p>+ <p>All 926 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>@@ -108,7 +108,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 924 pages by name, path, or description…" aria-label="Filter pages" autocomplete="off" spellcheck="false" />+ <input id="sm-filter-input" type="search" placeholder="Filter 926 pages by name, path, or description…" aria-label="Filter pages" autocomplete="off" spellcheck="false" /><kbd id="sm-filter-kbd" aria-hidden="true">/</kbd></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>@@ -116,6 +116,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="/fade">+ <span class="sm-new-date">Sep 9, 2026</span>+ <span class="sm-title">Fade Radar: the wallets that are never right</span>+ <span class="sm-path">/fade</span>+ <span class="sm-desc">The inverse of the Smart Money Radar. Every pump.fun coin ranked by how much of its buy side comes from wallets with a judged on-chain record and not one winner in it, with the measured, out-of-sample odds behind each verdict.</span>+ </a>+ </li>+ <li>+ <a href="/docs/fade-radar">+ <span class="sm-new-date">Sep 9, 2026</span>+ <span class="sm-title">Docs · Fade Radar</span>+ <span class="sm-path">/docs/fade-radar</span>+ <span class="sm-desc">How the Fade Radar scores a coin's buy side: what makes a wallet a reverse indicator, the 0 to 100 fade score, the verdict bands, and the out-of-sample measurement behind them.</span>+ </a>+ </li><li><a href="/globe"><span class="sm-new-date">Sep 8, 2026</span>@@ -172,22 +188,6 @@<span class="sm-desc">How a JavaScript site is served to search engines: the four server-side render paths, the contract that keeps a page and its sitemap entry agreeing, and how to audit the live origin.</span></a></li>- <li>- <a href="/awesome">- <span class="sm-new-date">Sep 7, 2026</span>- <span class="sm-title">Awesome 3D Agents</span>- <span class="sm-path">/awesome</span>- <span class="sm-desc">A curated, link-checked list of everything you need to give an AI agent a body: text-to-3D models, capture and Gaussian splatting, avatars, rigging, motion generation, lipsync and voice, web renderers, asset pipelines, and the agent frameworks that drive them. Searchable and filterable, and published as an awesome list on GitHub.</span>- </a>- </li>- <li>- <a href="/irl/sign">- <span class="sm-new-date">Sep 5, 2026</span>- <span class="sm-title">Printable IRL sign</span>- <span class="sm-path">/irl/sign</span>- <span class="sm-desc">Print a sign for a placed IRL agent: its name, thumbnail and a QR of the visit link. Scan it at the spot to open IRL, walk up, and meet the 3D AI agent in AR. Carries no coordinate.</span>- </a>- </li></ul></section><nav class="sm-toc" aria-label="Sections">@@ -1359,7 +1359,7 @@<section class="sm-section" id="crypto"><header>- <h2>Crypto<span class="sm-count" data-count>143</span></h2>+ <h2>Crypto<span class="sm-count" data-count>144</span></h2><p class="sm-section-desc">On-chain features: pay-per-call, token launches, vanity wallets.</p></header><ul class="sm-list">@@ -1727,6 +1727,13 @@<span class="sm-desc">A live first-party reputation graph of every pump.fun wallet. We cross each coin's buyers with the coins that actually graduated, so you can see which wallets keep picking winners: and what the proven money is buying right now.</span></a></li>+ <li>+ <a href="/fade">+ <span class="sm-title">Fade Radar: the wallets that are never right</span>+ <span class="sm-path">/fade</span>+ <span class="sm-desc">The inverse of the Smart Money Radar. Every pump.fun coin ranked by how much of its buy side comes from wallets with a judged on-chain record and not one winner in it, with the measured, out-of-sample odds behind each verdict.</span>+ </a>+ </li><li><a href="/pumpfun"><span class="sm-title">Pump.fun Stream</span>@@ -2548,7 +2555,7 @@<section class="sm-section" id="learn"><header>- <h2>Learn<span class="sm-count" data-count>425</span></h2>+ <h2>Learn<span class="sm-count" data-count>426</span></h2><p class="sm-section-desc">Docs, tutorials, and reference.</p></header><ul class="sm-list">@@ -3147,6 +3154,13 @@<span class="sm-desc">A live first-party reputation graph of every pump.fun wallet: cross each coin's buyers with the coins that actually graduated to surface the wallets that keep picking winners.</span></a></li>+ <li>+ <a href="/docs/fade-radar">+ <span class="sm-title">Docs · Fade Radar</span>+ <span class="sm-path">/docs/fade-radar</span>+ <span class="sm-desc">How the Fade Radar scores a coin's buy side: what makes a wallet a reverse indicator, the 0 to 100 fade score, the verdict bands, and the out-of-sample measurement behind them.</span>+ </a>+ </li><li><a href="/docs/radar"><span class="sm-title">Docs · Coin Radar</span>