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(community): submit the Open Source Friday request and draft the reply that closes Andrea's loop

nirholas71524a08f7ff
diff --git a/docs/ALL.md b/docs/ALL.md
index 73884f003..20d4ecdea 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-26 from **564 files** (~8018 KB).
+> Single-file snapshot of every document under [`docs/`](.). Generated 2026-08-26 from **565 files** (~8021 KB).
> The individual source files remain the canonical, editable copies — this file is a read-only aggregate.
## Table of contents
@@ -324,14 +324,14 @@
- [world-lines.md](#sec-524)
- [x-archive.md](#sec-525)
- [x-memory-seeding.md](#sec-527)
-- [x402-buyer.md](#sec-552)
-- [x402-dev-tools.md](#sec-553)
-- [x402-distribution.md](#sec-554)
-- [x402-endpoints.md](#sec-555)
-- [x402-ring-economy.md](#sec-556)
-- [x402-solana-july-roundup-response.md](#sec-557)
-- [x402-studio.md](#sec-558)
-- [x402.md](#sec-559)
+- [x402-buyer.md](#sec-553)
+- [x402-dev-tools.md](#sec-554)
+- [x402-distribution.md](#sec-555)
+- [x402-endpoints.md](#sec-556)
+- [x402-ring-economy.md](#sec-557)
+- [x402-solana-july-roundup-response.md](#sec-558)
+- [x402-studio.md](#sec-559)
+- [x402.md](#sec-560)
### agent-abilities
@@ -612,20 +612,21 @@
- [x-posts/onchain-agent-wallets-x-post.md](#sec-543)
- [x-posts/open-source-ecosystem.md](#sec-544)
- [x-posts/oracle-trading-mcp-x-post.md](#sec-545)
-- [x-posts/pumpfun-article-x-post.md](#sec-546)
-- [x-posts/sperax-staking-in-chat-x-post.md](#sec-547)
-- [x-posts/the-first-19-weeks.md](#sec-548)
-- [x-posts/threews-avatar-launch.md](#sec-549)
-- [x-posts/threews-avatar-video-script.md](#sec-550)
-- [x-posts/x-meetup-posts.md](#sec-551)
+- [x-posts/osf-issue-reply.md](#sec-546)
+- [x-posts/pumpfun-article-x-post.md](#sec-547)
+- [x-posts/sperax-staking-in-chat-x-post.md](#sec-548)
+- [x-posts/the-first-19-weeks.md](#sec-549)
+- [x-posts/threews-avatar-launch.md](#sec-550)
+- [x-posts/threews-avatar-video-script.md](#sec-551)
+- [x-posts/x-meetup-posts.md](#sec-552)
### zauth
-- [zauth/database.md](#sec-560)
-- [zauth/index.md](#sec-561)
-- [zauth/provider-hub.md](#sec-562)
-- [zauth/reposcan.md](#sec-563)
-- [zauth/vector.md](#sec-564)
+- [zauth/database.md](#sec-561)
+- [zauth/index.md](#sec-562)
+- [zauth/provider-hub.md](#sec-563)
+- [zauth/reposcan.md](#sec-564)
+- [zauth/vector.md](#sec-565)
---
@@ -1510,11 +1511,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-559) resource: an AI agent pays a few cents in USDC, hands in a URL,
+own [x402](#sec-560) 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-555); the stages below are what you do to
+3D) is [`/api/x402/forge`](#sec-556); the stages below are what you do to
a mesh *after* it exists.
```
@@ -1527,7 +1528,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-555).
+2. **The whole chain in one call** — [`POST /api/x402/pipeline`](#sec-556).
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
@@ -1590,7 +1591,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-552).
+[x402 buyer client](#sec-553).
## Stages
@@ -1749,8 +1750,8 @@ returned as-is. Poll budget is tunable via `X402_PIPELINE_POLL_BUDGET_MS`
## Related
-- [x402 paid endpoints](#sec-555) — the full catalog + pricing model
-- [x402 buyer client](#sec-552) — how to settle payments as an agent
+- [x402 paid endpoints](#sec-556) — the full catalog + pricing model
+- [x402 buyer client](#sec-553) — how to settle payments as an agent
- [Avatar pipeline](#sec-113) — the generation + rig lanes in depth
---
@@ -13640,7 +13641,7 @@ would hide it.
## Related
-- [x402 paid endpoints](#sec-555): the other side of the ledger. This
+- [x402 paid endpoints](#sec-556): 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.
@@ -14938,7 +14939,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-559)).
+3. **Pay** — the service answers an HTTP `402` and the agent signs a stablecoin micropayment ([x402](#sec-560)).
4. **Vouch** — after the work, write feedback back to the Reputation Registry, closing the loop for the next agent.
The one-liner worth remembering:
@@ -14998,7 +14999,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-402) · [Leave a vouch](#sec-376) · [ERC-8004 identity](#sec-189) · [x402 payments](#sec-559)
+**Next:** [Read an agent's reputation](/tutorials/agent-reputation) · [Reputation on Solana](#sec-402) · [Leave a vouch](#sec-376) · [ERC-8004 identity](#sec-189) · [x402 payments](#sec-560)
---
@@ -18289,7 +18290,7 @@ An agent can pay a human-readable name instead of a base58 address. `/api/x402/p
- [Custody you can verify](#sec-171) — limits, freeze, Merkle proof-of-custody, social recovery and inheritance
- [Financial controls](#sec-222) — 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-559) — how agents pay for services
+- [x402 protocol](#sec-560) — how agents pay for services
- [Coin launches](#sec-144) — how the wallet signs a pump.fun launch
---
@@ -28920,7 +28921,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-555) and
+[x402 endpoints](#sec-556) and
[the autonomous economy](#sec-105).
Treat prompts as public. If you need a private lane, use the account-scoped
@@ -28972,7 +28973,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-555): every paid endpoint on the platform.
+- [x402 endpoints](#sec-556): every paid endpoint on the platform.
---
@@ -31025,7 +31026,7 @@ zero.
platform's cut.
- [Economy master](#sec-183) — the funding-root subsystem, its ledger, and the
topup/sweepback crons in depth.
-- [x402 ring economy](#sec-556) — how the autonomous payment ring settles
+- [x402 ring economy](#sec-557) — how the autonomous payment ring settles
USDC between agents.
---
@@ -31251,9 +31252,9 @@ corroborate — the ops financial-integrity surface alerts on those. Detail:
## Related
-- [x402 endpoints](#sec-555) — the paid endpoints this loop calls.
+- [x402 endpoints](#sec-556) — the paid endpoints this loop calls.
- [Financial controls](#sec-222): where settlements land and how the reconciliation job audits them.
-- [x402 buyer client](#sec-552) — the client wrappers it pays with.
+- [x402 buyer client](#sec-553) — the client wrappers it pays with.
- [Circulation engine](#sec-141) — the separate SOL/$THREE activity loop.
---
@@ -32918,7 +32919,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-555)).
+[MCP tools](#sec-279), [x402 endpoints](#sec-556)).
### ② Auto-rig
@@ -35357,7 +35358,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-559), [three.ws/docs/mcp](#sec-281)
+- How agents reach and pay for tools: [three.ws/docs/x402](#sec-560), [three.ws/docs/mcp](#sec-281)
---
@@ -36923,7 +36924,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-559)
+Paste a token contract address, get back a live, agent-payable [x402](#sec-560)
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.
@@ -37073,7 +37074,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-555) for the full
+back to the default. See [x402 paid endpoints](#sec-556) for the full
price-override scheme.
---
@@ -37232,9 +37233,9 @@ right now. If the endpoint is unreachable the page says so and offers a retry.
## Related
-- [x402 on three.ws](#sec-559): the protocol, the wire format, and how the
+- [x402 on three.ws](#sec-560): the protocol, the wire format, and how the
platform settles.
-- [x402 paid endpoints](#sec-555): the full catalog of our paid
+- [x402 paid endpoints](#sec-556): the full catalog of our paid
endpoints, their prices, and the `X402_PRICE_*` override scheme.
- [Receipt Vault](../pages/receipts.html): where the buyer's signed receipt for a
settled payment to this endpoint can be retrieved.
@@ -41642,7 +41643,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-559) 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-560) 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/`.
@@ -41651,7 +41652,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-559): 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-560): 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.
@@ -41662,7 +41663,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-559) · [SDK docs](#sec-383) · register via [Register On-Chain](#sec-474).
+- Start: [MCP setup](#sec-281) · [x402 docs](#sec-560) · [SDK docs](#sec-383) · register via [Register On-Chain](#sec-474).
- 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.]`
@@ -41749,7 +41750,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-559) (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-560) (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)
@@ -41769,7 +41770,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-559) for the agent-economy rails · [Register On-Chain](#sec-474) for reputation.
+- Build: [x402 docs](#sec-560) for the agent-economy rails · [Register On-Chain](#sec-474) 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.]`
@@ -44919,7 +44920,7 @@ Every step of recovery and inheritance writes to the custody trail and the audit
- [Financial controls](#sec-222) — plain-English spend rules and real-time wallet defense on these rails
- [Trading surfaces](#sec-426) — Mission Control executes through this same guarded path
- [The trading experiment](#sec-424) — an autonomous agent operating inside these limits, journaled
-- [x402](#sec-559) — the payment protocol these wallets spend over
+- [x402](#sec-560) — the payment protocol these wallets spend over
---
@@ -46244,7 +46245,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-553).
+[Authentication](#sec-103), [x402 developer tools](#sec-554).
---
@@ -47447,7 +47448,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-556) ·
+[x402 ring economy](#sec-557) ·
[economy funding root](#sec-183) · [money map](#sec-291)
---
@@ -48034,7 +48035,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-556) /
+ other engine (see [x402 ring economy](#sec-557) /
[autonomous x402](#sec-105)).
## Related
@@ -48043,7 +48044,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-556) — closed-loop in-house x402 settlement.
+- [x402 ring economy](#sec-557) — closed-loop in-house x402 settlement.
---
@@ -49558,8 +49559,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-555) — the full paid catalog and pricing.
-- [x402 Buyer Client](#sec-552) — how to settle a 402 challenge from code.
+- [x402 Paid Endpoints](#sec-556) — the full paid catalog and pricing.
+- [x402 Buyer Client](#sec-553) — how to settle a 402 challenge from code.
- [Avatar creation](#sec-109) — generate a rigged avatar in the web UI.
---
@@ -53070,7 +53071,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-559).
+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-560).
## Running the benchmark
@@ -53133,7 +53134,7 @@ Two guards keep a bad run from becoming a published number:
## Related
-- [x402: paid agent skills](#sec-559): the payment rail the $0.10 lane rides
+- [x402: paid agent skills](#sec-560): 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-381) and [3D provenance](#sec-344): 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)
@@ -53686,7 +53687,7 @@ Ranked by accounting/regulatory risk. Each is a tracked remediation item.
## Related
- [Money map](#sec-291) — who receives each payment.
-- [x402 endpoints](#sec-555) — the paid endpoint catalog.
+- [x402 endpoints](#sec-556) — the paid endpoint catalog.
- [Solana signers runbook](../api/_lib/solana-signers.js) — the wallets + funding.
---
@@ -54607,7 +54608,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-559). Nothing on the page is curated or seeded by
+[x402 payment protocol](#sec-560). 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
@@ -54657,7 +54658,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-556), and the loop's daily spend cap
+ [x402 ring economy](#sec-557), 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
@@ -54735,11 +54736,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-556): the wider self-paid endpoint
+- [x402 ring economy](#sec-557): the wider self-paid endpoint
economy the seeder wallet participates in.
- [How the Forge works](#sec-241): the generation pipeline the
agents are paying for.
-- [x402 on three.ws](#sec-559): the payment protocol itself.
+- [x402 on three.ws](#sec-560): the payment protocol itself.
---
@@ -56753,7 +56754,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-559), 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-560), no account needed. The page you use and the API an agent uses are the same pipeline underneath.
## Try it
@@ -56919,7 +56920,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-189) or [Solana](#sec-403) |
-| A paid API anyone (including agents) can call | [x402 monetization](#sec-559) |
+| A paid API anyone (including agents) can call | [x402 monetization](#sec-560) |
| 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-474) |
@@ -58276,7 +58277,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-559)**.
+**[docs/x402.md](#sec-560)**.
---
@@ -58616,7 +58617,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-559) — the x402 payment protocol on three.ws
+- [docs/x402.md](#sec-560) — 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
@@ -59212,7 +59213,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-559) and is surfaced publicly at [/fits](https://three.ws/fits).
+[x402](#sec-560) 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
@@ -62154,7 +62155,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-559).
+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-560).
---
@@ -63007,7 +63008,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-555) endpoint returns the
+ paid [`/api/x402/skill-marketplace`](#sec-556) 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
@@ -64084,7 +64085,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-559). This
+others expose paid tools that settle per call in USDC over [x402](#sec-560). 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
@@ -64224,7 +64225,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-555) — the same capabilities over REST.
+- [x402 paid endpoints](#sec-556) — 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.
@@ -64903,7 +64904,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-559) — 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-560) — never a second, MCP-only payment flow.
```bash
# Equivalent to: GET /api/v1/x/dexscreener/token?addresses=FeMbDoX7R1Psc4GEcvJdsbNbZA3bfztcyDCatJVJpump
@@ -67136,7 +67137,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 endpoints](#sec-555): the *other* direction: money paid **to** our endpoints (`x402_audit_log`), not agent spend.
+- [x402 endpoints](#sec-556): the *other* direction: money paid **to** our endpoints (`x402_audit_log`), not agent spend.
---
@@ -67397,7 +67398,7 @@ 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-555) (the paid endpoint catalog),
+Companion docs: [x402 endpoints](#sec-556) (the paid endpoint catalog),
[Financial controls](#sec-222) (how settlements are recorded),
[Solana signers runbook](../api/_lib/solana-signers.js) (the
signer/funder wallets and how to fund them).
@@ -67498,7 +67499,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-555).
+ [x402 endpoints](#sec-556).
- **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,
@@ -67571,8 +67572,8 @@ that set `auto_fund_enabled = true` (default off). See
## Related
- [Financial controls & audit register](#sec-222) — every ledger's integrity, reconciliation, retention, monitoring, and the ranked gap list.
-- [x402 endpoints](#sec-555) — the paid endpoint catalog and price overrides.
-- [x402 ring economy](#sec-556) — the internal recirculation loop.
+- [x402 endpoints](#sec-556) — the paid endpoint catalog and price overrides.
+- [x402 ring economy](#sec-557) — the internal recirculation loop.
- [Pump platform fee](#sec-349) — the pump trade fee detail.
- [Coin-launch wallets](#sec-508) — launch-time wallet flow.
- [Creator revenue splits](../api/_lib/cosmetics-economy.js) — `recordSaleAndSplit`: the cosmetic split math and its real USDC payout.
@@ -70024,7 +70025,7 @@ the **back burner**: still deployed, still payable, deliberately off the listing
documented at the bottom of this page.
> Related: [REST API Reference](#sec-096) · [MCP servers](#sec-281) ·
-> [x402 payments](#sec-559) · seller-side protocol spec:
+> [x402 payments](#sec-560) · 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,
@@ -70943,7 +70944,7 @@ Thank you for the first hundred.
Every place the three.ws codebase, its packages, its listings, or its community lives outside three.ws itself, with the link to cite and the number behind it. This is the canonical reference for announcements (the 100-star post, the X article, the weekly report): if two pieces of copy quote different numbers, this page wins. Every link below returned a live page on August 25, 2026; every count came from the registry's own API on the same day. Regenerate the milestone graphic that renders these numbers with `node scripts/render-github-stars-banner.mjs`.
-Related: [listings.md](#sec-269) (marketplace status and submission history), [x402-distribution.md](#sec-554) (every x402 crawler and directory, with mechanism), [community.md](#sec-151), [partners.md](#sec-326).
+Related: [listings.md](#sec-269) (marketplace status and submission history), [x402-distribution.md](#sec-555) (every x402 crawler and directory, with mechanism), [community.md](#sec-151), [partners.md](#sec-326).
## The repo
@@ -71047,6 +71048,7 @@ Mint `FeMbDoX7R1Psc4GEcvJdsbNbZA3bfztcyDCatJVJpump`. Venues: [pump.fun (verified
**Program page:** https://github.com/githubevents/open-source-friday
**Criteria:** [admin/project-criteria.md](https://github.com/githubevents/open-source-friday/blob/main/admin/project-criteria.md)
**Request form:** https://github.com/githubevents/open-source-friday/issues/new?template=osf-guest-invite.yml
+**Our request:** https://github.com/githubevents/open-source-friday/issues/254 (opened 2026-08-25)
---
@@ -71112,7 +71114,7 @@ On 2026-08-21 the repo sat at 98. The call was to treat that as noise rather tha
---
-## 3. The issue: exact field-by-field content
+## 3. The issue: exact field-by-field content (submitted as [#254](https://github.com/githubevents/open-source-friday/issues/254))
The form (`osf-guest-invite.yml`) auto-titles as `Open Source Friday - [PROJECT NAME] - [MM-DD-YYYY]`, labels `open-source-friday, open-source, twitch, pending`, and assigns @AndreaGriffiths11, @KevinCrosby, @marlenezw, @madebygps. A date is not required to submit: check "Not yet" and they send the booking link on approval.
@@ -71217,7 +71219,8 @@ Every hard criterion is met, stars included. What remains is one click, polish,
| 2026-08-25 | Three seed Discussions posted (#122, #123, #124) | Done |
| 2026-08-25 | Pin #122 | Owner, one click |
| 2026-08-26 | README front door trimmed, demo clip recorded | Agent |
-| 2026-08-27 | **Issue submitted**, reply posted to Andrea's X thread | Owner |
+| 2026-08-25 | **Issue submitted**: [open-source-friday#254](https://github.com/githubevents/open-source-friday/issues/254) | Done |
+| 2026-08-25 | Reply to Andrea's X thread with the issue link (draft: [x-posts/osf-issue-reply.md](#sec-546)) | Owner |
| 2026-08-28+ | Booking link arrives on approval, book the slot | Owner |
| ~2026-09-11 | Stream (earliest date satisfying the two-week rule) | Owner |
@@ -73558,7 +73561,7 @@ The page closes with four reasons, useful as the short pitch when someone asks:
- [Press kit](#sec-342): 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-559): the payment rail behind the agent-to-agent micropayments every partner surface references
+- [x402](#sec-560): the payment rail behind the agent-to-agent micropayments every partner surface references
---
@@ -74179,9 +74182,9 @@ curl -s $BASE/api/credits -H "$AUTH" | jq .balance_usd
## Related
-- [x402 Protocol](#sec-559): the challenge / verify / settle mechanics behind every paid call.
-- [x402 Buyer Client](#sec-552): paying x402 endpoints from your own wallet instead of a session.
-- [x402 Developer Tools](#sec-553): free echo / debug / receipt-verification tools for debugging a paid call.
+- [x402 Protocol](#sec-560): the challenge / verify / settle mechanics behind every paid call.
+- [x402 Buyer Client](#sec-553): paying x402 endpoints from your own wallet instead of a session.
+- [x402 Developer Tools](#sec-554): free echo / debug / receipt-verification tools for debugging a paid call.
---
@@ -77291,7 +77294,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-559) rail and the platform does the rest:
+[x402](#sec-560) 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**,
@@ -77383,7 +77386,7 @@ curl -X POST https://three.ws/api/x402/pump-launch \
curl "https://three.ws/api/crypto/launches"
```
-See [x402 buyer client](#sec-552) for how to satisfy the 402 challenge in
+See [x402 buyer client](#sec-553) for how to satisfy the 402 challenge in
code.
## Output
@@ -77433,12 +77436,12 @@ token itself always deploys on **Solana mainnet** — pump.fun is mainnet-only.
## Related
-- [x402 paid endpoints](#sec-555) — the full catalog and pricing.
+- [x402 paid endpoints](#sec-556) — the full catalog and pricing.
- [Crypto Data API](#sec-179) — the free `symbol` and `launches`
endpoints that bookend a launch.
- [Repo → Coin Launcher](#sec-347) — the batch/CLI launcher that
routes 100% of creator rewards to a GitHub identity (shares the same engine).
-- [x402 protocol](#sec-559) — challenge/settle mechanics.
+- [x402 protocol](#sec-560) — challenge/settle mechanics.
---
@@ -82179,7 +82182,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-429) — score a Robinhood Chain wallet's cross-chain
reputation before transacting with it.
-- [x402 distribution](#sec-554) — how the paid portfolio endpoint gets discovered
+- [x402 distribution](#sec-555) — how the paid portfolio endpoint gets discovered
across the x402 ecosystem.
---
@@ -84709,7 +84712,7 @@ curl -s https://three.ws/api/signals/subscribe -H 'authorization: Bearer YOUR_TO
- [Custody you can verify](#sec-171) - the spend caps, freeze, and audit trail the subscriber wallet pays and trades under
- [Financial controls](#sec-222) - the plain-English rules and firewall the mirror respects
- [Oracle](#sec-323) - the conviction engine and its own follow/copy tier
-- [x402](#sec-559) - the USDC payment protocol every signal settles over
+- [x402](#sec-560) - the USDC payment protocol every signal settles over
- [Trader card](#sec-420) - 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
@@ -85498,7 +85501,7 @@ whose pending balance clears $0.01, so nobody pays gas to move dust.
## Related
- [Skills marketplace](#sec-396): publishing, pricing, and installing skills
-- [x402 endpoints](#sec-555): every paid endpoint and who each one pays
+- [x402 endpoints](#sec-556): every paid endpoint and who each one pays
- [Money map](#sec-291): how value moves across the whole platform
- [Remix royalties](#sec-374): the parallel royalty rail for 3D creations
@@ -88709,8 +88712,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-380) — 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-554) — 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-553) — 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-555) — 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-554) — 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
@@ -88785,7 +88788,7 @@ Deeper references that don't fit a track above but answer real questions:
- [Demo routes](#sec-174): the canonical map of every `/demo/*` and `/demos/*` route
- [Agent trading spec](#sec-405): the proposed agent trading capability contract
- [ERC-8004 validation attestation](#sec-190): the attestation written when an agent registers on-chain
-- [zauth](#sec-561): the vendored security infrastructure docs our agent auth builds on
+- [zauth](#sec-562): 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-350): the vendored on-chain program reference behind the launch surfaces
- [pump-fun-mcp at the edge](#sec-346): the Cloudflare Workers mirror of the pump.fun MCP endpoint
@@ -88806,7 +88809,7 @@ Deeper references that don't fit a track above but answer real questions:
- [Guardian console](#sec-238): 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-172): a new deterministic 3D creative challenge every day
-- [x402 Studio](#sec-558): the merchant console for running a paid x402 business on three.ws
+- [x402 Studio](#sec-559): 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-397): 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
@@ -90264,7 +90267,7 @@ The response reports `fired`, `paid`, `buys`, `pending`, `errors`, `toll_spent_u
## Related
-- [docs/x402-ring-economy.md](#sec-556) — the closed-loop x402 ring the toll settles through.
+- [docs/x402-ring-economy.md](#sec-557) — 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.
@@ -92314,7 +92317,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-555).
+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-556).
## Related
@@ -93081,7 +93084,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-559)).
+(Base or Solana mainnet, via [x402](#sec-560)).
Pass any counterparty identifier. The type is auto-detected and scored from whatever
real on-chain evidence exists for it:
@@ -93199,7 +93202,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-559).
+dropped >10 points). See the [x402 catalog](#sec-560).
---
@@ -93224,7 +93227,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-559)).
+— $0.005 USDC per call (Base or Solana mainnet, via [x402](#sec-560)).
It verifies a **claim** that `identity` controls `address`, for **any** identity type,
on any chain — regardless of the platform the counterparty came from:
@@ -93298,7 +93301,7 @@ score *whether to trust* them.
---
-See also: [x402 paid endpoints](#sec-559) · [Agent Bouncer](#sec-096) · [ERC-8004 identity](#sec-189)
+See also: [x402 paid endpoints](#sec-560) · [Agent Bouncer](#sec-096) · [ERC-8004 identity](#sec-189)
---
@@ -118885,7 +118888,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-559) rail and the
+no account, and no SOL. Pay per call in USDC over the [x402](#sec-560) rail and the
server grinds (or delivers from stock) a brand-new keypair that matches.
| Endpoint | What it is | Chars | Price | Pick it when |
@@ -119120,7 +119123,7 @@ challenges and the discovery doc stay in parity.
## Related
-- [x402 endpoints overview](#sec-555)
+- [x402 endpoints overview](#sec-556)
- [three-vanity/v1 protocol spec](#sec-005)
- [Pump Launcher](#sec-348) — accepts an optional vanity mint prefix/suffix
- Web grinder + verifier: [`/vanity-wallet`](https://three.ws/vanity-wallet), [`/vanity/verify`](https://three.ws/vanity/verify)
@@ -119628,7 +119631,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 paid endpoints](#sec-555): the platform's own endpoint
+- [x402 paid endpoints](#sec-556): 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
@@ -124173,11 +124176,11 @@ explicit approval). Each file states what it's for and what has already been ver
| [`metaplex-agent-deployer-x-post.md`](#sec-538) | The browser deployer at nirholas.github.io/metaplex-agent-mcp |
| [`3d-ar-studio-launch.md`](#sec-528) | 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-531) | 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-549) | The three.ws avatar pipeline launch copy |
+| [`threews-avatar-launch.md`](#sec-550) | The three.ws avatar pipeline launch copy |
| [`oracle-trading-mcp-x-post.md`](#sec-545) | The oracle trading MCP server launch |
-| [`sperax-staking-in-chat-x-post.md`](#sec-547) | 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 |
+| [`sperax-staking-in-chat-x-post.md`](#sec-548) | 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-542) | The news archive |
-| [`pumpfun-article-x-post.md`](#sec-546) | The pump.fun article |
+| [`pumpfun-article-x-post.md`](#sec-547) | The pump.fun article |
## Video and narration scripts
@@ -124185,15 +124188,16 @@ explicit approval). Each file states what it's for and what has already been ver
| --- | --- |
| [`metaplex-agent-mcp-veo-script.md`](#sec-540) | 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-537) | Spoken narration for the deployer clip |
-| [`threews-avatar-video-script.md`](#sec-550) | Shot list for the avatar clip |
+| [`threews-avatar-video-script.md`](#sec-551) | Shot list for the avatar clip |
| [`3d-ar-studio-video-script.md`](#sec-529) | Narration and shot prompts for the AR Studio launch video |
## Events and community
| File | What it covers |
| --- | --- |
+| [`osf-issue-reply.md`](#sec-546) | The reply to Andrea Griffiths closing the loop on the Open Source Friday request (open-source-friday#254), in a Premium-length and a 280-character form |
| [`event-x-posts.md`](#sec-532) | Event campaign copy, split by account (`@trythreews` institutional, `@nichxbt` personal) |
-| [`x-meetup-posts.md`](#sec-551) | The in-platform community meetup announcement |
+| [`x-meetup-posts.md`](#sec-552) | The in-platform community meetup announcement |
| [`ibm-skillsbuild-x-post.md`](#sec-535) | The IBM SkillsBuild badge |
| [`fomo-verified-x-post.md`](#sec-533) | FOMO verification |
@@ -124219,7 +124223,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-549) sells the avatar-has-a-body
+did. Related file: [threews-avatar-launch.md](#sec-550) 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
@@ -126798,6 +126802,58 @@ place to be wrong.
<a id="sec-546"></a>
+> **Source:** `docs/x-posts/osf-issue-reply.md` · [↑ table of contents](#table-of-contents)
+
+# Reply to Andrea: the Open Source Friday request is in
+
+**What it is for.** Andrea Griffiths (@acolombiadev, GitHub) replied to Nich's post on 2026-08-21 with "Hey Nich, please open an issue" and the program criteria. The issue is now open. This is the reply that closes that loop, posted as a reply in her thread, not as a fresh post, so it lands in front of her and the people who liked the exchange.
+
+**Verified true at time of writing (2026-08-25):**
+
+- The request issue exists: https://github.com/githubevents/open-source-friday/issues/254
+- The repo passes every hard criterion in their `project-criteria.md`: Contributor Covenant, contributing guide, Apache-2.0 license (GitHub detects it), 104 stars, six curated `good first issue`s, Discussions seeded, triage and onboarding docs published.
+- The reply carries no numbers that could go stale before she reads it except the star count, which only goes up.
+
+## The reply (reply to Andrea's "please open an issue" post)
+
+Post from @nichxbt.
+
+```
+Done: github.com/githubevents/open-source-friday/issues/254
+
+Since you asked, three.ws went Apache-2.0, crossed 100 stars, opened Discussions, and published a 15-minute clone-to-PR guide with a live good-first-issue list. The bit I want to do on air is a contributor adding a new rig convention, PR opened live.
+
+Thank you for the nudge.
+```
+
+Measured: 307 characters with the URL counted at 23. Under the 280 cap only for Premium accounts; if @nichxbt is not Premium, use the short form below.
+
+## Short form (fits 280 for a non-Premium account)
+
+```
+Done: github.com/githubevents/open-source-friday/issues/254
+
+Since you asked: three.ws went Apache-2.0, passed 100 stars, and opened Discussions. The segment I want to do on air is a contributor adding a rig convention, PR opened live.
+
+Thank you for the nudge.
+```
+
+Measured: 231 characters with the URL counted at 23.
+
+## Do not
+
+- Do not post it cold as a new tweet. It is a reply. The whole value is that it answers her in her thread.
+- Do not quote-post her. She asked a direct question; answer it directly.
+- Do not tag the other program maintainers. Our account has no triage rights on their repo, so the issue carries none of the template labels or assignees; this reply to Andrea is the notification, and she labels it on their side.
+
+## After it is posted
+
+Nothing. The next move is theirs: on approval they apply the `approved` label and a bot comments on #254 with the booking link. Book a Friday at least two weeks out (2026-09-11 is the first realistic one), then follow the stream runsheet in [../open-source-friday-plan.md](#sec-311).
+
+---
+
+<a id="sec-547"></a>
+
> **Source:** `docs/x-posts/pumpfun-article-x-post.md` · [↑ table of contents](#table-of-contents)
# X post: pump.fun wrote an article about three.ws
@@ -126913,7 +126969,7 @@ Pick one option. Do not post all four.
---
-<a id="sec-547"></a>
+<a id="sec-548"></a>
> **Source:** `docs/x-posts/sperax-staking-in-chat-x-post.md` · [↑ table of contents](#table-of-contents)
@@ -127019,7 +127075,7 @@ on the `/staking` page footer, so anyone who tries it gets exactly what the post
---
-<a id="sec-548"></a>
+<a id="sec-549"></a>
> **Source:** `docs/x-posts/the-first-19-weeks.md` · [↑ table of contents](#table-of-contents)
@@ -127080,14 +127136,14 @@ The First 19 Weeks is out: the whole story of three.ws since the first commit, 9
---
-<a id="sec-549"></a>
+<a id="sec-550"></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-550).
+[threews-avatar-video-script.md](#sec-551).
**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.
@@ -127237,7 +127293,7 @@ Carries the part that does not fit the main post without spending its outbound l
---
-<a id="sec-550"></a>
+<a id="sec-551"></a>
> **Source:** `docs/x-posts/threews-avatar-video-script.md` · [↑ table of contents](#table-of-contents)
@@ -127245,7 +127301,7 @@ 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-549), the spoken lines live in
+[threews-avatar-launch.md](#sec-550), the spoken lines live in
[metaplex-agent-deployer-video-script.md](#sec-537), and the
deployer-specific shot list lives in [metaplex-agent-mcp-x-post.md](#sec-541).
@@ -127390,7 +127446,7 @@ Keep the pause after "It has no body." That silence is the whole premise.
---
-<a id="sec-551"></a>
+<a id="sec-552"></a>
> **Source:** `docs/x-posts/x-meetup-posts.md` · [↑ table of contents](#table-of-contents)
@@ -127447,13 +127503,13 @@ https://community.ibm.com/community/user/discussion/community-meetup-inside-thre
---
-<a id="sec-552"></a>
+<a id="sec-553"></a>
> **Source:** `docs/x402-buyer.md` · [↑ table of contents](#table-of-contents)
# x402 Buyer Client
-To consume a paid [x402 endpoint](#sec-555) — ours or anyone's — a
+To consume a paid [x402 endpoint](#sec-556) — 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
@@ -127543,13 +127599,13 @@ set) back into the payment so attribution survives the round trip.
## Related
-- [x402 protocol](#sec-559) — the underlying challenge/settle mechanics.
-- [x402 paid endpoints](#sec-555) — what you can buy from us.
+- [x402 protocol](#sec-560) — the underlying challenge/settle mechanics.
+- [x402 paid endpoints](#sec-556) — what you can buy from us.
- [Autonomous x402 loop](#sec-105) — uses this client on a schedule.
---
-<a id="sec-553"></a>
+<a id="sec-554"></a>
> **Source:** `docs/x402-dev-tools.md` · [↑ table of contents](#table-of-contents)
@@ -127761,13 +127817,13 @@ implementation against a live server.
---
-<a id="sec-554"></a>
+<a id="sec-555"></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-559). Building them is
+three.ws sells 90+ pay-per-call services over [x402](#sec-560). 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,
@@ -127982,24 +128038,24 @@ script. Everything else above updates itself.
## Related
-- [x402 overview](#sec-559) · [Paid endpoints reference](#sec-555) ·
- [Autonomous loop](#sec-105) · [Buyer client](#sec-552)
+- [x402 overview](#sec-560) · [Paid endpoints reference](#sec-556) ·
+ [Autonomous loop](#sec-105) · [Buyer client](#sec-553)
---
-<a id="sec-555"></a>
+<a id="sec-556"></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-559): the caller hits the endpoint, receives a `402 Payment Required`
+[x402](#sec-560): 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-552). For the loop
+To call these as a buyer, see [x402 buyer client](#sec-553). 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
@@ -128261,9 +128317,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-553). |
-| `/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-553). |
-| `/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-553). |
+| `/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-554). |
+| `/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-554). |
+| `/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-554). |
| `/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
@@ -128276,15 +128332,15 @@ input and do not promote any specific token.
## Related
- [Pump Launcher](#sec-348) — the full launch flow, inputs/outputs, and the free `symbol` → launch → `launches` funnel.
-- [x402 protocol](#sec-559) — the challenge/settle mechanics.
-- [x402 buyer client](#sec-552) — how to pay these endpoints in code.
+- [x402 protocol](#sec-560) — the challenge/settle mechanics.
+- [x402 buyer client](#sec-553) — how to pay these endpoints in code.
- [Financial controls](#sec-222): where settled payments are recorded.
- [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-556"></a>
+<a id="sec-557"></a>
> **Source:** `docs/x402-ring-economy.md` · [↑ table of contents](#table-of-contents)
@@ -129383,7 +129439,7 @@ activation runbook above is the fix.
---
-<a id="sec-557"></a>
+<a id="sec-558"></a>
> **Source:** `docs/x402-solana-july-roundup-response.md` · [↑ table of contents](#table-of-contents)
@@ -129442,7 +129498,7 @@ the specific claim the roundup credited us for. Second choice: the AR drop-in on
---
-<a id="sec-558"></a>
+<a id="sec-559"></a>
> **Source:** `docs/x402-studio.md` · [↑ table of contents](#table-of-contents)
@@ -129452,11 +129508,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-559) 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-560) 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-552) and the [paid endpoint catalog](#sec-555).
+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-553) and the [paid endpoint catalog](#sec-556).
## How it works
@@ -129542,16 +129598,16 @@ const { tx_base64, blockhash } = await res.json();
## Related
-- [x402: paid agent skills](#sec-559): the payment protocol Studio sits on top of
+- [x402: paid agent skills](#sec-560): the payment protocol Studio sits on top of
- [Financial controls](#sec-222): where settled payments are recorded
-- [x402 paid endpoints](#sec-555): the platform's own catalog of paid endpoints
-- [x402 buyer client](#sec-552): the caller side of a 402 challenge
-- [x402 developer tools](#sec-553) and [x402 distribution](#sec-554)
+- [x402 paid endpoints](#sec-556): the platform's own catalog of paid endpoints
+- [x402 buyer client](#sec-553): the caller side of a 402 challenge
+- [x402 developer tools](#sec-554) and [x402 distribution](#sec-555)
- Pages: [/x402/studio](https://three.ws/x402/studio) · [/x402](https://three.ws/x402)
---
-<a id="sec-559"></a>
+<a id="sec-560"></a>
> **Source:** `docs/x402.md` · [↑ table of contents](#table-of-contents)
@@ -129565,7 +129621,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-555).
+[x402 paid endpoints](#sec-556).
**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.
@@ -129726,15 +129782,15 @@ Each package has its own repository with a full README, API reference, and examp
## Related
-- [x402 paid endpoints](#sec-555) — the catalog of the platform's own paid endpoints.
+- [x402 paid endpoints](#sec-556) — the catalog of the platform's own paid endpoints.
- [Financial controls](#sec-222): where settled payments are recorded.
-- [x402 buyer client](#sec-552) — how to settle a 402 challenge in code.
+- [x402 buyer client](#sec-553) — 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-560"></a>
+<a id="sec-561"></a>
> **Source:** `docs/zauth/database.md` · [↑ table of contents](#table-of-contents)
@@ -129880,7 +129936,7 @@ Use this endpoint to browse all known x402 endpoints before your agents commit t
---
-<a id="sec-561"></a>
+<a id="sec-562"></a>
> **Source:** `docs/zauth/index.md` · [↑ table of contents](#table-of-contents)
@@ -129900,11 +129956,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-564)### [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-563)### [DatabaseLive registry of x402 endpoints. AI agents continuously test and verify endpoints, tracking success rates, pricing, and response data.Database](#sec-560)### [Provider HubManage your x402 endpoints. Monitor health, track agent interactions, configure refunds, and verify your services through our SDK.Provider Hub](#sec-562)
+### [VectorAI-powered vulnerability scanner. Automated recon, multi-category exploit testing, and detailed security reports for your web applications.Vector](#sec-565)### [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-564)### [DatabaseLive registry of x402 endpoints. AI agents continuously test and verify endpoints, tracking success rates, pricing, and response data.Database](#sec-561)### [Provider HubManage your x402 endpoints. Monitor health, track agent interactions, configure refunds, and verify your services through our SDK.Provider Hub](#sec-563)
---
-<a id="sec-562"></a>
+<a id="sec-563"></a>
> **Source:** `docs/zauth/provider-hub.md` · [↑ table of contents](#table-of-contents)
@@ -130006,7 +130062,7 @@ Supply your EVM or Solana private keys to enable automatic refunds when your end
---
-<a id="sec-563"></a>
+<a id="sec-564"></a>
> **Source:** `docs/zauth/reposcan.md` · [↑ table of contents](#table-of-contents)
@@ -130332,7 +130388,7 @@ TypeScript -@x402/fetch
---
-<a id="sec-564"></a>
+<a id="sec-565"></a>
> **Source:** `docs/zauth/vector.md` · [↑ table of contents](#table-of-contents)
diff --git a/docs/open-source-friday-plan.md b/docs/open-source-friday-plan.md
index 01f784864..b51bacfa5 100644
--- a/docs/open-source-friday-plan.md
+++ b/docs/open-source-friday-plan.md
@@ -5,6 +5,7 @@
**Program page:** https://github.com/githubevents/open-source-friday
**Criteria:** [admin/project-criteria.md](https://github.com/githubevents/open-source-friday/blob/main/admin/project-criteria.md)
**Request form:** https://github.com/githubevents/open-source-friday/issues/new?template=osf-guest-invite.yml
+**Our request:** https://github.com/githubevents/open-source-friday/issues/254 (opened 2026-08-25)
---
@@ -70,7 +71,7 @@ On 2026-08-21 the repo sat at 98. The call was to treat that as noise rather tha
---
-## 3. The issue: exact field-by-field content
+## 3. The issue: exact field-by-field content (submitted as [#254](https://github.com/githubevents/open-source-friday/issues/254))
The form (`osf-guest-invite.yml`) auto-titles as `Open Source Friday - [PROJECT NAME] - [MM-DD-YYYY]`, labels `open-source-friday, open-source, twitch, pending`, and assigns @AndreaGriffiths11, @KevinCrosby, @marlenezw, @madebygps. A date is not required to submit: check "Not yet" and they send the booking link on approval.
@@ -175,7 +176,8 @@ Every hard criterion is met, stars included. What remains is one click, polish,
| 2026-08-25 | Three seed Discussions posted (#122, #123, #124) | Done |
| 2026-08-25 | Pin #122 | Owner, one click |
| 2026-08-26 | README front door trimmed, demo clip recorded | Agent |
-| 2026-08-27 | **Issue submitted**, reply posted to Andrea's X thread | Owner |
+| 2026-08-25 | **Issue submitted**: [open-source-friday#254](https://github.com/githubevents/open-source-friday/issues/254) | Done |
+| 2026-08-25 | Reply to Andrea's X thread with the issue link (draft: [x-posts/osf-issue-reply.md](x-posts/osf-issue-reply.md)) | Owner |
| 2026-08-28+ | Booking link arrives on approval, book the slot | Owner |
| ~2026-09-11 | Stream (earliest date satisfying the two-week rule) | Owner |
diff --git a/docs/x-posts/README.md b/docs/x-posts/README.md
index 71b5703bc..6d9061841 100644
--- a/docs/x-posts/README.md
+++ b/docs/x-posts/README.md
@@ -45,6 +45,7 @@ explicit approval). Each file states what it's for and what has already been ver
| File | What it covers |
| --- | --- |
+| [`osf-issue-reply.md`](osf-issue-reply.md) | The reply to Andrea Griffiths closing the loop on the Open Source Friday request (open-source-friday#254), in a Premium-length and a 280-character form |
| [`event-x-posts.md`](event-x-posts.md) | Event campaign copy, split by account (`@trythreews` institutional, `@nichxbt` personal) |
| [`x-meetup-posts.md`](x-meetup-posts.md) | The in-platform community meetup announcement |
| [`ibm-skillsbuild-x-post.md`](ibm-skillsbuild-x-post.md) | The IBM SkillsBuild badge |
diff --git a/docs/x-posts/osf-issue-reply.md b/docs/x-posts/osf-issue-reply.md
new file mode 100644
index 000000000..6986ed718
--- /dev/null
+++ b/docs/x-posts/osf-issue-reply.md
@@ -0,0 +1,45 @@
+# Reply to Andrea: the Open Source Friday request is in
+
+**What it is for.** Andrea Griffiths (@acolombiadev, GitHub) replied to Nich's post on 2026-08-21 with "Hey Nich, please open an issue" and the program criteria. The issue is now open. This is the reply that closes that loop, posted as a reply in her thread, not as a fresh post, so it lands in front of her and the people who liked the exchange.
+
+**Verified true at time of writing (2026-08-25):**
+
+- The request issue exists: https://github.com/githubevents/open-source-friday/issues/254
+- The repo passes every hard criterion in their `project-criteria.md`: Contributor Covenant, contributing guide, Apache-2.0 license (GitHub detects it), 104 stars, six curated `good first issue`s, Discussions seeded, triage and onboarding docs published.
+- The reply carries no numbers that could go stale before she reads it except the star count, which only goes up.
+
+## The reply (reply to Andrea's "please open an issue" post)
+
+Post from @nichxbt.
+
+```
+Done: github.com/githubevents/open-source-friday/issues/254
+
+Since you asked, three.ws went Apache-2.0, crossed 100 stars, opened Discussions, and published a 15-minute clone-to-PR guide with a live good-first-issue list. The bit I want to do on air is a contributor adding a new rig convention, PR opened live.
+
+Thank you for the nudge.
+```
+
+Measured: 307 characters with the URL counted at 23. Under the 280 cap only for Premium accounts; if @nichxbt is not Premium, use the short form below.
+
+## Short form (fits 280 for a non-Premium account)
+
+```
+Done: github.com/githubevents/open-source-friday/issues/254
+
+Since you asked: three.ws went Apache-2.0, passed 100 stars, and opened Discussions. The segment I want to do on air is a contributor adding a rig convention, PR opened live.
+
+Thank you for the nudge.
+```
+
+Measured: 231 characters with the URL counted at 23.
+
+## Do not
+
+- Do not post it cold as a new tweet. It is a reply. The whole value is that it answers her in her thread.
+- Do not quote-post her. She asked a direct question; answer it directly.
+- Do not tag the other program maintainers. Our account has no triage rights on their repo, so the issue carries none of the template labels or assignees; this reply to Andrea is the notification, and she labels it on their side.
+
+## After it is posted
+
+Nothing. The next move is theirs: on approval they apply the `approved` label and a bot comments on #254 with the booking link. Book a Friday at least two weeks out (2026-09-11 is the first realistic one), then follow the stream runsheet in [../open-source-friday-plan.md](../open-source-friday-plan.md).