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.

10.8 KB
Raw Blame

three.ws on the AWS Builder Center

The AWS Builder Center is Amazon's community publishing platform for engineers building on AWS. three.ws publishes there under the official organization account, @threews, as part of our AWS Partner Network membership.

This page is the index of that writing: what is published, where it lives, and what code each article documents. If you are adding an article, the checklist at the bottom is the process.

Published articles

1. How we metered a SaaS product through AWS Marketplace with the AWS SDK for JavaScript v3

Published 30 May 2026. Tags: aws-payment-cryptography, blockchain, metadata, agent-toolkit, agentic-ai.

Read it on the AWS Builder Center

The full AWS Marketplace SaaS usage-based integration, end to end: ResolveCustomer on the fulfillment URL, MeterUsage and BatchMeterUsage for consumption reporting, GetEntitlements for tiered feature gating, and SNS lifecycle webhooks with real signature verification. It closes on the part nobody else writes about: bridging an AWS CustomerIdentifier into the same access check that already served an on-chain x402 paywall, so one authorization path bills two economies.

2. Build Autonomous AI Agents with 3D Bodies and On-Chain Payments | three.ws on AWS

Published 27 June 2026. Tags: ai, agent-toolkit, blockchain, aws-partners, multi-agent-orchestrator.

Read it on the AWS Builder Center

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.

Published by AWS about three.ws

Articles written by AWS staff, not by us. These are not our byline and we do not control their content; they are recorded here because they are the strongest third-party evidence of the integration.

The Agentic Economy Is Here: x402, MCP, AI Agents, Crypto, and 3D Worlds Converging | AWS Strategic Partnerships

Published 26 June 2026 by Kelly Wu (AWS). Part of the AWS-run series "AWS Partners with three.ws | AWS Strategic Partnerships". Tags: aws-partners, aws-service-catalog, agentic-economy, x402, model-context-protocol.

Read it on the AWS Builder Center

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, x402, agent wallets, the <agent-3d> web component
  • 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; a slug containing the digits also resolves, because the content ID is what routes.

In draft

Written and reviewed in this repo, not yet submitted:

Draft Subject
aws-builder-center-before-the-signature.md Flagship. The whole authorization spine in one piece: Marketplace entitlements under Concurrent Agreements, budgets instead of private keys, the budget check as a predicate in the UPDATE, the SSRF guard around an LLM-chosen URL, the payment outcome with no clean answer, signed inference receipts, agent vitals, hardware-backed signing, and the fabrication gate in front of a manufactured object. Supersedes the four topic drafts below.
aws-builder-center-agent-payment-sessions.md Agent Payment Sessions: giving an agent a budget instead of a private key, and enforcing it atomically in Postgres
aws-builder-center-mcp-agents.md An MCP server whose paid tools settle per call in USDC over HTTP 402
mobile-launch/aws-builder-center-article.md One web product, three native apps, zero forks: the Seeker, Android, and iPhone shells, with the AWS SDK v3 storage client and the Marketplace front door
aws-builder-center-agent-commerce-spine.md The authorization spine behind autonomous commerce: Marketplace entitlements under Concurrent Agreements, spend policy instead of a credential, x402 preflight, agent vitals, and the physical fulfillment lane at the end of the chain
aws-builder-center-universal-retargeting.md Any skeleton, one clip library: how 113 pre-baked clips play on humanoid avatars from many exporters in the browser with no rig allowlist. Bone-name canonicalization, the bind correction, the A-pose re-aim, the fallen-pose guard, and the conventions that still fail. Companion thread: universal-retargeting-thread.md
aws-builder-center-immutable-embed-releases.md A URL is a promise: moving channels beside write-once versioned URLs for the <agent-3d> web component, the release ledger, Subresource Integrity pins, the 2026-10-01 incident that broke every pin, and how the pattern maps to S3 Object Lock and CloudFront. Companion thread: immutable-embed-releases-thread.md
aws-builder-center-claims-ledger.md An AI-assisted publishing pipeline that refuses to post what it cannot prove: the claims ledger, probes, proof reels filmed against production, content-hash-bound reviews, the idempotent publish ledger, and the model failover chain. Companion thread: claims-ledger-thread.md
aws-builder-center-open-weight-3d-forge.md Running open-weight text-to-3D in production: the Forge's lane router and failover ladder across self-hosted GPU workers (TRELLIS, Hunyuan3D, TripoSG) and hosted rungs, cold starts and weight staging, meshopt decoding in every mesh worker, vendored shared code, and forge_creations as per-generation ground truth. Companion thread: open-weight-3d-forge-thread.md

Publishing checklist

The Builder Center editor accepts Markdown, so a draft in docs/ is the article. To take one from draft to published:

  1. Write the draft as docs/aws-builder-center-<topic>.md with the frontmatter block the existing drafts use (title, venue, account, description, tags). Every code sample must be real code from this repo, and every claim must be verifiable against it. The Builder Center audience reads the linked source.
  2. Check the rules: npm run check:rules -- --paths docs/aws-builder-center-<topic>.md.
  3. Check the links: npm run audit:docs.
  4. Publish from builder.aws.com/create/content using the official account, pasting the Markdown body and setting the tags from the frontmatter.
  5. Record the canonical URL by adding a section to this page: title, publish date, tags, the live URL, the source draft, and the code it documents.
  6. Announce it by adding an item to data/rss/items.json (the curated news feed) with the canonical Builder Center URL as link, then regenerate with npm run build:news. The item becomes a page under /news/<slug> and enters the RSS feed automatically.
  7. Log it in data/changelog.json with the docs tag.

Why we publish here

The Builder Center is where AWS customers evaluating a partner product go looking for evidence that the engineering is real. A marketing page claims an integration exists; a walkthrough of the exact SDK calls, the signature-verification pitfalls, and the failure modes proves it. Every article we publish there points at readable source in this repository, so a reader can check the claim in the same sitting.