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.

docs(hubs): add the hubs index and a STRUCTURE.md row for the eleven ecosystem directories

nirholasb94d00fd9913
diff --git a/STRUCTURE.md b/STRUCTURE.md
index 564dbf1a8..9c72c5b15 100644
--- a/STRUCTURE.md
+++ b/STRUCTURE.md
@@ -375,6 +375,7 @@ bottom.
| X post archive + engagement analysis (internal) | Snapshots [data/x-archive/](data/x-archive), schema [api/_lib/migrations/20260814120000_x_account_archive.sql](api/_lib/migrations/20260814120000_x_account_archive.sql), normalization + analysis [scripts/x-archive-lib.mjs](scripts/x-archive-lib.mjs), commands [scripts/x-archive-import.mjs](scripts/x-archive-import.mjs) · [scripts/x-archive-refresh.mjs](scripts/x-archive-refresh.mjs) · [scripts/x-archive-analyze.mjs](scripts/x-archive-analyze.mjs), report [docs/x-archive/](docs/x-archive) | Internal · doc [docs/x-archive.md](docs/x-archive.md) | Every post our own X accounts published, kept as raw snapshot files and indexed into `x_account_posts` / `x_account_post_snapshots` so engagement is a measured time series rather than a memory. `npm run x:archive:analyze` regenerates a report ranking posts by engagement and by engagement *rate*, and scores every measurable signal (media, mentions, length, subject, hour) as lift against the corpus median. Two scraper defects are handled rather than inherited: a profile scrape returns reposts of other accounts with `isRetweet: false` (authorship is read from the permalink instead), and X renders like counts lazily so real posts arrive at "0 likes" (those are archived, named, and excluded from the medians until `npm run x:archive:refresh` replaces them with exact X API counters). Distinct from `x_posts`, which is what platform users publish through [api/x/post.js](api/x/post.js). Tests: [tests/x-archive.test.js](tests/x-archive.test.js) |
| Interactive 3D history timeline | [pages/timeline.html](pages/timeline.html) `→ /timeline`, [src/timeline.js](src/timeline.js), data [data/timeline.json](data/timeline.json) | Live | three.ws's public history (launches, partnerships, listings, press, product ships) as an explorable 3D scene: 60+ milestones as glowing markers along a curved path, 360° free-orbit or a marker-to-marker Walk mode with a guide beacon (reuses the shared `AnimationManager` + default rig from [src/walk.js](src/walk.js)'s pattern), a synced bottom scrubber, category filters, and a detail panel linking to the original source where one exists (IBM Community, NVIDIA Developer Forums, Yahoo Finance, Phemex, CoinGecko, HackerNoon). Real accessible HTML-list fallback for no-WebGL or fetch-failure. |
| Upstream resilience toolkit | [scripts/resilience/](scripts/resilience) + [scripts/audit-upstreams.mjs](scripts/audit-upstreams.mjs) `→ npm run audit:upstreams`, baseline [data/upstream-baseline.json](data/upstream-baseline.json), generated map [docs/resilience.md](docs/resilience.md) | Live | Answers the question a fallback alone cannot: when a third-party service is down, what is each endpoint ALLOWED to say? An AST pass grades every outbound call site on five protections (deadline, retry, failover, last-good, breaker) and ratchets against a committed baseline, so a new unbounded call fails the build while the existing tail is paid down at its own pace. On top of it, endpoints declare a degradation contract (`may-serve-stale`, `must-refuse`, `must-not-serve-stale`) that [tests/upstream-degradation.test.js](tests/upstream-degradation.test.js) proves by replacing fetch with a dead upstream and judging the real response. Built after four fallbacks that each passed review turned out to serve remembered data on paths where staleness costs money or grants access. Complements [scripts/check-fetch-timeouts.mjs](scripts/check-fetch-timeouts.mjs), which enforces the deadline floor. Docs: [scripts/resilience/README.md](scripts/resilience/README.md) |
+| Ecosystem hubs (curated directories) | [hubs/](hubs) | Ready to publish as separate repos | Eleven self-contained JSON-backed awesome-list hubs (agent payments, identity, wallets, protocols, skills, data APIs, browser agents, Solana agents, embodied agents, generative 3D, Robinhood Crypto), each with schema, validator, README generator and contribution templates. Index: [hubs/README.md](hubs/README.md) |
## Workers and services not mapped above
diff --git a/hubs/README.md b/hubs/README.md
new file mode 100644
index 000000000..639ddf345
--- /dev/null
+++ b/hubs/README.md
@@ -0,0 +1,27 @@
+# Hubs
+
+Curated, machine-readable directories for fast-growing corners of crypto, AI and 3D. Each folder is self-contained (JSON dataset, schema, validator, README generator, contribution templates, CC0 license) and is built to be lifted into its own GitHub repo.
+
+| Hub | Scope |
+|---|---|
+| [awesome-agent-payments](awesome-agent-payments) | x402, AP2, ACP, MPP, facilitators and agent commerce (Solana first) |
+| [awesome-agent-identity](awesome-agent-identity) | ERC-8004, agent registries, attestations and reputation (Solana first) |
+| [awesome-solana-agents](awesome-solana-agents) | Agent kits, MCP servers, skills and tooling on Solana |
+| [awesome-agent-wallets](awesome-agent-wallets) | MPC, TEE, smart accounts, session keys and policy engines |
+| [awesome-agent-protocols](awesome-agent-protocols) | A2A, MCP, ANP, gateways, SDKs and discovery |
+| [awesome-agent-skills](awesome-agent-skills) | SKILL.md bundles, registries, authoring and scanning tools |
+| [awesome-agent-data-apis](awesome-agent-data-apis) | Paid and machine-readable data for agents |
+| [awesome-browser-agents](awesome-browser-agents) | WebMCP, browser-use, computer-use and headless infrastructure |
+| [awesome-embodied-agents](awesome-embodied-agents) | AI avatars, digital humans, VRM/glTF and web 3D runtimes |
+| [awesome-generative-3d](awesome-generative-3d) | Text/image-to-3D, splatting, rigging and glTF pipelines |
+| [awesome-robinhood-crypto](awesome-robinhood-crypto) | Robinhood Crypto API clients, MCP servers and Robinhood Chain tooling |
+
+## Working on a hub
+
+```
+cd hubs/<hub>
+node scripts/validate.mjs # schema, URLs, ordering, dash check
+node scripts/build-readme.mjs # regenerate the README tables from data/entries.json
+```
+
+Edit `data/entries.json` only; the README tables between the `ENTRIES` markers are generated. Entries must be verified against the project's own page or repo before they are added. Hubs ship with a placeholder `$id` in `data/schema.json` that is replaced with the real repo URL when a hub is published.