Skip to content

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.

chore(changelog): regenerate the public feed for the video studio avatar entry

nirholas1364b0f37620
diff --git a/CHANGELOG.md b/CHANGELOG.md
index f728b0920..b3180e82a 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -106,6 +106,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr
- **The stablecoin peg monitor stops calling an unpriced coin a depeg**: The paid peg monitor at /api/x402/stablecoin-health scores every USD-pegged stablecoin against $1. Its upstream feed leaves the price blank for a large minority of the coins it tracks, and the monitor was reading that blank as a price of zero, so 75 coins with no quote at all were reported as fully depegged and shipped in the depeg alert list. They now report a status of unknown with a null price, which cut the alert list from 120 entries to the 46 coins that are genuinely off peg. Two paid endpoints alongside it stopped selling a wrong answer during a database outage: the skill marketplace's most-purchased-skills mode was returning an empty list that read like nobody hired anything, and now fails cleanly before the payment settles, while the spend-session canary reports why its create-and-consume cycle failed instead of an unexplained false. (`/docs/x402-endpoints`) `[fix]`
- **The status page tells you how old its numbers are, and the support page stops sending questions to a page that does not exist**: Four learn-and-docs pages were saying things that were no longer true. The status page computed a 'last check' stamp and then lost it a second later, because the translation pass rewrote that whole line after the live data had been written into it; readers saw the cadence sentence with no freshness at all, which matters because the status feed is edge-cached and can be minutes older than the page in front of you. The stamp now lives in its own element the translation pass cannot overwrite. The support page's 'Questions & help' card pointed at GitHub Discussions, which is switched off for the repository, so every reader who clicked it landed on a 404; questions now open a real question template in the issue tracker, and the same dead link is gone from the template chooser on GitHub. The live-event page still advertised a June session as upcoming, with 'Save your spot' and an Add to calendar button for a date that had passed, so it now switches to past-event copy on its own once the event ends. The custody guide claimed each attestation epoch is anchored on Solana without saying what you see when that step does not run; it now names the exact status the API returns and tells you which two fields to read before treating a root as anchored. (`/status`) `[fix, docs]`
- **The vanity grinders stop keeping any copy of a key you bought, and receipt checks now work from a plain link**: Two changes to the pay-per-call vanity endpoints and the free receipt verifier. First, security: when a paid call is retried, the server keeps a short-lived copy of the original response so you are never charged twice. On the provably-fair grinder that copy included the receipt's serverSeed, and the seed is enough to recompute the private key, so a retry cache that was only ever meant to hold public metadata was in fact holding key material. The stored copy is now stripped of the secret and the seed on both grinders, sealed deliveries included, and a retry returns the public metadata with a plain note that the key was delivered once. The key you receive in the live response is unchanged. Second, the free receipt verifier can now confirm a settlement transaction over a plain GET link: /api/x402/verify-receipt?hash=<tx>&network=solana, which works from a browser, a curl one-liner, or an uptime probe with no request body. Checking an attestation still uses POST because it needs the whole signed object. (`/docs/x402-dev-tools`) `[security, improvement]`
+- **The video studio stops loading an avatar it is about to throw away**: Open /create/video signed out and the page did two things at once: it started downloading the default avatar model, and it checked whether you were signed in so it could send you to the login page. The redirect always won, which killed the model download halfway through and left an error in the browser console for the abandoned file, plus one more for every texture the viewer had started unpacking. Nothing was broken on screen, but a signed-out visitor was made to pull down three quarters of a megabyte of 3D model on their way to a login form, on whatever connection they happened to be on. The page now waits until it knows who you are before it loads anything: signed in, the avatar appears exactly as before, picked from your own avatars with the bundled one as the fallback; signed out, nothing is fetched and the console stays clean. (`/create/video`) `[fix, improvement]`
- **Three paid three.ws services were invisible in the public x402 directory**: An hourly job keeps the platform's paid, agent-callable services listed on 402index, the public directory other agents search when they need a service to pay for. Before submitting a service the job confirmed the endpoint was really deployed, and it used a strict test: send a bare request and require a payment-required answer back. That test quietly disqualified any service whose paywall sits behind a parameter rather than on the bare address. Premium vanity addresses are exactly that shape: asking with no parameters is a free browse of what is in stock, and only naming a specific address asks for payment. The job cannot construct a valid paid request for an arbitrary service, so there was no hour on which such a service could ever have passed the test, and it was skipped in silence on every tick. Three live paid services were affected and had never been listed: premium vanity addresses, the pipeline endpoint, and pay-by-name. The check now asks the question it always meant to ask, which is whether the route exists at all. A missing route or a failing origin still keeps a service out of the directory, so the limited number of submissions allowed per hour is still protected, but a service that is genuinely deployed now gets listed whatever shape its paywall takes. `[fix]`
- **Three paid x402 endpoints stop shortchanging the agents that call them**: The JSON schema checker at /api/x402/schema-check never read the request body, so every paid call charged the caller and answered that the requested feed was unsupported. It now reads the body it was always meant to, validates the changelog feed for real, and refuses an unknown target with a 400 before any payment settles. The per-call skill gate at /api/x402/skill-call answered browser preflight requests with a payment challenge and no cross-origin headers, which made it uncallable from any in-browser wallet; it now answers preflight correctly on every path, and a database outage returns a plain retry-shortly message instead of echoing internal configuration detail. The paid capacity probe at /api/x402/rate-limit-probe now only accepts metered routes as its target, so a paying caller cannot aim the server's own price lookup at an unrelated internal route. The remix endpoint's refusals (unknown source, empty instruction) are no longer recorded as payment leaks in the x402 ledger. (`/docs/x402-endpoints`) `[fix, security]`
- **Three pieces of docs text that were too faint to read comfortably are now legible**: An accessibility sweep of the documentation found three places where text sat below the readable-contrast standard against the surface behind it: the comment lines inside every code sample, which is where most of our samples put the explanation, the See what changed link on the page-freshness banner, and the Live label on runnable code blocks. All three came from the same habit of dimming text that was already dark, and all three are now above the standard in both the dark and light themes. The status page KPI labels got the same treatment. Nothing moved and no wording changed, the affected text is simply readable now. (`/docs/custody`) `[improvement, docs]`
diff --git a/public/changelog.json b/public/changelog.json
index eabe0ea62..b4dbebef0 100644
--- a/public/changelog.json
+++ b/public/changelog.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-08-14T21:58:07.469Z",
+ "generated_at": "2026-08-15T01:22:33.715Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json",
"site": {
"name": "three.ws",
@@ -1089,6 +1089,17 @@
"improvement"
]
},
+ {
+ "date": "2026-08-14",
+ "type": "update",
+ "title": "The video studio stops loading an avatar it is about to throw away",
+ "summary": "Open /create/video signed out and the page did two things at once: it started downloading the default avatar model, and it checked whether you were signed in so it could send you to the login page. The redirect always won, which killed the model download halfway through and left an error in the browser console for the abandoned file, plus one more for every texture the viewer had started unpacking. Nothing was broken on screen, but a signed-out visitor was made to pull down three quarters of a megabyte of 3D model on their way to a login form, on whatever connection they happened to be on. The page now waits until it knows who you are before it loads anything: signed in, the avatar appears exactly as before, picked from your own avatars with the bundled one as the fallback; signed out, nothing is fetched and the console stays clean.",
+ "link": "/create/video",
+ "tags": [
+ "fix",
+ "improvement"
+ ]
+ },
{
"date": "2026-08-14",
"type": "update",
diff --git a/public/changelog.xml b/public/changelog.xml
index b8fa10bdd..b4f9053a7 100644
--- a/public/changelog.xml
+++ b/public/changelog.xml
@@ -806,6 +806,14 @@
<category>security</category>
<description>Two changes to the pay-per-call vanity endpoints and the free receipt verifier. First, security: when a paid call is retried, the server keeps a short-lived copy of the original response so you are never charged twice. On the provably-fair grinder that copy included the receipt's serverSeed, and the seed is enough to recompute the private key, so a retry cache that was only ever meant to hold public metadata was in fact holding key material. The stored copy is now stripped of the secret and the seed on both grinders, sealed deliveries included, and a retry returns the public metadata with a plain note that the key was delivered once. The key you receive in the live response is unchanged. Second, the free receipt verifier can now confirm a settlement transaction over a plain GET link: /api/x402/verify-receipt?hash=&lt;tx&gt;&amp;network=solana, which works from a browser, a curl one-liner, or an uptime probe with no request body. Checking an attestation still uses POST because it needs the whole signed object.</description>
</item>
+ <item>
+ <title>The video studio stops loading an avatar it is about to throw away</title>
+ <link>https://three.ws/create/video</link>
+ <guid isPermaLink="false">2026-08-14:The video studio stops loading an avatar it is about to throw away</guid>
+ <pubDate>Fri, 14 Aug 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>Open /create/video signed out and the page did two things at once: it started downloading the default avatar model, and it checked whether you were signed in so it could send you to the login page. The redirect always won, which killed the model download halfway through and left an error in the browser console for the abandoned file, plus one more for every texture the viewer had started unpacking. Nothing was broken on screen, but a signed-out visitor was made to pull down three quarters of a megabyte of 3D model on their way to a login form, on whatever connection they happened to be on. The page now waits until it knows who you are before it loads anything: signed in, the avatar appears exactly as before, picked from your own avatars with the bundled one as the fallback; signed out, nothing is fetched and the console stays clean.</description>
+ </item>
<item>
<title>Three paid three.ws services were invisible in the public x402 directory</title>
<link>https://three.ws/changelog</link>
diff --git a/public/features.json b/public/features.json
index 3b2c87b17..7737330f9 100644
--- a/public/features.json
+++ b/public/features.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-08-14T21:10:58.792Z",
+ "generated_at": "2026-08-15T01:22:33.684Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json",
"site": {
"name": "three.ws",