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(examples): point the doc pages at the examples repo and fail the export on a dead reference
nirholas2ae697f684a2
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex 366ba4958..2baf0ad6e 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -7,6 +7,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr## 2026-09-03- **Docs · Connect a home that is only on your network** (`/docs/home-relay`): 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 code, and nothing listens on your network, no port is forwarded, and three.ws never receives a Home Assistant token. Includes the operator half: the relay service, its configuration and deploy, how the allowlist is changed, and how to prove the whole path against a real house on a network the server cannot route to.+- **Docs · Give your voice assistant a face** (`/docs/home-satellite`): 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 never does, the eleven states the display can be in, and the rule the whole thing is built around, that closing the page never stops your voice assistant working.- **Docs · Home households and roles** (`/docs/home-households`): 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 see, how invitations are issued and accepted, what happens to somebody's access when they leave, and the rule everything hangs off, that a guest can never confirm an action that opens a building.- **Docs · Home plans and quotas** (`/docs/home-plans`): 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 action, so locking up, closing a garage or valve and arming an alarm work over quota and past due; and nothing about the confirmation gate, the action log's integrity or the role system is ever a paid feature.- **Docs · Home privacy and retention** (`/docs/home-privacy`): 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 are never persisted, the 90-day action-log window and the control that changes it, the export and deletion paths, the logging rules, and the disclosure text shown at connect and at the voice opt-in.@@ -23,20 +24,24 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr- **Voice satellite** (`/smart-home/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 answers and reacts, on any screen in the house. Home Assistant keeps the wake word, the speech recognition and the answer; closing the page never stops the voice working.- **Your home data** (`/smart-home/privacy`): 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 entries go, download all of it as JSON, or delete one home or every trace of all of them. Room names, device states and voice audio are never stored at all.- **A stranger cannot make your agent open your front door**: The home lane now has a written threat model and eleven security checks that run with every build, and the standard they hold is a lock, not a database row. The big fix: the address you give for your house is now resolved and pinned on our side before anything dials it, so a web address that secretly points back into our own network is refused instead of connected to, and it is re-checked every time your house reconnects rather than trusted from the day you added it. A device or integration in your house cannot talk your agent into anything either: we wrote an unlock instruction into a real room name, a real device name and a real scene name, ran a real agent against that house, and the front door stayed locked. Your privacy page is now rate limited like everything else, so nobody can hammer the export or the delete. (`/smart-home`) `[security, improvement]`+- **Agent avatars on the Pay page load instead of 404ing**: Every agent card on the x402 Pay page asked for its owner's avatar picture at a URL that has never existed on this site, so the picture always 404'd and the card fell back to a plain letter tile. The page now uses the real thumbnail the rest of three.ws uses, so an agent with a public avatar shows its face on the card, and an agent whose avatar is private still gets the letter tile without a wasted failed request. (`/pay`) `[fix]`- **Any assistant can now run your house, and it still will not open your door**: There is a new way to connect your home that needs no three.ws account and no remote web address at all: install @three-ws/home-mcp in Claude, Cursor, or anything else that speaks Model Context Protocol, give it your Home Assistant address and a token, and it reads your rooms, runs the scenes you already built, and calls services. Because it runs on your own machine, your ordinary home network address works and nothing about your house leaves the building. The safety rule is the same one the rest of the platform uses, applied honestly to this setup: locking up, closing the garage and arming the alarm run straight away and never ask. Unlocking, opening a door and disarming are refused outright, every time, because saying yes to opening a building takes a person and this kind of connection has no person in it to ask. If you genuinely want one specific door handled without asking, you name that exact door yourself when you start it, by hand, and nothing your assistant can do will widen that to any other door. We proved it against a real Home Assistant rather than a stand-in: the front door was told to unlock seven different ways, including with a fake confirmation smuggled into the request, and it stayed locked every time. Alongside it there is now a full walkthrough from nothing to a working agent in a real house, covering what to do when it says your home is unreachable, and what a guest in your household can and cannot do. (`/smart-home`) `[feature, sdk, docs]`- **Coin Radar tells you when it is your filter, not the market, that is empty**: Search the radar for a ticker it has not seen and the board used to say "Radar is clear, waiting for the next launch", which blamed a quiet market for a filter you set and gave you no way back. Most of Radar's filters run on the server, so an over-tight one came back looking exactly like a quiet window. Now the board reads your filters instead of the response: it says no coins match, lists every filter you have on as a chip you can click to drop just that one, and keeps a reset-everything button next to it. The 24-hour pulse strip across the top also got an honest state of its own. It is a separate request from the live feed, and when it failed it used to shimmer as if still loading forever; now it says the aggregate did not load, offers a retry, and leaves the feed below running. On a 320px phone every card was losing about 19 pixels off its right edge to a layout overflow that the mobile scroll guard was quietly clipping; cards now fit the screen they are on. (`/radar`) `[fix, improvement]`- **Connect a home that only exists on your own network**: Most Home Assistant installs sit on a home network with nothing exposed to the internet, so until now three.ws had no way to reach them. Now the house connects to us instead. Install one integration through HACS, paste a ten-minute pairing code, and your agent can see your rooms and run your scenes with nothing listening on your network, no port forwarded, and no firewall rule changed. The part worth saying plainly: three.ws never receives a Home Assistant token for a home connected this way. The integration signs in to Home Assistant on your own machine with a credential it makes for itself and never sends anywhere, so there is nothing stored here that would open your house. What we can do through that connection is a fixed list, enforced twice, once by us and once by the integration on your machine: reads, your room layout, and device controls. It can never run code on the machine Home Assistant lives on, restart or reconfigure your instance, or reach anything else on your network. Unlocking, opening and disarming still stop and ask a person first, every time, exactly as they do for a home connected by address. Disconnecting works from either end and takes effect immediately. There is an honest threat model in the docs, including what a compromise of three.ws would mean for a connected house; read it before you decide. (`/docs/home-relay`) `[feature, security]`- **Connect your house to your agent, and see every way it can go wrong**: The /smart-home page now takes you from "I have a Home Assistant somewhere" to a connected house, and it is honest at every step. An address that only exists on your home network is refused the moment you type it, with the two real ways round it, instead of spinning for fifteen seconds. A rejected token says so and puts the cursor back in the token box. A house that stops answering keeps its rooms on screen, marked stale with how long ago it last replied, rather than blanking out. Your access token is sent once, encrypted at rest, and never comes back to the page: it is not in your browser storage, not in a URL, and not in any response. Disconnecting says plainly that the stored token is erased and reminds you to delete it in Home Assistant too. (`/smart-home`) `[feature]`- **Endpoint Shopper takes payment on the page, so a paid run actually runs**: Paying for an Endpoint Shopper run used to send you to the generic payment page, which arrived with no price and no wallet options because it could not read the challenge this route sends. Even if it had, it would have replayed the run as an empty request: your task and budget were left behind on the previous page, so a completed payment unlocked nothing. Payment now happens on /shopper itself. The card quotes the real price, lists the Base and Solana wallets the endpoint accepts, reports connecting, signing and settling as they happen, and replays the exact task and budget you typed, so the answer and its cost breakdown appear right where you were, with a link to the settlement transaction. The example task chips are now real buttons you can reach with the keyboard, the task box and budget slider carry proper labels, and the Marketplace and Fact Checker links no longer vanish from the header on a phone. (`/shopper`) `[fix, improvement]`+- **Every SDK doc now points at code you can actually run**: Eight developer docs pages described a capability without ever showing you a working project that uses it, so finding the runnable version meant guessing at folder names on GitHub. The SDK, MCP, embedding, authentication, create-an-agent, Solana, agent-payments and agent-wallets pages now each end with a Runnable example section linking straight to the project that backs them: a browser demo, a Node script that drives the free MCP server end to end, nine single-file HTML embeds you can open with no build step, the full wallet sign-in round trip, and a complete agent defined entirely as files. The machine-readable index that AI agents read to navigate the site now carries the examples location too, so an agent asked to build against three.ws can fetch working code instead of inferring it from prose. Every one of those examples is installed, run and link-checked before release, so a link on a docs page never points at something broken. (`/docs/sdk`) `[docs, improvement]`- **Live Trading Theater: the tape opens full and the connection light tells the truth**: The theater got a pass over every state it can be in. The connection light in the top bar used to say Connecting for the whole visit even after the live feed had connected seconds earlier, because the page's translation pass ran last and put the placeholder wording back; it now reports the connection it actually has, and the same fix stops the sound button telling a screen reader the sound is off while it is on. The Live tape used to be a blank column until something happened on-chain: it now opens seeded with real recent activity, shows placeholder rows while that is loading, and says what it is waiting for when the feed is genuinely quiet. A slow roster response no longer dumps you straight onto the error card; the page tries again with more room and says it is still assembling. Recent-activity entries that had nowhere to link are plain text now instead of links that went nowhere, and the ones that do link to a three.ws page stay in your tab instead of opening a new one. The nameplates over each 3D trader were invisible to screen readers even though they are the only keyboard route into a trader's wallet and reputation panel; they are now reachable, and every remaining control on the page has a visible focus ring. (`/theater`) `[fix, improvement]`- **Older Home Assistant houses get their agent tools back**: If your house runs a Home Assistant release from 2025, three.ws was telling you the Model Context Protocol Server integration was not enabled even when it was, and your agent lost the curated tool list you had set up for it. Home Assistant moved that endpoint between releases: the older ones serve it over one connection style and the newer ones over another, and we were only asking for the newer one. three.ws now asks your house which one it speaks and uses that, instead of guessing from a version number. Nothing to change on your side. We also now test every release we support on a real Home Assistant before we say we support it, so the supported range is a measurement rather than a promise: 2025.10 and newer, with everything working across all of it. (`/smart-home`) `[fix]`- **One unreachable home can no longer take the others down with it**: Homes connect over a live socket, and a house whose broadband keeps dropping in and out was able to crash the server process that held it, which meant every other connected home on that server went quiet at the same time. The cause was in the open-source Home Assistant client we build on: it reconnects a subscription after a drop without handling the case where the connection dies again mid-reconnect. That is now handled on our side, the failure is reported instead of being lost, and the connection recovers on its own. We have written the problem up for the upstream project too. Found by deliberately flapping a real house on and off every five seconds for two minutes. `[fix, infra]`- **Restyle Studio: upload works from the keyboard, and reverting a version really rewinds the source**: Two things on the Restyle Studio page were quietly broken. "Upload GLB" was a styled label wrapped around a hidden file input, so it could not be reached by keyboard or by a screen reader at all: the only way to bring your own model in was a mouse click. It is now a real button, in the tab order, with the same look. Separately, clicking an older entry in the Versions strip reloaded that model on the stage but left every following action pointed at the newest checkpoint, so an AI restyle or a Save right after a revert quietly re-skinned the wrong model and filed the result under the version you had gone back to. Reverting now re-anchors the source, so restyle, Save version, and "Save all as versions" all branch from the version you are actually looking at. The rest of the sweep is smaller but adds up: the metalness, roughness and emissive sliders and the model-URL and instruction fields now have real labels; every async result note is announced instead of silently changing; a successful save reads as success rather than as another grey hint; clicking "Load URL" with an empty box tells you what it wants instead of doing nothing; dropping a file on the stage highlights the target and says so when the file is not a model; picking the same file twice in a row works; and "Load the sample model" clears the failing ?url= so a reload does not land straight back in the error state. (`/restyle`) `[fix, improvement]`- **Scene Studio stops hiding its own menu bar, and tells a new scene what to do next**: The 3D scene editor was pinning itself 13 pixels too high, so the site header covered the top of the File, Edit, Add, View, Render and Help row and sliced the tops off the letters at every window size; the autosave checkbox was hidden entirely. It now sits below the header. The Import, Export and Share buttons were parked on top of the Scene, Project and Settings tabs, which made those tabs unreadable and unclickable on any desktop window; they now dock beside the sidebar and follow it when you drag it wider or narrower. At phone width the menu bar used to spill Help onto a second row that the layout could not show, and it now keeps all six on one line. A brand-new scene is no longer a silent black grid: a card explains the three ways to start and disappears the moment you add anything. Importing a model by URL now happens in a proper dialog that checks the link and explains what is wrong inline, instead of a bare browser prompt, and a failed import, export or share now says what went wrong and what to try next in the same notification style as the rest of the site rather than a browser alert box. Sharing a scene labels it with the scene's own name instead of the page's title. The translate, rotate and scale buttons are icon-only and had no names at all for screen readers; they now announce both their name and which one is active. The page also gained the heading every other page on the site has. (`/scene`) `[fix, improvement]`+- **Search keeps its filters honest, and says so when it cannot answer**: Sharing a filtered search link now works the way it looks: open /search?type=agent and the Agents filter is the one highlighted, instead of the row claiming All while the results were already narrowed. After a search runs, the types that turned up nothing for that query fade back, so you can see at a glance where the matches actually are. When the search index itself is unreachable the page now says it is warming up and offers a retry plus the browse galleries, rather than telling you nothing matched, which was never true. A failed search says what went wrong and gives you the same retry and browse links. Pressing Enter runs the query immediately without waiting for the pause-and-search delay, and Escape clears it. Result cards lost their duplicate untitled thumbnail link, creators without a public profile read as plain names instead of links that went nowhere, the search box and the remix instruction field are properly labelled for screen readers, and every focusable control on the page now shows a visible focus ring. (`/search`) `[fix, improvement]`- **See what your connected homes use, before a limit ever stops you**: Your smart home plan now has a page. It shows every allowance whether or not you are near it: how many homes you have connected, how many people are in each household, how many live screens, how many voice minutes and agent turns you have used this month, and the exact date each one resets. Two things a plan can never do are written on the page itself, because they matter more than any number on it. Locking a door, closing a garage or a water valve and arming an alarm are never refused by a limit, on any plan, in any state, including on a home your plan has paused. And confirmation prompts, your action log and every safety property of household roles are on every plan, free included: safety is not an upgrade. If a plan change ever leaves you with more homes than it covers, nothing is disconnected and nothing is deleted. The extra homes are paused, with their access tokens and their whole history untouched, and you pick which ones are live from the same page. (`/smart-home/plan`) `[feature, improvement]`- **See, export and delete everything a connected home stores**: Connecting a house to three.ws hands over a key to a physical building, so the answer to "what do you keep, and for how long" is now a page you can read and an endpoint you can call. Every piece of data a connected home creates is listed with why it exists and what removes it, including the parts we deliberately never store: the names of your rooms and devices, their states, and any audio from voice control. There is no record of which lights were on, or when. The log of what the agent did in your home is yours: it keeps 90 days by default, you can shorten it to a single day and the old entries go immediately, and an operator who has to keep records for longer can, with a written reason. One endpoint shows you what is stored, downloads all of it as JSON, and deletes one home or every trace of all of them. (`/docs/home-privacy`) `[feature, security, docs]`- **Sign Mirror tells you what went wrong, and remembers how close you got**: The ASL practice mirror got a pass over every state it can be in. When the camera cannot start it now says which thing failed and what to do about it: permission refused, no camera on the device, the camera busy in another app, or the hand tracker itself failing to download. It used to print the raw internal error, which nobody could act on. While the tracker downloads you see that it is downloading, instead of a panel that still says the camera is off. Turning the camera off puts the panel back to telling you what to do next rather than leaving an empty box. Every letter square now carries the best score you have reached on it, so twenty six identical squares become a map of where your practice actually is, and that score is kept between sessions. Screen readers now hear the finger being named, and the live skeleton and the per finger bars are redrawn in place instead of being rebuilt on every camera frame, which takes real work off the machine doing the grading. (`/sign-mirror`) `[fix, improvement]`- **Talk to your house without finding a phone, and a background "yeah" can never open your front door**: Hands-free is here for connected homes. Turn it on at /voice/home, say the wake word, and ask for what you want: "turn the kitchen light off" works while you are carrying groceries. The wake word is matched by a model that runs inside your own browser tab, so that audio never leaves your device; only the sentence you say afterwards is sent, and only to be turned into text. While the microphone is live there is an indicator on the page that cannot be switched off, and Mute genuinely stops the microphone at the device rather than hiding a dot. Talk over the agent and it stops mid-sentence and listens, in about a tenth of a second, and it will not wake itself up when it happens to say its own wake word out loud. The part we spent the most care on is the door. Anything that opens your house is spoken back in full first, the exact device appears on screen while you decide, and only the word "confirm" goes through. A "yeah" or a "sure" overheard from a conversation on the other side of the room does not, and on a device with no screen the agent refuses to take an unlock by voice at all and offers your phone instead. Four wake phrases to choose from, twelve designed states including an honest one for deployments where speech recognition is not available, and every stage of the round trip timed live on screen so you can see where the seconds go. (`/voice/home`) `[feature, security]`+- **The payments feed now tells you which volume is ours and which is real demand**: three.ws runs a closed loop where platform wallets pay platform endpoints on a schedule, to keep the payment rails warm and provably live. That traffic is real money on a real chain, and it is the overwhelming majority of settled volume, so anyone reading the raw total was reading our own money back to us. The x402 volume report on the paid analytics endpoint now carries a revenue split alongside the totals: how many calls and how much USDC came from outside wallets, how much is the internal loop, and how much is test traffic that was never money at all. A new command, npm run readout:revenue, prints the same breakdown for any window and refuses to print an external figure when it cannot tell our wallets apart from anyone else's, rather than quietly reporting a flattering one. One classifier backs both, so the API and the command can never disagree. (`/docs/autonomous-x402`) `[improvement, infra]`- **The rest of the smart home now speaks your language, and the wall display stays awake**: The connect page learned all 87 languages last week; the invitation, plan and voice satellite pages had the same gap and now speak them too, along with the live 3D house. Setting a page to Arabic or Hebrew also actually mirrors it now: the reveal button, the coloured bars beside notices, and the room and device columns in the live house used to stay stuck on the left. If you have asked your device to reduce motion, the house stops animating between states while staying completely live, so lights and locks still update the instant they change, they just arrive rather than glide. The live house also keeps the screen awake now, which is what you want on a kitchen tablet on a shelf, and gives that up the moment you switch away, which is what you want on a phone in your pocket. On a phone with a notch the house fills the screen without hiding its own controls behind the cutout. (`/smart-home`) `[improvement, fix]`- **The signal marketplace tells you how to get on it, and reads correctly to a screen reader**: No verified trader has published a paid feed yet, so the marketplace's empty state is what everyone actually sees, and it only pointed at the leaderboard. It now also points at the place you publish from: the Signals tab of your agent wallet. The rank and network filters used to announce themselves as tabs, which promises a screen-reader user a panel to arrow between that this page does not have; they are now announced as the pressed toggles they really are, wired to the board they re-rank. The Retry button on a failed load and both empty-state buttons had no hover or keyboard-focus styling at all, so a keyboard user could not see where they were; all three now light up on hover and show a focus ring. Landing on the page with a stale or misspelled sort in the address bar rewrites it to the board you are actually looking at, so a shared link always opens the view it names. And a feed link that no longer resolves now gets a real page heading instead of a floating error message. (`/signals`) `[improvement, fix]`- **The sniper scoreboard reads correctly in the light theme, and tells you what it is doing while it loads**: The strategy board was building a second copy of its own stylesheet in JavaScript and appending it to the page, so those rules won every tie and quietly reverted the real one. In the light theme that meant profit figures and the LLM badges rendered in a near-white green and lavender on white paper, close to invisible; they now use the same colours as every other crypto page and read properly in both themes. Loading is no longer a blank space under the headline: the board paints a skeleton in the exact shape of the table while it reads each agent's live wallet balance off the chain. If the feed cannot be reached you now get a plain sentence about what went wrong plus a button to try again, instead of a raw browser error and a silent 30-second wait, and a refresh that fails on top of a board that already has numbers keeps the numbers, says they are the last good read, and offers the same retry. Switching the time window while a slower request is still in flight can no longer paint the wrong window's figures. The judgment ledger says so when there are no LLM verdicts in the window rather than disappearing. And the table stopped showing a hand cursor over rows and headers that were never clickable or sortable. (`/sniper/experiments`) `[fix, improvement]`@@ -47,6 +52,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr- **three.ws Drive: your agent, in the car**: There is a new page at /drive built for a car screen instead of a desk. Your agent is on it full size, you hold one big button and talk, and it answers out loud in its own voice with its face moving. It shows you one line of what it said rather than a wall of chat, because you are driving. It starts dark, because a bright panel at night is glare, and it will switch to a day palette on one press or one sentence. The keyboard stays out of the way while you are moving: if your browser can tell how fast you are going, text entry locks itself the moment you pull away and comes back when you have properly stopped. A few things you say never leave the car at all, so "repeat that", "stop talking", "louder" and "night mode" happen instantly, while "stop at the next charger" still goes to your agent like any other question. It works today on a head unit browser, on a phone in a cradle, and on Android Automotive. The Apple CarPlay version is built and waiting on Apple's approval for voice assistants in the car. One thing this fixed for everyone: an avatar used to answer in silence if you were not signed in, and now it always has a voice. (`/drive`) `[feature, improvement]`- **Tour Atlas counts its own stops honestly, and says why a stop has no picture**: The atlas advertised 185 stops in its page title, its search prompt, its social cards and its listing everywhere on the site. It has had 263 for a while, and nothing was checking, so the number quietly went stale. It now says 263, and the atlas guard fails the build if that number ever stops matching the manifest again. Eighteen stops carry no screenshot because they are live 3D or live-market pages that never stop painting long enough to be photographed; their cards used to claim the page 'did not respond', which was untrue of all of them, and now they say what actually happened and invite you to open the page live. Opening one of those stops used to show an empty black frame above the write-up, and now shows the same explanation. If the atlas itself cannot load you get a plain sentence about what went wrong and a Try again button, instead of a raw browser error or an instruction to run a developer command. And a /tour/atlas#stop-name link now opens that stop even when you are already on the page or have a filter narrowing the grid. (`/tour/atlas`) `[fix, improvement]`- **We tried making your agent a Matter device, measured it, and decided against it for now**: Matter is the standard that lets smart-home gear from different brands work together, and the plan had always been to make a three.ws agent show up as a Matter device so that any smart-home controller could see it, drop it in a room, and use it in an automation. We built it and pointed it at a real Home Assistant to find out whether the idea holds up. It does, technically: the agent paired in under a second over an ordinary network with no Bluetooth and no special radio, Home Assistant listed it as a proper device with a name, a model and a serial number, put it in the living room, and messages went both ways in well under a second. It also held the line that matters most: an automation that asked the agent to unlock a front door was refused and the door stayed locked, because an automation is not a person saying yes, and only a real confirmation from a person opened it. We are still not shipping it, and the honest reason is that it would be a narrower version of something you can already have. The three.ws Home Assistant integration already puts your agent inside your house with the whole conversation available to it, where Matter would offer a switch and a sensor. On top of that, appearing in the big-name smart-home apps needs a certified manufacturer identity we do not hold. The full write-up, every measurement, and the exact conditions that would change our answer are now in the smart-home documentation, so nobody has to guess or start over. (`/docs/smart-home`) `[docs]`+- **Your Home Assistant voice assistant can have a face now**: If you already run Home Assistant with a voice pipeline, it hears you, understands you, turns on the lights and answers, and the whole visual side of that is an LED ring. You can now point that same pipeline at a three.ws agent and get a face on any screen in the house: it reacts while you speak, the transcript fills in as your own speech recognition produces it, and it lip-syncs the answer to the audio your own text-to-speech generated. Home Assistant keeps every part of the pipeline, running on your own hardware exactly as it does today. Setup is a pairing code, one Docker command, and adding it in Home Assistant as a Wyoming Protocol integration. Nothing needs to be exposed to the internet: Home Assistant connects out to the satellite on your own network, the satellite connects out to us, and there is no port to forward. The rule the whole thing is built around is that closing the page never stops your voice assistant working, so the run finishes, the lights still change, and the only thing you lose is the face. (`/smart-home/satellite`) `[feature]`- **Your home is a household now, and a house sitter still cannot open your front door**: A house has more than one person in it, and until now the only way to let a partner, a house sitter or a colleague use a connected home was to hand over your password. Every home has a household. On its card under “Who can reach this home” you can invite somebody by email and choose exactly what they get. There are five roles and each one says plainly what it can and cannot do at the moment you pick it. Someone who lives there can control everything and approve unlocking a door. A guest can turn the lights on and can never approve unlocking anything, ever, no matter what your agent asks them: that refusal is enforced on our servers and there is no version of the app that could offer them the button. A guest or a viewer can also be given just the kitchen, or just three specific devices, and the rooms you did not give them are removed from what they receive rather than hidden on screen, so 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 can never keep opening on the say-so of a person who has left. And every action in your home log is attributed to the person who took it, so “who did what” has a real answer. (`/smart-home`) `[feature, security]`- **Your home tells you when it stops answering, and whether the problem is ours**: When a connected house goes quiet, the manage page now says what happened and what to do about it, without you having to ask anyone. It names the real reason the handshake failed, separates a Home Assistant that rejected our token (make a new one) from a Home Assistant we cannot reach at all (check the instance), and keeps the last room state on screen instead of emptying the page. The part that matters most: it tells you whose problem it is. If enough other homes are failing at the same moment, it says so plainly and tells you there is nothing for you to do, so nobody spends an evening rebooting a router that was never broken. A house that already looks unhealthy loads the explanation on its own; a house that looks fine keeps its panel closed until you open it, so nothing extra is fetched for homes that are working. (`/smart-home`) `[feature, improvement]`- **Your house reads in your language, in your units, at a size a finger can hit**: Three fixes to the smart home page, all of them things you would have noticed. It now speaks all 87 languages: the page was written to be translated but never loaded the piece that does the translating, so everyone got English, and Arabic and Hebrew never flipped to right to left. Temperatures now come from your house rather than from an assumption. If your Home Assistant is set to Fahrenheit, every room reads in Fahrenheit, and a room at 70 no longer shows as blazing hot because the comfort range was written in Celsius. A house that mixes a Celsius sensor with a Fahrenheit thermostat is converted before it is averaged, so the number you see belongs to a real scale. The small print at the top of the page also got lighter so it clears the contrast standard, in both the light and dark themes, and the Show button next to the token field is now big enough to tap without missing. (`/smart-home`) `[fix, improvement]`diff --git a/data/changelog.json b/data/changelog.jsonindex 8fffb9703..6581a9f58 100644--- a/data/changelog.json+++ b/data/changelog.json@@ -1,6 +1,16 @@{"$comment": "Curated changelog entries for three.ws, the editorial layer of the public changelog. New PAGE launches are tracked automatically via the `added` field in data/pages.json; this file is for everything else holders care about: improvements, fixes, SDK releases, trading/payments capabilities, security work. scripts/build-page-index.mjs merges both sources into CHANGELOG.md, public/changelog.json, and public/changelog.xml. Newest first. Allowed tags: feature, improvement, fix, sdk, infra, docs, security. `link` is optional and must be a live three.ws path.","entries": [+ {+ "date": "2026-09-03",+ "title": "Every SDK doc now points at code you can actually run",+ "summary": "Eight developer docs pages described a capability without ever showing you a working project that uses it, so finding the runnable version meant guessing at folder names on GitHub. The SDK, MCP, embedding, authentication, create-an-agent, Solana, agent-payments and agent-wallets pages now each end with a Runnable example section linking straight to the project that backs them: a browser demo, a Node script that drives the free MCP server end to end, nine single-file HTML embeds you can open with no build step, the full wallet sign-in round trip, and a complete agent defined entirely as files. The machine-readable index that AI agents read to navigate the site now carries the examples location too, so an agent asked to build against three.ws can fetch working code instead of inferring it from prose. Every one of those examples is installed, run and link-checked before release, so a link on a docs page never points at something broken.",+ "tags": [+ "docs",+ "improvement"+ ],+ "link": "/docs/sdk"+ },{"date": "2026-09-03","title": "Agent avatars on the Pay page load instead of 404ing",@@ -26149,6 +26159,16 @@"improvement"],"link": "/search"+ },+ {+ "date": "2026-09-03",+ "title": "The payments feed now tells you which volume is ours and which is real demand",+ "summary": "three.ws runs a closed loop where platform wallets pay platform endpoints on a schedule, to keep the payment rails warm and provably live. That traffic is real money on a real chain, and it is the overwhelming majority of settled volume, so anyone reading the raw total was reading our own money back to us. The x402 volume report on the paid analytics endpoint now carries a revenue split alongside the totals: how many calls and how much USDC came from outside wallets, how much is the internal loop, and how much is test traffic that was never money at all. A new command, npm run readout:revenue, prints the same breakdown for any window and refuses to print an external figure when it cannot tell our wallets apart from anyone else's, rather than quietly reporting a flattering one. One classifier backs both, so the API and the command can never disagree.",+ "tags": [+ "improvement",+ "infra"+ ],+ "link": "/docs/autonomous-x402"}]}diff --git a/data/pages.json b/data/pages.jsonindex 4808435eb..152f79622 100644--- a/data/pages.json+++ b/data/pages.json@@ -6,7 +6,8 @@"tagline": "Give your AI a body.","description": "three.ws is the AI-agent layer for the open web: build, embed, monetize, and trade autonomous agents with real 3D avatars, on-chain identity (ERC-8004), pay-per-call (x402), and pump.fun token launches.","contact": "https://x.com/trythreews",- "github": "https://github.com/nirholas/three.ws"+ "github": "https://github.com/nirholas/three.ws",+ "examples": "https://github.com/nirholas/three.ws/tree/main/examples"},"sections": [{diff --git a/docs/a2a-payments.md b/docs/a2a-payments.mdindex 851e8e420..fed323be7 100644--- a/docs/a2a-payments.md+++ b/docs/a2a-payments.md@@ -198,3 +198,12 @@ every autonomous category while the owner's withdraw stays open, and that thereceipts come back from the live owner surfaces. No funds move: every spend stopsat the reservation layer, which is the same layer that runs before any key istouched in production. It needs `docker` and ports 5817, 5818 and 3817.++---++## Runnable example++[`agent-payments-sdk/`](https://github.com/nirholas/three.ws/tree/main/agent-payments-sdk) The `@three-ws/agent-payments` package: agent-to-agent payments over x402 and a2a, with its quickstart in the README.++It is part of the curated set `npm run export:satellites` publishes as the public+three.ws examples repo, so it is installed, run, and link-checked before every release.diff --git a/docs/agent-wallets.md b/docs/agent-wallets.mdindex cd0d10b30..d6033eebf 100644--- a/docs/agent-wallets.md+++ b/docs/agent-wallets.md@@ -88,3 +88,12 @@ An agent can pay a human-readable name instead of a base58 address. `/api/x402/p- [What agents can do](agent-abilities.md) — the complete dossier, including a page per wallet ability- [x402 protocol](x402.md) — how agents pay for services- [Coin launches](coin-launches.md) — how the wallet signs a pump.fun launch++---++## Runnable example++[`examples/metamask-agent-wallet/`](https://github.com/nirholas/three.ws/tree/main/examples/metamask-agent-wallet) A localhost bridge plus a single page that gives an agent a real server-side wallet through the authenticated MetaMask Agentic CLI.++It is part of the curated set `npm run export:satellites` publishes as the public+three.ws examples repo, so it is installed, run, and link-checked before every release.diff --git a/docs/authentication.md b/docs/authentication.mdindex a0dda97a5..d2cc7accd 100644--- a/docs/authentication.md+++ b/docs/authentication.md@@ -674,3 +674,12 @@ Password hashing cost is configurable via `PASSWORD_ROUNDS` (default: `11` bcryp- [ERC-8004 identity](/docs/erc8004): what a connected wallet unlocks on-chain- [Embedding guide](/docs/embedding): embeds work unauthenticated; auth is only for editing and publishing- [Architecture overview](/docs/architecture): where sessions and the API server fit++---++## Runnable example++[`examples/wallet-sign-in/`](https://github.com/nirholas/three.ws/tree/main/examples/wallet-sign-in) The complete Sign-In with Solana and Sign-In with Ethereum round trips, run against the live auth API.++It is part of the curated set `npm run export:satellites` publishes as the public+three.ws examples repo, so it is installed, run, and link-checked before every release.diff --git a/docs/create-agent.md b/docs/create-agent.mdindex d8f17bde9..107106ce6 100644--- a/docs/create-agent.md+++ b/docs/create-agent.md@@ -124,3 +124,12 @@ Full reference: [packages/create-agent/README.md](https://github.com/nirholas/th- **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](glance.md) 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).++---++## Runnable example++[`examples/coach-leo/`](https://github.com/nirholas/three.ws/tree/main/examples/coach-leo) The smallest complete agent defined entirely as files: a manifest, a system prompt, and one installed skill. Copy it as the template for your own.++It is part of the curated set `npm run export:satellites` publishes as the public+three.ws examples repo, so it is installed, run, and link-checked before every release.diff --git a/docs/embedding.md b/docs/embedding.mdindex dcb5a40f7..e4e2afbb6 100644--- a/docs/embedding.md+++ b/docs/embedding.md@@ -737,3 +737,12 @@ The platform records anonymous embed impressions (country, referrer hostname) vi- [Widgets](widgets.md) — 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++---++## Runnable example++[`examples/`](https://github.com/nirholas/three.ws/tree/main/examples) Nine single-file HTML embeds, each one openable straight in a browser with no build step: the bare avatar, the one-line demo, two agents in one scene, and the widget RPC bridge.++It is part of the curated set `npm run export:satellites` publishes as the public+three.ws examples repo, so it is installed, run, and link-checked before every release.diff --git a/docs/mcp.md b/docs/mcp.mdindex 377a44548..5b12943fb 100644--- a/docs/mcp.md+++ b/docs/mcp.md@@ -938,3 +938,12 @@ Contributors: `npm run audit:mcp-safety` enforces this. It parses each tool's ha- [3D Studio MCP (free)](/docs/mcp-studio): the no-auth, no-payment 3D generation server- [Spatial MCP](/docs/spatial-mcp): returning live 3D scenes as native MCP responses- [x402](/docs/x402): the USDC micropayment rail behind the paid tools++---++## Runnable example++[`examples/agent-native-3d/`](https://github.com/nirholas/three.ws/tree/main/examples/agent-native-3d) A Node script that drives the free MCP server end to end: generate a mesh, rig it, save it as a persona, speak through it, and emit every embed snippet.++It is part of the curated set `npm run export:satellites` publishes as the public+three.ws examples repo, so it is installed, run, and link-checked before every release.diff --git a/docs/ops/examples-repo-export.md b/docs/ops/examples-repo-export.mdindex 47e622241..4780b6b91 100644--- a/docs/ops/examples-repo-export.md+++ b/docs/ops/examples-repo-export.md@@ -141,12 +141,30 @@ plain directory; the owner turns it into a repo.5. **Never pull, fetch, or merge from the satellite.** To update it later,re-run the export and repeat steps 2 to 4. The satellite is output, never input.-## Cross-linking (rolling, after the repo exists)--- three.ws docs pages link to the matching example folder; the examples README- already links back to `https://three.ws/docs` and the live platform.-- `public/llms.txt` / `llms-full.txt` reference the examples repo.-- The org profile README pins `examples` and the monorepo.-- Ship a `data/changelog.json` entry when the repo goes public (this is a- user-visible developer resource). The export script itself is internal- tooling and gets no changelog entry.+## Cross-linking++The cross-links are wired and live today, pointed at the curated source in this+monorepo (`examples/` and the SDK directories), because the satellite repo does+not exist yet and shipping a link to a 404 is worse than shipping no link.++Already in place:++- **Eight docs pages carry a `## Runnable example` section** linking to the folder+ that backs them: `docs/sdk.md`, `docs/mcp.md`, `docs/embedding.md`,+ `docs/authentication.md`, `docs/create-agent.md`, `docs/solana.md`,+ `docs/a2a-payments.md`, `docs/agent-wallets.md`.+- **`public/llms.txt` and `public/llms-full.txt` carry an examples pointer**, emitted+ by `scripts/build-page-index.mjs` from a single constant, `site.examples` in+ `data/pages.json`. Nothing else hardcodes that URL.+- **The exported root README links back** to `https://three.ws/docs`, the changelog,+ and the live platform, and states that the monorepo is the source of truth.++When the repo goes public, flip it in this order:++1. Set `site.examples` in `data/pages.json` to `https://github.com/three-ws/examples`+ and run `node scripts/build-page-index.mjs`. That moves both llms feeds at once.+2. Repoint the eight `## Runnable example` links at the satellite paths+ (`quickstarts/`, `tutorials/`, `embeds/`, `agents/`).+3. Pin `examples` and the monorepo on the org profile README.+4. Add the `data/changelog.json` entry: the repo is a user-visible developer+ resource. The export script itself is internal tooling and gets no entry.diff --git a/docs/sdk.md b/docs/sdk.mdindex 3ebea7e21..0ab2b4598 100644--- a/docs/sdk.md+++ b/docs/sdk.md@@ -433,3 +433,12 @@ python3 -m http.server 8080- [JavaScript API](/docs/js-api): viewer, validator, and component internals- [REST API Reference](/docs/api-reference): the HTTP surface the SDK talks to- [x402](/docs/x402): the payment packages listed above++---++## Runnable example++[`sdk/example/`](https://github.com/nirholas/three.ws/tree/main/sdk/example) A browser demo that installs `@three-ws/sdk` from npm and mounts an agent with the code on this page.++It is part of the curated set `npm run export:satellites` publishes as the public+three.ws examples repo, so it is installed, run, and link-checked before every release.diff --git a/docs/solana.md b/docs/solana.mdindex 71af0bc43..0cca7e03f 100644--- a/docs/solana.md+++ b/docs/solana.md@@ -271,3 +271,12 @@ A full ERC-8004-equivalent on Solana (Identity / Reputation / Validation as Anch- [Agent Reputation on Solana](/docs/solana-reputation): how attestations become a trust grade- [SAS Credentialed Attestations](/docs/sas-attestations): authority-signed credentials- [ERC-8004](/docs/erc8004): the EVM identity path this flow mirrors++---++## Runnable example++[`solana-agent-sdk/`](https://github.com/nirholas/three.ws/tree/main/solana-agent-sdk) The `@three-ws/solana-agent` package: Solana-native agent actions, wallet providers, and x402 exact payments, with its quickstart in the README.++It is part of the curated set `npm run export:satellites` publishes as the public+three.ws examples repo, so it is installed, run, and link-checked before every release.diff --git a/packages/home-mcp/server.json b/packages/home-mcp/server.jsonindex 77bb647e8..e34d4539d 100644--- a/packages/home-mcp/server.json+++ b/packages/home-mcp/server.json@@ -2,7 +2,7 @@"$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json","name": "io.github.nirholas/home-mcp","title": "three.ws Home",- "description": "Read and safely act on a real Home Assistant house: floors, rooms, live state, the household's own scenes, and gated service calls.",+ "description": "Read and safely act on a real Home Assistant house: rooms, live state, scenes, gated actions.","websiteUrl": "https://three.ws","icons": [{diff --git a/public/changelog.json b/public/changelog.jsonindex 34be38588..c9a96b859 100644--- a/public/changelog.json+++ b/public/changelog.json@@ -1,5 +1,5 @@{- "generated_at": "2026-09-03T04:48:32.387Z",+ "generated_at": "2026-09-03T07:27:18.798Z","generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json","site": {"name": "three.ws",@@ -16,6 +16,16 @@"launch"]},+ {+ "date": "2026-09-03",+ "type": "launch",+ "title": "Docs · Give your voice assistant a face",+ "summary": "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 never does, the eleven states the display can be in, and the rule the whole thing is built around, that closing the page never stops your voice assistant working.",+ "link": "/docs/home-satellite",+ "tags": [+ "launch"+ ]+ },{"date": "2026-09-03","type": "launch",@@ -177,6 +187,16 @@"improvement"]},+ {+ "date": "2026-09-03",+ "type": "update",+ "title": "Agent avatars on the Pay page load instead of 404ing",+ "summary": "Every agent card on the x402 Pay page asked for its owner's avatar picture at a URL that has never existed on this site, so the picture always 404'd and the card fell back to a plain letter tile. The page now uses the real thumbnail the rest of three.ws uses, so an agent with a public avatar shows its face on the card, and an agent whose avatar is private still gets the letter tile without a wasted failed request.",+ "link": "/pay",+ "tags": [+ "fix"+ ]+ },{"date": "2026-09-03","type": "update",@@ -232,6 +252,17 @@"improvement"]},+ {+ "date": "2026-09-03",+ "type": "update",+ "title": "Every SDK doc now points at code you can actually run",+ "summary": "Eight developer docs pages described a capability without ever showing you a working project that uses it, so finding the runnable version meant guessing at folder names on GitHub. The SDK, MCP, embedding, authentication, create-an-agent, Solana, agent-payments and agent-wallets pages now each end with a Runnable example section linking straight to the project that backs them: a browser demo, a Node script that drives the free MCP server end to end, nine single-file HTML embeds you can open with no build step, the full wallet sign-in round trip, and a complete agent defined entirely as files. The machine-readable index that AI agents read to navigate the site now carries the examples location too, so an agent asked to build against three.ws can fetch working code instead of inferring it from prose. Every one of those examples is installed, run and link-checked before release, so a link on a docs page never points at something broken.",+ "link": "/docs/sdk",+ "tags": [+ "docs",+ "improvement"+ ]+ },{"date": "2026-09-03","type": "update",@@ -286,6 +317,17 @@"improvement"]},+ {+ "date": "2026-09-03",+ "type": "update",+ "title": "Search keeps its filters honest, and says so when it cannot answer",+ "summary": "Sharing a filtered search link now works the way it looks: open /search?type=agent and the Agents filter is the one highlighted, instead of the row claiming All while the results were already narrowed. After a search runs, the types that turned up nothing for that query fade back, so you can see at a glance where the matches actually are. When the search index itself is unreachable the page now says it is warming up and offers a retry plus the browse galleries, rather than telling you nothing matched, which was never true. A failed search says what went wrong and gives you the same retry and browse links. Pressing Enter runs the query immediately without waiting for the pause-and-search delay, and Escape clears it. Result cards lost their duplicate untitled thumbnail link, creators without a public profile read as plain names instead of links that went nowhere, the search box and the remix instruction field are properly labelled for screen readers, and every focusable control on the page now shows a visible focus ring.",+ "link": "/search",+ "tags": [+ "fix",+ "improvement"+ ]+ },{"date": "2026-09-03","type": "update",@@ -331,6 +373,17 @@"security"]},+ {+ "date": "2026-09-03",+ "type": "update",+ "title": "The payments feed now tells you which volume is ours and which is real demand",+ "summary": "three.ws runs a closed loop where platform wallets pay platform endpoints on a schedule, to keep the payment rails warm and provably live. That traffic is real money on a real chain, and it is the overwhelming majority of settled volume, so anyone reading the raw total was reading our own money back to us. The x402 volume report on the paid analytics endpoint now carries a revenue split alongside the totals: how many calls and how much USDC came from outside wallets, how much is the internal loop, and how much is test traffic that was never money at all. A new command, npm run readout:revenue, prints the same breakdown for any window and refuses to print an external figure when it cannot tell our wallets apart from anyone else's, rather than quietly reporting a flattering one. One classifier backs both, so the API and the command can never disagree.",+ "link": "/docs/autonomous-x402",+ "tags": [+ "improvement",+ "infra"+ ]+ },{"date": "2026-09-03","type": "update",@@ -439,6 +492,16 @@"docs"]},+ {+ "date": "2026-09-03",+ "type": "update",+ "title": "Your Home Assistant voice assistant can have a face now",+ "summary": "If you already run Home Assistant with a voice pipeline, it hears you, understands you, turns on the lights and answers, and the whole visual side of that is an LED ring. You can now point that same pipeline at a three.ws agent and get a face on any screen in the house: it reacts while you speak, the transcript fills in as your own speech recognition produces it, and it lip-syncs the answer to the audio your own text-to-speech generated. Home Assistant keeps every part of the pipeline, running on your own hardware exactly as it does today. Setup is a pairing code, one Docker command, and adding it in Home Assistant as a Wyoming Protocol integration. Nothing needs to be exposed to the internet: Home Assistant connects out to the satellite on your own network, the satellite connects out to us, and there is no port to forward. The rule the whole thing is built around is that closing the page never stops your voice assistant working, so the run finishes, the lights still change, and the only thing you lose is the face.",+ "link": "/smart-home/satellite",+ "tags": [+ "feature"+ ]+ },{"date": "2026-09-03","type": "update",diff --git a/public/changelog.xml b/public/changelog.xmlindex 754c4462d..8edc61441 100644--- a/public/changelog.xml+++ b/public/changelog.xml@@ -14,6 +14,14 @@<category>launch</category><description>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 code, and nothing listens on your network, no port is forwarded, and three.ws never receives a Home Assistant token. Includes the operator half: the relay service, its configuration and deploy, how the allowlist is changed, and how to prove the whole path against a real house on a network the server cannot route to.</description></item>+ <item>+ <title>Docs · Give your voice assistant a face</title>+ <link>https://three.ws/docs/home-satellite</link>+ <guid isPermaLink="false">2026-09-03:Docs · Give your voice assistant a face</guid>+ <pubDate>Thu, 03 Sep 2026 12:00:00 GMT</pubDate>+ <category>launch</category>+ <description>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 never does, the eleven states the display can be in, and the rule the whole thing is built around, that closing the page never stops your voice assistant working.</description>+ </item><item><title>Docs · Home households and roles</title><link>https://three.ws/docs/home-households</link>@@ -142,6 +150,14 @@<category>security</category><description>The home lane now has a written threat model and eleven security checks that run with every build, and the standard they hold is a lock, not a database row. The big fix: the address you give for your house is now resolved and pinned on our side before anything dials it, so a web address that secretly points back into our own network is refused instead of connected to, and it is re-checked every time your house reconnects rather than trusted from the day you added it. A device or integration in your house cannot talk your agent into anything either: we wrote an unlock instruction into a real room name, a real device name and a real scene name, ran a real agent against that house, and the front door stayed locked. Your privacy page is now rate limited like everything else, so nobody can hammer the export or the delete.</description></item>+ <item>+ <title>Agent avatars on the Pay page load instead of 404ing</title>+ <link>https://three.ws/pay</link>+ <guid isPermaLink="false">2026-09-03:Agent avatars on the Pay page load instead of 404ing</guid>+ <pubDate>Thu, 03 Sep 2026 12:00:00 GMT</pubDate>+ <category>fix</category>+ <description>Every agent card on the x402 Pay page asked for its owner's avatar picture at a URL that has never existed on this site, so the picture always 404'd and the card fell back to a plain letter tile. The page now uses the real thumbnail the rest of three.ws uses, so an agent with a public avatar shows its face on the card, and an agent whose avatar is private still gets the letter tile without a wasted failed request.</description>+ </item><item><title>Any assistant can now run your house, and it still will not open your door</title><link>https://three.ws/smart-home</link>@@ -182,6 +198,14 @@<category>fix</category><description>Paying for an Endpoint Shopper run used to send you to the generic payment page, which arrived with no price and no wallet options because it could not read the challenge this route sends. Even if it had, it would have replayed the run as an empty request: your task and budget were left behind on the previous page, so a completed payment unlocked nothing. Payment now happens on /shopper itself. The card quotes the real price, lists the Base and Solana wallets the endpoint accepts, reports connecting, signing and settling as they happen, and replays the exact task and budget you typed, so the answer and its cost breakdown appear right where you were, with a link to the settlement transaction. The example task chips are now real buttons you can reach with the keyboard, the task box and budget slider carry proper labels, and the Marketplace and Fact Checker links no longer vanish from the header on a phone.</description></item>+ <item>+ <title>Every SDK doc now points at code you can actually run</title>+ <link>https://three.ws/docs/sdk</link>+ <guid isPermaLink="false">2026-09-03:Every SDK doc now points at code you can actually run</guid>+ <pubDate>Thu, 03 Sep 2026 12:00:00 GMT</pubDate>+ <category>docs</category>+ <description>Eight developer docs pages described a capability without ever showing you a working project that uses it, so finding the runnable version meant guessing at folder names on GitHub. The SDK, MCP, embedding, authentication, create-an-agent, Solana, agent-payments and agent-wallets pages now each end with a Runnable example section linking straight to the project that backs them: a browser demo, a Node script that drives the free MCP server end to end, nine single-file HTML embeds you can open with no build step, the full wallet sign-in round trip, and a complete agent defined entirely as files. The machine-readable index that AI agents read to navigate the site now carries the examples location too, so an agent asked to build against three.ws can fetch working code instead of inferring it from prose. Every one of those examples is installed, run and link-checked before release, so a link on a docs page never points at something broken.</description>+ </item><item><title>Live Trading Theater: the tape opens full and the connection light tells the truth</title><link>https://three.ws/theater</link>@@ -222,6 +246,14 @@<category>fix</category><description>The 3D scene editor was pinning itself 13 pixels too high, so the site header covered the top of the File, Edit, Add, View, Render and Help row and sliced the tops off the letters at every window size; the autosave checkbox was hidden entirely. It now sits below the header. The Import, Export and Share buttons were parked on top of the Scene, Project and Settings tabs, which made those tabs unreadable and unclickable on any desktop window; they now dock beside the sidebar and follow it when you drag it wider or narrower. At phone width the menu bar used to spill Help onto a second row that the layout could not show, and it now keeps all six on one line. A brand-new scene is no longer a silent black grid: a card explains the three ways to start and disappears the moment you add anything. Importing a model by URL now happens in a proper dialog that checks the link and explains what is wrong inline, instead of a bare browser prompt, and a failed import, export or share now says what went wrong and what to try next in the same notification style as the rest of the site rather than a browser alert box. Sharing a scene labels it with the scene's own name instead of the page's title. The translate, rotate and scale buttons are icon-only and had no names at all for screen readers; they now announce both their name and which one is active. The page also gained the heading every other page on the site has.</description></item>+ <item>+ <title>Search keeps its filters honest, and says so when it cannot answer</title>+ <link>https://three.ws/search</link>+ <guid isPermaLink="false">2026-09-03:Search keeps its filters honest, and says so when it cannot answer</guid>+ <pubDate>Thu, 03 Sep 2026 12:00:00 GMT</pubDate>+ <category>fix</category>+ <description>Sharing a filtered search link now works the way it looks: open /search?type=agent and the Agents filter is the one highlighted, instead of the row claiming All while the results were already narrowed. After a search runs, the types that turned up nothing for that query fade back, so you can see at a glance where the matches actually are. When the search index itself is unreachable the page now says it is warming up and offers a retry plus the browse galleries, rather than telling you nothing matched, which was never true. A failed search says what went wrong and gives you the same retry and browse links. Pressing Enter runs the query immediately without waiting for the pause-and-search delay, and Escape clears it. Result cards lost their duplicate untitled thumbnail link, creators without a public profile read as plain names instead of links that went nowhere, the search box and the remix instruction field are properly labelled for screen readers, and every focusable control on the page now shows a visible focus ring.</description>+ </item><item><title>See what your connected homes use, before a limit ever stops you</title><link>https://three.ws/smart-home/plan</link>@@ -254,6 +286,14 @@<category>feature</category><description>Hands-free is here for connected homes. Turn it on at /voice/home, say the wake word, and ask for what you want: "turn the kitchen light off" works while you are carrying groceries. The wake word is matched by a model that runs inside your own browser tab, so that audio never leaves your device; only the sentence you say afterwards is sent, and only to be turned into text. While the microphone is live there is an indicator on the page that cannot be switched off, and Mute genuinely stops the microphone at the device rather than hiding a dot. Talk over the agent and it stops mid-sentence and listens, in about a tenth of a second, and it will not wake itself up when it happens to say its own wake word out loud. The part we spent the most care on is the door. Anything that opens your house is spoken back in full first, the exact device appears on screen while you decide, and only the word "confirm" goes through. A "yeah" or a "sure" overheard from a conversation on the other side of the room does not, and on a device with no screen the agent refuses to take an unlock by voice at all and offers your phone instead. Four wake phrases to choose from, twelve designed states including an honest one for deployments where speech recognition is not available, and every stage of the round trip timed live on screen so you can see where the seconds go.</description></item>+ <item>+ <title>The payments feed now tells you which volume is ours and which is real demand</title>+ <link>https://three.ws/docs/autonomous-x402</link>+ <guid isPermaLink="false">2026-09-03:The payments feed now tells you which volume is ours and which is real demand</guid>+ <pubDate>Thu, 03 Sep 2026 12:00:00 GMT</pubDate>+ <category>improvement</category>+ <description>three.ws runs a closed loop where platform wallets pay platform endpoints on a schedule, to keep the payment rails warm and provably live. That traffic is real money on a real chain, and it is the overwhelming majority of settled volume, so anyone reading the raw total was reading our own money back to us. The x402 volume report on the paid analytics endpoint now carries a revenue split alongside the totals: how many calls and how much USDC came from outside wallets, how much is the internal loop, and how much is test traffic that was never money at all. A new command, npm run readout:revenue, prints the same breakdown for any window and refuses to print an external figure when it cannot tell our wallets apart from anyone else's, rather than quietly reporting a flattering one. One classifier backs both, so the API and the command can never disagree.</description>+ </item><item><title>The rest of the smart home now speaks your language, and the wall display stays awake</title><link>https://three.ws/smart-home</link>@@ -334,6 +374,14 @@<category>docs</category><description>Matter is the standard that lets smart-home gear from different brands work together, and the plan had always been to make a three.ws agent show up as a Matter device so that any smart-home controller could see it, drop it in a room, and use it in an automation. We built it and pointed it at a real Home Assistant to find out whether the idea holds up. It does, technically: the agent paired in under a second over an ordinary network with no Bluetooth and no special radio, Home Assistant listed it as a proper device with a name, a model and a serial number, put it in the living room, and messages went both ways in well under a second. It also held the line that matters most: an automation that asked the agent to unlock a front door was refused and the door stayed locked, because an automation is not a person saying yes, and only a real confirmation from a person opened it. We are still not shipping it, and the honest reason is that it would be a narrower version of something you can already have. The three.ws Home Assistant integration already puts your agent inside your house with the whole conversation available to it, where Matter would offer a switch and a sensor. On top of that, appearing in the big-name smart-home apps needs a certified manufacturer identity we do not hold. The full write-up, every measurement, and the exact conditions that would change our answer are now in the smart-home documentation, so nobody has to guess or start over.</description></item>+ <item>+ <title>Your Home Assistant voice assistant can have a face now</title>+ <link>https://three.ws/smart-home/satellite</link>+ <guid isPermaLink="false">2026-09-03:Your Home Assistant voice assistant can have a face now</guid>+ <pubDate>Thu, 03 Sep 2026 12:00:00 GMT</pubDate>+ <category>feature</category>+ <description>If you already run Home Assistant with a voice pipeline, it hears you, understands you, turns on the lights and answers, and the whole visual side of that is an LED ring. You can now point that same pipeline at a three.ws agent and get a face on any screen in the house: it reacts while you speak, the transcript fills in as your own speech recognition produces it, and it lip-syncs the answer to the audio your own text-to-speech generated. Home Assistant keeps every part of the pipeline, running on your own hardware exactly as it does today. Setup is a pairing code, one Docker command, and adding it in Home Assistant as a Wyoming Protocol integration. Nothing needs to be exposed to the internet: Home Assistant connects out to the satellite on your own network, the satellite connects out to us, and there is no port to forward. The rule the whole thing is built around is that closing the page never stops your voice assistant working, so the run finishes, the lights still change, and the only thing you lose is the face.</description>+ </item><item><title>Your home is a household now, and a house sitter still cannot open your front door</title><link>https://three.ws/smart-home</link>diff --git a/public/features.json b/public/features.jsonindex 3de86f899..d449d1e34 100644--- a/public/features.json+++ b/public/features.json@@ -1,5 +1,5 @@{- "generated_at": "2026-09-03T04:50:15.957Z",+ "generated_at": "2026-09-03T07:27:18.729Z","generated_by": "scripts/build-page-index.mjs from data/pages.json","site": {"name": "three.ws",@@ -7,7 +7,8 @@"tagline": "Give your AI a body.","description": "three.ws is the AI-agent layer for the open web: build, embed, monetize, and trade autonomous agents with real 3D avatars, on-chain identity (ERC-8004), pay-per-call (x402), and pump.fun token launches.","contact": "https://x.com/trythreews",- "github": "https://github.com/nirholas/three.ws"+ "github": "https://github.com/nirholas/three.ws",+ "examples": "https://github.com/nirholas/three.ws/tree/main/examples"},"sections": [{diff --git a/public/llms-full.txt b/public/llms-full.txtindex 5287c47f1..9368e4eea 100644--- a/public/llms-full.txt+++ b/public/llms-full.txt@@ -5,6 +5,7 @@ three.ws is the AI-agent layer for the open web: build, embed, monetize, and traCanonical site: https://three.wsTagline: Give your AI a body.Source code: https://github.com/nirholas/three.ws+Runnable examples: https://github.com/nirholas/three.ws/tree/main/examplesContact / social: https://x.com/trythreewsThis file is generated from data/pages.json. It lists every public surface on the site, grouped by section, so AI agents and crawlers can navigate without scraping the home page.diff --git a/public/llms.txt b/public/llms.txtindex dd7556229..24c92a630 100644--- a/public/llms.txt+++ b/public/llms.txt@@ -5,6 +5,7 @@Tagline: Give your AI a body.Site: https://three.wsSource: https://github.com/nirholas/three.ws+Examples: https://github.com/nirholas/three.ws/tree/main/examplesContact: https://x.com/trythreews## For AI agentsdiff --git a/scripts/build-page-index.mjs b/scripts/build-page-index.mjsindex 8f0adee61..aa002123c 100644--- a/scripts/build-page-index.mjs+++ b/scripts/build-page-index.mjs@@ -148,6 +148,7 @@ function buildLlmsTxt() {lines.push(`Tagline: ${site.tagline}`);lines.push(`Site: ${baseUrl}`);if (site.github) lines.push(`Source: ${site.github}`);+ if (site.examples) lines.push(`Examples: ${site.examples}`);if (site.contact) lines.push(`Contact: ${site.contact}`);lines.push('');// The machine-readable section leads, and skips the `indexable` filter its@@ -193,6 +194,7 @@ function buildLlmsFull() {lines.push(`Canonical site: ${baseUrl}`);lines.push(`Tagline: ${site.tagline}`);if (site.github) lines.push(`Source code: ${site.github}`);+ if (site.examples) lines.push(`Runnable examples: ${site.examples}`);if (site.contact) lines.push(`Contact / social: ${site.contact}`);lines.push('');lines.push('This file is generated from data/pages.json. It lists every public surface on the site, grouped by section, so AI agents and crawlers can navigate without scraping the home page.');diff --git a/scripts/export-satellites.mjs b/scripts/export-satellites.mjsindex d632fe034..8b9bad9cf 100644--- a/scripts/export-satellites.mjs+++ b/scripts/export-satellites.mjs@@ -175,7 +175,14 @@ function routeRef(ref, fromRel, toRel) {if (doc) return `${HOST}/${target.startsWith('docs/tutorials/') ? 'tutorials' : 'docs'}/${doc[1]}`;// Everything else in the monorepo: a permalink a reader can actually open.- const isDir = existsSync(join(REPO, target)) && statSync(join(REPO, target)).isDirectory();+ // "Can actually open" is the whole point, so the target has to exist. A+ // reference to a file that is not in the monorepo either is dead: minting a+ // permalink for it would launder a broken reference into a plausible GitHub+ // URL that 404s, and the structure stage would then see no relative path left+ // to complain about. Returning null instead leaves the original reference in+ // place so that stage flags it and aborts the export.+ if (!existsSync(join(REPO, target))) return null;+ const isDir = statSync(join(REPO, target)).isDirectory();return `${MONOREPO_URL}/${isDir ? 'tree' : 'blob'}/main/${target}`;}@@ -278,14 +285,14 @@ function listFiles(dir, acc = []) {// public agent with a dangling skill uri is broken for the reader who tries it.// ---------------------------------------------------------------------------const AGENTS = [- { dir: 'coach-leo', title: 'Coach Leo', shows: 'A full character agent: system prompt, manifest, and skill wiring.', run: 'Load into the three.ws agent builder (instructions.md + manifest.json).', docs: `${HOST}/docs/agents` },- { dir: 'metamask-agent-wallet', title: 'MetaMask agent wallet', shows: 'A wallet-connected agent: a localhost bridge exposing the MetaMask Agentic CLI to a demo page.', run: 'node server.mjs, then open index.html at http://localhost:4280', docs: `${HOST}/docs/wallet` },+ { dir: 'coach-leo', title: 'Coach Leo', shows: 'A full character agent: system prompt, manifest, and skill wiring.', run: 'Load into the three.ws agent builder (instructions.md + manifest.json).', docs: `${HOST}/docs/create-agent` },+ { dir: 'metamask-agent-wallet', title: 'MetaMask agent wallet', shows: 'A wallet-connected agent: a localhost bridge exposing the MetaMask Agentic CLI to a demo page.', run: 'node server.mjs, then open index.html at http://localhost:4280', docs: `${HOST}/docs/agent-wallets` },];const QUICKSTARTS = [{ slug: 'sdk', pkg: '@three-ws/sdk', readme: 'sdk/README.md', section: /^## Quick start/m, exampleDir: 'sdk/example', blurb: 'The core three.ws SDK: build an agent, embed a 3D avatar, register on-chain.', docs: `${HOST}/docs/sdk` },- { slug: 'solana-agent-sdk', pkg: '@three-ws/solana-agent', readme: 'solana-agent-sdk/README.md', section: /^## Quick start/m, blurb: 'Solana-native agent actions, wallet providers, and x402 exact payments.', docs: `${HOST}/docs/solana-agent-sdk` },- { slug: 'agent-payments-sdk', pkg: '@three-ws/agent-payments', readme: 'agent-payments-sdk/README.md', section: /^## Quick start/m, blurb: 'Agent-to-agent payments over x402 and a2a on Solana and EVM.', docs: `${HOST}/docs/agent-payments` },+ { slug: 'solana-agent-sdk', pkg: '@three-ws/solana-agent', readme: 'solana-agent-sdk/README.md', section: /^## Quick start/m, blurb: 'Solana-native agent actions, wallet providers, and x402 exact payments.', docs: `${HOST}/docs/solana` },+ { slug: 'agent-payments-sdk', pkg: '@three-ws/agent-payments', readme: 'agent-payments-sdk/README.md', section: /^## Quick start/m, blurb: 'Agent-to-agent payments over x402 and a2a on Solana and EVM.', docs: `${HOST}/docs/a2a-payments` },{ slug: 'mcp-server', pkg: '@three-ws/mcp-server', readme: 'mcp-server/README.md', section: /^## Quickstart \(30 seconds\)/m, blurb: 'The three.ws MCP server: 3D generation, Solana, markets, and agent tools in Claude/Cursor.', docs: `${HOST}/docs/mcp` },];