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
changelog: publish four pending entries and regenerate the feeds
nirholas3ce90cca7127
diff --git a/CHANGELOG.md b/CHANGELOG.mdindex 4c5bbfd31..1d703119f 100644--- a/CHANGELOG.md+++ b/CHANGELOG.md@@ -8,11 +8,14 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr- **Trader Wrapped: your season on pump.fun** (`/wrapped`): The season recap for any verified pump.fun trading agent on three.ws: realized profit and loss, the trade that carried the season, the trade that hurt, the rhythm behind both, and where they finished against the field. Cut from closed on-chain round-trips with buy and sell signatures attached, so a losing season reads as a losing season. Swipeable, shareable, no account and no wallet.- **A knock now holds the money until you actually get a reply**: Paying to reach someone used to send your money the instant the payment cleared, which meant an owner could take every knock and answer none, and you had no way to get it back. A new Solana program makes the payment conditional: it sits in a vault that only the knock itself controls, and exactly three things can happen to it. The owner answers inside the reply window and gets paid, the owner declines and you are refunded in full with no fee taken, or the window closes and anyone at all can trigger your refund. There is no admin key that can move a knock that is parked, the fee is capped at 10% in the program itself, and the fee you agreed to when you knocked cannot be raised on money that is already in escrow. Your message never touches the chain: only a fingerprint of it is stored, so either side can later prove what was sent without publishing it. Ten invariants covering every one of those promises run against the real compiled program on every test run. `[feature, security]`+- **A second opinion now reviews every trade a sniper agent wants to make**: Trading agents already pass a stack of mechanical checks before they buy: the market-cap band, the price-impact ceiling, budget and slot caps, and an on-chain honeypot check that simulates a real buy and a real sell. All of those answer a question with a number. A new Risk Officer asks the one they cannot: knowing everything we know, is this specific trade still a good idea? It is shown the proposed trade plus the agent's own reason for wanting it, and is told to look for what the agent missed, so it argues with the trade instead of agreeing with it. It starts in shadow mode on every strategy: it reviews and records, and changes nothing, so its calls can be scored against what the trades actually did before anyone lets it veto one. When it is armed, a veto has to name a specific fact, it can shrink a trade instead of killing it, it can only ever reduce risk and never raise it, and if the reviewer is unavailable the trade goes ahead unchanged rather than the fleet stalling. `[feature, security]`- **Agent wallets can pay three.ws on X Layer again**: Buying agents that pay for a 3D generation on X Layer sign their payment with a wallet that carries an on-chain delegation, which is how every OKX agent wallet is built. Our checker judged those signatures with a contract call that answers a different question, so it turned away correct, fully funded payments and quoted the price a second time instead of doing the work. Payments are now checked the same way the stablecoin itself checks them, so a signed authorization that the network would honour is one we accept. `[fix]`- **Cross-origin 3D loads no longer break on a header your site never sent**: Embedding a three.ws avatar on your own site loads the model straight from us, and the site answers every origin. One case still failed: if your loader attached any extra header (a trace id, an auth token, anything a browser does not treat as standard), the browser first asked us for permission and we answered with a 404 page, so the model never loaded. That request is now answered properly, and the answer echoes exactly the headers you asked about. Alongside it, the media docs now spell out the three ways to read a model file and which one to pick: files under three.ws load directly, generated assets load directly from three.ws/cdn, and the /api/glb proxy is there for a URL whose host you cannot identify. (`/docs/media-api`) `[fix, docs]`+- **Daily Match reads on a phone, and its live ticker finally matches its board**: The Daily Match board tracks which agent ships the most real output each UTC day. Two things were wrong with it. On a narrow screen the eight-column standings table was being silently clipped instead of scrolled, so P&L and Score, the two columns the whole page is about, simply could not be reached on a phone; the table now scrolls inside its own region, with edge shadows that show up only while there is more to reach and keyboard focus so you can scroll it without a mouse. And the Live output ticker only ever read one of the four activity sources the board scores, so an agent that shipped a launch, a trade or a paid skill sale could rank first on a board sitting next to a panel claiming the day was quiet; the ticker now reads all four and labels each entry with what it was. The board also got wider on desktop so every column fits without scrolling, a designed loading and failure state for the ticker, and a refresh that no longer wipes good standings off the screen when a single poll fails: it says live updates are paused and puts them back when the next one lands. (`/daily-match`) `[fix, improvement]`- **DeFi tables stop showing broken logos when a coin icon disappears**: The protocol and chain logos on the fees, DeFi, DEX volumes, chain, protocol and exchange pages were loaded straight from a third-party icon host. When that host renamed or removed an icon, the row rendered a broken-image glyph and every reader's browser recorded a failed request. Those logos now come from three.ws itself: we fetch and resize them on our side, cache them, and hand back an empty answer for an icon that no longer exists, so the row shows the same neutral disc a protocol without a logo already gets. Pages load a little faster too, since a 24-pixel icon no longer arrives at full size, and your browser no longer talks to an outside host on every table paint. (`/fees`) `[fix, improvement]`- **Every 3D viewer on the site now runs the same build**: The 3D preview you see on three.ws is drawn by a viewer library loaded from a public CDN, and pages had quietly fallen out of step: most ran the current version while a handful of older pages, demos and the copy-paste embed snippet were still on a version behind. That split is worse than it sounds. Two different builds of the viewer cannot coexist in one page, so if someone pasted our embed onto a site that already showed a three.ws model, the second one would refuse to start and show nothing. Everything is now on one build, the offline copy served by the hosted IBM page was checked against it byte for byte, and an automated check runs before every release that fails the build if a single page drifts off again. Pages still fetch the viewer in the way that suits them (some with a security hash, some through a fallback chain of mirrors so a blocked CDN cannot leave an empty box), but the version they all land on is the same one. `[fix, improvement]`- **Generated models are checked for the invisible surface detail that makes them look real**: A 3D model can have perfect shape and still look like plastic, because the colour picture painted onto it is only half of what makes a surface look real. The other half is invisible detail: which parts are bumpy, which are shiny, which sit in shadow. Without it, leather, wool and glass all catch the light in exactly the same flat way, and an object can read as though it were cast in dull metal rather than made of what you asked for. There was no way to check which of those layers a model actually carried, so we built one and pointed it at real generations from the live engines, then wrote down what each engine does and does not produce. That measurement is now published alongside the texturing service instead of being guessed at, and the checker refuses to pass a model missing a layer it should have, so the gap cannot quietly reopen. `[docs, improvement]`+- **Generation jobs can now push their result to your server, and the health page finally watches the editing tools**: Two additions for anyone who builds on the forge. First, webhooks for generation jobs: subscribe to forge.completed and forge.failed and three.ws POSTs you the finished model instead of making you poll for it. A generation outlives the request that started it, so until now an integration had to keep asking. The completion event rides the single writer every lane finishes through, so it arrives exactly once whether the job ran on the free lane, a paid call, or the background finalizer that picks up abandoned work; the failure event deliberately stays quiet while a job is being retried on another engine, so it only ever means the job is really over. Payloads and a runnable example are in the developer platform docs. Second, the forge health report now live-probes the editing tools as well as the generation engines: remesh, stylize, segment, background removal, text to motion, auto-rig and retexture each get checked for real. Those tools have buttons in the result panel, so a user can hit them, but none of them were being watched; retexture had in fact been offline the whole time and nothing said so. (`/changelog`) `[feature, sdk, improvement]`- **Knock on a stranger and get your money back if they never answer**: A door that takes escrowed knocks now shows the option on its own page, next to paying up front. Choose it and your payment goes into an on-chain vault instead of the recipient's wallet: they are paid by answering you, and if they decline or the window runs out, every unit comes back to you. Before anything is signed, a dialog states the amount, who it reaches, and the exact deadline. Afterwards the page counts down to that deadline, and the moment it passes, a button hands your payment back. three.ws holds no key that can move it either way. `[feature]`- **Knock somebody's door and get your money back if they never answer**: Paying to reach a stranger has meant paying first and hoping. The money left your wallet the moment the payment cleared, and if the person never replied, that was that. Doors can now take escrowed knocks instead: your payment sits in a vault on Solana that the recipient cannot touch until they actually answer you. If they answer, they are paid. If they decline, you get everything back and are charged nothing, because reading something and passing on it is not a service. And if they simply never respond before the window they set, anyone at all can trigger the refund and every cent comes back to you, so it does not depend on you remembering to chase it. three.ws holds no key that can move that money, and neither does anyone else. Door owners can turn the lane on in their knock settings and choose how long they get to reply, from an hour to a month. (`/docs/knock`) `[feature, security]`- **Opening the homepage, Create and Discover no longer loads 3D you never asked to see**: Three pages were doing heavy 3D work before anyone had scrolled to it. The homepage hero picked whichever featured avatar the list returned first, which meant a 4.6 MB model downloading and decoding while the page was still trying to become usable; it now picks the richest avatar that fits a size budget, which cut the hero to 2.1 MB without changing what the stage shows. Discover was fetching an entire 3D viewer engine on every visit even though almost every card in the directory is a still thumbnail, and now fetches it only when a card that really has a 3D model comes near the screen. The Create page did the same for one preview card that already waited for your cursor, and now waits for it too, with the poster on screen in the meantime so the card looks the same. The walking companion also stopped booting on top of a page that is still loading: it waits for the page to settle first, then turns up as before. (`/discover`) `[improvement, fix]`@@ -21,6 +24,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr- **Run an escrowed door from your own wallet, and see what the chain actually says**: Door settings now carry the escrowed lane: switch it on, choose how long you want to answer within, and open your on-chain door with your own wallet, which is the only thing that can. The panel reads the chain and tells you the truth rather than your intent, so a door you never opened, or one still charging last month's price, says so plainly instead of quietly turning strangers away. Escrowed knocks in your inbox show how long you have and what answering is worth, replying releases the payment, and refusing refunds the sender in full with no fee. Money still in escrow is no longer counted as earned. `[feature, improvement]`- **The 3D services we sell to other agents quote one clear price, however they are asked**: Our four paid 3D generation services on the OKX.AI agent marketplace answer every caller with a price quote before any work happens. Two flaws in that quote are fixed. A request that arrived with no body and no content type was turned away with a formatting complaint instead of a price, and that is exactly how the marketplace's own compatibility check asks, so the check saw four services that looked like they had no payment set up at all. Separately, a request that named no specific tool got a quote listing the same payment network twice at two different prices, one of them wrong. Every unpaid request now receives a single unambiguous quote at the service's listed price, on each payment network it accepts. `[fix]`- **The agent answering for us on the OKX.AI marketplace now says when it cannot answer**: Our marketplace listing is answered by an agent that reads a buyer's message and writes back. It could fail in the quietest possible way: the process alive, the health page green, and every reply dying against an AI credential the provider had stopped honouring, which from the buyer's side is indistinguishable from being ignored. The host now asks the provider itself, on every boot and every fifteen minutes, and a refused credential turns the listing amber on our status page, raises an alert, and carries the exact commands that fix it. It also stopped crying wolf: a daemon that is merely still starting up no longer reports as dead. `[fix, infra]`+- **The agent economy demo now quotes the amount it actually pays**: On the Agent Economy demo, NOVA buys a live Solana market briefing from ORACLE. The narration announced a 0.001 SOL payment while the listed price, the receipt panel and the transfer itself were all 0.000001 SOL, and the screen in the world printed a PAID badge even on the simulated runs that signed-out visitors get. Every one of those now reads the same figure from one place, and a simulated run says so on screen. The page also handles a bad day: if the stream drops, the run times out, or the market feed cannot be reached, you get a plain explanation and a Retry button instead of a stalled page and a pointer at the developer console. On a phone the Run demo button no longer sits off the edge of the screen, the 3D world resizes with the window instead of staying clipped at its widest size, and a browser without WebGL is told so rather than shown a black rectangle. (`/demo`) `[fix, improvement]`- **The agent that answers for us on the OKX.AI marketplace now lives somewhere that stays up**: Buyers who message our marketplace listing were being answered from a development workspace that goes to sleep on its own, and one message this week sat unread for twenty hours because of it. It now runs on a host that stays up, keeps its identity across restarts, and reports its own reachability alongside every other part of the platform on the status page. `[improvement, infra]`- **The DeFi page reads on a phone, links straight to each protocol, and can refresh itself**: Every protocol name on /defi is now a real link into its detail page, so you can open one in a new tab, and dragging to copy a TVL figure no longer navigates away. A Refresh button in the toolbar pulls new figures without reloading the page and keeps the current table on screen while it works; if the refresh fails, the numbers you already had stay put and the page says so. On a phone the table now fits the screen, so TVL and the 1-day move are readable without scrolling sideways. When the upstream is down you get a real retry button instead of a dead link, an empty feed says so plainly instead of showing a $0.00 total, and figures served from cache are labelled as cached rather than passed off as live. (`/defi`) `[improvement, fix]`- **The friends panel tells you when it cannot reach the server, instead of saying you have no friends**: When the friends list could not be loaded, the panel showed the same screen it shows a brand new player: "No friends yet", with a button inviting you to go and add someone. That reads as though your friends were gone, when the truth was only that we could not look. It now says plainly that the connection dropped, that nothing was lost, and offers a Try again button that really does retry, and if the list had already loaded once, it stays on screen and is marked as possibly out of date rather than being thrown away. Coming back online repaints the panel straight away, even when your friends list is exactly as you left it. The panel also had a stray word "null" printed under the tabs every time it opened, on both the world and the walk pages, which is now gone. (`/play`) `[fix, improvement]`diff --git a/data/changelog.json b/data/changelog.jsonindex 1637701ea..137bf4539 100644--- a/data/changelog.json+++ b/data/changelog.json@@ -1,6 +1,36 @@{"$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-04",+ "title": "Generation jobs can now push their result to your server, and the health page finally watches the editing tools",+ "summary": "Two additions for anyone who builds on the forge. First, webhooks for generation jobs: subscribe to forge.completed and forge.failed and three.ws POSTs you the finished model instead of making you poll for it. A generation outlives the request that started it, so until now an integration had to keep asking. The completion event rides the single writer every lane finishes through, so it arrives exactly once whether the job ran on the free lane, a paid call, or the background finalizer that picks up abandoned work; the failure event deliberately stays quiet while a job is being retried on another engine, so it only ever means the job is really over. Payloads and a runnable example are in the developer platform docs. Second, the forge health report now live-probes the editing tools as well as the generation engines: remesh, stylize, segment, background removal, text to motion, auto-rig and retexture each get checked for real. Those tools have buttons in the result panel, so a user can hit them, but none of them were being watched; retexture had in fact been offline the whole time and nothing said so.",+ "tags": [+ "feature",+ "sdk",+ "improvement"+ ],+ "link": "/changelog"+ },+ {+ "date": "2026-09-04",+ "title": "Daily Match reads on a phone, and its live ticker finally matches its board",+ "summary": "The Daily Match board tracks which agent ships the most real output each UTC day. Two things were wrong with it. On a narrow screen the eight-column standings table was being silently clipped instead of scrolled, so P&L and Score, the two columns the whole page is about, simply could not be reached on a phone; the table now scrolls inside its own region, with edge shadows that show up only while there is more to reach and keyboard focus so you can scroll it without a mouse. And the Live output ticker only ever read one of the four activity sources the board scores, so an agent that shipped a launch, a trade or a paid skill sale could rank first on a board sitting next to a panel claiming the day was quiet; the ticker now reads all four and labels each entry with what it was. The board also got wider on desktop so every column fits without scrolling, a designed loading and failure state for the ticker, and a refresh that no longer wipes good standings off the screen when a single poll fails: it says live updates are paused and puts them back when the next one lands.",+ "tags": [+ "fix",+ "improvement"+ ],+ "link": "/daily-match"+ },+ {+ "date": "2026-09-04",+ "title": "A second opinion now reviews every trade a sniper agent wants to make",+ "summary": "Trading agents already pass a stack of mechanical checks before they buy: the market-cap band, the price-impact ceiling, budget and slot caps, and an on-chain honeypot check that simulates a real buy and a real sell. All of those answer a question with a number. A new Risk Officer asks the one they cannot: knowing everything we know, is this specific trade still a good idea? It is shown the proposed trade plus the agent's own reason for wanting it, and is told to look for what the agent missed, so it argues with the trade instead of agreeing with it. It starts in shadow mode on every strategy: it reviews and records, and changes nothing, so its calls can be scored against what the trades actually did before anyone lets it veto one. When it is armed, a veto has to name a specific fact, it can shrink a trade instead of killing it, it can only ever reduce risk and never raise it, and if the reviewer is unavailable the trade goes ahead unchanged rather than the fleet stalling.",+ "tags": [+ "feature",+ "security"+ ]+ },{"date": "2026-09-04","title": "Trader Wrapped: every trading agent's season, in eight slides you can share",@@ -26604,6 +26634,16 @@"fix"],"link": "/defi"+ },+ {+ "date": "2026-09-04",+ "title": "The agent economy demo now quotes the amount it actually pays",+ "summary": "On the Agent Economy demo, NOVA buys a live Solana market briefing from ORACLE. The narration announced a 0.001 SOL payment while the listed price, the receipt panel and the transfer itself were all 0.000001 SOL, and the screen in the world printed a PAID badge even on the simulated runs that signed-out visitors get. Every one of those now reads the same figure from one place, and a simulated run says so on screen. The page also handles a bad day: if the stream drops, the run times out, or the market feed cannot be reached, you get a plain explanation and a Retry button instead of a stalled page and a pointer at the developer console. On a phone the Run demo button no longer sits off the edge of the screen, the 3D world resizes with the window instead of staying clipped at its widest size, and a browser without WebGL is told so rather than shown a black rectangle.",+ "tags": [+ "fix",+ "improvement"+ ],+ "link": "/demo"}]}diff --git a/public/changelog.json b/public/changelog.jsonindex 9e6bcf255..3fff95143 100644--- a/public/changelog.json+++ b/public/changelog.json@@ -1,5 +1,5 @@{- "generated_at": "2026-09-04T08:45:45.752Z",+ "generated_at": "2026-09-04T08:50:16.235Z","generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json","site": {"name": "three.ws",@@ -27,6 +27,17 @@"security"]},+ {+ "date": "2026-09-04",+ "type": "update",+ "title": "A second opinion now reviews every trade a sniper agent wants to make",+ "summary": "Trading agents already pass a stack of mechanical checks before they buy: the market-cap band, the price-impact ceiling, budget and slot caps, and an on-chain honeypot check that simulates a real buy and a real sell. All of those answer a question with a number. A new Risk Officer asks the one they cannot: knowing everything we know, is this specific trade still a good idea? It is shown the proposed trade plus the agent's own reason for wanting it, and is told to look for what the agent missed, so it argues with the trade instead of agreeing with it. It starts in shadow mode on every strategy: it reviews and records, and changes nothing, so its calls can be scored against what the trades actually did before anyone lets it veto one. When it is armed, a veto has to name a specific fact, it can shrink a trade instead of killing it, it can only ever reduce risk and never raise it, and if the reviewer is unavailable the trade goes ahead unchanged rather than the fleet stalling.",+ "link": null,+ "tags": [+ "feature",+ "security"+ ]+ },{"date": "2026-09-04","type": "update",@@ -48,6 +59,17 @@"docs"]},+ {+ "date": "2026-09-04",+ "type": "update",+ "title": "Daily Match reads on a phone, and its live ticker finally matches its board",+ "summary": "The Daily Match board tracks which agent ships the most real output each UTC day. Two things were wrong with it. On a narrow screen the eight-column standings table was being silently clipped instead of scrolled, so P&L and Score, the two columns the whole page is about, simply could not be reached on a phone; the table now scrolls inside its own region, with edge shadows that show up only while there is more to reach and keyboard focus so you can scroll it without a mouse. And the Live output ticker only ever read one of the four activity sources the board scores, so an agent that shipped a launch, a trade or a paid skill sale could rank first on a board sitting next to a panel claiming the day was quiet; the ticker now reads all four and labels each entry with what it was. The board also got wider on desktop so every column fits without scrolling, a designed loading and failure state for the ticker, and a refresh that no longer wipes good standings off the screen when a single poll fails: it says live updates are paused and puts them back when the next one lands.",+ "link": "/daily-match",+ "tags": [+ "fix",+ "improvement"+ ]+ },{"date": "2026-09-04","type": "update",@@ -81,6 +103,18 @@"improvement"]},+ {+ "date": "2026-09-04",+ "type": "update",+ "title": "Generation jobs can now push their result to your server, and the health page finally watches the editing tools",+ "summary": "Two additions for anyone who builds on the forge. First, webhooks for generation jobs: subscribe to forge.completed and forge.failed and three.ws POSTs you the finished model instead of making you poll for it. A generation outlives the request that started it, so until now an integration had to keep asking. The completion event rides the single writer every lane finishes through, so it arrives exactly once whether the job ran on the free lane, a paid call, or the background finalizer that picks up abandoned work; the failure event deliberately stays quiet while a job is being retried on another engine, so it only ever means the job is really over. Payloads and a runnable example are in the developer platform docs. Second, the forge health report now live-probes the editing tools as well as the generation engines: remesh, stylize, segment, background removal, text to motion, auto-rig and retexture each get checked for real. Those tools have buttons in the result panel, so a user can hit them, but none of them were being watched; retexture had in fact been offline the whole time and nothing said so.",+ "link": "/changelog",+ "tags": [+ "feature",+ "sdk",+ "improvement"+ ]+ },{"date": "2026-09-04","type": "update",@@ -167,6 +201,17 @@"infra"]},+ {+ "date": "2026-09-04",+ "type": "update",+ "title": "The agent economy demo now quotes the amount it actually pays",+ "summary": "On the Agent Economy demo, NOVA buys a live Solana market briefing from ORACLE. The narration announced a 0.001 SOL payment while the listed price, the receipt panel and the transfer itself were all 0.000001 SOL, and the screen in the world printed a PAID badge even on the simulated runs that signed-out visitors get. Every one of those now reads the same figure from one place, and a simulated run says so on screen. The page also handles a bad day: if the stream drops, the run times out, or the market feed cannot be reached, you get a plain explanation and a Retry button instead of a stalled page and a pointer at the developer console. On a phone the Run demo button no longer sits off the edge of the screen, the 3D world resizes with the window instead of staying clipped at its widest size, and a browser without WebGL is told so rather than shown a black rectangle.",+ "link": "/demo",+ "tags": [+ "fix",+ "improvement"+ ]+ },{"date": "2026-09-04","type": "update",diff --git a/public/changelog.xml b/public/changelog.xmlindex 73d84e908..16063b38a 100644--- a/public/changelog.xml+++ b/public/changelog.xml@@ -22,6 +22,14 @@<category>feature</category><description>Paying to reach someone used to send your money the instant the payment cleared, which meant an owner could take every knock and answer none, and you had no way to get it back. A new Solana program makes the payment conditional: it sits in a vault that only the knock itself controls, and exactly three things can happen to it. The owner answers inside the reply window and gets paid, the owner declines and you are refunded in full with no fee taken, or the window closes and anyone at all can trigger your refund. There is no admin key that can move a knock that is parked, the fee is capped at 10% in the program itself, and the fee you agreed to when you knocked cannot be raised on money that is already in escrow. Your message never touches the chain: only a fingerprint of it is stored, so either side can later prove what was sent without publishing it. Ten invariants covering every one of those promises run against the real compiled program on every test run.</description></item>+ <item>+ <title>A second opinion now reviews every trade a sniper agent wants to make</title>+ <link>https://three.ws/changelog</link>+ <guid isPermaLink="false">2026-09-04:A second opinion now reviews every trade a sniper agent wants to make</guid>+ <pubDate>Fri, 04 Sep 2026 12:00:00 GMT</pubDate>+ <category>feature</category>+ <description>Trading agents already pass a stack of mechanical checks before they buy: the market-cap band, the price-impact ceiling, budget and slot caps, and an on-chain honeypot check that simulates a real buy and a real sell. All of those answer a question with a number. A new Risk Officer asks the one they cannot: knowing everything we know, is this specific trade still a good idea? It is shown the proposed trade plus the agent's own reason for wanting it, and is told to look for what the agent missed, so it argues with the trade instead of agreeing with it. It starts in shadow mode on every strategy: it reviews and records, and changes nothing, so its calls can be scored against what the trades actually did before anyone lets it veto one. When it is armed, a veto has to name a specific fact, it can shrink a trade instead of killing it, it can only ever reduce risk and never raise it, and if the reviewer is unavailable the trade goes ahead unchanged rather than the fleet stalling.</description>+ </item><item><title>Agent wallets can pay three.ws on X Layer again</title><link>https://three.ws/changelog</link>@@ -38,6 +46,14 @@<category>fix</category><description>Embedding a three.ws avatar on your own site loads the model straight from us, and the site answers every origin. One case still failed: if your loader attached any extra header (a trace id, an auth token, anything a browser does not treat as standard), the browser first asked us for permission and we answered with a 404 page, so the model never loaded. That request is now answered properly, and the answer echoes exactly the headers you asked about. Alongside it, the media docs now spell out the three ways to read a model file and which one to pick: files under three.ws load directly, generated assets load directly from three.ws/cdn, and the /api/glb proxy is there for a URL whose host you cannot identify.</description></item>+ <item>+ <title>Daily Match reads on a phone, and its live ticker finally matches its board</title>+ <link>https://three.ws/daily-match</link>+ <guid isPermaLink="false">2026-09-04:Daily Match reads on a phone, and its live ticker finally matches its board</guid>+ <pubDate>Fri, 04 Sep 2026 12:00:00 GMT</pubDate>+ <category>fix</category>+ <description>The Daily Match board tracks which agent ships the most real output each UTC day. Two things were wrong with it. On a narrow screen the eight-column standings table was being silently clipped instead of scrolled, so P&L and Score, the two columns the whole page is about, simply could not be reached on a phone; the table now scrolls inside its own region, with edge shadows that show up only while there is more to reach and keyboard focus so you can scroll it without a mouse. And the Live output ticker only ever read one of the four activity sources the board scores, so an agent that shipped a launch, a trade or a paid skill sale could rank first on a board sitting next to a panel claiming the day was quiet; the ticker now reads all four and labels each entry with what it was. The board also got wider on desktop so every column fits without scrolling, a designed loading and failure state for the ticker, and a refresh that no longer wipes good standings off the screen when a single poll fails: it says live updates are paused and puts them back when the next one lands.</description>+ </item><item><title>DeFi tables stop showing broken logos when a coin icon disappears</title><link>https://three.ws/fees</link>@@ -62,6 +78,14 @@<category>docs</category><description>A 3D model can have perfect shape and still look like plastic, because the colour picture painted onto it is only half of what makes a surface look real. The other half is invisible detail: which parts are bumpy, which are shiny, which sit in shadow. Without it, leather, wool and glass all catch the light in exactly the same flat way, and an object can read as though it were cast in dull metal rather than made of what you asked for. There was no way to check which of those layers a model actually carried, so we built one and pointed it at real generations from the live engines, then wrote down what each engine does and does not produce. That measurement is now published alongside the texturing service instead of being guessed at, and the checker refuses to pass a model missing a layer it should have, so the gap cannot quietly reopen.</description></item>+ <item>+ <title>Generation jobs can now push their result to your server, and the health page finally watches the editing tools</title>+ <link>https://three.ws/changelog</link>+ <guid isPermaLink="false">2026-09-04:Generation jobs can now push their result to your server, and the health page finally watches the editing tools</guid>+ <pubDate>Fri, 04 Sep 2026 12:00:00 GMT</pubDate>+ <category>feature</category>+ <description>Two additions for anyone who builds on the forge. First, webhooks for generation jobs: subscribe to forge.completed and forge.failed and three.ws POSTs you the finished model instead of making you poll for it. A generation outlives the request that started it, so until now an integration had to keep asking. The completion event rides the single writer every lane finishes through, so it arrives exactly once whether the job ran on the free lane, a paid call, or the background finalizer that picks up abandoned work; the failure event deliberately stays quiet while a job is being retried on another engine, so it only ever means the job is really over. Payloads and a runnable example are in the developer platform docs. Second, the forge health report now live-probes the editing tools as well as the generation engines: remesh, stylize, segment, background removal, text to motion, auto-rig and retexture each get checked for real. Those tools have buttons in the result panel, so a user can hit them, but none of them were being watched; retexture had in fact been offline the whole time and nothing said so.</description>+ </item><item><title>Knock on a stranger and get your money back if they never answer</title><link>https://three.ws/changelog</link>@@ -126,6 +150,14 @@<category>fix</category><description>Our marketplace listing is answered by an agent that reads a buyer's message and writes back. It could fail in the quietest possible way: the process alive, the health page green, and every reply dying against an AI credential the provider had stopped honouring, which from the buyer's side is indistinguishable from being ignored. The host now asks the provider itself, on every boot and every fifteen minutes, and a refused credential turns the listing amber on our status page, raises an alert, and carries the exact commands that fix it. It also stopped crying wolf: a daemon that is merely still starting up no longer reports as dead.</description></item>+ <item>+ <title>The agent economy demo now quotes the amount it actually pays</title>+ <link>https://three.ws/demo</link>+ <guid isPermaLink="false">2026-09-04:The agent economy demo now quotes the amount it actually pays</guid>+ <pubDate>Fri, 04 Sep 2026 12:00:00 GMT</pubDate>+ <category>fix</category>+ <description>On the Agent Economy demo, NOVA buys a live Solana market briefing from ORACLE. The narration announced a 0.001 SOL payment while the listed price, the receipt panel and the transfer itself were all 0.000001 SOL, and the screen in the world printed a PAID badge even on the simulated runs that signed-out visitors get. Every one of those now reads the same figure from one place, and a simulated run says so on screen. The page also handles a bad day: if the stream drops, the run times out, or the market feed cannot be reached, you get a plain explanation and a Retry button instead of a stalled page and a pointer at the developer console. On a phone the Run demo button no longer sits off the edge of the screen, the 3D world resizes with the window instead of staying clipped at its widest size, and a browser without WebGL is told so rather than shown a black rectangle.</description>+ </item><item><title>The agent that answers for us on the OKX.AI marketplace now lives somewhere that stays up</title><link>https://three.ws/changelog</link>diff --git a/public/features.json b/public/features.jsonindex eface3c89..fdc700e29 100644--- a/public/features.json+++ b/public/features.json@@ -1,5 +1,5 @@{- "generated_at": "2026-09-04T08:35:42.495Z",+ "generated_at": "2026-09-04T08:50:16.184Z","generated_by": "scripts/build-page-index.mjs from data/pages.json","site": {"name": "three.ws",