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.

build(nav): surface the new pages in the footer, README and API reference

nirholas6c3a6e42ff40
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 561343184..a4860d985 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -37,8 +37,10 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr
- **Agent payments now stop themselves when the fee wallet runs dry**: The platform sponsors the network fee on every agent payment. When that wallet ran down to the point where it could not cover a single fee, the check meant to pause payments could not run, because it depended on a balance lookup and the network providers were rate-limited at the same moment. Payments kept being attempted for three hours and none of them could complete. The pause now reads its answer from the failure itself, which costs nothing and works exactly when the network is too busy to answer questions. The status page also names the real cause now, a wallet that needs funding, instead of pointing at the payment rail. `[fix, infra]`
- **AI agents can now see the 3D models they make**: Until today every 3D generator on the internet, ours included, answered with a link to a file an AI agent cannot open. A person clicks it; an agent is blind to it, which is why an agent that makes a 3D model has never been able to tell a clean one from a melted one. That changes now: ask to look at any model and it comes back rendered from four angles as actual pictures the agent sees, with the geometry explained in plain language. An agent can finally check its own work, spot that the back of the model was never finished, and try again saying exactly what was wrong. It works over MCP, over a plain web request, and through a new open-source package called @three-ws/see, and it is free, including for agents that bought a model from us and want to confirm they got what they paid for. (`/docs/3d-vision`) `[feature, sdk]`
- **Every release note now shows you the code that shipped it**: Until today this site kept two separate records of the same work: a changelog written for people, and a commit feed written by engineers, neither aware of the other. The new ship log joins them. Each release note now lists the commits that produced it, and says how confident it is in each match and why it made it, in plain words you can argue with. Commits nobody ever wrote up are grouped and shown too, so the work that shipped quietly is visible instead of lost. The announcements in the Telegram channel now carry a link to the exact code behind them, the raw commit feed reads in plain language instead of engineering shorthand, and it no longer posts merges or dependency bumps. The whole thing is a free, open-source package that works on anyone's repository. (`/ship`) `[feature, sdk, improvement]`
+- **Glance: your agent on your Windows home screen, in your README, and in your terminal**: Your agent now has a card: its name, what it did in the last 24 hours, when it last acted, and a tap straight back into it. Pin it to the Windows 11 widgets board and it installs with the site itself, no app store, and refreshes on its own every fifteen minutes; signed out it shows a sign-in card instead of an error, and offline it keeps showing the last card it saw. The same card is one image URL you can paste into a GitHub README, a Slack message, or any page, and it follows the reader's light or dark mode. There is a live element for websites, a command you can run in a terminal to watch an agent work, and an npm package for building your own. Android is next, then macOS and iOS. (`/glance`) `[feature, sdk]`
- **Herald: your terminal can now make a 3D character walk onto your screen and talk to you**: We took the part of three.ws where an avatar delivers a notification in person and turned it into something anyone can use, on any website. @three-ws/herald is an open library: one line of code and a 3D character walks into the corner of your page, looks at the person using it, and tells them, with a link to the thing it is about. It is not a toast library. It is an interrupt budget: an importance floor, quiet hours, a rate limit, dedupe, freshness, batch collapse, and a stable reason for every message it refuses to deliver, so you can always answer why you did not hear about something. No GPU, an iframe, or reduced motion falls back to an accessible card that screen readers announce the same moment everyone else hears it. There is also a rail: with an API key, anything that can make an HTTPS request reaches the browser tab you already have open. Run npx @three-ws/herald watch -- npm test and your avatar tells you when the build finishes, keeping the exit code. Wire the MCP server into Claude or Cursor and an agent that worked for twenty minutes can walk on and tell you it is done. An announcement always goes to your own sessions, so no key can interrupt anyone but its owner. Try the whole thing, rules engine included, at three.ws/herald. (`/herald`) `[feature, sdk]`
- **Knock: put a price on reaching you, and hear what gets through in person**: Every account can now open a door at three.ws/knock/<username> and set what one message from a stranger is worth, anywhere from a tenth of a cent to a thousand dollars, or free. Anyone can pay it to get exactly one message through: a person pays with the wallet already in their browser, and an agent pays over x402 with no human involved. The USDC settles straight to your own wallet; three.ws never holds it and takes none of it. What arrives is not another badge: your 3D companion walks on screen wherever you are on the site and says who is at the door and what they paid, ranked by that amount, so the expensive ones interrupt and the free ones wait in the feed. You set the price, the daily cap, the message length and a block list, and every one of those refusals happens before any payment, so a message that was never going to land is never one somebody was charged for. Only the one-line subject is ever read aloud. Senders get a receipt link they can check for your reply without an account here, which means answering someone never hands out your address. There is a browsable directory of open doors, an npm package and CLI for agents (@three-ws/knock), and an MCP server (@three-ws/knock-mcp) that deliberately holds no wallet: it quotes a paid door and stops, so a human always approves the spend. (`/knock`) `[feature, sdk]`
+- **Model Diff: see exactly what changed between two 3D models**: Every 3D pipeline has one failure that costs more than all the others put together, and it is completely silent. Animation clips find a character's joints by name. Rename a bone, drop a joint, or run a file through a tool that renumbers things, and the model still loads, still renders, and never moves again. Nothing errors. You find out when somebody tells you the character is standing there frozen. Model Diff is the check that catches it. Drop two files and it tells you what actually changed: the geometry, the materials, the textures, the skeleton, the clips, with renames recognised as renames instead of one thing vanishing and an unrelated thing appearing. It ignores the meaningless noise a re-export always introduces and flags the edits that matter, and it grades every difference, so you can tell a recoloured jacket from a rig that just lost both eye joints. Both models load into the same 3D scene: lay one over the other, drag a line across to wipe between them, or stand them side by side, and click any line in the report to fly the camera to the thing it names. Nothing you drop is uploaded. The same engine is a free API anyone can call without a key, a command you can put in a build so a broken export fails it, and a tool your AI agent can use to check its own work before it publishes it. (`/diff`) `[feature, sdk, improvement]`
- **Next on the roadmap: your agent on your home screen**: A fifth phase has been added to the public roadmap: native widgets. Right now three.ws is something you open. The plan is for the agent you own to sit on your home screen and your desktop, showing itself and one live number about it, refreshed by the system without you opening anything, with a tap that drops you back into the right screen. Android is first, because the Android app is already built and signed: three.ws ships as a real app for Solana Seeker, and as of today Google confirms the app's release key against the site, so a three.ws link opens inside the app instead of a browser tab. Windows 11 follows through the installed web app, which needs no separate store submission, then macOS and iOS through a shared widget extension. None of it is shipped yet. It is written down, scoped and public so you can hold us to it, and the phase is on the roadmap in the repo along with the work order behind it. `[docs]`
- **Photo uploads, avatar saves, launches and team tasks fail fast instead of hanging**: A handful of steps still had no time limit on the outside service they called. When that service accepted the connection and then went quiet, the request sat there until the platform killed it, and you got a spinner that ended in nothing: a photo-to-avatar upload that never came back, a saved model that never finished downloading, a coin launch stuck fetching its own thumbnail, an ordinals order whose status never loaded, a team task where one hired agent held up the whole run. Each of those now has a deadline and a clear answer when it is missed, and the ones that are safe to repeat retry once first. Anything that spends money or starts a generation is never repeated: it is bounded and then reported, so no upload is billed twice and no hire is paid twice. Saving a model from a link is also checked more tightly now, against the address it actually connects to and with the size limit applied while it downloads. `[improvement, fix, infra]`
- **Report a bug and it arrives as a test that fails until it is fixed**: When you tell the agent in the corner that something is broken, it now sends what you actually did: the steps you took, the page, and the error the browser saw. Those steps compile into a real test that fails while the bug is there and passes once it is gone, so the slowest part of fixing anything (working out how to make it happen again) is done before anyone starts. You can see every step that gets attached before you send, and nothing you typed into a field is ever recorded, only how much. The recorder is open source and works on any site: install @three-ws/witness. (`/docs/witness`) `[feature, sdk, improvement]`
diff --git a/README.md b/README.md
index 5e266fc38..c7df56ceb 100644
--- a/README.md
+++ b/README.md
@@ -10652,7 +10652,7 @@ three.ws ships in five phases. Each phase closes a specific gap between the curr
| **2** | Agent personalization + voice cloning | 🟡 In progress — voice clone, persona, memory seeds shipped behind `/demos`; main-flow integration next |
| **3** | Onchain economy (agent tokens, reputation markets, royalties) | 🟡 In progress: bonding-curve sim, EAS-reputation viewer, 0xsplits + EAS SDKs landed; per-call skill royalties accrue on paid skill calls (`royalty_ledger`); contracts + audits next |
| **4** | Open inference network (decentralized GPU layer) | 🟡 Live core: open node-operator client (CPU + CUDA images) + `/api/nodes` job queue with signed, server-recomputed receipts shipped; Livepeer federation behind a flag |
-| **5** | Native widgets (agent on your home screen and desktop) | 🔵 Planned: Android app widget inside the shipped `ws.three.app` TWA first, then Windows 11, then macOS and iOS |
+| **5** | Native widgets (agent on your home screen and desktop) | 🟡 In progress: Glance shipped the card endpoint, the Windows 11 widget (installs from the PWA manifest, no store) and the `<agent-glance>` element; Android app widget next, then macOS and iOS |
---
@@ -10772,20 +10772,22 @@ This is a different product from the embeddable web widgets at [three.ws/widgets
**Order of delivery**
-| # | Surface | Shell needed | Notes |
-| - | ------- | ------------ | ----- |
-| 1 | Android home screen | Already shipped (`ws.three.app`) | Native `AppWidgetProvider` overlay added to the Bubblewrap project, refreshed by `WorkManager`, tapping deep links into the TWA |
-| 2 | Windows 11 widgets board | None | The installed PWA declares a `widgets` manifest member and an Adaptive Card template; the service worker answers `widgetinstall` and `widgetclick` |
-| 3 | macOS | Small SwiftUI host app | WidgetKit extension plus a menu bar companion; needs an Apple Developer account |
-| 4 | iOS | App Store wrapper | Same WidgetKit extension target as macOS; gated on shipping the iOS app itself |
+| # | Surface | Shell needed | Status |
+| - | ------- | ------------ | ------ |
+| 1 | Windows 11 widgets board | None | **Shipped.** The installed PWA declares a `widgets` manifest member and an Adaptive Card template ([/api/glance/template](api/glance/template.js)); the service worker ([public/glance-sw.js](public/glance-sw.js)) answers `widgetinstall`, `widgetresume`, `widgetclick` and `periodicsync` |
+| 2 | Any web page | None | **Shipped.** `<agent-glance>` ([public/glance/element.js](public/glance/element.js)), plus one SVG URL for a README, a Slack unfurl, or any `<img>` |
+| 3 | Android home screen | Already shipped (`ws.three.app`) | Next. Native `AppWidgetProvider` overlay added to the Bubblewrap project, refreshed by `WorkManager`, tapping deep links into the TWA. The card endpoint it needs is live |
+| 4 | macOS | Small SwiftUI host app | WidgetKit extension plus a menu bar companion; needs an Apple Developer account |
+| 5 | iOS | App Store wrapper | Same WidgetKit extension target as macOS; gated on shipping the iOS app itself |
**Deliverables**
-- A cacheable widget data endpoint: one signed, per-account URL returning the agent card as a PNG (Android, macOS, iOS) and as JSON for the Windows Adaptive Card, built on the existing render pipeline rather than a second renderer
+- ✅ A cacheable card endpoint, [/api/glance/card](api/glance/card.js), serving one model as JSON, SVG and Adaptive Card, plus [/api/glance/mine](api/glance/mine.js) for the signed-in owner's own agent. Spec: [specs/GLANCE_CARD.md](specs/GLANCE_CARD.md)
+- ✅ Windows 11 widget through the PWA manifest, so it installs with no separate store submission, degrading to the last cached card when the machine is offline and to a sign-in card when nobody is signed in
+- ✅ Card content that is worth a home screen slot: the agent, one live number (actions in the last 24 hours), its last action, and a direct way back in
+- ✅ A playground and install guide at [/glance](public/glance/index.html), and an npm client, [@three-ws/agent-glance](packages/agent-glance), with a terminal renderer
- Android app widget in three sizes, refreshed on a battery-aware schedule, degrading to the last cached card when the device is offline
-- Windows 11 widget through the PWA manifest, so it installs with no separate store submission
- A native shell for Apple platforms, which is also the prerequisite for an iOS build of three.ws
-- Widget content that is worth a home screen slot: the agent, its recent activity, and a direct action (create, chat, open my agents)
**Verification:** a widget installed from the Android app updates without opening the app, survives a reboot and airplane mode, and returns the user into the right screen on tap. Work order: [prompts/roadmap/native-widgets.md](prompts/roadmap/native-widgets.md).
diff --git a/data/changelog.json b/data/changelog.json
index 047875b70..e0e1e018d 100644
--- a/data/changelog.json
+++ b/data/changelog.json
@@ -1,6 +1,27 @@
{
"$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-28",
+ "title": "Model Diff: see exactly what changed between two 3D models",
+ "summary": "Every 3D pipeline has one failure that costs more than all the others put together, and it is completely silent. Animation clips find a character's joints by name. Rename a bone, drop a joint, or run a file through a tool that renumbers things, and the model still loads, still renders, and never moves again. Nothing errors. You find out when somebody tells you the character is standing there frozen. Model Diff is the check that catches it. Drop two files and it tells you what actually changed: the geometry, the materials, the textures, the skeleton, the clips, with renames recognised as renames instead of one thing vanishing and an unrelated thing appearing. It ignores the meaningless noise a re-export always introduces and flags the edits that matter, and it grades every difference, so you can tell a recoloured jacket from a rig that just lost both eye joints. Both models load into the same 3D scene: lay one over the other, drag a line across to wipe between them, or stand them side by side, and click any line in the report to fly the camera to the thing it names. Nothing you drop is uploaded. The same engine is a free API anyone can call without a key, a command you can put in a build so a broken export fails it, and a tool your AI agent can use to check its own work before it publishes it.",
+ "tags": [
+ "feature",
+ "sdk",
+ "improvement"
+ ],
+ "link": "/diff"
+ },
+ {
+ "date": "2026-08-28",
+ "title": "Glance: your agent on your Windows home screen, in your README, and in your terminal",
+ "summary": "Your agent now has a card: its name, what it did in the last 24 hours, when it last acted, and a tap straight back into it. Pin it to the Windows 11 widgets board and it installs with the site itself, no app store, and refreshes on its own every fifteen minutes; signed out it shows a sign-in card instead of an error, and offline it keeps showing the last card it saw. The same card is one image URL you can paste into a GitHub README, a Slack message, or any page, and it follows the reader's light or dark mode. There is a live element for websites, a command you can run in a terminal to watch an agent work, and an npm package for building your own. Android is next, then macOS and iOS.",
+ "tags": [
+ "feature",
+ "sdk"
+ ],
+ "link": "/glance"
+ },
{
"date": "2026-08-28",
"title": "Herald: your terminal can now make a 3D character walk onto your screen and talk to you",
diff --git a/docs/api-reference.md b/docs/api-reference.md
index 1d7afcac6..df846bd04 100644
--- a/docs/api-reference.md
+++ b/docs/api-reference.md
@@ -1574,11 +1574,13 @@ GET /api/render/glb?glbUrl=<url>&width=1200&height=630&background=%230a0a0a
POST /api/render/glb { "glbUrl": "...", "width": 1024, "height": 1024, "background": "#0a0a0a" }
```
-Public renderer: any public GLB URL in, a PNG out (headless chromium +
-`<model-viewer>`, the same pipeline the OG cards use). The GET form makes a
-render URL-addressable for `og:image` unfurls, `<img>` tags, and markdown
-embeds; responses CDN-cache for a day so crawlers hit chromium once per
-model. Dimensions clamp to 64-2048; GLBs over 10 MB are rejected before the
+Public renderer: any public GLB URL in, a PNG out, the same pipeline the OG
+cards use. Renders run on a CPU software rasterizer in-process (typically
+200-900 ms, no browser); headless chromium stays as the failover for models
+whose geometry or textures need a decoder the rasterizer does not ship (Draco,
+KTX2/Basis). The GET form makes a render URL-addressable for `og:image`
+unfurls, `<img>` tags, and markdown embeds; responses CDN-cache for a day so
+crawlers render once per model. Dimensions clamp to 64-2048; GLBs over 10 MB are rejected before the
browser boots; only public http(s) sources are fetched (SSRF-guarded);
60 renders / 10 min / IP, a budget shared with `/api/render/avatar-clip`.
@@ -1612,6 +1614,50 @@ failing. `cameraOrbit.theta`/`phi` are degrees (yaw, and pitch from the top);
`posePresetId` is `400 unknown_pose`. Same 10 MB cap, SSRF guard, and render
budget as `/api/render/glb`.
+### Animated avatar renderer: `GET /api/render/animate`
+
+```
+GET /api/render/animate (the clip catalog)
+GET /api/render/animate?avatar=<id>&clip=wave
+GET /api/render/animate?src=https://example.com/model.glb&clip=idle&size=256
+→ image/png (an animated PNG)
+```
+
+One URL, one file, a moving avatar. The response is an animated PNG, so it
+plays anywhere a still image works: an `<img>` tag, a GitHub README, a Notion
+page, a Discord embed. There is no player, no script and no WebGL involved on
+either side.
+
+```markdown
+![my agent](https://three.ws/api/render/animate?avatar=<id>&clip=wave&size=256)
+```
+
+| Parameter | Meaning |
+|---|---|
+| `avatar` | Avatar UUID. Public avatars only; a private one is `404`. |
+| `src` | Any public GLB URL instead of an avatar id (SSRF-guarded, 12 MB cap). |
+| `clip` | Clip name from the catalog above. Default `idle`. |
+| `frames` | 1-48, default 20. |
+| `fps` | 1-30, default 16. |
+| `size` | 64-640 square, default 320. `width`/`height` override it. |
+| `bg` | `transparent` (default) or a CSS colour. |
+| `focus` | `full`, `bust` or `head`. Default `full`. |
+| `spin` | 0-360 degrees of turntable spread across the loop. |
+| `t` | Seconds into the clip for the first frame. |
+
+The clip is retargeted onto the model's own skeleton by bone name, so one
+library clip drives Ready Player Me, Avaturn, VRM, Mixamo and Blender rigs
+alike. A body that cannot take the clip (no humanoid skeleton) still animates:
+the loop falls back to a full turntable rather than an error.
+
+Calling with no parameters returns the catalog: every clip name, label and
+duration in the built-in motion library. Unknown clip names are
+`400 unknown_clip` and list the alternatives. Same 60 renders / 10 min / IP
+budget as the renderers above; responses CDN-cache for a week.
+
+Rendering is done by [`@three-ws/render`](../packages/render/README.md), the
+GPU-free software rasterizer that also backs the OG cards.
+
### Forge-Off votes — `POST /api/forge-vote`
```
diff --git a/public/changelog.xml b/public/changelog.xml
index 18f0bad1e..58d9c258c 100644
--- a/public/changelog.xml
+++ b/public/changelog.xml
@@ -254,6 +254,14 @@
<category>feature</category>
<description>Until today this site kept two separate records of the same work: a changelog written for people, and a commit feed written by engineers, neither aware of the other. The new ship log joins them. Each release note now lists the commits that produced it, and says how confident it is in each match and why it made it, in plain words you can argue with. Commits nobody ever wrote up are grouped and shown too, so the work that shipped quietly is visible instead of lost. The announcements in the Telegram channel now carry a link to the exact code behind them, the raw commit feed reads in plain language instead of engineering shorthand, and it no longer posts merges or dependency bumps. The whole thing is a free, open-source package that works on anyone's repository.</description>
</item>
+ <item>
+ <title>Glance: your agent on your Windows home screen, in your README, and in your terminal</title>
+ <link>https://three.ws/glance</link>
+ <guid isPermaLink="false">2026-08-28:Glance: your agent on your Windows home screen, in your README, and in your terminal</guid>
+ <pubDate>Fri, 28 Aug 2026 12:00:00 GMT</pubDate>
+ <category>feature</category>
+ <description>Your agent now has a card: its name, what it did in the last 24 hours, when it last acted, and a tap straight back into it. Pin it to the Windows 11 widgets board and it installs with the site itself, no app store, and refreshes on its own every fifteen minutes; signed out it shows a sign-in card instead of an error, and offline it keeps showing the last card it saw. The same card is one image URL you can paste into a GitHub README, a Slack message, or any page, and it follows the reader's light or dark mode. There is a live element for websites, a command you can run in a terminal to watch an agent work, and an npm package for building your own. Android is next, then macOS and iOS.</description>
+ </item>
<item>
<title>Herald: your terminal can now make a 3D character walk onto your screen and talk to you</title>
<link>https://three.ws/herald</link>
@@ -270,6 +278,14 @@
<category>feature</category>
<description>Every account can now open a door at three.ws/knock/&lt;username&gt; and set what one message from a stranger is worth, anywhere from a tenth of a cent to a thousand dollars, or free. Anyone can pay it to get exactly one message through: a person pays with the wallet already in their browser, and an agent pays over x402 with no human involved. The USDC settles straight to your own wallet; three.ws never holds it and takes none of it. What arrives is not another badge: your 3D companion walks on screen wherever you are on the site and says who is at the door and what they paid, ranked by that amount, so the expensive ones interrupt and the free ones wait in the feed. You set the price, the daily cap, the message length and a block list, and every one of those refusals happens before any payment, so a message that was never going to land is never one somebody was charged for. Only the one-line subject is ever read aloud. Senders get a receipt link they can check for your reply without an account here, which means answering someone never hands out your address. There is a browsable directory of open doors, an npm package and CLI for agents (@three-ws/knock), and an MCP server (@three-ws/knock-mcp) that deliberately holds no wallet: it quotes a paid door and stops, so a human always approves the spend.</description>
</item>
+ <item>
+ <title>Model Diff: see exactly what changed between two 3D models</title>
+ <link>https://three.ws/diff</link>
+ <guid isPermaLink="false">2026-08-28:Model Diff: see exactly what changed between two 3D models</guid>
+ <pubDate>Fri, 28 Aug 2026 12:00:00 GMT</pubDate>
+ <category>feature</category>
+ <description>Every 3D pipeline has one failure that costs more than all the others put together, and it is completely silent. Animation clips find a character's joints by name. Rename a bone, drop a joint, or run a file through a tool that renumbers things, and the model still loads, still renders, and never moves again. Nothing errors. You find out when somebody tells you the character is standing there frozen. Model Diff is the check that catches it. Drop two files and it tells you what actually changed: the geometry, the materials, the textures, the skeleton, the clips, with renames recognised as renames instead of one thing vanishing and an unrelated thing appearing. It ignores the meaningless noise a re-export always introduces and flags the edits that matter, and it grades every difference, so you can tell a recoloured jacket from a rig that just lost both eye joints. Both models load into the same 3D scene: lay one over the other, drag a line across to wipe between them, or stand them side by side, and click any line in the report to fly the camera to the thing it names. Nothing you drop is uploaded. The same engine is a free API anyone can call without a key, a command you can put in a build so a broken export fails it, and a tool your AI agent can use to check its own work before it publishes it.</description>
+ </item>
<item>
<title>Next on the roadmap: your agent on your home screen</title>
<link>https://three.ws/changelog</link>
diff --git a/public/footer.html b/public/footer.html
index 9f41e6fc6..8511ae722 100644
--- a/public/footer.html
+++ b/public/footer.html
@@ -78,6 +78,7 @@
<div class="h-footer-link-col">
<h3 class="h-footer-link-heading" data-i18n="footer.developers">Developers</h3>
<a href="/docs" data-i18n="footer.docs">Docs</a>
+ <a href="/ship" data-i18n="footer.ship_log">Ship log</a>
<a href="/crypto-api" data-i18n="footer.crypto_api">Crypto API</a>
<a href="/status" data-i18n="footer.status">Status</a>
<a href="/support" data-i18n="footer.support">Support</a>
diff --git a/public/locales/en.json b/public/locales/en.json
index c8ce332eb..f8d5dd54e 100644
--- a/public/locales/en.json
+++ b/public/locales/en.json
@@ -7712,6 +7712,7 @@
"privacy_policy": "Privacy Policy",
"product": "Product",
"resources": "Resources",
+ "ship_log": "Ship log",
"sitemap": "Sitemap",
"solscan": "Solscan",
"status": "Status",