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.
X mention bot: "make me an avatar"
When someone mentions the account with "make me an avatar", the bot turns their own X profile picture into a rigged 3D avatar and replies with a rendered image, the creation link and a link that opens the avatar in the pose studio. This is the avatar intent of the X mention bot. On the platform account it runs in dry run only: each reply is recorded on the mention's x_mention_events row and nothing is posted to X until the account goes live. An agent with its own X account answers in its persona and goes live only when its policy has dry run off and the X bot is live.
Whose picture
Only the author of the mention. The picture comes from the mention's own author object (the user expansion the reader attaches to every post), never from the text. A mention that names another account ("make me an avatar using @someone profile picture") parses to the same intent with no handle in its arguments, so there is no path by which another account's picture can be fetched. The handler also requires the author object to be the person who asked, and records not_own_image as a skip otherwise.
What happens to it
- A default profile picture (X's grey placeholder) gets a reply that links to https://three.ws/create and is recorded with reason
default_avatar. Nothing is generated. - The
_normal(48 px) URL is upgraded to the_400x400file and fetched from X's photo CDN only (pbs.twimg.com/profile_images/..., https, redirects refused, 5 MB cap, 15 second timeout, JPEG or PNG check and magic-byte check). Any other host is a skip with reasonimage_rejected:not_cdnand no request is made. - A vision model reviews it for ages-13+ safety and for showing a person, character or creature. This fails closed: with no vision provider the bot replies with the /create link and generates nothing (
review_unavailable). An unsafe picture gets a fixed refusal that echoes nothing. - The studio's rigged-avatar lane runs: image to 3D at the avatar tier, then auto-rig, the same two stages as the
forge_avatarMCP tool. The creation is attributed to the system bot account and the X author (forge_creations.x_author_id) and is unlisted. - The reply carries the render of the rigged model as media,
/m/<creation id>and/pose?src=<rigged glb>. If the rig fails, the unrigged mesh is returned (reasonavatar_done_unrigged:*). - Every success reply ends with a claim line (
withClaimNoteinapi/_lib/x-creation-claim.js): "Saved to your library." when the author has already linked the same X id, otherwise a link to https://three.ws/x/claim. Linking X later moves the bot-owned creation into the author's library and logs the move inx_creation_claims. - A job that outlives
X_MAKE_BUDGET_MSis recorded aspendingwith its stage (meshorrig). Every cron tick,finishPendingAvatarsprobes it once: a finished mesh starts its rig, a finished rig replies, and a failed or overdue job (X_MAKE_GIVE_UP_MS) gets the mesh if one exists or the failure reply.
Code
api/_lib/x-mention-avatar.js:handleAvatar,finishPendingAvatars,reviewProfileImage,composeAvatarReply,isDefaultProfileImage,poseLink.api/_lib/x-media-image.js:xProfileImageUrl, andfetchXImage(url, { profile: true }).api/_lib/x-creation-claim.js: claim lines and the move into the author's library (page:pages/x-claim.html).api/_lib/x-mention-poll.js: dispatchesavatarmentions and runs the follow-up each tick.tests/x-mention-avatar.test.js: own image, named-other-account cases, default image, moderation, CDN rules, pending follow-up.scripts/x-mention-avatar-dry-run.mjs: real dry runs from the real profile pictures of recent mentions; writesprompts/x-grok/_generated/avatar-dry-run.json.
Run it
node --env-file=.env.local scripts/x-mention-avatar-dry-run.mjs --base https://three.ws
Related: X mention bot safety rules, photo to 3D.