Open-source platform for 3D AI agents. Turn text or a photo into a rigged, animated GLB avatar, give it an LLM brain, memory and a wallet, and embed it anywhere with one web component. Remote MCP server, x402 payments, Three.js, browser-native.
JavaScript 3d-generationai-agentsanimationavatardigital-humangenerative-aiglbgltfimage-to-3dllmmcpmcp-servermodel-context-protocolsolanatext-to-3dthreejsweb-componentswebglwebxrx402
docs(x-posts): reframe the AR fix as a shipped capability and drop the duplicate index row
nirholas366288b4fc58
diff --git a/docs/x-posts/README.md b/docs/x-posts/README.mdindex 3def4d917..71b5703bc 100644--- a/docs/x-posts/README.md+++ b/docs/x-posts/README.md@@ -29,7 +29,6 @@ explicit approval). Each file states what it's for and what has already been ver| [`threews-avatar-launch.md`](threews-avatar-launch.md) | The three.ws avatar pipeline launch copy || [`oracle-trading-mcp-x-post.md`](oracle-trading-mcp-x-post.md) | The oracle trading MCP server launch || [`sperax-staking-in-chat-x-post.md`](sperax-staking-in-chat-x-post.md) | 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 |-| [`ar-quick-look-fix-x-post.md`](ar-quick-look-fix-x-post.md) | A bug fix, not a feature: `three.ws/ar` and `three.ws/ar/studio` now open real AR on iPhone the way `/avatars/:id/ar` already did || [`news-archive-x-post.md`](news-archive-x-post.md) | The news archive || [`pumpfun-article-x-post.md`](pumpfun-article-x-post.md) | The pump.fun article |diff --git a/docs/x-posts/ar-quick-look-fix-x-post.md b/docs/x-posts/ar-quick-look-fix-x-post.mdindex d8a7c0c78..09b472e64 100644--- a/docs/x-posts/ar-quick-look-fix-x-post.md+++ b/docs/x-posts/ar-quick-look-fix-x-post.md@@ -5,10 +5,11 @@ Announcement copy for a bug fix, not a new feature: `three.ws/ar` (AR Forge) anddid. Related file: [threews-avatar-launch.md](./threews-avatar-launch.md) sells the avatar-has-a-bodystory; 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 claimed to support Quick Look on-iPhone. Only one of them actually did. The other two silently degraded, in two different ways, and-nobody who wasn't holding an iPhone would have noticed. That gap is now closed. No roadmap talk, no-"coming soon."+**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 thegate below):**@@ -49,76 +50,100 @@ shipping to production needs the owner's go-ahead. Do not schedule or post any d`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.-**Things to NOT claim:**+**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.-1. **Do not say "new AR feature."** Nothing new was added to what AR Forge or AR Studio could already- do on Android or in the browser. The whole story is that iPhone now gets what was always promised.-2. **Do not name the old bug's exact symptom as if it were widely reported.** Frame it as "we found- this ourselves and fixed it," not "users complained." Nobody publicly complained; it was caught in- review.-3. **Do not claim AR Studio's iPhone experience places multiple objects with real tracking.** Quick+**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.** QuickLook places one object at a time by design (a USDZ is a single scene). Multi-object placement withreal tracking is still Android/WebXR only; the per-model "Place in your space" button on iOS iscorrect 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)+## 1. Main post (recommended), from @trythreews-258 characters with X's 23-character URL count.+216 characters with X's 23-character URL count.-> We shipped three AR surfaces. Only one of them actually opened AR on an iPhone.->-> The other two quietly fell back to a flat 3D view or a fake camera overlay. Nobody would've-> noticed unless they were holding an iPhone.+> 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.>-> Fixed. All three now use real Quick Look.+> Forge a model. Place it in your room. Watch it look real.>> three.ws/ar-Why this one: the honesty is the hook. Admitting a real gap and naming the fix precisely reads as-credible in a way "AR now works!" never does, and it invites the reply "wait, which two."+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.-## 2. Alternate: the technical explainer+### From @nichxbt (the human one, quote-tweeting the @trythreews post above)-269 characters.+Same two-account split as [event-x-posts.md](./event-x-posts.md): `@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.-> Apple Quick Look needs a real USDZ file. `<model-viewer>` does not generate one from a GLB on its-> own, no matter what the docs imply.->-> Two of our AR pages never set it. iPhone silently got a downgrade nobody could see from the code.->-> Fixed, verified on-device.+> 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 (`ios-src`, no auto-conversion) is-more convincing than any adjective. It also preempts "how do you know it's fixed."+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-264 characters.+221 characters.> AR that doesn't know where your floor is isn't AR. It's a video filter.>-> Our multi-model AR studio faked it on iPhone with a camera overlay: no real scale, nothing to rest-> the model on.->-> Now it hands off to Apple's own Quick Look. Real tracking, real floor.+> 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, which travels further-than a bug-fix framing on its own.+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-Under 200 characters. Good as a reply-chain opener or a standalone if the thread below feels heavy.+153 characters. Good as a reply-chain opener or a standalone if the thread below feels heavy.-> Fixed: `three.ws/ar` and `three.ws/ar/studio` now open real Apple Quick Look on iPhone, the same-> way our avatar pages always have.->-> No more silent fallback to a flat 3D view.+> 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@@ -130,36 +155,26 @@ Post 1 is the main post above. Then:**2/**-> Quick Look needs a USDZ file, not a GLB. `<model-viewer>`'s AR attribute offers Quick Look as a-> mode, but it will not convert the model for you: you have to hand it a real USDZ as `ios-src`, or-> the button quietly does nothing useful.+> 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/**-> Our avatar AR page (`/avatars/:id/ar`) always did this: fetch the GLB, convert it to USDZ in the-> browser with three.js's own exporter, hand it to Quick Look. That page was always correct.->-> AR Forge and AR Studio were not built the same way.+> 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 Forge fell back silently to the plain interactive 3D viewer on iPhone. No error, no warning: the-> button just stopped being an AR button.->-> AR Studio went further: it faked AR with your camera feed and the phone's gyroscope. The model-> floats. Nothing anchors it to your floor. It looks like AR in a screenshot and nothing like it in-> your hand.+> 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/**-> Both are fixed the same way: a shared page now runs the exact USDZ conversion the avatar page-> always used, and both surfaces hand off to it on iPhone.->-> Android's Scene Viewer redirect was already correct the whole time and didn't need touching.+> 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 forge a scene at three.ws/ar/studio and tap the AR button.+> Try it: three.ws/ar, or build a full scene at three.ws/ar/studio.>> three.ws@@ -167,34 +182,37 @@ Post 1 is the main post above. Then:## 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?"**-> `<model-viewer>`'s AR attributes make Quick Look look wired up even when it isn't: the button-> renders, the attribute is set, and the only visible symptom is that tapping it on an iPhone does-> nothing useful. It doesn't throw an error. Caught in review, not from a report.+> 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?"**-> No, and we're not claiming that. Quick Look places one object at a time; that's how USDZ works.-> What's fixed is that placing one is now real device AR instead of a camera overlay. Multi-object-> placement with true tracking stays an Android/WebXR thing for now.+> 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 bug, not a data issue. Nothing about accounts, wallets, or stored-> models was involved.+> 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 with the honesty, not the fix.** "We found a real gap and closed it" earns more trust than- "new AR upgrade," and it's the more accurate description of what happened.-- **Do not mention $THREE.** This is a reliability fix, not a growth feature; forcing a coin mention- onto it would read as opportunistic.-- **Screenshots, if used, should be before/after on the same physical spot**, the way- [3d-ar-studio-launch.md](./3d-ar-studio-launch.md) already frames its media: a real floor in frame- is the whole point, so a screenshot without one undercuts the post.+- **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](./3d-ar-studio-launch.md) 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](./3d-ar-studio-launch.md)). That post is about giving the surface away as- a library; this one is about a bug on the site everyone already uses. Mixing them muddies both.+ a library; this one is about how good AR feels on three.ws today. Mixing them muddies both.diff --git a/docs/x-posts/metaplex-agent-deployer-x-post.md b/docs/x-posts/metaplex-agent-deployer-x-post.mdindex 9906e8134..59cfffcd9 100644--- a/docs/x-posts/metaplex-agent-deployer-x-post.md+++ b/docs/x-posts/metaplex-agent-deployer-x-post.md@@ -165,3 +165,67 @@ Use this if you would rather not quote-tweet.> MCP registry: io.github.nirholas/metaplex-agent- **Do not** open with "Introducing" or "excited to announce". Both main posts start with the claimitself, which is what gets reposted.++---++## 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.diff --git a/docs/x-posts/metaplex-agent-mcp-launch.md b/docs/x-posts/metaplex-agent-mcp-launch.mdindex ea02f5cc3..81c166b11 100644--- a/docs/x-posts/metaplex-agent-mcp-launch.md+++ b/docs/x-posts/metaplex-agent-mcp-launch.md@@ -169,3 +169,28 @@ outbound slot.> enforced by the Solana token program itself, not a raw key. And if you just want to see the> 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.diff --git a/docs/x-posts/threews-avatar-launch.md b/docs/x-posts/threews-avatar-launch.mdindex 0157053da..804badf71 100644--- a/docs/x-posts/threews-avatar-launch.md+++ b/docs/x-posts/threews-avatar-launch.md@@ -53,3 +53,98 @@ from an avatar company.> The avatar in the video was generated from a text prompt on three.ws, rigged automatically, and> rendered in the browser. No modeling, no rigging software, no download.++---++## 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.