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.

feat(deployments): link the feed to the new Genesis-style deploy page

nirholase6286aa7759e
diff --git a/STRUCTURE.md b/STRUCTURE.md
index e9dd707e3..6154d354e 100644
--- a/STRUCTURE.md
+++ b/STRUCTURE.md
@@ -152,6 +152,7 @@ bottom.
| Open Inference Protocol (OIN v0.1) | spec [specs/OPEN_INFERENCE_PROTOCOL.md](specs/OPEN_INFERENCE_PROTOCOL.md), verifier [api/_lib/oin-verify.js](api/_lib/oin-verify.js), conformance runner [scripts/oin-conformance.mjs](scripts/oin-conformance.mjs), reference node [workers/stylize/oin.py](workers/stylize/oin.py) | In-repo | Phase 4 roadmap: the vendor-neutral wire protocol that decouples inference from any single provider. A job envelope, a signed capability advertisement at `GET /.well-known/oin`, and an Ed25519-signed response bound to the job by a SHA-256 digest over its RFC 8785 canonical form, so any third party can verify a node's result without trusting the transport or the platform. The stylize worker is the reference node behind `OIN_ENABLED=true` (byte-for-byte its pre-OIN self with the flag off) and self-hosted operators with no GCS bucket sign filesystem artifacts via `OIN_RESULT_DIR`. `node scripts/oin-conformance.mjs --node <url>` drives advertisement, submit, poll, response verification, and artifact hashing end to end. Settlement rides on [specs/inference-receipts.md](specs/inference-receipts.md). Tests: [tests/oin-verify.test.js](tests/oin-verify.test.js), [workers/stylize/test_stylize.py](workers/stylize/test_stylize.py) |
| Production server (Google Cloud Run) | [server/](server) + [Dockerfile](Dockerfile) | Live | Single Express container serving the static frontend, the vercel.json route table, and all `api/**` handlers with Vercel-parity routing; deploy via `npm run deploy:gcp` ([server/cloudbuild.yaml](server/cloudbuild.yaml)), crons via [scripts/create-gcp-scheduler.mjs](scripts/create-gcp-scheduler.mjs) · see [server/README.md](server/README.md) |
| Multiplayer 3D world (world.three.ws) | [deploy/world/](deploy/world) — [Dockerfile](deploy/world/Dockerfile), [cloudrun.yaml](deploy/world/cloudrun.yaml), [apply-hardening.sh](deploy/world/apply-hardening.sh), patches in [deploy/world/patches/](deploy/world/patches); health monitor [api/cron/world-health.js](api/cron/world-health.js) | Live · `hyperfy-world` on Cloud Run | [Hyperfy](https://github.com/hyperfy-xyz/hyperfy) pinned to an exact upstream commit and rebuilt with three local patches (server-side upload cap, `/status` blueprint-asset enumeration, fail-closed-without-`ADMIN_CODE`). World state (SQLite + uploaded assets) lives in the GCS bucket `world-three-ws-data` mounted at `/app/world`, so the container is stateless. **The world is gated:** without `ADMIN_CODE` Hyperfy's `effectiveRank` falls back to `Ranks.ADMIN` and every anonymous visitor gets server-side build rights — the fail-open default that emptied the world on 2026-06-12. Deploy + verify with `bash deploy/world/apply-hardening.sh`; builders unlock in-world with `/admin <code>`. See [deploy/world/README.md](deploy/world/README.md) |
+| Metaplex Agent Registry deploy (Genesis-333 mint for everyone) | [pages/deploy-onchain.html](pages/deploy-onchain.html) + [src/deploy-onchain.js](src/deploy-onchain.js) `→ /deploy-onchain`, shared builders [packages/metaplex-agent-mcp/src/lib/](packages/metaplex-agent-mcp/src/lib) (published as `@three-ws/metaplex-agent-mcp`, also in the official MCP registry as `io.github.nirholas/metaplex-agent`) | Live | Mint any agent into the Metaplex Agent Registry in the exact Genesis 333 shape: data: URI metadata, verified creator, 5% royalties, immutable metadata, EIP-8004 identity with `model.uri` + `x402Support`. The page signs with the user's own wallet (Phantom/Solflare/Backpack, `signAllTransactions`) through the same-origin RPC proxy; the MCP server gives agents the identical mint with their own key (preview-first, `confirm:true` gated) plus a prepare/send lane for external wallets. Both consume one isomorphic builder library, and [tests](packages/metaplex-agent-mcp/test/genesis-shape.test.mjs) pin the output byte-for-byte to the live Genesis #332 URIs. Devnet is a free rehearsal lane end-to-end. |
| On-chain contracts (Solidity + Solana) | [contracts/](contracts) · [contracts/README.md](contracts/README.md) | Mixed: `ThreeWSPayments` + `ThreeWSFactory` live on BSC/Base/Arbitrum, the rest in-repo | Every contract and program three.ws owns, in one Foundry project plus two Anchor programs. ERC-8004 identity/reputation/validation registries (reference implementations of the canonical deployments the platform actually reads), the live x402 USDC receiver and its CREATE2 vanity factory, `AgentPayments`, `GreenfieldVault`, `WorldMoves`, and the Solana `skill_license` / `agent_invocation` programs. `forge test` covers the Solidity set with 242 tests across 8 suites; the Solana side is covered by the LiteSVM row below. Deploy status per contract and the address provenance per chain: [contracts/DEPLOYMENTS.md](contracts/DEPLOYMENTS.md) |
| Contract audit pack | [contracts/AUDIT-README.md](contracts/AUDIT-README.md), invariants [specs/ECONOMY_CONTRACT_INVARIANTS.md](specs/ECONOMY_CONTRACT_INVARIANTS.md), threat model [specs/ECONOMY_CONTRACT_THREAT_MODEL.md](specs/ECONOMY_CONTRACT_THREAT_MODEL.md), static analysis [contracts/audit/](contracts/audit) | In-repo | Everything a review firm needs on day one for the reputation, royalty and delegation contracts: scope + deploy status per contract, stable invariant ids with a positive and a negative test each, an assets/actors/failure-modes threat model, and committed Slither + Clippy output with every finding fixed or dispositioned in writing |
| Recurring payments (subscriptions + DCA) | Page [public/recurring.html](public/recurring.html) `→ /recurring`, module [src/recurring.js](src/recurring.js), lifecycle rules [api/_lib/recurring.js](api/_lib/recurring.js), APIs [api/agent-subscriptions.js](api/agent-subscriptions.js) `→ /api/agent-subscriptions` and [api/dca-strategies.js](api/dca-strategies.js) `→ /api/dca-strategies`, hourly crons `run-subscriptions` + `run-dca` in [api/cron/[name].js](api/cron/%5Bname%5D.js), schema [api/_lib/migrations/20260813191500_recurring_payment_lifecycle.sql](api/_lib/migrations/20260813191500_recurring_payment_lifecycle.sql) | Live | One signed ERC-7710 permission, then money moves on a schedule: a subscription transfers a fixed USDC amount to an agent's wallet each period, a DCA strategy swaps the same amount into a token through Uniswap V3. `/recurring` is the whole lifecycle in one place (create, pause, resume, cancel, per-charge history) plus an Incoming tab scoped by agent ownership rather than by payer, so a creator sees what is being paid in. Every attempt is written to `subscription_charges` / `dca_executions`, and one shared classifier decides what a failure means: a revoked or expired permission pauses the schedule with the reason attached, a network blip releases the period claim and retries for three ticks, a timeout is never retried (the only failure that could double-charge), a diverged DCA quote skips the period for free, and a platform-side relayer outage never counts against the owner at all. Settlement needs `AGENT_RELAYER_KEY` + `RPC_URL_<chainId>` on the deployment; DCA creation needs `DCA_ALLOWED_TOKEN_OUT` + `DCA_CHAIN_ID`. Docs: [docs/recurring-payments.md](docs/recurring-payments.md). Tests: [tests/recurring-charge-outcomes.test.js](tests/recurring-charge-outcomes.test.js), [tests/api/recurring-subscription-cron.test.js](tests/api/recurring-subscription-cron.test.js) |
diff --git a/pages/deployments.html b/pages/deployments.html
index 79c50e0a5..fb1c7d180 100644
--- a/pages/deployments.html
+++ b/pages/deployments.html
@@ -57,6 +57,7 @@
<strong>Metaplex Core</strong> agent mints on Solana, the moment each one confirms. Real deployments only,
crawled straight from chain logs.
</p>
+ <p class="dp-deploy-cta"><a href="/deploy-onchain">Deploy yours on-chain →</a></p>
<div class="dp-net" role="tablist" aria-label="Network">
<button type="button" class="dp-net-btn active" data-network="mainnet" role="tab" aria-selected="true" data-i18n="deployments.mainnet">Mainnet</button>
<button type="button" class="dp-net-btn" data-network="testnet" role="tab" aria-selected="false" data-i18n="deployments.testnet">Testnet</button>
diff --git a/src/deployments.css b/src/deployments.css
index eeb69c69d..63de0060b 100644
--- a/src/deployments.css
+++ b/src/deployments.css
@@ -25,6 +25,18 @@
.dp-sub { max-width: 640px; margin: 0 auto; color: var(--ink-dim, #999); font-size: var(--text-lg, 1.02rem); line-height: 1.5; }
.dp-sub strong { color: var(--ink, #e8e8e8); font-weight: 600; }
+/* Deploy CTA: the feed's one action, straight to /deploy-onchain. */
+.dp-deploy-cta { margin: var(--space-md, 16px) 0 0; }
+.dp-deploy-cta a {
+ display: inline-block; font-size: var(--text-sm, .85rem); font-weight: 600; text-decoration: none;
+ color: var(--ink-bright, #fff); padding: 9px 20px;
+ border: 1px solid var(--stroke-strong, rgba(255,255,255,.16)); border-radius: var(--radius-pill, 999px);
+ background: var(--surface-2, rgba(255,255,255,.05));
+ transition: border-color .14s ease, background .14s ease;
+}
+.dp-deploy-cta a:hover { border-color: var(--ink-dim, #888); background: var(--surface-3, rgba(255,255,255,.08)); }
+.dp-deploy-cta a:focus-visible { outline: 2px solid var(--accent, #fff); outline-offset: 2px; }
+
/* Network toggle */
.dp-net { display: inline-flex; gap: 2px; margin-top: var(--space-md, 16px); padding: 3px; background: var(--surface-1, rgba(255,255,255,.03)); border: 1px solid var(--stroke, rgba(255,255,255,.08)); border-radius: var(--radius-pill, 999px); }
.dp-net-btn { appearance: none; font: inherit; font-size: var(--text-sm, .8rem); font-weight: 500; cursor: pointer; color: var(--ink-dim, #888); background: transparent; border: none; border-radius: var(--radius-pill, 999px); padding: 6px 16px; transition: color .14s ease, background .14s ease; }