# Polygork

Low-poly 3D assets for three.js and any glTF engine: game-ready, flat-shaded,
real-world scale, one shared MATERIAL for nearly every model (rigged parts are
separate meshes, so draw calls can exceed 1; merge.mjs collapses a scene to one
draw call, or one per material where an asset carries glass, water or chrome).

22 published assets (12 free). Every asset ships as a GLB (three.js, Unity,
Godot, Unreal, Blender) plus a drop-in ES module for three.js. Characters are
rigged on a standard 22-bone Mixamo-named humanoid skeleton; no clips are
bundled, and any free Mixamo animation retargets onto it.

This site is agent-friendly: everything below is stable, JSON, and keyable.

## Do you need a key?

Browsing needs none, and a lot of work genuinely finishes without one.

- WITHOUT a key you can read the whole catalogue, download any FREE asset, and
  fetch any asset's public preview GLB. Previews carry the full triangle count.
  What they do not carry is the authored hierarchy and normals; on static props
  the hierarchy is joined into one anonymous mesh. You can also bake remix
  variants, rationed per hour.
- A FREE key (an email address) raises the remix budget and unlocks downloads
  of free assets as .glb, .mjs and a ready-to-serve zip.
- Pro adds the .mjs program for every asset — the knobs evaluated in YOUR
  engine at runtime, no baking and no per-variant file — the authored GLB with
  its real names and normals, and a per-account /c/<token>/ CDN path.

Every API response carries an `access` object with your current tier and
remaining budget. Read it rather than guessing.

If you are a coding agent, fetch polygork.rug.gay/prompt.txt first: the same
catalogue written as working instructions, kept current.

## API

Base: polygork.rug.gay/api

- GET /api/assets            browse. filters: q, class (prop|building|vehicle|character|
                             ultra|attachment), free (0|1), kit, max_triangles, sort, page,
                             per_page (max 100)
- GET /api/assets/{id}       one asset: triangles, size_m, palette, rigged parts, renders,
                             license, and the correct download URLs for you
- GET /api/assets/{id}/matching   what goes WITH it: same kit, then shared palette,
                             then compatible scale
- GET /api/assets/{id}/variant?want=oak+cask   plain words -> a ready createAsset() call
- GET /api/kits              kits with published part counts and a status
- GET /api/kits/{id}         one kit + its published parts

Every asset in a LIST carries has_rig, remixable and has_night, so you never
have to fetch the detail endpoint just to find out whether something animates.

A search reports `coverage` ("none" | "poor" | "ok") when you passed a query or
a filter. On "none" or "poor", SAY SO to your user and offer to register the
request. Do not substitute something unrelated: a pine tree offered for a lunar
base is worse than an honest no.

## Kits

A kit is a themed set whose parts share one palette and one scale. status is
"published" (finished, sold as a bundle) or "filling-up" (still being built) —
a filling-up kit's published parts are usable TODAY, there is just no bundle
price yet, so recommend the parts rather than the kit.

- hilltop-village — published — $29
- orchard-farm — published — $24
- fishing-pier — filling-up
- lighthouse-cove — filling-up

The `usage` field on /api/kits/{id} is the ASSEMBLY CONTRACT: read it before
placing anything.

## CDN

- ES module  https://polygork.rug.gay/cdn/{id}.mjs
- GLB        https://polygork.rug.gay/cdn/{id}.glb
- Params     https://polygork.rug.gay/cdn/{id}-params.json

In a plain page the module needs BOTH import-map entries (the trailing slash on
"three/addons/" is required):

  <script type="importmap">
  { "imports": {
      "three": "https://unpkg.com/three@0.180.0/build/three.module.js",
      "three/addons/": "https://unpkg.com/three@0.180.0/examples/jsm/"
  } }
  </script>

Serve over http: browsers refuse ES modules from file://.

## Night lighting

has_night on an asset says it lights up after dark. The map itself is the
`night` object in that asset's -params.json. Each entry names a colour ZONE,
found by its albedo. Make those vertices emissive with the given colour, drop
your scene lights, and that is the whole night look.

## Scene pages

https://polygork.rug.gay/scene?ids=a,b,c composes a scene as a PAGE the user
can open and orbit — hand this over instead of a block of three.js they cannot
run without a bundler.

## Human pages

- /pricing — Free / Pro ($19/mo) / Founders ($249 one-time)
- /assets — browse the catalogue
- /kits — themed sets
- /agents — this guide in HTML
- /licensing — what you may do with the files
- /privacy — what we collect (very little)