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.

fix(dashboard-next/analytics): keep one bad payload from blanking the whole page

nirholasd49c820b6d71
diff --git a/CHANGELOG.md b/CHANGELOG.md
index e832621c6..b4ec4fa47 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -9,11 +9,13 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr
- **Docs · Open-Source Footprint** (`/docs/open-source-footprint`): Every registry, marketplace, community, and directory where three.ws code and listings live, with live links and the number behind each one.
- **Docs · The $THREE thesis** (`/docs/three-thesis`): The long-form case for $THREE: what three.ws is, every utility and sink the token has, how platform revenue routes into buybacks, where it trades and is verified, the ecosystem footprint, the roadmap, and every risk the platform documents about itself.
- **Docs · Weekly Report #1** (`/docs/weekly-report-1`): The first three.ws weekly report: a week-by-week roundup of everything shipped from the first commit on 2026-04-14 through 2026-08-25, with every launch, partnership, announcement, and where $THREE fits.
+- **Billing & Passes names your creators, keeps its retry buttons live, and the dashboard fits a phone screen**: On /dashboard/billing, creator subscriptions now show the creator's name (linked to their profile), the real renewal or end date, a colour-coded status, and the plan price with its interval, instead of a raw account id. When the passes or subscriptions feed cannot be reached, the Retry button now actually reloads that section. Across every dashboard page, the top bar no longer forces the layout wider than a 320px phone screen, so nothing is clipped off the right edge. (`/dashboard/billing`) `[fix, improvement]`
- **Compare reads correctly on a phone and stops mislabelling gains and losses**: The side-by-side coin comparison had three problems worth fixing. Percentage rows rendered every number the same neutral colour, so a loss looked like a gain unless it happened to be the row winner, and the winning cell was painted green even when it was a 37% drawdown; gains are now green, losses red, and the row winner is marked by weight and a tint that reads on either. The performance overlay gained date labels along its bottom edge, and on a phone it now draws at the width of the screen instead of shrinking a desktop-sized chart to a third of its height with unreadable text. Switching range fast could also leave a year of history drawn under a 7-day label; the chart now ignores a slow answer that a newer range has already replaced. (`/compare`) `[fix, improvement]`
- **Connect X no longer dead-ends when X sign-in is switched off**: Seeding an agent's memory from X starts by connecting your X account, and on a deployment where X sign-in is not switched on every Connect X button led to a page of raw error text with no way back. Those buttons now say X connections are not enabled and why, in the agent editor's Social tab and the avatar editor's X panel as well as in Settings, and following an old connect link lands you back on the page you started from with the reason stated instead of stranding you. Nothing about consent, seeding, or revocation changes. (`/settings`) `[fix]`
- **Creator Gallery cards stay put while you scroll, and the leaderboards show they are loading**: On /creations, the 3D preview on every gallery card and leaderboard row was accidentally accepting drag input, so a card could be flung out of frame and a swipe over one scrolled nothing on a phone instead of moving the feed. The previews now spin on their own and hand the drag back to the page. The trending and top-creator columns also render shimmer rows while they load instead of sitting blank, the browse tally no longer shows a stale number over a loading grid, and keyboard focus on the search field is now clearly outlined. (`/creations`) `[fix, improvement]`
- **Credits shows your $THREE discount tier, and no longer goes blank when it cannot load**: The Credits page had a hole where its error state should be: if the balance request failed, every panel disappeared and the page ended below the heading with nothing on it. There is now a designed card that says what happened, links to platform status, and retries in one click, and a dropped connection reads as a real sentence instead of the browser's "Failed to fetch". The page also finally states the thing it promises: a pill showing the $THREE tier you are actually charged at, with the discount you are getting or how much more $THREE reaches the next tier. On a 320px phone the whole layout used to be a hundred pixels wider than the screen with the right edge silently cut off, so nothing over there was reachable; the page now fits, and the history table scrolls inside its own box. Smaller fixes throughout: every button and field has a visible keyboard focus ring, the deposit address has a copy button, the $THREE unit price shows real decimals instead of rounding to $0.00, the amount field and the history controls stay translated when you switch asset or load another page, and the price list dropped the dashes from its labels. (`/credits`) `[fix, improvement]`
- **Crew HQ keeps its 3D room standing, and crew links now open where they point**: Crew HQ refreshes who is in the world every 20 seconds, and it used to rebuild the whole room to do it: every member's 3D figure was destroyed and recreated four times a minute, which burns through the handful of live 3D canvases a browser will give a page and could catch a figure mid-load. The room now writes the new state into the figures already standing and only rebuilds when the roster itself changes, and opening a shared crew link no longer flashes the loading skeleton over a room that is already there. A member whose model cannot be loaded now shows their portrait on the plinth instead of an empty space. Signed-out visitors get a clean page: the sign-in-only crew request is no longer fired at all, the crew directory loads beside the room rather than behind it, and it stops listing the crew you are already looking at. A tag nobody flies offers the founding form only to someone who can actually take it, and a dropped connection now says what happened and how to retry instead of showing the browser's "Failed to fetch". (`/crews`) `[fix, improvement]`
+- **Dashboard Analytics fits a phone screen and its failure page can actually reload**: On a 320px phone the time-range buttons refused to wrap, which pushed every panel below them past the right edge of the screen; they wrap now and nothing scrolls sideways. The rare failure page showed a Reload button that did nothing when tapped, so it now reloads, and it explains what happened in plain language with a link to support instead of only printing a developer error string. A malformed response from one of the services behind the page no longer blanks the whole dashboard: the panel that depends on it degrades on its own and the rest still draws. The page also stops requesting a monetization report it never displayed, and its search-engine description finally says what the page shows: revenue over time, revenue by skill, widget views and chats, the conversion funnel, and per-agent performance. (`/dashboard/analytics`) `[fix, improvement]`
- **Describe it to 3D stops offering a retry that cannot work, and finally follows your light theme**: Every attempt on this page costs about a minute of GPU time, so the page was handing out the wrong recovery. When your avatar library was full, it showed the failure and a Try again button that burned the same minute and hit the same ceiling; it now links straight to your dashboard to free a slot or to Pricing to raise it, and drops the retry entirely. When the image engine is throttled it quotes the wait the server actually asked for and counts the retry button down in place instead of letting you click into another rejection. A failed build no longer keeps spinning its orb and claiming it is still rendering, a dropped connection says so instead of showing a generic shrug, and the recovery links inside the error box are readable and keyboard focusable. Separately, the page had a light-theme hole: the toggle was live but only half the colours flipped, so the composer, the example chips and the result panel stayed near black on a white page and the main button rendered black text on blue, under the readable-contrast floor. Light mode is now a complete palette, and the site-wide theme switcher no longer decides a page cannot do light before the stylesheet that gives it light has loaded, which was silently serving dark to people who had chosen light on about a third of page loads. The prompt counter, placeholder and build clock were also too dim to read in either theme and are not any more. (`/create/prompt`) `[fix, improvement]`
- **Text-to-3D no longer hangs when the concept painter stalls**: Every text-to-3D generation starts by painting a concept image, and that step tried its image providers one after another with no overall time limit. When the first provider stalled, a request could sit for two and a half minutes before answering, and anything with a shorter patience (ChatGPT, agent clients) simply saw nothing. The painter now works to one shared budget: a slow provider hands off with real time left for the next one, and if the whole chain runs out you get a quick, honest retry-in-a-moment answer instead of a hang. Image-to-3D was never affected. (`/forge`) `[fix]`
- **The first-contribution guide now hands you real open work, and the docs sidebar can find it**: The 15-minute contributor guide walked through adding MikuMikuDance rig support as its example, but that support had already shipped, so anyone following it literally would have re-done merged work and been told a bone was unmapped when it was not. It now shows the MMD change as the finished reference, exactly as it landed with its tests, and points you at two rig conventions that are genuinely still open, each with the bones that fail today. The community, triage, and first-contribution pages also appear in the docs sidebar under Guides instead of being reachable only from the README, and the triage page now explains every label the repo actually uses. (`/docs/first-contribution`) `[docs, fix]`
@@ -3355,7 +3357,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr
- **Claim threews.sol Subdomain** (`/threews/claim`): Claim your own <name>.threews.sol subdomain and get a Brave-resolvable personal showcase page.
- **Dashboard** (`/dashboard`): Your account dashboard: agents, avatars, payments, keys, MCP servers, monetization, billing.
- **Dashboard · Account** (`/dashboard/account`): Manage connected wallets, SNS, delegation, and action log.
-- **Dashboard · Analytics** (`/dashboard/analytics`): API call volume, x402 spend, and per-agent usage breakdowns.
+- **Dashboard · Analytics** (`/dashboard/analytics`): Revenue over time, revenue by skill, widget views and chats, conversion funnel, and per-agent performance across your three.ws agents.
- **Dashboard · Settings** (`/dashboard/settings`): Avatar storage modes (R2 vs IPFS), sessions, your notification inbox, per-category notification channel preferences (in-app/push/email/Telegram), and dashboard preferences.
- **Full Animation & Emotion Control, Plus Pump.fun Live Feed** (`/blog/animation-emotion-control`): three.ws now ships full animation and emotion control for 3D agents, with live Pump.fun feed integration. Your agents react to any API or data feed in real time.
- **GMGN Smart Money** (`/gmgn`): Live smart-money signals narrated by a 3D AI agent. Tracks which wallets are loading on Solana, Ethereum, Base, and BNB Chain in real time.
diff --git a/data/changelog.json b/data/changelog.json
index 40006f9e9..9ee3b258d 100644
--- a/data/changelog.json
+++ b/data/changelog.json
@@ -4,7 +4,7 @@
{
"date": "2026-08-25",
"title": "Dashboard Analytics fits a phone screen and its failure page can actually reload",
- "summary": "On a 320px phone the time-range buttons refused to wrap, which pushed every panel below them past the right edge of the screen; they wrap now and nothing scrolls sideways. The rare shell-level failure page showed a Reload button that did nothing when tapped, so it now reloads. The page also stops requesting a monetization report it never displayed, and its search-engine description finally says what the page shows: revenue over time, revenue by skill, widget views and chats, the conversion funnel, and per-agent performance.",
+ "summary": "On a 320px phone the time-range buttons refused to wrap, which pushed every panel below them past the right edge of the screen; they wrap now and nothing scrolls sideways. The rare failure page showed a Reload button that did nothing when tapped, so it now reloads, and it explains what happened in plain language with a link to support instead of only printing a developer error string. A malformed response from one of the services behind the page no longer blanks the whole dashboard: the panel that depends on it degrades on its own and the rest still draws. The page also stops requesting a monetization report it never displayed, and its search-engine description finally says what the page shows: revenue over time, revenue by skill, widget views and chats, the conversion funnel, and per-agent performance.",
"tags": [
"fix",
"improvement"
diff --git a/public/changelog.json b/public/changelog.json
index ce665a4a5..a4d198591 100644
--- a/public/changelog.json
+++ b/public/changelog.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-08-25T17:06:41.379Z",
+ "generated_at": "2026-08-25T17:44:51.441Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json",
"site": {
"name": "three.ws",
@@ -36,6 +36,17 @@
"launch"
]
},
+ {
+ "date": "2026-08-25",
+ "type": "update",
+ "title": "Billing & Passes names your creators, keeps its retry buttons live, and the dashboard fits a phone screen",
+ "summary": "On /dashboard/billing, creator subscriptions now show the creator's name (linked to their profile), the real renewal or end date, a colour-coded status, and the plan price with its interval, instead of a raw account id. When the passes or subscriptions feed cannot be reached, the Retry button now actually reloads that section. Across every dashboard page, the top bar no longer forces the layout wider than a 320px phone screen, so nothing is clipped off the right edge.",
+ "link": "/dashboard/billing",
+ "tags": [
+ "fix",
+ "improvement"
+ ]
+ },
{
"date": "2026-08-25",
"type": "update",
@@ -90,6 +101,17 @@
"improvement"
]
},
+ {
+ "date": "2026-08-25",
+ "type": "update",
+ "title": "Dashboard Analytics fits a phone screen and its failure page can actually reload",
+ "summary": "On a 320px phone the time-range buttons refused to wrap, which pushed every panel below them past the right edge of the screen; they wrap now and nothing scrolls sideways. The rare failure page showed a Reload button that did nothing when tapped, so it now reloads, and it explains what happened in plain language with a link to support instead of only printing a developer error string. A malformed response from one of the services behind the page no longer blanks the whole dashboard: the panel that depends on it degrades on its own and the rest still draws. The page also stops requesting a monetization report it never displayed, and its search-engine description finally says what the page shows: revenue over time, revenue by skill, widget views and chats, the conversion funnel, and per-agent performance.",
+ "link": "/dashboard/analytics",
+ "tags": [
+ "fix",
+ "improvement"
+ ]
+ },
{
"date": "2026-08-25",
"type": "update",
@@ -32304,7 +32326,7 @@
"date": "2026-05-25",
"type": "launch",
"title": "Dashboard · Analytics",
- "summary": "API call volume, x402 spend, and per-agent usage breakdowns.",
+ "summary": "Revenue over time, revenue by skill, widget views and chats, conversion funnel, and per-agent performance across your three.ws agents.",
"link": "/dashboard/analytics",
"tags": [
"launch"
diff --git a/public/changelog.xml b/public/changelog.xml
index 9e951061d..8201a7606 100644
--- a/public/changelog.xml
+++ b/public/changelog.xml
@@ -30,6 +30,14 @@
<category>launch</category>
<description>The first three.ws weekly report: a week-by-week roundup of everything shipped from the first commit on 2026-04-14 through 2026-08-25, with every launch, partnership, announcement, and where $THREE fits.</description>
</item>
+ <item>
+ <title>Billing &amp; Passes names your creators, keeps its retry buttons live, and the dashboard fits a phone screen</title>
+ <link>https://three.ws/dashboard/billing</link>
+ <guid isPermaLink="false">2026-08-25:Billing &amp; Passes names your creators, keeps its retry buttons live, and the dashboard fits a phone screen</guid>
+ <pubDate>Tue, 25 Aug 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>On /dashboard/billing, creator subscriptions now show the creator's name (linked to their profile), the real renewal or end date, a colour-coded status, and the plan price with its interval, instead of a raw account id. When the passes or subscriptions feed cannot be reached, the Retry button now actually reloads that section. Across every dashboard page, the top bar no longer forces the layout wider than a 320px phone screen, so nothing is clipped off the right edge.</description>
+ </item>
<item>
<title>Compare reads correctly on a phone and stops mislabelling gains and losses</title>
<link>https://three.ws/compare</link>
@@ -70,6 +78,14 @@
<category>fix</category>
<description>Crew HQ refreshes who is in the world every 20 seconds, and it used to rebuild the whole room to do it: every member's 3D figure was destroyed and recreated four times a minute, which burns through the handful of live 3D canvases a browser will give a page and could catch a figure mid-load. The room now writes the new state into the figures already standing and only rebuilds when the roster itself changes, and opening a shared crew link no longer flashes the loading skeleton over a room that is already there. A member whose model cannot be loaded now shows their portrait on the plinth instead of an empty space. Signed-out visitors get a clean page: the sign-in-only crew request is no longer fired at all, the crew directory loads beside the room rather than behind it, and it stops listing the crew you are already looking at. A tag nobody flies offers the founding form only to someone who can actually take it, and a dropped connection now says what happened and how to retry instead of showing the browser's &quot;Failed to fetch&quot;.</description>
</item>
+ <item>
+ <title>Dashboard Analytics fits a phone screen and its failure page can actually reload</title>
+ <link>https://three.ws/dashboard/analytics</link>
+ <guid isPermaLink="false">2026-08-25:Dashboard Analytics fits a phone screen and its failure page can actually reload</guid>
+ <pubDate>Tue, 25 Aug 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>On a 320px phone the time-range buttons refused to wrap, which pushed every panel below them past the right edge of the screen; they wrap now and nothing scrolls sideways. The rare failure page showed a Reload button that did nothing when tapped, so it now reloads, and it explains what happened in plain language with a link to support instead of only printing a developer error string. A malformed response from one of the services behind the page no longer blanks the whole dashboard: the panel that depends on it degrades on its own and the rest still draws. The page also stops requesting a monetization report it never displayed, and its search-engine description finally says what the page shows: revenue over time, revenue by skill, widget views and chats, the conversion funnel, and per-agent performance.</description>
+ </item>
<item>
<title>Describe it to 3D stops offering a retry that cannot work, and finally follows your light theme</title>
<link>https://three.ws/create/prompt</link>
@@ -24644,7 +24660,7 @@
<guid isPermaLink="false">2026-05-25:Dashboard · Analytics</guid>
<pubDate>Mon, 25 May 2026 12:00:00 GMT</pubDate>
<category>launch</category>
- <description>API call volume, x402 spend, and per-agent usage breakdowns.</description>
+ <description>Revenue over time, revenue by skill, widget views and chats, conversion funnel, and per-agent performance across your three.ws agents.</description>
</item>
<item>
<title>Dashboard · Settings</title>
diff --git a/public/features.json b/public/features.json
index 5cfa734a1..813c81f32 100644
--- a/public/features.json
+++ b/public/features.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-08-25T17:06:41.173Z",
+ "generated_at": "2026-08-25T17:44:51.362Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json",
"site": {
"name": "three.ws",
@@ -2923,7 +2923,7 @@
{
"path": "/dashboard/analytics",
"title": "Dashboard · Analytics",
- "description": "API call volume, x402 spend, and per-agent usage breakdowns.",
+ "description": "Revenue over time, revenue by skill, widget views and chats, conversion funnel, and per-agent performance across your three.ws agents.",
"added": "2026-05-25",
"auth": "required",
"indexable": false,
diff --git a/public/llms-full.txt b/public/llms-full.txt
index 2d0844036..3eab51aeb 100644
--- a/public/llms-full.txt
+++ b/public/llms-full.txt
@@ -1781,7 +1781,7 @@ URL: https://three.ws/dashboard/analytics
Auth: required (sign-in)
Indexable: no (excluded from sitemap)
-API call volume, x402 spend, and per-agent usage breakdowns.
+Revenue over time, revenue by skill, widget views and chats, conversion funnel, and per-agent performance across your three.ws agents.
### Dashboard · Settings
diff --git a/public/sitemap/index.html b/public/sitemap/index.html
index 1c1548979..a62aa4bca 100644
--- a/public/sitemap/index.html
+++ b/public/sitemap/index.html
@@ -2254,7 +2254,7 @@
<a href="/dashboard/analytics">
<span class="sm-title">Dashboard · Analytics<span class="sm-badge sm-badge-auth">sign-in</span><span class="sm-badge sm-badge-internal">internal</span></span>
<span class="sm-path">/dashboard/analytics</span>
- <span class="sm-desc">API call volume, x402 spend, and per-agent usage breakdowns.</span>
+ <span class="sm-desc">Revenue over time, revenue by skill, widget views and chats, conversion funnel, and per-agent performance across your three.ws agents.</span>
</a>
</li>
<li>
diff --git a/src/dashboard-next/pages/analytics.js b/src/dashboard-next/pages/analytics.js
index 26d48053a..08d2bd611 100644
--- a/src/dashboard-next/pages/analytics.js
+++ b/src/dashboard-next/pages/analytics.js
@@ -37,7 +37,7 @@ let me = null;
return;
}
const main = document.querySelector('.dn-main-inner') || document.body;
- main.innerHTML = `<h1 class="dn-h1">Analytics</h1><div class="dn-panel"><div class="dn-panel-title" style="color:var(--nxt-danger)">Failed to load</div><div class="dn-panel-sub">${esc(err?.message || 'unknown')}</div><button type="button" class="dn-btn" data-action="reload">Reload</button></div>`;
+ main.innerHTML = `<h1 class="dn-h1">Analytics</h1><div class="dn-panel"><div class="dn-panel-title" style="color:var(--nxt-danger)">Analytics could not be drawn</div><div class="dn-panel-sub">Something went wrong while building this page. Reloading usually clears it. If it keeps happening, <a href="/support">tell us</a> and quote the detail below.</div><div class="dn-panel-sub" style="margin-top:6px;font-family:ui-monospace,SFMono-Regular,Menlo,monospace;font-size:11px;opacity:0.7">${esc(err?.message || 'unknown error')}</div><button type="button" class="dn-btn" data-action="reload" style="margin-top:12px">Reload</button></div>`;
main.querySelector('[data-action="reload"]')?.addEventListener('click', () => location.reload());
});
@@ -88,8 +88,11 @@ async function loadAndRender(root) {
return;
}
- const agentList = agents?.agents ?? [];
- const widgetList = widgets?.widgets ?? [];
+ // Shape-guard the collections rather than trusting the payload: an upstream
+ // that answers 200 with a non-array (a deploy skew, a proxy error page parsed
+ // as JSON) would otherwise throw out of here and blank the whole page.
+ const agentList = Array.isArray(agents?.agents) ? agents.agents : [];
+ const widgetList = Array.isArray(widgets?.widgets) ? widgets.widgets : [];
const widgetStats = await Promise.all(
widgetList.slice(0, 20).map(w =>
@@ -110,8 +113,8 @@ async function loadAndRender(root) {
const revTotal = Number(revenue?.summary?.net_total ?? 0);
const revPayments = Number(revenue?.summary?.payment_count ?? 0);
- const timeseries = revenue?.timeseries ?? [];
- const bySkill = revenue?.by_skill ?? [];
+ const timeseries = Array.isArray(revenue?.timeseries) ? revenue.timeseries : [];
+ const bySkill = Array.isArray(revenue?.by_skill) ? revenue.by_skill : [];
// Fetch per-agent payments for the activity table
const recentPayments = await fetchRecentActivity(agentList);