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(readme): say open source everywhere and put the contributor path on the first screen

nirholasba05fde46d25
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 7fa2cb6ad..f300a0592 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -4,6 +4,10 @@
Public history for [three.ws](https://three.ws), newest first. New pages come from `added` dates in data/pages.json; everything else is curated in data/changelog.json. Also available as [JSON](https://three.ws/changelog.json) and [RSS](https://three.ws/changelog.xml), live at [three.ws/changelog](https://three.ws/changelog).
+## 2026-08-22
+
+- **The README now says open source, because it is**: Ten places across the README and our published articles still described three.ws as source-available, which understated the Apache 2.0 license the project actually ships under. They now say open source, and the README explains what that buys you: fork it, self-host it, ship commercial work on it. The top of the README also carries a license badge, a live count of good first issues, and a one-line path for anyone who wants to contribute rather than just use it. The security reporting line no longer points at a retired mirror repository. (`/docs/first-contribution`) `[docs]`
+
## 2026-08-21
- **Docs · Community** (`/docs/community`): Where the three.ws community talks: GitHub Discussions, the Telegram community, the X community, the IBM Community group, and the release channel, with guidance on which room fits which question.
diff --git a/README.md b/README.md
index 9d7afd30b..ac518f7b5 100644
--- a/README.md
+++ b/README.md
@@ -2,14 +2,16 @@
[**Website**](https://three.ws) · [**Docs**](https://three.ws/docs) · [**Changelog**](https://three.ws/changelog) · [**X / Twitter**](https://x.com/trythreews) · [**GitHub**](https://github.com/nirholas/three.ws) · [**$THREE on pump.fun**](https://pump.fun/FeMbDoX7R1Psc4GEcvJdsbNbZA3bfztcyDCatJVJpump)
-[![site](https://img.shields.io/website?url=https%3A%2F%2Fthree.ws&label=three.ws)](https://three.ws) [![npm](https://img.shields.io/npm/v/%40three-ws%2Fsdk?label=%40three-ws%2Fsdk)](https://www.npmjs.com/package/@three-ws/sdk) [![npm](https://img.shields.io/npm/v/%40three-ws%2Fmcp-server?label=%40three-ws%2Fmcp-server)](https://www.npmjs.com/package/@three-ws/mcp-server) [![MCP Registry](https://img.shields.io/badge/MCP_Registry-io.github.nirholas-blue)](https://registry.modelcontextprotocol.io/?q=io.github.nirholas) [![x402scan](https://img.shields.io/badge/x402scan-listed-green)](https://www.x402scan.com/server/17cbd874-52ac-4920-a020-b22ff2489a07)
+[![site](https://img.shields.io/website?url=https%3A%2F%2Fthree.ws&label=three.ws)](https://three.ws) [![npm](https://img.shields.io/npm/v/%40three-ws%2Fsdk?label=%40three-ws%2Fsdk)](https://www.npmjs.com/package/@three-ws/sdk) [![npm](https://img.shields.io/npm/v/%40three-ws%2Fmcp-server?label=%40three-ws%2Fmcp-server)](https://www.npmjs.com/package/@three-ws/mcp-server) [![MCP Registry](https://img.shields.io/badge/MCP_Registry-io.github.nirholas-blue)](https://registry.modelcontextprotocol.io/?q=io.github.nirholas) [![x402scan](https://img.shields.io/badge/x402scan-listed-green)](https://www.x402scan.com/server/17cbd874-52ac-4920-a020-b22ff2489a07) [![License: Apache 2.0](https://img.shields.io/badge/license-Apache--2.0-blue)](LICENSE) [![good first issues](https://img.shields.io/github/issues/nirholas/three.ws/good%20first%20issue?label=good%20first%20issues&color=7057ff)](https://github.com/nirholas/three.ws/labels/good%20first%20issue)
https://github.com/user-attachments/assets/d52515d1-cb04-4dd6-98bd-fef233312dc4
-**Give your AI a body.** three.ws is a source-available, browser-native 3D AI agent platform. Type a prompt and [**Forge**](https://three.ws/forge) generates a textured 3D model, or drop a GLB you already have. Add an LLM brain, register on-chain, and embed anywhere: no plugins, no server uploads, no installs required.
+**Give your AI a body.** three.ws is an open source (Apache-2.0), browser-native 3D AI agent platform. Type a prompt and [**Forge**](https://three.ws/forge) generates a textured 3D model, or drop a GLB you already have. Add an LLM brain, register on-chain, and embed anywhere: no plugins, no server uploads, no installs required.
> **Try it in 60 seconds:** open [three.ws/forge](https://three.ws/forge), type *"a brass steampunk owl, full body"*, and download the GLB. Text→3D, image→3D, and sketch→3D — free draft tier, no account. [Jump to the Forge section ↓](#forge--text--image-to-3d)
+> **Want to build it with us?** [Your first contribution](docs/first-contribution.md) goes from clone to open pull request in about 15 minutes, with a full worked example. Every [`good first issue`](https://github.com/nirholas/three.ws/labels/good%20first%20issue) names the file to change and the command that proves it worked. Say hello in [Discussions](https://github.com/nirholas/three.ws/discussions) or [Telegram](https://t.me/three_ws_community).
+
### Meet the avatar: a live 3D model, right here in markdown
Drag to rotate. This is not an image or a video: it is an interactive 3D model rendered natively by GitHub. The avatar was generated from a one-line text prompt on [three.ws Forge](https://three.ws/forge) (free tier), decimated to 1,200 triangles, and embedded as ASCII STL with [readme-3d](packages/readme-3d), our open-source toolkit for putting 3D models in any GitHub README, issue, or discussion.
@@ -8531,7 +8533,7 @@ At its core, it does five things:
The backend is a set of serverless-style handlers (in `api/`) served in production by a single Google Cloud Run container ([server/index.mjs](server/index.mjs)), backed by Neon Postgres for metadata, Cloudflare R2 for model storage, and Upstash Redis for rate limiting. It exposes a full OAuth 2.1 authorization server and an MCP (Model Context Protocol) endpoint so external AI systems can drive avatars programmatically.
-three.ws is production-ready and serves [three.ws](https://three.ws) live on Google Cloud Run: `GET https://three.ws/api/version` returns the exact commit the site is running right now. The entire stack (viewer, agent runtime, contracts, backend, and web component) is source-available in this repository; see [LICENSE](LICENSE) for terms.
+three.ws is production-ready and serves [three.ws](https://three.ws) live on Google Cloud Run: `GET https://three.ws/api/version` returns the exact commit the site is running right now. The entire stack (viewer, agent runtime, contracts, backend, and web component) is open source in this repository under the [Apache License 2.0](LICENSE): fork it, self-host it, and ship commercial work on it.
---
@@ -11339,7 +11341,7 @@ See [CONTRIBUTING.md](CONTRIBUTING.md) for the full contributor guide. Contribut
Please **do not** file public GitHub issues for vulnerabilities. Disclosure runs on a coordinated timeline so users get a fix before details circulate.
-1. Email **[email protected]** (or open a [private GitHub security advisory](https://github.com/nirholas/three.ws/security/advisories/new) on the mirror repos) with a clear write-up: affected component, reproduction steps, and the impact you observed.
+1. Email **[email protected]** or open a [private GitHub security advisory](https://github.com/nirholas/three.ws/security/advisories/new), with a clear write-up: affected component, reproduction steps, and the impact you observed.
2. You will receive an acknowledgement within two business days.
3. We aim to ship a fix or mitigation within 30 days for high-severity reports, and to credit reporters in the release notes (unless you ask to remain anonymous).
diff --git a/data/changelog.json b/data/changelog.json
index 74b39f241..09434a030 100644
--- a/data/changelog.json
+++ b/data/changelog.json
@@ -1,6 +1,15 @@
{
"$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-22",
+ "title": "The README now says open source, because it is",
+ "summary": "Ten places across the README and our published articles still described three.ws as source-available, which understated the Apache 2.0 license the project actually ships under. They now say open source, and the README explains what that buys you: fork it, self-host it, ship commercial work on it. The top of the README also carries a license badge, a live count of good first issues, and a one-line path for anyone who wants to contribute rather than just use it. The security reporting line no longer points at a retired mirror repository.",
+ "tags": [
+ "docs"
+ ],
+ "link": "/docs/first-contribution"
+ },
{
"date": "2026-08-21",
"title": "three.ws is now open source under Apache 2.0",
diff --git a/docs/ALL.md b/docs/ALL.md
index 8564bf0e4..a83454986 100644
--- a/docs/ALL.md
+++ b/docs/ALL.md
@@ -1,7 +1,7 @@
<!-- GENERATED by scripts/combine-docs.mjs — do not edit by hand. Edit the source files under docs/ and re-run. -->
# three.ws — Combined Documentation
-> Single-file snapshot of every document under [`docs/`](.). Generated 2026-08-21 from **556 files** (~7831 KB).
+> Single-file snapshot of every document under [`docs/`](.). Generated 2026-08-22 from **557 files** (~7839 KB).
> The individual source files remain the canonical, editable copies — this file is a read-only aggregate.
## Table of contents
@@ -317,15 +317,15 @@
- [world-lines.md](#sec-518)
- [x-archive.md](#sec-519)
- [x-memory-seeding.md](#sec-521)
-- [x402-buyer.md](#sec-543)
-- [x402-dev-tools.md](#sec-544)
-- [x402-distribution.md](#sec-545)
-- [x402-endpoints.md](#sec-546)
-- [x402-revenue.md](#sec-547)
-- [x402-ring-economy.md](#sec-548)
-- [x402-solana-july-roundup-response.md](#sec-549)
-- [x402-studio.md](#sec-550)
-- [x402.md](#sec-551)
+- [x402-buyer.md](#sec-544)
+- [x402-dev-tools.md](#sec-545)
+- [x402-distribution.md](#sec-546)
+- [x402-endpoints.md](#sec-547)
+- [x402-revenue.md](#sec-548)
+- [x402-ring-economy.md](#sec-549)
+- [x402-solana-july-roundup-response.md](#sec-550)
+- [x402-studio.md](#sec-551)
+- [x402.md](#sec-552)
### agent-abilities
@@ -596,31 +596,32 @@
- [x-posts/3d-ar-studio-video-script.md](#sec-523)
- [x-posts/README.md](#sec-524)
- [x-posts/ar-quick-look-fix-x-post.md](#sec-525)
-- [x-posts/event-x-posts.md](#sec-526)
-- [x-posts/fomo-verified-x-post.md](#sec-527)
-- [x-posts/ibm-skillsbuild-x-post.md](#sec-528)
-- [x-posts/mcp-registry-fleet-x-post.md](#sec-529)
-- [x-posts/metaplex-agent-deployer-video-script.md](#sec-530)
-- [x-posts/metaplex-agent-deployer-x-post.md](#sec-531)
-- [x-posts/metaplex-agent-mcp-launch.md](#sec-532)
-- [x-posts/metaplex-agent-mcp-veo-script.md](#sec-533)
-- [x-posts/metaplex-agent-mcp-x-post.md](#sec-534)
-- [x-posts/news-archive-x-post.md](#sec-535)
-- [x-posts/onchain-agent-wallets-x-post.md](#sec-536)
-- [x-posts/oracle-trading-mcp-x-post.md](#sec-537)
-- [x-posts/pumpfun-article-x-post.md](#sec-538)
-- [x-posts/sperax-staking-in-chat-x-post.md](#sec-539)
-- [x-posts/threews-avatar-launch.md](#sec-540)
-- [x-posts/threews-avatar-video-script.md](#sec-541)
-- [x-posts/x-meetup-posts.md](#sec-542)
+- [x-posts/coinbase-listing-thank-you-reply.md](#sec-526)
+- [x-posts/event-x-posts.md](#sec-527)
+- [x-posts/fomo-verified-x-post.md](#sec-528)
+- [x-posts/ibm-skillsbuild-x-post.md](#sec-529)
+- [x-posts/mcp-registry-fleet-x-post.md](#sec-530)
+- [x-posts/metaplex-agent-deployer-video-script.md](#sec-531)
+- [x-posts/metaplex-agent-deployer-x-post.md](#sec-532)
+- [x-posts/metaplex-agent-mcp-launch.md](#sec-533)
+- [x-posts/metaplex-agent-mcp-veo-script.md](#sec-534)
+- [x-posts/metaplex-agent-mcp-x-post.md](#sec-535)
+- [x-posts/news-archive-x-post.md](#sec-536)
+- [x-posts/onchain-agent-wallets-x-post.md](#sec-537)
+- [x-posts/oracle-trading-mcp-x-post.md](#sec-538)
+- [x-posts/pumpfun-article-x-post.md](#sec-539)
+- [x-posts/sperax-staking-in-chat-x-post.md](#sec-540)
+- [x-posts/threews-avatar-launch.md](#sec-541)
+- [x-posts/threews-avatar-video-script.md](#sec-542)
+- [x-posts/x-meetup-posts.md](#sec-543)
### zauth
-- [zauth/database.md](#sec-552)
-- [zauth/index.md](#sec-553)
-- [zauth/provider-hub.md](#sec-554)
-- [zauth/reposcan.md](#sec-555)
-- [zauth/vector.md](#sec-556)
+- [zauth/database.md](#sec-553)
+- [zauth/index.md](#sec-554)
+- [zauth/provider-hub.md](#sec-555)
+- [zauth/reposcan.md](#sec-556)
+- [zauth/vector.md](#sec-557)
---
@@ -1505,11 +1506,11 @@ text/image ──► mesh_forge ──► static GLB ──► rig_mesh ──
three.ws runs a full 3D asset pipeline — the same lanes the platform uses to turn
a prompt into a rigged, game-ready character. Every working stage is sold as its
-own [x402](#sec-551) resource: an AI agent pays a few cents in USDC, hands in a URL,
+own [x402](#sec-552) resource: an AI agent pays a few cents in USDC, hands in a URL,
and gets back a finished asset URL. No API key, no account, no signup.
Nobody else in the x402 ecosystem offers this. The generation stage (text/image →
-3D) is [`/api/x402/forge`](#sec-546); the stages below are what you do to
+3D) is [`/api/x402/forge`](#sec-547); the stages below are what you do to
a mesh *after* it exists.
```
@@ -1522,7 +1523,7 @@ a mesh *after* it exists.
1. **One stage at a time** — `POST /api/x402/pipeline-<stage>`. One payment buys
one finished asset, returned inline as a durable first-party URL. This is the
reference below.
-2. **The whole chain in one call** — [`POST /api/x402/pipeline`](#sec-546).
+2. **The whole chain in one call** — [`POST /api/x402/pipeline`](#sec-547).
Submit an ordered chain (`generate → rig → remesh → gameready → stylize`); the
402 quote is the exact sum of the requested stages, and you poll the job free
at `GET /api/forge?job=<id>` while it advances. Use this when you want the full
@@ -1585,7 +1586,7 @@ console.log(output_url);
The wrapper answers the 402, signs the payment, and retries the same request, all
before your `await` resolves. Paying from a three.ws agent wallet instead of a
raw key, or settling on Solana, is covered in
-[x402 buyer client](#sec-543).
+[x402 buyer client](#sec-544).
## Stages
@@ -1744,8 +1745,8 @@ returned as-is. Poll budget is tunable via `X402_PIPELINE_POLL_BUDGET_MS`
## Related
-- [x402 paid endpoints](#sec-546) — the full catalog + pricing model
-- [x402 buyer client](#sec-543) — how to settle payments as an agent
+- [x402 paid endpoints](#sec-547) — the full catalog + pricing model
+- [x402 buyer client](#sec-544) — how to settle payments as an agent
- [Avatar pipeline](#sec-113) — the generation + rig lanes in depth
---
@@ -13635,7 +13636,7 @@ would hide it.
## Related
-- [x402 revenue and receipts](#sec-547): the other side of the ledger. This
+- [x402 revenue and receipts](#sec-548): the other side of the ledger. This
page counts agent-to-agent payments recorded in `agent_hires`; endpoint revenue
paid **to** the platform's own paid endpoints is recorded separately in
`x402_audit_log`. Do not add the two together.
@@ -14933,7 +14934,7 @@ Reputation only matters because money moves on the other side of it. The two hal
1. **Discover** a service via the Identity Registry.
2. **Check** its reputation — proceed only if it clears your threshold.
-3. **Pay** — the service answers an HTTP `402` and the agent signs a stablecoin micropayment ([x402](#sec-551)).
+3. **Pay** — the service answers an HTTP `402` and the agent signs a stablecoin micropayment ([x402](#sec-552)).
4. **Vouch** — after the work, write feedback back to the Reputation Registry, closing the loop for the next agent.
The one-liner worth remembering:
@@ -14993,7 +14994,7 @@ The only difference is **reach**. The Club's reputation dies the moment a wallet
That portability is what lets a three.ws agent be trusted by an agent that has never heard of three.ws. It's the foundation the agent economy is built on — and the reason reputation, not payments, is the harder and more important half of the stack.
-**Next:** [Read an agent's reputation](/tutorials/agent-reputation) · [Reputation on Solana](#sec-398) · [Leave a vouch](#sec-372) · [ERC-8004 identity](#sec-190) · [x402 payments](#sec-551)
+**Next:** [Read an agent's reputation](/tutorials/agent-reputation) · [Reputation on Solana](#sec-398) · [Leave a vouch](#sec-372) · [ERC-8004 identity](#sec-190) · [x402 payments](#sec-552)
---
@@ -18284,7 +18285,7 @@ An agent can pay a human-readable name instead of a base58 address. `/api/x402/p
- [Custody you can verify](#sec-172) — limits, freeze, Merkle proof-of-custody, social recovery and inheritance
- [Financial controls](#sec-223) — plain-English spend rules, compiled and enforced deterministically
- [What agents can do](#sec-009) — the complete dossier, including a page per wallet ability
-- [x402 protocol](#sec-551) — how agents pay for services
+- [x402 protocol](#sec-552) — how agents pay for services
- [Coin launches](#sec-144) — how the wallet signs a pump.fun launch
---
@@ -28948,7 +28949,7 @@ Solscan-linked "x402" provenance badge. Inline-done lanes publish immediately;
async lanes are completed server-side by `api/cron/forge-finalize`, so the
artifact lands even if you never poll. Recording happens after your response is
sent and never affects your result. See
-[x402 endpoints](#sec-546) and
+[x402 endpoints](#sec-547) and
[the autonomous economy](#sec-105).
Treat prompts as public. If you need a private lane, use the account-scoped
@@ -29000,7 +29001,7 @@ const glb = Buffer.from(await (await fetch(glbUrl)).arrayBuffer());
`text_to_3d` / `image_to_3d` tools for in-conversation use, priced from the
same tier table. This REST endpoint is the pay-per-call surface for autonomous
agents.
-- [x402 endpoints](#sec-546): every paid endpoint on the platform.
+- [x402 endpoints](#sec-547): every paid endpoint on the platform.
---
@@ -31053,7 +31054,7 @@ zero.
platform's cut.
- [Economy master](#sec-184) — the funding-root subsystem, its ledger, and the
topup/sweepback crons in depth.
-- [x402 ring economy](#sec-548) — how the autonomous payment ring settles
+- [x402 ring economy](#sec-549) — how the autonomous payment ring settles
USDC between agents.
---
@@ -31281,9 +31282,9 @@ corroborate — the ops financial-integrity surface alerts on those. Detail:
## Related
-- [x402 endpoints](#sec-546) — the paid endpoints this loop calls.
-- [x402 revenue & receipts](#sec-547) — where settlements land, the proof-of-volume ledger, and the reconciliation job.
-- [x402 buyer client](#sec-543) — the client wrappers it pays with.
+- [x402 endpoints](#sec-547) — the paid endpoints this loop calls.
+- [x402 revenue & receipts](#sec-548) — where settlements land, the proof-of-volume ledger, and the reconciliation job.
+- [x402 buyer client](#sec-544) — the client wrappers it pays with.
- [Circulation engine](#sec-141) — the separate SOL/$THREE activity loop.
---
@@ -32948,7 +32949,7 @@ prompt / image
Generation quality is a **tier** ([api/_lib/forge-tiers.js](../api/_lib/forge-tiers.js)): `draft`, `standard`
(default), or `high` — more geometric budget at higher tiers. The tier sets the
price identically across REST and MCP transports (see
-[MCP tools](#sec-279), [x402 endpoints](#sec-546)).
+[MCP tools](#sec-279), [x402 endpoints](#sec-547)).
### ② Auto-rig
@@ -33837,7 +33838,7 @@ This is a walk through the pattern we shipped instead, in production, at [three.
> The agent does not hold a wallet. It proposes spend. Governance enforces policy.
-Everything below is real code from our source-available repository, including the concurrency bug we had to design around and the failure mode that has no clean answer.
+Everything below is real code from our open source (Apache-2.0) repository, including the concurrency bug we had to design around and the failure mode that has no clean answer.
## The three bad options, and what each one actually costs
@@ -34321,7 +34322,7 @@ But a lot of teams don't want to touch crypto to pay an invoice. They want it on
The result is one authorization path that meters two ways: an AWS-subscribed customer and a stablecoin-paying developer hit the exact same endpoint, and the platform bills whichever economy that caller belongs to. This post is how we built it with the AWS SDK for JavaScript v3, the parts of the SaaS integration that are easy to get subtly wrong, and the bridge that ties an AWS `CustomerIdentifier` to an x402 key.
-Everything here is real code from our source-available repo, not pseudocode: the metering and webhook handlers call the AWS Marketplace APIs in `us-east-1` (where the Marketplace Metering and Entitlement services live).
+Everything here is real code from our open source (Apache-2.0) repo, not pseudocode: the metering and webhook handlers call the AWS Marketplace APIs in `us-east-1` (where the Marketplace Metering and Entitlement services live).
## The three integration points of a SaaS listing
@@ -35387,7 +35388,7 @@ One product. Two ways in. One authorization path.
**Learn more**
- Platform: [three.ws](https://three.ws)
- AWS Marketplace and procurement: [three.ws/docs/aws-marketplace](#sec-123)
-- How agents reach and pay for tools: [three.ws/docs/x402](#sec-551), [three.ws/docs/mcp](#sec-281)
+- How agents reach and pay for tools: [three.ws/docs/x402](#sec-552), [three.ws/docs/mcp](#sec-281)
---
@@ -36953,7 +36954,7 @@ grep -l 'vite-plugin-pwa:register-sw' dist/widget.html dist/embed.html # expec
# CA to x402
-Paste a token contract address, get back a live, agent-payable [x402](#sec-551)
+Paste a token contract address, get back a live, agent-payable [x402](#sec-552)
market-intel endpoint for that exact token. The generated endpoint costs a small
USDC payment per call, is discoverable in the x402 bazaar, and needs no keys, no
backend, and no deploy from the person who generated it.
@@ -37103,7 +37104,7 @@ actually settles against.
Operators can retune the price at deploy time with
`X402_PRICE_TOKEN_INTEL=<atomics>`; a non-integer value logs a warning and falls
-back to the default. See [x402 paid endpoints](#sec-546) for the full
+back to the default. See [x402 paid endpoints](#sec-547) for the full
price-override scheme.
---
@@ -37119,7 +37120,7 @@ A standard three.ws paid endpoint built on the shared handler
`X-PAYMENT` header gets a `402` challenge carrying the accepted networks, asset,
price, and pay-to address; the buyer retries with a signed payment and receives
the intel. Settlement is recorded like any other endpoint payment (see
-[x402 revenue and receipts](#sec-547)).
+[x402 revenue and receipts](#sec-548)).
The paid response body is the token block computed fresh at call time:
@@ -37262,11 +37263,11 @@ right now. If the endpoint is unreachable the page says so and offers a retry.
## Related
-- [x402 on three.ws](#sec-551): the protocol, the wire format, and how the
+- [x402 on three.ws](#sec-552): the protocol, the wire format, and how the
platform settles.
-- [x402 paid endpoints](#sec-546): the full catalog of our paid
+- [x402 paid endpoints](#sec-547): the full catalog of our paid
endpoints, their prices, and the `X402_PRICE_*` override scheme.
-- [x402 revenue and receipts](#sec-547): where a settled payment for this
+- [x402 revenue and receipts](#sec-548): where a settled payment for this
endpoint is recorded and how the buyer's receipt is issued.
---
@@ -40431,7 +40432,7 @@ For a CoinMarketCap reader, the load-bearing question is always: *is any of this
- **Real voice.** Peer-to-peer WebRTC with spatial HRTF audio, proximity-gated so it scales and so it sounds right.
- **Real buys.** A native pump.fun transaction built server-side and signed by your own wallet, not a redirect dressed up as a feature.
-And it's **source-available** and readable, like the rest of the platform.
+And it's **open source** and readable, like the rest of the platform.
## Why this matters
@@ -40462,7 +40463,7 @@ The chart has always told you *what* a coin is doing. /play lets you go stand wh
---
-*three.ws is an open-source, browser-native platform for 3D AI agents and on-chain communities, live at [three.ws](https://three.ws) and source-available. Coin Communities (/play) is live at [three.ws/play](https://three.ws/play).*
+*three.ws is an open-source, browser-native platform for 3D AI agents and on-chain communities, live at [three.ws](https://three.ws) and open source under Apache-2.0. Coin Communities (/play) is live at [three.ws/play](https://three.ws/play).*
---
@@ -40481,7 +40482,7 @@ target: CoinMarketCap Community / Editorial
For most of the last two years, the conversation about AI and crypto has lived inside a narrow lane: chatbots that can read a wallet balance, agents that can sign a swap, frameworks that promise "autonomous trading" but stall the moment the demo ends. What's been missing is the layer underneath all of that, a way for an AI agent to actually *exist* as a first-class object on the internet. To have an embodiment users can see. An identity that survives a model swap. A wallet that can pay for its own compute. A reputation that follows it across apps. A way to be embedded anywhere a YouTube video can be embedded today.
-[three.ws](https://three.ws) is building exactly that. It is an open-source platform that turns an AI agent into a persistent, ownable, multi-chain object, a 3D body in the browser, an LLM brain, an onchain identity registered on any of 15+ EVM networks (or Solana), and a distributable web component you can drop into any page on the internet. Every layer is source-available and readable end to end. The full stack is live and in production.
+[three.ws](https://three.ws) is building exactly that. It is an open-source platform that turns an AI agent into a persistent, ownable, multi-chain object, a 3D body in the browser, an LLM brain, an onchain identity registered on any of 15+ EVM networks (or Solana), and a distributable web component you can drop into any page on the internet. Every layer is open source under Apache-2.0 and readable end to end. The full stack is live and in production.
This article is about the part of three.ws that matters most to the crypto-native reader: **the onchain layer**. How the platform uses ERC-8004 across the EVM ecosystem, why it deploys to the same address on every chain, how Solana fits in, what role IPFS plays, and where the project is heading with agent tokens, reputation markets, skill royalties, and a decentralized inference network.
@@ -40647,7 +40648,7 @@ Plenty of teams are building AI agents. Plenty of teams are building agent ident
- The reputation system is open and pseudonymous, not curated by a moderator.
- The economic future of the platform, agent tokens, royalties, payments, inference settlement, is being built on contracts and cryptographic permissions, not on Stripe and a terms-of-service page.
-The platform is source-available. The viewer, the runtime, the contracts, the backend, the embedding layer, all of it is readable. If three.ws disappeared tomorrow, the agents minted today would still be onchain, their manifests would still be pinned to IPFS, the contracts would still be callable, and any reasonably motivated developer could rebuild the frontend in a weekend.
+The platform is open source under the Apache License 2.0. The viewer, the runtime, the contracts, the backend, the embedding layer, all of it is readable, forkable, and yours to run. If three.ws disappeared tomorrow, the agents minted today would still be onchain, their manifests would still be pinned to IPFS, the contracts would still be callable, and any reasonably motivated developer could rebuild the frontend in a weekend.
That's the property that distinguishes a *protocol* from a product. Most "AI agent platforms" today are products. three.ws is being built as a protocol, with an unfortunately polished product layer attached so people who are not developers can use it.
@@ -40665,7 +40666,7 @@ If you've been waiting for the moment AI and crypto stop talking past each other
---
-*three.ws is source-available. The repo, contracts, and full roadmap are at [github.com/nirholas/three.ws](https://github.com/nirholas/three.ws). The platform is live at [three.ws](https://three.ws).*
+*three.ws is open source under Apache-2.0. The repo, contracts, and full roadmap are at [github.com/nirholas/three.ws](https://github.com/nirholas/three.ws). The platform is live at [three.ws](https://three.ws).*
---
@@ -40788,7 +40789,7 @@ close.
---
*three.ws is an open-source, browser-native platform for 3D AI agents and on-chain communities, live
-at [three.ws](https://three.ws) and source-available. The Three.ws User Group on IBM Community is
+at [three.ws](https://three.ws) and open source under Apache-2.0. The Three.ws User Group on IBM Community is
at [community.ibm.com](https://community.ibm.com/community/user/usergroup?CommunityKey=e71510cc-d953-408f-9a1c-019f5c0a7016).*
---
@@ -41660,7 +41661,7 @@ A headless agent is a black box. There's no standard way for another agent to di
Four real surfaces give your agent a body, an interface, a wallet, and an identity:
1. **MCP server** — [`@three-ws/mcp-server`](#sec-281) exposes three.ws tools over MCP (JSON-RPC 2.0 over HTTP) so Claude Desktop, Cursor, Claude Code, or any MCP host can drive an avatar and its tools programmatically.
-2. **x402 paid endpoints** — [native x402](#sec-551) paid endpoints on Base, BSC, and Solana let agents pay each other in USDC for API calls, asset downloads, and skill royalties. Discover and transact via the [bazaar](https://three.ws/x402); **pay-by-name** resolves `@username` / `*.sol` to a recipient so the payer verifies a human-readable name before signing.
+2. **x402 paid endpoints** — [native x402](#sec-552) paid endpoints on Base, BSC, and Solana let agents pay each other in USDC for API calls, asset downloads, and skill royalties. Discover and transact via the [bazaar](https://three.ws/x402); **pay-by-name** resolves `@username` / `*.sol` to a recipient so the payer verifies a human-readable name before signing.
3. **A2A — agent-to-agent protocol** — an [A2A client + server, MCP bridge, DID resolution, and spending ledger](../README.md#a2a--agent-to-agent-protocol) so agents transact autonomously through delegated signer wallets and EIP-7710 permissions.
4. **On-chain identity** — register the agent as an [ERC-8004 token on any EVM chain or a Metaplex Core asset on Solana](../README.md#on-chain-identity-erc-8004--metaplex-core). Each agent gets a stable ID, an owner wallet, a delegated signer, an IPFS-pinned manifest, and a signed action log. SDKs live in [`sdk/`](../sdk) (`@three-ws/sdk`), with EVM payments in `agent-payments-sdk/` and Solana in `solana-agent-sdk/`.
@@ -41669,7 +41670,7 @@ Four real surfaces give your agent a body, an interface, a wallet, and an identi
> **Imagine a developer, "Vega," who built a market-intelligence agent** and wants it to (a) be callable by other agents, (b) charge for premium queries, and (c) have an identity its callers can trust. Here's the path they'd take.
1. Vega wires the [`@three-ws/mcp-server`](#sec-281) into their MCP host config (`npx -y @three-ws/mcp-server`) so their agent's tools are reachable over MCP.
-2. They expose the premium "deep snapshot" query as an [x402 paid endpoint](#sec-551): callers hit it, receive a `402` with a price manifest, pay USDC on Base (or Solana), and retry to get the data. The endpoint advertises a `recipient_name` so payers see a readable identity before signing.
+2. They expose the premium "deep snapshot" query as an [x402 paid endpoint](#sec-552): callers hit it, receive a `402` with a price manifest, pay USDC on Base (or Solana), and retry to get the data. The endpoint advertises a `recipient_name` so payers see a readable identity before signing.
3. They register the agent on-chain with the SDK in [`sdk/`](../sdk) — ERC-8004 on an EVM chain or a Metaplex Core asset on Solana — giving it a stable ID, a delegated signer wallet, and a signed action log. Its [on-chain passport](https://three.ws/a/sol/EXAMPLE_ASSET) renders at `/a/[chain]/[id]`.
4. Another agent discovers Vega's service in the [bazaar](https://three.ws/x402), pays via x402, and consumes it over A2A — agents paying agents, settled in USDC, with both identities verifiable on-chain.
5. **Deliverable:** an embodied, MCP-callable agent with a paid endpoint and a forgery-proof on-chain identity — a real economic actor other agents can find, trust, and pay.
@@ -41680,7 +41681,7 @@ A standards-based interface (MCP + A2A), a working USDC payment rail (x402 on Ba
## Next step / CTA
-- Start: [MCP setup](#sec-281) · [x402 docs](#sec-551) · [SDK docs](#sec-379) · register via [Register On-Chain](#sec-468).
+- Start: [MCP setup](#sec-281) · [x402 docs](#sec-552) · [SDK docs](#sec-379) · register via [Register On-Chain](#sec-468).
- Browse: the [x402 bazaar](https://three.ws/x402) and [MCP Registry listing](https://registry.modelcontextprotocol.io/?q=three.ws).
- **Social spotlight angle (G03):** "Your headless agent → MCP-callable, x402-payable, and on-chain in an afternoon."
- `[REAL CASE STUDY — fill on consent: a developer whose agent earned or paid via x402 in production.]`
@@ -41767,7 +41768,7 @@ A token's community lives in scattered chat apps and a price chart. There's no s
Three real surfaces turn a token into a living world with its own economy:
1. **Coin Communities — a live 3D world per token** — [`/communities`](https://three.ws/communities) and [`/play`](https://three.ws/play) give every Solana token its own shared 3D world. Holders who pick the same world land **together**: peer avatars, chat, emotes, voxel building, and a live market-cap screen. The [`$THREE` home town](https://three.ws/play) is the flagship world.
-2. **An agent economy — agents paying agents** — inside the `$THREE` home town, autonomous agents transact **on-chain via x402** (agents paying each other in USDC for services), demonstrating a real agent-exchange economy, not a simulation. This builds on the platform's [native x402 rails](#sec-551) (Base, BSC, Solana).
+2. **An agent economy — agents paying agents** — inside the `$THREE` home town, autonomous agents transact **on-chain via x402** (agents paying each other in USDC for services), demonstrating a real agent-exchange economy, not a simulation. This builds on the platform's [native x402 rails](#sec-552) (Base, BSC, Solana).
3. **On-chain reputation & identity** — agents and contributions carry [ERC-8004 / Metaplex Core identity](../README.md#on-chain-identity-erc-8004--metaplex-core) with signed action logs and a [reputation registry](https://three.ws/reputation), plus a pump.fun-native launch/visualize toolset at [`/pumpfun`](https://three.ws/pumpfun) and [`/pump-visualizer`](https://three.ws/pump-visualizer).
## Example workflow (hypothetical)
@@ -41787,7 +41788,7 @@ A shared 3D home for the token's holders, a real (not mocked) on-chain agent-exc
## Next step / CTA
- Start: [`/communities`](https://three.ws/communities) → the [`$THREE` home town](https://three.ws/play) → [`/pumpfun`](https://three.ws/pumpfun) and [`/pump-visualizer`](https://three.ws/pump-visualizer).
-- Build: [x402 docs](#sec-551) for the agent-economy rails · [Register On-Chain](#sec-468) for reputation.
+- Build: [x402 docs](#sec-552) for the agent-economy rails · [Register On-Chain](#sec-468) for reputation.
- **Social spotlight angle (G03):** "Watch two agents pay each other on-chain inside a live 3D `$THREE` town — your community's home."
- `[REAL CASE STUDY — fill on consent: a community that gathered in its 3D world and what changed for engagement.]`
@@ -45054,7 +45055,7 @@ Every step of recovery and inheritance writes to the custody trail and the audit
- [Financial controls](#sec-223) — plain-English spend rules and real-time wallet defense on these rails
- [Trading surfaces](#sec-420) — Mission Control executes through this same guarded path
- [The trading experiment](#sec-418) — an autonomous agent operating inside these limits, journaled
-- [x402](#sec-551) — the payment protocol these wallets spend over
+- [x402](#sec-552) — the payment protocol these wallets spend over
---
@@ -46379,7 +46380,7 @@ The browser UI for all of this lives in the dashboard:
Base URL: `https://three.ws`
Related docs: [MCP integration](#sec-281), [API reference](#sec-096),
-[Authentication](#sec-103), [x402 developer tools](#sec-544).
+[Authentication](#sec-103), [x402 developer tools](#sec-545).
---
@@ -47582,7 +47583,7 @@ CRON_SECRET=… DURATION_MINUTES=10 node scripts/economy-heartbeat.mjs
build reports `status: 404` and never stops the others.
Related: [circulation engine](#sec-141) ·
-[x402 ring economy](#sec-548) ·
+[x402 ring economy](#sec-549) ·
[economy funding root](#sec-184) · [money map](#sec-291)
---
@@ -48169,7 +48170,7 @@ of the tree the master feeds:
sponsor settle floor) and `x402-ring-payer` (`X402_SEED_SOLANA_SECRET_BASE58`,
fallback `X402_AGENT_SOLANA_SECRET_BASE58`, floor 0.03 SOL, `holdsTokens` so
sweepback leaves its USDC float alone) are topped up by this master like every
- other engine (see [x402 ring economy](#sec-548) /
+ other engine (see [x402 ring economy](#sec-549) /
[autonomous x402](#sec-105)).
## Related
@@ -48178,7 +48179,7 @@ of the tree the master feeds:
engine signer, its encoding, and how to fund/consolidate the economy wallets.
- [Circulation engine](#sec-141) — the autonomous agent-to-agent
activity loop the funded engines drive.
-- [x402 ring economy](#sec-548) — closed-loop in-house x402 settlement.
+- [x402 ring economy](#sec-549) — closed-loop in-house x402 settlement.
---
@@ -49693,8 +49694,8 @@ Embody is a thin, honest wire over pieces that already exist — no new pipeline
## Related
- [Live embodiment](#sec-278) — the 3D Studio tools that persist and drive a body in chat.
-- [x402 Paid Endpoints](#sec-546) — the full paid catalog and pricing.
-- [x402 Buyer Client](#sec-543) — how to settle a 402 challenge from code.
+- [x402 Paid Endpoints](#sec-547) — the full paid catalog and pricing.
+- [x402 Buyer Client](#sec-544) — how to settle a 402 challenge from code.
- [Avatar creation](#sec-109) — generate a rigged avatar in the web UI.
---
@@ -53205,7 +53206,7 @@ Read the published benchmark:
curl 'https://three.ws/api/fact-check-benchmark'
```
-Once the free quota is spent, the same POST returns `402` with an x402 challenge; pay it with any x402 client (for example `@three-ws/x402-fetch`) and retry. See [x402](#sec-551).
+Once the free quota is spent, the same POST returns `402` with an x402 challenge; pay it with any x402 client (for example `@three-ws/x402-fetch`) and retry. See [x402](#sec-552).
## Running the benchmark
@@ -53268,7 +53269,7 @@ Two guards keep a bad run from becoming a published number:
## Related
-- [x402: paid agent skills](#sec-551): the payment rail the $0.10 lane rides
+- [x402: paid agent skills](#sec-552): the payment rail the $0.10 lane rides
- [API reference: Fact Check API](#sec-096): the endpoint's full request and response reference
- [SAS credentialed attestations](#sec-377) and [3D provenance](#sec-340): the platform's on-chain attestation primitives (distinct from this content-hash attestation)
- Pages: [/fact-check](https://three.ws/fact-check) · [/x402](https://three.ws/x402)
@@ -53823,8 +53824,8 @@ Ranked by accounting/regulatory risk. Each is a tracked remediation item.
## Related
- [Money map](#sec-291) — who receives each payment.
-- [x402 revenue & receipts](#sec-547) — the x402 recording detail.
-- [x402 endpoints](#sec-546) — the paid endpoint catalog.
+- [x402 revenue & receipts](#sec-548) — the x402 recording detail.
+- [x402 endpoints](#sec-547) — the paid endpoint catalog.
- [Solana signers runbook](../api/_lib/solana-signers.js) — the wallets + funding.
---
@@ -54700,7 +54701,7 @@ dashboard at [/quality-bench](https://three.ws/quality-bench) (internal).
[three.ws/forged](https://three.ws/forged) is a public gallery of 3D props that
the platform's own autonomous agents bought with real USDC over the
-[x402 payment protocol](#sec-551). Nothing on the page is curated or seeded by
+[x402 payment protocol](#sec-552). Nothing on the page is curated or seeded by
hand: an agent wallet paid the Forge, the Forge generated the prop, the payment
settled on Solana mainnet, and the finished asset landed in the gallery carrying
its receipt. Every card shows the price paid, the paying agent wallet, and a
@@ -54750,7 +54751,7 @@ runs as a registry entry inside that loop, and on each run it:
is a real on-chain USDC transfer from the loop's seeder wallet, settled by
the platform's self-hosted facilitator on Solana mainnet. The same seeder
wallet is the `x402-ring-payer` signer in the
- [x402 ring economy](#sec-548), and the loop's daily spend cap
+ [x402 ring economy](#sec-549), and the loop's daily spend cap
applies to these calls like every other.
3. **Scores diversity.** The prompt is embedded (a configured provider when
available, a deterministic local feature-hash space otherwise) and scored
@@ -54828,11 +54829,11 @@ The endpoint is also listed in the [API reference](#sec-096).
- [Autonomous x402 loop](#sec-105): the engine that buys these
assets, its spend caps, and where every call is logged.
-- [x402 ring economy](#sec-548): the wider self-paid endpoint
+- [x402 ring economy](#sec-549): the wider self-paid endpoint
economy the seeder wallet participates in.
- [How the Forge works](#sec-242): the generation pipeline the
agents are paying for.
-- [x402 on three.ws](#sec-551): the payment protocol itself.
+- [x402 on three.ws](#sec-552): the payment protocol itself.
---
@@ -56846,7 +56847,7 @@ A finished model is a starting point, not a dead end:
## Agents use the exact same machinery
-Everything above is also a tool call. AI agents (Claude, ChatGPT, or your own) generate models through our [free MCP server](#sec-278) or plain HTTP, and other agents pay per call with USDC over [x402](#sec-551), no account needed. The page you use and the API an agent uses are the same pipeline underneath.
+Everything above is also a tool call. AI agents (Claude, ChatGPT, or your own) generate models through our [free MCP server](#sec-278) or plain HTTP, and other agents pay per call with USDC over [x402](#sec-552), no account needed. The page you use and the API an agent uses are the same pipeline underneath.
## Try it
@@ -57012,7 +57013,7 @@ Quick lookup for "I want to ship X":
| A character that controls a scene from page events | The JS API (`agent.say()`, `agent.ask()`) — see [js-api.md](#sec-261) |
| Programmatic avatar viewing/creation in your own app | `@three-ws/avatar` |
| An on-chain identity for your AI | [ERC-8004](#sec-190) or [Solana](#sec-399) |
-| A paid API anyone (including agents) can call | [x402 monetization](#sec-551) |
+| A paid API anyone (including agents) can call | [x402 monetization](#sec-552) |
| Multiple agents in one scene | `<agent-stage>` — see [multi-agent.md](#sec-294) |
| To register a domain (e.g. ENS) as agent identity | [register-onchain.md tutorial](#sec-468) |
@@ -57664,7 +57665,7 @@ Full recap once the day wraps.
follow-up, not a replacement for the original event post.
- **Do not post an X/Twitter version of this.** This content is for the IBM Community group only;
the group is the audience that gets the personal, honest register. The `@trythreews` and
- `@nichxbt` X copy in [event-x-posts.md](#sec-526) is a separate, distinct campaign and
+ `@nichxbt` X copy in [event-x-posts.md](#sec-527) is a separate, distinct campaign and
stays in its organizer voice.
- **Let Jessica edit freely.** This is a starting draft in her established voice (see the section
"Why I think this format is worth your hour" in her earlier blog post), not a final script.
@@ -58303,7 +58304,7 @@ This is the developer guide for the `@three-ws/ibm-x402-mcp` tool suite. For the
broader IBM integration (the platform showcase, Guardian Trust Layer, the
credentials-based `@three-ws/ibm-watsonx-mcp` connector) see **[docs/ibm.md](#sec-253)**.
For the x402 protocol primitives used elsewhere on the platform see
-**[docs/x402.md](#sec-551)**.
+**[docs/x402.md](#sec-552)**.
---
@@ -58643,7 +58644,7 @@ Catalog/listing copy is maintained in
## See also
- [docs/ibm.md](#sec-253) — the full IBM Granite / watsonx integration and showcase
-- [docs/x402.md](#sec-551) — the x402 payment protocol on three.ws
+- [docs/x402.md](#sec-552) — the x402 payment protocol on three.ws
- [docs/mcp.md](#sec-281) — wiring MCP servers into a client
- [docs/mcp-x402-bazaar.md](#sec-280) — x402 service discovery
- [packages/ibm-x402-mcp](../packages/ibm-x402-mcp) — the npm package source
@@ -59239,7 +59240,7 @@ primitives.
This is **not** the same rail as the USDC cosmetics shop for the standalone
character creator, which sells a different catalog through
-[x402](#sec-551) and is surfaced publicly at [/fits](https://three.ws/fits).
+[x402](#sec-552) and is surfaced publicly at [/fits](https://three.ws/fits).
Two catalogs, two currencies, two rails. Do not confuse them.
It is also not the only way to own a wardrobe item. A third tier exists that the
@@ -62181,7 +62182,7 @@ Ecosystem directories are the discovery surfaces that L1/L2 communities, chain f
|---|---|---|
| **BNB Chain · Dappbay** | Live | [dappbay.bnbchain.org/detail/three](https://dappbay.bnbchain.org/detail/three) — categories: *AI Agent Launchpad · AI Data · AI Infra*. Announcement: [three.ws Listed on BNB Chain's Dappbay Directory](/blog/three-ws-on-bnb-chain-dappbay.html). |
-Dappbay is BNB Chain's official dApp directory. The listing is about distribution and discovery into BNB Chain's AI dApp audience — three.ws still settles agent payments on Solana, Base, and Polygon via the chain-agnostic [x402 protocol](#sec-551).
+Dappbay is BNB Chain's official dApp directory. The listing is about distribution and discovery into BNB Chain's AI dApp audience — three.ws still settles agent payments on Solana, Base, and Polygon via the chain-agnostic [x402 protocol](#sec-552).
---
@@ -63006,7 +63007,7 @@ sales and zero exhausted trials before it was found. See
endpoints are complete, but there is not yet a free, paginated "browse all
skills for sale" HTTP endpoint with sort/filter; discovery today is per-agent
(agents themselves are browsable at `GET /api/marketplace/agents`), and the
- paid [`/api/x402/skill-marketplace`](#sec-546) endpoint returns the
+ paid [`/api/x402/skill-marketplace`](#sec-547) endpoint returns the
live skill listing catalog with pricing for $0.001 USDC.
- **Auto-grant.** A confirmed skill purchase is recorded and the license NFT is
minted, but the purchased skill is not automatically attached to the buyer's
@@ -64083,7 +64084,7 @@ CSP entry cannot drift apart.
three.ws ships several [MCP](#sec-281) servers: tool servers that AI assistants
(Claude, ChatGPT, any MCP client) can call directly. One is free and 3D-only; the
-others expose paid tools that settle per call in USDC over [x402](#sec-551). This
+others expose paid tools that settle per call in USDC over [x402](#sec-552). This
page explains how the servers are grouped and how the paid ones charge.
> **Looking for a specific tool?** The complete, always-current list lives at
@@ -64223,7 +64224,7 @@ promote no specific token.
- [MCP](#sec-281) overview · [3D Studio MCP](#sec-278) ·
[3D Studio (paid)](#sec-275) · [x402 bazaar](#sec-280)
-- [x402 paid endpoints](#sec-546) — the same capabilities over REST.
+- [x402 paid endpoints](#sec-547) — the same capabilities over REST.
- [MCP tool safety](#sec-277) - what each tool's safety annotations mean,
and the build check that verifies them against the code.
- [The full catalog](/mcp-tools) - every tool, searchable by safety and price.
@@ -64902,7 +64903,7 @@ Call any endpoint in the free [Crypto Data API](#sec-096) (the same aggregator b
}
```
-An unknown `provider`/`endpoint` pair returns an error result listing every valid pair. A registered endpoint marked free runs within the same per-IP quota the REST free lane enforces — no wallet needed. An endpoint with no free tier, or a free quota you've exhausted, returns a JSON-RPC `-32402` error naming the exact REST URL and USDC price to pay via [x402](#sec-551) — never a second, MCP-only payment flow.
+An unknown `provider`/`endpoint` pair returns an error result listing every valid pair. A registered endpoint marked free runs within the same per-IP quota the REST free lane enforces — no wallet needed. An endpoint with no free tier, or a free quota you've exhausted, returns a JSON-RPC `-32402` error naming the exact REST URL and USDC price to pay via [x402](#sec-552) — never a second, MCP-only payment flow.
```bash
# Equivalent to: GET /api/v1/x/dexscreener/token?addresses=FeMbDoX7R1Psc4GEcvJdsbNbZA3bfztcyDCatJVJpump
@@ -67135,7 +67136,7 @@ The same bus powers surfaces that are not tickers at all:
- [Circulation engine](#sec-141) — the largest producer of activity.
- [Autonomous x402 loop](#sec-105) — treasury-paid intel purchases.
- [Agent wallets](#sec-072) — how spends are gated before they're recorded.
-- [x402 revenue & receipts](#sec-547) — the *other* direction: money paid **to** our endpoints (`x402_audit_log`), not agent spend.
+- [x402 revenue & receipts](#sec-548) — the *other* direction: money paid **to** our endpoints (`x402_audit_log`), not agent spend.
---
@@ -67396,8 +67397,8 @@ wallet receives each kind of payment, what share the platform keeps, and which
treasury pays it forward. If you're adding a paid surface or auditing revenue,
start here.
-Companion docs: [x402 endpoints](#sec-546) (the paid endpoint catalog),
-[x402 revenue & receipts](#sec-547) (how settlements are recorded),
+Companion docs: [x402 endpoints](#sec-547) (the paid endpoint catalog),
+[x402 revenue & receipts](#sec-548) (how settlements are recorded),
[Solana signers runbook](../api/_lib/solana-signers.js) (the
signer/funder wallets and how to fund them).
@@ -67497,7 +67498,7 @@ unit economics.
[ring catalog](../api/_lib/x402/ring-catalog.js), the single source of truth)
across intel/oracle, agent/reputation, generation/3D, launch/naming/utility,
club, avatar shop, and bazaars. Full list and prices:
- [x402 endpoints](#sec-546).
+ [x402 endpoints](#sec-547).
- **Paid MCP tools** —
- Main MCP ([api/mcp.js](../api/mcp.js), pricing `api/_lib/pump-pricing.js`):
`mint_3d_asset` $0.25, `retexture_model` $0.10, `optimize_model` $0.05,
@@ -67570,9 +67571,9 @@ that set `auto_fund_enabled = true` (default off). See
## Related
- [Financial controls & audit register](#sec-223) — every ledger's integrity, reconciliation, retention, monitoring, and the ranked gap list.
-- [x402 endpoints](#sec-546) — the paid endpoint catalog and price overrides.
-- [x402 revenue & receipts](#sec-547) — where settlements are recorded.
-- [x402 ring economy](#sec-548) — the internal recirculation loop.
+- [x402 endpoints](#sec-547) — the paid endpoint catalog and price overrides.
+- [x402 revenue & receipts](#sec-548) — where settlements are recorded.
+- [x402 ring economy](#sec-549) — the internal recirculation loop.
- [Pump platform fee](#sec-345) — the pump trade fee detail.
- [Coin-launch wallets](#sec-502) — launch-time wallet flow.
- [Creator revenue splits](../api/_lib/cosmetics-economy.js) — `recordSaleAndSplit`: the cosmetic split math and its real USDC payout.
@@ -70013,7 +70014,7 @@ are reachable directly at the endpoints documented here rather than through the
Current listing state is tracked in [`prompts/okx-ai/PROGRESS.md`](../prompts/okx-ai/PROGRESS.md).
> Related: [REST API Reference](#sec-096) · [MCP servers](#sec-281) ·
-> [x402 payments](#sec-551) · seller-side protocol spec: [`specs/okx-agent-payments.md`](../specs/okx-agent-payments.md)
+> [x402 payments](#sec-552) · seller-side protocol spec: [`specs/okx-agent-payments.md`](../specs/okx-agent-payments.md)
The **single source of truth** for every service (names, 2-part OKX descriptions, prices,
endpoints, input schemas) is [`api/_lib/okx-catalog.js`](../api/_lib/okx-catalog.js), the
@@ -70742,7 +70743,7 @@ Before, the repo shipped a proprietary LICENSE ("All rights reserved... may not
What landed:
- [LICENSE](../LICENSE) is now the verbatim Apache-2.0 text, byte-identical to the canonical copy apart from the copyright line, verified by diff against a reference copy in the dependency tree.
-- [NOTICE](../NOTICE) records attribution for the vendored and derived code that keeps its own license: the character studio fork, the vendored three.js editor, the animation clip library, and the club assets. Every path in it was checked to exist.
+- [NOTICE](../NOTICE) records attribution for the vendored and derived code that keeps its own license: the forked avatar builder, the vendored three.js editor, the animation clip library, and the club assets. Every path in it was checked to exist.
- All **102** first-party `package.json` manifests moved from `"SEE LICENSE IN LICENSE"` to `"license": "Apache-2.0"`, each re-parsed as JSON before it was written. Vendored third-party trees were never in scope: the sweep only touched manifests carrying our own proprietary marker.
- The README License section now explains what the license actually permits instead of asserting the opposite.
@@ -70774,7 +70775,7 @@ Apache-2.0 over MIT for two reasons: CONTRIBUTING.md already promised it to ever
### Still to do
1. **Post the three seeded Discussions.** Written and ready in [contributing/discussion-seeds.md](#sec-162): a Welcome post (pin it), a Show and tell thread, and an open Roadmap thread. The workspace token has `issues: write` but not `discussions: write`, so this is 60 seconds of paste by a human. Zero threads is what reads as nobody being home; three real ones fixes it.
-2. **Trim the README's front door.** It is 401 KB. Nobody evaluating a livestream guest reads 401 KB. The first screen needs what it is, a 10-second demo GIF, and the install line. Everything else moves below the fold or into `docs/`.
+2. **The README front door is better than its file size suggests.** 8,402 of its 11,372 lines are one inline STL model that GitHub renders as an interactive 3D viewer, so a reader on github.com sees a widget, not 8,000 lines of vertex data. The prose is about 3,000 lines. The first screen now carries the license and good-first-issue badges and a contributor CTA alongside the user one. What is still worth doing is a 10-second demo GIF above the fold, since the current hero is a video attachment that does not autoplay in every context.
3. **Record a 45-second demo clip** (prompt to rigged avatar to embedded on a page). Reusable: README, the issue body, and every amplification post. Per section 5, video and images are what move GitHub's own numbers.
---
@@ -72064,7 +72065,7 @@ Per the documentation rules in `CLAUDE.md`, all of these apply and none are opti
### Phase 5: the X post
-Draft lives at [`docs/oracle-trading-mcp-x-post.md`](#sec-537). Written before
+Draft lives at [`docs/oracle-trading-mcp-x-post.md`](#sec-538). Written before
the work ships so the announcement shapes the scope rather than the reverse: if a claim in that
post is not true when the phases are done, the phases are not done.
@@ -72948,7 +72949,7 @@ The page closes with four reasons, useful as the short pitch when someone asks:
- [Press kit](#sec-338): marks, announcement graphics, boilerplate, and the rules for all of it
- [Listings and distribution](#sec-269): marketplaces, ecosystem directories, and media partners with per-listing status
- [Integrations](#sec-257): the catalog of ways to put an agent on a site you do not control
-- [x402](#sec-551): the payment rail behind the agent-to-agent micropayments every partner surface references
+- [x402](#sec-552): the payment rail behind the agent-to-agent micropayments every partner surface references
---
@@ -73553,9 +73554,9 @@ curl -s $BASE/api/credits -H "$AUTH" | jq .balance_usd
## Related
-- [x402 Protocol](#sec-551): the challenge / verify / settle mechanics behind every paid call.
-- [x402 Buyer Client](#sec-543): paying x402 endpoints from your own wallet instead of a session.
-- [x402 Developer Tools](#sec-544): free echo / debug / receipt-verification tools for debugging a paid call.
+- [x402 Protocol](#sec-552): the challenge / verify / settle mechanics behind every paid call.
+- [x402 Buyer Client](#sec-544): paying x402 endpoints from your own wallet instead of a session.
+- [x402 Developer Tools](#sec-545): free echo / debug / receipt-verification tools for debugging a paid call.
---
@@ -76518,7 +76519,7 @@ rate-limits under the ~450 txs a full run makes. Pass a dedicated `--rpc`
`POST /api/x402/pump-launch` launches a brand-new [pump.fun](https://pump.fun)
token for an autonomous agent in a single paid request. The agent needs **no
SOL, no wallet, and no three.ws account** — it pays a flat USDC fee over the
-[x402](#sec-551) rail and the platform does the rest:
+[x402](#sec-552) rail and the platform does the rest:
- fronts the ~0.022 SOL bonding-curve deploy cost from a funded launcher keypair,
- optionally grinds a **vanity mint address**,
@@ -76610,7 +76611,7 @@ curl -X POST https://three.ws/api/x402/pump-launch \
curl "https://three.ws/api/crypto/launches"
```
-See [x402 buyer client](#sec-543) for how to satisfy the 402 challenge in
+See [x402 buyer client](#sec-544) for how to satisfy the 402 challenge in
code.
## Output
@@ -76660,12 +76661,12 @@ token itself always deploys on **Solana mainnet** — pump.fun is mainnet-only.
## Related
-- [x402 paid endpoints](#sec-546) — the full catalog and pricing.
+- [x402 paid endpoints](#sec-547) — the full catalog and pricing.
- [Crypto Data API](#sec-180) — the free `symbol` and `launches`
endpoints that bookend a launch.
- [Repo → Coin Launcher](#sec-343) — the batch/CLI launcher that
routes 100% of creator rewards to a GitHub identity (shares the same engine).
-- [x402 protocol](#sec-551) — challenge/settle mechanics.
+- [x402 protocol](#sec-552) — challenge/settle mechanics.
---
@@ -81406,7 +81407,7 @@ math; Chainlink feed prices are already multiplier-adjusted, so they're never re
service-catalog descriptor) applied to the rest of three.ws's market data.
- [Trust primitives](#sec-423) — score a Robinhood Chain wallet's cross-chain
reputation before transacting with it.
-- [x402 distribution](#sec-545) — how the paid portfolio endpoint gets discovered
+- [x402 distribution](#sec-546) — how the paid portfolio endpoint gets discovered
across the x402 ecosystem.
---
@@ -83936,7 +83937,7 @@ curl -s https://three.ws/api/signals/subscribe -H 'authorization: Bearer YOUR_TO
- [Custody you can verify](#sec-172) - the spend caps, freeze, and audit trail the subscriber wallet pays and trades under
- [Financial controls](#sec-223) - the plain-English rules and firewall the mirror respects
- [Oracle](#sec-320) - the conviction engine and its own follow/copy tier
-- [x402](#sec-551) - the USDC payment protocol every signal settles over
+- [x402](#sec-552) - the USDC payment protocol every signal settles over
- [Trader card](#sec-414) - the verified track record that regresses a feed's edge
- [/leaderboard](https://three.ws/leaderboard) - build a verified record, then publish a feed of your own
@@ -84725,7 +84726,7 @@ whose pending balance clears $0.01, so nobody pays gas to move dust.
## Related
- [Skills marketplace](#sec-392): publishing, pricing, and installing skills
-- [x402 endpoints](#sec-546): every paid endpoint and who each one pays
+- [x402 endpoints](#sec-547): every paid endpoint and who each one pays
- [Money map](#sec-291): how value moves across the whole platform
- [Remix royalties](#sec-370): the parallel royalty rail for 3D creations
@@ -87936,8 +87937,8 @@ Curious what happens between the prompt and the model? [How the Forge works](#se
- **Publishing news, or wondering what we show of yours?** → [Publisher rights in the news reader](#sec-296) — three.ws quotes a capped lead excerpt and links out, never the article body; covers the enforced limits, how a withdrawn story is removed (410 + deindex + purge), and how to ask us to take something down
- **Your agent needs market data?** → [Market Data API](#sec-273) — the live feeds behind every /markets page (prices, TVL, yields, stablecoins, gas, derivatives, exploits) as 17 pay-per-call x402 endpoints from $0.001 USDC, plus the one-call `market-pulse` bundle; start at the free index [/api/x402/market](https://three.ws/api/x402/market)
- **Trading Robinhood Chain?** → [Robinhood Chain on three.ws](#sec-376) — the 24/7 tokenized-equity board (live Chainlink NAV vs. DEX premium), a memecoin screener, and a real wallet-connect buy flow at [/markets/robinhood](https://three.ws/markets/robinhood), backed by 6 free + 1 paid `/api/v1/robinhood/*` endpoints
-- **Listing our services across the x402 ecosystem?** → [x402 distribution](#sec-545) — the operating playbook for x402scan, the CDP Bazaar, agentic.market, 402index, and every other directory: how each one indexes providers, what ranks us (settled tx + distinct buyers, trailing 30 days), what's automated, and what needs a human
-- **Debugging an x402 integration?** → [x402 developer tools](#sec-544) — a free test bench: echo your payment envelope (signatures redacted), debug a failed 402 exchange into an ordered fix list, and verify a receipt's attestation and on-chain settlement, all against a live server without spending anything
+- **Listing our services across the x402 ecosystem?** → [x402 distribution](#sec-546) — the operating playbook for x402scan, the CDP Bazaar, agentic.market, 402index, and every other directory: how each one indexes providers, what ranks us (settled tx + distinct buyers, trailing 30 days), what's automated, and what needs a human
+- **Debugging an x402 integration?** → [x402 developer tools](#sec-545) — a free test bench: echo your payment envelope (signatures redacted), debug a failed 402 exchange into an ordered fix list, and verify a receipt's attestation and on-chain settlement, all against a live server without spending anything
- **Paying from the BNB ecosystem?** → [BNB Chain payments](#sec-127) — three.ws speaks MPP (BNB's Machine Payments Protocol) as well as x402, so agents can pay our endpoints on BNB Chain and our agents can pay theirs; covers the buyer/seller flow, the x402↔MPP bridge spec, and MegaFuel gasless (zero-gas) sends with an honest self-pay fallback
- **Walking in real time, on-chain?** → [The on-chain world](#sec-129) — `/agora`'s Play mode has an opt-in toggle that commits your walk to a real BNB Chain contract at its live ~0.45s block cadence, gaslessly, and renders every other on-chain player as a live ghost marker; covers why this only works on BNB Chain, the architecture, and a reproducible two-wallet proof
- **Buying an encrypted 3D model?** → [The vault](#sec-128) — `/vault` sells access to encrypted 3D models gated by a real BSC purchase that triggers a real cross-chain Greenfield permission grant; covers the buyer flow (browse, buy, settle, unlock, view — all decrypted client-side), the local session-key wallet model, and a reproducible anvil-fork browser proof
@@ -88011,7 +88012,7 @@ Deeper references that don't fit a track above but answer real questions:
- [Demo routes](#sec-175): the canonical map of every `/demo/*` and `/demos/*` route
- [Agent trading spec](#sec-401): the proposed agent trading capability contract
- [ERC-8004 validation attestation](#sec-191): the attestation written when an agent registers on-chain
-- [zauth](#sec-553): the vendored security infrastructure docs our agent auth builds on
+- [zauth](#sec-554): the vendored security infrastructure docs our agent auth builds on
- [Agent tokens](#sec-070): configure the coin an agent will become, rehearse the launch for free against a real cluster, then launch it on Solana
- [pump.fun program docs](#sec-346): the vendored on-chain program reference behind the launch surfaces
- [pump-fun-mcp at the edge](#sec-342): the Cloudflare Workers mirror of the pump.fun MCP endpoint
@@ -88032,7 +88033,7 @@ Deeper references that don't fit a track above but answer real questions:
- [Guardian console](#sec-239): the inbox for the other side of social recovery and inheritance of agent wallets
- [Coin Clash](#sec-142): token-gated community battles between coin factions
- [Daily Forge](#sec-173): a new deterministic 3D creative challenge every day
-- [x402 Studio](#sec-550): the merchant console for running a paid x402 business on three.ws
+- [x402 Studio](#sec-551): the merchant console for running a paid x402 business on three.ws
- [Contributing](#sec-161): local environment setup through a mergeable pull request
- [ERC-8004 smart contracts](#sec-393): contract interfaces, deployed addresses, and how to read and write each registry
- [Internationalization](#sec-244): how the UI translation catalog works and how to add a locale
@@ -88846,7 +88847,7 @@ The response reports `fired`, `paid`, `buys`, `pending`, `errors`, `toll_spent_u
## Related
-- [docs/x402-ring-economy.md](#sec-548) — the closed-loop x402 ring the toll settles through.
+- [docs/x402-ring-economy.md](#sec-549) — the closed-loop x402 ring the toll settles through.
- [api/_lib/token/buyback.js](../api/_lib/token/buyback.js) — the daily buyback lane.
- [api/_lib/token/config.js](../api/_lib/token/config.js) — `$THREE` mint, treasury, and split policy.
@@ -90319,7 +90320,7 @@ curl 'https://three.ws/api/trades/feed'
curl 'https://three.ws/api/oracle/batch?mints=<MINT1>,<MINT2>&network=mainnet'
```
-Agents wanting the same intel over MCP: see [docs/mcp.md](#sec-281) (`@three-ws/intel-mcp`, `@three-ws/portfolio-mcp`) — and the paid x402 lanes in [x402-endpoints](#sec-546).
+Agents wanting the same intel over MCP: see [docs/mcp.md](#sec-281) (`@three-ws/intel-mcp`, `@three-ws/portfolio-mcp`) — and the paid x402 lanes in [x402-endpoints](#sec-547).
## Related
@@ -91084,7 +91085,7 @@ any chain**, regardless of which platform that counterparty was minted on.
## Cross-chain Agent Reputation
**`GET /api/x402/agent-reputation?subject=<identifier>`** — $0.01 USDC per call
-(Base or Solana mainnet, via [x402](#sec-551)).
+(Base or Solana mainnet, via [x402](#sec-552)).
Pass any counterparty identifier. The type is auto-detected and scored from whatever
real on-chain evidence exists for it:
@@ -91202,7 +91203,7 @@ Returns `{ mode, count, scored_count, unknown_count, avg_score, subjects: [ …f
The same POST route also serves three.ws-fleet monitoring over the platform's indexed
active-agent set: `mode: "sweep"` (fleet average + flagged low-trust agents),
`mode: "leaderboard"` (top N by score), and `mode: "decay_report"` (agents whose score
-dropped >10 points). See the [x402 catalog](#sec-551).
+dropped >10 points). See the [x402 catalog](#sec-552).
---
@@ -91227,7 +91228,7 @@ claims **"I am the deployer of contract X"** or **"I own wallet W / name N / age
self-report.
**`GET /api/x402/onchain-identity-verify?identity=<id>&address=<addr>&chain=<caip2>`**
-— $0.005 USDC per call (Base or Solana mainnet, via [x402](#sec-551)).
+— $0.005 USDC per call (Base or Solana mainnet, via [x402](#sec-552)).
It verifies a **claim** that `identity` controls `address`, for **any** identity type,
on any chain — regardless of the platform the counterparty came from:
@@ -91301,7 +91302,7 @@ score *whether to trust* them.
---
-See also: [x402 paid endpoints](#sec-551) · [Agent Bouncer](#sec-096) · [ERC-8004 identity](#sec-190)
+See also: [x402 paid endpoints](#sec-552) · [Agent Bouncer](#sec-096) · [ERC-8004 identity](#sec-190)
---
@@ -116906,7 +116907,7 @@ The toggle's CSS class reflects the highest severity: `level-0` (errors), `level
Three x402 endpoints that hand an agent a **branded Solana address** — one that
starts with your ticker/prefix and/or ends with a chosen suffix — with no wallet,
-no account, and no SOL. Pay per call in USDC over the [x402](#sec-551) rail and the
+no account, and no SOL. Pay per call in USDC over the [x402](#sec-552) rail and the
server grinds (or delivers from stock) a brand-new keypair that matches.
| Endpoint | What it is | Chars | Price | Pick it when |
@@ -117141,7 +117142,7 @@ challenges and the discovery doc stay in parity.
## Related
-- [x402 endpoints overview](#sec-546)
+- [x402 endpoints overview](#sec-547)
- [three-vanity/v1 protocol spec](#sec-005)
- [Pump Launcher](#sec-344) — accepts an optional vanity mint prefix/suffix
- Web grinder + verifier: [`/vanity-wallet`](https://three.ws/vanity-wallet), [`/vanity/verify`](https://three.ws/vanity/verify)
@@ -117649,7 +117650,7 @@ appears only when there is something to show, pointing at the filtered
- [The autonomous economy](#sec-104): the wallets, spend policies,
paid skills, and trading loops whose real activity this page measures.
-- [x402 revenue and receipts](#sec-547): the platform's own endpoint
+- [x402 revenue and receipts](#sec-548): the platform's own endpoint
revenue, recorded in a different table and never mixed into the marketplace or
trading figures here.
- [Agent Economy Volume](#sec-052): the agent-to-agent USDC
@@ -122174,36 +122175,37 @@ explicit approval). Each file states what it's for and what has already been ver
| File | What it announces |
| --- | --- |
-| [`onchain-agent-wallets-x-post.md`](#sec-536) | Agent wallets with an on-chain spending allowance instead of a private key: SPL Token delegation, guardrails, x402, revocable custody |
-| [`mcp-registry-fleet-x-post.md`](#sec-529) | The fleet as a whole: 72 MCP servers under one namespace in the official registry, all current |
-| [`metaplex-agent-mcp-launch.md`](#sec-532) | The open-source agent infrastructure announcement covering `@three-ws/metaplex-agent-mcp` and `@three-ws/onchain-agent-wallets`, and why the integrations are bullish for $THREE |
-| [`metaplex-agent-mcp-x-post.md`](#sec-534) | The MCP server that mints an agent into the Metaplex Agent Registry with its own wallet and EIP-8004 identity |
-| [`metaplex-agent-deployer-x-post.md`](#sec-531) | The browser deployer at nirholas.github.io/metaplex-agent-mcp |
+| [`onchain-agent-wallets-x-post.md`](#sec-537) | Agent wallets with an on-chain spending allowance instead of a private key: SPL Token delegation, guardrails, x402, revocable custody |
+| [`mcp-registry-fleet-x-post.md`](#sec-530) | The fleet as a whole: 72 MCP servers under one namespace in the official registry, all current |
+| [`metaplex-agent-mcp-launch.md`](#sec-533) | The open-source agent infrastructure announcement covering `@three-ws/metaplex-agent-mcp` and `@three-ws/onchain-agent-wallets`, and why the integrations are bullish for $THREE |
+| [`metaplex-agent-mcp-x-post.md`](#sec-535) | The MCP server that mints an agent into the Metaplex Agent Registry with its own wallet and EIP-8004 identity |
+| [`metaplex-agent-deployer-x-post.md`](#sec-532) | The browser deployer at nirholas.github.io/metaplex-agent-mcp |
| [`3d-ar-studio-launch.md`](#sec-522) | 3D AR Studio, the AR studio extracted from three.ws and published as an open-source package |
| [`ar-quick-look-fix-x-post.md`](#sec-525) | AR Forge and AR Studio now open real Apple Quick Look / Google Scene Viewer on a phone, matching what `/avatars/:id/ar` already did. Shipped to `main` locally, **not yet deployed**: do not post until verified live on a real iPhone |
-| [`threews-avatar-launch.md`](#sec-540) | The three.ws avatar pipeline launch copy |
-| [`oracle-trading-mcp-x-post.md`](#sec-537) | The oracle trading MCP server launch |
-| [`sperax-staking-in-chat-x-post.md`](#sec-539) | SperaxOS chat-native staking, balance, and buy-SPA tool calls. The embedded `/staking` page is not working yet: do not announce until the blockers in the file clear |
-| [`news-archive-x-post.md`](#sec-535) | The news archive |
-| [`pumpfun-article-x-post.md`](#sec-538) | The pump.fun article |
+| [`threews-avatar-launch.md`](#sec-541) | The three.ws avatar pipeline launch copy |
+| [`oracle-trading-mcp-x-post.md`](#sec-538) | The oracle trading MCP server launch |
+| [`sperax-staking-in-chat-x-post.md`](#sec-540) | SperaxOS chat-native staking, balance, and buy-SPA tool calls. The embedded `/staking` page is not working yet: do not announce until the blockers in the file clear |
+| [`news-archive-x-post.md`](#sec-536) | The news archive |
+| [`pumpfun-article-x-post.md`](#sec-539) | The pump.fun article |
## Video and narration scripts
| File | What it covers |
| --- | --- |
-| [`metaplex-agent-mcp-veo-script.md`](#sec-533) | Shot-by-shot Veo (image-to-video) prompts for the agent infrastructure clip, built from a three.ws 3D avatar as the reference frame |
-| [`metaplex-agent-deployer-video-script.md`](#sec-530) | Spoken narration for the deployer clip |
-| [`threews-avatar-video-script.md`](#sec-541) | Shot list for the avatar clip |
+| [`metaplex-agent-mcp-veo-script.md`](#sec-534) | Shot-by-shot Veo (image-to-video) prompts for the agent infrastructure clip, built from a three.ws 3D avatar as the reference frame |
+| [`metaplex-agent-deployer-video-script.md`](#sec-531) | Spoken narration for the deployer clip |
+| [`threews-avatar-video-script.md`](#sec-542) | Shot list for the avatar clip |
| [`3d-ar-studio-video-script.md`](#sec-523) | Narration and shot prompts for the AR Studio launch video |
## Events and community
| File | What it covers |
| --- | --- |
-| [`event-x-posts.md`](#sec-526) | Event campaign copy, split by account (`@trythreews` institutional, `@nichxbt` personal) |
-| [`x-meetup-posts.md`](#sec-542) | The in-platform community meetup announcement |
-| [`ibm-skillsbuild-x-post.md`](#sec-528) | The IBM SkillsBuild badge |
-| [`fomo-verified-x-post.md`](#sec-527) | FOMO verification |
+| [`event-x-posts.md`](#sec-527) | Event campaign copy, split by account (`@trythreews` institutional, `@nichxbt` personal) |
+| [`x-meetup-posts.md`](#sec-543) | The in-platform community meetup announcement |
+| [`ibm-skillsbuild-x-post.md`](#sec-529) | The IBM SkillsBuild badge |
+| [`coinbase-listing-thank-you-reply.md`](#sec-526) | The long thank-you reply for the Coinbase listing moment: credit to Jesse Pollak and Base for x402, the ERC-8004 contracts we build on, and every three.ws partner |
+| [`fomo-verified-x-post.md`](#sec-528) | FOMO verification |
## Conventions
@@ -122227,7 +122229,7 @@ entry is dead once the file is no longer routed.
Announcement copy for a bug fix, not a new feature: `three.ws/ar` (AR Forge) and `three.ws/ar/studio`
(AR Studio) now place a model in your real room on iPhone the way `three.ws/avatars/:id/ar` already
-did. Related file: [threews-avatar-launch.md](#sec-540) sells the avatar-has-a-body
+did. Related file: [threews-avatar-launch.md](#sec-541) sells the avatar-has-a-body
story; this one sells "AR here means AR, on every phone, not just some of them."
**Thesis of this announcement:** every AR surface on the site now runs real ARKit Quick Look on
@@ -122310,7 +122312,7 @@ the resolution of a problem, and "watch it look real" is a dare to try it, not a
### From @nichxbt (the human one, quote-tweeting the @trythreews post above)
-Same two-account split as [event-x-posts.md](#sec-526): `@trythreews` posts the
+Same two-account split as [event-x-posts.md](#sec-527): `@trythreews` posts the
institutional version above, `@nichxbt` quote-tweets it with the human one a few minutes later, not
simultaneously. Her post is pure enthusiasm, first person, no bug talk.
@@ -122446,6 +122448,148 @@ what three.ws does well rather than dwelling on the fix.
<a id="sec-526"></a>
+> **Source:** `docs/x-posts/coinbase-listing-thank-you-reply.md` · [↑ table of contents](#table-of-contents)
+
+# Thank-you reply: the Coinbase listing moment
+
+Reply copy for **@nichxbt** under [the listing post](https://x.com/nichxbt) that
+[@jessepollak](https://x.com/jessepollak) answered with "huge congrats!!!!" on 2026-08-21.
+
+**Tone:** sincere, warm, confident. Not a joke, not a flex, not a price post. This is a
+thank-you to a builder from a builder, and the only currency in it is credit.
+
+**Verified true today:** $THREE lives on Solana at
+`FeMbDoX7R1Psc4GEcvJdsbNbZA3bfztcyDCatJVJpump`; three.ws settles real x402 micropayments in
+USDC on Solana and Base, on a loop that runs every minute with real on-chain settlement and no
+mocks ([`docs/autonomous-x402.md`](#sec-105)); agent identity is registered against
+the ERC-8004 registries on Base mainnet (chain 8453), where a registration costs roughly
+$0.10 to $0.25 in gas ([`docs/erc8004.md`](#sec-190), [`docs/smart-contracts.md`](#sec-393));
+the partner ecosystem at [three.ws/partners](https://three.ws/partners) covers OpenAI, IBM, AWS,
+Google Cloud, Alibaba Cloud, NVIDIA, Quicknode, and HackerNoon.
+
+**Do not claim:** a negotiated or centralized Coinbase listing agreement, any Coinbase
+partnership, any endorsement by Jesse Pollak or the Base team, any price or market-cap number,
+or that buybacks are executing. Jesse's own post is the source: every token on Base and Solana
+is now surfaced in the main Coinbase app. Thank the change, never inflate it.
+
+**Format:** this is a long-form reply and it is well past 280 characters, so it posts from the
+Premium account. If it has to fit the free limit, use the short version at the bottom.
+
+---
+
+## The reply (post this)
+
+> Thank you, Jesse. Truly.
+>
+> I have been building long enough to know what a reply like that is worth on a day like this,
+> and it is worth more than the listing. You did not have to say anything. You said something
+> anyway, and you said it first, and you said it with real warmth. That is the part I will
+> remember when the chart has done whatever the chart is going to do.
+>
+> So let me say thank you properly, because a two-word reply does not cover it.
+>
+> Thank you for building. Not announcing, not positioning, not reserving the right to build
+> later. Building. Base did not arrive as a promise, it arrived as a chain people could ship on
+> the same afternoon they heard about it, with gas cheap enough that a single person with an
+> idea and no funding could put something real on it. That decision has quietly paid for
+> thousands of experiments that would never have survived a mainnet gas bill. Ours is one of
+> them.
+>
+> Thank you for innovating out loud. Killing the centralized listing process is not a feature
+> release, it is a statement about who the market is for. For years the honest answer to a small
+> team asking "how do we get listed" was: know someone, wait, hope. Today the answer is: ship
+> something worth holding and the door is already open. You turned a gate into a road. Every
+> founder who is currently building in a bedroom at 2am with no contacts and no budget just got
+> handed the same distribution as everyone else, and most of them do not even know it yet. They
+> will.
+>
+> Thank you for x402. This one is personal for us. three.ws is not a token with an app attached,
+> it is an economy of AI agents that pay each other, and payment was the hard part for years.
+> Agents could think, they could call tools, they could hold a wallet, but they could not
+> transact in the one motion the web already understands: a request, a 402, a signature, a
+> settlement, a response. x402 gave that back to HTTP. Our agents now settle real USDC per call,
+> on Solana and on Base, on a loop that runs every single minute of every single day, with
+> receipts, spend caps, and no simulation anywhere in the path. When an agent on our platform
+> buys market intel, it actually pays for it. When someone builds a service on us, other agents
+> can actually buy it. That is not a demo. That is a working market, and the standard underneath
+> it came from your side of the table.
+>
+> Thank you for the contracts we build on. Our agent identity lives on Base at the ERC-8004
+> registries, which means an agent created on three.ws is not a row in our database, it is a
+> public, verifiable, portable identity that outlives us. Anyone can resolve it. Anyone can check
+> who owns it. Anyone can read its reputation without asking our permission or trusting our
+> uptime. Registration costs a couple of dimes and confirms in a couple of seconds. Ten years of
+> crypto infrastructure had to work for that sentence to be boring, and on Base it is boring,
+> which is the highest compliment infrastructure can receive.
+>
+> And thank you to Coinbase. Not for the listing itself, for the philosophy behind it. Choosing
+> to surface what the market chose instead of what a committee approved is a hard call to make
+> when you are the biggest venue in the room, and it gives up real gatekeeping power on purpose.
+> That is the kind of decision that only makes sense if you actually believe the open version
+> wins. We believe it too. It is why every line of three.ws is Apache-2.0 and why our SDKs, our
+> MCP servers, and our agent stack are public for anyone to fork, including our competitors.
+>
+> To our partners: OpenAI, IBM, AWS, Google Cloud, Alibaba Cloud, NVIDIA, Quicknode, HackerNoon.
+> Thank you for taking a small team seriously before there was any reason to. Every one of you
+> said yes at a stage where saying no would have been the safe, defensible, completely reasonable
+> answer. You gave us compute, distribution, review, credibility, and in more than one case a
+> direct line to an engineer who fixed our problem on a weekend. None of that shows up in a
+> ticker. All of it shows up in the product.
+>
+> To the $THREE holders, and I mean the ones who were here months ago when there was nothing to
+> look at but a roadmap and a promise: you funded this. Not abstractly. Literally. You held
+> through quiet weeks that would have broken a less patient community, and you kept showing up in
+> the channel asking good questions instead of asking when. Whatever this becomes, you were early
+> in the only sense that ever mattered, which is that you were early on purpose.
+>
+> Here is what I want to say to anyone else reading this who is building something and wondering
+> whether it is worth it.
+>
+> It is worth it. The infrastructure you needed five years ago exists now. Blockspace is cheap.
+> Identity is standardized. Payments are a header. Distribution is no longer a phone call you are
+> not connected enough to make. Every excuse that used to be legitimate has been systematically
+> dismantled by people who chose to make the ladder public instead of pulling it up behind them.
+> All that is left is the work, and the work has always been the fun part.
+>
+> We are going to keep our head down and earn this. More agents, more open source, more of the
+> economy wired end to end, and every bit of it shipped in public where you can check it. The
+> listing is not the finish line and it was never the goal. It is a bigger room. We intend to
+> deserve it.
+>
+> Thank you, genuinely, from all of us at three.ws.
+>
+> Now back to building.
+
+---
+
+## Short version (fits the 280-character limit)
+
+*(274 characters, no links)*
+
+> Thank you, Jesse. You did not have to reply and you did, first and warmly.
+>
+> Thank you for building Base, for x402, and for making listing something you earn by shipping
+> instead of by knowing someone. Our agents settle real USDC every minute because of it.
+>
+> Back to building.
+
+---
+
+## Notes for the poster
+
+- Post it as a **reply to Jesse's reply**, not as a new post. The warmth only reads correctly in
+ the thread where the thanks was earned.
+- Do not add a link. A link turns a thank-you into a marketing post and the timeline can tell the
+ difference instantly.
+- Do not quote-tweet your own announcement to attach this. Reply in place.
+- If it needs trimming for reach, cut whole paragraphs from the middle rather than shortening
+ every paragraph. The open, the x402 paragraph, the partners paragraph, the holders paragraph,
+ and the close are the load-bearing ones.
+
+---
+
+<a id="sec-527"></a>
+
> **Source:** `docs/x-posts/event-x-posts.md` · [↑ table of contents](#table-of-contents)
# X posts: Three.ws User Group first in-world meetup (IBM Community)
@@ -122758,7 +122902,7 @@ Practical notes for reused footage:
---
-<a id="sec-527"></a>
+<a id="sec-528"></a>
> **Source:** `docs/x-posts/fomo-verified-x-post.md` · [↑ table of contents](#table-of-contents)
@@ -122852,7 +122996,7 @@ Shorter alternate:
---
-<a id="sec-528"></a>
+<a id="sec-529"></a>
> **Source:** `docs/x-posts/ibm-skillsbuild-x-post.md` · [↑ table of contents](#table-of-contents)
@@ -123060,7 +123204,7 @@ https://www.credly.com/badges/b7ea921a-ce3d-4f4d-bfac-38f95276d361/twitter via @
---
-<a id="sec-529"></a>
+<a id="sec-530"></a>
> **Source:** `docs/x-posts/mcp-registry-fleet-x-post.md` · [↑ table of contents](#table-of-contents)
@@ -123177,14 +123321,14 @@ Post 1 is the main post. Then:
---
-<a id="sec-530"></a>
+<a id="sec-531"></a>
> **Source:** `docs/x-posts/metaplex-agent-deployer-video-script.md` · [↑ table of contents](#table-of-contents)
# Spoken script: the agent deployer video
The words only. Visual prompts, camera, and palette live in
-[metaplex-agent-mcp-x-post.md](#sec-534); this file is what gets said, cut
+[metaplex-agent-mcp-x-post.md](#sec-535); this file is what gets said, cut
into the 8-second beats Veo generates so each line lands inside one clip.
**Pacing rule:** 8 seconds of natural speech is 18 to 22 words at the absolute ceiling, and 12 to 16
@@ -123284,7 +123428,7 @@ For a single generation with no editing. One breath, one idea.
---
-<a id="sec-531"></a>
+<a id="sec-532"></a>
> **Source:** `docs/x-posts/metaplex-agent-deployer-x-post.md` · [↑ table of contents](#table-of-contents)
@@ -123522,7 +123666,7 @@ our own product, no pretending to be a bystander.
---
-<a id="sec-532"></a>
+<a id="sec-533"></a>
> **Source:** `docs/x-posts/metaplex-agent-mcp-launch.md` · [↑ table of contents](#table-of-contents)
@@ -123725,14 +123869,14 @@ fund them, which is already the safe, verified claim.
---
-<a id="sec-533"></a>
+<a id="sec-534"></a>
> **Source:** `docs/x-posts/metaplex-agent-mcp-veo-script.md` · [↑ table of contents](#table-of-contents)
# Veo script: the open-source stack
Shot-by-shot **visual** prompts for a Veo image-to-video clip to run alongside
-[`metaplex-agent-mcp-launch.md`](#sec-532). Text-to-video only, no dialogue, no
+[`metaplex-agent-mcp-launch.md`](#sec-533). Text-to-video only, no dialogue, no
voiceover: the reference frame is a three.ws 3D avatar, and every prompt below is written to be
pasted straight into Veo as-is.
@@ -123836,7 +123980,7 @@ to show something spreading to others, not just one agent getting a wallet.
---
-<a id="sec-534"></a>
+<a id="sec-535"></a>
> **Source:** `docs/x-posts/metaplex-agent-mcp-x-post.md` · [↑ table of contents](#table-of-contents)
@@ -124113,7 +124257,7 @@ keys, your limits.**
---
-<a id="sec-535"></a>
+<a id="sec-536"></a>
> **Source:** `docs/x-posts/news-archive-x-post.md` · [↑ table of contents](#table-of-contents)
@@ -124207,7 +124351,7 @@ mirror, archive search, and the agent knowledge corpus. See [docs/news-rights.md
---
-<a id="sec-536"></a>
+<a id="sec-537"></a>
> **Source:** `docs/x-posts/onchain-agent-wallets-x-post.md` · [↑ table of contents](#table-of-contents)
@@ -124393,7 +124537,7 @@ Post 1 is the main post above. Then:
---
-<a id="sec-537"></a>
+<a id="sec-538"></a>
> **Source:** `docs/x-posts/oracle-trading-mcp-x-post.md` · [↑ table of contents](#table-of-contents)
@@ -124534,7 +124678,7 @@ place to be wrong.
---
-<a id="sec-538"></a>
+<a id="sec-539"></a>
> **Source:** `docs/x-posts/pumpfun-article-x-post.md` · [↑ table of contents](#table-of-contents)
@@ -124651,7 +124795,7 @@ Pick one option. Do not post all four.
---
-<a id="sec-539"></a>
+<a id="sec-540"></a>
> **Source:** `docs/x-posts/sperax-staking-in-chat-x-post.md` · [↑ table of contents](#table-of-contents)
@@ -124757,14 +124901,14 @@ on the `/staking` page footer, so anyone who tries it gets exactly what the post
---
-<a id="sec-540"></a>
+<a id="sec-541"></a>
> **Source:** `docs/x-posts/threews-avatar-launch.md` · [↑ table of contents](#table-of-contents)
# Give your AI a body: the avatar film
X copy for the platform film. The shot prompts that produce the video live in
-[threews-avatar-video-script.md](#sec-541).
+[threews-avatar-video-script.md](#sec-542).
**Thesis:** the tagline, literally. A model with no form gets one, the form moves, the form holds
its own wallet, the form walks out into the real world. Nothing about supply, price, or buybacks.
@@ -124914,7 +125058,7 @@ Carries the part that does not fit the main post without spending its outbound l
---
-<a id="sec-541"></a>
+<a id="sec-542"></a>
> **Source:** `docs/x-posts/threews-avatar-video-script.md` · [↑ table of contents](#table-of-contents)
@@ -124922,9 +125066,9 @@ Carries the part that does not fit the main post without spending its outbound l
Prompts for a video model (Veo, run through ElevenLabs), using a three.ws 3D avatar render as the
reference image. This file is the **picture**, not the words. The X copy it ships with is in
-[threews-avatar-launch.md](#sec-540), the spoken lines live in
-[metaplex-agent-deployer-video-script.md](#sec-530), and the
-deployer-specific shot list lives in [metaplex-agent-mcp-x-post.md](#sec-534).
+[threews-avatar-launch.md](#sec-541), the spoken lines live in
+[metaplex-agent-deployer-video-script.md](#sec-531), and the
+deployer-specific shot list lives in [metaplex-agent-mcp-x-post.md](#sec-535).
The idea being sold here is the tagline and nothing else: **give your AI a body.** A model with no
form gets one, the form moves, the form owns a wallet, the form walks out into the real world. Four
@@ -125067,7 +125211,7 @@ Keep the pause after "It has no body." That silence is the whole premise.
---
-<a id="sec-542"></a>
+<a id="sec-543"></a>
> **Source:** `docs/x-posts/x-meetup-posts.md` · [↑ table of contents](#table-of-contents)
@@ -125124,13 +125268,13 @@ https://community.ibm.com/community/user/discussion/community-meetup-inside-thre
---
-<a id="sec-543"></a>
+<a id="sec-544"></a>
> **Source:** `docs/x402-buyer.md` · [↑ table of contents](#table-of-contents)
# x402 Buyer Client
-To consume a paid [x402 endpoint](#sec-546) — ours or anyone's — a
+To consume a paid [x402 endpoint](#sec-547) — ours or anyone's — a
caller has to perform the "402 dance": probe the URL, read the payment challenge,
sign and settle a payment, then retry with an `X-PAYMENT` header. three.ws ships a
buyer client that wraps that whole sequence in one call, with spending-cap
@@ -125220,13 +125364,13 @@ set) back into the payment so attribution survives the round trip.
## Related
-- [x402 protocol](#sec-551) — the underlying challenge/settle mechanics.
-- [x402 paid endpoints](#sec-546) — what you can buy from us.
+- [x402 protocol](#sec-552) — the underlying challenge/settle mechanics.
+- [x402 paid endpoints](#sec-547) — what you can buy from us.
- [Autonomous x402 loop](#sec-105) — uses this client on a schedule.
---
-<a id="sec-544"></a>
+<a id="sec-545"></a>
> **Source:** `docs/x402-dev-tools.md` · [↑ table of contents](#table-of-contents)
@@ -125438,13 +125582,13 @@ implementation against a live server.
---
-<a id="sec-545"></a>
+<a id="sec-546"></a>
> **Source:** `docs/x402-distribution.md` · [↑ table of contents](#table-of-contents)
# x402 Distribution — getting listed and ranked everywhere
-three.ws sells 90+ pay-per-call services over [x402](#sec-551). Building them is
+three.ws sells 90+ pay-per-call services over [x402](#sec-552). Building them is
half the job; the other half is making sure every x402 directory, crawler, and
agent marketplace can find them — and ranks us at the top. This page is the
operating playbook for that distribution: how each surface indexes providers,
@@ -125659,24 +125803,24 @@ script. Everything else above updates itself.
## Related
-- [x402 overview](#sec-551) · [Paid endpoints reference](#sec-546) ·
- [Autonomous loop](#sec-105) · [Buyer client](#sec-543)
+- [x402 overview](#sec-552) · [Paid endpoints reference](#sec-547) ·
+ [Autonomous loop](#sec-105) · [Buyer client](#sec-544)
---
-<a id="sec-546"></a>
+<a id="sec-547"></a>
> **Source:** `docs/x402-endpoints.md` · [↑ table of contents](#table-of-contents)
# x402 Paid Endpoints
three.ws exposes a catalog of HTTP endpoints that charge per call over
-[x402](#sec-551): the caller hits the endpoint, receives a `402 Payment Required`
+[x402](#sec-552): the caller hits the endpoint, receives a `402 Payment Required`
challenge, settles a small USDC payment, and retries with an `X-PAYMENT` header to
get the result. This page is the reference for **our own** paid endpoints, their
prices, and the price-override scheme.
-To call these as a buyer, see [x402 buyer client](#sec-543). For the loop
+To call these as a buyer, see [x402 buyer client](#sec-544). For the loop
that calls many of them on a schedule, see [Autonomous x402 loop](#sec-105).
> Source: handlers under [`api/x402/`](../api/x402), pricing
@@ -125928,7 +126072,7 @@ directory.
| Endpoint | Default | Returns |
| ---------------------------------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `/api/x402/analytics` | $0.005 | Platform reports — pick `report=revenue` for the x402 endpoint-revenue summary (see [x402 revenue & receipts](#sec-547)), plus club and listing analytics. |
+| `/api/x402/analytics` | $0.005 | Platform reports — pick `report=revenue` for the x402 endpoint-revenue summary (see [x402 revenue & receipts](#sec-548)), plus club and listing analytics. |
| `/api/x402/mcp-tool-catalog` | $0.001 | Snapshot of every MCP tool (name, paid/free, price, input shape) and a diff vs the last snapshot (added / removed / re-priced tools). |
| **Free read surfaces** | — | — |
| `/api/x402/my-receipts` | free | A buyer's own settled receipts, gated by a wallet signature (SIWX) rather than a payment. |
@@ -125938,9 +126082,9 @@ directory.
| `/api/x402/glb-optimization-report`| free | GLB Size Optimizer catalog feed: what the `glb-size-optimizer` autonomous-loop entry has measured. |
| `/api/x402/network-cost` | free | Cross-chain payment-cost recommendation feed from the hourly cross-chain-cost pipeline snapshots. |
| `/api/x402/runway-lab` | free | Live seed for [/economy-lab](https://three.ws/economy-lab): the fee wallet's real SOL balance and hard floor, the running deploy's governor config, today's spend from `x402_self_facilitator_log`, observed fee-per-settle and 24h demand, and the refusal histogram bucketed by cause (governor / floor / dust guard / duplicate). Read-only; every field is already public through `/api/x402-ring` and `/api/x402-status`. |
-| `/api/x402/echo` | free | httpbin for x402 — decodes your `X-PAYMENT` header (signatures redacted) and returns a local verify verdict without settling. See [x402 dev tools](#sec-544). |
-| `/api/x402/debug` | free | Diagnoses a failed 402 exchange (`{challenge, payment, response}`) into an ordered `{severity, field, problem, fix}` list. See [x402 dev tools](#sec-544). |
-| `/api/x402/verify-receipt` | free | Recomputes a paid response's SHA-256 attestation and confirms a settlement tx on-chain. See [x402 dev tools](#sec-544). |
+| `/api/x402/echo` | free | httpbin for x402 — decodes your `X-PAYMENT` header (signatures redacted) and returns a local verify verdict without settling. See [x402 dev tools](#sec-545). |
+| `/api/x402/debug` | free | Diagnoses a failed 402 exchange (`{challenge, payment, response}`) into an ordered `{severity, field, problem, fix}` list. See [x402 dev tools](#sec-545). |
+| `/api/x402/verify-receipt` | free | Recomputes a paid response's SHA-256 attestation and confirms a settlement tx on-chain. See [x402 dev tools](#sec-545). |
| `/api/x402/inference-verify` | free | Audits a metered-inference receipt from a paid `llm-proxy` call: per-check verdicts for the issuer signature, the node's response signature, prompt/response hash re-derivation from raw text, on-chain settlement confirmation, and whether the issuer matches the platform's published signers. See [Run an inference node](#sec-256). |
## $THREE only
@@ -125953,21 +126097,21 @@ input and do not promote any specific token.
## Related
- [Pump Launcher](#sec-344) — the full launch flow, inputs/outputs, and the free `symbol` → launch → `launches` funnel.
-- [x402 protocol](#sec-551) — the challenge/settle mechanics.
-- [x402 buyer client](#sec-543) — how to pay these endpoints in code.
-- [x402 revenue & receipts](#sec-547) — where settled payments are recorded and how to read endpoint revenue.
+- [x402 protocol](#sec-552) — the challenge/settle mechanics.
+- [x402 buyer client](#sec-544) — how to pay these endpoints in code.
+- [x402 revenue & receipts](#sec-548) — where settled payments are recorded and how to read endpoint revenue.
- [Autonomous x402 loop](#sec-105) — the scheduled buyer that drives volume through these endpoints.
- [MCP tools](#sec-279) — the same capabilities exposed as paid MCP tools.
---
-<a id="sec-547"></a>
+<a id="sec-548"></a>
> **Source:** `docs/x402-revenue.md` · [↑ table of contents](#table-of-contents)
# x402 Revenue & Receipts
-Every time someone pays one of three.ws's [paid endpoints](#sec-546), the
+Every time someone pays one of three.ws's [paid endpoints](#sec-547), the
settlement is recorded. This page is the reference for **where that money is
recorded**, how to read endpoint revenue, and how the durable receipt is issued to
the buyer.
@@ -126155,7 +126299,7 @@ LIMIT 10;
## The revenue report — `/api/x402/analytics`
You don't have to query SQL. The `analytics` endpoint serves the same numbers,
-pre-aggregated. It is itself a [paid endpoint](#sec-546) ($0.005 default).
+pre-aggregated. It is itself a [paid endpoint](#sec-547) ($0.005 default).
It is a `POST` endpoint: pass `report` and `period` in the JSON body:
```bash
@@ -126231,7 +126375,7 @@ CREATE TABLE x402_receipts (
```
A buyer reads **their own** receipts at
-[`/api/x402/my-receipts`](#sec-546) — that endpoint is free but gated by
+[`/api/x402/my-receipts`](#sec-547) — that endpoint is free but gated by
a wallet signature (SIWX), so a buyer proves ownership of the `payer` address
rather than paying again.
@@ -126440,15 +126584,15 @@ settled activity (include it), and label it as such.
## Related
-- [x402 paid endpoints](#sec-546) — the catalog of what charges and how much.
-- [x402 protocol](#sec-551) — the challenge / verify / settle mechanics.
-- [x402 buyer client](#sec-543) — how to settle a 402 challenge in code.
+- [x402 paid endpoints](#sec-547) — the catalog of what charges and how much.
+- [x402 protocol](#sec-552) — the challenge / verify / settle mechanics.
+- [x402 buyer client](#sec-544) — how to settle a 402 challenge in code.
- [Autonomous x402 loop](#sec-105) — the scheduled buyer that drives volume, including the Volume Bootstrap Loop and the reconciliation job.
- [Money feed](#sec-289) — the agent-spend side of the ledger (the Money Pulse), distinct from endpoint revenue.
---
-<a id="sec-548"></a>
+<a id="sec-549"></a>
> **Source:** `docs/x402-ring-economy.md` · [↑ table of contents](#table-of-contents)
@@ -127543,7 +127687,7 @@ activation runbook above is the fix.
- [STRUCTURE.md](../STRUCTURE.md) — surface map
- [/api/x402-revenue](../api/x402-revenue.js) — the **public** organic-revenue
feed (self-cycled ring volume is excluded from the "organic" framing here)
-- [docs/x402-revenue.md](#sec-547) — revenue surface docs
+- [docs/x402-revenue.md](#sec-548) — revenue surface docs
- [api/_lib/x402/ring-allowlist.js](../api/_lib/x402/ring-allowlist.js) — the
controlled-wallet set + spend invariants
- [api/cron/x402-ring-leak-scan.js](../api/cron/x402-ring-leak-scan.js) — the
@@ -127551,7 +127695,7 @@ activation runbook above is the fix.
---
-<a id="sec-549"></a>
+<a id="sec-550"></a>
> **Source:** `docs/x402-solana-july-roundup-response.md` · [↑ table of contents](#table-of-contents)
@@ -127569,7 +127713,7 @@ exact permalink from the account's profile before posting; quote-tweet directly
rather than typing a URL by hand.
Two accounts, two jobs, same split used for the IBM Community campaign in
-[event-x-posts.md](#sec-526): `@trythreews` posts the institutional version, `@nichxbt`
+[event-x-posts.md](#sec-527): `@trythreews` posts the institutional version, `@nichxbt`
posts the human one. Do not post both within a few minutes of each other.
---
@@ -127610,7 +127754,7 @@ the specific claim the roundup credited us for. Second choice: the AR drop-in on
---
-<a id="sec-550"></a>
+<a id="sec-551"></a>
> **Source:** `docs/x402-studio.md` · [↑ table of contents](#table-of-contents)
@@ -127620,11 +127764,11 @@ x402 Studio is the merchant console for running a paid x402 business on three.ws
Page: [/x402/studio](https://three.ws/x402/studio)
-APIs: `/api/x402-merchant` (settings), `/api/x402-skus` (products), `/api/sns` (name resolution), `/api/x402/pay-by-name` (USDC send). See [x402: paid agent skills](#sec-551) for the underlying payment protocol.
+APIs: `/api/x402-merchant` (settings), `/api/x402-skus` (products), `/api/sns` (name resolution), `/api/x402/pay-by-name` (USDC send). See [x402: paid agent skills](#sec-552) for the underlying payment protocol.
## Why it exists
-x402 turns any HTTP endpoint into a paid one: the server answers `402 Payment Required` with a manifest, the caller pays in USDC, and the call retries and settles. That primitive is powerful but low-level. Studio is the console on top of it, the difference between "you can hand-write a 402 challenge" and "you can run a storefront." A merchant configures once and gets hosted checkout links, a shareable storefront, a copy-paste pay button, revenue stats, and payouts to a wallet they control, without writing payment code. It is the seller-facing companion to the [x402 buyer client](#sec-543) and the [paid endpoint catalog](#sec-546).
+x402 turns any HTTP endpoint into a paid one: the server answers `402 Payment Required` with a manifest, the caller pays in USDC, and the call retries and settles. That primitive is powerful but low-level. Studio is the console on top of it, the difference between "you can hand-write a 402 challenge" and "you can run a storefront." A merchant configures once and gets hosted checkout links, a shareable storefront, a copy-paste pay button, revenue stats, and payouts to a wallet they control, without writing payment code. It is the seller-facing companion to the [x402 buyer client](#sec-544) and the [paid endpoint catalog](#sec-547).
## How it works
@@ -127710,16 +127854,16 @@ const { tx_base64, blockhash } = await res.json();
## Related
-- [x402: paid agent skills](#sec-551): the payment protocol Studio sits on top of
-- [x402 revenue and receipts](#sec-547): where settled payments are recorded
-- [x402 paid endpoints](#sec-546): the platform's own catalog of paid endpoints
-- [x402 buyer client](#sec-543): the caller side of a 402 challenge
-- [x402 developer tools](#sec-544) and [x402 distribution](#sec-545)
+- [x402: paid agent skills](#sec-552): the payment protocol Studio sits on top of
+- [x402 revenue and receipts](#sec-548): where settled payments are recorded
+- [x402 paid endpoints](#sec-547): the platform's own catalog of paid endpoints
+- [x402 buyer client](#sec-544): the caller side of a 402 challenge
+- [x402 developer tools](#sec-545) and [x402 distribution](#sec-546)
- Pages: [/x402/studio](https://three.ws/x402/studio) · [/x402](https://three.ws/x402)
---
-<a id="sec-551"></a>
+<a id="sec-552"></a>
> **Source:** `docs/x402.md` · [↑ table of contents](#table-of-contents)
@@ -127733,7 +127877,7 @@ of Pump.fun agent payments: callers pay an agent in any SPL token to invoke a
skill, and the agent verifies the on-chain payment before dispatching the
call. It is written for developers wiring paid skills (server side) or paying
for them (client side); the platform's own catalog of paid endpoints lives at
-[x402 paid endpoints](#sec-546).
+[x402 paid endpoints](#sec-547).
**Live activity:** [x402scan dashboard](https://www.x402scan.com/server/17cbd874-52ac-4920-a020-b22ff2489a07)
— browse paid calls, revenue, and per-skill pricing for this server.
@@ -127894,15 +128038,15 @@ Each package has its own repository with a full README, API reference, and examp
## Related
-- [x402 paid endpoints](#sec-546) — the catalog of the platform's own paid endpoints.
-- [x402 revenue & receipts](#sec-547) — where settled payments are recorded and how to read endpoint revenue.
-- [x402 buyer client](#sec-543) — how to settle a 402 challenge in code.
+- [x402 paid endpoints](#sec-547) — the catalog of the platform's own paid endpoints.
+- [x402 revenue & receipts](#sec-548) — where settled payments are recorded and how to read endpoint revenue.
+- [x402 buyer client](#sec-544) — how to settle a 402 challenge in code.
- [x402 bazaar over MCP](#sec-280) — discover and pay endpoints through the MCP bazaar.
- [Autonomous x402](#sec-105) — agents paying for services on their own.
---
-<a id="sec-552"></a>
+<a id="sec-553"></a>
> **Source:** `docs/zauth/database.md` · [↑ table of contents](#table-of-contents)
@@ -128048,7 +128192,7 @@ Use this endpoint to browse all known x402 endpoints before your agents commit t
---
-<a id="sec-553"></a>
+<a id="sec-554"></a>
> **Source:** `docs/zauth/index.md` · [↑ table of contents](#table-of-contents)
@@ -128068,11 +128212,11 @@ zauth is the security and trust layer that allows agents to act with confidence,
## Products
-### [VectorAI-powered vulnerability scanner. Automated recon, multi-category exploit testing, and detailed security reports for your web applications.Vector](#sec-556)### [RepoScanAI-powered code analysis for crypto communities. Scan GitHub repos for red flags, get trust scores, and compare code similarity across millions of repositories.RepoScan](#sec-555)### [DatabaseLive registry of x402 endpoints. AI agents continuously test and verify endpoints, tracking success rates, pricing, and response data.Database](#sec-552)### [Provider HubManage your x402 endpoints. Monitor health, track agent interactions, configure refunds, and verify your services through our SDK.Provider Hub](#sec-554)
+### [VectorAI-powered vulnerability scanner. Automated recon, multi-category exploit testing, and detailed security reports for your web applications.Vector](#sec-557)### [RepoScanAI-powered code analysis for crypto communities. Scan GitHub repos for red flags, get trust scores, and compare code similarity across millions of repositories.RepoScan](#sec-556)### [DatabaseLive registry of x402 endpoints. AI agents continuously test and verify endpoints, tracking success rates, pricing, and response data.Database](#sec-553)### [Provider HubManage your x402 endpoints. Monitor health, track agent interactions, configure refunds, and verify your services through our SDK.Provider Hub](#sec-555)
---
-<a id="sec-554"></a>
+<a id="sec-555"></a>
> **Source:** `docs/zauth/provider-hub.md` · [↑ table of contents](#table-of-contents)
@@ -128174,7 +128318,7 @@ Supply your EVM or Solana private keys to enable automatic refunds when your end
---
-<a id="sec-555"></a>
+<a id="sec-556"></a>
> **Source:** `docs/zauth/reposcan.md` · [↑ table of contents](#table-of-contents)
@@ -128500,7 +128644,7 @@ TypeScript -@x402/fetch
---
-<a id="sec-556"></a>
+<a id="sec-557"></a>
> **Source:** `docs/zauth/vector.md` · [↑ table of contents](#table-of-contents)
diff --git a/docs/aws-builder-center-agent-payment-sessions.md b/docs/aws-builder-center-agent-payment-sessions.md
index c52779739..5b0032680 100644
--- a/docs/aws-builder-center-agent-payment-sessions.md
+++ b/docs/aws-builder-center-agent-payment-sessions.md
@@ -22,7 +22,7 @@ This is a walk through the pattern we shipped instead, in production, at [three.
> The agent does not hold a wallet. It proposes spend. Governance enforces policy.
-Everything below is real code from our source-available repository, including the concurrency bug we had to design around and the failure mode that has no clean answer.
+Everything below is real code from our open source (Apache-2.0) repository, including the concurrency bug we had to design around and the failure mode that has no clean answer.
## The three bad options, and what each one actually costs
diff --git a/docs/aws-builder-center-marketplace-x402.md b/docs/aws-builder-center-marketplace-x402.md
index b1de3d310..b485f61d3 100644
--- a/docs/aws-builder-center-marketplace-x402.md
+++ b/docs/aws-builder-center-marketplace-x402.md
@@ -21,7 +21,7 @@ But a lot of teams don't want to touch crypto to pay an invoice. They want it on
The result is one authorization path that meters two ways: an AWS-subscribed customer and a stablecoin-paying developer hit the exact same endpoint, and the platform bills whichever economy that caller belongs to. This post is how we built it with the AWS SDK for JavaScript v3, the parts of the SaaS integration that are easy to get subtly wrong, and the bridge that ties an AWS `CustomerIdentifier` to an x402 key.
-Everything here is real code from our source-available repo, not pseudocode: the metering and webhook handlers call the AWS Marketplace APIs in `us-east-1` (where the Marketplace Metering and Entitlement services live).
+Everything here is real code from our open source (Apache-2.0) repo, not pseudocode: the metering and webhook handlers call the AWS Marketplace APIs in `us-east-1` (where the Marketplace Metering and Entitlement services live).
## The three integration points of a SaaS listing
diff --git a/docs/coinmarketcap-article-play.md b/docs/coinmarketcap-article-play.md
index 5c5cf0624..58e117ba6 100644
--- a/docs/coinmarketcap-article-play.md
+++ b/docs/coinmarketcap-article-play.md
@@ -105,7 +105,7 @@ For a CoinMarketCap reader, the load-bearing question is always: *is any of this
- **Real voice.** Peer-to-peer WebRTC with spatial HRTF audio, proximity-gated so it scales and so it sounds right.
- **Real buys.** A native pump.fun transaction built server-side and signed by your own wallet, not a redirect dressed up as a feature.
-And it's **source-available** and readable, like the rest of the platform.
+And it's **open source** and readable, like the rest of the platform.
## Why this matters
@@ -136,4 +136,4 @@ The chart has always told you *what* a coin is doing. /play lets you go stand wh
---
-*three.ws is an open-source, browser-native platform for 3D AI agents and on-chain communities, live at [three.ws](https://three.ws) and source-available. Coin Communities (/play) is live at [three.ws/play](https://three.ws/play).*
+*three.ws is an open-source, browser-native platform for 3D AI agents and on-chain communities, live at [three.ws](https://three.ws) and open source under Apache-2.0. Coin Communities (/play) is live at [three.ws/play](https://three.ws/play).*
diff --git a/docs/coinmarketcap-article.md b/docs/coinmarketcap-article.md
index 7d7ba55ee..69da8fb8d 100644
--- a/docs/coinmarketcap-article.md
+++ b/docs/coinmarketcap-article.md
@@ -9,7 +9,7 @@ target: CoinMarketCap Community / Editorial
For most of the last two years, the conversation about AI and crypto has lived inside a narrow lane: chatbots that can read a wallet balance, agents that can sign a swap, frameworks that promise "autonomous trading" but stall the moment the demo ends. What's been missing is the layer underneath all of that, a way for an AI agent to actually *exist* as a first-class object on the internet. To have an embodiment users can see. An identity that survives a model swap. A wallet that can pay for its own compute. A reputation that follows it across apps. A way to be embedded anywhere a YouTube video can be embedded today.
-[three.ws](https://three.ws) is building exactly that. It is an open-source platform that turns an AI agent into a persistent, ownable, multi-chain object, a 3D body in the browser, an LLM brain, an onchain identity registered on any of 15+ EVM networks (or Solana), and a distributable web component you can drop into any page on the internet. Every layer is source-available and readable end to end. The full stack is live and in production.
+[three.ws](https://three.ws) is building exactly that. It is an open-source platform that turns an AI agent into a persistent, ownable, multi-chain object, a 3D body in the browser, an LLM brain, an onchain identity registered on any of 15+ EVM networks (or Solana), and a distributable web component you can drop into any page on the internet. Every layer is open source under Apache-2.0 and readable end to end. The full stack is live and in production.
This article is about the part of three.ws that matters most to the crypto-native reader: **the onchain layer**. How the platform uses ERC-8004 across the EVM ecosystem, why it deploys to the same address on every chain, how Solana fits in, what role IPFS plays, and where the project is heading with agent tokens, reputation markets, skill royalties, and a decentralized inference network.
@@ -175,7 +175,7 @@ Plenty of teams are building AI agents. Plenty of teams are building agent ident
- The reputation system is open and pseudonymous, not curated by a moderator.
- The economic future of the platform, agent tokens, royalties, payments, inference settlement, is being built on contracts and cryptographic permissions, not on Stripe and a terms-of-service page.
-The platform is source-available. The viewer, the runtime, the contracts, the backend, the embedding layer, all of it is readable. If three.ws disappeared tomorrow, the agents minted today would still be onchain, their manifests would still be pinned to IPFS, the contracts would still be callable, and any reasonably motivated developer could rebuild the frontend in a weekend.
+The platform is open source under the Apache License 2.0. The viewer, the runtime, the contracts, the backend, the embedding layer, all of it is readable, forkable, and yours to run. If three.ws disappeared tomorrow, the agents minted today would still be onchain, their manifests would still be pinned to IPFS, the contracts would still be callable, and any reasonably motivated developer could rebuild the frontend in a weekend.
That's the property that distinguishes a *protocol* from a product. Most "AI agent platforms" today are products. three.ws is being built as a protocol, with an unfortunately polished product layer attached so people who are not developers can use it.
@@ -193,4 +193,4 @@ If you've been waiting for the moment AI and crypto stop talking past each other
---
-*three.ws is source-available. The repo, contracts, and full roadmap are at [github.com/nirholas/three.ws](https://github.com/nirholas/three.ws). The platform is live at [three.ws](https://three.ws).*
+*three.ws is open source under Apache-2.0. The repo, contracts, and full roadmap are at [github.com/nirholas/three.ws](https://github.com/nirholas/three.ws). The platform is live at [three.ws](https://three.ws).*
diff --git a/docs/coinmarketcap-live-article.md b/docs/coinmarketcap-live-article.md
index 40716ee94..a5620322d 100644
--- a/docs/coinmarketcap-live-article.md
+++ b/docs/coinmarketcap-live-article.md
@@ -113,5 +113,5 @@ close.
---
*three.ws is an open-source, browser-native platform for 3D AI agents and on-chain communities, live
-at [three.ws](https://three.ws) and source-available. The Three.ws User Group on IBM Community is
+at [three.ws](https://three.ws) and open source under Apache-2.0. The Three.ws User Group on IBM Community is
at [community.ibm.com](https://community.ibm.com/community/user/usergroup?CommunityKey=e71510cc-d953-408f-9a1c-019f5c0a7016).*
diff --git a/docs/open-source-friday-plan.md b/docs/open-source-friday-plan.md
index 33631c97d..6c3c1a583 100644
--- a/docs/open-source-friday-plan.md
+++ b/docs/open-source-friday-plan.md
@@ -65,7 +65,7 @@ Apache-2.0 over MIT for two reasons: CONTRIBUTING.md already promised it to ever
### Still to do
1. **Post the three seeded Discussions.** Written and ready in [contributing/discussion-seeds.md](contributing/discussion-seeds.md): a Welcome post (pin it), a Show and tell thread, and an open Roadmap thread. The workspace token has `issues: write` but not `discussions: write`, so this is 60 seconds of paste by a human. Zero threads is what reads as nobody being home; three real ones fixes it.
-2. **Trim the README's front door.** It is 401 KB. Nobody evaluating a livestream guest reads 401 KB. The first screen needs what it is, a 10-second demo GIF, and the install line. Everything else moves below the fold or into `docs/`.
+2. **The README front door is better than its file size suggests.** 8,402 of its 11,372 lines are one inline STL model that GitHub renders as an interactive 3D viewer, so a reader on github.com sees a widget, not 8,000 lines of vertex data. The prose is about 3,000 lines. The first screen now carries the license and good-first-issue badges and a contributor CTA alongside the user one. What is still worth doing is a 10-second demo GIF above the fold, since the current hero is a video attachment that does not autoplay in every context.
3. **Record a 45-second demo clip** (prompt to rigged avatar to embedded on a page). Reusable: README, the issue body, and every amplification post. Per section 5, video and images are what move GitHub's own numbers.
---
diff --git a/public/changelog.json b/public/changelog.json
index 5f59aeb37..c99d68564 100644
--- a/public/changelog.json
+++ b/public/changelog.json
@@ -1,11 +1,21 @@
{
- "generated_at": "2026-08-21T19:49:02.329Z",
+ "generated_at": "2026-08-22T02:40:42.490Z",
"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-08-22",
+ "type": "update",
+ "title": "The README now says open source, because it is",
+ "summary": "Ten places across the README and our published articles still described three.ws as source-available, which understated the Apache 2.0 license the project actually ships under. They now say open source, and the README explains what that buys you: fork it, self-host it, ship commercial work on it. The top of the README also carries a license badge, a live count of good first issues, and a one-line path for anyone who wants to contribute rather than just use it. The security reporting line no longer points at a retired mirror repository.",
+ "link": "/docs/first-contribution",
+ "tags": [
+ "docs"
+ ]
+ },
{
"date": "2026-08-21",
"type": "launch",
diff --git a/public/changelog.xml b/public/changelog.xml
index f2efe7ab7..36e1cd686 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>The README now says open source, because it is</title>
+ <link>https://three.ws/docs/first-contribution</link>
+ <guid isPermaLink="false">2026-08-22:The README now says open source, because it is</guid>
+ <pubDate>Sat, 22 Aug 2026 12:00:00 GMT</pubDate>
+ <category>docs</category>
+ <description>Ten places across the README and our published articles still described three.ws as source-available, which understated the Apache 2.0 license the project actually ships under. They now say open source, and the README explains what that buys you: fork it, self-host it, ship commercial work on it. The top of the README also carries a license badge, a live count of good first issues, and a one-line path for anyone who wants to contribute rather than just use it. The security reporting line no longer points at a retired mirror repository.</description>
+ </item>
<item>
<title>Docs · Community</title>
<link>https://three.ws/docs/community</link>
diff --git a/public/features.json b/public/features.json
index 5f95effc9..c46382d5b 100644
--- a/public/features.json
+++ b/public/features.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-08-21T19:49:02.320Z",
+ "generated_at": "2026-08-22T02:40:42.481Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json",
"site": {
"name": "three.ws",