Open-source platform for 3D AI agents. Turn text or a photo into a rigged, animated GLB avatar, give it an LLM brain, memory and a wallet, and embed it anywhere with one web component. Remote MCP server, x402 payments, Three.js, browser-native.
JavaScript 3d-generationai-agentsanimationavatardigital-humangenerative-aiglbgltfimage-to-3dllmmcpmcp-servermodel-context-protocolsolanatext-to-3dthreejsweb-componentswebglwebxrx402
fix(cors): stop the free 3D endpoints advertising payment headers they never honor
nirholas3d8502752b7a
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex 2c673f075..8d759ff76 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -8,6 +8,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr- **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.- **Docs · Rivalries** (`/docs/rivalries`): What changed on the trader board: who passed whom, who just arrived, and who is closing. Derived from close timestamps rather than a snapshot table, so the matchups work retroactively and cannot disagree with the leaderboard.+- **Docs · Trader card embed** (`/docs/trader-card-embed`): Put a live three.ws trader on any page with one script tag. The card shows the verified on-chain record and lets readers fork a coin or ghost-copy the trader, signing with their own wallet.- **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]`@@ -16,6 +17,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr- **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]`+- **Every translated news page is advertised as translated again**: The site publishes a manifest of which pages carry translated copy, and it was missing 113 of them: every news page. The build wrote that manifest before the news pages had been through the translation pass, so it read them as English-only and shipped a list 113 pages short. Nothing was untranslated, the translations were there and served correctly, but anything reading the manifest to decide what to offer in a reader's language (the language picker's page-level hints, and crawlers looking for alternates) was told those pages had no other language. The build now annotates the news pages first and counts afterwards, so the published count is 357 rather than 244. (`/news`) `[fix]`- **Fact-check now reads the part of a source that is actually about your claim**: When the fact-checker fell back to Wikipedia, it only ever read each article's opening summary. An opening summary says what a page is about, so it carries the answer only when your claim is about the page's subject. Ask whether Napoleon was unusually short and it read the first lines of "Napoleon", "Napoleon III" and "Napoleonic Wars", none of which mention height at all, so every source was scored as saying nothing and the verdict came back "not enough evidence" while the passage about his height sat further down the same article. The checker now reads each article in full and picks the paragraphs that actually discuss your claim, so that question returns the "Appearance and image" and "Napoleon's height" sections instead. Reference lists are skipped, since they repeat your words without asserting anything, and the deeper read is bounded by the time the check already had, so a slow source can never cost you the evidence that already arrived. (`/docs/fact-check`) `[improvement]`- **Fact-check now reads the part of a source that is actually about your claim**: When the fact-checker fell back to Wikipedia, it only ever read each article's opening summary. An opening summary says what a page is about, so it carries the answer only when your claim is about the page's subject. Ask whether Napoleon was unusually short and it read the first lines of "Napoleon", "Napoleon III" and "Napoleonic Wars", none of which mention height at all, so every source was scored as saying nothing and the verdict came back "not enough evidence" while the passage about his height sat further down the same article. The checker now reads each article in full and picks the paragraphs that actually discuss your claim, so that question returns the "Appearance and image" and "Napoleon's height" sections instead. Reference lists are skipped, since they repeat your words without asserting anything, and the deeper read is bounded by the time the check already had, so a slow source can never cost you the evidence that already arrived. (`/docs/fact-check`) `[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]`@@ -26,6 +28,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr- **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]`- **Payment sessions: the MCP config you copy now works, and a failed load tells you what to do**: The Copy MCP config button on /payments handed out a config that could never connect. It baked in a shortened stand-in for your session token instead of the real one (the real token is shown only once, at creation, and is never retrievable afterwards), and it wrote your sign-in cookie in the wrong format. The snippet now points at two environment variables you export yourself, so the file you save never holds a secret, and a note beside it says exactly what each one is. Failures on the page also stopped hiding behind machine jargon: when the service refused a request, the page showed you its internal code, so trying to create a session with an empty balance read as the word insufficient_credits and nothing else. You now get the plain sentence, and when the balance is the problem, a link straight to Add credits. If the list itself cannot load, the four counters at the top no longer shimmer forever as though something were still loading: the page says what failed, leaves your sessions and budgets untouched, and offers a Try again button. Smaller things along the way: the Docs button used to open a page that did not exist, filtering to a status with nothing in it now offers a way back to the full list, the status filters are reachable on a narrow phone instead of being cut off at the edge, and every field in both dialogs is properly labelled for screen readers. (`/payments`) `[fix, improvement]`- **Pump Dashboard: the live feed shows real launches again instead of raw JSON**: A full audit of /pump-dashboard, the pump.fun trading desk. The headline defect was the feed itself: every event streaming in from the realtime socket was labelled UNKNOWN and printed as a wall of raw JSON, because the socket names its event type in a field the page never read. Launches, graduations and trades now render as readable rows with the token name, symbol, mint and size, whale-sized trades are tagged as whales, and the socket's own subscription acknowledgements stop appearing as feed entries. Recent activity loaded on arrival was stamped with the current time, so a graduation from yesterday claimed to have happened seconds ago; each row now carries the time it actually happened. Filtering the feed to a type with nothing in it left an empty panel with no explanation, and now says what is being filtered and offers a way back to everything. The Token Scanner gave no sign it was working during a scan that routinely takes ten seconds, and could hang forever with no result and no error if a Solana provider accepted the request and never answered; it now shows a busy state, times out, and explains a failure with a way to retry. The Quote Engine printed raw machine codes at you (internal_error, no_curve) where a sentence belongs, and the quote service itself answered a rate-limited Solana chain with a generic internal error instead of an honest "try again in a moment". The Watch List fired a request that could only fail unless you had pointed the dashboard at your own PumpKit backend, and now explains the requirement and takes you to the setting. Twenty-one form fields across the desk got the labels screen readers need, the feed's filter row is now a properly labelled group of toggles, and the high-conviction stats no longer clip their labels on a 320 pixel phone. (`/pump-dashboard`) `[fix, improvement]`+- **Put a live trader on your own page with one script tag**: A trader with a following had no way to show it anywhere except on three.ws. Every public trader profile now has an Embed this trader button that hands over a one-line snippet: paste it into a site, a blog post, a link in bio or a stream overlay and the trader's live record renders there, updating itself. It shows realized profit or loss for the period, win rate, settled trades, whatever they are holding right now and their last few results, and every coin on it carries a Fork button that opens the real trade panel back on three.ws, signed by the reader's own wallet. The card holds no funds, asks for no key and signs nothing. It follows the reader's light or dark setting, stops updating when nobody is looking at it, keeps the last good card on screen if a refresh fails rather than blanking the page it sits on, and shows a loss exactly as plainly as a win. The snippet carries the leader's referral code, so the traffic it brings back is credited to them, and the panel previews the real card before they copy anything. (`/docs/trader-card-embed`) `[feature]`- **Rankings survives a stalled leaderboard and stops reading the whole board aloud**: If the rankings service went quiet, /rankings sat on a shimmering skeleton forever with no way out: a request that never answered looked exactly like one still loading. The board now gives up after 15 seconds and shows the same error card it already had, with a Retry button and the reason, so a stall is always recoverable. Switching metrics still cancels the previous request silently, so a fast tap never surfaces a false error. For screen readers, the results list itself was marked live, so every metric switch and every Show more re-announced up to a hundred rows; the board now announces one short line instead, such as "Creations: showing 50 of 169 ranked creators". Page copy also lost its stray dashes. (`/rankings`) `[fix, improvement]`- **Render Lab: every control leads somewhere, and the contact sheet shows its work**: Render Lab now behaves when the things it depends on do not. The Open image button no longer sits there looking live before a render exists: it reads as unavailable until there is an image, and goes back to unavailable if the render fails. When no featured avatars come back, the model strip explains that and points at the field and at /create instead of showing a blank row. When the pose catalog cannot be reached, the panel says so and offers a retry rather than a lone None chip that reads like the model has no poses. Contact sheet tiles now shimmer while they render, so a sheet in flight looks like it is working instead of like a grid of empty squares, and a tile the renderer could not produce says so and keeps its label. Where a panel is switched off because the model cannot honor it, the explanation and its escape hatch stay at full strength and stay clickable: the link into Rig Doctor was previously unclickable, and the shortcut to a model with a full face rig now finds one from the live catalog instead of loading a raw file the slow way. Dragging the size slider no longer writes a new address on every step, which Safari eventually refuses outright. Copied links now carry the quality setting, so a link really does reopen the exact configuration. Framing, pose and model options are one stop for keyboard and screen reader users and move with the arrow keys, instead of costing 29 tab presses to walk past. The capabilities endpoint the whole page is built on is now documented in the Media API reference, which is where the page has always linked. (`/render-lab`) `[fix, improvement, docs]`- **Restyle Studio: a failed save now tells you what went wrong and what still works**: A full audit of /restyle, the material and PBR editor. Every failure coming back from the server was thrown away and replaced with a bare status code: a rejected model URL read as "Restyle failed: restyle failed (400)" when the server had actually said which part of the URL it would not accept. The page now shows the real reason on all four calls it makes (AI restyle, seeded variants, version checkpoints, and texture generation). A second case got its own wording: when the model store itself is unavailable, the note says so, and points out that your edits are still live in the viewer and that Export GLB keeps working, because export runs entirely in your browser and needs no server at all. Dropping a local file used to be told to "load a public URL instead" even when the URL was never the problem, which sent people in circles; the advice now matches the actual failure. Verified end to end in a real browser: the 18 material presets, the live metalness, roughness, colour and emissive sliders, the seeded variant strip, Reset, and a validated GLB export all check out, as do the loading and error states, keyboard focus on every control, and the layout at 320, 768 and 1440 pixels. (`/restyle`) `[fix, improvement]`@@ -38,7 +41,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr- **Smart Home: the connection pool now sizes itself to the server it is running on**: The number of houses one server holds open at once was set by hand, in a different place from the memory that has to hold them, and the two drifted apart three times. Left alone, that ends with a server running out of memory and taking the whole API down with it, which every part of three.ws would feel, not just Smart Home. The pool now reads the memory its own container actually has and refuses to hold more houses than fit, saying so in the health endpoint when it does. When there is less room it connects fewer houses per server and keeps working, instead of risking an outage for everybody. (`/docs/smart-home`) `[infra, fix]`- **The "have you tried" card no longer hangs off the side of the screen on a phone**: The small suggestion card that appears in the bottom corner of the site was drawn 34 pixels wider than the space it asked for, because its padding and border were being added on top of its width instead of counted inside it. On a phone that pushed the card 22 pixels past the left edge of the screen, so its kicker, title and description were all cut off mid-word and the button inside it ran wider than the card itself. This only happened on the pages that do not load the main site stylesheet, which includes the whole markets family: the screener, coin pages, categories, the heatmap and about thirty others. The card now sits fully on screen with an even gutter on both sides at every width, and its button fits inside it. (`/screener`) `[fix]`- **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 3D studio stops promising "5 seconds to go" for eleven minutes**: Every surface that waits on a generation, the ChatGPT widget and the custom GPT included, showed a countdown built from the lane's own time estimate. Once a model outran that estimate the countdown stopped at five seconds and stayed there for the rest of the job: on a generation measured this week that meant reading "roughly 5s to go" for the final eleven minutes. The countdown now runs only while there is genuinely time left on the estimate, and past it the wait says the job keeps running in the background and shows how long it has actually been going, which is a number that moves. The inline 3D viewer in ChatGPT also now loads its model through three.ws itself rather than straight from the asset store, so it renders from any host that embeds it instead of only from our own pages. (`/forge`) `[fix, improvement]`+- **The 3D studio stops promising "5 seconds to go" for eleven minutes**: Every surface that waits on a generation, the ChatGPT widget and the custom GPT included, showed a countdown built from the lane's own time estimate. Once a model outran that estimate the countdown stopped at five seconds and stayed there for the rest of the job: on a generation measured this week that meant reading "roughly 5s to go" for the final eleven minutes. The countdown now runs only while there is genuinely time left on the estimate, and past it the wait says the job keeps running in the background and shows how long it has actually been going, which is a number that moves. The inline 3D viewer in ChatGPT also now loads its model through three.ws itself rather than straight from the asset store, so it renders from any host that embeds it instead of only from our own pages. Separately, the free 3D endpoints no longer announce payment-related headers to browsers: they never accepted a payment, but the shared header defaults named them anyway, which was misleading to anyone reading the network tab. (`/forge`) `[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]`@@ -70,6 +73,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr- **The trading arena now says who just passed whom**: The live leaderboard on the arena told you who was ahead and nothing about what had changed, so a place changing hands, which happens several times a week on its own, went unnoticed. A grudge-match strip now sits under the standings: each trader is paired with the one directly above them, labelled as an overtake, a debut or a standing chase, with the profit or loss both sides settled in the last 24 hours as the reason. It is worked out from the same closed on-chain trades the board is ranked from, by rebuilding what the board actually said 24 hours ago out of the trade timestamps rather than trusting a stored snapshot, so the matchups reach back over history the platform already has and can never disagree with the leaderboard or with either trader's profile. Every line is written from those numbers: it will not call a trader behind when they in fact hold more SOL and rank lower on consistency, and it will not say someone booked nothing when they simply did not trade. Each matchup links to the leader's verified record and to a ghost-copy of them with no money at risk. Also available to agents and scripts at /api/sniper/rivalries. (`/play/arena`) `[feature]`- **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]`+- **Voice satellite: the token command works where you actually run it, and an unpaired satellite explains itself**: Two fixes for the Home Assistant voice satellite. The command that prints a viewing token for a screen on your own network was documented to be run on the machine already running the satellite, but doing exactly that failed: it tried to start a second copy of the service and died because the ports were already taken. It now reads the identity it needs and prints the token, with nothing else running. Separately, a satellite that has not been paired yet answers its health check again and says why it is unpaired, and turns a browser away with that same reason instead of a blank refusal. That is the state you are in on a fresh install, which is exactly when you need something to read. (`/smart-home/satellite`) `[fix]`- **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 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 own agent now stands in your live house**: The 3D home at /smart-home/<id> always drew a generic figure standing in your rooms, even when you had given your agent a face months ago. It now shows your agent: the same avatar the walk world, /play and the voice satellite use, read from the one record the whole platform treats as "my agent". Switch agents in another tab and the body in the house follows, with no reload. It is fetched after the house has already drawn, so nothing waits on it, and the platform's default body stands in when you have no agent yet, no avatar yet, or an avatar you keep private, which by design publishes no model for any page to read. (`/docs/home-scene`) `[improvement]`diff --git a/api/3d/studio.js b/api/3d/studio.jsindex e730bce69..db9a317fd 100644--- a/api/3d/studio.js+++ b/api/3d/studio.js@@ -247,7 +247,7 @@ async function poll(req, res, jobId, title) {}export default wrap(async (req, res) => {- if (cors(req, res, { methods: 'GET,POST,OPTIONS' })) return;+ if (cors(req, res, { methods: 'GET,POST,OPTIONS', payments: false })) return;if (!method(req, res, ['GET', 'POST'])) return;if (req.method === 'POST') return generate(req, res);diff --git a/api/_lib/http.js b/api/_lib/http.jsindex e0feb76c6..b8f8be5f8 100644--- a/api/_lib/http.js+++ b/api/_lib/http.js@@ -488,7 +488,7 @@ export function varyOn(res, ...fields) {export function cors(req,res,- { origins = null, methods = 'GET,POST,OPTIONS', credentials = false } = {},+ { origins = null, methods = 'GET,POST,OPTIONS', credentials = false, payments = true } = {},) {const origin = req.headers.origin;if (origins === '*') {@@ -499,16 +499,24 @@ export function cors(if (credentials) res.setHeader('access-control-allow-credentials', 'true');}res.setHeader('access-control-allow-methods', methods);+ // `payments: false` is for the surfaces we present as having no payment+ // capability at all (the free ChatGPT connector and the endpoints its widget+ // touches). Advertising a payment request header and exposing a+ // PAYMENT-REQUIRED response header on one of those is a claim a reviewer can+ // read straight off the network tab, and it contradicts the rest of the+ // surface. The default stays `true`, so every metered caller is unchanged.res.setHeader('access-control-allow-headers',- 'authorization, content-type, mcp-session-id, mcp-protocol-version, x-payment, payment-signature, idempotency-key, x-irl-device, x-irl-fix, x-forge-client, x-agent-id, x-forge-seed',+ payments+ ? 'authorization, content-type, mcp-session-id, mcp-protocol-version, x-payment, payment-signature, idempotency-key, x-irl-device, x-irl-fix, x-forge-client, x-agent-id, x-forge-seed'+ : 'authorization, content-type, mcp-session-id, mcp-protocol-version, idempotency-key, x-irl-device, x-irl-fix, x-forge-client, x-agent-id, x-forge-seed',);// x402: clients (drop-in modal, x402-fetch) must read these to drive the// 402-pay-retry flow and surface settlement receipts. Without `expose`,// cross-origin readers only see CORS-safelisted response headers.res.setHeader('access-control-expose-headers',- 'PAYMENT-REQUIRED, PAYMENT-RESPONSE, x-payment-response, x-payment-network, x-payment-tx, link',+ payments ? 'PAYMENT-REQUIRED, PAYMENT-RESPONSE, x-payment-response, x-payment-network, x-payment-tx, link' : 'link',);res.setHeader('access-control-max-age', '86400');if (req.method === 'OPTIONS') {diff --git a/api/ar.js b/api/ar.jsindex 677e2c771..5b38bed20 100644--- a/api/ar.js+++ b/api/ar.js@@ -84,7 +84,7 @@ font-family:ui-sans-serif,system-ui,-apple-system,"Segoe UI",Roboto,sans-serif;b}export default wrap(async (req, res) => {- if (cors(req, res, { methods: 'GET,OPTIONS' })) return;+ if (cors(req, res, { methods: 'GET,OPTIONS', payments: false })) return;// The CORS preflight already advertises GET only; enforce it too, so a POST// gets a 405 with an Allow header instead of a redirect.if (!method(req, res, ['GET'])) return;diff --git a/api/glb.js b/api/glb.jsindex 981fc5a48..c2bfc8680 100644--- a/api/glb.js+++ b/api/glb.js@@ -27,7 +27,7 @@ const MAX_BYTES = 30 * 1024 * 1024;const TIMEOUT_MS = 20_000;export default wrap(async function handler(req, res) {- if (cors(req, res, { origins: '*', methods: 'GET,OPTIONS' })) return;+ if (cors(req, res, { origins: '*', methods: 'GET,OPTIONS', payments: false })) return;if (!method(req, res, ['GET'])) return;const ip = clientIp(req);diff --git a/api/mcp-studio.js b/api/mcp-studio.jsindex 5ccda6b7c..b2dcfc63e 100644--- a/api/mcp-studio.js+++ b/api/mcp-studio.js@@ -43,7 +43,7 @@ function callsGenerationTool(body) {}export default wrap(async (req, res) => {- if (cors(req, res, { methods: 'GET,HEAD,POST,OPTIONS', origins: '*' })) return;+ if (cors(req, res, { methods: 'GET,HEAD,POST,OPTIONS', origins: '*', payments: false })) return;// No server-initiated SSE stream — this server answers requests synchronously.if (req.method === 'GET' || req.method === 'HEAD') {diff --git a/data/changelog.json b/data/changelog.jsonindex 0fbeb4b31..951f8cf06 100644--- a/data/changelog.json+++ b/data/changelog.json@@ -1,10 +1,28 @@{"$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-09",+ "title": "Put a live trader on your own page with one script tag",+ "summary": "A trader with a following had no way to show it anywhere except on three.ws. Every public trader profile now has an Embed this trader button that hands over a one-line snippet: paste it into a site, a blog post, a link in bio or a stream overlay and the trader's live record renders there, updating itself. It shows realized profit or loss for the period, win rate, settled trades, whatever they are holding right now and their last few results, and every coin on it carries a Fork button that opens the real trade panel back on three.ws, signed by the reader's own wallet. The card holds no funds, asks for no key and signs nothing. It follows the reader's light or dark setting, stops updating when nobody is looking at it, keeps the last good card on screen if a refresh fails rather than blanking the page it sits on, and shows a loss exactly as plainly as a win. The snippet carries the leader's referral code, so the traffic it brings back is credited to them, and the panel previews the real card before they copy anything.",+ "tags": [+ "feature"+ ],+ "link": "/docs/trader-card-embed"+ },+ {+ "date": "2026-09-09",+ "title": "Voice satellite: the token command works where you actually run it, and an unpaired satellite explains itself",+ "summary": "Two fixes for the Home Assistant voice satellite. The command that prints a viewing token for a screen on your own network was documented to be run on the machine already running the satellite, but doing exactly that failed: it tried to start a second copy of the service and died because the ports were already taken. It now reads the identity it needs and prints the token, with nothing else running. Separately, a satellite that has not been paired yet answers its health check again and says why it is unpaired, and turns a browser away with that same reason instead of a blank refusal. That is the state you are in on a fresh install, which is exactly when you need something to read.",+ "tags": [+ "fix"+ ],+ "link": "/smart-home/satellite"+ },{"date": "2026-09-09","title": "The 3D studio stops promising \"5 seconds to go\" for eleven minutes",- "summary": "Every surface that waits on a generation, the ChatGPT widget and the custom GPT included, showed a countdown built from the lane's own time estimate. Once a model outran that estimate the countdown stopped at five seconds and stayed there for the rest of the job: on a generation measured this week that meant reading \"roughly 5s to go\" for the final eleven minutes. The countdown now runs only while there is genuinely time left on the estimate, and past it the wait says the job keeps running in the background and shows how long it has actually been going, which is a number that moves. The inline 3D viewer in ChatGPT also now loads its model through three.ws itself rather than straight from the asset store, so it renders from any host that embeds it instead of only from our own pages.",+ "summary": "Every surface that waits on a generation, the ChatGPT widget and the custom GPT included, showed a countdown built from the lane's own time estimate. Once a model outran that estimate the countdown stopped at five seconds and stayed there for the rest of the job: on a generation measured this week that meant reading \"roughly 5s to go\" for the final eleven minutes. The countdown now runs only while there is genuinely time left on the estimate, and past it the wait says the job keeps running in the background and shows how long it has actually been going, which is a number that moves. The inline 3D viewer in ChatGPT also now loads its model through three.ws itself rather than straight from the asset store, so it renders from any host that embeds it instead of only from our own pages. Separately, the free 3D endpoints no longer announce payment-related headers to browsers: they never accepted a payment, but the shared header defaults named them anyway, which was misleading to anyone reading the network tab.","tags": ["fix","improvement"diff --git a/prompts/store-submissions/_generated/openai-submission.md b/prompts/store-submissions/_generated/openai-submission.mdindex 1c916bb09..598763f6e 100644--- a/prompts/store-submissions/_generated/openai-submission.md+++ b/prompts/store-submissions/_generated/openai-submission.md@@ -46,6 +46,13 @@ the escalation deterministic; that is the single owner-gated dependency left ondescriptions, and the widget description) had an em-dash the house style bans. The stored`studio-resources-list.json` evidence had silently been written in the correct form, so the kit andproduction disagreed; the source is now fixed and they agree after the deploy.+- The free surface no longer advertises payment headers. Every endpoint shares one `cors()` helper,+ which announced `x-payment` in `access-control-allow-headers` and `PAYMENT-REQUIRED` in+ `access-control-expose-headers`. The JSON bodies were always clean, but a reviewer with devtools+ open would have read a payment capability off the network tab of the very connector this package+ describes as free. The four free ChatGPT-facing endpoints (`/api/mcp-studio`, `/api/3d/studio`,+ `/api/ar`, `/api/glb`) now pass `payments: false` and omit both. The metered x402 surface is+ untouched: the flag defaults to on, and `tests/mcp-studio.test.js` pins both halves.The historical 2026-07-14 blockers below stay cleared.diff --git a/public/changelog-recent.json b/public/changelog-recent.jsonindex 6af629017..a9d1728a3 100644--- a/public/changelog-recent.json+++ b/public/changelog-recent.json@@ -1,11 +1,11 @@{- "generated_at": "2026-09-09T15:29:36.953Z",+ "generated_at": "2026-09-09T15:37:11.696Z","generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json","site": {"name": "three.ws","url": "https://three.ws"},- "total": 3645,+ "total": 3649,"complete": false,"full_feed": "/changelog.json","entries": [@@ -29,6 +29,16 @@"launch"]},+ {+ "date": "2026-09-09",+ "type": "launch",+ "title": "Docs · Trader card embed",+ "summary": "Put a live three.ws trader on any page with one script tag. The card shows the verified on-chain record and lets readers fork a coin or ghost-copy the trader, signing with their own wallet.",+ "link": "/docs/trader-card-embed",+ "tags": [+ "launch"+ ]+ },{"date": "2026-09-09","type": "launch",@@ -114,6 +124,16 @@"improvement"]},+ {+ "date": "2026-09-09",+ "type": "update",+ "title": "Every translated news page is advertised as translated again",+ "summary": "The site publishes a manifest of which pages carry translated copy, and it was missing 113 of them: every news page. The build wrote that manifest before the news pages had been through the translation pass, so it read them as English-only and shipped a list 113 pages short. Nothing was untranslated, the translations were there and served correctly, but anything reading the manifest to decide what to offer in a reader's language (the language picker's page-level hints, and crawlers looking for alternates) was told those pages had no other language. The build now annotates the news pages first and counts afterwards, so the published count is 357 rather than 244.",+ "link": "/news",+ "tags": [+ "fix"+ ]+ },{"date": "2026-09-09","type": "update",@@ -220,6 +240,16 @@"improvement"]},+ {+ "date": "2026-09-09",+ "type": "update",+ "title": "Put a live trader on your own page with one script tag",+ "summary": "A trader with a following had no way to show it anywhere except on three.ws. Every public trader profile now has an Embed this trader button that hands over a one-line snippet: paste it into a site, a blog post, a link in bio or a stream overlay and the trader's live record renders there, updating itself. It shows realized profit or loss for the period, win rate, settled trades, whatever they are holding right now and their last few results, and every coin on it carries a Fork button that opens the real trade panel back on three.ws, signed by the reader's own wallet. The card holds no funds, asks for no key and signs nothing. It follows the reader's light or dark setting, stops updating when nobody is looking at it, keeps the last good card on screen if a refresh fails rather than blanking the page it sits on, and shows a loss exactly as plainly as a win. The snippet carries the leader's referral code, so the traffic it brings back is credited to them, and the panel previews the real card before they copy anything.",+ "link": "/docs/trader-card-embed",+ "tags": [+ "feature"+ ]+ },{"date": "2026-09-09","type": "update",@@ -356,7 +386,7 @@"date": "2026-09-09","type": "update","title": "The 3D studio stops promising \"5 seconds to go\" for eleven minutes",- "summary": "Every surface that waits on a generation, the ChatGPT widget and the custom GPT included, showed a countdown built from the lane's own time estimate. Once a model outran that estimate the countdown stopped at five seconds and stayed there for the rest of the job: on a generation measured this week that meant reading \"roughly 5s to go\" for the final eleven minutes. The countdown now runs only while there is genuinely time left on the estimate, and past it the wait says the job keeps running in the background and shows how long it has actually been going, which is a number that moves. The inline 3D viewer in ChatGPT also now loads its model through three.ws itself rather than straight from the asset store, so it renders from any host that embeds it instead of only from our own pages.",+ "summary": "Every surface that waits on a generation, the ChatGPT widget and the custom GPT included, showed a countdown built from the lane's own time estimate. Once a model outran that estimate the countdown stopped at five seconds and stayed there for the rest of the job: on a generation measured this week that meant reading \"roughly 5s to go\" for the final eleven minutes. The countdown now runs only while there is genuinely time left on the estimate, and past it the wait says the job keeps running in the background and shows how long it has actually been going, which is a number that moves. The inline 3D viewer in ChatGPT also now loads its model through three.ws itself rather than straight from the asset store, so it renders from any host that embeds it instead of only from our own pages. Separately, the free 3D endpoints no longer announce payment-related headers to browsers: they never accepted a payment, but the shared header defaults named them anyway, which was misleading to anyone reading the network tab.","link": "/forge","tags": ["fix",@@ -701,6 +731,16 @@"improvement"]},+ {+ "date": "2026-09-09",+ "type": "update",+ "title": "Voice satellite: the token command works where you actually run it, and an unpaired satellite explains itself",+ "summary": "Two fixes for the Home Assistant voice satellite. The command that prints a viewing token for a screen on your own network was documented to be run on the machine already running the satellite, but doing exactly that failed: it tried to start a second copy of the service and died because the ports were already taken. It now reads the identity it needs and prints the token, with nothing else running. Separately, a satellite that has not been paired yet answers its health check again and says why it is unpaired, and turns a browser away with that same reason instead of a blank refusal. That is the state you are in on a fresh install, which is exactly when you need something to read.",+ "link": "/smart-home/satellite",+ "tags": [+ "fix"+ ]+ },{"date": "2026-09-09","type": "update",@@ -1570,48 +1610,6 @@"fix","improvement"]- },- {- "date": "2026-09-05",- "type": "update",- "title": "The VS Code extension now animates, refines, optimizes and reviews your models, and checks your embeds",- "summary": "Open a rigged model in VS Code, press Animate, and pick from the same 2,800-clip motion library the site uses: the clip is retargeted onto that model's own skeleton right in the editor, and Bake clip writes it into a copy of the file so it plays in Unity, Unreal or Blender too. Describe a motion in words and the GPU fleet samples one for you. Refine takes a change like make it metallic and generates a new version anchored to the current one, keeping the version history. Optimize runs the platform's web passes on your machine and tells you what it saved. Compare pulls the committed version straight out of git, opens both side by side, and writes a structural review of what changed. Check quality asks a vision model to score the render and hands its fix straight to Refine. A turntable GIF button makes README material in one click. And in HTML, React, Vue, Svelte, Astro and Markdown files the editor now checks agent-3d tags as you type: a missing source or size, an unpinned library script, a stale integrity hash the browser would refuse, a misspelt attribute, each with a one-click fix, plus hovers and completions for every attribute.",- "link": "/docs/vscode",- "tags": [- "feature",- "sdk",- "improvement"- ]- },- {- "date": "2026-09-05",- "type": "update",- "title": "Walk up to an IRL agent, talk to it out loud, and stand it on your floor in AR",- "summary": "Tap any agent you discover on IRL and the card now leads with Talk and View in AR. Talk is a real conversation with the agent standing in front of you: hold the mic and speak, or type. It answers in its own persona, out loud in its voice (its cloned voice when it has one), and the 3D model's mouth moves with the words while it keeps breathing. Press the mic while it is talking to interrupt it. View in AR works on anyone's agent, not only your own: iPhone opens it in Quick Look on the real floor, animated, with a banner that brings you back to the conversation; Android phones with ARCore anchor it to the detected floor right inside the page, tap to place and pinch to size; every other device opens the AR launcher. Owners see a new \"talked with your agent\" event in their IRL feed when someone starts a conversation. The transcript stays between the visitor and the agent.",- "link": "/irl",- "tags": [- "feature"- ]- },- {- "date": "2026-09-05",- "type": "update",- "title": "Your agent now lives in a handheld console you can put on any website",- "summary": "The new Pocket Console at /pocket is a real handheld with a real 3D agent inside the screen. The D-pad walks it, A waves, B jumps, START swaps between the agent walking, its live stats, and a menu of every public agent you can slot in like a cartridge, and L and R flip through them. It takes keyboard, touch and a plugged-in game controller. Four shell finishes, four scenes, and the whole state travels in the link, so what you share is the device exactly as you left it. Add chrome=off and one iframe puts the console, your agent included, on your own site: transparent background, no sign-in, no SDK, no API key.",- "link": "/pocket",- "tags": [- "feature"- ]- },- {- "date": "2026-09-04",- "type": "launch",- "title": "Docs · Trader Wrapped",- "summary": "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 is read-only arithmetic over round-trips that already settled on-chain.",- "link": "/docs/trader-wrapped",- "tags": [- "launch"- ]}]}diff --git a/public/changelog.json b/public/changelog.jsonindex c5cdf426e..64847f206 100644--- a/public/changelog.json+++ b/public/changelog.json@@ -1,5 +1,5 @@{- "generated_at": "2026-09-09T15:29:36.906Z",+ "generated_at": "2026-09-09T15:37:11.632Z","generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json","site": {"name": "three.ws",@@ -26,6 +26,16 @@"launch"]},+ {+ "date": "2026-09-09",+ "type": "launch",+ "title": "Docs · Trader card embed",+ "summary": "Put a live three.ws trader on any page with one script tag. The card shows the verified on-chain record and lets readers fork a coin or ghost-copy the trader, signing with their own wallet.",+ "link": "/docs/trader-card-embed",+ "tags": [+ "launch"+ ]+ },{"date": "2026-09-09","type": "launch",@@ -111,6 +121,16 @@"improvement"]},+ {+ "date": "2026-09-09",+ "type": "update",+ "title": "Every translated news page is advertised as translated again",+ "summary": "The site publishes a manifest of which pages carry translated copy, and it was missing 113 of them: every news page. The build wrote that manifest before the news pages had been through the translation pass, so it read them as English-only and shipped a list 113 pages short. Nothing was untranslated, the translations were there and served correctly, but anything reading the manifest to decide what to offer in a reader's language (the language picker's page-level hints, and crawlers looking for alternates) was told those pages had no other language. The build now annotates the news pages first and counts afterwards, so the published count is 357 rather than 244.",+ "link": "/news",+ "tags": [+ "fix"+ ]+ },{"date": "2026-09-09","type": "update",@@ -217,6 +237,16 @@"improvement"]},+ {+ "date": "2026-09-09",+ "type": "update",+ "title": "Put a live trader on your own page with one script tag",+ "summary": "A trader with a following had no way to show it anywhere except on three.ws. Every public trader profile now has an Embed this trader button that hands over a one-line snippet: paste it into a site, a blog post, a link in bio or a stream overlay and the trader's live record renders there, updating itself. It shows realized profit or loss for the period, win rate, settled trades, whatever they are holding right now and their last few results, and every coin on it carries a Fork button that opens the real trade panel back on three.ws, signed by the reader's own wallet. The card holds no funds, asks for no key and signs nothing. It follows the reader's light or dark setting, stops updating when nobody is looking at it, keeps the last good card on screen if a refresh fails rather than blanking the page it sits on, and shows a loss exactly as plainly as a win. The snippet carries the leader's referral code, so the traffic it brings back is credited to them, and the panel previews the real card before they copy anything.",+ "link": "/docs/trader-card-embed",+ "tags": [+ "feature"+ ]+ },{"date": "2026-09-09","type": "update",@@ -353,7 +383,7 @@"date": "2026-09-09","type": "update","title": "The 3D studio stops promising \"5 seconds to go\" for eleven minutes",- "summary": "Every surface that waits on a generation, the ChatGPT widget and the custom GPT included, showed a countdown built from the lane's own time estimate. Once a model outran that estimate the countdown stopped at five seconds and stayed there for the rest of the job: on a generation measured this week that meant reading \"roughly 5s to go\" for the final eleven minutes. The countdown now runs only while there is genuinely time left on the estimate, and past it the wait says the job keeps running in the background and shows how long it has actually been going, which is a number that moves. The inline 3D viewer in ChatGPT also now loads its model through three.ws itself rather than straight from the asset store, so it renders from any host that embeds it instead of only from our own pages.",+ "summary": "Every surface that waits on a generation, the ChatGPT widget and the custom GPT included, showed a countdown built from the lane's own time estimate. Once a model outran that estimate the countdown stopped at five seconds and stayed there for the rest of the job: on a generation measured this week that meant reading \"roughly 5s to go\" for the final eleven minutes. The countdown now runs only while there is genuinely time left on the estimate, and past it the wait says the job keeps running in the background and shows how long it has actually been going, which is a number that moves. The inline 3D viewer in ChatGPT also now loads its model through three.ws itself rather than straight from the asset store, so it renders from any host that embeds it instead of only from our own pages. Separately, the free 3D endpoints no longer announce payment-related headers to browsers: they never accepted a payment, but the shared header defaults named them anyway, which was misleading to anyone reading the network tab.","link": "/forge","tags": ["fix",@@ -698,6 +728,16 @@"improvement"]},+ {+ "date": "2026-09-09",+ "type": "update",+ "title": "Voice satellite: the token command works where you actually run it, and an unpaired satellite explains itself",+ "summary": "Two fixes for the Home Assistant voice satellite. The command that prints a viewing token for a screen on your own network was documented to be run on the machine already running the satellite, but doing exactly that failed: it tried to start a second copy of the service and died because the ports were already taken. It now reads the identity it needs and prints the token, with nothing else running. Separately, a satellite that has not been paired yet answers its health check again and says why it is unpaired, and turns a browser away with that same reason instead of a blank refusal. That is the state you are in on a fresh install, which is exactly when you need something to read.",+ "link": "/smart-home/satellite",+ "tags": [+ "fix"+ ]+ },{"date": "2026-09-09","type": "update",diff --git a/public/changelog.xml b/public/changelog.xmlindex 14c453004..c1c6eaafa 100644--- a/public/changelog.xml+++ b/public/changelog.xml@@ -22,6 +22,14 @@<category>launch</category><description>What changed on the trader board: who passed whom, who just arrived, and who is closing. Derived from close timestamps rather than a snapshot table, so the matchups work retroactively and cannot disagree with the leaderboard.</description></item>+ <item>+ <title>Docs · Trader card embed</title>+ <link>https://three.ws/docs/trader-card-embed</link>+ <guid isPermaLink="false">2026-09-09:Docs · Trader card embed</guid>+ <pubDate>Wed, 09 Sep 2026 12:00:00 GMT</pubDate>+ <category>launch</category>+ <description>Put a live three.ws trader on any page with one script tag. The card shows the verified on-chain record and lets readers fork a coin or ghost-copy the trader, signing with their own wallet.</description>+ </item><item><title>Fade Radar: the wallets that are never right</title><link>https://three.ws/fade</link>@@ -86,6 +94,14 @@<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>Every translated news page is advertised as translated again</title>+ <link>https://three.ws/news</link>+ <guid isPermaLink="false">2026-09-09:Every translated news page is advertised as translated again</guid>+ <pubDate>Wed, 09 Sep 2026 12:00:00 GMT</pubDate>+ <category>fix</category>+ <description>The site publishes a manifest of which pages carry translated copy, and it was missing 113 of them: every news page. The build wrote that manifest before the news pages had been through the translation pass, so it read them as English-only and shipped a list 113 pages short. Nothing was untranslated, the translations were there and served correctly, but anything reading the manifest to decide what to offer in a reader's language (the language picker's page-level hints, and crawlers looking for alternates) was told those pages had no other language. The build now annotates the news pages first and counts afterwards, so the published count is 357 rather than 244.</description>+ </item><item><title>Fact-check now reads the part of a source that is actually about your claim</title><link>https://three.ws/docs/fact-check</link>@@ -166,6 +182,14 @@<category>fix</category><description>A full audit of /pump-dashboard, the pump.fun trading desk. The headline defect was the feed itself: every event streaming in from the realtime socket was labelled UNKNOWN and printed as a wall of raw JSON, because the socket names its event type in a field the page never read. Launches, graduations and trades now render as readable rows with the token name, symbol, mint and size, whale-sized trades are tagged as whales, and the socket's own subscription acknowledgements stop appearing as feed entries. Recent activity loaded on arrival was stamped with the current time, so a graduation from yesterday claimed to have happened seconds ago; each row now carries the time it actually happened. Filtering the feed to a type with nothing in it left an empty panel with no explanation, and now says what is being filtered and offers a way back to everything. The Token Scanner gave no sign it was working during a scan that routinely takes ten seconds, and could hang forever with no result and no error if a Solana provider accepted the request and never answered; it now shows a busy state, times out, and explains a failure with a way to retry. The Quote Engine printed raw machine codes at you (internal_error, no_curve) where a sentence belongs, and the quote service itself answered a rate-limited Solana chain with a generic internal error instead of an honest "try again in a moment". The Watch List fired a request that could only fail unless you had pointed the dashboard at your own PumpKit backend, and now explains the requirement and takes you to the setting. Twenty-one form fields across the desk got the labels screen readers need, the feed's filter row is now a properly labelled group of toggles, and the high-conviction stats no longer clip their labels on a 320 pixel phone.</description></item>+ <item>+ <title>Put a live trader on your own page with one script tag</title>+ <link>https://three.ws/docs/trader-card-embed</link>+ <guid isPermaLink="false">2026-09-09:Put a live trader on your own page with one script tag</guid>+ <pubDate>Wed, 09 Sep 2026 12:00:00 GMT</pubDate>+ <category>feature</category>+ <description>A trader with a following had no way to show it anywhere except on three.ws. Every public trader profile now has an Embed this trader button that hands over a one-line snippet: paste it into a site, a blog post, a link in bio or a stream overlay and the trader's live record renders there, updating itself. It shows realized profit or loss for the period, win rate, settled trades, whatever they are holding right now and their last few results, and every coin on it carries a Fork button that opens the real trade panel back on three.ws, signed by the reader's own wallet. The card holds no funds, asks for no key and signs nothing. It follows the reader's light or dark setting, stops updating when nobody is looking at it, keeps the last good card on screen if a refresh fails rather than blanking the page it sits on, and shows a loss exactly as plainly as a win. The snippet carries the leader's referral code, so the traffic it brings back is credited to them, and the panel previews the real card before they copy anything.</description>+ </item><item><title>Rankings survives a stalled leaderboard and stops reading the whole board aloud</title><link>https://three.ws/rankings</link>@@ -268,7 +292,7 @@<guid isPermaLink="false">2026-09-09:The 3D studio stops promising "5 seconds to go" for eleven minutes</guid><pubDate>Wed, 09 Sep 2026 12:00:00 GMT</pubDate><category>fix</category>- <description>Every surface that waits on a generation, the ChatGPT widget and the custom GPT included, showed a countdown built from the lane's own time estimate. Once a model outran that estimate the countdown stopped at five seconds and stayed there for the rest of the job: on a generation measured this week that meant reading "roughly 5s to go" for the final eleven minutes. The countdown now runs only while there is genuinely time left on the estimate, and past it the wait says the job keeps running in the background and shows how long it has actually been going, which is a number that moves. The inline 3D viewer in ChatGPT also now loads its model through three.ws itself rather than straight from the asset store, so it renders from any host that embeds it instead of only from our own pages.</description>+ <description>Every surface that waits on a generation, the ChatGPT widget and the custom GPT included, showed a countdown built from the lane's own time estimate. Once a model outran that estimate the countdown stopped at five seconds and stayed there for the rest of the job: on a generation measured this week that meant reading "roughly 5s to go" for the final eleven minutes. The countdown now runs only while there is genuinely time left on the estimate, and past it the wait says the job keeps running in the background and shows how long it has actually been going, which is a number that moves. The inline 3D viewer in ChatGPT also now loads its model through three.ws itself rather than straight from the asset store, so it renders from any host that embeds it instead of only from our own pages. Separately, the free 3D endpoints no longer announce payment-related headers to browsers: they never accepted a payment, but the shared header defaults named them anyway, which was misleading to anyone reading the network tab.</description></item><item><title>The agent-wallet demo pays again when an endpoint asks the buyer to cover its own network fee</title>@@ -518,6 +542,14 @@<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>Voice satellite: the token command works where you actually run it, and an unpaired satellite explains itself</title>+ <link>https://three.ws/smart-home/satellite</link>+ <guid isPermaLink="false">2026-09-09:Voice satellite: the token command works where you actually run it, and an unpaired satellite explains itself</guid>+ <pubDate>Wed, 09 Sep 2026 12:00:00 GMT</pubDate>+ <category>fix</category>+ <description>Two fixes for the Home Assistant voice satellite. The command that prints a viewing token for a screen on your own network was documented to be run on the machine already running the satellite, but doing exactly that failed: it tried to start a second copy of the service and died because the ports were already taken. It now reads the identity it needs and prints the token, with nothing else running. Separately, a satellite that has not been paired yet answers its health check again and says why it is unpaired, and turns a browser away with that same reason instead of a blank refusal. That is the state you are in on a fresh install, which is exactly when you need something to read.</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>diff --git a/public/features.json b/public/features.jsonindex 204b5434d..b01aaa123 100644--- a/public/features.json+++ b/public/features.json@@ -1,5 +1,5 @@{- "generated_at": "2026-09-09T15:29:36.885Z",+ "generated_at": "2026-09-09T15:37:11.595Z","generated_by": "scripts/build-page-index.mjs from data/pages.json","site": {"name": "three.ws",@@ -4218,6 +4218,16 @@"tags": [],"showcase": false},+ {+ "path": "/docs/trader-card-embed",+ "title": "Docs · Trader card embed",+ "description": "Put a live three.ws trader on any page with one script tag. The card shows the verified on-chain record and lets readers fork a coin or ghost-copy the trader, signing with their own wallet.",+ "added": "2026-09-09",+ "auth": null,+ "indexable": true,+ "tags": [],+ "showcase": false+ },{"path": "/docs/clash","title": "Docs · Coin Clash",diff --git a/tests/mcp-studio.test.js b/tests/mcp-studio.test.jsindex 38c049161..c6948fe92 100644--- a/tests/mcp-studio.test.js+++ b/tests/mcp-studio.test.js@@ -241,6 +241,44 @@ describe('mcp-studio dispatch', () => {expect(COMPONENT_HTML).toContain('poster');});+ it('advertises no payment headers on the free surface, so the network tab agrees with the listing', async () => {+ // The app is submitted to OpenAI as having zero payment capability, and+ // that claim has to hold at the header layer too: a reviewer with devtools+ // open would otherwise read `x-payment` in allow-headers and+ // `PAYMENT-REQUIRED` in expose-headers on the very connector we describe+ // as free. Those belong to the metered x402 surface, which still gets them+ // because `payments` defaults to true.+ const { cors } = await import('../api/_lib/http.js');+ const headers = {};+ const res = {+ setHeader: (k, v) => { headers[k.toLowerCase()] = String(v); },+ getHeader: (k) => headers[k.toLowerCase()],+ end: () => {},+ };+ cors({ method: 'GET', headers: { origin: 'https://web-sandbox.oaiusercontent.com' } }, res, {+ origins: '*',+ methods: 'GET,HEAD,POST,OPTIONS',+ payments: false,+ });+ expect(headers['access-control-allow-origin']).toBe('*');+ expect(headers['access-control-allow-headers']).not.toMatch(/payment/i);+ expect(headers['access-control-expose-headers']).not.toMatch(/payment/i);+ // The non-payment plumbing the connector actually needs survives.+ expect(headers['access-control-allow-headers']).toContain('mcp-session-id');+ expect(headers['access-control-allow-headers']).toContain('mcp-protocol-version');++ // The metered surface is untouched: omitting the flag keeps both lists.+ const paidHeaders = {};+ const paidRes = {+ setHeader: (k, v) => { paidHeaders[k.toLowerCase()] = String(v); },+ getHeader: (k) => paidHeaders[k.toLowerCase()],+ end: () => {},+ };+ cors({ method: 'GET', headers: {} }, paidRes, { origins: '*' });+ expect(paidHeaders['access-control-allow-headers']).toContain('x-payment');+ expect(paidHeaders['access-control-expose-headers']).toContain('PAYMENT-REQUIRED');+ });+it('routes the widget model fetch through /api/glb so it survives the ChatGPT sandbox origin', async () => {// model-viewer FETCHES the GLB, so the bytes need an// access-control-allow-origin the widget's origin is covered by. The