Skip to content

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

docs(crypto-api): document GET /api/crypto/linkage and changelog the release

nirholas14453d052127
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 8b088a238..2f205893f 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -6,6 +6,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr
## 2026-10-14
+- **A new wallet linkage score flags a coin's creator buying their own launch**: GET /api/crypto/linkage cross-checks 2-10 Solana addresses for shared control: a 0-100 same-controller score per pair, combining six real on-chain signals by noisy-OR (shared fee payer, one address funding the other, both sharing a first funder, SPL token-account control, direct transfers, a shared funder sending similar amounts in a short window), every match backed by the signature or account that triggered it. It is keyless, free, and part of the public Crypto Data API, and now wired into two places that act on money: the Trade Safety Firewall warns when an early buyer scores as the same controller as a coin's creator (wash-trading dressed up as demand), and copy-trading refuses to size an order behind a leader whose own wallet links to the creator of the coin they are 'signaling', showing the follower exactly why. The same scorer ships as the wallet_linkage tool in the hosted intel MCP server for any AI agent to call directly. (`/crypto-api`) `[feature, security]`
- **A read-only drift report for every standalone GitHub mirror**: npm run mirrors:drift compares each of the ~105 standalone mirrors in data/standalone-mirrors.json against its monorepo source at the last synced commit (GitHub API, with a README-timestamp fallback when rate-limited), flags any package whose GitHub copy has diverged, and writes the result to tasks/mirror-drift-<date>.json. It never pushes or mutates a mirror; it is the audit step that found the two fixes above. (`/docs/contributing`) `[infra, docs]`
- **Atomic is now a six-tab Transaction V1 lab, not just an inspector**: /atomic grew five tabs beyond the Inspector, each reachable by click, arrow-key/Home/End tab navigation, or a deep link (?tab=mask, ?tab=sponsor, ?tab=planner, ?tab=diff, ?tab=wallet). The config mask decoder reads a V1 transaction's real TransactionConfigMask u32 and its fixed-width ConfigValues byte by byte, flagging a half-set priority-fee pair or a reserved bit SIMD-0385 has not assigned yet. The sponsor cap view shows a paymaster exactly what it is agreeing to pay, reading V1's inline config instead of a Compute Budget instruction scan that sees nothing on a V1 transaction. The size and budget planner compiles a pasted instruction set with @solana/kit to an exact byte count against legacy, V0, or V1's ceiling, including an exact lamport total for a chosen priority fee. The legacy/V0/V1 diff compiles the same instructions three ways and reports the real byte deltas, honestly, including the case where V1's inline config makes it larger than legacy. The wallet V1 capability check connects the browser's injected wallet and reports the same verdict the rest of three.ws would get from findV1WalletStandardSigner before ever requesting a real V1 signature. Nothing here is estimated: every number comes from compiling and decoding real transactions, and nothing is ever signed, simulated, or broadcast. (`/atomic`) `[feature]`
- **Atomic now replays a pump.fun transaction step by step**: Atomic (/atomic) decodes every Pump, PumpSwap, and PumpFees event in a transaction's logs, oldest first, and renders it as a Replay panel: a bonding-curve-position bar, a human-readable description of each step (create, buy/sell, graduation, creator-fee collection and distribution, GitHub social-fee claims, and post-graduation PumpSwap swaps), and the SOL/token amounts that moved. An event the installed SDK does not recognize still renders, labeled unrecognized, instead of silently disappearing. For a create transaction, the panel also pages through the earliest trades on that mint since launch, walking Solana's signature history backward in bounded pages since RPC has no forward cursor. `[feature]`
diff --git a/data/changelog.json b/data/changelog.json
index 0bec3444a..ca5b4746d 100644
--- a/data/changelog.json
+++ b/data/changelog.json
@@ -1,6 +1,16 @@
{
"$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, desktop (desktop entries become the desktop app's release notes). `link` is optional and must be a live three.ws path.",
"entries": [
+ {
+ "date": "2026-10-14",
+ "title": "A new wallet linkage score flags a coin's creator buying their own launch",
+ "summary": "GET /api/crypto/linkage cross-checks 2-10 Solana addresses for shared control: a 0-100 same-controller score per pair, combining six real on-chain signals by noisy-OR (shared fee payer, one address funding the other, both sharing a first funder, SPL token-account control, direct transfers, a shared funder sending similar amounts in a short window), every match backed by the signature or account that triggered it. It is keyless, free, and part of the public Crypto Data API, and now wired into two places that act on money: the Trade Safety Firewall warns when an early buyer scores as the same controller as a coin's creator (wash-trading dressed up as demand), and copy-trading refuses to size an order behind a leader whose own wallet links to the creator of the coin they are 'signaling', showing the follower exactly why. The same scorer ships as the wallet_linkage tool in the hosted intel MCP server for any AI agent to call directly.",
+ "tags": [
+ "feature",
+ "security"
+ ],
+ "link": "/crypto-api"
+ },
{
"date": "2026-10-14",
"title": "The native $THREE launchpad now taxes snipers, not just steady trading",
diff --git a/docs/crypto-api.md b/docs/crypto-api.md
index a0e6d978d..fe4b0a61c 100644
--- a/docs/crypto-api.md
+++ b/docs/crypto-api.md
@@ -48,6 +48,7 @@ is documented in its section below and machine-readable in the OpenAPI doc.
| [`/api/crypto/bonding`](https://three.ws/api/crypto/bonding) | `GET` | Where a pump.fun token sits on its bonding curve — % to graduation, SOL in the curve, and whether it has migrated to an AMM. |
| [`/api/crypto/holders`](https://three.ws/api/crypto/holders) | `GET` | Holder distribution for a Solana token — top wallets with % of supply, cumulative top-10 share, and a documented concentration verdict. |
| [`/api/crypto/launches`](https://three.ws/api/crypto/launches) | `GET` | The freshest pump.fun launches, newest first — age, market cap, bonding-curve progress, dev wallet — with `minMarketCap` / `maxAgeMin` filters built for polling agents. |
+| [`/api/crypto/linkage`](https://three.ws/api/crypto/linkage) | `GET` | Whether 2-10 Solana wallets share a controller - pairwise 0-100 same-controller scores with evidence (shared fee payer, first-funder, token-account control, direct transfer, funding burst). |
| [`/api/crypto/portfolio`](https://three.ws/api/crypto/portfolio) | `GET` | A wallet read shaped for a portfolio view - stable/major/other split, top-asset allocation, per-token 24h change, and an aggregate 24h move that states its own coverage. |
| [`/api/crypto/security`](https://three.ws/api/crypto/security) | `GET` | Pre-trade rug check for a Solana token — authority, concentration, liquidity, mutability, and LP-custody facts composed into a deterministic riskLevel. |
| [`/api/crypto/symbol`](https://three.ws/api/crypto/symbol) | `GET` · `POST` | Whether up to 20 candidate tickers are taken — exact and fuzzy (look-alike) collisions across live registries. |
@@ -1052,6 +1053,88 @@ curl -s "https://three.ws/api/crypto/airdrops?address=<wallet>" \
---
+## `GET /api/crypto/linkage` - Wallet linkage (same-controller scoring)
+
+**Use-case.** A *sniper or copy-trade agent* vetting a coin's early buyers
+needs to know whether they are independent actors or the creator's own alts
+dressed up as organic demand, and a *copy-trade follower* needs to know a
+leader isn't secretly the creator of the coin they're "signaling". One call
+answers both: pairwise 0-100 same-controller scores, with evidence, across
+2-10 Solana addresses.
+
+### Request
+
+| Param | Type | Default | Notes |
+|-------------|--------|----------|-------|
+| `addresses` | string | required | Comma-separated list of 2 to 10 Solana addresses to cross-check. |
+
+### Response
+
+```json
+{
+ "addresses": ["FeMbDoX7R1Psc4GEcvJdsbNbZA3bfztcyDCatJVJpump", "11111111111111111111111111111111"],
+ "pairs": [
+ {
+ "a": "FeMbDoX7R1Psc4GEcvJdsbNbZA3bfztcyDCatJVJpump",
+ "b": "11111111111111111111111111111111",
+ "score": 0,
+ "band": "none",
+ "topSignal": null,
+ "signals": [],
+ "evidence": []
+ }
+ ],
+ "complete": true,
+ "ts": "2026-10-14T20:00:00.000Z"
+}
+```
+
+- **`score`/`band`** - a 0-100 noisy-OR combination of six signals (shared fee
+ payer, one address funding the other, both sharing a first funder, SPL
+ token-account control, direct transfers, a shared funder sending similar
+ amounts in a short window), bucketed into `none` / `weak` / `moderate` /
+ `strong` / `confirmed`.
+- **`topSignal`** - the single highest-weight signal that fired for the pair,
+ or `null` when no signal fired.
+- **`evidence`** - the signature or account that triggered each contributing
+ signal, so a caller can verify the claim on-chain rather than trust the score
+ blind.
+- **`complete: false`** - at least one address's history walk hit its time or
+ request budget before finishing. The score is still real, just possibly
+ based on partial history.
+
+### Sources
+
+Solana RPC only (this deployment's own failover chain, keyless): account info,
+parsed transaction history, and signature lists for each address. A known
+service/exchange wallet that funds many unrelated addresses is excluded from
+the shared-funder signals at runtime (`WALLET_LINKAGE_EXCLUDED_ACCOUNTS` /
+`WALLET_LINKAGE_EXCLUSIONS_PATH`) rather than evidence of a link.
+
+### States
+
+- **2-10 valid Solana addresses** -> `200` with scored pairs.
+- **Missing `addresses`** -> `400 missing_addresses`.
+- **Fewer than 2 or more than 10 addresses** -> `400 invalid_address_count`.
+- **An EVM address mixed in** -> `400 unsupported_chain` (Solana only; this
+ endpoint is Solana-first by design, not an EVM gap).
+- **A malformed address** -> `400 invalid_address`.
+- **Solana RPC unreachable** -> `503 upstream_unavailable` with
+ `Retry-After: 15`, or a `200` stale envelope if a cached result exists.
+- **Rate-limited** -> `429`.
+
+### Examples
+
+```bash
+# Are these two wallets the same controller?
+curl -s "https://three.ws/api/crypto/linkage?addresses=<walletA>,<walletB>"
+
+# Highest-scoring pair only
+curl -s "https://three.ws/api/crypto/linkage?addresses=<a>,<b>,<c>" | jq '.pairs | max_by(.score)'
+```
+
+---
+
## Related
- [Market Data API](/docs/market-data-api) - the paid x402 twin: coin prices, DeFi TVL, yields, gas, and the per-datapoint fabric
diff --git a/public/changelog-recent.json b/public/changelog-recent.json
index e8126e7b2..7ac4ed8e8 100644
--- a/public/changelog-recent.json
+++ b/public/changelog-recent.json
@@ -1,14 +1,25 @@
{
- "generated_at": "2026-10-14T20:00:23.214Z",
+ "generated_at": "2026-10-14T20:51:56.774Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json",
"site": {
"name": "three.ws",
"url": "https://three.ws"
},
- "total": 4091,
+ "total": 4092,
"complete": false,
"full_feed": "/changelog.json",
"entries": [
+ {
+ "date": "2026-10-14",
+ "type": "update",
+ "title": "A new wallet linkage score flags a coin's creator buying their own launch",
+ "summary": "GET /api/crypto/linkage cross-checks 2-10 Solana addresses for shared control: a 0-100 same-controller score per pair, combining six real on-chain signals by noisy-OR (shared fee payer, one address funding the other, both sharing a first funder, SPL token-account control, direct transfers, a shared funder sending similar amounts in a short window), every match backed by the signature or account that triggered it. It is keyless, free, and part of the public Crypto Data API, and now wired into two places that act on money: the Trade Safety Firewall warns when an early buyer scores as the same controller as a coin's creator (wash-trading dressed up as demand), and copy-trading refuses to size an order behind a leader whose own wallet links to the creator of the coin they are 'signaling', showing the follower exactly why. The same scorer ships as the wallet_linkage tool in the hosted intel MCP server for any AI agent to call directly.",
+ "link": "/crypto-api",
+ "tags": [
+ "feature",
+ "security"
+ ]
+ },
{
"date": "2026-10-14",
"type": "update",
@@ -1546,17 +1557,6 @@
"feature",
"improvement"
]
- },
- {
- "date": "2026-10-10",
- "type": "update",
- "title": "Agents get their own email inbox",
- "summary": "Every agent can now have an email address on agents.three.ws, with an inbox right on its profile (the Mail button). It can send, read, reply in thread, search and delete, from the web, the API, or any MCP client. Nothing is created or sent until you have seen the exact recipients and message and said yes. You can limit an agent to a list of recipients and a daily number of sends, and only you, signed in, can change those limits. Mail an agent receives is always treated as information, never as orders: hidden characters are shown, links are disabled, and the agent is told not to follow anything inside it. Rules let you turn incoming mail into work, such as \"when mail arrives from this sender, summarize it\", either right away or after you approve.",
- "link": "/agent-mail",
- "tags": [
- "feature",
- "security"
- ]
}
]
}
diff --git a/public/changelog.json b/public/changelog.json
index f3f052103..8fdced06c 100644
--- a/public/changelog.json
+++ b/public/changelog.json
@@ -1,11 +1,22 @@
{
- "generated_at": "2026-10-14T20:00:23.194Z",
+ "generated_at": "2026-10-14T20:51:56.754Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json",
"site": {
"name": "three.ws",
"url": "https://three.ws"
},
"entries": [
+ {
+ "date": "2026-10-14",
+ "type": "update",
+ "title": "A new wallet linkage score flags a coin's creator buying their own launch",
+ "summary": "GET /api/crypto/linkage cross-checks 2-10 Solana addresses for shared control: a 0-100 same-controller score per pair, combining six real on-chain signals by noisy-OR (shared fee payer, one address funding the other, both sharing a first funder, SPL token-account control, direct transfers, a shared funder sending similar amounts in a short window), every match backed by the signature or account that triggered it. It is keyless, free, and part of the public Crypto Data API, and now wired into two places that act on money: the Trade Safety Firewall warns when an early buyer scores as the same controller as a coin's creator (wash-trading dressed up as demand), and copy-trading refuses to size an order behind a leader whose own wallet links to the creator of the coin they are 'signaling', showing the follower exactly why. The same scorer ships as the wallet_linkage tool in the hosted intel MCP server for any AI agent to call directly.",
+ "link": "/crypto-api",
+ "tags": [
+ "feature",
+ "security"
+ ]
+ },
{
"date": "2026-10-14",
"type": "update",
diff --git a/public/changelog.xml b/public/changelog.xml
index 1340a2a46..a96d89e76 100644
--- a/public/changelog.xml
+++ b/public/changelog.xml
@@ -6,6 +6,14 @@
<atom:link href="https://three.ws/changelog.xml" rel="self" type="application/rss+xml"/>
<description>What's new on three.ws: features, improvements, and releases, newest first.</description>
<language>en</language>
+ <item>
+ <title>A new wallet linkage score flags a coin's creator buying their own launch</title>
+ <link>https://three.ws/crypto-api</link>
+ <guid isPermaLink="false">2026-10-14:A new wallet linkage score flags a coin's creator buying their own launch</guid>
+ <pubDate>Wed, 14 Oct 2026 12:00:00 GMT</pubDate>
+ <category>feature</category>
+ <description>GET /api/crypto/linkage cross-checks 2-10 Solana addresses for shared control: a 0-100 same-controller score per pair, combining six real on-chain signals by noisy-OR (shared fee payer, one address funding the other, both sharing a first funder, SPL token-account control, direct transfers, a shared funder sending similar amounts in a short window), every match backed by the signature or account that triggered it. It is keyless, free, and part of the public Crypto Data API, and now wired into two places that act on money: the Trade Safety Firewall warns when an early buyer scores as the same controller as a coin's creator (wash-trading dressed up as demand), and copy-trading refuses to size an order behind a leader whose own wallet links to the creator of the coin they are 'signaling', showing the follower exactly why. The same scorer ships as the wallet_linkage tool in the hosted intel MCP server for any AI agent to call directly.</description>
+ </item>
<item>
<title>A read-only drift report for every standalone GitHub mirror</title>
<link>https://three.ws/docs/contributing</link>
diff --git a/public/features.json b/public/features.json
index 3360eb253..35cab0aa5 100644
--- a/public/features.json
+++ b/public/features.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-10-14T20:00:23.182Z",
+ "generated_at": "2026-10-14T20:51:56.741Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json",
"site": {
"name": "three.ws",
diff --git a/public/sitemap/index.html b/public/sitemap/index.html
index f5be9ba7d..c49ff27f5 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,16 +95,16 @@
<header><div id="nav-container"></div></header>
<main class="sm-wrap">
<div class="sm-hero">
- <h1 data-i18n="sitemap_index.sitemap">Sitemap</h1>
+ <h1>Sitemap</h1>
<p><span>1078</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">
@@ -114,8 +114,8 @@
</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="/video-to-motion">
@@ -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>75</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>
@@ -741,7 +741,7 @@
<section class="sm-section" id="build">
<header>
<h2><span data-i18n="sitemap_index.section_build">Build</span><span class="sm-count" data-count>94</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>
@@ -1408,7 +1408,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>
@@ -1599,7 +1599,7 @@
<section class="sm-section" id="crypto">
<header>
<h2><span data-i18n="sitemap_index.section_crypto">Crypto</span><span class="sm-count" data-count>170</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>
@@ -2798,7 +2798,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>
@@ -2884,7 +2884,7 @@
<section class="sm-section" id="account">
<header>
<h2><span data-i18n="sitemap_index.section_account">Account</span><span class="sm-count" data-count>15</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>
@@ -2998,7 +2998,7 @@
<section class="sm-section" id="learn">
<header>
<h2><span data-i18n="sitemap_index.section_learn">Learn</span><span class="sm-count" data-count>509</span></h2>
- <p class="sm-section-desc" data-i18n="sitemap_index.docs_tutorials_and_reference">Docs, tutorials, and reference.</p>
+ <p class="sm-section-desc">Docs, tutorials, and reference.</p>
</header>
<ul class="sm-list">
<li>
@@ -6570,7 +6570,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>
@@ -6924,7 +6924,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>18</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>
@@ -7059,7 +7059,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>
@@ -7850,10 +7850,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>