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.
JavaScript 3d-generationai-agentsanimationavatardigital-humangenerative-aiglbgltfimage-to-3dllmmcpmcp-servermodel-context-protocolsolanatext-to-3dthreejsweb-componentswebglwebxrx402
docs(dextools): map every surface that links DEXTools and mark proposal pillars 3 and 4 built
nirholasd2ba900e3dd9
diff --git a/docs/listings.md b/docs/listings.mdindex 8b44030e2..8397f66d6 100644--- a/docs/listings.md+++ b/docs/listings.md@@ -126,6 +126,39 @@ DEXTools also runs [Social Boost](https://www.dextools.io/app/social-boost), whiThe same list renders on [/three-token](/three-token#tk-social-boost) from one record, [src/pump/dextools-social-boost.js](../src/pump/dextools-social-boost.js). DEXTools publishes no API for past winners, so a new win is added there by hand (newest first, with its receipt) and mirrored in this table. Story: [three.ws Wins DEXTools Social Boost](/blog/three-ws-dextools-social-boost-buyback).+#### Where DEXTools appears on three.ws++Social Boost ranks by visits to a pair page, so every surface that shows a coin also sends people to that coin's DEXTools page:++| Surface | What it shows |+|---|---|+| [/three-token](/three-token) | The DEXTools chart widget as the $THREE chart, the Social Boost wins, and the pair page link |+| Every coin chart (`/launches/<mint>`, `/coin/:id`, `/trades`, Mission Control, the Oracle, `/pump-dashboard`) | DEXTools as a chart source in the switcher ([coin pages](./coin-pages.md)) |+| Trading terminal rows (coin pages, the $THREE dashboard, the pump.fun feed widget, Oracle share pages) | DEXTools leads the row ([src/shared/trading-terminals.js](../src/shared/trading-terminals.js)) |+| [/launch](/launch) success screen | A DEXTools button and the "Rally on DEXTools" Social Boost card, right after a coin goes live |+| `/launches/<mint>` Take action | The same Social Boost card for any coin |+| `/coin3d` | A DEXTools link in the HUD. A scene embedded by `?pair=` links back to that exact pair ([coin3d embed](./coin3d-embed.md)) |+| `/oracle/coin/<mint>` | A DEXTools button beside the other market links |+| Agent profiles, character pages, `/gmgn`, `/pumpfun`, the token dashboard | A DEXTools chart link for every coin shown |++**Which page a link opens.** DEXTools files a pump.fun mint as the coin's bonding-curve pair, so a raw-mint link sends a graduated coin to its dead curve page. Links that already know the pair use it. Every other link goes through [`GET /api/coin/dextools`](https://three.ws/api/coin/dextools?address=FeMbDoX7R1Psc4GEcvJdsbNbZA3bfztcyDCatJVJpump&from=docs), which resolves the most-liquid pool, redirects to its pair page, and pins $THREE to the pair its Social Boost wins are credited to. The redirect counts each visit per UTC day, coin and sending surface (no visitor data), and [`GET /api/coin/dextools-stats`](https://three.ws/api/coin/dextools-stats) publishes those totals, so the traffic three.ws sends DEXTools can be checked rather than claimed.++**The Social Boost card** is one component, `socialBoostCard()` in [src/shared/dextools-boost.js](../src/shared/dextools-boost.js). It explains the ranking, cites the $THREE wins from the record above, and gives three actions: open the DEXTools page, post a ready-made rally to X, and copy the link. It takes the host page's button classes and an optional `href`, so a surface can route it through the counted redirect with its own `from` tag:++```js+import { socialBoostCard } from './shared/dextools-boost.js';+import { dextoolsTokenUrl } from './shared/trading-terminals.js';++const card = socialBoostCard({+ mint,+ symbol: 'THREE',+ href: dextoolsTokenUrl(mint, { from: 'my-surface' }),+ buttonClass: 'btn',+ primaryClass: 'btn primary',+});+if (card) host.append(card); // null for an address it cannot link+```+---## Open Sourcediff --git a/docs/partners/dextools-proposal.md b/docs/partners/dextools-proposal.mdindex e695404ab..4399bd152 100644--- a/docs/partners/dextools-proposal.md+++ b/docs/partners/dextools-proposal.md@@ -5,6 +5,8 @@**TL;DR**The integration usually announced as a partnership, DEXTools charts live inside a partner product, is already shipped on three.ws and has been for months. What is not shipped anywhere is the other direction. three.ws renders any market as a live 3D scene, and as of today that scene is embeddable with one iframe keyed by the **pair address**, which is the identifier a DEXTools pair page already has in its URL. That is a visual layer no other chart terminal can put next to a chart, built on a relationship that already has public receipts on both sides.+**Status, 2026-10-08.** Pillars 3 and 4 below are now built on our side. Every coin launched through three.ws gets a DEXTools button and a Social Boost card on its success screen and its coin page. DEXTools leads the trading-terminal row on every coin surface. Every DEXTools link we render goes through a counted redirect whose per-day totals are public at `/api/coin/dextools-stats`, so the traffic we send DEXTools is something you can check rather than take on faith. Full surface map: [listings, DEXTools](../listings.md#dextools). Pillar 1 still needs DEXTools; pillar 2 is ready whenever you are.+---## What already exists between usdiff --git a/docs/partners/opportunities.md b/docs/partners/opportunities.mdindex 39a86cc31..fd4448675 100644--- a/docs/partners/opportunities.md+++ b/docs/partners/opportunities.md@@ -98,7 +98,7 @@ The work is done or nearly done. A human on our side has to act.| IBM G2 review | Draft ready in [ibm-g2-review.md](../../marketing/partner-packets/ibm-g2-review.md), written in the past tense because production has had no `WATSONX_*` credentials since at least 2026-07-29 (checked 2026-09-16) | The actual watsonx.ai user rewrites it in their own words with their own console screenshot, or restores the credentials first | Owner || CoinGecko market addition for $THREE | Form researched; only one of our live venues qualifies | Submit for that venue | Owner || HackerNoon author page | Checked 2026-09-16: [hackernoon.com/u/three-ws](https://hackernoon.com/u/three-ws) is live but shows **no published stories** ("eagerly awaiting @three-ws's next masterpiece"). RSS import lands in the drafts queue; nothing has gone out from it | Open the HackerNoon drafts queue and submit the imported announcements for editorial review | Owner |-| DEXTools, reciprocal 3D embed | Our side is shipped: DEXTools charts are already a provider in every three.ws chart switcher, and as of 2026-09-20 `/coin3d` is framable and keyed by pair address, which is the identifier a DEXTools pair page already holds. The relationship has public receipts in both directions: three $THREE Social Boost wins with DEXTools buybacks behind them | Send [dextools-proposal.md](./dextools-proposal.md) to a DEXTools partnerships or front-end contact. Nothing else is blocked; the embed is live and free whether or not they answer | Owner |+| DEXTools, reciprocal 3D embed | Our side is shipped: DEXTools charts are already a provider in every three.ws chart switcher, and as of 2026-09-20 `/coin3d` is framable and keyed by pair address, which is the identifier a DEXTools pair page already holds. As of 2026-10-08 proposal pillars 3 and 4 are built too: DEXTools leads every terminal row, launches get a Social Boost card, and every link we send is counted at `/api/coin/dextools-stats` ([surface map](../listings.md#dextools)). The relationship has public receipts in both directions: three $THREE Social Boost wins with DEXTools buybacks behind them | Send [dextools-proposal.md](./dextools-proposal.md) to a DEXTools partnerships or front-end contact. Nothing else is blocked; the embed is live and free whether or not they answer | Owner || Glama connector claim | Checked 2026-09-16: at least seven three.ws connectors are listed. The main `three.ws` connector is unclaimed and reports **Unhealthy** because Glama has no OAuth test credentials for `https://three.ws/api/mcp` | Claim ownership on the connector page (maintainer email `[email protected]` is already declared in `public/.well-known/glama.json`), then add a test profile under Admin | Owner |### Anthropic, which this page was missing