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.

fix(aws-docs): stop promising AWS invoicing, credits and EDP that the free x402 listing never bills

nirholas8fd15dbc1b5e
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 04f604cf0..21ca8caeb 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -27,6 +27,7 @@ Public history for [three.ws](https://three.ws), newest first. New pages come fr
- **The $THREE rider pass now recognises the wallets that paid for it**: The rider pass is a $THREE gate: you qualify either by holding $THREE or by sending 8,000 of it to the rider vault. Only the first half worked. The check answered purely from what a wallet currently holds, so anyone who bought a pass, and therefore no longer held the tokens they had just sent, was told they had no pass. The payments the vault recorded were written to the database and never read by anything. Both sources are now consulted, and a positive answer from either one stands on its own, so a paid pass still verifies while the chain node is unreachable and a holder pass still verifies during a database outage. A single transaction carrying payments from two different wallets used to fail outright and be retried forever by the payment listener, granting neither wallet a pass; every payer in a batch is now credited. The config the rider client loads at startup answered with a page of empty values when the deployment was not set up, which crashed the client with an unexplained error; it now says plainly that the feature is not configured. Repeating the address in the query string returned a server error and now returns a normal validation message. `[fix]`
- **The agent showcase pages all the way through, and the strategy board ranks the whole marketplace**: Three fixes to public read surfaces. Paging the ERC-8004 agent showcase past the first page could repeat a row forever or quietly skip one, because the cursor rounded the registration timestamp to the millisecond while the index stores microseconds, and an agent whose registry event carried no timestamp at all fell out of every page after the first. Both are fixed, and asking for a fractional number of results now returns a page instead of a server error. The published strategy board's default 'performance' order was ranking only the most recently published slice, so a proven, high-return strategy could sit invisible behind newer unproven ones; it now ranks the whole published pool before trimming to your page. And /sitemap.xml no longer answers a POST or a DELETE with the sitemap. (`/showcase`) `[fix]`
- **The agent wallet MCP server now quotes its own address when it asks an agent to pay**: Agents that connect to the wallet server at /api/mcp-agent without a three.ws account can pay per call in USDC instead. The payment request it handed back named the main three.ws MCP server, not itself, so a paying agent signed a payment scoped to an endpoint it had not called and service directories listed the wallet server under the wrong description and tool list. It now describes itself: its own address, its own wallet-and-payments summary, and a directory example that only searches for services rather than spending anything. Separately, the one-sentence agent builder no longer mangles accented names when it suggests a handle: Munz now becomes munz rather than mu-nz. (`/docs/mcp-agent`) `[fix]`
+- **The AWS page stops promising AWS invoicing three.ws does not do, and the GLB optimizer reads compressed avatars again**: Three corrections found by reading the docs pages against the code they describe. The AWS page told you a three.ws subscription would bill usage onto your AWS invoice, draw down AWS credits, and count toward Enterprise Discount Program commitments. None of that is the plan: the Marketplace subscription is free, and usage is paid per call in USDC over x402, exactly as it is for any other caller, so there is nothing to reconcile on your AWS bill at all. The page now says that, and describes the free subscription, the single key that opens every x402 endpoint, and the absence of any trial clock. Separately, the GLB optimization command documented on the 3D asset pipeline page failed on every compressed avatar, which is most of them, because it loaded the glTF extensions without the matching decoders; it now decodes meshopt and Draco and leaves the output as plain glTF the way its own contract promises. The NVIDIA models page also listed the tool-capable fallback model under the wrong vendor prefix. (`/aws`) `[fix, docs]`
- **The creations gallery now counts every creation a creator has made, and pages all the way to the end**: The gallery ranked creators and paged the feed over only the newest 120 creations, however many the feed actually held. A creator's older work was invisible in their profile count, the top-creator board scored people on a fraction of their output, and scrolling the gallery dead-ended early with items still left to show. It now reads the full feed depth it always meant to, and does it in two database round trips instead of two per item, so the deeper read loads faster than the shallow one did. (`/creations`) `[fix, improvement]`
- **The KOL, Loom and marketplace MCP servers now tell you why a call failed, and ship runnable examples**: When a market-data provider was rate-limited, these servers passed back only a bare code like provider_unavailable and threw away the sentence explaining it. They now surface the full reason. The KOL portfolio tool used to answer a provider outage with an empty card that read as a quiet wallet with no trades; it now reports the outage as an outage, so nobody sizes up a trader from a blank. The KOL and Loom packages also gained runnable examples that talk to the live public API, and the naming SDK now answers an unregistered .eth name the same way it answers an unclaimed .sol one, with data instead of an exception. `[fix, sdk]`
- **The public news feed can no longer be knocked out by a single post**: Everything that reads three.ws announcements, RSS readers and the HackerNoon importer alike, reads one feed at three.ws/rss/announcements.xml. That format has no partial failure: one illegal character anywhere in it makes the entire feed unreadable, so a single post could have taken every subscriber offline rather than costing one item. Three inputs could do that, and none of them can now. A code sample in an announcement that happened to contain the sequence that ends a raw-content block used to end it early and corrupt every item after it. Control characters the format forbids outright, which no amount of escaping can rescue, were passed straight through; they are now dropped, while emoji and other real characters are kept untouched. And a post whose wording happened to match a marker the feed builder uses internally while turning links into links stopped the feed building at all, returning an error to every reader instead. Separately, the feed takes an optional parameter for reading one of the archived accounts instead of the curated list, and misspelling it used to hand back the curated feed with no hint anything was wrong, so a subscriber could sit on the wrong feed indefinitely. It now says plainly that the source is unknown and lists the ones that exist. `[fix, infra]`
diff --git a/data/changelog.json b/data/changelog.json
index 2c1ec19bf..1d2ab9a05 100644
--- a/data/changelog.json
+++ b/data/changelog.json
@@ -1,6 +1,25 @@
{
"$comment": "Curated changelog entries for three.ws, the editorial layer of the public changelog. New PAGE launches are tracked automatically via the `added` field in data/pages.json; this file is for everything else holders care about: improvements, fixes, SDK releases, trading/payments capabilities, security work. scripts/build-page-index.mjs merges both sources into CHANGELOG.md, public/changelog.json, and public/changelog.xml. Newest first. Allowed tags: feature, improvement, fix, sdk, infra, docs, security. `link` is optional and must be a live three.ws path.",
"entries": [
+ {
+ "date": "2026-08-16",
+ "title": "The AWS page stops promising AWS invoicing three.ws does not do, and the GLB optimizer reads compressed avatars again",
+ "summary": "Three corrections found by reading the docs pages against the code they describe. The AWS page told you a three.ws subscription would bill usage onto your AWS invoice, draw down AWS credits, and count toward Enterprise Discount Program commitments. None of that is the plan: the Marketplace subscription is free, and usage is paid per call in USDC over x402, exactly as it is for any other caller, so there is nothing to reconcile on your AWS bill at all. The page now says that, and describes the free subscription, the single key that opens every x402 endpoint, and the absence of any trial clock. Separately, the GLB optimization command documented on the 3D asset pipeline page failed on every compressed avatar, which is most of them, because it loaded the glTF extensions without the matching decoders; it now decodes meshopt and Draco and leaves the output as plain glTF the way its own contract promises. The NVIDIA models page also listed the tool-capable fallback model under the wrong vendor prefix.",
+ "tags": [
+ "fix",
+ "docs"
+ ],
+ "link": "/aws"
+ },
+ {
+ "date": "2026-08-16",
+ "title": "Wallet reputation stops losing coins it never got around to judging",
+ "summary": "The rollup that turns launch history into wallet reputation was judging 80 coins every five minutes while the intel firehose was recording about 32,000 new mints a day, so it fell roughly 8,000 coins a day behind. That backlog does not wait its turn: the rollup works oldest-first and only reaches back 14 days, which is exactly when retention prunes the record, so the tail of the queue aged out and those buyers never counted toward anyone’s reputation at all. 309,000 coins were sitting unjudged with the oldest already 8.4 days from the cliff. The per-run budget is now 400, which outruns the firehose several times over, drains the backlog within days and then idles. Scores across the smart-money surfaces get their full evidence base back. The operations health board also tracks the retention and reconstruct sweeps, so a stall in either is visible instead of showing up later as a symptom.",
+ "tags": [
+ "fix",
+ "infra"
+ ]
+ },
{
"date": "2026-08-16",
"title": "The agent showcase pages all the way through, and the strategy board ranks the whole marketplace",
diff --git a/docs/nvidia-models.md b/docs/nvidia-models.md
index 7b8e0d6f0..4109d9987 100644
--- a/docs/nvidia-models.md
+++ b/docs/nvidia-models.md
@@ -107,7 +107,7 @@ This lane powers the platform's built-in AI surfaces — chat, embedded site wid
| Llama 4 Maverick | `meta/llama-4-maverick-17b-128e-instruct` | balanced | Meta's 128-expert MoE — fast, multimodal-capable |
| MiniMax M2.7 | `minimaxai/minimax-m2.7` | balanced | General reasoning and chat |
-For anonymous (signed-out) callers, only the genuinely free tiers — the OpenRouter open-weight default plus these NVIDIA NIM models — are selectable. Each shows "unavailable" until the key is set, and `meta/llama-3.3-nemotron-super-49b-v1.5` also appears in the routing catalog as a tool-capable fallback model.
+For anonymous (signed-out) callers, only the genuinely free tiers (the OpenRouter open-weight default plus these NVIDIA NIM models) are selectable. Each shows "unavailable" until the key is set, and `nvidia/llama-3.3-nemotron-super-49b-v1.5` also appears in the routing catalog as a tool-capable fallback model.
> **Where the line is:** Nemotron and the `nvidia/…`-prefixed models are NVIDIA's own. The others in this table (DeepSeek, Kimi, Llama 4, MiniMax) are third-party open weights that NVIDIA *hosts and serves free* on NIM — so they ride the same key, but the model itself isn't NVIDIA's. The point of NIM is exactly this: one free key, a whole model garden.
diff --git a/pages/aws/index.html b/pages/aws/index.html
index bf18eeaef..ebe7058ad 100644
--- a/pages/aws/index.html
+++ b/pages/aws/index.html
@@ -10,7 +10,7 @@
<meta property="og:type" content="website" />
<meta property="og:title" content="three.ws on AWS — 3D AI Agent Platform" data-i18n-attr="content:aws_index.meta_og_title"/>
- <meta property="og:description" content="Open-source 3D AI agent platform. AWS Partner. Marketplace listing coming soon — subscribe with AWS credits, bill to your AWS invoice." data-i18n-attr="content:aws_index.meta_og_description"/>
+ <meta property="og:description" content="Open-source 3D AI agent platform. AWS Partner. Marketplace listing coming soon: a free subscription, with usage paid per call in USDC over x402." data-i18n-attr="content:aws_index.meta_og_description2"/>
<meta property="og:url" content="https://three.ws/aws" />
<meta property="og:image" content="https://three.ws/screenshots/viewer.png" />
@@ -131,7 +131,7 @@
<h1 data-i18n-html="aws_index.three_ws_on_aws">three.ws on <span class="gradient">AWS</span>.</h1>
<p class="lede" data-i18n-html="aws_index.three_ws_is_an_open_source_3d">
- three.ws is an open-source 3D AI agent platform — WebGL viewer, Claude-driven runtime, on-chain identity, embed anywhere with one tag. <strong>Now an AWS Partner.</strong> Marketplace listing coming soon — subscribe with AWS credits, bill to your AWS invoice, count toward EDP commitments.
+ three.ws is an open-source 3D AI agent platform: WebGL viewer, Claude-driven runtime, on-chain identity, embed anywhere with one tag. <strong>Now an AWS Partner.</strong> Marketplace listing coming soon: the subscription is free, and usage is paid per call in USDC over x402.
</p>
<div class="cta-row">
@@ -157,36 +157,36 @@
<div class="icon">
<svg width="18" height="18" viewBox="0 0 24 24" fill="none" stroke="#cccccc" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M12 2v20M2 12h20"/></svg>
</div>
- <h3 data-i18n="aws_index.aws_credits_eligible">AWS credits eligible</h3>
- <p data-i18n="aws_index.use_existing_aws_credits_and_activate_fundin">Use existing AWS credits and Activate funding against three.ws subscriptions.</p>
+ <h3 data-i18n="aws_index.free_aws_subscription">Free AWS subscription</h3>
+ <p data-i18n="aws_index.subscribing_is_free_no_pricing_dimensions">Subscribing is free: no pricing dimensions, no minimum, no commitment. It links your AWS account to a three.ws account and issues your x402 access key.</p>
</div>
<div class="benefit">
<div class="icon">
<svg width="18" height="18" viewBox="0 0 24 24" fill="none" stroke="#cccccc" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><rect x="2" y="6" width="20" height="14" rx="2"/><path d="M2 10h20M6 16h4"/></svg>
</div>
- <h3 data-i18n="aws_index.consolidated_billing">Consolidated billing</h3>
- <p data-i18n="aws_index.usage_rolls_onto_your_aws_invoice_under">Usage rolls onto your AWS invoice under AWS Marketplace Software — no new vendor in procurement.</p>
+ <h3 data-i18n="aws_index.pay_per_call_in_usdc">Pay per call in USDC</h3>
+ <p data-i18n="aws_index.usage_is_paid_per_call_over_x402">Usage is paid per call in USDC over x402 (HTTP 402), exactly as it is for every other caller. AWS Marketplace does not meter or bill it, so there is nothing to reconcile on your AWS invoice.</p>
</div>
<div class="benefit">
<div class="icon">
<svg width="18" height="18" viewBox="0 0 24 24" fill="none" stroke="#cccccc" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><path d="M20 6L9 17l-5-5"/></svg>
</div>
- <h3 data-i18n="aws_index.edp_commit_toward">EDP commit toward</h3>
- <p data-i18n="aws_index.marketplace_spend_counts_toward_your_enterpr">Marketplace spend counts toward your Enterprise Discount Program commitments.</p>
+ <h3 data-i18n="aws_index.one_key_every_x402_endpoint">One key, every x402 endpoint</h3>
+ <p data-i18n="aws_index.the_key_the_subscription_issues_calls">The key the subscription issues calls every /api/x402/* endpoint. You can use x402 today without an AWS subscription at all.</p>
</div>
<div class="benefit">
<div class="icon">
<svg width="18" height="18" viewBox="0 0 24 24" fill="none" stroke="#cccccc" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><circle cx="12" cy="12" r="10"/><path d="M12 6v6l4 2"/></svg>
</div>
- <h3 data-i18n="aws_index.free_trial_included">Free trial included</h3>
- <p data-i18n="aws_index.try_three_ws_community_edition_with_no">Try three.ws Community Edition with no commitment. Subscription activates only after the trial ends.</p>
+ <h3 data-i18n="aws_index.no_trial_clock_to_run_out">No trial clock to run out</h3>
+ <p data-i18n="aws_index.there_is_no_trial_and_no_activation_step">There is no trial and no activation step. The subscription stays free for as long as you keep it, and you pay only for the calls you actually make.</p>
</div>
<div class="benefit">
<div class="icon">
<svg width="18" height="18" viewBox="0 0 24 24" fill="none" stroke="#cccccc" stroke-width="2" stroke-linecap="round" stroke-linejoin="round"><rect x="3" y="3" width="18" height="18" rx="3"/><path d="M9 9h6v6H9z"/></svg>
</div>
- <h3 data-i18n="aws_index.metering_in_us_east_1">Metering in us-east-1</h3>
- <p data-i18n-html="aws_index.entitlement_and_metering_calls_reach_the">Entitlement and metering calls reach the AWS Marketplace APIs in us-east-1, the region AWS serves them from. Set <code>AWS_MP_REGION</code> to point somewhere else.</p>
+ <h3 data-i18n="aws_index.marketplace_apis_in_us_east_1">Marketplace APIs in us-east-1</h3>
+ <p data-i18n-html="aws_index.registration_and_entitlement_calls_reach_the">Registration and entitlement calls reach the AWS Marketplace APIs in us-east-1, the region AWS serves them from. Set <code>AWS_MP_REGION</code> to point somewhere else.</p>
</div>
<div class="benefit">
<div class="icon">
diff --git a/public/changelog.json b/public/changelog.json
index 6829d36f3..00efb834e 100644
--- a/public/changelog.json
+++ b/public/changelog.json
@@ -1,5 +1,5 @@
{
- "generated_at": "2026-08-16T07:59:12.032Z",
+ "generated_at": "2026-08-16T08:06:17.799Z",
"generated_by": "scripts/build-page-index.mjs from data/pages.json + data/changelog.json",
"site": {
"name": "three.ws",
@@ -226,6 +226,17 @@
"fix"
]
},
+ {
+ "date": "2026-08-16",
+ "type": "update",
+ "title": "The AWS page stops promising AWS invoicing three.ws does not do, and the GLB optimizer reads compressed avatars again",
+ "summary": "Three corrections found by reading the docs pages against the code they describe. The AWS page told you a three.ws subscription would bill usage onto your AWS invoice, draw down AWS credits, and count toward Enterprise Discount Program commitments. None of that is the plan: the Marketplace subscription is free, and usage is paid per call in USDC over x402, exactly as it is for any other caller, so there is nothing to reconcile on your AWS bill at all. The page now says that, and describes the free subscription, the single key that opens every x402 endpoint, and the absence of any trial clock. Separately, the GLB optimization command documented on the 3D asset pipeline page failed on every compressed avatar, which is most of them, because it loaded the glTF extensions without the matching decoders; it now decodes meshopt and Draco and leaves the output as plain glTF the way its own contract promises. The NVIDIA models page also listed the tool-capable fallback model under the wrong vendor prefix.",
+ "link": "/aws",
+ "tags": [
+ "fix",
+ "docs"
+ ]
+ },
{
"date": "2026-08-16",
"type": "update",
diff --git a/public/changelog.xml b/public/changelog.xml
index b2c24073a..c9587c90c 100644
--- a/public/changelog.xml
+++ b/public/changelog.xml
@@ -174,6 +174,14 @@
<category>fix</category>
<description>Agents that connect to the wallet server at /api/mcp-agent without a three.ws account can pay per call in USDC instead. The payment request it handed back named the main three.ws MCP server, not itself, so a paying agent signed a payment scoped to an endpoint it had not called and service directories listed the wallet server under the wrong description and tool list. It now describes itself: its own address, its own wallet-and-payments summary, and a directory example that only searches for services rather than spending anything. Separately, the one-sentence agent builder no longer mangles accented names when it suggests a handle: Munz now becomes munz rather than mu-nz.</description>
</item>
+ <item>
+ <title>The AWS page stops promising AWS invoicing three.ws does not do, and the GLB optimizer reads compressed avatars again</title>
+ <link>https://three.ws/aws</link>
+ <guid isPermaLink="false">2026-08-16:The AWS page stops promising AWS invoicing three.ws does not do, and the GLB optimizer reads compressed avatars again</guid>
+ <pubDate>Sun, 16 Aug 2026 12:00:00 GMT</pubDate>
+ <category>fix</category>
+ <description>Three corrections found by reading the docs pages against the code they describe. The AWS page told you a three.ws subscription would bill usage onto your AWS invoice, draw down AWS credits, and count toward Enterprise Discount Program commitments. None of that is the plan: the Marketplace subscription is free, and usage is paid per call in USDC over x402, exactly as it is for any other caller, so there is nothing to reconcile on your AWS bill at all. The page now says that, and describes the free subscription, the single key that opens every x402 endpoint, and the absence of any trial clock. Separately, the GLB optimization command documented on the 3D asset pipeline page failed on every compressed avatar, which is most of them, because it loaded the glTF extensions without the matching decoders; it now decodes meshopt and Draco and leaves the output as plain glTF the way its own contract promises. The NVIDIA models page also listed the tool-capable fallback model under the wrong vendor prefix.</description>
+ </item>
<item>
<title>The creations gallery now counts every creation a creator has made, and pages all the way to the end</title>
<link>https://three.ws/creations</link>
diff --git a/public/locales/en.json b/public/locales/en.json
index 06ed74dce..25be38f40 100644
--- a/public/locales/en.json
+++ b/public/locales/en.json
@@ -1952,28 +1952,38 @@
"edp_commit_toward": "EDP commit toward",
"entitlement_and_metering_calls_reach_the": "Entitlement and metering calls reach the AWS Marketplace APIs in us-east-1, the region AWS serves them from. Set <code>AWS_MP_REGION</code> to point somewhere else.",
"everything_in_three_ws_open_source_productio": "Everything in three.ws — open source, production-ready, runs in any modern browser.",
+ "free_aws_subscription": "Free AWS subscription",
"free_trial_included": "Free trial included",
"get_notified_when_the_listing_goes_live": "Get notified when the listing goes live.",
"github": "GitHub",
"how_we_metered_a_saas_product": "How we metered a SaaS product through AWS Marketplace with the AWS SDK for JavaScript v3",
+ "marketplace_apis_in_us_east_1": "Marketplace APIs in us-east-1",
"marketplace_spend_counts_toward_your_enterpr": "Marketplace spend counts toward your Enterprise Discount Program commitments.",
"meta_description": "three.ws is an AWS Partner. Open-source 3D AI agent platform — WebGL-native viewer, LLM-driven runtime, on-chain identity. AWS Marketplace listing coming soon.",
"meta_og_description": "Open-source 3D AI agent platform. AWS Partner. Marketplace listing coming soon — subscribe with AWS credits, bill to your AWS invoice.",
+ "meta_og_description2": "Open-source 3D AI agent platform. AWS Partner. Marketplace listing coming soon: a free subscription, with usage paid per call in USDC over x402.",
"meta_og_title": "three.ws on AWS — 3D AI Agent Platform",
"meta_title": "three.ws on AWS — 3D AI Agent Platform · AWS Partner",
"meta_twitter_description": "Open-source 3D AI agent platform. AWS Partner. Marketplace listing coming soon.",
"meta_twitter_title": "three.ws on AWS",
"metering_in_us_east_1": "Metering in us-east-1",
+ "no_trial_clock_to_run_out": "No trial clock to run out",
+ "one_key_every_x402_endpoint": "One key, every x402 endpoint",
"open_source": "Open source.",
"our_writing_on_the_aws_builder_center": "Our writing on the AWS Builder Center.",
+ "pay_per_call_in_usdc": "Pay per call in USDC",
"privacy": "Privacy",
+ "registration_and_entitlement_calls_reach_the": "Registration and entitlement calls reach the AWS Marketplace APIs in us-east-1, the region AWS serves them from. Set <code>AWS_MP_REGION</code> to point somewhere else.",
"resolvecustomer_meterusage_entitlements": "ResolveCustomer, MeterUsage, GetEntitlements, and SNS lifecycle webhooks with real signature verification, then bridging an AWS CustomerIdentifier into the same access check that serves an on-chain x402 paywall.",
"software_path": "Software Path",
"standard_contract": "Standard Contract",
"star_on_github": "Star on GitHub",
+ "subscribing_is_free_no_pricing_dimensions": "Subscribing is free: no pricing dimensions, no minimum, no commitment. It links your AWS account to a three.ws account and issues your x402 access key.",
"terms": "Terms",
"the_aws_marketplace_listing_is_in_review": "The AWS Marketplace listing is in review. Until it publishes, you can:",
"the_integration": "The integration.",
+ "the_key_the_subscription_issues_calls": "The key the subscription issues calls every /api/x402/* endpoint. You can use x402 today without an AWS subscription at all.",
+ "there_is_no_trial_and_no_activation_step": "There is no trial and no activation step. The subscription stays free for as long as you keep it, and you pay only for the calls you actually make.",
"three_ws": "three.ws",
"three_ws_2": "three.ws",
"three_ws_implements_the_full_aws_marketplace": "three.ws implements the full AWS Marketplace SaaS contract — registration, metering, entitlements, and signed SNS subscription lifecycle webhooks.",
@@ -1982,6 +1992,7 @@
"three_ws_on_aws": "three.ws on <span class=\"gradient\">AWS</span>.",
"three_ws_subscribes_under_the_aws_standard": "three.ws subscribes under the AWS Standard Contract for Marketplace. Procurement-ready out of the box.",
"try_three_ws_community_edition_with_no": "Try three.ws Community Edition with no commitment. Subscription activates only after the trial ends.",
+ "usage_is_paid_per_call_over_x402": "Usage is paid per call in USDC over x402 (HTTP 402), exactly as it is for every other caller. AWS Marketplace does not meter or bill it, so there is nothing to reconcile on your AWS invoice.",
"usage_rolls_onto_your_aws_invoice_under": "Usage rolls onto your AWS invoice under AWS Marketplace Software — no new vendor in procurement.",
"use_existing_aws_credits_and_activate_fundin": "Use existing AWS credits and Activate funding against three.ws subscriptions.",
"we_publish_the_engineering_behind_this": "We publish the engineering behind this integration on Amazon's community platform, under the official @threews account. Both articles link back to the Apache 2.0 source.",