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.

3.4 KB
Raw Blame

Use Cases & Example Workflows

Five "here's how three.ws solves your problem" narratives, one per audience. Each ties real, shipped features to a concrete outcome and walks through a reproducible, step-by-step example.

Who these are for

Audience File The job-to-be-done
Indie creator indie-creator.md Turn a selfie or a text prompt into a 3D agent and embed it anywhere.
Game studio game-studio.md Drop a GLB pipeline, an LLM-driven NPC runtime, and a live multiplayer world into a game.
AI-agent developer ai-agent-developer.md Give an agent a body, paid endpoints (x402), an MCP/A2A interface, and on-chain identity.
Brand / marketer brand-marketer.md Put an embeddable, verifiable talking agent on a site, distributed through cloud marketplaces.
Crypto community crypto-community.md Give a token community a live 3D world, an agent economy, and on-chain reputation.

How to read these (the honesty frame)

Every scenario on these pages is an example workflow — clearly labeled "Imagine a creator who…" or similar. They are illustrations of how a persona would use three.ws, walked through with real routes you can reproduce today.

  • No fabricated customers. No company is presented as a real three.ws customer. Where a real customer story would strengthen a page, there is a [REAL CASE STUDY — fill on consent] placeholder. That placeholder is never replaced with an invented name.
  • No invented metrics. No "shipped 40% faster," no made-up retention or conversion numbers. Outcomes are described honestly in terms of what the feature does, not fictional results.
  • No testimonials unless and until a real, consenting customer provides one.
  • Every feature is real. Each capability cited maps to a shipped route or doc, re-confirmed against README.md. If a route moved, the walkthrough is wrong — fix it, don't ship around it.

Affiliation language (guardrails)

  • IBM / watsonx / Granite — the agent runtime is built on IBM watsonx.ai running IBM Granite models, and three.ws is an IBM Business Partner. The /ibm/* showcase surfaces are independent developer demos three.ws built to explore Granite on watsonx.ai — not official IBM products, deliverables, or endorsements. Never write "official IBM partnership" about the public demos.
  • AWS — three.ws is an AWS Partner with an AWS Marketplace SaaS listing (in review). That is a marketplace listing, not an AWS endorsement of the product.
  • Solana / pump.fun — integrations, not endorsements. Same caution for every third party.

The only coin

$THREE is the only coin referenced anywhere in this content. Contract address: FeMbDoX7R1Psc4GEcvJdsbNbZA3bfztcyDCatJVJpump. Every example mint, token, or community in these files is $THREE or a clearly-synthetic placeholder. No other coin appears.

Related assets

  • Press kit / fact sheet (Workstream G04) — reuse its confirmed links so capability claims stay consistent. Link to it; don't duplicate it.
  • Social spotlights (G03) — each use case below has a feature angle worth a spotlight post; angles are noted inline.
  • Demo scripts (G02) — a walkthrough can reference the matching demo script for visuals.