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): publish the Coin Intelligence filter fix and rebuild the feeds

nirholase7c6cbfbae85
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 065462adf..4779696ce 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -8,6 +8,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr
- **A broken paid endpoint is no longer reported as a free one**: Payment sessions let you hand an agent a budget instead of a key, and two parts of that path judged an endpoint by one rule: if it did not ask for payment, the call was free. That is only true when the endpoint actually succeeded. A paid API answering 404, 400, or 500 was being scored as a free call, and the consequences ran in the wrong direction in both places. The dry run at /pay/simulator, whose whole job is to tell you in advance whether a budget and an allowlist will carry a workload, reported a plan as feasible at a cost of nothing when in fact every endpoint in it was erroring: free calls are never priced, never allowlist-checked, and never counted, so a wall of failures looked like a clean run. And an agent spending through a session got back a success envelope saying no payment was needed for an endpoint that had just failed on it. Both now separate the two cases: a real success with no payment challenge is still free and still costs nothing, while an error status is reported as an endpoint failure carrying the status the endpoint actually returned. No session is charged either way. The simulator lists each failing endpoint by name in its problems list and no longer calls the plan feasible. (`/pay/simulator`) `[fix]`
- **A market intelligence outage no longer tells you your own API key was rejected**: The two market intelligence reads in the unified API, recent narrative intel and momentum-ranked projects, pass a key we hold to the upstream provider; a caller needs no key at all. When that provider stopped accepting our key, both reads answered "unauthorized" with the provider's own wording, so an agent reading the response concluded its own credentials were bad and retried with different ones forever, when nothing on the caller's side was wrong. Both reads now say plainly that the service is temporarily unavailable because this deployment's upstream key was rejected, which is a status clients already know to retry rather than re-authenticate against. The older market intelligence endpoints always classified this correctly; the classification now lives in one place, so the two doors cannot drift apart again, and the error tables in the API reference list every code either one can return. (`/docs/api-reference`) `[fix, docs]`
+- **A Premium Data API pass you bought straight from your wallet now shows up on your billing page**: You can buy a pass without an account, paying from a Solana wallet on the Data API page. Do that, then sign in with the same wallet later, and billing showed you nothing: the pass was live, the API key worked, but the page insisted you had never bought anything. It was reading a single legacy address field on the account, and signing in with a Solana wallet never fills that field, so the lookup could not match a purchase it was standing right next to. Billing now resolves every Solana wallet you have signed into the account and shows every pass any of them bought, including purchases made before the account existed, with each pass's key, rate limit, and usage. Only wallets you have actually signed in with count, so nobody can claim someone else's purchases by typing an address. Two smaller repairs alongside it: the pricing endpoint now reports each asset's decimal precision from the same source that computes the amount you owe, rather than a fixed number that could one day render a price wrong by a factor of a hundred; and key rotation is now metered per account, because every rotation mints a real key. (`/dashboard/billing`) `[fix, improvement]`
- **A profile’s follower count now matches the people the follower list can actually show you**: The follower and following numbers on a profile counted every follow ever recorded, including ones from accounts that were later deleted or that never claimed a username. The list behind those numbers only shows people you can open a profile for, so a profile could advertise followers and then open to an empty list. Both numbers are now counted over exactly the people the list renders, so the badge and the list always agree. The list itself also stopped dropping those accounts only after it had already paged, which could hand you a blank page of followers with no way to reach the real ones behind it. Separately, the Creations tab used to answer a corrupted page cursor with a silent empty page that read as "nothing more to load"; it now says the cursor is malformed, and an unknown filter is rejected instead of quietly returning everything. `[fix]`
- **A retried agent spend can no longer hand its transaction to somebody else, and an unsupported chain says so instead of blaming the network**: When an agent redeems a permission you granted it, it can send a retry key so a request whose answer it never saw is not paid for twice. That key was filed under the permission alone rather than under the agent that used it, and it was read before the check that the caller owns the permission at all, so a different agent replaying the same permission and key was handed the original transaction hash and receipt instead of being turned away. The key is now filed per caller: a retry only ever returns your own result, and anyone else gets the same not-found answer they should always have got. Two more fixes in the same endpoint. A permission recorded on a chain three.ws has no delegation contract on could never settle, but the attempt came back as a network error, which reads as a temporary outage worth retrying rather than the permanent chain mismatch it is; it is now named plainly and refused before it consumes any of the permission's spending allowance. And the relayer kept its own private one-address-per-chain list of blockchain endpoints, separate from the failover chain the rest of the platform uses, so it would have refused to work on the next supported chain even where the shared endpoints reach it fine. It now uses the shared list, with any operator override still taking priority. The permissions guide gained a section on how the retry key behaves and how long it lasts. (`/docs/permissions`) `[security, fix]`
- **A shared link to a docs page now opens that page instead of stranding you**: Every cross-reference inside a docs page turns into a link like /docs/agent-wallets#financial-controls. Following one worked, but the URL you copied afterwards did not: on a fresh load the viewer only recognised the second half if that doc happened to be listed in the sidebar, and silently left you on the page you arrived from otherwise. Links to Financial controls, the x402 payment tutorial, and the wallet access and proof-of-custody chapters all failed that way. The viewer now asks the server whether the doc exists before giving up, so those links land where they say they will, and the browser tab takes the destination's name. Separately, /docs/3d-api was serving the 3D API landing page rather than the reference doc that the API's own discovery response, the OpenAPI license link, and the docs sidebar all point at; it now serves the reference doc, and the landing page keeps its home at /3d. (`/docs/agent-wallets`) `[fix, docs]`
@@ -21,6 +22,8 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr
- **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]`
+- **Coin Intelligence search and verdict filters now look at the whole feed, not just its newest page**: The Coin Intelligence radar lets you narrow the live launch feed by verdict (Strong, Watch, Caution, Avoid) and search it by name, symbol, or mint. Both filters were applied only to the page of coins already fetched, so asking for 60 Strong coins returned whichever handful of the newest 60 launches happened to be Strong: one, on a busy day. That reads as "the engine found nothing" when the engine had plenty. Search had the same blind spot, and could not see a coin that matched but sat a page or two back. Search is now run by the database across the observed feed, and the verdict filter looks through a much deeper recent window before handing back the page you asked for, so a filtered view returns a full page whenever a full page of matches exists. Searching for a literal percent sign or underscore now matches that character instead of behaving as a wildcard. The live trade tape at /api/pump/dex-trades also became readable from any origin, matching every other public pump.fun read endpoint, so an agent running on its own domain can consume it directly. (`/coin-intel`) `[fix, improvement]`
+- **Daily usage caps stopped resetting themselves partway through the day**: When the fast counter store is unavailable, the daily caps that bound expensive actions (persona extraction, voice cloning, withdrawals) fall back to a shared database counter, and a housekeeping job trims counters whose window has passed. That job decided what counted as 'passed' from the shortest-lived counter the server it ran on happened to have loaded, so a server that had only handled short-window traffic deleted everybody's in-progress daily rows. The effect was invisible and generous in the wrong direction: a cap of five per day would let a caller through six, eight, twelve times, because the tally kept getting wiped mid-day. Housekeeping now measures against the longest window any cap can use, so a daily tally survives until its day is genuinely over. `[fix, infra]`
- **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]`
- **Eight build tutorials now match what the platform actually does**: An audit of eight tutorials found instructions that could not work. The AI-brain tutorial described a model line-up that had been superseded: it never mentioned the Claude 5 family (Sonnet 5, Opus 5, Fable 5), which are live and selectable, and it recommended Sonnet 4.6 as the default. It also sent you to screens that do not exist, telling you to add API keys under a gear icon in My Agents and to change models, sampling knobs, and streaming under a Brain menu. Provider keys actually live in the AI Provider Keys panel on your account page, the model is a field on the agent's embed policy, and streaming has no off-switch. The promised usage tab with token charts and threshold emails did not exist either; the tutorial now documents the real per-agent usage read and points at the monthly quota and per-minute rate limit, which are the controls actually enforced before your money is spent. It also now explains that a visitor can never escalate your agent onto a paid model. The custom-GLB tutorial was worse for anyone following along: it linked a Studio address that no longer resolves, and four of its commands invoked gltf-transform subcommands that have never existed, so converting an FBX, renaming animation clips, and the full Mixamo walkthrough all failed at the first step. Those are replaced with the converter the platform itself uses and a clip-renaming script that was run against a real avatar to confirm it works. Its Draco flag was wrong, its upload path pointed at the wrong page, and it still warned that an avatar without an idle clip would stand frozen in a T-pose, which stopped being true when animation retargeting became universal. Finally, the page-events tutorial listed the wrong fallback order for emote animations. (`/tutorials/connect-ai-brain`) `[docs, fix]`
- **Looking up an on-chain agent by its CAIP reference works again**: The public resolver that turns an ERC-8004 agent reference into its owner, token URI and verified agent card could not be reached at all. An agent reference ends in a slash before its token id, and the documentation told callers to percent-encode the whole reference, which turns that slash into %2F. The API refuses any address segment holding an encoded separator, because that is the same trick used to escape a path and reach files that were never meant to be served, so every correctly-formed lookup was turned away as an unknown address before it ever reached the resolver. The verification badge you can embed on your own site built its request in exactly that shape, so it never showed a result either. The resolver now accepts the reference with its slash as a normal part of the address, the badge asks for it that way, and the documentation shows the form that works. The protection against encoded separators is untouched. New tests resolve the address through the same routing the live site uses, so this cannot quietly break again. (`/docs/api-reference`) `[fix]`
@@ -50,11 +53,14 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr
- **The guard and gesture tutorials stop teaching steps that fail, and one that wiped your clip list**: Two tutorials had drifted away from the code they document, and following either one exactly produced a bad outcome rather than a confusing one. The gesture tutorial's API example padded its request body with an empty clip array, and told readers that field was required; it has not been required for a while, and an empty array is a real value, so anyone who copied that snippet to change one gesture slot silently erased every custom clip on their agent. The endpoint's actual rule is now stated: every field is optional, present replaces it, absent leaves it alone. That page also listed four gestures on the /walk quick keys that are not on them, so pressing 1 through 8 never produced what it described; the eight keys are now named in order, with the wheel and the code call given for the four that have no key. The guard tutorial's registry entry left out the proof block, which the registry auditor has since made mandatory, so a reader who followed every step to the end hit a failure the page never mentioned. It now includes a working proof, shows the exact error you get without one, and adds a step for the command that runs it, which is the difference between a guard that is wired up and a guard anyone has shown still catches anything. Its summary line also described a completely different guard from the one it builds. (`/docs/tutorials/write-a-guard`) `[docs, fix]`
- **The LLM usage panel in your dashboard settings finally shows your real numbers**: Settings has a panel meant to show how much AI inference your agents have used this month. It always said "No usage yet", no matter how much you had used, because the endpoint behind it never sent the figures the panel was written to read. It does now: calls this month, tokens consumed, what those calls cost, and a per-model table showing which models did the work, busiest first. The same response also had two storage limits going out as text rather than numbers, which is the kind of difference that turns a size comparison into nonsense; both are numbers now. An API key with the profile scope can read all of it, so you can pull your own usage from a script, and the developer guide shows the exact shape. (`/dashboard/settings`) `[fix, improvement]`
- **The persona builder stops reporting a model outage as if you had been signed out**: The two routes behind the persona builder (the one that turns your interview answers or a sample of your own writing into a structured persona, and the one that replies to you in that persona's voice) used to hand you whatever status code the model provider returned. If a server-side key expired, the provider answered 401 and so did we, which reads to a browser as an expired session on a request where nothing was wrong with your sign-in. Both now report a provider failure as exactly what it is: a server-side fault, with a plain message and no implication that you need to log back in. Separately, when the platform's daily model-spend ceiling is reached, the builder now says so and tells you when it resets, instead of asking you to retry something that could not have succeeded for the rest of the day. Both routes also now record their model usage against your account, so the spend they generate is visible and capped rather than untracked, and the daily extraction budget now holds across every server instance instead of being counted separately on each one. `[fix, improvement]`
+- **The persona extraction and preview endpoints are documented in the API reference**: Both routes have been live and usable for a while (turn a short interview or a sample of someone's writing into a structured voice profile, then audition that profile against a test message), but the only way to learn their request shape was to read the demo page's source. The API reference now covers them properly: every field with its limits, a real request and response for each, the exact meaning of every error status, and the per-user call budgets. The demo at /demos/persona-extract.html remains the fastest way to see them work. (`/docs/api-reference`) `[docs]`
- **The plugin marketplace stops hiding a plugin when you page through it**: Browsing plugins a page at a time could show you the same plugin twice and never show another one at all. The catalogue was sorted by install count and publish date, and the built-in plugins were all published in the same instant with zero installs, so that sort left them tied and the database was free to order the tied rows differently on every request. One plugin therefore landed on two consecutive pages and one fell through the gap. The order is now decided all the way down, so paging through the catalogue returns every plugin exactly once. Searching also takes your text literally: typing a percent sign or an underscore used to act as a database wildcard and match rows it should not. Publishing got stricter at the same time, because a plugin manifest is handed to the model as a tool definition by whoever installs it: a tool name now has to be plain letters, digits, underscores, or hyphens, every tool needs a real description, and a manifest has to fit the same 64KB ceiling that importing one by URL already enforced. And pointing the importer at a repository web page instead of the raw manifest file now says exactly that, rather than showing a raw parser error. (`/marketplace`) `[fix, improvement]`
- **The pump.fun trade history works again, notification settings show every category, and a bad agent id stops reading as a server crash**: Three fixes across the public MCP packages and the API behind them. Asking for a token's recent buys and sells (get_token_trades on the free pump.fun MCP server) had stopped working entirely: the platform reads several transactions in one batched call, and the free Solana providers we route through cap those batches at one call each, so they rejected the whole request and the tool returned a raw provider error instead of trades. The platform now recognises that refusal, re-sends the reads one at a time to the same provider, and remembers the cap so later calls skip the wasted attempt; every batched on-chain read benefits, including wallet and agent activity history. Separately, the notifications MCP server told agents there were six notification categories when there are seven, so an agent could never change how it hears about a finished 3D generation; all seven are now listed, along with the security notices that always reach your bell inbox. And the agent provenance log answered a non-uuid agent id with an internal error and a support reference; it now says plainly that the id must be a uuid. `[fix, sdk]`
+- **The referral visit beacon now names the real fault when it cannot read a request**: Referral share links (?ref=CODE) fire a small beacon that records the visit, so the share to signup funnel is measurable. If a caller sent that beacon without a JSON content-type header, or with a body too large to read, the endpoint answered that the referral code was malformed, which is the one thing that was not wrong: the code had never been read. A bad or missing content-type now returns 415 unsupported_media_type, an unreadable body returns 400 bad_request, and an oversized one returns 413 payload_too_large, so anyone hosting their own landing page for a three.ws referral link fixes the header instead of hunting a code that was fine. The write path also picked up its first test coverage: referrer resolution, unknown-code visits, and the once-per-visitor-per-day dedup are now pinned, so the funnel counts cannot drift unnoticed. (`/dashboard/referrals`) `[fix, improvement]`
- **The tokenized-stock board sorts the way you asked, with the busiest names first**: The Robinhood Chain stock board (and the API behind it) accepts a sort column and a direction. Both ran backwards: asking for the highest 24h volume returned the quietest tokens, the ones with no market at all led every column, and passing dir=asc handed back descending results. Numeric columns now read highest-first by default, dir=asc genuinely flips them, and a token with no price or no NAV feed sorts to the end in either direction instead of crowding the top. The response now also echoes the sort and direction that actually ran, so an unknown sort value comes back as the default it fell to rather than as the value you sent; the memecoin screener echoes its sort the same honest way. (`/markets/robinhood`) `[fix]`
- **The trades feed stopped labelling a winning exit with a losing multiple**: When an agent sells part of a position to take its initial stake back and lets the rest ride, only that final sell is recorded against the position, while the profit percentage covers both sells. The feed was working out the “×” badge from the final sell alone, so a trade that returned +88% could show up as “0.56× +88%” on the same row. The multiple is now worked out from the trade's actual return, so the two numbers always agree. A coin's page also asked the feed for every trade on that coin and was quietly given only the ones above +10%, hiding the rest of that coin's history; it now gets what it asked for. The feed also answers a malformed page cursor or coin address by saying so, instead of returning results for the wrong coin, and a database problem no longer looks like a platform where nobody has ever turned a profit. (`/trades`) `[fix]`
- **The trading and MCP docs now match what the code and the live API actually do**: An audit of eight documentation pages ran every command they print and checked every claim against the code behind it, then corrected what had drifted. The biggest one was in the trading tutorial: the command it gave you for verifying a fleet's fills on-chain asked for a field the leaderboard does not publish, so it returned an empty explorer link for every agent and the verification step could not be completed at all. It now uses the fields that exist, linking both legs of each trade straight to Solscan, and it skips agents whose wallet has not been provisioned yet instead of building a URL that goes nowhere. The MCP tool safety page undercounted the tools that share a name across two servers, which matters because that collision is exactly why a trust policy has to key on the namespaced id; it now lists all nine and prints a command that re-derives the list so it cannot go stale again. The MCP tool catalog itself had drifted from its source and was serving outdated descriptions for three tools, on a page whose whole promise is that it is generated from source and cannot drift; it has been regenerated. The package extraction guide had every version in its roster out of date along with its build and test columns, and still described a publisher field as missing that was set some time ago. The 10 SOL trading experiment page stated a risk rule in absolute terms that contradicted the setup script it tells you to run, which read as a bug in one of the two; the rule now carries the scope the code actually applies. (`/docs/mcp-safety`) `[docs, fix]`
+- **The trusted-agent leaderboard now ranks every candidate, not an arbitrary sample of them**: The leaderboard scores a capped pool of agents on every request, and that pool was selected in whatever order the database happened to return, from a candidate set roughly twice the cap. Half the agents with a real track record were silently skipped, so a top-scoring agent could be missing from the board entirely and two identical page loads could disagree on the ranking. The pool is now ordered by settled ledger volume before it is capped, so the strongest candidates are always scored and the board is stable between requests. Two related repairs: asking for a leaderboard with a non-numeric size (limit=abc) returned an empty board that looked exactly like 'no agent here is trusted', and now returns a plain error; and a database outage no longer publishes an empty leaderboard as if it were the truth, it reports the outage. (`/trending`) `[fix]`
- **The Tutor’s running tab and end-of-session invoice now show what you actually paid**: The Tutor charges one cent per answer and keeps an itemized tab you can reload later and close for a signed invoice. That ledger only ever knew how to store itself in a key-value service this deployment does not run, so nothing was ever written down: reopening the page never restored your history, and ending a session always produced an invoice reading "no questions" and a total of zero, however many answers you had paid for. The tab is now stored in the platform’s own database, so it survives a reload, a new browser tab, and any server restart, and the invoice lists every answer with its charge and a verification hash over the line items. Closing a session twice returns the identical invoice instead of a freshly stamped one, closing a session id that was never used no longer makes that id unusable for its real owner, and if the ledger itself is ever unreachable the page says so rather than quietly reporting that you owe nothing. Asking a question still succeeds even if the ledger write fails, because a bookkeeping outage should never cost you the answer you paid for. (`/tutor`) `[fix]`
- **The vanity receipt verifier stops calling honest receipts fraudulent, and the avatar CLI takes a Solana address**: Two documented commands did not do what their page said. The command-line verifier for a provably-fair vanity address receipt scored the difficulty claim with the retired flat model, the one that treats every Base58 character as equally likely. Every receipt issued since the leading-character correction landed therefore failed its difficulty check and was reported as untrustworthy, even though the in-browser verifier at /vanity/verify passed the same receipt. The verifier now reads the model each receipt names in its own signed difficulty block, exactly as the page and the SDK do, so current receipts verify and older ones keep verifying under the model they were issued under. Separately, the Rig Doctor page showed an avatar-manifest command taking a Solana address as the owner, which the CLI rejected outright: it understood Ethereum addresses and full CAIP-10 identifiers and nothing else. Since Solana is the home chain, a bare Solana address is now accepted and recorded as solana:mainnet-beta. Alongside those, eight tutorial and reference pages were audited against the code they describe: the Vercel self-hosting guide had a stale copy of the config file and pointed at a migrations folder that has moved, the MCP guide listed three placeholder OAuth scopes where the live server publishes twelve real per-capability ones, and the Avatar CLI page pinned a version number that npm has never had. (`/docs/rig-doctor`) `[fix, docs, sdk]`
- **The vanity SDK now uses the payment wallet you hand it, and the in-chat 3D avatar keeps its tuned lighting**: Three fixes in the developer packages. The @three-ws/vanity SDK documented a fetch option on its paid address-grinding lane but silently ignored it, so a developer who passed a payment-enabled fetch got a payment-required error back instead of the keypair they paid for; that option now works, as do a custom API host and key. The avatar MCP server's in-chat 3D viewer had been hand-tuned with softer shadows, brighter exposure and a neutral environment light, but the script that rebuilds it before every release still produced the old flat version, so the next release would have quietly undone the tuning; the script now produces the tuned viewer, and the same settings apply to the fallback view for chat apps that cannot run the interactive one. The tool SDK's quick-start example pointed at an API that does not exist and skipped the wrapper an MCP server needs to return anything at all, so following it produced a tool that answered with nothing; it now runs end to end against a real free three.ws endpoint. `[fix, sdk, docs]`
diff --git a/data/changelog.json b/data/changelog.json
index a1c3319a7..751a6bc64 100644
--- a/data/changelog.json
+++ b/data/changelog.json
@@ -1,6 +1,63 @@
{
"$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": "Daily usage caps stopped resetting themselves partway through the day",
+ "summary": "When the fast counter store is unavailable, the daily caps that bound expensive actions (persona extraction, voice cloning, withdrawals) fall back to a shared database counter, and a housekeeping job trims counters whose window has passed. That job decided what counted as 'passed' from the shortest-lived counter the server it ran on happened to have loaded, so a server that had only handled short-window traffic deleted everybody's in-progress daily rows. The effect was invisible and generous in the wrong direction: a cap of five per day would let a caller through six, eight, twelve times, because the tally kept getting wiped mid-day. Housekeeping now measures against the longest window any cap can use, so a daily tally survives until its day is genuinely over.",
+ "tags": [
+ "fix",
+ "infra"
+ ]
+ },
+ {
+ "date": "2026-08-15",
+ "title": "The persona extraction and preview endpoints are documented in the API reference",
+ "summary": "Both routes have been live and usable for a while (turn a short interview or a sample of someone's writing into a structured voice profile, then audition that profile against a test message), but the only way to learn their request shape was to read the demo page's source. The API reference now covers them properly: every field with its limits, a real request and response for each, the exact meaning of every error status, and the per-user call budgets. The demo at /demos/persona-extract.html remains the fastest way to see them work.",
+ "tags": [
+ "docs"
+ ],
+ "link": "/docs/api-reference"
+ },
+ {
+ "date": "2026-08-15",
+ "title": "The trusted-agent leaderboard now ranks every candidate, not an arbitrary sample of them",
+ "summary": "The leaderboard scores a capped pool of agents on every request, and that pool was selected in whatever order the database happened to return, from a candidate set roughly twice the cap. Half the agents with a real track record were silently skipped, so a top-scoring agent could be missing from the board entirely and two identical page loads could disagree on the ranking. The pool is now ordered by settled ledger volume before it is capped, so the strongest candidates are always scored and the board is stable between requests. Two related repairs: asking for a leaderboard with a non-numeric size (limit=abc) returned an empty board that looked exactly like 'no agent here is trusted', and now returns a plain error; and a database outage no longer publishes an empty leaderboard as if it were the truth, it reports the outage.",
+ "tags": [
+ "fix"
+ ],
+ "link": "/trending"
+ },
+ {
+ "date": "2026-08-15",
+ "title": "A Premium Data API pass you bought straight from your wallet now shows up on your billing page",
+ "summary": "You can buy a pass without an account, paying from a Solana wallet on the Data API page. Do that, then sign in with the same wallet later, and billing showed you nothing: the pass was live, the API key worked, but the page insisted you had never bought anything. It was reading a single legacy address field on the account, and signing in with a Solana wallet never fills that field, so the lookup could not match a purchase it was standing right next to. Billing now resolves every Solana wallet you have signed into the account and shows every pass any of them bought, including purchases made before the account existed, with each pass's key, rate limit, and usage. Only wallets you have actually signed in with count, so nobody can claim someone else's purchases by typing an address. Two smaller repairs alongside it: the pricing endpoint now reports each asset's decimal precision from the same source that computes the amount you owe, rather than a fixed number that could one day render a price wrong by a factor of a hundred; and key rotation is now metered per account, because every rotation mints a real key.",
+ "tags": [
+ "fix",
+ "improvement"
+ ],
+ "link": "/dashboard/billing"
+ },
+ {
+ "date": "2026-08-15",
+ "title": "Coin Intelligence search and verdict filters now look at the whole feed, not just its newest page",
+ "summary": "The Coin Intelligence radar lets you narrow the live launch feed by verdict (Strong, Watch, Caution, Avoid) and search it by name, symbol, or mint. Both filters were applied only to the page of coins already fetched, so asking for 60 Strong coins returned whichever handful of the newest 60 launches happened to be Strong: one, on a busy day. That reads as \"the engine found nothing\" when the engine had plenty. Search had the same blind spot, and could not see a coin that matched but sat a page or two back. Search is now run by the database across the observed feed, and the verdict filter looks through a much deeper recent window before handing back the page you asked for, so a filtered view returns a full page whenever a full page of matches exists. Searching for a literal percent sign or underscore now matches that character instead of behaving as a wildcard. The live trade tape at /api/pump/dex-trades also became readable from any origin, matching every other public pump.fun read endpoint, so an agent running on its own domain can consume it directly.",
+ "tags": [
+ "fix",
+ "improvement"
+ ],
+ "link": "/coin-intel"
+ },
+ {
+ "date": "2026-08-15",
+ "title": "The referral visit beacon now names the real fault when it cannot read a request",
+ "summary": "Referral share links (?ref=CODE) fire a small beacon that records the visit, so the share to signup funnel is measurable. If a caller sent that beacon without a JSON content-type header, or with a body too large to read, the endpoint answered that the referral code was malformed, which is the one thing that was not wrong: the code had never been read. A bad or missing content-type now returns 415 unsupported_media_type, an unreadable body returns 400 bad_request, and an oversized one returns 413 payload_too_large, so anyone hosting their own landing page for a three.ws referral link fixes the header instead of hunting a code that was fine. The write path also picked up its first test coverage: referrer resolution, unknown-code visits, and the once-per-visitor-per-day dedup are now pinned, so the funnel counts cannot drift unnoticed.",
+ "tags": [
+ "fix",
+ "improvement"
+ ],
+ "link": "/dashboard/referrals"
+ },
{
"date": "2026-08-15",
"title": "Scanning for trade candidates is faster on creator-filtered rules and honest about how much it looked at",
diff --git a/public/changelog.json b/public/changelog.json
index 9106c2ebf..b032f70f2 100644
--- a/public/changelog.json
+++ b/public/changelog.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-08-15T15:52:49.645Z",
+ "generated_at": "2026-08-15T16:20:54.817Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json",
"site": {
"name": "three.ws",
@@ -27,6 +27,17 @@
"docs"
]
},
+ {
+ "date": "2026-08-15",
+ "type": "update",
+ "title": "A Premium Data API pass you bought straight from your wallet now shows up on your billing page",
+ "summary": "You can buy a pass without an account, paying from a Solana wallet on the Data API page. Do that, then sign in with the same wallet later, and billing showed you nothing: the pass was live, the API key worked, but the page insisted you had never bought anything. It was reading a single legacy address field on the account, and signing in with a Solana wallet never fills that field, so the lookup could not match a purchase it was standing right next to. Billing now resolves every Solana wallet you have signed into the account and shows every pass any of them bought, including purchases made before the account existed, with each pass's key, rate limit, and usage. Only wallets you have actually signed in with count, so nobody can claim someone else's purchases by typing an address. Two smaller repairs alongside it: the pricing endpoint now reports each asset's decimal precision from the same source that computes the amount you owe, rather than a fixed number that could one day render a price wrong by a factor of a hundred; and key rotation is now metered per account, because every rotation mints a real key.",
+ "link": "/dashboard/billing",
+ "tags": [
+ "fix",
+ "improvement"
+ ]
+ },
{
"date": "2026-08-15",
"type": "update",
@@ -166,6 +177,28 @@
"fix"
]
},
+ {
+ "date": "2026-08-15",
+ "type": "update",
+ "title": "Coin Intelligence search and verdict filters now look at the whole feed, not just its newest page",
+ "summary": "The Coin Intelligence radar lets you narrow the live launch feed by verdict (Strong, Watch, Caution, Avoid) and search it by name, symbol, or mint. Both filters were applied only to the page of coins already fetched, so asking for 60 Strong coins returned whichever handful of the newest 60 launches happened to be Strong: one, on a busy day. That reads as \"the engine found nothing\" when the engine had plenty. Search had the same blind spot, and could not see a coin that matched but sat a page or two back. Search is now run by the database across the observed feed, and the verdict filter looks through a much deeper recent window before handing back the page you asked for, so a filtered view returns a full page whenever a full page of matches exists. Searching for a literal percent sign or underscore now matches that character instead of behaving as a wildcard. The live trade tape at /api/pump/dex-trades also became readable from any origin, matching every other public pump.fun read endpoint, so an agent running on its own domain can consume it directly.",
+ "link": "/coin-intel",
+ "tags": [
+ "fix",
+ "improvement"
+ ]
+ },
+ {
+ "date": "2026-08-15",
+ "type": "update",
+ "title": "Daily usage caps stopped resetting themselves partway through the day",
+ "summary": "When the fast counter store is unavailable, the daily caps that bound expensive actions (persona extraction, voice cloning, withdrawals) fall back to a shared database counter, and a housekeeping job trims counters whose window has passed. That job decided what counted as 'passed' from the shortest-lived counter the server it ran on happened to have loaded, so a server that had only handled short-window traffic deleted everybody's in-progress daily rows. The effect was invisible and generous in the wrong direction: a cap of five per day would let a caller through six, eight, twelve times, because the tally kept getting wiped mid-day. Housekeeping now measures against the longest window any cap can use, so a daily tally survives until its day is genuinely over.",
+ "link": null,
+ "tags": [
+ "fix",
+ "infra"
+ ]
+ },
{
"date": "2026-08-15",
"type": "update",
@@ -483,6 +516,16 @@
"improvement"
]
},
+ {
+ "date": "2026-08-15",
+ "type": "update",
+ "title": "The persona extraction and preview endpoints are documented in the API reference",
+ "summary": "Both routes have been live and usable for a while (turn a short interview or a sample of someone's writing into a structured voice profile, then audition that profile against a test message), but the only way to learn their request shape was to read the demo page's source. The API reference now covers them properly: every field with its limits, a real request and response for each, the exact meaning of every error status, and the per-user call budgets. The demo at /demos/persona-extract.html remains the fastest way to see them work.",
+ "link": "/docs/api-reference",
+ "tags": [
+ "docs"
+ ]
+ },
{
"date": "2026-08-15",
"type": "update",
@@ -505,6 +548,17 @@
"sdk"
]
},
+ {
+ "date": "2026-08-15",
+ "type": "update",
+ "title": "The referral visit beacon now names the real fault when it cannot read a request",
+ "summary": "Referral share links (?ref=CODE) fire a small beacon that records the visit, so the share to signup funnel is measurable. If a caller sent that beacon without a JSON content-type header, or with a body too large to read, the endpoint answered that the referral code was malformed, which is the one thing that was not wrong: the code had never been read. A bad or missing content-type now returns 415 unsupported_media_type, an unreadable body returns 400 bad_request, and an oversized one returns 413 payload_too_large, so anyone hosting their own landing page for a three.ws referral link fixes the header instead of hunting a code that was fine. The write path also picked up its first test coverage: referrer resolution, unknown-code visits, and the once-per-visitor-per-day dedup are now pinned, so the funnel counts cannot drift unnoticed.",
+ "link": "/dashboard/referrals",
+ "tags": [
+ "fix",
+ "improvement"
+ ]
+ },
{
"date": "2026-08-15",
"type": "update",
@@ -536,6 +590,16 @@
"fix"
]
},
+ {
+ "date": "2026-08-15",
+ "type": "update",
+ "title": "The trusted-agent leaderboard now ranks every candidate, not an arbitrary sample of them",
+ "summary": "The leaderboard scores a capped pool of agents on every request, and that pool was selected in whatever order the database happened to return, from a candidate set roughly twice the cap. Half the agents with a real track record were silently skipped, so a top-scoring agent could be missing from the board entirely and two identical page loads could disagree on the ranking. The pool is now ordered by settled ledger volume before it is capped, so the strongest candidates are always scored and the board is stable between requests. Two related repairs: asking for a leaderboard with a non-numeric size (limit=abc) returned an empty board that looked exactly like 'no agent here is trusted', and now returns a plain error; and a database outage no longer publishes an empty leaderboard as if it were the truth, it reports the outage.",
+ "link": "/trending",
+ "tags": [
+ "fix"
+ ]
+ },
{
"date": "2026-08-15",
"type": "update",
diff --git a/public/changelog.xml b/public/changelog.xml
index 47213e988..2aa5d9941 100644
--- a/public/changelog.xml
+++ b/public/changelog.xml
@@ -22,6 +22,14 @@
<category>fix</category>
<description>The two market intelligence reads in the unified API, recent narrative intel and momentum-ranked projects, pass a key we hold to the upstream provider; a caller needs no key at all. When that provider stopped accepting our key, both reads answered &quot;unauthorized&quot; with the provider's own wording, so an agent reading the response concluded its own credentials were bad and retried with different ones forever, when nothing on the caller's side was wrong. Both reads now say plainly that the service is temporarily unavailable because this deployment's upstream key was rejected, which is a status clients already know to retry rather than re-authenticate against. The older market intelligence endpoints always classified this correctly; the classification now lives in one place, so the two doors cannot drift apart again, and the error tables in the API reference list every code either one can return.</description>
</item>
+ <item>
+ <title>A Premium Data API pass you bought straight from your wallet now shows up on your billing page</title>
+ <link>https://three.ws/dashboard/billing</link>
+ <guid isPermaLink="false">2026-08-15:A Premium Data API pass you bought straight from your wallet now shows up on your billing page</guid>
+ <pubDate>Sat, 15 Aug 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>You can buy a pass without an account, paying from a Solana wallet on the Data API page. Do that, then sign in with the same wallet later, and billing showed you nothing: the pass was live, the API key worked, but the page insisted you had never bought anything. It was reading a single legacy address field on the account, and signing in with a Solana wallet never fills that field, so the lookup could not match a purchase it was standing right next to. Billing now resolves every Solana wallet you have signed into the account and shows every pass any of them bought, including purchases made before the account existed, with each pass's key, rate limit, and usage. Only wallets you have actually signed in with count, so nobody can claim someone else's purchases by typing an address. Two smaller repairs alongside it: the pricing endpoint now reports each asset's decimal precision from the same source that computes the amount you owe, rather than a fixed number that could one day render a price wrong by a factor of a hundred; and key rotation is now metered per account, because every rotation mints a real key.</description>
+ </item>
<item>
<title>A profile’s follower count now matches the people the follower list can actually show you</title>
<link>https://three.ws/changelog</link>
@@ -126,6 +134,22 @@
<category>fix</category>
<description>Pasting a wallet into Claim Your Wallet could answer &quot;not indexed yet&quot; 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.</description>
</item>
+ <item>
+ <title>Coin Intelligence search and verdict filters now look at the whole feed, not just its newest page</title>
+ <link>https://three.ws/coin-intel</link>
+ <guid isPermaLink="false">2026-08-15:Coin Intelligence search and verdict filters now look at the whole feed, not just its newest page</guid>
+ <pubDate>Sat, 15 Aug 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>The Coin Intelligence radar lets you narrow the live launch feed by verdict (Strong, Watch, Caution, Avoid) and search it by name, symbol, or mint. Both filters were applied only to the page of coins already fetched, so asking for 60 Strong coins returned whichever handful of the newest 60 launches happened to be Strong: one, on a busy day. That reads as &quot;the engine found nothing&quot; when the engine had plenty. Search had the same blind spot, and could not see a coin that matched but sat a page or two back. Search is now run by the database across the observed feed, and the verdict filter looks through a much deeper recent window before handing back the page you asked for, so a filtered view returns a full page whenever a full page of matches exists. Searching for a literal percent sign or underscore now matches that character instead of behaving as a wildcard. The live trade tape at /api/pump/dex-trades also became readable from any origin, matching every other public pump.fun read endpoint, so an agent running on its own domain can consume it directly.</description>
+ </item>
+ <item>
+ <title>Daily usage caps stopped resetting themselves partway through the day</title>
+ <link>https://three.ws/changelog</link>
+ <guid isPermaLink="false">2026-08-15:Daily usage caps stopped resetting themselves partway through the day</guid>
+ <pubDate>Sat, 15 Aug 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>When the fast counter store is unavailable, the daily caps that bound expensive actions (persona extraction, voice cloning, withdrawals) fall back to a shared database counter, and a housekeeping job trims counters whose window has passed. That job decided what counted as 'passed' from the shortest-lived counter the server it ran on happened to have loaded, so a server that had only handled short-window traffic deleted everybody's in-progress daily rows. The effect was invisible and generous in the wrong direction: a cap of five per day would let a caller through six, eight, twelve times, because the tally kept getting wiped mid-day. Housekeeping now measures against the longest window any cap can use, so a daily tally survives until its day is genuinely over.</description>
+ </item>
<item>
<title>Docs pages stop opening with a wall of raw metadata, and the AWS pages say where the Marketplace listing actually stands</title>
<link>https://three.ws/docs/aws-marketplace</link>
@@ -358,6 +382,14 @@
<category>fix</category>
<description>The two routes behind the persona builder (the one that turns your interview answers or a sample of your own writing into a structured persona, and the one that replies to you in that persona's voice) used to hand you whatever status code the model provider returned. If a server-side key expired, the provider answered 401 and so did we, which reads to a browser as an expired session on a request where nothing was wrong with your sign-in. Both now report a provider failure as exactly what it is: a server-side fault, with a plain message and no implication that you need to log back in. Separately, when the platform's daily model-spend ceiling is reached, the builder now says so and tells you when it resets, instead of asking you to retry something that could not have succeeded for the rest of the day. Both routes also now record their model usage against your account, so the spend they generate is visible and capped rather than untracked, and the daily extraction budget now holds across every server instance instead of being counted separately on each one.</description>
</item>
+ <item>
+ <title>The persona extraction and preview endpoints are documented in the API reference</title>
+ <link>https://three.ws/docs/api-reference</link>
+ <guid isPermaLink="false">2026-08-15:The persona extraction and preview endpoints are documented in the API reference</guid>
+ <pubDate>Sat, 15 Aug 2026 12:00:00 GMT</pubDate>
+ <category>docs</category>
+ <description>Both routes have been live and usable for a while (turn a short interview or a sample of someone's writing into a structured voice profile, then audition that profile against a test message), but the only way to learn their request shape was to read the demo page's source. The API reference now covers them properly: every field with its limits, a real request and response for each, the exact meaning of every error status, and the per-user call budgets. The demo at /demos/persona-extract.html remains the fastest way to see them work.</description>
+ </item>
<item>
<title>The plugin marketplace stops hiding a plugin when you page through it</title>
<link>https://three.ws/marketplace</link>
@@ -374,6 +406,14 @@
<category>fix</category>
<description>Three fixes across the public MCP packages and the API behind them. Asking for a token's recent buys and sells (get_token_trades on the free pump.fun MCP server) had stopped working entirely: the platform reads several transactions in one batched call, and the free Solana providers we route through cap those batches at one call each, so they rejected the whole request and the tool returned a raw provider error instead of trades. The platform now recognises that refusal, re-sends the reads one at a time to the same provider, and remembers the cap so later calls skip the wasted attempt; every batched on-chain read benefits, including wallet and agent activity history. Separately, the notifications MCP server told agents there were six notification categories when there are seven, so an agent could never change how it hears about a finished 3D generation; all seven are now listed, along with the security notices that always reach your bell inbox. And the agent provenance log answered a non-uuid agent id with an internal error and a support reference; it now says plainly that the id must be a uuid.</description>
</item>
+ <item>
+ <title>The referral visit beacon now names the real fault when it cannot read a request</title>
+ <link>https://three.ws/dashboard/referrals</link>
+ <guid isPermaLink="false">2026-08-15:The referral visit beacon now names the real fault when it cannot read a request</guid>
+ <pubDate>Sat, 15 Aug 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>Referral share links (?ref=CODE) fire a small beacon that records the visit, so the share to signup funnel is measurable. If a caller sent that beacon without a JSON content-type header, or with a body too large to read, the endpoint answered that the referral code was malformed, which is the one thing that was not wrong: the code had never been read. A bad or missing content-type now returns 415 unsupported_media_type, an unreadable body returns 400 bad_request, and an oversized one returns 413 payload_too_large, so anyone hosting their own landing page for a three.ws referral link fixes the header instead of hunting a code that was fine. The write path also picked up its first test coverage: referrer resolution, unknown-code visits, and the once-per-visitor-per-day dedup are now pinned, so the funnel counts cannot drift unnoticed.</description>
+ </item>
<item>
<title>The tokenized-stock board sorts the way you asked, with the busiest names first</title>
<link>https://three.ws/markets/robinhood</link>
@@ -398,6 +438,14 @@
<category>docs</category>
<description>An audit of eight documentation pages ran every command they print and checked every claim against the code behind it, then corrected what had drifted. The biggest one was in the trading tutorial: the command it gave you for verifying a fleet's fills on-chain asked for a field the leaderboard does not publish, so it returned an empty explorer link for every agent and the verification step could not be completed at all. It now uses the fields that exist, linking both legs of each trade straight to Solscan, and it skips agents whose wallet has not been provisioned yet instead of building a URL that goes nowhere. The MCP tool safety page undercounted the tools that share a name across two servers, which matters because that collision is exactly why a trust policy has to key on the namespaced id; it now lists all nine and prints a command that re-derives the list so it cannot go stale again. The MCP tool catalog itself had drifted from its source and was serving outdated descriptions for three tools, on a page whose whole promise is that it is generated from source and cannot drift; it has been regenerated. The package extraction guide had every version in its roster out of date along with its build and test columns, and still described a publisher field as missing that was set some time ago. The 10 SOL trading experiment page stated a risk rule in absolute terms that contradicted the setup script it tells you to run, which read as a bug in one of the two; the rule now carries the scope the code actually applies.</description>
</item>
+ <item>
+ <title>The trusted-agent leaderboard now ranks every candidate, not an arbitrary sample of them</title>
+ <link>https://three.ws/trending</link>
+ <guid isPermaLink="false">2026-08-15:The trusted-agent leaderboard now ranks every candidate, not an arbitrary sample of them</guid>
+ <pubDate>Sat, 15 Aug 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>The leaderboard scores a capped pool of agents on every request, and that pool was selected in whatever order the database happened to return, from a candidate set roughly twice the cap. Half the agents with a real track record were silently skipped, so a top-scoring agent could be missing from the board entirely and two identical page loads could disagree on the ranking. The pool is now ordered by settled ledger volume before it is capped, so the strongest candidates are always scored and the board is stable between requests. Two related repairs: asking for a leaderboard with a non-numeric size (limit=abc) returned an empty board that looked exactly like 'no agent here is trusted', and now returns a plain error; and a database outage no longer publishes an empty leaderboard as if it were the truth, it reports the outage.</description>
+ </item>
<item>
<title>The Tutor’s running tab and end-of-session invoice now show what you actually paid</title>
<link>https://three.ws/tutor</link>