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.
Forge-Off: community voting on the Forge
Forge-Off turns the passive "Fresh from the Forge" strip on /forge into a live, competitive board. Every public creation can be upvoted, the strip can be re-sorted from newest to most-voted, and the top model each week is crowned into a permanent hall of fame that feeds the Sketchfab showcase.
It is auth-free, like the rest of the Forge: one vote per browser, no login.
A vote is keyed to the same anonymous browser id (forge:cid) the Forge already
uses to scope "Your creations", so a visitor's own upvotes light up across the
strip without an account.
For visitors
On the "Fresh from the Forge" section of /forge:
- Upvote: each card has an upvote pill (chevron + count). Tap it to vote, tap again to remove your vote. The count is the whole community's; the filled state is only yours. The button is optimistic and reconciles against the server tally, so a double-tap or a slow network never leaves it wrong.
- Fresh / Top this week: a toggle in the section header. Fresh is the historical newest-first, visual-first strip. Top this week is the Forge-Off board: the most-voted public models created during the current Forge-Off week (Monday→Monday UTC), highest first.
- The weekly winner: every Monday the top-voted model of the week just ended is crowned permanently. Later votes never rewrite a past week's winner.
The same strip and voting appear on the signed-in /forge-studio surface.
API
Cast or remove a vote
POST /api/forge-vote
Content-Type: application/json
x-forge-client: <stable browser id>
{ "creation_id": "<uuid>", "vote": true } # upvote
{ "creation_id": "<uuid>", "vote": false } # remove your vote
Response:
{ "ok": true, "creation_id": "<uuid>", "vote_count": 5, "voted": true }
vote_countis the fresh authoritative tally (recomputed from the vote table, never a drifting counter).votedis your state after the call.- Voting is idempotent: a second upvote from the same browser is a no-op.
- A missing or shared (
anon) client id is rejected400 no_client_id: a real vote needs a real, unique voter so the tally means something. - Votes are only accepted on public, finished, non-rejected creations. Anything
else returns
404 not_votable. - An invalid
creation_idreturns400 invalid_creation.
Rate limit: 120 votes / 10 min per IP (the one-vote-per-creation primary key already caps real influence; this just blunts carpet-voting).
Read the board
GET /api/forge-gallery?scope=community&sort=top&window=week&limit=24
x-forge-client: <stable browser id> # optional, resolves your `voted` flags
sort=fresh(default): newest, visual-first.sort=top: ranked byvote_countdesc,created_atdesc.window=week: withsort=top, narrow to the current Forge-Off week.- Each returned creation carries
vote_countand, when a client id is sent,voted. An anonymous read is CDN-cacheable; a voter-aware read isprivate, and the response varies onx-forge-client, so the edge never hands the anonymous copy to a browser that sent a client id. - The read is CORS-open to any origin: it is the same public catalogue the
standalone AR studio (npm:
3d-ar-studio) shows as its Community tab from whatever page embeds it. Rate limiting is the control, not the origin.
How it fits together
visitor taps upvote
│ POST /api/forge-vote (voter = hashed forge:cid)
▼
forge_votes ──(recompute)──► forge_creations.vote_count
│ │
│ GET ?sort=top&window=week │ Mon 00:07 UTC
▼ ▼
"Top this week" board api/cron/forge-off-crown
│ writes the week's winner
▼
forge_board_winners ──► Sketchfab showcase
The Sketchfab showcase cron reads forge_board_winners and
vote_count to decide what to distribute to the official three.ws Sketchfab
account. Before Forge-Off shipped, nothing wrote votes or crowned winners, so
that pipeline's strongest tier was starved; voting + the weekly crown feed it.
Implementation
| Piece | Where |
|---|---|
| Vote / board store logic | api/_lib/forge-store.js: castVote, removeVote, listShowcase (sort/window/voter), forgeOffWeekStart |
| Vote endpoint | api/forge-vote.js |
| Board read | api/forge-gallery.js (scope=community) |
| Weekly crowning cron | api/cron/forge-off-crown.js (7 0 * * 1) |
| UI (vote button, Fresh/Top toggle) | src/forge-showcase.js and its /forge-studio twin src/forge-studio/forge-showcase.js |
| Schema | migration 20260625120000_forge_board.sql: forge_votes, forge_creations.vote_count, forge_board_winners |
A creator deleting their own creation (DELETE /api/forge-creation?id=, the
two-tap delete on a "Your creations" card) takes its forge_votes rows with
it; a past week's forge_board_winners row survives with its creation
reference cleared, so the hall of fame never loses a week.
Backfill a past week's winner (owner): GET /api/cron/forge-off-crown?week=YYYY-MM-DD
(add &dry_run=1 to preview). Authorized with CRON_SECRET.