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.

docs(changelog): log the x402 key-rotation CSRF fix, the wallet send repair, and the trade-scan speedup

nirholas69a61a1a0bcd
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 6bec99928..065462adf 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -18,7 +18,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr
- **Agent .sol name lookups work again, and the avatar manifest schema now answers at its own address**: The avatar-agent MCP server resolves .eth and .sol names to wallet addresses. Its .sol side went through a hosted name-lookup service that has since been retired: every request came back as "not found", which reads exactly like an unregistered domain, so a working name and a nonexistent one were indistinguishable. Solana names are now read straight from the chain, from the same name-service accounts the three.ws backend already reads, so the lookup depends on nothing but a Solana RPC. Two things were fixed alongside it. The per-lookup time budget was under five seconds, which a cold Ethereum lookup routinely exceeds, so real names were being reported as timeouts; it is now fifteen seconds and adjustable. And a lookup that genuinely fails now says why instead of quietly reporting "not found". Separately, the avatar manifest schema names https://three.ws/schema/avatar.v1.json as its own identifier, but nothing was served there, so any validator that followed the identifier got a 404. The schema is now published at that address, with a test that keeps the served copy identical to the one shipped in the package. `[fix, sdk]`
- **Agent Screen is usable on a phone, and reads correctly to a screen reader**: Watching an agent work on a narrow screen was close to impossible. The row of viewer controls along the top (fit, screenshot, picture-in-picture, fullscreen, ambient, zen, and the link back to the agent) ran off the edge of the page with no way to reach them, the agent name and its live badge painted over the buttons underneath, and the two panels that open by default covered the live screen and the avatar cam completely: the whole point of the page, hidden. The control row now scrolls sideways so every control stays reachable at any width, the name keeps its space, and on a phone the page opens on a bare stage with the panels one tap away. Three fixes for anyone using a keyboard or a screen reader landed with it: the page now has a real heading and a main region for the skip link to jump to, the hidden Skip to content link stopped rendering as visible text at the top of the page, and every text field on the page gained a proper label. Finally, if the agent list fails to load for any reason other than being signed out, the page says what went wrong and offers a retry instead of telling a signed-in owner to go sign in. (`/agent-screen`) `[fix, improvement]`
- **Arming an Oracle agent for live trading no longer rounds your trade size up**: The arm page clamps the risk knobs on the server so a bad number can never reach the trading loop, and those clamps have a floor: the smallest trade the loop will place is 0.001 SOL. That floor was being applied in the wrong direction. Ask to arm a live agent with a per-trade size of zero, and instead of being told no, you were armed for real spending at 0.001 SOL a trade with a half-SOL daily ceiling you never asked for. The check meant to catch this looked at the number after the clamp had already raised it, so it could never fire. Arming live now refuses any per-trade size below the floor, and any daily cap smaller than a single trade, and tells you which number to fix; nothing is armed until you do. Clamping a too-large number back down to the ceiling is unchanged, and simulate runs keep the same forgiving behaviour as before. The arm page also shows the reason a save was rejected instead of one generic line, so an ownership problem no longer reads the same as a bad trade size, and a failed Telegram test now prints what Telegram actually said. (`/oracle/arm`) `[fix, security]`
-- **Asking for a voice that does not exist now tells you so, instead of quietly speaking in a different one**: The voice API accepts a provider and a voice id from the voice catalog. If the id was not one that provider actually has, nothing said so: the request was answered with audio rendered in that lane's default voice, and on the metered lanes it was billed, so a single typo in a voice id came back as a stranger's voice at full price with a success status. A well-formed id for a voice that had been removed took the opposite route and failed as a server error, which reads as our fault and tells a client to retry something that will never work. Both now return a plain rejection that names the id you sent and the catalog address to pick a real one from, and that check runs before anything is charged. Leaving the voice id out still gets you the lane default on purpose. Asking the catalog for a provider that does not exist used to return an empty list that was indistinguishable from a provider being down; it now says which providers exist. ElevenLabs voices, whose catalog grows every time you clone or add one, are still decided by ElevenLabs, but an id it rejects is reported as your request being wrong rather than ours, with any charge refunded first. Voice cloning also now asks who you are before reporting anything about how this server is configured. (`/docs/api-reference`) `[fix, improvement]`
+- **Asking for a voice that does not exist now tells you so, instead of quietly speaking in a different one**: The voice API accepts a provider and a voice id from the voice catalog. If the id was not one that provider actually has, nothing said so: the request was answered with audio rendered in that lane's default voice, and on the metered lanes it was billed, so a single typo in a voice id came back as a stranger's voice at full price with a success status. A well-formed id for a voice that had been removed took the opposite route and failed as a server error, which reads as our fault and tells a client to retry something that will never work. Both now return a plain rejection that names the id you sent and the catalog address to pick a real one from, and that check runs before anything is charged. Leaving the voice id out still gets you the lane default on purpose. Asking the catalog for a provider that does not exist used to return an empty list that was indistinguishable from a provider being down; it now says which providers exist. ElevenLabs voices, whose catalog grows every time you clone or add one, are still decided by ElevenLabs, but an id it rejects is reported as your request being wrong rather than ours, with any charge refunded first. Voice cloning also now asks who you are before reporting anything about how this server is configured. In the same pass, a key ElevenLabs turns down when you list your voices or browse the public voice library now comes back as your key being rejected, so the page can ask you for a new one, instead of a gateway error that invites a retry which can never succeed. (`/docs/api-reference`) `[fix, improvement]`
- **Avatars can move their lips again: the Audio2Face lane is back**: Every call that turns speech into facial animation had been failing with an upstream not-found error, so a talking avatar spoke with a frozen face and the one-shot say() path returned nothing usable. The hosted model id the lane pointed at had stopped resolving for our NVIDIA account. It now points at the hosted Audio2Face NIM that is actually live, verified end to end: a synthesized clip drives a 30 fps ARKit blendshape track whose jaw genuinely opens and closes with the words. The discovery helper that finds these model ids was missing the name NVIDIA publishes them under, which is why the outage looked like a configuration mystery; it now finds them. `[fix]`
- **Claim Your Wallet stopped telling real traders they had no track record**: Pasting a wallet into Claim Your Wallet could answer "not indexed yet" to a wallet with thousands of indexed pump.fun trades. The page only accepted a wallet the reputation scorer had already graded, and that scorer runs on a rollup that lags the trade indexer by design, so a wallet the platform had watched trade for days was still turned away. Any wallet with a real on-chain record now renders its full ledger and window aggregates immediately, with the reputation panel honestly reading unproven until the grade lands. Three more fixes shipped with it. Win and loss counts now cover closed positions only, so a trader still holding sixty fresh bags no longer reads as sixty losses, and a new realized profit-and-loss figure sits beside the existing net figure that charges an open bag's entry as if it were written off. Asking for devnet returned the wallet's mainnet trades; both halves of the read are now scoped to the network you asked for. And if the database is unreachable, the page now says the record is temporarily unavailable and offers a retry, instead of publishing an empty scorecard that the CDN would then serve to everyone for the next few minutes. (`/claim-wallet`) `[fix]`
- **Docs pages stop opening with a wall of raw metadata, and the AWS pages say where the Marketplace listing actually stands**: Nine documentation pages are written as article drafts, so each one starts with a small block of publishing metadata: the title, where it is meant to run, its tags. That block is meant for the tooling, not for you, but the docs reader had no idea what it was and rendered it as an enormous heading at the very top of the article, above the actual writing. It is now recognised and hidden, on the page and in the Copy page text, so those articles begin where they should. Reading the same pages closely turned up claims that had drifted: several said three.ws was already live on AWS Marketplace and billing usage to your AWS invoice. The integration is built and deployed, but the listing itself has not been published yet and the pricing decision is a free subscription with no AWS metering, so the AWS pages now say exactly that and point at the page that tracks the status. The MCP article's vanity-address tool was also listed at a metered price of up to fifty cents; it is a flat five cents per grind, which is what the code has always charged. (`/docs/aws-marketplace`) `[docs, fix]`
@@ -28,9 +28,12 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr
- **Paying for a skill by Solana Pay QR now shows a real three.ws merchant card**: When a wallet scans a Solana Pay code for a skill purchase, it first asks our server who the merchant is and shows the answer in the sheet you approve before signing. That reply pointed at a logo file that has never existed, so the icon came back as a 404 and the merchant appeared broken at the exact moment you decide whether to pay, under the retired 3D-Agent name rather than three.ws. The probe now returns the live logo and the current name, and answers wallets that ask from a browser, which the Solana Pay spec requires. Confirming a purchase through the off-web webhook also accepts the settlement hash an EVM payment needs, so a card that settled on Base can finish instead of sitting on pending forever, and a confirmation failure now reaches our error tracker rather than disappearing into a generic 500. (`/marketplace`) `[fix]`
- **Pinning an avatar to IPFS works for real avatars, not just tiny ones**: Minting an avatar from the Avatar Studio pins the model and its metadata to IPFS, and the whole file is sent through the platform so the storage credential never has to reach your browser. The endpoint said it accepted files up to 10 MB, but it was actually rejecting anything over roughly 730 KB, which is smaller than almost any real avatar. The error it gave back was a bare 'payload too large' that named no limit, so there was nothing to act on. The cause was two size limits that had never been reconciled: files are sent as text, which makes them a third larger in transit, and the transport limit was left at its default while the documented limit was set eight times higher. The limits now agree. Inline uploads are accepted up to 5 MB, which is what the request size can actually carry, and anything larger has a clear path: upload it to storage first and pin it by URL, a lane that has always accepted 50 MB. Over-sized uploads now say which ceiling was crossed. Two smaller fixes came with it: the filename you send is now the filename filed with the storage provider, instead of every avatar being stored as 'avatar.glb' and every metadata file as 'manifest.json', which made a pin list impossible to read; and a request with a genuine mistake in it, such as a file from somewhere the platform does not own, now gets an error explaining the mistake rather than a generic 'service unavailable' that hid it. The endpoint is now documented in the API reference. `[fix, docs]`
- **Plan checkout: a paid upgrade can only ever settle on real mainnet, and a late payment is no longer stranded**: Paying for a plan creates a quote, you send the funds, then the server checks the chain before it upgrades you. Three things in that path were wrong. The checkout side has always refused test-network quotes in production, because test-network dollars are free from a faucet, but the confirm side still let a caller name the test network itself, and it is the confirm side that decides which chain it looks at and which dollar it accepts. Both ends now read the same setting, so a production upgrade can only ever be settled by real funds on mainnet. Second, an Ethereum-side payment has to wait twelve blocks before it counts, which meant funds sent near the end of a session could land on-chain and then be refused for arriving late, with the money already gone; that lane now honors the same one-hour grace window the Solana lane has, so an on-chain payment is always claimable. Third, confirming an Ethereum payment could reach a Solana quote and mark it expired, and asking to buy a skill from a malformed agent id answered a generic server error instead of telling you what was wrong with the request. (`/pricing`) `[fix, security]`
+- **Rotating or revoking an x402 API key now requires a proof the request came from you**: The billing page's rotate and revoke buttons destroy a live API credential, but the endpoint behind them accepted any request that carried your session cookie. A page on another site could have posted to it and killed a working key without you ever seeing the response. Both actions now require a single-use token the page fetches for each write, and the page tells you plainly when a token has gone stale or you have tried too often. Rotating also mints the replacement key before retiring the old one, so a failure part way through can no longer leave you with no key at all. (`/billing/keys`) `[security, fix]`
- **Saving a big build no longer re-downloads the whole world first**: Every time you saved a world, the service fetched and re-parsed the entire previous version of that world just to check who owns it. On a large build that meant a full extra download and parse on each autosave, for a single ownership field. The check now reads only the small index record, so saves on big worlds are noticeably quicker and the storage layer does half the work. Two error replies also got honest labels: a build that exceeds the size cap now answers "payload too large" and a request sent with the wrong content type answers "unsupported media type", instead of both arriving as a generic validation error that gave a client nothing to act on. `[improvement, fix]`
+- **Scanning for trade candidates is faster on creator-filtered rules and honest about how much it looked at**: The Trading Brain's "Scan for matches" preview shows the live launches your rule would buy right now, each with a real quote and a real safety verdict, and it never trades on its own. Three fixes. A rule that filters on the creator's track record has to look that record up over the network, and the scan was buying that lookup for every launch in the feed page, including ones it had already rejected for being too old or too small; it now pays for a creator lookup only when the rest of the rule already likes the coin, which is the difference between a scan that returns and one that crawls. The result said it had scanned the whole feed page even though it stops as soon as it has priced six matches, so the count overstated the work behind the answer; it now reports what it actually examined alongside the size of the page it read from. And an agent's Solana address is a field you can edit, so a value that is not a real address turned the preview into a server error rather than a scan; the safety check now resolves that address itself and the scan completes. The scan also gained its own per-owner limit, because every match it prices costs a live on-chain quote and a safety simulation. Separately, when the Trading Brain refuses something, the panel now shows the reason the server sent instead of a generic "Scan failed", so a rate limit, a kill switch, or an unreachable launch feed each read as themselves. `[fix, improvement]`
- **Seeding an agent from GitHub is locked to your own click, and a mistyped pick no longer costs you six hours**: Three fixes to the GitHub memory lane, the one that reads the profile, repositories, and READMEs you tick and distills them into what your agent knows about your work. First: writing or deleting those memories now requires the one-time token the site attaches to your own actions, so another site cannot make your browser re-seed or wipe an agent behind your back. Every neighbouring memory action already worked this way; this one did not. Second: seeding is allowed once every six hours per agent, and that window used to be spent by attempts that never read anything, so ticking nothing and pressing Seed, or picking a repository that had been renamed since the list loaded, locked you out for six hours over a correctable mistake. The window is now taken only once your selection checks out, immediately before anything is actually read. Third: when every model provider is busy at once, the seed used to fail with a bare internal error and a support reference; it now says plainly that nothing was read, that your existing memories are untouched, and roughly how long until you can try again. (`/docs/github-memory-seeding`) `[security, fix]`
- **Self-hosting docs no longer hand you a command that wipes your environment**: The deployment guide told self-hosters to set Cloud Run environment variables with `gcloud run services update --set-env-vars`. That flag replaces the service environment wholesale, so following the instruction for a single key silently deletes every other variable the service had. The guide now uses `--update-env-vars` and says plainly why. Four more corrections landed in the same sweep across the deployment, configuration and contributing pages: the Avaturn signup link and the GitHub Discussions links were dead (Discussions are not enabled on the repository, so bug reports and design questions both go to Issues); the in-browser avatar builder was documented as needing its own hosted origin in production when the normal build already serves it same-origin at /avatar-studio; and three counts that had drifted from the code (cron jobs, MCP server packages, contract tests) were replaced with pointers to the files that hold the real numbers. (`/docs/deployment`) `[docs, fix]`
+- **Sending $THREE from the wallet works, and swaps stopped failing outright**: Two things were broken in the transaction builder behind the in-app wallet and the chat wallet tools. Sending any Token-2022 coin, which includes $THREE itself and every pump.fun-era launch, failed with a generic server error: the builder assumed the older token program and never asked the chain which one actually owns the mint. It reads that from the chain now and signs against the right program, so a $THREE transfer builds, and it opens the recipient's token account in the same transaction when they do not have one yet. Swaps had been failing entirely because they still called a Jupiter address that no longer exists anywhere on the internet; they now go through the same Jupiter client the rest of the platform uses, and a real quote comes back. Alongside that, mistakes in what you send are finally answered as mistakes instead of a support reference: a mistyped address, an address that is not a token, a memo that is too long, a signature that is not really a signature, or a balance that is too small each come back naming what is wrong, before your wallet ever asks you to approve something that could only fail. Amounts are also converted with exact decimal math now, so no transfer is off by a rounding error. `[fix]`
- **The 3D API and agent manifest references now match what the endpoints actually return**: The agent manifest page told you to validate a manifest with assertValid from @three-ws/avatar-schema. That package validates avatar manifests (mesh, skeleton, owner), not agent manifests, so the sample always threw. It now shows loadManifest from the published bundle, running against a live agent, and says plainly which document the avatar schema covers. On the 3D API page, the sample responses showed a model URL shape the service never returns, the inspect example was a stale capture of a model that has since been re-exported, and the Forge Pro tier table claimed draft and standard generations come back with no textures when every tier bakes them (1K, 2K, and 4K plus PBR at high). All three are corrected against live calls, and the page now explains why browser code should load a generated GLB through the first-party CDN path rather than the object store URL directly. The prompt art-director note is confirmed accurate and the code comment that contradicted it was fixed. (`/docs/3d-api`) `[fix, docs]`
- **The 3D pipeline docs stop telling you to run a command that does not exist**: Every paid stage on the 3D asset pipeline page (rig, remesh, game-ready, stylize, background removal) showed you how to pay for it by running npx @x402/fetch. There is no such command: that package publishes a library, not a CLI, so anyone who copied a sample got a could-not-determine-executable error and no asset. The samples are now the real thing: an unpaid curl that returns the live 402 challenge and costs nothing, plus one Node snippet that wraps fetch with our published @three-ws/x402-fetch buyer and actually settles. The end-to-end generate, rig and game-ready walkthrough was rewritten the same way and now polls the forge job with the fields the API really returns. The page also stops promising a specific settlement network, because the 402 challenge names the networks itself. Alongside it: the changelog page CDN pinning table listed four alias URLs that all 404 and pointed at an integrity file for a version that no longer publishes one; the AgenC page opening sentence linked the word AgenC to a different protocol page; and the vanity protocol spec showed a stale copy of the service key document, which now matches what the live endpoint serves. (`/docs/3d-pipeline`) `[docs, fix]`
- **The AgenC task room explains itself now, instead of showing a wall of raw error text**: The task room renders every task a wallet has posted on the AgenC coordination protocol as a 3D agent driven by its live on-chain state. It has been rebuilt around the moments where it used to leave you stuck. An unreadable wallet address, a Solana outage, and a dropped connection all used to print the raw server reply into an otherwise empty page; each now gets its own explanation, a Retry button, and a link to the docs on posting a task, and the room keeps retrying by itself when the fault is upstream and stops when it is something only you can fix. A wallet with no tasks says so and offers to check the other cluster instead of leaving you guessing. While a load is in flight you get skeleton cards rather than the word loading, and a line above the grid tells you how many tasks are showing, on which cluster, and when they were last refreshed. Card status colors now match the states the chain actually reports, so a task in progress or awaiting validation is no longer left uncolored, and each card links to its account on Solana Explorer. On a phone the wallet field no longer runs off the edge of the screen, the title no longer sits under the site logo, both form fields are labelled for screen readers, and every control has a visible focus ring. The room also stops running a 3D viewer for every card at once: avatars load as their cards come into view, up to eight at a time, and are released when you scroll past, which keeps a large board from stalling the browser and stops off-screen cards polling the chain for nothing. (`/agenc/room`) `[improvement, fix]`
@@ -39,6 +42,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr
- **The Agent Exchange stops offering a purchase its wallet cannot pay for**: On /agent-exchange two 3D agents buy and sell live crypto intel, and the buyer settles $0.01 of real USDC on Solana for every signal. The page already warned you when the buyer's wallet was too empty to settle, but it left the Buy intel button live anyway, so the only thing a click could produce was a failed payment. The button now turns itself off and says why, and the warning carries a Check again button, so a wallet you fund while the page is open recovers without a reload. The balance is also re-read after every purchase, so a settlement that empties the wallet is reflected immediately instead of one click too late. When the balance check itself does not answer, the page used to say nothing at all and quietly log a browser error; it now tells you the balance is unknown and offers the same retry. Two smaller fixes came with it: the page title and the buy button were being rewritten at load time from the translation catalog, which had drifted from the page and still carried the old punctuation, now corrected in all 85 languages; and the two avatar frames were keyboard stops that did nothing and showed no focus outline, so they are out of the tab order and the topic chips and buy button are two tabs closer for anyone navigating by keyboard. (`/agent-exchange`) `[fix, improvement]`
- **The agent-payment and MCP docs now show the code that actually ships**: Three developer docs had drifted from the code they document, in ways that cost a reader real time. The Payment Sessions walkthrough, which is the guide for giving an agent a budget instead of a wallet key, quoted five snippets that no longer match the source: the branch that refuses a payment when the budget will not cover it, the host-allowlist check (which has moved into a shared module so the dry-run simulator and the live enforcement can never disagree), the expiry sweep that refunds unspent budget, the dollars-to-atomic-units helper, and a column missing from the table definition. All five now match the shipped code line for line, and the page links the two source files it had not been pointing at. The MCP article listed the Solana vanity grinder at up to $0.50 scaled by the work done; it is a flat $0.05 per successful grind, and its setup example set a wallet variable the package does not read, so anyone copying it would have configured a payout address that was silently ignored. That example now shows only the variable that works, and says plainly that settlement is USDC on Solana mainnet. The IBM Granite forecasting example showed three data points for a tool that requires at least sixty-four, so a copied sample was guaranteed to be rejected; it now says so. (`/docs/aws-builder-center-agent-payment-sessions`) `[docs, fix]`
- **The Alibaba Cloud MCP server starts now, and five MCP packages document how to import them**: The @three-ws/alibaba-cloud-mcp package, which lets an agent use Qwen chat, embeddings, and model discovery on your own Alibaba Cloud key, could not start at all. Two faults, both on the first line of use: the check for whether the file was launched directly crashed before the server ever opened, and the three tools were registered with a schema format the MCP library rejects. Both are fixed, so the server now boots, advertises its tools, and answers a client. The payment-sessions MCP package had a documentation fault with the same cost: its quick start told you to set your session variable to the whole cookie including the name, which the server then wrapped in the cookie name again, so every session-management call came back unauthorized. It now says to use the cookie value, and ships its two runnable examples inside the published package instead of only in the repository. Five packages (payment sessions, Agora, alerts, the assistant widget, and Alibaba Cloud) gained a Programmatic use section showing the exact code to import their tools into a host of your own, and the sniper package's HTTP table now lists every endpoint it actually serves, including the paid close-position route it had left out. `[fix, sdk, docs]`
+- **The Duplicate button on your widgets works again**: Duplicating a widget from the dashboard failed every single time. The clone request never gave the new widget an identifier, and because the database requires one, the copy was rejected before it was written and the page showed only a generic server error with a support reference. A second, correct copy of the same clone logic was already in the codebase and the route simply was not using it; the route now runs that one, so duplicating gives you a real new widget with its own id, its own name ending in (copy), and the original's type, look, avatar and visibility carried over. The duplicate request also now carries the same cross-site request protection every other widget change already had, and it accepts an API key with write access, so you can clone a widget from a script as well as from the dashboard. Two smaller corrections travelled with it. When no chat provider is configured and the platform answers a visitor with its own placeholder line, that message is no longer filed in your transcript as though a model had written it. And chatting with one of the showcase widgets in the public gallery no longer tries to file a transcript against a widget that does not exist, which failed on every message. The developer reference now documents duplicate, stats, chat, transcripts and the knowledge base, all of which were live but undocumented. (`/dashboard/widgets`) `[fix, docs]`
- **The embed and sharing tutorials now describe the surfaces that actually exist**: An audit of eight beginner tutorials found several describing features the platform does not have. The avatar-swap tutorial sent readers to Widget Studio for a body swap it cannot do, through a gallery with filters, preview buttons, and a 'Bust cache' save dialog that were never built; it now documents the real one-click swap in the agent editor's Outfit panel, and explains why nothing needs a cache purge. The sharing tutorial claimed rich social previews came from the plain agent URL, which actually serves a generic card, and described a headless renderer, a 24-hour image cache, a 'Refresh preview image' button, and a private-profile toggle that do not exist; it now points at the real share URL that carries the agent's name, description, and card, and explains what genuinely controls discoverability. The AR tutorial's iframe example used an address that returns 404 for an avatar id. The embed quickstart showed an agent ID in the wrong format, overstated the bundle size, and had the effect of the shadow DOM backwards. The docs-world tutorial gained the search palette it never mentioned, and the greeting tutorial now warns that the editor's Greeting field is not what makes an embed talk. Five page descriptions were corrected too, including one promising knobs the tutorial never covered. (`/tutorials/swap-avatar-in-studio`) `[docs, fix]`
- **The embed tutorials now name the attribute that actually hides the built-in chat**: Several tutorials told you to set avatar-chat="off" to hide an agent's built-in chat input. It does not do that: it moves the avatar out of the chat column and lays the chat out as a plain bottom bar, leaving the input on screen. The multi-agent walkthrough leaned on it to keep its behind-the-scenes stage-director messages hidden, so anyone following it verbatim saw those messages leak into the visible chat. The affected tutorials now use chat="off", the real bare-avatar switch, and note that the brain still boots behind it so say(), ask(), and the event stream keep working. The same accuracy pass corrected the walking-avatar leaderboard example, which read fields the API never returns and so always rendered an empty top-walkers list, and the JavaScript API event table, which named the wrong key for the skill a tool-call event reports. (`/tutorials/web-component-end-to-end`) `[fix, docs]`
- **The embodied AgenC demo hands you a live task, and reacts to the state a claimed task is actually in**: The /agenc/embodied page binds a 3D agent to a real AgenC task on Solana, and until now it opened on an empty input box: it needed a task account address and offered no way anywhere on the page to find one. It now lists real tasks three.ws itself posted, claimed, and settled on-chain, newest first, so the demo works the moment it loads; a new public read, /api/agenc/recent-tasks, serves that list. Two things it showed were also wrong. The scene coloured itself for a state named Claimed, which the chain has never used: a claimed task is In Progress on-chain, so the halo, the badge, and the per-state animation switch all sat inert through the one transition the demo exists to show. And the page named a program address that no read has touched since the protocol's interface moved; it now shows the program each live read actually ran against. Pasting an address that holds something other than a task used to report a server error, as though the platform were broken, rather than saying no such task exists there; that is now a plain not-found, with the page telling you to check the address or switch cluster. The panel has designed loading, empty, and error states throughout, the form fields have real labels, the layout no longer scrolls sideways on a phone, and a task that cannot be read is retried with a backoff instead of being re-requested every four seconds forever. (`/agenc/embodied`) `[fix, improvement, feature]`
diff --git a/api/tournaments/[id].js b/api/tournaments/[id].js
index a370c6e97..a7db26dc1 100644
--- a/api/tournaments/[id].js
+++ b/api/tournaments/[id].js
@@ -43,10 +43,21 @@ async function resolveUser(req) {
return null;
}
+/**
+ * The id and the action, from the route params rather than the path.
+ *
+ * Both runtimes hand them over as query values: the filesystem resolver merges
+ * `[id]`/`[action]` params into req.query, and the vercel.json rewrite carries them
+ * as `?id=..&action=..` while rewriting the PATH to the literal
+ * /api/tournaments/[id]/[action]. Reading the path first would therefore see the
+ * placeholder `[id]` behind the rewrite and answer 400 for every valid request.
+ */
function parseRoute(req) {
const url = new URL(req.url, `http://${req.headers.host || 'x'}`);
const parts = url.pathname.split('/').filter(Boolean); // ['api','tournaments',id,sub]
- return { id: parts[2] || '', sub: parts[3] || null, url };
+ const id = String(req.query?.id ?? parts[2] ?? '');
+ const sub = req.query?.action ?? parts[3] ?? null;
+ return { id, sub: sub ? String(sub) : null, url };
}
export default wrap(async (req, res) => {
diff --git a/data/changelog.json b/data/changelog.json
index b14d5a168..a1c3319a7 100644
--- a/data/changelog.json
+++ b/data/changelog.json
@@ -1,6 +1,33 @@
{
"$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-08-15",
+ "title": "Scanning for trade candidates is faster on creator-filtered rules and honest about how much it looked at",
+ "summary": "The Trading Brain's \"Scan for matches\" preview shows the live launches your rule would buy right now, each with a real quote and a real safety verdict, and it never trades on its own. Three fixes. A rule that filters on the creator's track record has to look that record up over the network, and the scan was buying that lookup for every launch in the feed page, including ones it had already rejected for being too old or too small; it now pays for a creator lookup only when the rest of the rule already likes the coin, which is the difference between a scan that returns and one that crawls. The result said it had scanned the whole feed page even though it stops as soon as it has priced six matches, so the count overstated the work behind the answer; it now reports what it actually examined alongside the size of the page it read from. And an agent's Solana address is a field you can edit, so a value that is not a real address turned the preview into a server error rather than a scan; the safety check now resolves that address itself and the scan completes. The scan also gained its own per-owner limit, because every match it prices costs a live on-chain quote and a safety simulation. Separately, when the Trading Brain refuses something, the panel now shows the reason the server sent instead of a generic \"Scan failed\", so a rate limit, a kill switch, or an unreachable launch feed each read as themselves.",
+ "tags": [
+ "fix",
+ "improvement"
+ ]
+ },
+ {
+ "date": "2026-08-15",
+ "title": "Sending $THREE from the wallet works, and swaps stopped failing outright",
+ "summary": "Two things were broken in the transaction builder behind the in-app wallet and the chat wallet tools. Sending any Token-2022 coin, which includes $THREE itself and every pump.fun-era launch, failed with a generic server error: the builder assumed the older token program and never asked the chain which one actually owns the mint. It reads that from the chain now and signs against the right program, so a $THREE transfer builds, and it opens the recipient's token account in the same transaction when they do not have one yet. Swaps had been failing entirely because they still called a Jupiter address that no longer exists anywhere on the internet; they now go through the same Jupiter client the rest of the platform uses, and a real quote comes back. Alongside that, mistakes in what you send are finally answered as mistakes instead of a support reference: a mistyped address, an address that is not a token, a memo that is too long, a signature that is not really a signature, or a balance that is too small each come back naming what is wrong, before your wallet ever asks you to approve something that could only fail. Amounts are also converted with exact decimal math now, so no transfer is off by a rounding error.",
+ "tags": [
+ "fix"
+ ]
+ },
+ {
+ "date": "2026-08-15",
+ "title": "Rotating or revoking an x402 API key now requires a proof the request came from you",
+ "summary": "The billing page's rotate and revoke buttons destroy a live API credential, but the endpoint behind them accepted any request that carried your session cookie. A page on another site could have posted to it and killed a working key without you ever seeing the response. Both actions now require a single-use token the page fetches for each write, and the page tells you plainly when a token has gone stale or you have tried too often. Rotating also mints the replacement key before retiring the old one, so a failure part way through can no longer leave you with no key at all.",
+ "tags": [
+ "security",
+ "fix"
+ ],
+ "link": "/billing/keys"
+ },
{
"date": "2026-08-15",
"title": "The Duplicate button on your widgets works again",
@@ -135,7 +162,7 @@
{
"date": "2026-08-15",
"title": "Asking for a voice that does not exist now tells you so, instead of quietly speaking in a different one",
- "summary": "The voice API accepts a provider and a voice id from the voice catalog. If the id was not one that provider actually has, nothing said so: the request was answered with audio rendered in that lane's default voice, and on the metered lanes it was billed, so a single typo in a voice id came back as a stranger's voice at full price with a success status. A well-formed id for a voice that had been removed took the opposite route and failed as a server error, which reads as our fault and tells a client to retry something that will never work. Both now return a plain rejection that names the id you sent and the catalog address to pick a real one from, and that check runs before anything is charged. Leaving the voice id out still gets you the lane default on purpose. Asking the catalog for a provider that does not exist used to return an empty list that was indistinguishable from a provider being down; it now says which providers exist. ElevenLabs voices, whose catalog grows every time you clone or add one, are still decided by ElevenLabs, but an id it rejects is reported as your request being wrong rather than ours, with any charge refunded first. Voice cloning also now asks who you are before reporting anything about how this server is configured.",
+ "summary": "The voice API accepts a provider and a voice id from the voice catalog. If the id was not one that provider actually has, nothing said so: the request was answered with audio rendered in that lane's default voice, and on the metered lanes it was billed, so a single typo in a voice id came back as a stranger's voice at full price with a success status. A well-formed id for a voice that had been removed took the opposite route and failed as a server error, which reads as our fault and tells a client to retry something that will never work. Both now return a plain rejection that names the id you sent and the catalog address to pick a real one from, and that check runs before anything is charged. Leaving the voice id out still gets you the lane default on purpose. Asking the catalog for a provider that does not exist used to return an empty list that was indistinguishable from a provider being down; it now says which providers exist. ElevenLabs voices, whose catalog grows every time you clone or add one, are still decided by ElevenLabs, but an id it rejects is reported as your request being wrong rather than ours, with any charge refunded first. Voice cloning also now asks who you are before reporting anything about how this server is configured. In the same pass, a key ElevenLabs turns down when you list your voices or browse the public voice library now comes back as your key being rejected, so the page can ask you for a new one, instead of a gateway error that invites a retry which can never succeed.",
"tags": [
"fix",
"improvement"
diff --git a/prompts/swarm-100/api-tournaments-01.md b/prompts/swarm-100/api-tournaments-01.md
deleted file mode 100644
index c23d851a9..000000000
--- a/prompts/swarm-100/api-tournaments-01.md
+++ /dev/null
@@ -1,102 +0,0 @@
-# API audit: api/tournaments batch 01 (2 files)
-
-How to run: paste this file's repo path into a fresh Claude Code chat in this
-repository and say "run this work order". This file is fully self-contained:
-it depends on no other prompt file anywhere. If neighboring files in
-prompts/swarm-100/ are gone, that work is done; if present, ignore them.
-Every claim below rots; step 0 re-measures, and what you measure wins.
-
-## Operating clause (binding)
-
-- Read CLAUDE.md first. Its rules override everything, including this file.
-- Finish 100% in this session. Never end the turn with a question, an option
- list, or an unexecuted plan. A judgment call goes in one line of the final
- report; it never becomes a question that halts work.
-- The only permitted stops are the CLAUDE.md stop-and-ask gates: spending real
- funds or any irreversible on-chain write, git push or a production deploy,
- committing content that references a crypto project other than $THREE, and
- destroying unrecoverable data.
-- No mocks, no fake data, no placeholder stubs, no unfinished-work markers, no
- commented-out code. Real APIs and real integrations only.
-- The em-dash and en-dash characters are banned in everything you write.
-- Concurrent agents share this worktree: stage explicit paths only (never a
- bare add-everything), and commit finished work promptly.
-- Before committing, run: npm run check:rules -- --paths <files you touched>.
- It must exit 0.
-
-## Step 0: re-derive the current state
-
-1. Confirm each file below still exists; deleted ones are done, skip them.
-2. For each, decide routability: grep its path in vercel.json and read how
- server/index.mjs maps filesystem handlers. Routed files get an endpoint
- audit; internal modules get a code and test audit.
-3. Start a local server for endpoint checks: node server/index.mjs with .env
- loaded, on a free PORT if 3000 is busy.
-
-## Task: audit these api files, then fix everything found
-
-Files in this batch:
-
-- api/tournaments/[id].js
-- api/tournaments/index.js
-
-For every routed handler:
-
-1. Exercise it with curl against the local server: the success path returns
- real data with the correct status; malformed input returns a 4xx JSON
- error, never a stack trace or an HTML error page; auth is enforced where
- the code intends it; CORS matches neighboring handlers.
-2. Hard-rule scan: no mock fallbacks, no fake-data arrays, no stubbed
- responses, no unfinished markers. Errors are handled at the boundary and
- internal code trusts itself.
-3. Do not spend funds or sign anything on-chain while probing. Payment and
- trading handlers get their validation and error paths exercised, never a
- live settlement.
-
-For every internal (non-routed) module:
-
-4. Something must import it; if nothing does, delete it as dead code (verify
- with a repo-wide grep first).
-5. Its main path and one failure path must be covered in tests/; add the
- missing test if not.
-
-## Definition of done
-
-- [ ] Every listed file has recorded evidence: a curl transcript for routed
- handlers, a passing test or a deletion for internal modules.
-- [ ] Zero hard-rule violations remain in these files.
-- [ ] vitest run passes; npm run check:rules -- --paths <touched files>
- exits 0.
-
-## Never blocked
-
-| Blocker | Resolution (act, do not ask) |
-|---|---|
-| Missing env var or credential | Check .env and .env.local, then the Cloud Run service env, then Secret Manager (the CLAUDE.md self-unblock playbook has the exact commands). If it truly exists nowhere, wire the code fully behind the env var, prove the wiring with a dry run, and name the single missing var in the report. |
-| gcloud not on PATH | Run: export PATH="$HOME/google-cloud-sdk/bin:$PATH" |
-| Dev server port 3000 busy | Another agent may be serving this repo; probe it and reuse if so. Otherwise start your own on a free port: npx vite --port 3101 |
-| Playwright browser missing | npx playwright install chromium |
-| A surface needs a signed-in user | Register a fresh account through the real /register flow against the real API and use it. Never mock the session. |
-| A defect sits in code you did not touch | Fix it if it blocks a Definition of done line (root cause it, never mask it). Otherwise note it in the report and continue. |
-| An unrelated test is red | Same rule. Never pipe npm test through tail; it masks exit codes. |
-
-## Close out (required)
-
-1. Verify every Definition of done line with the actual command output in
- front of you. Never claim a line you did not verify.
-2. Commit with explicit paths and a subject that describes the diff (house
- style: type(scope): what changed and why a reader cares).
-3. Delete this prompt file in that same commit:
-
- git rm prompts/swarm-100/api-tournaments-01.md
-
- The shrinking directory is this campaign's only progress ledger; there is
- no progress log to update.
-4. Final report: what step 0 measured, what changed (file list), evidence per
- Definition of done line, and any one-line judgment calls. No trailing
- questions, no unexecuted plans.
-
-If a line genuinely cannot pass inside this session (an external party must
-respond, or an owner-gated action is the final step), finish everything else,
-leave this file in place, and state exactly which line remains and who owns
-it. Never delete this file on a partial.
diff --git a/prompts/swarm-100/api-trading-01.md b/prompts/swarm-100/api-trading-01.md
deleted file mode 100644
index e6d5bb7e7..000000000
--- a/prompts/swarm-100/api-trading-01.md
+++ /dev/null
@@ -1,101 +0,0 @@
-# API audit: api/trading batch 01 (1 files)
-
-How to run: paste this file's repo path into a fresh Claude Code chat in this
-repository and say "run this work order". This file is fully self-contained:
-it depends on no other prompt file anywhere. If neighboring files in
-prompts/swarm-100/ are gone, that work is done; if present, ignore them.
-Every claim below rots; step 0 re-measures, and what you measure wins.
-
-## Operating clause (binding)
-
-- Read CLAUDE.md first. Its rules override everything, including this file.
-- Finish 100% in this session. Never end the turn with a question, an option
- list, or an unexecuted plan. A judgment call goes in one line of the final
- report; it never becomes a question that halts work.
-- The only permitted stops are the CLAUDE.md stop-and-ask gates: spending real
- funds or any irreversible on-chain write, git push or a production deploy,
- committing content that references a crypto project other than $THREE, and
- destroying unrecoverable data.
-- No mocks, no fake data, no placeholder stubs, no unfinished-work markers, no
- commented-out code. Real APIs and real integrations only.
-- The em-dash and en-dash characters are banned in everything you write.
-- Concurrent agents share this worktree: stage explicit paths only (never a
- bare add-everything), and commit finished work promptly.
-- Before committing, run: npm run check:rules -- --paths <files you touched>.
- It must exit 0.
-
-## Step 0: re-derive the current state
-
-1. Confirm each file below still exists; deleted ones are done, skip them.
-2. For each, decide routability: grep its path in vercel.json and read how
- server/index.mjs maps filesystem handlers. Routed files get an endpoint
- audit; internal modules get a code and test audit.
-3. Start a local server for endpoint checks: node server/index.mjs with .env
- loaded, on a free PORT if 3000 is busy.
-
-## Task: audit these api files, then fix everything found
-
-Files in this batch:
-
-- api/trading/scan.js
-
-For every routed handler:
-
-1. Exercise it with curl against the local server: the success path returns
- real data with the correct status; malformed input returns a 4xx JSON
- error, never a stack trace or an HTML error page; auth is enforced where
- the code intends it; CORS matches neighboring handlers.
-2. Hard-rule scan: no mock fallbacks, no fake-data arrays, no stubbed
- responses, no unfinished markers. Errors are handled at the boundary and
- internal code trusts itself.
-3. Do not spend funds or sign anything on-chain while probing. Payment and
- trading handlers get their validation and error paths exercised, never a
- live settlement.
-
-For every internal (non-routed) module:
-
-4. Something must import it; if nothing does, delete it as dead code (verify
- with a repo-wide grep first).
-5. Its main path and one failure path must be covered in tests/; add the
- missing test if not.
-
-## Definition of done
-
-- [ ] Every listed file has recorded evidence: a curl transcript for routed
- handlers, a passing test or a deletion for internal modules.
-- [ ] Zero hard-rule violations remain in these files.
-- [ ] vitest run passes; npm run check:rules -- --paths <touched files>
- exits 0.
-
-## Never blocked
-
-| Blocker | Resolution (act, do not ask) |
-|---|---|
-| Missing env var or credential | Check .env and .env.local, then the Cloud Run service env, then Secret Manager (the CLAUDE.md self-unblock playbook has the exact commands). If it truly exists nowhere, wire the code fully behind the env var, prove the wiring with a dry run, and name the single missing var in the report. |
-| gcloud not on PATH | Run: export PATH="$HOME/google-cloud-sdk/bin:$PATH" |
-| Dev server port 3000 busy | Another agent may be serving this repo; probe it and reuse if so. Otherwise start your own on a free port: npx vite --port 3101 |
-| Playwright browser missing | npx playwright install chromium |
-| A surface needs a signed-in user | Register a fresh account through the real /register flow against the real API and use it. Never mock the session. |
-| A defect sits in code you did not touch | Fix it if it blocks a Definition of done line (root cause it, never mask it). Otherwise note it in the report and continue. |
-| An unrelated test is red | Same rule. Never pipe npm test through tail; it masks exit codes. |
-
-## Close out (required)
-
-1. Verify every Definition of done line with the actual command output in
- front of you. Never claim a line you did not verify.
-2. Commit with explicit paths and a subject that describes the diff (house
- style: type(scope): what changed and why a reader cares).
-3. Delete this prompt file in that same commit:
-
- git rm prompts/swarm-100/api-trading-01.md
-
- The shrinking directory is this campaign's only progress ledger; there is
- no progress log to update.
-4. Final report: what step 0 measured, what changed (file list), evidence per
- Definition of done line, and any one-line judgment calls. No trailing
- questions, no unexecuted plans.
-
-If a line genuinely cannot pass inside this session (an external party must
-respond, or an owner-gated action is the final step), finish everything else,
-leave this file in place, and state exactly which line remains and who owns
-it. Never delete this file on a partial.
diff --git a/prompts/swarm-100/api-user-01.md b/prompts/swarm-100/api-user-01.md
deleted file mode 100644
index 915c159a4..000000000
--- a/prompts/swarm-100/api-user-01.md
+++ /dev/null
@@ -1,106 +0,0 @@
-# API audit: api/user batch 01 (6 files)
-
-How to run: paste this file's repo path into a fresh Claude Code chat in this
-repository and say "run this work order". This file is fully self-contained:
-it depends on no other prompt file anywhere. If neighboring files in
-prompts/swarm-100/ are gone, that work is done; if present, ignore them.
-Every claim below rots; step 0 re-measures, and what you measure wins.
-
-## Operating clause (binding)
-
-- Read CLAUDE.md first. Its rules override everything, including this file.
-- Finish 100% in this session. Never end the turn with a question, an option
- list, or an unexecuted plan. A judgment call goes in one line of the final
- report; it never becomes a question that halts work.
-- The only permitted stops are the CLAUDE.md stop-and-ask gates: spending real
- funds or any irreversible on-chain write, git push or a production deploy,
- committing content that references a crypto project other than $THREE, and
- destroying unrecoverable data.
-- No mocks, no fake data, no placeholder stubs, no unfinished-work markers, no
- commented-out code. Real APIs and real integrations only.
-- The em-dash and en-dash characters are banned in everything you write.
-- Concurrent agents share this worktree: stage explicit paths only (never a
- bare add-everything), and commit finished work promptly.
-- Before committing, run: npm run check:rules -- --paths <files you touched>.
- It must exit 0.
-
-## Step 0: re-derive the current state
-
-1. Confirm each file below still exists; deleted ones are done, skip them.
-2. For each, decide routability: grep its path in vercel.json and read how
- server/index.mjs maps filesystem handlers. Routed files get an endpoint
- audit; internal modules get a code and test audit.
-3. Start a local server for endpoint checks: node server/index.mjs with .env
- loaded, on a free PORT if 3000 is busy.
-
-## Task: audit these api files, then fix everything found
-
-Files in this batch:
-
-- api/user/provider-keys.js
-- api/user/wallet/fund-agent.js
-- api/user/wallet/history.js
-- api/user/wallet/index.js
-- api/user/wallet/send.js
-- api/user/x402-subscriptions.js
-
-For every routed handler:
-
-1. Exercise it with curl against the local server: the success path returns
- real data with the correct status; malformed input returns a 4xx JSON
- error, never a stack trace or an HTML error page; auth is enforced where
- the code intends it; CORS matches neighboring handlers.
-2. Hard-rule scan: no mock fallbacks, no fake-data arrays, no stubbed
- responses, no unfinished markers. Errors are handled at the boundary and
- internal code trusts itself.
-3. Do not spend funds or sign anything on-chain while probing. Payment and
- trading handlers get their validation and error paths exercised, never a
- live settlement.
-
-For every internal (non-routed) module:
-
-4. Something must import it; if nothing does, delete it as dead code (verify
- with a repo-wide grep first).
-5. Its main path and one failure path must be covered in tests/; add the
- missing test if not.
-
-## Definition of done
-
-- [ ] Every listed file has recorded evidence: a curl transcript for routed
- handlers, a passing test or a deletion for internal modules.
-- [ ] Zero hard-rule violations remain in these files.
-- [ ] vitest run passes; npm run check:rules -- --paths <touched files>
- exits 0.
-
-## Never blocked
-
-| Blocker | Resolution (act, do not ask) |
-|---|---|
-| Missing env var or credential | Check .env and .env.local, then the Cloud Run service env, then Secret Manager (the CLAUDE.md self-unblock playbook has the exact commands). If it truly exists nowhere, wire the code fully behind the env var, prove the wiring with a dry run, and name the single missing var in the report. |
-| gcloud not on PATH | Run: export PATH="$HOME/google-cloud-sdk/bin:$PATH" |
-| Dev server port 3000 busy | Another agent may be serving this repo; probe it and reuse if so. Otherwise start your own on a free port: npx vite --port 3101 |
-| Playwright browser missing | npx playwright install chromium |
-| A surface needs a signed-in user | Register a fresh account through the real /register flow against the real API and use it. Never mock the session. |
-| A defect sits in code you did not touch | Fix it if it blocks a Definition of done line (root cause it, never mask it). Otherwise note it in the report and continue. |
-| An unrelated test is red | Same rule. Never pipe npm test through tail; it masks exit codes. |
-
-## Close out (required)
-
-1. Verify every Definition of done line with the actual command output in
- front of you. Never claim a line you did not verify.
-2. Commit with explicit paths and a subject that describes the diff (house
- style: type(scope): what changed and why a reader cares).
-3. Delete this prompt file in that same commit:
-
- git rm prompts/swarm-100/api-user-01.md
-
- The shrinking directory is this campaign's only progress ledger; there is
- no progress log to update.
-4. Final report: what step 0 measured, what changed (file list), evidence per
- Definition of done line, and any one-line judgment calls. No trailing
- questions, no unexecuted plans.
-
-If a line genuinely cannot pass inside this session (an external party must
-respond, or an owner-gated action is the final step), finish everything else,
-leave this file in place, and state exactly which line remains and who owns
-it. Never delete this file on a partial.
diff --git a/public/changelog.json b/public/changelog.json
index b4dab9103..9106c2ebf 100644
--- a/public/changelog.json
+++ b/public/changelog.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-08-15T15:48:31.663Z",
+ "generated_at": "2026-08-15T15:52:49.645Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json",
"site": {
"name": "three.ws",
@@ -139,7 +139,7 @@
"date": "2026-08-15",
"type": "update",
"title": "Asking for a voice that does not exist now tells you so, instead of quietly speaking in a different one",
- "summary": "The voice API accepts a provider and a voice id from the voice catalog. If the id was not one that provider actually has, nothing said so: the request was answered with audio rendered in that lane's default voice, and on the metered lanes it was billed, so a single typo in a voice id came back as a stranger's voice at full price with a success status. A well-formed id for a voice that had been removed took the opposite route and failed as a server error, which reads as our fault and tells a client to retry something that will never work. Both now return a plain rejection that names the id you sent and the catalog address to pick a real one from, and that check runs before anything is charged. Leaving the voice id out still gets you the lane default on purpose. Asking the catalog for a provider that does not exist used to return an empty list that was indistinguishable from a provider being down; it now says which providers exist. ElevenLabs voices, whose catalog grows every time you clone or add one, are still decided by ElevenLabs, but an id it rejects is reported as your request being wrong rather than ours, with any charge refunded first. Voice cloning also now asks who you are before reporting anything about how this server is configured.",
+ "summary": "The voice API accepts a provider and a voice id from the voice catalog. If the id was not one that provider actually has, nothing said so: the request was answered with audio rendered in that lane's default voice, and on the metered lanes it was billed, so a single typo in a voice id came back as a stranger's voice at full price with a success status. A well-formed id for a voice that had been removed took the opposite route and failed as a server error, which reads as our fault and tells a client to retry something that will never work. Both now return a plain rejection that names the id you sent and the catalog address to pick a real one from, and that check runs before anything is charged. Leaving the voice id out still gets you the lane default on purpose. Asking the catalog for a provider that does not exist used to return an empty list that was indistinguishable from a provider being down; it now says which providers exist. ElevenLabs voices, whose catalog grows every time you clone or add one, are still decided by ElevenLabs, but an id it rejects is reported as your request being wrong rather than ours, with any charge refunded first. Voice cloning also now asks who you are before reporting anything about how this server is configured. In the same pass, a key ElevenLabs turns down when you list your voices or browse the public voice library now comes back as your key being rejected, so the page can ask you for a new one, instead of a gateway error that invites a retry which can never succeed.",
"link": "/docs/api-reference",
"tags": [
"fix",
@@ -241,6 +241,17 @@
"security"
]
},
+ {
+ "date": "2026-08-15",
+ "type": "update",
+ "title": "Rotating or revoking an x402 API key now requires a proof the request came from you",
+ "summary": "The billing page's rotate and revoke buttons destroy a live API credential, but the endpoint behind them accepted any request that carried your session cookie. A page on another site could have posted to it and killed a working key without you ever seeing the response. Both actions now require a single-use token the page fetches for each write, and the page tells you plainly when a token has gone stale or you have tried too often. Rotating also mints the replacement key before retiring the old one, so a failure part way through can no longer leave you with no key at all.",
+ "link": "/billing/keys",
+ "tags": [
+ "security",
+ "fix"
+ ]
+ },
{
"date": "2026-08-15",
"type": "update",
@@ -252,6 +263,17 @@
"fix"
]
},
+ {
+ "date": "2026-08-15",
+ "type": "update",
+ "title": "Scanning for trade candidates is faster on creator-filtered rules and honest about how much it looked at",
+ "summary": "The Trading Brain's \"Scan for matches\" preview shows the live launches your rule would buy right now, each with a real quote and a real safety verdict, and it never trades on its own. Three fixes. A rule that filters on the creator's track record has to look that record up over the network, and the scan was buying that lookup for every launch in the feed page, including ones it had already rejected for being too old or too small; it now pays for a creator lookup only when the rest of the rule already likes the coin, which is the difference between a scan that returns and one that crawls. The result said it had scanned the whole feed page even though it stops as soon as it has priced six matches, so the count overstated the work behind the answer; it now reports what it actually examined alongside the size of the page it read from. And an agent's Solana address is a field you can edit, so a value that is not a real address turned the preview into a server error rather than a scan; the safety check now resolves that address itself and the scan completes. The scan also gained its own per-owner limit, because every match it prices costs a live on-chain quote and a safety simulation. Separately, when the Trading Brain refuses something, the panel now shows the reason the server sent instead of a generic \"Scan failed\", so a rate limit, a kill switch, or an unreachable launch feed each read as themselves.",
+ "link": null,
+ "tags": [
+ "fix",
+ "improvement"
+ ]
+ },
{
"date": "2026-08-15",
"type": "update",
@@ -274,6 +296,16 @@
"fix"
]
},
+ {
+ "date": "2026-08-15",
+ "type": "update",
+ "title": "Sending $THREE from the wallet works, and swaps stopped failing outright",
+ "summary": "Two things were broken in the transaction builder behind the in-app wallet and the chat wallet tools. Sending any Token-2022 coin, which includes $THREE itself and every pump.fun-era launch, failed with a generic server error: the builder assumed the older token program and never asked the chain which one actually owns the mint. It reads that from the chain now and signs against the right program, so a $THREE transfer builds, and it opens the recipient's token account in the same transaction when they do not have one yet. Swaps had been failing entirely because they still called a Jupiter address that no longer exists anywhere on the internet; they now go through the same Jupiter client the rest of the platform uses, and a real quote comes back. Alongside that, mistakes in what you send are finally answered as mistakes instead of a support reference: a mistyped address, an address that is not a token, a memo that is too long, a signature that is not really a signature, or a balance that is too small each come back naming what is wrong, before your wallet ever asks you to approve something that could only fail. Amounts are also converted with exact decimal math now, so no transfer is off by a rounding error.",
+ "link": null,
+ "tags": [
+ "fix"
+ ]
+ },
{
"date": "2026-08-15",
"type": "update",
@@ -363,6 +395,17 @@
"docs"
]
},
+ {
+ "date": "2026-08-15",
+ "type": "update",
+ "title": "The Duplicate button on your widgets works again",
+ "summary": "Duplicating a widget from the dashboard failed every single time. The clone request never gave the new widget an identifier, and because the database requires one, the copy was rejected before it was written and the page showed only a generic server error with a support reference. A second, correct copy of the same clone logic was already in the codebase and the route simply was not using it; the route now runs that one, so duplicating gives you a real new widget with its own id, its own name ending in (copy), and the original's type, look, avatar and visibility carried over. The duplicate request also now carries the same cross-site request protection every other widget change already had, and it accepts an API key with write access, so you can clone a widget from a script as well as from the dashboard. Two smaller corrections travelled with it. When no chat provider is configured and the platform answers a visitor with its own placeholder line, that message is no longer filed in your transcript as though a model had written it. And chatting with one of the showcase widgets in the public gallery no longer tries to file a transcript against a widget that does not exist, which failed on every message. The developer reference now documents duplicate, stats, chat, transcripts and the knowledge base, all of which were live but undocumented.",
+ "link": "/dashboard/widgets",
+ "tags": [
+ "fix",
+ "docs"
+ ]
+ },
{
"date": "2026-08-15",
"type": "update",
diff --git a/public/changelog.xml b/public/changelog.xml
index eddc78e07..47213e988 100644
--- a/public/changelog.xml
+++ b/public/changelog.xml
@@ -108,7 +108,7 @@
<guid isPermaLink="false">2026-08-15:Asking for a voice that does not exist now tells you so, instead of quietly speaking in a different one</guid>
<pubDate>Sat, 15 Aug 2026 12:00:00 GMT</pubDate>
<category>fix</category>
- <description>The voice API accepts a provider and a voice id from the voice catalog. If the id was not one that provider actually has, nothing said so: the request was answered with audio rendered in that lane's default voice, and on the metered lanes it was billed, so a single typo in a voice id came back as a stranger's voice at full price with a success status. A well-formed id for a voice that had been removed took the opposite route and failed as a server error, which reads as our fault and tells a client to retry something that will never work. Both now return a plain rejection that names the id you sent and the catalog address to pick a real one from, and that check runs before anything is charged. Leaving the voice id out still gets you the lane default on purpose. Asking the catalog for a provider that does not exist used to return an empty list that was indistinguishable from a provider being down; it now says which providers exist. ElevenLabs voices, whose catalog grows every time you clone or add one, are still decided by ElevenLabs, but an id it rejects is reported as your request being wrong rather than ours, with any charge refunded first. Voice cloning also now asks who you are before reporting anything about how this server is configured.</description>
+ <description>The voice API accepts a provider and a voice id from the voice catalog. If the id was not one that provider actually has, nothing said so: the request was answered with audio rendered in that lane's default voice, and on the metered lanes it was billed, so a single typo in a voice id came back as a stranger's voice at full price with a success status. A well-formed id for a voice that had been removed took the opposite route and failed as a server error, which reads as our fault and tells a client to retry something that will never work. Both now return a plain rejection that names the id you sent and the catalog address to pick a real one from, and that check runs before anything is charged. Leaving the voice id out still gets you the lane default on purpose. Asking the catalog for a provider that does not exist used to return an empty list that was indistinguishable from a provider being down; it now says which providers exist. ElevenLabs voices, whose catalog grows every time you clone or add one, are still decided by ElevenLabs, but an id it rejects is reported as your request being wrong rather than ours, with any charge refunded first. Voice cloning also now asks who you are before reporting anything about how this server is configured. In the same pass, a key ElevenLabs turns down when you list your voices or browse the public voice library now comes back as your key being rejected, so the page can ask you for a new one, instead of a gateway error that invites a retry which can never succeed.</description>
</item>
<item>
<title>Avatars can move their lips again: the Audio2Face lane is back</title>
@@ -182,6 +182,14 @@
<category>fix</category>
<description>Paying for a plan creates a quote, you send the funds, then the server checks the chain before it upgrades you. Three things in that path were wrong. The checkout side has always refused test-network quotes in production, because test-network dollars are free from a faucet, but the confirm side still let a caller name the test network itself, and it is the confirm side that decides which chain it looks at and which dollar it accepts. Both ends now read the same setting, so a production upgrade can only ever be settled by real funds on mainnet. Second, an Ethereum-side payment has to wait twelve blocks before it counts, which meant funds sent near the end of a session could land on-chain and then be refused for arriving late, with the money already gone; that lane now honors the same one-hour grace window the Solana lane has, so an on-chain payment is always claimable. Third, confirming an Ethereum payment could reach a Solana quote and mark it expired, and asking to buy a skill from a malformed agent id answered a generic server error instead of telling you what was wrong with the request.</description>
</item>
+ <item>
+ <title>Rotating or revoking an x402 API key now requires a proof the request came from you</title>
+ <link>https://three.ws/billing/keys</link>
+ <guid isPermaLink="false">2026-08-15:Rotating or revoking an x402 API key now requires a proof the request came from you</guid>
+ <pubDate>Sat, 15 Aug 2026 12:00:00 GMT</pubDate>
+ <category>security</category>
+ <description>The billing page's rotate and revoke buttons destroy a live API credential, but the endpoint behind them accepted any request that carried your session cookie. A page on another site could have posted to it and killed a working key without you ever seeing the response. Both actions now require a single-use token the page fetches for each write, and the page tells you plainly when a token has gone stale or you have tried too often. Rotating also mints the replacement key before retiring the old one, so a failure part way through can no longer leave you with no key at all.</description>
+ </item>
<item>
<title>Saving a big build no longer re-downloads the whole world first</title>
<link>https://three.ws/changelog</link>
@@ -190,6 +198,14 @@
<category>improvement</category>
<description>Every time you saved a world, the service fetched and re-parsed the entire previous version of that world just to check who owns it. On a large build that meant a full extra download and parse on each autosave, for a single ownership field. The check now reads only the small index record, so saves on big worlds are noticeably quicker and the storage layer does half the work. Two error replies also got honest labels: a build that exceeds the size cap now answers &quot;payload too large&quot; and a request sent with the wrong content type answers &quot;unsupported media type&quot;, instead of both arriving as a generic validation error that gave a client nothing to act on.</description>
</item>
+ <item>
+ <title>Scanning for trade candidates is faster on creator-filtered rules and honest about how much it looked at</title>
+ <link>https://three.ws/changelog</link>
+ <guid isPermaLink="false">2026-08-15:Scanning for trade candidates is faster on creator-filtered rules and honest about how much it looked at</guid>
+ <pubDate>Sat, 15 Aug 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>The Trading Brain's &quot;Scan for matches&quot; preview shows the live launches your rule would buy right now, each with a real quote and a real safety verdict, and it never trades on its own. Three fixes. A rule that filters on the creator's track record has to look that record up over the network, and the scan was buying that lookup for every launch in the feed page, including ones it had already rejected for being too old or too small; it now pays for a creator lookup only when the rest of the rule already likes the coin, which is the difference between a scan that returns and one that crawls. The result said it had scanned the whole feed page even though it stops as soon as it has priced six matches, so the count overstated the work behind the answer; it now reports what it actually examined alongside the size of the page it read from. And an agent's Solana address is a field you can edit, so a value that is not a real address turned the preview into a server error rather than a scan; the safety check now resolves that address itself and the scan completes. The scan also gained its own per-owner limit, because every match it prices costs a live on-chain quote and a safety simulation. Separately, when the Trading Brain refuses something, the panel now shows the reason the server sent instead of a generic &quot;Scan failed&quot;, so a rate limit, a kill switch, or an unreachable launch feed each read as themselves.</description>
+ </item>
<item>
<title>Seeding an agent from GitHub is locked to your own click, and a mistyped pick no longer costs you six hours</title>
<link>https://three.ws/docs/github-memory-seeding</link>
@@ -206,6 +222,14 @@
<category>docs</category>
<description>The deployment guide told self-hosters to set Cloud Run environment variables with `gcloud run services update --set-env-vars`. That flag replaces the service environment wholesale, so following the instruction for a single key silently deletes every other variable the service had. The guide now uses `--update-env-vars` and says plainly why. Four more corrections landed in the same sweep across the deployment, configuration and contributing pages: the Avaturn signup link and the GitHub Discussions links were dead (Discussions are not enabled on the repository, so bug reports and design questions both go to Issues); the in-browser avatar builder was documented as needing its own hosted origin in production when the normal build already serves it same-origin at /avatar-studio; and three counts that had drifted from the code (cron jobs, MCP server packages, contract tests) were replaced with pointers to the files that hold the real numbers.</description>
</item>
+ <item>
+ <title>Sending $THREE from the wallet works, and swaps stopped failing outright</title>
+ <link>https://three.ws/changelog</link>
+ <guid isPermaLink="false">2026-08-15:Sending $THREE from the wallet works, and swaps stopped failing outright</guid>
+ <pubDate>Sat, 15 Aug 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>Two things were broken in the transaction builder behind the in-app wallet and the chat wallet tools. Sending any Token-2022 coin, which includes $THREE itself and every pump.fun-era launch, failed with a generic server error: the builder assumed the older token program and never asked the chain which one actually owns the mint. It reads that from the chain now and signs against the right program, so a $THREE transfer builds, and it opens the recipient's token account in the same transaction when they do not have one yet. Swaps had been failing entirely because they still called a Jupiter address that no longer exists anywhere on the internet; they now go through the same Jupiter client the rest of the platform uses, and a real quote comes back. Alongside that, mistakes in what you send are finally answered as mistakes instead of a support reference: a mistyped address, an address that is not a token, a memo that is too long, a signature that is not really a signature, or a balance that is too small each come back naming what is wrong, before your wallet ever asks you to approve something that could only fail. Amounts are also converted with exact decimal math now, so no transfer is off by a rounding error.</description>
+ </item>
<item>
<title>The 3D API and agent manifest references now match what the endpoints actually return</title>
<link>https://three.ws/docs/3d-api</link>
@@ -270,6 +294,14 @@
<category>fix</category>
<description>The @three-ws/alibaba-cloud-mcp package, which lets an agent use Qwen chat, embeddings, and model discovery on your own Alibaba Cloud key, could not start at all. Two faults, both on the first line of use: the check for whether the file was launched directly crashed before the server ever opened, and the three tools were registered with a schema format the MCP library rejects. Both are fixed, so the server now boots, advertises its tools, and answers a client. The payment-sessions MCP package had a documentation fault with the same cost: its quick start told you to set your session variable to the whole cookie including the name, which the server then wrapped in the cookie name again, so every session-management call came back unauthorized. It now says to use the cookie value, and ships its two runnable examples inside the published package instead of only in the repository. Five packages (payment sessions, Agora, alerts, the assistant widget, and Alibaba Cloud) gained a Programmatic use section showing the exact code to import their tools into a host of your own, and the sniper package's HTTP table now lists every endpoint it actually serves, including the paid close-position route it had left out.</description>
</item>
+ <item>
+ <title>The Duplicate button on your widgets works again</title>
+ <link>https://three.ws/dashboard/widgets</link>
+ <guid isPermaLink="false">2026-08-15:The Duplicate button on your widgets works again</guid>
+ <pubDate>Sat, 15 Aug 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>Duplicating a widget from the dashboard failed every single time. The clone request never gave the new widget an identifier, and because the database requires one, the copy was rejected before it was written and the page showed only a generic server error with a support reference. A second, correct copy of the same clone logic was already in the codebase and the route simply was not using it; the route now runs that one, so duplicating gives you a real new widget with its own id, its own name ending in (copy), and the original's type, look, avatar and visibility carried over. The duplicate request also now carries the same cross-site request protection every other widget change already had, and it accepts an API key with write access, so you can clone a widget from a script as well as from the dashboard. Two smaller corrections travelled with it. When no chat provider is configured and the platform answers a visitor with its own placeholder line, that message is no longer filed in your transcript as though a model had written it. And chatting with one of the showcase widgets in the public gallery no longer tries to file a transcript against a widget that does not exist, which failed on every message. The developer reference now documents duplicate, stats, chat, transcripts and the knowledge base, all of which were live but undocumented.</description>
+ </item>
<item>
<title>The embed and sharing tutorials now describe the surfaces that actually exist</title>
<link>https://three.ws/tutorials/swap-avatar-in-studio</link>
diff --git a/public/features.json b/public/features.json
index d04a84b68..598eb4204 100644
--- a/public/features.json
+++ b/public/features.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-08-15T15:48:31.617Z",
+ "generated_at": "2026-08-15T15:52:49.588Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json",
"site": {
"name": "three.ws",
diff --git a/tests/arena-tournament-api.test.js b/tests/arena-tournament-api.test.js
index ea5fa47e1..e637e3d38 100644
--- a/tests/arena-tournament-api.test.js
+++ b/tests/arena-tournament-api.test.js
@@ -25,7 +25,7 @@ import { describe, it, expect, vi, beforeEach } from 'vitest';
import { fileURLToPath } from 'node:url';
import { join, relative } from 'node:path';
-import { resolveApi } from '../server/route-resolve.mjs';
+import { loadRouteTable, resolveApi, resolvePhase1 } from '../server/route-resolve.mjs';
import { threeToAtomics } from '../api/tournaments/index.js';
const db = vi.hoisted(() => ({ queries: [], conflict: true }));
@@ -73,6 +73,19 @@ describe('Arena tournament routes reach a handler', () => {
const hit = resolveApi(API_ROOT, ['tournaments', ID, 'join'], {});
expect(hit.params).toEqual({ id: ID, action: 'join' });
});
+
+ it('carries the id and action as query values through the vercel.json rewrite', () => {
+ // The rewrite replaces the PATH with the literal /api/tournaments/[id]/[action],
+ // so the handler must read both from the params. Anything that goes back to
+ // parsing them off the pathname answers 400 for every request behind Vercel.
+ const { phase1Routes } = loadRouteTable(join(REPO, 'vercel.json'));
+ const path = `/api/tournaments/${ID}/join`;
+ const hit = resolvePhase1(phase1Routes, { method: 'POST', headers: {}, url: path }, new URL(`http://x${path}`));
+
+ expect(hit.path).toBe('/api/tournaments/[id]/[action]');
+ expect(hit.extraQuery).toEqual({ id: ID, action: 'join' });
+ expect(resolve(hit.path)).toBe('api/tournaments/[id]/[action].js');
+ });
});
describe('threeToAtomics', () => {
diff --git a/vercel.json b/vercel.json
index d0f7368b1..2a4b3d330 100644
--- a/vercel.json
+++ b/vercel.json
@@ -27,6 +27,9 @@
"api/tournaments/[id].js": {
"maxDuration": 120
},
+ "api/tournaments/[id]/[action].js": {
+ "maxDuration": 120
+ },
"{api/agents/networth,api/avatars/from-forge,api/pay/execute,api/pay/simulate,api/cron/launcher-claimer,api/seed/synthesize,api/cron/x402-ring-tick}.js": {
"maxDuration": 60
},