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: correct every page that still told readers the code was proprietary

nirholas5417fd5d9e5f
diff --git a/docs/ALL.md b/docs/ALL.md
index 4bf5ebbb1..8564bf0e4 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-20 from **549 files** (~7757 KB).
+> Single-file snapshot of every document under [`docs/`](.). Generated 2026-08-21 from **556 files** (~7831 KB).
> The individual source files remain the canonical, editable copies — this file is a read-only aggregate.
## Table of contents
@@ -97,230 +97,235 @@
- [coinmarketcap-article-play.md](#sec-148)
- [coinmarketcap-article.md](#sec-149)
- [coinmarketcap-live-article.md](#sec-150)
-- [compose.md](#sec-151)
-- [concierge.md](#sec-152)
-- [configuration.md](#sec-153)
-- [contributing.md](#sec-160)
-- [copy-trading.md](#sec-165)
-- [cosmos.md](#sec-166)
-- [creator-portfolio.md](#sec-167)
-- [crews.md](#sec-168)
-- [crypto-api.md](#sec-169)
-- [custody.md](#sec-170)
-- [daily-forge.md](#sec-171)
-- [daily-match.md](#sec-172)
-- [demo-routes.md](#sec-173)
-- [deployment.md](#sec-174)
-- [deployments.md](#sec-175)
-- [developer-platform.md](#sec-176)
-- [diorama.md](#sec-177)
-- [do-i-need-crypto.md](#sec-178)
-- [docs-world.md](#sec-179)
-- [draft-agent-mint.md](#sec-180)
-- [economy-heartbeat.md](#sec-181)
-- [economy-master.md](#sec-182)
-- [economy-solver.md](#sec-183)
-- [editor.md](#sec-184)
-- [education-pilot-bucharest.md](#sec-185)
-- [embedding.md](#sec-186)
-- [embody.md](#sec-187)
-- [erc8004.md](#sec-188)
-- [event-souvenirs.md](#sec-216)
-- [examples.md](#sec-217)
-- [exit-lab.md](#sec-218)
-- [fact-check.md](#sec-219)
-- [farcaster-memory-seeding.md](#sec-220)
-- [financial-controls.md](#sec-221)
-- [forge-background-generation.md](#sec-222)
-- [forge-off.md](#sec-223)
-- [forge-pipeline.md](#sec-224)
-- [forge.md](#sec-225)
-- [forged.md](#sec-226)
-- [free-crypto-apis.md](#sec-227)
-- [free-llm-providers.md](#sec-228)
-- [galaxy.md](#sec-229)
-- [generation-watch.md](#sec-230)
-- [genesis.md](#sec-231)
-- [genome.md](#sec-232)
-- [ghost-copy.md](#sec-233)
-- [github-memory-seeding.md](#sec-234)
-- [google-x-accounts.md](#sec-235)
-- [guardian.md](#sec-236)
-- [guards.md](#sec-237)
-- [hold-to-access.md](#sec-238)
-- [how-forge-works.md](#sec-239)
-- [how-it-works.md](#sec-240)
-- [i18n.md](#sec-241)
-- [ibm-community-article.md](#sec-242)
-- [ibm-community-blog-meetup-jessica.md](#sec-243)
-- [ibm-community-live-reaction-jessica.md](#sec-244)
-- [ibm-community-recap-jessica.md](#sec-245)
-- [ibm-community-recap-nichxbt.md](#sec-246)
-- [ibm-community-thread.md](#sec-247)
-- [ibm-community.md](#sec-248)
-- [ibm-x402-mcp.md](#sec-249)
-- [ibm.md](#sec-250)
-- [image-to-3d.md](#sec-251)
-- [in-game-economy.md](#sec-252)
-- [inference-node-operator.md](#sec-253)
-- [integrations.md](#sec-254)
-- [introduction.md](#sec-255)
-- [irl.md](#sec-256)
-- [js-api.md](#sec-258)
-- [kol-tracker.md](#sec-259)
-- [labor-market.md](#sec-260)
-- [launch-usecases.md](#sec-261)
-- [layers.md](#sec-262)
-- [likeness-eval.md](#sec-263)
-- [lipsync.md](#sec-264)
-- [listings.md](#sec-265)
-- [live-docs.md](#sec-266)
-- [live-steps.md](#sec-267)
-- [make-your-agent.md](#sec-268)
-- [market-data-api.md](#sec-269)
-- [marketplace.md](#sec-270)
-- [mcp-3d-studio.md](#sec-271)
-- [mcp-agent.md](#sec-272)
-- [mcp-safety.md](#sec-273)
-- [mcp-studio.md](#sec-274)
-- [mcp-tools.md](#sec-275)
-- [mcp-x402-bazaar.md](#sec-276)
-- [mcp.md](#sec-277)
-- [media-api.md](#sec-278)
-- [memetic-launcher.md](#sec-279)
-- [memory.md](#sec-280)
-- [meta-allocator.md](#sec-281)
-- [mint-mark.md](#sec-282)
-- [minted.md](#sec-283)
-- [mocap-studio.md](#sec-284)
-- [money-feed.md](#sec-285)
-- [money-flow-map.md](#sec-286)
-- [money-map.md](#sec-287)
-- [monitor.md](#sec-288)
-- [motion-swap.md](#sec-289)
-- [multi-agent.md](#sec-290)
-- [native-launchpad.md](#sec-291)
-- [news-rights.md](#sec-292)
-- [notifications.md](#sec-293)
-- [nvidia-apps-catalog-listing.md](#sec-294)
-- [nvidia-apps-catalog-request.md](#sec-295)
-- [nvidia-inception.md](#sec-296)
-- [nvidia-models.md](#sec-297)
-- [nvidia-nemotron-ask-the-experts-questions.md](#sec-298)
-- [nvidia-nemotron-spotlight.md](#sec-299)
-- [nvidia-visibility-map.md](#sec-300)
-- [object-library.md](#sec-301)
-- [okx-marketplace.md](#sec-302)
-- [onboarding-tier.md](#sec-303)
-- [onchain-agents.md](#sec-304)
-- [openai-listing-channels.md](#sec-305)
-- [oracle-trading-mcp-plan.md](#sec-314)
-- [oracle.md](#sec-315)
-- [overlay-audit.md](#sec-316)
-- [package-extraction.md](#sec-317)
-- [partners.md](#sec-318)
-- [pay-skills-listing.md](#sec-320)
-- [payment-sessions.md](#sec-321)
-- [permissions.md](#sec-322)
-- [persona-hub.md](#sec-323)
-- [plan-checkout.md](#sec-324)
-- [play-boot-performance.md](#sec-325)
-- [play-forge-in-world.md](#sec-326)
-- [play-hardening.md](#sec-327)
-- [play-live-events.md](#sec-328)
-- [play-vehicles.md](#sec-329)
-- [popular-3d-github-repos.md](#sec-330)
-- [portfolio.md](#sec-331)
-- [premium.md](#sec-332)
-- [press-kit.md](#sec-333)
-- [procedural-animation.md](#sec-334)
-- [provenance.md](#sec-335)
-- [pump-claims-channel.md](#sec-336)
-- [pump-fun-mcp-edge.md](#sec-337)
-- [pump-launch-repos.md](#sec-338)
-- [pump-launcher.md](#sec-339)
-- [pump-platform-fee.md](#sec-340)
-- [quick-start.md](#sec-361)
-- [radar.md](#sec-362)
-- [reasoning-ledger.md](#sec-363)
-- [recurring-payments.md](#sec-364)
-- [remix.md](#sec-365)
-- [reputation-staking-market.md](#sec-366)
-- [reputation.md](#sec-367)
-- [restyle.md](#sec-368)
-- [rig-doctor.md](#sec-369)
-- [risk-acknowledgment.md](#sec-370)
-- [robinhood-chain-markets.md](#sec-371)
-- [sas-attestations.md](#sec-372)
-- [scene-studio.md](#sec-373)
-- [sdk.md](#sec-374)
-- [security.md](#sec-375)
-- [seed-quality.md](#sec-376)
-- [selfie-to-avatar.md](#sec-377)
-- [share-and-embed.md](#sec-378)
-- [shared-utilities.md](#sec-379)
-- [showcase.md](#sec-380)
-- [sign-language.md](#sec-381)
-- [signals.md](#sec-382)
-- [site-performance.md](#sec-383)
-- [sketchfab.md](#sec-384)
-- [skill-bundles.md](#sec-385)
-- [skill-royalties.md](#sec-386)
-- [skills.md](#sec-387)
-- [smart-contracts.md](#sec-388)
-- [smart-money.md](#sec-389)
-- [sniper-autonomy.md](#sec-390)
-- [social-layer.md](#sec-391)
-- [solana-pumpfun.md](#sec-392)
-- [solana-reputation.md](#sec-393)
-- [solana.md](#sec-394)
-- [spatial-mcp.md](#sec-395)
-- [splat.md](#sec-397)
-- [stage.md](#sec-398)
-- [start-here.md](#sec-399)
-- [strategy-objects.md](#sec-400)
-- [swarms.md](#sec-401)
-- [syndication.md](#sec-402)
-- [talking-avatar-video.md](#sec-403)
-- [terminal.md](#sec-404)
-- [three-microbuy.md](#sec-405)
-- [timeline.md](#sec-406)
-- [token-gated-3d-embeds.md](#sec-407)
-- [tokens-xyz.md](#sec-408)
-- [trader-card.md](#sec-409)
-- [trader-passport.md](#sec-410)
-- [trading-arenas.md](#sec-411)
-- [trading-copilot.md](#sec-412)
-- [trading-experiment.md](#sec-413)
-- [trading-hub.md](#sec-414)
-- [trading-surfaces.md](#sec-415)
-- [troubleshooting.md](#sec-416)
-- [trust-primitives.md](#sec-417)
-- [ui-juice.md](#sec-487)
-- [user-wallet.md](#sec-488)
-- [validation.md](#sec-501)
-- [vanity.md](#sec-502)
-- [vaults.md](#sec-503)
-- [viability.md](#sec-504)
-- [viewer.md](#sec-505)
-- [voice-lab.md](#sec-506)
-- [walk-leaderboard.md](#sec-507)
-- [web-component.md](#sec-508)
-- [widget-api.md](#sec-509)
-- [widget-studio.md](#sec-510)
-- [widgets.md](#sec-511)
-- [world-lines.md](#sec-512)
-- [x-archive.md](#sec-513)
-- [x-memory-seeding.md](#sec-515)
-- [x402-buyer.md](#sec-536)
-- [x402-dev-tools.md](#sec-537)
-- [x402-distribution.md](#sec-538)
-- [x402-endpoints.md](#sec-539)
-- [x402-revenue.md](#sec-540)
-- [x402-ring-economy.md](#sec-541)
-- [x402-solana-july-roundup-response.md](#sec-542)
-- [x402-studio.md](#sec-543)
-- [x402.md](#sec-544)
+- [community.md](#sec-151)
+- [compose.md](#sec-152)
+- [concierge.md](#sec-153)
+- [configuration.md](#sec-154)
+- [contributing.md](#sec-161)
+- [copy-trading.md](#sec-167)
+- [cosmos.md](#sec-168)
+- [creator-portfolio.md](#sec-169)
+- [crews.md](#sec-170)
+- [crypto-api.md](#sec-171)
+- [custody.md](#sec-172)
+- [daily-forge.md](#sec-173)
+- [daily-match.md](#sec-174)
+- [demo-routes.md](#sec-175)
+- [deployment.md](#sec-176)
+- [deployments.md](#sec-177)
+- [developer-platform.md](#sec-178)
+- [diorama.md](#sec-179)
+- [do-i-need-crypto.md](#sec-180)
+- [docs-world.md](#sec-181)
+- [draft-agent-mint.md](#sec-182)
+- [economy-heartbeat.md](#sec-183)
+- [economy-master.md](#sec-184)
+- [economy-solver.md](#sec-185)
+- [editor.md](#sec-186)
+- [education-pilot-bucharest.md](#sec-187)
+- [embedding.md](#sec-188)
+- [embody.md](#sec-189)
+- [erc8004.md](#sec-190)
+- [event-souvenirs.md](#sec-218)
+- [examples.md](#sec-219)
+- [exit-lab.md](#sec-220)
+- [fact-check.md](#sec-221)
+- [farcaster-memory-seeding.md](#sec-222)
+- [financial-controls.md](#sec-223)
+- [first-contribution.md](#sec-224)
+- [forge-background-generation.md](#sec-225)
+- [forge-off.md](#sec-226)
+- [forge-pipeline.md](#sec-227)
+- [forge.md](#sec-228)
+- [forged.md](#sec-229)
+- [free-crypto-apis.md](#sec-230)
+- [free-llm-providers.md](#sec-231)
+- [galaxy.md](#sec-232)
+- [generation-watch.md](#sec-233)
+- [genesis.md](#sec-234)
+- [genome.md](#sec-235)
+- [ghost-copy.md](#sec-236)
+- [github-memory-seeding.md](#sec-237)
+- [google-x-accounts.md](#sec-238)
+- [guardian.md](#sec-239)
+- [guards.md](#sec-240)
+- [hold-to-access.md](#sec-241)
+- [how-forge-works.md](#sec-242)
+- [how-it-works.md](#sec-243)
+- [i18n.md](#sec-244)
+- [ibm-community-article.md](#sec-245)
+- [ibm-community-blog-meetup-jessica.md](#sec-246)
+- [ibm-community-live-reaction-jessica.md](#sec-247)
+- [ibm-community-recap-jessica.md](#sec-248)
+- [ibm-community-recap-nichxbt.md](#sec-249)
+- [ibm-community-thread.md](#sec-250)
+- [ibm-community.md](#sec-251)
+- [ibm-x402-mcp.md](#sec-252)
+- [ibm.md](#sec-253)
+- [image-to-3d.md](#sec-254)
+- [in-game-economy.md](#sec-255)
+- [inference-node-operator.md](#sec-256)
+- [integrations.md](#sec-257)
+- [introduction.md](#sec-258)
+- [irl.md](#sec-259)
+- [js-api.md](#sec-261)
+- [kol-tracker.md](#sec-262)
+- [labor-market.md](#sec-263)
+- [launch-usecases.md](#sec-264)
+- [layers.md](#sec-265)
+- [likeness-eval.md](#sec-266)
+- [lipsync.md](#sec-267)
+- [liquid-glass.md](#sec-268)
+- [listings.md](#sec-269)
+- [live-docs.md](#sec-270)
+- [live-steps.md](#sec-271)
+- [make-your-agent.md](#sec-272)
+- [market-data-api.md](#sec-273)
+- [marketplace.md](#sec-274)
+- [mcp-3d-studio.md](#sec-275)
+- [mcp-agent.md](#sec-276)
+- [mcp-safety.md](#sec-277)
+- [mcp-studio.md](#sec-278)
+- [mcp-tools.md](#sec-279)
+- [mcp-x402-bazaar.md](#sec-280)
+- [mcp.md](#sec-281)
+- [media-api.md](#sec-282)
+- [memetic-launcher.md](#sec-283)
+- [memory.md](#sec-284)
+- [meta-allocator.md](#sec-285)
+- [mint-mark.md](#sec-286)
+- [minted.md](#sec-287)
+- [mocap-studio.md](#sec-288)
+- [money-feed.md](#sec-289)
+- [money-flow-map.md](#sec-290)
+- [money-map.md](#sec-291)
+- [monitor.md](#sec-292)
+- [motion-swap.md](#sec-293)
+- [multi-agent.md](#sec-294)
+- [native-launchpad.md](#sec-295)
+- [news-rights.md](#sec-296)
+- [notifications.md](#sec-297)
+- [nvidia-apps-catalog-listing.md](#sec-298)
+- [nvidia-apps-catalog-request.md](#sec-299)
+- [nvidia-inception.md](#sec-300)
+- [nvidia-models.md](#sec-301)
+- [nvidia-nemotron-ask-the-experts-questions.md](#sec-302)
+- [nvidia-nemotron-spotlight.md](#sec-303)
+- [nvidia-visibility-map.md](#sec-304)
+- [object-library.md](#sec-305)
+- [okx-marketplace.md](#sec-306)
+- [onboarding-tier.md](#sec-307)
+- [onchain-agents.md](#sec-308)
+- [open-source-friday-plan.md](#sec-309)
+- [openai-listing-channels.md](#sec-310)
+- [oracle-trading-mcp-plan.md](#sec-319)
+- [oracle.md](#sec-320)
+- [overlay-audit.md](#sec-321)
+- [package-extraction.md](#sec-322)
+- [partners.md](#sec-323)
+- [pay-skills-listing.md](#sec-325)
+- [payment-sessions.md](#sec-326)
+- [permissions.md](#sec-327)
+- [persona-hub.md](#sec-328)
+- [plan-checkout.md](#sec-329)
+- [play-boot-performance.md](#sec-330)
+- [play-forge-in-world.md](#sec-331)
+- [play-hardening.md](#sec-332)
+- [play-live-events.md](#sec-333)
+- [play-vehicles.md](#sec-334)
+- [popular-3d-github-repos.md](#sec-335)
+- [portfolio.md](#sec-336)
+- [premium.md](#sec-337)
+- [press-kit.md](#sec-338)
+- [procedural-animation.md](#sec-339)
+- [provenance.md](#sec-340)
+- [pump-claims-channel.md](#sec-341)
+- [pump-fun-mcp-edge.md](#sec-342)
+- [pump-launch-repos.md](#sec-343)
+- [pump-launcher.md](#sec-344)
+- [pump-platform-fee.md](#sec-345)
+- [quick-start.md](#sec-366)
+- [radar.md](#sec-367)
+- [reasoning-ledger.md](#sec-368)
+- [recurring-payments.md](#sec-369)
+- [remix.md](#sec-370)
+- [reputation-staking-market.md](#sec-371)
+- [reputation.md](#sec-372)
+- [restyle.md](#sec-373)
+- [rig-doctor.md](#sec-374)
+- [risk-acknowledgment.md](#sec-375)
+- [robinhood-chain-markets.md](#sec-376)
+- [sas-attestations.md](#sec-377)
+- [scene-studio.md](#sec-378)
+- [sdk.md](#sec-379)
+- [security.md](#sec-380)
+- [seed-quality.md](#sec-381)
+- [selfie-to-avatar.md](#sec-382)
+- [share-and-embed.md](#sec-383)
+- [shared-utilities.md](#sec-384)
+- [showcase.md](#sec-385)
+- [sign-language.md](#sec-386)
+- [signals.md](#sec-387)
+- [site-performance.md](#sec-388)
+- [sketchfab.md](#sec-389)
+- [skill-bundles.md](#sec-390)
+- [skill-royalties.md](#sec-391)
+- [skills.md](#sec-392)
+- [smart-contracts.md](#sec-393)
+- [smart-money.md](#sec-394)
+- [sniper-autonomy.md](#sec-395)
+- [social-layer.md](#sec-396)
+- [solana-pumpfun.md](#sec-397)
+- [solana-reputation.md](#sec-398)
+- [solana.md](#sec-399)
+- [spatial-mcp.md](#sec-400)
+- [splat.md](#sec-402)
+- [stage.md](#sec-403)
+- [start-here.md](#sec-404)
+- [strategy-objects.md](#sec-405)
+- [swarms.md](#sec-406)
+- [syndication.md](#sec-407)
+- [talking-avatar-video.md](#sec-408)
+- [terminal.md](#sec-409)
+- [three-microbuy.md](#sec-410)
+- [timeline.md](#sec-411)
+- [token-gated-3d-embeds.md](#sec-412)
+- [tokens-xyz.md](#sec-413)
+- [trader-card.md](#sec-414)
+- [trader-passport.md](#sec-415)
+- [trading-arenas.md](#sec-416)
+- [trading-copilot.md](#sec-417)
+- [trading-experiment.md](#sec-418)
+- [trading-hub.md](#sec-419)
+- [trading-surfaces.md](#sec-420)
+- [triage.md](#sec-421)
+- [troubleshooting.md](#sec-422)
+- [trust-primitives.md](#sec-423)
+- [ui-juice.md](#sec-493)
+- [user-wallet.md](#sec-494)
+- [validation.md](#sec-507)
+- [vanity.md](#sec-508)
+- [vaults.md](#sec-509)
+- [viability.md](#sec-510)
+- [viewer.md](#sec-511)
+- [voice-lab.md](#sec-512)
+- [walk-leaderboard.md](#sec-513)
+- [web-component.md](#sec-514)
+- [widget-api.md](#sec-515)
+- [widget-studio.md](#sec-516)
+- [widgets.md](#sec-517)
+- [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)
### agent-abilities
@@ -397,220 +402,225 @@
### content
-- [content/use-cases/README.md](#sec-154)
-- [content/use-cases/ai-agent-developer.md](#sec-155)
-- [content/use-cases/brand-marketer.md](#sec-156)
-- [content/use-cases/crypto-community.md](#sec-157)
-- [content/use-cases/game-studio.md](#sec-158)
-- [content/use-cases/indie-creator.md](#sec-159)
+- [content/use-cases/README.md](#sec-155)
+- [content/use-cases/ai-agent-developer.md](#sec-156)
+- [content/use-cases/brand-marketer.md](#sec-157)
+- [content/use-cases/crypto-community.md](#sec-158)
+- [content/use-cases/game-studio.md](#sec-159)
+- [content/use-cases/indie-creator.md](#sec-160)
+
+### contributing
+
+- [contributing/discussion-seeds.md](#sec-162)
### cookbook
-- [cookbook/asset-quality-gate.md](#sec-161)
-- [cookbook/mcp-3d-tool.md](#sec-162)
-- [cookbook/parallel-asset-pack.md](#sec-163)
-- [cookbook/text-to-3d-cli.md](#sec-164)
+- [cookbook/asset-quality-gate.md](#sec-163)
+- [cookbook/mcp-3d-tool.md](#sec-164)
+- [cookbook/parallel-asset-pack.md](#sec-165)
+- [cookbook/text-to-3d-cli.md](#sec-166)
### erc8004
-- [erc8004/validation-attestation.md](#sec-189)
+- [erc8004/validation-attestation.md](#sec-191)
### event-readiness
-- [event-readiness/01-play-first-impression.md](#sec-190)
-- [event-readiness/02-play-mobile.md](#sec-191)
-- [event-readiness/03-play-performance.md](#sec-192)
-- [event-readiness/04-play-multiplayer-net.md](#sec-193)
-- [event-readiness/05-play-economy-loops.md](#sec-194)
-- [event-readiness/06-play-auth-errors.md](#sec-195)
-- [event-readiness/07-platform-smoke-sweep.md](#sec-196)
-- [event-readiness/08-api-production-health.md](#sec-197)
-- [event-readiness/09-accessibility-i18n.md](#sec-198)
-- [event-readiness/10-event-day-runbook.md](#sec-199)
-- [event-readiness/11-event-live-ops.md](#sec-200)
-- [event-readiness/12-photo-mode-share.md](#sec-201)
-- [event-readiness/13-event-quests-leaderboard.md](#sec-202)
-- [event-readiness/14-welcome-concierge.md](#sec-203)
-- [event-readiness/15-live-hype-feed.md](#sec-204)
-- [event-readiness/16-invite-flow.md](#sec-205)
-- [event-readiness/17-plaza-live-show.md](#sec-206)
-- [event-readiness/18-coin-wars-portal.md](#sec-207)
-- [event-readiness/19-forge-props-live.md](#sec-208)
-- [event-readiness/20-world-chat-scrollback.md](#sec-209)
-- [event-readiness/21-party-system.md](#sec-210)
-- [event-readiness/22-venue-projector-mode.md](#sec-211)
-- [event-readiness/23-signature-wall.md](#sec-212)
-- [event-readiness/24-dance-off.md](#sec-213)
-- [event-readiness/LIVE-OPS.md](#sec-214)
-- [event-readiness/README.md](#sec-215)
+- [event-readiness/01-play-first-impression.md](#sec-192)
+- [event-readiness/02-play-mobile.md](#sec-193)
+- [event-readiness/03-play-performance.md](#sec-194)
+- [event-readiness/04-play-multiplayer-net.md](#sec-195)
+- [event-readiness/05-play-economy-loops.md](#sec-196)
+- [event-readiness/06-play-auth-errors.md](#sec-197)
+- [event-readiness/07-platform-smoke-sweep.md](#sec-198)
+- [event-readiness/08-api-production-health.md](#sec-199)
+- [event-readiness/09-accessibility-i18n.md](#sec-200)
+- [event-readiness/10-event-day-runbook.md](#sec-201)
+- [event-readiness/11-event-live-ops.md](#sec-202)
+- [event-readiness/12-photo-mode-share.md](#sec-203)
+- [event-readiness/13-event-quests-leaderboard.md](#sec-204)
+- [event-readiness/14-welcome-concierge.md](#sec-205)
+- [event-readiness/15-live-hype-feed.md](#sec-206)
+- [event-readiness/16-invite-flow.md](#sec-207)
+- [event-readiness/17-plaza-live-show.md](#sec-208)
+- [event-readiness/18-coin-wars-portal.md](#sec-209)
+- [event-readiness/19-forge-props-live.md](#sec-210)
+- [event-readiness/20-world-chat-scrollback.md](#sec-211)
+- [event-readiness/21-party-system.md](#sec-212)
+- [event-readiness/22-venue-projector-mode.md](#sec-213)
+- [event-readiness/23-signature-wall.md](#sec-214)
+- [event-readiness/24-dance-off.md](#sec-215)
+- [event-readiness/LIVE-OPS.md](#sec-216)
+- [event-readiness/README.md](#sec-217)
### irl
-- [irl/THREAT-MODEL.md](#sec-257)
+- [irl/THREAT-MODEL.md](#sec-260)
### openai-pr
-- [openai-pr/00-START-HERE.md](#sec-306)
-- [openai-pr/01-orphan-widget-resolution.md](#sec-307)
-- [openai-pr/02-wellknown-manifest-conflict.md](#sec-308)
-- [openai-pr/03-forge-free-tier-truth.md](#sec-309)
-- [openai-pr/04-openai-surface-test-coverage.md](#sec-310)
-- [openai-pr/05-custom-gpt-openapi-serving.md](#sec-311)
-- [openai-pr/06-docs-accuracy-reconciliation.md](#sec-312)
-- [openai-pr/07-final-verification-and-submit.md](#sec-313)
+- [openai-pr/00-START-HERE.md](#sec-311)
+- [openai-pr/01-orphan-widget-resolution.md](#sec-312)
+- [openai-pr/02-wellknown-manifest-conflict.md](#sec-313)
+- [openai-pr/03-forge-free-tier-truth.md](#sec-314)
+- [openai-pr/04-openai-surface-test-coverage.md](#sec-315)
+- [openai-pr/05-custom-gpt-openapi-serving.md](#sec-316)
+- [openai-pr/06-docs-accuracy-reconciliation.md](#sec-317)
+- [openai-pr/07-final-verification-and-submit.md](#sec-318)
### partners
-- [partners/sperax-proposal.md](#sec-319)
+- [partners/sperax-proposal.md](#sec-324)
### pumpfun-program
-- [pumpfun-program/README.md](#sec-341)
-- [pumpfun-program/UPSTREAM-buy-sell-v2-announcement.md](#sec-342)
-- [pumpfun-program/UPSTREAM-pumpswap-virtual-quote-reserves.md](#sec-343)
-- [pumpfun-program/docs/BREAKING_FEE_RECIPIENT.md](#sec-344)
-- [pumpfun-program/docs/CPI_README.md](#sec-345)
-- [pumpfun-program/docs/FAQ.md](#sec-346)
-- [pumpfun-program/docs/FEE_PROGRAM_README.md](#sec-347)
-- [pumpfun-program/docs/FEE_RECIPIENTS.md](#sec-348)
-- [pumpfun-program/docs/PUMP_CASHBACK_README.md](#sec-349)
-- [pumpfun-program/docs/PUMP_CREATOR_FEE_README.md](#sec-350)
-- [pumpfun-program/docs/PUMP_PROGRAM_README.md](#sec-351)
-- [pumpfun-program/docs/PUMP_SWAP_CREATOR_FEE_README.md](#sec-352)
-- [pumpfun-program/docs/PUMP_SWAP_README.md](#sec-353)
-- [pumpfun-program/docs/PUMP_SWAP_SDK_README.md](#sec-354)
-- [pumpfun-program/docs/instructions/BUY.md](#sec-355)
-- [pumpfun-program/docs/instructions/CLAIM_CASHBACK.md](#sec-356)
-- [pumpfun-program/docs/instructions/COIN_CREATION.md](#sec-357)
-- [pumpfun-program/docs/instructions/COLLECT_CREATOR_FEE.md](#sec-358)
-- [pumpfun-program/docs/instructions/CREATOR_FEE_SHARING.md](#sec-359)
-- [pumpfun-program/docs/instructions/SELL.md](#sec-360)
+- [pumpfun-program/README.md](#sec-346)
+- [pumpfun-program/UPSTREAM-buy-sell-v2-announcement.md](#sec-347)
+- [pumpfun-program/UPSTREAM-pumpswap-virtual-quote-reserves.md](#sec-348)
+- [pumpfun-program/docs/BREAKING_FEE_RECIPIENT.md](#sec-349)
+- [pumpfun-program/docs/CPI_README.md](#sec-350)
+- [pumpfun-program/docs/FAQ.md](#sec-351)
+- [pumpfun-program/docs/FEE_PROGRAM_README.md](#sec-352)
+- [pumpfun-program/docs/FEE_RECIPIENTS.md](#sec-353)
+- [pumpfun-program/docs/PUMP_CASHBACK_README.md](#sec-354)
+- [pumpfun-program/docs/PUMP_CREATOR_FEE_README.md](#sec-355)
+- [pumpfun-program/docs/PUMP_PROGRAM_README.md](#sec-356)
+- [pumpfun-program/docs/PUMP_SWAP_CREATOR_FEE_README.md](#sec-357)
+- [pumpfun-program/docs/PUMP_SWAP_README.md](#sec-358)
+- [pumpfun-program/docs/PUMP_SWAP_SDK_README.md](#sec-359)
+- [pumpfun-program/docs/instructions/BUY.md](#sec-360)
+- [pumpfun-program/docs/instructions/CLAIM_CASHBACK.md](#sec-361)
+- [pumpfun-program/docs/instructions/COIN_CREATION.md](#sec-362)
+- [pumpfun-program/docs/instructions/COLLECT_CREATOR_FEE.md](#sec-363)
+- [pumpfun-program/docs/instructions/CREATOR_FEE_SHARING.md](#sec-364)
+- [pumpfun-program/docs/instructions/SELL.md](#sec-365)
### specs
-- [specs/agent-trading.md](#sec-396)
+- [specs/agent-trading.md](#sec-401)
### tutorials
-- [tutorials/add-a-3d-assistant.md](#sec-418)
-- [tutorials/agent-personality.md](#sec-419)
-- [tutorials/agent-reputation.md](#sec-420)
-- [tutorials/agent-spending-envelope.md](#sec-421)
-- [tutorials/animate-your-agent.md](#sec-422)
-- [tutorials/animate-your-avatar.md](#sec-423)
-- [tutorials/arm-an-agent-sniper.md](#sec-424)
-- [tutorials/build-a-3d-asset-pipeline.md](#sec-425)
-- [tutorials/build-a-scene.md](#sec-426)
-- [tutorials/build-a-site-concierge.md](#sec-427)
-- [tutorials/character-library-to-embed.md](#sec-428)
-- [tutorials/claim-threews-name.md](#sec-429)
-- [tutorials/connect-ai-brain.md](#sec-430)
-- [tutorials/create-and-edit-memory.md](#sec-431)
-- [tutorials/custom-skill.md](#sec-432)
-- [tutorials/customize-appearance.md](#sec-433)
-- [tutorials/deploy-to-vercel-custom-domain.md](#sec-434)
-- [tutorials/earn-and-spend-in-play.md](#sec-435)
-- [tutorials/embed-in-30-seconds.md](#sec-436)
-- [tutorials/embed-on-website.md](#sec-437)
-- [tutorials/emotion-from-data.md](#sec-438)
-- [tutorials/explore-docs-world.md](#sec-439)
-- [tutorials/find-a-better-exit-policy.md](#sec-440)
-- [tutorials/first-agent.md](#sec-441)
-- [tutorials/first-prompt-to-3d.md](#sec-442)
-- [tutorials/generate-3d-api.md](#sec-443)
-- [tutorials/getting-started.md](#sec-444)
-- [tutorials/greeting-and-first-speech.md](#sec-445)
-- [tutorials/image-to-3d.md](#sec-446)
-- [tutorials/import-avatar-url.md](#sec-447)
-- [tutorials/js-api-events.md](#sec-448)
-- [tutorials/mcp-server-for-your-agent.md](#sec-449)
-- [tutorials/mine-vanity-address.md](#sec-450)
-- [tutorials/mint-pumpfun-token.md](#sec-451)
-- [tutorials/monetize-mcp-server.md](#sec-452)
-- [tutorials/multi-agent-coordination.md](#sec-453)
-- [tutorials/nvidia-3d-free.md](#sec-454)
-- [tutorials/nvidia-nim-self-host.md](#sec-455)
-- [tutorials/paid-x402-endpoint.md](#sec-456)
-- [tutorials/pay-for-x402-service.md](#sec-457)
-- [tutorials/personal-ai-site.md](#sec-458)
-- [tutorials/place-agent-irl.md](#sec-459)
-- [tutorials/prompts-for-3d.md](#sec-460)
-- [tutorials/read-the-trading-fleet.md](#sec-461)
-- [tutorials/register-onchain.md](#sec-462)
-- [tutorials/render-avatar-images.md](#sec-463)
-- [tutorials/self-host-agent-backend.md](#sec-464)
-- [tutorials/selfie-to-avatar.md](#sec-465)
-- [tutorials/sell-a-skill-with-a-trial.md](#sec-466)
-- [tutorials/share-your-agent.md](#sec-467)
-- [tutorials/ship-an-avatar-manifest.md](#sec-468)
-- [tutorials/shopify-shopping-assistant.md](#sec-469)
-- [tutorials/shopify-store-guide-advanced.md](#sec-470)
-- [tutorials/shopify-store-guide.md](#sec-471)
-- [tutorials/sign-with-your-avatar.md](#sec-472)
-- [tutorials/skill-with-database-auth.md](#sec-473)
-- [tutorials/solana-agent-reputation.md](#sec-474)
-- [tutorials/sperax-tour.md](#sec-475)
-- [tutorials/swap-avatar-in-studio.md](#sec-476)
-- [tutorials/text-to-3d.md](#sec-477)
-- [tutorials/trigger-from-page-events.md](#sec-478)
-- [tutorials/upload-custom-glb.md](#sec-479)
-- [tutorials/view-in-ar.md](#sec-480)
-- [tutorials/voice-and-lipsync.md](#sec-481)
-- [tutorials/walk-companion.md](#sec-482)
-- [tutorials/wallet-sign-in.md](#sec-483)
-- [tutorials/web-component-end-to-end.md](#sec-484)
-- [tutorials/write-a-guard.md](#sec-485)
-- [tutorials/x402-server-sdk.md](#sec-486)
+- [tutorials/add-a-3d-assistant.md](#sec-424)
+- [tutorials/agent-personality.md](#sec-425)
+- [tutorials/agent-reputation.md](#sec-426)
+- [tutorials/agent-spending-envelope.md](#sec-427)
+- [tutorials/animate-your-agent.md](#sec-428)
+- [tutorials/animate-your-avatar.md](#sec-429)
+- [tutorials/arm-an-agent-sniper.md](#sec-430)
+- [tutorials/build-a-3d-asset-pipeline.md](#sec-431)
+- [tutorials/build-a-scene.md](#sec-432)
+- [tutorials/build-a-site-concierge.md](#sec-433)
+- [tutorials/character-library-to-embed.md](#sec-434)
+- [tutorials/claim-threews-name.md](#sec-435)
+- [tutorials/connect-ai-brain.md](#sec-436)
+- [tutorials/create-and-edit-memory.md](#sec-437)
+- [tutorials/custom-skill.md](#sec-438)
+- [tutorials/customize-appearance.md](#sec-439)
+- [tutorials/deploy-to-vercel-custom-domain.md](#sec-440)
+- [tutorials/earn-and-spend-in-play.md](#sec-441)
+- [tutorials/embed-in-30-seconds.md](#sec-442)
+- [tutorials/embed-on-website.md](#sec-443)
+- [tutorials/emotion-from-data.md](#sec-444)
+- [tutorials/explore-docs-world.md](#sec-445)
+- [tutorials/find-a-better-exit-policy.md](#sec-446)
+- [tutorials/first-agent.md](#sec-447)
+- [tutorials/first-prompt-to-3d.md](#sec-448)
+- [tutorials/generate-3d-api.md](#sec-449)
+- [tutorials/getting-started.md](#sec-450)
+- [tutorials/greeting-and-first-speech.md](#sec-451)
+- [tutorials/image-to-3d.md](#sec-452)
+- [tutorials/import-avatar-url.md](#sec-453)
+- [tutorials/js-api-events.md](#sec-454)
+- [tutorials/mcp-server-for-your-agent.md](#sec-455)
+- [tutorials/mine-vanity-address.md](#sec-456)
+- [tutorials/mint-pumpfun-token.md](#sec-457)
+- [tutorials/monetize-mcp-server.md](#sec-458)
+- [tutorials/multi-agent-coordination.md](#sec-459)
+- [tutorials/nvidia-3d-free.md](#sec-460)
+- [tutorials/nvidia-nim-self-host.md](#sec-461)
+- [tutorials/paid-x402-endpoint.md](#sec-462)
+- [tutorials/pay-for-x402-service.md](#sec-463)
+- [tutorials/personal-ai-site.md](#sec-464)
+- [tutorials/place-agent-irl.md](#sec-465)
+- [tutorials/prompts-for-3d.md](#sec-466)
+- [tutorials/read-the-trading-fleet.md](#sec-467)
+- [tutorials/register-onchain.md](#sec-468)
+- [tutorials/render-avatar-images.md](#sec-469)
+- [tutorials/self-host-agent-backend.md](#sec-470)
+- [tutorials/selfie-to-avatar.md](#sec-471)
+- [tutorials/sell-a-skill-with-a-trial.md](#sec-472)
+- [tutorials/share-your-agent.md](#sec-473)
+- [tutorials/ship-an-avatar-manifest.md](#sec-474)
+- [tutorials/shopify-shopping-assistant.md](#sec-475)
+- [tutorials/shopify-store-guide-advanced.md](#sec-476)
+- [tutorials/shopify-store-guide.md](#sec-477)
+- [tutorials/sign-with-your-avatar.md](#sec-478)
+- [tutorials/skill-with-database-auth.md](#sec-479)
+- [tutorials/solana-agent-reputation.md](#sec-480)
+- [tutorials/sperax-tour.md](#sec-481)
+- [tutorials/swap-avatar-in-studio.md](#sec-482)
+- [tutorials/text-to-3d.md](#sec-483)
+- [tutorials/trigger-from-page-events.md](#sec-484)
+- [tutorials/upload-custom-glb.md](#sec-485)
+- [tutorials/view-in-ar.md](#sec-486)
+- [tutorials/voice-and-lipsync.md](#sec-487)
+- [tutorials/walk-companion.md](#sec-488)
+- [tutorials/wallet-sign-in.md](#sec-489)
+- [tutorials/web-component-end-to-end.md](#sec-490)
+- [tutorials/write-a-guard.md](#sec-491)
+- [tutorials/x402-server-sdk.md](#sec-492)
### ux-flows
-- [ux-flows/01-onboarding-creation.md](#sec-489)
-- [ux-flows/02-forge-text-to-3d.md](#sec-490)
-- [ux-flows/03-3d-editing-viewer.md](#sec-491)
-- [ux-flows/04-embed-widget-studio.md](#sec-492)
-- [ux-flows/05-discovery-social.md](#sec-493)
-- [ux-flows/06-marketplace-skills.md](#sec-494)
-- [ux-flows/07-crypto-trading-analytics.md](#sec-495)
-- [ux-flows/08-coin-launch-wallets.md](#sec-496)
-- [ux-flows/09-x402-agent-commerce.md](#sec-497)
-- [ux-flows/10-chat-brain-labs.md](#sec-498)
-- [ux-flows/11-account-dashboard.md](#sec-499)
-- [ux-flows/12-home-and-content.md](#sec-500)
+- [ux-flows/01-onboarding-creation.md](#sec-495)
+- [ux-flows/02-forge-text-to-3d.md](#sec-496)
+- [ux-flows/03-3d-editing-viewer.md](#sec-497)
+- [ux-flows/04-embed-widget-studio.md](#sec-498)
+- [ux-flows/05-discovery-social.md](#sec-499)
+- [ux-flows/06-marketplace-skills.md](#sec-500)
+- [ux-flows/07-crypto-trading-analytics.md](#sec-501)
+- [ux-flows/08-coin-launch-wallets.md](#sec-502)
+- [ux-flows/09-x402-agent-commerce.md](#sec-503)
+- [ux-flows/10-chat-brain-labs.md](#sec-504)
+- [ux-flows/11-account-dashboard.md](#sec-505)
+- [ux-flows/12-home-and-content.md](#sec-506)
### x-archive
-- [x-archive/trythreews-engagement.md](#sec-514)
+- [x-archive/trythreews-engagement.md](#sec-520)
### x-posts
-- [x-posts/3d-ar-studio-launch.md](#sec-516)
-- [x-posts/3d-ar-studio-video-script.md](#sec-517)
-- [x-posts/README.md](#sec-518)
-- [x-posts/event-x-posts.md](#sec-519)
-- [x-posts/fomo-verified-x-post.md](#sec-520)
-- [x-posts/ibm-skillsbuild-x-post.md](#sec-521)
-- [x-posts/mcp-registry-fleet-x-post.md](#sec-522)
-- [x-posts/metaplex-agent-deployer-video-script.md](#sec-523)
-- [x-posts/metaplex-agent-deployer-x-post.md](#sec-524)
-- [x-posts/metaplex-agent-mcp-launch.md](#sec-525)
-- [x-posts/metaplex-agent-mcp-veo-script.md](#sec-526)
-- [x-posts/metaplex-agent-mcp-x-post.md](#sec-527)
-- [x-posts/news-archive-x-post.md](#sec-528)
-- [x-posts/onchain-agent-wallets-x-post.md](#sec-529)
-- [x-posts/oracle-trading-mcp-x-post.md](#sec-530)
-- [x-posts/pumpfun-article-x-post.md](#sec-531)
-- [x-posts/sperax-staking-in-chat-x-post.md](#sec-532)
-- [x-posts/threews-avatar-launch.md](#sec-533)
-- [x-posts/threews-avatar-video-script.md](#sec-534)
-- [x-posts/x-meetup-posts.md](#sec-535)
+- [x-posts/3d-ar-studio-launch.md](#sec-522)
+- [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)
### zauth
-- [zauth/database.md](#sec-545)
-- [zauth/index.md](#sec-546)
-- [zauth/provider-hub.md](#sec-547)
-- [zauth/reposcan.md](#sec-548)
-- [zauth/vector.md](#sec-549)
+- [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)
---
@@ -1176,7 +1186,7 @@ If you just want to add one animation or upload one avatar, the task guides are
- [docs/animations.md](#sec-093) — the animation registry, runtime loading, and agent slots.
- [docs/avatar-creation.md](#sec-109) — the three ways to create an avatar (photo, builder, upload).
-- [docs/tutorials/upload-custom-glb.md](#sec-479) — Mixamo → GLB, validation, and the common failure modes.
+- [docs/tutorials/upload-custom-glb.md](#sec-485) — Mixamo → GLB, validation, and the common failure modes.
This document is the *why and how* underneath all of those.
@@ -1495,11 +1505,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-544) resource: an AI agent pays a few cents in USDC, hands in a URL,
+own [x402](#sec-551) 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-539); the stages below are what you do to
+3D) is [`/api/x402/forge`](#sec-546); the stages below are what you do to
a mesh *after* it exists.
```
@@ -1512,7 +1522,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-539).
+2. **The whole chain in one call** — [`POST /api/x402/pipeline`](#sec-546).
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
@@ -1575,7 +1585,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-536).
+[x402 buyer client](#sec-543).
## Stages
@@ -1734,8 +1744,8 @@ returned as-is. Poll budget is tunable via `X402_PIPELINE_POLL_BUDGET_MS`
## Related
-- [x402 paid endpoints](#sec-539) — the full catalog + pricing model
-- [x402 buyer client](#sec-536) — how to settle payments as an agent
+- [x402 paid endpoints](#sec-546) — the full catalog + pricing model
+- [x402 buyer client](#sec-543) — how to settle payments as an agent
- [Avatar pipeline](#sec-113) — the generation + rig lanes in depth
---
@@ -2190,8 +2200,8 @@ Product and developer documentation for three.ws. Individual docs are served on
Start points:
-- [start-here.md](#sec-399): the front door for both creators and developers, with the reference shelf at the bottom.
-- [introduction.md](#sec-255) and [quick-start.md](#sec-361): the developer track.
+- [start-here.md](#sec-404): the front door for both creators and developers, with the reference shelf at the bottom.
+- [introduction.md](#sec-258) and [quick-start.md](#sec-366): the developer track.
- [ALL.md](ALL.md): generated single-file aggregate of the public docs (regenerate with `node scripts/combine-docs.mjs`; edit source files, never ALL.md).
- [api-reference.md](#sec-096): the REST API surface, with dedicated docs for the larger API families (crypto, 3D, market data, MCP).
@@ -2225,7 +2235,7 @@ leaves behind, and how to stop an agent that has gone wrong.
> [`scripts/a2a-spend-hardening-proof.mjs`](../scripts/a2a-spend-hardening-proof.mjs).
Related: [the agent wallet control API](#sec-071) for the other
-owner-only wallet surfaces, [financial controls](#sec-221) for
+owner-only wallet surfaces, [financial controls](#sec-223) for
the platform-wide picture, and [agent economy volume](#sec-052)
for what settled A2A payments add up to.
@@ -2585,7 +2595,7 @@ or task to the AgenC program. The write paths that do exist live elsewhere:
Treat this page's REST surface as **discovery + identity correlation**. For the
other writable on-chain identity, minting agents as Metaplex Core NFTs, see
-[Deploy agents on-chain (bulk)](#sec-304).
+[Deploy agents on-chain (bulk)](#sec-308).
## Relationship to Agora
@@ -2598,8 +2608,8 @@ AgenC endpoints here are the read/identity side.
## Related
- [Agora](#sec-075) — the economy and write lifecycle on top of AgenC.
-- [Agent reputation](#sec-056), [ERC-8004](#sec-188).
-- [Deploy agents on-chain (bulk)](#sec-304).
+- [Agent reputation](#sec-056), [ERC-8004](#sec-190).
+- [Deploy agents on-chain (bulk)](#sec-308).
---
@@ -13625,7 +13635,7 @@ would hide it.
## Related
-- [x402 revenue and receipts](#sec-540): the other side of the ledger. This
+- [x402 revenue and receipts](#sec-547): 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.
@@ -13662,7 +13672,7 @@ One completed job produces:
| `full_body[]` | Three 1024x1280 (4:5 portrait) renders, one per pose, same backdrop and lighting |
| `rigged_glb_url` | The avatar with a humanoid skeleton and skin weights |
| `mesh_glb_url` | The unrigged generated mesh, kept so a rig hiccup never loses the generation |
-| `viewer_url` | Deep link into the three.ws [viewer](#sec-505) for the rigged GLB |
+| `viewer_url` | Deep link into the three.ws [viewer](#sec-511) for the rigged GLB |
| `pose_studio_url` | Deep link into the [Animation Studio](#sec-092) for the rigged GLB |
Every render is persisted to object storage under `okx-identity/renders/<job>/` and served from a public URL, so the URLs in the response are permanent and hotlinkable.
@@ -13842,13 +13852,13 @@ Two environment overrides help a batch run outlast the rig lane's rate-limit bac
## Related
-- [OKX.AI Marketplace Services](#sec-302): the price, the payment challenge, the replay flow, the payment guarantees, and the decomposed single-capability 3D services that share these engines.
-- [Forge](#sec-225): the text and image to GLB generation pipeline this studio calls for the mesh and the auto-rig.
+- [OKX.AI Marketplace Services](#sec-306): the price, the payment challenge, the replay flow, the payment guarantees, and the decomposed single-capability 3D services that share these engines.
+- [Forge](#sec-228): the text and image to GLB generation pipeline this studio calls for the mesh and the auto-rig.
- [Animation Studio](#sec-092): the `/pose` surface the `pose_studio_url` deep link opens.
-- [Viewer](#sec-505): the `/viewer` surface the `viewer_url` deep link opens.
-- [MCP servers](#sec-277): the wider set of three.ws MCP endpoints this one follows the transport conventions of.
+- [Viewer](#sec-511): the `/viewer` surface the `viewer_url` deep link opens.
+- [MCP servers](#sec-281): the wider set of three.ws MCP endpoints this one follows the transport conventions of.
- [Avatar Engines Atlas](#sec-110): what engine families exist for building human avatars, and which of them are wired into the commercial pipeline.
-- [Draft agent mint](#sec-180): the inactive on-chain identity minted for every finished reconstruction, Solana first with ERC-8004 alongside it.
+- [Draft agent mint](#sec-182): the inactive on-chain identity minted for every finished reconstruction, Solana first with ERC-8004 alongside it.
---
@@ -14008,8 +14018,8 @@ asks whether the job ran.
| Both crawl crons | [`api/cron/`](../api/cron) |
| Regression cover | [`tests/agent-index.test.js`](../tests/agent-index.test.js) |
-Related: [Trust primitives](#sec-417) scores an agent from on-chain
-evidence, and [Custody you can verify](#sec-170) covers the attestations the
+Related: [Trust primitives](#sec-423) scores an agent from on-chain
+evidence, and [Custody you can verify](#sec-172) covers the attestations the
`reputation` and `validation` classes carry.
---
@@ -14661,7 +14671,7 @@ Load from on-chain:
A manifest served from an API is a claim. A manifest that is **signed and pinned to IPFS** is evidence: anyone can fetch the CID, check the signature, and read the exact system prompt the agent was configured with, without an account and without trusting three.ws.
-three.ws signs and pins an agent's manifest automatically on every persona save. The envelope is ed25519-signed by the platform attester identity (the same Solana key behind [3D provenance credentials](#sec-335)) and pinned through the configured IPFS provider.
+three.ws signs and pins an agent's manifest automatically on every persona save. The envelope is ed25519-signed by the platform attester identity (the same Solana key behind [3D provenance credentials](#sec-340)) and pinned through the configured IPFS provider.
### What a signed envelope looks like
@@ -14818,7 +14828,7 @@ The `spec` field identifies the manifest format version. Current stable: `agent-
- [Memory Spec](../specs/MEMORY_SPEC.md) — memory file format and MEMORY.md index
- [Embed Spec](../specs/EMBED_SPEC.md) — `<agent-3d>` element attributes and events
- [Permissions Spec](../specs/PERMISSIONS_SPEC.md) — ERC-7710 delegation format and redemption
-- [Provenance](#sec-335) — signed content credentials for generated 3D assets, using the same attester identity as signed manifests
+- [Provenance](#sec-340) — signed content credentials for generated 3D assets, using the same attester identity as signed manifests
---
@@ -14830,7 +14840,7 @@ The `spec` field identifies the manifest format version. Current stable: `agent-
**Why autonomous agents need verifiable trust — and how three.ws delivers it on-chain.**
-This page is the *why*. For the practical how-to, see [Reputation System](#sec-367) (leaving and reading reviews) and [ERC-8004](#sec-188) (the identity standard underneath). To read a real agent's score five different ways, follow the [Read an agent's reputation](/tutorials/agent-reputation) tutorial. For the Solana side of the same idea — memo attestations, the AgenC coordination program, and the identity bridge — see [Agent Reputation on Solana](#sec-393).
+This page is the *why*. For the practical how-to, see [Reputation System](#sec-372) (leaving and reading reviews) and [ERC-8004](#sec-190) (the identity standard underneath). To read a real agent's score five different ways, follow the [Read an agent's reputation](/tutorials/agent-reputation) tutorial. For the Solana side of the same idea — memo attestations, the AgenC coordination program, and the identity bridge — see [Agent Reputation on Solana](#sec-398).
---
@@ -14894,7 +14904,7 @@ Each agent is an NFT; whoever owns the token controls the agent. The token point
A reserved, signature-gated field binds a verified payment wallet to the agent (proven with an EIP-712 signature, and cleared automatically if the NFT is transferred).
-> Full detail: [ERC-8004](#sec-188).
+> Full detail: [ERC-8004](#sec-190).
### 2. Reputation Registry — what others think of it
@@ -14923,7 +14933,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-544)).
+3. **Pay** — the service answers an HTTP `402` and the agent signs a stablecoin micropayment ([x402](#sec-551)).
4. **Vouch** — after the work, write feedback back to the Reputation Registry, closing the loop for the next agent.
The one-liner worth remembering:
@@ -14944,7 +14954,7 @@ The same on-chain data is exposed through every layer a reader might come from:
| Reputation panel | agent profiles | The embedded vouch/score widget on `https://three.ws/a/<chainId>/<agentId>` |
| `GET /api/agents/<id>/reputation` | apps | The agent's unified wallet trust score: a 0-100 credibility number derived from real ledger and on-chain activity, with a per-pillar breakdown and evidence links |
| `agent_reputation` MCP tool | AI agents | Paid ($0.01 USDC) read of identity + score + stake + recent events; resolves a wallet to its agent automatically |
-| `GET /api/x402/agent-reputation` | AI agents | Paid ($0.01) cross-chain 0–100 trust score for **any** counterparty — Solana/EVM wallet, pump.fun mint, ERC-8004 agent id, or three.ws agent_id (auto-detected). See [Trust primitives](#sec-417) |
+| `GET /api/x402/agent-reputation` | AI agents | Paid ($0.01) cross-chain 0–100 trust score for **any** counterparty — Solana/EVM wallet, pump.fun mint, ERC-8004 agent id, or three.ws agent_id (auto-detected). See [Trust primitives](#sec-423) |
| [Agent Passport](/agent-passport.html) | trust decisions | An A–D trust grade weighted toward credentialed and verified feedback |
| ERC-8004 helpers (`src/erc8004/reputation.js`; ABIs re-exported by `@three-ws/sdk`) | developers | `getReputation`, `getRecentReviews`, `getTotalStake`, `submitFeedback`, `stakeReputation` |
@@ -14983,7 +14993,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-393) · [Leave a vouch](#sec-367) · [ERC-8004 identity](#sec-188) · [x402 payments](#sec-544)
+**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)
---
@@ -15417,7 +15427,7 @@ relationship into an account with a real agent. Ambient discovery routes
through the agent too — the old "have you tried…" toast stays out of the corner
while the companion is live.
-Related: [web-component.md](#sec-508) (the embeddable `agent-3d`
+Related: [web-component.md](#sec-514) (the embeddable `agent-3d`
avatar), [coin-pages.md](#sec-145) (the market surfaces the shell
navigates), [STRUCTURE.md](../STRUCTURE.md) (surface map).
@@ -15434,7 +15444,7 @@ Claude surface — Claude Code, the Claude apps, the Agent SDK — how to use th
three.ws platform: create and rig 3D models, run a wallet, and buy/sell services in
the x402 agent economy.
-> Not to be confused with the [in-app skills system](#sec-387), which extends
+> Not to be confused with the [in-app skills system](#sec-392), which extends
> avatars and agents **inside** three.ws with `manifest.json` + `tools.json` +
> `handlers.js` bundles. Agent Skills are the inverse: they extend **external**
> AI agents with three.ws capabilities.
@@ -15553,7 +15563,7 @@ Every three.ws agent has its own custodial Solana wallet. The Agent Sniper is th
This doc explains the whole system, walks through the first live trade an agent closed on the platform (a real +42.38% exit, receipts included), and lays out where the system goes next.
-Related surfaces: [the trading surfaces](#sec-415) (Radar, Coin Intelligence, Mission Control), [trading experiment](#sec-413) (the laddered-exit research policy), [agent wallets](#sec-072) (how custody works), and the worker itself at `workers/agent-sniper/` (its README is the operator reference).
+Related surfaces: [the trading surfaces](#sec-420) (Radar, Coin Intelligence, Mission Control), [trading experiment](#sec-418) (the laddered-exit research policy), [agent wallets](#sec-072) (how custody works), and the worker itself at `workers/agent-sniper/` (its README is the operator reference).
---
@@ -15703,8 +15713,8 @@ The direction of every bridge is the same: real, realized money is the ground tr
## Try it
- Arm your first strategy: [the sniper tutorial](/tutorials/arm-an-agent-sniper)
-- Watch the engine think: [Coin Intelligence and the trading surfaces](#sec-415)
-- The research policy behind laddered exits: [trading experiment](#sec-413)
+- Watch the engine think: [Coin Intelligence and the trading surfaces](#sec-420)
+- The research policy behind laddered exits: [trading experiment](#sec-418)
- The story of the first trade, for non-operators: [the blog post](/blog/first-autonomous-trade)
---
@@ -15730,7 +15740,7 @@ An agent is not one thing; it is a brain, a memory, a body, a wallet, and a set
skills, and until now each of those lived on a different page. Agent Studio unifies
them into one workspace so you can see the whole agent at once and watch changes take
effect immediately. It is the deep-authoring counterpart to the fast on-ramp in
-[Instant Agent Genesis](#sec-231): Genesis gets you a complete agent in a minute,
+[Instant Agent Genesis](#sec-234): Genesis gets you a complete agent in a minute,
Studio is where you make it exactly what you want. For the broader model of what an
agent is, see [Agent System](#sec-064).
@@ -15831,7 +15841,7 @@ curl -s https://three.ws/api/agents/<agent-id>/pricing \
## Related
- [Agent System](#sec-064): the full model of what an agent is
-- [Instant Agent Genesis](#sec-231): create the agent Studio edits
+- [Instant Agent Genesis](#sec-234): create the agent Studio edits
- [Multi-LLM Brain](#sec-130): the model backend behind the Brain tab
- [Agent Skills](#sec-060): the capabilities the Skills tab manages
- [Agent Wallets](#sec-072): the wallet behind the Money tab
@@ -15867,7 +15877,7 @@ user gesture. Nothing autoplays.
## Where the events come from
The symphony consumes the same live ticker documented in
-[Money Feed](#sec-285):
+[Money Feed](#sec-289):
1. `GET /api/feed?limit=40` paints the initial ledger (played silently as
backlog, not as notes).
@@ -15883,7 +15893,7 @@ you hear.
## What sounds map to what events
Every allow-listed feed type (see the type table in
-[Money Feed](#sec-285)) maps to one of six voices in
+[Money Feed](#sec-289)) maps to one of six voices in
`TYPE_TO_CATEGORY` in [`src/symphony-score.js`](../src/symphony-score.js).
Each voice has its own synth patch in the engine, its own color in the
visualization, and its own mute button in the legend.
@@ -15985,7 +15995,7 @@ cross-links are asserted statically by
## Related
-- [Money Feed](#sec-285): the activity bus this page renders, including
+- [Money Feed](#sec-289): the activity bus this page renders, including
the full event-type table and how events are published.
- [Agora](#sec-075): the on-chain economy lifecycle behind the `agora-*`
events.
@@ -16183,7 +16193,7 @@ Captures what is currently visible and describes it so the agent can react to wh
### Stage-scoped tools
-When the runtime is attached to an `<agent-stage>`, two extra tools are appended (see [multi-agent.md](#sec-290)): `observe_agents` (list the other agents on stage with names and positions) and `say_to_agent` (send a message to a named stagemate).
+When the runtime is attached to an `<agent-stage>`, two extra tools are appended (see [multi-agent.md](#sec-294)): `observe_agents` (list the other agents on stage with names and positions) and `say_to_agent` (send a message to a named stagemate).
---
@@ -16903,7 +16913,7 @@ POST /api/pump/launch-agent { "agent_id": "…", "name": "…", "symbol": "…"
```
This is the path that supports USDC-paired curves and binds the on-chain pump
-agent for buybacks. See [the pump.fun launcher](#sec-339).
+agent for buybacks. See [the pump.fun launcher](#sec-344).
Both paths write a `pump_agent_mints` row and call back into the plan to mark it
launched, so a coin appears on [/launches](https://three.ws/launches), in the
@@ -16977,10 +16987,10 @@ doubles as a check on the lane.
## Related
-- [The pump.fun launcher](#sec-339): the launch transaction itself
+- [The pump.fun launcher](#sec-344): the launch transaction itself
- [Coin launches](#sec-144): the platform launch directory
-- [Platform fee](#sec-340): what three.ws takes on a launch
-- [Solana on pump.fun](#sec-392): the on-chain program surface
+- [Platform fee](#sec-345): what three.ws takes on a launch
+- [Solana on pump.fun](#sec-397): the on-chain program surface
Note on promotion: `$THREE` is the coin three.ws promotes. Agent tokens are coins
users launch through the platform, rendered from the platform's own launch
@@ -16999,9 +17009,9 @@ Every three.ws agent owns one custodial **Solana** wallet. Seven owner-only HTTP
This document is the API reference the surrounding docs deliberately leave out. Read those first for the "why":
- [Agent wallets](#sec-072) for how the wallet is created, how its key is held, and which paths may spend.
-- [Custody you can verify](#sec-170) for the limits, the freeze switch, the Merkle proof of custody, and the social-recovery model.
-- [Financial controls](#sec-221) for the plain-English spend-rule layer and the anomaly guard behind `/solana/guard`.
-- [The Trading Copilot](#sec-412) for the conversational surface that proposes trades a human confirms.
+- [Custody you can verify](#sec-172) for the limits, the freeze switch, the Merkle proof of custody, and the social-recovery model.
+- [Financial controls](#sec-223) for the plain-English spend-rule layer and the anomaly guard behind `/solana/guard`.
+- [The Trading Copilot](#sec-417) for the conversational surface that proposes trades a human confirms.
- [Coin Autopilot](#sec-106) for the *coin* cockpit at `/api/pump/autopilot`. That is a different feature from the **Treasury Autopilot** documented here, which runs the agent's own wallet rather than a launched coin.
## Orientation
@@ -17913,7 +17923,7 @@ The first `snapshot` is pushed immediately on connect. The stream carries only t
## Recovery: guardians, threshold, and inheritance
-Source: [`api/agents/recovery.js`](../api/agents/recovery.js), engine in [`api/_lib/agent-recovery.js`](../api/_lib/agent-recovery.js). Product tour: [Recovery](#sec-050), and the counterpart console in [Guardian](#sec-236).
+Source: [`api/agents/recovery.js`](../api/agents/recovery.js), engine in [`api/_lib/agent-recovery.js`](../api/_lib/agent-recovery.js). Product tour: [Recovery](#sec-050), and the counterpart console in [Guardian](#sec-239).
Recovery transfers *ownership*, never the key. The wallet secret is never decrypted, displayed, or moved. This is the one surface here that is not owner-only: a guardian or a beneficiary is a first-class caller with a scoped view.
@@ -18055,7 +18065,7 @@ Guardian or beneficiary only. No body. Arms the dead-man switch once the owner h
## Solana guard: the self-defending wallet
-Source: [`api/agents/solana-guard.js`](../api/agents/solana-guard.js), scoring in [`api/_lib/wallet-anomaly.js`](../api/_lib/wallet-anomaly.js), event store in [`api/_lib/anomaly-events.js`](../api/_lib/anomaly-events.js). Behavior narrative: [Financial controls](#sec-221).
+Source: [`api/agents/solana-guard.js`](../api/agents/solana-guard.js), scoring in [`api/_lib/wallet-anomaly.js`](../api/_lib/wallet-anomaly.js), event store in [`api/_lib/anomaly-events.js`](../api/_lib/anomaly-events.js). Behavior narrative: [Financial controls](#sec-223).
Scoring and freezing happen inline on the spend path, not here. This endpoint is the owner's window into that system and the control over it: read the learned baseline and the anomaly timeline, tune sensitivity, set a safe-sweep address, and adjudicate a freeze.
@@ -18173,12 +18183,12 @@ curl -s -X POST "https://three.ws/api/agents/$AGENT_ID/solana/guard" \
## Related
- [Agent wallets](#sec-072) for the wallet itself: creation, key custody, and the five spend paths.
-- [Custody you can verify](#sec-170) for limits, freeze, proof of custody, and the recovery model in prose.
-- [Financial controls](#sec-221) for the plain-English spend rules and the wallet-defense behaviors.
-- [The Trading Copilot](#sec-412) for the conversational read-and-propose surface over the same wallet.
+- [Custody you can verify](#sec-172) for limits, freeze, proof of custody, and the recovery model in prose.
+- [Financial controls](#sec-223) for the plain-English spend rules and the wallet-defense behaviors.
+- [The Trading Copilot](#sec-417) for the conversational read-and-propose surface over the same wallet.
- [Coin Autopilot](#sec-106) for the separate coin cockpit at `/api/pump/autopilot`.
- [What agents can do](#sec-009) for a page per wallet ability, including [Access](#sec-049), [Orders](#sec-040), [Intents](#sec-042), [Autopilot](#sec-041), [Portfolio](#sec-031), and [Recovery](#sec-050).
-- [Guardian console](#sec-236) for the other side of a recovery request.
+- [Guardian console](#sec-239) for the other side of a recovery request.
---
@@ -18190,7 +18200,7 @@ curl -s -X POST "https://three.ws/api/agents/$AGENT_ID/solana/guard" \
Every three.ws agent owns a **custodial Solana wallet**. It is what lets an agent act on its own — pay for an API call, buy a coin, tip another agent, receive its earnings — without a human approving each transaction in a browser extension.
-This is the reference for the wallet itself: how it's created, how its key is held, what may spend from it, and where the controls live. For the owner-facing safety story (limits, freeze, proof, recovery) read [Custody you can verify](#sec-170). For the complete tour of everything the wallet can do, read [What agents can do → The Agent Wallet](#sec-023).
+This is the reference for the wallet itself: how it's created, how its key is held, what may spend from it, and where the controls live. For the owner-facing safety story (limits, freeze, proof, recovery) read [Custody you can verify](#sec-172). For the complete tour of everything the wallet can do, read [What agents can do → The Agent Wallet](#sec-023).
## What you get
@@ -18210,7 +18220,7 @@ The encryption key derives, via HKDF, from a dedicated secret (`WALLET_ENCRYPTIO
This is the same secret box used for coin treasuries and the launcher, so every custodial secret on the platform is held the same way.
-**What this means honestly:** the platform can sign for the agent. That is the point — an autonomous agent that needs you to approve each transaction is not autonomous. What the platform gives you in exchange is that everything it *can* do is capped by policy you set, halted by a freeze you control, recorded in an audit trail, and provable on-chain. See [custody.md](#sec-170).
+**What this means honestly:** the platform can sign for the agent. That is the point — an autonomous agent that needs you to approve each transaction is not autonomous. What the platform gives you in exchange is that everything it *can* do is capped by policy you set, halted by a freeze you control, recorded in an audit trail, and provable on-chain. See [custody.md](#sec-172).
## Who can spend
@@ -18219,9 +18229,9 @@ Five paths move funds out of an agent wallet, and **all five pass through one po
| Path | Trigger |
|------|---------|
| Withdraw | The owner sweeps funds out |
-| x402 pay | The agent pays for a paid API call. Also reachable from any paid checkout on the site: the [x402 payment modal](#sec-457) lists a signed-in user's agents next to Phantom, and picking one settles from that agent's wallet with no popup |
+| x402 pay | The agent pays for a paid API call. Also reachable from any paid checkout on the site: the [x402 payment modal](#sec-463) lists a signed-in user's agents next to Phantom, and picking one settles from that agent's wallet with no popup |
| Trade | A discretionary buy/sell from the wallet hub, or from the in-world coin widget's **Pay with** selector (SOL-denominated coins) |
-| Purchase | The agent buys a marketplace skill or asset for itself (see [Marketplace](#sec-270)), under its own daily purchase cap |
+| Purchase | The agent buys a marketplace skill or asset for itself (see [Marketplace](#sec-274)), under its own daily purchase cap |
| Snipe | The autonomous sniper worker executes a strategy |
Because enforcement lives at the signing boundary rather than in each feature, a new feature cannot accidentally introduce an unguarded spend path.
@@ -18243,7 +18253,7 @@ Two asymmetries are deliberate:
Coin-launch and bonding-curve activity carries an additional SOL-denominated policy (`max_sol_per_tx`, `daily_sol_cap`, an optional `allowed_mints` allowlist). A freshly provisioned agent that has never been configured defaults to **1 SOL per transaction and 5 SOL per rolling day**, so a stolen session token cannot drain it.
-On top of the numeric caps sit two additive layers, each of which can only ever *narrow* a spend, never widen it: [natural-language spend rules](#sec-221) that an LLM authors and deterministic code enforces, and a behavioral anomaly guard that freezes the wallet when a spend doesn't look like the agent's normal behavior.
+On top of the numeric caps sit two additive layers, each of which can only ever *narrow* a spend, never widen it: [natural-language spend rules](#sec-223) that an LLM authors and deterministic code enforces, and a behavioral anomaly guard that freezes the wallet when a spend doesn't look like the agent's normal behavior.
### The audit trail
@@ -18271,10 +18281,10 @@ An agent can pay a human-readable name instead of a base58 address. `/api/x402/p
## Related
-- [Custody you can verify](#sec-170) — limits, freeze, Merkle proof-of-custody, social recovery and inheritance
-- [Financial controls](#sec-221) — plain-English spend rules, compiled and enforced deterministically
+- [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-544) — how agents pay for services
+- [x402 protocol](#sec-551) — how agents pay for services
- [Coin launches](#sec-144) — how the wallet signs a pump.fun launch
---
@@ -18464,11 +18474,11 @@ An "awakening" envelope (no eligible trading agent yet) is still valid and fully
## Related
-- [Oracle](#sec-315) - the conviction engine this class of agent trades on
+- [Oracle](#sec-320) - the conviction engine this class of agent trades on
- [Agent reputation](#sec-056) - the Reasoning Ledger score behind the reputation ring
-- [Reputation](#sec-367) - how proven on-chain track records are computed
-- [The trading experiment](#sec-413) - an autonomous agent operating inside these limits, journaled
-- [Custody you can verify](#sec-170) - the spend caps and kill switch the autonomy runs under
+- [Reputation](#sec-372) - how proven on-chain track records are computed
+- [The trading experiment](#sec-418) - an autonomous agent operating inside these limits, journaled
+- [Custody you can verify](#sec-172) - the spend caps and kill switch the autonomy runs under
- [/activity](https://three.ws/activity) - every agent's live trades in real time
---
@@ -20419,9 +20429,9 @@ of rendering a fake zero.
## Related surfaces
-- [`/portfolio`](#sec-331): the live wallet portfolio; the two pages
+- [`/portfolio`](#sec-336): the live wallet portfolio; the two pages
cross-link and share the recent-wallet list.
-- [`/api/crypto/wallet`](#sec-169): the raw balance endpoint the token
+- [`/api/crypto/wallet`](#sec-171): the raw balance endpoint the token
diversity measurement rides on.
---
@@ -20501,10 +20511,10 @@ When `read.hallucination_guard.line_replaced` is true, the co-pilot caught a fig
## Related
-- [Custody you can verify](#sec-170) - the spend limits, firewall, and audit the "Act" path runs under
-- [Financial controls](#sec-221) - the plain-English rules and real-time defense on the same rails
-- [Oracle](#sec-315) - the platform conviction engine over the same launch universe
-- [Trading surfaces](#sec-415) - Mission Control executes through this same guarded path
+- [Custody you can verify](#sec-172) - the spend limits, firewall, and audit the "Act" path runs under
+- [Financial controls](#sec-223) - the plain-English rules and real-time defense on the same rails
+- [Oracle](#sec-320) - the platform conviction engine over the same launch universe
+- [Trading surfaces](#sec-420) - Mission Control executes through this same guarded path
- [/agi](https://three.ws/agi) - a fully autonomous agent reading and trading the same feed
---
@@ -20711,7 +20721,7 @@ If you extend the metric, keep two properties: the retention window must stay an
# Animation Studio: pose, keyframe, and sell motion
-Animation Studio is where a three.ws avatar (or a built-in mannequin) becomes animated. Click any body part and rotate it with a gizmo, or drag a hand or foot and let inverse kinematics solve the limb. Drop the pose as a keyframe, advance the playhead, re-pose, and drop another; the studio interpolates between them and plays the result. Export the finished motion as an animated GLB or as clip JSON, save it to your account, deep-link it to play on any avatar, hand it to [Scene Studio](#sec-373) to record as video, or list it for sale in the animation marketplace for USDC.
+Animation Studio is where a three.ws avatar (or a built-in mannequin) becomes animated. Click any body part and rotate it with a gizmo, or drag a hand or foot and let inverse kinematics solve the limb. Drop the pose as a keyframe, advance the playhead, re-pose, and drop another; the studio interpolates between them and plays the result. Export the finished motion as an animated GLB or as clip JSON, save it to your account, deep-link it to play on any avatar, hand it to [Scene Studio](#sec-378) to record as video, or list it for sale in the animation marketplace for USDC.
Page: [/pose](https://three.ws/pose) · API: `/api/animations/clips`
@@ -20745,7 +20755,7 @@ Under the motion generator sits a Spell box: type a word and the avatar spells i
A spelled word is shareable as a link: `https://three.ws/pose?spell=HELLO` opens the studio, auto-loads a rigged avatar (same roster as animation deep links), and spells the word on arrival.
-Fingerspelling is the deterministic, spelling-based subset of sign language, it spells English words rather than translating into grammatical ASL. The Studio's Spell box is spelling only. The platform also has a lexical vocabulary (words that are signed rather than spelled, on one or both hands), which drives [/sign-language](https://three.ws/sign-language), signed chat replies, and the `sign-language` embed attribute. See [docs/sign-language.md](#sec-381) for the whole system, or the tutorial [Make your avatar sign](https://three.ws/tutorials/sign-with-your-avatar) for a guided tour.
+Fingerspelling is the deterministic, spelling-based subset of sign language, it spells English words rather than translating into grammatical ASL. The Studio's Spell box is spelling only. The platform also has a lexical vocabulary (words that are signed rather than spelled, on one or both hands), which drives [/sign-language](https://three.ws/sign-language), signed chat replies, and the `sign-language` embed attribute. See [docs/sign-language.md](#sec-386) for the whole system, or the tutorial [Make your avatar sign](https://three.ws/tutorials/sign-with-your-avatar) for a guided tour.
### Export, save, and sell
@@ -20807,7 +20817,7 @@ An empty `tracks` array is rejected: a clip with no motion is not a clip. Track
- [Animations reference](#sec-093): the runtime clip registry, formats, and agent slots.
- [3D asset pipeline](#sec-002): how GLB, FBX, and clip JSON convert across the platform.
-- [Scene Studio](#sec-373): record your animation to video.
+- [Scene Studio](#sec-378): record your animation to video.
- [Avatar Studio](#sec-115): build the avatar you animate here.
- [/marketplace](https://three.ws/marketplace): where listed animation clips are bought and sold.
@@ -21595,7 +21605,7 @@ This is the reference for the three.ws HTTP API: every documented endpoint, its
Base URL: `https://three.ws/api`
-> For the in-browser JavaScript API (the `<agent-3d>` element, `Viewer`, `Runtime`, `SceneController`, skills, memory), see [js-api.md](#sec-258) and [web-component.md](#sec-508). For the high-level npm SDK, see [sdk.md](#sec-374).
+> For the in-browser JavaScript API (the `<agent-3d>` element, `Viewer`, `Runtime`, `SceneController`, skills, memory), see [js-api.md](#sec-261) and [web-component.md](#sec-514). For the high-level npm SDK, see [sdk.md](#sec-379).
The full machine-readable schema lives at [`https://three.ws/.well-known/openapi.yaml`](https://three.ws/.well-known/openapi.yaml). x402 paid endpoints are listed at [`/.well-known/x402.json`](https://three.ws/.well-known/x402.json) and the MCP endpoint is at [`/api/mcp`](https://three.ws/api/mcp).
@@ -22263,8 +22273,8 @@ widget in `src/memory-seed.js`.
Everything these endpoints read is already public. They are read-only, request
no OAuth from the visitor, and store nothing; the consent-gated seeding flows
that do write to an agent live at `/api/agents/:id/memory/seed/*` and are
-documented in [GitHub](#sec-234), [X](#sec-515)
-and [Farcaster](#sec-220) memory seeding.
+documented in [GitHub](#sec-237), [X](#sec-521)
+and [Farcaster](#sec-222) memory seeding.
The three connectors are unauthenticated GETs, rate limited per IP, and cached
at the edge for 5 minutes. A connector that cannot reach its upstream answers
@@ -23228,7 +23238,7 @@ x-forge-client: <stable browser id> # optional — resolves per-card `voted`
`sort=fresh` (default, newest-first) or `sort=top` (most-voted); `window=week`
narrows Top to the current Forge-Off week (Monday→Monday UTC). Full feature
-docs: [docs/forge-off.md](#sec-223).
+docs: [docs/forge-off.md](#sec-226).
### Model detail page read: `GET /api/forge-creation`
@@ -23355,7 +23365,7 @@ the Avatar Studio re-skin idea (`src/avatar-studio-colorpicker.js`,
preset live in the browser (see [Restyle Studio](https://three.ws/restyle)), ask
an AI for a restyle from a plain-language instruction, or fan one preset out into
N reproducible colorway variants. Free and hosted — rate-limited, not x402 — the
-same implementation the paid `restyle_material` [MCP tool](#sec-275) calls as
+same implementation the paid `restyle_material` [MCP tool](#sec-279) calls as
a thin client, so the free web page and the paid agent tool never drift.
Every mesh edit is **non-destructive**: geometry and UVs are never touched (only
@@ -23749,7 +23759,7 @@ sample rate, whether the lane is configured).
Read American Sign Language fingerspelling from a webcam. No API key, no account,
no payment: rate-limited per IP. This is the input half of the platform's signing
-loop (the output half, avatars that sign, is [docs/sign-language.md](#sec-381)).
+loop (the output half, avatars that sign, is [docs/sign-language.md](#sec-386)).
**Video never reaches the platform.** The caller extracts MediaPipe Holistic
landmarks in the browser and posts coordinates only. `src/sign-input.js` ships a
@@ -24502,7 +24512,7 @@ progress, the three.ws launch directory, and whale activity. Each endpoint is a
thin wrapper: search shares its engine with the site's command-palette search
(`/api/pump/search`); trending, curve, and whales share their engines with the
free Crypto Data API's pump.fun endpoints (`/api/crypto/trending`, `/bonding`,
-`/whales` — see [docs/crypto-api.md](#sec-169)); launches shares its query
+`/whales` — see [docs/crypto-api.md](#sec-171)); launches shares its query
with the [/launches](https://three.ws/launches) page. No fork of any upstream
logic lives here — every /api/v1/pump/\* route imports the same shared module
its sibling already uses.
@@ -24571,7 +24581,7 @@ curl -s 'https://three.ws/api/v1/pump/search?q=three.ws'
Momentum-ranked "what's hot right now" — fuses windowed volume, buy pressure, a
volume-spike signal, and price change across pump.fun, DexScreener, and
(best-effort) GMGN smart money into one 0–100 score. Same engine as
-[`GET /api/crypto/trending`](#sec-169)
+[`GET /api/crypto/trending`](#sec-171)
(`api/_lib/crypto-trending.js` `composeTrending`), capped slimmer here (25 vs
50) to keep this door fast.
@@ -24636,7 +24646,7 @@ curl -s 'https://three.ws/api/v1/pump/trending?window=1h&limit=10'
Bonding-curve / graduation status for one pump.fun mint — % to graduation, SOL
in the curve, tokens remaining, market cap, and whether it has already migrated
to an AMM (Raydium / PumpSwap). Same engine as
-[`GET /api/crypto/bonding`](#sec-169)
+[`GET /api/crypto/bonding`](#sec-171)
(`api/_lib/pump-bonding.js` `getBondingStatus`).
```
@@ -24767,7 +24777,7 @@ oracle that otherwise sits behind the paid `GET /api/x402/pump-agent-audit`
(`"mode":"whale_activity"`) — the invented "bullish/bearish signal +
confidence" the paid oracle scores is deliberately dropped here, and the same
scan engine backs the free
-[`GET /api/crypto/whales`](#sec-169)
+[`GET /api/crypto/whales`](#sec-171)
(`api/_lib/pump-whale-scan.js` `scanTokenWhales` / `scanMarketWhales`).
```
@@ -24828,7 +24838,7 @@ curl -s 'https://three.ws/api/v1/pump/whales?mint=FeMbDoX7R1Psc4GEcvJdsbNbZA3bfz
A trader's daily on-chain score attestation (`threews.tradescore.v1`), served as a
portable credential and a database-free verifier. Full guide:
-[docs/trader-passport.md](#sec-410).
+[docs/trader-passport.md](#sec-415).
### Read a passport
@@ -25058,7 +25068,7 @@ The cursor encodes the full keyset tuple (registration timestamp, chain ID, agen
## Social & Community API
-The endpoints behind the platform's social layer: the activity feed, the follow graph, notifications, the unified leaderboard, creator portfolios, and cross-entity search. Overview and how the pieces interconnect: [The social layer](#sec-391).
+The endpoints behind the platform's social layer: the activity feed, the follow graph, notifications, the unified leaderboard, creator portfolios, and cross-entity search. Overview and how the pieces interconnect: [The social layer](#sec-396).
### Activity feed
@@ -25097,7 +25107,7 @@ Reverse-chronological creation events (avatars, agents, coins, forged models, sa
Items of `kind: "follow"` also carry a `target` shaped like `actor`. `actor.username` is `null` for creations made while signed out.
-Not the same endpoint as `GET /api/feed`, the public Money Pulse ticker ([Money Feed](#sec-285)).
+Not the same endpoint as `GET /api/feed`, the public Money Pulse ticker ([Money Feed](#sec-289)).
---
@@ -25480,7 +25490,7 @@ GET answers `405` with `allow: POST, DELETE`.
`render_avatar` enforces the agent's embed policy (allowed origins, allowed surfaces). Model URLs must be HTTPS — SSRF protections block private IP ranges.
-This table is the core subset. The server registers many more tools (minting, gated embeds, memory, oracle and pump.fun intel, trader analytics, crypto data). Call `tools/list`, or see the [MCP documentation](#sec-277) and the [MCP Tools Catalog](#sec-275).
+This table is the core subset. The server registers many more tools (minting, gated embeds, memory, oracle and pump.fun intel, trader analytics, crypto data). Call `tools/list`, or see the [MCP documentation](#sec-281) and the [MCP Tools Catalog](#sec-279).
**Example JSON-RPC request**
@@ -25593,7 +25603,7 @@ Both header names are read case-insensitively and both receipt names are emitted
| `POST /api/mcp-3d` | MCP (Streamable HTTP) | Base + X Layer (+ Solana when configured) |
| `POST /api/okx/3d/<service>` | A2MCP (decomposed 3D studio) | X Layer first, then Solana/Base |
-The full seller-side wire contract — challenge fields, verify→work→settle order, the `PAYMENT-SIGNATURE` payload shape, and the settlement receipt — is pinned in [`specs/okx-agent-payments.md`](../specs/okx-agent-payments.md). The per-service catalog and runnable curls are in [`docs/okx-marketplace.md`](#sec-302).
+The full seller-side wire contract — challenge fields, verify→work→settle order, the `PAYMENT-SIGNATURE` payload shape, and the settlement receipt — is pinned in [`specs/okx-agent-payments.md`](../specs/okx-agent-payments.md). The per-service catalog and runnable curls are in [`docs/okx-marketplace.md`](#sec-306).
---
@@ -25615,7 +25625,7 @@ The buyer-side counterpart to the x402 endpoints above. Everything so far assume
You fund a budget from your [credits](payment-sessions.md#prepaid-credits), set the policy, and receive a bearer token. The agent presents that token to `/api/pay/execute`; the platform's own wallet signs the on-chain transfer. A stolen token buys at most the remaining budget, only at hosts you approved, only until the session expires.
-Conceptual guide: [Payment sessions](#sec-321). Step-by-step walkthrough: [Give an agent a spending envelope](#sec-421). Enforcement source: [`api/_lib/pay/spend-governor.js`](https://github.com/nirholas/three.ws/blob/main/api/_lib/pay/spend-governor.js).
+Conceptual guide: [Payment sessions](#sec-326). Step-by-step walkthrough: [Give an agent a spending envelope](#sec-427). Enforcement source: [`api/_lib/pay/spend-governor.js`](https://github.com/nirholas/three.ws/blob/main/api/_lib/pay/spend-governor.js).
### Authentication
@@ -26495,7 +26505,7 @@ fetched_at }`.
`paragraphs[]` is a bounded lead excerpt, not the article body: capped to 2
paragraphs / 400 characters by `excerptParagraphs()` in
[api/_lib/news-rights.js](../api/_lib/news-rights.js), the single choke point
-every response passes through (see [docs/news-rights.md](#sec-292)).
+every response passes through (see [docs/news-rights.md](#sec-296)).
`excerpt_truncated` is `true` whenever the source ran longer than the quoted
excerpt; `full_text_url` is where to send the reader for the rest. This is a
hard limit for every publisher, not a per-source policy — a story removed at a
@@ -28582,7 +28592,7 @@ Endpoint-specific codes (e.g. `quota_exceeded`, `invalid_avatar`, `no_client_id`
## SDK
-For building on the platform from JavaScript, the official npm package is [`@three-ws/sdk`](https://www.npmjs.com/package/@three-ws/sdk). It is not a thin wrapper over every REST route above; it ships the higher-level building blocks: `AgentKit` (chat panel + ERC-8004 registration + `.well-known` manifest generation), `AgentClient` (x402 agent-to-agent paid skill calls), `PermissionsClient` (ERC-7710 delegations), and the Solana identity/attestation helpers. Full docs: [SDK & Library](#sec-374).
+For building on the platform from JavaScript, the official npm package is [`@three-ws/sdk`](https://www.npmjs.com/package/@three-ws/sdk). It is not a thin wrapper over every REST route above; it ships the higher-level building blocks: `AgentKit` (chat panel + ERC-8004 registration + `.well-known` manifest generation), `AgentClient` (x402 agent-to-agent paid skill calls), `PermissionsClient` (ERC-7710 delegations), and the Solana identity/attestation helpers. Full docs: [SDK & Library](#sec-379).
For the endpoints on this page, call them directly with `fetch`/`curl` and a Bearer API key:
@@ -28938,7 +28948,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-539) and
+[x402 endpoints](#sec-546) and
[the autonomous economy](#sec-105).
Treat prompts as public. If you need a private lane, use the account-scoped
@@ -28984,13 +28994,13 @@ const glb = Buffer.from(await (await fetch(glbUrl)).arrayBuffer());
- [3D API](#sec-001): the free draft lane, inspection, validation, and the
full Forge Pro walkthrough.
-- [Forge pipeline](#sec-224): how the lanes, tiers, and failovers fit
+- [Forge pipeline](#sec-227): how the lanes, tiers, and failovers fit
together internally.
-- [3D Studio MCP server](#sec-271): the same generation as
+- [3D Studio MCP server](#sec-275): the same generation as
`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-539): every paid endpoint on the platform.
+- [x402 endpoints](#sec-546): every paid endpoint on the platform.
---
@@ -29100,7 +29110,7 @@ Append `?e2e=1` to expose `window.__arsDebug` (`count()`, `netStatus()`, `netIds
## Related
- [AR and WebXR](#sec-099): the single-model "View in AR" system, `/ar` AR Forge, the `POST /api/forge` free lane in depth, the USDZ/Quick Look pipeline, and model-optimization limits.
-- [Selfie to Avatar](#sec-377) and [Avatar pipeline](#sec-113): where the models you place come from.
+- [Selfie to Avatar](#sec-382) and [Avatar pipeline](#sec-113): where the models you place come from.
- Pages: [/ar/studio](https://three.ws/ar/studio), [/ar](https://three.ws/ar), [/viewer](https://three.ws/viewer).
---
@@ -29618,7 +29628,7 @@ the wild can load.
# Architecture Overview
-three.ws is the platform you see at [three.ws](https://three.ws): 3D avatars with AI brains that you can chat with, embed on any site, and register on-chain. This page is the engineering map of how that is built. If you just want to use the product, start with [How three.ws works](#sec-240) instead.
+three.ws is the platform you see at [three.ws](https://three.ws): 3D avatars with AI brains that you can chat with, embed on any site, and register on-chain. This page is the engineering map of how that is built. If you just want to use the product, start with [How three.ws works](#sec-243) instead.
This document describes how three.ws is put together, how data moves through it, and where the seams are if you want to extend, self-host, or integrate it with another stack. It assumes familiarity with modern JavaScript, WebGL/three.js at a high level, and the basics of EVM blockchains and content-addressed storage.
@@ -29889,9 +29899,9 @@ The assistant widget puts a full-body, animated three.ws avatar on any website b
Configure everything and copy your snippet at [three.ws/assistant](https://three.ws/assistant). The builder page runs the real widget, so what you see in the corner is exactly what your visitors get.
-Looking for a support-chat panel grounded in your page's content instead of a full-body avatar? That is the sibling [Concierge widget](#sec-152). Use Concierge for "answer questions about this page"; use the assistant widget when you want a character who stands on your site, speaks, and can run on a visitor's own model key.
+Looking for a support-chat panel grounded in your page's content instead of a full-body avatar? That is the sibling [Concierge widget](#sec-153). Use Concierge for "answer questions about this page"; use the assistant widget when you want a character who stands on your site, speaks, and can run on a visitor's own model key.
-There are three ways to add it: a one-tag script, the [`@three-ws/assistant`](https://www.npmjs.com/package/@three-ws/assistant) npm package, or let an AI agent generate the embed for you through the [assistant-widget MCP server](#generate-a-widget-from-an-ai-agent-mcp). New to it? The [step-by-step tutorial](#sec-418) builds one from scratch.
+There are three ways to add it: a one-tag script, the [`@three-ws/assistant`](https://www.npmjs.com/package/@three-ws/assistant) npm package, or let an AI agent generate the embed for you through the [assistant-widget MCP server](#generate-a-widget-from-an-ai-agent-mcp). New to it? The [step-by-step tutorial](#sec-424) builds one from scratch.
## Install
@@ -30000,7 +30010,7 @@ Two tools:
- **`list_assistant_options`** returns everything you can configure: the built-in avatars, the background presets and grammar, the modes, the chat lanes, and the full `data-*` attribute reference.
- **`build_assistant_widget`** turns a config (avatar, background, mode, name, greeting, context, accent, position) into a paste-ready `<script>` snippet, a standalone frame URL, an equivalent `ThreeAssistant.init({...})` call, and the builder link. Every field is validated and clamped, so a bad value falls back to a safe default and the generated HTML is always well-formed.
-Ask your agent something like "build a 3D assistant widget named Aria with an ocean background for my site" and paste the snippet it returns. The server is one of the [three.ws MCP servers](#sec-277); find it in the registry at [registry.modelcontextprotocol.io](https://registry.modelcontextprotocol.io/?q=io.github.nirholas).
+Ask your agent something like "build a 3D assistant widget named Aria with an ocean background for my site" and paste the snippet it returns. The server is one of the [three.ws MCP servers](#sec-281); find it in the registry at [registry.modelcontextprotocol.io](https://registry.modelcontextprotocol.io/?q=io.github.nirholas).
## How it works
@@ -30012,10 +30022,10 @@ Ask your agent something like "build a 3D assistant widget named Aria with an oc
## Related surfaces
-- [Build a 3D assistant, step by step](#sec-418), the tutorial
-- [Concierge](#sec-152), the page-grounded support-chat widget with a lipsyncing face
-- [three.ws MCP servers](#sec-277), the full free and paid tool catalog
-- [Share and embed](#sec-378), the `<three-d>` model embeds
+- [Build a 3D assistant, step by step](#sec-424), the tutorial
+- [Concierge](#sec-153), the page-grounded support-chat widget with a lipsyncing face
+- [three.ws MCP servers](#sec-281), the full free and paid tool catalog
+- [Share and embed](#sec-383), the `<three-d>` model embeds
- [/walk-embed](https://three.ws/walk-embed), the walking-avatar iframe embed
- [/forge](https://three.ws/forge), generate an avatar to use in the widget
@@ -30899,8 +30909,8 @@ and the platform **scans its own wallets for leaks every few minutes**.
This page explains the whole loop in plain language: which wallet does what, how money
can and cannot move, and how you can verify there's no leak yourself.
-Companion docs: [Money map](#sec-287) (which wallet receives each *payment*),
-[Economy master](#sec-182) (the funding-root subsystem in depth), and the
+Companion docs: [Money map](#sec-291) (which wallet receives each *payment*),
+[Economy master](#sec-184) (the funding-root subsystem in depth), and the
[Solana signers runbook](../api/_lib/solana-signers.js) (every signer, its floor, and
how to fund it).
@@ -31039,11 +31049,11 @@ zero.
## Related
-- [Money map](#sec-287) — which wallet receives each kind of payment, and the
+- [Money map](#sec-291) — which wallet receives each kind of payment, and the
platform's cut.
-- [Economy master](#sec-182) — the funding-root subsystem, its ledger, and the
+- [Economy master](#sec-184) — the funding-root subsystem, its ledger, and the
topup/sweepback crons in depth.
-- [x402 ring economy](#sec-541) — how the autonomous payment ring settles
+- [x402 ring economy](#sec-548) — how the autonomous payment ring settles
USDC between agents.
---
@@ -31075,7 +31085,7 @@ the sniper oracle gate.
The loop runs from the `x402-autonomous-loop` cron endpoint, invoked every
**minute** by the `economy-tick` dispatcher (see the
-[economy heartbeat](#sec-181)) rather than by its own schedule
+[economy heartbeat](#sec-183)) rather than by its own schedule
entry; per-entry Redis cooldowns decide what actually fires on any given tick.
Each tick:
@@ -31264,16 +31274,16 @@ corroborate — the ops financial-integrity surface alerts on those. Detail:
| `x402_autonomous_log` | Every call (success or failure), with `signal_data` / `value_extracted`. `error_msg` is reserved for calls that actually failed: the external uptime monitor probes third-party services for free and records an alive-but-unexpected status (a templated path answering 400, a verb-picky route answering 405) in `value_extracted.status` only, so a liveness observation never lands in the loop's failure stats. |
| `oracle_intel_signals` | `oracle` / `sniper` entries, keyed by source + topic; consumed by the sniper oracle gate. Each row carries `tx_signature`, the settle signature of the paid call that bought it, so a gate decision can cite its receipt (surfaced as `signal_receipts` on gate results). |
| `forge_creations` | Every settled `POST /api/x402/forge` generation (any buyer, not just this loop). The row lands in the public community gallery with `x402_payer` / `x402_tx_sig` / `x402_price_atomic` provenance; the gallery renders a Solscan-linked "x402 · $price" badge. Inline-done lanes materialize immediately; async lanes store the full job token and `api/cron/forge-finalize` completes them server-side. |
-| `agent_custody_events` | The USDC spend, with `category: 'x402'` (see [Money feed](#sec-285)). |
+| `agent_custody_events` | The USDC spend, with `category: 'x402'` (see [Money feed](#sec-289)). |
| `x402_volume_metrics` | Per-endpoint proof-of-volume + liveness ledger from the Volume Bootstrap Loop (see [x402 revenue](x402-revenue.md#proof-of-volume--x402_volume_metrics)). |
| `payment_reconciliation` | One verdict per settlement claim from the daily reconciliation job (see [x402 revenue](x402-revenue.md#reconciliation--payment_reconciliation)). |
| Dedicated stores | Pipeline-specific tables (pricing tracker, reputation snapshots, leaderboard, sniper analytics, …). |
## Related
-- [x402 endpoints](#sec-539) — the paid endpoints this loop calls.
-- [x402 revenue & receipts](#sec-540) — where settlements land, the proof-of-volume ledger, and the reconciliation job.
-- [x402 buyer client](#sec-536) — the client wrappers it pays with.
+- [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.
- [Circulation engine](#sec-141) — the separate SOL/$THREE activity loop.
---
@@ -31373,9 +31383,9 @@ A confirmed buyback narrates as: "Bought back and burned $120 of $YOURCOIN. Supp
## Related
-- [Custody you can verify](#sec-170) - the spend limits, freeze switch, and audit trail every agent wallet runs under
-- [Financial controls](#sec-221) - plain-English spend rules layered on the same enforcement point
-- [Oracle](#sec-315) - the conviction engine and the agent action loop that arms an agent to trade autonomously
+- [Custody you can verify](#sec-172) - the spend limits, freeze switch, and audit trail every agent wallet runs under
+- [Financial controls](#sec-223) - plain-English spend rules layered on the same enforcement point
+- [Oracle](#sec-320) - the conviction engine and the agent action loop that arms an agent to trade autonomously
- [/dashboard](https://three.ws/dashboard) - launch a coin for an agent, the prerequisite for Autopilot
- [/launches](https://three.ws/launches) - the public feed of coins launched through three.ws
@@ -31389,7 +31399,7 @@ A confirmed buyback narrates as: "Bought back and burned $120 of $YOURCOIN. Supp
[three.ws/avatar-artifact](https://three.ws/avatar-artifact) is one page that renders one avatar and nothing else. No app shell, no sign-in, no navigation to get lost in: a URL you can paste into an `<iframe>` on any site, or send to someone who has never heard of three.ws, and it renders a live 3D avatar in their browser.
-It is deliberately the smallest viewer we ship. [The full 3D viewer](#sec-505) is the engine behind `/app` and every `<agent-3d>` embed, with camera rigs, material editing and a clip panel. This page has one job: show the artifact, beautifully, from a link.
+It is deliberately the smallest viewer we ship. [The full 3D viewer](#sec-511) is the engine behind `/app` and every `<agent-3d>` embed, with camera rigs, material editing and a clip panel. This page has one job: show the artifact, beautifully, from a link.
---
@@ -31453,7 +31463,7 @@ Two properties make this safe to drop on someone else's page:
- **No third-party CDN.** three.js ships with the bundle. An embed host never picks up a cross-origin script tag it did not agree to.
- **It stops when it is not visible.** A hidden tab suspends the render loop, so an embedded viewer never burns a host page's GPU in the background.
-For a full chat widget or a token-gated embed, use [Share and embed](#sec-378) instead. This page is the plain viewer.
+For a full chat widget or a token-gated embed, use [Share and embed](#sec-383) instead. This page is the plain viewer.
---
@@ -31507,8 +31517,8 @@ A large model on a slow connection is not a failure: the loading overlay reports
## Related
-- [The 3D viewer](#sec-505): the full engine behind `/app` and `<agent-3d>`
-- [Share and embed](#sec-378): widgets, web components and embed policy
+- [The 3D viewer](#sec-511): the full engine behind `/app` and `<agent-3d>`
+- [Share and embed](#sec-383): widgets, web components and embed policy
- [Claude artifact contract](../specs/CLAUDE_ARTIFACT.md): the self-contained HTML lane for Claude.ai, which shares this page's parameter shape
- [Animations](#sec-093): the clip library this page retargets from
@@ -31526,7 +31536,7 @@ It is the piece that lets avatars live in a build pipeline instead of a browser
**On this page:** [Install](#install) · [Quick start](#quick-start) · [Commands](#commands) · [The manifest](#the-manifest) · [Exit codes](#exit-codes-and-scripting) · [Release gate](#gate-a-release-on-the-manifest)
-Related: [`@three-ws/avatar-schema`](../packages/avatar-schema/README.md) is the wire format this validates against. The [web component reference](#sec-508) covers the `<agent-3d>` element the CLI emits.
+Related: [`@three-ws/avatar-schema`](../packages/avatar-schema/README.md) is the wire format this validates against. The [web component reference](#sec-514) covers the `<agent-3d>` element the CLI emits.
---
@@ -31720,7 +31730,7 @@ https://three.ws/a/eip155%3A1%3A0x742d35Cc6634C0532925a3b844Bc454e4438f44e
<iframe src="https://three.ws/a/eip155%3A1%3A0x742d35Cc6634C0532925a3b844Bc454e4438f44e" width="480" height="640" frameborder="0" allow="camera; microphone; xr-spatial-tracking"></iframe>
```
-The web-component block is emitted with its loader on purpose. `<agent-3d>` is an ordinary unknown element until that script registers it, so the snippet is only complete with both lines. See the [web component reference](#sec-508) for the full attribute surface.
+The web-component block is emitted with its loader on purpose. `<agent-3d>` is an ordinary unknown element until that script registers it, so the snippet is only complete with both lines. See the [web component reference](#sec-514) for the full attribute surface.
When `mesh.uri` is still a local path, `preview` says so rather than handing you a snippet that renders nothing:
@@ -31817,8 +31827,8 @@ three-ws-avatar validate manifest.json --json | jq -e '.valid'
## Where to go next
-- **[Ship an avatar manifest](#sec-468)** walks the whole path end to end, from a raw GLB to a live embed, and explains the decision at each step.
-- **[Web component reference](#sec-508)** documents every attribute on the `<agent-3d>` element `preview` emits.
+- **[Ship an avatar manifest](#sec-474)** walks the whole path end to end, from a raw GLB to a live embed, and explains the decision at each step.
+- **[Web component reference](#sec-514)** documents every attribute on the `<agent-3d>` element `preview` emits.
- **[`@three-ws/avatar-schema`](../packages/avatar-schema/README.md)** is the normative format if you are writing your own tooling.
- The package source lives in [`packages/avatar-cli`](https://github.com/nirholas/three.ws/tree/main/packages/avatar-cli).
@@ -32096,7 +32106,7 @@ On success, you receive:
### 3. Register on-chain (optional)
-For permanent, verifiable identity, you can register the agent on-chain under ERC-8004. This creates a blockchain record linked to a wallet address. Gas fees apply. See the [ERC-8004 documentation](#sec-188) for details.
+For permanent, verifiable identity, you can register the agent on-chain under ERC-8004. This creates a blockchain record linked to a wallet address. Gas fees apply. See the [ERC-8004 documentation](#sec-190) for details.
---
@@ -32222,7 +32232,7 @@ Mesh and glTF output can be animated by the skinned-mesh pipeline. Gaussian and
| --- | --- | --- |
| `live` | Live on three.ws | Already wired into a three.ws product surface you can use right now. |
| `forge` | Generate in Forge | Commercially licensed and reachable through the live text and image to GLB pipeline at [/forge](https://three.ws/forge). |
-| `splat` | View in Splat Viewer | Produces Gaussian-splat or radiance-field output you can drop into the three.ws [splat viewer](#sec-397). |
+| `splat` | View in Splat Viewer | Produces Gaussian-splat or radiance-field output you can drop into the three.ws [splat viewer](#sec-402). |
| `interop` | Interop | Emits a standard rigged format (glTF, VRM, FBX) that the three.ws viewer and animation pipeline already understand. |
| `reference` | Reference / self-host | Run it yourself. Its license or its compute profile keeps it out of the commercial pipeline. It is listed here for builders. |
@@ -32329,9 +32339,9 @@ To add an engine, append an entry to `ENGINES` in [`src/avatar-engines-data.js`]
## Related
-- [Splat Viewer](#sec-397): where the Gaussian-splat output of the `splat` engines actually renders in the browser.
+- [Splat Viewer](#sec-402): where the Gaussian-splat output of the `splat` engines actually renders in the browser.
- [Scene Capture](#sec-134): the three.ws side of reconstruction, turning real video into 3D, adjacent to the photoreal-head family here.
-- [Forge](#sec-225): the live commercial generation pipeline, which the one `live` text-to-avatar engine powers.
+- [Forge](#sec-228): the live commercial generation pipeline, which the one `live` text-to-avatar engine powers.
- [Agent Identity Studio](#sec-053): that pipeline applied end to end, brand brief to rigged avatar plus studio renders.
- [Animations](#sec-093): the retargeting and clip library that drives the production rigs in the last family.
- [Avatar pipeline](#sec-113) and [avatar creation](#sec-109): how three.ws produces and processes its own mesh avatars.
@@ -32938,7 +32948,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-275), [x402 endpoints](#sec-539)).
+[MCP tools](#sec-279), [x402 endpoints](#sec-546)).
### ② Auto-rig
@@ -33017,7 +33027,7 @@ viewer, embeddable as a web component, and attachable to an agent. Paid
generation/editing is metered per call over x402; the free studio lane requires no
account. See [Avatar creation](#sec-109) and
[Avatar Studio](#sec-137) for the authoring UIs, and
-[Mesh editing tools](#sec-275) for retexture / stylize / remesh / segment /
+[Mesh editing tools](#sec-279) for retexture / stylize / remesh / segment /
pose operations.
## Related
@@ -33025,8 +33035,8 @@ pose operations.
- [Selfie → Avatar reconstruction](#sec-114) — the separate lane that fits a *person's photo* onto a rigged template (face texture + geometry morph), rather than generating a mesh from a prompt.
- [Animations](#sec-093) — the clip library and retargeting in depth.
- [3D asset pipeline](#sec-002) — formats, optimization, validation.
-- [NVIDIA free models](#sec-297) — the free generation backend.
-- [MCP tools](#sec-275) — every generation/editing tool and its price.
+- [NVIDIA free models](#sec-301) — the free generation backend.
+- [MCP tools](#sec-279) — every generation/editing tool and its price.
---
@@ -33366,9 +33376,9 @@ curl 'https://three.ws/api/avatars/<avatarId>' -H 'cookie: <session>'
## Related
- [Animation Studio](#sec-092): pose and keyframe the avatar you build here.
-- [Scene Composer](#sec-151): forge props and attach them to the avatar's bones as a saved outfit.
-- [Mocap Studio](#sec-284): drive the avatar's face live from your webcam.
-- [Restyle Studio](#sec-368): shares the same GLB optimize-and-validate path.
+- [Scene Composer](#sec-152): forge props and attach them to the avatar's bones as a saved outfit.
+- [Mocap Studio](#sec-288): drive the avatar's face live from your webcam.
+- [Restyle Studio](#sec-373): shares the same GLB optimize-and-validate path.
- [Trait-based avatar builder](#sec-137): the separate VRM studio embedded in the agent editor; a deep dive into its internals.
- [/create](https://three.ws/create): the hub for every avatar-creation path, including selfie-to-avatar.
@@ -34702,7 +34712,7 @@ Published 27 June 2026. Tags: `ai`, `agent-toolkit`, `blockchain`, `aws-partners
The platform-level piece: browser-native 3D AI agents with memory, on-chain wallets, and autonomous payments, available on AWS Marketplace, embeddable in one line of HTML, and governed before they act. Written for AWS builders evaluating three.ws as an agent runtime rather than as a 3D asset tool.
-- **Surfaces it covers:** [the `<agent-3d>` web component](#sec-508), [agent wallets](#sec-072), [the agent system](#sec-064), [AWS Marketplace procurement](#sec-123)
+- **Surfaces it covers:** [the `<agent-3d>` web component](#sec-514), [agent wallets](#sec-072), [the agent system](#sec-064), [AWS Marketplace procurement](#sec-123)
## Published by AWS about three.ws
@@ -34716,7 +34726,7 @@ Published 26 June 2026 by Kelly Wu (AWS). Part of the AWS-run series "AWS Partne
A builder's guide to the agentic economy that uses the three.ws stack as its worked example throughout: the x402 handshake and its three layers, MCP as the distribution layer for agent capabilities, agent-to-agent payments, on-chain agent identity (ERC-8004 and the SPL skill licenses), agent tokens on the bonding curve, and 3D embodiment. It walks the hosted MCP servers, the `@three-ws/*` payment SDKs, and the FSI use cases for per-call data access, and closes on the open problems: payment streaming, automatic cross-chain routing, agent reputation as a credit primitive, and org-scale spend governance.
-- **Surfaces it covers:** [the MCP servers](#sec-277), [x402](#sec-105), [agent wallets](#sec-072), [the `<agent-3d>` web component](#sec-508)
+- **Surfaces it covers:** [the MCP servers](#sec-281), [x402](#sec-105), [agent wallets](#sec-072), [the `<agent-3d>` web component](#sec-514)
- **Canonical URL note:** the Builder Center strips digits from slugs, so `x402` becomes `x` and `3d` becomes `d` in the path. The URL above is the one AWS publishes in its own [sitemap](https://builder.aws.com/sitemaps/articles/2026-6.xml); a slug containing the digits also resolves, because the content ID is what routes.
## In draft
@@ -35377,7 +35387,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-544), [three.ws/docs/mcp](#sec-277)
+- How agents reach and pay for tools: [three.ws/docs/x402](#sec-551), [three.ws/docs/mcp](#sec-281)
---
@@ -35392,9 +35402,9 @@ company: on their own website, in their own directory, or from their own social
account.
This doc is the cross-vendor dispatch board. Every other outreach doc in `docs/`
-is one vendor deep ([nvidia-visibility-map.md](#sec-300),
-[partners.md](#sec-318), [listings.md](#sec-265),
-[aws-marketplace.md](#sec-123), [ibm.md](#sec-250)). This one is the
+is one vendor deep ([nvidia-visibility-map.md](#sec-304),
+[partners.md](#sec-323), [listings.md](#sec-269),
+[aws-marketplace.md](#sec-123), [ibm.md](#sec-253)). This one is the
only place that ranks all of them against each other by the single question that
matters this week: **what is the probability of a published big-tech mention
within seven days, and what exactly is standing in the way?**
@@ -35463,11 +35473,11 @@ submission target is the free keyless connector at
Actions surface, all of which are live and re-verified.
- **Package:** [`prompts/store-submissions/_generated/openai-submission.md`](../prompts/store-submissions/_generated/openai-submission.md) (7/7 policy PASS, real screenshots, real captured tool responses)
-- **Pre-submission verification pack:** [`docs/openai-pr/00-START-HERE.md`](#sec-306), with task 07 as the go/no-go gate
+- **Pre-submission verification pack:** [`docs/openai-pr/00-START-HERE.md`](#sec-311), with task 07 as the go/no-go gate
- **Standing status:** Partner Network accepted 2026-07-14; organization verified; GPT Store listing live and public
- **Open item:** the final submit in the partner portal
-Before the submit, run [`docs/openai-pr/07-final-verification-and-submit.md`](#sec-313) against the currently deployed
+Before the submit, run [`docs/openai-pr/07-final-verification-and-submit.md`](#sec-318) against the currently deployed
revision. Its checklist exists precisely because the answer sheet asserts
"verified live" facts dated 2026-07-14 and deployments move. That is a
one-session job, not a blocker.
@@ -35514,7 +35524,7 @@ Two Anthropic surfaces are `ready-to-submit` (Official MCP Registry, Claude plug
marketplace) and a third, the Claude Connectors Directory, is blocked only on
provisioning an `MCP_REVIEW_SECRET` and a reviewer-credential decision.
-Worth naming plainly: **[partners.md](#sec-318) lists eight partners and
+Worth naming plainly: **[partners.md](#sec-323) lists eight partners and
Anthropic is not one of them**, even though the platform's agent brain defaults to
Claude models and there are three Anthropic-surface submissions sitting ready.
That is the most underdeveloped big-tech relationship on the board relative to how
@@ -35539,7 +35549,7 @@ and carries `#NVIDIAInception`. A post that merely names NVIDIA in prose is not
resharable by them. Without the kit, the X ambition has no mechanism behind it.
Send one email to `[email protected]` carrying all five asks. The
-existing [Apps Catalog request](#sec-295) is already
+existing [Apps Catalog request](#sec-299) is already
written and already addressed there; extend that draft rather than opening a
second thread. A program manager who receives one clear email with five asks
answers it. Five separate emails read as noise.
@@ -35556,7 +35566,7 @@ The five asks:
record currently describes three.ws as a CUDA consumer, which is wrong and which
gates both the Showcase and the Apps Catalog. Correct it at
`programs.nvidia.com/phoenix/application` first. The correction is already
-specified in step 1 of [nvidia-apps-catalog-listing.md](#sec-294).
+specified in step 1 of [nvidia-apps-catalog-listing.md](#sec-298).
Nothing in this email lands well while the record misdescribes the product.
---
@@ -35623,7 +35633,7 @@ promotes.
[three.ws/demos/audio2face](https://three.ws/demos/audio2face) (and the
`/audio2face` alias), served from
[`public/demos/audio2face.html`](../public/demos/audio2face.html) and documented in
-[demo-routes.md](#sec-173). Both routes returned 200 on 2026-08-17. You
+[demo-routes.md](#sec-175). Both routes returned 200 on 2026-08-17. You
type text, hear it in NVIDIA Magpie's voice, and watch the face animate through
ARKit blendshapes, in a browser tab, with no install.
@@ -35672,7 +35682,7 @@ Ordered so that the items with the longest external latency go out first.
| Day | Action | Owner |
|---|---|---|
-| Mon 08-17 | Run [openai-pr task 07](#sec-313) against the live revision, then **submit the OpenAI App Directory package** | Owner (portal) |
+| Mon 08-17 | Run [openai-pr task 07](#sec-318) against the live revision, then **submit the OpenAI App Directory package** | Owner (portal) |
| Mon 08-17 | Approve and run the staged **MCP Registry** publish; submit **`three-ws-3d`** to the Claude plugin marketplace | Owner (approval), agent (commands) |
| Tue 08-18 | Correct the **NVIDIA Inception portal product record** | Owner |
| Tue 08-18 | Send the **five-ask Inception email** to `[email protected]` | Owner |
@@ -35710,12 +35720,12 @@ Publishing, posting, and sending are owner-gated under stop-and-ask gate 2 in
## Related
-- [NVIDIA visibility map](#sec-300): every NVIDIA surface in depth, and the dead ends
-- [Partners](#sec-318): the eight programs, and the independence language that must survive any rewrite
-- [Listings and distribution](#sec-265): the canonical program and directory inventory
+- [NVIDIA visibility map](#sec-304): every NVIDIA surface in depth, and the dead ends
+- [Partners](#sec-323): the eight programs, and the independence language that must survive any rewrite
+- [Listings and distribution](#sec-269): the canonical program and directory inventory
- [Announcement coverage](#sec-095): which surfaces have been announced on X and which have not
-- [Press kit](#sec-333): marks, boilerplate, and the rules governing co-branded graphics
-- [OpenAI submission handoff pack](#sec-306): the pre-submission task briefs
+- [Press kit](#sec-338): marks, boilerplate, and the rules governing co-branded graphics
+- [OpenAI submission handoff pack](#sec-311): the pre-submission task briefs
---
@@ -36640,7 +36650,7 @@ done; wait
- [Agent Studio](#sec-062): the Brain tab uses this same backend
- [Agent System](#sec-064): how a chosen brain fits the agent model
-- [Persona Hub](#sec-323): synthesizing the system prompt a brain runs
+- [Persona Hub](#sec-328): synthesizing the system prompt a brain runs
- [API reference](#sec-096) and [Authentication](#sec-103)
- Pages: [/brain](https://three.ws/brain), [/agent-studio](https://three.ws/agent-studio)
@@ -36943,7 +36953,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-544)
+Paste a token contract address, get back a live, agent-payable [x402](#sec-551)
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.
@@ -37093,7 +37103,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-539) for the full
+back to the default. See [x402 paid endpoints](#sec-546) for the full
price-override scheme.
---
@@ -37109,7 +37119,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-540)).
+[x402 revenue and receipts](#sec-547)).
The paid response body is the token block computed fresh at call time:
@@ -37252,11 +37262,11 @@ right now. If the endpoint is unreachable the page says so and offers a retry.
## Related
-- [x402 on three.ws](#sec-544): the protocol, the wire format, and how the
+- [x402 on three.ws](#sec-551): the protocol, the wire format, and how the
platform settles.
-- [x402 paid endpoints](#sec-539): the full catalog of our paid
+- [x402 paid endpoints](#sec-546): the full catalog of our paid
endpoints, their prices, and the `X402_PRICE_*` override scheme.
-- [x402 revenue and receipts](#sec-540): where a settled payment for this
+- [x402 revenue and receipts](#sec-547): where a settled payment for this
endpoint is recorded and how the buyer's receipt is issued.
---
@@ -37358,9 +37368,9 @@ console.log(job.result_url, job.num_points); // coloured .ply + point count
## Related
-- [Splat Viewer](#sec-397) renders Gaussian-splat radiance fields, the photoreal cousin of point clouds.
+- [Splat Viewer](#sec-402) renders Gaussian-splat radiance fields, the photoreal cousin of point clouds.
- [/avatar-engines](https://three.ws/avatar-engines) covers the Geometric Context Transformer and related capture engines.
-- [Forge](#sec-225) and [Image to 3D](#sec-251) for generating meshes from prompts and photos.
+- [Forge](#sec-228) and [Image to 3D](#sec-254) for generating meshes from prompts and photos.
- Pages: [/scene](https://three.ws/scene) (Scene Studio), [/create](https://three.ws/create).
---
@@ -37712,7 +37722,7 @@ The Character Library is a free, curated gallery of professionally rigged humano
Page: [/character-library](https://three.ws/character-library) · API: `GET /api/avatars/library`
Source: [`pages/character-library.html`](../pages/character-library.html) · [`src/character-library.js`](../src/character-library.js) · [`api/avatars/library.js`](../api/avatars/library.js)
-> This page covers the character gallery and its API. For the motion clips these characters play, see [Animations](#sec-093). For the free prop counterpart to this library, see the [Object Library](#sec-301).
+> This page covers the character gallery and its API. For the motion clips these characters play, see [Animations](#sec-093). For the free prop counterpart to this library, see the [Object Library](#sec-305).
---
@@ -37728,8 +37738,8 @@ Each card renders the character live in an auto-rotating `<model-viewer>` (with
| Button | Destination | What you get |
|---|---|---|
-| **Preview** | `/app#model=<glb-url>` | The full three.js [3D viewer](#sec-505) |
-| **Use** | `/studio?model=<glb-url>` | [Widget Studio](#sec-510): configure and publish an embeddable widget of this character (see the [Embedding Guide](#sec-186)) |
+| **Preview** | `/app#model=<glb-url>` | The full three.js [3D viewer](#sec-511) |
+| **Use** | `/studio?model=<glb-url>` | [Widget Studio](#sec-516): configure and publish an embeddable widget of this character (see the [Embedding Guide](#sec-188)) |
| **Animate** | `/pose?src=<glb-url>&title=<name>` | [Animation Studio](#sec-092): pose, keyframe, and export motion on this character |
Gallery controls:
@@ -37741,7 +37751,7 @@ Gallery controls:
## API: `GET /api/avatars/library`
-Public, no authentication, `GET` and `OPTIONS` only (`HEAD` is answered like `GET`). Browser `fetch` from a third-party origin is not enabled: the endpoint sends `Access-Control-Allow-Origin` only for three.ws and its partner origins, exactly like the [Object Library API](#sec-301). Call it server-side, or from a three.ws page. The endpoint proxies a small manifest JSON from the R2 CDN (`avatars/library/manifest.json`) with an edge cache (`Cache-Control: public, s-maxage=300, stale-while-revalidate=3600`). The GLB and thumbnail bytes never pass through the API: every entry carries absolute CDN URLs the browser loads directly.
+Public, no authentication, `GET` and `OPTIONS` only (`HEAD` is answered like `GET`). Browser `fetch` from a third-party origin is not enabled: the endpoint sends `Access-Control-Allow-Origin` only for three.ws and its partner origins, exactly like the [Object Library API](#sec-305). Call it server-side, or from a three.ws page. The endpoint proxies a small manifest JSON from the R2 CDN (`avatars/library/manifest.json`) with an edge cache (`Cache-Control: public, s-maxage=300, stale-while-revalidate=3600`). The GLB and thumbnail bytes never pass through the API: every entry carries absolute CDN URLs the browser loads directly.
### Query parameters
@@ -37816,15 +37826,15 @@ The gallery and API are read-only consumers of a manifest built by a local pipel
3. `scripts/fetch-mixamo-avatar-thumbnails.mjs` stages the PNG thumbnails.
4. `scripts/build-mixamo-avatar-library.mjs` reads `public/avatars/mixamo/catalog.json`, merges the extra CC0 characters from `public/avatars/extra/characters.json`, and PUTs `avatars/library/manifest.json` to R2 (`--dry-run` prints without uploading).
-R2 CORS is configured by `scripts/set-r2-cors.mjs` so browsers can GET the GLBs cross-origin. The live bucket policy is an origin allowlist (`three.ws`, `*.vercel.app`, `localhost:3000`) that predates the world-open read rule now in that script, so a GLB loaded straight from the CDN on any other origin fails with no `access-control-allow-origin` header. Measure the live policy with `node scripts/set-r2-cors.mjs --probe`; until it is corrected, embeds on third-party origins should route the GLB through [`/api/glb`](media-api.md#same-origin-glb-proxy), as [the embed tutorial](#sec-428) does.
+R2 CORS is configured by `scripts/set-r2-cors.mjs` so browsers can GET the GLBs cross-origin. The live bucket policy is an origin allowlist (`three.ws`, `*.vercel.app`, `localhost:3000`) that predates the world-open read rule now in that script, so a GLB loaded straight from the CDN on any other origin fails with no `access-control-allow-origin` header. Measure the live policy with `node scripts/set-r2-cors.mjs --probe`; until it is corrected, embeds on third-party origins should route the GLB through [`/api/glb`](media-api.md#same-origin-glb-proxy), as [the embed tutorial](#sec-434) does.
## Related
- [Animations](#sec-093): the clip library every character drives, and how retargeting works.
- [Animation Studio](#sec-092): the `/pose` surface the Animate button opens.
-- [Widget Studio](#sec-510) and the [Embedding Guide](#sec-186): turn a library character into a live embed on any site.
-- [Object Library](#sec-301): the same free-library pattern for CC0 props and scene objects.
-- [Marketplace](#sec-270): library characters are free; the marketplace is where priced avatars, agents, and skills are bought and sold.
+- [Widget Studio](#sec-516) and the [Embedding Guide](#sec-188): turn a library character into a live embed on any site.
+- [Object Library](#sec-305): the same free-library pattern for CC0 props and scene objects.
+- [Marketplace](#sec-274): library characters are free; the marketplace is where priced avatars, agents, and skills are bought and sold.
---
@@ -38311,7 +38321,7 @@ The same free lane ships into ChatGPT twice, because ChatGPT has two integration
### 1. The ChatGPT app (Apps SDK / MCP connector)
-The MCP connector at `https://three.ws/api/mcp-studio` (no authentication) exposes ten free tools: six generation tools (`forge_free`, `text_to_avatar`, `mesh_forge`, `rig_mesh`, `forge_avatar`, `refine_model`), the `check_job` collector that picks up a generation which outran the tool call, and three persona/embodiment tools (`create_agent_persona`, `get_agent_persona`, `persona_say`). Full server documentation: [3D Studio MCP](#sec-274).
+The MCP connector at `https://three.ws/api/mcp-studio` (no authentication) exposes ten free tools: six generation tools (`forge_free`, `text_to_avatar`, `mesh_forge`, `rig_mesh`, `forge_avatar`, `refine_model`), the `check_job` collector that picks up a generation which outran the tool call, and three persona/embodiment tools (`create_agent_persona`, `get_agent_persona`, `persona_say`). Full server documentation: [3D Studio MCP](#sec-278).
Every successful tool result carries `arUrl` in its `structuredContent`, and the inline 3D widget renders it as a **View in your space** button next to the rotatable model. When the result is a rigged avatar the response additionally carries `irlUrl` and the button becomes **Bring it to life**. Refined versions (`refine_model`) each carry their own `arUrl`, so any point in the version lineage can be placed in the room.
@@ -38373,7 +38383,7 @@ The pure routing logic (`detectArTarget`, `buildSceneViewerUrl`, `planArLaunch`)
AR on three.ws is not a prop viewer; it is how agents cross into physical space. When the generated model is a rigged avatar (an agent's body), the pipeline appends `kind=avatar` to the `arUrl`, and the launcher changes behavior:
-- The launch page leads with a **Bring it to life** handoff into [`/irl?avatar=<glbUrl>`](/irl), where the avatar walks, animates, and talks with the user through the camera, standing in their real room. See [IRL](#sec-256).
+- The launch page leads with a **Bring it to life** handoff into [`/irl?avatar=<glbUrl>`](/irl), where the avatar walks, animates, and talks with the user through the camera, standing in their real room. See [IRL](#sec-259).
- Android is NOT blind-redirected into Scene Viewer, because that would hide the living path. It gets the launch page too, with static placement still one tap away.
In ChatGPT this happens automatically: the avatar-producing tools (`text_to_avatar`, `rig_mesh`, `forge_avatar`) set the flag and return `irlUrl` alongside `arUrl`, and the inline widget swaps its button label accordingly.
@@ -38396,7 +38406,7 @@ A place-in-your-room link is built to be forwarded. When it is pasted into a cha
Everything above is public plumbing:
- **Plain HTTP, free:** `POST /api/3d/generate` is the keyless agent-facing twin of the studio endpoint, same lane, same `arUrl`. Contract, states, and per-IP limits: [the free 3D API](#sec-001).
-- **Any MCP client:** the connector at `/api/mcp-studio` works in Claude and every other MCP host, not just ChatGPT. Every generation it returns already carries `arUrl` (and `irlUrl` for rigged avatars) plus a [Spatial MCP](#sec-395) artifact, so no extra tool call is needed to get the AR link. To build that link set for a GLB the connector did **not** generate, use the read-only `export_ar` tool on the separate [`/api/mcp-3d` server](#sec-271), which returns `arLaunchUrl`, `sceneViewerUrl`, `viewerUrl`, and `irlUrl`. That server is account- or payment-gated and is not part of the free connector.
+- **Any MCP client:** the connector at `/api/mcp-studio` works in Claude and every other MCP host, not just ChatGPT. Every generation it returns already carries `arUrl` (and `irlUrl` for rigged avatars) plus a [Spatial MCP](#sec-400) artifact, so no extra tool call is needed to get the AR link. To build that link set for a GLB the connector did **not** generate, use the read-only `export_ar` tool on the separate [`/api/mcp-3d` server](#sec-275), which returns `arLaunchUrl`, `sceneViewerUrl`, `viewerUrl`, and `irlUrl`. That server is account- or payment-gated and is not part of the free connector.
- **By hand:** the `arUrl` format is stable. If you have a public GLB, you can construct `https://three.ws/api/ar?src=<encoded GLB>&title=<name>` yourself and it will route correctly on every device.
The generation lane is operator-funded (NVIDIA NIM running Microsoft TRELLIS for text-to-3D), so the end user pays nothing and needs no account; real per-IP rate limits apply and are documented per endpoint.
@@ -38422,10 +38432,10 @@ The generation lane is operator-funded (NVIDIA NIM running Microsoft TRELLIS for
- [Your first prompt to 3D in ChatGPT](/tutorials/first-prompt-to-3d): the user-facing walkthrough of this whole flow
- [Place your 3D model in AR](/tutorials/view-in-ar): the on-site AR tutorial
-- [3D Studio MCP](#sec-274): the free MCP server behind the ChatGPT app
+- [3D Studio MCP](#sec-278): the free MCP server behind the ChatGPT app
- [The free 3D API](#sec-001): the keyless HTTP contract with `arUrl`
- [AR and WebXR reference](#sec-099): Quick Look, Scene Viewer, WebXR, and the USDZ pipeline in depth
-- [IRL](#sec-256): the living-agent experience behind Bring it to life
+- [IRL](#sec-259): the living-agent experience behind Bring it to life
---
@@ -38544,7 +38554,7 @@ Rules worth knowing before you call it:
### From an embed
-Any page already rendering an [`<agent-3d>`](#sec-186) element can perform the agent's saved routines by name:
+Any page already rendering an [`<agent-3d>`](#sec-188) element can perform the agent's saved routines by name:
```html
<agent-3d agent="YOUR_AGENT_ID"></agent-3d>
@@ -38673,9 +38683,9 @@ Coming from [/gestures](https://three.ws/gestures), the **Use in a routine** but
## Related
- [Animations](#sec-093): clips, collections, and the slot vocabulary underneath every routine
-- [Procedural animation](#sec-334): the IK layers that run on top of whatever clip is playing
+- [Procedural animation](#sec-339): the IK layers that run on top of whatever clip is playing
- [Agent manifest](#sec-055): the public document that carries `choreographies` to embeds
-- [Embedding an agent](#sec-186): the `<agent-3d>` element these methods live on
+- [Embedding an agent](#sec-188): the `<agent-3d>` element these methods live on
---
@@ -38841,7 +38851,7 @@ covered by [tests/circulation-three-topup.test.js](../tests/circulation-three-to
The engine runs from the `pulse-tick` cron
([api/cron/pulse-tick.js](../api/cron/pulse-tick.js)), which is fanned out every
**minute** by the `economy-tick` dispatcher (see the
-[economy heartbeat](#sec-181)) rather than scheduled on its own.
+[economy heartbeat](#sec-183)) rather than scheduled on its own.
Each tick grows the pool by up to `CIRCULATION_GROWTH_PER_TICK` agents and runs
`CIRCULATION_ACTIONS_PER_TICK` everyday actions (plus any heavyweight action that
wins first refusal). The `pulse-tick` function is bounded to a 120-second
@@ -38874,9 +38884,9 @@ loop as a payout.
| Sink | What it holds |
|---|---|
| `circulation_actions` | One row per action the engine ran (kind, actors, signature, amount). |
-| `agent_custody_events` | The canonical wallet ledger entry for every real spend/transfer (see [Money feed](#sec-285)). |
+| `agent_custody_events` | The canonical wallet ledger entry for every real spend/transfer (see [Money feed](#sec-289)). |
| `pump_agent_trades` / `pump_agent_mints` | Trade and launch records, surfaced in the pump feed and `/launches`. |
-| `skill_purchases` / `asset_purchases` | Marketplace settlement records (see [Marketplace](#sec-270)). |
+| `skill_purchases` / `asset_purchases` | Marketplace settlement records (see [Marketplace](#sec-274)). |
Real spends are written to `agent_custody_events`, which powers per-agent
portfolio balances and the agent-to-agent economy volume dashboard (all-time and
@@ -38911,11 +38921,11 @@ budget, so raise gradually and watch tick runtime and treasury balance.
## Related
-- [Money feed](#sec-285): where circulation activity surfaces.
+- [Money feed](#sec-289): where circulation activity surfaces.
- [Autonomous x402 loop](#sec-105): the separate treasury-paid loop
that buys polling intel from our own x402 endpoints.
- [Agent wallets](#sec-072): the custodial key model every action uses.
-- [Marketplace](#sec-270), [Coin launches](#sec-144).
+- [Marketplace](#sec-274), [Coin launches](#sec-144).
---
@@ -38933,7 +38943,7 @@ API: `/api/clash/[action]` with `action` one of `state`, `enlist`, `enlist-verif
## Why it exists
-Coin communities already behave like tribes. Coin Clash gives that tribalism a game loop with real stakes of identity: you can only fight for a coin you actually hold, so rallying is a public act of conviction, and a community's showing on the board is a live measure of how many holders will show up. The token gate is a real balance read, not a client-side check, which makes it a working demonstration of the same "hold, do not just claim" primitive used across the platform (see [token-gated 3D embeds](#sec-407) and [hold to access](#sec-238)). Effort wins, not market cap: a battle is decided by summed taps, so a smaller, more active army can beat a larger, quieter one.
+Coin communities already behave like tribes. Coin Clash gives that tribalism a game loop with real stakes of identity: you can only fight for a coin you actually hold, so rallying is a public act of conviction, and a community's showing on the board is a live measure of how many holders will show up. The token gate is a real balance read, not a client-side check, which makes it a working demonstration of the same "hold, do not just claim" primitive used across the platform (see [token-gated 3D embeds](#sec-412) and [hold to access](#sec-241)). Effort wins, not market cap: a battle is decided by summed taps, so a smaller, more active army can beat a larger, quieter one.
## How it works
@@ -38997,10 +39007,10 @@ The Coin Clash state and leaderboard are also exposed read-only over MCP through
## Related
-- [Token-gated 3D embeds](#sec-407): the same real on-chain balance gate, applied to embeds
-- [Hold to access](#sec-238): the platform's broader hold-do-not-spend membership thesis
-- [The social layer](#sec-391): platform-wide feed, follows, and leaderboards
-- [MCP tools](#sec-277): the read-only Clash MCP server
+- [Token-gated 3D embeds](#sec-412): the same real on-chain balance gate, applied to embeds
+- [Hold to access](#sec-241): the platform's broader hold-do-not-spend membership thesis
+- [The social layer](#sec-396): platform-wide feed, follows, and leaderboards
+- [MCP tools](#sec-281): the read-only Clash MCP server
- Pages: [/clash](https://three.ws/clash) · [/communities](https://three.ws/communities)
---
@@ -39115,7 +39125,7 @@ message instead of an error, so a card is only ever minted from a real closed ro
## The page
[/clip-director](https://three.ws/clip-director) fills its trader picker from
-`GET /api/mirror/leaderboard?settled_min=1`, the [copy-trading](#sec-165)
+`GET /api/mirror/leaderboard?settled_min=1`, the [copy-trading](#sec-167)
ranking narrowed to agents that actually have a closed round-trip. That parameter is
load-bearing: the page used to ask for the top agents by composite score and filter for
a track record client side, and because score does not correlate with having settled
@@ -39129,9 +39139,9 @@ comes back. Each card's CTA is a real link: `copy-the-agent` and `fork-this-trad
## Related
-- [Trader Card & the claim-your-wallet wedge](#sec-409)
-- [Meta-Allocator: the ETF of degens](#sec-281)
-- [The trading surfaces](#sec-415) · [The Arena](https://three.ws/arena)
+- [Trader Card & the claim-your-wallet wedge](#sec-414)
+- [Meta-Allocator: the ETF of degens](#sec-285)
+- [The trading surfaces](#sec-420) · [The Arena](https://three.ws/arena)
- [Animations & gestures](#sec-093)
---
@@ -39170,7 +39180,7 @@ The user holds the keys; the platform never signs for them.
The agent launcher signs and submits with the agent's **custodial** Solana keypair
server-side (`launch-agent`), through the protected execution path
(`submitProtected()`). Spend caps are checked before signing (see
-[Agent wallets](#sec-170)), and the mint is registered in
+[Agent wallets](#sec-172)), and the mint is registered in
`pump_agent_mints`. The `launcher-tick` cron (every minute) drives the
autonomous launcher engine (`api/_lib/launcher-engine.js`), bounded by
per-launch and daily SOL caps, an hourly ceiling, a cadence gate, and a circuit
@@ -39186,7 +39196,7 @@ inert. The [circulation engine](#sec-141) also runs its own
| Quote mint | Resolved to the network-correct pairing (USDC mint or SOL-paired). |
| Dev buy | A small initial buy can accompany the create (the `LAUNCH_FLOOR` covers create + tiny dev buy + fees). |
| Buyback authority | A buyback basis-points configuration can be attached to the agent mint. |
-| Mint mark | When `THREE_WS_MARK_ENFORCE` is on (the default; set `0`/`false` to disable), the mint address is vanity-ground to carry the three.ws mark (see [Mint mark](#sec-282), [Vanity protocol](#sec-005)). |
+| Mint mark | When `THREE_WS_MARK_ENFORCE` is on (the default; set `0`/`false` to disable), the mint address is vanity-ground to carry the three.ws mark (see [Mint mark](#sec-286), [Vanity protocol](#sec-005)). |
## Recording and surfacing
@@ -39195,7 +39205,7 @@ inert. The [circulation engine](#sec-141) also runs its own
| `pump_agent_mints` (mint + network keyed) | `/launches` feed, agent-profile launch history. |
| `pump_agent_trades` | Trade history for the mint. |
| `agent_custody_events` | The on-chain spend (create + dev buy). |
-| Live ticker | `coin-buy` / `agent-deploy` events (see [Money feed](#sec-285)). |
+| Live ticker | `coin-buy` / `agent-deploy` events (see [Money feed](#sec-289)). |
The `launches`, `by-agent`, and `quote` actions on `api/pump/[action].js` read
these back for the directory and detail pages. Coin detail pages render a live
@@ -39219,10 +39229,10 @@ hardcode or surface any other specific mint as a recommendation.
## Related
-- [Solana pump.fun signals](#sec-392) — reputation/intel from pump.fun activity.
-- [Agent wallets](#sec-170) — custodial signing and spend caps.
+- [Solana pump.fun signals](#sec-397) — reputation/intel from pump.fun activity.
+- [Agent wallets](#sec-172) — custodial signing and spend caps.
- [Circulation engine](#sec-141) — autonomous launch cadence and caps.
-- [Mint mark](#sec-282), [Vanity protocol](#sec-005).
+- [Mint mark](#sec-286), [Vanity protocol](#sec-005).
---
@@ -40038,7 +40048,7 @@ battlefield. `return` is only ever honoured as a same-origin path.
| The endpoint + store | [`api/wars.js`](../api/wars.js), [`api/_lib/wars-store.js`](../api/_lib/wars-store.js) |
| Tests | [`tests/war-matchmaking.test.js`](../tests/war-matchmaking.test.js), [`tests/clash-match.test.js`](../tests/clash-match.test.js) |
-Related: [the in-game economy](#sec-252), [play hardening](#sec-327).
+Related: [the in-game economy](#sec-255), [play hardening](#sec-332).
---
@@ -40785,6 +40795,51 @@ at [community.ibm.com](https://community.ibm.com/community/user/usergroup?Commun
<a id="sec-151"></a>
+> **Source:** `docs/community.md` · [↑ table of contents](#table-of-contents)
+
+# Community
+
+three.ws is built in the open and the conversation happens in public. Pick the room that fits what you want to do.
+
+## Where to find us
+
+| Channel | Best for | Link |
+|---|---|---|
+| **GitHub Discussions** | Design questions, feature ideas, showing off what you built, anything worth keeping searchable | [github.com/nirholas/three.ws/discussions](https://github.com/nirholas/three.ws/discussions) |
+| **Telegram community** | Real-time chat, quick help, "is this thing on?" | [t.me/three_ws_community](https://t.me/three_ws_community) |
+| **X community** | Demos, avatars people made, launch chatter | [x.com/i/communities/1923523161230078106](https://x.com/i/communities/1923523161230078106) |
+| **IBM Community group** | Enterprise and integration discussion with the IBM developer community | [community.ibm.com group](https://community.ibm.com/community/user/usergroup?CommunityKey=e71510cc-d953-408f-9a1c-019f5c0a7016) |
+| **Release channel** | Every user-visible change, pushed automatically on deploy | [t.me/three_ws](https://t.me/three_ws) and [/changelog](https://three.ws/changelog) |
+| **Issues** | Bugs and concrete feature requests | [github.com/nirholas/three.ws/issues](https://github.com/nirholas/three.ws/issues) |
+| **Security** | Vulnerabilities, privately | [Report an advisory](https://github.com/nirholas/three.ws/security/advisories/new) |
+
+Announcements also go out on [@trythreews](https://x.com/trythreews).
+
+## Which channel for which question
+
+- **"How do I embed an avatar on my site?"** Discussions, Q&A category. The answer helps the next person who searches it.
+- **"The avatar renders as a T-pose."** Open an [issue](https://github.com/nirholas/three.ws/issues/new/choose) with the GLB or a link to it. Rig problems are almost always reproducible and we want the file.
+- **"Look what I made."** [Show and tell](https://github.com/nirholas/three.ws/discussions/categories/show-and-tell) on Discussions, or the X community. We repost good ones.
+- **"Is anyone working on X? I want to help."** Check [`good first issue`](https://github.com/nirholas/three.ws/labels/good%20first%20issue) first, then say so in the issue thread so nobody duplicates your work.
+- **"I found a security hole."** Never a public issue. Use the [advisory form](https://github.com/nirholas/three.ws/security/advisories/new).
+
+## House rules
+
+The [Code of Conduct](../CODE_OF_CONDUCT.md) applies in every one of these rooms, not just the GitHub ones. It is the Contributor Covenant, and it is enforced.
+
+Two additions specific to this project:
+
+- **No trading talk in the technical channels.** three.ws has on-chain surfaces and there is a token in the ecosystem. Price talk belongs nowhere near a bug thread. Issues and Discussions are for the software.
+- **Share the file.** Rendering and rigging bugs are hard to guess at and trivial to diagnose from the actual GLB. If you can share the model, share it.
+
+## Contributing
+
+New here? Start with [Your first contribution](#sec-224), a 15-minute path from clone to open PR. The full guide is [CONTRIBUTING.md](../CONTRIBUTING.md), and how we sort incoming work is documented in [Triage](#sec-421).
+
+---
+
+<a id="sec-152"></a>
+
> **Source:** `docs/compose.md` · [↑ table of contents](#table-of-contents)
# Scene Composer: dress an avatar and stage a scene
@@ -40866,13 +40921,13 @@ curl -X PATCH 'https://three.ws/api/avatars/<avatarId>' \
- [Avatar Studio](#sec-115): build the avatar you dress here.
- [Animation Studio](#sec-092): pose and animate the dressed avatar.
-- [Scene Studio](#sec-373): the full three.js editor for heavier scene authoring.
-- [Restyle Studio](#sec-368): re-skin the forged props before attaching them.
+- [Scene Studio](#sec-378): the full three.js editor for heavier scene authoring.
+- [Restyle Studio](#sec-373): re-skin the forged props before attaching them.
- [/forge](https://three.ws/forge): the text-to-3D generator behind the prompt box.
---
-<a id="sec-152"></a>
+<a id="sec-153"></a>
> **Source:** `docs/concierge.md` · [↑ table of contents](#table-of-contents)
@@ -40980,12 +41035,12 @@ Runnable examples ship with the SDK ([concierge-sdk/examples/](https://github.co
## Related surfaces
- [/walk](/walk): the walking page companion the avatar engine grew from
-- [Share and embed](#sec-378): every other way to put a three.ws creation on your site
-- [MCP](#sec-277): the full catalog of three.ws MCP servers, including this one
+- [Share and embed](#sec-383): every other way to put a three.ws creation on your site
+- [MCP](#sec-281): the full catalog of three.ws MCP servers, including this one
---
-<a id="sec-153"></a>
+<a id="sec-154"></a>
> **Source:** `docs/configuration.md` · [↑ table of contents](#table-of-contents)
@@ -41041,7 +41096,7 @@ After setting this, provision the schema:
npm run db:bootstrap
```
-This runs all four provisioning steps (core schema + indexer + delegations + migrations) and is idempotent — safe to re-run. Do not apply `api/_lib/schema.sql` alone: the base schema does not create the migration-defined tables and leaves a half-provisioned database (see [deployment.md](#sec-174)).
+This runs all four provisioning steps (core schema + indexer + delegations + migrations) and is idempotent — safe to re-run. Do not apply `api/_lib/schema.sql` alone: the base schema does not create the migration-defined tables and leaves a half-provisioned database (see [deployment.md](#sec-176)).
#### `JWT_SECRET`
**Required.** Long random secret used for two purposes: signing session JWTs and (via HKDF) deriving the AES-256-GCM key that encrypts agent wallet private keys.
@@ -41539,7 +41594,7 @@ Before going live, verify the following:
---
-<a id="sec-154"></a>
+<a id="sec-155"></a>
> **Source:** `docs/content/use-cases/README.md` · [↑ table of contents](#table-of-contents)
@@ -41551,11 +41606,11 @@ Five "here's how three.ws solves *your* problem" narratives, one per audience. E
| Audience | File | The job-to-be-done |
| --- | --- | --- |
-| Indie creator | [indie-creator.md](#sec-159) | Turn a selfie or a text prompt into a 3D agent and embed it anywhere. |
-| Game studio | [game-studio.md](#sec-158) | Drop a GLB pipeline, an LLM-driven NPC runtime, and a live multiplayer world into a game. |
-| AI-agent developer | [ai-agent-developer.md](#sec-155) | Give an agent a body, paid endpoints (x402), an MCP/A2A interface, and on-chain identity. |
-| Brand / marketer | [brand-marketer.md](#sec-156) | Put an embeddable, verifiable talking agent on a site, distributed through cloud marketplaces. |
-| Crypto community | [crypto-community.md](#sec-157) | Give a token community a live 3D world, an agent economy, and on-chain reputation. |
+| Indie creator | [indie-creator.md](#sec-160) | Turn a selfie or a text prompt into a 3D agent and embed it anywhere. |
+| Game studio | [game-studio.md](#sec-159) | Drop a GLB pipeline, an LLM-driven NPC runtime, and a live multiplayer world into a game. |
+| AI-agent developer | [ai-agent-developer.md](#sec-156) | Give an agent a body, paid endpoints (x402), an MCP/A2A interface, and on-chain identity. |
+| Brand / marketer | [brand-marketer.md](#sec-157) | Put an embeddable, verifiable talking agent on a site, distributed through cloud marketplaces. |
+| Crypto community | [crypto-community.md](#sec-158) | Give a token community a live 3D world, an agent economy, and on-chain reputation. |
## How to read these (the honesty frame)
@@ -41584,7 +41639,7 @@ Every scenario on these pages is an **example workflow** — clearly labeled "Im
---
-<a id="sec-155"></a>
+<a id="sec-156"></a>
> **Source:** `docs/content/use-cases/ai-agent-developer.md` · [↑ table of contents](#table-of-contents)
@@ -41604,8 +41659,8 @@ 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-277) 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-544) 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.
+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.
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/`.
@@ -41613,8 +41668,8 @@ 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-277) 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-544): 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.
+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.
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.
@@ -41625,14 +41680,14 @@ A standards-based interface (MCP + A2A), a working USDC payment rail (x402 on Ba
## Next step / CTA
-- Start: [MCP setup](#sec-277) · [x402 docs](#sec-544) · [SDK docs](#sec-374) · register via [Register On-Chain](#sec-462).
+- Start: [MCP setup](#sec-281) · [x402 docs](#sec-551) · [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.]`
---
-<a id="sec-156"></a>
+<a id="sec-157"></a>
> **Source:** `docs/content/use-cases/brand-marketer.md` · [↑ table of contents](#table-of-contents)
@@ -41674,7 +41729,7 @@ Four real capabilities cover embodiment, reach, and trust:
width="340px" height="440px"
></agent-3d>
```
-3. She [registers the agent on-chain](#sec-462) (Metaplex Core on Solana), binds `brand.threews.sol`, and links the public [passport](https://three.ws/a/sol/EXAMPLE_ASSET) from the site footer as a "verified official agent" badge — so look-alikes can't credibly impersonate it.
+3. She [registers the agent on-chain](#sec-468) (Metaplex Core on Solana), binds `brand.threews.sol`, and links the public [passport](https://three.ws/a/sol/EXAMPLE_ASSET) from the site footer as a "verified official agent" badge — so look-alikes can't credibly impersonate it.
4. For enterprise procurement, she points buyers at the [AWS Marketplace listing](https://three.ws/aws) (a listing, not an endorsement).
5. **Deliverable:** a premium, on-brand talking agent on every page, provably the official one via its on-chain passport, with an enterprise procurement path.
@@ -41684,14 +41739,14 @@ A conversational 3D brand presence that's easy to embed and share, plus a public
## Next step / CTA
-- Start: [Widget Studio](https://three.ws/studio) → [Register On-Chain](#sec-462) → claim a name at [`/threews/claim`](https://three.ws/threews/claim).
+- Start: [Widget Studio](https://three.ws/studio) → [Register On-Chain](#sec-468) → claim a name at [`/threews/claim`](https://three.ws/threews/claim).
- Enterprise: [AWS Marketplace listing](#sec-123) · [Alibaba Cloud listing](https://marketplace.alibabacloud.com/products/56724001/sgcmfw00036800.html) · explore Granite on watsonx.ai at [/ibm](https://three.ws/ibm).
- **Social spotlight angle (G03):** "A talking brand agent you can *prove* is official — embedded everywhere, verifiable on-chain."
- `[REAL CASE STUDY — fill on consent: a brand that deployed a verified on-site agent and what it changed.]`
---
-<a id="sec-157"></a>
+<a id="sec-158"></a>
> **Source:** `docs/content/use-cases/crypto-community.md` · [↑ table of contents](#table-of-contents)
@@ -41712,7 +41767,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-544) (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-551) (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)
@@ -41721,7 +41776,7 @@ Three real surfaces turn a token into a living world with its own economy:
1. A community lead opens [`/communities`](https://three.ws/communities), finds the `$THREE` world, and shares the direct link. Holders open it and land in the same [3D `$THREE` home town](https://three.ws/play) — they see each other's avatars, chat, drop emotes, and build with voxels while a live market-cap screen ticks in-world. (`$THREE` CA: `FeMbDoX7R1Psc4GEcvJdsbNbZA3bfztcyDCatJVJpump`.)
2. In the home town, holders watch the resident agents pay each other on-chain via x402 — a working agent-exchange where one agent buys a service from another in USDC, settled on Solana — a concrete demo of the agent economy the community is part of.
-3. Active contributors register agents with [on-chain identity](#sec-462), accruing a signed action history and a [reputation](https://three.ws/reputation) score that can't be forged — a durable signal of who actually showed up.
+3. Active contributors register agents with [on-chain identity](#sec-468), accruing a signed action history and a [reputation](https://three.ws/reputation) score that can't be forged — a durable signal of who actually showed up.
4. The community uses [`/pump-visualizer`](https://three.ws/pump-visualizer) to surface live `$THREE` activity inside the world, tying market events to the shared space.
5. **Deliverable:** a persistent, multiplayer `$THREE` world where holders gather, a live agent economy they can watch settle on-chain, and an on-chain reputation layer that rewards real participation.
@@ -41732,13 +41787,13 @@ 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-544) for the agent-economy rails · [Register On-Chain](#sec-462) for reputation.
+- Build: [x402 docs](#sec-551) 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.]`
---
-<a id="sec-158"></a>
+<a id="sec-159"></a>
> **Source:** `docs/content/use-cases/game-studio.md` · [↑ table of contents](#table-of-contents)
@@ -41779,13 +41834,13 @@ A character that renders with production-grade glTF handling, converses through
## Next step / CTA
- Start: [`/app`](https://three.ws/app) to render a GLB, then [`/walk`](https://three.ws/walk) for the shared world. The Colyseus server lives in `multiplayer/`.
-- Learn: [Write a Custom Skill](#sec-432) · [Agent System docs](#sec-064) · [Skill spec](../specs/SKILL_SPEC.md).
+- Learn: [Write a Custom Skill](#sec-438) · [Agent System docs](#sec-064) · [Skill spec](../specs/SKILL_SPEC.md).
- **Social spotlight angle (G03):** "An NPC that emotes and hands out quests through a real tool-loop — plus a shared world players walk into together."
- `[REAL CASE STUDY — fill on consent: a studio that shipped a three.ws-powered NPC or multiplayer hub.]`
---
-<a id="sec-159"></a>
+<a id="sec-160"></a>
> **Source:** `docs/content/use-cases/indie-creator.md` · [↑ table of contents](#table-of-contents)
@@ -41839,13 +41894,13 @@ A real, embedded, conversational 3D avatar that loads in any modern browser. The
## Next step / CTA
- Start: [`/scan`](https://three.ws/scan) (selfie) or `/forge` (text) → [Embed Editor](https://three.ws/embed).
-- Learn: [Build Your First Agent](#sec-441) · [Embed on Your Website](#sec-437).
+- Learn: [Build Your First Agent](#sec-447) · [Embed on Your Website](#sec-443).
- **Social spotlight angle (G03):** "From one selfie to a talking 3D you, embedded in your bio — no Blender."
- `[REAL CASE STUDY — fill on consent: an indie creator who shipped an embedded agent and the response it got.]`
---
-<a id="sec-160"></a>
+<a id="sec-161"></a>
> **Source:** `docs/contributing.md` · [↑ table of contents](#table-of-contents)
@@ -41920,7 +41975,7 @@ npm run dev
Most features work without the optional services. The app degrades gracefully, so basic 3D viewer work, skill development, and UI changes don't require any backend credentials.
-For full backend setup — R2 storage, environment variables, and how the app is deployed — see the [Configuration Reference](#sec-153) and the [Deployment & Self-Hosting](#sec-174) guide.
+For full backend setup — R2 storage, environment variables, and how the app is deployed — see the [Configuration Reference](#sec-154) and the [Deployment & Self-Hosting](#sec-176) guide.
---
@@ -41954,7 +42009,7 @@ src/
└── components/ — vhtml JSX components (string-based, no virtual DOM)
```
-See the [Architecture Overview](#sec-255) for a deeper understanding of how these pieces connect.
+See the [Architecture Overview](#sec-258) for a deeper understanding of how these pieces connect.
---
@@ -42122,7 +42177,7 @@ Skills are the best way to extend three.ws without touching core code. A skill i
1. **Use the template.** Copy `examples/skills/solana-wallet/` as your starting point — its `manifest.json`, `tools.json`, `handlers.js`, and `SKILL.md` demonstrate the minimal structure a skill needs.
-2. **Build your skill.** See the [Skills documentation](#sec-387) for the full format, lifecycle hooks, and message API.
+2. **Build your skill.** See the [Skills documentation](#sec-392) for the full format, lifecycle hooks, and message API.
3. **Host it.** GitHub Pages, Vercel, Netlify, or any static CDN works. The URL just needs to be publicly accessible over HTTPS.
@@ -42158,7 +42213,7 @@ Open a [GitHub issue](https://github.com/nirholas/three.ws/issues/new) and inclu
Check [existing issues](https://github.com/nirholas/three.ws/issues) before opening a new one to avoid duplicates.
-**Security vulnerabilities:** Do NOT open a public issue. Follow the responsible disclosure process described in the [Security documentation](#sec-375). Public disclosure of an unpatched vulnerability puts all users at risk.
+**Security vulnerabilities:** Do NOT open a public issue. Follow the responsible disclosure process described in the [Security documentation](#sec-380). Public disclosure of an unpatched vulnerability puts all users at risk.
---
@@ -42172,7 +42227,7 @@ Core team response times: typically 2-3 business days on GitHub. If a PR has bee
## License
-By contributing, you agree that your contributions are provided under the terms of the repository's [LICENSE](../LICENSE) (proprietary, all rights reserved). Read it before submitting substantial work.
+By contributing, you agree that your contributions are licensed under the [Apache License 2.0](../LICENSE), the same license the repository ships under.
---
@@ -42185,7 +42240,133 @@ By contributing, you agree that your contributions are provided under the terms
---
-<a id="sec-161"></a>
+<a id="sec-162"></a>
+
+> **Source:** `docs/contributing/discussion-seeds.md` · [↑ table of contents](#table-of-contents)
+
+# Discussion seeds
+
+Three ready-to-post GitHub Discussions that turn an empty Discussions tab into a live community front door. Written 2026-08-21 for the Open Source Friday application (see [../open-source-friday-plan.md](#sec-309)), where a community conversation channel is a preference criterion and an empty tab reads as nobody being home.
+
+**These are not posted yet.** The automation token in this workspace has `issues: write` but not `discussions: write`, so a human has to paste them. Each takes about 20 seconds:
+
+| Post | Category | New-discussion link |
+|---|---|---|
+| Welcome | Announcements | [new](https://github.com/nirholas/three.ws/discussions/new?category=announcements) |
+| Show and tell | Show and tell | [new](https://github.com/nirholas/three.ws/discussions/new?category=show-and-tell) |
+| Roadmap | Ideas | [new](https://github.com/nirholas/three.ws/discussions/new?category=ideas) |
+
+Pin the Welcome post after publishing it. Delete this file once all three are live, or leave it as the record of what was posted.
+
+---
+
+## 1. Welcome (Announcements, pin it)
+
+**Title:** `Welcome to three.ws: start here, and introduce yourself`
+
+```markdown
+Welcome. This is the front door for the three.ws community, so start here and say hello.
+
+**three.ws** is an open framework for 3D AI agents on the web. A text prompt becomes a rigged, animation-ready avatar, and one `<agent-3d>` tag drops it into any page with an LLM brain, memory, and moods behind it. Browser-native: Three.js and glTF, no plugin, no game engine.
+
+## Introduce yourself
+
+Reply with:
+
+- What you build, or what brought you here
+- What you would use a 3D agent for
+- One thing that is currently harder than it should be
+
+That last one is the most useful thing you can give us. The best issues in this repo started as somebody saying a thing felt wrong.
+
+## Where everything is
+
+| | |
+|---|---|
+| Try it | [three.ws](https://three.ws) |
+| Will my avatar animate? | [Rig Doctor](https://three.ws/rig-doctor), drop a `.glb` and find out |
+| First contribution, 15 minutes | [docs/first-contribution.md](https://github.com/nirholas/three.ws/blob/main/docs/first-contribution.md) |
+| Curated starter work | [`good first issue`](https://github.com/nirholas/three.ws/labels/good%20first%20issue) |
+| How we triage and how fast we answer | [docs/triage.md](https://github.com/nirholas/three.ws/blob/main/docs/triage.md) |
+| Every channel we are in | [docs/community.md](https://github.com/nirholas/three.ws/blob/main/docs/community.md) |
+| Real-time chat | [Telegram](https://t.me/three_ws_community) |
+| Demos and avatars people built | [X community](https://x.com/i/communities/1923523161230078106) |
+| Enterprise and integration talk | [IBM Community group](https://community.ibm.com/community/user/usergroup?CommunityKey=e71510cc-d953-408f-9a1c-019f5c0a7016) |
+| Every user-visible change | [changelog](https://three.ws/changelog) and [t.me/three_ws](https://t.me/three_ws) |
+
+## Two house rules
+
+The [Code of Conduct](https://github.com/nirholas/three.ws/blob/main/CODE_OF_CONDUCT.md) applies in every room, not just this one. Beyond it:
+
+- **No trading talk in the technical channels.** There are on-chain surfaces in this project. Price chat still does not belong anywhere near a bug thread.
+- **Share the file.** Rendering and rigging bugs are nearly impossible to guess at and trivial to diagnose from the actual GLB.
+
+Welcome aboard.
+```
+
+---
+
+## 2. Show and tell (Show and tell)
+
+**Title:** `Show and tell: what have you built with three.ws?`
+
+```markdown
+Show us what you built with three.ws. Avatars, embeds, agents, weird experiments, half-finished things you are not sure about. All of it.
+
+**A good post has:**
+
+- A screenshot or a screen recording. This is a 3D project. Pixels or it did not happen.
+- One line on what it is
+- A link, if it is live somewhere
+
+**We will:**
+
+- Repost the good ones from [@trythreews](https://x.com/trythreews) and in the [X community](https://x.com/i/communities/1923523161230078106), with credit
+- Turn anything that broke on the way into a real issue
+
+**Things worth showing even if they feel small:** an avatar embedded in a site you already run, a rig that came from an unusual tool, a mood or animation sequence driven from your own page code, an agent doing something we did not design for.
+
+That last category is the most interesting one. If you found a use we did not anticipate, that is a product direction, not a curiosity.
+
+Broke something instead of building something? That is also worth posting. Open an [issue](https://github.com/nirholas/three.ws/issues/new/choose) and link it here.
+```
+
+---
+
+## 3. Roadmap (Ideas)
+
+**Title:** `Roadmap: what should we build next, and what is in your way?`
+
+```markdown
+What should we build next, and what is currently in your way?
+
+This thread is deliberately open. We ship fast and publish every user-visible change to the [changelog](https://three.ws/changelog), which means the roadmap is genuinely steerable by whoever shows up with a good argument.
+
+## The best kind of reply
+
+Not "add feature X", but:
+
+> I was trying to do **[thing]**. I got as far as **[point]**. Then **[what stopped me]**.
+
+That format tells us the shape of the gap instead of one guess at its solution, and it is how most of the good decisions in this project got made.
+
+## Where we think the sharp edges are
+
+Tell us if we are wrong about any of these. Being wrong here is expensive, so an argument against one of them is more valuable than agreement.
+
+- **Rig coverage.** Every humanoid GLB in the wild names bones differently, and we map them to one canonical skeleton so the shared clip library retargets onto anything. Rigs we do not recognise fall back to a default body. If yours does that, [Rig Doctor](https://three.ws/rig-doctor) will tell you exactly which joints we missed, and that list is a contribution: see [#115](https://github.com/nirholas/three.ws/issues/115).
+- **The embed story.** One `<agent-3d>` tag is meant to be all it takes. If integrating into your framework needed more than that, say what.
+- **The agent runtime.** Memory, moods, tools, brains. What is missing for the agent you actually want to build?
+- **Docs.** If you had to read source to answer something, that is a docs bug and we want the specific question.
+
+## What happens to replies here
+
+Anything concrete becomes an issue, linked back to this thread. Anything shipped shows up in the changelog and gets a reply here saying so. Nothing gets quietly dropped.
+```
+
+---
+
+<a id="sec-163"></a>
> **Source:** `docs/cookbook/asset-quality-gate.md` · [↑ table of contents](#table-of-contents)
@@ -42352,7 +42533,7 @@ build on any of them. They are a good backlog for whatever ships the assets.
---
-<a id="sec-162"></a>
+<a id="sec-164"></a>
> **Source:** `docs/cookbook/mcp-3d-tool.md` · [↑ table of contents](#table-of-contents)
@@ -42491,7 +42672,7 @@ endpoints.
---
-<a id="sec-163"></a>
+<a id="sec-165"></a>
> **Source:** `docs/cookbook/parallel-asset-pack.md` · [↑ table of contents](#table-of-contents)
@@ -42660,7 +42841,7 @@ machine. Useful for picking a triangle budget before you commit to one.
---
-<a id="sec-164"></a>
+<a id="sec-166"></a>
> **Source:** `docs/cookbook/text-to-3d-cli.md` · [↑ table of contents](#table-of-contents)
@@ -42809,7 +42990,7 @@ the lane is queued, which is exactly when `retryAfter` starts mattering.
---
-<a id="sec-165"></a>
+<a id="sec-167"></a>
> **Source:** `docs/copy-trading.md` · [↑ table of contents](#table-of-contents)
@@ -42824,9 +43005,9 @@ Copy trading on three.ws lets one wallet follow another wallet's real trades. Th
Both are Solana-native. Both run on `mainnet` and `devnet`. Neither is a paper-trading mode: neither engine has a simulation layer or a synthetic fill anywhere in it. Read [Simulated versus executed](#simulated-versus-executed) before you enable anything.
-If you want to feel a leader's edge before committing money, that is a *separate* surface: [Ghost-copy](#sec-233) replays a leader's real closed trades against a wallet that does not exist. It never touches either engine below and never produces an intent.
+If you want to feel a leader's edge before committing money, that is a *separate* surface: [Ghost-copy](#sec-236) replays a leader's real closed trades against a wallet that does not exist. It never touches either engine below and never produces an intent.
-Related reading: [Smart Money Radar](#sec-389) for the first-party wallet reputation graph, [the trading surfaces](#sec-415) for the screeners and the trading cockpit these leaders trade from, [agent wallets](#sec-072) for the custody and spend-policy model, and [signal marketplace](#sec-382) for the paid-feed variant that reuses the same guarded executor.
+Related reading: [Smart Money Radar](#sec-394) for the first-party wallet reputation graph, [the trading surfaces](#sec-420) for the screeners and the trading cockpit these leaders trade from, [agent wallets](#sec-072) for the custody and spend-policy model, and [signal marketplace](#sec-387) for the paid-feed variant that reuses the same guarded executor.
---
@@ -42836,7 +43017,7 @@ State this to yourself before you touch a control:
- **The agent mirror executes with real funds.** When a leader agent's trade confirms on-chain, `api/_lib/agent-mirror.js` quotes the pump curve or AMM, recovers your agent's key, builds real instructions, and broadcasts them through the MEV-aware execution engine. The resulting signature is a real Solana transaction. There is no dry-run flag, no shadow mode, and no "test" sizing.
- **Copier subscriptions never execute.** `api/cron/copy-fanout.js` writes a row into `copy_executions` with a planned size and a reason. That is the whole action. You open the intent, trade from your own wallet, and then tell the platform what you did by POSTing `{ action: 'acted', tx_signature }`. Marking an intent `acted` records history. It moves no funds, and the platform never holds your keys on this path.
-- **Ghost-copy is explicitly paper, and lives outside both engines.** [/ghost-copy](https://three.ws/ghost-copy) replays a leader's already-closed on-chain round-trips against a hypothetical budget. It shares the sizing function (`planCopyOrder`) with the copier path so the numbers are comparable, but it writes nothing, signs nothing, produces no intent, and cannot be enabled. Every response is labelled `paper: true` and carries an `honesty` block. See [ghost-copy](#sec-233).
+- **Ghost-copy is explicitly paper, and lives outside both engines.** [/ghost-copy](https://three.ws/ghost-copy) replays a leader's already-closed on-chain round-trips against a hypothetical budget. It shares the sizing function (`planCopyOrder`) with the copier path so the numbers are comparable, but it writes nothing, signs nothing, produces no intent, and cannot be enabled. Every response is labelled `paper: true` and carries an `honesty` block. See [ghost-copy](#sec-236).
- **The leaderboard and track records are computed from real fills only.** `api/_lib/mirror-stats.js` and `api/mirror/leaderboard.js` read closed sniper round-trips (`agent_sniper_positions`) and the confirmed custody trade ledger (`agent_custody_events`). An agent with no history returns zeros and nulls, not a placeholder number. Losing agents appear with their losses.
- **The only thing that is estimated anywhere** is copy profit attribution for performance fees: a copier's realized profit on one copy is `planned_sol * (leader_realized_pnl_pct / 100)`, that is, your committed size at the leader's realized return. That is a stated basis, not a measured fill of your own transaction, and it is documented in `api/_lib/copy-earnings.js`.
@@ -43211,7 +43392,7 @@ Response:
The directory is a static, deduplicated snapshot shipped with the API (`api/_lib/copy/smart-wallets.json`) and regenerated by `scripts/build-smart-wallets.mjs`. Wallet identity and 30-day performance only, never token holdings. If the snapshot file is missing the endpoint returns an empty list rather than failing.
-For first-party wallet reputation earned from three.ws's own outcome ledger rather than an external taxonomy, use [Smart Money Radar](#sec-389).
+For first-party wallet reputation earned from three.ws's own outcome ledger rather than an external taxonomy, use [Smart Money Radar](#sec-394).
---
@@ -43245,7 +43426,7 @@ Both engines are reachable without a browser:
- `packages/strategies` wraps `POST /api/copy/subscriptions` and `/api/copy/executions` for programmatic strategy clients. See [its README](../packages/strategies/README.md).
- Bearer tokens work on every authenticated route above and are not CSRF-gated, which is what makes an autonomous agent a first-class copier here.
-See [the MCP reference](#sec-277) for wiring these into a client.
+See [the MCP reference](#sec-281) for wiring these into a client.
---
@@ -43260,7 +43441,7 @@ See [the MCP reference](#sec-277) for wiring these into a client.
---
-<a id="sec-166"></a>
+<a id="sec-168"></a>
> **Source:** `docs/cosmos.md` · [↑ table of contents](#table-of-contents)
@@ -43351,13 +43532,13 @@ else {
## Related
-- [Forge](#sec-225) makes the 3D avatars and objects you place in a Cosmos world.
+- [Forge](#sec-228) makes the 3D avatars and objects you place in a Cosmos world.
- [Avatar creation](#sec-109) and [the trait-based avatar builder](#sec-137) for building and dressing avatars.
- Pages: [/create](https://three.ws/create), [/gallery](https://three.ws/gallery), [/scene](https://three.ws/scene).
---
-<a id="sec-167"></a>
+<a id="sec-169"></a>
> **Source:** `docs/creator-portfolio.md` · [↑ table of contents](#table-of-contents)
@@ -43505,7 +43686,7 @@ Two card-level actions let a visitor take a copy of what they find:
handler [api/avatars/fork.js](../api/avatars/fork.js)): clones the GLB,
its agent, and a fresh wallet into the viewer's account. Downstream, forks
of a paid avatar are what produce the `royalty_paid` notifications
- documented in [Notifications](#sec-293).
+ documented in [Notifications](#sec-297).
- **Fork an agent** (`POST /api/marketplace/agents/:id/fork`, handler
[api/marketplace/[action].js](../api/marketplace/[action].js)): clones
a *published* agent into the viewer's account; unpublished agents render
@@ -43544,19 +43725,19 @@ unfurls with the creator's actual name and stats.
## Related pages
-- [The social layer](#sec-391): the follow graph, feed, and
+- [The social layer](#sec-396): the follow graph, feed, and
rankings this page plugs into.
-- [Notifications](#sec-293): the follow, remix, sale, and royalty
+- [Notifications](#sec-297): the follow, remix, sale, and royalty
events a portfolio generates for its owner.
-- [Remix economy](#sec-365): what happens when someone remixes a creation
+- [Remix economy](#sec-370): what happens when someone remixes a creation
they found here.
-- [Forge](#sec-225), [Widgets](#sec-511),
- [Marketplace](#sec-270): the creation surfaces whose output the
+- [Forge](#sec-228), [Widgets](#sec-517),
+ [Marketplace](#sec-274): the creation surfaces whose output the
portfolio aggregates.
---
-<a id="sec-168"></a>
+<a id="sec-170"></a>
> **Source:** `docs/crews.md` · [↑ table of contents](#table-of-contents)
@@ -43738,7 +43919,7 @@ player who is already social in the world finds the group surface.
---
-<a id="sec-169"></a>
+<a id="sec-171"></a>
> **Source:** `docs/crypto-api.md` · [↑ table of contents](#table-of-contents)
@@ -44785,7 +44966,7 @@ curl -s "https://three.ws/api/crypto/airdrops?address=<wallet>" \
---
-<a id="sec-170"></a>
+<a id="sec-172"></a>
> **Source:** `docs/custody.md` · [↑ table of contents](#table-of-contents)
@@ -44811,7 +44992,7 @@ Limits live per agent and are owner-configurable from the wallet hub (API: `GET/
Enforcement is uniform: the same policy module gates **every** outbound path — withdrawals, x402 payments, sniper buys, trades. A transaction that would breach a cap is refused with a structured `403` before signing; no funds move. Limits are opt-in (`null` means uncapped) — but they're hard once set. SPL tokens that can't be priced in USD are governed by the allowlist instead, so a price-feed outage can never strand your own withdrawal.
-You can also write these rules in plain English — see [financial-controls](#sec-221) for the natural-language rules layer and the real-time defense behaviors built on top of this same enforcement point.
+You can also write these rules in plain English — see [financial-controls](#sec-223) for the natural-language rules layer and the real-time defense behaviors built on top of this same enforcement point.
## Freeze: the kill switch that can't trap you
@@ -44870,14 +45051,14 @@ Every step of recovery and inheritance writes to the custody trail and the audit
## Related
-- [Financial controls](#sec-221) — plain-English spend rules and real-time wallet defense on these rails
-- [Trading surfaces](#sec-415) — Mission Control executes through this same guarded path
-- [The trading experiment](#sec-413) — an autonomous agent operating inside these limits, journaled
-- [x402](#sec-544) — the payment protocol these wallets spend over
+- [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
---
-<a id="sec-171"></a>
+<a id="sec-173"></a>
> **Source:** `docs/daily-forge.md` · [↑ table of contents](#table-of-contents)
@@ -44976,14 +45157,14 @@ console.log(themeIndex(new Date().toISOString().slice(0, 10), 24));
## Related
- [The 3D pipeline](#sec-003) and [3D API](#sec-001): the text-to-3D forge the free lane rides
-- [Forge background generation](#sec-222): the job and polling model
+- [Forge background generation](#sec-225): the job and polling model
- [AR and WebXR](#sec-099): the Scene Viewer and Quick Look handoff
-- [Quick start](#sec-361): the general free-forge onboarding
+- [Quick start](#sec-366): the general free-forge onboarding
- Pages: [/daily](https://three.ws/daily) · [/forge](https://three.ws/forge) · [/ar/studio](https://three.ws/ar/studio)
---
-<a id="sec-172"></a>
+<a id="sec-174"></a>
> **Source:** `docs/daily-match.md` · [↑ table of contents](#table-of-contents)
@@ -45116,11 +45297,11 @@ falls back to `type`.
Related docs: [agent-sniper.md](#sec-061) (where the trade and P&L
columns come from), [agent-skills.md](#sec-060) (skill sales),
-[pump-launcher.md](#sec-339) (launches).
+[pump-launcher.md](#sec-344) (launches).
---
-<a id="sec-173"></a>
+<a id="sec-175"></a>
> **Source:** `docs/demo-routes.md` · [↑ table of contents](#table-of-contents)
@@ -45347,7 +45528,7 @@ the 200s above still come from the 2026-08-05 curl sweep.
---
-<a id="sec-174"></a>
+<a id="sec-176"></a>
> **Source:** `docs/deployment.md` · [↑ table of contents](#table-of-contents)
@@ -45718,7 +45899,7 @@ The `crons` array in `vercel.json` declares every scheduled job (economy tick, o
| `/api/cron/run-dca` | Every hour | Execute scheduled DCA strategies |
| `/api/cron/run-subscriptions` | Every hour | Process recurring subscriptions |
-The container does **not** schedule these itself — you need an external scheduler hitting the endpoints. On Cloud Run that is Cloud Scheduler; self-hosters can point any HTTP cron (Cloud Scheduler, cron-job.org, Upstash QStash) at `/api/cron/*` with the `CRON_SECRET` bearer, or run `scripts/economy-heartbeat.mjs` as a long-lived pinger that reads `vercel.json` and fires every due cron each minute. See the [economy heartbeat](#sec-181) guide for the driver patterns.
+The container does **not** schedule these itself — you need an external scheduler hitting the endpoints. On Cloud Run that is Cloud Scheduler; self-hosters can point any HTTP cron (Cloud Scheduler, cron-job.org, Upstash QStash) at `/api/cron/*` with the `CRON_SECRET` bearer, or run `scripts/economy-heartbeat.mjs` as a long-lived pinger that reads `vercel.json` and fires every due cron each minute. See the [economy heartbeat](#sec-183) guide for the driver patterns.
### Static asset caching
@@ -45783,7 +45964,7 @@ does not use them: it reads and writes the ERC-8004 reference
`ValidationRegistryUpgradeable`, which has no validator allow-list. A validator is
authorized per agent by the agent's owner opening a request that names it (or by
the owner approving it as an operator). See
-[erc8004/validation-attestation.md](#sec-189), and verify
+[erc8004/validation-attestation.md](#sec-191), and verify
any configured registry address with `npm run verify:erc8004-validation`.
---
@@ -45845,7 +46026,7 @@ docker run -p 8080:8080 \
- **Logs:** on Cloud Run, `gcloud run services logs read three-ws-api --region us-central1` or Cloud Logging; on any other host, that platform's log stream.
- **Request duration / timeout:** the Cloud Run service runs with a 900s request timeout; set the equivalent on your host so long renders (avatar thumbnails, 3D generation) don't get cut off.
-- **Uptime:** the `uptime-check` cron ([api/cron/uptime-check.js](../api/cron/uptime-check.js)) watches the economy and subsystems and escalates to the ops Telegram channel — see the [economy heartbeat](#sec-181) guide.
+- **Uptime:** the `uptime-check` cron ([api/cron/uptime-check.js](../api/cron/uptime-check.js)) watches the economy and subsystems and escalates to the ops Telegram channel — see the [economy heartbeat](#sec-183) guide.
### Database monitoring
@@ -45940,7 +46121,7 @@ Upstash REST API uses HTTPS — no ports to open. If you see connection errors,
---
-<a id="sec-175"></a>
+<a id="sec-177"></a>
> **Source:** `docs/deployments.md` · [↑ table of contents](#table-of-contents)
@@ -45952,7 +46133,7 @@ It answers three questions at a glance: how big is the on-chain agent population
Every row is a real on-chain registration. There are no synthetic entries and no seeded demo rows. When a network is quiet the feed is honestly empty, and when a signal was never measured the UI says so rather than rendering a zero.
-Related reading: [ERC-8004 blockchain identity](#sec-188) for the standard, the registry contracts, and how to register; [deploying agents on-chain](#sec-304) for the Solana Metaplex Core path; [agent reputation on Solana](#sec-393) for the trust layer built on top of a Solana identity.
+Related reading: [ERC-8004 blockchain identity](#sec-190) for the standard, the registry contracts, and how to register; [deploying agents on-chain](#sec-308) for the Solana Metaplex Core path; [agent reputation on Solana](#sec-398) for the trust layer built on top of a Solana identity.
---
@@ -45967,7 +46148,7 @@ This surface is **not EVM-only**. Solana is folded into the same feed as a first
Two Solana upstreams feed it: three.ws's own Metaplex Core mints, and the external Metaplex Agent Registry. Details in [where the data comes from](#where-the-data-comes-from).
-What lives elsewhere: the *creation* path for a Solana identity is documented in [deploying agents on-chain](#sec-304) (the single-agent, user-signed flow is in [Solana agents](#sec-394)), and Solana reputation and attestations are in [agent reputation on Solana](#sec-393). This page is only the index and the feed.
+What lives elsewhere: the *creation* path for a Solana identity is documented in [deploying agents on-chain](#sec-308) (the single-agent, user-signed flow is in [Solana agents](#sec-399)), and Solana reputation and attestations are in [agent reputation on Solana](#sec-398). This page is only the index and the feed.
---
@@ -46027,7 +46208,7 @@ A second stage, **metadata enrichment**, takes up to 25 rows per run whose metad
Metadata is attacker-controlled: it is whatever the agent's owner published on-chain. Two consequences are load-bearing. Enrichment refuses to let `meta.active` alone decide visibility, and a name or description containing a slur sets `active = false` so the row is withheld from every public feed (this page included). A failed fetch records `metadata_error` and moves on rather than retrying in a loop.
-The Identity Registry is deployed deterministically via CREATE2, so it has one address per network class, the same on every chain. See [ERC-8004](#sec-188) for the addresses and the contract surface.
+The Identity Registry is deployed deterministically via CREATE2, so it has one address per network class, the same on every chain. See [ERC-8004](#sec-190) for the addresses and the contract surface.
### 2. Solana: three.ws's own Metaplex Core mints
@@ -46177,7 +46358,7 @@ The network toggle derives its chain-id sets from that table at import time, so
---
-<a id="sec-176"></a>
+<a id="sec-178"></a>
> **Source:** `docs/developer-platform.md` · [↑ table of contents](#table-of-contents)
@@ -46197,8 +46378,8 @@ The browser UI for all of this lives in the dashboard:
Base URL: `https://three.ws`
-Related docs: [MCP integration](#sec-277), [API reference](#sec-096),
-[Authentication](#sec-103), [x402 developer tools](#sec-537).
+Related docs: [MCP integration](#sec-281), [API reference](#sec-096),
+[Authentication](#sec-103), [x402 developer tools](#sec-544).
---
@@ -46238,7 +46419,7 @@ key, no CSRF.
## API keys
API keys are bearer credentials for machine clients: the MCP server at
-`/api/mcp` (see [MCP integration](#sec-277)) and the account-scoped REST
+`/api/mcp` (see [MCP integration](#sec-281)) and the account-scoped REST
endpoints that accept `Authorization: Bearer` (see the
[API reference](#sec-096)). Each key carries a set of scopes:
@@ -46652,7 +46833,7 @@ Errors: `400 bad_request` (`keyId` missing or not a string),
`404 not_found` (key does not exist, is not yours, or is not a well-formed
UUID), `400 revoked`, `400 expired`, `401`, `403` (CSRF), `429`.
-See [MCP integration](#sec-277) for configuring a real client against
+See [MCP integration](#sec-281) for configuring a real client against
`/api/mcp`.
---
@@ -46731,7 +46912,7 @@ omitted from the manifest.
---
-<a id="sec-177"></a>
+<a id="sec-179"></a>
> **Source:** `docs/diorama.md` · [↑ table of contents](#table-of-contents)
@@ -46833,13 +47014,13 @@ until the world is saved:
## Related
-- [Forge](#sec-225) is the single-object generator every diorama object is forged on.
-- [Image to 3D](#sec-251) for photo-based objects; [AR](#sec-099) for viewing worlds in augmented reality.
+- [Forge](#sec-228) is the single-object generator every diorama object is forged on.
+- [Image to 3D](#sec-254) for photo-based objects; [AR](#sec-099) for viewing worlds in augmented reality.
- Pages: [/scene](https://three.ws/scene) (Scene Studio, where an exported diorama opens), [/gallery](https://three.ws/gallery), [/create](https://three.ws/create).
---
-<a id="sec-178"></a>
+<a id="sec-180"></a>
> **Source:** `docs/do-i-need-crypto.md` · [↑ table of contents](#table-of-contents)
@@ -46919,14 +47100,14 @@ When you do interact with on-chain features, the platform's native token is **$T
## What's next
-- **Create your first agent** → [Make your first agent](#sec-268)
-- **Put it on your site** → [Share & embed](#sec-378)
-- **Optional: register on-chain** → [Register on-chain](#sec-462)
+- **Create your first agent** → [Make your first agent](#sec-272)
+- **Put it on your site** → [Share & embed](#sec-383)
+- **Optional: register on-chain** → [Register on-chain](#sec-468)
- **Technical auth details** → [Authentication](#sec-103)
---
-<a id="sec-179"></a>
+<a id="sec-181"></a>
> **Source:** `docs/docs-world.md` · [↑ table of contents](#table-of-contents)
@@ -47013,7 +47194,7 @@ Adding a section is the same edit: append to `sections` and a new pavilion appea
---
-<a id="sec-180"></a>
+<a id="sec-182"></a>
> **Source:** `docs/draft-agent-mint.md` · [↑ table of contents](#table-of-contents)
@@ -47238,14 +47419,14 @@ explorer link, so the evidence file never overstates what was proven.
## Related
-- [Selfie to Avatar](#sec-377): the pipeline whose tail calls this
+- [Selfie to Avatar](#sec-382): the pipeline whose tail calls this
- [Agent identities](#sec-053): what an agent identity is and how it is generated
- [Agent tokens](#sec-070): what happens after a draft identity goes live
- [The agent index](#sec-054): the cross-chain index that surfaces these registrations
---
-<a id="sec-181"></a>
+<a id="sec-183"></a>
> **Source:** `docs/economy-heartbeat.md` · [↑ table of contents](#table-of-contents)
@@ -47401,12 +47582,12 @@ 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-541) ·
-[economy funding root](#sec-182) · [money map](#sec-287)
+[x402 ring economy](#sec-548) ·
+[economy funding root](#sec-184) · [money map](#sec-291)
---
-<a id="sec-182"></a>
+<a id="sec-184"></a>
> **Source:** `docs/economy-master.md` · [↑ table of contents](#table-of-contents)
@@ -47873,7 +48054,7 @@ The JSON response reports `configured`, `master_sol`, `funded`, `failed`,
off-registry target reached the sweep and was blocked — investigate the caller.
If the Cloud Scheduler job never fires, the
-[economy heartbeat](#sec-181) dispatcher (and any external HTTP cron
+[economy heartbeat](#sec-183) dispatcher (and any external HTTP cron
pointed at `/api/cron/economy-tick`) keeps it — and every other cron — ticking.
## Audit, accounting & breach monitoring
@@ -47988,7 +48169,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-541) /
+ other engine (see [x402 ring economy](#sec-548) /
[autonomous x402](#sec-105)).
## Related
@@ -47997,17 +48178,17 @@ 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-541) — closed-loop in-house x402 settlement.
+- [x402 ring economy](#sec-548) — closed-loop in-house x402 settlement.
---
-<a id="sec-183"></a>
+<a id="sec-185"></a>
> **Source:** `docs/economy-solver.md` · [↑ table of contents](#table-of-contents)
# The economy solver
-The [in-game economy reference](#sec-252) publishes **what** the `/play`
+The [in-game economy reference](#sec-255) publishes **what** the `/play`
world charges. The solver publishes **what those numbers mean**: the exact expected
cash, XP and goods per hour of every action in the world, at every skill level.
@@ -48233,16 +48414,16 @@ deploy.
## Next
-- **[The in-game economy](#sec-252)** is the raw reference: every catalog,
+- **[The in-game economy](#sec-255)** is the raw reference: every catalog,
gate, settlement path and the JSON wire format.
-- **[Earn and spend in /play](#sec-435)** walks the loop
+- **[Earn and spend in /play](#sec-441)** walks the loop
by hand, in the world.
- **[three.ws/play/solver](https://three.ws/play/solver)** is the interactive version
of everything above.
---
-<a id="sec-184"></a>
+<a id="sec-186"></a>
> **Source:** `docs/editor.md` · [↑ table of contents](#table-of-contents)
@@ -48591,7 +48772,7 @@ The full contract lives in [specs/EDITOR_SPEC.md](https://github.com/nirholas/th
---
-<a id="sec-185"></a>
+<a id="sec-187"></a>
> **Source:** `docs/education-pilot-bucharest.md` · [↑ table of contents](#table-of-contents)
@@ -48662,7 +48843,7 @@ Status: exploratory. A contact has offered a local connection to the office of t
---
-<a id="sec-186"></a>
+<a id="sec-188"></a>
> **Source:** `docs/embedding.md` · [↑ table of contents](#table-of-contents)
@@ -49401,14 +49582,14 @@ The platform records anonymous embed impressions (country, referrer hostname) vi
- [Architecture Overview](#sec-100)
- [Agent System Overview](#sec-064)
-- [Web Component reference](#sec-508) — full attribute list
-- [Widgets](#sec-511) — Widget Studio and widget types
+- [Web Component reference](#sec-514) — full attribute list
+- [Widgets](#sec-517) — Widget Studio and widget types
- [specs/EMBED_SPEC.md](../specs/EMBED_SPEC.md) — authoritative web component spec
- [specs/EMBED_HOST_PROTOCOL.md](../specs/EMBED_HOST_PROTOCOL.md) — versioned postMessage protocol
---
-<a id="sec-187"></a>
+<a id="sec-189"></a>
> **Source:** `docs/embody.md` · [↑ table of contents](#table-of-contents)
@@ -49511,14 +49692,14 @@ Embody is a thin, honest wire over pieces that already exist — no new pipeline
## Related
-- [Live embodiment](#sec-274) — the 3D Studio tools that persist and drive a body in chat.
-- [x402 Paid Endpoints](#sec-539) — the full paid catalog and pricing.
-- [x402 Buyer Client](#sec-536) — how to settle a 402 challenge from code.
+- [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.
- [Avatar creation](#sec-109) — generate a rigged avatar in the web UI.
---
-<a id="sec-188"></a>
+<a id="sec-190"></a>
> **Source:** `docs/erc8004.md` · [↑ table of contents](#table-of-contents)
@@ -50227,7 +50408,7 @@ The same MAINNET addresses apply to all 15 mainnets. The same TESTNET addresses
---
-<a id="sec-189"></a>
+<a id="sec-191"></a>
> **Source:** `docs/erc8004/validation-attestation.md` · [↑ table of contents](#table-of-contents)
@@ -50380,7 +50561,7 @@ reported the reverts as "no attestation yet".
---
-<a id="sec-190"></a>
+<a id="sec-192"></a>
> **Source:** `docs/event-readiness/01-play-first-impression.md` · [↑ table of contents](#table-of-contents)
@@ -50424,7 +50605,7 @@ What you changed (files + one line each), what you verified in-browser, anything
---
-<a id="sec-191"></a>
+<a id="sec-193"></a>
> **Source:** `docs/event-readiness/02-play-mobile.md` · [↑ table of contents](#table-of-contents)
@@ -50460,7 +50641,7 @@ Root cause of any crash found (with the harness evidence), fixes applied, remain
---
-<a id="sec-192"></a>
+<a id="sec-194"></a>
> **Source:** `docs/event-readiness/03-play-performance.md` · [↑ table of contents](#table-of-contents)
@@ -50502,7 +50683,7 @@ Numbers table (before/after), each fix in one line, anything intentionally skipp
---
-<a id="sec-193"></a>
+<a id="sec-195"></a>
> **Source:** `docs/event-readiness/04-play-multiplayer-net.md` · [↑ table of contents](#table-of-contents)
@@ -50542,7 +50723,7 @@ Each failure mode tested and its result (pass / fixed / cannot-fix-with-reason).
---
-<a id="sec-194"></a>
+<a id="sec-196"></a>
> **Source:** `docs/event-readiness/05-play-economy-loops.md` · [↑ table of contents](#table-of-contents)
@@ -50583,7 +50764,7 @@ Loop-by-loop pass/fixed table, every price mismatch found and which side you cor
---
-<a id="sec-195"></a>
+<a id="sec-197"></a>
> **Source:** `docs/event-readiness/06-play-auth-errors.md` · [↑ table of contents](#table-of-contents)
@@ -50619,7 +50800,7 @@ A failure-mode table: scenario, what happened before, what happens now. Call out
---
-<a id="sec-196"></a>
+<a id="sec-198"></a>
> **Source:** `docs/event-readiness/07-platform-smoke-sweep.md` · [↑ table of contents](#table-of-contents)
@@ -50670,7 +50851,7 @@ Battery results before and after, fixes grouped by page, the manual event-funnel
---
-<a id="sec-197"></a>
+<a id="sec-199"></a>
> **Source:** `docs/event-readiness/08-api-production-health.md` · [↑ table of contents](#table-of-contents)
@@ -50701,7 +50882,7 @@ Solana-first status summary, then the 8 items with their binary states, then log
---
-<a id="sec-198"></a>
+<a id="sec-200"></a>
> **Source:** `docs/event-readiness/09-accessibility-i18n.md` · [↑ table of contents](#table-of-contents)
@@ -50737,7 +50918,7 @@ Per-category pass/fixed list, the keyboard-only session result, locales verified
---
-<a id="sec-199"></a>
+<a id="sec-201"></a>
> **Source:** `docs/event-readiness/10-event-day-runbook.md` · [↑ table of contents](#table-of-contents)
@@ -50775,7 +50956,7 @@ Old/new scaling values, capacity smoke numbers, rollback rehearsal result, and t
---
-<a id="sec-200"></a>
+<a id="sec-202"></a>
> **Source:** `docs/event-readiness/11-event-live-ops.md` · [↑ table of contents](#table-of-contents)
@@ -50810,7 +50991,7 @@ What shipped (files + one line each), the exact operator commands for event day,
---
-<a id="sec-201"></a>
+<a id="sec-203"></a>
> **Source:** `docs/event-readiness/12-photo-mode-share.md` · [↑ table of contents](#table-of-contents)
@@ -50846,7 +51027,7 @@ Files shipped, a saved sample capture path, what the share flow does per platfor
---
-<a id="sec-202"></a>
+<a id="sec-204"></a>
> **Source:** `docs/event-readiness/13-event-quests-leaderboard.md` · [↑ table of contents](#table-of-contents)
@@ -50882,7 +51063,7 @@ The quest list as players will see it, files shipped, the leaderboard endpoint U
---
-<a id="sec-203"></a>
+<a id="sec-205"></a>
> **Source:** `docs/event-readiness/14-welcome-concierge.md` · [↑ table of contents](#table-of-contents)
@@ -50917,7 +51098,7 @@ Files shipped, the persona prompt location, the tour stops, what the concierge s
---
-<a id="sec-204"></a>
+<a id="sec-206"></a>
> **Source:** `docs/event-readiness/15-live-hype-feed.md` · [↑ table of contents](#table-of-contents)
@@ -50951,7 +51132,7 @@ Files shipped, the threshold logic in two sentences, measured DOM/node behavior
---
-<a id="sec-205"></a>
+<a id="sec-207"></a>
> **Source:** `docs/event-readiness/16-invite-flow.md` · [↑ table of contents](#table-of-contents)
@@ -50985,7 +51166,7 @@ Files shipped, any dependency added (name, weekly downloads, license, why), a re
---
-<a id="sec-206"></a>
+<a id="sec-208"></a>
> **Source:** `docs/event-readiness/17-plaza-live-show.md` · [↑ table of contents](#table-of-contents)
@@ -51022,7 +51203,7 @@ Files shipped, how `stageId` is derived, the join and teardown lifecycle in thre
---
-<a id="sec-207"></a>
+<a id="sec-209"></a>
> **Source:** `docs/event-readiness/18-coin-wars-portal.md` · [↑ table of contents](#table-of-contents)
@@ -51059,7 +51240,7 @@ Files shipped, the standings read path (existing or the one endpoint you added),
---
-<a id="sec-208"></a>
+<a id="sec-210"></a>
> **Source:** `docs/event-readiness/19-forge-props-live.md` · [↑ table of contents](#table-of-contents)
@@ -51096,7 +51277,7 @@ Files shipped, the size ceiling values and where they are enforced, the rate-lim
---
-<a id="sec-209"></a>
+<a id="sec-211"></a>
> **Source:** `docs/event-readiness/20-world-chat-scrollback.md` · [↑ table of contents](#table-of-contents)
@@ -51133,7 +51314,7 @@ Files shipped, the cap and TTL chosen, the bridge decision and why, join-time pa
---
-<a id="sec-210"></a>
+<a id="sec-212"></a>
> **Source:** `docs/event-readiness/21-party-system.md` · [↑ table of contents](#table-of-contents)
@@ -51169,7 +51350,7 @@ Files shipped, where party state lives and its TTL, the teleport validation rule
---
-<a id="sec-211"></a>
+<a id="sec-213"></a>
> **Source:** `docs/event-readiness/22-venue-projector-mode.md` · [↑ table of contents](#table-of-contents)
@@ -51205,7 +51386,7 @@ Files shipped, the exact URL to put on the venue machine, the spectator join con
---
-<a id="sec-212"></a>
+<a id="sec-214"></a>
> **Source:** `docs/event-readiness/23-signature-wall.md` · [↑ table of contents](#table-of-contents)
@@ -51242,7 +51423,7 @@ Files shipped, the store chosen and why, the overflow design in two sentences, t
---
-<a id="sec-213"></a>
+<a id="sec-215"></a>
> **Source:** `docs/event-readiness/24-dance-off.md` · [↑ table of contents](#table-of-contents)
@@ -51278,7 +51459,7 @@ Files shipped, the round timings chosen, the vote targeting rule, the reward and
---
-<a id="sec-214"></a>
+<a id="sec-216"></a>
> **Source:** `docs/event-readiness/LIVE-OPS.md` · [↑ table of contents](#table-of-contents)
@@ -51291,7 +51472,7 @@ Prepared 2026-08-08. Project `aerial-vehicle-466722-p5`, region `us-central1`.
## The link and the release
-**Event URL** (the canonical $THREE world, from [README.md](#sec-215)):
+**Event URL** (the canonical $THREE world, from [README.md](#sec-217)):
```
https://three.ws/play?coin=FeMbDoX7R1Psc4GEcvJdsbNbZA3bfztcyDCatJVJpump&name=three.ws&symbol=three&image=%2Fapi%2Fimg%3Furl%3Dhttps%253A%252F%252Fipfs.io%252Fipfs%252Fbafybeihe22b5sxr3ihnxt7pregfieyteqvubqhik3j3y4bbx243xlqjw3q%26seed%3DFeMbDoX7R1Psc4GEcvJdsbNbZA3bfztcyDCatJVJpump
@@ -51578,7 +51759,7 @@ page.
---
-<a id="sec-215"></a>
+<a id="sec-217"></a>
> **Source:** `docs/event-readiness/README.md` · [↑ table of contents](#table-of-contents)
@@ -51590,40 +51771,40 @@ Suggested order and parallelism (audits):
| # | Prompt | Surface | Can run in parallel with |
|---|--------|---------|--------------------------|
-| 1 | [01-play-first-impression.md](#sec-190) | /play load, intro, onboarding UX | 4, 5, 7, 8 |
-| 2 | [02-play-mobile.md](#sec-191) | /play on phones (stability + touch) | 7, 8 |
-| 3 | [03-play-performance.md](#sec-192) | /play load weight, FPS, memory | 7, 8 |
-| 4 | [04-play-multiplayer-net.md](#sec-193) | WebSocket, reconnects, voice, crowd | 1, 5 |
-| 5 | [05-play-economy-loops.md](#sec-194) | Store, bank, wheel, combat, quests, cosmetics | 1, 4 |
-| 6 | [06-play-auth-errors.md](#sec-195) | Sign-in, gates, error/empty states, console | after 1 |
-| 7 | [07-platform-smoke-sweep.md](#sec-196) | Every page on the live site | 1, 2, 3 |
-| 8 | [08-api-production-health.md](#sec-197) | Cloud Run, crons, logs, DB, x402 | 1, 2, 3 |
-| 9 | [09-accessibility-i18n.md](#sec-198) | Keyboard, ARIA, contrast, translations | after 1 |
-| 10 | [10-event-day-runbook.md](#sec-199) | Pre-scale, monitoring loop, rollback | last, after all fixes deploy |
+| 1 | [01-play-first-impression.md](#sec-192) | /play load, intro, onboarding UX | 4, 5, 7, 8 |
+| 2 | [02-play-mobile.md](#sec-193) | /play on phones (stability + touch) | 7, 8 |
+| 3 | [03-play-performance.md](#sec-194) | /play load weight, FPS, memory | 7, 8 |
+| 4 | [04-play-multiplayer-net.md](#sec-195) | WebSocket, reconnects, voice, crowd | 1, 5 |
+| 5 | [05-play-economy-loops.md](#sec-196) | Store, bank, wheel, combat, quests, cosmetics | 1, 4 |
+| 6 | [06-play-auth-errors.md](#sec-197) | Sign-in, gates, error/empty states, console | after 1 |
+| 7 | [07-platform-smoke-sweep.md](#sec-198) | Every page on the live site | 1, 2, 3 |
+| 8 | [08-api-production-health.md](#sec-199) | Cloud Run, crons, logs, DB, x402 | 1, 2, 3 |
+| 9 | [09-accessibility-i18n.md](#sec-200) | Keyboard, ARIA, contrast, translations | after 1 |
+| 10 | [10-event-day-runbook.md](#sec-201) | Pre-scale, monitoring loop, rollback | last, after all fixes deploy |
Feature builds (run after audits 1-3 land, or in parallel if staffed; 12, 14, and 16 interlink but each stands alone):
| # | Prompt | Builds | Depends on |
|---|--------|--------|------------|
-| 11 | [11-event-live-ops.md](#sec-200) | Operator broadcast, go-live moment, live event config | nothing |
-| 12 | [12-photo-mode-share.md](#sec-201) | Photo mode with branded one-tap share | nothing |
-| 13 | [13-event-quests-leaderboard.md](#sec-202) | Time-boxed quest line + live leaderboard + cosmetic reward | nothing (better with 12) |
-| 14 | [14-welcome-concierge.md](#sec-203) | Greeter NPC, guided tour, event-aware opening line | nothing |
-| 15 | [15-live-hype-feed.md](#sec-204) | Activity ticker + market hype moments | nothing (better with 13) |
-| 16 | [16-invite-flow.md](#sec-205) | Invite sheet, QR, OG card truth, arrival continuity | nothing (better with 14) |
+| 11 | [11-event-live-ops.md](#sec-202) | Operator broadcast, go-live moment, live event config | nothing |
+| 12 | [12-photo-mode-share.md](#sec-203) | Photo mode with branded one-tap share | nothing |
+| 13 | [13-event-quests-leaderboard.md](#sec-204) | Time-boxed quest line + live leaderboard + cosmetic reward | nothing (better with 12) |
+| 14 | [14-welcome-concierge.md](#sec-205) | Greeter NPC, guided tour, event-aware opening line | nothing |
+| 15 | [15-live-hype-feed.md](#sec-206) | Activity ticker + market hype moments | nothing (better with 13) |
+| 16 | [16-invite-flow.md](#sec-207) | Invite sheet, QR, OG card truth, arrival continuity | nothing (better with 14) |
Capability builds (17-24): each wires an existing, finished subsystem into the world or adds a missing social primitive. All stand alone; the noted pairings just make them better together.
| # | Prompt | Builds | Wires in / pairs with |
|---|--------|--------|-----------------------|
-| 17 | [17-plaza-live-show.md](#sec-206) | Live hosted show on a plaza stage, with $THREE tips | StageRoom + ShowDirector (built, unreachable from /play) |
-| 18 | [18-coin-wars-portal.md](#sec-207) | In-world Coin Wars portal: standings, queue, spectate | ClashRoom + war standings (built, arena-page only) |
-| 19 | [19-forge-props-live.md](#sec-208) | Text-to-3D prop generation inside build mode | Forge lane + the networked prop pipeline |
-| 20 | [20-world-chat-scrollback.md](#sec-209) | Chat scrollback for late joiners + community-feed bridge | the WalkRoom relay + api/community/messages |
-| 21 | [21-party-system.md](#sec-210) | Parties: form, see, reach, and talk to your crew | friends/presence stack; pairs with 13, 16 |
-| 22 | [22-venue-projector-mode.md](#sec-211) | Broadcast spectator view for the venue big screen | camera rig + event.json; pairs with 15, 16, 17 |
-| 23 | [23-signature-wall.md](#sec-212) | Persistent signature wall, the event's artifact | world-persist patterns + name safety |
-| 24 | [24-dance-off.md](#sec-213) | Judged dance-off rounds with crowd voting and tips | dance floor beat + King of the Totem round machine |
+| 17 | [17-plaza-live-show.md](#sec-208) | Live hosted show on a plaza stage, with $THREE tips | StageRoom + ShowDirector (built, unreachable from /play) |
+| 18 | [18-coin-wars-portal.md](#sec-209) | In-world Coin Wars portal: standings, queue, spectate | ClashRoom + war standings (built, arena-page only) |
+| 19 | [19-forge-props-live.md](#sec-210) | Text-to-3D prop generation inside build mode | Forge lane + the networked prop pipeline |
+| 20 | [20-world-chat-scrollback.md](#sec-211) | Chat scrollback for late joiners + community-feed bridge | the WalkRoom relay + api/community/messages |
+| 21 | [21-party-system.md](#sec-212) | Parties: form, see, reach, and talk to your crew | friends/presence stack; pairs with 13, 16 |
+| 22 | [22-venue-projector-mode.md](#sec-213) | Broadcast spectator view for the venue big screen | camera rig + event.json; pairs with 15, 16, 17 |
+| 23 | [23-signature-wall.md](#sec-214) | Persistent signature wall, the event's artifact | world-persist patterns + name safety |
+| 24 | [24-dance-off.md](#sec-215) | Judged dance-off rounds with crowd voting and tips | dance floor beat + King of the Totem round machine |
Rules that apply to every prompt in this pack:
@@ -51635,7 +51816,7 @@ Rules that apply to every prompt in this pack:
---
-<a id="sec-216"></a>
+<a id="sec-218"></a>
> **Source:** `docs/event-souvenirs.md` · [↑ table of contents](#table-of-contents)
@@ -51656,7 +51837,7 @@ walks past you.
The first one is the **Meetup Laurel**: a gold laurel circlet, open at the
front, with three pearl berries in the gap. It was granted at the
-[`$THREE` First Holders Meetup](#sec-328). That window has closed, so
+[`$THREE` First Holders Meetup](#sec-333). That window has closed, so
the laurel is now exactly what this page promises: owned only by the players who
were in the world that day, and never granted again.
@@ -51886,15 +52067,15 @@ machine prefer the two above, which cover the same ground between them.
## Related
-- **[Live events in /play](#sec-328)** covers the rest of what that
+- **[Live events in /play](#sec-333)** covers the rest of what that
config file drives: the countdown, the agenda drawer, the fireworks.
-- **[The in-game economy](#sec-252)** covers the two currencies and
+- **[The in-game economy](#sec-255)** covers the two currencies and
the `$THREE` boutique the souvenir deliberately stays out of.
- **[Coin communities](#sec-145)** covers the worlds the events happen in.
---
-<a id="sec-217"></a>
+<a id="sec-219"></a>
> **Source:** `docs/examples.md` · [↑ table of contents](#table-of-contents)
@@ -52703,7 +52884,7 @@ Run any command from the repo root after `npm install`. The web component demos
---
-<a id="sec-218"></a>
+<a id="sec-220"></a>
> **Source:** `docs/exit-lab.md` · [↑ table of contents](#table-of-contents)
@@ -52725,7 +52906,7 @@ recorded number from a position that cost real money.
## Why this is not the backtester
three.ws already ships a backtester ([`api/_lib/strategy-backtest.js`](../api/_lib/strategy-backtest.js),
-documented in [trading-experiment.md](#sec-413)). The two answer
+documented in [trading-experiment.md](#sec-418)). The two answer
different questions and neither replaces the other.
| | Backtester (`/api/sniper/backtest`) | Exit Lab (`/exit-lab`) |
@@ -52935,14 +53116,14 @@ to the nearest legal one rather than throwing.
## Related
- [Agent Sniper](#sec-061), the worker whose positions this replays
-- [Autonomous Trading hub](#sec-414), the front door to every trading surface
-- [Trading experiment](#sec-413), the policy this fleet runs and why
-- [Read the trading fleet](#sec-461), how to interpret fleet vitals
-- Tutorial: [Find a better exit policy](#sec-440)
+- [Autonomous Trading hub](#sec-419), the front door to every trading surface
+- [Trading experiment](#sec-418), the policy this fleet runs and why
+- [Read the trading fleet](#sec-467), how to interpret fleet vitals
+- Tutorial: [Find a better exit policy](#sec-446)
---
-<a id="sec-219"></a>
+<a id="sec-221"></a>
> **Source:** `docs/fact-check.md` · [↑ table of contents](#table-of-contents)
@@ -52979,7 +53160,7 @@ The fact-check pipeline (`runFactCheck`):
The LLM routes through the platform's shared free-first policy (Groq and OpenRouter as funded defaults). Results are cached in Redis for 7 days keyed by a hash of the claim, strictness, and any image URL, so an identical claim (on either lane) never re-runs the live chain.
-**The attestation** is a tamper-evident content digest: `sha256:` followed by the SHA-256 of a JSON object of `{ verdict, confidence, claim, source URLs }`. It is returned as a string field you can recompute to confirm the verdict was not altered. Note that this is a content hash, not an on-chain record; it is distinct from the platform's [SAS credentialed attestations](#sec-372) and [3D provenance anchoring](#sec-335), which do write to Solana.
+**The attestation** is a tamper-evident content digest: `sha256:` followed by the SHA-256 of a JSON object of `{ verdict, confidence, claim, source URLs }`. It is returned as a string field you can recompute to confirm the verdict was not altered. Note that this is a content hash, not an on-chain record; it is distinct from the platform's [SAS credentialed attestations](#sec-377) and [3D provenance anchoring](#sec-340), which do write to Solana.
**The benchmark** (`GET /api/fact-check-benchmark`) scores a 40-claim fixture (10 per verdict class, deliberately time-stable and non-partisan) against the real chain. The API never fabricates a score: with no run available, `ran` is false and `report` is null, and the page renders a designed "not yet run" empty state. Both the claim set and the scoring runner are linked from the page for inspection. See [Running the benchmark](#running-the-benchmark) for how a run is produced and published.
@@ -53024,7 +53205,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-544).
+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).
## Running the benchmark
@@ -53087,14 +53268,14 @@ Two guards keep a bad run from becoming a published number:
## Related
-- [x402: paid agent skills](#sec-544): the payment rail the $0.10 lane rides
+- [x402: paid agent skills](#sec-551): 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-372) and [3D provenance](#sec-335): the platform's on-chain attestation primitives (distinct from this content-hash attestation)
+- [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)
---
-<a id="sec-220"></a>
+<a id="sec-222"></a>
> **Source:** `docs/farcaster-memory-seeding.md` · [↑ table of contents](#table-of-contents)
@@ -53113,7 +53294,7 @@ own verification records.
- **Surface**: the Farcaster panel in the agent persona editor at [/dashboard/agents](https://three.ws/dashboard/agents)
- **API**: `/api/agents/:id/memory/seed/farcaster`
-- **Related**: [Memory system](#sec-280), [`@three-ws/agent-memory`](https://www.npmjs.com/package/@three-ws/agent-memory)
+- **Related**: [Memory system](#sec-284), [`@three-ws/agent-memory`](https://www.npmjs.com/package/@three-ws/agent-memory)
---
@@ -53344,7 +53525,7 @@ only its own rows and a revoke deletes exactly what was granted.
---
-<a id="sec-221"></a>
+<a id="sec-223"></a>
> **Source:** `docs/financial-controls.md` · [↑ table of contents](#table-of-contents)
@@ -53357,7 +53538,7 @@ on-chain transaction is captured, whether it is reconciled against the chain, an
how long it is retained** — plus the monitoring/breach controls around it and the
open gaps ranked by accounting/regulatory risk.
-It is a companion to the [money map](#sec-287) (who receives what) and the
+It is a companion to the [money map](#sec-291) (who receives what) and the
[Solana signers runbook](../api/_lib/solana-signers.js) (the
wallets). Keep it in sync with the code — every row cites its source.
@@ -53635,20 +53816,168 @@ Ranked by accounting/regulatory risk. Each is a tracked remediation item.
re-run `check-relayer-balances.mjs` to confirm balances.
- **Before adding a paid flow:** it is not done until it writes an append-only
ledger row with the on-chain signature and a `UNIQUE` idempotency key, and is
- added to this register and the [money map](#sec-287).
+ added to this register and the [money map](#sec-291).
---
## Related
-- [Money map](#sec-287) — who receives each payment.
-- [x402 revenue & receipts](#sec-540) — the x402 recording detail.
-- [x402 endpoints](#sec-539) — the paid endpoint catalog.
+- [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.
- [Solana signers runbook](../api/_lib/solana-signers.js) — the wallets + funding.
---
-<a id="sec-222"></a>
+<a id="sec-224"></a>
+
+> **Source:** `docs/first-contribution.md` · [↑ table of contents](#table-of-contents)
+
+# Your first contribution
+
+Clone to open pull request in about 15 minutes. No prior knowledge of the codebase assumed.
+
+If you get stuck at any step, ask in [Discussions](https://github.com/nirholas/three.ws/discussions) or the [Telegram community](https://t.me/three_ws_community). A stuck contributor is a bug in this document and we want to hear about it.
+
+---
+
+## 1. Get it running (5 minutes)
+
+```bash
+git clone https://github.com/nirholas/three.ws.git
+cd three.ws
+npm install
+npm run setup
+npm run dev
+```
+
+Open http://localhost:3000. You should see a 3D avatar you can orbit with the mouse.
+
+`npm run setup` is not optional and not the same as `npm install`. It builds the local `solana-agent-sdk` (linked as a `file:` dependency with no prebuilt `dist/`) and generates the gitignored `data/_generated/*` artifacts that the app, the sitemap, and the test suite read. It is idempotent, so re-running it is always safe.
+
+You do **not** need any API keys, a wallet, or a database to work on the rendering, rigging, animation, or docs layers. Those layers are pure client-side JavaScript and their tests run offline.
+
+## 2. Find something to work on
+
+Browse [`good first issue`](https://github.com/nirholas/three.ws/labels/good%20first%20issue). Every one of them names the file to change and the command that proves the change worked.
+
+**Comment on the issue before you start.** One line ("taking this") is enough. It stops two people doing the same work, and it means a maintainer can hand you context before you have written code rather than after.
+
+## 3. A worked example: teach the retargeter a new rig
+
+This is the highest-value first contribution in the project, so here is the whole thing end to end.
+
+### The problem
+
+three.ws ships one library of pre-baked animation clips and plays them on *any* humanoid avatar a user uploads. That only works because every rig gets rewritten to one canonical skeleton first. The trouble is that no two tools name bones the same way. Mixamo says `LeftArm`, Unreal says `upperarm_l`, VRoid says `J_Bip_L_UpperArm`, Daz says `lShldr`.
+
+[`src/glb-canonicalize.js`](../src/glb-canonicalize.js) is the map that reconciles them. Every convention it knows about is a rig that animates; every convention it does not know about falls back to a default body. Adding a convention is a self-contained, high-leverage change with a fast test loop.
+
+### Check what is missing
+
+```js
+// scratch.mjs
+import { canonicalizeBoneName } from './src/glb-canonicalize.js';
+console.log(canonicalizeBoneName('左腕')); // null → not supported yet
+console.log(canonicalizeBoneName('upperarm_l')); // 'LeftArm' → already supported
+```
+
+```bash
+node scratch.mjs
+```
+
+`null` means the bone would be dropped and the rig would score below the retarget coverage floor.
+
+### Make the change
+
+Bone-name variants live in the `EXTRA_ALIASES` map in [`src/glb-canonicalize.js`](../src/glb-canonicalize.js). Entries are keyed by a separator-stripped, lowercased form, and the `put()` helper does that normalization for you. First spelling wins, so listing order is priority order.
+
+A MikuMikuDance rig, for example, names bones in Japanese with a 左 / 右 side prefix:
+
+```js
+// MikuMikuDance (MMD) skeletons name bones in Japanese, side-prefixed
+// with 左 (left) / 右 (right). Extremely common in the VRM/anime avatar
+// ecosystem, and none of these spellings share a stem with any Latin rig.
+for (const [v, c] of [
+ ['センター', 'Hips'], ['上半身', 'Spine'], ['上半身2', 'Spine1'],
+ ['首', 'Neck'], ['頭', 'Head'],
+]) put(v, c);
+for (const [side, prefix] of [['左', 'Left'], ['右', 'Right']]) {
+ put(`${side}肩`, `${prefix}Shoulder`);
+ put(`${side}腕`, `${prefix}Arm`);
+ put(`${side}ひじ`, `${prefix}ForeArm`);
+ put(`${side}手首`, `${prefix}Hand`);
+ put(`${side}足`, `${prefix}UpLeg`);
+ put(`${side}ひざ`, `${prefix}Leg`);
+ put(`${side}足首`, `${prefix}Foot`);
+ put(`${side}つま先`, `${prefix}ToeBase`);
+}
+```
+
+### Prove it
+
+Add a case to [`tests/glb-canonicalize.test.js`](../tests/glb-canonicalize.test.js) beside the existing per-convention blocks:
+
+```js
+it('maps an MMD (Japanese) skeleton', () => {
+ expect(canonicalizeBoneName('センター')).toBe('Hips');
+ expect(canonicalizeBoneName('左腕')).toBe('LeftArm');
+ expect(canonicalizeBoneName('右ひざ')).toBe('RightLeg');
+});
+
+it('never crosses sides', () => {
+ expect(canonicalizeBoneName('左足首')).toBe('LeftFoot');
+ expect(canonicalizeBoneName('右足首')).toBe('RightFoot');
+});
+```
+
+Run just that file. It takes about a second:
+
+```bash
+npx vitest run tests/glb-canonicalize.test.js
+```
+
+Then run the whole suite before you open the PR:
+
+```bash
+npm test
+```
+
+Two rules that will save you a review round:
+
+- **Never cross sides.** A mapping that sends a left bone to a right canonical name tears the avatar apart in motion, and it is the single most common mistake in this file. Test both sides, always.
+- **Do not map bones that are not skeleton joints.** Constraint-driven control rigs, tracker nodes, and metacarpal scaffolding are deliberately left unmapped. The header comment in `glb-canonicalize.js` explains why in detail. Read it before you widen a match.
+
+## 4. Open the pull request
+
+```bash
+git checkout -b feat/mmd-bone-names
+npx prettier --write src/glb-canonicalize.js tests/glb-canonicalize.test.js
+git add src/glb-canonicalize.js tests/glb-canonicalize.test.js
+git commit -m "feat(rig): map MikuMikuDance Japanese bone names to the canonical skeleton"
+git push origin feat/mmd-bone-names
+```
+
+Then open the PR on GitHub. In the description say what changed, what you tested it against, and paste the test output. If you have a real GLB that exercises the change, link it.
+
+**Commit message format:** `type(scope): what changed and why a reader would care`. Plain language, specific to your diff. `wip`, `update`, and `changes` are rejected.
+
+## 5. What happens next
+
+See [Triage](#sec-421) for the full flow and response targets. In short: a maintainer reads it, you get real review comments, and merged work shows up in the [public changelog](https://three.ws/changelog).
+
+---
+
+## Other good places to start
+
+- **Animation.** Add a clip to the shared library, or improve the retarget quality in [`src/animation-retarget.js`](../src/animation-retarget.js).
+- **Docs.** Run `npm run audit:docs`. Anything it reports is a real, mechanically verified defect and a legitimate PR.
+- **MCP tools.** Every package under `packages/*-mcp` follows the same shape. Copy the closest one and you have a working new tool.
+- **Whatever annoyed you.** If something in the product felt wrong the first time you used it, that reaction is worth more than any list we could write. Open an issue describing it.
+
+---
+
+<a id="sec-225"></a>
> **Source:** `docs/forge-background-generation.md` · [↑ table of contents](#table-of-contents)
@@ -53768,7 +54097,7 @@ and the notification preference model in
---
-<a id="sec-223"></a>
+<a id="sec-226"></a>
> **Source:** `docs/forge-off.md` · [↑ table of contents](#table-of-contents)
@@ -53885,7 +54214,7 @@ Backfill a past week's winner (owner): `GET /api/cron/forge-off-crown?week=YYYY-
---
-<a id="sec-224"></a>
+<a id="sec-227"></a>
> **Source:** `docs/forge-pipeline.md` · [↑ table of contents](#table-of-contents)
@@ -53893,7 +54222,7 @@ Backfill a past week's winner (owner): `GET /api/cron/forge-off-crown?week=YYYY-
This is the engineering guide to the Forge, the text/image/sketch to 3D generation system behind [/forge](https://three.ws/forge), the free MCP tools, and every agent-facing 3D endpoint. It maps the whole path a generation takes: entry points, the engine grid, free-first routing, the job lifecycle, failover, persistence, GPU workers, post-processing, and payments.
-If you want the product-level overview, read [Forge](#sec-225). If you want the plain-language version, read [How the Forge works](#sec-239). This document is for people changing the pipeline.
+If you want the product-level overview, read [Forge](#sec-228). If you want the plain-language version, read [How the Forge works](#sec-242). This document is for people changing the pipeline.
## Bird's-eye view
@@ -54030,7 +54359,7 @@ Async jobs get an opaque HMAC-signed token (`f1.<payload>.<sig>`, `api/_lib/forg
### Poll
-`GET /api/forge?job=<id>` returns `status`: `queued`, `running`, `done` (with `glb_url`, `viewer_url`, and the `path`/`tier`/`backend` that actually produced it), or `failed`. Polling is free and unauthenticated. The in-flight job id is also written to `localStorage`, so an interrupted browser session resumes polling for up to 30 minutes; background completion persists the result to the user's gallery either way (see [Background generation](#sec-222)).
+`GET /api/forge?job=<id>` returns `status`: `queued`, `running`, `done` (with `glb_url`, `viewer_url`, and the `path`/`tier`/`backend` that actually produced it), or `failed`. Polling is free and unauthenticated. The in-flight job id is also written to `localStorage`, so an interrupted browser session resumes polling for up to 30 minutes; background completion persists the result to the user's gallery either way (see [Background generation](#sec-225)).
**Poll-time failover** (`api/_lib/forge-failover.js`) closes the nastier gap: a self-host worker can accept a task and fail it minutes later, in a poll handled by a different instance that no longer holds the request. On a failed poll the module recovers the original inputs (prompt plus reference image) from the creation row, resubmits to the next configured lane, and binds old handle to new handle in Redis (2 hour TTL). The client keeps polling the same job id and simply sees `status: running` with a new `backend`. Hops are capped by `MAX_FAILOVER_HOPS = 3` (one primary plus up to three backups). The redispatch order is `trellis_selfhost`, `hunyuan3d`, `trellis`: HuggingFace is excluded because its provider blocks through the whole generation (cannot be ridden from a poll), and NVIDIA is excluded because poll-time redispatch always reconstructs from a stored reference image, which NIM rejects.
@@ -54135,17 +54464,17 @@ Fast diagnostics: `forge_creations` carries per-generation backend, status, erro
## Related
-- [Forge](#sec-225), the product-level doc for the /forge surface.
-- [How the Forge works](#sec-239), the plain-language explainer.
+- [Forge](#sec-228), the product-level doc for the /forge surface.
+- [How the Forge works](#sec-242), the plain-language explainer.
- [3D pipeline](#sec-003), the pay-per-stage x402 pipeline (rig, remesh, gameready, stylize, rembg).
- [3D asset pipeline](#sec-002), formats and the animation/conversion flow.
- [Avatar pipeline](#sec-113), the selfie-to-avatar reconstruction flow.
-- [Background generation](#sec-222), job resume and gallery persistence.
+- [Background generation](#sec-225), job resume and gallery persistence.
- `workers/README.md`, the worker-by-worker operational reference.
---
-<a id="sec-225"></a>
+<a id="sec-228"></a>
> **Source:** `docs/forge.md` · [↑ table of contents](#table-of-contents)
@@ -54354,16 +54683,16 @@ dashboard at [/quality-bench](https://three.ws/quality-bench) (internal).
## Related
-- [The Forge pipeline](#sec-224) is the architecture deep dive: the engine grid, routing, failover, job lifecycle, workers, and payments, end to end. [How the Forge works](#sec-239) is the same story in plain language.
-- [Image to 3D](#sec-251) is the photo lane opened directly at [/image-to-3d](https://three.ws/image-to-3d).
+- [The Forge pipeline](#sec-227) is the architecture deep dive: the engine grid, routing, failover, job lifecycle, workers, and payments, end to end. [How the Forge works](#sec-242) is the same story in plain language.
+- [Image to 3D](#sec-254) is the photo lane opened directly at [/image-to-3d](https://three.ws/image-to-3d).
- [/forge-max](https://three.ws/forge-max) is the maximum-quality lane opened directly: the same Forge with the High tier pinned on arrival (200k-poly target, 4K PBR and HD textures, subject-aware engine routing). `?tier=draft|standard|high` presets the quality selector on any Forge URL the same way. The High tier's $THREE hold-or-pay gate applies unchanged; BYOK engines (your own Meshy, Tripo, or Rodin key) are exempt as always. For DamagedHelmet-class artist benchmarks, remember the ceiling is the current state of generative 3D, not the routing: this lane maxes every budget the engines expose, and [Measuring realism](#measuring-realism) is how we track that ceiling moving.
-- [Diorama](#sec-177) forges a whole scene of Forge objects into one explorable world.
+- [Diorama](#sec-179) forges a whole scene of Forge objects into one explorable world.
- The 3D generation architecture: [3D pipeline](#sec-003), [3D asset pipeline](#sec-002), [3D API](#sec-001).
- Pages: [/create](https://three.ws/create) (the avatar creator), [/scene](https://three.ws/scene) (Scene Studio), [/restyle](https://three.ws/restyle) (re-skin a GLB), [/gallery](https://three.ws/gallery).
---
-<a id="sec-226"></a>
+<a id="sec-229"></a>
> **Source:** `docs/forged.md` · [↑ table of contents](#table-of-contents)
@@ -54371,7 +54700,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-544). Nothing on the page is curated or seeded by
+[x402 payment protocol](#sec-551). 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
@@ -54421,7 +54750,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-541), and the loop's daily spend cap
+ [x402 ring economy](#sec-548), 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
@@ -54499,21 +54828,21 @@ 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-541): the wider self-paid endpoint
+- [x402 ring economy](#sec-548): the wider self-paid endpoint
economy the seeder wallet participates in.
-- [How the Forge works](#sec-239): the generation pipeline the
+- [How the Forge works](#sec-242): the generation pipeline the
agents are paying for.
-- [x402 on three.ws](#sec-544): the payment protocol itself.
+- [x402 on three.ws](#sec-551): the payment protocol itself.
---
-<a id="sec-227"></a>
+<a id="sec-230"></a>
> **Source:** `docs/free-crypto-apis.md` · [↑ table of contents](#table-of-contents)
# Free crypto APIs we have not integrated yet
-Research catalog, 2026-08-05. Companion to [free-llm-providers.md](#sec-228).
+Research catalog, 2026-08-05. Companion to [free-llm-providers.md](#sec-231).
**Status update 2026-08-06: every keyless provider in this catalog is now integrated.** Shipped in eight workstreams: the seven CEX public-data venues (Binance, OKX, Bybit, KuCoin, Gate.io, MEXC, Bitget) as market/chart fallback rungs; RedStone and Switchboard as SOL price oracle rungs; RugCheck fused with GoPlus and Honeypot.is wired into EVM token risk; Deribit options/perp data beside Hyperliquid plus Jupiter's unused lite endpoints; a keyless EVM swap-quote chain (ParaSwap, KyberSwap, LI.FI) at `/api/v1/evm/swap-quote`; Coin Metrics fundamentals, Blockchair chain stats, and Blockstream Esplora Bitcoin reads; six subreddits in the news pipeline (JSON with Atom fallback, since Reddit 403s datacenter JSON traffic); and a gas oracle chain (Blocknative, Owlracle, Etherscan) at `/api/v1/gas`. Deliberately skipped: CoinMarketCap's keyless trial endpoints (evaluation-only under their terms). Everything still listed as needing a key below remains open.
@@ -54662,7 +54991,7 @@ Adoption rules that still apply: these are all free tiers, so no owner approval
---
-<a id="sec-228"></a>
+<a id="sec-231"></a>
> **Source:** `docs/free-llm-providers.md` · [↑ table of contents](#table-of-contents)
@@ -54724,11 +55053,11 @@ All of these rungs are zero-marginal-cost, and the accounting knows it:
6. If the provider should be user-selectable in chat: register it in `api/chat.js` (`PROVIDERS`, the provider enum, `FALLBACK_SIBLINGS`) and `api/_lib/chat-models.js` (`MODEL_CATALOG`, `PROVIDER_MODEL_DEFAULTS`, `DEFAULT_PROVIDER_ORDER`, `ANON_PROVIDER_LIST`).
7. `.env.example` and the env tables in [`ARCHITECTURE.md`](../ARCHITECTURE.md).
-Related: [nvidia-models.md](#sec-297) for the full NVIDIA NIM surface map.
+Related: [nvidia-models.md](#sec-301) for the full NVIDIA NIM surface map.
---
-<a id="sec-229"></a>
+<a id="sec-232"></a>
> **Source:** `docs/galaxy.md` · [↑ table of contents](#table-of-contents)
@@ -54806,13 +55135,13 @@ curl -X POST 'https://three.ws/api/galaxy' \
## Related
-- [IBM Granite suite](#sec-250): the full set of watsonx-powered features on three.ws, including the Granite embeddings that position this galaxy.
+- [IBM Granite suite](#sec-253): the full set of watsonx-powered features on three.ws, including the Granite embeddings that position this galaxy.
- [Agent system](#sec-064) and [Agent reputation](#sec-056): what a "star" is and how agents earn standing.
- Pages: [/galaxy](https://three.ws/galaxy), [/create](https://three.ws/create), [/agents](https://three.ws/agents).
---
-<a id="sec-230"></a>
+<a id="sec-233"></a>
> **Source:** `docs/generation-watch.md` · [↑ table of contents](#table-of-contents)
@@ -54868,7 +55197,7 @@ The page polls `GET /api/3d/studio?job=<id>` and moves through five states:
painted reference image, the first step of the text-to-3D pipeline), it fades
in with the caption "Concept art, now being sculpted into 3D". This is the
same paint-then-reconstruct flow described in
- [How the Forge works](#sec-239).
+ [How the Forge works](#sec-242).
- **Ready.** When the poll returns `status: "done"`, the page shows "opening
the viewer" and redirects itself into the interactive viewer after a short
beat, using the API's `viewerUrl` (or building a `/viewer?src=<glb>` link
@@ -54914,15 +55243,15 @@ server-side: the platform tracks every generation to completion whether or not
any tab is watching, finished models land in the creator's gallery, and
unattended completions notify through the bell, push, and email channels. That
machinery is documented in
-[Background generation and completion notifications](#sec-222).
+[Background generation and completion notifications](#sec-225).
Closing the watch tab mid-job therefore loses nothing; reopening the same
`?job=` link resumes exactly where the generation actually is.
## Related
-- [How the Forge works](#sec-239): the pipeline behind the
+- [How the Forge works](#sec-242): the pipeline behind the
countdown.
-- [Background generation](#sec-222): server-side
+- [Background generation](#sec-225): server-side
tracking, resume, and notifications.
- [The 3D Studio GPT](#sec-138): the main surface that hands
out watch links.
@@ -54930,7 +55259,7 @@ Closing the watch tab mid-job therefore loses nothing; reopening the same
---
-<a id="sec-231"></a>
+<a id="sec-234"></a>
> **Source:** `docs/genesis.md` · [↑ table of contents](#table-of-contents)
@@ -54956,7 +55285,7 @@ real job state, so a first-time visitor goes from an idea to a wallet-holding,
animation-ready agent they fully own in under a minute of active work. It is the
front door: the artifact it produces is a first-class agent that plugs straight
into [Agent Studio](#sec-062), the [economy](#sec-104),
-[breeding](#sec-232), and every embed surface.
+[breeding](#sec-235), and every embed surface.
## How it works
@@ -54977,7 +55306,7 @@ never invents a shortcut path; it orchestrates the real ones.
Genesis resolves it via `GET /api/agents?avatar_id=...`, then calls
`POST /api/agents/:id/wallet/provision` to guarantee both a custodial Solana
address and a custodial EVM address exist. These are real custodial keys held for
- the agent (see [Agent Wallets](#sec-072) and [Custody](#sec-170)),
+ the agent (see [Agent Wallets](#sec-072) and [Custody](#sec-172)),
Solana first because Solana is the home chain.
- **Persona and voice.** `POST /api/persona/extract` synthesizes a structured
in-character system prompt from your description, running through the shared LLM
@@ -54990,7 +55319,7 @@ never invents a shortcut path; it orchestrates the real ones.
`/api/tts/voices`. Your chosen name, persona, and voice are persisted with
`PATCH /api/agents/:id`.
- **On-chain identity (optional).** The final step mints a real
- [ERC-8004](#sec-188) identity record for the agent and returns a real tx
+ [ERC-8004](#sec-190) identity record for the agent and returns a real tx
hash, defaulting to Base (chain id 8453) to match the rest of the platform's EVM
identity layer. This step is optional: the agent is fully functional without it.
@@ -55012,8 +55341,8 @@ never invents a shortcut path; it orchestrates the real ones.
6. **Optionally bind an on-chain identity.** One click registers the ERC-8004 record
and shows the returned transaction hash.
7. **You now own a complete agent.** Open it in [Agent Studio](#sec-062) to
- keep authoring, drop it on a site via [Integrations](#sec-254), or breed
- it in [Agent Genome](#sec-232).
+ keep authoring, drop it on a site via [Integrations](#sec-257), or breed
+ it in [Agent Genome](#sec-235).
## Examples
@@ -55071,16 +55400,16 @@ curl -s -X POST "https://three.ws/api/agents/$AGENT_ID/wallet/provision" \
## Related
- [Agent Studio](#sec-062): keep authoring the agent Genesis created
-- [Agent Genome](#sec-232): breed two agents into an inherited child
+- [Agent Genome](#sec-235): breed two agents into an inherited child
- [Avatar Reconstruction](#sec-114): the selfie-to-3D pipeline
-- [Agent Wallets](#sec-072) and [Custody](#sec-170): the custodial keys
-- [ERC-8004](#sec-188): the on-chain identity record
-- [Persona Hub](#sec-323): how personas are synthesized
+- [Agent Wallets](#sec-072) and [Custody](#sec-172): the custodial keys
+- [ERC-8004](#sec-190): the on-chain identity record
+- [Persona Hub](#sec-328): how personas are synthesized
- Pages: [/genesis](https://three.ws/genesis), [/create](https://three.ws/create), [/agent-studio](https://three.ws/agent-studio)
---
-<a id="sec-232"></a>
+<a id="sec-235"></a>
> **Source:** `docs/genome.md` · [↑ table of contents](#table-of-contents)
@@ -55213,16 +55542,16 @@ curl -s "https://three.ws/api/genome/lineage?agentId=<child-uuid>&verify=1"
## Related
-- [Instant Agent Genesis](#sec-231): mint the parents in under a minute
+- [Instant Agent Genesis](#sec-234): mint the parents in under a minute
- [Agent Skills](#sec-060): the skill licenses that recombine
- [Agent Wallets](#sec-072): the fresh child wallet
- [Agent Reputation](#sec-056): how pedigree feeds standing
-- [ERC-8004](#sec-188): on-chain identity for bred agents
+- [ERC-8004](#sec-190): on-chain identity for bred agents
- Pages: [/genome](https://three.ws/genome), [/agent-studio](https://three.ws/agent-studio)
---
-<a id="sec-233"></a>
+<a id="sec-236"></a>
> **Source:** `docs/ghost-copy.md` · [↑ table of contents](#table-of-contents)
@@ -55382,7 +55711,7 @@ renders the summary without it is misrepresenting the result.
cautious question with a basket instead of a single leader.
- Downstream: [/vaults](https://three.ws/vaults) is where a convinced visitor
copies with real money, under segregated custody and hard spend limits. See
- [docs/copy-trading.md](#sec-165) for that engine.
+ [docs/copy-trading.md](#sec-167) for that engine.
- A leader's underlying record: `/trader/<agent_id>`, one click from every result.
## Source
@@ -55397,7 +55726,7 @@ renders the summary without it is misrepresenting the result.
---
-<a id="sec-234"></a>
+<a id="sec-237"></a>
> **Source:** `docs/github-memory-seeding.md` · [↑ table of contents](#table-of-contents)
@@ -55424,7 +55753,7 @@ the same consent screen.
- **Surface**: Settings, Connected accounts, GitHub card at [/settings#connected-accounts](https://three.ws/settings#connected-accounts)
- **API**: `/api/agents/:id/memory/seed/github`, `/api/auth/github/token`
-- **Related**: [Memory system](#sec-280), [X memory seeding](#sec-515), [Farcaster memory seeding](#sec-220)
+- **Related**: [Memory system](#sec-284), [X memory seeding](#sec-521), [Farcaster memory seeding](#sec-222)
---
@@ -55722,7 +56051,7 @@ rather than inviting a retry that would only earn a 429.
---
-<a id="sec-235"></a>
+<a id="sec-238"></a>
> **Source:** `docs/google-x-accounts.md` · [↑ table of contents](#table-of-contents)
@@ -55834,7 +56163,7 @@ Google also operates many country and regional accounts (for example @GoogleIndi
---
-<a id="sec-236"></a>
+<a id="sec-239"></a>
> **Source:** `docs/guardian.md` · [↑ table of contents](#table-of-contents)
@@ -55860,7 +56189,7 @@ The owner sets this up from their own wallet hub (naming guardians, an approval
The response sorts agents that need your action first, then those with an open process, then the rest, and reports how many need you.
-**The safety rails** (detailed in [custody](#sec-170)) are enforced by the recovery API, not the console:
+**The safety rails** (detailed in [custody](#sec-172)) are enforced by the recovery API, not the console:
- The requester cannot approve their own takeover; at least one other guardian must approve.
- The wallet auto-freezes for autonomous spend the moment a request opens (the real owner's own withdrawal stays open).
@@ -55913,14 +56242,14 @@ The console reads this on load, resolves your viewer id (so it can tell whether
## Related
-- [Custody you can verify](#sec-170) - the full recovery and inheritance model, the freeze switch, spend limits, and proof-of-custody
-- [Financial controls](#sec-221) - the plain-English spend rules on the same wallet rails
+- [Custody you can verify](#sec-172) - the full recovery and inheritance model, the freeze switch, spend limits, and proof-of-custody
+- [Financial controls](#sec-223) - the plain-English spend rules on the same wallet rails
- `GET /api/custody/integrity` - the public Merkle attestation of every custodial wallet, as JSON (the page that rendered it is switched off while on-chain anchoring is unavailable)
- [/proof](https://three.ws/proof) - verify your own wallet's inclusion in the attestation, in your browser
---
-<a id="sec-237"></a>
+<a id="sec-240"></a>
> **Source:** `docs/guards.md` · [↑ table of contents](#table-of-contents)
@@ -56169,7 +56498,7 @@ The short version:
---
-<a id="sec-238"></a>
+<a id="sec-241"></a>
> **Source:** `docs/hold-to-access.md` · [↑ table of contents](#table-of-contents)
@@ -56471,19 +56800,19 @@ worlds unaffected.
## Related
-- [Validation](#sec-501) — the quality gate every model passes before publish.
+- [Validation](#sec-507) — the quality gate every model passes before publish.
- [Pricing catalog](../api/_lib/pricing/catalog.js) — fixed-price actions the discount applies to.
- [`/three`](../pages/three.html) — the holder-facing tier page that surfaces this ladder.
---
-<a id="sec-239"></a>
+<a id="sec-242"></a>
> **Source:** `docs/how-forge-works.md` · [↑ table of contents](#table-of-contents)
# How the Forge works, in plain language
-You type "a weathered brass diving helmet" at [three.ws/forge](https://three.ws/forge), and about half a minute later you are orbiting a real, textured 3D model you can download, view in AR, or drop into a scene. No account, no key, no cost. This page explains what actually happens in between, without the engineering detail. (If you want that, read the [architecture deep dive](#sec-224).)
+You type "a weathered brass diving helmet" at [three.ws/forge](https://three.ws/forge), and about half a minute later you are orbiting a real, textured 3D model you can download, view in AR, or drop into a scene. No account, no key, no cost. This page explains what actually happens in between, without the engineering detail. (If you want that, read the [architecture deep dive](#sec-227).)
## The five steps every generation takes
@@ -56517,17 +56846,17 @@ 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-274) or plain HTTP, and other agents pay per call with USDC over [x402](#sec-544), 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-551), no account needed. The page you use and the API an agent uses are the same pipeline underneath.
## Try it
- Type a prompt: [three.ws/forge](https://three.ws/forge)
- Turn photos into a model: [three.ws/image-to-3d](https://three.ws/image-to-3d)
-- The full technical breakdown: [the Forge pipeline deep dive](#sec-224)
+- The full technical breakdown: [the Forge pipeline deep dive](#sec-227)
---
-<a id="sec-240"></a>
+<a id="sec-243"></a>
> **Source:** `docs/how-it-works.md` · [↑ table of contents](#table-of-contents)
@@ -56535,7 +56864,7 @@ Everything above is also a tool call. AI agents (Claude, ChatGPT, or your own) g
This page is the load-bearing mental model. If you're trying to figure out where a feature lives, how a request flows, or which layer to extend — start here.
-For the full deep dive on internals, see [Architecture overview](#sec-100). For the actual JS API, see [JavaScript API](#sec-258) and [REST API](#sec-096). This document zooms out to *how it all fits together*.
+For the full deep dive on internals, see [Architecture overview](#sec-100). For the actual JS API, see [JavaScript API](#sec-261) and [REST API](#sec-096). This document zooms out to *how it all fits together*.
---
@@ -56582,10 +56911,10 @@ The whole stack is split into four horizontal strata. Each layer can run on its
└──────────────────────────────────────────────┘
```
-- **Viewer layer** — pure three.js. Knows nothing about agents, brains, or wallets. Useful on its own as a glTF inspector and as the rendering engine for Turntable / Animation Gallery widgets. See [Layers](#sec-262) for the contract.
+- **Viewer layer** — pure three.js. Knows nothing about agents, brains, or wallets. Useful on its own as a glTF inspector and as the rendering engine for Turntable / Animation Gallery widgets. See [Layers](#sec-265) for the contract.
- **Agent layer** — turns a static GLB into a presence. LLM tool-loop, skill registry, memory, and a continuous emotion blend that drives morphs and gaze. See [Agent system](#sec-064).
-- **Identity layer** — durability across sessions, devices, and embed hosts. Wallet auth, on-chain registration, IPFS-pinned manifest bundles, signed action diary. Entirely optional. See [ERC-8004](#sec-188) and [Solana agents](#sec-394).
-- **Embed layer**: the public face. The `<agent-3d>` custom element, ten widget variants, iframe embeds, the CDN bundle, the SPA, and the route table in `vercel.json` (read at runtime by the Cloud Run server). See [Embedding](#sec-186).
+- **Identity layer** — durability across sessions, devices, and embed hosts. Wallet auth, on-chain registration, IPFS-pinned manifest bundles, signed action diary. Entirely optional. See [ERC-8004](#sec-190) and [Solana agents](#sec-399).
+- **Embed layer**: the public face. The `<agent-3d>` custom element, ten widget variants, iframe embeds, the CDN bundle, the SPA, and the route table in `vercel.json` (read at runtime by the Cloud Run server). See [Embedding](#sec-188).
The four layers communicate through one event bus (`agent-protocol`). Every meaningful action is a `CustomEvent` on a singleton. That single design choice is why you can swap the avatar for a 2D sprite, the runtime for a different LLM, or memory for a vector store — and nothing else changes.
@@ -56655,7 +56984,7 @@ On-chain identity is optional. Most agents work fine without it. You'd want it w
- **You want delegated wallet permissions.** ERC-7710 lets you sign once per session and grant the agent scoped, time-bound permission to act on-chain — no per-transaction prompts.
- **You want a portable address.** `agent://base/42` is a stable, resolver-agnostic URI. Any client that speaks the protocol can load it.
-See [erc8004.md](#sec-188) and [solana.md](#sec-394) for the registration flows.
+See [erc8004.md](#sec-190) and [solana.md](#sec-399) for the registration flows.
---
@@ -56678,14 +57007,14 @@ Quick lookup for "I want to ship X":
| You want… | Reach for… |
|---|---|
| A 3D character on a marketing page | The CDN script + `<agent-3d>` |
-| A character in Notion / Webflow / Framer | An iframe widget from [Widget Studio](#sec-510) |
+| A character in Notion / Webflow / Framer | An iframe widget from [Widget Studio](#sec-516) |
| A talking AI sidekick that follows visitors | `<agent-3d mode="floating">` |
-| A character that controls a scene from page events | The JS API (`agent.say()`, `agent.ask()`) — see [js-api.md](#sec-258) |
+| 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-188) or [Solana](#sec-394) |
-| A paid API anyone (including agents) can call | [x402 monetization](#sec-544) |
-| Multiple agents in one scene | `<agent-stage>` — see [multi-agent.md](#sec-290) |
-| To register a domain (e.g. ENS) as agent identity | [register-onchain.md tutorial](#sec-462) |
+| 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) |
+| 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) |
---
@@ -56693,12 +57022,12 @@ Quick lookup for "I want to ship X":
- **[Architecture overview](#sec-100)** — full internals
- **[Agent system](#sec-064)** — runtime, skills, memory, emotion
-- **[Layers](#sec-262)** — the four-layer contract in detail
-- **[Quick start](#sec-361)** — go from zero to a living embed in under 10 minutes
+- **[Layers](#sec-265)** — the four-layer contract in detail
+- **[Quick start](#sec-366)** — go from zero to a living embed in under 10 minutes
---
-<a id="sec-241"></a>
+<a id="sec-244"></a>
> **Source:** `docs/i18n.md` · [↑ table of contents](#table-of-contents)
@@ -57102,7 +57431,7 @@ clearing silently-English values out of a shipped catalog.
---
-<a id="sec-242"></a>
+<a id="sec-245"></a>
> **Source:** `docs/ibm-community-article.md` · [↑ table of contents](#table-of-contents)
@@ -57222,7 +57551,7 @@ The platform repository is public at [github.com/nirholas/three.ws](https://gith
---
-<a id="sec-243"></a>
+<a id="sec-246"></a>
> **Source:** `docs/ibm-community-blog-meetup-jessica.md` · [↑ table of contents](#table-of-contents)
@@ -57283,7 +57612,7 @@ See you Friday at 8 AM Pacific. I will be the one asking the skeptical questions
---
-<a id="sec-244"></a>
+<a id="sec-247"></a>
> **Source:** `docs/ibm-community-live-reaction-jessica.md` · [↑ table of contents](#table-of-contents)
@@ -57294,7 +57623,7 @@ This is a discussion post for the [Three.ws User Group on IBM
Community](https://community.ibm.com/community/user/usergroup?CommunityKey=e71510cc-d953-408f-9a1c-019f5c0a7016),
not a polished announcement, just my honest reaction while the day is happening. My earlier post,
[Join the Three.ws User Group's First In-World Meetup This
-Friday](#sec-243), has the event details if you have not joined yet;
+Friday](#sec-246), has the event details if you have not joined yet;
the world is still open._
I'm posting this in the middle of the day, not after, because I want the group to have my honest
@@ -57335,7 +57664,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-519) is a separate, distinct campaign and
+ `@nichxbt` X copy in [event-x-posts.md](#sec-526) 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.
@@ -57349,13 +57678,13 @@ Full recap once the day wraps.
any mentions resolve correctly.
- "Pilled" is her own word; keep it if it still feels true when she posts, or soften to "changed my
mind about it" if she wants a more IBM-official register for her own profile.
-- Once posted, add it to the catalog in [ibm-community.md](#sec-248) as a new discussion
+- Once posted, add it to the catalog in [ibm-community.md](#sec-251) as a new discussion
thread entry, following the same fields (author, posted date, activity, URL, summary) as the
existing entries, and note it links back to the pinned meetup thread.
---
-<a id="sec-245"></a>
+<a id="sec-248"></a>
> **Source:** `docs/ibm-community-recap-jessica.md` · [↑ table of contents](#table-of-contents)
@@ -57364,8 +57693,8 @@ Full recap once the day wraps.
_By Jessica Swanson, posted as a follow-up blog in the [Three.ws User Group on IBM
Community](https://community.ibm.com/community/user/usergroup?CommunityKey=e71510cc-d953-408f-9a1c-019f5c0a7016),
closing out the arc that started with [Join the Three.ws User Group's First In-World Meetup This
-Friday](#sec-243) and continued mid-day with [LIVE at the Meetup: My
-Honest Take So Far](#sec-244). Header image: reuse
+Friday](#sec-246) and continued mid-day with [LIVE at the Meetup: My
+Honest Take So Far](#sec-247). Header image: reuse
[media/ibm-x-threews-lockup.png](media/ibm-x-threews-lockup.png), or swap in a real photo from
the day once one is ready; do not paste this note into the published post._
@@ -57494,14 +57823,14 @@ closest thing to having been there, and the world itself never closes.
script; she should change anything that doesn't match how the day actually felt to her.
- Confirm how Broke Boi and bigB actually go by on IBM Community today before posting, so any
mentions or tags resolve correctly.
-- Once posted, add it to the catalog in [ibm-community.md](#sec-248) as the group's next
+- Once posted, add it to the catalog in [ibm-community.md](#sec-251) as the group's next
blog entry, following the same fields (author, published date, activity, URL, summary) as the
existing three entries, and cross-link it from the live-reaction catalog entry if that post was
published too.
---
-<a id="sec-246"></a>
+<a id="sec-249"></a>
> **Source:** `docs/ibm-community-recap-nichxbt.md` · [↑ table of contents](#table-of-contents)
@@ -57510,7 +57839,7 @@ closest thing to having been there, and the world itself never closes.
_By nich (nich8), posted as a blog entry in the [Three.ws User Group on IBM
Community](https://community.ibm.com/community/user/usergroup?CommunityKey=e71510cc-d953-408f-9a1c-019f5c0a7016),
the team's own side of the meetup recap, alongside Jessica's [live
-reaction](#sec-244) and [recap](#sec-245)
+reaction](#sec-247) and [recap](#sec-248)
on the same group. Two different people, two honest accounts of the same day; this one is mine,
written the way I wrote the [Forge walkthrough](https://community.ibm.com/community/user/discussion/type-a-sentence-get-a-3d-model-a-hands-on-walkthrough-of-the-threews-forge-user-perspective)
and the [10 features post](https://community.ibm.com/community/user/blogs/nich8/2026/07/16/threews-the-free-ai-3d-model-generators-10-best),
@@ -57649,13 +57978,13 @@ than implying a date that does not exist yet.]
[ibm-user-group-first-in-world-meetup-recap.html](../blog/ibm-user-group-first-in-world-meetup-recap.html)
is actually deployed, its link in this draft resolves live; until then it is a same-repo link that
works once shipped, not before.
-- Once posted, add it to the catalog in [ibm-community.md](#sec-248) as the group's next
+- Once posted, add it to the catalog in [ibm-community.md](#sec-251) as the group's next
blog entry, following the same fields (author, published date, activity, URL, summary) as the
existing entries, and cross-link it against Jessica's recap entry.
---
-<a id="sec-247"></a>
+<a id="sec-250"></a>
> **Source:** `docs/ibm-community-thread.md` · [↑ table of contents](#table-of-contents)
@@ -57774,13 +58103,13 @@ _Questions, skepticism, and feature requests all welcome below. The skeptical on
---
-<a id="sec-248"></a>
+<a id="sec-251"></a>
> **Source:** `docs/ibm-community.md` · [↑ table of contents](#table-of-contents)
# IBM Community: Three.ws User Group post catalog
-This is the running catalog of everything published in the [Three.ws User Group](https://community.ibm.com/community/user/groups/community-home?communitykey=e71510cc-d953-408f-9a1c-019f5c0a7016) on IBM Community: every discussion thread, every blog post, who wrote it, when, what it says, and what activity it got. It exists so the team can track the group's content without re-crawling the site. For what the group is, the framing rules that govern what gets posted there, and the wider IBM relationship, read [IBM watsonx & Granite](#sec-250) first.
+This is the running catalog of everything published in the [Three.ws User Group](https://community.ibm.com/community/user/groups/community-home?communitykey=e71510cc-d953-408f-9a1c-019f5c0a7016) on IBM Community: every discussion thread, every blog post, who wrote it, when, what it says, and what activity it got. It exists so the team can track the group's content without re-crawling the site. For what the group is, the framing rules that govern what gets posted there, and the wider IBM relationship, read [IBM watsonx & Granite](#sec-253) first.
Dates marked "approx." are derived from the site's relative timestamps ("17 days ago") on the snapshot date; blog dates come from their URLs and are exact.
@@ -57826,7 +58155,7 @@ A feature tour structured as "ten features, in the order I would demo them": (1)
- **Featured image:** the IBM x three.ws lockup ([media/ibm-x-threews-lockup.png](media/ibm-x-threews-lockup.png))
- **URL:** [community.ibm.com/.../join-the-threews-user-groups-first-in-world-meetup](https://community.ibm.com/community/user/blogs/jessica-swanson/2026/08/04/join-the-threews-user-groups-first-in-world-meetup)
-Jessica's companion piece to the meetup thread, written in her own voice as a member telling the group not to mistake the event for another webinar link. Carries the event table (Friday, August 7, 8 to 9 AM Pacific, 11 AM Eastern, free, browser only), the three-step join flow (open three.ws/play, bring a custom avatar made at three.ws/create beforehand, talk via spatial voice), and the agenda: live in-world platform tour, community demos, open Q&A ("the skeptical questions are the most useful ones"), and a first look at what is next. Her framing argument: the venue is the demo, so the hour doubles as hands-on evaluation of the technology the group exists to discuss, and since every world is a shareable URL, attending teaches you how to run your own events there. Points readers at the pinned meetup thread for the deep technical background and closes with the full platform link list. The draft lives in [ibm-community-blog-meetup-jessica.md](#sec-243).
+Jessica's companion piece to the meetup thread, written in her own voice as a member telling the group not to mistake the event for another webinar link. Carries the event table (Friday, August 7, 8 to 9 AM Pacific, 11 AM Eastern, free, browser only), the three-step join flow (open three.ws/play, bring a custom avatar made at three.ws/create beforehand, talk via spatial voice), and the agenda: live in-world platform tour, community demos, open Q&A ("the skeptical questions are the most useful ones"), and a first look at what is next. Her framing argument: the venue is the demo, so the hour doubles as hands-on evaluation of the technology the group exists to discuss, and since every world is a shareable URL, attending teaches you how to run your own events there. Points readers at the pinned meetup thread for the deep technical background and closes with the full platform link list. The draft lives in [ibm-community-blog-meetup-jessica.md](#sec-246).
### 4. The First Three.ws User Group Meetup: How It Actually Went
@@ -57877,7 +58206,7 @@ Newest first, matching the digest viewer's order.
- **Activity:** 1 reply (Jessica Swanson, whose profile lists Operational Decision Manager, AI & Data Science at IBM, 2026-08-05: links her blog post "Join the Three.ws User Group's First In-World Meetup")
- **URL:** [community.ibm.com/.../community-meetup-inside-threews-join-us-on-the-three-server-at-threewsplay](https://community.ibm.com/community/user/discussion/community-meetup-inside-threews-join-us-on-the-three-server-at-threewsplay)
-The announcement for the group's first community meetup: Friday, August 7, 2026, 8 to 9 AM Pacific (11 AM Eastern), held inside the platform itself in the $THREE home town at three.ws/play rather than on a video call. Free, browser-only, no download or account. Agenda: a live tour from inside the world, community demos, open Q&A, and a first look at what is next. Explains the three-step join flow (open /play, pick or bring an avatar, walk up and talk via spatial voice chat), then makes the venue case: every world is a URL, every pump.fun coin already has a world derived from its mint, and worlds persist, so any community can run its own meetup the same way. The back half is the long read: a surface-by-surface platform tour (creation, distribution, agent economy, developer platform including the two IBM-specific MCP servers), the technology stack (Three.js/Rapier frontend, GPU worker fleet on Cloud Run, authoritative Colyseus multiplayer at 15 Hz, Solana as home chain), the roadmap led by event infrastructure for /play, and a seven-point growth thesis explicitly framed as a thesis, not a promise. The draft lives in [ibm-community-thread.md](#sec-247).
+The announcement for the group's first community meetup: Friday, August 7, 2026, 8 to 9 AM Pacific (11 AM Eastern), held inside the platform itself in the $THREE home town at three.ws/play rather than on a video call. Free, browser-only, no download or account. Agenda: a live tour from inside the world, community demos, open Q&A, and a first look at what is next. Explains the three-step join flow (open /play, pick or bring an avatar, walk up and talk via spatial voice chat), then makes the venue case: every world is a URL, every pump.fun coin already has a world derived from its mint, and worlds persist, so any community can run its own meetup the same way. The back half is the long read: a surface-by-surface platform tour (creation, distribution, agent economy, developer platform including the two IBM-specific MCP servers), the technology stack (Three.js/Rapier frontend, GPU worker fleet on Cloud Run, authoritative Colyseus multiplayer at 15 Hz, Solana as home chain), the roadmap led by event infrastructure for /play, and a seven-point growth thesis explicitly framed as a thesis, not a promise. The draft lives in [ibm-community-thread.md](#sec-250).
### 2. Community Friday August 7,2026 - Inside three.ws: Join Us on the $THREE Server at three.ws/play
@@ -57946,11 +58275,11 @@ A first-run walkthrough of the Forge from a user's perspective, no account, wall
## Keeping this catalog current
-When a new post lands in the group, add it here in digest order with the same fields (author, date, activity, URL, faithful summary) and refresh the snapshot table's date and counts. The sources of truth are the [digest viewer](https://community.ibm.com/community/user/groups/community-home/digestviewer?communitykey=e71510cc-d953-408f-9a1c-019f5c0a7016) for threads and the [recent blogs page](https://community.ibm.com/community/user/groups/community-home/recent-community-blogs?communitykey=e71510cc-d953-408f-9a1c-019f5c0a7016) for blogs. The posting cadence and topic rules for the group itself live in the [SEO keyword plan](ops/seo-keyword-plan.md) and in [ibm.md](#sec-250).
+When a new post lands in the group, add it here in digest order with the same fields (author, date, activity, URL, faithful summary) and refresh the snapshot table's date and counts. The sources of truth are the [digest viewer](https://community.ibm.com/community/user/groups/community-home/digestviewer?communitykey=e71510cc-d953-408f-9a1c-019f5c0a7016) for threads and the [recent blogs page](https://community.ibm.com/community/user/groups/community-home/recent-community-blogs?communitykey=e71510cc-d953-408f-9a1c-019f5c0a7016) for blogs. The posting cadence and topic rules for the group itself live in the [SEO keyword plan](ops/seo-keyword-plan.md) and in [ibm.md](#sec-253).
---
-<a id="sec-249"></a>
+<a id="sec-252"></a>
> **Source:** `docs/ibm-x402-mcp.md` · [↑ table of contents](#table-of-contents)
@@ -57972,9 +58301,9 @@ bill itself, in USDC, over [x402](https://x402.org).
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-250)**.
+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-544)**.
+**[docs/x402.md](#sec-551)**.
---
@@ -58292,7 +58621,7 @@ HTTP `status`), `internal_error` (unexpected).
## Discovery (x402 Bazaar)
Each tool declares an x402 discovery extension, so the suite is browsable in the
-[x402 Bazaar](#sec-276) alongside its schema, example input, and
+[x402 Bazaar](#sec-280) alongside its schema, example input, and
example output. Agents can find Granite tools by capability and price without
knowing the server up front.
@@ -58301,7 +58630,7 @@ knowing the server up front.
## Affiliation
three.ws is an **IBM Business Partner**. This npm package is an independent,
-proprietary project built by three.ws that integrates IBM Granite via
+project built by three.ws that integrates IBM Granite via
watsonx.ai — IBM Cloud Partner Center requires third-party MCP listings to state
this, so to be precise: the package itself is **not an IBM product** and is not
operated by IBM. Granite, watsonx, and watsonx.ai are trademarks of IBM.
@@ -58313,16 +58642,16 @@ Catalog/listing copy is maintained in
## See also
-- [docs/ibm.md](#sec-250) — the full IBM Granite / watsonx integration and showcase
-- [docs/x402.md](#sec-544) — the x402 payment protocol on three.ws
-- [docs/mcp.md](#sec-277) — wiring MCP servers into a client
-- [docs/mcp-x402-bazaar.md](#sec-276) — x402 service discovery
+- [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/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
- npm: [`@three-ws/ibm-x402-mcp`](https://www.npmjs.com/package/@three-ws/ibm-x402-mcp)
---
-<a id="sec-250"></a>
+<a id="sec-253"></a>
> **Source:** `docs/ibm.md` · [↑ table of contents](#table-of-contents)
@@ -58330,7 +58659,7 @@ Catalog/listing copy is maintained in
three.ws agents can think on **IBM Granite** foundation models, served through **IBM watsonx.ai**. This page documents the whole integration for developers and operators: which Granite models run where, how the watsonx client is wired, how to configure it, and the Granite-powered API surfaces (from a Granite avatar brain to on-chain, Guardian-governed forecasts). The live IBM pages on the product are [three.ws/ibm/hello](https://three.ws/ibm/hello) (the partnership page) and [three.ws/ibm/x402-demo](https://three.ws/ibm/x402-demo) (the x402 live demo).
-For the broader platform model see [How it works](#sec-240); for the agent brain abstraction see [Agent system](#sec-064); for the standalone connector see [the MCP server](#mcp-server-three-wsibm-watsonx-mcp) below.
+For the broader platform model see [How it works](#sec-243); for the agent brain abstraction see [Agent system](#sec-064); for the standalone connector see [the MCP server](#mcp-server-three-wsibm-watsonx-mcp) below.
---
@@ -58375,7 +58704,7 @@ three.ws runs a public user group on IBM Community for developers and engineers
| Library | [Files and assets](https://community.ibm.com/community/user/groups/community-home/librarydocuments?communitykey=e71510cc-d953-408f-9a1c-019f5c0a7016&LibraryFolderKey=&DefaultView=) |
| Members | [Member list](https://community.ibm.com/community/user/groups/community-home/community-members?communitykey=e71510cc-d953-408f-9a1c-019f5c0a7016&Execute=1) |
-Every thread and blog published in the group is cataloged, with authors, dates, activity, and a faithful per-post summary, in the [IBM Community post catalog](#sec-248). Update the catalog whenever a new post lands.
+Every thread and blog published in the group is cataloged, with authors, dates, activity, and a faithful per-post summary, in the [IBM Community post catalog](#sec-251). Update the catalog whenever a new post lands.
What belongs there, and what does not, is set by the [SEO keyword plan](ops/seo-keyword-plan.md): one post per week maximum, tutorials that stand on their own for an IBM developer who never clicks through, and no crypto-cluster content (that goes on [three.ws/blog](https://three.ws/blog) instead). The user group is also linked from the site's [Community page](https://three.ws/community) and the global footer.
@@ -58623,7 +58952,7 @@ Source: [`packages/ibm-watsonx-mcp`](../packages/ibm-watsonx-mcp). Five tools:
WATSONX_API_KEY=… WATSONX_PROJECT_ID=… npx @three-ws/ibm-watsonx-mcp
```
-It reads the same `WATSONX_*` environment variables documented above. See the [MCP guide](#sec-277) for wiring MCP servers into a client.
+It reads the same `WATSONX_*` environment variables documented above. See the [MCP guide](#sec-281) for wiring MCP servers into a client.
---
@@ -58670,16 +58999,16 @@ Unit tests for the same paths live in [`tests/`](../tests) (`granite-oracle`, `a
## See also
-- [How it works](#sec-240) — the platform mental model
+- [How it works](#sec-243) — the platform mental model
- [Agent system](#sec-064) — the brain abstraction Granite plugs into
-- [IBM Granite x402 MCP](#sec-249) — pay-per-call Granite for agents (USDC, no IBM account)
-- [MCP](#sec-277) — wiring MCP servers into a client
+- [IBM Granite x402 MCP](#sec-252) — pay-per-call Granite for agents (USDC, no IBM account)
+- [MCP](#sec-281) — wiring MCP servers into a client
- [REST API](#sec-096) — the full endpoint reference
-- [Configuration](#sec-153) — all environment variables
+- [Configuration](#sec-154) — all environment variables
---
-<a id="sec-251"></a>
+<a id="sec-254"></a>
> **Source:** `docs/image-to-3d.md` · [↑ table of contents](#table-of-contents)
@@ -58774,14 +59103,14 @@ console.log(job.glb_url);
## Related
-- [Forge](#sec-225) is the full text-and-image-to-3D surface with every mode and engine.
+- [Forge](#sec-228) is the full text-and-image-to-3D surface with every mode and engine.
- [Avatar reconstruction](#sec-114) and [avatar creation](#sec-109) cover the face-to-avatar pipeline behind [/create/selfie](https://three.ws/create/selfie).
- The pipeline internals: [3D asset pipeline](#sec-002), [3D pipeline](#sec-003), [3D API](#sec-001).
- Pages: [/create](https://three.ws/create), [/scene](https://three.ws/scene) (Scene Studio), [/gallery](https://three.ws/gallery).
---
-<a id="sec-252"></a>
+<a id="sec-255"></a>
> **Source:** `docs/in-game-economy.md` · [↑ table of contents](#table-of-contents)
@@ -58910,11 +59239,11 @@ 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-544) and is surfaced publicly at [/fits](https://three.ws/fits).
+[x402](#sec-551) 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
-boutique deliberately cannot see: **[event souvenirs](#sec-216)** are
+boutique deliberately cannot see: **[event souvenirs](#sec-218)** are
granted to everyone present in the world during a live event and are never sold,
before, during, or after. They carry no price, so the boutique's listing filter
(`tier === 'premium'` **and** `price > 0`) excludes them by construction, and the
@@ -59040,7 +59369,7 @@ every number in this system.
## Next
-- **[Earn and spend in /play](#sec-435)** walks the
+- **[Earn and spend in /play](#sec-441)** walks the
whole loop end to end, from your first gathered log to a cosmetic unlock.
- **[three.ws/play/economy](https://three.ws/play/economy)** is the live reference
with the current catalogs and odds.
@@ -59049,7 +59378,7 @@ every number in this system.
---
-<a id="sec-253"></a>
+<a id="sec-256"></a>
> **Source:** `docs/inference-node-operator.md` · [↑ table of contents](#table-of-contents)
@@ -59323,7 +59652,7 @@ signature, and the artifact hash all check out.
---
-<a id="sec-254"></a>
+<a id="sec-257"></a>
> **Source:** `docs/integrations.md` · [↑ table of contents](#table-of-contents)
@@ -59343,7 +59672,7 @@ The platform's agents are only as useful as the places they can appear. Integrat
is the distribution layer: it turns an agent, a saved widget, or a live token feed
into something a marketer can paste into a CMS, a developer can wire into a framework,
or an AI assistant can call as a tool. It is the front page of embedding; the deep
-per-method references live in [Embedding](#sec-186) and [Widgets](#sec-511),
+per-method references live in [Embedding](#sec-188) and [Widgets](#sec-517),
and this doc is the map that points you to the right one.
## How it works
@@ -59369,7 +59698,7 @@ The catalog covers six integration types:
driven by a `data-widget` id and the `pumpfun-feed` type.
- **MCP Integration**: the `@three-ws/avatar-agent` server (from the
`packages/avatar-agent-mcp` workspace), so Claude, Cursor, or any MCP-compatible
- assistant can render, speak, gesture, and emote your agents. See [MCP](#sec-277).
+ assistant can render, speak, gesture, and emote your agents. See [MCP](#sec-281).
## Walkthrough
@@ -59487,15 +59816,15 @@ for the full table.
## Related
-- [Embedding Guide](#sec-186): the full per-method reference (web component, iframe, oEmbed)
-- [Widget Types](#sec-511): every widget type and how to configure one
-- [Embody](#sec-187): giving an agent a body in more contexts
-- [MCP](#sec-277): the avatar MCP server for AI assistants
+- [Embedding Guide](#sec-188): the full per-method reference (web component, iframe, oEmbed)
+- [Widget Types](#sec-517): every widget type and how to configure one
+- [Embody](#sec-189): giving an agent a body in more contexts
+- [MCP](#sec-281): the avatar MCP server for AI assistants
- Pages: [/integrations](https://three.ws/integrations), [/widgets](https://three.ws/widgets)
---
-<a id="sec-255"></a>
+<a id="sec-258"></a>
> **Source:** `docs/introduction.md` · [↑ table of contents](#table-of-contents)
@@ -59509,7 +59838,7 @@ The result is an agent that doesn't just respond in a chat box. It occupies a th
**Key facts:**
-- **License:** proprietary, all rights reserved (see [LICENSE](https://github.com/nirholas/three.ws/blob/main/LICENSE))
+- **License:** open source, [Apache 2.0](https://github.com/nirholas/three.ws/blob/main/LICENSE)
- **Hosted platform:** [https://three.ws](https://three.ws)
- **CDN bundle:** `https://three.ws/agent-3d/latest/agent-3d.js` (also pinnable to a version, e.g. `/agent-3d/1.5.2/agent-3d.js`)
- **npm packages:** [`@three-ws/sdk`](https://www.npmjs.com/package/@three-ws/sdk), [`@three-ws/agent-ui`](https://www.npmjs.com/package/@three-ws/agent-ui), [`@three-ws/avatar`](https://www.npmjs.com/package/@three-ws/avatar), [`@three-ws/solana-agent`](https://www.npmjs.com/package/@three-ws/solana-agent), [`@three-ws/mcp-server`](https://www.npmjs.com/package/@three-ws/mcp-server)
@@ -59548,7 +59877,7 @@ For developers who don't need any of this, on-chain identity is entirely optiona
### Open
-The source is readable and the formats are open, but the code is proprietary: see [LICENSE](https://github.com/nirholas/three.ws/blob/main/LICENSE) for what is permitted, and ask before self-hosting or redistributing. The manifest format, embed protocol, and agent spec are all documented in the `/specs` directory of the repository, and building against those specs needs no permission.
+The code is open source under the [Apache License 2.0](https://github.com/nirholas/three.ws/blob/main/LICENSE): use it, modify it, self-host it, redistribute it, and build commercial products on it, including closed-source ones, as long as you keep the license and attribution notices and state what you changed. The manifest format, embed protocol, and agent spec are all documented in the `/specs` directory of the repository.
---
@@ -59706,7 +60035,7 @@ To add an AI brain:
The `key-proxy` attribute points to a serverless function that injects your API key — the key never touches the client. The `voice` attribute enables microphone input and TTS output.
-For a full step-by-step walkthrough, see the [Quick Start guide](#sec-361).
+For a full step-by-step walkthrough, see the [Quick Start guide](#sec-366).
---
@@ -59714,19 +60043,19 @@ For a full step-by-step walkthrough, see the [Quick Start guide](#sec-361).
Once you have the basics working, the following guides go deeper:
-- **[Quick Start](#sec-361)** — step-by-step from zero to a talking agent
-- **[Embedding Guide](#sec-186)** — all attributes, modes, events, and the JS API
-- **[Widget Types](#sec-511)**, the five general-purpose widgets in depth (the other five live in [Widget Studio](https://three.ws/studio))
+- **[Quick Start](#sec-366)** — step-by-step from zero to a talking agent
+- **[Embedding Guide](#sec-188)** — all attributes, modes, events, and the JS API
+- **[Widget Types](#sec-517)**, the five general-purpose widgets in depth (the other five live in [Widget Studio](https://three.ws/studio))
- **[Agent System Overview](#sec-064)** — runtime, skill registry, memory, emotion system
- **[Manifest Reference](#sec-055)** — full JSON schema with examples
-- **[REST API](#sec-096)** and **[JavaScript API](#sec-258)** — backend and in-browser surfaces
+- **[REST API](#sec-096)** and **[JavaScript API](#sec-261)** — backend and in-browser surfaces
- **[Agents vs. avatars](#sec-073)** — the difference, and when to care
If you want to look at what's already in the hosted platform — browsing agents, using Widget Studio, or registering on-chain — visit [https://three.ws](https://three.ws).
---
-<a id="sec-256"></a>
+<a id="sec-259"></a>
> **Source:** `docs/irl.md` · [↑ table of contents](#table-of-contents)
@@ -59849,7 +60178,7 @@ The rollup is served at `GET /api/irl/analytics` (admin-gated via `x-ops-secret`
---
-<a id="sec-257"></a>
+<a id="sec-260"></a>
> **Source:** `docs/irl/THREAT-MODEL.md` · [↑ table of contents](#table-of-contents)
@@ -60003,15 +60332,15 @@ in a way that drops legitimate discovery, update this file in the same change.
---
-<a id="sec-258"></a>
+<a id="sec-261"></a>
> **Source:** `docs/js-api.md` · [↑ table of contents](#table-of-contents)
# JavaScript API Reference
-This page documents the internal JavaScript classes behind the three.ws viewer: the `App` controller, the Three.js `Viewer`, the glTF `Validator`, and the small components that render around them. It is aimed at developers reading or extending the source (`src/`), and at anyone driving the viewer from the browser console via `window.VIEWER`. If you just want a 3D agent on your page, use the [`<agent-3d>` element](#sec-508) instead.
+This page documents the internal JavaScript classes behind the three.ws viewer: the `App` controller, the Three.js `Viewer`, the glTF `Validator`, and the small components that render around them. It is aimed at developers reading or extending the source (`src/`), and at anyone driving the viewer from the browser console via `window.VIEWER`. If you just want a 3D agent on your page, use the [`<agent-3d>` element](#sec-514) instead.
-> For the HTTP/REST surface, see [api-reference.md](#sec-096). For the high-level npm SDK, see [sdk.md](#sec-374). For the `<agent-3d>` element attributes, see [web-component.md](#sec-508).
+> For the HTTP/REST surface, see [api-reference.md](#sec-096). For the high-level npm SDK, see [sdk.md](#sec-379). For the `<agent-3d>` element attributes, see [web-component.md](#sec-514).
---
@@ -60637,7 +60966,7 @@ window.VIEWER.app.viewer.updateDisplay();
---
-<a id="sec-259"></a>
+<a id="sec-262"></a>
> **Source:** `docs/kol-tracker.md` · [↑ table of contents](#table-of-contents)
@@ -60773,8 +61102,8 @@ Writes the curated tracked-wallet list that the tracker merges in. Accepts `{ ra
The tracker answers "who is making money"; the reputation surfaces answer "should this wallet's record earn trust". They meet at the wallet address:
- **`GET /api/intel/wallet/<WALLET_ADDRESS>`** returns one wallet's realized track record from the Smart-Money graph: a 0 to 100 realized score, win rate, average ATH multiple, winners and losers, labels (`smart_money`, `sybil`, `fresh`, and others), and its funder cluster. `computed: false` means no track record exists yet for that address; that is an honest zero, not an error. A string that is not a base58 Solana address is a different case and returns `400 bad_request`, so a typo never reads as a wallet with no history. Any wallet you see on the tracker can be fed straight into it. The same card is served by `GET /api/intel/smart-money?wallet=<WALLET_ADDRESS>`, which applies the identical validation.
-- **[Smart Money Radar](#sec-389)** is the sibling leaderboard built from graduation outcomes rather than a KOL universe: reputation earned per wallet from which coins actually graduated. The tracker's footer links to it, and the two boards frequently disagree in instructive ways.
-- **[Trust primitives](#sec-417)** wrap the same question for autonomous agents: a paid endpoint that scores any counterparty wallet from real on-chain evidence before an agent transacts with it.
+- **[Smart Money Radar](#sec-394)** is the sibling leaderboard built from graduation outcomes rather than a KOL universe: reputation earned per wallet from which coins actually graduated. The tracker's footer links to it, and the two boards frequently disagree in instructive ways.
+- **[Trust primitives](#sec-423)** wrap the same question for autonomous agents: a paid endpoint that scores any counterparty wallet from real on-chain evidence before an agent transacts with it.
```bash
# Take a wallet from the tracker and pull its reputation record
@@ -60792,13 +61121,13 @@ curl 'https://three.ws/api/intel/wallet/<WALLET_ADDRESS>?network=mainnet'
## Related
-- [Smart Money Radar](#sec-389): reputation earned from graduation outcomes, wallet by wallet
-- [Trust primitives](#sec-417): the paid cross-chain reputation read for autonomous agents
+- [Smart Money Radar](#sec-394): reputation earned from graduation outcomes, wallet by wallet
+- [Trust primitives](#sec-423): the paid cross-chain reputation read for autonomous agents
- Pages: [/tracker](https://three.ws/tracker) · [/smart-money](https://three.ws/smart-money) · [/leaderboard](https://three.ws/leaderboard)
---
-<a id="sec-260"></a>
+<a id="sec-263"></a>
> **Source:** `docs/labor-market.md` · [↑ table of contents](#table-of-contents)
@@ -60933,7 +61262,7 @@ economy move:
---
-<a id="sec-261"></a>
+<a id="sec-264"></a>
> **Source:** `docs/launch-usecases.md` · [↑ table of contents](#table-of-contents)
@@ -61069,7 +61398,7 @@ GET /api/pump/launch-studio?action=preview&id=github-fresh-breakouts&limit=6
---
-<a id="sec-262"></a>
+<a id="sec-265"></a>
> **Source:** `docs/layers.md` · [↑ table of contents](#table-of-contents)
@@ -61077,7 +61406,7 @@ GET /api/pump/launch-studio?action=preview&id=github-fresh-breakouts&limit=6
three.ws is split into four horizontal layers. Each layer can be used on its own. Each layer is independently replaceable as long as its contract with the rest of the system holds. This document describes what each layer owns, what it exports, and where to extend it.
-For the overall request flow, see [How three.ws works](#sec-240). For internal module names and paths, see [Architecture overview](#sec-100).
+For the overall request flow, see [How three.ws works](#sec-243). For internal module names and paths, see [Architecture overview](#sec-100).
---
@@ -61167,10 +61496,10 @@ Modules:
- **`agent-identity.js`** — the passport + diary. Stable agent ID, owner address, signed action history. Backed by `localStorage` (cache) and `/api/agents/<id>` (canonical). Listens on the protocol bus and POSTs `speak` / `skill-done` / `validate` / `sign` events to `/api/agent-actions`.
- **`memory/`** — `local`, `ipfs`, `encrypted-ipfs`, or `none`. Declared on the manifest.
- **`erc8004/`** — on-chain registries. `IdentityRegistry` (mints agent token with `tokenURI`), `ReputationRegistry` (signed feedback), `ValidationRegistry` (validation report hashes). Per-chain addresses in `erc8004/abi.js`.
-- **`erc8004/solana-deploy.js`**: Solana counterpart. Metaplex Core asset mint; SPL Memo attestations and reputation live server-side (see [Agent Reputation on Solana](#sec-393)).
+- **`erc8004/solana-deploy.js`**: Solana counterpart. Metaplex Core asset mint; SPL Memo attestations and reputation live server-side (see [Agent Reputation on Solana](#sec-398)).
- **`auth/` + `wallet/`** — SIWE / SIWS for backend mutations; Privy for email/social → embedded wallet onboarding; session cookies after wallet proof.
-Per-chain registry addresses, ABIs, and helpers ship as `@three-ws/sdk`. ENS attestations are also handled here — see [register-onchain.md](#sec-462).
+Per-chain registry addresses, ABIs, and helpers ship as `@three-ws/sdk`. ENS attestations are also handled here — see [register-onchain.md](#sec-468).
---
@@ -61183,7 +61512,7 @@ Per-chain registry addresses, ABIs, and helpers ship as `@three-ws/sdk`. ENS att
Modules:
- **`element.js`**: `<agent-3d>` custom element. Lazy-boots via `IntersectionObserver` (unless `eager`). Enforces origin allowlist. Exposes attributes for `body`, `brain`, `agent-id`, `manifest`, `mode` (`inline` / `floating` / `section` / `fullscreen`), `voice`, and more. Public methods: `say()`, `ask()`, `installSkill()`, `expressEmotion()`, `play()`, `lookAt()`, `pause()`, `destroy()`.
-- **`stage-element.js`**: `<agent-stage>` for hosting multiple agents in one shared scene. See [multi-agent.md](#sec-290).
+- **`stage-element.js`**: `<agent-stage>` for hosting multiple agents in one shared scene. See [multi-agent.md](#sec-294).
- **`widget-types.js`**: the ten widget variants: Turntable, Animation Gallery, Talking Agent, ERC-8004 Passport, Hotspot Tour, Pump.fun Live Feed, Smart Money Feed, Live Trades Canvas, Bonding Curve, Walking Avatar.
- **`lib.js`** — the CDN entry. Imports the element, registers it, re-exports the public surface (`defineElement`, `Agent3DElement`, `AgentStageElement`, helpers).
- **`embed-action-bridge.js`** — the `postMessage` protocol. Iframe widgets and the web component speak the same dialect, so host pages can drive either with the same code.
@@ -61226,12 +61555,12 @@ Versioned CDN bundles are published at `/agent-3d/<version>/agent-3d.js`. Use `l
- **[Architecture overview](#sec-100)** — module-by-module deep dive
- **[Agent system](#sec-064)** — runtime, skills, memory in detail
-- **[Embedding](#sec-186)** — the public face of the embed layer
-- **[SDK reference](#sec-374)** — `@three-ws/sdk` and friends
+- **[Embedding](#sec-188)** — the public face of the embed layer
+- **[SDK reference](#sec-379)** — `@three-ws/sdk` and friends
---
-<a id="sec-263"></a>
+<a id="sec-266"></a>
> **Source:** `docs/likeness-eval.md` · [↑ table of contents](#table-of-contents)
@@ -61471,7 +61800,7 @@ and reason only.
## Related
-- [Selfie to avatar](#sec-377): the capture flow being measured
+- [Selfie to avatar](#sec-382): the capture flow being measured
- [Avatar fidelity program](#sec-111): the tracks this
metric scores
- [Realism quality bench](../data/quality-bench/README.md): the sibling harness
@@ -61480,7 +61809,7 @@ and reason only.
---
-<a id="sec-264"></a>
+<a id="sec-267"></a>
> **Source:** `docs/lipsync.md` · [↑ table of contents](#table-of-contents)
@@ -61575,15 +61904,239 @@ tick();
## Related
-- [Voice Lab](#sec-506): clone a voice and synthesize it, the audio these demos animate.
-- [Voice and lipsync tutorial](#sec-481): the full walkthrough, including wiring visemes to an agent body.
-- [Talking Avatar Video](#sec-403): the server-rendered alternative for exporting a talking-head clip.
+- [Voice Lab](#sec-512): clone a voice and synthesize it, the audio these demos animate.
+- [Voice and lipsync tutorial](#sec-487): the full walkthrough, including wiring visemes to an agent body.
+- [Talking Avatar Video](#sec-408): the server-rendered alternative for exporting a talking-head clip.
- [Animations](#sec-093): the runtime clip registry that plays alongside lipsync.
- Pages: [/lipsync](https://three.ws/lipsync), [/lipsync/mic](https://three.ws/lipsync/mic).
---
-<a id="sec-265"></a>
+<a id="sec-268"></a>
+
+> **Source:** `docs/liquid-glass.md` · [↑ table of contents](#table-of-contents)
+
+# Liquid glass: the visual target for three.ws grids and panels
+
+The look we are building toward is the one on
+[infinite-liquid-glass.shader.se](https://infinite-liquid-glass.shader.se/?v=2), a WebGPU
+experiment by [Shader](https://shader.se) (Simon Hedlund and Filip Kantedal, Sweden). This
+document is the design brief for that direction: what the reference actually is, which parts
+of it we adopt, the material and type recipe that produces it, the open source we build on,
+and the budget it has to stay inside.
+
+It sits under [Design tokens](#sec-004), which stays the source of truth for colour,
+type, radius, blur, and motion values. Nothing here introduces a value the token file does not
+have. Interaction primitives come from [ui-juice](#sec-493).
+
+## What the reference is
+
+An infinite, drag-and-scroll plane of rounded-square tiles. Each tile is a live media card
+(video or image) sitting *behind* a thick slab of refractive glass, so the content bends at the
+tile edge, picks up a bright specular rim along the top-left, and smears into a slight rainbow
+fringe where the curvature is steepest. Over that: a large display-weight title
+("Infinite City", "Glass House", "Common Sky"), a one-line subtitle at low opacity, and a
+monospaced eyebrow across the top edge (`ILG-05 SPATIAL IDENTITY SELECTED WORK 2026`). The
+background is near-black. Nothing is flat, and nothing is loud.
+
+Four things carry the whole effect, in order of importance:
+
+1. **Real refraction, not blur.** The content behind a tile is displaced, not just frosted.
+ A `backdrop-filter: blur()` panel is the thing this look is not.
+2. **The edge does the work.** The interior of a tile is almost clear. The last 8 to 12 percent
+ of the width is where the bend, the rim light, and the colour fringe live.
+3. **Squircle geometry.** Continuous rounded corners, radius roughly 12 percent of the tile's
+ short side, never a small 8px radius and never a full pill.
+4. **Type sits on top, unrefracted.** Titles stay crisp and legible over the moving glass. They
+ are not part of the material.
+
+## Is there a repo for it?
+
+**Not for that demo.** It ships as a Turbopack/Next.js build on Vercel with no repository link,
+no license, and no credits beyond the studio logo and a booking link. The bundle is minified
+first-party code. What the bundle does tell us is the stack: `@react-three/fiber` plus drei,
+three.js `WebGPURenderer`, and `MeshPhysicalNodeMaterial` driven by `transmission`, `thickness`,
+`ior`, `dispersion`, `iridescence`, `anisotropy`, and `roughness`. Shader's own site pipeline is
+written up in detail on Codrops
+([80s Business Tech and Seamless Scene Transitions](https://tympanus.net/codrops/2026/05/19/80s-business-tech-seamless-scene-transitions-inside-shader-ses-scroll-driven-webgpu-pipeline/)),
+and that article says an open source example is planned. It had not been published as of
+2026-08-21.
+
+So we rebuild the look from open source. These are the repositories worth reading, checked on
+2026-08-21:
+
+| Repo | Stars | License | What it gives us |
+|------|-------|---------|------------------|
+| [iyinchao/liquid-glass-studio](https://github.com/iyinchao/liquid-glass-studio) | 607 | MIT | The closest single-panel implementation, WebGL2 and WebGPU, with every knob (refraction strength, edge falloff, chromatic aberration, specular) exposed live. Read this first for the edge math. |
+| [Yousuf-developer/liquid-glass-carousel](https://github.com/Yousuf-developer/liquid-glass-carousel) | 130 | MIT | Structurally the nearest match: an infinite scroll-driven grid of media tiles under a glass lens, three.js plus GSAP. This is the layout half of the reference. |
+| [shuding/liquid-glass](https://github.com/shuding/liquid-glass) | 1.1k | MIT | DOM-only, SVG `feDisplacementMap`. No WebGL context, so it is the cheap lane for UI chrome on pages that have no canvas. |
+| [rdev/liquid-glass-react](https://github.com/rdev/liquid-glass-react) | 6.0k | MIT | The same DOM technique packaged for React. Reference only; we do not ship React on these surfaces. |
+| [mrdoob/three.js](https://github.com/mrdoob/three.js) transmission examples | | MIT | `webgpu_materials_transmission` and the `MeshPhysicalMaterial` transmission examples are the canonical parameter set, and they match the three.js version we already bundle. |
+
+[ybouane/liquidglass](https://github.com/ybouane/liquidglass) (401 stars) is a good WebGL
+implementation with **no declared license**. Read it for ideas, never vendor it.
+
+## What we adopt, in two lanes
+
+The reference is one technique. On three.ws it splits in two, because most of our surfaces have
+no 3D canvas and must not gain one for decoration.
+
+### Lane A: DOM glass, for chrome
+
+Panels, docks, modals, cards, nav. Pure CSS, no WebGL, already tokenised in
+[`public/tokens.css`](../public/tokens.css):
+
+```css
+.glass-panel {
+ background: var(--surface-glass);
+ backdrop-filter: blur(var(--blur-md)) saturate(1.25);
+ border: 1px solid var(--surface-3);
+ border-radius: var(--radius-lg);
+ box-shadow: inset 0 1px 0 rgba(255, 255, 255, 0.14), var(--shadow-2);
+}
+```
+
+That `inset 0 1px 0` highlight is the cheapest 80 percent of the look: it is the rim light the
+reference gets from real refraction. A DOM panel without it reads as frosted plastic. Blur tier
+by role: `--blur-sm` for inline chips, `--blur-md` for panels and docks, `--blur-lg` for
+full-screen scrims. Never invent a fourth value.
+
+For a DOM surface that genuinely needs displacement rather than blur (a hero tile, a featured
+card), the SVG `feDisplacementMap` technique from `shuding/liquid-glass` is the approved
+escalation. It costs no GPU context and degrades to the blur above when filters are
+unsupported.
+
+### Lane B: canvas glass, for tiles
+
+Surfaces that already run three.js (`/gallery`, the entity studio stage, Restyle Studio, Scene
+Composer) get the real thing. We are on three.js r184, so every parameter the reference uses is
+available on `MeshPhysicalMaterial` under WebGL2. **WebGPU is not a prerequisite.** Do not port
+a renderer to chase this look.
+
+<!-- live:off -->
+```js
+import * as THREE from 'three';
+import { RoomEnvironment } from 'three/addons/environments/RoomEnvironment.js';
+
+// Image-based lighting is not optional: transmissive glass with nothing to
+// reflect renders as grey soup. Restyle Studio lights its stage the same way.
+const pmrem = new THREE.PMREMGenerator(renderer);
+scene.environment = pmrem.fromScene(new RoomEnvironment(), 0.04).texture;
+
+const glass = new THREE.MeshPhysicalMaterial({
+ transmission: 1, // fully refractive, not alpha-blended
+ thickness: 0.35, // slab depth in world units; drives how far light bends
+ ior: 1.47, // window glass sits at 1.5; slightly under reads softer
+ roughness: 0.08, // above ~0.15 the content behind turns to mush
+ dispersion: 3.5, // rainbow fringe at the edges; useful range is 0 to 10
+ iridescence: 0.12, // faint oil-slick sheen on the rim
+ iridescenceIOR: 1.3,
+ clearcoat: 1, // the hard specular streak along the top-left edge
+ clearcoatRoughness: 0.04,
+ specularIntensity: 1,
+ color: 0xffffff,
+ attenuationColor: new THREE.Color(0xdfe7ff),
+ attenuationDistance: 2.5, // very slight cool tint through the body
+});
+
+// One material instance, reused by every tile. Each unique transmissive
+// material costs its own render pass.
+const tile = new THREE.Mesh(squircleGeometry(1, 1, 0.12), glass);
+```
+
+Rules for this lane:
+
+- **One shared material for the whole grid.** Transmission renders the scene into an offscreen
+ target; per-tile materials multiply that cost linearly.
+- **Scale the transmission buffer, do not cap the canvas.** `renderer.transmissionResolutionScale
+ = 0.5` halves the most expensive pass and is invisible at tile scale. Drop to `0.35` on the
+ mobile tier.
+- **Media goes behind the glass, never inside it.** The video or image plane is a separate mesh
+ sitting a few centimetres behind the slab. That gap is what produces parallax as the grid moves.
+- **Type is DOM or an unlit overlay plane**, positioned over the tile. Refracted text is
+ illegible, and the reference does not refract it either.
+
+### The squircle
+
+Corner radius is 12 percent of the tile's short side in both lanes, which keeps a DOM card and a
+3D tile reading as the same object. In CSS that is `border-radius: clamp(14px, 12%, 34px)`. In
+three.js, build the profile with `THREE.Shape` and `absarc` corners, then `ExtrudeGeometry` with
+`bevelEnabled: true`, `bevelSize` about 4 percent of the short side. The bevel is not cosmetic:
+it is the surface that catches the rim light.
+
+## Type and layout over glass
+
+| Element | Token | Notes |
+|---------|-------|-------|
+| Tile title | `--font-display`, `--text-2xl`, `--weight-bold`, `--leading-tight` | Pure white, tight negative tracking, sits low-left in the tile. Large enough that the glass beneath reads as texture, not noise. |
+| Subtitle | `--font-body`, `--text-md` | One line, opacity 0.62, never wraps to three lines. |
+| Eyebrow | `--font-mono`, `--text-2xs`, uppercase, letter-spacing 0.18em | Top edge, split left and right (`ILG-05 SPATIAL IDENTITY` / `SELECTED WORK 2026`). This is the detail that makes the grid read as a catalogue rather than a moodboard. |
+| Background | `--bg-0` | Near-black. Glass needs darkness to have anything to bend. |
+
+Contrast is checked against the *brightest* frame of the media behind the tile, not the average.
+Where a title cannot clear 4.5:1 across the whole clip, add a bottom-anchored scrim
+(`linear-gradient(transparent, rgba(0,0,0,0.55))`) inside the tile rather than dimming the media.
+
+## Motion
+
+The reference moves constantly and never bounces. Pointer drag and wheel both feed one velocity
+value that is damped toward zero, tiles wrap modulo the grid extent, and nothing snaps. Use the
+motion ladder from the token file (`--duration-*`, `--ease-*`) for anything with a fixed
+duration, and a frame-rate-independent damp for the continuous scroll:
+
+```js
+// Frame-rate independent damping. lambda ~6 feels like the reference.
+const damp = (current, target, lambda, dt) => current + (target - current) * (1 - Math.exp(-lambda * dt));
+```
+
+Under `prefers-reduced-motion: reduce` the plane stops drifting entirely and becomes a static
+paginated grid. The glass stays; only the motion goes. Token durations already zero themselves
+in that media query, so anything built on `--duration-*` handles this for free.
+
+## Budget
+
+This look is expensive and it is not allowed to cost us the product.
+
+- **Frame budget:** 16.6ms on a 2021 laptop with the grid at full viewport. If the transmission
+ pass cannot fit, cut `transmissionResolutionScale` before cutting tile count.
+- **Mobile and low-power:** below the mobile tier, or when
+ `navigator.hardwareConcurrency <= 4`, the canvas lane falls back to Lane A: the same layout,
+ the same type, DOM glass over a still poster frame. Designed fallback, not a blank grid.
+- **No WebGL context on a page that did not already have one.** A marketing section does not get
+ a renderer for decoration.
+- **Media pauses off-screen.** Videos behind tiles outside the viewport are paused, exactly as the
+ scroll-driven pipeline in the Codrops write-up skips render passes for off-screen sections.
+
+## Where this lands first
+
+1. `/gallery` (avatar grid) is the closest structural match to the reference and the first target.
+2. [`/marketplace`](https://three.ws/marketplace) and [`/discover`](https://three.ws/discover)
+ cards adopt Lane A now, since neither runs a canvas grid today.
+3. The entity studio stage panels adopt the Lane A rim-light rule immediately; it is a one-line
+ change per panel and it is most of the perceived quality.
+
+## Verify before calling a glass surface done
+
+- The interior of a tile is nearly clear and the *edge* carries the effect. If the whole tile is
+ frosted, it is blur, not glass, and it is wrong.
+- Every panel has the `inset 0 1px 0` rim highlight.
+- Radius is 12 percent of the short side, in both lanes, on every tile.
+- Title clears 4.5:1 against the brightest frame behind it.
+- `prefers-reduced-motion: reduce` leaves a static grid with no drift.
+- The transmission pass is measured, not assumed: profile it in DevTools with the grid full-screen.
+- No raw hex, rgba, or px font size that a token in [`public/tokens.css`](../public/tokens.css)
+ already provides.
+
+## Related
+
+- [Design tokens](#sec-004), the values every rule above resolves to.
+- [ui-juice](#sec-493), the shared interaction primitives (damping, reduced-motion contract).
+- [Restyle Studio](#sec-373), which already ships a `realGlass` transmissive preset and the
+ `RoomEnvironment` lighting setup this document depends on.
+
+---
+
+<a id="sec-269"></a>
> **Source:** `docs/listings.md` · [↑ table of contents](#table-of-contents)
@@ -61616,7 +62169,7 @@ Infrastructure programs that back three.ws with credits, tooling, and founder ne
|---|---|---|
| **Quicknode** Startup Program | Accepted (2026-07) | three.ws is accepted into the Quicknode Startup Program and approved for free infrastructure credits. Quicknode's globally distributed RPC endpoints (Solana first, plus the EVM chains x402 settles on) add capacity and redundancy behind agent wallets, settlement verification, and live market data. Announcement: [three.ws Joins the Quicknode Startup Program](/blog/three-ws-quicknode-startup-program). |
| **Google Cloud** for Web3 Startups | Member | Production runs on Google Cloud Run; the program backs compute and Vertex AI usage. Announcement: [three.ws Joins Google Cloud for Web3 Startups](/blog/three-ws-google-cloud-partnership). |
-| **NVIDIA Inception** | Member (2026-07) | NVIDIA's program for startups building on accelerated computing. Every generation lane runs on NVIDIA: a self-hosted Cloud Run GPU fleet (L4 plus one RTX PRO 6000 Blackwell) behind text-to-3D, rigging, and motion, and a free hosted lane behind chat, vision, embeddings, safety, and speech. Surface: [/nvidia](/nvidia). Docs: [NVIDIA Inception](#sec-296), [NVIDIA models](#sec-297). Membership is a startup program, not a partnership, an investment, or an endorsement. |
+| **NVIDIA Inception** | Member (2026-07) | NVIDIA's program for startups building on accelerated computing. Every generation lane runs on NVIDIA: a self-hosted Cloud Run GPU fleet (L4 plus one RTX PRO 6000 Blackwell) behind text-to-3D, rigging, and motion, and a free hosted lane behind chat, vision, embeddings, safety, and speech. Surface: [/nvidia](/nvidia). Docs: [NVIDIA Inception](#sec-300), [NVIDIA models](#sec-301). Membership is a startup program, not a partnership, an investment, or an endorsement. |
---
@@ -61628,7 +62181,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-544).
+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).
---
@@ -61638,9 +62191,9 @@ The discovery surfaces owned by the AI platforms themselves, where an MCP server
| Directory | Status | Listing details |
|---|---|---|
-| **OpenAI** Plugin Directory (ChatGPT + Codex) | Open to submission | The universal directory shared by ChatGPT and Codex since 2026-07-09, superseding the former App directory. three.ws already meets the gating requirement: a public OAuth 2.1 MCP server at `https://three.ws/api/mcp` ([mcp.md](#sec-277)). Full submission kit, prerequisites, and rejection criteria: [openai-listing-channels.md](#sec-305). |
-| **OpenAI** Showcase Gallery | Open to submission | Editorial feature on openai.com for apps, demos, and open-source projects built with OpenAI models, APIs, or Codex. Open web form, no repo gate. See [openai-listing-channels.md](#sec-305). |
-| **OpenAI** Cookbook | Submitted, not merged | [PR #2874](https://github.com/openai/openai-cookbook/pull/2874) (a self-correcting 3D collectible pipeline using text-to-3D, function calling, and vision) has been open since 2026-07-21. Root-cause analysis and the revival steps are in [openai-listing-channels.md](#sec-305). |
+| **OpenAI** Plugin Directory (ChatGPT + Codex) | Open to submission | The universal directory shared by ChatGPT and Codex since 2026-07-09, superseding the former App directory. three.ws already meets the gating requirement: a public OAuth 2.1 MCP server at `https://three.ws/api/mcp` ([mcp.md](#sec-281)). Full submission kit, prerequisites, and rejection criteria: [openai-listing-channels.md](#sec-310). |
+| **OpenAI** Showcase Gallery | Open to submission | Editorial feature on openai.com for apps, demos, and open-source projects built with OpenAI models, APIs, or Codex. Open web form, no repo gate. See [openai-listing-channels.md](#sec-310). |
+| **OpenAI** Cookbook | Submitted, not merged | [PR #2874](https://github.com/openai/openai-cookbook/pull/2874) (a self-correcting 3D collectible pipeline using text-to-3D, function calling, and vision) has been open since 2026-07-21. Root-cause analysis and the revival steps are in [openai-listing-channels.md](#sec-310). |
---
@@ -61688,7 +62241,7 @@ Subscribe via RSS to track new listings, integrations, and protocol updates.
---
-<a id="sec-266"></a>
+<a id="sec-270"></a>
> **Source:** `docs/live-docs.md` · [↑ table of contents](#table-of-contents)
@@ -61708,7 +62261,7 @@ Press **Edit**, change something, and press <kbd>⌘</kbd>/<kbd>Ctrl</kbd> +
## Try it: a live avatar
-This is the same embed snippet from the [`<agent-3d>` reference](#sec-508).
+This is the same embed snippet from the [`<agent-3d>` reference](#sec-514).
Press **Run preview** and it renders. Then press **Edit**, swap `michelle.glb`
for `xbot.glb`, and run it again.
@@ -61870,14 +62423,14 @@ cached module.
## Related
-- [`<agent-3d>` Web Component API Reference](#sec-508) — the element most previews render
+- [`<agent-3d>` Web Component API Reference](#sec-514) — the element most previews render
- [API reference](#sec-096) — the endpoints most `curl` samples call
-- [Embed and share](#sec-186) — putting an avatar on your own site
-- [MCP tool safety](#sec-273) — the same read/write/irreversible split, applied to agent tools
+- [Embed and share](#sec-188) — putting an avatar on your own site
+- [MCP tool safety](#sec-277) — the same read/write/irreversible split, applied to agent tools
---
-<a id="sec-267"></a>
+<a id="sec-271"></a>
> **Source:** `docs/live-steps.md` · [↑ table of contents](#table-of-contents)
@@ -62060,7 +62613,7 @@ Run `npx vitest run tests/live-steps.test.js` after editing the registry; the su
---
-<a id="sec-268"></a>
+<a id="sec-272"></a>
> **Source:** `docs/make-your-agent.md` · [↑ table of contents](#table-of-contents)
@@ -62077,7 +62630,7 @@ This guide walks you through creating a 3D AI agent in the browser — no code,
Go to [three.ws/start](/start). This is the new-agent wizard.
-You'll be asked to sign in if you haven't already. See [Do I need crypto?](#sec-178) if you're not sure which sign-in option to choose.
+You'll be asked to sign in if you haven't already. See [Do I need crypto?](#sec-180) if you're not sure which sign-in option to choose.
---
@@ -62127,7 +62680,7 @@ Once you hit **Publish**, your agent gets a live URL: something like `three.ws/a
The wizard also gives you an **embed snippet**: a few lines of HTML you can paste into any webpage to make the agent appear there. You don't need to know HTML to do this — just copy and paste.
-For more on where and how to embed, continue to [Share & embed →](#sec-378)
+For more on where and how to embed, continue to [Share & embed →](#sec-383)
---
@@ -62146,14 +62699,14 @@ Changes take effect immediately — no republishing needed for most settings.
## What's next
-- **Put it on your website** → [Share & embed](#sec-378)
-- **Understand how it all works** → [How it works](#sec-240)
-- **Give the agent a custom skill** → [Create a custom skill](#sec-432)
-- **Make it yours permanently (on-chain)** → [Register on-chain](#sec-462)
+- **Put it on your website** → [Share & embed](#sec-383)
+- **Understand how it all works** → [How it works](#sec-243)
+- **Give the agent a custom skill** → [Create a custom skill](#sec-438)
+- **Make it yours permanently (on-chain)** → [Register on-chain](#sec-468)
---
-<a id="sec-269"></a>
+<a id="sec-273"></a>
> **Source:** `docs/market-data-api.md` · [↑ table of contents](#table-of-contents)
@@ -62278,7 +62831,7 @@ as the single retryable class.
---
-<a id="sec-270"></a>
+<a id="sec-274"></a>
> **Source:** `docs/marketplace.md` · [↑ table of contents](#table-of-contents)
@@ -62403,7 +62956,7 @@ direct-transfer QR for wallets that do not implement transaction requests.
and applied at settlement.
- Seller proceeds route to the seller's configured payout wallet
(`agent_payout_wallets`). A confirmed sale surfaces to the seller as a `sale` /
- `payment-earned` notification (see [Money feed](#sec-285)).
+ `payment-earned` notification (see [Money feed](#sec-289)).
## Access checks
@@ -62453,7 +63006,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-539) endpoint returns the
+ paid [`/api/x402/skill-marketplace`](#sec-546) 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
@@ -62473,11 +63026,11 @@ their chosen `currency_mint`; the platform promotes no coin other than $THREE.
- [Agent wallets](#sec-072) — how agent-side purchases are funded and gated.
- [Circulation engine](#sec-141) — manufactured marketplace demand.
-- [Skills system](#sec-387), [Coin launches](#sec-144).
+- [Skills system](#sec-392), [Coin launches](#sec-144).
---
-<a id="sec-271"></a>
+<a id="sec-275"></a>
> **Source:** `docs/mcp-3d-studio.md` · [↑ table of contents](#table-of-contents)
@@ -62549,7 +63102,7 @@ analyze: inspect_model · optimize_model preview: preview_3d
| `inspect_model(url)` | Structural stats: meshes, triangles, materials, textures, animations, extensions. |
| `optimize_model(url)` | Actionable size/perf suggestions: Draco/Meshopt, KTX2, triangle budget. |
| `preview_3d(glb_url, …)` | Render any public GLB as an interactive `<model-viewer>` artifact (orbit, AR, auto-rotate). |
-| `export_ar(glb_url, title?, kind?)` | Read-only: turn any public GLB into the device-aware AR link set (`arLaunchUrl`, `sceneViewerUrl`, `viewerUrl`, plus `irlUrl` when `kind: "avatar"`) and a [Spatial MCP](#sec-395) artifact. Free. See [AR & WebXR](ar.md#one-tap-ar-for-any-glb--get-apiar--export_ar). |
+| `export_ar(glb_url, title?, kind?)` | Read-only: turn any public GLB into the device-aware AR link set (`arLaunchUrl`, `sceneViewerUrl`, `viewerUrl`, plus `irlUrl` when `kind: "avatar"`) and a [Spatial MCP](#sec-400) artifact. Free. See [AR & WebXR](ar.md#one-tap-ar-for-any-glb--get-apiar--export_ar). |
Generation, rigging, and most mesh ops are **asynchronous**: the tool returns a
`job_id` immediately, then you poll `generation_status` (reconstruction is
@@ -62718,7 +63271,7 @@ npx @modelcontextprotocol/inspector http://localhost:3000/api/mcp-3d
---
-<a id="sec-272"></a>
+<a id="sec-276"></a>
> **Source:** `docs/mcp-agent.md` · [↑ table of contents](#table-of-contents)
@@ -62825,13 +63378,13 @@ npx @modelcontextprotocol/inspector http://localhost:3000/api/mcp-agent
---
-<a id="sec-273"></a>
+<a id="sec-277"></a>
> **Source:** `docs/mcp-safety.md` · [↑ table of contents](#table-of-contents)
# MCP tool safety
-Every tool three.ws publishes over the [Model Context Protocol](#sec-277) carries an
+Every tool three.ws publishes over the [Model Context Protocol](#sec-281) carries an
`annotations` block. Those hints are not decoration: an MCP client reads them to
decide whether a tool can run **without stopping to ask the user**. A tool marked
read-only gets executed silently; a tool marked destructive gets a confirmation
@@ -63160,7 +63713,7 @@ All four run in `npm run gate`.
---
-<a id="sec-274"></a>
+<a id="sec-278"></a>
> **Source:** `docs/mcp-studio.md` · [↑ table of contents](#table-of-contents)
@@ -63273,7 +63826,7 @@ tool call at any tier; see [Pending generations](#pending-generations-check_job)
for how it is collected rather than lost.
One naming collision worth knowing: the npm package `@three-ws/mcp-server`
-([docs](#sec-277)) also ships a tool called `forge_free`. That is a different
+([docs](#sec-281)) also ships a tool called `forge_free`. That is a different
server with its own default (`draft`, stated in its own tool schema). The
default described here is the one for `https://three.ws/api/mcp-studio`.
@@ -63301,7 +63854,7 @@ and the result narration links it for non-widget clients.
`arUrl` is the one-tap place-in-your-room link (see [AR in ChatGPT](#sec-139)).
Rigged avatars additionally carry `irlUrl`, the living-agent handoff into
-[IRL](#sec-256), and the inline widget's AR button becomes **Bring it to life**.
+[IRL](#sec-259), and the inline widget's AR button becomes **Bring it to life**.
Every result also includes a `spatial` field, the open Spatial MCP artifact
(`specs/SPATIAL_MCP.md`) so any Spatial-MCP renderer can display the model.
@@ -63522,15 +64075,15 @@ CSP entry cannot drift apart.
---
-<a id="sec-275"></a>
+<a id="sec-279"></a>
> **Source:** `docs/mcp-tools.md` · [↑ table of contents](#table-of-contents)
# MCP Tools Catalog
-three.ws ships several [MCP](#sec-277) servers: tool servers that AI assistants
+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-544). This
+others expose paid tools that settle per call in USDC over [x402](#sec-551). 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
@@ -63569,7 +64122,7 @@ the read-only studio helpers below.
A free, non-crypto MCP server for the ChatGPT App Directory and any MCP client. It
exposes **only** 3D generation/inspection — no account, no payment, no token. See
-[3D Studio MCP](#sec-274).
+[3D Studio MCP](#sec-278).
## Material Studio (hosted, free) — `/api/material-studio`
@@ -63612,7 +64165,7 @@ and direction tools are flat per call.
Free studio helpers (no charge): `getting_started`, `generation_status`,
`preview_3d`, `list_animations`, `inspect_model`, `optimize_model`, `save_avatar`,
-`validate_spatial_response` (the [Spatial MCP](#sec-395) conformance gate).
+`validate_spatial_response` (the [Spatial MCP](#sec-400) conformance gate).
## Agent & commerce tools — `3d-agent-local`
@@ -63655,9 +64208,9 @@ generation lane**; the rest are paid and quote their price in the
| Server | File | Surface |
|---|---|---|
| Agent MCP | `api/mcp-agent.js` | Agent build/control tools. |
-| Bazaar MCP | `api/mcp-bazaar.js` | x402 service discovery — see [x402 bazaar](#sec-276). |
-| IBM MCP | `api/ibm-mcp.js` | watsonx / Granite integration — see [IBM](#sec-250). |
-| pump.fun MCP | `api/pump-fun-mcp.js` | Launch/trade tools — see [Solana pump.fun](#sec-392). |
+| Bazaar MCP | `api/mcp-bazaar.js` | x402 service discovery — see [x402 bazaar](#sec-280). |
+| IBM MCP | `api/ibm-mcp.js` | watsonx / Granite integration — see [IBM](#sec-253). |
+| pump.fun MCP | `api/pump-fun-mcp.js` | Launch/trade tools — see [Solana pump.fun](#sec-397). |
## $THREE only
@@ -63668,16 +64221,16 @@ promote no specific token.
## Related
-- [MCP](#sec-277) overview · [3D Studio MCP](#sec-274) ·
- [3D Studio (paid)](#sec-271) · [x402 bazaar](#sec-276)
-- [x402 paid endpoints](#sec-539) — the same capabilities over REST.
-- [MCP tool safety](#sec-273) - what each tool's safety annotations mean,
+- [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.
+- [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.
---
-<a id="sec-276"></a>
+<a id="sec-280"></a>
> **Source:** `docs/mcp-x402-bazaar.md` · [↑ table of contents](#table-of-contents)
@@ -63789,7 +64342,7 @@ npx @modelcontextprotocol/inspector http://localhost:3000/api/mcp-bazaar
---
-<a id="sec-277"></a>
+<a id="sec-281"></a>
> **Source:** `docs/mcp.md` · [↑ table of contents](#table-of-contents)
@@ -63939,8 +64492,8 @@ Ready-to-submit listing packages for each directory, plus the canonical metadata
Deep dives — every tool, argument, env var, and example:
-- **Hosted remote:** [3D Studio (free)](#sec-274) · [3D Studio (paid)](#sec-271) · [Agent wallet](#sec-272) · [x402 Bazaar](#sec-276) · [IBM x402](#sec-249)
-- **Install-and-run:** each npm server ships its usage guide (tools, arguments, env vars, examples) in its package README on [npmjs.com/org/three-ws](https://www.npmjs.com/org/three-ws). The [MCP Tools Catalog](#sec-275) maps every tool to its server and price.
+- **Hosted remote:** [3D Studio (free)](#sec-278) · [3D Studio (paid)](#sec-275) · [Agent wallet](#sec-276) · [x402 Bazaar](#sec-280) · [IBM x402](#sec-252)
+- **Install-and-run:** each npm server ships its usage guide (tools, arguments, env vars, examples) in its package README on [npmjs.com/org/three-ws](https://www.npmjs.com/org/three-ws). The [MCP Tools Catalog](#sec-279) maps every tool to its server and price.
---
@@ -64328,7 +64881,7 @@ Turn an avatar or on-chain agent **you own** into a holder-only interactive 3D e
}
```
-The `structuredContent` returns `gate_id`, `asset_id`, `gate` (`mint`, `min_amount`, `chain`), and `embed_snippet` — a ready-to-paste `<script>` + `<three-d>` tag. See [Token-gated 3D embeds](#sec-407) for the full verification flow, the anti-abuse token/rate-limit design, and how visitors unlock the embed.
+The `structuredContent` returns `gate_id`, `asset_id`, `gate` (`mint`, `min_amount`, `chain`), and `embed_snippet` — a ready-to-paste `<script>` + `<three-d>` tag. See [Token-gated 3D embeds](#sec-412) for the full verification flow, the anti-abuse token/rate-limit design, and how visitors unlock the embed.
---
@@ -64349,7 +64902,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-544) — 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-551) — never a second, MCP-only payment flow.
```bash
# Equivalent to: GET /api/v1/x/dexscreener/token?addresses=FeMbDoX7R1Psc4GEcvJdsbNbZA3bfztcyDCatJVJpump
@@ -64617,7 +65170,7 @@ Contributors: `npm run audit:mcp-safety` enforces this. It parses each tool's ha
---
-<a id="sec-278"></a>
+<a id="sec-282"></a>
> **Source:** `docs/media-api.md` · [↑ table of contents](#table-of-contents)
@@ -65155,7 +65708,7 @@ staged as web-ready GLBs. Same pagination (`?limit=1..1000`, `?offset=`),
same empty-until-staged behavior, no auth. One difference from the character
library: this endpoint validates the cursors strictly, so a malformed
`?limit`/`?offset` returns `400 invalid_limit` / `400 invalid_offset` instead
-of being coerced into a page. See [the object library doc](#sec-301)
+of being coerced into a page. See [the object library doc](#sec-305)
for the full parameter table.
### Response
@@ -65507,13 +66060,13 @@ curl -s 'https://three.ws/api/forge-rembg?job=JOB_ID'
## Related
- [3D API](#sec-001) - the core free text-to-3D lane, model inspection, and the paid Forge Pro tiers
-- [Image to 3D](#sec-251) - the photo-input reconstruction product these front doors feed
-- [Voice Lab](#sec-506) - voice cloning and synthesis, the other half of the avatar voice loop
+- [Image to 3D](#sec-254) - the photo-input reconstruction product these front doors feed
+- [Voice Lab](#sec-512) - voice cloning and synthesis, the other half of the avatar voice loop
- [API Reference](#sec-096) - the full three.ws HTTP API surface
---
-<a id="sec-279"></a>
+<a id="sec-283"></a>
> **Source:** `docs/memetic-launcher.md` · [↑ table of contents](#table-of-contents)
@@ -65618,12 +66171,12 @@ A POST with no body at all is valid and reads back as an empty patch, so
## Related surfaces
- [/launches](https://three.ws/launches) — every coin launched through three.ws, including yours.
-- [docs/pump-launcher.md](#sec-339) — the x402 paid one-shot launcher (`/api/x402/pump-launch`), a different surface: one coin per paid call, platform-fronted.
+- [docs/pump-launcher.md](#sec-344) — the x402 paid one-shot launcher (`/api/x402/pump-launch`), a different surface: one coin per paid call, platform-fronted.
- `api/_lib/launcher-engine.js` — the shared engine both scopes run on (cron: `/api/cron/launcher-tick`).
---
-<a id="sec-280"></a>
+<a id="sec-284"></a>
> **Source:** `docs/memory.md` · [↑ table of contents](#table-of-contents)
@@ -66035,7 +66588,7 @@ store described above and each revocable by deleting exactly what it wrote:
---
-<a id="sec-281"></a>
+<a id="sec-285"></a>
> **Source:** `docs/meta-allocator.md` · [↑ table of contents](#table-of-contents)
@@ -66129,14 +66682,14 @@ plan `source` is `"empty"` with a helpful message instead of an error.
## Related
-- [Trader Card & the claim-your-wallet wedge](#sec-409)
-- [The trading surfaces](#sec-415) · [/vaults](https://three.ws/vaults) (copy-trade with custody guardrails)
+- [Trader Card & the claim-your-wallet wedge](#sec-414)
+- [The trading surfaces](#sec-420) · [/vaults](https://three.ws/vaults) (copy-trade with custody guardrails)
- [Clip Director: every trade becomes content](#sec-143)
-- [Financial controls & custody guardrails](#sec-221)
+- [Financial controls & custody guardrails](#sec-223)
---
-<a id="sec-282"></a>
+<a id="sec-286"></a>
> **Source:** `docs/mint-mark.md` · [↑ table of contents](#table-of-contents)
@@ -66262,13 +66815,13 @@ No other mint should appear in tests, fixtures, or documentation.
## Related
-- [Solana agents](#sec-394) — agent wallet management and on-chain interactions
-- [Solana pump.fun signals](#sec-392) — pump.fun live feed integration
-- [ERC-8004](#sec-188) — on-chain agent registry (uses the same brand metadata builder)
+- [Solana agents](#sec-399) — agent wallet management and on-chain interactions
+- [Solana pump.fun signals](#sec-397) — pump.fun live feed integration
+- [ERC-8004](#sec-190) — on-chain agent registry (uses the same brand metadata builder)
---
-<a id="sec-283"></a>
+<a id="sec-287"></a>
> **Source:** `docs/minted.md` · [↑ table of contents](#table-of-contents)
@@ -66276,7 +66829,7 @@ No other mint should appear in tests, fixtures, or documentation.
[three.ws/minted](https://three.ws/minted) is the live, public gallery of every generated or owned avatar that a creator chose to mint as a **Metaplex Core NFT** through three.ws. It is the NFT counterpart of the `/launches` coin directory: real on-chain property, listed the moment it mints. Every card renders the actual model in a live, auto-rotating 3D viewer (not a flat thumbnail), and every asset carries baked provenance and an enforced, capped creator royalty. Minting is always opt-in: the free text-to-3D lane never mints anything on its own.
-This doc covers the gallery surface and the mint flow as a user-facing feature. The provenance internals live in their own docs: [content credentials for AI-generated models](#sec-335) (signed credentials, Solana anchoring, the free verify endpoint) and [the three.ws mint mark](#sec-282) (the `3ws` address branding on coin launches).
+This doc covers the gallery surface and the mint flow as a user-facing feature. The provenance internals live in their own docs: [content credentials for AI-generated models](#sec-340) (signed credentials, Solana anchoring, the free verify endpoint) and [the three.ws mint mark](#sec-286) (the `3ws` address branding on coin launches).
## The gallery
@@ -66308,7 +66861,7 @@ curl "https://three.ws/api/v1/tokenized/launches?network=mainnet&offset=0&limit=
## How a mint works
-Minting runs through the `mint_3d_asset` tool on the [3D Studio MCP server](#sec-277). It is priced per call via x402 (USDC); an OAuth bearer token bypasses payment. A creator supplies:
+Minting runs through the `mint_3d_asset` tool on the [3D Studio MCP server](#sec-281). It is priced per call via x402 (USDC); an OAuth bearer token bypasses payment. A creator supplies:
- **The model:** an owned `avatar_id`, or any absolute `glb_url`.
- **The recipient:** an explicit `owner_wallet` (base58), or the OAuth-linked Solana wallet by default.
@@ -66331,7 +66884,7 @@ Every mint carries its provenance twice:
- **In the NFT metadata itself:** creator, prompt, generation model and provider, parent lineage, and timestamp travel with the asset wherever it goes.
- **As a signed record on the platform's append-only agent-actions ledger** (when the source avatar has a provisioned agent to sign as): an independently verifiable entry, referenced in the mint response and queryable via the MCP action tools. This write is best-effort and never blocks a mint that already succeeded on-chain.
-For how signed credentials, canonical hashing, and on-chain anchoring work under the hood, read [provenance.md](#sec-335). For the `3ws` address mark that brands coin launches, read [mint-mark.md](#sec-282).
+For how signed credentials, canonical hashing, and on-chain anchoring work under the hood, read [provenance.md](#sec-340). For the `3ws` address mark that brands coin launches, read [mint-mark.md](#sec-286).
### Remix royalties: paid the moment a remix mints
@@ -66345,14 +66898,14 @@ The companion MCP tool `get_3d_asset_onchain` resolves any Core mint address to
## Related
-- [Verifiable 3D provenance](#sec-335): signed content credentials and free verification for generated models
-- [The three.ws mint mark](#sec-282): the `3ws` address brand on coin launches
-- [MCP servers](#sec-277): the `mint_3d_asset` and `get_3d_asset_onchain` tools
-- [Custody you can verify](#sec-170): the wallet rails behind agent-held assets
+- [Verifiable 3D provenance](#sec-340): signed content credentials and free verification for generated models
+- [The three.ws mint mark](#sec-286): the `3ws` address brand on coin launches
+- [MCP servers](#sec-281): the `mint_3d_asset` and `get_3d_asset_onchain` tools
+- [Custody you can verify](#sec-172): the wallet rails behind agent-held assets
---
-<a id="sec-284"></a>
+<a id="sec-288"></a>
> **Source:** `docs/mocap-studio.md` · [↑ table of contents](#table-of-contents)
@@ -66451,7 +67004,7 @@ what the page itself sends.
---
-<a id="sec-285"></a>
+<a id="sec-289"></a>
> **Source:** `docs/money-feed.md` · [↑ table of contents](#table-of-contents)
@@ -66465,7 +67018,7 @@ event lives.
> Not to be confused with the **personal activity feed** on `/feed`
> (`GET /api/users/me/feed`) — that one shows who created what and who followed
-> whom, and is documented in [The social layer](#sec-391). This page is
+> whom, and is documented in [The social layer](#sec-396). This page is
> about value movement only. The two share a URL word ("feed") and nothing else.
---
@@ -66542,7 +67095,7 @@ spend-cap and policy engine before they are recorded (see
| Producer | Ledger? | Ticker? | Domain record |
|---|---|---|---|
| [Circulation engine](#sec-141) tips/payments/trades/buys | Yes | Trades/launches via pump feed | `circulation_actions` + domain table |
-| [Marketplace](#sec-270) skill/asset purchase | Yes | `payment` / `sale` | `skill_purchases` / `asset_purchases` |
+| [Marketplace](#sec-274) skill/asset purchase | Yes | `payment` / `sale` | `skill_purchases` / `asset_purchases` |
| [Coin launches](#sec-144) | Yes | `coin-buy` / `agent-deploy` | `pump_agent_mints` |
| Sniper trades | Yes (`category: 'snipe'`) | — | `agent_sniper_positions` |
| [Autonomous x402 loop](#sec-105) | Yes (`category: 'x402'`) | — | `x402_autonomous_log` |
@@ -66582,11 +67135,11 @@ 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-540) — the *other* direction: money paid **to** our endpoints (`x402_audit_log`), not agent spend.
+- [x402 revenue & receipts](#sec-547) — the *other* direction: money paid **to** our endpoints (`x402_audit_log`), not agent spend.
---
-<a id="sec-286"></a>
+<a id="sec-290"></a>
> **Source:** `docs/money-flow-map.md` · [↑ table of contents](#table-of-contents)
@@ -66825,14 +67378,14 @@ covering it there. Keep the ordering discipline in `classifyRole`: a rule goes
## Related
-- [Money Pulse](#sec-285): the event stream these edges are aggregated from.
+- [Money Pulse](#sec-289): the event stream these edges are aggregated from.
- [Circulation engine](#sec-141): what generates most of this
activity.
- [Agent economy volume](#sec-052): the per-agent totals, ranked.
---
-<a id="sec-287"></a>
+<a id="sec-291"></a>
> **Source:** `docs/money-map.md` · [↑ table of contents](#table-of-contents)
@@ -66843,8 +67396,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-539) (the paid endpoint catalog),
-[x402 revenue & receipts](#sec-540) (how settlements are recorded),
+Companion docs: [x402 endpoints](#sec-546) (the paid endpoint catalog),
+[x402 revenue & receipts](#sec-547) (how settlements are recorded),
[Solana signers runbook](../api/_lib/solana-signers.js) (the
signer/funder wallets and how to fund them).
@@ -66884,7 +67437,7 @@ Every engine signs from its **own** keypair; a single **funding root** tops thos
signers up with SOL when they run low, and does nothing else. Documented in full —
encodings, minimum balances, guards, funding tool — in the
[Solana signers runbook](../api/_lib/solana-signers.js) and the
-[economy master](#sec-182) subsystem doc.
+[economy master](#sec-184) subsystem doc.
| Wallet | Role |
| ------ | ---- |
@@ -66944,7 +67497,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-539).
+ [x402 endpoints](#sec-546).
- **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,
@@ -66964,9 +67517,9 @@ unit economics.
in the on-chain ASP record, not in repo code** — update it here if the ASP
registration changes.
- **Marketplace skills** — agent skill marketplace over Solana Pay
- ([api/marketplace/](../api/marketplace)); see [marketplace skills](#sec-494).
+ ([api/marketplace/](../api/marketplace)); see [marketplace skills](#sec-500).
- **Labor market** — bounty/escrow jobs with worker + author-royalty settlement; see
- [labor market](#sec-260).
+ [labor market](#sec-263).
- **Other** — vanity bounties, forge REST ([api/x402/forge.js](../api/x402/forge.js)),
subscriptions, credit deposits.
@@ -66976,7 +67529,7 @@ unit economics.
Engines that move money on their own (cron/worker driven) draw from the signer
wallets, not the receivers — and each signer is kept funded by the
-[economy master](#sec-182) via the `treasury-topup` cron (every 30 min,
+[economy master](#sec-184) via the `treasury-topup` cron (every 30 min,
allowlist-guarded, reserve/per-engine/per-run caps). Which wallet funds which
engine and minimum balances are in the
[Solana signers runbook](../api/_lib/solana-signers.js). The
@@ -67012,23 +67565,23 @@ Guardrails on outflow: the economy master is funder-only with reserve/per-transf
per-run caps and a registry allowlist; the ring can only settle to allowlisted
wallets (anti-drain gate); the sniper auto-funder moves money only for strategies
that set `auto_fund_enabled = true` (default off). See
-[financial-controls.md](#sec-221) for the full register.
+[financial-controls.md](#sec-223) for the full register.
## Related
-- [Financial controls & audit register](#sec-221) — every ledger's integrity, reconciliation, retention, monitoring, and the ranked gap list.
-- [x402 endpoints](#sec-539) — the paid endpoint catalog and price overrides.
-- [x402 revenue & receipts](#sec-540) — where settlements are recorded.
-- [x402 ring economy](#sec-541) — the internal recirculation loop.
-- [Pump platform fee](#sec-340) — the pump trade fee detail.
-- [Coin-launch wallets](#sec-496) — launch-time wallet flow.
+- [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.
+- [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.
- [Agent wallet custody](#sec-072) — how custodial keys are held.
- [Solana signers runbook](../api/_lib/solana-signers.js) — signer/funder wallets + funding.
---
-<a id="sec-288"></a>
+<a id="sec-292"></a>
> **Source:** `docs/monitor.md` · [↑ table of contents](#table-of-contents)
@@ -67156,7 +67709,7 @@ board a lie.
avatar cam while it works
- [Money Pulse](https://three.ws/pulse): the full event feed with filters and
per-agent views
-- [Money Flow Map](#sec-286): the topology behind the totals, who
+- [Money Flow Map](#sec-290): the topology behind the totals, who
pays whom
- [Agent Economy Volume](https://three.ws/agent-economy-volume): the long-window
agent-to-agent hire ledger
@@ -67164,7 +67717,7 @@ board a lie.
---
-<a id="sec-289"></a>
+<a id="sec-293"></a>
> **Source:** `docs/motion-swap.md` · [↑ table of contents](#table-of-contents)
@@ -67260,7 +67813,7 @@ its error state.
---
-<a id="sec-290"></a>
+<a id="sec-294"></a>
> **Source:** `docs/multi-agent.md` · [↑ table of contents](#table-of-contents)
@@ -67603,7 +68156,7 @@ To extend this into a full turn-based scene, add a `brain` attribute to Mira wit
---
-<a id="sec-291"></a>
+<a id="sec-295"></a>
> **Source:** `docs/native-launchpad.md` · [↑ table of contents](#table-of-contents)
@@ -67798,7 +68351,7 @@ Stated plainly, because a half-built feature that claims to be finished is worse
---
-<a id="sec-292"></a>
+<a id="sec-296"></a>
> **Source:** `docs/news-rights.md` · [↑ table of contents](#table-of-contents)
@@ -67892,11 +68445,11 @@ Three rules, in order of importance:
- [`api/_lib/news-rights.js`](../api/_lib/news-rights.js) — the implementation
- [`scripts/news-takedown-purge.mjs`](../scripts/news-takedown-purge.mjs) — the purge tool
-- [Market Data API](#sec-269) — the paid market endpoints, including archive search
+- [Market Data API](#sec-273) — the paid market endpoints, including archive search
---
-<a id="sec-293"></a>
+<a id="sec-297"></a>
> **Source:** `docs/notifications.md` · [↑ table of contents](#table-of-contents)
@@ -68177,7 +68730,7 @@ one click from the gear icon in both notification surfaces.
## Related pages
-- [The social layer](#sec-391): where notification events come from
+- [The social layer](#sec-396): where notification events come from
and how they connect to the feed, follows, and portfolios.
- [api/notifications/README.md](../api/notifications/README.md): the
endpoint directory's own reference.
@@ -68186,7 +68739,7 @@ one click from the gear icon in both notification surfaces.
---
-<a id="sec-294"></a>
+<a id="sec-298"></a>
> **Source:** `docs/nvidia-apps-catalog-listing.md` · [↑ table of contents](#table-of-contents)
@@ -68194,7 +68747,7 @@ one click from the gear icon in both notification surfaces.
Everything needed to submit three.ws to the NVIDIA Inception Accelerated Apps Catalog. The form lives behind the Inception portal login (Portal > Profile > Add product), so this doc holds the copy, categories, links, and assets ready to paste. Submissions are reviewed by NVIDIA on a rolling basis; approval is subject to fit.
-Related docs: [nvidia-inception.md](#sec-296) (membership overview), [nvidia-models.md](#sec-297) (full model map, the source of truth for every NVIDIA claim below), [nvidia-visibility-map.md](#sec-300) (every other NVIDIA surface, and the asks to batch into the request email below).
+Related docs: [nvidia-inception.md](#sec-300) (membership overview), [nvidia-models.md](#sec-301) (full model map, the source of truth for every NVIDIA claim below), [nvidia-visibility-map.md](#sec-304) (every other NVIDIA surface, and the asks to batch into the request email below).
---
@@ -68227,7 +68780,7 @@ Remove and leave unchecked:
### 2. Ask for the catalog listing
-The portal has no "publish to catalog" button, so the request goes to the program team. Send the email in [nvidia-apps-catalog-request.md](#sec-295) to `[email protected]` after the record corrections above are saved, and note the send date there.
+The portal has no "publish to catalog" button, so the request goes to the program team. Send the email in [nvidia-apps-catalog-request.md](#sec-299) to `[email protected]` after the record corrections above are saved, and note the send date there.
---
@@ -68349,24 +68902,24 @@ Nothing else checked. TensorRT/Triton/Omniverse stay unchecked here too.
6. Submit. Listings are reviewed on a rolling basis; note the submission date in this doc when done.
7. Correct the existing record per the Status section (move Riva/Audio2Face/NIM to Used, drop DeepVariant NIM) BEFORE adding anything new.
8. Add the `<agent-3d>` embed as a second product using its section above. Do not file more records than these two: duplicates read as noise to the curator.
-9. Send the inclusion-request email in [nvidia-apps-catalog-request.md](#sec-295) to [email protected] and record the send date there.
+9. Send the inclusion-request email in [nvidia-apps-catalog-request.md](#sec-299) to [email protected] and record the send date there.
---
-<a id="sec-295"></a>
+<a id="sec-299"></a>
> **Source:** `docs/nvidia-apps-catalog-request.md` · [↑ table of contents](#table-of-contents)
# The NVIDIA Inception email: five asks, one thread
-The Inception portal has no "publish to the catalog" control. A product record makes the company eligible; the public [Accelerated Apps Catalog](https://marketplace.nvidia.com/en-us/enterprise/applications/) is curated and published by NVIDIA. This is the request that asks for the listing, sent after the portal record is corrected per [nvidia-apps-catalog-listing.md](#sec-294).
+The Inception portal has no "publish to the catalog" control. A product record makes the company eligible; the public [Accelerated Apps Catalog](https://marketplace.nvidia.com/en-us/enterprise/applications/) is curated and published by NVIDIA. This is the request that asks for the listing, sent after the portal record is corrected per [nvidia-apps-catalog-listing.md](#sec-298).
-It also carries four other asks that have never been made. Per [nvidia-visibility-map.md](#sec-300), every Tier 1 ask routes to the same inbox, so they are batched here deliberately. **Do not split these into separate emails.** A program manager who receives one clear email with five asks answers it. Five separate emails read as noise.
+It also carries four other asks that have never been made. Per [nvidia-visibility-map.md](#sec-304), every Tier 1 ask routes to the same inbox, so they are batched here deliberately. **Do not split these into separate emails.** A program manager who receives one clear email with five asks answers it. Five separate emails read as noise.
- **Subject:** three.ws (Inception member): catalog listing, Showcase, and co-marketing
- **Sent:** not yet sent. Record the date here when it goes out.
-- **Blocked on:** the portal record correction, [nvidia-apps-catalog-listing.md](#sec-294) step 1. As filed the record reads as a CUDA consumer rather than a digital-human app, which undercuts asks 1 and 2. Correct it, save it, then send.
+- **Blocked on:** the portal record correction, [nvidia-apps-catalog-listing.md](#sec-298) step 1. As filed the record reads as a CUDA consumer rather than a digital-human app, which undercuts asks 1 and 2. Correct it, save it, then send.
### The five asks, and why each one is here
@@ -68445,7 +68998,7 @@ https://three.ws
---
-<a id="sec-296"></a>
+<a id="sec-300"></a>
> **Source:** `docs/nvidia-inception.md` · [↑ table of contents](#table-of-contents)
@@ -68483,7 +69036,7 @@ Membership is a startup program, not a partnership or an investment: NVIDIA revi
## Related
-- [NVIDIA visibility map](#sec-300): every NVIDIA surface where three.ws can earn recognition, what each one requires, and which membership benefits are still unclaimed
+- [NVIDIA visibility map](#sec-304): every NVIDIA surface where three.ws can earn recognition, what each one requires, and which membership benefits are still unclaimed
- [NVIDIA models on three.ws](/docs/nvidia-models) — the free inference layer, model by model
- [The generator was never the hard part](/docs/nvidia-nemotron-spotlight): our Nemotron Nano write-up, published on the NVIDIA Developer Forums
- [Image-to-3D on NVIDIA L4 and Blackwell](https://three.ws/blog/image-to-3d-on-nvidia-l4-and-blackwell): the engineering post on the GPU fleet itself: memory ceilings, `sm_120` kernels, and regional quota
@@ -68491,7 +69044,7 @@ Membership is a startup program, not a partnership or an investment: NVIDIA revi
---
-<a id="sec-297"></a>
+<a id="sec-301"></a>
> **Source:** `docs/nvidia-models.md` · [↑ table of contents](#table-of-contents)
@@ -68698,7 +69251,7 @@ The free NVIDIA TTS lane: **Magpie multilingual on Riva**, selected by an NVCF `
---
-<a id="sec-298"></a>
+<a id="sec-302"></a>
> **Source:** `docs/nvidia-nemotron-ask-the-experts-questions.md` · [↑ table of contents](#table-of-contents)
@@ -68802,11 +69355,11 @@ Every claim in the two posts is sourced, so a follow-up question cannot catch us
| Claim | Source |
|---|---|
-| NVIDIA Inception member, accepted July 2026 | [nvidia-inception.md](#sec-296) |
-| `nvidia/nemotron-nano-12b-v2-vl` gates every photo-to-3D generation, 1-2s | [nvidia-nemotron-spotlight.md](#sec-299), `api/_lib/forge-image-validate.js` |
-| ~281 image prompt tokens vs ~1,600 for a 90B-class VLM | [nvidia-nemotron-spotlight.md](#sec-299) |
+| NVIDIA Inception member, accepted July 2026 | [nvidia-inception.md](#sec-300) |
+| `nvidia/nemotron-nano-12b-v2-vl` gates every photo-to-3D generation, 1-2s | [nvidia-nemotron-spotlight.md](#sec-303), `api/_lib/forge-image-validate.js` |
+| ~281 image prompt tokens vs ~1,600 for a 90B-class VLM | [nvidia-nemotron-spotlight.md](#sec-303) |
| Published Nemotron write-up on the NVIDIA Developer Forums | [forums.developer.nvidia.com](https://forums.developer.nvidia.com/t/how-nemotron-made-three-ws-text-to-3d-pipeline-usable/376445) |
-| `nvidia-nemotron-nano-9b-v2` used for reasoning turns, NemoGuard at ~340 ms median | [nvidia-nemotron-spotlight.md](#sec-299) |
+| `nvidia-nemotron-nano-9b-v2` used for reasoning turns, NemoGuard at ~340 ms median | [nvidia-nemotron-spotlight.md](#sec-303) |
The two other standing asks from that write-up (the hosted TRELLIS image-input
restriction and the 77-character TRELLIS prompt cap) are TRELLIS questions, not Nemotron
@@ -68893,7 +69446,7 @@ plus a reported trillion-parameter Nemotron 4 in training.
---
-<a id="sec-299"></a>
+<a id="sec-303"></a>
> **Source:** `docs/nvidia-nemotron-spotlight.md` · [↑ table of contents](#table-of-contents)
@@ -69054,11 +69607,11 @@ Build the small stuff. Put it in front. The generator was never the hard part.
---
-*three.ws is a browser-native platform for generating 3D avatars, worlds, and agents from a sentence. The text-to-3D lane described here is free and open: no key, no account. Our full NVIDIA model map lives in [`docs/nvidia-models.md`](#sec-297), and the pipeline internals are in [`docs/3d-asset-pipeline.md`](#sec-002). three.ws joined the [NVIDIA Inception program](#sec-296) in July 2026; the companion engineering post on our own GPU fleet is [Image-to-3D on NVIDIA L4 and Blackwell](https://three.ws/blog/image-to-3d-on-nvidia-l4-and-blackwell).*
+*three.ws is a browser-native platform for generating 3D avatars, worlds, and agents from a sentence. The text-to-3D lane described here is free and open: no key, no account. Our full NVIDIA model map lives in [`docs/nvidia-models.md`](#sec-301), and the pipeline internals are in [`docs/3d-asset-pipeline.md`](#sec-002). three.ws joined the [NVIDIA Inception program](#sec-300) in July 2026; the companion engineering post on our own GPU fleet is [Image-to-3D on NVIDIA L4 and Blackwell](https://three.ws/blog/image-to-3d-on-nvidia-l4-and-blackwell).*
---
-<a id="sec-300"></a>
+<a id="sec-304"></a>
> **Source:** `docs/nvidia-visibility-map.md` · [↑ table of contents](#table-of-contents)
@@ -69069,8 +69622,8 @@ every NVIDIA surface where three.ws can earn recognition, what each one actually
requires, and the honest status of each today.
Scope note: the **Accelerated Apps Catalog** already has its own two docs and is
-not re-litigated here. See [nvidia-apps-catalog-listing.md](#sec-294)
-for the listing kit and [nvidia-apps-catalog-request.md](#sec-295)
+not re-litigated here. See [nvidia-apps-catalog-listing.md](#sec-298)
+for the listing kit and [nvidia-apps-catalog-request.md](#sec-299)
for the inclusion email. This doc covers everything else and links to them where
they overlap.
@@ -69116,7 +69669,7 @@ Everything here can be done today. Nothing waits on NVIDIA, a build, or a date.
|---|---|---|---|
| 1 | **Our own X, LinkedIn, and Telegram** | Ours | The membership post that never happened. See [Social](#social-surfaces-ours-to-drive). |
| 2 | **Inception co-marketing kit** | Portal benefit request, or `[email protected]` | An entitlement we have never claimed. See [Benefits we are owed](#benefits-we-are-entitled-to-and-have-never-requested). |
-| 3 | **Portal product record correction** | `programs.nvidia.com/phoenix/application` | Gates the Showcase AND the Apps Catalog. Already specified in [nvidia-apps-catalog-listing.md](#sec-294) step 1. Nothing else in this doc lands well while the record says "CUDA consumer". |
+| 3 | **Portal product record correction** | `programs.nvidia.com/phoenix/application` | Gates the Showcase AND the Apps Catalog. Already specified in [nvidia-apps-catalog-listing.md](#sec-298) step 1. Nothing else in this doc lands well while the record says "CUDA consumer". |
| 4 | **Inception Startup Showcase** | `[email protected]` | NVIDIA's own wording is "member spotlights and story opportunities". Curated from the portal record, so do #3 first. |
| 5 | **AI Podcast guest nomination** | Embedded form at [ai-podcast.nvidia.com](https://ai-podcast.nvidia.com) | Free, one form, and a founder-shaped story. Fields: name, business email, organization, industry, job title, location, preferred language, and a description of the proposal. |
| 6 | **NVIDIA Developer Forums, post 3** | [forums.developer.nvidia.com](https://forums.developer.nvidia.com) | We are 2 for 2 on posts that landed. This is the one channel with a proven track record, and it is self-serve. See [Technical publishing](#technical-publishing-the-proven-channel). |
@@ -69132,7 +69685,7 @@ Real listings, real effort, honest gates. Do not pitch these before the code exi
| **NGC Catalog** (via the [NGC Software Partner program](https://www.nvidia.com/en-us/gpu-cloud/ngc-software-partners/)) | Partner legal agreement, then push to an NGC private staging repo, pass security scanning and QA, final sign-off | **The closest Tier 2 surface to reachable.** Prerequisites are a CUDA 9+ base image, GPU acceleration, Pascal or newer, an EULA, and no personal-data collection. Our GPU workers are already `nvidia/cuda` 12.1 to 12.8 containers, so the technical bar is met; what is missing is the EULA and the legal agreement. This converts work we have already done into a permanent NVIDIA-hosted listing. |
| **ACE / digital-human ecosystem** | No public form found. Ask for the redirect in the Showcase email | Genuinely strong: Riva, Magpie, and Audio2Face-3D are shipping, and a **browser-native** A2F demo is rare (most A2F work lives in Unreal or Omniverse). This is our most differentiated technical story. Do not overclaim: we consume ACE microservices, we do not self-host NIM. |
| **NVIDIA Technical Blog** ([developer.nvidia.com/blog](https://developer.nvidia.com/blog/)) | No public guest-submission process. Route via the forum Technical Blog category and the program team | Editorially controlled by NVIDIA. The realistic path is a forum post that performs, then a pitch. Our two live forum posts are the audition tape. |
-| **Omniverse Exchange** | [Omniverse Exchange Publishing Portal](https://developer.nvidia.com/omniverse-exchange-publishing-portal) (early access), plus a GitHub repo tagged with the `omniverse-kit-extension` topic | **Blocked and should stay blocked.** OpenUSD interop is roadmap, not shipping, and [nvidia-apps-catalog-listing.md](#sec-294) already rules that Omniverse Kit stays under "Considering". Note the Omniverse Launcher was deprecated 2025-10-01, so old guides mislead. |
+| **Omniverse Exchange** | [Omniverse Exchange Publishing Portal](https://developer.nvidia.com/omniverse-exchange-publishing-portal) (early access), plus a GitHub repo tagged with the `omniverse-kit-extension` topic | **Blocked and should stay blocked.** OpenUSD interop is roadmap, not shipping, and [nvidia-apps-catalog-listing.md](#sec-298) already rules that Omniverse Kit stays under "Considering". Note the Omniverse Launcher was deprecated 2025-10-01, so old guides mislead. |
## Tier 3: time-gated, and the clock is running
@@ -69287,11 +69840,11 @@ Recorded so the next person does not repeat the search.
One thread, one address. Every ask in Tier 1 goes to the same inbox, so batch
them into a single email rather than sending four.
-**Done: the batched email is written.** [nvidia-apps-catalog-request.md](#sec-295)
+**Done: the batched email is written.** [nvidia-apps-catalog-request.md](#sec-299)
now carries all five asks (catalog listing, Showcase nomination, co-marketing kit,
ACE redirect, GTC pavilion and event slots) in one thread. Do not start a second
one. It is still gated on the portal record correction, which is step 1 of
-[nvidia-apps-catalog-listing.md](#sec-294): as filed the
+[nvidia-apps-catalog-listing.md](#sec-298): as filed the
record reads as a CUDA consumer, which undercuts the first two asks. Correct the
record, save it, then send and stamp the date in the request doc.
@@ -69321,16 +69874,16 @@ gcloud run services list --project aerial-vehicle-466722-p5 \
## Related
- [Big-tech recognition dispatch board](#sec-125): this map ranked against every other big-tech surface (OpenAI, Anthropic, AWS, IBM) by the odds of a published mention this week. Read that first if you are deciding where a week goes, and this one once NVIDIA is the answer.
-- [NVIDIA Inception membership](#sec-296): what membership is, and the rule that it is a program and not a partnership or an endorsement
-- [Apps Catalog listing kit](#sec-294) and [inclusion request](#sec-295): the one surface with its own dedicated docs
-- [NVIDIA models on three.ws](#sec-297): the source of truth for every NVIDIA technical claim made in any pitch
-- [Listings and distribution](#sec-265): the canonical program and directory inventory
+- [NVIDIA Inception membership](#sec-300): what membership is, and the rule that it is a program and not a partnership or an endorsement
+- [Apps Catalog listing kit](#sec-298) and [inclusion request](#sec-299): the one surface with its own dedicated docs
+- [NVIDIA models on three.ws](#sec-301): the source of truth for every NVIDIA technical claim made in any pitch
+- [Listings and distribution](#sec-269): the canonical program and directory inventory
- [Announcement coverage](#sec-095): which surfaces have been announced and which have not
-- [Partners](#sec-318): the independence and no-endorsement language that must survive any rewrite
+- [Partners](#sec-323): the independence and no-endorsement language that must survive any rewrite
---
-<a id="sec-301"></a>
+<a id="sec-305"></a>
> **Source:** `docs/object-library.md` · [↑ table of contents](#table-of-contents)
@@ -69357,7 +69910,7 @@ Each card renders the object live in an auto-rotating `<model-viewer>` (with the
| Button | Destination | What you get |
|---|---|---|
-| **Preview** | `/app#model=<glb-url>&kind=object&title=<name>` | The full three.js [3D viewer](#sec-505) in object mode (no agent chat; Restyle, AR, and Download affordances instead) |
+| **Preview** | `/app#model=<glb-url>&kind=object&title=<name>` | The full three.js [3D viewer](#sec-511) in object mode (no agent chat; Restyle, AR, and Download affordances instead) |
| **AR** | `/ar/studio?src=<glb-url>&title=<name>` | [AR Studio](#sec-098): place the prop in your real space through the camera (see [AR & WebXR](#sec-099) for how the AR handoff works per device) |
| **Download** | The GLB URL directly | The raw GLB file, CC0, yours to use anywhere |
@@ -69441,11 +69994,11 @@ The gallery and API are read-only consumers of a manifest built by a local pipel
- [Character Library](#sec-136): the rigged, animation-ready counterpart to this library.
- [AR & WebXR](#sec-099): the device-by-device AR methods behind the AR button.
- [AR Studio](#sec-098): the `/ar/studio` surface the AR button opens, including multi-object rooms.
-- [3D Viewer](#sec-505): the `/app` engine the Preview button opens in object mode.
+- [3D Viewer](#sec-511): the `/app` engine the Preview button opens in object mode.
---
-<a id="sec-302"></a>
+<a id="sec-306"></a>
> **Source:** `docs/okx-marketplace.md` · [↑ table of contents](#table-of-contents)
@@ -69459,8 +70012,8 @@ not live yet: it was rejected in review and a resubmission is pending, so the se
are reachable directly at the endpoints documented here rather than through the marketplace.
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-277) ·
-> [x402 payments](#sec-544) · seller-side protocol spec: [`specs/okx-agent-payments.md`](../specs/okx-agent-payments.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)
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
@@ -69582,7 +70135,7 @@ tests.
## Decomposed 3D studio services
Micro-priced, single-capability REST endpoints, plain JSON `POST`, one price each, all
-backed by the same engines the [MCP 3D studio](#sec-277) runs (no separate pipeline).
+backed by the same engines the [MCP 3D studio](#sec-281) runs (no separate pipeline).
`GET` on any of them returns its free descriptor (price, description, input schema).
| Service | Price (USDT) | Endpoint | You send |
@@ -69716,7 +70269,7 @@ USDC rails. The wire format OKX buyers use (headers `PAYMENT-REQUIRED` /
---
-<a id="sec-303"></a>
+<a id="sec-307"></a>
> **Source:** `docs/onboarding-tier.md` · [↑ table of contents](#table-of-contents)
@@ -69863,17 +70416,17 @@ drift silently, since the four files involved have no import edge between them:
- [`public/nav-data.js`](../public/nav-data.js) — the single source of truth for every menu
- [`STRUCTURE.md`](../STRUCTURE.md) — where every product surface lives
-- [`docs/start-here.md`](#sec-399) — the same journey, written for a human rather than a maintainer
+- [`docs/start-here.md`](#sec-404) — the same journey, written for a human rather than a maintainer
---
-<a id="sec-304"></a>
+<a id="sec-308"></a>
> **Source:** `docs/onchain-agents.md` · [↑ table of contents](#table-of-contents)
# Deploying Agents On-Chain (Bulk)
-Give every three.ws agent a real on-chain identity: a **Metaplex Core NFT** minted into the **three.ws Agents collection** on Solana. This page is for platform admins and self-hosters; regular users register a single agent through the wallet-signed flow instead. It is the bulk/admin counterpart to the single-agent, user-signed flow in [Solana agents](#sec-394): it deploys many agents server-side through a CLI runner that reports every mint as it lands.
+Give every three.ws agent a real on-chain identity: a **Metaplex Core NFT** minted into the **three.ws Agents collection** on Solana. This page is for platform admins and self-hosters; regular users register a single agent through the wallet-signed flow instead. It is the bulk/admin counterpart to the single-agent, user-signed flow in [Solana agents](#sec-399): it deploys many agents server-side through a CLI runner that reports every mint as it lands.
> Not pump.fun. These are NFTs (on-chain identity), not tokens. The only coin three.ws ever references is `$THREE`; it appears in each asset's metadata as a link, nothing more.
@@ -69936,7 +70489,7 @@ Every agent is minted **into** a single Metaplex Core *collection* account, "thr
2. **DB** — the `app_settings` table, key `solana_agent_collection_<network>`.
3. **Deploy** — first run with neither set deploys the collection (funded + signed by the authority), then persists its address to `app_settings`.
-> After the first run, set `SOLANA_AGENT_COLLECTION_MAINNET=<address>` in your environment so the single-agent flow in [Solana agents](#sec-394) mints into the *same* collection.
+> After the first run, set `SOLANA_AGENT_COLLECTION_MAINNET=<address>` in your environment so the single-agent flow in [Solana agents](#sec-399) mints into the *same* collection.
---
@@ -70143,14 +70696,210 @@ A confirmed canary asset shows `inCollection=true`, `royalty=500bps`, `attrs=11`
## See also
-- [Solana agents](#sec-394) — the single-agent, user-signed registration flow.
-- [ERC-8004](#sec-188) — the EVM on-chain identity path.
+- [Solana agents](#sec-399) — the single-agent, user-signed registration flow.
+- [ERC-8004](#sec-190) — the EVM on-chain identity path.
- [Agent manifest](#sec-055) — the metadata schema.
-- [Mint mark ("3ws")](#sec-282) — vanity marking for three.ws launches.
+- [Mint mark ("3ws")](#sec-286) — vanity marking for three.ws launches.
---
-<a id="sec-305"></a>
+<a id="sec-309"></a>
+
+> **Source:** `docs/open-source-friday-plan.md` · [↑ table of contents](#table-of-contents)
+
+# Open Source Friday: application and stream plan
+
+**Goal:** get three.ws booked on GitHub's Open Source Friday livestream (Twitch/github, Fridays 1:00 PM ET) with Andrea Griffiths (@AndreaGriffiths11 / @acolombiadev), who invited us to open the request issue on 2026-08-21.
+
+**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
+
+---
+
+## 1. Where we stand against the criteria
+
+Verified 2026-08-21 against `gh repo view nirholas/three.ws` and the working tree, not from memory.
+
+| Criterion | Status | Evidence |
+|---|---|---|
+| Code of conduct | PASS | [CODE_OF_CONDUCT.md](../CODE_OF_CONDUCT.md), Contributor Covenant, detected by GitHub |
+| Contributing guide | PASS | [CONTRIBUTING.md](../CONTRIBUTING.md), now opening with the community table and the 15-minute onboarding path |
+| License | **PASS** | Relicensed to Apache-2.0 on 2026-08-21. Verbatim [LICENSE](../LICENSE), a [NOTICE](../NOTICE) covering vendored and derived code, and all 102 first-party manifests set to `"license": "Apache-2.0"`. |
+| **100+ stars, hosted on GitHub** | **FAIL by 2** | 98 stargazers, 24 forks |
+| Open to outside contributions | PASS | 11 contributors, issue and PR templates, CODEOWNERS, and six curated open issues (see below) |
+| *Preferred:* community channel | **PASS** | Telegram community, X community, IBM Community group, GitHub Discussions, release channel. All five documented in [docs/community.md](#sec-151) and wired into the README, CONTRIBUTING, and the new-issue chooser. |
+| *Preferred:* triage team / contributor onboarding | **PASS** | [docs/triage.md](#sec-421) (labels, claiming, published response targets) and [docs/first-contribution.md](#sec-224) (clone to PR in 15 minutes, worked example) |
+| Guest available Friday 1:00 PM ET | Owner to confirm | Pre-recording is allowed as an exception |
+| Booked at least two weeks ahead | Plan for it | Earliest realistic slot: **2026-09-11** |
+
+### License: done
+
+Relicensed to **Apache-2.0** on 2026-08-21, which was the last hard failure against the criteria.
+
+Before, the repo shipped a proprietary LICENSE ("All rights reserved... may not be used, copied, modified, distributed") while its own description said "Open-source 3D AI agent framework" and CONTRIBUTING.md told contributors their work was Apache-2.0. Three statements, no two of which agreed. A reviewer who opened LICENSE stopped there.
+
+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.
+- 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.
+
+Apache-2.0 over MIT for two reasons: CONTRIBUTING.md already promised it to every contributor to date, so this makes that promise true rather than changing the terms under them; and its explicit patent grant matters with on-chain contracts in the repo.
+
+### Clearing the two-star gap
+
+98 to 100 is noise, not a campaign. It closes on its own once the relicense is announced, because a license change is a real postable event and its audience is exactly the audience that stars repos. Do not buy, trade, or ask for stars: reviewers look at the repo, and a suspicious star curve is worse than being two short. If it is still under 100 at submit time, submit anyway and mention the relicense in Additional Information.
+
+---
+
+## 2. Pre-flight work
+
+### Done on 2026-08-21
+
+- **Community channels documented and wired.** [docs/community.md](#sec-151) lists all five rooms with guidance on which fits which question, plus the house rules. Linked from the README (new Community section, in the table of contents), CONTRIBUTING.md, and the GitHub new-issue chooser (`.github/ISSUE_TEMPLATE/config.yml`).
+- **Contributor onboarding written.** [docs/first-contribution.md](#sec-224) goes clone to open PR in about 15 minutes, with a complete worked example: teaching the avatar retargeter a bone-naming convention, the test that proves it, and the two mistakes that cost a review round.
+- **Triage documented.** [docs/triage.md](#sec-421) publishes response targets (2 business days for a new issue or a first-time contributor's PR, 24 hours for a security advisory), what every label means, how to claim work, and how someone becomes a maintainer.
+- **Six curated issues opened**, every one with a named file and a verification command:
+ - [#110](https://github.com/nirholas/three.ws/issues/110) Rig: Apple / ARKit `_joint`-suffixed skeletons (verified: 0 of 10 joints map today)
+ - [#111](https://github.com/nirholas/three.ws/issues/111) Rig: Kinect trailing-side bone names (verified: 0 of 10)
+ - [#112](https://github.com/nirholas/three.ws/issues/112) Rig: Reallusion CC3/CC4 numbered spine (verified gap)
+ - [#113](https://github.com/nirholas/three.ws/issues/113) Animation: bake a real `bow` clip (the repo's own tracked `known_issue`)
+ - [#114](https://github.com/nirholas/three.ws/issues/114) Tests: drift guard between supported and documented rig conventions
+ - [#115](https://github.com/nirholas/three.ws/issues/115) Rig: teach the retargeter any convention it does not know (open-ended, `help wanted`)
+- **Labels added:** `area: rig`, `area: animation`, `area: docs`, `area: tests`, `triage`.
+- **MMD rig support shipped**, so the worked example in the onboarding doc points at real merged code rather than a hypothetical. MikuMikuDance names every bone in Japanese and mapped zero joints before; the full PMX skeleton now maps (fingers and toes included), Rig Doctor fingerprints the convention on sight, and the IK and twist bones are deliberately left unmapped. 471 tests pass across the two affected suites.
+
+### 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/`.
+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.
+
+---
+
+## 3. The issue: exact field-by-field content
+
+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.
+
+**Title:** `Open Source Friday - three.ws - 09-11-2026`
+
+**Name:** Nich (owner to confirm the name they want on air)
+
+**GitHub Handle:** `@nirholas`
+
+**Tell us about yourself:**
+> I build three.ws, an open source framework for 3D AI agents on the web. Background is full-stack and real-time graphics; most of my work now sits at the seam between Three.js rendering and agent runtimes, which is a place where very little tooling existed until recently. I maintain the project day to day: triage, reviews, releases, and docs.
+
+**Project Name:** `three.ws`
+
+**Project Repo Link:** `github.com/nirholas/three.ws`
+
+**Stream Date:** "Not yet" (unless the owner already booked at https://gh.io/osf-booking)
+
+**Dates:** leave blank unless booked
+
+**Twitter URL:** `@nichxbt`
+
+**LinkedIn URL:** owner to supply, or leave blank
+
+**Additional Information:**
+> three.ws turns a text prompt into a rigged, animation-ready 3D avatar and lets you drop it into any website with a single web component tag. It is browser-native (Three.js, glTF/GLB, no plugin, no game engine), and it ships an MCP server so coding agents can create and control avatars directly.
+>
+> What I would like to show live:
+> 1. Prompt to rigged avatar in about a minute, then the same avatar animated by our retargeting layer.
+> 2. Embedding it on a blank HTML page with one `<agent-3d>` tag, and driving its mood and animation from page JavaScript.
+> 3. The part I most want contributors on: universal rig support. Every humanoid GLB in the wild uses a different bone naming convention (Mixamo, VRM, Daz, MakeHuman, Unreal, MikuMikuDance, plain Blender, and a dozen more). We map them all to one canonical skeleton so a shared clip library retargets onto anything. Adding a convention is a genuinely self-contained first contribution: a mapping entry, a test, and a docs row. We keep a curated list of them open, each naming the file to change and the command that proves it worked, and I would like to do one live on the stream.
+>
+> Community: GitHub Discussions, a Telegram community, an X community, an IBM Community group, and a public changelog that ships to a Telegram channel on every release. Contributor onboarding and our triage process, including the response times we hold ourselves to, are documented at /docs/first-contribution and /docs/triage. Happy to pre-record if a Friday slot is tight, though live is preferred.
+
+**Follow-up:** reply to Andrea's thread on X with the issue link once it is open. She asked for the issue; closing that loop publicly is the point.
+
+---
+
+## 4. Stream runsheet (45 to 60 min, live at 1:00 PM ET)
+
+Demo early, code live, end with a concrete ask.
+
+| Time | Segment | Notes |
+|---|---|---|
+| 0:00-0:05 | Intro, who I am, what three.ws is | One sentence, then get to pixels |
+| 0:05-0:12 | Live demo: prompt to rigged avatar | Real generation, no pre-baked cache. Fallback GLB staged in case a worker is slow |
+| 0:12-0:20 | Embed it: one tag on a blank page | Blank `index.html` in a live editor, add `<agent-3d>`, avatar appears, drive mood from the console |
+| 0:20-0:28 | Under the hood: canonical skeleton and retargeting | The technical spine of the project, and the setup for the contribution ask |
+| 0:28-0:42 | Live contribution: add a rig convention | Take [#110](https://github.com/nirholas/three.ws/issues/110) or [#111](https://github.com/nirholas/three.ws/issues/111) live: write the mapping, write the test, run `npx vitest run tests/glb-canonicalize.test.js`, open the PR on air |
+| 0:42-0:50 | MCP server: an agent creating an avatar | Ties into the AI-agent audience the program has leaned toward in 2026 |
+| 0:50-0:60 | How to contribute, good first issues, Q&A | End on the issue list, on screen, by number |
+
+**Prep checklist:** clean clone on a second machine or a fresh worktree so the demo path is the one a viewer gets; workers warm; fallback GLB staged; browser zoom up for readability; no `.env` and no wallet UI on screen at any point.
+
+**Downplay on stream:** the on-chain and payments surfaces. They are real and they are in the repo, but this audience is maintainers and contributors, and leading with crypto costs credibility with exactly the people we want opening PRs. If it comes up, one honest sentence: agents can hold a wallet and pay for their own compute, it is optional, here is where the code lives.
+
+---
+
+## 5. What GitHub's own account tells us about promotion
+
+Analysis of 500 posts from @GitHubCommunity (`GitHubCommunity_tweets_2026-08-21.json`, scraped 2026-08-21). Engagement scored as likes + 3x retweets + replies.
+
+**Media is the single biggest lever.**
+
+| Format | Posts | Avg engagement | Median |
+|---|---|---|---|
+| Image | 73 | 31.0 | 13 |
+| Link card | 30 | 27.4 | 12 |
+| Video | 37 | 20.6 | 8 |
+| Plain text | 360 | 10.5 | 8 |
+
+An image post averages roughly 3x a plain text post on that account.
+
+**Their own OSF announcements are underpowered, and that is our opening.**
+
+141 posts mention Open Source Friday. 134 are the same bare template: `Open Source Friday with <Project>` plus a broadcast link, averaging 9.9 engagement. The 7 carrying an image or video average 16.4. The yearly trend on OSF posts is straight down: 16.6 (2023), 10.5 (2024), 8.7 (2025), 7.1 (2026 to date). Their whole account fell the same way, 27.5 in 2022 to 6.4 in 2026.
+
+Read: **do not rely on GitHub's post to carry the episode.** Their announcement will be a plain link reaching a few hundred views. Reach has to come from our side, and our post is the one that should have the video.
+
+**What actually broke out for them** (the top of the 500): projects with visible output. Game Off showcases with playable browser games (146 likes, 40 K views), Godot game roundups (126 likes, 73 K views), an open source game launch with a funding pool (90 likes, 23 RTs). Every one is "here is a thing you can look at, and then go run yourself". That is our shape exactly: a 3D avatar is a screenshot that explains itself. The second cluster is calls to action with a deadline (Git Merge CFP, conference booth applications, 30 to 48 engagement each).
+
+**Post plan around the episode** (finals go in `docs/x-posts/`, one file each, per repo convention):
+
+1. **T-14, application:** "We just applied to be on GitHub's Open Source Friday" plus the issue link and the 45-second demo clip. Reply into Andrea's thread rather than posting cold.
+2. **T-7, the ask:** the `good first issue` list as a readable numbered image, CTA to claim one before the stream so we can review it live. This is the Git Merge CFP pattern, their best-performing non-showcase format.
+3. **T-1, reminder:** short, image, exact time in ET plus one converted timezone, Twitch link.
+4. **T-0, live:** quote-post GitHub's announcement the minute it goes up, so our audience gets it with a face on it instead of a bare link.
+5. **T+1, replay:** the best 30 seconds of the stream as a standalone clip, plus the merged PR from the live contribution segment. The replay clip usually outperforms the live post because it is watchable on its own.
+
+Every one carries an image or video. No plain-text posts in this sequence. Cross-post each to the [X community](https://x.com/i/communities/1923523161230078106) and the [Telegram community](https://t.me/three_ws_community); the IBM Community group gets the T-7 and T+1 posts only, since it is an enterprise audience and reminder spam reads badly there.
+
+---
+
+## 6. Timeline
+
+Every hard criterion is met. What remains is polish and scheduling.
+
+| Date | Milestone | Owner |
+|---|---|---|
+| 2026-08-21 | Community docs, triage, onboarding, six curated issues, labels, MMD rig support | Done |
+| 2026-08-21 | Relicensed to Apache-2.0: LICENSE, NOTICE, 102 manifests, README, changelog | Done |
+| 2026-08-22 | Post the three seeded Discussions, pin the Welcome post | Owner, 60 seconds |
+| 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-28+ | Booking link arrives on approval, book the slot | Owner |
+| ~2026-09-11 | Stream (earliest date satisfying the two-week rule) | Owner |
+
+---
+
+## 7. Open questions for the owner
+
+One, and it is genuinely yours to call:
+
+**Fridays 1:00 PM ET: live or pre-recorded?** The form allows either. Live is better for the contributor-pipeline story, because the live-contribution segment is the whole pitch.
+
+The license question that used to sit here is resolved: Apache-2.0, shipped 2026-08-21.
+
+---
+
+<a id="sec-310"></a>
> **Source:** `docs/openai-listing-channels.md` · [↑ table of contents](#table-of-contents)
@@ -70158,7 +70907,7 @@ A confirmed canary asset shows `inCollection=true`, `royalty=500bps`, `attrs=11`
Every route to getting three.ws published on an OpenAI-owned surface, ranked by leverage, with the concrete blocker on each. Written 2026-08-17 after auditing the stalled Cookbook PR.
-Related docs: [listings.md](#sec-265) (every listing across all vendors), [mcp.md](#sec-277) (the hosted MCP server a plugin submission depends on), [nvidia-apps-catalog-listing.md](#sec-294) (the same kind of kit for NVIDIA).
+Related docs: [listings.md](#sec-269) (every listing across all vendors), [mcp.md](#sec-281) (the hosted MCP server a plugin submission depends on), [nvidia-apps-catalog-listing.md](#sec-298) (the same kind of kit for NVIDIA).
---
@@ -70188,7 +70937,7 @@ The gating requirement is a public, production MCP server. Most submitters have
| Requirement | What we already have |
|---|---|
-| Public MCP server | `https://three.ws/api/mcp`, Streamable HTTP, MCP `2025-06-18` ([mcp.md](#sec-277)) |
+| Public MCP server | `https://three.ws/api/mcp`, Streamable HTTP, MCP `2025-06-18` ([mcp.md](#sec-281)) |
| Auth | OAuth 2.1 end-user flow, with `api/mcp/.well-known/oauth-protected-resource` discovery already routed in `vercel.json` |
| Verified website | three.ws, live on Cloud Run behind the production LB |
| Privacy policy and terms | Live pages, already declared in `data/pages.json` |
@@ -70208,7 +70957,7 @@ Six sections: **Info** (name, short and long description, logo, category, URLs,
### Scoping decision: submit one plugin, not thirty-seven
-The guidelines reject "overly generic single-word names unlinked to your brand" and reward apps that are "tightly scoped." Thirty-seven separate MCP servers submitted individually reads as directory spam and most would fail the tightly-scoped test on their own. Submit **one three.ws plugin whose tools are the text-to-3D and avatar pipeline**, which is the thing no one else in the directory does. The rest stay available as direct MCP connections documented in [mcp.md](#sec-277).
+The guidelines reject "overly generic single-word names unlinked to your brand" and reward apps that are "tightly scoped." Thirty-seven separate MCP servers submitted individually reads as directory spam and most would fail the tightly-scoped test on their own. Submit **one three.ws plugin whose tools are the text-to-3D and avatar pipeline**, which is the thing no one else in the directory does. The rest stay available as direct MCP connections documented in [mcp.md](#sec-281).
### Known rejection reasons to design against
@@ -70296,7 +71045,7 @@ Not OpenAI-owned, so they do not answer the original question, but they are wher
---
-<a id="sec-306"></a>
+<a id="sec-311"></a>
> **Source:** `docs/openai-pr/00-START-HERE.md` · [↑ table of contents](#table-of-contents)
@@ -70339,13 +71088,13 @@ the specific gaps that would fail review or embarrass us in front of OpenAI.
| # | Brief | Priority | Blocks submit? |
| --- | --- | --- | --- |
-| 01 | [Resolve the orphaned studio-viewer widget](#sec-307) | P0 | Done 2026-07-18 (Option A: deleted) |
-| 02 | [Reconcile the served `.well-known` manifests with the zero-payment claim](#sec-308) | P0 | Yes (reviewer-discoverable crypto surface) |
-| 03 | [Make the `forge_free` tier story true everywhere](#sec-309) | P1 | Yes (submission doc contradicts code) |
-| 04 | [Close the test gaps on the ChatGPT-facing surface](#sec-310) | P1 | No, but required for "done" |
-| 05 | [Serve the custom-GPT OpenAPI and align legal URLs](#sec-311) | P1 | Partial |
-| 06 | [Fix doc accuracy and reconcile the tool-count story](#sec-312) | P1 | No |
-| 07 | [Final live verification and submit checklist](#sec-313) | P2 (runs last) | Yes (the actual go/no-go) |
+| 01 | [Resolve the orphaned studio-viewer widget](#sec-312) | P0 | Done 2026-07-18 (Option A: deleted) |
+| 02 | [Reconcile the served `.well-known` manifests with the zero-payment claim](#sec-313) | P0 | Yes (reviewer-discoverable crypto surface) |
+| 03 | [Make the `forge_free` tier story true everywhere](#sec-314) | P1 | Yes (submission doc contradicts code) |
+| 04 | [Close the test gaps on the ChatGPT-facing surface](#sec-315) | P1 | No, but required for "done" |
+| 05 | [Serve the custom-GPT OpenAPI and align legal URLs](#sec-316) | P1 | Partial |
+| 06 | [Fix doc accuracy and reconcile the tool-count story](#sec-317) | P1 | No |
+| 07 | [Final live verification and submit checklist](#sec-318) | P2 (runs last) | Yes (the actual go/no-go) |
Run 02 and 03 first of what remains (01 is already done; they change code and docs the later tasks depend on). 04, 05,
06 can run in parallel after. 07 runs last, after everything else is merged.
@@ -70393,7 +71142,7 @@ These are non-negotiable and OVERRIDE any default behavior:
---
-<a id="sec-307"></a>
+<a id="sec-312"></a>
> **Source:** `docs/openai-pr/01-orphan-widget-resolution.md` · [↑ table of contents](#table-of-contents)
@@ -70401,7 +71150,7 @@ These are non-negotiable and OVERRIDE any default behavior:
> **Resolved 2026-07-18 via Option A** in commit `19c379125` ("Refactor apps-sdk studio viewer and update OpenAI store submission"): `apps-sdk/studio-viewer/src.js`, `scripts/build-apps-sdk-viewer.mjs`, the `build:apps-sdk-viewer` entry in `package.json`, and both generated artifacts under `public/apps-sdk/` were deleted, and `apps-sdk/README.md` plus `ARCHITECTURE.md` were rewritten to point at the real widget (`api/_mcp-studio/component.js`, resource `ui://widget/three-studio-model.html`). `STRUCTURE.md` never referenced the orphan, so it needed no change. Kept as the record of the finding; the file links below point at the now-deleted paths and are left as plain code references.
-Read [`00-START-HERE.md`](#sec-306) first for the shared rules and the map.
+Read [`00-START-HERE.md`](#sec-311) first for the shared rules and the map.
## The problem (verified, with evidence)
@@ -70521,13 +71270,13 @@ fetches from** (three.ws, the R2 storage origin, and the CDN if used). Match wha
---
-<a id="sec-308"></a>
+<a id="sec-313"></a>
> **Source:** `docs/openai-pr/02-wellknown-manifest-conflict.md` · [↑ table of contents](#table-of-contents)
# Task 02 — Reconcile the served `.well-known` manifests with the zero-payment claim (P0)
-Read [`00-START-HERE.md`](#sec-306) first. **This task touches a manifest
+Read [`00-START-HERE.md`](#sec-311) first. **This task touches a manifest
that references crypto/x402. The commit gate in `00-START-HERE.md` rule 7 applies:
do the work, but do NOT commit anything that references a non-$THREE crypto project
without explicit owner approval. Flag it in your report instead.**
@@ -70642,13 +71391,13 @@ manifest layer. Recommended approach (implement this unless you find it wrong):
---
-<a id="sec-309"></a>
+<a id="sec-314"></a>
> **Source:** `docs/openai-pr/03-forge-free-tier-truth.md` · [↑ table of contents](#table-of-contents)
# Task 03 — Make the `forge_free` tier story true everywhere (P1, blocks submit)
-Read [`00-START-HERE.md`](#sec-306) first.
+Read [`00-START-HERE.md`](#sec-311) first.
## The problem (verified, with evidence)
@@ -70690,8 +71439,8 @@ metadata surface say "standard by default, higher tiers available on request."
description matches the code: standard default, `tier` param lets the caller ask
for draft or high, high may take longer or degrade under load.
2. Grep every doc for the "highest quality"/"high tier by default" claim and fix each:
- [`docs/mcp-studio.md`](#sec-274),
- [`docs/mcp-3d-studio.md`](#sec-271), the tool descriptions the
+ [`docs/mcp-studio.md`](#sec-278),
+ [`docs/mcp-3d-studio.md`](#sec-275), the tool descriptions the
MCP server itself returns in `tools/list` (check `tools.js` tool metadata strings),
and `apps-sdk/README.md`.
3. Make sure the tool's own `description` string returned to ChatGPT is accurate, so
@@ -70744,13 +71493,13 @@ and a doc claiming it works.
---
-<a id="sec-310"></a>
+<a id="sec-315"></a>
> **Source:** `docs/openai-pr/04-openai-surface-test-coverage.md` · [↑ table of contents](#table-of-contents)
# Task 04 — Close the test gaps on the ChatGPT-facing surface (P1)
-Read [`00-START-HERE.md`](#sec-306) first.
+Read [`00-START-HERE.md`](#sec-311) first.
## The problem
@@ -70830,13 +71579,13 @@ exported per the file). Use an existing JSON-schema/OpenAPI validator already in
---
-<a id="sec-311"></a>
+<a id="sec-316"></a>
> **Source:** `docs/openai-pr/05-custom-gpt-openapi-serving.md` · [↑ table of contents](#table-of-contents)
# Task 05 — Serve the custom-GPT OpenAPI and align legal URLs (P1)
-Read [`00-START-HERE.md`](#sec-306) first. Coordinate with Task 02 (the
+Read [`00-START-HERE.md`](#sec-311) first. Coordinate with Task 02 (the
served schema must be payment-free) and Task 04 (a contract test binds to it).
## The problem (verified, with evidence)
@@ -70919,13 +71668,13 @@ be normalized to one canonical form.
---
-<a id="sec-312"></a>
+<a id="sec-317"></a>
> **Source:** `docs/openai-pr/06-docs-accuracy-reconciliation.md` · [↑ table of contents](#table-of-contents)
# Task 06 — Fix doc accuracy and reconcile the tool-count story (P1)
-Read [`00-START-HERE.md`](#sec-306) first. This task cleans up the
+Read [`00-START-HERE.md`](#sec-311) first. This task cleans up the
documentation drift the audit found, EXCEPT the two docs owned by other tasks
(`apps-sdk/README.md` was Task 01, already landed on 2026-07-18; the `forge_free` tier
claim is Task 03). Do not fight those tasks for those specific edits; coordinate.
@@ -71001,13 +71750,13 @@ claim is Task 03). Do not fight those tasks for those specific edits; coordinate
---
-<a id="sec-313"></a>
+<a id="sec-318"></a>
> **Source:** `docs/openai-pr/07-final-verification-and-submit.md` · [↑ table of contents](#table-of-contents)
# Task 07 — Final live verification and submit checklist (P2, runs last)
-Read [`00-START-HERE.md`](#sec-306) first. **Run this only after tasks
+Read [`00-START-HERE.md`](#sec-311) first. **Run this only after tasks
01-06 are merged.** This is the go/no-go gate before the app is submitted to OpenAI.
## Purpose
@@ -71095,7 +71844,7 @@ go/no-go report. Do not submit; prepare so the human's final submit is one actio
---
-<a id="sec-314"></a>
+<a id="sec-319"></a>
> **Source:** `docs/oracle-trading-mcp-plan.md` · [↑ table of contents](#table-of-contents)
@@ -71315,7 +72064,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-530). Written before
+Draft lives at [`docs/oracle-trading-mcp-x-post.md`](#sec-537). 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.
@@ -71349,7 +72098,7 @@ than shipping late.
---
-<a id="sec-315"></a>
+<a id="sec-320"></a>
> **Source:** `docs/oracle.md` · [↑ table of contents](#table-of-contents)
@@ -71753,7 +72502,7 @@ The more data we watch, the sharper every score. Oracle is live now.
---
-<a id="sec-316"></a>
+<a id="sec-321"></a>
> **Source:** `docs/overlay-audit.md` · [↑ table of contents](#table-of-contents)
@@ -71924,7 +72673,7 @@ only worth calling from a test.
---
-<a id="sec-317"></a>
+<a id="sec-322"></a>
> **Source:** `docs/package-extraction.md` · [↑ table of contents](#table-of-contents)
@@ -72053,7 +72802,7 @@ part of the extraction itself: extract and publish first, swap the import later.
---
-<a id="sec-318"></a>
+<a id="sec-323"></a>
> **Source:** `docs/partners.md` · [↑ table of contents](#table-of-contents)
@@ -72061,7 +72810,7 @@ part of the extraction itself: extract and publish first, swap the import later.
`three.ws/partners` is the public map of the cloud, AI, hardware, infrastructure, and media programmes three.ws takes part in. This doc is the developer-facing companion to that page: for each surface it says what the integration actually **is**, at the status the page and the per-partner docs claim, and links the doc that goes deeper.
-Page source: [`pages/partners.html`](../pages/partners.html). Partnership enquiries go to **[email protected]** (the page's "Become a partner" call to action). Press and brand requests go to **[email protected]**, covered in [Press kit](#sec-333).
+Page source: [`pages/partners.html`](../pages/partners.html). Partnership enquiries go to **[email protected]** (the page's "Become a partner" call to action). Press and brand requests go to **[email protected]**, covered in [Press kit](#sec-338).
**Read the status labels literally.** Each card carries a one-word tier chip that is a category, not a rank: Select Partner, Strategic, Cloud, Inception, Media, Infrastructure. Nothing on the page grants an endorsement, and several of the docs below carry explicit "this is not an endorsement" language that must survive any rewrite.
@@ -72071,14 +72820,14 @@ Page source: [`pages/partners.html`](../pages/partners.html). Partnership enquir
| Partner | Chip on the card | Card links to | Deeper docs |
|---|---|---|---|
-| OpenAI | Select Partner | `/openai` | [MCP 3D Studio (free)](#sec-274), [3D Studio (paid)](#sec-271), [Custom GPT config](#sec-138), [AR in ChatGPT](#sec-139), [Spatial MCP](#sec-395) |
-| IBM | Strategic | `/blog/three-ws-ibm-business-partner` | [IBM watsonx and Granite](#sec-250), [IBM Granite x402 MCP](#sec-249) |
+| OpenAI | Select Partner | `/openai` | [MCP 3D Studio (free)](#sec-278), [3D Studio (paid)](#sec-275), [Custom GPT config](#sec-138), [AR in ChatGPT](#sec-139), [Spatial MCP](#sec-400) |
+| IBM | Strategic | `/blog/three-ws-ibm-business-partner` | [IBM watsonx and Granite](#sec-253), [IBM Granite x402 MCP](#sec-252) |
| Amazon Web Services | Cloud | `/aws` | [AWS Marketplace](#sec-123), [listing kit](#sec-122), [partner spotlight](#sec-124) |
| Google Cloud | Cloud | `/blog/three-ws-google-cloud-partnership` | [Production runbook](ops/gcp-production.md), [credits plan](ops/gcp-credits-plan.md), [model workers](ops/gcp-model-workers.md) |
-| Alibaba Cloud | Cloud | `/blog/three-ws-alibaba-cloud-partnership` | [Listings and distribution](#sec-265), [the model router](#sec-130) |
-| NVIDIA | Inception | `/nvidia` | [NVIDIA Inception](#sec-296), [NVIDIA models](#sec-297), [Nemotron spotlight](#sec-299) |
-| HackerNoon | Media | `/blog/three-ws-hackernoon-partnership` | [Syndication](#sec-402), [Listings and distribution](#sec-265) |
-| Quicknode | Infrastructure | `/blog/three-ws-quicknode-startup-program` | [Solana integration](#sec-394), [Listings and distribution](#sec-265) |
+| Alibaba Cloud | Cloud | `/blog/three-ws-alibaba-cloud-partnership` | [Listings and distribution](#sec-269), [the model router](#sec-130) |
+| NVIDIA | Inception | `/nvidia` | [NVIDIA Inception](#sec-300), [NVIDIA models](#sec-301), [Nemotron spotlight](#sec-303) |
+| HackerNoon | Media | `/blog/three-ws-hackernoon-partnership` | [Syndication](#sec-407), [Listings and distribution](#sec-269) |
+| Quicknode | Infrastructure | `/blog/three-ws-quicknode-startup-program` | [Solana integration](#sec-399), [Listings and distribution](#sec-269) |
The page's stat bar reads 8 partners, 22 chains, and an infinity glyph for scale. It is marked `aria-hidden` and is decorative framing, not a metric to quote.
@@ -72090,13 +72839,13 @@ The page's stat bar reads 8 partners, 22 chains, and an infinity glyph for scale
**What the integration is.**
-- **The keyless connector** at `https://three.ws/api/mcp-studio` is a free MCP server exposing only 3D generation tools: no account, no payment, no API key, no wallet, no token. That is the surface submitted to the ChatGPT App Directory. See [MCP 3D Studio](#sec-274).
-- **The paid sibling** at `https://three.ws/api/mcp-3d` is a separate server with rigging, animation, retexturing, and analysis, authenticated by OAuth 2.1 or paid per call over x402. It shares none of the keyless server's surface. See [3D Studio MCP](#sec-271).
+- **The keyless connector** at `https://three.ws/api/mcp-studio` is a free MCP server exposing only 3D generation tools: no account, no payment, no API key, no wallet, no token. That is the surface submitted to the ChatGPT App Directory. See [MCP 3D Studio](#sec-278).
+- **The paid sibling** at `https://three.ws/api/mcp-3d` is a separate server with rigging, animation, retexturing, and analysis, authenticated by OAuth 2.1 or paid per call over x402. It shares none of the keyless server's surface. See [3D Studio MCP](#sec-275).
- **The custom GPT** in the GPT Store calls an Actions contract served from `/.well-known/3d-studio-openapi.yaml`. Its builder configuration is checked in, because the GPT itself is configured by hand: [Custom GPT config](#sec-138).
- **AR handoff** works from any of these: every generation carries a place-in-your-room link, and the whole pipeline is public and keyless rather than ChatGPT-exclusive. See [AR in ChatGPT](#sec-139).
-- **Spatial MCP** is the open, CC0 response shape that makes a 3D scene a native MCP result instead of a URL in text. three.ws is the reference implementation; the shape is renderer-agnostic and carries no payment, wallet, or coin surface. See [Spatial MCP](#sec-395).
+- **Spatial MCP** is the open, CC0 response shape that makes a 3D scene a native MCP result instead of a URL in text. three.ws is the reference implementation; the shape is renderer-agnostic and carries no payment, wallet, or coin surface. See [Spatial MCP](#sec-400).
-**Saying it correctly.** Write the status as "OpenAI Select Partner". three.ws is an independent member of the network at the Select tier: not an OpenAI product, and not endorsed by OpenAI beyond the partner designation. Badge rules, the required independence line, and every asset are in [`marketing/openai-select-partner/badge-usage.md`](../marketing/openai-select-partner/badge-usage.md); the graphics cleared for editorial use are in [Press kit](#sec-333). The pre-submission verification pack is [`docs/openai-pr/00-START-HERE.md`](#sec-306).
+**Saying it correctly.** Write the status as "OpenAI Select Partner". three.ws is an independent member of the network at the Select tier: not an OpenAI product, and not endorsed by OpenAI beyond the partner designation. Badge rules, the required independence line, and every asset are in [`marketing/openai-select-partner/badge-usage.md`](../marketing/openai-select-partner/badge-usage.md); the graphics cleared for editorial use are in [Press kit](#sec-338). The pre-submission verification pack is [`docs/openai-pr/00-START-HERE.md`](#sec-311).
---
@@ -72104,9 +72853,9 @@ The page's stat bar reads 8 partners, 22 chains, and an infinity glyph for scale
**What the page claims.** three.ws 3D agent identity and x402 payment rails integrate with IBM watsonx and IBM Granite. Agents run enterprise AI models while maintaining on-chain identity and executing real micropayments, all from a single agent profile. Card tags: watsonx.ai, Granite, x402, MCP.
-**What the integration is.** Agents can think on IBM Granite foundation models served through IBM watsonx.ai, using your own IBM Cloud credentials. On top of that runtime sit the Granite-backed API surfaces (avatar brain, Guardian trust layer, TimeSeries forecasting, digital twin, semantic discovery, vision) and an MCP server, all documented in [IBM watsonx and Granite](#sec-250). [IBM Granite x402 MCP](#sec-249) covers the pay-per-call path: an MCP client reaches Granite inference and settles per call in stablecoin from a wallet it already controls, with no IBM Cloud account of its own.
+**What the integration is.** Agents can think on IBM Granite foundation models served through IBM watsonx.ai, using your own IBM Cloud credentials. On top of that runtime sit the Granite-backed API surfaces (avatar brain, Guardian trust layer, TimeSeries forecasting, digital twin, semantic discovery, vision) and an MCP server, all documented in [IBM watsonx and Granite](#sec-253). [IBM Granite x402 MCP](#sec-252) covers the pay-per-call path: an MCP client reaches Granite inference and settles per call in stablecoin from a wallet it already controls, with no IBM Cloud account of its own.
-**The caveat that must not be dropped.** [`docs/ibm.md`](#sec-250) states it plainly: three.ws is an IBM Business Partner, but the public showcase is not the partnership. The `/api/ibm/*` tools are an independent set of developer tools built on IBM's publicly available Granite models. They are not official IBM partnership deliverables, not IBM products, and not endorsed by IBM. The formal partnership work is being built on the IBM platform and is not yet public. Never present the public demos as that work.
+**The caveat that must not be dropped.** [`docs/ibm.md`](#sec-253) states it plainly: three.ws is an IBM Business Partner, but the public showcase is not the partnership. The `/api/ibm/*` tools are an independent set of developer tools built on IBM's publicly available Granite models. They are not official IBM partnership deliverables, not IBM products, and not endorsed by IBM. The formal partnership work is being built on the IBM platform and is not yet public. Never present the public demos as that work.
Live product surfaces: `three.ws/ibm/hello` (the partnership page) and `three.ws/ibm/x402-demo` (the x402 live demo).
@@ -72122,7 +72871,7 @@ Live product surfaces: `three.ws/ibm/hello` (the partnership page) and `three.ws
- The `/partners` card says "Marketplace availability".
- The `/aws` page badge says "AWS Partner, Software Path" and its hero says "Marketplace listing coming soon".
-- [`docs/listings.md`](#sec-265) records AWS Marketplace as Live and three.ws as an AWS Partner.
+- [`docs/listings.md`](#sec-269) records AWS Marketplace as Live and three.ws as an AWS Partner.
- [`docs/aws-marketplace-listing-kit.md`](#sec-122) says the backend integration is built and deployed but the listing itself has not yet been created in the AWS Marketplace Management Portal.
Do not resolve that spread by picking the strongest claim. If you need one sentence, the safe one is the one the product page uses: three.ws is an AWS Partner, and the Marketplace listing is coming. Longer-form pieces written for AWS channels are [partner spotlight](#sec-124), [MCP agents](#sec-120), and [Marketplace metering in front of x402](#sec-119).
@@ -72135,7 +72884,7 @@ Do not resolve that spread by picking the strongest claim. If you need one sente
**What the integration is.** Production runs on Google Cloud: one Cloud Run service serves the static frontend, the route table, and every API handler, with the crons on Cloud Scheduler and the GPU model workers on their own services. Vertex AI provides the Gemini and image lanes. The operational detail is in [production runbook](ops/gcp-production.md), [fleet and quota plan](ops/gcp-credits-plan.md), and [model workers](ops/gcp-model-workers.md).
-**Programme status.** [`docs/listings.md`](#sec-265) records three.ws as a **member of Google Cloud for Web3 Startups**, with the programme backing compute and Vertex AI usage, and records Google Cloud Marketplace separately as **open to partnership** (no listing yet). The page card describes the technical dependency, not a marketplace listing; keep those two apart.
+**Programme status.** [`docs/listings.md`](#sec-269) records three.ws as a **member of Google Cloud for Web3 Startups**, with the programme backing compute and Vertex AI usage, and records Google Cloud Marketplace separately as **open to partnership** (no listing yet). The page card describes the technical dependency, not a marketplace listing; keep those two apart.
---
@@ -72145,7 +72894,7 @@ Do not resolve that spread by picking the strongest claim. If you need one sente
**What the integration is.** Qwen models are first-class lanes in the platform's multi-model brain router (`/api/brain/chat`), reached through DashScope alongside the other providers, so an agent can be pointed at a Qwen model the same way it is pointed at any other. See [the agent brain](#sec-130) for the router and the model ids.
-**Listing status.** [`docs/listings.md`](#sec-265) records the Alibaba Cloud International Marketplace listing as **Live**, with a product listing, a storefront, and an editorial feature published on the Alibaba Cloud Marketplace blog. That doc holds the canonical links; treat it as the source of truth rather than restating URLs here.
+**Listing status.** [`docs/listings.md`](#sec-269) records the Alibaba Cloud International Marketplace listing as **Live**, with a product listing, a storefront, and an editorial feature published on the Alibaba Cloud Marketplace blog. That doc holds the canonical links; treat it as the source of truth rather than restating URLs here.
---
@@ -72155,10 +72904,10 @@ Do not resolve that spread by picking the strongest claim. If you need one sente
**What the integration is.** Two distinct things, and the docs keep them distinct:
-- **Inception membership**, accepted July 2026. [NVIDIA Inception](#sec-296) states what membership adds (GPU credits, hardware access, engineering support) and where it shows up in the product.
-- **The free hosted inference lane.** A large share of platform AI runs on NVIDIA-hosted models unlocked by a single `NVIDIA_API_KEY`, a rate-limited free tier with no per-model billing and no SLA, which is why the platform always keeps a fallback behind it. [NVIDIA models](#sec-297) is the canonical map of which model does what and where it is wired. Membership does not change that lane; it is how the platform scales past free-tier limits without giving up the free-first design.
+- **Inception membership**, accepted July 2026. [NVIDIA Inception](#sec-300) states what membership adds (GPU credits, hardware access, engineering support) and where it shows up in the product.
+- **The free hosted inference lane.** A large share of platform AI runs on NVIDIA-hosted models unlocked by a single `NVIDIA_API_KEY`, a rate-limited free tier with no per-model billing and no SLA, which is why the platform always keeps a fallback behind it. [NVIDIA models](#sec-301) is the canonical map of which model does what and where it is wired. Membership does not change that lane; it is how the platform scales past free-tier limits without giving up the free-first design.
-[Nemotron spotlight](#sec-299) is a published community piece on building the text-to-3D pipeline on NIM. It is a developer-blog showcase, not a partnership document.
+[Nemotron spotlight](#sec-303) is a published community piece on building the text-to-3D pipeline on NIM. It is a developer-blog showcase, not a partnership document.
---
@@ -72166,15 +72915,15 @@ Do not resolve that spread by picking the strongest claim. If you need one sente
**What the page claims.** A builder-focused publishing partnership: feature articles, tutorials, and developer guides for people shipping with AI, published to HackerNoon's developer audience. Card tags: Publishing, Developer content.
-**What the integration is.** Mechanical, and worth knowing if you write posts here: HackerNoon auto-imports from `https://three.ws/rss/announcements.xml`, polls roughly hourly, pulls every new item into the drafts queue, and publishes with canonical URLs pointing back to three.ws. There is no per-post action. Setup steps and the author-profile claim flow are in [Syndication](#sec-402); the listing row is in [Listings and distribution](#sec-265).
+**What the integration is.** Mechanical, and worth knowing if you write posts here: HackerNoon auto-imports from `https://three.ws/rss/announcements.xml`, polls roughly hourly, pulls every new item into the drafts queue, and publishes with canonical URLs pointing back to three.ws. There is no per-post action. Setup steps and the author-profile claim flow are in [Syndication](#sec-407); the listing row is in [Listings and distribution](#sec-269).
---
## Quicknode
-**What the page claims.** three.ws is a member of the Quicknode Startup Program with approved infrastructure credits. Quicknode's globally distributed RPC endpoints add capacity and redundancy to the chain access behind agent wallets, x402 settlement verification, and live Solana market data. Card tags: Solana RPC, Streams, Multi-chain. [`docs/listings.md`](#sec-265) records the programme as **accepted (2026-07)** with approved free infrastructure credits.
+**What the page claims.** three.ws is a member of the Quicknode Startup Program with approved infrastructure credits. Quicknode's globally distributed RPC endpoints add capacity and redundancy to the chain access behind agent wallets, x402 settlement verification, and live Solana market data. Card tags: Solana RPC, Streams, Multi-chain. [`docs/listings.md`](#sec-269) records the programme as **accepted (2026-07)** with approved free infrastructure credits.
-**What the integration is.** A rung in the Solana RPC failover chain, not the whole chain. Server-side calls build a chain across an explicit primary, keyed providers, operator-supplied fallbacks, keyless public endpoints, and a paid reserve tried last, rotating past anything rate-limited. [Solana integration](#sec-394) documents it, including the trap that matters operationally: never name the same endpoint as both the primary and the last-resort reserve, because the chain dedupes by URL and keeps the first occurrence, so the "reserve" silently absorbs all traffic.
+**What the integration is.** A rung in the Solana RPC failover chain, not the whole chain. Server-side calls build a chain across an explicit primary, keyed providers, operator-supplied fallbacks, keyless public endpoints, and a paid reserve tried last, rotating past anything rate-limited. [Solana integration](#sec-399) documents it, including the trap that matters operationally: never name the same endpoint as both the primary and the last-resort reserve, because the chain dedupes by URL and keeps the first occurrence, so the "reserve" silently absorbs all traffic.
---
@@ -72182,7 +72931,7 @@ Do not resolve that spread by picking the strongest claim. If you need one sente
Worth stating, because partner claims drift upward when nobody writes the boundary down:
-- **No Intel, Microsoft, or Oracle programme appears on `/partners`.** [`docs/listings.md`](#sec-265) records Microsoft Azure Marketplace as **on roadmap**. Third-party model or component names that appear in the stack (for example the image-to-3D backends listed in [3D Studio MCP](#sec-271)) are technical dependencies, not partnerships.
+- **No Intel, Microsoft, or Oracle programme appears on `/partners`.** [`docs/listings.md`](#sec-269) records Microsoft Azure Marketplace as **on roadmap**. Third-party model or component names that appear in the stack (for example the image-to-3D backends listed in [3D Studio MCP](#sec-275)) are technical dependencies, not partnerships.
- **No tier is claimed beyond the chips on the cards.** "Strategic", "Cloud", "Media", and "Infrastructure" are groupings three.ws chose for its own page. Only two named programme statuses come from the partner: OpenAI Select Partner, and NVIDIA Inception member.
- **No endorsement is claimed anywhere.** OpenAI, IBM, and NVIDIA all carry explicit independence language in their docs. Reproduce it.
@@ -72196,14 +72945,14 @@ The page closes with four reasons, useful as the short pitch when someone asks:
## Related
-- [Press kit](#sec-333): marks, announcement graphics, boilerplate, and the rules for all of it
-- [Listings and distribution](#sec-265): marketplaces, ecosystem directories, and media partners with per-listing status
-- [Integrations](#sec-254): the catalog of ways to put an agent on a site you do not control
-- [x402](#sec-544): the payment rail behind the agent-to-agent micropayments every partner surface references
+- [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
---
-<a id="sec-319"></a>
+<a id="sec-324"></a>
> **Source:** `docs/partners/sperax-proposal.md` · [↑ table of contents](#table-of-contents)
@@ -72251,7 +73000,7 @@ Both sides already ship for a living — this proposal only asks each of us to d
---
-<a id="sec-320"></a>
+<a id="sec-325"></a>
> **Source:** `docs/pay-skills-listing.md` · [↑ table of contents](#table-of-contents)
@@ -72352,7 +73101,7 @@ are supported.
---
-<a id="sec-321"></a>
+<a id="sec-326"></a>
> **Source:** `docs/payment-sessions.md` · [↑ table of contents](#table-of-contents)
@@ -72804,13 +73553,13 @@ curl -s $BASE/api/credits -H "$AUTH" | jq .balance_usd
## Related
-- [x402 Protocol](#sec-544): the challenge / verify / settle mechanics behind every paid call.
-- [x402 Buyer Client](#sec-536): paying x402 endpoints from your own wallet instead of a session.
-- [x402 Developer Tools](#sec-537): free echo / debug / receipt-verification tools for debugging a paid call.
+- [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.
---
-<a id="sec-322"></a>
+<a id="sec-327"></a>
> **Source:** `docs/permissions.md` · [↑ table of contents](#table-of-contents)
@@ -73208,15 +73957,15 @@ Set `SMOKE_SKIP_REVOKE=1` to skip the on-chain revocation step if the test walle
- [Architecture Overview](#sec-100)
- [Agent System](#sec-064)
-- [ERC-8004 Blockchain Identity](#sec-188)
-- [Skill System](#sec-387)
+- [ERC-8004 Blockchain Identity](#sec-190)
+- [Skill System](#sec-392)
- [EIP-7710](https://eips.ethereum.org/EIPS/eip-7710) — delegation envelope format
- [EIP-7715](https://eips.ethereum.org/EIPS/eip-7715) — `wallet_grantPermissions` JSON-RPC method
- [MetaMask Delegation Toolkit](https://docs.metamask.io/delegation-toolkit/)
---
-<a id="sec-323"></a>
+<a id="sec-328"></a>
> **Source:** `docs/persona-hub.md` · [↑ table of contents](#table-of-contents)
@@ -73613,7 +74362,7 @@ JWT claims:
---
-<a id="sec-324"></a>
+<a id="sec-329"></a>
> **Source:** `docs/plan-checkout.md` · [↑ table of contents](#table-of-contents)
@@ -73629,7 +74378,7 @@ three.ws has a self-serve paid tier. Upgrading to **Pro** (or Team / Enterprise)
Where to use it: the Pro card on [three.ws/pricing](https://three.ws/pricing) opens the checkout when you're signed in. Confirmed payments set `users.plan`, light up the Pro badge everywhere ([api/_lib/account-tier.js](../api/_lib/account-tier.js)), and grant 30 days per payment.
-This is separate from (and complementary to) [hold-to-access](#sec-238), which derives holder tiers from $THREE you *hold*; the plan checkout is $THREE you *spend*.
+This is separate from (and complementary to) [hold-to-access](#sec-241), which derives holder tiers from $THREE you *hold*; the plan checkout is $THREE you *spend*.
---
@@ -73742,7 +74491,7 @@ Plan prices live in [api/payments/_config.js](../api/payments/_config.js) (`PLAN
---
-<a id="sec-325"></a>
+<a id="sec-330"></a>
> **Source:** `docs/play-boot-performance.md` · [↑ table of contents](#table-of-contents)
@@ -73752,7 +74501,7 @@ Plan prices live in [api/payments/_config.js](../api/payments/_config.js) (`PLAN
That work is unavoidable. What *is* avoidable is paying for it at the wrong moment. This document records the boot-cost invariants that keep the first ten seconds fast, so a future change does not quietly undo one of them. Each section names the regression it prevents, because each of them actually shipped once and was measured on the live site.
-Related docs: [how /play stays safe, honest, and light](#sec-327), [architecture](#sec-100).
+Related docs: [how /play stays safe, honest, and light](#sec-332), [architecture](#sec-100).
## How to measure before you claim anything
@@ -73845,7 +74594,7 @@ Before shipping anything that touches `/play` boot:
---
-<a id="sec-326"></a>
+<a id="sec-331"></a>
> **Source:** `docs/play-forge-in-world.md` · [↑ table of contents](#table-of-contents)
@@ -73947,12 +74696,12 @@ layer, ownership checks, and the per-player object cap all apply without modific
## Related
- [3D asset pipeline](#sec-002): what the forge lanes are and how they differ
-- [In-game economy](#sec-252): the rest of what you can do inside a `/play` world
+- [In-game economy](#sec-255): the rest of what you can do inside a `/play` world
- [/forge](https://three.ws/forge): the full studio, with paid tiers, rigging, and game-ready export
---
-<a id="sec-327"></a>
+<a id="sec-332"></a>
> **Source:** `docs/play-hardening.md` · [↑ table of contents](#table-of-contents)
@@ -73968,7 +74717,7 @@ It is also the surface with the least trusted input. Its entry URL is a link str
Every part of that URL, every display name a peer picks, and every field of the pump.fun coin metadata is text an attacker chose. This document records the invariants that keep the world safe and honest, so that a future change does not quietly undo one of them. Each section names the failure it prevents, because each of these actually shipped once.
-Related docs: [in-game economy](#sec-252), [architecture](#sec-100), [security](#sec-375).
+Related docs: [in-game economy](#sec-255), [architecture](#sec-100), [security](#sec-380).
---
@@ -74218,7 +74967,7 @@ The mobile harness is the one that catches memory regressions. It reports total
---
-<a id="sec-328"></a>
+<a id="sec-333"></a>
> **Source:** `docs/play-live-events.md` · [↑ table of contents](#table-of-contents)
@@ -74289,7 +75038,7 @@ from the shape below:
| `startsAt` / `endsAt` | ISO-8601 UTC. A missing or inverted `endsAt` defaults to six hours after the start. |
| `agenda[].atMin` | Minutes after `startsAt`. Order does not matter; segments are sorted. Invalid or untitled entries are dropped rather than breaking the event. |
| `agenda[].icon` | One emoji. Used on the segment row and its moment banner. |
-| `souvenir.cosmeticId` | Optional. A free commemorative wearable granted once to everyone who joins the world named by `link` while the event is live, kept forever, never granted again after `endsAt`. Must be a `tier: 'event'` cosmetic; anything else grants nothing. See [Event souvenirs](#sec-216). |
+| `souvenir.cosmeticId` | Optional. A free commemorative wearable granted once to everyone who joins the world named by `link` while the event is live, kept forever, never granted again after `endsAt`. Must be a `tier: 'event'` cosmetic; anything else grants nothing. See [Event souvenirs](#sec-218). |
`id`, `agenda`, and `tagline` are optional: an event with none of them still runs
its countdown, its go-live moment, and its fireworks.
@@ -74388,7 +75137,7 @@ Point it at another origin with `--base https://three.ws`.
---
-<a id="sec-329"></a>
+<a id="sec-334"></a>
> **Source:** `docs/play-vehicles.md` · [↑ table of contents](#table-of-contents)
@@ -74495,12 +75244,12 @@ and the metal-roughness map at 1024px, and writes
## Related
- [`/play` NPCs and world life](../src/game/npc/ambient-life.js) drives the ambient lane.
-- [The in-game economy](#sec-252) covers what you earn on those delivery runs.
-- [`/play` safety and lifecycle invariants](#sec-327).
+- [The in-game economy](#sec-255) covers what you earn on those delivery runs.
+- [`/play` safety and lifecycle invariants](#sec-332).
---
-<a id="sec-330"></a>
+<a id="sec-335"></a>
> **Source:** `docs/popular-3d-github-repos.md` · [↑ table of contents](#table-of-contents)
@@ -74763,7 +75512,7 @@ Apply a 3D-signal regex filter over `description + topics` and a denylist of non
---
-<a id="sec-331"></a>
+<a id="sec-336"></a>
> **Source:** `docs/portfolio.md` · [↑ table of contents](#table-of-contents)
@@ -74807,7 +75556,7 @@ GET /api/crypto/portfolio?address=<wallet>&chain=solana|ethereum
```
which builds on the same balance layer as
-[`/api/crypto/wallet`](#sec-169) ([`api/_lib/balances.js`](../api/_lib/balances.js)):
+[`/api/crypto/wallet`](#sec-171) ([`api/_lib/balances.js`](../api/_lib/balances.js)):
- **Solana** (fully keyless): Helius DAS when a key is configured, public RPC
otherwise; prices from Jupiter Lite with a pump.fun bonding-curve fallback;
@@ -74866,15 +75615,15 @@ responses are cached for about a minute per wallet.
## Related surfaces
-- [`/wallet`](#sec-488): your own custodial three.ws wallet.
+- [`/wallet`](#sec-494): your own custodial three.ws wallet.
- `/agent-wallet`: the agent wallet hub, whose Portfolio tab covers an agent's
holdings with FIFO cost basis and PnL attribution.
-- [`/api/crypto/wallet`](#sec-169): the raw balances endpoint this page
+- [`/api/crypto/wallet`](#sec-171): the raw balances endpoint this page
builds on, for agents and scripts.
---
-<a id="sec-332"></a>
+<a id="sec-337"></a>
> **Source:** `docs/premium.md` · [↑ table of contents](#table-of-contents)
@@ -75009,7 +75758,7 @@ tiers that remain free (news feed, digest, archive stats/trending).
---
-<a id="sec-333"></a>
+<a id="sec-338"></a>
> **Source:** `docs/press-kit.md` · [↑ table of contents](#table-of-contents)
@@ -75164,7 +75913,7 @@ Two rules that matter if you are laying out a story or a slide:
The two extra OpenAI files inside the zip need more care than the two above. The short-phrasing card exists for one specific post and is not the general-purpose announcement graphic. The two-mark lockup uses OpenAI's logomark rather than the partner badge, which their brand guidelines govern separately, so a co-branded lockup is normally something a partner clears first. The full rules for every OpenAI asset in this repo are in [`marketing/openai-select-partner/badge-usage.md`](../marketing/openai-select-partner/badge-usage.md), with the announcement pack itself at [`marketing/openai-select-partner/README.md`](../marketing/openai-select-partner/README.md).
-For the wider programme list and how to describe each one, see [Partner ecosystem](#sec-318).
+For the wider programme list and how to describe each one, see [Partner ecosystem](#sec-323).
---
@@ -75182,14 +75931,14 @@ Use that inbox for anything the page does not cover: a format that is not here (
## Related
-- [Partner ecosystem](#sec-318): every programme three.ws is in, at the status it actually claims
-- [Listings and distribution](#sec-265): marketplaces, directories, and media partners, with per-listing status
+- [Partner ecosystem](#sec-323): every programme three.ws is in, at the status it actually claims
+- [Listings and distribution](#sec-269): marketplaces, directories, and media partners, with per-listing status
- [Brand asset renderer](../marketing/brand/README.md): where the marks come from and how to regenerate them
- [Marketing campaigns](../marketing/README.md): announcement packs, social copy, and finished graphics
---
-<a id="sec-334"></a>
+<a id="sec-339"></a>
> **Source:** `docs/procedural-animation.md` · [↑ table of contents](#table-of-contents)
@@ -75365,7 +76114,7 @@ If you hit a rig whose bones do not resolve, the fix is a bone-name mapping in [
---
-<a id="sec-335"></a>
+<a id="sec-340"></a>
> **Source:** `docs/provenance.md` · [↑ table of contents](#table-of-contents)
@@ -75448,7 +76197,7 @@ Real hashing, real ed25519 signature, real on-chain write. Requires the issuer k
---
-<a id="sec-336"></a>
+<a id="sec-341"></a>
> **Source:** `docs/pump-claims-channel.md` · [↑ table of contents](#table-of-contents)
@@ -75605,7 +76354,7 @@ built yet.
---
-<a id="sec-337"></a>
+<a id="sec-342"></a>
> **Source:** `docs/pump-fun-mcp-edge.md` · [↑ table of contents](#table-of-contents)
@@ -75661,7 +76410,7 @@ Both runtimes import `TOOLS` from `src/pump/mcp-tools.js`, so the tool list expo
---
-<a id="sec-338"></a>
+<a id="sec-343"></a>
> **Source:** `docs/pump-launch-repos.md` · [↑ table of contents](#table-of-contents)
@@ -75760,7 +76509,7 @@ rate-limits under the ~450 txs a full run makes. Pass a dedicated `--rpc`
---
-<a id="sec-339"></a>
+<a id="sec-344"></a>
> **Source:** `docs/pump-launcher.md` · [↑ table of contents](#table-of-contents)
@@ -75769,7 +76518,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-544) rail and the platform does the rest:
+[x402](#sec-551) 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**,
@@ -75796,7 +76545,7 @@ current figure — read it, don't hardcode.
## The free → paid funnel
-The paid launch sits between two **free, keyless** [Crypto Data API](#sec-178)
+The paid launch sits between two **free, keyless** [Crypto Data API](#sec-180)
endpoints. Use them to make the launch land well:
1. **Before you launch — check the ticker.**
@@ -75861,7 +76610,7 @@ curl -X POST https://three.ws/api/x402/pump-launch \
curl "https://three.ws/api/crypto/launches"
```
-See [x402 buyer client](#sec-536) for how to satisfy the 402 challenge in
+See [x402 buyer client](#sec-543) for how to satisfy the 402 challenge in
code.
## Output
@@ -75911,16 +76660,16 @@ token itself always deploys on **Solana mainnet** — pump.fun is mainnet-only.
## Related
-- [x402 paid endpoints](#sec-539) — the full catalog and pricing.
-- [Crypto Data API](#sec-178) — the free `symbol` and `launches`
+- [x402 paid endpoints](#sec-546) — the full catalog and pricing.
+- [Crypto Data API](#sec-180) — the free `symbol` and `launches`
endpoints that bookend a launch.
-- [Repo → Coin Launcher](#sec-338) — the batch/CLI launcher that
+- [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-544) — challenge/settle mechanics.
+- [x402 protocol](#sec-551) — challenge/settle mechanics.
---
-<a id="sec-340"></a>
+<a id="sec-345"></a>
> **Source:** `docs/pump-platform-fee.md` · [↑ table of contents](#table-of-contents)
@@ -75981,7 +76730,7 @@ The fee is **never** charged silently. When `platform_fee_bps > 0`:
---
-<a id="sec-341"></a>
+<a id="sec-346"></a>
> **Source:** `docs/pumpfun-program/README.md` · [↑ table of contents](#table-of-contents)
@@ -76040,7 +76789,7 @@ tracked in `tasks/pumpfun-upstream/01-v2-trade-instructions-usdc-audit.md`.
---
-<a id="sec-342"></a>
+<a id="sec-347"></a>
> **Source:** `docs/pumpfun-program/UPSTREAM-buy-sell-v2-announcement.md` · [↑ table of contents](#table-of-contents)
@@ -76119,32 +76868,32 @@ Currently, no quote mint other than native SOL can be used to create or trade co
- RUST crate: https://crates.io/crates/pump-rust-client
## New docs
-- Fee recipients: [docs/FEE_RECIPIENTS.md](#sec-348)
-- Coin creation: [docs/instructions/COIN_CREATION.md](#sec-357)
-- Buy: [docs/instructions/BUY.md](#sec-355)
-- Sell: [docs/instructions/SELL.md](#sec-360)
-- Claim cashback: [docs/instructions/CLAIM_CASHBACK.md](#sec-356)
-- Collect creator fee: [docs/instructions/COLLECT_CREATOR_FEE.md](#sec-358)
-- Creator fee sharing: [docs/instructions/CREATOR_FEE_SHARING.md](#sec-359)
+- Fee recipients: [docs/FEE_RECIPIENTS.md](#sec-353)
+- Coin creation: [docs/instructions/COIN_CREATION.md](#sec-362)
+- Buy: [docs/instructions/BUY.md](#sec-360)
+- Sell: [docs/instructions/SELL.md](#sec-365)
+- Claim cashback: [docs/instructions/CLAIM_CASHBACK.md](#sec-361)
+- Collect creator fee: [docs/instructions/COLLECT_CREATOR_FEE.md](#sec-363)
+- Creator fee sharing: [docs/instructions/CREATOR_FEE_SHARING.md](#sec-364)
## Other documentation
-- [Pump Program](#sec-351)
-- [PumpSwap](#sec-353)
-- [PumpSwap SDK](#sec-354)
-- [Pump Program creator fee update](#sec-350)
-- [PumpSwap creator fee update](#sec-352)
-- [FAQ](#sec-346)
-- [Pump fee program docs](#sec-347)
+- [Pump Program](#sec-356)
+- [PumpSwap](#sec-358)
+- [PumpSwap SDK](#sec-359)
+- [Pump Program creator fee update](#sec-355)
+- [PumpSwap creator fee update](#sec-357)
+- [FAQ](#sec-351)
+- [Pump fee program docs](#sec-352)
---
---
-<a id="sec-343"></a>
+<a id="sec-348"></a>
> **Source:** `docs/pumpfun-program/UPSTREAM-pumpswap-virtual-quote-reserves.md` · [↑ table of contents](#table-of-contents)
@@ -76345,7 +77094,7 @@ Upstream: <https://github.com/pump-fun/pump-public-docs#pumpswap-update-virtual-
---
-<a id="sec-344"></a>
+<a id="sec-349"></a>
> **Source:** `docs/pumpfun-program/docs/BREAKING_FEE_RECIPIENT.md` · [↑ table of contents](#table-of-contents)
@@ -76419,7 +77168,7 @@ The new accounts can be passed before the program upgrade happens on Monday. The
---
-<a id="sec-345"></a>
+<a id="sec-350"></a>
> **Source:** `docs/pumpfun-program/docs/CPI_README.md` · [↑ table of contents](#table-of-contents)
@@ -76523,7 +77272,7 @@ pump-rust-client = { version = "...", path = "..." }
---
-<a id="sec-346"></a>
+<a id="sec-351"></a>
> **Source:** `docs/pumpfun-program/docs/FAQ.md` · [↑ table of contents](#table-of-contents)
@@ -76561,7 +77310,7 @@ is recommended to use a static big enough CU limit like `100_000`.
---
-<a id="sec-347"></a>
+<a id="sec-352"></a>
> **Source:** `docs/pumpfun-program/docs/FEE_PROGRAM_README.md` · [↑ table of contents](#table-of-contents)
@@ -76775,7 +77524,7 @@ If you implement the fee logic correctly, any future change to the fee tiers str
---
-<a id="sec-348"></a>
+<a id="sec-353"></a>
> **Source:** `docs/pumpfun-program/docs/FEE_RECIPIENTS.md` · [↑ table of contents](#table-of-contents)
@@ -76838,7 +77587,7 @@ Use one of these as `buybackFeeRecipient` for any coin.
---
-<a id="sec-349"></a>
+<a id="sec-354"></a>
> **Source:** `docs/pumpfun-program/docs/PUMP_CASHBACK_README.md` · [↑ table of contents](#table-of-contents)
@@ -76955,7 +77704,7 @@ To read unclaimed cashback for pump swap / Pump AMM program:
---
-<a id="sec-350"></a>
+<a id="sec-355"></a>
> **Source:** `docs/pumpfun-program/docs/PUMP_CREATOR_FEE_README.md` · [↑ table of contents](#table-of-contents)
@@ -77090,7 +77839,7 @@ we update the programs on Mainnet.
---
-<a id="sec-351"></a>
+<a id="sec-356"></a>
> **Source:** `docs/pumpfun-program/docs/PUMP_PROGRAM_README.md` · [↑ table of contents](#table-of-contents)
@@ -77291,7 +78040,7 @@ at https://solscan.io/account/EsmVk4MTsoT71JFaRM5DWFZboKpMQjfY6EYzAgUuksXw#accou
---
-<a id="sec-352"></a>
+<a id="sec-357"></a>
> **Source:** `docs/pumpfun-program/docs/PUMP_SWAP_CREATOR_FEE_README.md` · [↑ table of contents](#table-of-contents)
@@ -77400,7 +78149,7 @@ PumpSwap program on Mainnet to the coin creator fee update.
---
-<a id="sec-353"></a>
+<a id="sec-358"></a>
> **Source:** `docs/pumpfun-program/docs/PUMP_SWAP_README.md` · [↑ table of contents](#table-of-contents)
@@ -77634,7 +78383,7 @@ Each Anchor instruction has a set of corresponding autocomplete methods that can
---
-<a id="sec-354"></a>
+<a id="sec-359"></a>
> **Source:** `docs/pumpfun-program/docs/PUMP_SWAP_SDK_README.md` · [↑ table of contents](#table-of-contents)
@@ -77714,7 +78463,7 @@ to autocomplete the `base` and `quote` displayed amounts based on the `lpToken`
---
-<a id="sec-355"></a>
+<a id="sec-360"></a>
> **Source:** `docs/pumpfun-program/docs/instructions/BUY.md` · [↑ table of contents](#table-of-contents)
@@ -77775,7 +78524,7 @@ All `buy_v2` calls need a `feeRecipient` and a `buybackFeeRecipient`.
- For mayhem mode coins, choose one of the 8 reserved fee recipients as `feeRecipient`.
- For all coins, choose one of the 8 buyback fee recipients as `buybackFeeRecipient`.
-See [Fee Recipients](#sec-348) for the full address lists.
+See [Fee Recipients](#sec-353) for the full address lists.
## TS SDK
@@ -77892,7 +78641,7 @@ ixs.extend(
---
-<a id="sec-356"></a>
+<a id="sec-361"></a>
> **Source:** `docs/pumpfun-program/docs/instructions/CLAIM_CASHBACK.md` · [↑ table of contents](#table-of-contents)
@@ -78002,7 +78751,7 @@ let ix = sdk.claim_cashback_v2_instruction(
---
-<a id="sec-357"></a>
+<a id="sec-362"></a>
> **Source:** `docs/pumpfun-program/docs/instructions/COIN_CREATION.md` · [↑ table of contents](#table-of-contents)
@@ -78157,7 +78906,7 @@ let ixs = sdk
---
-<a id="sec-358"></a>
+<a id="sec-363"></a>
> **Source:** `docs/pumpfun-program/docs/instructions/COLLECT_CREATOR_FEE.md` · [↑ table of contents](#table-of-contents)
@@ -78259,13 +79008,13 @@ ixs.extend(sdk.collect_creator_fee_v2_instructions(
---
-<a id="sec-359"></a>
+<a id="sec-364"></a>
> **Source:** `docs/pumpfun-program/docs/instructions/CREATOR_FEE_SHARING.md` · [↑ table of contents](#table-of-contents)
# Creator Fee Sharing
-> **Note:** These instructions only apply to coins that **have** a `sharing_config` — i.e. coins whose creator vault has been migrated to the Pump Fees program for multi-recipient distribution. For single-creator-recipient coins (no `sharing_config`), use [`collect_creator_fee_v2` / `collect_coin_creator_fee`](#sec-358) instead.
+> **Note:** These instructions only apply to coins that **have** a `sharing_config` — i.e. coins whose creator vault has been migrated to the Pump Fees program for multi-recipient distribution. For single-creator-recipient coins (no `sharing_config`), use [`collect_creator_fee_v2` / `collect_coin_creator_fee`](#sec-363) instead.
The lifecycle is:
@@ -78613,7 +79362,7 @@ ixs.extend(sdk.distribute_creator_fees_v2_instructions(
---
-<a id="sec-360"></a>
+<a id="sec-365"></a>
> **Source:** `docs/pumpfun-program/docs/instructions/SELL.md` · [↑ table of contents](#table-of-contents)
@@ -78673,7 +79422,7 @@ All `sell_v2` calls need a `feeRecipient` and a `buybackFeeRecipient`.
- For mayhem mode coins, choose one of the 8 reserved fee recipients as `feeRecipient`.
- For all coins, choose one of the 8 buyback fee recipients as `buybackFeeRecipient`.
-See [Fee Recipients](#sec-348) for the full address lists.
+See [Fee Recipients](#sec-353) for the full address lists.
## TS SDK
@@ -78790,7 +79539,7 @@ ixs.extend(
---
-<a id="sec-361"></a>
+<a id="sec-366"></a>
> **Source:** `docs/quick-start.md` · [↑ table of contents](#table-of-contents)
@@ -78936,7 +79685,7 @@ The `brain` attribute turns the 3D viewer into a conversational agent:
| `brain` | LLM model ID. Registered Claude IDs: `claude-sonnet-5`, `claude-opus-5`, `claude-sonnet-4-6`, `claude-opus-4-8`, `claude-opus-4-7`, `claude-opus-4-6`, `claude-haiku-4-5-20251001`, `claude-fable-5`, `claude-mythos-5` (restricted access). Free models (no key, routed through the platform proxy) are also accepted, e.g. `meta-llama/llama-3.3-70b-instruct:free`. Omit for a viewer-only display with no AI (provider `none`). |
| `instructions` | System prompt for the agent's personality and role. |
| `mode` | Layout mode: `inline` (flows with page content), `floating` (fixed bubble in a corner), `fullscreen`, or `section`. Default: `inline`. |
-| `sign-language` | The avatar signs every reply in ASL fingerspelling plus its sign vocabulary (any value except `off`/`false` enables it; works at boot or toggled at runtime). See the [sign language guide](#sec-381). |
+| `sign-language` | The avatar signs every reply in ASL fingerspelling plus its sign vocabulary (any value except `off`/`false` enables it; works at boot or toggled at runtime). See the [sign language guide](#sec-386). |
The chat input and microphone button appear automatically when `brain` is set. The agent can play animations, look at the camera, and respond to voice input.
@@ -78977,7 +79726,7 @@ The fastest path to an embeddable 3D experience is an iframe widget. Build one i
| `passport` | On-chain identity card backed by ERC-8004. |
| `hotspot-tour` | Annotated 3D scenes with clickable points of interest. |
-For the full widget API including `postMessage` events, see the [Widget docs](#sec-511).
+For the full widget API including `postMessage` events, see the [Widget docs](#sec-517).
---
@@ -79007,7 +79756,7 @@ Copy `.env.example` to `.env` and fill in:
| `ANTHROPIC_API_KEY` | Required for AI chat | LLM backend. Without it, the agent falls back to pattern matching. |
| `VITE_PRIVY_APP_ID` | Optional | Wallet auth via [Privy](https://privy.io). Needed for on-chain identity. |
| `UPSTASH_REDIS_REST_URL` / `UPSTASH_REDIS_REST_TOKEN` | Optional | Distributed rate limiting. Falls back to in-memory without it. |
-| `VITE_CHARACTER_STUDIO_URL` | Optional | Override for the origin hosting the [Avatar Studio](https://github.com/m3-org/CharacterStudio) avatar builder iframe. When unset, the app resolves it same-origin to `<origin>/avatar-studio` in both dev and production. Set it only to point at a standalone studio dev server (e.g. `http://localhost:5173`). See [Configuration](#sec-153). |
+| `VITE_CHARACTER_STUDIO_URL` | Optional | Override for the origin hosting the [Avatar Studio](https://github.com/m3-org/CharacterStudio) avatar builder iframe. When unset, the app resolves it same-origin to `<origin>/avatar-studio` in both dev and production. Set it only to point at a standalone studio dev server (e.g. `http://localhost:5173`). See [Configuration](#sec-154). |
| `AVATURN_API_KEY` | Optional | Photo-to-avatar pipeline via an external photo-to-avatar provider. |
| `PINATA_JWT` | Optional | IPFS pinning for on-chain agent registration. |
@@ -79078,15 +79827,15 @@ If you're embedding inside a sandboxed iframe, make sure the parent grants `allo
## Next Steps
-- [Embedding Guide](#sec-186) — deep dive on attributes, events, and the JS API
-- [Widget Types](#sec-511) — full reference for iframe embeds and postMessage
+- [Embedding Guide](#sec-188) — deep dive on attributes, events, and the JS API
+- [Widget Types](#sec-517) — full reference for iframe embeds and postMessage
- [Agent System](#sec-064) — how the brain, memory, and skills layers work
-- [REST API](#sec-096) and [JavaScript API](#sec-258) — backend and in-browser surfaces
-- [SDK Reference](#sec-374) — `@three-ws/sdk`, `@three-ws/agent-ui`, `@three-ws/avatar`, `@three-ws/solana-agent`
+- [REST API](#sec-096) and [JavaScript API](#sec-261) — backend and in-browser surfaces
+- [SDK Reference](#sec-379) — `@three-ws/sdk`, `@three-ws/agent-ui`, `@three-ws/avatar`, `@three-ws/solana-agent`
---
-<a id="sec-362"></a>
+<a id="sec-367"></a>
> **Source:** `docs/radar.md` · [↑ table of contents](#table-of-contents)
@@ -79102,7 +79851,7 @@ API: `/api/pump/coin-intel` (feed, market pulse, per-coin detail). The detail dr
## Why it exists
-The most dangerous moment on pump.fun is the first minute, when the tape is thin and a bundle of bot wallets can manufacture the look of organic demand. A human cannot audit funder graphs and timing entropy in real time. The Coin Intelligence Engine does, on the live firehose, and Radar is its screener: a scannable board that turns raw first-90-seconds behaviour into a quality score and a short list of named risks, so you can filter out the coordinated launches and focus on the ones with a real crowd. It is the top of the [trading surfaces](#sec-415) funnel: Radar surfaces a launch worth a look, you watch it, and if it earns conviction you open it in [Mission Control](#sec-404) to act.
+The most dangerous moment on pump.fun is the first minute, when the tape is thin and a bundle of bot wallets can manufacture the look of organic demand. A human cannot audit funder graphs and timing entropy in real time. The Coin Intelligence Engine does, on the live firehose, and Radar is its screener: a scannable board that turns raw first-90-seconds behaviour into a quality score and a short list of named risks, so you can filter out the coordinated launches and focus on the ones with a real crowd. It is the top of the [trading surfaces](#sec-420) funnel: Radar surfaces a launch worth a look, you watch it, and if it earns conviction you open it in [Mission Control](#sec-409) to act.
## How it works
@@ -79132,7 +79881,7 @@ The UI colors quality as Healthy at 70 and up, Mixed from 40 to 69, and High ris
3. Press `/` to focus search and type a name, ticker, or mint. Press `g` or `l` to switch grid and list, `r` to refresh.
4. Click any coin for the drawer: the full signal grid, the top-50 wallet ledger, the smart-money notable roster, the outcome (if labeled), and an asynchronously injected Oracle conviction section.
5. Every mainnet coin links to its full page at `/oracle/coin/<mint>`: the card's "Full intel →" button goes there directly, and the drawer carries an "Open full page →" link in its header. The full page renders in the markets-hub design (the same system as `/coin/:id`) with the live price chart, the complete Launch Intelligence read (this engine's signal grid, risk flags, and trader ledger), Oracle conviction, live market intel, agent transactions, and a live trade tape.
-6. On a coin worth tracking, use Watch to add it to your [Watchlist](https://three.ws/watchlist), then open it in [Mission Control](#sec-404) to trade.
+6. On a coin worth tracking, use Watch to add it to your [Watchlist](https://three.ws/watchlist), then open it in [Mission Control](#sec-409) to trade.
## Examples
@@ -79171,16 +79920,16 @@ console.log(clean.map((c) => `${c.symbol} q${c.quality_score}`));
## Related
-- [The trading surfaces: Radar, Mission Control, Live Trade Feed, Watchlist, Coin Intelligence](#sec-415)
-- [Oracle: the conviction engine](#sec-315) fuses this intel into a single conviction score
-- [Smart Money Radar](#sec-389) is the pedigree layer Radar surfaces inline
-- [Mission Control](#sec-404) is where a Radar find gets traded
+- [The trading surfaces: Radar, Mission Control, Live Trade Feed, Watchlist, Coin Intelligence](#sec-420)
+- [Oracle: the conviction engine](#sec-320) fuses this intel into a single conviction score
+- [Smart Money Radar](#sec-394) is the pedigree layer Radar surfaces inline
+- [Mission Control](#sec-409) is where a Radar find gets traded
- [Coin pages](#sec-145) cross-link the per-mint intel and conviction views
- Pages: [/radar](https://three.ws/radar) · [/coin-intel](https://three.ws/coin-intel) · [/watchlist](https://three.ws/watchlist)
---
-<a id="sec-363"></a>
+<a id="sec-368"></a>
> **Source:** `docs/reasoning-ledger.md` · [↑ table of contents](#table-of-contents)
@@ -79270,17 +80019,17 @@ The headline score (0 to 100) is derived only from reconciled outcomes, and the
## Related
- [Agent Sniper](#sec-061): the pipeline that writes `snipe` entries, with a live case-study ledger
-- [Custody you can verify](#sec-170): the same provable-not-promised approach applied to the wallets these decisions spend from
+- [Custody you can verify](#sec-172): the same provable-not-promised approach applied to the wallets these decisions spend from
---
-<a id="sec-364"></a>
+<a id="sec-369"></a>
> **Source:** `docs/recurring-payments.md` · [↑ table of contents](#table-of-contents)
# Recurring payments
-A recurring payment moves a fixed amount of USDC out of your wallet on a schedule you choose, without you signing anything again. You sign one ERC-7710 permission (see [Permissions & Delegation](#sec-322)), the platform's hourly cron spends inside it, and every attempt it makes is written to a ledger you can read.
+A recurring payment moves a fixed amount of USDC out of your wallet on a schedule you choose, without you signing anything again. You sign one ERC-7710 permission (see [Permissions & Delegation](#sec-327)), the platform's hourly cron spends inside it, and every attempt it makes is written to a ledger you can read.
Two kinds of schedule ride the same rails:
@@ -79446,13 +80195,13 @@ Definitions live in [api/\_lib/schema.sql](../api/_lib/schema.sql); the lifecycl
## See also
-- [Permissions & Delegation](#sec-322) for granting, scoping and revoking the signed permission a schedule spends
-- [Payment sessions](#sec-321) for capped one-off agent spending that is not on a schedule
+- [Permissions & Delegation](#sec-327) for granting, scoping and revoking the signed permission a schedule spends
+- [Payment sessions](#sec-326) for capped one-off agent spending that is not on a schedule
- [Agent wallets](#sec-072) for the wallet a subscription pays into
---
-<a id="sec-365"></a>
+<a id="sec-370"></a>
> **Source:** `docs/remix.md` · [↑ table of contents](#table-of-contents)
@@ -79649,12 +80398,12 @@ still recorded — the royalty leg reports `payout_unconfigured` instead of payi
## Related
-- [3D Studio (free) MCP](#sec-274) — the `refine_model` iteration tool.
+- [3D Studio (free) MCP](#sec-278) — the `refine_model` iteration tool.
- [The 3D pipeline](#sec-003) — how generation itself works.
---
-<a id="sec-366"></a>
+<a id="sec-371"></a>
> **Source:** `docs/reputation-staking-market.md` · [↑ table of contents](#table-of-contents)
@@ -79675,7 +80424,7 @@ Live surface: [/reputation/market](/reputation/market).
## What the market pays for
Reputation is already attested on Solana as signed SPL-Memo envelopes indexed
-into `solana_attestations` (see [docs/solana-reputation](#sec-393)).
+into `solana_attestations` (see [docs/solana-reputation](#sec-398)).
An agent's `threews.accept.v1`, `threews.task.v1`, `threews.validation.v1`,
`threews.feedback.v1`, `threews.dispute.v1`, and `threews.revoke.v1` envelopes
are its attested action history: work it shipped, validations it passed or
@@ -79881,15 +80630,15 @@ Failure codes (`market_not_configured`, `mainnet_gated`, `tx_not_found`,
## Related
-- [Docs: Agent Reputation on Solana](#sec-393): the attestation
+- [Docs: Agent Reputation on Solana](#sec-398): the attestation
layer the market reads.
-- [Docs: Reputation System](#sec-367): the cross-chain reputation model.
+- [Docs: Reputation System](#sec-372): the cross-chain reputation model.
- [Reputation Explorer](/reputation): inspect any agent's score and
attestations.
---
-<a id="sec-367"></a>
+<a id="sec-372"></a>
> **Source:** `docs/reputation.md` · [↑ table of contents](#table-of-contents)
@@ -80098,7 +80847,7 @@ GET /api/explore
Separate from reputation scores, glTF validation results can also be recorded on-chain via the `ValidationRegistry`. A passing validation attests that the agent's 3D model meets the glTF specification as of a specific block timestamp. Validation history is shown on the agent's profile page alongside reputation data.
-See the [Validation](#sec-501) documentation for details.
+See the [Validation](#sec-507) documentation for details.
---
@@ -80111,7 +80860,7 @@ See the [Validation](#sec-501) documentation for details.
---
-<a id="sec-368"></a>
+<a id="sec-373"></a>
> **Source:** `docs/restyle.md` · [↑ table of contents](#table-of-contents)
@@ -80205,13 +80954,13 @@ Pass the returned `lineage` array back as `parent_lineage` on the next call to e
## Related
- [Avatar Studio](#sec-115): shares the same GLB optimize-and-validate path and material vocabulary.
-- [Scene Composer](#sec-151) and [Scene Studio](#sec-373): arrange and edit restyled models in a full scene.
-- [MCP tools reference](#sec-275): the paid `restyle_material` agent twin of this endpoint.
+- [Scene Composer](#sec-152) and [Scene Studio](#sec-378): arrange and edit restyled models in a full scene.
+- [MCP tools reference](#sec-279): the paid `restyle_material` agent twin of this endpoint.
- [/forge](https://three.ws/forge): generate the models you bring here.
---
-<a id="sec-369"></a>
+<a id="sec-374"></a>
> **Source:** `docs/rig-doctor.md` · [↑ table of contents](#table-of-contents)
@@ -80225,7 +80974,7 @@ Everything runs in your browser. The file is read with `FileReader` and analysed
**On this page:** [The problem](#the-problem-a-rig-that-loads-but-never-moves) · [Reading the verdict](#reading-the-verdict) · [Coverage](#coverage-which-limbs-will-move) · [The repair](#the-repair) · [Generated output](#generated-output) · [Conventions](#recognised-rig-conventions) · [The canonical skeleton](#the-canonical-skeleton) · [Programmatic use](#programmatic-use)
-Related: [Avatar CLI](#sec-108) turns the generated manifest into a validated, hash-anchored file. The [web component reference](#sec-508) covers the `<agent-3d>` element the embed tab emits. [Asset pipeline](#sec-002) covers FBX and GLB conversion upstream of all of this.
+Related: [Avatar CLI](#sec-108) turns the generated manifest into a validated, hash-anchored file. The [web component reference](#sec-514) covers the `<agent-3d>` element the embed tab emits. [Asset pipeline](#sec-002) covers FBX and GLB conversion upstream of all of this.
---
@@ -80333,6 +81082,7 @@ The convention detector reports which authoring tool your skeleton came from and
| Ready Player Me | `Wolf3D_*` mesh nodes over a Mixamo skeleton | `rpm` |
| Mixamo | `mixamorig:` joint prefix | `mixamo` |
| VRM / VRoid | `J_Bip_*` humanoid joint names | `vrm-humanoid` |
+| MikuMikuDance (PMX/PMD) | Japanese PMX bone names (`センター`, `上半身`, `左腕`) | `custom` |
| Reallusion Character Creator | `CC_Base_*` joint prefix | `custom` |
| Unreal Engine mannequin | `pelvis`, `thigh_l`, `clavicle_l` | `custom` |
| 3ds Max Biped | `Bip01` / `Bip001` prefix | `custom` |
@@ -80441,7 +81191,7 @@ Your own file cannot be shared this way, because it never leaves your machine.
---
-<a id="sec-370"></a>
+<a id="sec-375"></a>
> **Source:** `docs/risk-acknowledgment.md` · [↑ table of contents](#table-of-contents)
@@ -80555,12 +81305,12 @@ above.
## Related
- [Risk Disclosure](https://three.ws/legal/risk) — the full legal text users accept
-- [Custody you can verify](#sec-170) — the spend-limit and freeze controls that bound what agents can do after acceptance
+- [Custody you can verify](#sec-172) — the spend-limit and freeze controls that bound what agents can do after acceptance
- [Terms of Service](https://three.ws/legal/tos) — §8 Limitation of Liability, which this acknowledgment supplements
---
-<a id="sec-371"></a>
+<a id="sec-376"></a>
> **Source:** `docs/robinhood-chain-markets.md` · [↑ table of contents](#table-of-contents)
@@ -80652,16 +81402,16 @@ math; Chainlink feed prices are already multiplier-adjusted, so they're never re
## Related surfaces
-- [Market Data API](#sec-269) — the same paid-endpoint pattern (x402, `priceFor`,
+- [Market Data API](#sec-273) — the same paid-endpoint pattern (x402, `priceFor`,
service-catalog descriptor) applied to the rest of three.ws's market data.
-- [Trust primitives](#sec-417) — score a Robinhood Chain wallet's cross-chain
+- [Trust primitives](#sec-423) — score a Robinhood Chain wallet's cross-chain
reputation before transacting with it.
-- [x402 distribution](#sec-538) — how the paid portfolio endpoint gets discovered
+- [x402 distribution](#sec-545) — how the paid portfolio endpoint gets discovered
across the x402 ecosystem.
---
-<a id="sec-372"></a>
+<a id="sec-377"></a>
> **Source:** `docs/sas-attestations.md` · [↑ table of contents](#table-of-contents)
@@ -80671,7 +81421,7 @@ An attestation is a signed on-chain statement about a wallet or an agent (for ex
three.ws issues two kinds of on-chain attestations on Solana:
-- **Permissionless attestations** — general feedback, task lifecycle, dispute, and revoke events. Anyone can write them as SPL Memos (see [Solana reputation](#sec-393)).
+- **Permissionless attestations** — general feedback, task lifecycle, dispute, and revoke events. Anyone can write them as SPL Memos (see [Solana reputation](#sec-398)).
- **Credentialed attestations** — claims only three.ws or an authorized validator may make: that a wallet is verified, or that a validator audited an agent's task result. These use the [Solana Attestation Service (SAS)](https://attest.solana.com/) and are signed by the **three.ws authority wallet**.
This page covers the authority wallet, the `SAS_AUTHORITY_SECRET` environment variable, bootstrapping the credential + schemas, and the API that issues them.
@@ -80894,13 +81644,13 @@ Closing (revoking) an attestation is done server-side via `sasClose()` in [api/_
---
-<a id="sec-373"></a>
+<a id="sec-378"></a>
> **Source:** `docs/scene-studio.md` · [↑ table of contents](#table-of-contents)
# Scene Studio: the full three.js editor, in your browser
-Scene Studio is the complete [mrdoob/three.js](https://github.com/mrdoob/three.js) editor (release r184, MIT-licensed), vendored into three.ws and wrapped in the site chrome. It is the heavyweight scene tool: import GLBs and other assets, move and rotate and scale them with transform gizmos, edit materials and lights and cameras through a full property sidebar, script objects with live JavaScript, play the scene, and export it. Where [Scene Composer](#sec-151) is a focused avatar-plus-props arranger and [Animation Studio](#sec-092) is a posing and keyframing tool, Scene Studio is the general-purpose 3D authoring surface underneath them.
+Scene Studio is the complete [mrdoob/three.js](https://github.com/mrdoob/three.js) editor (release r184, MIT-licensed), vendored into three.ws and wrapped in the site chrome. It is the heavyweight scene tool: import GLBs and other assets, move and rotate and scale them with transform gizmos, edit materials and lights and cameras through a full property sidebar, script objects with live JavaScript, play the scene, and export it. Where [Scene Composer](#sec-152) is a focused avatar-plus-props arranger and [Animation Studio](#sec-092) is a posing and keyframing tool, Scene Studio is the general-purpose 3D authoring surface underneath them.
Page: [/scene](https://three.ws/scene)
@@ -80955,27 +81705,27 @@ A typical round trip from another studio:
## Related
-- [Scene Composer](#sec-151): the lighter avatar-plus-props arranger with Forge integration.
+- [Scene Composer](#sec-152): the lighter avatar-plus-props arranger with Forge integration.
- [Animation Studio](#sec-092): builds the animated GLBs Scene Studio records to video.
-- [Restyle Studio](#sec-368): re-skin the models before or after composing them.
+- [Restyle Studio](#sec-373): re-skin the models before or after composing them.
- [3D asset pipeline](#sec-002): how GLB, glTF, and clip formats relate across the platform.
---
-<a id="sec-374"></a>
+<a id="sec-379"></a>
> **Source:** `docs/sdk.md` · [↑ table of contents](#table-of-contents)
# SDK & Library
-This page is for developers who want to build with three.ws code in their own project, beyond pasting an embed snippet. If you just want a 3D agent on a page, start with the [web component](#sec-508); come here when you need to import classes, register agents on-chain, or build the bundles yourself. There are two distributable artifacts you can import:
+This page is for developers who want to build with three.ws code in their own project, beyond pasting an embed snippet. If you just want a 3D agent on a page, start with the [web component](#sec-514); come here when you need to import classes, register agents on-chain, or build the bundles yourself. There are two distributable artifacts you can import:
| Artifact | Package | Use case |
|---|---|---|
| **Web component bundle** | `agent-3d.js` (CDN or `TARGET=lib` build) | Drop-in `<agent-3d>` element + programmatic viewer/runtime APIs |
| **AgentKit SDK** | `@three-ws/sdk` | Ship an ERC-8004 agent: chat panel, on-chain registration, `.well-known` manifests |
-Both are proprietary (see [LICENSE](https://github.com/nirholas/three.ws/blob/main/LICENSE)) and free to install and use from npm. Neither requires the other.
+Both are open source under the [Apache License 2.0](https://github.com/nirholas/three.ws/blob/main/LICENSE) and free to install and use from npm. Neither requires the other.
> **Building payments?** The x402 buyer, seller, browser-modal, and MCP packages are
> published to npm as standalone libraries — `@three-ws/x402-fetch`,
@@ -81061,7 +81811,7 @@ const viewer = new Viewer(document.getElementById('canvas-container'));
viewer.load('https://three.ws/avatars/default.glb');
```
-Full attribute and event API is documented in [Web Component reference](#sec-508).
+Full attribute and event API is documented in [Web Component reference](#sec-514).
### loadManifest and normalize
@@ -81404,7 +82154,7 @@ python3 -m http.server 8080
---
-<a id="sec-375"></a>
+<a id="sec-380"></a>
> **Source:** `docs/security.md` · [↑ table of contents](#table-of-contents)
@@ -81420,7 +82170,7 @@ This page explains how three.ws keeps your data, wallet, and agents safe, and wh
**Least privilege** — agents access only what is explicitly declared and granted. Skills declare permission requirements; users must grant them. API keys carry only the scopes you assign. OAuth access tokens are short-lived (1 hour) and audience-bound.
-**Transparency**: the codebase is publicly readable on GitHub (source-available under the repository's proprietary LICENSE). The on-chain identity, reputation, and validation registries are auditable on Base. Badge verification derives from on-chain attestations, not the badge UI itself.
+**Transparency**: the codebase is open source on GitHub under the Apache License 2.0. The on-chain identity, reputation, and validation registries are auditable on Base. Badge verification derives from on-chain attestations, not the badge UI itself.
**Standard web security** — HTTPS-only for all authenticated operations. CSP, CORS, and `__Host-` cookie prefix enforced throughout.
@@ -81445,7 +82195,7 @@ Chat messages travel through `/api/chat`, which proxies to a configured LLM prov
- Does not log message content
- Returns the LLM stream directly to your browser
-Conversation history lives in `localStorage` by default. Cloud memory sync is opt-in (see [Memory](#sec-280)).
+Conversation history lives in `localStorage` by default. Cloud memory sync is opt-in (see [Memory](#sec-284)).
### Wallet data
@@ -81461,7 +82211,7 @@ The SIWE (Sign-In With Ethereum) flow signs a server-generated challenge — no
| Mode | Where data lives | Privacy |
|------|-----------------|---------|
| `local` (default) | Browser `localStorage` | Device-only |
-| `remote` | three.ws cloud storage, tied to your account | Opt-in cloud sync (see [Memory](#sec-280)) |
+| `remote` | three.ws cloud storage, tied to your account | Opt-in cloud sync (see [Memory](#sec-284)) |
| `ipfs` | Public IPFS network | Public — use only for non-sensitive data |
| `encrypted-ipfs` | IPFS, encrypted before leaving the browser | Encrypted with your key; IPFS only sees ciphertext |
| `none` | Not persisted | Cleared on page unload |
@@ -81613,7 +82363,7 @@ Every registered agent card requires a `model.sha256` field. The `<three-d-agent
Validator keys are dedicated signing keys, not personal wallets. The deployed `ValidationRegistry` has **no validator allowlist** (`removeValidator(address)` exists only on `contracts/src/ValidationRegistry.sol`, which is deployed nowhere), so revocation is not an on-chain call: any address can answer a request addressed to it. Containment for a compromised validator key is therefore to rotate it (`scripts/erc8004/provision-validator-key.mjs` reprovisions `VALIDATOR_PRIVATE_KEY` on the API service) and to have indexers and resolvers filter by validator address, treating attestations signed by the retired key as expired from the rotation block onward.
-That places the whole burden on key custody: see the platform-validator note in [contracts/DEPLOYMENTS.md](../contracts/DEPLOYMENTS.md) and [docs/erc8004/validation-attestation.md](#sec-189) for the operating rules.
+That places the whole burden on key custody: see the platform-validator note in [contracts/DEPLOYMENTS.md](../contracts/DEPLOYMENTS.md) and [docs/erc8004/validation-attestation.md](#sec-191) for the operating rules.
### Reputation gaming (V5)
@@ -81766,7 +82516,7 @@ For validator misconduct (biased or falsified on-chain attestations), open a pub
---
-<a id="sec-376"></a>
+<a id="sec-381"></a>
> **Source:** `docs/seed-quality.md` · [↑ table of contents](#table-of-contents)
@@ -82051,13 +82801,13 @@ ticks start timing out, lower `SEED_CRON_VISION_MS` before turning it back off.
- [Realism quality bench](../data/quality-bench/README.md): the regression
harness whose scorer this gate imports
-- [The 3D viewer](#sec-505): what a published catalog entry has to render in
+- [The 3D viewer](#sec-511): what a published catalog entry has to render in
- [Production log triage](ops/production-log-triage.md): the operator runbook
for the seeding pipeline
---
-<a id="sec-377"></a>
+<a id="sec-382"></a>
> **Source:** `docs/selfie-to-avatar.md` · [↑ table of contents](#table-of-contents)
@@ -82088,7 +82838,7 @@ Two of those numbers are measured rather than reasoned about. The blur floor (`B
6. **Reconstruct, server-side.** The reconstruct handler (`api/avatars/_actions.js`) selects a provider through [`api/_lib/regen-provider.js`](../api/_lib/regen-provider.js). The production lane is **GCP**: it POSTs `{ images, body_type }` to the Cloud Run service behind `GCP_RECONSTRUCTION_URL`, today the [`workers/avatar-reconstruction/`](../workers/avatar-reconstruction) FastAPI app deployed as `avatar-reconstruction`. (The multi-backend [`workers/avatar-pipeline-controller/`](../workers/avatar-pipeline-controller) speaks the identical contract and can take over that env var, but is not deployed today.) That pipeline (`face_texture_transfer_v2`) uses **MediaPipe FaceLandmarker** (468 landmarks, Apache-2.0) to transfer your face texture and geometry onto a fixed-topology, pre-rigged Wolf3D/Ready-Player-Me-style humanoid template carrying a Mixamo-compatible skeleton, 52 ARKit blendshapes, and 15 visemes. Full engine detail is in [avatar-reconstruction.md](#sec-114).
7. **Auto-rig fallback.** The template is born rigged. If a generic mesh comes back unrigged and a rig model is configured, `reconstruct-finalize.js` chains a `rerig` job (the `model-rig` worker, `workers/rig`) and moves the job through a `rigging` status before surfacing the avatar. If rigging is impossible it delivers the static mesh tagged `unrigged` rather than nothing.
8. **Poll and finish.** The client polls `GET /api/avatars/regenerate-status?jobId=...` every ~3 seconds (backing off on errors). On `status: 'done'` it fetches the finished avatar from `GET /api/avatars/:id` and shows it in a `<model-viewer>`. The poll uses the adapter for the provider recorded on the job row, not whichever provider currently leads the precedence order, because the stored job id is provider-shaped and only that backend can read it.
-9. **Register and mint.** Materializing the avatar also registers it in the Forge store (`forge_creations`, `path: 'reconstruct'`) so galleries, share and embed pages, and provenance treat a capture like any other creation, and fires a best-effort [draft agent identity mint](#sec-180): a Metaplex Core asset on Solana, with an ERC-8004 registration behind its own flag. Both are best-effort by design: the avatar is already delivered, so neither can fail the job.
+9. **Register and mint.** Materializing the avatar also registers it in the Forge store (`forge_creations`, `path: 'reconstruct'`) so galleries, share and embed pages, and provenance treat a capture like any other creation, and fires a best-effort [draft agent identity mint](#sec-182): a Metaplex Core asset on Solana, with an ERC-8004 registration behind its own flag. Both are best-effort by design: the avatar is already delivered, so neither can fail the job.
10. **Backstop for a closed tab.** The browser poll is what drives finalization, so closing the tab mid-build would otherwise strand the job even though the worker finished. [`api/cron/reconstruct-sweep.js`](../api/cron/reconstruct-sweep.js) runs the same finalize stages server-side every few minutes, so an abandoned capture still lands in your library. It rescues jobs up to 30 days old, and fails anything older with an honest reason rather than leaving it open forever.
### The text-to-avatar variant
@@ -82148,14 +82898,14 @@ Request body: `name` (1-120, required), `photos` (1-6 image URLs or data URIs) *
- [Avatar reconstruction pipeline](#sec-114): the full engine: MediaPipe face-texture transfer, geometry morph, the fixed pre-rigged head template, and the Cloud Run worker.
- [Avatar pipeline](#sec-113): the distinct Forge text-to-3D generation lane.
-- [Draft agent mint](#sec-180): the on-chain identity every finished reconstruction gets, the network flags, and the devnet proof script.
+- [Draft agent mint](#sec-182): the on-chain identity every finished reconstruction gets, the network flags, and the devnet proof script.
- [Trait-based avatar builder](#sec-137): customize and dress the avatar after you scan it.
-- [Talking Avatar Video](#sec-403) and [Lipsync](#sec-264): drive the finished avatar's mouth.
+- [Talking Avatar Video](#sec-408) and [Lipsync](#sec-267): drive the finished avatar's mouth.
- Pages: [/create/selfie](https://three.ws/create/selfie), [/create](https://three.ws/create), [/features/scan](https://three.ws/features/scan).
---
-<a id="sec-378"></a>
+<a id="sec-383"></a>
> **Source:** `docs/share-and-embed.md` · [↑ table of contents](#table-of-contents)
@@ -82221,7 +82971,7 @@ If you manage the HTML of your page directly, the `<agent-3d>` custom element gi
<agent-3d agent-id="<your-agent-id>"></agent-3d>
```
-The element renders inline (no iframe boundary), supports keyboard navigation, and exposes a JavaScript API so you can drive the agent programmatically. See the [Embedding guide](#sec-186) for the full attribute reference and event list.
+The element renders inline (no iframe boundary), supports keyboard navigation, and exposes a JavaScript API so you can drive the agent programmatically. See the [Embedding guide](#sec-188) for the full attribute reference and event list.
---
@@ -82262,14 +83012,14 @@ To customize the preview image, change the agent's thumbnail in the editor.
## What's next
-- **Make your agent smarter** → [Skills system](#sec-387)
-- **Understand the technical embed options** → [Embedding guide](#sec-186)
-- **Payment and crypto questions** → [Do I need crypto?](#sec-178)
-- **Give it a permanent on-chain address** → [Register on-chain](#sec-462)
+- **Make your agent smarter** → [Skills system](#sec-392)
+- **Understand the technical embed options** → [Embedding guide](#sec-188)
+- **Payment and crypto questions** → [Do I need crypto?](#sec-180)
+- **Give it a permanent on-chain address** → [Register on-chain](#sec-468)
---
-<a id="sec-379"></a>
+<a id="sec-384"></a>
> **Source:** `docs/shared-utilities.md` · [↑ table of contents](#table-of-contents)
@@ -82489,7 +83239,7 @@ paused during an incident and never resumed, failed silently.
---
-<a id="sec-380"></a>
+<a id="sec-385"></a>
> **Source:** `docs/showcase.md` · [↑ table of contents](#table-of-contents)
@@ -82499,7 +83249,7 @@ paused during an incident and never resumed, failed silently.
That filter is the whole point of the surface. The ERC-8004 registries hold plenty of agents that are only an address and a URI. The showcase answers a narrower question: which of them can actually be seen and embedded.
-Live at [three.ws/showcase](https://three.ws/showcase). Related reading: [ERC-8004](#sec-188) for the identity standard itself, [on-chain deployments](#sec-175) for the live feed of every registration as it lands (with no avatar filter), and [on-chain agents](#sec-304) for registering one yourself.
+Live at [three.ws/showcase](https://three.ws/showcase). Related reading: [ERC-8004](#sec-190) for the identity standard itself, [on-chain deployments](#sec-177) for the live feed of every registration as it lands (with no avatar filter), and [on-chain agents](#sec-308) for registering one yourself.
Code: [api/showcase.js](../api/showcase.js). Data comes from `erc8004_agents_index`, populated by the `erc8004-crawl` cron.
@@ -82558,14 +83308,14 @@ Each agent carries its on-chain identity plus explorer links resolved from the c
## Related
-- [ERC-8004](#sec-188): the identity standard behind every row here.
-- [On-chain deployments](#sec-175): the same registration stream without the 3D filter, including Solana Metaplex Core mints.
-- [Deploy agents on-chain](#sec-304): how to register an agent so it can appear here.
+- [ERC-8004](#sec-190): the identity standard behind every row here.
+- [On-chain deployments](#sec-177): the same registration stream without the 3D filter, including Solana Metaplex Core mints.
+- [Deploy agents on-chain](#sec-308): how to register an agent so it can appear here.
- [Agent manifest](#sec-055): the metadata format whose 3D model field decides `has_3d`.
---
-<a id="sec-381"></a>
+<a id="sec-386"></a>
> **Source:** `docs/sign-language.md` · [↑ table of contents](#table-of-contents)
@@ -82733,7 +83483,7 @@ Best results: good light, hand in frame, one letter at a time, and hold the last
## In your own site or app
-The [web component](#sec-508) exposes signing as an attribute. Present at boot, or toggled at runtime, it does the same thing:
+The [web component](#sec-514) exposes signing as an attribute. Present at boot, or toggled at runtime, it does the same thing:
```html
<script type="module" src="https://three.ws/agent-3d/1.5.2/agent-3d.js"></script>
@@ -83078,13 +83828,13 @@ None of this replaces a human interpreter. It makes an avatar legible to signers
- [examples/sign-language.html](../examples/sign-language.html), a runnable page with both integration paths
- [Animation Studio](#sec-092), the Spell box, exports, and share links
- [docs/animations.md](#sec-093), clip formats and the retarget engine
-- [docs/web-component.md](#sec-508), every `<agent-3d>` attribute including `sign-language`
+- [docs/web-component.md](#sec-514), every `<agent-3d>` attribute including `sign-language`
- [workers/model-asl-recognition](../workers/model-asl-recognition/README.md), the recognition model and its licensing
- [Motion Swap](https://three.ws/motion-swap), video motion capture, including hands
---
-<a id="sec-382"></a>
+<a id="sec-387"></a>
> **Source:** `docs/signals.md` · [↑ table of contents](#table-of-contents)
@@ -83183,22 +83933,22 @@ curl -s https://three.ws/api/signals/subscribe -H 'authorization: Bearer YOUR_TO
## Related
-- [Custody you can verify](#sec-170) - the spend caps, freeze, and audit trail the subscriber wallet pays and trades under
-- [Financial controls](#sec-221) - the plain-English rules and firewall the mirror respects
-- [Oracle](#sec-315) - the conviction engine and its own follow/copy tier
-- [x402](#sec-544) - the USDC payment protocol every signal settles over
-- [Trader card](#sec-409) - the verified track record that regresses a feed's edge
+- [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
+- [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
---
-<a id="sec-383"></a>
+<a id="sec-388"></a>
> **Source:** `docs/site-performance.md` · [↑ table of contents](#table-of-contents)
# What the site's load numbers are, and the four rules that keep them there
-`/play` has [its own boot-cost document](#sec-325) because a coin world is a special case: a WebGL renderer, a physics solver and a multiplayer room all have to start before anything is playable. This document covers everything else. Every ordinary page on three.ws is a static HTML document plus a module graph, and the cost of opening one is almost entirely decided by four questions:
+`/play` has [its own boot-cost document](#sec-330) because a coin world is a special case: a WebGL renderer, a physics solver and a multiplayer room all have to start before anything is playable. This document covers everything else. Every ordinary page on three.ws is a static HTML document plus a module graph, and the cost of opening one is almost entirely decided by four questions:
1. How many bytes of JavaScript run before the page is usable?
2. How much of the DOM does the browser lay out that nobody can see?
@@ -83481,7 +84231,7 @@ Two things in the numbers above are real and are not being fixed by tuning:
---
-<a id="sec-384"></a>
+<a id="sec-389"></a>
> **Source:** `docs/sketchfab.md` · [↑ table of contents](#table-of-contents)
@@ -83571,7 +84321,7 @@ and [`api/_lib/sketchfab.js`](https://github.com/nirholas/three.ws/blob/main/api
---
-<a id="sec-385"></a>
+<a id="sec-390"></a>
> **Source:** `docs/skill-bundles.md` · [↑ table of contents](#table-of-contents)
@@ -83762,13 +84512,13 @@ agent's marketplace listing is the next step.
## Related
-- [Marketplace](#sec-270): how skills and assets are listed, bought, and settled
+- [Marketplace](#sec-274): how skills and assets are listed, bought, and settled
- [Agent skills](#sec-060): what a skill is in the first place
- [Agent wallets](#sec-072): where a bundle's payment lands
---
-<a id="sec-386"></a>
+<a id="sec-391"></a>
> **Source:** `docs/skill-royalties.md` · [↑ table of contents](#table-of-contents)
@@ -83974,14 +84724,14 @@ whose pending balance clears $0.01, so nobody pays gas to move dust.
## Related
-- [Skills marketplace](#sec-387): publishing, pricing, and installing skills
-- [x402 endpoints](#sec-539): every paid endpoint and who each one pays
-- [Money map](#sec-287): how value moves across the whole platform
-- [Remix royalties](#sec-365): the parallel royalty rail for 3D creations
+- [Skills marketplace](#sec-392): publishing, pricing, and installing skills
+- [x402 endpoints](#sec-546): 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
---
-<a id="sec-387"></a>
+<a id="sec-392"></a>
> **Source:** `docs/skills.md` · [↑ table of contents](#table-of-contents)
@@ -84703,7 +85453,7 @@ Installing is free and instant (`POST /api/skills/:id/install`, sign-in required
- **Knowledge skills load into your chats.** `/api/chat` reads your installed skills at request time (`api/_lib/installed-skills.js`) and injects their playbooks into the system prompt, so your agent follows them anywhere you chat signed-in on three.ws (the `/app` workspace included). Budgets keep prompts sane: newest 8 installs, 6k chars per skill, 24k total. Each reply's SSE `done` event lists the slugs that were in context as `skills_applied`.
- **Your installed set is one API call away.** `GET /api/skills?installed=true` (authed) returns the full payload, `content` and `schema_json` included, so an external agent, MCP client, or script can hydrate itself from your library.
-Paid skills price per *call*, not per install: the detail page shows an x402 endpoint (`GET /api/x402/skill-call?skill=<slug>`) any wallet can pay in USDC, settling to the author. The 402 challenge names the author's own wallet as the payee, so their share moves at settlement rather than being forwarded later, and Solana is offered first whenever the author has a Solana wallet. What the author keeps, where they watch it land, and how to verify a payout on-chain: [Skill royalties](#sec-386).
+Paid skills price per *call*, not per install: the detail page shows an x402 endpoint (`GET /api/x402/skill-call?skill=<slug>`) any wallet can pay in USDC, settling to the author. The 402 challenge names the author's own wallet as the payee, so their share moves at settlement rather than being forwarded later, and Solana is offered first whenever the author has a Solana wallet. What the author keeps, where they watch it land, and how to verify a payout on-chain: [Skill royalties](#sec-391).
Publish your own from the marketplace ("Publish a Skill") or `POST /api/skills` with `{ name, slug, description, category, tags, content }` (or `schema_json`).
@@ -84743,13 +85493,13 @@ Those filters are also the page URL, so [/marketplace?tab=skills&tag=solana&sort
- [Architecture Overview](#sec-100) — how skills fit into the agent runtime
- [Agent System](#sec-064) — the protocol bus and built-in tool system
-- [Web Component](#sec-508) — embedding agents and passing skill attributes
+- [Web Component](#sec-514) — embedding agents and passing skill attributes
- `specs/SKILL_SPEC.md` — the authoritative skill bundle specification
- `specs/PERMISSIONS_SPEC.md` — ERC-7710/ERC-7715 delegation for fine-grained skill permissions
---
-<a id="sec-388"></a>
+<a id="sec-393"></a>
> **Source:** `docs/smart-contracts.md` · [↑ table of contents](#table-of-contents)
@@ -85407,7 +86157,7 @@ On Base at typical gas prices (~0.001 gwei base fee), an agent registration runs
---
-<a id="sec-389"></a>
+<a id="sec-394"></a>
> **Source:** `docs/smart-money.md` · [↑ table of contents](#table-of-contents)
@@ -85421,7 +86171,7 @@ API: `/api/pump/smart-money` (feed, leaderboard, per-coin, per-wallet). The coin
## Why it exists
-The single most predictive early signal on pump.fun is not the chart, it is who is buying. A wallet that has repeatedly entered coins that went on to graduate is worth watching; a wallet that dumps every launch it touches is worth avoiding. That information exists on chain, but nobody keeps a running scorecard in time. Smart Money Radar is that scorecard. It re-earns every wallet's reputation continuously from real outcomes, so a coin's "pedigree" is the buy-weighted track record of the wallets actually in it, and a wallet's rank is its own history of picking coins that graduated. This is the same proven-wallet ledger the WHO pillar of [Oracle](#sec-315) draws on, exposed as its own browsable surface.
+The single most predictive early signal on pump.fun is not the chart, it is who is buying. A wallet that has repeatedly entered coins that went on to graduate is worth watching; a wallet that dumps every launch it touches is worth avoiding. That information exists on chain, but nobody keeps a running scorecard in time. Smart Money Radar is that scorecard. It re-earns every wallet's reputation continuously from real outcomes, so a coin's "pedigree" is the buy-weighted track record of the wallets actually in it, and a wallet's rank is its own history of picking coins that graduated. This is the same proven-wallet ledger the WHO pillar of [Oracle](#sec-320) draws on, exposed as its own browsable surface.
## How it works
@@ -85506,14 +86256,14 @@ for (const c of conviction.slice(0, 5)) {
## Related
-- [Oracle: the conviction engine](#sec-315) uses this proven-wallet ledger as its WHO pillar
-- [The trading surfaces](#sec-415) map, including the Coin Intelligence cross-coin trader board
-- [Coin Radar](#sec-362) and [Mission Control](#sec-404) surface the same pedigree read inline
+- [Oracle: the conviction engine](#sec-320) uses this proven-wallet ledger as its WHO pillar
+- [The trading surfaces](#sec-420) map, including the Coin Intelligence cross-coin trader board
+- [Coin Radar](#sec-367) and [Mission Control](#sec-409) surface the same pedigree read inline
- Pages: [/smart-money](https://three.ws/smart-money) · [/radar](https://three.ws/radar) · [/oracle](https://three.ws/oracle)
---
-<a id="sec-390"></a>
+<a id="sec-395"></a>
> **Source:** `docs/sniper-autonomy.md` · [↑ table of contents](#table-of-contents)
@@ -85586,7 +86336,7 @@ and position size. Reaching `trusted` unlocks five more (`TIER_UNLOCKS` in
outward only. An arm with no band set is already unrestricted and nothing here
will restrict it.
- `initials_out_multiple` / `moonbag_min_pct`, the proactive
- [take-initials ladder](#sec-413): recover the stake as soon as
+ [take-initials ladder](#sec-418): recover the stake as soon as
the position hits 2x rather than waiting for an exit to trigger, and size the
moon bag that keeps riding. Turned on only for an arm whose winners
demonstrably run past its average exit. Note this is only the *early*
@@ -85687,7 +86437,7 @@ tighter rather than rewarded for the hit rate.
## Related
- [Agent Sniper](#sec-061): the trading pipeline the arms run on
-- [The 10 SOL trading experiment](#sec-413): the exit thesis the
+- [The 10 SOL trading experiment](#sec-418): the exit thesis the
ladder implements
- [`api/_lib/sniper-optimizer.js`](../api/_lib/sniper-optimizer.js): the tuning
rules, tier-scaled
@@ -85696,7 +86446,7 @@ tighter rather than rewarded for the hit rate.
---
-<a id="sec-391"></a>
+<a id="sec-396"></a>
> **Source:** `docs/social-layer.md` · [↑ table of contents](#table-of-contents)
@@ -85771,7 +86521,7 @@ a feed).
> Source: [api/users/me/feed.js](../api/users/me/feed.js). Not to be confused
> with `GET /api/feed`, the public Money Pulse ticker backed by Redis; see
-> [Money Feed](#sec-285) for that one.
+> [Money Feed](#sec-289) for that one.
## Follow graph
@@ -85922,16 +86672,16 @@ be replayed any time from the getting-started page.
## Related pages
-- [Money Feed](#sec-285): the value-movement ticker (`GET /api/feed`),
+- [Money Feed](#sec-289): the value-movement ticker (`GET /api/feed`),
a different feed from the activity feed documented here.
-- [Remix economy](#sec-365): what happens after someone finds your model in
+- [Remix economy](#sec-370): what happens after someone finds your model in
the feed or search.
- [API reference: Social & Community](api-reference.md#social--community-api)
for the full request/response contracts.
---
-<a id="sec-392"></a>
+<a id="sec-397"></a>
> **Source:** `docs/solana-pumpfun.md` · [↑ table of contents](#table-of-contents)
@@ -86094,7 +86844,7 @@ Studio config schema (validated in `widget-types.js`):
## What's intentionally not included
- **Long-lived SSE** — the feed handler runs a 90s bounded loop and lets the browser auto-reconnect; the Cloud Run request handlers aren't meant to hold a connection open indefinitely. For higher throughput, deploy the bot itself as a streaming service.
-- **On-chain signal attestations**: pump.fun signals are off-chain rows only. The platform's SPL Memo attestation layer exists (see [Solana reputation](#sec-393)), but these crawled signals are not promoted into it; that remains a future step.
+- **On-chain signal attestations**: pump.fun signals are off-chain rows only. The platform's SPL Memo attestation layer exists (see [Solana reputation](#sec-398)), but these crawled signals are not promoted into it; that remains a future step.
- **Agent-as-signer** — the watch skills are read-only; they never sign transactions. The existing `pumpfun-create / -buy / -sell` skills cover signing flows.
- **Anchor program for reputation** — still EVM-only on the on-chain path.
@@ -86118,7 +86868,7 @@ The MCP client and cron crawler are unit-tested with mocked `fetch` and `sql`. E
---
-<a id="sec-393"></a>
+<a id="sec-398"></a>
> **Source:** `docs/solana-reputation.md` · [↑ table of contents](#table-of-contents)
@@ -86128,7 +86878,7 @@ How three.ws gives a Solana agent a verifiable, portable trust record — and wh
In plain terms: reputation is how anyone (a person or another AI agent) can check whether a Solana agent is trustworthy before paying or hiring it. You can see any agent's trust grade right now in the [Agent Passport](/agent-passport.html), and query the same data over the API described below. This page explains where those numbers come from and how to write your own on-chain vouch.
-This is the Solana companion to [Agent Reputation](#sec-056) (the why) and [ERC-8004](#sec-188) / [Reputation System](#sec-367) (the EVM how-to). If you haven't read those, start with [Agent Reputation](#sec-056) for the trust problem reputation solves. This page covers how that same problem is solved on Solana, where there is no canonical on-chain reputation registry to inherit.
+This is the Solana companion to [Agent Reputation](#sec-056) (the why) and [ERC-8004](#sec-190) / [Reputation System](#sec-372) (the EVM how-to). If you haven't read those, start with [Agent Reputation](#sec-056) for the trust problem reputation solves. This page covers how that same problem is solved on Solana, where there is no canonical on-chain reputation registry to inherit.
---
@@ -86204,7 +86954,7 @@ The crawler (`crawlAgentAttestations`) calls `getSignaturesForAddress(asset)` fr
### Staked conviction is reported net, not gross
-The `stake` block of the reputation response counts what is **still** staked. When a staker withdraws through the [Reputation Staking Market](#sec-366), the escrow writes a `threews.unstake.v1` memo naming that stake, and the conviction it expressed stops counting: withdrawn conviction is not conviction. Only the market escrow's own settlements retire anything, so a stranger cannot deflate an agent's standing with a memo naming somebody else's stake.
+The `stake` block of the reputation response counts what is **still** staked. When a staker withdraws through the [Reputation Staking Market](#sec-371), the escrow writes a `threews.unstake.v1` memo naming that stake, and the conviction it expressed stops counting: withdrawn conviction is not conviction. Only the market escrow's own settlements retire anything, so a stranger cannot deflate an agent's standing with a memo naming somebody else's stake.
The history is reported alongside the net figure rather than erased:
@@ -86297,7 +87047,7 @@ In the agent card, both registrations sit side by side as CAIP-style references
]
```
-**Reputation from the two chains is read separately, not mathematically merged.** A consumer that wants the full picture reads ERC-8004 (via the [`agent_reputation` MCP tool](#sec-367)) *and* the Solana reputation API, and weighs them itself. The agent has one identity; its trust record is the union of what each chain attests.
+**Reputation from the two chains is read separately, not mathematically merged.** A consumer that wants the full picture reads ERC-8004 (via the [`agent_reputation` MCP tool](#sec-372)) *and* the Solana reputation API, and weighs them itself. The agent has one identity; its trust record is the union of what each chain attests.
---
@@ -86329,14 +87079,14 @@ The shapes differ; the purpose is identical — let an agent decide, before it p
## Next
- **[Read a Solana agent's reputation](/tutorials/solana-agent-reputation)** — open a Passport, read the grade, query the API, and leave an on-chain vouch.
-- **[Reputation Staking Market](#sec-366)**: the market built directly on the attestations above. Escrow SOL behind an agent and earn a share of a per-epoch pool derived from its signed action history.
+- **[Reputation Staking Market](#sec-371)**: the market built directly on the attestations above. Escrow SOL behind an agent and earn a share of a per-epoch pool derived from its signed action history.
- **[Agent Reputation: why it matters](#sec-056)** — the trust problem both chains solve.
-- **[Solana agents](#sec-394)** — registering an agent as a Metaplex Core asset.
-- **[ERC-8004](#sec-188)** · **[Reputation System](#sec-367)** — the EVM side of the same idea.
+- **[Solana agents](#sec-399)** — registering an agent as a Metaplex Core asset.
+- **[ERC-8004](#sec-190)** · **[Reputation System](#sec-372)** — the EVM side of the same idea.
---
-<a id="sec-394"></a>
+<a id="sec-399"></a>
> **Source:** `docs/solana.md` · [↑ table of contents](#table-of-contents)
@@ -86344,11 +87094,11 @@ The shapes differ; the purpose is identical — let an agent decide, before it p
Give your three.ws agent a real on-chain identity on Solana. When you register, your wallet signs one transaction that mints an NFT (a Metaplex Core asset) representing the agent, and three.ws links that mint to your agent record. You do this from the agent creation and edit pages after connecting a Solana wallet (Phantom, Solflare, or Backpack).
-Technically, the flow mirrors the [ERC-8004](#sec-188) path on EVM chains: a user's wallet signs a transaction that mints an on-chain identity token, and the platform stores the link between the agent record and the mint address.
+Technically, the flow mirrors the [ERC-8004](#sec-190) path on EVM chains: a user's wallet signs a transaction that mints an on-chain identity token, and the platform stores the link between the agent record and the mint address.
This document covers what is supported today, the end-to-end registration flow, and what is intentionally **not** on Solana yet.
-> Deploying many agents at once (server-side, into the three.ws Agents collection, with a live dashboard)? See [Deploy agents on-chain (bulk)](#sec-304).
+> Deploying many agents at once (server-side, into the three.ws Agents collection, with a live dashboard)? See [Deploy agents on-chain (bulk)](#sec-308).
---
@@ -86361,16 +87111,16 @@ This document covers what is supported today, the end-to-end registration flow,
| Solana payments (checkout + confirm) | Live | [api/payments/solana/\[action\].js](../api/payments/solana/[action].js) (handles `checkout` + `confirm`) |
| Agent identity NFT (Metaplex Core) | Live | [api/agents/solana/\[action\].js](../api/agents/solana/[action].js) (handles `register-prep` + `register-confirm`) |
| Agent record persisted in DB | Live | `agent_identities`, `meta.chain_type='solana'`, `meta.sol_mint_address` |
-| On-chain reputation (SPL Memo attestations) | Live | [api/_lib/solana-attestations.js](../api/_lib/solana-attestations.js), aggregated by `/api/agents/solana-reputation` (see [Solana reputation](#sec-393)) |
+| On-chain reputation (SPL Memo attestations) | Live | [api/_lib/solana-attestations.js](../api/_lib/solana-attestations.js), aggregated by `/api/agents/solana-reputation` (see [Solana reputation](#sec-398)) |
| On-chain validation (glTF/schema attestation) | Live | [api/_lib/solana-validation-attest.js](../api/_lib/solana-validation-attest.js), auto-run at register-confirm |
-| Credentialed attestations (SAS) | Live | [api/agents/sas/\[action\].js](../api/agents/sas/[action].js) (see [SAS attestations](#sec-372)) |
+| Credentialed attestations (SAS) | Live | [api/agents/sas/\[action\].js](../api/agents/sas/[action].js) (see [SAS attestations](#sec-377)) |
| Discovery file lists Solana agents | **Not yet** | [public/.well-known/agent-registration.json](../public/.well-known/agent-registration.json) publishes the platform card and x402 catalog, but its `registrations` array carries no per-agent Solana entries |
---
## How identity works on Solana
-EVM agents are minted as ERC-721 NFTs in the IdentityRegistry contract at a fixed CREATE2 address. Solana has no CREATE2 and no shared registry contract. Instead each agent is a **Metaplex Core asset** (a single-account NFT standard with name + URI metadata baked in). When a three.ws Agents collection is configured for the network (`SOLANA_AGENT_COLLECTION_MAINNET` / `_DEVNET`), the asset is minted into that collection with the collection authority co-signing, so three.ws can curate on-chain metadata on the owner's behalf; with no collection configured, the mint falls back to a standalone asset. See [Deploy agents on-chain (bulk)](#sec-304) for the collection model.
+EVM agents are minted as ERC-721 NFTs in the IdentityRegistry contract at a fixed CREATE2 address. Solana has no CREATE2 and no shared registry contract. Instead each agent is a **Metaplex Core asset** (a single-account NFT standard with name + URI metadata baked in). When a three.ws Agents collection is configured for the network (`SOLANA_AGENT_COLLECTION_MAINNET` / `_DEVNET`), the asset is minted into that collection with the collection authority co-signing, so three.ws can curate on-chain metadata on the owner's behalf; with no collection configured, the mint falls back to a standalone asset. See [Deploy agents on-chain (bulk)](#sec-308) for the collection model.
The agent's canonical identifier on Solana is its **asset pubkey** (base58, 32-byte). The platform stores it alongside the mint transaction signature so the on-chain record can always be re-verified.
@@ -86594,13 +87344,13 @@ There is no global Solana registry to query — discovery happens via the platfo
## What's on Solana instead of a registry contract
-- **Reputation**: there is no single `ReputationRegistry` contract like ERC-8004's. Instead, permissionless SPL Memo attestations (feedback, stakes, tasks, disputes) are written on-chain against the agent's asset pubkey, crawled into `solana_attestations`, and aggregated by `/api/agents/solana-reputation`. Off-chain pump.fun behavior signals land in `pumpfun_signals` and feed the same score. See [Solana reputation](#sec-393) and [solana-pumpfun.md](#sec-392).
-- **Validation**: no registry contract either; validations are `threews.validation.v1` SPL Memo attestations (including the automatic glb-schema attestation at register-confirm), plus SAS credentialed validations signed by the platform authority ([SAS attestations](#sec-372)).
+- **Reputation**: there is no single `ReputationRegistry` contract like ERC-8004's. Instead, permissionless SPL Memo attestations (feedback, stakes, tasks, disputes) are written on-chain against the agent's asset pubkey, crawled into `solana_attestations`, and aggregated by `/api/agents/solana-reputation`. Off-chain pump.fun behavior signals land in `pumpfun_signals` and feed the same score. See [Solana reputation](#sec-398) and [solana-pumpfun.md](#sec-397).
+- **Validation**: no registry contract either; validations are `threews.validation.v1` SPL Memo attestations (including the automatic glb-schema attestation at register-confirm), plus SAS credentialed validations signed by the platform authority ([SAS attestations](#sec-377)).
## What's intentionally not on Solana yet
- **Delegated wallet (EIP-712)**: There is no equivalent for Solana agents. Owner = the wallet that signed the mint.
-- **Cross-chain identifier**: EVM agents use `eip155:<chainId>:<registry>:<agentId>` (CAIP-10). The user-signed flow stores the asset pubkey directly; only the bulk deploy path records a CAIP-2-style `solana:<cluster-genesis>` chain id in `meta.onchain.chain` (see [onchain-agents.md](#sec-304)).
+- **Cross-chain identifier**: EVM agents use `eip155:<chainId>:<registry>:<agentId>` (CAIP-10). The user-signed flow stores the asset pubkey directly; only the bulk deploy path records a CAIP-2-style `solana:<cluster-genesis>` chain id in `meta.onchain.chain` (see [onchain-agents.md](#sec-308)).
- **Discovery**: `agent-registration.json` publishes the platform-level card and x402 catalog, but its `registrations` array does not list individual Solana agents. Adding them means defining a JSON schema for Metaplex Core assets; not done yet.
A full ERC-8004-equivalent on Solana (Identity / Reputation / Validation as Anchor programs with a parallel JS client) remains a separate, larger piece of work; this document covers what ships today.
@@ -86616,7 +87366,7 @@ A full ERC-8004-equivalent on Solana (Identity / Reputation / Validation as Anch
---
-<a id="sec-395"></a>
+<a id="sec-400"></a>
> **Source:** `docs/spatial-mcp.md` · [↑ table of contents](#table-of-contents)
@@ -86747,7 +87497,7 @@ Free 3D Studio (`structuredContent.spatial`): `forge_free`, `text_to_avatar`, `m
---
-<a id="sec-396"></a>
+<a id="sec-401"></a>
> **Source:** `docs/specs/agent-trading.md` · [↑ table of contents](#table-of-contents)
@@ -86834,7 +87584,7 @@ Real routes (no mocks), server-side guards with tests (including the $THREE-sell
---
-<a id="sec-397"></a>
+<a id="sec-402"></a>
> **Source:** `docs/splat.md` · [↑ table of contents](#table-of-contents)
@@ -86905,7 +87655,7 @@ Supported inputs at a glance:
---
-<a id="sec-398"></a>
+<a id="sec-403"></a>
> **Source:** `docs/stage.md` · [↑ table of contents](#table-of-contents)
@@ -87069,16 +87819,16 @@ The browser resolves the realtime server from, in order: `window.STAGE_SERVER_UR
## Related
- [Agent wallets](#sec-072): the host wallet a stage provisions at creation and receives tips into.
-- [Lip-sync](#sec-264) and [Voice Lab](#sec-506): the speech and mouth-shape machinery the host performs with.
+- [Lip-sync](#sec-267) and [Voice Lab](#sec-512): the speech and mouth-shape machinery the host performs with.
- [Agent abilities](#sec-010): the always-on Stage Show variant that runs the same ShowDirector inside an agent's own screen.
-- [Notifications](#sec-293): the go-live and tip notifications a stage emits.
-- [Agora](#sec-075) and [IRL presence](#sec-256): the other rooms on the same realtime backbone, with the same presence discipline.
+- [Notifications](#sec-297): the go-live and tip notifications a stage emits.
+- [Agora](#sec-075) and [IRL presence](#sec-259): the other rooms on the same realtime backbone, with the same presence discipline.
- [Multiplayer server](../multiplayer/README.md): how the room server is run and deployed.
- Pages: [/agents](https://three.ws/agents) to find a host, [/club](https://three.ws/club) and [/theater](https://three.ws/theater) for the other live 3D venues.
---
-<a id="sec-399"></a>
+<a id="sec-404"></a>
> **Source:** `docs/start-here.md` · [↑ table of contents](#table-of-contents)
@@ -87112,9 +87862,9 @@ Think of it as giving your AI a body and a face. Instead of a plain text chatbox
## Two kinds of people use three.ws
-**Creators (no code required):** You want to publish a 3D AI character — for your business, your personal site, a product, or just for fun. You use the web interface to pick an avatar, describe the agent's personality, and get an embed snippet to drop into your site. Start with [Make your first agent →](#sec-268)
+**Creators (no code required):** You want to publish a 3D AI character — for your business, your personal site, a product, or just for fun. You use the web interface to pick an avatar, describe the agent's personality, and get an embed snippet to drop into your site. Start with [Make your first agent →](#sec-272)
-**Developers:** You want to build on top of the platform — integrate the `<agent-3d>` web component, write custom skills, call the REST API, or self-host the stack. Start with the [Introduction →](#sec-255) or [Quick start →](#sec-361)
+**Developers:** You want to build on top of the platform — integrate the `<agent-3d>` web component, write custom skills, call the REST API, or self-host the stack. Start with the [Introduction →](#sec-258) or [Quick start →](#sec-366)
---
@@ -87138,15 +87888,15 @@ For a deeper explanation of how agents and avatars differ, see [Agents vs. Avata
If you're here to create and share agents rather than write code, follow this path in order:
1. **[Agents vs. Avatars](#sec-073)** — understand the two core concepts (5 min read)
-2. **[Make your first agent](#sec-268)** — create a 3D AI character in the browser, no code
-3. **[Share & embed](#sec-378)** — get the embed snippet and put your agent anywhere
-4. **[Do I need crypto?](#sec-178)** — honest answers to the wallet and payment questions
+2. **[Make your first agent](#sec-272)** — create a 3D AI character in the browser, no code
+3. **[Share & embed](#sec-383)** — get the embed snippet and put your agent anywhere
+4. **[Do I need crypto?](#sec-180)** — honest answers to the wallet and payment questions
-Make something the community upvotes and it can reach beyond three.ws: the top-voted forge models are published to our official Sketchfab account, prompt and backlink included. See [Sketchfab showcase](#sec-384).
+Make something the community upvotes and it can reach beyond three.ws: the top-voted forge models are published to our official Sketchfab account, prompt and backlink included. See [Sketchfab showcase](#sec-389).
-Generations don't need a babysitter, either: start a forge job, close the tab, and the platform finishes it, saves it to your gallery, and notifies you when it's ready. See [Background generation](#sec-222).
+Generations don't need a babysitter, either: start a forge job, close the tab, and the platform finishes it, saves it to your gallery, and notifies you when it's ready. See [Background generation](#sec-225).
-Curious what happens between the prompt and the model? [How the Forge works](#sec-239) tells the story in plain language; [the Forge pipeline](#sec-224) is the full engineering deep dive.
+Curious what happens between the prompt and the model? [How the Forge works](#sec-242) tells the story in plain language; [the Forge pipeline](#sec-227) is the full engineering deep dive.
---
@@ -87154,85 +87904,85 @@ Curious what happens between the prompt and the model? [How the Forge works](#se
- **Just exploring?** → Open [Discover](/discover) to browse agents others have built
- **Creating your first agent** → Go to [/start](/start) — a 5-step wizard walks you through it
-- **Want to know why the avatars feel alive?** → [Procedural animation](#sec-334) — the runtime IK layers that run on top of the recorded clips: gaze that follows your cursor or meets your eyes, and feet that land on uneven ground instead of floating over it
+- **Want to know why the avatars feel alive?** → [Procedural animation](#sec-339) — the runtime IK layers that run on top of the recorded clips: gaze that follows your cursor or meets your eyes, and feet that land on uneven ground instead of floating over it
- **Want your agent to perform, not just react?** → [Choreography](#sec-140): compose gestures into a named routine on a real timeline at [/choreograph](https://three.ws/choreograph), preview the whole performance on a live avatar, save it to your agent, and play it from any embed with `el.playRoutine('welcome')`. A routine is also just a link, so you can share one with someone who has no account
-- **Want your avatar to sign in ASL?** → Start with the 15-minute walkthrough, [Make your avatar sign](https://three.ws/tutorials/sign-with-your-avatar): type a phrase and watch it signed at [/sign-language](https://three.ws/sign-language), share it as a link (`?say=happy+to+meet+you`), spell a word onto your own avatar and export it as an animated GLB, turn on signed chat replies with the 🤟 toggle or the `sign-language` embed attribute, and fingerspell back with your webcam. The full reference is [Sign language](#sec-381)
+- **Want your avatar to sign in ASL?** → Start with the 15-minute walkthrough, [Make your avatar sign](https://three.ws/tutorials/sign-with-your-avatar): type a phrase and watch it signed at [/sign-language](https://three.ws/sign-language), share it as a link (`?say=happy+to+meet+you`), spell a word onto your own avatar and export it as an animated GLB, turn on signed chat replies with the 🤟 toggle or the `sign-language` embed attribute, and fingerspell back with your webcam. The full reference is [Sign language](#sec-386)
- **Wondering who the little character in the corner is?** → [The agent shell](#sec-059) — every visitor gets a named agent in the first five seconds (claim it to make it real), the ⌘K palette runs real commands (`forge …`, `digest`, `price btc`, `ask …`), and shell pages navigate without ever unloading your agent
- **Want to drive your agent's computer yourself?** → [Take the wheel](#sec-058), every agent has a live screen you can watch on [/agent-screen](https://three.ws/agent-screen); if you own it, click **Take control** to grab the wheel of its real cast browser (mouse, scroll, keyboard, navigation). The agent stands aside while you drive, and the browser holds no wallet, so control can never move funds
- **Meeting avatars in the worlds?** → Press <kbd>I</kbd> on anyone in `/play`, `/city`, a coin world, or `/agora` to see who they are — the [avatar inspector](#sec-112) shows their reputation, wallet, and profile
-- **Running a live event in the world?** → [Live events in `/play`](#sec-328): one config file turns the `$THREE` home town into a place something is happening in: a countdown chip, an agenda drawer that knows what is on right now and what is next, a gold banner at every segment change, and a fireworks show every client renders identically from the wall clock without a single packet. Covers the config, the six phases, previewing without waiting for the date, and the browser audit to run before you go live
-- **Want people to keep something for showing up?** -> [Event souvenirs](#sec-216): everyone who walks into the event world while an event is live is handed a free commemorative wearable, kept forever, and once the window closes it is never granted again. No purchase path, before or after, which is the whole point: a cosmetic you can buy later says nothing about you. Covers the one-line config (the same file the countdown already reads), what the server refuses to do with a mistyped one, and how to author the next item
+- **Running a live event in the world?** → [Live events in `/play`](#sec-333): one config file turns the `$THREE` home town into a place something is happening in: a countdown chip, an agenda drawer that knows what is on right now and what is next, a gold banner at every segment change, and a fireworks show every client renders identically from the wall clock without a single packet. Covers the config, the six phases, previewing without waiting for the date, and the browser audit to run before you go live
+- **Want people to keep something for showing up?** -> [Event souvenirs](#sec-218): everyone who walks into the event world while an event is live is handed a free commemorative wearable, kept forever, and once the window closes it is never granted again. No purchase path, before or after, which is the whole point: a cosmetic you can buy later says nothing about you. Covers the one-line config (the same file the countdown already reads), what the server refuses to do with a mistyped one, and how to author the next item
- **Want your community to fight another one?** -> [Coin Wars](#sec-146): every coin world's plaza has a war portal showing that community's live Elo standing, its last battles, and any war running right now. Press `E` to prove you hold the coin, queue the community, and the moment a second one queues you both drop into the same arena at `/play/war`. Covers the matchKey rendezvous, the signed pairing that stops a fighter inventing an opponent, the `/api/wars` surface, and the return link that lands you back in the world you left
-- **Changing anything in the `/play` world?** → [How `/play` stays safe, honest, and light](#sec-327): the invariants that keep the largest interactive surface on the platform from breaking. Untrusted names never become markup, a coin's artwork can't escape its CSS, a broken world link says so instead of building a phantom world, a reconnect retires the peers who left, and everything the world loads gets freed (the difference between "works on a laptop" and "works on a phone"). Each rule names the failure it prevents, because each one shipped once
-- **Making `/play` load faster (or worried you slowed it down)?** → [Why `/play` opens fast, and how to keep it that way](#sec-325): the boot-cost invariants behind the heaviest page on the platform. The physics runtime is never a static import, decorative content waits for the world to settle, shader programs compile before the frame that draws them, the scene is lit on its first frame rather than after a download, and the quality governor never judges a world that is still assembling. Each rule names the regression it prevents, with the measurement that found it
-- **Slowing down an ordinary page (or trying to speed one up)?** → [What the site's load numbers are, and the four rules that keep them there](#sec-383): the load-cost invariants for every page that is not `/play`. A catalogue grid never lays out the rows nobody can see, analytics waits for the first idle moment, the CDN bundle is minified despite a build-tool rule that says otherwise, below-the-fold sections load below the fold, and thumbnails decode off the critical path. Each rule carries the Lighthouse measurement that produced it, and the command to re-run it
-- **Following creators?** → [The social layer](#sec-391): follow anyone from their `/u/:username` portfolio, watch their work land on [/feed](/feed), climb the [/rankings](/rankings) leaderboards with streaks and badges, get bell notifications for remixes, DMs, and coin graduations, and search everything at once on [/search](/search)
-- **Placing agents in the real world?** → [IRL](#sec-256): pin an agent at a real GPS spot from your phone, and anyone who physically walks up can see it, talk to it, and pay it. Real crypto can be escrowed at places ([Money Drops](irl.md#money-drops)) and agents sign proofs that you were really there ([World Lines](irl.md#world-lines))
-- **Making 3D models?** → [The free 3D Studio MCP](#sec-274) turns a prompt into a model, avatar, or rigged character — and lets you refine it by talking to it (*"make it metallic"*) with a revertable version history. Publish a model as remixable and earn on-chain royalties when others build on it: [the remix economy](#sec-365). Vote on the best community models and win the weekly board: [Forge-Off](#sec-223)
+- **Changing anything in the `/play` world?** → [How `/play` stays safe, honest, and light](#sec-332): the invariants that keep the largest interactive surface on the platform from breaking. Untrusted names never become markup, a coin's artwork can't escape its CSS, a broken world link says so instead of building a phantom world, a reconnect retires the peers who left, and everything the world loads gets freed (the difference between "works on a laptop" and "works on a phone"). Each rule names the failure it prevents, because each one shipped once
+- **Making `/play` load faster (or worried you slowed it down)?** → [Why `/play` opens fast, and how to keep it that way](#sec-330): the boot-cost invariants behind the heaviest page on the platform. The physics runtime is never a static import, decorative content waits for the world to settle, shader programs compile before the frame that draws them, the scene is lit on its first frame rather than after a download, and the quality governor never judges a world that is still assembling. Each rule names the regression it prevents, with the measurement that found it
+- **Slowing down an ordinary page (or trying to speed one up)?** → [What the site's load numbers are, and the four rules that keep them there](#sec-388): the load-cost invariants for every page that is not `/play`. A catalogue grid never lays out the rows nobody can see, analytics waits for the first idle moment, the CDN bundle is minified despite a build-tool rule that says otherwise, below-the-fold sections load below the fold, and thumbnails decode off the critical path. Each rule carries the Lighthouse measurement that produced it, and the command to re-run it
+- **Following creators?** → [The social layer](#sec-396): follow anyone from their `/u/:username` portfolio, watch their work land on [/feed](/feed), climb the [/rankings](/rankings) leaderboards with streaks and badges, get bell notifications for remixes, DMs, and coin graduations, and search everything at once on [/search](/search)
+- **Placing agents in the real world?** → [IRL](#sec-259): pin an agent at a real GPS spot from your phone, and anyone who physically walks up can see it, talk to it, and pay it. Real crypto can be escrowed at places ([Money Drops](irl.md#money-drops)) and agents sign proofs that you were really there ([World Lines](irl.md#world-lines))
+- **Making 3D models?** → [The free 3D Studio MCP](#sec-278) turns a prompt into a model, avatar, or rigged character — and lets you refine it by talking to it (*"make it metallic"*) with a revertable version history. Publish a model as remixable and earn on-chain royalties when others build on it: [the remix economy](#sec-370). Vote on the best community models and win the weekly board: [Forge-Off](#sec-226)
- **Using ChatGPT?** → [AR in ChatGPT](#sec-139) is how a sentence typed into ChatGPT becomes a 3D model standing in your room, from the free generation lane to the one-tap AR link; [your first prompt to 3D](/tutorials/first-prompt-to-3d) walks you through it in five minutes
-- **Making videos without showing your face?** → [Motion Swap](#sec-289) — upload a video of yourself and get it back with your 3D avatar performing your exact motion instead of you; pose tracking and masking run server-side, compositing and export happen in your browser at [/motion-swap](https://three.ws/motion-swap)
-- **Want a support chat with a face on your own site?** → [Concierge](#sec-152) — a one-tag chat widget where a rigged 3D avatar lipsyncs streaming answers grounded in your live page, with voice in and out; [the build tutorial](#sec-427) shows how every part works
+- **Making videos without showing your face?** → [Motion Swap](#sec-293) — upload a video of yourself and get it back with your 3D avatar performing your exact motion instead of you; pose tracking and masking run server-side, compositing and export happen in your browser at [/motion-swap](https://three.ws/motion-swap)
+- **Want a support chat with a face on your own site?** → [Concierge](#sec-153) — a one-tag chat widget where a rigged 3D avatar lipsyncs streaming answers grounded in your live page, with voice in and out; [the build tutorial](#sec-433) shows how every part works
- **Want a full-body avatar assistant on your site instead?** → [Assistant widget](#sec-101) — a launcher button opens an animated 3D character standing directly on your page (or a color/gradient), with a free-lane or bring-your-own-key chatbot and a speak mode that says whatever you type, out loud, in a speech bubble
-- **Trading?** → [The trading surfaces](#sec-415) maps the solo stack (Radar, Coin Intelligence, Live Trade Feed, Watchlist, Mission Control); [trading arenas](#sec-411) covers tournaments, the theater, vaults, and swarms; [Oracle](#sec-315) is the conviction engine underneath all of it
-- **Want your agent to trade for you?** → [Agent Sniper](#sec-061) — the full autonomous-trading pipeline (entry gates, the simulate-the-sell trade firewall, hash-chained decision ledger, exit ladder), with the audited case study of the platform's first live +42% trade; [arm one in minutes](#sec-424)
+- **Trading?** → [The trading surfaces](#sec-420) maps the solo stack (Radar, Coin Intelligence, Live Trade Feed, Watchlist, Mission Control); [trading arenas](#sec-416) covers tournaments, the theater, vaults, and swarms; [Oracle](#sec-320) is the conviction engine underneath all of it
+- **Want your agent to trade for you?** → [Agent Sniper](#sec-061) — the full autonomous-trading pipeline (entry gates, the simulate-the-sell trade firewall, hash-chained decision ledger, exit ladder), with the audited case study of the platform's first live +42% trade; [arm one in minutes](#sec-430)
- **Wondering what stands between the chat agent and your wallet?** → [The agent runtime and transaction guard](#sec-057): every fund-moving tool call in /chat is preflighted through a seven-layer policy engine (blacklist, approval policy, dollar caps, spend envelope, MEV slippage clamp) before the wallet ever prompts, and the approval modal shows the verdict; the engine ships as [`@three-ws/agent-runtime`](../packages/agent-runtime) for your own agents
-- **Curious how the trading fleet improves itself?** → [Earned autonomy](#sec-390), where each arm's own realized record decides how much rope it gets: wider tuning bounds, unlocked settings, a bigger share of the fleet budget, and a deeper evidence pack in front of its LLM judge, all re-earned continuously and none of it able to touch a safety rail
-- **Trusting an agent with money?** → [Custody you can verify](#sec-170) — spend limits, freeze, Merkle proof-of-custody, and social recovery; [claim your wallet](#sec-409) turns any pump.fun track record into a public, provable Trader Card. Every real-funds feature sits behind the [risk acknowledgment](#sec-370) — read the [Risk Disclosure](https://three.ws/legal/risk) before committing anything
-- **Need a track record another app can verify?** → [Trader Passport](#sec-410): the daily on-chain attestation of a trader's score, served as a public credential any terminal can fetch, pin, and re-check against Solana without trusting us. Includes a database-free verify endpoint and the committed-versus-live drift, so a stale snapshot can never pass as a current claim
-- **Wondering how your avatar ends up on a chain without you doing anything?** → [Draft agent mint](#sec-180): every finished reconstruction is written to durable storage and minted as an inactive on-chain identity in the background, a Metaplex Core asset on Solana with an ERC-8004 registration behind its own flag. No wallet prompt, no fee, nothing to remember. Covers the network flags (including the single switch that arms mainnet), what lands in the database, and the devnet proof script
+- **Curious how the trading fleet improves itself?** → [Earned autonomy](#sec-395), where each arm's own realized record decides how much rope it gets: wider tuning bounds, unlocked settings, a bigger share of the fleet budget, and a deeper evidence pack in front of its LLM judge, all re-earned continuously and none of it able to touch a safety rail
+- **Trusting an agent with money?** → [Custody you can verify](#sec-172) — spend limits, freeze, Merkle proof-of-custody, and social recovery; [claim your wallet](#sec-414) turns any pump.fun track record into a public, provable Trader Card. Every real-funds feature sits behind the [risk acknowledgment](#sec-375) — read the [Risk Disclosure](https://three.ws/legal/risk) before committing anything
+- **Need a track record another app can verify?** → [Trader Passport](#sec-415): the daily on-chain attestation of a trader's score, served as a public credential any terminal can fetch, pin, and re-check against Solana without trusting us. Includes a database-free verify endpoint and the committed-versus-live drift, so a stale snapshot can never pass as a current claim
+- **Wondering how your avatar ends up on a chain without you doing anything?** → [Draft agent mint](#sec-182): every finished reconstruction is written to durable storage and minted as an inactive on-chain identity in the background, a Metaplex Core asset on Solana with an ERC-8004 registration behind its own flag. No wallet prompt, no fee, nothing to remember. Covers the network flags (including the single switch that arms mainnet), what lands in the database, and the devnet proof script
- **Want an agent's on-chain history without scanning a chain yourself?** → [The agent index](#sec-054): the platform's own cross-chain index of agent registrations, token launches, reputation attestations, transfers and delegations, Solana first and EVM alongside it. One public endpoint returns the timeline with the absolute on-chain timestamp and a block-explorer link per event, plus how stale the index is, so "no history" is never confused with "we have not looked"
-- **Vetting a counterparty before you pay it?** → [Trust primitives](#sec-417) — the cross-chain Agent Reputation endpoint scores ANY wallet, mint, or agent id (Solana or EVM) 0–100 from real on-chain evidence, in one paid call, before your agent transacts
+- **Vetting a counterparty before you pay it?** → [Trust primitives](#sec-423) — the cross-chain Agent Reputation endpoint scores ANY wallet, mint, or agent id (Solana or EVM) 0–100 from real on-chain evidence, in one paid call, before your agent transacts
- **Wondering where the platform's money goes?** → [The autonomous economy](#sec-104): how the on-chain treasury funds itself, the funding-root → engines → sweepback loop, the locks that keep every dollar inside platform-owned wallets, and the two leak scanners that audit every wallet on-chain every few minutes (as of 2026-07-12: 44,122 transactions scanned, zero leaks; the live totals stay re-derivable from each scanner's own cursor)
-- **Publishing news, or wondering what we show of yours?** → [Publisher rights in the news reader](#sec-292) — 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-269) — 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-371) — 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-538) — 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-537) — 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
+- **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
- **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
-- **Want a branded on-chain address?** → [Vanity grinder](#sec-502) — grind a Solana address that starts with your ticker (branded token mint or agent/treasury wallet) in one paid USDC call; keypair or importable mnemonic, nothing stored, optional sealed delivery, plus a provably-fair variant and a pre-ground premium inventory
-- **Going Pro?** → [Paid plans](#sec-324) — upgrade with a single on-chain payment in USDC, SOL, or $THREE (the platform coin takes 20% off); [hold-to-access](#sec-238) covers the separate hold-$THREE tier ladder
-- **Building a community perk?** → [Token-gated 3D embeds](#sec-407) — turn an avatar or on-chain agent into a holder-only interactive embed; visitors prove a real, server-verified on-chain balance before the live scene renders, no download-only gate
-- **Watching a generation cook?** → [Generation Watch](#sec-230): the /watch page tracks a running text-to-3D generation live, from the countdown to the automatic hand-off into the viewer
-- **Browsing what the agents bought?** → [The Agent-Forged Gallery](#sec-226): 3D props purchased by autonomous agents with real USDC over x402, each carrying its paying wallet, price, and on-chain settlement receipt
-- **Need a ready-made character or prop?** → The [Character Library](#sec-136) has 106 rigged characters (one click into the Studio, Animation Studio, or an embed) and the [Object Library](#sec-301) has hundreds of CC0 props with live preview, AR placement, and direct GLB download
-- **Rendering avatars outside the viewer?** → [Media and render API](#sec-278): avatar PNG renders for `<img>` tags, posed clip renders, the runtime GLB optimizer, the CORS-open model proxy, and the free vision and speech-to-text endpoints; companion to the [3D API](#sec-001)
-- **Putting avatars in your build pipeline?** → [Avatar CLI](#sec-108): four offline commands that scaffold a hash-anchored avatar manifest from a wallet and a GLB, validate it against the published schema, and print an embed snippet that renders. Non-zero exits make it a release gate, so a re-exported mesh fails your build instead of your page. [Ship an avatar manifest](#sec-468) is the guided walkthrough
-- **Uploaded an avatar that loads but never moves?** → [Rig Doctor](#sec-369): drop the `.glb` and find out in a second why. It names the skeleton convention, scores torso, arms, hands, and legs separately so you learn which limbs stay frozen rather than a useless overall percentage, plays real clips on your own rig to prove it, and hands back a repaired file when the joint names are the only problem. Runs entirely in your browser; nothing is uploaded
-- **Minting your work on-chain?** → [Minted 3D assets](#sec-283): the /minted gallery of avatars minted as Metaplex Core NFTs, the opt-in mint flow, baked provenance, and enforced remix royalties
-- **Letting an agent spend without your key?** → [Payment Sessions](#sec-321): fund a capped envelope from prepaid credits, hand the agent a bearer token, and it pays x402 endpoints under your caps and allowlist, refundable on cancel
-- **Paying on a schedule instead of per call?** → [Recurring payments](#sec-364): sign one permission, then a fixed USDC amount moves every day or week (or gets swapped into a token, for DCA) without you signing again. Manage the whole lifecycle at [/recurring](https://three.ws/recurring): create, pause, resume, cancel, read every charge a schedule ever made, and see what is being paid into your own agents. A failed period is never a silent gap: a revoked permission pauses the schedule with the reason on it, a network blip retries for three ticks, and a timeout is never retried because that is the one failure that could charge you twice
-- **Earning proof you were somewhere?** → [World Lines](#sec-512): walk to an agent's real-world spot, complete its challenge (a tap, a passphrase, or a quiz), and its wallet signs an ed25519 proof of presence you own and anyone can verify. No coordinate finer than a roughly 1 km cell is ever stored
-- **Want your walking to count for something?** → [The Walk Leaderboard](#sec-507): distance, sites, and time ranked daily, weekly, and all-time, for signed-in and anonymous walkers alike, with an honest account of how a session is counted and what a guard can and cannot prove
+- **Want a branded on-chain address?** → [Vanity grinder](#sec-508) — grind a Solana address that starts with your ticker (branded token mint or agent/treasury wallet) in one paid USDC call; keypair or importable mnemonic, nothing stored, optional sealed delivery, plus a provably-fair variant and a pre-ground premium inventory
+- **Going Pro?** → [Paid plans](#sec-329) — upgrade with a single on-chain payment in USDC, SOL, or $THREE (the platform coin takes 20% off); [hold-to-access](#sec-241) covers the separate hold-$THREE tier ladder
+- **Building a community perk?** → [Token-gated 3D embeds](#sec-412) — turn an avatar or on-chain agent into a holder-only interactive embed; visitors prove a real, server-verified on-chain balance before the live scene renders, no download-only gate
+- **Watching a generation cook?** → [Generation Watch](#sec-233): the /watch page tracks a running text-to-3D generation live, from the countdown to the automatic hand-off into the viewer
+- **Browsing what the agents bought?** → [The Agent-Forged Gallery](#sec-229): 3D props purchased by autonomous agents with real USDC over x402, each carrying its paying wallet, price, and on-chain settlement receipt
+- **Need a ready-made character or prop?** → The [Character Library](#sec-136) has 106 rigged characters (one click into the Studio, Animation Studio, or an embed) and the [Object Library](#sec-305) has hundreds of CC0 props with live preview, AR placement, and direct GLB download
+- **Rendering avatars outside the viewer?** → [Media and render API](#sec-282): avatar PNG renders for `<img>` tags, posed clip renders, the runtime GLB optimizer, the CORS-open model proxy, and the free vision and speech-to-text endpoints; companion to the [3D API](#sec-001)
+- **Putting avatars in your build pipeline?** → [Avatar CLI](#sec-108): four offline commands that scaffold a hash-anchored avatar manifest from a wallet and a GLB, validate it against the published schema, and print an embed snippet that renders. Non-zero exits make it a release gate, so a re-exported mesh fails your build instead of your page. [Ship an avatar manifest](#sec-474) is the guided walkthrough
+- **Uploaded an avatar that loads but never moves?** → [Rig Doctor](#sec-374): drop the `.glb` and find out in a second why. It names the skeleton convention, scores torso, arms, hands, and legs separately so you learn which limbs stay frozen rather than a useless overall percentage, plays real clips on your own rig to prove it, and hands back a repaired file when the joint names are the only problem. Runs entirely in your browser; nothing is uploaded
+- **Minting your work on-chain?** → [Minted 3D assets](#sec-287): the /minted gallery of avatars minted as Metaplex Core NFTs, the opt-in mint flow, baked provenance, and enforced remix royalties
+- **Letting an agent spend without your key?** → [Payment Sessions](#sec-326): fund a capped envelope from prepaid credits, hand the agent a bearer token, and it pays x402 endpoints under your caps and allowlist, refundable on cancel
+- **Paying on a schedule instead of per call?** → [Recurring payments](#sec-369): sign one permission, then a fixed USDC amount moves every day or week (or gets swapped into a token, for DCA) without you signing again. Manage the whole lifecycle at [/recurring](https://three.ws/recurring): create, pause, resume, cancel, read every charge a schedule ever made, and see what is being paid into your own agents. A failed period is never a silent gap: a revoked permission pauses the schedule with the reason on it, a network blip retries for three ticks, and a timeout is never retried because that is the one failure that could charge you twice
+- **Earning proof you were somewhere?** → [World Lines](#sec-518): walk to an agent's real-world spot, complete its challenge (a tap, a passphrase, or a quiz), and its wallet signs an ed25519 proof of presence you own and anyone can verify. No coordinate finer than a roughly 1 km cell is ever stored
+- **Want your walking to count for something?** → [The Walk Leaderboard](#sec-513): distance, sites, and time ranked daily, weekly, and all-time, for signed-in and anonymous walkers alike, with an honest account of how a session is counted and what a guard can and cannot prove
- **Driving an agent wallet from code?** → [The agent wallet control API](#sec-071): the reference for all seven owner-only surfaces on an agent's Solana wallet (scoped session keys, programmable orders, plain-language intents, Treasury Autopilot, portfolio P&L, guardians and the dead-man switch, and the anomaly guard), each with its exact JSON, every error, and a curl example
- **Letting your agent pay other agents on its own?** → [Autonomous agent-to-agent payments](#sec-007): the signed Intent Mandate that authorizes the class of spend, the seven gates every payment passes, the per-call / per-day / per-counterparty ceilings and the kill switch that halts a running agent mid-mandate, the receipt each payment leaves in the owner's ledger, and the one command that proves all of it against a real database
- **Turning a token into a paid endpoint?** → [CA to x402](#sec-133): paste a contract address and get a live agent-payable market-intel endpoint, discoverable in the bazaar, with the generated snippets
-- **Want other agents to pay for your tools?** → [Monetize an MCP server](#sec-452): build an MCP server that charges per `tools/call` in USDC on Solana, with a free orientation tool in front of the paid ones and the verify-work-settle ordering that means a failed call never takes money. The runnable code is [examples/paid-mcp-server](https://github.com/nirholas/three.ws/tree/main/examples/paid-mcp-server)
-- **Published a skill and want to get paid for it?** → [Skill royalties](#sec-386): every paid call to a skill you wrote routes your share straight to your own wallet at settlement (Solana first), with the exact split, the ledger where you watch it land with an explorer link per payout, and a proof lane that verifies the whole accounting path without moving a cent
-- **Checking whether the economy is real?** → [Agent economy volume](#sec-052) counts only settled agent-to-agent USDC for paid skills, and [Viability](#sec-504) shows the unit economics (GMV, take rate, repeat buyers, realized P&L) from on-chain data with no projections
-- **Designing an agent's look and brand?** → [Agent Identity Studio](#sec-053) turns a brand brief into a rigged avatar plus posed studio renders; [Living Stages](#sec-398) covers shareable stages; [the Avatar Engines Atlas](#sec-110) is the factual survey of the engines in this space and which ones we animate
+- **Want other agents to pay for your tools?** → [Monetize an MCP server](#sec-458): build an MCP server that charges per `tools/call` in USDC on Solana, with a free orientation tool in front of the paid ones and the verify-work-settle ordering that means a failed call never takes money. The runnable code is [examples/paid-mcp-server](https://github.com/nirholas/three.ws/tree/main/examples/paid-mcp-server)
+- **Published a skill and want to get paid for it?** → [Skill royalties](#sec-391): every paid call to a skill you wrote routes your share straight to your own wallet at settlement (Solana first), with the exact split, the ledger where you watch it land with an explorer link per payout, and a proof lane that verifies the whole accounting path without moving a cent
+- **Checking whether the economy is real?** → [Agent economy volume](#sec-052) counts only settled agent-to-agent USDC for paid skills, and [Viability](#sec-510) shows the unit economics (GMV, take rate, repeat buyers, realized P&L) from on-chain data with no projections
+- **Designing an agent's look and brand?** → [Agent Identity Studio](#sec-053) turns a brand brief into a rigged avatar plus posed studio renders; [Living Stages](#sec-403) covers shareable stages; [the Avatar Engines Atlas](#sec-110) is the factual survey of the engines in this space and which ones we animate
- **Need to prove what an agent was told to do?** → [Signed manifests](agent-manifest.md#signed-manifests-v03): every persona save signs the agent's full configuration, system prompt included, and pins it to IPFS. Anyone with the CID can verify the signature offline (`node scripts/verify-agent-manifest.mjs --cid …`) and diff the pinned record against the agent running today, with no account and no trust in us
-- **Writing about us?** → [The press kit](#sec-333) has the logos, the usage rules, and the boilerplate (editorial use needs no permission), and [the partner ecosystem](#sec-318) maps every partner program to what the integration actually is
-- **Backing an agent with capital?** → [USDC agent vaults](#sec-503): NAV-priced deposits and redemptions, the drawdown breaker that halts a vault, performance-fee claims, and the public audit ledger anyone can read
-- **Funding your own agents?** → [Your master wallet](#sec-488): the per-user custodial hub you fund once, then top up agent wallets, send SOL or USDC, and read on-chain history from
-- **Following a trader instead of picking?** → [Copy trading](#sec-165): follow a leader two ways, either your agent mirroring real Solana trades inside its own spend policy, or sized intents you sign yourself. Nothing is simulated, so the doc covers the leaderboard weighting, the Smart Money directory, and how performance fees accrue
-- **Not ready to risk money on a trader yet?** → [Ghost-copy](#sec-233): paper-copy any verified agent over their real closed on-chain trades and see the equity curve your budget would have had, sized by the same engine that runs live copy trades. No wallet, no signature, no account, and every trade your budget could not reach is listed with the reason
-- **Watching identities land on-chain?** → [On-chain deployments](#sec-175): the live feed of agent identities registering on-chain as it happens, Solana Metaplex Core mints alongside ERC-8004 registrations across 15 EVM chains, with chain footprint and capability stats
-- **Building against the API?** → [The developer platform](#sec-176): API keys, usage metrics, signed webhooks, the one-call MCP connection test, and the public tool and skills catalogs, with a runnable example per endpoint
-- **Auditing an agent's decisions?** → [The Reasoning Ledger](#sec-363): hash-chained, on-chain-anchored records of every consequential agent decision, verifiable by anyone at /ledger
-- **Following Solana traders?** → [KOL Tracker](#sec-259): KOLs ranked by realized P&L computed from their own wallets' on-chain trades (never self-reported), with the public API behind it
+- **Writing about us?** → [The press kit](#sec-338) has the logos, the usage rules, and the boilerplate (editorial use needs no permission), and [the partner ecosystem](#sec-323) maps every partner program to what the integration actually is
+- **Backing an agent with capital?** → [USDC agent vaults](#sec-509): NAV-priced deposits and redemptions, the drawdown breaker that halts a vault, performance-fee claims, and the public audit ledger anyone can read
+- **Funding your own agents?** → [Your master wallet](#sec-494): the per-user custodial hub you fund once, then top up agent wallets, send SOL or USDC, and read on-chain history from
+- **Following a trader instead of picking?** → [Copy trading](#sec-167): follow a leader two ways, either your agent mirroring real Solana trades inside its own spend policy, or sized intents you sign yourself. Nothing is simulated, so the doc covers the leaderboard weighting, the Smart Money directory, and how performance fees accrue
+- **Not ready to risk money on a trader yet?** → [Ghost-copy](#sec-236): paper-copy any verified agent over their real closed on-chain trades and see the equity curve your budget would have had, sized by the same engine that runs live copy trades. No wallet, no signature, no account, and every trade your budget could not reach is listed with the reason
+- **Watching identities land on-chain?** → [On-chain deployments](#sec-177): the live feed of agent identities registering on-chain as it happens, Solana Metaplex Core mints alongside ERC-8004 registrations across 15 EVM chains, with chain footprint and capability stats
+- **Building against the API?** → [The developer platform](#sec-178): API keys, usage metrics, signed webhooks, the one-call MCP connection test, and the public tool and skills catalogs, with a runnable example per endpoint
+- **Auditing an agent's decisions?** → [The Reasoning Ledger](#sec-368): hash-chained, on-chain-anchored records of every consequential agent decision, verifiable by anyone at /ledger
+- **Following Solana traders?** → [KOL Tracker](#sec-262): KOLs ranked by realized P&L computed from their own wallets' on-chain trades (never self-reported), with the public API behind it
- **Listening to the economy?** → [Agent Symphony](#sec-063): /symphony plays the live agent economy as generative music; every event type has a voice, and solo mode isolates one agent by ear
-- **Catching up on your inbox?** → [Notifications](#sec-293): the bell, the /notifications center, category filters, and the full inbox API
-- **Showing off your work?** → [The creator portfolio](#sec-167): everything on your public /u/username page, what makes an item public, and how following works from it
-- **Exploring our history?** → [The Story So Far](#sec-406): three.ws history as an explorable 3D scene at /timeline, and how a new milestone gets added to it
-- **Competing today?** → [Daily Match](#sec-172): live daily standings over real agent output (actions, trades, skill sales, launches), resetting 00:00 UTC
-- **Developer docs** → Read the [Introduction](#sec-255) for the full technical picture
-- **Contributing code?** → [Shared utilities](#sec-379) — the modules to import instead of hand-rolling: sanitized Markdown, toasts, fuzzy search, retry/circuit-breaking, bounded caches and concurrency pools, and safe CSV export
-- **Your agent needs a face?** → [OKX.AI marketplace services](#sec-302) — the Agent Identity Studio and the pay-per-call 3D services other agents buy from us; demo identities at [/agent-identities](/agent-identities)
+- **Catching up on your inbox?** → [Notifications](#sec-297): the bell, the /notifications center, category filters, and the full inbox API
+- **Showing off your work?** → [The creator portfolio](#sec-169): everything on your public /u/username page, what makes an item public, and how following works from it
+- **Exploring our history?** → [The Story So Far](#sec-411): three.ws history as an explorable 3D scene at /timeline, and how a new milestone gets added to it
+- **Competing today?** → [Daily Match](#sec-174): live daily standings over real agent output (actions, trades, skill sales, launches), resetting 00:00 UTC
+- **Developer docs** → Read the [Introduction](#sec-258) for the full technical picture
+- **Contributing code?** → [Shared utilities](#sec-384) — the modules to import instead of hand-rolling: sanitized Markdown, toasts, fuzzy search, retry/circuit-breaking, bounded caches and concurrency pools, and safe CSV export
+- **Your agent needs a face?** → [OKX.AI marketplace services](#sec-306) — the Agent Identity Studio and the pay-per-call 3D services other agents buy from us; demo identities at [/agent-identities](/agent-identities)
- **Buying 3D asset work per call?** → [The 3D Asset Pipeline](#sec-003) — pay a few cents in USDC to rig, remesh, make game-ready, stylize, or background-remove an asset; one call, one finished URL, no account or API key
-- **Want your agent to have a body?** → [Embodiment](#sec-187) — one $1 USDC call turns a prompt or image into a rigged, animated, voiced 3D avatar plus a one-tag embed for any website; no account, no separate rigging step
-- **Building UI?** → [ui-juice](#sec-487) is the shared game-feel library (count-ups, sparklines, ring gauges, live dots, the "it shipped" ripple) every surface animates with
+- **Want your agent to have a body?** → [Embodiment](#sec-189) — one $1 USDC call turns a prompt or image into a rigged, animated, voiced 3D avatar plus a one-tag embed for any website; no account, no separate rigging step
+- **Building UI?** → [ui-juice](#sec-493) is the shared game-feel library (count-ups, sparklines, ring gauges, live dots, the "it shipped" ripple) every surface animates with
- **Teaching another AI to use three.ws?** → [The Agent Skills pack](#sec-060) — portable `SKILL.md` folders that give any Claude surface (Claude Code, the Claude apps, the Agent SDK) three.ws's 3D-creation, wallet, and x402-economy skills; the 3D subset is cross-platform-safe
- **Wondering why a gallery shows an initial instead of a picture?** → [Avatar thumbnails](#sec-116) — where an avatar's preview image comes from, the one rule every code path obeys (never publish a thumbnail URL whose object doesn't exist), the two crons that keep coverage at 100%, and how to run the backfill
@@ -87242,54 +87992,54 @@ Curious what happens between the prompt and the model? [How the Forge works](#se
Deeper references that don't fit a track above but answer real questions:
-- [Docs World](#sec-179): these same docs as a walkable 3D world, where every section is a pavilion you can stroll up to and read inside the scene
-- [Agent Monitor](#sec-288): the ops room at [/monitor](https://three.ws/monitor), twelve live panels covering fleet activity, money, revenue, creations and uptime, plus how to add a panel
+- [Docs World](#sec-181): these same docs as a walkable 3D world, where every section is a pavilion you can stroll up to and read inside the scene
+- [Agent Monitor](#sec-292): the ops room at [/monitor](https://three.ws/monitor), twelve live panels covering fleet activity, money, revenue, creations and uptime, plus how to add a panel
- [Design tokens](#sec-004): the canonical design vocabulary (colors, spacing, type, motion) every surface builds from
-- [NVIDIA models on three.ws](#sec-297): the free hosted inference layer model by model, one key behind text-to-3D, chat, vision, embeddings, safety, and speech
-- [Run an inference node](#sec-253): join the supply side of the open inference network with your own hardware, from clone to a signed, verified result, on CPU or an NVIDIA GPU
-- [Free LLM providers](#sec-228): the failover chain of a dozen free AI providers behind every text completion, what each free tier gives, and how to add the next rung
-- [Tokens API on three.ws](#sec-408): the Solana Foundation asset layer that tells us which mints are the same asset, why it sits second in the market-data cascade, and the one env var that turns it on
-- [NVIDIA Inception membership](#sec-296): what the platform already runs on NVIDIA silicon and what the program adds on top
-- [NVIDIA visibility map](#sec-300): every NVIDIA surface worth being on (Showcase, GTC, NGC, ACE, the forums, social), the verified intake route for each, and the member benefits nobody has claimed yet
+- [NVIDIA models on three.ws](#sec-301): the free hosted inference layer model by model, one key behind text-to-3D, chat, vision, embeddings, safety, and speech
+- [Run an inference node](#sec-256): join the supply side of the open inference network with your own hardware, from clone to a signed, verified result, on CPU or an NVIDIA GPU
+- [Free LLM providers](#sec-231): the failover chain of a dozen free AI providers behind every text completion, what each free tier gives, and how to add the next rung
+- [Tokens API on three.ws](#sec-413): the Solana Foundation asset layer that tells us which mints are the same asset, why it sits second in the market-data cascade, and the one env var that turns it on
+- [NVIDIA Inception membership](#sec-300): what the platform already runs on NVIDIA silicon and what the program adds on top
+- [NVIDIA visibility map](#sec-304): every NVIDIA surface worth being on (Showcase, GTC, NGC, ACE, the forums, social), the verified intake route for each, and the member benefits nobody has claimed yet
- [Big-tech recognition dispatch board](#sec-125): every big-tech surface ranked against every other by the odds of a published mention this week, which six are already one action from shipping, and what to stop chasing
-- [The generator was never the hard part](#sec-299): our Nemotron Nano write-up, published on the NVIDIA Developer Forums
+- [The generator was never the hard part](#sec-303): our Nemotron Nano write-up, published on the NVIDIA Developer Forums
- [three.ws on the AWS Builder Center](#sec-121): the index of our published AWS engineering writing, what code each article documents, and the checklist for publishing the next one
-- [The onboarding tier](#sec-303): why a first-time visitor sees ~20 nav destinations instead of ~100, how the Simple ⇄ Everything switch works, and which tier a new page belongs in
+- [The onboarding tier](#sec-307): why a first-time visitor sees ~20 nav destinations instead of ~100, how the Simple ⇄ Everything switch works, and which tier a new page belongs in
- [What an agent can do](#sec-010): the full abilities dossier, generated from the source article
-- [Use cases and example workflows](#sec-154): five audience-specific walkthroughs tying shipped features to concrete outcomes
-- [UX Flow Atlas](#sec-489): screen-by-screen traces of the platform's core flows, starting with onboarding and creation
-- [Demo routes](#sec-173): the canonical map of every `/demo/*` and `/demos/*` route
-- [Agent trading spec](#sec-396): the proposed agent trading capability contract
-- [ERC-8004 validation attestation](#sec-189): the attestation written when an agent registers on-chain
-- [zauth](#sec-546): the vendored security infrastructure docs our agent auth builds on
+- [Use cases and example workflows](#sec-155): five audience-specific walkthroughs tying shipped features to concrete outcomes
+- [UX Flow Atlas](#sec-495): screen-by-screen traces of the platform's core flows, starting with onboarding and creation
+- [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
- [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-341): the vendored on-chain program reference behind the launch surfaces
-- [pump-fun-mcp at the edge](#sec-337): the Cloudflare Workers mirror of the pump.fun MCP endpoint
-- [Package extraction](#sec-317): how reusable packages graduate out of the monorepo
+- [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
+- [Package extraction](#sec-322): how reusable packages graduate out of the monorepo
- [Agent task briefs](#sec-065): self-contained task prompts for AI agents working on the platform
-- [Troubleshooting and FAQ](#sec-416): fixes organized by symptom
-- [The 3D viewer](#sec-505): the rendering layer reference (model loading, cameras, animation, lighting)
+- [Troubleshooting and FAQ](#sec-422): fixes organized by symptom
+- [The 3D viewer](#sec-511): the rendering layer reference (model loading, cameras, animation, lighting)
- [Avatar Artifact](#sec-107): the standalone viewer page, its ?agent= and ?model= parameters, and the iframe you paste anywhere
-- [Farcaster memory seeding](#sec-220): give an agent your Farcaster voice, proved with a wallet the account already verified, and revoke it in one click
-- [X memory seeding](#sec-515): seed an agent from your public X posts behind an explicit, versioned consent you can revoke (revocation deletes what the seed wrote)
-- [GitHub memory seeding](#sec-234): tick the profile, repositories, and READMEs your agent may read, and nothing outside that list is ever fetched or stored (disconnecting deletes every fact it wrote)
+- [Farcaster memory seeding](#sec-222): give an agent your Farcaster voice, proved with a wallet the account already verified, and revoke it in one click
+- [X memory seeding](#sec-521): seed an agent from your public X posts behind an explicit, versioned consent you can revoke (revocation deletes what the seed wrote)
+- [GitHub memory seeding](#sec-237): tick the profile, repositories, and READMEs your agent may read, and nothing outside that list is ever fetched or stored (disconnecting deletes every fact it wrote)
- [Memory seed connectors](api-reference.md#memory-seed-connectors-api): the public read-only lane behind the seeding demo. Turn a GitHub, X, or Farcaster handle into a footprint payload, then synthesize a memory seed from any subset of them
-- [The catalog quality gate](#sec-376): how a platform-seeded model earns its slot in the public catalog, the two stages it must pass, and why a rejected asset is kept rather than deleted
-- [Likeness evaluation](#sec-263): the Phase 1 verification metric, measured rather than asserted. Every reconstruction is rendered at three yaws and compared to the photos it was built from with an open-source face-recognition embedding, so "4 out of 5" means one fixed, calibrated thing
-- [Examples gallery](#sec-217): copy-paste-ready code for common use cases
+- [The catalog quality gate](#sec-381): how a platform-seeded model earns its slot in the public catalog, the two stages it must pass, and why a rejected asset is kept rather than deleted
+- [Likeness evaluation](#sec-266): the Phase 1 verification metric, measured rather than asserted. Every reconstruction is rendered at three yaws and compared to the photos it was built from with an open-source face-recognition embedding, so "4 out of 5" means one fixed, calibrated thing
+- [Examples gallery](#sec-219): copy-paste-ready code for common use cases
- [Cookbook](/cookbook): recipes you download and run, each one a real file executed against the live API, with the prose explaining why it is shaped that way
-- [Premium](#sec-332): the monthly Data API pass, one on-chain payment replacing per-call micropayments for 30 days
-- [Guardian console](#sec-236): the inbox for the other side of social recovery and inheritance of agent wallets
+- [Premium](#sec-337): the monthly Data API pass, one on-chain payment replacing per-call micropayments for 30 days
+- [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-171): a new deterministic 3D creative challenge every day
-- [x402 Studio](#sec-543): the merchant console for running a paid x402 business on three.ws
-- [Contributing](#sec-160): local environment setup through a mergeable pull request
-- [ERC-8004 smart contracts](#sec-388): contract interfaces, deployed addresses, and how to read and write each registry
-- [Internationalization](#sec-241): how the UI translation catalog works and how to add a locale
+- [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
+- [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
---
-<a id="sec-400"></a>
+<a id="sec-405"></a>
> **Source:** `docs/strategy-objects.md` · [↑ table of contents](#table-of-contents)
@@ -87395,16 +88145,16 @@ curl -s https://three.ws/api/sniper/backtest \
## Related
-- [Custody you can verify](#sec-170) - the spend limits and audit trail every live run is bounded by
-- [Financial controls](#sec-221) - the plain-English rules and firewall layered on the same enforcement point
-- [Oracle](#sec-315) - the conviction engine an entry gate can require before it fires
-- [Trading surfaces](#sec-415) - where equipped strategies execute through the guarded path
-- [Trading arenas](#sec-411) - competitive surfaces where strategies are put to the test
+- [Custody you can verify](#sec-172) - the spend limits and audit trail every live run is bounded by
+- [Financial controls](#sec-223) - the plain-English rules and firewall layered on the same enforcement point
+- [Oracle](#sec-320) - the conviction engine an entry gate can require before it fires
+- [Trading surfaces](#sec-420) - where equipped strategies execute through the guarded path
+- [Trading arenas](#sec-416) - competitive surfaces where strategies are put to the test
- [/strategies](https://three.ws/strategies) and [/strategy-lab](https://three.ws/strategy-lab) - the library and the workbench
---
-<a id="sec-401"></a>
+<a id="sec-406"></a>
> **Source:** `docs/swarms.md` · [↑ table of contents](#table-of-contents)
@@ -87414,9 +88164,9 @@ A **swarm** is a group of agents that pool real SOL into one on-chain treasury a
Two things make this different from a group chat with a shared wallet. The treasury is a real Solana account, so **every balance ties to chain and there are no virtual balances**: contributing and exiting execute actual transfers, spend-guarded and audited. And the kill switch is not the creator's alone, so a creator cannot trap members' funds in a swarm that is losing.
-Live at [three.ws/swarms](https://three.ws/swarms). This document covers the swarm surface specifically. For how agents coordinate in general (delegation, agent-to-agent messaging, task handoff), read [multi-agent](#sec-290) first, which this builds on rather than repeats. For the single-agent trading pipeline that a swarm's treasury reuses, see [agent sniper](#sec-061), and for the earned-autonomy model behind each member's weight, see [earned autonomy](#sec-390).
+Live at [three.ws/swarms](https://three.ws/swarms). This document covers the swarm surface specifically. For how agents coordinate in general (delegation, agent-to-agent messaging, task handoff), read [multi-agent](#sec-294) first, which this builds on rather than repeats. For the single-agent trading pipeline that a swarm's treasury reuses, see [agent sniper](#sec-061), and for the earned-autonomy model behind each member's weight, see [earned autonomy](#sec-395).
-> **This moves real money.** `contribute` and `exit` transfer real SOL on Solana mainnet. Nothing here is simulated. Read the [risk acknowledgment](#sec-370) before joining a swarm with funds you cannot afford to lose.
+> **This moves real money.** `contribute` and `exit` transfer real SOL on Solana mainnet. Nothing here is simulated. Read the [risk acknowledgment](#sec-375) before joining a swarm with funds you cannot afford to lose.
Code: [api/swarms/index.js](../api/swarms/index.js) (directory plus every mutation), [api/swarms/[id].js](../api/swarms/[id].js) (dashboard state and the live stream), [api/_lib/swarms.js](../api/_lib/swarms.js) (policy, treasury, consensus, kill switch).
@@ -87621,14 +88371,14 @@ Every failure returns `{ error, error_description }` with a specific code rather
## Related
-- [Multi-agent coordination](#sec-290), the general model swarms specialize.
-- [Trading arenas](#sec-411), which covers swarms alongside tournaments, the theater, and vaults.
-- [USDC agent vaults](#sec-503), the other way to pool capital behind an agent. A vault has one manager and NAV-priced shares; a swarm has many voters and one treasury.
-- [Custody you can verify](#sec-170) for the spend guards every transfer here passes through.
+- [Multi-agent coordination](#sec-294), the general model swarms specialize.
+- [Trading arenas](#sec-416), which covers swarms alongside tournaments, the theater, and vaults.
+- [USDC agent vaults](#sec-509), the other way to pool capital behind an agent. A vault has one manager and NAV-priced shares; a swarm has many voters and one treasury.
+- [Custody you can verify](#sec-172) for the spend guards every transfer here passes through.
---
-<a id="sec-402"></a>
+<a id="sec-407"></a>
> **Source:** `docs/syndication.md` · [↑ table of contents](#table-of-contents)
@@ -87704,12 +88454,12 @@ so any item added to the feed is picked up on their next crawl with a
canonical URL pointing back to `three.ws/news/<slug>`. Nothing to
configure on our side beyond keeping the feed valid.
-See also: [Partners](#sec-318), [Listings and
-distribution](#sec-265).
+See also: [Partners](#sec-323), [Listings and
+distribution](#sec-269).
---
-<a id="sec-403"></a>
+<a id="sec-408"></a>
> **Source:** `docs/talking-avatar-video.md` · [↑ table of contents](#table-of-contents)
@@ -87722,9 +88472,9 @@ API: `POST /api/avatar/presign-audio` · `GET`/`POST /api/avatar/video-generate`
## Why it exists
-Real-time browser lipsync (see [Lipsync](#sec-264)) is perfect for live avatars, but it cannot produce a finished, shareable file with rendered frames, matched motion, and a scene. Talking Avatar Video is the export path: it takes an avatar you already own and an audio track you supply and returns a polished clip. It closes the loop from "I made an avatar" to "here is a video of my avatar saying this," without any local tooling.
+Real-time browser lipsync (see [Lipsync](#sec-267)) is perfect for live avatars, but it cannot produce a finished, shareable file with rendered frames, matched motion, and a scene. Talking Avatar Video is the export path: it takes an avatar you already own and an audio track you supply and returns a polished clip. It closes the loop from "I made an avatar" to "here is a video of my avatar saying this," without any local tooling.
-Note on scope: the shipped flow uploads an audio file. It does not synthesize speech from a typed script and it does not offer a voice picker inside this page (the page's marketing meta text mentions "type a script, pick a voice," but the UI does neither). To generate the audio first, use [Voice Lab](#sec-506) and bring the resulting clip here.
+Note on scope: the shipped flow uploads an audio file. It does not synthesize speech from a typed script and it does not offer a voice picker inside this page (the page's marketing meta text mentions "type a script, pick a voice," but the UI does neither). To generate the audio first, use [Voice Lab](#sec-512) and bring the resulting clip here.
## How it works
@@ -87800,14 +88550,14 @@ curl -H 'cookie: __Host-sid=<SESSION>' \
## Related
-- [Voice Lab](#sec-506): clone or synthesize the audio track you upload here.
-- [Lipsync](#sec-264): the real-time, in-browser lipsync path (no export).
-- [Selfie to Avatar](#sec-377) and [Avatar reconstruction](#sec-114): create the avatar you render.
+- [Voice Lab](#sec-512): clone or synthesize the audio track you upload here.
+- [Lipsync](#sec-267): the real-time, in-browser lipsync path (no export).
+- [Selfie to Avatar](#sec-382) and [Avatar reconstruction](#sec-114): create the avatar you render.
- Pages: [/create/video](https://three.ws/create/video), [/create](https://three.ws/create), [/dashboard](https://three.ws/dashboard).
---
-<a id="sec-404"></a>
+<a id="sec-409"></a>
> **Source:** `docs/terminal.md` · [↑ table of contents](#table-of-contents)
@@ -87821,7 +88571,7 @@ APIs (all real, all called by the page): `/api/pump/trades-stream` (SSE firehose
## Why it exists
-Early pump.fun trading punishes context-switching. The launch is on one tab, the intel score on another, the wallet in a third, and by the time you have alt-tabbed to all of them the candle is gone. Mission Control collapses the whole loop into a single screen you drive from the home row: read the launch, read whether it is real, size it, and send the order without ever touching the mouse. It sits at the top of the [trading surfaces](#sec-415) map. Radar and Coin Intelligence answer "what launched and is it real," the Live Trade Feed answers "what won," and Mission Control is where you act on all of it. It is the only surface that executes.
+Early pump.fun trading punishes context-switching. The launch is on one tab, the intel score on another, the wallet in a third, and by the time you have alt-tabbed to all of them the candle is gone. Mission Control collapses the whole loop into a single screen you drive from the home row: read the launch, read whether it is real, size it, and send the order without ever touching the mouse. It sits at the top of the [trading surfaces](#sec-420) map. Radar and Coin Intelligence answer "what launched and is it real," the Live Trade Feed answers "what won," and Mission Control is where you act on all of it. It is the only surface that executes.
## How it works
@@ -87926,15 +88676,15 @@ Settled trades for graduated coins are unaffected: they come from
## Related
-- [The trading surfaces: Radar, Mission Control, Live Trade Feed, Watchlist, Coin Intelligence](#sec-415)
-- [Coin Radar](#sec-362) and [Smart Money Radar](#sec-389) feed the same intel into their own surfaces
-- [Oracle: the conviction engine](#sec-315) supplies the fused conviction score
-- [Financial controls and custody guardrails](#sec-221) and [custody](#sec-170) document the server-side rails every order runs through
+- [The trading surfaces: Radar, Mission Control, Live Trade Feed, Watchlist, Coin Intelligence](#sec-420)
+- [Coin Radar](#sec-367) and [Smart Money Radar](#sec-394) feed the same intel into their own surfaces
+- [Oracle: the conviction engine](#sec-320) supplies the fused conviction score
+- [Financial controls and custody guardrails](#sec-223) and [custody](#sec-172) document the server-side rails every order runs through
- Pages: [/terminal](https://three.ws/terminal) · [/radar](https://three.ws/radar) · [/trades](https://three.ws/trades) · [/watchlist](https://three.ws/watchlist)
---
-<a id="sec-405"></a>
+<a id="sec-410"></a>
> **Source:** `docs/three-microbuy.md` · [↑ table of contents](#table-of-contents)
@@ -88096,13 +88846,13 @@ The response reports `fired`, `paid`, `buys`, `pending`, `errors`, `toll_spent_u
## Related
-- [docs/x402-ring-economy.md](#sec-541) — the closed-loop x402 ring the toll settles through.
+- [docs/x402-ring-economy.md](#sec-548) — 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.
---
-<a id="sec-406"></a>
+<a id="sec-411"></a>
> **Source:** `docs/timeline.md` · [↑ table of contents](#table-of-contents)
@@ -88234,7 +88984,7 @@ server reads that route table on boot).
---
-<a id="sec-407"></a>
+<a id="sec-412"></a>
> **Source:** `docs/token-gated-3d-embeds.md` · [↑ table of contents](#table-of-contents)
@@ -88242,7 +88992,7 @@ server reads that route table on boot).
> **Audience:** Creators who want a holder-only interactive 3D scene, and developers wiring the flow up themselves.
-three.ws already lets you embed a live, interactive 3D avatar or on-chain agent on any page with one script tag ([Share & embed](#sec-378), [Embedding Guide](#sec-186)). Token gating adds one thing on top: **the scene only renders for a visitor who holds enough of a specific token** — verified with a real on-chain balance read, not a client-side check anyone could fake.
+three.ws already lets you embed a live, interactive 3D avatar or on-chain agent on any page with one script tag ([Share & embed](#sec-383), [Embedding Guide](#sec-188)). Token gating adds one thing on top: **the scene only renders for a visitor who holds enough of a specific token** — verified with a real on-chain balance read, not a client-side check anyone could fake.
The canonical use case is **$THREE-holder-only content**: a private avatar, a branded scene, a preview only your community can see. The gate also accepts any SPL token at runtime — a project can gate with their own coin — but three.ws never markets or defaults to anything other than `$THREE`.
@@ -88347,13 +89097,13 @@ Every check that matters happens on the server:
- Spec (wire formats, resolver contract, token format): [specs/EMBED_SPEC.md § Token Gating](../specs/EMBED_SPEC.md#token-gating)
- MCP tool: [docs/mcp.md § create_gated_embed](mcp.md#create_gated_embed)
-- Embed runtime this builds on: [`<three-d>` / embed v1](https://three.ws/embed/v1/preview), [Share & embed](#sec-378)
+- Embed runtime this builds on: [`<three-d>` / embed v1](https://three.ws/embed/v1/preview), [Share & embed](#sec-383)
- Nothing rendering where you pasted the snippet? The [Embed Doctor](https://three.ws/embed-doctor) loads your page in a real browser and names the line to change. It checks a `<three-d>` gated snippet exactly like an ungated `<agent-3d>` one, and a locked embed reads as healthy: the lock is the product working, not a failure.
-- Related: [Hold-to-access tiers](#sec-238) (site-wide $THREE tiers, distinct from per-embed gates)
+- Related: [Hold-to-access tiers](#sec-241) (site-wide $THREE tiers, distinct from per-embed gates)
---
-<a id="sec-408"></a>
+<a id="sec-413"></a>
> **Source:** `docs/tokens-xyz.md` · [↑ table of contents](#table-of-contents)
@@ -88519,12 +89269,12 @@ The batch market read is deliberately **not** cached here. Its caller in the mar
## Related
-- [Market Data API](#sec-269) - the pay-per-call x402 endpoints behind every `/markets` page
-- [Free LLM providers](#sec-228) - the same failover-chain pattern applied to text completion
+- [Market Data API](#sec-273) - the pay-per-call x402 endpoints behind every `/markets` page
+- [Free LLM providers](#sec-231) - the same failover-chain pattern applied to text completion
---
-<a id="sec-409"></a>
+<a id="sec-414"></a>
> **Source:** `docs/trader-card.md` · [↑ table of contents](#table-of-contents)
@@ -88543,13 +89293,13 @@ The Wallet Intelligence view renders, for any base-58 address:
## Where the numbers come from
-Nothing here is typed in by the trader. The Oracle smart-money brain continuously indexes pump.fun trading: per-wallet, per-coin buy/sell aggregates observed on-chain, joined with each coin's outcome (graduated, rugged, ATH multiple). Rollup workers grade every indexed wallet into a reputation row — the same pedigree ledger that powers Oracle's WHO pillar ([the conviction engine](#sec-315)). Per-coin P&L is simply `sold − bought` in SOL, with USD as a live enrichment that hides itself rather than guessing when the price feed is down.
+Nothing here is typed in by the trader. The Oracle smart-money brain continuously indexes pump.fun trading: per-wallet, per-coin buy/sell aggregates observed on-chain, joined with each coin's outcome (graduated, rugged, ATH multiple). Rollup workers grade every indexed wallet into a reputation row — the same pedigree ledger that powers Oracle's WHO pillar ([the conviction engine](#sec-320)). Per-coin P&L is simply `sold − bought` in SOL, with USD as a live enrichment that hides itself rather than guessing when the price feed is down.
If a wallet hasn't been indexed yet (the engine tracks wallets it has observed trading pump.fun launches), the page says "not indexed yet" instead of rendering an empty scorecard. "Indexed" means the wallet has been *observed trading*, which happens well before the rollup workers grade it into a reputation row: a wallet with real trades and no grade yet still gets the full ledger and window aggregates, with the reputation panel honestly reading `unproven` until the scorer catches up.
**Realized vs. open.** Win, loss, and win-rate figures count *closed* positions only, because an untouched bag is not a loss. A position counts as closed once effectively all of the bought supply has been sold. `realized_pnl_sol` is the sum over those closed positions; `net_pnl_sol` books every lamport in and out of the loaded window, so it charges an open bag's entry as if it were written off. For a wallet that is still holding, `net_pnl_sol` is the floor and `realized_pnl_sol` is the outcome so far.
-**One precision worth knowing:** the pasted-wallet view reports *raw* on-chain aggregates. The platform's own [trader leaderboard](https://three.ws/leaderboard) — which ranks three.ws agents — applies a stricter pipeline on top: round-trips on coins the trader launched themselves are split out of the credited record ("self-dealing excluded"), snipe hit-rate only counts mints with a proven on-chain birth, and a verification badge requires minimum closed trades, unique coins, and a churn ceiling. Two truth layers, both honest about what they measure: external wallets get the raw read; verified agents get the audited one. Details in [trading-arenas](#sec-411).
+**One precision worth knowing:** the pasted-wallet view reports *raw* on-chain aggregates. The platform's own [trader leaderboard](https://three.ws/leaderboard) — which ranks three.ws agents — applies a stricter pipeline on top: round-trips on coins the trader launched themselves are split out of the credited record ("self-dealing excluded"), snipe hit-rate only counts mints with a proven on-chain birth, and a verification badge requires minimum closed trades, unique coins, and a churn ceiling. Two truth layers, both honest about what they measure: external wallets get the raw read; verified agents get the audited one. Details in [trading-arenas](#sec-416).
## Claiming: one signature, no gas
@@ -88580,18 +89330,18 @@ Returns the identity summary, KPI aggregates, and the per-coin ledger (up to 60
- `claimable` is true once there is a real on-chain record to claim, which includes an indexed-but-not-yet-graded wallet. A wallet with neither is the unindexed case.
- `network` accepts `mainnet` (default) or `devnet`, and scopes both the reputation read and the coin ledger. Anything else falls back to `mainnet`.
-The read is CDN-cacheable for two minutes. It never answers an empty record on a database fault: an unreachable brain returns `503 service_unavailable` with `Retry-After` and `Cache-Control: no-store`, so a transient outage can't be cached as "this trader has no track record". Agent-side, the same pedigree data flows through the intel MCP tools ([docs/mcp.md](#sec-277)).
+The read is CDN-cacheable for two minutes. It never answers an empty record on a database fault: an unreachable brain returns `503 service_unavailable` with `Retry-After` and `Cache-Control: no-store`, so a transient outage can't be cached as "this trader has no track record". Agent-side, the same pedigree data flows through the intel MCP tools ([docs/mcp.md](#sec-281)).
## Related
-- [Trader Passport](#sec-410): the on-chain credential a claimed record earns, and how another app verifies it
-- [Oracle](#sec-315) — the WHO pillar runs on this same wallet-reputation ledger
-- [Trading arenas](#sec-411) — where a verified track record unlocks tournaments, vaults, and mirrors
-- [Trading surfaces](#sec-415) — the solo trading stack
+- [Trader Passport](#sec-415): the on-chain credential a claimed record earns, and how another app verifies it
+- [Oracle](#sec-320) — the WHO pillar runs on this same wallet-reputation ledger
+- [Trading arenas](#sec-416) — where a verified track record unlocks tournaments, vaults, and mirrors
+- [Trading surfaces](#sec-420) — the solo trading stack
---
-<a id="sec-410"></a>
+<a id="sec-415"></a>
> **Source:** `docs/trader-passport.md` · [↑ table of contents](#table-of-contents)
@@ -88755,20 +89505,20 @@ The Proof tab of [`/trader/<agent_id>`](https://three.ws/trader) renders the pas
## Related
-- [Claim your wallet](#sec-409): the read-only track record that comes before any credential
-- [Trading arenas](#sec-411): what a verified record unlocks
-- [Copy trading](#sec-165): leaderboard weighting and performance fees
+- [Claim your wallet](#sec-414): the read-only track record that comes before any credential
+- [Trading arenas](#sec-416): what a verified record unlocks
+- [Copy trading](#sec-167): leaderboard weighting and performance fees
- [API reference](#sec-096): every public endpoint
---
-<a id="sec-411"></a>
+<a id="sec-416"></a>
> **Source:** `docs/trading-arenas.md` · [↑ table of contents](#table-of-contents)
# Competitive & pooled trading: Arena, Sniper Arena, Theater, Vaults, Swarms
-Solo trading has the [five-surface stack](#sec-415). This doc covers the five surfaces where trading becomes a *spectator sport or a team sport*: tournaments with $THREE prizes, a 3D floor of autonomous agents, a live theater with one-click copy trading, backable vaults, and capital-pooling swarms.
+Solo trading has the [five-surface stack](#sec-420). This doc covers the five surfaces where trading becomes a *spectator sport or a team sport*: tournaments with $THREE prizes, a 3D floor of autonomous agents, a live theater with one-click copy trading, backable vaults, and capital-pooling swarms.
One shared truth layer underneath all of them: every ranking, prize, and payout on these pages is computed from `agent_sniper_positions` — the table of real, transaction-signed agent trades — through one scoring module (`api/_lib/trader-stats.js`). Same numbers everywhere; wins are provable by Solscan link, and round-trips on a trader's own launched coins are split out of the credited record rather than counted (the anti-self-dealing rule).
@@ -88810,7 +89560,7 @@ This surface is deliberately read-only — the agents on the floor are run by th
Agents as performers. The theater renders real avatars on a 3D stage reacting to their own **real confirmed on-chain events** — buys, launches, x402 payments — from the platform's live event feed, with a scrolling tape and a replay rail. Three themed rooms rotate the roster (top-trust agents, newest launches, and more). Click any performer for a read-only HUD: trust score, live wallet balances (SOL/USDC/$THREE), and its Solscan address.
-The theater's headline action is **Copy this trader**: signed in, you pick one of your own funded agents, set a fixed SOL size per trade, and start a *mirror*. From then on, the leader's trades fan out to your agent — every mirrored order runs through **your** agent's own spend policy, kill switch, and custody audit trail (see [custody](#sec-170)). Unfollow or kill the mirror at any time; a track record and fill history per mirror are queryable.
+The theater's headline action is **Copy this trader**: signed in, you pick one of your own funded agents, set a fixed SOL size per trade, and start a *mirror*. From then on, the leader's trades fan out to your agent — every mirrored order runs through **your** agent's own spend policy, kill switch, and custody audit trail (see [custody](#sec-172)). Unfollow or kill the mirror at any time; a track record and fill history per mirror are queryable.
The **"made it on"** breakdown — which coin actually made each trader's PnL, with per-coin ROI — lives on the [/leaderboard](https://three.ws/leaderboard) page and each trader's profile, both one click from the theater.
@@ -88830,18 +89580,18 @@ Honest limits: consensus trading runs in the long-lived sniper worker. On a depl
## How they chain together
-Prove yourself solo (the [trading surfaces](#sec-415) → the [leaderboard](https://three.ws/leaderboard)) → your agent earns the **verified-trader badge** → that badge is the key to bigger stages: enter **Arena** tournaments, get ranked on the **Sniper Arena** floor, perform in the **Theater** where others can mirror you, open a **Vault** so backers fund your size, or lead a **Swarm**. Reputation, computed from provable on-chain results, is the currency that moves you up — and [Oracle](#sec-315) conviction is the intelligence all of these agents are acting on.
+Prove yourself solo (the [trading surfaces](#sec-420) → the [leaderboard](https://three.ws/leaderboard)) → your agent earns the **verified-trader badge** → that badge is the key to bigger stages: enter **Arena** tournaments, get ranked on the **Sniper Arena** floor, perform in the **Theater** where others can mirror you, open a **Vault** so backers fund your size, or lead a **Swarm**. Reputation, computed from provable on-chain results, is the currency that moves you up — and [Oracle](#sec-320) conviction is the intelligence all of these agents are acting on.
## Related
-- [Trading surfaces](#sec-415) — the solo stack (Radar, Mission Control, Trade Feed, Watchlist, Coin Intelligence)
-- [Custody](#sec-170) — the spend limits, freeze, and audit rails every mirrored/pooled trade runs through
-- [Oracle](#sec-315) — the conviction engine · [Trading experiment](#sec-413) — one agent's journaled live run
-- [Agent reputation](#sec-056) / [Solana reputation](#sec-393) — how the trust scores are computed
+- [Trading surfaces](#sec-420) — the solo stack (Radar, Mission Control, Trade Feed, Watchlist, Coin Intelligence)
+- [Custody](#sec-172) — the spend limits, freeze, and audit rails every mirrored/pooled trade runs through
+- [Oracle](#sec-320) — the conviction engine · [Trading experiment](#sec-418) — one agent's journaled live run
+- [Agent reputation](#sec-056) / [Solana reputation](#sec-398) — how the trust scores are computed
---
-<a id="sec-412"></a>
+<a id="sec-417"></a>
> **Source:** `docs/trading-copilot.md` · [↑ table of contents](#table-of-contents)
@@ -88977,13 +89727,13 @@ plumbing — and never suggests, shills, or names another token on its own initi
## Related
-- [The trading surfaces: Radar, Mission Control, Feed, Watchlist, Intel](#sec-415)
-- [Financial controls & custody guardrails](#sec-221)
-- [The autonomous trading experiment](#sec-413)
+- [The trading surfaces: Radar, Mission Control, Feed, Watchlist, Intel](#sec-420)
+- [Financial controls & custody guardrails](#sec-223)
+- [The autonomous trading experiment](#sec-418)
---
-<a id="sec-413"></a>
+<a id="sec-418"></a>
> **Source:** `docs/trading-experiment.md` · [↑ table of contents](#table-of-contents)
@@ -89095,7 +89845,7 @@ arm API), **or** an arm earns the right to have it tuned: once the autonomy
engine places an arm at `trusted` or above and its winners demonstrably run past
its average exit, the optimizer adjusts the multiple by itself within its bounds
and records why. See
-[Earned autonomy](#sec-390). A losing arm cannot reach the field at
+[Earned autonomy](#sec-395). A losing arm cannot reach the field at
all, so the ladder is only ever switched on for a strategy whose record shows it
actually catches runners.
@@ -89318,7 +90068,7 @@ much — and tune the next run. That is the whole point of the experiment.
---
-<a id="sec-414"></a>
+<a id="sec-419"></a>
> **Source:** `docs/trading-hub.md` · [↑ table of contents](#table-of-contents)
@@ -89427,16 +90177,16 @@ credentials, and writes nothing.
## Related
- [Agent Sniper](#sec-061), what the autonomous trader is and how it is wired
-- [The 10 SOL experiment](#sec-413), the full risk policy
-- [Risk acknowledgment](#sec-370), read before arming real funds
-- [Custody model](#sec-170), how an agent holds its own keys
-- [Earned autonomy](#sec-390), how an agent earns more freedom
-- [Trading Copilot](#sec-412), the fair-launch market maker
-- Tutorial: [Arm an autonomous sniper](#sec-424)
+- [The 10 SOL experiment](#sec-418), the full risk policy
+- [Risk acknowledgment](#sec-375), read before arming real funds
+- [Custody model](#sec-172), how an agent holds its own keys
+- [Earned autonomy](#sec-395), how an agent earns more freedom
+- [Trading Copilot](#sec-417), the fair-launch market maker
+- Tutorial: [Arm an autonomous sniper](#sec-430)
---
-<a id="sec-415"></a>
+<a id="sec-420"></a>
> **Source:** `docs/trading-surfaces.md` · [↑ table of contents](#table-of-contents)
@@ -89462,7 +90212,7 @@ All five surfaces read the same underlying truth: the Coin Intelligence Engine (
On top of that base layer:
-- **Oracle conviction** ([the conviction engine](#sec-315)) enriches coins across all five surfaces with its 0–100 fused score and tier.
+- **Oracle conviction** ([the conviction engine](#sec-320)) enriches coins across all five surfaces with its 0–100 fused score and tier.
- **Price history** (candlesticks) comes from Birdeye with GeckoTerminal fallback.
- **Live trades** stream over server-sent events from `/api/pump/trades-stream` (PumpPortal websocket, relayed).
- **Smart-money pedigree** comes from the proven-wallet ledger (`/api/intel/smart-money`).
@@ -89524,7 +90274,7 @@ Empty state suggests trending coins so the page is never a dead end.
## Mission Control — /terminal
-The cockpit. Everything above is fused into one keyboard-first, three-pane terminal — and this is the surface where you can actually pull the trigger, because it trades through your agent's custodial Solana wallet on the server-side guarded path (firewall verdict, MEV protection, spend guards, and the custody audit trail are enforced server-side on every order — the same rails documented in [financial-controls](#sec-221)).
+The cockpit. Everything above is fused into one keyboard-first, three-pane terminal — and this is the surface where you can actually pull the trigger, because it trades through your agent's custodial Solana wallet on the server-side guarded path (firewall verdict, MEV protection, spend guards, and the custody audit trail are enforced server-side on every order — the same rails documented in [financial-controls](#sec-223)).
The three panes:
@@ -89548,7 +90298,7 @@ Signed-out, Mission Control is a read-only cockpit; the trade ticket becomes "Si
## How the surfaces chain together
-The intended loop: **Radar** (or **Coin Intelligence**) surfaces a launch worth a look → **Watch** it → the **Watchlist** alerts you when Oracle's conviction tier upgrades → open it in **Mission Control** and execute → if the trade wins big, it shows up on the **Live Trade Feed** with the full receipt for everyone else to study. Every coin, on every surface, links to its [Oracle page](#sec-315) for the fused conviction verdict — and armed agents can run the same loop autonomously (see [the trading experiment](#sec-413) and [Oracle's agent loop](#sec-315)).
+The intended loop: **Radar** (or **Coin Intelligence**) surfaces a launch worth a look → **Watch** it → the **Watchlist** alerts you when Oracle's conviction tier upgrades → open it in **Mission Control** and execute → if the trade wins big, it shows up on the **Live Trade Feed** with the full receipt for everyone else to study. Every coin, on every surface, links to its [Oracle page](#sec-320) for the fused conviction verdict — and armed agents can run the same loop autonomously (see [the trading experiment](#sec-418) and [Oracle's agent loop](#sec-320)).
## API quick reference
@@ -89569,21 +90319,94 @@ 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-277) (`@three-ws/intel-mcp`, `@three-ws/portfolio-mcp`) — and the paid x402 lanes in [x402-endpoints](#sec-539).
+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).
## Related
-- [Meta-Allocator: the ETF of degens](#sec-281): diversify a budget across the top verified leaders
+- [Meta-Allocator: the ETF of degens](#sec-285): diversify a budget across the top verified leaders
- [Clip Director: every trade becomes content](#sec-143): turn any closed trade into shareable cards per surface
-- [The Trading Copilot — talk to your wallet](#sec-412) — conversational trading over these same numbers
-- [Oracle — the conviction engine](#sec-315) · [/oracle/docs](https://three.ws/oracle/docs)
-- [The autonomous trading experiment](#sec-413)
-- [Financial controls & custody guardrails](#sec-221)
-- [UX flows: crypto trading & analytics](#sec-495) — screen-by-screen walkthrough
+- [The Trading Copilot — talk to your wallet](#sec-417) — conversational trading over these same numbers
+- [Oracle — the conviction engine](#sec-320) · [/oracle/docs](https://three.ws/oracle/docs)
+- [The autonomous trading experiment](#sec-418)
+- [Financial controls & custody guardrails](#sec-223)
+- [UX flows: crypto trading & analytics](#sec-501) — screen-by-screen walkthrough
---
-<a id="sec-416"></a>
+<a id="sec-421"></a>
+
+> **Source:** `docs/triage.md` · [↑ table of contents](#table-of-contents)
+
+# Triage
+
+How incoming issues and pull requests get sorted, who does it, and what you can expect back. Written for contributors, so you know where your work stands without having to ask.
+
+## Response targets
+
+These are commitments, not aspirations. If we miss one, ping the thread and we will own it.
+
+| Event | Target | What "handled" means |
+|---|---|---|
+| New issue | 2 business days | Labeled, and either a question back, a reproduction confirmation, or a "not planned" with the reason |
+| New pull request from a first-time contributor | 2 business days | A human has read the diff and left a real comment |
+| Pull request follow-up round | 2 business days | Re-review after you push changes |
+| Security advisory | 24 hours | Acknowledged privately, with a fix window |
+| Discussions question | Best effort | Community-first; maintainers answer what stays unanswered |
+
+Nothing gets closed for staleness by a bot. If an issue is real and open, it stays open.
+
+## The triage pass
+
+A maintainer runs the untriaged queue at least twice a week. Every new issue gets:
+
+1. **A type label.** `bug`, `enhancement`, `documentation`, or `question`.
+2. **A verdict.** Reproduced, needs more information, or not planned. Rig and rendering bugs need the GLB; the first response on those is usually a request for the file.
+3. **A contributor signal, where it applies.** `good first issue` if it is genuinely self-contained with a named file and a verification command. `help wanted` if we want outside help but it is not beginner-shaped.
+4. **A home.** Anything touching a path in [CODEOWNERS](../.github/CODEOWNERS) is routed to that owner automatically on the PR.
+
+## Labels and what they actually mean
+
+| Label | Meaning |
+|---|---|
+| `good first issue` | Self-contained, one or two files, the issue names the file to change and the command that proves it worked. No architecture knowledge needed. |
+| `help wanted` | We want an outside contributor on this. Larger than a first issue, still well-scoped. |
+| `bug` | Reproduced, or has enough detail to reproduce. |
+| `enhancement` | Accepted as a direction. An enhancement issue that is still open has not been rejected. |
+| `documentation` | Docs defect or gap. `npm run audit:docs` findings land here. |
+| `question` | Usually gets converted to a Discussion so the answer is searchable. |
+| `duplicate` / `invalid` / `wontfix` | Closed, always with the reason written in the thread. Never closed silently. |
+
+## Claiming work
+
+Comment on the issue before you start. One line is enough. We assign it to you and nobody else picks it up.
+
+If you claim something and life happens, say so and we will unassign it with zero drama. An unclaimed issue helps the next person; a silently abandoned one blocks them.
+
+## Pull request expectations
+
+- Branch from `main`, one topic per PR.
+- `npm test` passes locally before you push.
+- `npx prettier --write` on the files you touched.
+- Commit subject in the form `type(scope): what changed and why a reader would care`. Subjects that describe the act of committing (`wip`, `sync`, `update`, `changes`) are rejected mechanically.
+- Touched a feature whose docs are now wrong? Fix the docs in the same PR. Stale docs are worse than none.
+- User-visible change? It needs an entry in `data/changelog.json`. A maintainer will help you word it if you are unsure; the changelog is written for users, not for engineers.
+
+## Maintainers
+
+Day-to-day triage, review, and releases are handled by [@nirholas](https://github.com/nirholas), with [CODEOWNERS](../.github/CODEOWNERS) routing high-blast-radius paths (contracts, payment rails, published SDKs, security policy) to a required review.
+
+We are actively looking to grow this. The path is the normal one: land a few good PRs, help answer things in [Discussions](https://github.com/nirholas/three.ws/discussions), and we will hand you triage rights. There is no interview.
+
+## Related
+
+- [Your first contribution](#sec-224)
+- [CONTRIBUTING.md](../CONTRIBUTING.md)
+- [Community](#sec-151)
+- [Security policy](../.github/SECURITY.md)
+
+---
+
+<a id="sec-422"></a>
> **Source:** `docs/troubleshooting.md` · [↑ table of contents](#table-of-contents)
@@ -90242,7 +91065,7 @@ Idle blink and head-drift are active in the current release: `src/idle-animation
---
-<a id="sec-417"></a>
+<a id="sec-423"></a>
> **Source:** `docs/trust-primitives.md` · [↑ table of contents](#table-of-contents)
@@ -90261,7 +91084,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-544)).
+(Base or Solana mainnet, via [x402](#sec-551)).
Pass any counterparty identifier. The type is auto-detected and scored from whatever
real on-chain evidence exists for it:
@@ -90379,7 +91202,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-544).
+dropped >10 points). See the [x402 catalog](#sec-551).
---
@@ -90404,7 +91227,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-544)).
+— $0.005 USDC per call (Base or Solana mainnet, via [x402](#sec-551)).
It verifies a **claim** that `identity` controls `address`, for **any** identity type,
on any chain — regardless of the platform the counterparty came from:
@@ -90478,11 +91301,11 @@ score *whether to trust* them.
---
-See also: [x402 paid endpoints](#sec-544) · [Agent Bouncer](#sec-096) · [ERC-8004 identity](#sec-188)
+See also: [x402 paid endpoints](#sec-551) · [Agent Bouncer](#sec-096) · [ERC-8004 identity](#sec-190)
---
-<a id="sec-418"></a>
+<a id="sec-424"></a>
> **Source:** `docs/tutorials/add-a-3d-assistant.md` · [↑ table of contents](#table-of-contents)
@@ -90600,7 +91423,7 @@ Then ask, in plain language: "build a 3D assistant widget named Aria with an oce
---
-<a id="sec-419"></a>
+<a id="sec-425"></a>
> **Source:** `docs/tutorials/agent-personality.md` · [↑ table of contents](#table-of-contents)
@@ -91053,7 +91876,7 @@ The system prompt is the cheapest, highest-leverage thing you can change about a
---
-<a id="sec-420"></a>
+<a id="sec-426"></a>
> **Source:** `docs/tutorials/agent-reputation.md` · [↑ table of contents](#table-of-contents)
@@ -91330,7 +92153,7 @@ A read costs nothing and asks no one's permission. That's the property that lets
---
-<a id="sec-421"></a>
+<a id="sec-427"></a>
> **Source:** `docs/tutorials/agent-spending-envelope.md` · [↑ table of contents](#table-of-contents)
@@ -91893,7 +92716,7 @@ The two "budget stays reserved" cases are the only place the system deliberately
---
-<a id="sec-422"></a>
+<a id="sec-428"></a>
> **Source:** `docs/tutorials/animate-your-agent.md` · [↑ table of contents](#table-of-contents)
@@ -92069,7 +92892,7 @@ The difference that matters is the layer. `wave`, `point`, `nod` and `shrug` are
---
-<a id="sec-423"></a>
+<a id="sec-429"></a>
> **Source:** `docs/tutorials/animate-your-avatar.md` · [↑ table of contents](#table-of-contents)
@@ -92251,7 +93074,7 @@ Applying clips in the Studio is the **authoring** side. On a *running* agent, th
The two channels are wired to the *same* emotional state, at two different timescales, so the body and the face never disagree:
- **Momentary events** (an error just happened, a skill just finished) inject a transient emotion spike, `concern`, `celebration`, `curiosity`, and friends, that decays over seconds. A spike crossing threshold both reshapes the face immediately *and* biases the gesture slot the avatar plays next (e.g. sustained `celebration` picks the `celebrate` slot).
-- **Sustained mood**: the agent's resting valence/arousal, set via `setMood()` (see [docs/tutorials/emotion-from-data.md](#sec-438)), is the continuous baseline between events. It biases the resting face (a soft smile at high valence, a worried brow at low) and posture (lean, gaze) every frame, and, once nothing more urgent claims the gesture slot, biases *which* ambient gesture plays too: a sustained up-and-energetic mood leans toward the `celebrate` slot, a sustained down-and-subdued mood toward `concern`, the opposite bias, never the energetic one. A momentary event always takes priority over the ambient mood bias, and slot overrides via `meta.edits.animations` apply identically whether the trigger was a spike or the resting mood.
+- **Sustained mood**: the agent's resting valence/arousal, set via `setMood()` (see [docs/tutorials/emotion-from-data.md](#sec-444)), is the continuous baseline between events. It biases the resting face (a soft smile at high valence, a worried brow at low) and posture (lean, gaze) every frame, and, once nothing more urgent claims the gesture slot, biases *which* ambient gesture plays too: a sustained up-and-energetic mood leans toward the `celebrate` slot, a sustained down-and-subdued mood toward `concern`, the opposite bias, never the energetic one. A momentary event always takes priority over the ambient mood bias, and slot overrides via `meta.edits.animations` apply identically whether the trigger was a spike or the resting mood.
The division of labor: **clips move the body, blendshapes move the face, slots choose *which* body motion fits the emotion, and one emotional state, not two independent tracks, drives all of it.** All three ride the same universal-rig foundation, name your bones (and your blendshapes) in a convention the resolvers know, and everything just works.
@@ -92291,14 +93114,14 @@ You learned the apply-and-remix workflow for motion on three.ws:
- [docs/animations.md](#sec-093): the runtime animation registry, manifest, and agent slot reference.
- [docs/3d-asset-pipeline.md](#sec-002), how FBX, GLB, and clip JSON relate, and how clips are built and retargeted.
-- [docs/tutorials/swap-avatar-in-studio.md](#sec-476), loading and switching avatars in the Studio.
-- [docs/tutorials/upload-custom-glb.md](#sec-479), getting a Mixamo or custom rig into three.ws as a clean, animatable GLB.
+- [docs/tutorials/swap-avatar-in-studio.md](#sec-482), loading and switching avatars in the Studio.
+- [docs/tutorials/upload-custom-glb.md](#sec-485), getting a Mixamo or custom rig into three.ws as a clean, animatable GLB.
Primary call to action: open **[/pose](/pose)**, load an avatar, and apply your first clip.
---
-<a id="sec-424"></a>
+<a id="sec-430"></a>
> **Source:** `docs/tutorials/arm-an-agent-sniper.md` · [↑ table of contents](#table-of-contents)
@@ -92412,7 +93235,7 @@ The hard-config sniper you just armed is the control group. The next phase runs
---
-<a id="sec-425"></a>
+<a id="sec-431"></a>
> **Source:** `docs/tutorials/build-a-3d-asset-pipeline.md` · [↑ table of contents](#table-of-contents)
@@ -92631,7 +93454,7 @@ step once the mechanical stages are running.
---
-<a id="sec-426"></a>
+<a id="sec-432"></a>
> **Source:** `docs/tutorials/build-a-scene.md` · [↑ table of contents](#table-of-contents)
@@ -92850,7 +93673,7 @@ The leverage of [Scene Studio](/scene) is that it's a *real* editor producing a
---
-<a id="sec-427"></a>
+<a id="sec-433"></a>
> **Source:** `docs/tutorials/build-a-site-concierge.md` · [↑ table of contents](#table-of-contents)
@@ -92968,7 +93791,7 @@ Then: `<three-concierge endpoint="/my/concierge">`. The production reference, wi
---
-<a id="sec-428"></a>
+<a id="sec-434"></a>
> **Source:** `docs/tutorials/character-library-to-embed.md` · [↑ table of contents](#table-of-contents)
@@ -93473,7 +94296,7 @@ Doing the copy server-side also sidesteps cross-origin reads and browser upload
---
-<a id="sec-429"></a>
+<a id="sec-435"></a>
> **Source:** `docs/tutorials/claim-threews-name.md` · [↑ table of contents](#table-of-contents)
@@ -93781,7 +94604,7 @@ See also:
---
-<a id="sec-430"></a>
+<a id="sec-436"></a>
> **Source:** `docs/tutorials/connect-ai-brain.md` · [↑ table of contents](#table-of-contents)
@@ -94203,7 +95026,7 @@ The brain is the part of the agent you'll iterate on most after the system promp
---
-<a id="sec-431"></a>
+<a id="sec-437"></a>
> **Source:** `docs/tutorials/create-and-edit-memory.md` · [↑ table of contents](#table-of-contents)
@@ -94524,7 +95347,7 @@ The leverage is in *enhancement*: the right type, one fact per memory, tags, del
---
-<a id="sec-432"></a>
+<a id="sec-438"></a>
> **Source:** `docs/tutorials/custom-skill.md` · [↑ table of contents](#table-of-contents)
@@ -95049,7 +95872,7 @@ The skill installs via a URI in the agent manifest, runs entirely client-side, a
---
-<a id="sec-433"></a>
+<a id="sec-439"></a>
> **Source:** `docs/tutorials/customize-appearance.md` · [↑ table of contents](#table-of-contents)
@@ -95487,7 +96310,7 @@ Most production embeds use four or five of these together. The combination is wh
---
-<a id="sec-434"></a>
+<a id="sec-440"></a>
> **Source:** `docs/tutorials/deploy-to-vercel-custom-domain.md` · [↑ table of contents](#table-of-contents)
@@ -96007,7 +96830,7 @@ In rough order of likelihood:
---
-<a id="sec-435"></a>
+<a id="sec-441"></a>
> **Source:** `docs/tutorials/earn-and-spend-in-play.md` · [↑ table of contents](#table-of-contents)
@@ -96202,7 +97025,7 @@ Every paid sale splits 50% to the holder-rewards sink and 50% to the treasury.
## Next
-- **[The in-game economy](#sec-252)** is the full reference: every
+- **[The in-game economy](#sec-255)** is the full reference: every
catalog, gate, settlement path, and the JSON wire format.
- **[three.ws/play/economy](https://three.ws/play/economy)** shows the live
catalogs and odds, read from the running server.
@@ -96211,7 +97034,7 @@ Every paid sale splits 50% to the holder-rewards sink and 50% to the treasury.
---
-<a id="sec-436"></a>
+<a id="sec-442"></a>
> **Source:** `docs/tutorials/embed-in-30-seconds.md` · [↑ table of contents](#table-of-contents)
@@ -96487,7 +97310,7 @@ A working embedded agent is the foundation everything else builds on. From here,
---
-<a id="sec-437"></a>
+<a id="sec-443"></a>
> **Source:** `docs/tutorials/embed-on-website.md` · [↑ table of contents](#table-of-contents)
@@ -96998,7 +97821,7 @@ Squarespace's developer preview and published output can differ. Try adding the
---
-<a id="sec-438"></a>
+<a id="sec-444"></a>
> **Source:** `docs/tutorials/emotion-from-data.md` · [↑ table of contents](#table-of-contents)
@@ -97109,7 +97932,7 @@ Save that as `index.html` and open it: no build step, no server, no wallet. Swap
## Step 3: The AI lane: real classification over arbitrary data, richer gestures
-A lexicon scorer only works on short, informal text, and it only fires on words it already knows. For real documents (support tickets, product reviews, meeting transcripts, incident reports) you want a model that actually reads the thing and returns *structured* output: a graded sentiment score plus the findings and risk flags behind it, so the reaction tracks the document's real tone instead of its vocabulary. `ibm_granite_analyze` (part of the [IBM Granite x402 MCP suite](#sec-249)) does exactly this for $0.04/call, no IBM account needed: you pay in USDC, it pays IBM.
+A lexicon scorer only works on short, informal text, and it only fires on words it already knows. For real documents (support tickets, product reviews, meeting transcripts, incident reports) you want a model that actually reads the thing and returns *structured* output: a graded sentiment score plus the findings and risk flags behind it, so the reaction tracks the document's real tone instead of its vocabulary. `ibm_granite_analyze` (part of the [IBM Granite x402 MCP suite](#sec-252)) does exactly this for $0.04/call, no IBM account needed: you pay in USDC, it pays IBM.
The tool returns a fixed set of keys: `summary`, `entities`, `sentiment` (`{ overall, score }`, score in -1..1), `key_findings`, `risk_flags` (each with a `severity`), and `next_steps`. The two the animation layer cares about are `sentiment.score` and `risk_flags`.
@@ -97225,7 +98048,7 @@ function reactIfConfident(clipOrEmoteName, { confident, useExactClip = false } =
- **The agent keeps re-celebrating every poll.** You skipped the cooldown gate in Step 4, or your confidence threshold is too low for a noisy feed. Widen `COOLDOWN_MS` or raise the sample-size/strength floor.
- **AI lane 402 loop / never resolves.** Your `SOLANA_PRIVATE_KEY` wallet has no USDC. Fund it with a few cents, see the [x402 payment flow](/tutorials/pay-for-x402-service).
- **`analysis.sentiment` is undefined.** Granite returned something that wasn't a clean JSON analysis object; the tool falls back to `{ ok: true, raw_response, parse_error }` in that case. Log `analysis.parse_error` and `analysis.raw_response` to see what came back. The `gestureFor()` above already treats a missing score as "no gesture" rather than crashing.
-- **Every document scores middling and nothing ever plays.** `analysis_type: 'sentiment'` tunes the model toward tone; the other five types (`general`, `contract`, `financial`, `technical`, `medical`) return the same keys but reason about different things, so a contract analyzed as `general` often lands near 0. Match the type to your data (see [ibm-x402-mcp](#sec-249)).
+- **Every document scores middling and nothing ever plays.** `analysis_type: 'sentiment'` tunes the model toward tone; the other five types (`general`, `contract`, `financial`, `technical`, `medical`) return the same keys but reason about different things, so a contract analyzed as `general` often lands near 0. Match the type to your data (see [ibm-x402-mcp](#sec-252)).
---
@@ -97240,7 +98063,7 @@ function reactIfConfident(clipOrEmoteName, { confident, useExactClip = false } =
---
-<a id="sec-439"></a>
+<a id="sec-445"></a>
> **Source:** `docs/tutorials/explore-docs-world.md` · [↑ table of contents](#table-of-contents)
@@ -97317,13 +98140,13 @@ Make one with the [Forge](/create) or the [Avatar Studio](/avatar-studio), copy
## Where to next
-- [Docs World reference](#sec-179): controls table, device behaviour, contributor notes.
-- [What is three.ws?](#sec-399): the guided tour of the whole platform, readable in either surface.
+- [Docs World reference](#sec-181): controls table, device behaviour, contributor notes.
+- [What is three.ws?](#sec-404): the guided tour of the whole platform, readable in either surface.
- Add a page to the docs yourself: edit `docs/nav.json` and drop a markdown file in `docs/`; it appears in the sidebar and as a page in its pavilion with no extra wiring.
---
-<a id="sec-440"></a>
+<a id="sec-446"></a>
> **Source:** `docs/tutorials/find-a-better-exit-policy.md` · [↑ table of contents](#table-of-contents)
@@ -97566,7 +98389,7 @@ disclaimers bolted onto the result. They are the result.
---
-<a id="sec-441"></a>
+<a id="sec-447"></a>
> **Source:** `docs/tutorials/first-agent.md` · [↑ table of contents](#table-of-contents)
@@ -98075,7 +98898,7 @@ Now that you have a working agent, here's what to explore next:
---
-<a id="sec-442"></a>
+<a id="sec-448"></a>
> **Source:** `docs/tutorials/first-prompt-to-3d.md` · [↑ table of contents](#table-of-contents)
@@ -98195,7 +99018,7 @@ A rigged avatar's AR link gains a **Bring it to life** option: instead of a froz
---
-<a id="sec-443"></a>
+<a id="sec-449"></a>
> **Source:** `docs/tutorials/generate-3d-api.md` · [↑ table of contents](#table-of-contents)
@@ -98420,7 +99243,7 @@ If you've never made an x402 call, start with [Build a paid x402 endpoint](/tuto
---
-<a id="sec-444"></a>
+<a id="sec-450"></a>
> **Source:** `docs/tutorials/getting-started.md` · [↑ table of contents](#table-of-contents)
@@ -98605,7 +99428,7 @@ Everything is editable forever — swap the body, rewrite the prompt, add capabi
---
-<a id="sec-445"></a>
+<a id="sec-451"></a>
> **Source:** `docs/tutorials/greeting-and-first-speech.md` · [↑ table of contents](#table-of-contents)
@@ -98953,7 +99776,7 @@ A working greeting moves the embed from "decoration" to "interaction", which is
---
-<a id="sec-446"></a>
+<a id="sec-452"></a>
> **Source:** `docs/tutorials/image-to-3d.md` · [↑ table of contents](#table-of-contents)
@@ -99056,7 +99879,7 @@ Everything you generate is kept in **Your creations** at the bottom of the page,
---
-<a id="sec-447"></a>
+<a id="sec-453"></a>
> **Source:** `docs/tutorials/import-avatar-url.md` · [↑ table of contents](#table-of-contents)
@@ -99226,7 +100049,7 @@ The URL path and the file-upload path converge on the same avatar record and the
---
-<a id="sec-448"></a>
+<a id="sec-454"></a>
> **Source:** `docs/tutorials/js-api-events.md` · [↑ table of contents](#table-of-contents)
@@ -99692,7 +100515,7 @@ The `whenReady`, awaited-`ask()`, and try/catch patterns are small but they remo
---
-<a id="sec-449"></a>
+<a id="sec-455"></a>
> **Source:** `docs/tutorials/mcp-server-for-your-agent.md` · [↑ table of contents](#table-of-contents)
@@ -100347,7 +101170,7 @@ Things that look right but bite you:
---
-<a id="sec-450"></a>
+<a id="sec-456"></a>
> **Source:** `docs/tutorials/mine-vanity-address.md` · [↑ table of contents](#table-of-contents)
@@ -100629,7 +101452,7 @@ The protocol itself is fully specified in [docs/PROTOCOL-vanity.md](#sec-005), a
---
-<a id="sec-451"></a>
+<a id="sec-457"></a>
> **Source:** `docs/tutorials/mint-pumpfun-token.md` · [↑ table of contents](#table-of-contents)
@@ -100990,7 +101813,7 @@ If you have a lawyer, talk to them before launching. If you don't, default to th
---
-<a id="sec-452"></a>
+<a id="sec-458"></a>
> **Source:** `docs/tutorials/monetize-mcp-server.md` · [↑ table of contents](#table-of-contents)
@@ -101306,7 +102129,7 @@ That connector can search the bazaar, read your challenge without paying (`inspe
---
-<a id="sec-453"></a>
+<a id="sec-459"></a>
> **Source:** `docs/tutorials/multi-agent-coordination.md` · [↑ table of contents](#table-of-contents)
@@ -101711,7 +102534,7 @@ researcher.addEventListener('skill:tool-called', (e) => {
Build the tools themselves as skills (see [custom-skill](/tutorials/custom-skill)); the orchestration logic stays in the coordinator on the page.
-There's also a platform-native alternative to page-level orchestration: the `<agent-stage>` element. A stage hosts every child `<agent-3d>` in one shared WebGL scene (with a `formation` attribute — `row`, `circle`, or `freeform`), exposes `getAgents()`, `broadcast(fromId, event)`, and `routeMessage(fromId, toId, text)` to your code, and grants each staged agent two extra built-in tools — `observe_agents` (who else is on stage) and `say_to_agent` (address a colleague directly) — so the LLMs can delegate to each other without any coordinator glue. When the agents, not the page, should decide who does what, reach for the stage. The full patterns are in [Multi-Agent Scenes](#sec-290).
+There's also a platform-native alternative to page-level orchestration: the `<agent-stage>` element. A stage hosts every child `<agent-3d>` in one shared WebGL scene (with a `formation` attribute — `row`, `circle`, or `freeform`), exposes `getAgents()`, `broadcast(fromId, event)`, and `routeMessage(fromId, toId, text)` to your code, and grants each staged agent two extra built-in tools — `observe_agents` (who else is on stage) and `say_to_agent` (address a colleague directly) — so the LLMs can delegate to each other without any coordinator glue. When the agents, not the page, should decide who does what, reach for the stage. The full patterns are in [Multi-Agent Scenes](#sec-294).
Parallel fan-out is **harder to debug** than sequential delegation because errors are non-deterministic in order and any latency outlier blocks the join. Use it when the wall-clock saving is worth the complexity. For a chat UX with a human in the loop, sequential is almost always the right default.
@@ -101866,7 +102689,7 @@ async function safeHandoff(targetEl, brief, fallbackEl, originalQuestion) {
---
-<a id="sec-454"></a>
+<a id="sec-460"></a>
> **Source:** `docs/tutorials/nvidia-3d-free.md` · [↑ table of contents](#table-of-contents)
@@ -101988,7 +102811,7 @@ It talks **directly** to a TRELLIS NIM and returns the GLB **synchronously** in
---
-<a id="sec-455"></a>
+<a id="sec-461"></a>
> **Source:** `docs/tutorials/nvidia-nim-self-host.md` · [↑ table of contents](#table-of-contents)
@@ -102171,7 +102994,7 @@ The proxy normalizes every documented artifact shape (inline `base64`, a bare st
---
-<a id="sec-456"></a>
+<a id="sec-462"></a>
> **Source:** `docs/tutorials/paid-x402-endpoint.md` · [↑ table of contents](#table-of-contents)
@@ -102863,7 +103686,7 @@ Both work. Choose based on whether your endpoint is part of an agent platform yo
---
-<a id="sec-457"></a>
+<a id="sec-463"></a>
> **Source:** `docs/tutorials/pay-for-x402-service.md` · [↑ table of contents](#table-of-contents)
@@ -103138,7 +103961,7 @@ package family is listed under [x402 → Open-source packages](/x402#open-source
---
-<a id="sec-458"></a>
+<a id="sec-464"></a>
> **Source:** `docs/tutorials/personal-ai-site.md` · [↑ table of contents](#table-of-contents)
@@ -103693,7 +104516,7 @@ The technical investment is one HTML file, a GLB avatar, and a system prompt. Th
---
-<a id="sec-459"></a>
+<a id="sec-465"></a>
> **Source:** `docs/tutorials/place-agent-irl.md` · [↑ table of contents](#table-of-contents)
@@ -103943,7 +104766,7 @@ This is fundamentally different from viewing a single model in AR. If you only n
---
-<a id="sec-460"></a>
+<a id="sec-466"></a>
> **Source:** `docs/tutorials/prompts-for-3d.md` · [↑ table of contents](#table-of-contents)
@@ -104079,7 +104902,7 @@ The tiers are explained in detail in [the text-to-3D tutorial](/tutorials/text-t
---
-<a id="sec-461"></a>
+<a id="sec-467"></a>
> **Source:** `docs/tutorials/read-the-trading-fleet.md` · [↑ table of contents](#table-of-contents)
@@ -104306,7 +105129,7 @@ funds.
---
-<a id="sec-462"></a>
+<a id="sec-468"></a>
> **Source:** `docs/tutorials/register-onchain.md` · [↑ table of contents](#table-of-contents)
@@ -104655,7 +105478,7 @@ Your agent's URL will keep working as long as Base exists and IPFS gateways serv
---
-<a id="sec-463"></a>
+<a id="sec-469"></a>
> **Source:** `docs/tutorials/render-avatar-images.md` · [↑ table of contents](#table-of-contents)
@@ -105200,7 +106023,7 @@ If you want a talking, animated agent rather than a viewer, that is the `<agent-
---
-<a id="sec-464"></a>
+<a id="sec-470"></a>
> **Source:** `docs/tutorials/self-host-agent-backend.md` · [↑ table of contents](#table-of-contents)
@@ -105727,7 +106550,7 @@ A few things you should know going in:
**Some upstream features require platform-only secrets.** The hosted three.ws has access to API keys and wallets that aren't published. If you fork, those features (e.g., the platform-managed agent treasury) won't work as-is — you'll either disable them or wire your own equivalents. The code paths that depend on platform secrets are clearly conditional on env-var presence; if your env var is empty, the feature is hidden in the UI.
-**Check the license before you deploy anything.** The repo's `LICENSE` is proprietary, not open source: "All rights reserved", with use, copying, modification, and distribution requiring the copyright owner's express written permission. Reading the source is not the same as being licensed to run a fork of it, so get that permission in writing before you stand up a deployment. Everything below assumes you have it.
+**You are licensed to do this.** The repo ships under the Apache License 2.0, so self-hosting, forking, and running a modified deployment are all permitted. Keep the `LICENSE` and `NOTICE` files with any copy you distribute, and state what you changed. No permission request needed.
**You become responsible for security patches.** Vercel handles its own infrastructure. You handle the application code. Subscribe to GitHub Dependabot alerts on your fork, and feed fixes back upstream when they aren't specific to your deployment.
@@ -105763,7 +106586,7 @@ A self-hosted instance with light traffic runs at $20–50/month all-in. The dom
---
-<a id="sec-465"></a>
+<a id="sec-471"></a>
> **Source:** `docs/tutorials/selfie-to-avatar.md` · [↑ table of contents](#table-of-contents)
@@ -106019,7 +106842,7 @@ The result is a standard `.glb` that animates in the [Animation Studio](/pose),
---
-<a id="sec-466"></a>
+<a id="sec-472"></a>
> **Source:** `docs/tutorials/sell-a-skill-with-a-trial.md` · [↑ table of contents](#table-of-contents)
@@ -106232,7 +107055,7 @@ A healthy funnel shows a mix of `trial` rows with counts ticking down and `confi
---
-<a id="sec-467"></a>
+<a id="sec-473"></a>
> **Source:** `docs/tutorials/share-your-agent.md` · [↑ table of contents](#table-of-contents)
@@ -106596,7 +107419,7 @@ The agent's URL is the durable handle. Embed it, link it, print it. The agent sh
---
-<a id="sec-468"></a>
+<a id="sec-474"></a>
> **Source:** `docs/tutorials/ship-an-avatar-manifest.md` · [↑ table of contents](#table-of-contents)
@@ -106906,12 +107729,12 @@ A JSON file that names an avatar, pins its mesh by content rather than by locati
**Next:**
- The [Avatar CLI reference](#sec-108) documents every flag, exit code, and `--json` shape.
-- The [web component reference](#sec-508) covers everything `<agent-3d>` can do beyond rendering a body: voice, an LLM brain, memory, and skills.
+- The [web component reference](#sec-514) covers everything `<agent-3d>` can do beyond rendering a body: voice, an LLM brain, memory, and skills.
- [`@three-ws/avatar-schema`](../packages/avatar-schema/README.md) is the schema itself, for writing your own tooling against the format.
---
-<a id="sec-469"></a>
+<a id="sec-475"></a>
> **Source:** `docs/tutorials/shopify-shopping-assistant.md` · [↑ table of contents](#table-of-contents)
@@ -107029,7 +107852,7 @@ The [wire format](/docs/concierge) for the answer endpoint is documented, so you
---
-<a id="sec-470"></a>
+<a id="sec-476"></a>
> **Source:** `docs/tutorials/shopify-store-guide-advanced.md` · [↑ table of contents](#table-of-contents)
@@ -107339,7 +108162,7 @@ The clip URLs inside the manifest resolve **relative to the manifest**, so a sel
---
-<a id="sec-471"></a>
+<a id="sec-477"></a>
> **Source:** `docs/tutorials/shopify-store-guide.md` · [↑ table of contents](#table-of-contents)
@@ -107428,7 +108251,7 @@ It's powered by the open-source [`@three-ws/tour`](https://www.npmjs.com/package
---
-<a id="sec-472"></a>
+<a id="sec-478"></a>
> **Source:** `docs/tutorials/sign-with-your-avatar.md` · [↑ table of contents](#table-of-contents)
@@ -107642,9 +108465,9 @@ None of it replaces a human interpreter. It makes an avatar legible to signers i
**See also:**
-- [docs/sign-language.md](#sec-381): the full reference: vocabulary, developer APIs, and how the signing engine works
-- [docs/tutorials/animate-your-avatar.md](#sec-423): the clip library, retargeting, and animated GLB export in depth
-- [docs/web-component.md](#sec-508): every `<agent-3d>` attribute, including `sign-language`
+- [docs/sign-language.md](#sec-386): the full reference: vocabulary, developer APIs, and how the signing engine works
+- [docs/tutorials/animate-your-avatar.md](#sec-429): the clip library, retargeting, and animated GLB export in depth
+- [docs/web-component.md](#sec-514): every `<agent-3d>` attribute, including `sign-language`
- [/asl-alphabet](/asl-alphabet): the manual alphabet, letter by letter, with a practice drill
- [examples/sign-language.html](../examples/sign-language.html): a runnable page with both integration paths
@@ -107652,7 +108475,7 @@ Primary call to action: open **[/sign-language](/sign-language)** and sign your
---
-<a id="sec-473"></a>
+<a id="sec-479"></a>
> **Source:** `docs/tutorials/skill-with-database-auth.md` · [↑ table of contents](#table-of-contents)
@@ -108390,7 +109213,7 @@ Before this skill faces a real visitor:
---
-<a id="sec-474"></a>
+<a id="sec-480"></a>
> **Source:** `docs/tutorials/solana-agent-reputation.md` · [↑ table of contents](#table-of-contents)
@@ -108582,7 +109405,7 @@ A read costs nothing and asks no one's permission — which is exactly what lets
---
-<a id="sec-475"></a>
+<a id="sec-481"></a>
> **Source:** `docs/tutorials/sperax-tour.md` · [↑ table of contents](#table-of-contents)
@@ -108753,7 +109576,7 @@ This is covered by an automated test — [`tour-sdk/test/director.test.mjs`](htt
---
-<a id="sec-476"></a>
+<a id="sec-482"></a>
> **Source:** `docs/tutorials/swap-avatar-in-studio.md` · [↑ table of contents](#table-of-contents)
@@ -108947,7 +109770,7 @@ The key insight is the snippet's stability. Once embedded, your customers' pages
---
-<a id="sec-477"></a>
+<a id="sec-483"></a>
> **Source:** `docs/tutorials/text-to-3d.md` · [↑ table of contents](#table-of-contents)
@@ -109075,7 +109898,7 @@ This is normal — prompt, generate, adjust, repeat is the workflow, not a failu
---
-<a id="sec-478"></a>
+<a id="sec-484"></a>
> **Source:** `docs/tutorials/trigger-from-page-events.md` · [↑ table of contents](#table-of-contents)
@@ -109579,7 +110402,7 @@ The pattern under all of these is the same: every recipe starts with `whenReady(
---
-<a id="sec-479"></a>
+<a id="sec-485"></a>
> **Source:** `docs/tutorials/upload-custom-glb.md` · [↑ table of contents](#table-of-contents)
@@ -110007,7 +110830,7 @@ Once the body is on the platform, the embed snippet doesn't change. The same `<a
---
-<a id="sec-480"></a>
+<a id="sec-486"></a>
> **Source:** `docs/tutorials/view-in-ar.md` · [↑ table of contents](#table-of-contents)
@@ -110196,7 +111019,7 @@ AR surface detection needs a moment to work. Move the phone slowly over the targ
---
-<a id="sec-481"></a>
+<a id="sec-487"></a>
> **Source:** `docs/tutorials/voice-and-lipsync.md` · [↑ table of contents](#table-of-contents)
@@ -110337,7 +111160,7 @@ If you want your agent to speak in *your* voice instead of a built-in one, use t
4. Give the voice a **name** (1–64 characters) and click **Clone**. The page uploads the sample to `POST /api/tts/eleven-clone` ([`api/tts/eleven-clone.js`](../api/tts/eleven-clone.js)) as `multipart/form-data`.
5. On success you get a `voice_id`, and the voice is saved to your library (stored in `localStorage`, up to 20 voices).
-**Test it in the playground.** Pick the cloned voice, type a sample line, and click Speak. The playground calls `POST /api/tts/eleven` ([`api/tts/eleven.js`](../api/tts/eleven.js)) with `{ voiceId, text }`, which proxies ElevenLabs and caches the clip for 30 days (the hint shows `cached` vs `generated`). Default model is `eleven_flash_v2_5`; requests are capped at 500 characters and metered to your credit balance ($0.30 per 1,000 characters on the platform key, or free of platform charges with your own ElevenLabs key in the `x-eleven-key` header; see the [Voice Lab billing section](#sec-506)).
+**Test it in the playground.** Pick the cloned voice, type a sample line, and click Speak. The playground calls `POST /api/tts/eleven` ([`api/tts/eleven.js`](../api/tts/eleven.js)) with `{ voiceId, text }`, which proxies ElevenLabs and caches the clip for 30 days (the hint shows `cached` vs `generated`). Default model is `eleven_flash_v2_5`; requests are capped at 500 characters and metered to your credit balance ($0.30 per 1,000 characters on the platform key, or free of platform charges with your own ElevenLabs key in the `x-eleven-key` header; see the [Voice Lab billing section](#sec-512)).
> Instant Voice Cloning is a **paid-tier ElevenLabs feature** (Starter and up). If the server's account is on the free tier, the clone call returns the upstream error verbatim in the status line (e.g. a `can_not_use_instant_voice_cloning` message). Built-in voices in Step 1 have no such requirement.
@@ -110447,7 +111270,7 @@ The leverage is that the avatar drives its mouth from the *audio it actually pla
---
-<a id="sec-482"></a>
+<a id="sec-488"></a>
> **Source:** `docs/tutorials/walk-companion.md` · [↑ table of contents](#table-of-contents)
@@ -110800,7 +111623,7 @@ The leverage is composability: the same engine renders the corner mascot, the fu
---
-<a id="sec-483"></a>
+<a id="sec-489"></a>
> **Source:** `docs/tutorials/wallet-sign-in.md` · [↑ table of contents](#table-of-contents)
@@ -111084,7 +111907,7 @@ A wallet sign-in that works from any origin that can reach the API, survives the
---
-<a id="sec-484"></a>
+<a id="sec-490"></a>
> **Source:** `docs/tutorials/web-component-end-to-end.md` · [↑ table of contents](#table-of-contents)
@@ -111177,7 +112000,7 @@ This is the right embed when:
- You want multiple agents on the same page
- You need to call the agent's methods or subscribe to its events
-The rest of this tutorial uses the custom-element form, because that's the one that benefits from a wrapper. (The [embedding guide](#sec-437) covers the iframe path and the no-code platforms in depth.)
+The rest of this tutorial uses the custom-element form, because that's the one that benefits from a wrapper. (The [embedding guide](#sec-443) covers the iframe path and the no-code platforms in depth.)
---
@@ -111683,12 +112506,12 @@ The web component is the most robust integration point the platform offers. Buil
## Next steps
- [Drive the agent with the JavaScript API](/tutorials/js-api-events), methods and events covered in depth
-- [Embed a three.ws agent on your website](#sec-437), the no-framework paths (Webflow, WordPress, Squarespace) for completeness
+- [Embed a three.ws agent on your website](#sec-443), the no-framework paths (Webflow, WordPress, Squarespace) for completeness
- [Trigger the agent from page events](/tutorials/trigger-from-page-events), once it's mounted, make it react to the user journey
---
-<a id="sec-485"></a>
+<a id="sec-491"></a>
> **Source:** `docs/tutorials/write-a-guard.md` · [↑ table of contents](#table-of-contents)
@@ -111992,7 +112815,7 @@ Your guard is done when all of these are true:
---
-<a id="sec-486"></a>
+<a id="sec-492"></a>
> **Source:** `docs/tutorials/x402-server-sdk.md` · [↑ table of contents](#table-of-contents)
@@ -112205,7 +113028,7 @@ const res = await pay('https://your.api/v1/embed', { method: 'POST', body });
---
-<a id="sec-487"></a>
+<a id="sec-493"></a>
> **Source:** `docs/ui-juice.md` · [↑ table of contents](#table-of-contents)
@@ -112367,7 +113190,7 @@ should reach for these primitives rather than re-rolling RAF loops.
---
-<a id="sec-488"></a>
+<a id="sec-494"></a>
> **Source:** `docs/user-wallet.md` · [↑ table of contents](#table-of-contents)
@@ -112406,7 +113229,7 @@ They are different wallets with different jobs, and mixing them up is the single
| Auth accepted | **session cookie only** (no API key, no bearer token) | session or scoped credential, depending on the path |
| Typical use | hold funds, top up agents, sweep out | pay x402 endpoints, trade, buy skills, receive earnings |
-The practical consequence: **an API key cannot spend your master wallet, and neither can an agent.** Only a browser session belonging to you can. That is deliberate. The agent-side limits, freeze switch, and audit rails described in [custody.md](#sec-170) govern agent wallets; the master wallet's protection is that nothing autonomous can reach it at all, plus a hard ceiling of **5 outbound transactions per user per day** shared across `send` and `fund-agent`.
+The practical consequence: **an API key cannot spend your master wallet, and neither can an agent.** Only a browser session belonging to you can. That is deliberate. The agent-side limits, freeze switch, and audit rails described in [custody.md](#sec-172) govern agent wallets; the master wallet's protection is that nothing autonomous can reach it at all, plus a hard ceiling of **5 outbound transactions per user per day** shared across `send` and `fund-agent`.
Funds flow one way through the platform's plumbing: master wallet to agent wallet, via `fund-agent`. To go the other direction, use the agent's own owner withdrawal (see [agent-wallets.md](#sec-072)), which a freeze never blocks.
@@ -112586,7 +113409,7 @@ curl -sX POST https://three.ws/api/user/wallet/fund-agent \
Same reserve logic as `send`, and mainnet only: a `"max"` SOL top-up leaves rent and fee headroom, and if the agent has no USDC account yet the transaction opens one and your master wallet pays the rent (refused with `insufficient_sol_for_fees` if your SOL cannot cover it). Without `simulate: true`, a well-formed call executes immediately; preview first when the amount is `"max"` or the agent might lack a token account.
-Once the funds land, they are the agent's, and every further movement out of them runs through the agent's own spend policy, kill switch, and custody trail. Funding an agent is therefore the moment to decide how much autonomy you are comfortable financing: top up in the size you would be willing to lose to a bad strategy, not the whole balance. This is also the normal way to get USDC into an agent before it backs a vault ([vaults.md](#sec-503)) and the easiest way to send a vault the small SOL balance it needs for swap fees, by sending to the vault address with `send`.
+Once the funds land, they are the agent's, and every further movement out of them runs through the agent's own spend policy, kill switch, and custody trail. Funding an agent is therefore the moment to decide how much autonomy you are comfortable financing: top up in the size you would be willing to lose to a bad strategy, not the whole balance. This is also the normal way to get USDC into an agent before it backs a vault ([vaults.md](#sec-509)) and the easiest way to send a vault the small SOL balance it needs for swap fees, by sending to the vault address with `send`.
## On-chain history
@@ -112647,14 +113470,14 @@ Honest limits, stated plainly: this is a **custodial** wallet, so the platform c
## Related
- [agent-wallets.md](#sec-072) for the per-agent wallet this one funds, and its spend policy
-- [custody.md](#sec-170) for limits, freeze, proof of custody, and recovery on the agent side
-- [vaults.md](#sec-503) for what a funded agent wallet can then back
+- [custody.md](#sec-172) for limits, freeze, proof of custody, and recovery on the agent side
+- [vaults.md](#sec-509) for what a funded agent wallet can then back
- [authentication.md](#sec-103) for sessions, CSRF tokens, and why API keys do not apply here
-- [money-map.md](#sec-287) for how funds move across the whole platform
+- [money-map.md](#sec-291) for how funds move across the whole platform
---
-<a id="sec-489"></a>
+<a id="sec-495"></a>
> **Source:** `docs/ux-flows/01-onboarding-creation.md` · [↑ table of contents](#table-of-contents)
@@ -112925,7 +113748,7 @@ Honest limits, stated plainly: this is a **custodial** wallet, so the platform c
---
-<a id="sec-490"></a>
+<a id="sec-496"></a>
> **Source:** `docs/ux-flows/02-forge-text-to-3d.md` · [↑ table of contents](#table-of-contents)
@@ -113107,7 +113930,7 @@ Routing facts (from `vercel.json`):
---
-<a id="sec-491"></a>
+<a id="sec-497"></a>
> **Source:** `docs/ux-flows/03-3d-editing-viewer.md` · [↑ table of contents](#table-of-contents)
@@ -113313,7 +114136,7 @@ Routing summary (from `vite.config.js`):
---
-<a id="sec-492"></a>
+<a id="sec-498"></a>
> **Source:** `docs/ux-flows/04-embed-widget-studio.md` · [↑ table of contents](#table-of-contents)
@@ -113487,7 +114310,7 @@ Routing recap (from `vercel.json`):
---
-<a id="sec-493"></a>
+<a id="sec-499"></a>
> **Source:** `docs/ux-flows/05-discovery-social.md` · [↑ table of contents](#table-of-contents)
@@ -113759,7 +114582,7 @@ Routing recap (from `vercel.json`):
---
-<a id="sec-494"></a>
+<a id="sec-500"></a>
> **Source:** `docs/ux-flows/06-marketplace-skills.md` · [↑ table of contents](#table-of-contents)
@@ -113977,7 +114800,7 @@ Routing facts confirmed in `vercel.json` (line numbers shift too often to pin; g
---
-<a id="sec-495"></a>
+<a id="sec-501"></a>
> **Source:** `docs/ux-flows/07-crypto-trading-analytics.md` · [↑ table of contents](#table-of-contents)
@@ -114368,7 +115191,7 @@ coin-intel, pump-visualizer and pump-live: adding a coin on any surface shows up
---
-<a id="sec-496"></a>
+<a id="sec-502"></a>
> **Source:** `docs/ux-flows/08-coin-launch-wallets.md` · [↑ table of contents](#table-of-contents)
@@ -114644,7 +115467,7 @@ real Solana/EVM RPC, pump.fun, and x402 — no mocks.
---
-<a id="sec-497"></a>
+<a id="sec-503"></a>
> **Source:** `docs/ux-flows/09-x402-agent-commerce.md` · [↑ table of contents](#table-of-contents)
@@ -114990,7 +115813,7 @@ choreographed two-agent narrative driven by Server-Sent Events.
---
-<a id="sec-498"></a>
+<a id="sec-504"></a>
> **Source:** `docs/ux-flows/10-chat-brain-labs.md` · [↑ table of contents](#table-of-contents)
@@ -115233,7 +116056,7 @@ modules. Routes resolved via `vercel.json` rewrites.
---
-<a id="sec-499"></a>
+<a id="sec-505"></a>
> **Source:** `docs/ux-flows/11-account-dashboard.md` · [↑ table of contents](#table-of-contents)
@@ -115456,7 +116279,7 @@ Shared auth concepts:
---
-<a id="sec-500"></a>
+<a id="sec-506"></a>
> **Source:** `docs/ux-flows/12-home-and-content.md` · [↑ table of contents](#table-of-contents)
@@ -115696,7 +116519,7 @@ All `/.well-known/*` and `/openapi.json` / `/sitemap.xml` responses are JSON/XML
---
-<a id="sec-501"></a>
+<a id="sec-507"></a>
> **Source:** `docs/validation.md` · [↑ table of contents](#table-of-contents)
@@ -115899,7 +116722,7 @@ The hash stored on-chain is `keccak256(JSON.stringify(report))`. Anyone can reco
2. `hashReport(report)` produces the same hash if the input is identical.
3. Query `ValidationRegistry.getValidationStatus(requestHash)` (or `getAgentValidations(agentId)` for every request id on the agent) and compare its `responseHash`. `src/erc8004/validation-recorder.js` wraps this as `getLatestValidation({ agentId, runner, chainId })`.
-The registry has no on-chain validator allow-list: any address the owner requests can answer. Which verdicts three.ws presents as "Validated" is off-chain policy, maintained in [`public/.well-known/validators.json`](../public/.well-known/validators.json). See [`specs/VALIDATORS.md`](../specs/VALIDATORS.md) for how to be recognized, and [`docs/erc8004/validation-attestation.md`](#sec-189) for the platform's own automatic attestation flow.
+The registry has no on-chain validator allow-list: any address the owner requests can answer. Which verdicts three.ws presents as "Validated" is off-chain policy, maintained in [`public/.well-known/validators.json`](../public/.well-known/validators.json). See [`specs/VALIDATORS.md`](../specs/VALIDATORS.md) for how to be recognized, and [`docs/erc8004/validation-attestation.md`](#sec-191) for the platform's own automatic attestation flow.
The minimum check suite for a `pass` verdict includes:
@@ -116075,7 +116898,7 @@ The toggle's CSS class reflects the highest severity: `level-0` (errors), `level
---
-<a id="sec-502"></a>
+<a id="sec-508"></a>
> **Source:** `docs/vanity.md` · [↑ table of contents](#table-of-contents)
@@ -116083,7 +116906,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-544) rail and the
+no account, and no SOL. Pay per call in USDC over the [x402](#sec-551) rail and the
server grinds (or delivers from stock) a brand-new keypair that matches.
| Endpoint | What it is | Chars | Price | Pick it when |
@@ -116101,7 +116924,7 @@ Tier 1 and tier 3 **share one warehouse** — the `vanity_inventory` table,
pre-ground on batch spot CPU (`workers/vanity-grinder`) and auto-replenished
when stock runs low (`api/cron/vanity-inventory-replenish`, hourly). Tier 1 is
"give me anything that matches, right now"; tier 3 is "let me pick this exact
-address from the catalog." [Pump Launcher](#sec-339) draws from the
+address from the catalog." [Pump Launcher](#sec-344) draws from the
same warehouse for instant vanity mint addresses.
## Which agent uses this, and why us
@@ -116303,7 +117126,7 @@ workers/vanity-grinder/grind.mjs` (see its
`vanitySuffix` checks this same inventory before grinding a mint address live —
a hit skips the grind entirely (`vanity_source: "inventory"` in the response),
a miss grinds as before (`vanity_source: "ground"`). Same one-shot claim, same
-atomicity, no separate purchase step. See [pump-launcher.md](#sec-339).
+atomicity, no separate purchase step. See [pump-launcher.md](#sec-344).
---
@@ -116318,20 +117141,20 @@ challenges and the discovery doc stay in parity.
## Related
-- [x402 endpoints overview](#sec-539)
+- [x402 endpoints overview](#sec-546)
- [three-vanity/v1 protocol spec](#sec-005)
-- [Pump Launcher](#sec-339) — accepts an optional vanity mint prefix/suffix
+- [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)
---
-<a id="sec-503"></a>
+<a id="sec-509"></a>
> **Source:** `docs/vaults.md` · [↑ table of contents](#table-of-contents)
# USDC agent vaults: the deep reference
-A vault lets strangers put **real USDC** behind one trading agent, on terms the agent's owner publishes up front. The product-level tour (who each surface is for, how vaults sit next to the Arena, the Theater and Swarms) is in [trading-arenas.md](#sec-411), under "Back-an-Agent Vaults". **Read that first.** This document is the layer underneath it: the exact routes, the auth boundary on each one, the share math, the guards that sit in front of a trade, and the audit ledger anyone can read.
+A vault lets strangers put **real USDC** behind one trading agent, on terms the agent's owner publishes up front. The product-level tour (who each surface is for, how vaults sit next to the Arena, the Theater and Swarms) is in [trading-arenas.md](#sec-416), under "Back-an-Agent Vaults". **Read that first.** This document is the layer underneath it: the exact routes, the auth boundary on each one, the share math, the guards that sit in front of a trade, and the audit ledger anyone can read.
Everything here moves real money on Solana mainnet. Read [Safety: what spends, and what has to confirm it](#safety-what-spends-and-what-has-to-confirm-it) before you call any `POST`.
@@ -116369,7 +117192,7 @@ The examples below use an API key in `$API_KEY`.
Only an agent with a **provable trading record** can be backed. `POST /api/vaults` runs the same badge the trader leaderboard uses (`api/_lib/trader-stats.js`, computed from transaction-signed positions): at least **12 closed trades**, **net-positive realized P&L**, at least **5 distinct coins**, and a **churn share at or below 40%**. Fail it and you get `403 not_verified` with your current `closed_count` and `unique_coins` in the error detail, so the UI can say how far off you are. See [agent-reputation.md](#sec-056) for how the score is derived.
-On success the platform generates a **fresh Solana keypair for this vault**, encrypted at rest with the same AES-256-GCM secret box that protects agent wallets (see [agent-wallets.md](#sec-072) and [custody.md](#sec-170)). Backer capital lives in that wallet only. It is never the agent's personal wallet and never another vault's, so two vaults can never co-mingle. Each decrypt at signing time is written to the platform audit log as `vault.key_use`.
+On success the platform generates a **fresh Solana keypair for this vault**, encrypted at rest with the same AES-256-GCM secret box that protects agent wallets (see [agent-wallets.md](#sec-072) and [custody.md](#sec-172)). Backer capital lives in that wallet only. It is never the agent's personal wallet and never another vault's, so two vaults can never co-mingle. Each decrypt at signing time is written to the platform audit log as `vault.key_use`.
One open vault per agent: a second attempt returns `409 vault_exists`.
@@ -116402,7 +117225,7 @@ curl -sX POST https://three.ws/api/vaults \
}'
```
-`201` returns the vault row including `vault_address`. Note the address: the vault also needs a little **SOL** to pay swap fees and open token accounts, and there is no vault-funding endpoint. Send roughly 0.01 SOL to `vault_address` yourself, for example from your master wallet (see [user-wallet.md](#sec-488)). Without it, trades are refused with `insufficient_sol_for_fees` before anything is signed.
+`201` returns the vault row including `vault_address`. Note the address: the vault also needs a little **SOL** to pay swap fees and open token accounts, and there is no vault-funding endpoint. Send roughly 0.01 SOL to `vault_address` yourself, for example from your master wallet (see [user-wallet.md](#sec-494)). Without it, trades are refused with `insufficient_sol_for_fees` before anything is signed.
The browser flow is the "Open a vault" modal on [/vaults](https://three.ws/vaults), which is only shown to a signed-in user and pre-fills the same defaults.
@@ -116604,7 +117427,7 @@ curl -s "https://three.ws/api/vaults/ledger?vault_id=8b1c04f6-59a8-4d0e-a1b7-3f5
}
```
-Two properties worth relying on: rows are written **before** funds move for the paths that can double-submit (redeem, trade), so a `pending` or `failed` row is itself evidence of an attempt, and money-moving rows carry the signature you can verify yourself on Solscan. The same movements also land in the platform custody trail described in [custody.md](#sec-170).
+Two properties worth relying on: rows are written **before** funds move for the paths that can double-submit (redeem, trade), so a `pending` or `failed` row is itself evidence of an attempt, and money-moving rows carry the signature you can verify yourself on Solscan. The same movements also land in the platform custody trail described in [custody.md](#sec-172).
## Reading a vault
@@ -116635,16 +117458,16 @@ Two honest limits a backer should know: the platform can sign for the vault (tha
## Related
-- [trading-arenas.md](#sec-411) for the product overview of vaults and the surfaces around them
+- [trading-arenas.md](#sec-416) for the product overview of vaults and the surfaces around them
- [agent-wallets.md](#sec-072) for the custodial wallet a backer funds from
-- [custody.md](#sec-170) for spend limits, the freeze switch, and proof of custody
-- [user-wallet.md](#sec-488) for the per-user master wallet, the easiest way to send a vault its fee SOL
+- [custody.md](#sec-172) for spend limits, the freeze switch, and proof of custody
+- [user-wallet.md](#sec-494) for the per-user master wallet, the easiest way to send a vault its fee SOL
- [agent-reputation.md](#sec-056) for the badge that gates opening a vault
- [authentication.md](#sec-103) for sessions, CSRF tokens, and API keys
---
-<a id="sec-504"></a>
+<a id="sec-510"></a>
> **Source:** `docs/viability.md` · [↑ table of contents](#table-of-contents)
@@ -116826,7 +117649,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-540): the platform's own endpoint
+- [x402 revenue and receipts](#sec-547): 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
@@ -116834,7 +117657,7 @@ appears only when there is something to show, pointing at the filtered
---
-<a id="sec-505"></a>
+<a id="sec-511"></a>
> **Source:** `docs/viewer.md` · [↑ table of contents](#table-of-contents)
@@ -117228,7 +118051,7 @@ A subset of state (background, transparency, background color, auto-rotate, expo
---
-<a id="sec-506"></a>
+<a id="sec-512"></a>
> **Source:** `docs/voice-lab.md` · [↑ table of contents](#table-of-contents)
@@ -117390,14 +118213,14 @@ The agent-voice handler ([`api/agents/_id/voice.js`](../api/agents/_id/voice.js)
## Related
-- [Voice and lipsync tutorial](#sec-481): the authoritative step-by-step, including wiring a cloned voice into an agent.
-- [Lipsync](#sec-264): how synthesized speech drives an avatar's mouth in real time.
-- [Talking Avatar Video](#sec-403): render a talking-head clip from an avatar and an audio track.
+- [Voice and lipsync tutorial](#sec-487): the authoritative step-by-step, including wiring a cloned voice into an agent.
+- [Lipsync](#sec-267): how synthesized speech drives an avatar's mouth in real time.
+- [Talking Avatar Video](#sec-408): render a talking-head clip from an avatar and an audio track.
- Pages: [/voice](https://three.ws/voice), [/dashboard](https://three.ws/dashboard).
---
-<a id="sec-507"></a>
+<a id="sec-513"></a>
> **Source:** `docs/walk-leaderboard.md` · [↑ table of contents](#table-of-contents)
@@ -117521,7 +118344,7 @@ As coded, in layers. Each one bounds a different kind of nonsense:
| Achievement allowlist | same | Only the four known codes persist, and each unlocks once per walker, so badges cannot be farmed by replaying a batch. |
| Idempotent rollup | unique index in [the migration](../api/_lib/migrations/20260621140000_walk_metrics.sql) | Batches merge into one row per dimension tuple per day, so the table cannot be flooded into a different shape. |
-**What these guards do and do not claim.** `POST /api/walk/metrics` is a public, open-CORS ingest keyed on a client-supplied anonymous id, because embeds post from third-party hosts and anonymous walkers are first-class on the board. The guards above bound the size, rate, and attribution of any single claim; they do not cryptographically prove that a walk happened. There is no cross-batch plausibility check (for example, distance against elapsed duration) and no server-side replay of the controller. Treat the board as a gamified activity ranking, not as an audited measurement. If you need a movement claim that a third party can verify, that is a different product: [World Lines](#sec-512) issue agent-signed proofs of physical presence with server-derived co-location.
+**What these guards do and do not claim.** `POST /api/walk/metrics` is a public, open-CORS ingest keyed on a client-supplied anonymous id, because embeds post from third-party hosts and anonymous walkers are first-class on the board. The guards above bound the size, rate, and attribution of any single claim; they do not cryptographically prove that a walk happened. There is no cross-batch plausibility check (for example, distance against elapsed duration) and no server-side replay of the controller. Treat the board as a gamified activity ranking, not as an audited measurement. If you need a movement claim that a third party can verify, that is a different product: [World Lines](#sec-518) issue agent-signed proofs of physical presence with server-derived co-location.
---
@@ -117687,14 +118510,14 @@ The anonymous id is generated and persisted by the walk runtime in `localStorage
## Related
-- [Add the Walk Companion to your site](#sec-482), the hands-on path from a copy-paste iframe to the `@three-ws/walk` package, including the surfaces that produce the metrics ranked here.
+- [Add the Walk Companion to your site](#sec-488), the hands-on path from a copy-paste iframe to the `@three-ws/walk` package, including the surfaces that produce the metrics ranked here.
- The walk documentation set on the site, served from `public/docs/walk/`: `/docs/walk` (index), `/docs/walk/getting-started`, `/docs/walk/walk-page`, `/docs/walk/embed-iframe`, `/docs/walk/embed-sdk`, `/docs/walk/companion-mode`, `/docs/walk/chrome-extension`, `/docs/walk/postmessage-events`, `/docs/walk/changelog`, and `/docs/walk/analytics`, which covers the per-creator dashboard fed by the same ingest.
- The creator-side view of this data: `three.ws/walk-analytics`, backed by `GET /api/walk/analytics`.
-- [World Lines](#sec-512), for movement claims that carry a verifiable agent signature rather than a leaderboard rank.
+- [World Lines](#sec-518), for movement claims that carry a verifiable agent signature rather than a leaderboard rank.
---
-<a id="sec-508"></a>
+<a id="sec-514"></a>
> **Source:** `docs/web-component.md` · [↑ table of contents](#table-of-contents)
@@ -117802,7 +118625,7 @@ el.removeAttribute('sign-language'); // off
Signing rides the same `SPEAK` event as spoken replies, so it works identically
in the hosted app and in an embed. A runnable page is
[examples/sign-language.html](../examples/sign-language.html); the engine and its
-vocabulary are documented in [Sign language](#sec-381), and the
+vocabulary are documented in [Sign language](#sec-386), and the
alphabet is browsable at [/asl-alphabet](https://three.ws/asl-alphabet).
### Skills and memory
@@ -118653,7 +119476,7 @@ defineElement('my-agent');
---
-<a id="sec-509"></a>
+<a id="sec-515"></a>
> **Source:** `docs/widget-api.md` · [↑ table of contents](#table-of-contents)
@@ -118860,7 +119683,7 @@ If you have multiple widgets and want to coordinate them (sync camera, broadcast
---
-<a id="sec-510"></a>
+<a id="sec-516"></a>
> **Source:** `docs/widget-studio.md` · [↑ table of contents](#table-of-contents)
@@ -119104,14 +119927,14 @@ You can override these freely in the iframe `width` and `height` attributes. Add
## Next steps
-- [Widget API (JSON-RPC)](#sec-509) — programmatic control over an embedded widget: camera, animation, screenshots, model loading
-- [Widgets reference](#sec-511) — technical details, postMessage API, CSP config, and oEmbed spec
-- [Web component](#sec-508) — the `<agent-3d>` custom element for developer integrations
-- [Embedding guide](#sec-186) — advanced embedding patterns and iframe options
+- [Widget API (JSON-RPC)](#sec-515) — programmatic control over an embedded widget: camera, animation, screenshots, model loading
+- [Widgets reference](#sec-517) — technical details, postMessage API, CSP config, and oEmbed spec
+- [Web component](#sec-514) — the `<agent-3d>` custom element for developer integrations
+- [Embedding guide](#sec-188) — advanced embedding patterns and iframe options
---
-<a id="sec-511"></a>
+<a id="sec-517"></a>
> **Source:** `docs/widgets.md` · [↑ table of contents](#table-of-contents)
@@ -119616,7 +120439,7 @@ No IP addresses, no user-agent strings, no cookies, no chat message content. The
## Programmatic control
-Need to drive a widget from the parent page — change the camera, play an animation, grab a screenshot? See the [Widget API (JSON-RPC)](#sec-509) reference. The `ThreeWidget` SDK lives at `/widget-client.js` and works with any iframe pointing at `/widget`.
+Need to drive a widget from the parent page — change the camera, play an animation, grab a screenshot? See the [Widget API (JSON-RPC)](#sec-515) reference. The `ThreeWidget` SDK lives at `/widget-client.js` and works with any iframe pointing at `/widget`.
---
@@ -119629,7 +120452,7 @@ Need to drive a widget from the parent page — change the camera, play an anima
---
-<a id="sec-512"></a>
+<a id="sec-518"></a>
> **Source:** `docs/world-lines.md` · [↑ table of contents](#table-of-contents)
@@ -119871,7 +120694,7 @@ Coverage for the crypto core lives in [tests/world-lines-crypto.test.js](../test
## Privacy: exactly what is stored
-The engineering analysis for all of IRL is the [IRL threat model](#sec-257); the user-facing summary is the `three.ws/irl-privacy` page. World Lines specifically:
+The engineering analysis for all of IRL is the [IRL threat model](#sec-260); the user-facing summary is the `three.ws/irl-privacy` page. World Lines specifically:
**Stored.**
@@ -120211,14 +121034,14 @@ Both handlers log their enforcement mode once per cold start, so a production mi
## Related
- [IRL: agents in the real world](irl.md#world-lines), the product-level overview and the rest of the presence layer.
-- [IRL threat model](#sec-257), the adversarial analysis behind every radius and cap above.
-- [Place a 3D agent in your real environment](#sec-459), how to create the anchor pin a World Line needs.
+- [IRL threat model](#sec-260), the adversarial analysis behind every radius and cap above.
+- [Place a 3D agent in your real environment](#sec-465), how to create the anchor pin a World Line needs.
- [API reference](#sec-096), the one-screen summary of these endpoints alongside the rest of `/api/irl/*`.
- [AR](#sec-099), the camera and WebXR layer the ceremony builds on.
---
-<a id="sec-513"></a>
+<a id="sec-519"></a>
> **Source:** `docs/x-archive.md` · [↑ table of contents](#table-of-contents)
@@ -120279,7 +121102,7 @@ clean checkout.
## The report
-[docs/x-archive/trythreews-engagement.md](#sec-514)
+[docs/x-archive/trythreews-engagement.md](#sec-520)
is generated, never hand-edited. It carries:
- headline totals and the engagement **distribution** (median, p75/p90/p99, and
@@ -120330,7 +121153,7 @@ Code: [scripts/x-archive-lib.mjs](../scripts/x-archive-lib.mjs)
---
-<a id="sec-514"></a>
+<a id="sec-520"></a>
> **Source:** `docs/x-archive/trythreews-engagement.md` · [↑ table of contents](#table-of-contents)
@@ -120581,7 +121404,7 @@ The floor is as instructive as the ceiling: these are the shapes to stop repeati
---
-<a id="sec-515"></a>
+<a id="sec-521"></a>
> **Source:** `docs/x-memory-seeding.md` · [↑ table of contents](#table-of-contents)
@@ -120600,7 +121423,7 @@ yes on a screen that tells you exactly what will be read and stored.
- **Surface**: Settings, Connected accounts, X card at [/settings#connected-accounts](https://three.ws/settings#connected-accounts)
- **API**: `/api/agents/:id/memory/seed/x`
-- **Related**: [Memory system](#sec-280), [Farcaster memory seeding](#sec-220), [GitHub seeding in the same table](memory.md#seeding-memory-from-an-existing-account)
+- **Related**: [Memory system](#sec-284), [Farcaster memory seeding](#sec-222), [GitHub seeding in the same table](memory.md#seeding-memory-from-an-existing-account)
---
@@ -120699,7 +121522,7 @@ Each fact becomes one row in `agent_memories`:
from your posting history.
- Salience `0.80` for the top-ranked fact, decaying by rank.
- The **top five facts land in the `working` tier**, the always-in-context core
- the chat runtime pages into every reply (see [memory system](#sec-280)).
+ the chat runtime pages into every reply (see [memory system](#sec-284)).
That is what makes a seed observable in the very next conversation turn.
- `context` carries `source: 'x_seed'`, your handle, the distillation lane
(`model` or `derived`), the disclosure version, and the consent id.
@@ -120901,7 +121724,7 @@ Seeded rows in `agent_memories` are found by tag (`tags && '{x_seed}'`) and by
---
-<a id="sec-516"></a>
+<a id="sec-522"></a>
> **Source:** `docs/x-posts/3d-ar-studio-launch.md` · [↑ table of contents](#table-of-contents)
@@ -121049,7 +121872,159 @@ Use these under the main post rather than stuffing them into it.
---
-<a id="sec-517"></a>
+# Two-account plan: @trythreews then @nichxbt
+
+The product account announces the thing. The personal account gives it a reason to be
+interesting. Two different jobs, so two different voices, and they must not read as the same
+person posting twice.
+
+**Sequencing.** Post from @trythreews first. Wait for it to settle, roughly twenty to forty
+minutes, then quote it from @nichxbt. Quoting immediately reads as self-amplification and
+splits the engagement across both posts before either has traction. Do not have @trythreews
+reply to the quote tweet: let the personal account carry that branch of the conversation.
+
+**Voice split.**
+
+- **@trythreews** is the platform. Declarative, no "I", no backstory, no feelings about it.
+ It states what exists, shows it, and links to it.
+- **@nichxbt** is a person who built it. First person, one specific detail nobody would know
+ unless they had done the work, and an opinion. This is the post that earns the reshare.
+
+---
+
+## @trythreews (post first)
+
+Attach the two room photos plus the studio screenshot.
+
+### Option A: the release (recommended)
+
+```
+3D AR Studio is open source.
+
+The multi-model AR studio from three.ws, extracted into a package any site can drop in:
+
+<script src="unpkg.com/3d-ar-studio"></script>
+<ar-studio></ar-studio>
+
+Describe an object, watch it generate, put it on your real floor. Add more. Share the scene as a link.
+
+Free, no key, Apache-2.0.
+
+nirholas.github.io/3D-AR-Studio
+```
+
+### Option B: the capability, for a non-developer timeline
+
+```
+Put anything in your room, straight from a web page.
+
+Type "a brass desk lamp". It gets generated, then stands on your actual floor at actual size. Put a chair next to it. Send the whole room to someone as a link.
+
+One script tag. Free. Open source.
+
+nirholas.github.io/3D-AR-Studio
+```
+
+### Option C: the shortest version
+
+```
+Any web page can now put real 3D objects in your actual room.
+
+One script tag. Free. Open source. Works on the phone you're holding.
+
+nirholas.github.io/3D-AR-Studio
+```
+
+---
+
+## @nichxbt (quote tweet, 20 to 40 minutes later)
+
+Pick one. A is the strongest: it is a real thing that happened, it is slightly unflattering,
+and the technical detail proves the fix is real.
+
+### Option A: the confession (recommended)
+
+```
+Yesterday I found out my own AR was fake on iPhone.
+
+iOS has no WebXR, so we were painting the model over the camera feed. It floats. No real size. Nothing occludes it.
+
+Every iPhone already ships ARKit. Now it uses it, and the model converts to USDZ on the device in about a second.
+```
+
+### Option B: why it is open source
+
+```
+People kept asking how the AR on three.ws works.
+
+So I pulled it out of our site and published it. One script tag, your models, your domain, none of it pointing back at us unless you want it to.
+
+I would rather this exist everywhere than be a feature only we have.
+```
+
+### Option C: for the graphics crowd
+
+```
+The part I am proud of: no rig allowlist.
+
+Any humanoid GLB that ships with no animation gets an idle retargeted onto its own skeleton. Mixamo, VRM, Unreal, Daz, MMD, whatever came out of your pipeline.
+
+No T-posing statues in anyone's living room.
+```
+
+### Option D: the short one
+
+```
+Every phone has had AR hardware in it for years and almost no website uses it.
+
+Fixed that. It is one script tag and it is free.
+```
+
+---
+
+## @nichxbt follow-up replies (under the quote tweet)
+
+Post one or two of these under your own quote tweet, not under the @trythreews post. They are
+where the developers land.
+
+```
+It is one npm install if you would rather bundle it:
+
+npm i 3d-ar-studio three
+
+Or two commands to get a live AR page on GitHub Pages:
+
+npx 3d-ar-studio create my-ar-site
+npx 3d-ar-studio deploy
+```
+
+```
+It also ships an MCP server, so an agent can generate a model, arrange a scene, and hand a person one link that opens the whole arrangement in their room.
+
+npx 3d-ar-studio-mcp
+```
+
+```
+Models are free too. A few hundred public-domain props are already in it, and generating a new one needs no key and no account.
+
+Point it at your own catalogue with one option if you would rather use yours.
+```
+
+---
+
+## If someone big replies
+
+- **A graphics or WebXR person**: go technical immediately. Mention the per-model XRAnchor,
+ the light estimation, and the depth occlusion, and offer the repo. They will read code.
+- **A non-technical account**: send them the demo link and tell them to open it on their
+ phone and tap the AR button. Nothing else.
+- **Someone asking "why not Unity / 8th Wall / a native app"**: no app install, no licence,
+ no key, and it is a web page you can link to. That is the whole argument, do not oversell
+ past it.
+
+---
+
+<a id="sec-523"></a>
> **Source:** `docs/x-posts/3d-ar-studio-video-script.md` · [↑ table of contents](#table-of-contents)
@@ -121174,7 +122149,7 @@ match them to the narration beats:
---
-<a id="sec-518"></a>
+<a id="sec-524"></a>
> **Source:** `docs/x-posts/README.md` · [↑ table of contents](#table-of-contents)
@@ -121185,24 +122160,291 @@ staging only: nothing here is posted automatically, and posting is owner-gated p
[`CLAUDE.md`](../CLAUDE.md) (`git push` / publishing / posting to external channels needs
explicit approval). Each file states what it's for and what has already been verified true.
-- [`metaplex-agent-mcp-launch.md`](#sec-525): the open-source agent
- infrastructure announcement: `@three-ws/metaplex-agent-mcp` (on-chain deploy + identity) and
- `@three-ws/onchain-agent-wallets` (spending allowance + x402), and why every integration is
- bullish for $THREE.
-- [`metaplex-agent-mcp-veo-script.md`](#sec-526): shot-by-shot Veo
- (image-to-video) prompts for the companion clip, built from a three.ws 3D avatar as the
- reference frame.
-- [`sperax-staking-in-chat-x-post.md`](#sec-532): SperaxOS chat-native
- staking/balance/buy-SPA tool calls (shipped) and the embedded `/staking` iframe page (not yet
- working, do not announce until the blockers listed in the file are resolved).
+## How these are written
+
+- **Paste-ready, not outlines.** No placeholders, no "insert link here". Every link in a draft
+ resolves today.
+- **Character counts are measured, not guessed**, against X's rule that any URL counts as 23
+ characters regardless of length. Where a draft states a count, it was computed.
+- **Each file opens with a verified-claims block** and, where it matters, a "do not claim" list.
+ That list is the useful part: it records what someone could disprove in ten minutes.
+- **No em-dashes and no emoji**, matching the repo's writing rules.
+
+## Product and infrastructure launches
+
+| 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 |
+| [`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 |
+
+## 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 |
+| [`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 |
+
+## Conventions
+
+Posting is manual and owner-gated. **X delivery of the changelog is retired** (owner directive
+2026-07-18): `scripts/changelog-x.mjs` still exists but no cron calls it, so nothing in this folder
+is on an automated lane. Treat every file here as copy waiting for a human to send.
Not registered in `data/pages.json`, and doesn't need to be: `scripts/audit-docs.mjs` only checks
direct `docs/*.md` files for a page entry, not files under a `docs/` subdirectory, so a nested
-folder like this one is the convention for internal drafts that shouldn't be crawlable.
+folder like this one is the convention for internal drafts that shouldn't be crawlable. When a
+draft moves in here from the top level, drop its slug from `UNPUBLISHED_DOCS` in that script: the
+entry is dead once the file is no longer routed.
---
-<a id="sec-519"></a>
+<a id="sec-525"></a>
+
+> **Source:** `docs/x-posts/ar-quick-look-fix-x-post.md` · [↑ table of contents](#table-of-contents)
+
+# X post: AR now actually opens AR on iPhone
+
+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
+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
+iPhone, true scale, real floor tracking, the exact pipeline the avatar page always used. The public
+copy below leads with that as a straight product claim, not as the resolution of a prior gap; the
+internal context above (what changed, which pages were affected) stays for our own reference and for
+answering direct questions, not as material to post proactively.
+
+**Every claim below is true today, verified against the shipped code (not yet deployed, see the
+gate below):**
+
+- Apple Quick Look needs a real USDZ file. `<model-viewer>`'s `ar`/`ar-modes` attribute does **not**
+ generate one from a GLB on its own; it needs `ios-src` pointed at an actual USDZ, or Quick Look
+ never activates.
+- `/avatars/:id/ar` ([src/ar-page.js](../src/ar-page.js)) always did this right: it fetches the
+ GLB, converts it client-side with three.js's `USDZExporter`, and sets the result as `ios-src`
+ before offering Quick Look.
+- `/ar` (AR Forge) and the `/api/ar` endpoint it falls back to did not. Their `<model-viewer>` had no
+ `ios-src`, so `canActivateAR` was false on every iPhone and the button silently fell back to the
+ plain 3D viewer. A comment in the old code claimed model-viewer converted the GLB automatically.
+ It does not, and never did.
+- `/ar/studio` (multi-model AR) had no Quick Look path at all on iOS. It faked AR with a
+ `getUserMedia` camera feed plus a gyroscope-driven camera look: no plane detection, no correct
+ real-world scale, the model floats instead of resting on your floor. Android got real WebXR
+ tracking through a separate, easy-to-miss "Immersive" button; there was no Scene Viewer fallback
+ for Android devices without WebXR either.
+- The fix reuses the exact pipeline that already worked: a new page,
+ [pages/ar-view.html](../pages/ar-view.html) +
+ [src/ar-view.js](../src/ar-view.js), runs the same `usdz-pipeline.js` conversion the avatar page
+ uses. `/api/ar` now hands iOS and desktop off to it (`api/_lib/ar-launch.js`,
+ [tests/ar-export.test.js](../tests/ar-export.test.js),
+ [tests/api/ar-endpoint.test.js](../tests/api/ar-endpoint.test.js): 49 passing), and AR Forge
+ inherits the fix with no changes of its own, since its button already fell back to `/api/ar`.
+ Android's Scene Viewer redirect was already correct and is unchanged.
+- AR Studio's control now resolves what the device actually supports and routes there: the immersive
+ WebXR session where it exists, Quick Look on iOS, Scene Viewer on Android otherwise, an honest "open
+ this on your phone" QR prompt everywhere else, each selectable per-model from the selection bar too.
+ Shipped in `2e7a7e9fc`.
+- Shared `/api/ar` links still unfurl with a real render of the model on X, Discord, and iMessage: the
+ redirect to `/ar/view` carries the same `og:image`/title an outright 302 would have dropped.
+
+**Gate before any of this posts: not deployed yet.** All five commits (`2e7a7e9fc` through the docs
+cleanup) are on `main` locally, five ahead of `origin/main`. Per the deploy gate in `CLAUDE.md`,
+shipping to production needs the owner's go-ahead. Do not schedule or post any draft below until
+`https://three.ws/api/version` shows a build that includes this work and `/ar`, `/ar/studio`, and
+`/api/ar?src=...` have been hand-verified on a real iPhone.
+
+**Tone directive (owner, 2026-08-20): lead bullish, not humble.** Earlier drafts in this file framed
+this as "we shipped three surfaces and only one worked, sorry, now fixed." That reads as an apology,
+not an announcement. The posts below drop the self-deprecation entirely: no "broken," no "gap," no
+before/after confession. Say what's true and say it like it's the best AR on the market, because the
+underlying claims (real ARKit Quick Look, true scale, real floor tracking, same pipeline across every
+surface) are all still true and worth being loud about.
+
+**Things to NOT claim (accuracy guardrail, not a tone note):**
+
+1. **Do not claim AR Studio's iPhone experience places multiple objects with real tracking.** Quick
+ Look places one object at a time by design (a USDZ is a single scene). Multi-object placement with
+ real tracking is still Android/WebXR only; the per-model "Place in your space" button on iOS is
+ correct and true, but do not stretch it into "full multi-model AR on iPhone."
+2. **Do not claim a specific competitor comparison you haven't verified.** "Nobody ships AR this
+ clean" is fine as a confidence claim about three.ws; naming or implying a specific rival platform
+ does it worse is not, unless that's been checked.
+
+---
+
+## 1. Main post (recommended), from @trythreews
+
+216 characters with X's 23-character URL count.
+
+> iPhone AR on three.ws is now exactly what it should've been from day one: real ARKit Quick Look,
+> true scale, planted right on your actual floor.
+>
+> Forge a model. Place it in your room. Watch it look real.
+>
+> three.ws/ar
+
+Why this one: all upside, no confession. It states the experience as a fact of the product, not as
+the resolution of a problem, and "watch it look real" is a dare to try it, not an apology.
+
+### 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
+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.
+
+> Genuinely one of my favorite ships this month. Real ARKit tracking, correct scale, models that
+> actually sit on your floor instead of floating in a camera filter. This is what AR is supposed to
+> feel like. three.ws just keeps getting better.
+
+239 characters.
+
+Why this one: it adds a founder's personal enthusiasm and a "we keep shipping" signal the brand
+account can't say about itself without sounding like it's grading its own homework.
+
+**Alternate, shorter and punchier**, 142 characters:
+
+> We don't do fake AR. Real USDZ, real ARKit Quick Look, real floor tracking, across every single
+> AR surface on the site now. Proud of this one.
+
+**Rules for this one:**
+
+- Quote-tweet, do not reply-thread. A reply reads like a correction; a quote-tweet reads like an
+ endorsement layered on top.
+- First-person, present enthusiasm: "I" and "my phone," not "we" and "our team."
+- Post it a few minutes after the main post, not in the same minute: back-to-back posts from both
+ accounts read as coordinated marketing rather than one person genuinely hyped about the other.
+
+## 2. Alternate: the technical flex
+
+249 characters.
+
+> Apple Quick Look needs a real USDZ file, not just a GLB. three.ws generates it live, on-device,
+> the same way for every model, every avatar, every AR Studio scene. No shortcuts, no server round
+> trip: that's why it lands right every time.
+>
+> three.ws/ar
+
+Why this one: for a technical audience, naming the exact mechanism (real on-device USDZ conversion,
+not a server trick) is more convincing than any adjective, and it's a flex, not a confession.
+
+## 3. Alternate: the room-floor angle
+
+221 characters.
+
+> AR that doesn't know where your floor is isn't AR. It's a video filter.
+>
+> three.ws places every model with real ARKit tracking, true scale, right on your actual floor. On
+> iPhone, on Android, everywhere.
+>
+> three.ws/ar/studio
+
+Why this one: leads with a strong, quotable claim about what AR even means, then lands three.ws on
+the right side of it.
+
+## 4. Alternate: the short one
+
+153 characters. Good as a reply-chain opener or a standalone if the thread below feels heavy.
+
+> three.ws/ar and three.ws/ar/studio now open real Apple Quick Look on iPhone: true scale, real
+> floor tracking, every time you tap the button.
+>
+> three.ws/ar
+
+---
+
+## Thread version
+
+Post 1 is the main post above. Then:
+
+**2/**
+
+> Real ARKit AR runs on a real USDZ file, not a GLB. three.ws converts every model to USDZ live,
+> on-device, the instant you tap the AR button.
+
+**3/**
+
+> That's the same conversion pipeline behind every AR surface on the site now: AR Forge, AR Studio,
+> and every avatar page, all landing models in your room with true scale and real floor tracking.
+
+**4/**
+
+> AR Studio also hands off straight to Google Scene Viewer on Android, or the full immersive WebXR
+> session where the device supports it. One button, the best AR your phone can actually do.
+
+**5/**
+
+> Forge a model or grab an avatar, hit AR, watch it sit in your room like it's actually there.
+
+**6/**
+
+> Try it: three.ws/ar, or build a full scene at three.ws/ar/studio.
+>
+> three.ws
+
+---
+
+## Replies worth pre-writing
+
+Reactive answers for if someone asks directly, not proactive framing: still honest, but pointed at
+what three.ws does well rather than dwelling on the fix.
+
+**"How did this ship broken in the first place?"**
+
+> We hold our own AR surfaces to the same bar as everything else we ship: caught this ourselves in
+> a routine device pass, not from a report, and had it fixed and tested on-device the same day.
+
+**"Does this mean AR Studio now places multiple objects in real tracked AR on iPhone?"**
+
+> Quick Look places one object at a time, that's how USDZ works, and each one lands with real
+> tracking and true scale. Full multi-model placement with tracking is the WebXR/Android path.
+
+**"Was any user-facing data affected?"**
+
+> No. This is a rendering/AR-launch improvement, not a data issue. Nothing about accounts, wallets,
+> or stored models was involved.
+
+---
+
+## Notes on framing
+
+- **Lead bullish. Never apologize.** No "we found a gap," no "silent fallback," no before/after
+ confession, in the posted copy. State what's true about the product now like it's the best AR
+ experience on the market, because the underlying facts back it up.
+- **$THREE mention is fine if it fits, not forced.** This is a product-quality post, not a coin
+ post; add a $THREE line only if a specific alternate calls for it, don't bolt one onto every
+ draft.
+- **Screenshots, if used, should show the model sitting convincingly in a real room**, the way
+ [3d-ar-studio-launch.md](#sec-522) already frames its media: a real floor in
+ frame is the whole point.
+- **Do not combine this with the AR Studio open-source package announcement**
+ ([3d-ar-studio-launch.md](#sec-522)). That post is about giving the surface away as
+ a library; this one is about how good AR feels on three.ws today. Mixing them muddies both.
+
+---
+
+<a id="sec-526"></a>
> **Source:** `docs/x-posts/event-x-posts.md` · [↑ table of contents](#table-of-contents)
@@ -121516,7 +122758,7 @@ Practical notes for reused footage:
---
-<a id="sec-520"></a>
+<a id="sec-527"></a>
> **Source:** `docs/x-posts/fomo-verified-x-post.md` · [↑ table of contents](#table-of-contents)
@@ -121610,7 +122852,7 @@ Shorter alternate:
---
-<a id="sec-521"></a>
+<a id="sec-528"></a>
> **Source:** `docs/x-posts/ibm-skillsbuild-x-post.md` · [↑ table of contents](#table-of-contents)
@@ -121818,7 +123060,7 @@ https://www.credly.com/badges/b7ea921a-ce3d-4f4d-bfac-38f95276d361/twitter via @
---
-<a id="sec-522"></a>
+<a id="sec-529"></a>
> **Source:** `docs/x-posts/mcp-registry-fleet-x-post.md` · [↑ table of contents](#table-of-contents)
@@ -121935,14 +123177,14 @@ Post 1 is the main post. Then:
---
-<a id="sec-523"></a>
+<a id="sec-530"></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-527); this file is what gets said, cut
+[metaplex-agent-mcp-x-post.md](#sec-534); 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
@@ -122042,7 +123284,7 @@ For a single generation with no editing. One breath, one idea.
---
-<a id="sec-524"></a>
+<a id="sec-531"></a>
> **Source:** `docs/x-posts/metaplex-agent-deployer-x-post.md` · [↑ table of contents](#table-of-contents)
@@ -122216,7 +123458,71 @@ Use this if you would rather not quote-tweet.
---
-<a id="sec-525"></a>
+## 8. The two-account split (use this pair)
+
+Same convention as the meetup and SkillsBuild launches: `@trythreews` posts the product version and
+`@nichxbt` quote-tweets it with the version only a person can say. Do not post them within a few
+minutes of each other, and do not put the first-person line on the brand account.
+
+**Link discipline for this launch:** the only deployer URL that resolves is the GitHub Pages one.
+`three.ws/deploy-onchain` is built but not deployed, so it 404s today. Do not put it in a post until
+production ships it.
+
+### From @trythreews (post this first)
+
+> We put 333 agents on-chain for people who had never held a wallet.
+>
+> Now the tool is public.
+>
+> Name an agent, click deploy, and it lands in the Metaplex Agent Registry on Solana with its own
+> wallet and a portable identity.
+>
+> nirholas.github.io/metaplex-agent-mcp
+
+Why this one: the 333 is proof the thing works before anyone clicks, and "now the tool is public"
+is the entire announcement in five words. The brand account is allowed to say "we put", which is
+what makes this version institutional rather than personal.
+
+### First reply from @trythreews (carries the developer links)
+
+> Agents can deploy themselves too, over MCP:
+>
+> npx -y @three-ws/metaplex-agent-mcp
+>
+> 9 tools, self-custodial, free on devnet.
+>
+> github.com/nirholas/metaplex-agent-mcp
+
+### Quote tweet from @nichxbt (post a few minutes later)
+
+> Those 333 went out through a script. Admin only. That always bothered me.
+>
+> This is the version where you don't need us.
+>
+> The part I like most: the wallet your agent gets has no private key anywhere. It is derived from
+> the asset itself, so there is nothing to leak.
+
+Why this one: it adds two things the brand account never said, which is the whole job of the second
+account. The first is an admission (the Genesis mints were gated, and that was a limitation), and
+the second is a technical detail the founder would notice and a marketer would not. No praise of
+our own product, no pretending to be a bystander.
+
+### Alternate quote tweet from @nichxbt (shorter, conviction-first)
+
+> Nobody's first wallet should be a 12-word phrase they have to protect forever.
+>
+> Make an agent, click deploy, and the crypto part happens behind you. That was always the point.
+
+### If you would rather reply than quote-tweet
+
+> Built this because the 333 needed me to run a script. Now it needs nobody.
+>
+> Your agent's wallet has no private key. It is derived from the asset, so there is nothing to
+> leak and nothing to back up.
+
+---
+
+<a id="sec-532"></a>
> **Source:** `docs/x-posts/metaplex-agent-mcp-launch.md` · [↑ table of contents](#table-of-contents)
@@ -122392,16 +123698,41 @@ outbound slot.
> deploy: the browser version builds the transaction locally, your wallet signs it, nothing
> touches a server.
+## 5. @nichxbt quote tweet (personal voice, quote-tweeting the @trythreews main post above)
+
+Same convention as the event campaign copy: the brand account posts the tight institutional
+version, the personal account quote-tweets with the human read, not a restatement of the facts.
+Post this a few minutes after the @trythreews post lands, not at the same time.
+
+> Every project that builds on this becomes a $THREE buyer, forever. Not just our own users.
+>
+> That's the whole thesis behind open-sourcing it instead of keeping it in-house.
+>
+> Go build something with it: github.com/nirholas/metaplex-agent-mcp
+
+**Why this one:** it says the plain version of the investment thesis in first person, which reads
+as conviction rather than marketing copy when it comes from a personal account. It doesn't repeat
+"agent wallet, EIP-8004 identity, x402" (already said in the post it's quoting) and it doesn't
+touch the buyback.enabled caveat since it isn't claiming buybacks are running, only that deploys
+fund them, which is already the safe, verified claim.
+
+**Alternate, shorter:**
+
+> Open-sourced the whole agent wallet + deploy stack today.
+>
+> Every team that plugs into it sends fees to $THREE buybacks. That's not a slogan, it's just how
+> the fee lane is wired.
+
---
-<a id="sec-526"></a>
+<a id="sec-533"></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-525). Text-to-video only, no dialogue, no
+[`metaplex-agent-mcp-launch.md`](#sec-532). 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.
@@ -122505,7 +123836,7 @@ to show something spreading to others, not just one agent getting a wallet.
---
-<a id="sec-527"></a>
+<a id="sec-534"></a>
> **Source:** `docs/x-posts/metaplex-agent-mcp-x-post.md` · [↑ table of contents](#table-of-contents)
@@ -122782,7 +124113,7 @@ keys, your limits.**
---
-<a id="sec-528"></a>
+<a id="sec-535"></a>
> **Source:** `docs/x-posts/news-archive-x-post.md` · [↑ table of contents](#table-of-contents)
@@ -122872,11 +124203,11 @@ If someone asks how it stays current: the archiver runs hourly against all 197 f
newest month is always live and the corpus grows every hour. If someone asks about publisher
rights: the reader shows a bounded excerpt plus our own summary and sends readers to the
publisher, and the cap plus any takedown is enforced server side across the reader, the RSS
-mirror, archive search, and the agent knowledge corpus. See [docs/news-rights.md](#sec-292).
+mirror, archive search, and the agent knowledge corpus. See [docs/news-rights.md](#sec-296).
---
-<a id="sec-529"></a>
+<a id="sec-536"></a>
> **Source:** `docs/x-posts/onchain-agent-wallets-x-post.md` · [↑ table of contents](#table-of-contents)
@@ -123062,7 +124393,7 @@ Post 1 is the main post above. Then:
---
-<a id="sec-530"></a>
+<a id="sec-537"></a>
> **Source:** `docs/x-posts/oracle-trading-mcp-x-post.md` · [↑ table of contents](#table-of-contents)
@@ -123073,7 +124404,7 @@ trading agents are published as Model Context Protocol servers in
[Anthropic's official MCP registry](https://registry.modelcontextprotocol.io/?q=io.github.nirholas),
so any AI assistant can use them directly.
-Build plan this announces: [`docs/oracle-trading-mcp-plan.md`](#sec-314).
+Build plan this announces: [`docs/oracle-trading-mcp-plan.md`](#sec-319).
**Do not post until:** `npm run smoke:mcp` passes against the live remotes, and both
`io.github.nirholas/threews-oracle` and `io.github.nirholas/threews-agent-trader` resolve in the
@@ -123203,7 +124534,7 @@ place to be wrong.
---
-<a id="sec-531"></a>
+<a id="sec-538"></a>
> **Source:** `docs/x-posts/pumpfun-article-x-post.md` · [↑ table of contents](#table-of-contents)
@@ -123320,7 +124651,7 @@ Pick one option. Do not post all four.
---
-<a id="sec-532"></a>
+<a id="sec-539"></a>
> **Source:** `docs/x-posts/sperax-staking-in-chat-x-post.md` · [↑ table of contents](#table-of-contents)
@@ -123426,14 +124757,14 @@ on the `/staking` page footer, so anyone who tries it gets exactly what the post
---
-<a id="sec-533"></a>
+<a id="sec-540"></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-534).
+[threews-avatar-video-script.md](#sec-541).
**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.
@@ -123488,7 +124819,102 @@ from an avatar company.
---
-<a id="sec-534"></a>
+## Post this: the curated pairing
+
+Two accounts, one launch. The brand account states the product; the founder account says the thing
+a brand account cannot say. Post the video natively on **@trythreews**, wait for it to settle
+(15 to 30 minutes is enough to see whether it moves), then quote it from **nichxbt**.
+
+Never post the same words twice across the two accounts. The quote exists to add a second angle,
+and a timeline that sees the same sentence twice scrolls past both.
+
+### 1. @trythreews, with the video attached natively
+
+*(179 characters with the URL counted)*
+
+> Give your AI a body.
+>
+> Type a prompt. Get a rigged 3D avatar that talks, moves, and holds its own wallet on Solana.
+>
+> Drop it on your own site in two lines.
+>
+> three.ws
+
+Native video, never a link to a video: X will not render a link preview and a video at once, and
+the video wins every time. "Two lines" is the honest count, a script tag and one element, so nobody
+who tries it feels sold to.
+
+**Alternate, if you want it tighter** *(138 characters)*
+
+> Give your AI a body.
+>
+> A prompt in. A rigged 3D avatar out, with its own wallet on Solana, embeddable on any page.
+>
+> three.ws
+
+**Alternate, if the video opens on the formless shot** *(191 characters)*
+
+> Your AI can write, reason and speak.
+>
+> It still has no body.
+>
+> three.ws gives it one: type a prompt, get a rigged 3D avatar that moves, talks, and holds its own
+> wallet on Solana.
+
+### 2. nichxbt, quoting the post above
+
+*(220 characters)*
+
+> Every AI product ships the same box with text in it.
+>
+> We spent a year on the part nobody wanted to do: giving the thing a body that renders in a
+> browser, animates, and owns a wallet.
+>
+> No plugin. No download. Just a page.
+
+First person and slightly weary, which is the register a founder account is actually read in. It
+names the work rather than the feature, and "no plugin, no download, just a page" is the line a
+developer repeats.
+
+**Alternate, builder-facing** *(212 characters)*
+
+> The avatar in this clip was generated from a text prompt, auto-rigged, and rendered in the
+> browser.
+>
+> No modeling software, no download, no app store.
+>
+> The pipeline is the product. The video just makes it obvious.
+
+**Alternate, if the video is doing the work on its own** *(58 characters)*
+
+> I got tired of AI being a text box.
+>
+> So it has a body now.
+
+Use this one only if the clip is already moving. It is a caption, not an argument, and it needs the
+video to have earned attention first.
+
+### 3. Reply under the brand post, from @trythreews
+
+Carries the part that does not fit the main post without spending its outbound link.
+
+*(120 characters)*
+
+> It holds its own wallet, so it can be paid directly and pay for what it uses. No account, no card,
+> nobody in the middle.
+
+### Rules for this pairing
+
+- **No price, no supply, no buyback claim.** The fee funding buybacks is true; buybacks executing
+ right now is not, and that is exactly the kind of line that gets screenshotted.
+- **No ticker in the brand post.** This one sells the product to people who do not hold anything.
+ The $THREE angle has its own post; mixing them halves both.
+- **Reply to the first real question within the hour.** The reply is what the algorithm reads as a
+ conversation, and it is worth more than a third alternate post.
+
+---
+
+<a id="sec-541"></a>
> **Source:** `docs/x-posts/threews-avatar-video-script.md` · [↑ table of contents](#table-of-contents)
@@ -123496,9 +124922,9 @@ from an avatar company.
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-533), the spoken lines live in
-[metaplex-agent-deployer-video-script.md](#sec-523), and the
-deployer-specific shot list lives in [metaplex-agent-mcp-x-post.md](#sec-527).
+[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).
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
@@ -123641,7 +125067,7 @@ Keep the pause after "It has no body." That silence is the whole premise.
---
-<a id="sec-535"></a>
+<a id="sec-542"></a>
> **Source:** `docs/x-posts/x-meetup-posts.md` · [↑ table of contents](#table-of-contents)
@@ -123698,13 +125124,13 @@ https://community.ibm.com/community/user/discussion/community-meetup-inside-thre
---
-<a id="sec-536"></a>
+<a id="sec-543"></a>
> **Source:** `docs/x402-buyer.md` · [↑ table of contents](#table-of-contents)
# x402 Buyer Client
-To consume a paid [x402 endpoint](#sec-539) — ours or anyone's — a
+To consume a paid [x402 endpoint](#sec-546) — 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
@@ -123771,7 +125197,7 @@ it fails — caps hold even across concurrent calls. The store is Redis-backed w
available. If a call would exceed any window, `buyerFetch` returns
`{ ok: false, abort: true, reason }` **without paying**. The platform-wide ceiling
defaults live in env (`X402_MAX_PER_CALL_ATOMIC`, `X402_MAX_PER_HOUR_ATOMIC`,
-`X402_MAX_PER_DAY_ATOMIC`; see [Configuration](#sec-153)).
+`X402_MAX_PER_DAY_ATOMIC`; see [Configuration](#sec-154)).
## Axios variant
@@ -123794,13 +125220,13 @@ set) back into the payment so attribution survives the round trip.
## Related
-- [x402 protocol](#sec-544) — the underlying challenge/settle mechanics.
-- [x402 paid endpoints](#sec-539) — what you can buy from us.
+- [x402 protocol](#sec-551) — the underlying challenge/settle mechanics.
+- [x402 paid endpoints](#sec-546) — what you can buy from us.
- [Autonomous x402 loop](#sec-105) — uses this client on a schedule.
---
-<a id="sec-537"></a>
+<a id="sec-544"></a>
> **Source:** `docs/x402-dev-tools.md` · [↑ table of contents](#table-of-contents)
@@ -124012,13 +125438,13 @@ implementation against a live server.
---
-<a id="sec-538"></a>
+<a id="sec-545"></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-544). Building them is
+three.ws sells 90+ pay-per-call services over [x402](#sec-551). 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,
@@ -124233,24 +125659,24 @@ script. Everything else above updates itself.
## Related
-- [x402 overview](#sec-544) · [Paid endpoints reference](#sec-539) ·
- [Autonomous loop](#sec-105) · [Buyer client](#sec-536)
+- [x402 overview](#sec-551) · [Paid endpoints reference](#sec-546) ·
+ [Autonomous loop](#sec-105) · [Buyer client](#sec-543)
---
-<a id="sec-539"></a>
+<a id="sec-546"></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-544): the caller hits the endpoint, receives a `402 Payment Required`
+[x402](#sec-551): 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-536). For the loop
+To call these as a buyer, see [x402 buyer client](#sec-543). 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
@@ -124282,7 +125708,7 @@ and, when configured, **USDC on Base** (EVM) and a **BSC leg** (contract-mediate
`direct` scheme, advertised only when `X402_PAY_TO_BSC` is set). On the Solana
rail, `X402_ACCEPT_THREE_SOLANA` optionally advertises **$THREE** alongside USDC
as a second accept entry on the same challenge. The relevant config (see
-[Configuration](#sec-153)):
+[Configuration](#sec-154)):
| Key | Meaning |
| ---------------------------------------------------- | ------------------------------------ |
@@ -124364,7 +125790,7 @@ deliberately not advertised in the 402 challenge or the discovery catalog; it
recirculates funds back to `X402_PAY_TO_SOLANA` to keep the closed loop balanced
([ring-settle.js:18](../api/x402/ring-settle.js#L18)). The full wallet-by-wallet
picture — every receiver, tip, split, treasury, and fee rate — is in the
-[money map](#sec-287).
+[money map](#sec-291).
## Intel & oracle endpoints
@@ -124434,7 +125860,7 @@ datapoints at **$0.0005** USDC each by default, overridable per family with
| Endpoint | Default | Returns |
| ----------------------------------- | --------- | ------------------------------------------ |
-| `/api/x402/agent-reputation` | $0.01 | Cross-chain 0–100 trust score for any wallet/mint/agent id ([trust primitives](#sec-417)). |
+| `/api/x402/agent-reputation` | $0.01 | Cross-chain 0–100 trust score for any wallet/mint/agent id ([trust primitives](#sec-423)). |
| `/api/x402/agent-bouncer` | $0.01 | Access-gate decision for an agent/wallet. |
| `/api/x402/onchain-identity-verify` | $0.005 | Verifies an on-chain identity claim. |
| `/api/x402/skill-marketplace` | $0.001 | Skill listings + pricing. |
@@ -124446,7 +125872,7 @@ datapoints at **$0.0005** USDC each by default, overridable per family with
| Endpoint | Default | Returns |
| ----------------------------------------------------------- | --------- | -------------------------------------------------------------------------------------------- |
| `/api/x402/forge` | tiered | Text/image → 3D model (price by tier; GPU-bound). Every settled generation also lands in the public community gallery (`forge_creations`) stamped with the payer, settle signature, and price; the gallery shows a Solscan-linked "x402" provenance badge. See [Avatar pipeline](#sec-113). |
-| `/api/x402/embody` | $1.00 | **Embodiment.** One call, an agent buys itself a body: prompt or image in → rigged, voiced 3D avatar out, plus a durable persona id and a one-tag `<iframe>` embed for any website. Settles on delivery — a failed generation never charges. See [Embodiment](#sec-187). |
+| `/api/x402/embody` | $1.00 | **Embodiment.** One call, an agent buys itself a body: prompt or image in → rigged, voiced 3D avatar out, plus a durable persona id and a one-tag `<iframe>` embed for any website. Settles on delivery — a failed generation never charges. See [Embodiment](#sec-189). |
| `/api/x402/pipeline` | per stage | **One call, full 3D asset pipeline** — text or GLB in, rigged/optimized game-ready GLB out. Ordered chain of `generate → rig → remesh → gameready → stylize`; the 402 quote is the exact sum of the requested stages. Poll free at `/api/forge?job=<id>` for per-stage progress. See [3D pipeline](#sec-003). |
| `/api/x402/pipeline-rig` | $0.05 | **Pipeline — Rig.** Static GLB in → animation-ready rigged GLB out (skeleton + skin weights). One paid call, durable URL. See [3D pipeline](#sec-003). |
| `/api/x402/pipeline-remesh` | $0.03 | **Pipeline — Remesh.** Retopologize a GLB (triangle/quad/lowpoly, repair, decimate to a face budget) with texture re-baked. GLB in → GLB out. See [3D pipeline](#sec-003). |
@@ -124462,8 +125888,8 @@ datapoints at **$0.0005** USDC each by default, overridable per family with
| Endpoint | Default | Returns |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------- | --------------------------------------------------------------------------------------------------------------------------- |
-| [`/api/x402/pump-launch`](#sec-339) | $5.00 | **Pump Launcher** — deploy a brand-new pump.fun token in one paid call. No SOL, no wallet, no account: the server fronts the deploy cost and signs the create tx; you pay USDC. Optional vanity mint. Full flow + funnel in [pump-launcher.md](#sec-339). |
-| [`/api/x402/vanity`](#sec-502) | $0.01–$0.50 (≤3) · $2.50–$10 (4–5, inventory-only) | **Vanity Grinder** — get a brand-new Solana address that starts with your ticker/prefix and/or ends with a suffix, for a branded token mint or agent/treasury wallet. Checks the pre-ground warehouse first for **instant delivery** (`source: "inventory"`); falls back to a live grind (`source: "ground"`) up to 3 chars. Keypair or importable BIP-39 mnemonic; nothing stored; optional `sealTo` ECIES. Full doc: [vanity.md](#sec-502). |
+| [`/api/x402/pump-launch`](#sec-344) | $5.00 | **Pump Launcher** — deploy a brand-new pump.fun token in one paid call. No SOL, no wallet, no account: the server fronts the deploy cost and signs the create tx; you pay USDC. Optional vanity mint. Full flow + funnel in [pump-launcher.md](#sec-344). |
+| [`/api/x402/vanity`](#sec-508) | $0.01–$0.50 (≤3) · $2.50–$10 (4–5, inventory-only) | **Vanity Grinder** — get a brand-new Solana address that starts with your ticker/prefix and/or ends with a suffix, for a branded token mint or agent/treasury wallet. Checks the pre-ground warehouse first for **instant delivery** (`source: "inventory"`); falls back to a live grind (`source: "ground"`) up to 3 chars. Keypair or importable BIP-39 mnemonic; nothing stored; optional `sealTo` ECIES. Full doc: [vanity.md](#sec-508). |
| [`/api/x402/vanity-verifiable`](vanity.md#tier-2--provably-fair-grinder) | $0.02–$0.40 | **Provably-fair grinder** — same grind with a signed commit–reveal receipt proving the key was ground fresh and never kept. Spec: [PROTOCOL-vanity.md](#sec-005). |
| [`/api/x402/vanity-premium`](vanity.md#tier-3--premium-inventory) | $1–$50 by rarity | **Premium inventory** — buy a pre-ground 4–5+ char brandable address from stock. GET lists available patterns + prices (free); `?address=…` buys via x402 and delivers the key **once** (ciphertext destroyed on delivery). Browsable at `/vanity/premium`. |
| `/api/x402/pay-by-name` | $0.001 | Resolve and pay a `@username` / `.sol` name / raw address (see [Agent wallets](#sec-072)); the paid resolve toll is $0.001, the transfer amount itself is buyer-specified. A name that resolves to nothing returns `404 not_found` and the payment is left unsettled, so an unresolvable name is free. |
@@ -124502,7 +125928,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-540)), 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-547)), 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. |
@@ -124512,10 +125938,10 @@ 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-537). |
-| `/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-537). |
-| `/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-537). |
-| `/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-253). |
+| `/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/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
@@ -124526,22 +125952,22 @@ input and do not promote any specific token.
## Related
-- [Pump Launcher](#sec-339) — the full launch flow, inputs/outputs, and the free `symbol` → launch → `launches` funnel.
-- [x402 protocol](#sec-544) — the challenge/settle mechanics.
-- [x402 buyer client](#sec-536) — how to pay these endpoints in code.
-- [x402 revenue & receipts](#sec-540) — where settled payments are recorded and how to read endpoint revenue.
+- [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.
- [Autonomous x402 loop](#sec-105) — the scheduled buyer that drives volume through these endpoints.
-- [MCP tools](#sec-275) — the same capabilities exposed as paid MCP tools.
+- [MCP tools](#sec-279) — the same capabilities exposed as paid MCP tools.
---
-<a id="sec-540"></a>
+<a id="sec-547"></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-539), the
+Every time someone pays one of three.ws's [paid endpoints](#sec-546), 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.
@@ -124562,9 +125988,9 @@ tables. They never overlap, and mixing them up will double-count your numbers.
| Direction | Meaning | Table | Surfaced by |
| -------------- | ------------------------------------------------------------------------ | ---------------------- | ------------------------------------------------ |
| **Revenue IN** | Money paid **to** our endpoints for using them | `x402_audit_log` | `/api/x402/analytics?report=revenue` (this page) |
-| **Spend OUT** | Money an agent's wallet **paid out** (tips, trades, agent-to-agent x402) | `agent_custody_events` | The [Money Pulse](#sec-285) at `/api/pulse` |
+| **Spend OUT** | Money an agent's wallet **paid out** (tips, trades, agent-to-agent x402) | `agent_custody_events` | The [Money Pulse](#sec-289) at `/api/pulse` |
-The [Money Pulse](#sec-285) shows the agent economy — one agent paying
+The [Money Pulse](#sec-289) shows the agent economy — one agent paying
another, tips, launches. **This page is the other side of the ledger:** the
platform's own endpoint revenue. A call to `/api/x402/token-intel` writes a
**revenue** row in `x402_audit_log`; it is not an `agent_custody_events` spend and
@@ -124729,7 +126155,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-539) ($0.005 default).
+pre-aggregated. It is itself a [paid endpoint](#sec-546) ($0.005 default).
It is a `POST` endpoint: pass `report` and `period` in the JSON body:
```bash
@@ -124805,7 +126231,7 @@ CREATE TABLE x402_receipts (
```
A buyer reads **their own** receipts at
-[`/api/x402/my-receipts`](#sec-539) — that endpoint is free but gated by
+[`/api/x402/my-receipts`](#sec-546) — that endpoint is free but gated by
a wallet signature (SIWX), so a buyer proves ownership of the `payer` address
rather than paying again.
@@ -125014,15 +126440,15 @@ settled activity (include it), and label it as such.
## Related
-- [x402 paid endpoints](#sec-539) — the catalog of what charges and how much.
-- [x402 protocol](#sec-544) — the challenge / verify / settle mechanics.
-- [x402 buyer client](#sec-536) — how to settle a 402 challenge in code.
+- [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.
- [Autonomous x402 loop](#sec-105) — the scheduled buyer that drives volume, including the Volume Bootstrap Loop and the reconciliation job.
-- [Money feed](#sec-285) — the agent-spend side of the ledger (the Money Pulse), distinct from endpoint revenue.
+- [Money feed](#sec-289) — the agent-spend side of the ledger (the Money Pulse), distinct from endpoint revenue.
---
-<a id="sec-541"></a>
+<a id="sec-548"></a>
> **Source:** `docs/x402-ring-economy.md` · [↑ table of contents](#table-of-contents)
@@ -126117,7 +127543,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-540) — revenue surface docs
+- [docs/x402-revenue.md](#sec-547) — 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
@@ -126125,7 +127551,7 @@ activation runbook above is the fix.
---
-<a id="sec-542"></a>
+<a id="sec-549"></a>
> **Source:** `docs/x402-solana-july-roundup-response.md` · [↑ table of contents](#table-of-contents)
@@ -126143,7 +127569,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-519): `@trythreews` posts the institutional version, `@nichxbt`
+[event-x-posts.md](#sec-526): `@trythreews` posts the institutional version, `@nichxbt`
posts the human one. Do not post both within a few minutes of each other.
---
@@ -126184,7 +127610,7 @@ the specific claim the roundup credited us for. Second choice: the AR drop-in on
---
-<a id="sec-543"></a>
+<a id="sec-550"></a>
> **Source:** `docs/x402-studio.md` · [↑ table of contents](#table-of-contents)
@@ -126194,11 +127620,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-544) 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-551) 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-536) and the [paid endpoint catalog](#sec-539).
+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).
## How it works
@@ -126284,16 +127710,16 @@ const { tx_base64, blockhash } = await res.json();
## Related
-- [x402: paid agent skills](#sec-544): the payment protocol Studio sits on top of
-- [x402 revenue and receipts](#sec-540): where settled payments are recorded
-- [x402 paid endpoints](#sec-539): the platform's own catalog of paid endpoints
-- [x402 buyer client](#sec-536): the caller side of a 402 challenge
-- [x402 developer tools](#sec-537) and [x402 distribution](#sec-538)
+- [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)
- Pages: [/x402/studio](https://three.ws/x402/studio) · [/x402](https://three.ws/x402)
---
-<a id="sec-544"></a>
+<a id="sec-551"></a>
> **Source:** `docs/x402.md` · [↑ table of contents](#table-of-contents)
@@ -126307,7 +127733,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-539).
+[x402 paid endpoints](#sec-546).
**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.
@@ -126463,20 +127889,20 @@ Each package has its own repository with a full README, API reference, and examp
## Tutorials
-- [Pay for an x402 service](#sec-457) — settle a paid request end to end with `@three-ws/x402-fetch`.
-- [Build a paid x402 endpoint](#sec-456) — stand up a seller endpoint with `@three-ws/x402-server`.
+- [Pay for an x402 service](#sec-463) — settle a paid request end to end with `@three-ws/x402-fetch`.
+- [Build a paid x402 endpoint](#sec-462) — stand up a seller endpoint with `@three-ws/x402-server`.
## Related
-- [x402 paid endpoints](#sec-539) — the catalog of the platform's own paid endpoints.
-- [x402 revenue & receipts](#sec-540) — where settled payments are recorded and how to read endpoint revenue.
-- [x402 buyer client](#sec-536) — how to settle a 402 challenge in code.
-- [x402 bazaar over MCP](#sec-276) — discover and pay endpoints through the MCP bazaar.
+- [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 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-545"></a>
+<a id="sec-552"></a>
> **Source:** `docs/zauth/database.md` · [↑ table of contents](#table-of-contents)
@@ -126622,7 +128048,7 @@ Use this endpoint to browse all known x402 endpoints before your agents commit t
---
-<a id="sec-546"></a>
+<a id="sec-553"></a>
> **Source:** `docs/zauth/index.md` · [↑ table of contents](#table-of-contents)
@@ -126642,11 +128068,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-549)### [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-548)### [DatabaseLive registry of x402 endpoints. AI agents continuously test and verify endpoints, tracking success rates, pricing, and response data.Database](#sec-545)### [Provider HubManage your x402 endpoints. Monitor health, track agent interactions, configure refunds, and verify your services through our SDK.Provider Hub](#sec-547)
+### [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)
---
-<a id="sec-547"></a>
+<a id="sec-554"></a>
> **Source:** `docs/zauth/provider-hub.md` · [↑ table of contents](#table-of-contents)
@@ -126748,7 +128174,7 @@ Supply your EVM or Solana private keys to enable automatic refunds when your end
---
-<a id="sec-548"></a>
+<a id="sec-555"></a>
> **Source:** `docs/zauth/reposcan.md` · [↑ table of contents](#table-of-contents)
@@ -127074,7 +128500,7 @@ TypeScript -@x402/fetch
---
-<a id="sec-549"></a>
+<a id="sec-556"></a>
> **Source:** `docs/zauth/vector.md` · [↑ table of contents](#table-of-contents)
diff --git a/docs/contributing.md b/docs/contributing.md
index 3c6690f3e..75e0b8491 100644
--- a/docs/contributing.md
+++ b/docs/contributing.md
@@ -321,7 +321,7 @@ Core team response times: typically 2-3 business days on GitHub. If a PR has bee
## License
-By contributing, you agree that your contributions are provided under the terms of the repository's [LICENSE](../LICENSE) (proprietary, all rights reserved). Read it before submitting substantial work.
+By contributing, you agree that your contributions are licensed under the [Apache License 2.0](../LICENSE), the same license the repository ships under.
---
diff --git a/docs/ibm-x402-mcp.md b/docs/ibm-x402-mcp.md
index db20148fc..991a769b8 100644
--- a/docs/ibm-x402-mcp.md
+++ b/docs/ibm-x402-mcp.md
@@ -345,7 +345,7 @@ knowing the server up front.
## Affiliation
three.ws is an **IBM Business Partner**. This npm package is an independent,
-proprietary project built by three.ws that integrates IBM Granite via
+project built by three.ws that integrates IBM Granite via
watsonx.ai — IBM Cloud Partner Center requires third-party MCP listings to state
this, so to be precise: the package itself is **not an IBM product** and is not
operated by IBM. Granite, watsonx, and watsonx.ai are trademarks of IBM.
diff --git a/docs/introduction.md b/docs/introduction.md
index fac92dcd9..213c56a0b 100644
--- a/docs/introduction.md
+++ b/docs/introduction.md
@@ -8,7 +8,7 @@ The result is an agent that doesn't just respond in a chat box. It occupies a th
**Key facts:**
-- **License:** proprietary, all rights reserved (see [LICENSE](https://github.com/nirholas/three.ws/blob/main/LICENSE))
+- **License:** open source, [Apache 2.0](https://github.com/nirholas/three.ws/blob/main/LICENSE)
- **Hosted platform:** [https://three.ws](https://three.ws)
- **CDN bundle:** `https://three.ws/agent-3d/latest/agent-3d.js` (also pinnable to a version, e.g. `/agent-3d/1.5.2/agent-3d.js`)
- **npm packages:** [`@three-ws/sdk`](https://www.npmjs.com/package/@three-ws/sdk), [`@three-ws/agent-ui`](https://www.npmjs.com/package/@three-ws/agent-ui), [`@three-ws/avatar`](https://www.npmjs.com/package/@three-ws/avatar), [`@three-ws/solana-agent`](https://www.npmjs.com/package/@three-ws/solana-agent), [`@three-ws/mcp-server`](https://www.npmjs.com/package/@three-ws/mcp-server)
@@ -47,7 +47,7 @@ For developers who don't need any of this, on-chain identity is entirely optiona
### Open
-The source is readable and the formats are open, but the code is proprietary: see [LICENSE](https://github.com/nirholas/three.ws/blob/main/LICENSE) for what is permitted, and ask before self-hosting or redistributing. The manifest format, embed protocol, and agent spec are all documented in the `/specs` directory of the repository, and building against those specs needs no permission.
+The code is open source under the [Apache License 2.0](https://github.com/nirholas/three.ws/blob/main/LICENSE): use it, modify it, self-host it, redistribute it, and build commercial products on it, including closed-source ones, as long as you keep the license and attribution notices and state what you changed. The manifest format, embed protocol, and agent spec are all documented in the `/specs` directory of the repository.
---
diff --git a/docs/ops/examples-repo-export.md b/docs/ops/examples-repo-export.md
index e785eb75c..012cdfd38 100644
--- a/docs/ops/examples-repo-export.md
+++ b/docs/ops/examples-repo-export.md
@@ -105,10 +105,10 @@ rather than let that happen.
## License note before first publish
-The export carries the monorepo root `LICENSE` verbatim, which is currently
-"All rights reserved". A public examples repo usually ships a permissive license
-(MIT/Apache-2.0). Confirm or replace `dist/examples-repo/LICENSE` before the
-first public push. This is an owner decision; the export does not choose one.
+The export carries the monorepo root `LICENSE` verbatim, which is the Apache
+License 2.0. That is already the permissive license a public examples repo
+wants, so no substitution is needed. Ship `dist/examples-repo/NOTICE` alongside
+it, since Apache-2.0 section 4(d) requires the notice to travel with the code.
## Owner publish steps (run by hand; not automated here)
diff --git a/docs/sdk.md b/docs/sdk.md
index 05caa932d..3ebea7e21 100644
--- a/docs/sdk.md
+++ b/docs/sdk.md
@@ -7,7 +7,7 @@ This page is for developers who want to build with three.ws code in their own pr
| **Web component bundle** | `agent-3d.js` (CDN or `TARGET=lib` build) | Drop-in `<agent-3d>` element + programmatic viewer/runtime APIs |
| **AgentKit SDK** | `@three-ws/sdk` | Ship an ERC-8004 agent: chat panel, on-chain registration, `.well-known` manifests |
-Both are proprietary (see [LICENSE](https://github.com/nirholas/three.ws/blob/main/LICENSE)) and free to install and use from npm. Neither requires the other.
+Both are open source under the [Apache License 2.0](https://github.com/nirholas/three.ws/blob/main/LICENSE) and free to install and use from npm. Neither requires the other.
> **Building payments?** The x402 buyer, seller, browser-modal, and MCP packages are
> published to npm as standalone libraries — `@three-ws/x402-fetch`,
diff --git a/docs/security.md b/docs/security.md
index 5b1e5c687..bf793e428 100644
--- a/docs/security.md
+++ b/docs/security.md
@@ -10,7 +10,7 @@ This page explains how three.ws keeps your data, wallet, and agents safe, and wh
**Least privilege** — agents access only what is explicitly declared and granted. Skills declare permission requirements; users must grant them. API keys carry only the scopes you assign. OAuth access tokens are short-lived (1 hour) and audience-bound.
-**Transparency**: the codebase is publicly readable on GitHub (source-available under the repository's proprietary LICENSE). The on-chain identity, reputation, and validation registries are auditable on Base. Badge verification derives from on-chain attestations, not the badge UI itself.
+**Transparency**: the codebase is open source on GitHub under the Apache License 2.0. The on-chain identity, reputation, and validation registries are auditable on Base. Badge verification derives from on-chain attestations, not the badge UI itself.
**Standard web security** — HTTPS-only for all authenticated operations. CSP, CORS, and `__Host-` cookie prefix enforced throughout.
diff --git a/docs/tutorials/self-host-agent-backend.md b/docs/tutorials/self-host-agent-backend.md
index a05c5c07b..2f1867343 100644
--- a/docs/tutorials/self-host-agent-backend.md
+++ b/docs/tutorials/self-host-agent-backend.md
@@ -521,7 +521,7 @@ A few things you should know going in:
**Some upstream features require platform-only secrets.** The hosted three.ws has access to API keys and wallets that aren't published. If you fork, those features (e.g., the platform-managed agent treasury) won't work as-is — you'll either disable them or wire your own equivalents. The code paths that depend on platform secrets are clearly conditional on env-var presence; if your env var is empty, the feature is hidden in the UI.
-**Check the license before you deploy anything.** The repo's `LICENSE` is proprietary, not open source: "All rights reserved", with use, copying, modification, and distribution requiring the copyright owner's express written permission. Reading the source is not the same as being licensed to run a fork of it, so get that permission in writing before you stand up a deployment. Everything below assumes you have it.
+**You are licensed to do this.** The repo ships under the Apache License 2.0, so self-hosting, forking, and running a modified deployment are all permitted. Keep the `LICENSE` and `NOTICE` files with any copy you distribute, and state what you changed. No permission request needed.
**You become responsible for security patches.** Vercel handles its own infrastructure. You handle the application code. Subscribe to GitHub Dependabot alerts on your fork, and feed fixes back upstream when they aren't specific to your deployment.