Skip to content

Open-source platform for 3D AI agents. Turn text or a photo into a rigged, animated GLB avatar, give it an LLM brain, memory and a wallet, and embed it anywhere with one web component. Remote MCP server, x402 payments, Three.js, browser-native.

chore(order-409): regenerate derived pages, note test:core drop, file order 410 for a pre-existing docs gap

nirholas03ec4735ec43
diff --git a/CHANGELOG.md b/CHANGELOG.md
index f33cc33c2..1ca939e91 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -17,6 +17,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr
- **Desktop app moves to Electron 45**: The desktop app now runs on Electron 45 and electron-builder 26, clearing 61 security advisories from the old Electron 33 toolchain. Launch at login still starts the app hidden in the tray; on Windows, toggle the setting once if the console window opens at login. `[desktop, security]`
- **Drive the CLI from scripts and agents, and download a run report**: Every three-ws command now takes --json (one JSON document on stdout, diagnostics on stderr) and --non-interactive (never prompts), with a stable exit-code table: 2 usage, 3 auth, 4 refused by a guard, 5 payment required, 6 network. New commands cover agents, runs, wallet balance, skill install and orders. `three-ws report run <id> --out run.html` writes one self-contained offline file with the goal, tool calls, decisions, trades, outcome and the decision-trail head hash, and the run page has a matching Download report button. (`/docs/cli`) `[feature, sdk]`
- **Engine bridges are packaged for the Unity, Godot and Unreal stores**: One command, npm run package:engine-stores, validates the Unity, Godot and Unreal bridges and builds a reproducible upload package for each, with listing metadata and a submission checklist. The Unity package and Unreal plugin manifests now carry their documentation links. (`/docs/engine-store-publishing`) `[sdk, docs]`
+- **Fixed three more legacy thumbnail links that browsers refused to load**: A handful of forge creations and 3D props stored from before an earlier URL fix still pointed straight at the storage bucket's own domain instead of three.ws's own CDN link, which Chrome blocks as an opaque cross-origin response. Model-page posters, a creation's related-models sidebar, forge share-card previews (the image X and Discord show when a link is pasted), and the Forged gallery's model-viewer thumbnails now all resolve through the same CDN link as everything else. (`/forge`) `[fix]`
- **Hundreds of dependency security advisories cleared across the repo**: Every committed lockfile was audited and patched: same-line security releases everywhere, vetted moves to patched majors (vitest 4, zod 4, helia 7, Svelte 5 and Vite 7 in the chat app, transformers 4 in HQ, gltf-transform 4 for the meshopt worker), and each package's tests and builds were rerun before and after. What remains are advisories with no patched release published anywhere (bigint-buffer, elliptic, node-forge) and pins that upstream SDKs still require. `[security, infra]`
- **Install the three.ws skills with one command on any agent runtime**: Run npx skills add nirholas/three-ws-skills (or the 3D-only and agent-economy repos) to install the three.ws skills into Claude Code, Codex, Cursor and any other runtime that reads the open Agent Skills format. Every skill now passes the Agent Skills spec validator, which fixed 21 skills whose frontmatter some installers could not parse, and an install test proves each repo lists and installs every skill in a clean directory. Publishing the repos is still the owner's step. (`/docs/agent-skills`) `[feature, docs]`
- **Long MCP answers arrive as a summary, and agents can search the docs**: list_my_agents, recall and crypto_data now answer with a short summary, a count, a handle and the first page when the list is long, and the new expand tool reads the rest on request. A 100-coin market list drops from about 47,800 to 4,400 tokens. Handles are signed, account-bound and last 15 minutes. The new free search_docs tool answers how-to questions from the docs index on the main and studio servers. (`/docs/mcp`) `[feature, docs]`
@@ -61,6 +62,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr
- **An agent can sign itself up and pay for its plan**: An autonomous agent now signs up with a Solana key and no email: it signs a single-use server challenge, receives an account, a custodial wallet and an API key, and can then buy the Builder or Scale plan with one USDC x402 payment on Solana. The CLI does the whole thing with `three-ws signup --agent`. Replayed or badly signed challenges are rejected, each key gets one account, and signups are rate limited and capped per day. (`/docs/agent-self-onboarding`) `[feature, sdk]`
- **AR Studio source now lives in the monorepo**: The 3d-ar-studio npm package and the /ar/studio page now run the same code: the package source moved into packages/ar-studio and the page imports its scene math, multi-anchor WebXR session, room client and lighting modules directly, so fixes land once instead of in two diverging copies. (`/ar/studio`) `[sdk, improvement]`
- **Backtests now prove they are free of look-ahead and can be repeated**: Every strategy backtest replays its entry gate with the future removed and reports any decision that changed, pins the exact dataset it ran on with a content hash, and marks older unpinned results as unreproducible. A new canary job checks each price and candle source against a known value every 30 minutes and tries the healthy ones first. (`/strategies`) `[feature]`
+- **Bonding-curve status API no longer hard-fails when pump.fun blips**: GET /api/crypto/bonding was returning a 503 to every caller during a pump.fun outage, even for mints it had already fetched successfully. It now caches each mint's bonding-curve status and keeps a longer last-known-good copy, so a failed upstream fetch serves that cached data (flagged with an x-pump-stale header) instead of a hard error. A 503 with a retry hint is now only returned for a mint that has no cached data at all. (`/api/crypto/bonding`) `[fix]`
- **Chain turnover on /chains**: The chains leaderboard now has a sortable Turnover column (24h DEX volume divided by TVL) that shows which chains have capital actively trading rather than parked. Chains with no TVL or no reported volume show n/a. (`/chains`) `[feature]`
- **Coin intel funder map is now a 3D graph**: The wallet network in the coin intel drawer renders as a GPU-instanced 3D force graph, with wallets sized by holdings and linked to their shared funder, a live-trades toggle, and reduced-motion support. Browsers without WebGL keep the 2D map. (`/coin-intel`) `[feature]`
- **Copy any model as a GitHub README 3D block**: Forge results, avatar pages, the avatar dashboard and model pages now have a Copy as GitHub README 3D action. It simplifies the model to a size GitHub renders and puts a stl code fence on your clipboard that GitHub shows as an interactive 3D viewer in any README, issue or pull request. The same converter is a free API (POST /api/readme-3d) and has a live page at /readme-3d. (`/readme-3d`) `[feature]`
@@ -321,7 +323,6 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr
- **Claim your X creations** (`/x/claim`): Models and avatars the three.ws bot made for you on X wait here. Link the same X account and every one of them moves into your library.
- **Docs · CAD Forge (text to parametric CAD)** (`/docs/cad-forge`): How a sentence becomes a kernel-checked build123d part: the write, build and repair loop, dimension parameters, the design page, the /api/cad HTTP API, the cad_generate and cad_rebuild MCP tools, and the sandbox that runs model-written code.
- **Docs · Grok Bot connector reference** (`/docs/grok-bot`): Connect Grok Bot to three.ws as a custom MCP connector: exact fields for each sign-in mode, which server to pick, the links every result carries, jobs and safe retries, free limits and install tokens, why a connector key can never spend, guided prompts, and a fix for every connection failure.
-- **Docs · Grok Bot connector reference** (`/docs/grok-bot`): Exact connector settings for Grok Bot, which sign-in and which server to pick, the links, jobs, retry and rate-limit contracts for unattended runs, the spend rule, and a fix for every failure the connector probe can report.
- **Docs · Modly and three.ws** (`/docs/modly`): Every way three.ws works with Modly, the free open-source 3D app: generate on your own GPU from /modly or the Forge, add three.ws cloud nodes and publishing to Modly, the desktop app, and the mesh tools and slicer handoff built from Modly ideas.
- **Docs · three.ws Forge for desktop** (`/docs/forge-desktop`): How to install and use three.ws Forge, the desktop 3D studio: run it from source or an installer, generate on your own GPU or the three.ws cloud, build node workflows, import CC0 models, sign in and publish to three.ws, and fix common setup problems.
- **Docs · Workbench** (`/docs/workbench`): How the Workbench runs a photo through an editable workflow of real GPU nodes, edits the result in the viewport, exports GLB, OBJ, STL or PLY, and how scripts call the same pipeline.
@@ -331,7 +332,6 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr
- **The Crawl** (`/crawl`): Watch three.ws agents read the open web in real browsers, live. Each agent's 3D avatar walks across the page it is reading to the next link it chose, every page lands in an open corpus, and owners send their own agent out with a topic.
- **three.ws for Grok Bot: a free 3D studio and a body for Grok** (`/grok`): Everything Grok Bot can do with three.ws on one page: generate textured 3D models, rig avatars, find ready-made CC0 assets and run your agents through one custom MCP connector. Real models made minutes ago, the exact connector settings, three recipes to schedule and the Grok skill file. Free, no account, no key.
- **three.ws Forge for Desktop** (`/forge-desktop`): Download three.ws Forge, the free desktop 3D studio for Windows, Linux and Apple silicon Macs. Turn a photo into a 3D model with open-source generators on your own GPU or the three.ws cloud, chain repair, remeshing, rigging and export in node workflows, import free CC0 models and publish to your three.ws account in one click. Based on Modly (MIT).
-- **Tutorial · Grok Bot recipes** (`/tutorials/grok-bot-recipes`): Six jobs to hand Grok Bot, each with the exact sentence, the tools it calls in order, and the real output of running that sequence against production: a daily 3D brief, a game jam asset pack, an avatar from a photo, an X post image as a 3D model, a weekly agent report and a $THREE market brief.
- **Workbench** (`/workbench`): A desktop-style image-to-3D workspace in the browser. Drop a photo, run it through a visual workflow of real GPU nodes (background removal, mesh generation, remeshing, auto-rigging, AI material restyle), then smooth, decimate and export GLB, OBJ, STL or PLY. Build and save your own workflows in a node editor. Free, no signup.
- **A build plan for the next 27 platform upgrades**: We surveyed the strongest open-source crypto and agent projects, compared them with three.ws, and wrote the plan for closing every gap: agents that learn skills from experience, a payer command line, on-chain spending budgets, more trading venues, safer chat trading and more. `[docs]`
- **A full setup guide for Grok Bot**: There is now one page that covers connecting Grok Bot to three.ws end to end: the exact connector settings, which sign-in to pick, how scheduled runs collect long renders and retry without generating twice, the rate limits, the rule that an agent can never spend, and a fix for every connection problem. (`/docs/grok-bot`) `[docs]`
@@ -377,7 +377,6 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr
- **Docs · Chart Companion** (`/docs/chart-companion`): How to watch a DEXTools chart with a 3D agent that reacts to every real swap: the URL parameters, streaming it as a transparent OBS overlay, embedding it with one iframe, bringing your own agent, and exactly how whale, streak and new-high reactions are decided.
- **Docs · DEXTools integration** (`/docs/dextools`): How three.ws and DEXTools connect: the /dextools hub, the embed builder that turns any DEXTools pair link into a 3D scene or Social Boost card snippet, the framable Boost on DEXTools card, and the counted redirect and public totals behind every visit three.ws sends to a DEXTools pair page.
- **Docs · three.ws for Grok** (`/docs/grok`): Connect Grok Bot, Grok connectors and the xAI API to one free remote MCP server that turns text or an image into a textured 3D model, a rigged avatar, or a named 3D persona that lip-syncs its replies. No account, payment or API key.
-- **Docs · three.ws for Grok** (`/docs/grok`): Connect Grok Bot, Grok connectors or the xAI API to the free three.ws remote MCP server at /api/mcp-grok: text and image to 3D, rigged avatars, and a named 3D persona that lip-syncs its replies, with no account, payment or API key.
- **Launch a Paired Coin** (`/launch/paired`): Have your 3D AI agent launch a coin on Robinhood Chain paired with up to five assets at once (tokenized stocks, WETH, stablecoins, chain coins) from its own wallet: a live cost quote with each pool's opening value, an atomic opening buy, spend-policy checks, and the same launch as an API call and MCP tools.
- **Launch on Robinhood Chain** (`/launch/robinhood`): Launch a coin on Robinhood Chain through Pons, signed by your 3D AI agent's own wallet: a live cost quote, an atomic opening buy, and an API your bots can call.
- **Paired Coins** (`/markets/robinhood/paired`): Coins on Robinhood Chain that trade against up to five assets at once: tokenized stocks, WETH, stablecoins and chain coins, each in its own bonding curve with liquidity locked forever. Live pools priced in dollars, charts per pool, every trade, a buy and sell ticket, and the AI agents that launched them.
diff --git a/prompts/finish/401-auto-restore-green-vitest.md b/prompts/finish/401-auto-restore-green-vitest.md
index 38c8f6e0d..468fdb0dd 100644
--- a/prompts/finish/401-auto-restore-green-vitest.md
+++ b/prompts/finish/401-auto-restore-green-vitest.md
@@ -21,6 +21,8 @@ How to run: paste this file's repo path into a fresh Claude Code chat in this re
`npm test` runs `vitest run && playwright test`, so every work order's "tests pass" line is unverifiable until this is green. One green suite unblocks honest verification for the whole queue.
+**Note, 2026-10-24 (order 409, post-merge):** after merging 113 main-only commits into `evolve` (order 409), `npm run test:core` reads **47 failed files, 76 failed tests** (2473 passed files, 37308 passed tests), down from the 52/108 measured above. The drop reflects fixes that already shipped on `main` (for example its own `data/pages.json` duplicate cleanup and `tests/native-launch-curve.test.js` rewrite), not work done by this order. The class map below was written against the pre-merge 52/108 run and has not been re-verified against the new 47/76 list; treat it as a starting point, re-run `npm run test:core` fresh in step 0 before trusting any specific class's file list.
+
The failures are not one bug. Grouped by what they look like (verify each with `npx vitest run <file>`; this grouping is a researched starting map, not gospel):
**A. One missing DB column in a test's own hand-written fixture schema (not a real migration gap).** `tests/approvals.test.js` fails all 19 of its cases with `error: column "meta" does not exist` from pglite. Root cause confirmed by reading the file: it creates its own `agent_identities` table at line 81 as `create table agent_identities (id uuid primary key, user_id uuid, name text, deleted_at timestamptz)`, with no `meta` column. `api/_lib/approvals.js:596` (added by the burner-cap policy feature, commit `e9359c74d`) does `SELECT meta FROM agent_identities WHERE id = ...` and reads `row.meta.burner_policy`. The real `agent_identities` table has had a `meta jsonb` column since migration `20260616235900_agent_identities_meta_skills.sql`; only this test's hand-rolled DDL is behind. Fix: add `meta jsonb not null default '{}'::jsonb` to the test's `create table` statement. Also grep `tests/burner-approvals.test.js` and any other file that hand-creates `agent_identities`, since the same gap likely repeats there.
diff --git a/prompts/finish/410-auto-register-awesome-solana-doc.md b/prompts/finish/410-auto-register-awesome-solana-doc.md
new file mode 100644
index 000000000..9b640d3a9
--- /dev/null
+++ b/prompts/finish/410-auto-register-awesome-solana-doc.md
@@ -0,0 +1,48 @@
+# 410. Register `docs/awesome-solana-ai-submission.md` in `data/pages.json`, or mark it deliberately unpublished
+
+How to run: paste this file's repo path into a fresh Claude Code chat in this repository and say "run this work order". Runnable now, no gate, no owner action required.
+
+## Operating clause (binding)
+
+- Read CLAUDE.md first. CLAUDE.md overrides everything, including this file.
+- Finish 100% in this session. Never end the turn with a question, an option list, or an unexecuted plan.
+- The only permitted stops are the CLAUDE.md stop-and-ask gates (spend/on-chain writes, push/deploy, posting externally, committing content referencing a crypto project other than `$THREE`, destroying unrecoverable data). This order touches none of them.
+- Concurrent agents share this worktree: stage explicit paths only (never `git add -A` or `git add .`), re-check `git status` and `git diff --staged` before committing.
+- The em-dash and en-dash characters are banned in everything you write.
+
+## Step 0: re-derive the current state
+
+ npm run audit:docs
+
+Confirm it still reports exactly this finding (it may have already been fixed by another agent; if `npm run audit:docs` is already clean, verify that, then retire this order the same way described below instead of making a change):
+
+ Public docs missing from data/pages.json (live but undiscoverable) (1):
+ docs/awesome-solana-ai-submission.md served at /docs/awesome-solana-ai-submission but absent from data/pages.json, so no crawler can find it.
+
+This was surfaced by order 409 (evolve/main reconciliation merge) as a pre-existing gap: the doc was added by main commit `0e0a806cd` ("docs(parity): add the awesome-solana-ai submission kit...") without a matching `data/pages.json` entry, so it has been live and undiscoverable since that commit, unrelated to the merge itself.
+
+## Task
+
+1. Read `docs/awesome-solana-ai-submission.md` to confirm what it documents and whether it is meant to be a crawlable, linked-to doc page or an internal-only submission kit (check whether anything in the repo links to `/docs/awesome-solana-ai-submission`; `npm run audit:links` output and a `grep -rn 'awesome-solana-ai-submission'` across `pages/`, `docs/`, and `prompts/` will show this).
+2. If it is meant to be discoverable (the common case for `docs/*.md`): add an entry for it in `data/pages.json`, matching the shape and section used by sibling doc entries already there (title, description, path `/docs/awesome-solana-ai-submission`, section, dates).
+3. If it is deliberately internal (for example, a one-time submission packet for a third-party directory rather than ongoing user-facing documentation): add its slug to the `UNPUBLISHED_DOCS` map in `scripts/audit-docs.mjs` (around line 287) with a one-line reason, following the existing entries' format exactly.
+4. Run `npm run audit:docs` and confirm the finding is gone.
+5. Run `npm run audit:links` to confirm no new dangling/broken link resulted.
+6. Run `npm run check:rules -- --paths <files you touched>` and fix anything it flags.
+
+## Done when
+
+- `npm run audit:docs` exits with 0 findings.
+- `npm run audit:links` shows no new broken/dangling entries caused by this change.
+- This file is removed with a dated entry in `prompts/finish/_context/production-100-PROGRESS.md` citing the fix commit SHA.
+
+## Never blocked
+
+| Looks like a blocker | It is not | Do this |
+|---|---|---|
+| Unsure whether the doc should be public or internal | The doc's own content and whether anything already links to it settles this | Read it; check for existing inbound links; default to publishing (the audit's own preferred fix) unless the content is clearly a one-time internal packet |
+| Another agent already fixed this | Routine for a shared worktree | Re-run `npm run audit:docs` first (step 0); if clean, retire this order without a code change |
+
+## Report format
+
+State: the step-0 `npm run audit:docs` result, which of the two fixes was applied and why, the post-fix `npm run audit:docs` and `npm run audit:links` output, and the commit SHA.
diff --git a/public/changelog-recent.json b/public/changelog-recent.json
index bccf19e40..ec51b298e 100644
--- a/public/changelog-recent.json
+++ b/public/changelog-recent.json
@@ -1,11 +1,11 @@
{
- "generated_at": "2026-10-24T02:18:41.033Z",
+ "generated_at": "2026-10-24T04:16:24.927Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json",
"site": {
"name": "three.ws",
"url": "https://three.ws"
},
- "total": 4192,
+ "total": 4191,
"complete": false,
"full_feed": "/changelog.json",
"entries": [
@@ -123,6 +123,16 @@
"docs"
]
},
+ {
+ "date": "2026-10-24",
+ "type": "update",
+ "title": "Fixed three more legacy thumbnail links that browsers refused to load",
+ "summary": "A handful of forge creations and 3D props stored from before an earlier URL fix still pointed straight at the storage bucket's own domain instead of three.ws's own CDN link, which Chrome blocks as an opaque cross-origin response. Model-page posters, a creation's related-models sidebar, forge share-card previews (the image X and Discord show when a link is pasted), and the Forged gallery's model-viewer thumbnails now all resolve through the same CDN link as everything else.",
+ "link": "/forge",
+ "tags": [
+ "fix"
+ ]
+ },
{
"date": "2026-10-24",
"type": "update",
@@ -545,6 +555,16 @@
"feature"
]
},
+ {
+ "date": "2026-10-23",
+ "type": "update",
+ "title": "Bonding-curve status API no longer hard-fails when pump.fun blips",
+ "summary": "GET /api/crypto/bonding was returning a 503 to every caller during a pump.fun outage, even for mints it had already fetched successfully. It now caches each mint's bonding-curve status and keeps a longer last-known-good copy, so a failed upstream fetch serves that cached data (flagged with an x-pump-stale header) instead of a hard error. A 503 with a retry hint is now only returned for a mint that has no cached data at all.",
+ "link": "/api/crypto/bonding",
+ "tags": [
+ "fix"
+ ]
+ },
{
"date": "2026-10-23",
"type": "update",
@@ -1544,28 +1564,6 @@
"feature",
"security"
]
- },
- {
- "date": "2026-10-12",
- "type": "update",
- "title": "Forge generation controls (target faces, bbox fit, rest pose) and a batch endpoint for fanning out N generations",
- "summary": "POST /api/forge and /api/x402/forge take three new, off-by-default controls: target_faces (alias of target_polycount) pins an explicit geometry budget on poly-aware backends; bbox: [x, y, z] uniformly rescales the delivered mesh to fit a box in meters, lane-agnostic since it runs as a post-generation GLB fit; pose: \"t\" | \"a\" requests a rest pose on backends without a caller-supplied reference image, with pose_applied echoed back so a photo-conditioned lane never silently ignores it. A new POST /api/forge-batch fans one call out to up to 8 independent /api/forge submissions, concurrency-capped by the caller's $THREE holder tier, and GET /api/forge-batch?batch=<id> polls the group: one item's failure never fails the batch, and group state is best-effort Redis so a job already returned stays pollable at /api/forge?job= even if the group expires. The Workbench's Generate Mesh node now exposes rest pose and width/height/depth bbox fields alongside the existing face budget, and a new Batch drawer (toolbar icon, or press B) queues up to 8 prompts at once against the new endpoint and opens any finished item straight into the viewport.",
- "link": "/docs/forge",
- "tags": [
- "feature",
- "improvement"
- ]
- },
- {
- "date": "2026-10-12",
- "type": "update",
- "title": "Real VRM avatars: spring bones, expressions, and .vrma clips via @pixiv/three-vrm",
- "summary": "The hand-rolled VRM loader is gone. vrm-boot.js now registers the real VRMLoaderPlugin (@pixiv/three-vrm) on the three.ws GLTFLoader, so VRM 0.x and 1.0 avatars get genuine MToon materials, spring-bone physics, node constraints, look-at, and all 18 expression presets, driven live by vrm.update(delta) in AnimationManager and mapped onto the ARKit-52 face-capture driver. VRMAnimationLoaderPlugin loads .vrma clips into the same retargeting pipeline that drives non-VRM humanoids, so a single clip plays on either. The Ready Player Me import page (/import-rpm) now accepts .vrm files alongside .glb, and a long-standing bug that 400'd every import at the final save step (it sent an invalid source value) is fixed. docs/avatar-engines.md upgrades three-vrm from interop to live.",
- "link": "/docs/avatar-engines",
- "tags": [
- "feature",
- "fix"
- ]
}
]
}
diff --git a/public/changelog.json b/public/changelog.json
index 308a0b9af..eb59867a8 100644
--- a/public/changelog.json
+++ b/public/changelog.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-10-24T02:18:40.977Z",
+ "generated_at": "2026-10-24T04:16:24.892Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json",
"site": {
"name": "three.ws",
@@ -120,6 +120,16 @@
"docs"
]
},
+ {
+ "date": "2026-10-24",
+ "type": "update",
+ "title": "Fixed three more legacy thumbnail links that browsers refused to load",
+ "summary": "A handful of forge creations and 3D props stored from before an earlier URL fix still pointed straight at the storage bucket's own domain instead of three.ws's own CDN link, which Chrome blocks as an opaque cross-origin response. Model-page posters, a creation's related-models sidebar, forge share-card previews (the image X and Discord show when a link is pasted), and the Forged gallery's model-viewer thumbnails now all resolve through the same CDN link as everything else.",
+ "link": "/forge",
+ "tags": [
+ "fix"
+ ]
+ },
{
"date": "2026-10-24",
"type": "update",
@@ -542,6 +552,16 @@
"feature"
]
},
+ {
+ "date": "2026-10-23",
+ "type": "update",
+ "title": "Bonding-curve status API no longer hard-fails when pump.fun blips",
+ "summary": "GET /api/crypto/bonding was returning a 503 to every caller during a pump.fun outage, even for mints it had already fetched successfully. It now caches each mint's bonding-curve status and keeps a longer last-known-good copy, so a failed upstream fetch serves that cached data (flagged with an x-pump-stale header) instead of a hard error. A 503 with a retry hint is now only returned for a mint that has no cached data at all.",
+ "link": "/api/crypto/bonding",
+ "tags": [
+ "fix"
+ ]
+ },
{
"date": "2026-10-23",
"type": "update",
@@ -3013,16 +3033,6 @@
"launch"
]
},
- {
- "date": "2026-10-09",
- "type": "launch",
- "title": "Docs · Grok Bot connector reference",
- "summary": "Exact connector settings for Grok Bot, which sign-in and which server to pick, the links, jobs, retry and rate-limit contracts for unattended runs, the spend rule, and a fix for every failure the connector probe can report.",
- "link": "/docs/grok-bot",
- "tags": [
- "launch"
- ]
- },
{
"date": "2026-10-09",
"type": "launch",
@@ -3113,16 +3123,6 @@
"launch"
]
},
- {
- "date": "2026-10-09",
- "type": "launch",
- "title": "Tutorial · Grok Bot recipes",
- "summary": "Six jobs to hand Grok Bot, each with the exact sentence, the tools it calls in order, and the real output of running that sequence against production: a daily 3D brief, a game jam asset pack, an avatar from a photo, an X post image as a 3D model, a weekly agent report and a $THREE market brief.",
- "link": "/tutorials/grok-bot-recipes",
- "tags": [
- "launch"
- ]
- },
{
"date": "2026-10-09",
"type": "launch",
@@ -3556,16 +3556,6 @@
"launch"
]
},
- {
- "date": "2026-10-08",
- "type": "launch",
- "title": "Docs · three.ws for Grok",
- "summary": "Connect Grok Bot, Grok connectors or the xAI API to the free three.ws remote MCP server at /api/mcp-grok: text and image to 3D, rigged avatars, and a named 3D persona that lip-syncs its replies, with no account, payment or API key.",
- "link": "/docs/grok",
- "tags": [
- "launch"
- ]
- },
{
"date": "2026-10-08",
"type": "launch",
diff --git a/public/changelog.xml b/public/changelog.xml
index 9c79bae6c..8b89c12e8 100644
--- a/public/changelog.xml
+++ b/public/changelog.xml
@@ -94,6 +94,14 @@
<category>sdk</category>
<description>One command, npm run package:engine-stores, validates the Unity, Godot and Unreal bridges and builds a reproducible upload package for each, with listing metadata and a submission checklist. The Unity package and Unreal plugin manifests now carry their documentation links.</description>
</item>
+ <item>
+ <title>Fixed three more legacy thumbnail links that browsers refused to load</title>
+ <link>https://three.ws/forge</link>
+ <guid isPermaLink="false">2026-10-24:Fixed three more legacy thumbnail links that browsers refused to load</guid>
+ <pubDate>Sat, 24 Oct 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>A handful of forge creations and 3D props stored from before an earlier URL fix still pointed straight at the storage bucket's own domain instead of three.ws's own CDN link, which Chrome blocks as an opaque cross-origin response. Model-page posters, a creation's related-models sidebar, forge share-card previews (the image X and Discord show when a link is pasted), and the Forged gallery's model-viewer thumbnails now all resolve through the same CDN link as everything else.</description>
+ </item>
<item>
<title>Hundreds of dependency security advisories cleared across the repo</title>
<link>https://three.ws/changelog</link>
@@ -422,6 +430,14 @@
<category>feature</category>
<description>Every strategy backtest replays its entry gate with the future removed and reports any decision that changed, pins the exact dataset it ran on with a content hash, and marks older unpinned results as unreproducible. A new canary job checks each price and candle source against a known value every 30 minutes and tries the healthy ones first.</description>
</item>
+ <item>
+ <title>Bonding-curve status API no longer hard-fails when pump.fun blips</title>
+ <link>https://three.ws/api/crypto/bonding</link>
+ <guid isPermaLink="false">2026-10-23:Bonding-curve status API no longer hard-fails when pump.fun blips</guid>
+ <pubDate>Fri, 23 Oct 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>GET /api/crypto/bonding was returning a 503 to every caller during a pump.fun outage, even for mints it had already fetched successfully. It now caches each mint's bonding-curve status and keeps a longer last-known-good copy, so a failed upstream fetch serves that cached data (flagged with an x-pump-stale header) instead of a hard error. A 503 with a retry hint is now only returned for a mint that has no cached data at all.</description>
+ </item>
<item>
<title>Chain turnover on /chains</title>
<link>https://three.ws/chains</link>
@@ -2334,14 +2350,6 @@
<category>launch</category>
<description>Connect Grok Bot to three.ws as a custom MCP connector: exact fields for each sign-in mode, which server to pick, the links every result carries, jobs and safe retries, free limits and install tokens, why a connector key can never spend, guided prompts, and a fix for every connection failure.</description>
</item>
- <item>
- <title>Docs · Grok Bot connector reference</title>
- <link>https://three.ws/docs/grok-bot</link>
- <guid isPermaLink="false">2026-10-09:Docs · Grok Bot connector reference</guid>
- <pubDate>Fri, 09 Oct 2026 12:00:00 GMT</pubDate>
- <category>launch</category>
- <description>Exact connector settings for Grok Bot, which sign-in and which server to pick, the links, jobs, retry and rate-limit contracts for unattended runs, the spend rule, and a fix for every failure the connector probe can report.</description>
- </item>
<item>
<title>Docs · Modly and three.ws</title>
<link>https://three.ws/docs/modly</link>
@@ -2414,14 +2422,6 @@
<category>launch</category>
<description>Download three.ws Forge, the free desktop 3D studio for Windows, Linux and Apple silicon Macs. Turn a photo into a 3D model with open-source generators on your own GPU or the three.ws cloud, chain repair, remeshing, rigging and export in node workflows, import free CC0 models and publish to your three.ws account in one click. Based on Modly (MIT).</description>
</item>
- <item>
- <title>Tutorial · Grok Bot recipes</title>
- <link>https://three.ws/tutorials/grok-bot-recipes</link>
- <guid isPermaLink="false">2026-10-09:Tutorial · Grok Bot recipes</guid>
- <pubDate>Fri, 09 Oct 2026 12:00:00 GMT</pubDate>
- <category>launch</category>
- <description>Six jobs to hand Grok Bot, each with the exact sentence, the tools it calls in order, and the real output of running that sequence against production: a daily 3D brief, a game jam asset pack, an avatar from a photo, an X post image as a 3D model, a weekly agent report and a $THREE market brief.</description>
- </item>
<item>
<title>Workbench</title>
<link>https://three.ws/workbench</link>
@@ -2758,14 +2758,6 @@
<category>launch</category>
<description>Connect Grok Bot, Grok connectors and the xAI API to one free remote MCP server that turns text or an image into a textured 3D model, a rigged avatar, or a named 3D persona that lip-syncs its replies. No account, payment or API key.</description>
</item>
- <item>
- <title>Docs · three.ws for Grok</title>
- <link>https://three.ws/docs/grok</link>
- <guid isPermaLink="false">2026-10-08:Docs · three.ws for Grok</guid>
- <pubDate>Thu, 08 Oct 2026 12:00:00 GMT</pubDate>
- <category>launch</category>
- <description>Connect Grok Bot, Grok connectors or the xAI API to the free three.ws remote MCP server at /api/mcp-grok: text and image to 3D, rigged avatars, and a named 3D persona that lip-syncs its replies, with no account, payment or API key.</description>
- </item>
<item>
<title>Launch a Paired Coin</title>
<link>https://three.ws/launch/paired</link>
diff --git a/public/features.json b/public/features.json
index 4705f5e5d..391a45394 100644
--- a/public/features.json
+++ b/public/features.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-10-24T00:37:29.388Z",
+ "generated_at": "2026-10-24T04:16:24.868Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json",
"site": {
"name": "three.ws",
@@ -7028,18 +7028,6 @@
"priority": 0.5,
"job": null
},
- {
- "path": "/docs/grok",
- "title": "Docs · three.ws for Grok",
- "description": "Connect Grok Bot, Grok connectors or the xAI API to the free three.ws remote MCP server at /api/mcp-grok: text and image to 3D, rigged avatars, and a named 3D persona that lip-syncs its replies, with no account, payment or API key.",
- "added": "2026-10-08",
- "auth": null,
- "indexable": true,
- "tags": [],
- "showcase": false,
- "priority": 0.5,
- "job": null
- },
{
"path": "/docs/google-adk",
"title": "Docs · three.ws with Google ADK",
@@ -7052,30 +7040,6 @@
"priority": 0.5,
"job": null
},
- {
- "path": "/tutorials/grok-bot-recipes",
- "title": "Tutorial · Grok Bot recipes",
- "description": "Six jobs to hand Grok Bot, each with the exact sentence, the tools it calls in order, and the real output of running that sequence against production: a daily 3D brief, a game jam asset pack, an avatar from a photo, an X post image as a 3D model, a weekly agent report and a $THREE market brief.",
- "added": "2026-10-09",
- "auth": null,
- "indexable": true,
- "tags": [],
- "showcase": false,
- "priority": 0.6,
- "job": null
- },
- {
- "path": "/docs/grok-bot",
- "title": "Docs · Grok Bot connector reference",
- "description": "Exact connector settings for Grok Bot, which sign-in and which server to pick, the links, jobs, retry and rate-limit contracts for unattended runs, the spend rule, and a fix for every failure the connector probe can report.",
- "added": "2026-10-09",
- "auth": null,
- "indexable": true,
- "tags": [],
- "showcase": false,
- "priority": 0.5,
- "job": null
- },
{
"path": "/docs/chatgpt-ar",
"title": "Docs · AR in ChatGPT",
diff --git a/public/llms.txt b/public/llms.txt
index e59d2acbf..ea9ab8f9e 100644
--- a/public/llms.txt
+++ b/public/llms.txt
@@ -103,6 +103,6 @@ Machine-readable entry points. Fetch these instead of scraping HTML.
## Optional
-- [llms-full.txt](https://three.ws/llms-full.txt): Every public page (1049) with full descriptions, plus the full markdown of the curated docs.
+- [llms-full.txt](https://three.ws/llms-full.txt): Every public page (1046) with full descriptions, plus the full markdown of the curated docs.
- [Sitemap](https://three.ws/sitemap): The same index for people, with search.
- [sitemap.xml](https://three.ws/sitemap.xml): XML sitemap for crawlers, including every agent and avatar page.
diff --git a/public/sitemap/index.html b/public/sitemap/index.html
index b6ba0ac25..5cc9f6a6a 100644
--- a/public/sitemap/index.html
+++ b/public/sitemap/index.html
@@ -3,16 +3,16 @@
<head>
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width,initial-scale=1" />
-<title data-i18n="sitemap_index.meta_title">Sitemap · three.ws</title>
-<meta name="description" content="Human-readable index of every page on three.ws." data-i18n-attr="content:sitemap_index.meta_description"/>
+<title>Sitemap · three.ws</title>
+<meta name="description" content="Human-readable index of every page on three.ws." />
<meta name="robots" content="index, follow, max-image-preview:large, max-snippet:-1" />
<link rel="canonical" href="https://three.ws/sitemap" />
<meta property="og:type" content="website" />
<meta property="og:site_name" content="three.ws" />
<meta property="og:locale" content="en_US" />
<meta property="og:url" content="https://three.ws/sitemap" />
-<meta property="og:title" content="Sitemap · three.ws" data-i18n-attr="content:sitemap_index.meta_og_title"/>
-<meta property="og:description" content="Human-readable index of every page on three.ws." data-i18n-attr="content:sitemap_index.meta_og_description"/>
+<meta property="og:title" content="Sitemap · three.ws" />
+<meta property="og:description" content="Human-readable index of every page on three.ws." />
<meta property="og:image" content="https://three.ws/api/page-og?s=main&amp;t=Sitemap&amp;d=Human-readable+index+of+every+page+on+three.ws.&amp;p=%2Fsitemap" />
<meta property="og:image:width" content="1200" />
<meta property="og:image:height" content="630" />
@@ -20,8 +20,8 @@
<meta property="og:image:alt" content="Sitemap - three.ws" />
<meta name="twitter:card" content="summary_large_image" />
<meta name="twitter:site" content="@trythreews" />
-<meta name="twitter:title" content="Sitemap · three.ws" data-i18n-attr="content:sitemap_index.meta_twitter_title"/>
-<meta name="twitter:description" content="Human-readable index of every page on three.ws." data-i18n-attr="content:sitemap_index.meta_twitter_description"/>
+<meta name="twitter:title" content="Sitemap · three.ws" />
+<meta name="twitter:description" content="Human-readable index of every page on three.ws." />
<meta name="twitter:image" content="https://three.ws/api/page-og?s=main&amp;t=Sitemap&amp;d=Human-readable+index+of+every+page+on+three.ws.&amp;p=%2Fsitemap" />
<script type="application/ld+json">{"@context":"https://schema.org","@graph":[{"@type":"WebPage","name":"Sitemap","description":"Human-readable index of every page on three.ws.","url":"https://three.ws/sitemap","isPartOf":{"@type":"WebSite","name":"three.ws","url":"https://three.ws"},"primaryImageOfPage":"https://three.ws/api/page-og?s=main&t=Sitemap&d=Human-readable+index+of+every+page+on+three.ws.&p=%2Fsitemap"}]}</script>
<link rel="alternate" type="application/xml" title="XML sitemap" href="/sitemap.xml" />
@@ -95,27 +95,27 @@
<header><div id="nav-container"></div></header>
<main class="sm-wrap">
<div class="sm-hero">
- <h1 data-i18n="sitemap_index.sitemap">Sitemap</h1>
- <p><span>1117</span> <span data-i18n="sitemap_index.pages_grouped">pages on three.ws, grouped by purpose. Looking for the machine-readable versions?</span></p>
+ <h1>Sitemap</h1>
+ <p><span>1114</span> <span data-i18n="sitemap_index.pages_grouped">pages on three.ws, grouped by purpose. Looking for the machine-readable versions?</span></p>
<div class="sm-formats">
- <a href="/everything" data-i18n-html="sitemap_index.browse_by_goal_not_by_section"><code>/everything</code> · browse by goal, not by section</a>
- <a href="/sitemap.xml" data-i18n-html="sitemap_index.for_search_engines"><code>sitemap.xml</code> · for search engines</a>
- <a href="/llms.txt" data-i18n-html="sitemap_index.for_ai_agents"><code>llms.txt</code> · for AI agents</a>
- <a href="/llms-full.txt" data-i18n-html="sitemap_index.long_form"><code>llms-full.txt</code> · long form</a>
- <a href="/api/features.json" data-i18n-html="sitemap_index.machine_manifest"><code>features.json</code> · machine manifest</a>
- <a href="/changelog" data-i18n-html="sitemap_index.what_s_new"><code>changelog</code> · what's new</a>
- <a href="/openapi.json" data-i18n-html="sitemap_index.http_api"><code>openapi.json</code> · HTTP API</a>
+ <a href="/everything"><code>/everything</code> · browse by goal, not by section</a>
+ <a href="/sitemap.xml"><code>sitemap.xml</code> · for search engines</a>
+ <a href="/llms.txt"><code>llms.txt</code> · for AI agents</a>
+ <a href="/llms-full.txt"><code>llms-full.txt</code> · long form</a>
+ <a href="/api/features.json"><code>features.json</code> · machine manifest</a>
+ <a href="/changelog"><code>changelog</code> · what's new</a>
+ <a href="/openapi.json"><code>openapi.json</code> · HTTP API</a>
</div>
</div>
<div class="sm-filter">
<svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" aria-hidden="true"><circle cx="11" cy="11" r="7"/><path d="m21 21-4.3-4.3"/></svg>
- <input id="sm-filter-input" type="search" placeholder="Filter 1117 pages by name, path, or description…" aria-label="Filter pages" autocomplete="off" spellcheck="false" />
+ <input id="sm-filter-input" type="search" placeholder="Filter 1114 pages by name, path, or description…" aria-label="Filter pages" autocomplete="off" spellcheck="false" />
<kbd id="sm-filter-kbd" aria-hidden="true">/</kbd>
</div>
<p class="sm-filter-count" role="status" aria-live="polite"><span id="sm-filter-count"></span><span id="sm-filter-hint" aria-hidden="true"></span></p>
<section class="sm-new" id="sm-new" aria-labelledby="sm-new-title">
- <h2 id="sm-new-title" data-i18n-html="sitemap_index.newestfull_changelog">Newest<a class="sm-new-more" href="/changelog">full changelog &rarr;</a></h2>
- <p class="sm-section-desc" data-i18n="sitemap_index.the_9_most_recently_launched_pages_straight">The 9 most recently launched pages, straight to the live surface.</p>
+ <h2 id="sm-new-title">Newest<a class="sm-new-more" href="/changelog">full changelog &rarr;</a></h2>
+ <p class="sm-section-desc">The 9 most recently launched pages, straight to the live surface.</p>
<ul class="sm-list">
<li>
<a href="/docs/webgpu-renderer">
@@ -192,22 +192,22 @@
</ul>
</section>
<nav class="sm-toc" aria-label="Sections">
- <a href="#main" data-i18n="sitemap_index.main">Main</a>
- <a href="#build" data-i18n="sitemap_index.build">Build</a>
- <a href="#labs" data-i18n="sitemap_index.labs">Labs</a>
- <a href="#crypto" data-i18n="sitemap_index.crypto">Crypto</a>
- <a href="#agent-tools" data-i18n="sitemap_index.agent_tools">Agent Tools</a>
- <a href="#account" data-i18n="sitemap_index.account">Account</a>
- <a href="#learn" data-i18n="sitemap_index.learn">Learn</a>
- <a href="#blog" data-i18n="sitemap_index.blog">Blog</a>
- <a href="#legal" data-i18n="sitemap_index.legal">Legal</a>
- <a href="#machine" data-i18n="sitemap_index.machine_readable">Machine-readable</a>
- <a href="#news" data-i18n="sitemap_index.news">News</a>
+ <a href="#main">Main</a>
+ <a href="#build">Build</a>
+ <a href="#labs">Labs</a>
+ <a href="#crypto">Crypto</a>
+ <a href="#agent-tools">Agent Tools</a>
+ <a href="#account">Account</a>
+ <a href="#learn">Learn</a>
+ <a href="#blog">Blog</a>
+ <a href="#legal">Legal</a>
+ <a href="#machine">Machine-readable</a>
+ <a href="#news">News</a>
</nav>
<section class="sm-section" id="main">
<header>
<h2><span data-i18n="sitemap_index.section_main">Main</span><span class="sm-count" data-count>78</span></h2>
- <p class="sm-section-desc" data-i18n="sitemap_index.entry_points_into_the_product">Entry points into the product.</p>
+ <p class="sm-section-desc">Entry points into the product.</p>
</header>
<ul class="sm-list">
<li>
@@ -762,7 +762,7 @@
<section class="sm-section" id="build">
<header>
<h2><span data-i18n="sitemap_index.section_build">Build</span><span class="sm-count" data-count>96</span></h2>
- <p class="sm-section-desc" data-i18n="sitemap_index.create_and_customize_an_agent">Create and customize an agent.</p>
+ <p class="sm-section-desc">Create and customize an agent.</p>
</header>
<ul class="sm-list">
<li>
@@ -1443,7 +1443,7 @@
<section class="sm-section" id="labs">
<header>
<h2><span data-i18n="sitemap_index.section_labs">Labs</span><span class="sm-count" data-count>26</span></h2>
- <p class="sm-section-desc" data-i18n="sitemap_index.experimental_features_actively_shipping_expe">Experimental features actively shipping. Expect fast iteration.</p>
+ <p class="sm-section-desc">Experimental features actively shipping. Expect fast iteration.</p>
</header>
<ul class="sm-list">
<li>
@@ -1634,7 +1634,7 @@
<section class="sm-section" id="crypto">
<header>
<h2><span data-i18n="sitemap_index.section_crypto">Crypto</span><span class="sm-count" data-count>175</span></h2>
- <p class="sm-section-desc" data-i18n="sitemap_index.on_chain_features_pay_per_call_token">On-chain features: pay-per-call, token launches, vanity wallets.</p>
+ <p class="sm-section-desc">On-chain features: pay-per-call, token launches, vanity wallets.</p>
</header>
<ul class="sm-list">
<li>
@@ -2868,7 +2868,7 @@
<section class="sm-section" id="agent-tools">
<header>
<h2><span data-i18n="sitemap_index.section_agent-tools">Agent Tools</span><span class="sm-count" data-count>11</span></h2>
- <p class="sm-section-desc" data-i18n="sitemap_index.manage_talk_to_and_deploy_individual_agents">Manage, talk to, and deploy individual agents.</p>
+ <p class="sm-section-desc">Manage, talk to, and deploy individual agents.</p>
</header>
<ul class="sm-list">
<li>
@@ -2954,7 +2954,7 @@
<section class="sm-section" id="account">
<header>
<h2><span data-i18n="sitemap_index.section_account">Account</span><span class="sm-count" data-count>16</span></h2>
- <p class="sm-section-desc" data-i18n="sitemap_index.sign_in_dashboard_billing">Sign-in, dashboard, billing.</p>
+ <p class="sm-section-desc">Sign-in, dashboard, billing.</p>
</header>
<ul class="sm-list">
<li>
@@ -3074,8 +3074,8 @@
<section class="sm-section" id="learn">
<header>
- <h2><span data-i18n="sitemap_index.section_learn">Learn</span><span class="sm-count" data-count>535</span></h2>
- <p class="sm-section-desc" data-i18n="sitemap_index.docs_tutorials_and_reference">Docs, tutorials, and reference.</p>
+ <h2><span data-i18n="sitemap_index.section_learn">Learn</span><span class="sm-count" data-count>532</span></h2>
+ <p class="sm-section-desc">Docs, tutorials, and reference.</p>
</header>
<ul class="sm-list">
<li>
@@ -4275,13 +4275,6 @@
<span class="sm-desc" data-i18n="sitemap_index.d_docs_mcp_studio">The free, no-auth MCP server behind the ChatGPT 3D Studio app: text and image to 3D, rigged avatars, conversational refinement, and living agent personas.</span>
</a>
</li>
- <li>
- <a href="/docs/grok">
- <span class="sm-title"><span data-i18n="sitemap_index.t_docs_grok">Docs · three.ws for Grok</span></span>
- <span class="sm-path" translate="no">/docs/grok</span>
- <span class="sm-desc" data-i18n="sitemap_index.d_docs_grok">Connect Grok Bot, Grok connectors or the xAI API to the free three.ws remote MCP server at /api/mcp-grok: text and image to 3D, rigged avatars, and a named 3D persona that lip-syncs its replies, with no account, payment or API key.</span>
- </a>
- </li>
<li>
<a href="/docs/google-adk">
<span class="sm-title"><span data-i18n="sitemap_index.t_docs_google_adk">Docs · three.ws with Google ADK</span></span>
@@ -4289,20 +4282,6 @@
<span class="sm-desc" data-i18n="sitemap_index.d_docs_google_adk">Connect a Google Agent Development Kit agent to the free three.ws 3D studio over MCPToolset: discover the tool catalog, forge and rig models, and run a full LlmAgent conversation. No account, payment or API key for the studio tools.</span>
</a>
</li>
- <li>
- <a href="/tutorials/grok-bot-recipes">
- <span class="sm-title"><span data-i18n="sitemap_index.t_tutorials_grok_bot_recipes">Tutorial · Grok Bot recipes</span></span>
- <span class="sm-path" translate="no">/tutorials/grok-bot-recipes</span>
- <span class="sm-desc" data-i18n="sitemap_index.d_tutorials_grok_bot_recipes">Six jobs to hand Grok Bot, each with the exact sentence, the tools it calls in order, and the real output of running that sequence against production: a daily 3D brief, a game jam asset pack, an avatar from a photo, an X post image as a 3D model, a weekly agent report and a $THREE market brief.</span>
- </a>
- </li>
- <li>
- <a href="/docs/grok-bot">
- <span class="sm-title"><span data-i18n="sitemap_index.t_docs_grok_bot">Docs · Grok Bot connector reference</span></span>
- <span class="sm-path" translate="no">/docs/grok-bot</span>
- <span class="sm-desc" data-i18n="sitemap_index.d_docs_grok_bot">Exact connector settings for Grok Bot, which sign-in and which server to pick, the links, jobs, retry and rate-limit contracts for unattended runs, the spend rule, and a fix for every failure the connector probe can report.</span>
- </a>
- </li>
<li>
<a href="/docs/chatgpt-ar">
<span class="sm-title"><span data-i18n="sitemap_index.t_docs_chatgpt_ar">Docs · AR in ChatGPT</span></span>
@@ -6829,7 +6808,7 @@
<section class="sm-section" id="blog">
<header>
<h2><span data-i18n="sitemap_index.section_blog">Blog</span><span class="sm-count" data-count>39</span></h2>
- <p class="sm-section-desc" data-i18n="sitemap_index.long_form_announcements_launches_and_writing">Long-form announcements, launches, and writing from three.ws.</p>
+ <p class="sm-section-desc">Long-form announcements, launches, and writing from three.ws.</p>
</header>
<ul class="sm-list">
<li>
@@ -7183,7 +7162,7 @@
<section class="sm-section" id="machine">
<header>
<h2><span data-i18n="sitemap_index.section_machine">Machine-readable</span><span class="sm-count" data-count>20</span></h2>
- <p class="sm-section-desc" data-i18n="sitemap_index.indexes_and_well_known_files_for_crawlers">Indexes and well-known files for crawlers and AI agents.</p>
+ <p class="sm-section-desc">Indexes and well-known files for crawlers and AI agents.</p>
</header>
<ul class="sm-list">
<li>
@@ -7332,7 +7311,7 @@
<section class="sm-section" id="news">
<header>
<h2><span data-i18n="sitemap_index.section_news">News</span><span class="sm-count" data-count>112</span></h2>
- <p class="sm-section-desc" data-i18n="sitemap_index.product_launches_integrations_and_announceme">Product launches, integrations, and announcements from three.ws.</p>
+ <p class="sm-section-desc">Product launches, integrations, and announcements from three.ws.</p>
</header>
<ul class="sm-list">
<li>
@@ -8123,10 +8102,10 @@
</section>
<div class="sm-empty" id="sm-empty" hidden>
<p><span data-i18n="sitemap_index.no_pages_match">No pages match</span> &ldquo;<span id="sm-empty-q"></span>&rdquo;.</p>
- <p class="sm-empty-hint" data-i18n="sitemap_index.try_a_shorter_word_or_search_everything">Try a shorter word, or search everything: global search covers agents, coins, and skills too.</p>
+ <p class="sm-empty-hint">Try a shorter word, or search everything: global search covers agents, coins, and skills too.</p>
<div class="sm-empty-actions">
- <button type="button" id="sm-empty-clear" data-i18n="sitemap_index.clear_filter">Clear filter</button>
- <a id="sm-empty-search" href="/search" data-i18n="sitemap_index.search_all_of_three_ws">Search all of three.ws</a>
+ <button type="button" id="sm-empty-clear">Clear filter</button>
+ <a id="sm-empty-search" href="/search">Search all of three.ws</a>
</div>
</div>
</main>